COMMUNICATIONS STANDARDS REVIEW · COMMUNICATIONS STANDARDS REVIEW Volume 5, Number 11 December...

COMMUNICATIONS STANDARDS

REVIEW

Volume 5, Number 11 December 1994

IN THIS ISSUE

The following reports of recent standards meetings represent the view of the reporter and are not official, authorized minutes of the meetings.

TR-41.6, Wireless User Premises Equipment (WUPE), September 12 – 16, 1994, Montreal, Quebec....................3TR-41.6 Meeting Roster, September 12 - 16, 1994, Montreal, Quebec..................................................4

TR-45.2, Inter-System Operations Standards, October 17 – 29, 1994, Tampa, FL..........................................5WG I Message Encoding and Protocol Selection..............................................................................5WG II & III Automatic Roaming and Call Delivery/Enhanced Handoff Requirements.................................8WG V Exceptional Transactions and Administrations Support............................................................8WG VI International Applications...............................................................................................8WG VII PSTN/ISDN Interface.....................................................................................................8TR-45.2 Meeting Roster, October 17-29, 1994, Tampa, FL...............................................................9

TR-41.6, Wireless User Premises Equipment (WUPE), October 25 – 28, 1994, Key West, FL............................9PN-3400, WCPE Interoperability Ad Hoc......................................................................................10

Q21/8 Interim Meeting, Specification of an ISDN PCI Interface, November 2 – 4, 1994, Paris, France................13Communications Standards Review Also Publishes:.........................................................................14

TR-46, Mobile & Personal Communications 1800 Mhz Standards, November 7 – 11, 1994, Austin, TX..............15TR-46.1.1 Service Requirements and Descriptions..........................................................................16TR-46.2.1 Network Signaling....................................................................................................16TR-46.2.1.2 ISDN Based A-Interface............................................................................................16TR-46 Partial Meeting Roster, November 7 – 11, 1994, Austin, TX.....................................................18

ITU-T SG 8 Rapporteur’s Meeting for Q5 and Q19, November 14 – 18, 1994, Bethesda, MD.............................19Q5/8 Group 3 Facsimile Apparatus..............................................................................................19Items Common to Q4/15 & Q5/8................................................................................................22Q19/8 Modulation Techniques for Telematic Services.......................................................................22Roster of Q5/8, Q9/8 and Q19/8 Rapporteur’s Meeting, November 14 – 18, 1994, Bethesda, MD................24

TR-45.5, Wideband Spread Spectrum Digital Technologies, November 14 – 18, 1994, Coronado, CA................25WG I User Needs and Services....................................................................................................26WG I TG I Speech Services........................................................................................................26WG I TG II Analog Issues.........................................................................................................27WG I TG IV Feature Requirements...............................................................................................27WG I TG V Data Services..........................................................................................................28WG II Signaling Protocols.......................................................................................................28WG II TG III Call Processing, Signaling Formats, and Protocols.........................................................28WG III Physical Layer.............................................................................................................28TR-45.0.A Ad Hoc Authentication Group......................................................................................29

Rapporteur’s meeting of Q1/8 Applicom, November 17 – 18, 1994, Sunnyvale. CA......................................30Roster of Q1/8 Rapporteur’s Meeting, November 17 – 18, 1994, Sunnyvale, CA.....................................31

Q3/15 RApporteurs’ Meeting On Audio Visual–Multimedia Systems, November 28 – 30, 1994, Middletown, NJ...32Q3/15 Rapporteur’s Meeting Roster, November 28 – 30, 1994, Middletown, NJ.....................................35

December, 1994 Vol. 5.11 Copyright © CSR 1994 1

COMMUNICATIONS STANDARDS REVIEW

TR-30.1, Modems, December 9, 1994, Orlando, FL...............................................................................36TR-30.1 Meeting Roster, December 9, 1994, Orlando, FL.................................................................36

Q1/14 Associate Rapporteurs Meeting for V.8bis December 9 – 11, 1994 Orlando, FL...................................37Q1/14 V.8bis Rapporteurs Meeting Roster, December 9–11, 1994, Orlando, FL......................................38

SG 14 Working Party 1 , Data Communications over the GSTN, December 12 – 16, 1994, Orlando, FL...............39Q1/14 V.34.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39Q1/14 V.SAVD...... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39Q1/14 Rapporteur’s Final Meeting..............................................................................................42Q2/14 DTE-DCE Protocols........................................................................................................43Q5/14 ISDN Terminal Adapters...................................................................................................44Q6/14 DTE-DCE interfaces........................................................................................................44Q7/14 V.25ter... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44Q10 V.56 Network Transmission Model for Evaluating Performance over 2-wire Voice Grade Connections.....45Working Party Plenary.............................................................................................................45Commentary by Dick Brandt......................................................................................................46SG 14 WP 1 Roster, December 12 – 16, 1994, Orlando, FL................................................................46

Acronym Definitions.....................................................................................................................471995 Meeting Schedules as of December 19, 1994................................................................................49

Communications Standards Reviewregularly covers the following committee meetings:

TIA (USA): TR-29 TR-45TR-30 TR-46TR-41

ITU T: SG 8 SG 15 / 1 and 15 / 2(CCITT) SG 14 (Formerly SGXVII)

2 Vol. 5.11 Copyright © CSR 1994 December 1994


REPORT OF TR-41.6, WIRELESS USER PREMISES EQUIPMENT (WUPE)SEPTEMBER 12 – 16, 1994, MONTREAL, QUEBEC

TR-41.6/94-09-125 (S. Kuan, Northern Telecom) is the proposed WCPE Networking Reference Configuration inflow chart form. It identifies interfaces between PCS switching centers and public or private networks. A small groupwill continue to work on this model.

TR-41.6/94-09-124 (S. Kuan, Northern Telecom) contains the proposed definition for interoperability for both lineinteroperability and private/public interoperability. It was revised to reflect the TR-41.6 charter and will be input forthe next meeting.

TR-41.6/94-09-122 (D. Steer, Northern Telecom) outlines suggested additions and changes to the RES (RadioEquipment and Systems) Approval Test Specification (follows I-ETS 300-176, DECT testing) to be used for WirelessUser Premises Equipment approval air interface testing. A general requirement was agreed to include ConformanceTest Specification within the master plan for each project.

TR-41.6/94-09-113 (T. Sterkel, AT&T) proposes a V&V process to be applied to any WUPE standard. It is basedupon a parallel procedure in TR-46.3/T1P1 JTC. It was reviewed and updated, and a decision was made to add it to allproject schedules.

TR-41.6/94-09-119 (N. King, Rolm) proposes requirements on wireless user premises equipment that will assurethat Emergency Access service is adequately supported. It is based upon a position paper agreed between APCO,NENA, NASNA, and PCIA with some changes of emphasis. There was a detailed discussion showing how the currentPCIA document may map into WUPE. It was decided to update the WUPE standard as needed to incorporate the resultsof P&A JEM and FCC work.

TR-41.6/94-09-121 (D. Steer, Northern Telecom) provides the draft text of the RF power measurement procedurefor devices operating in the Unlicensed PCS band that is currently under discussion within the ANSI/IEEE C63.7subcommittee. It was presented for information.

TR-41.6/94-09-123 (S. Kuan, Northern Telecom) proposes the organization for WUPE Network Layerspecification following DECT Network Layer.

PACS-WUPE

TR-41.6/94-09-141 (E. Ornelas, NEC) is the PACS-WUPE Ad Hoc report, including a complete table of contentsfor the three proposed standards, Personal Access Communications (PAC) Systems-Wireless User Premises Equipment– Common Air Interface Interoperability Standard, the Minimum Performance Standards for Personal Stations, and theMinimum Performance Standards for Cell Stations. TR-41.6/94-09-142 (E. Ornelas, NEC) contains the three Pro-ject Request and Authorization forms. The ad hoc established a charter, scope, and work plan (TR-41.6/94-09-143 ). In addition, they began work on proposed baseline text for PAC-U, Sections 1 through 7 (TR-41.6/94-08-107R1 , Panasonic, NEC, and Hitachi). It describes extensions to the licensed band PACS for operation in theunlicensed bands (PAC-U).

PCI (PERSONAL COMMUNICATIONS INTERFACE) PROJECT

It was noted that TR-46 has officially distributed the TR-41/TR-46 Memorandum of Understanding (MOU) and iscollecting official comments on it, but it has not yet been signed off.

TR-41.6/94-09-138 is the report of the PCI (Personal Communications Interface) Ad Hoc’s first meeting. TR-41.6/94-09-127 , the PCI Project Request and Authorization form, was agreed with one correction to align with theMOU between TR-41 and TR-46. TR-41.6/94-09-128 (S. Godo, Northern Telecom) is the proposed scope andmission for the PCI project, “Development of a draft PCI interoperability standard for the unlicensed band, based onthe CT2 standard but adapted to accommodate the FCC Part 15D Etiquette Rules.”

TR-41.6/94-09-126 (S. Godo, Northern Telecom) is a proposed work plan for PCI. Milestones include:• Initial baseline text complete: March 6, 1995• Stable draft ready: May 1, 1995• Ballot: June 12, 1995• Ballot resolution complete: September 11, 1995

TR-41.6/94-09-129 (S. Heeralall, Northern Telecom) is a draft table of contents for the PCI interoperabilitystandard.

December 1994 Vol. 5.11 Copyright © CSR 1994 3


OCDMA

TR-41.6/94-09-140 (H. Chen, Stanford Telecom) is the OCDMA (Orthogonal CDMA) Project Request andAuthorization form; TR-41.6/94-09-139© (H. Chen, Stanford Telecom) is the OCDMA system description. It isbased upon the orthogonal direct sequence CDMA system which offers significant capacity and voice quality advantagesover conventional, quasi-orthogonal CDMA. Specifications include 1910-1930 MHz, 16 kbit/s voice compression,transmitted data rate 41.6 kbit/s, chip rate 665.6 kcps.

PN-3400, WCPE INTEROPERABILITY STANDARD

TR-41.6/94-09-130 (P. Bligh, Mitel) is the proposed work plan for PN-3400, the WCPE interoperability standard.This is very similar to TR-41.6/94-09-126 , the proposed work plan for PCI, above.

TR-41.6/94-09-114 (T. Sterkel, AT&T) is a proposed table of contents for the WCPE interoperability standard.Attention was called to the proposed change in nomenclature for the Access Profile to a Customer Premises AccessProfile (CPAP), a Large Cell Access Profile (LCAP), and a Data Services Access Profile.

TR-41.6/94-09-133 (G. J. Wimpenny, Symbionics) is a working paper on WCPE Physical Layer, FrequencyChannelization. It proposes a channelization that is compliant with FCC regulations and has the additional advantageof allowing existing DECT chips to be used in single crystal designs.

TR-41.6/94-09-134 (G. J. Wimpenny, Symbionics) proposes that the North American WCPE standard be basedupon the ETSI DECT standard with appropriate modifications to the physical and MAC layers. TR-41.6/94-09-134 provides a proposal for the modified physical layer and is derived from ETSI specification ETS 300 175-2 (DECTPhysical Layer).

TR-41.6/94-09-136 (P. Murray, Ericsson) contains text edits for Section 3, Medium Access Layer, of the WCPEstandard.

It was reported that the FCC has released an Enhanced 911 memorandum. There will be an open meeting at the FCCon September 19, 1994.

TR-41.6/94-09-120© (J. Byrne, Nokia) is a proposal for the implementation of certain GAP (Generic Access Profile)features by the keypad protocol. It proposes using the keypad protocol for features such as Hold, Retrieve, and SpecificLine Selection to simplify implementation. DECT supports three methods to offer Supplementary Services but ismoving to keypad protocol for such features.

TR-41.6 MEETING ROSTER, SEPTEMBER 12 - 16, 1994, MONTREAL, QUEBEC

Peter Bligh, Mitel Chair TR-41.6

AT&T Ed Polansky Nokia Peter HarrisonAT&T TerrySterkel Northern Telecom Severin GodoEricsson, Peter Murray Northern Telecom Stewart KuanEricsson Radio Systems Dag Åkerberg Northern Telecom Jean L. PoirierFujitsu Edward “Jay” Farrell NTIA/ITS Liz PolIBM Brian Gaucher Rolm Neal J. KingMitel Peter Bligh Sharp Rock ShihMotorola Rick Sagers Symbionics Henk KoopmansNEC M. Nakagawa Symbionics GerardWimpennyNEC Paul Weismantel



REPORT OF TR-45.2, INTER-SYSTEM OPERATIONS STANDARDSOCTOBER 17 – 29, 1994, TAMPA, FL

The primary work, during these two weeks of meetings, was centered on the following:• Walk-through of IS-41-C (PN-2991, Cellular Radio Telecommunications Intersystem Operations).• Resolution to put IS-41-C (PN-2991) out for ballot in 1994.• PN-2991 was about one-half complete on the walk-through, and it was recommend that it not go out for ballot at

this meeting. Areas yet to be reviewed include: Short Message Service (SMS) text changes (estimated 12 decisionpoints), geographical authorization, chapter 5 with forty open issues, and sections 3, 8, and 9 of chapter 6.

• Resolving Ballot responses for IS-52-A (PN-3166), “Uniform Dialing Procedures and Call Processing Treatment forCellular Radio Telecommunications.”

• Resolution to complete ballot responses for PN-2799, “Cellular Feature Descriptions,” in 1994.• All ballot responses for SP-2985 (TSB-41, Technical Notes for IS-41B) were resolved; it was recommended to be

forwarded to TIA for publication pending the editor’s completion of changes.

TR-45.2/94.10.17.05 (CTIA) proposes developing an industry-wide migration plan for IS-41-B by amplifying thecurrently published TSB-56-A (Application Level Testing for IS-41 A). Various vendors have been involved with thiseffort and are in full support.

TR-45.2/94.10.17.06©, TR-45.2 Status Regarding International Roaming (C. Blum, AT&T), is a draft presentationprepared for the International Roaming Joint Experts Meeting to be held during the week of November 7, 1994 inWashington, DC. Recommendations include: no changes to existing EIA/TIA-553 equipment, and that future airinterface compatibility standards make provision for system access on the basis of a 15 digit IMSI as per ITU-T E.212.

TR-45.2/94.10.21.03© (P. Musgrove, McCaw) proposes that TR-45.2 should add to its work plan for 1995 the LawEnforcement Intercept capability currently being worked in the Alliance for Telecommunications Industry Solutions(ATIS), Electronic Communications Service Providers (ECSP), and Wireless Cellular Action Team (WCAT). It wasrecommended that the Law Enforcement Intercept capability should be included in the IS-53 Revision B and IS-41Revision D work plans.

TR-45.2/94.10.21.05 is a draft report from the Ad Hoc Group on Prioritizing and Coordinating of StandardsActivities, dated June 23, 1994. This document proposes processes for prioritizing standards activities, and forcoordinating work activities among the Sections of TIA’s Mobile & Personal Communications Division. It waspresented for information and consideration.

TR-45.2/94.10.28.05 (CTIA) is a project number application for a project to facilitate network interconnection ofIS-41 network elements. The tests will be automated whenever possible. The project will become aTelecommunications Services Bulletin (TSB), not an Interim Standard (IS). The work will be done outside of the TR-45.2 subcommittee, but final review and validation will be done by TR-45.2.

TR-45.2/94.10.28.06 is part of a Notice of Proposed Rule Making (NPRM) from the FCC regarding a revision ofthe Commission’s rules to ensure compatibility with enhanced 911 emergency calling systems. The NPRM wassubmitted for information only.

TR-45.2/94.10.21.02 provides an introduction and short overview of IS-41.

PN-3166, IS-52-A, U NIFORM DIALING PROCEDURES AND CALL PROCESSING

TR-45.2/94.10.17.04 and TR-45.2/94.10.17.04A contain ballot responses to PN-3166, “Uniform DialingProcedures and Call Processing Treatment for Cellular Radio Telecommunications,” (to become IS-52-A). There were26 responses: 11 “Yes,” 9 “Yes with Comment,” 3 “No,” and 3 “No Comment.” All “No” ballots were resolved; all“Yes with Comments” were reviewed except for the Alcatel SEL ballot, which will be handled at the next meeting.

WG I MESSAGE ENCODING AND PROTOCOL SELECTION

TR-45.2.1/94.10.17.03© through TR-45.2.1/94.10.17.08© were submitted by A. Boudreau (Ericsson) as proposedbaseline text changes to IS-41-C (PN-2991) as follows. All the contributions were accepted for inclusion in IS-41-C.Modifications are noted.

• TR-45.2.1/94.10.17.03©: MessageWaitingNotificationType parameter definition. It was accepted with theremoval of the Count Indication (CI) field.

• TR-45.2.1/94.10.17.04©: Procedures associated with the Authentication Failure Report message.



• TR-45.2.1/94.10.17.05©: Procedures associated with the Authentication Status Report message.• TR-45.2.1/94.10.17.06©: Procedures associated with the Authentication Directive Report message. It adds the

deny access parameter that corrects an error in TSB-51.• TR-45.2.1/94.10.17.07©: Procedures associated with the Flash Request message. It was accepted with some

modifications.• TR-45.2.1/94.10.17.08©: Procedures associated with the Authentication Request message.

TR-45.2.1/94.10.17.10© (C. Ishman, Motorola) contains Error Code Tables that were missing from the October 3,1994, version of the PN-2991.6 V&V text. Each table was reviewed with lengthy discussions on the type of errorreturns for the messages.

TR-45.2.1/94.10.17.14© (K. Carlson, Synacom) is the PN-2991.6 baseline text Revision 2 editing report.

TR-45.2.1/94.10.17.11© (M. Gallagher, Editor) describes the state of PN-2991.3 baseline text revision 2. The editorprovided a list of open issues that were discussed; most were accepted.

TR-45.2 .1 /94 .10 .17 .13 (K. Carlson, Synacom) proposes a form for the PN-2991 Validation and Verification(V&V) process. It also proposes a partitioning of the review process. It was agreed to use the proposed form to recordverbal comments, and to use contributions as the main basis for changes.

TR-45.2 .1 /94 .10.17.12 , Automatic Roaming Alternate Procedures (D. Crowe, Alcatel), proposes Stage II andStage III text on alternate procedures for several features defined in PN-2977 baseline (IS-53-A). It claims that theseprocedures have several advantages over the existing ones, including:• Features are controlled by the home system, allowing more flexibility in combining and enhancing PN-2977

(Cellular Features Description) features while retaining seamlessness.• Amount of inter-system signaling is reduced.• The complexity of IS-41 transactions is reduced, allowing faster development of inter-system operations.• The common requirements for MSC’s to support roaming are reduced since the user interface is always provided by

a system chosen by the HLR.It also acknowledges at least one disadvantage of this approach. It requires more use of trunks to perform dialogs,possibly long distance trunks. TR-45.2 .1 /94 .10.17.12 claims that this tradeoff is acceptable, since thedevelopment of more complex procedures can occur in the future for any features that are heavily used such that theeffort of optimization becomes worthwhile. After discussion, the contribution was withdrawn because the flowdiagrams had some incorrect concepts, but the basic concept was interesting to the group. TR-45 .2 .1 /94 .10 .17 .31 (D. Crowe, Alcatel) is a revision of TR-45.2 .1 /94 .10.17.12 . It was still not accepted bythe group.

TR-45.2.1/94.10.17.09© (C. Ishman, Motorola) contains Motorola’s post re-ballot comments for SP-2985A+ (IS-41Revision B, Technical Notes TSB-41). Several recommended changes were discussed; most of the comments wereaccepted for publishing in TSB-41 (SP-2985A++).

TR-45.2.1/94.10.17.22© (T. Jacobson, AT&T) proposes editorial changes only to PN-2985A+.

TR-45.2 .1 /94 .10 .17 .18 (T. Brooks, Northern Telecom) recommends changes to SP-2985 for decision pointnumber 11: De-registration (loss of radio contact does not mean that the mobile has powered down).

TR-45.2 .1 /94 .10 .17 .15 (T. Brooks, Northern Telecom) recommends a name change for the TrunkGroupIdentifierparameter and an additional type indicating no termination charges for the subscriber. It also recommends theclarification of the Roamer Port Access value.

TR-45.2 .1 /94 .10 .17 .16 (T. Brooks, Northern Telecom) recommends a simpler structure for the “VLR ReceivingRegistrationNotification INVOKE” procedure and proposes some corrections to the text.

TR-45.2 .1 /94 .10 .17 .17 (T. Brooks, Northern Telecom) recommends the addition of a four bit “Digits” value tothe OriginationTriggers parameter that allows the service provider to indicate that an OriginationRequest should belaunched for dialed numbers having fewer than X digits. Many changes were made to the document before the groupaccepted this modification.

TR-45.2.1/94.10.17.19© (D. Velte, Qualcomm) provides procedures to support SMS messages delivery for mobilestations operating in “Sleep Mode” and to support the SMS_NotificationIndicator parameter. The concept was acceptedby TR-45.2.1.



TR-45.2.1/94.10.17.20© (P. Musgrove, McCaw) proposes that a Message Center (MC) should not be burdened withthe knowledge of the ESNs corresponding to all served MINs. It recommends that the ESN should be changed frommandatory to optional in the SMSRequest message. The ESN is currently a mandatory parameter in the SMSRequestmessage sent from the MC to an HLR to request an SMS address for a particular SMS subscriber. The contributionwas accepted; the editor will make the necessary changes to make ESN optional in the MC.

TR-45.2.1/94.10.17.21© (P. Musgrove, McCaw) proposes to allow “*” and “#” signs to be valid destination digits.The current stage III text describing DestinationDigits does not allow them to be used as valid digits. These digitsmay, however, be useful for certain applications. For example, to support routing calls immediately to voice mail fora call delivery attempt to an inactive subscriber, the HLR could send DestinationDigits to a VLR/MSC with a “#” signprefixing the called number to indicate that a call should be directed to a local voice mail system that will not promptthe calling user for the called number. Similar applications for the “*” sign may be able to be used by the serviceproviders.

TR-45.2.1/94.10.17.23© (K. Carlson, Synacom) proposes parameter definitions for Short Message Services (SMS).It also proposes an SMS global title and recommends moving Section 5 to an appendix. AnSMS_NotificationIndicator parameter is included with new values to solve some problems when SMS is not available.Some parts were sent to the editor, and more study is to be done on the global title suggestion. A new contributionwill be submitted for the items that were discussed and supported.

TR-45.2 .1 /94 .10 .17 .24 (K. Carlson, Synacom) provides editorial comments on the SMS operations in Section8.

TR-45.2.1/94.10.17.25© through TR-45.2.1/94.10.17.30© were submitted by S.S. Chander (AT&T). All were sentto the SMS editing team for submission to the working group:

• TR-45.2.1/94.10.17.25© recommends additional Cause Codes for SMS.

• TR-45.2.1/94.10.17.26© recommends a default SubSystemNumber for Short Message Delivery processes related tothe three operations of SMDPP, SMDFWD and SMDBACK.

• TR-45.2.1/94.10.17.27© recommends that when a VLR passes a REGNOT to the HLR, the PC of the ServingMSC and the SSN of the SMD process within the Serving MSC must be included. This will enable the HLR tofully formulate and return the SMSA address with the (PC_SSN) in response to a SMSRequest from the MSC.

• TR-45.2.1/94.10.17.28© proposes clarifications with respect to MINs/ODAs and Teleservice IDs for SMS. Itproposes clarifications with respect to how the Original Destination Address may be populated. It also proposes aformat for Teleservice IDs for SMS.

• TR-45.2.1/94.10.17.29© proposes Operations Code values for the SMS operations of SMDPP, SMDFWD,SMDBACK, SMSREQ, and SMSNOT.

• TR-45.2.1/94.10.17.30© proposes Parameter Identifier codes for SMS parameters.

TR-45.2.1/94.10.17.32© (J. Crollick, GTE) recommends adding the SystemAccessType parameter to theQualificationRequest message to eliminate confusion and provide needed information.

TR-45.2.1/94.10.17.33© (T. Jacobson, AT&T) proposes additions and modifications to PN-2991.5 and to PN-2991.6that are needed in order to add VLR, HLR, and MSC Identification Number parameters (i.e., VLRIN, HLRIN,MSCIN). The VLRIN and HLRIN parameters would be used as the VLR and HLR identity. Inclusion of theseparameters will facilitate routing in complex configurations and in multiple network configurations that requireinternetworking or gateway functions. Agreement was reached to put these into the call delivery set of messages.

TR-45.2.1/94.10.17.34© (M. Houde, Ericsson) proposes changes to the SMS messages and parameters definition(revision C). It is based upon a Synacom contribution entitled, “SMS parameters definition (revision C),” that wasnot submitted. The issue of SMS_DestinationAddress and SMS_OriginationAddress was discussed. The text willremain as it currently stands.

TR-45.2.1/94.10.17.35© (M. Houde, Ericsson) proposes changes to the SMS procedures (revision C). It is basedupon a Synacom contribution entitled, “SMS Procedures (revision C),” TR-45.2.1/94.10.17.23©. The addition of bitsfor SMS_TerminationRestriction provides for more or less restriction as may be required. A new contribution will besubmitted for what was discussed and supported.



TR-45.2.1/94.10.17.36© (S.S. Chander, AT&T) contains comments and proposed changes to SMS operationsincluding:• Include “SMS_DestinationAddress” and “SMS_OriginatingAddress” as optional parameters in cases where they are

not carried by the underlying data transport• Change “NoChargeIndicator” to “ChargeIndicator”• “SMS_OriginalDestinationAddress” to be optional except when it is different than the MIN• Replace SMSDeliveryForward and SMSDeliveryBackward with a single common operation of

SMSDeliveryPostHandoff (SMDPHO)This contribution was not discussed, and will be carried forward for submission to the working group.

TR-45.2.1/94.10.17.37© (D. Munsinger and A. Holcman, Qualcomm) identifies Stage III requirements to supportcomplex IS-41-C parameters by defining new parameters that “encapsulate” existing handoff parameters. It was carriedforward to the next meeting.

TR-45.2.1/94.10.17.38© (T. Jacobson, AT&T) proposes the addition of the Redirection Directive operation to IS-41-C. The Redirection Directive operation offers enhanced traffic channel services through an Adjunct MSC that iscapable of supporting service control logic, voice responses, voice recognition, DTMF tone detection, voice messagestorage, etc. The Redirection Directive operation enables the Adjunct MSC to direct the Originating MSC to forwardthe call to a destination directory number selected by the Adjunct MSC’s service control logic.

WG II & III AUTOMATIC ROAMING AND CALL DELIVERY/ENHANCED HANDOFFREQUIREMENTS

TR-45.2 .2 /94 .10.20.01 is the meeting agenda with a list of 23 open issues attached. Most of these issues wereclosed during the meeting.

TR-45.2.2/94.10.20.03© (D. Velte, Qualcomm and M. Houde, Ericsson) proposes a common CDMA and TDMAsupport for terminal sleep mode. It was sent to the SMS editing team for stage II and III documentation.

TR-45.2 .2 /94 .10.20.04 (C. Blum, AT&T and J. Juliano, SNET Mobility) proposes changes in the stage II callflows to support the sharing of PIN with the VLR. The changes include:• Modify Registration Notification INVOKE to include Transaction Capability Parameter.• Define a new value (2 bits) in Transaction Capability to indicate:

- VLR supports SPINI- VLR accepts PIN

• On PIN registration, if a new PIN is accepted, HLR informs VLR of PIN change via Qualification Directive(Profile) -- Qualification Directive can also be used to revoke the PIN.

• Modify Profile to include PIN.• PIN parameter to be defined similar to Digits parameter, including number of digits and variable number of digits.

WG V EXCEPTIONAL TRANSACTIONS AND ADMINISTRATIONS SUPPORT

TR-45.2 .5 /94 .09.15.04 is a list of 44 potential features or services for PN-3362 (IS-53 Revision B), as a guidefor planning the work.

WG VI INTERNATIONAL APPLICATIONS

TR-45.2 .6 /94 .10.19.05 (D. Crowe, Alcatel) lists some of the NANP area codes, ITU-T E.164 country codes, andITU-T E.212 country codes that may be used to program the first three digits of a MIN. It illustrates the depth of theproblem of MIN ambiguity, especially for Central American countries that conflict when either E.164 or E.212country codes are used. In several cases, three different interpretations of one MIN are possible.

WG VII PSTN/ISDN I NTERFACE

TR-45.2.7 is calling for contributions concerning wireless emergency services, as they are related to network interfaces.



TR-45.2 MEETING ROSTER, OCTOBER 17-29, 1994, TAMPA, FL

John Marinho, AT&T Chair, TR-45.2Cheryl Blum, AT&T Vice-Chair, TR-45.2

AirTouch Comm. Huel HalliburtonAlcatel David CroweAmeritech Jean AlphonseAmeritech Jay TangAT&T Cheryl BlumAT&T Terry JacobsonBell South Cellular Thomas E. RichterBellcore Robert EphraimBellcore P. J. LouisCBIS Tony GolkaCTIA Ed HallEricsson Alain BoudreauEricsson A. Gains GardnerEricsson Michel HoudeGTE Telecom. Services Ben ChenGTE Telecom. Services Jeff CrollickGTE Telecom. Services Susan KumpfMcCaw Cellular Peter MusgraveMotorola Chuck IshmanNEC Stephen S. JonesNTI Terri L. BrooksQualcomm, Inc. Dennis VetteSNET Mobility Joe JulianoSW Bell Technology Resources Terry WattsSynacom Technology Kirk CarlsonSynacom Technology Mike Gallagher

REPORT OF TR-41.6, WIRELESS USER PREMISES EQUIPMENT (WUPE)OCTOBER 25 – 28, 1994, KEY WEST, FL

TR-41.6/94-10-160 (S. Kuan, Northern Telecom) is an update of the Reference Configuration Model from lastmeeting (TR-41.6/94-09-125). While this approach follows network models, it may be confusing to those from acellular background. A clarification showing cross references to other standards was suggested.

TR-41.6/94-10-162 (S. Kuan, Northern Telecom) contains a proposed definition for interoperability for both lineinteroperability and private/public interoperability. It is an update of TR-41.6/94-09-124 . TR-41.6/94-10-163(N. King, Siemens Rolm) proposes that the definition of interoperability stipulate that cross-vendor combinations ofequipment will actually operate together. The group agreed to combine both contributions to create a baseline for theinteroperability definition.

TR-41.6/94-10-161 (S. Kuan, Northern Telecom) is a proposed WUPE interworking definition for providing calldelivery within a private network. It also addresses the need for a common transport mechanism and the need for TR-41.6 to start addressing the Mobility Application Layer. The contribution generated substantive interest. There was anopen question as to whether PN-3400 (WCPE Interoperability Standard) includes this work. It creates the tie-in tointersystem networking and the Q-SIG standard. The need for Q-SIG as an interface, the appropriate timetables, andavailability are under review.

TR-41.6/94-10-150 (T. Sterkel, AT&T) is an update to a proposal for WUPE V&V processes (TR-41.6/94-09-113 ). It includes suggestions and a discrepancy form for review. There was an issue regarding what method ofcommunication would be used for technical issues by the V&V committee. The two choices were to create a separatecontribution or to use the V&V DDR form. Another issue is verification of the “Etiquette” compliance, and, if so, bywhat method?

TR-41.6/94-10-158 (P. Bligh, Mitel) proposes defining a standardized capability to synchronize WUPE equipmentoperating in close proximity. The group decided to evaluate opportunities for synchronization as a general WUPEcondition for all standards.



FCC NEWS

TR-41.6/94-10-155 (WINForum) contains the full text of the current FCC part 15 rules for Radio FrequencyDevices (as of July 27, 1994). A new M&O was issued by the FCC on October 20, 1994, but there was noinformation on the changes needed. There was a discussion regarding the issues created by the new FCC Part 15.323rule. A draft for the suggested clarification will be prepared for forwarding to the FCC.

PCI PROJECT

During a discussion of the PCI (Personal Communications Interface) Ad Hoc meeting, it was decided that the CT2founder’s group will be approached to include the U.S. as a territory under the Founder’s Group. This would includeIPR coverage. The V&V process will be discussed at the next meeting.

TR-41.6/94-10-165 (N. J. King, Siemens) proposes an approach to mobility management for both public andprivate wireless systems. The approach is guest registration by dial-up from the visited system to the home system.

TR-41.6/94.09&10.167a (G. Boudreau, Northern Telecom) proposes draft text for Sections 1 through 4 of thePCI standard for the unlicensed band. TR-41.6/94.09&10.167b proposes draft text for Sections 6 through 8.

ENHANCED 911

TR-41.6/94-10-164 , Open Issues for Enhanced 911 Services for Wireless User Premises Equipment (N. J. King,Siemens), is a follow up to discussions in the September meeting on TR-41.6/94-09-119 (N. J. King, Siemens).It identifies possible technical solutions to the potential issues. The FCC’s recent Notice of Proposed Rulemaking isattached. A joint meeting will be held with TR-41.1.9 on this topic. TR-41.6/94-11-214© is the report from theJoint Experts Meeting (JEM) on Public 800 Mobile and Personal Communications Support of 911 and E-911Emergency Services, sponsored by TR-45, and held in August 1994 (see report in CSR 5.8, September 1994, page15).

OCDMA (ORTHOGONAL CDMA)

TR-41.6/94-10-176© (H. Chen, Stanford Telecom) proposes that the OCDMA WUPE standard be based upon theETSI DECT standard with appropriate modifications to the physical and MAC layers. It is an updated proposal for themodified physical layer and is derived from ETSI specification ETS 300 175-2 and from orthogonal CDMAtechnology.

PACS-WUPE

TR-41.6/94-10-189 (E. Ornelas, NEC) contains the table of contents for the PAC-WUPE Air Interface. Theremainder of the document is in soft copy (TR-41.6/94-10-194 , MS Word 6.0, 2 diskettes).

PN-3400, WCPE INTEROPERABILITY STANDARD

TR-41.6/94-10-183© (ETSI TC-RES) is draft ETS 300 435. It is entitled “Radio Equipment and Systems (RES);Digital European Cordless Telecommunications (DECT) Data services profile Base standard including inter-working toconnectionless networks (Service types A and B, Class 1).”

TR-41.6/94-10-185© (D. Akerberg, Ericsson) contains the ETSI TBR-10 (Technical Basis for Regulation) document:General Terminal Attachment Requirements Telephony Applications.

PN-3400, WCPE INTEROPERABILITY AD HOC

PHYSICAL LAYER SPECIFICATION

TR-41.6/94-10-171 (D. Akerberg, Ericsson) contains draft text for extended carriers for the physical layerspecifications. It identifies a method of setting up the carrier number plan to accommodate asynchronous sub-bandchannels and future unlicensed spectrum allocations. Changes were made, and it will be sent as liaison to theANSI/IEEE C63 SC7 committee.

TR-41.6/94-10-186 contains text of the most current revisions to Part 15D dated October 20, 1994. It is the “delta” inthe Part 15.323 wording that affects the WCPE physical layer. Changes were made, and it will be sent as liaison tothe ANSI/IEEE C63 SC7 committee.



TR-41.6/94-10-179 (G. J. Wimpenny, Symbionics) presents analysis for Asynchronous sub-band channelization.Channel spacing of 937.5 kHz with a reduction of the first adjacent channel performance of about 3 dB appears towork. It will be sent as liaison to the ANSI/IEEE C63 SC7 committee.

TR-41.6/94-10-178 (G. J. Wimpenny, Symbionics) provides updates to the physical layer corrections based upondiscussions in the last meeting. Changes were made; it will be sent as liaison to the ANSI/IEEE C63 SC7committee.

TR-41.6/94-10-177 (G. J. Wimpenny, Symbionics) identifies issues regarding the legitimacy of the ANSIproposed power measurement technique. Changes were made; it will be sent as liaison to the ANSI/IEEE C63 SC7committee.

MEDIUM ACCESS (MAC) LAYER SPECIFICATION

TR-41.6/94-10-172 (D. Akerberg, Ericsson) contains draft text for extended carriers for the medium access layerspecifications. It identifies adjustments to the MAC layer that allow for the introduction of async sub-band channelsand potential future unlicensed spectrum allocations. It was decided to add a section to 3.4.2.4.3.1 to provide a newcode 1011 for “active rfp carriers.”

TR-41.6/94-10-146 (D. Akerberg, Ericsson) contains the modified draft text for Section 3, Medium Access Layer,of the WCPE standard as discussed in the last meeting. TR-41.6/94-10-180 (P. Morris, Symbionics) suggests aseries of editorial changes to TR-41.6/94-09-146 on the MAC layer. A new CPAP feature was mandated to pickup “active carrier” information in the paging channel. TR-41.6/94-10-187 is the updated version as discussed inthis meeting.

TR-41.6/94-07-84 is the WCPE Generic Access Profile (GAP). Feature items N.31 (Internal Call), N.32 (Holdcall), and N.33 (Reconnection of held call) were provisionally agreed as optional, but the process is still under study.N.34 (Specific line selection) was agreed as feature optional, process mandatory. N.26 (Authentication of FT [Fixedradio Terminal] and PT [Portable radio Terminal]) was provisionally accepted as mandatory. N.22 (Goto DTMF[infinite tone length]) for PT and FT was provisionally accepted as mandatory. N.12 (On air key allocation) wasunassigned pending further study. N.11 (Location registration) for FT was provisionally accepted as mandatory if thereis more than one location area. N.9 (Authentication of PP [Portable Part]) for FT was provisionally accepted asmandatory. N.5 (Register recall) will be re-labeled as “flash.” A clear definition is needed on what functions areinvoked by “flash.” Changes in DLC services D.9 (Encryption deactivation), D.10 (Extended page Lb broadcastservice), and M.* (MAC service to procedure mapping) changes were provisionally accepted. D.5 (Inter-cell voluntaryconnection handover) for FT/Business was provisionally accepted as mandatory with the TR-41.6/94-09-118 (R.Pombo, Motorola) new “note 1.” A change was suggested for correction of location update feature (N.11 - locationregistration).

TR-41.6/94-10-181 (P. Morris, Symbionics) gives an implementer’s perspective on how the proposed increase ofmandatory features increases the complexity beyond the ability of certain markets and the external memory of commonprocessors. It specifically requests that the new features be made optional.

TR-41.6/94-10-182 provides recommendations on improving protocol efficiency and response time. It was decidedto write this contribution showing clarified CPAP (Customer Premises Access Profile) wording and send it as liaisonto get information to the ETSI RES (Radio Equipment and Systems) 3 NTW Chair.

TR-41.6/94-10-151 (T. Sterkel, AT&T) outlines items in TR-41.6/94-07-84 that are problematic to key sets(link release procedure within feature N.19) and may cause problems with FCC rules (Part 15.323). Discussionclarified concerns in this contribution with no need identified to change the baseline proposal. An exception is thelocation update procedure for N.11 which was provisionally approved as PT mandatory and FT optional.

TR-41.6/94-10-166 (N. J. King, Siemens Rolm) requests the addition of protocol to allow DTMF generation. Itproposes that a feature called “Goto DTMF” be made an optional feature of the PT and implemented with a tonegenerator in the handset. It was decided that the function was already allowed without a new function.

TR-41.6/94-10-115 (T. Sterkel, AT&T) provides comments on the WCPE Access Profile in order to simplify theinterface.

TR-41.6/94-10-152 (T. Sterkel, AT&T) notes that Incoming Call Signaling needs a stimulus form to support thefeatures of advanced PBX (e.g., auto-answer). The process it proposes is “legal DECT,” but it is not allowed by theGAP. There was not a consensus to modify CPAP (Customer Premise Access Profile) to include this operation.



DATA SERVICES ACCESS PROFILE

There was a quick discussion of the progress of ETSI documentation on Data Services. There was interest in gettingthe preliminary data to TIA to be attached to the meeting minutes to start the review. There was not a clear indicationof whether data services will be completed as part of the first release of the WCPE standard.

LINK LAYER

With respect to Section 4, Link Layer, it was decided to complete the MAC layer, then review the DLC layer to makethe anticipated minor revisions caused by the MAC changes. There were clarifications and discussions regarding theswitching impact on the DLC and handover. Further contributions are expected.

NETWORK LAYER

TR-41.6/94-10-159 (S. Kuan, Northern Telecom) proposes baseline text for the WCPE Network Layer. It replacespreviously issued versions. Minor edits will be made in order to match the WCPE documentation standard and toincorporate artwork.

LCAP - LARGE CELL ACCESS PROFILE

TR-41.6/94-10-147 defines LCAP objectives:• Range of 700 meters• Mobility factor of 16.7 m/s• Interoperable with CPAP terminals/bases

TR-41.6/94-10-174 (D. Akerberg, Ericsson) contains draft text for the implementation of the preamble switchedantenna diversity option. The inclusion of the antenna diversity/preamble method was provisionally agreed. Theremay be additional enhancements needed. A contribution will be prepared that identifies changes required in the WCPEspecification for the antenna preamble method.

TR-41.6/94-10-149© (P. Harrison, Nokia) presents some RF path loss equations and applies them to the proposedWCPE standard.

TR-41.6/94-10-156 (R. Sagers, Motorola) presents measured RSSI coverage data for proposed Class I and Class IIconditions in an outdoor campus environment.

IDENTITIES AND ADDRESSES

TR-41.6/94-10-184 is a soft copy of SP-2977, “Cellular Features Description” from TR-45.2. It identifies a methodof coordinating identities and addressing.

SPEECH CODING

TR-41.6/94-10-157 (J. Needham, Mitel) identifies some areas in transmission requirements which requireinvestigation to allow completion of Section 8 of the WCPE Standard. Specific issues include a-law and µ-law, theloss plan, and the transmission of speech coding and the conflict between SLR/RLR and TOLR/ROLR.

TR-41.6/94-10-173 (D. Akerberg, Ericsson) is an overview of how ETSI sees speech transmission and theimplications on design and echo correction.

PN-3400 MASTER DOCUMENT

TR-41.6/94-10-193 is a copy of the WCPE Working Drafts, in MS Word for Windows 2.0 format (5 diskettes). Itincludes changes agreed at the meeting.

TR-41.6/94-10-154 (T. Sterkel, AT&T) is a proposed WCPE procedure for version control.

Editor’s note: TR-41.6 work in progress is now available as follows:BBS 202-639-4469 conference 39TELNET T1BBS.T1.ORG Conference 39FTP FTP.T1.ORG /PUB/TR41



REPORT OF Q21/8 INTERIM MEETING, SPECIFICATION OF AN ISDN PCIINTERFACE, NOVEMBER 2 – 4, 1994, PARIS, FRANCE

Editor’s note: In this report, PCI refers to Programmable Communications Interface.

N. Guedalia, NCC/Bezeq (Israel) is the Rapporteur of Q21/8.

T.ISDN-PCI Editor: P. Lequeux, ZTI (France)T.ISDN-PCI Associate Editor: C. Corte, CSELT (Italy)

The Rapporteur’s group decided to modify COM-8-58, the basic document for Recommendation T.ISDN-PCI, basedon the requirements outlined in Section 5 of the Q21/8 report from the last SG 8 meeting (TD-2107). Therestructured documents, as described below, will be sent for Resolution 1 procedures during the March 1995 SG 8meeting.

The German delegation’s position is that it is of no use to push the proposed Recommendation such that in one year itwill be where CAPI is today. The German delegates stated that there was not enough time for the concerned manufac-turers to study the contributions in a constructive manner since the time for distribution among the concernedmanufacturers was only several days. Furthermore, some of the active members of Q18/1 – who could have reviewedthe contributions – did not receive any contributions at all, although they are listed in the rapporteur’s mailing list..The German delegation favored deferring Resolution 1 procedures for the document.

T.ISDN-PCI RELATED DECISIONS

It has been decided to divide Rec. T.ISDN-PCI into the following parts:

Part 1 General ArchitecturePart 2 KernelPart 3 Supplementary ServicesPart 4 Protocol Management ExtensionsPart 5 Access Mechanisms

Part 1, the general architecture shall include chapters 1-5 of COM-8-58.

PART 2, THE KERNEL

Part 2, The Kernel, shall include chapters 1-4, 6 and 7, plus the exchange mechanism general description, Coding(information representation), and security. Annex B & F (of COM-8-58) shall be included in the Kernel.

Section 7.2 shall be reconstructed as follows:

• Introduction• General messages• Protocol management messagesProtocol management messages will be further divided to external architecture and to the messages supporting theextension mechanism.

Section 7.3 Control Plane Messages shall be reconstructed as follows:

• Introduction• Signaling related messages (which should also include messages from Q.931 not currently included in the PCI, and

which are necessary for international support)• External device control messages

In addition, features which enable the support of Internationalization (ISDN 1) will be added to this part.

PART 3, SUPPLEMENTARY SERVICES

Part 3, Supplementary services, shall include particular support of supplementary services, where the generalmechanism shall be part of the Kernel. This part shall be for further development and shall not be addressed at thismoment.



PART 4, EXTERNAL PROTOCOLS

Part 4, The External protocols, shall include all the U3 messages (the indication of which protocol from which layer isincluded shall be done in the Kernel). All the external protocols included in Part 4 shall be optional. Part 4 shall bereconstructed to the following documents:

• Protocol extension architecture• Layer 1 protocols• Layer 2 protocols• Layer 3 protocolsLayer 3 protocols shall be further divided into two documents: the existing protocols and the newly added ones.

Each of the protocols described shall contain the following information:

• Message set description, including a complete description of all messages• Description of the parameters including the U3 Protocol• State diagram• Mapping between message parameters and the protocol itself• Static attributes• Error management where applicable• Selection criteria where applicable

The Layer 1 protocol shall include only the transparent protocol.

The Layer 2 protocol shall be divided into two documents:• Existing protocols in the first document• PPP, SDLC and V.110 in the second document

The Layer 3 protocol document shall include only the existing protocols. All other protocols shall be submitted to SG8 as White Contributions.

PART 5, ACCESS METHODS

Part 5, Access methods, shall contain the particular support for the various access methods. Currently it includesDOS, WINDOWS, UNIX, OS/2, Windows NT, and Novell Netware. Part 5 shall be submitted, for the moment, as annon-normative part. Conformance to this Recommendation necessitates implementation of at least one access method,rather than all of them.

COMMUNICATIONS STANDARDS REVIEW ALSO PUBLISHES:

Communications Standards Summary (ISSN 1075-5721), a quarterly publication reporting onall active projects and recently completed standards of the Telecommunications Industry Association’s (TIA’s) TR-committees. To receive a complimentary issue of this TIA-authorized publication, please contact Elaine Baskin, Tel+1 415 856-9018, fax +1 415 856-6591, e-mail [email protected]

No Obligation



REPORT OF TR-46, MOBILE & PERSONAL COMMUNICATIONS 1800 MHZSTANDARDS, NOVEMBER 7 – 11, 1994, AUSTIN, TX

TR-46/94.11.07.05 is incoming correspondence from T1S1 regarding an active project to develop MobilityManagement Application Protocols (MMAPs) for a “C” Interface based on the T1P1 reference model. On the basis ofa discussion at the T1P1/TR-46/T1S1 ad hoc group meeting on October 11, 1994, they believe the following:• The TR-46 “A” and the T1P1 “C” reference points are very similar and almost identical• The MMAP work in T1S1 complements the “A” Interface work in TR-46• The expected completion date of the work in T1S1 (1Q95) dovetails with the expected completion date of the TR-46

“A” interface workIn view of the above, T1S1 feels that there is an opportunity for cooperation between the groups.

TR-46/94.11.07.07 (D. Bart, TIA) contains a draft advisory note regarding TIA standards based upon, or derivedfrom, ETSI standards. The TIA wants to ensure compliance with its Intellectual Property Rights policy.

TR-46/94.11.07.08 is correspondence from K. Heinz (ETSI) to D. Bart (TIA). One of ETSI’s technicalsubcommittees on multi-mode mobile earth stations for Satellite Personal Communication Networks (S-PCN) isrequesting guidance on whether Satellite Personal Communication Networks standards shall contain a clauseconcerning disabling conditions for fellow radio stations for the cases where appropriate radio networks are notprovided.

TR-46/94.11.07.09 is an open letter to the JTC(Air) participant companies from the JTC co-chairs concerning theissues of Intellectual Property Rights (IPR) as they relate to the draft standards being developed in the JTC. The letterasks four questions.• Does your company possess, or know of any company that might possess, an essential IPR(s) for any of the

technologies being worked or draft standards being developed by the JTC?• If your company possesses an essential IPR(s), will your company abide by the TIA and ANSI required licensing

policy text included with the letter (attached to the letter as Appendix A)?• If your company does not intent to abide by the TIA and ANSI IPR licensing policy, please notify the JTC and

identify which technologies will be impacted. This will enable those companies with interest in the affected tech-nologies to make decisions on those IPR(s) and to immediately begin developing “work arounds” for those patents.

• If you believe that other companies may possess an essential IPR, please notify the JTC so that the abovementioned questions may be forwarded to them.

Response was requested by October 31, 1994.

TR-46/94.11.07.11 (ITU-R, Study Group 8, TG 8/1) is the October meeting report for ITU-R TG 8/1. The ad hocgroup for migration towards FPLMTS was elevated to working group status; the group is working on third generationwireless.

JOINT AD HOC: TR-46, T1P1, T1S1

TR-46/94.11.07.12© (A. Alavi, Motorola) is a report on the joint Ad-Hoc meeting of TR-46/T1P1/T1S1 that washeld on October 11, 1994, relative to the development of an ISDN based PCS standard. It contains the conclusions andrecommendations resulting from the meeting, and it proposes that the member companies adopt recommendationsresulting from the meeting to ensure that a single standard can emerge. Please also see the meeting report in CSR 5.9,October 1994.

TR-46/94.11.07.13© (E. Moore, Bell Atlantic) proposes that TR-46 adopt T1S1’s Mobility Management ApplicationProtocol (MMAP) for use in TR-46’s ISDN-based A-Interface standard. The contribution is in discussion in TR-46.1.

TR-46/94.11.07.14© (J.R. Hilton and W.J. Miniscalco, GTE) also proposes that TR-46 develop and publish anISDN-based A-Interface standard that uses the application protocol under development in T1S1. GTE believes that thisapproach will satisfy the near-term requirement of producing consistent PCS standards in the shortest time possible aswell as the long-term requirement of providing a migration path to future PCS networks.

TR-46/94.11.07.16 (E. Moore, TR-46/T1S1 Liaison) is a liaison report on the October 10-14, 1994, T1S1meeting. It provides a summary of T1S1 key issues.



TR-46.1.1 SERVICE REQUIREMENTS AND DESCRIPTIONS

TR-46.1.1.1/94.11.08.01© (T. Deak, Siemens SC) proposes text for IS-104-A (Personal Communications ServiceDescriptions) to incorporate an agreement made during the previous group meeting to include subscriber interrogationof supplementary services.

TR-46.1.1.1/94.11.08.02© (G. Chien, Ericsson) proposes text for IS-104-A to add the Multi-Way Calling (MWC)supplementary service. The MWC supplementary service replaces Three-Way Calling supplementary service.

TR-46.1.1.1/94.11.08.03© (J. Salo and T. Jarvela, Nokia) proposes additional text to each of the Personal CallForwarding (PCF) - Not Reachable paragraphs in sections 2.2 through 2.6.

TR-46.1.1.1/94.11.10.01© is an updated version of TR-46.1.1.1/94.11.08.02© (G. Chien, Ericsson). It incorporatescomments and editorial changes from DSC.

TR-46.2.1 NETWORK SIGNALING

At the V&V Task Group meeting, Document Discrepancy Reports (DDR) 8, 18, 19, 22, 23, 24, 25, 26, and 27 wereremanded to TG 1 for approval of technical changes. DDR 028 remains open for working group action.

TR-46.2.1/94.11.07.03 (Motorola) discusses changes to the SS7-based A-Interface in order to make it compatible withthe recently released version of the JTC’s TAG2 air interface (CDMA). During discussion, some companies were infavor of delaying completion of the document until the revised technical input could be incorporated. They believe thatthis input could be provided and the document completed by the December meeting. Other companies expressedconcern that the amount of technical change was too much to be accepted and completed in one meeting. Somecompanies also expressed concern that other companies were not taking seriously the commitment to complete thisdocument by the current meeting. There was concern that additional requests for delays from other air interface groupscould be received at the next meeting and would lead to an even longer delay. With the following commitment fromMotorola, the group agreed to delay the completion of PN-3343 (SS7 Based A Interface) until the December meeting:

Motorola will bring in changes that are required to the December meeting. The V&V Task Group will complete workon the current document without consideration for future changes. The new changes will only be the minimumrequired. If the received technical changes are not acceptable or not received by this group by the December meetingopening, the document will be balloted without the CDMA air interface section. In addition, if major issues with theCDMA arise during the ballot comments, the section will be dropped if that will allow the remaining document to beissued as a standard.

WG 1, TG 1 proposed a WG 1, V&V Ad-Hoc Task Group, and TG 1 meeting during the week of November 28 forreceiving technical changes to resolve DDR 028 (regarding the SS7-based A-Interface). It was decided to open themeeting with WG 1 and then decide the remaining meeting plan. Motorola also agreed to have the technical inputrequired to resolve DDR 028 available for the November 28 meeting. It is the intent of the group to complete thetechnical changes and V&V of the document at that meeting and to have the document ready for forwarding to TR-46.2for ballot at the opening of the December meeting.

The SS7 A-Interface V&V Ad-Hoc Task Group reported one additional technical DDR, 033, but no resolution wasrecommended. It was referred to TG 1 for resolution. Discrepancy reports 007, 013, and 021 were reclassified toeditorial.

TR-46.2.1.2 ISDN BASED A-INTERFACE

TR-46.2.1.2/94.11.08.03©, Handoff Forward and Backward Scenarios (D. McClarren, Bellcore, same as TR-46.2.1.2/94.10.04.12b©), contains descriptions for Automatic Link Transfer, and it was reviewed for information. Ifrevised, it could be included in text or in an appendix.

TR-46.2.1.2/94.11.08.04©, Handoff Information Flows (D. McClarren, Bellcore, same as TR-46.2.1.2/94.10.04.12©), covers Inter-Switch Handoff procedures and information flows which provide continuity ofservice for the PS user when signal strength varies during an answered call. It was accepted in principal. The authorwill revise it to fit the handoff phase organization of the document.

TR-46.2.1.2/94.11.08.05© (D. McClarren, Bellcore) proposes text for section 5, Signaling and Transport Protocol.The protocol is the three layers specified by ANSI T1. It was accepted as text for the indicated sections. Also, it wasagreed to add T1.610 to section 2.1.



TR-46.2.1.2/94.11.08.06© and TR-46.2.1.2/94.11.08.06b (D. McClarren, Bellcore) are proposed text for section6.1.5. They include brief descriptions of each supplementary service from IS-104. They were accepted as text for sec-tion 6.1.5 except that they will be put into the subsections of each service rather than in the lead section as proposed.

TR-46.2.1.2/94.11.08.07©-(D. McClarren, Bellcore) describes the “non-conventional” DS1-based transport systeminterface when a Radio Port Control Unit (RPCU) is connected to a PCSC ISDN/Switch. It proposes multiplexedBRI. It was agreed to incorporate this work into an appendix.

TR-46.2.1.2/94.11.08.08 is T1P1 - Stage Two Service Descriptions, Version 7. Soft copy of the complete documentwas received and discussed. There was a consensus that the group should again communicate with TAGs explainingwhat is needed and when.

The group reconfirmed that it is up to the proponents of an air interface to bring in their contributions to ensure thatthey are supported.

TR-46.2 .1 .2 /94 .11 .08 .09 (N. Smith, Omnipoint) is baseline text for PN-3344, ISDN Based A-Interface (RadioSystem - PCSC) for 1800 MHz Personal Communications Systems, Revision 0.6, dated November 8, 1994.Editorial changes were reviewed and accepted.

TR-46.2 .1 .2 /94 .11 .08 .10 is T1P1’s Automatic Registration procedure. It is a section of the T1P1 Stage ServiceDescriptions document. It resulted in discussion of which functions are in PCSC and which are in RS, as well as howthe A- Interface maps to the C and D interface of T1P1. Also, there was discussion regarding terminology differencesbetween TR-46 and T1P1, and which T1P1 interfaces map to the A interface. It was agreed that message means shouldbe the same in the TR-46 standard as in the T1P1 Protocol; however, deciding which messages go across the A-Interface cannot be done at this time.

The next issue of Communications Standards Review (Vol. 6.1)is scheduled for February 1995.



TR-46 PARTIAL MEETING ROSTER, NOVEMBER 7 – 11, 1994, AUSTIN, TX

Anil Kripilani, Qualcomm Chair TR-46Stephen S. Jones, NEC Vice Chair TR-46

AirTouch Comm Rick JudsonAPC Mark PohlmanAPC Steve ZweifachASTRONET David DeVaneyAT&T Dave AndersenAT&T V. K. GargAT&T Alicia KwokAT&T Tom TowelAT&T Joe WilkesBellcore Cliff HaleviBellcore P.J. LouisBellcore Don McClarrenBell Atlantic Ed MooreBell South Don ZelmerDGM&S Steve NorthridgeDSC Comm. Dick KuenzerEricsson Gilbert ChienEricsson Miguel CoboEricsson Daniel CollinsEricsson T. GinterGTE Jay HiltonGTE William MiniscalcoMcCaw Ming ZhangMCI Chris WallaceMotorola Alex AlaviMotorola Brian ChenMotorola Karl LewisMotorola Jason LoshNEC Stephen JonesNokia Elina DurchmanNokia Harry HerlinNokia Atte LansisalmiNokia Joe McAreerNokia Jari SaloNTI Patrick JohnsonNTI Dhawal MogheNTI Tony SaboorianOmnipoint Gary JonesOmnipoint Neal SmithQualcomm Chih-ping HsuQualcomm Tom InklebargerSiemens Dick BlakeSiemens SC Ed CampbellSiemens SC Thomas DeakSiemens SC Bill Krehl



REPORT OF ITU-T SG 8 RAPPORTEUR’S MEETING FOR Q5 AND Q19NOVEMBER 14 – 18, 1994, BETHESDA, MD

This Rapporteurs’ meeting covered a number of topics within Q5’s Group 3 Facsimile Apparatus:

• Fax PCI• Echo Control Devices• Voice/Fax• Terminal Selection• Negotiation Procedures• Paper Formats• Mobile Fax• Fax Routing

Joint meetings were held with Q9/8, Security, and with Q4/15, Algorithmic Techniques in Voice BandTelecommunications Networks. Q19/8, Modulation Techniques, also met.

Q5/8 GROUP 3 FACSIMILE APPARATUS

The Rapporteur, B. Revillet (Canon Research, France), was assisted by H. Hertlein (DBP-Telekom, Germany) astechnical secretary.

FAX PCI (T.CLASS1 AND T.CLASS2)

The improvements in Fax PCI made at this meeting introduce differences between TIA and ITU-T T.class1 andT.class2 Recommendations. These Recommendations are in line with T.4 and T.30 issued in 1993. As the group dis-cussed the possibility of making ECM mandatory when using V.17 (see BET-8, under the Q19/8 report, above), itwas agreed that the same decision should also apply to T.class1 and T.class2.

BET-13 through BET-17, and BET-39 through BET-41 were submitted by J. Decuir, Microsoft.

BET-13 provides the status of draft recommendations V.25ter, T.class1, and T.class2.

BET-39 is the current draft of V.25ter. Both T.class1 and T.class2 refer to V.25ter commands.

BET-14 provides the revised proposal for interworking between T.class1, T.class2, and V.25ter commands.

BET-40 is the current draft of T.class1. BET-15 proposes a T.class1 inactivity timer definitions. The group agreedon a definition of the inactivity time (no activity on the line between the DCE and the DTE) applicable to bothT.class1 and T.class2. BET-16 proposes an Adaptive Reception Control (AR) for T.class1 (AutoCarrier detection).The group decided to enhance T.class1 by introducing new commands (+FAR). As a result, the DCE willautomatically detect the carrier (V.21 or high speed modem). The command will be mandatory.

BET-41 is the current draft of T.class2. BET-17 proposes a NSF message data indication (ND) in T.class2. Thegroup agreed to amend T.class2 to handle NSF messages that are transparently sent by the DCE to the DTE. Thiscommand will be mandatory.

ECHO CONTROL DEVICES/QUALITY OF SERVICE

In addition to the topics studied in common by SG 8 and SG 15, an invitation was made to give comments on E.measin BET-11 (Q2/2). BET-11 describes a measurement methodology for fax transmission quality. BET-12 is aliaison statement from Q10/1 to Q2/2 and Q5/8 regarding the definition of image quality parameters and cooperation inthe definition of quality of service in the telefax services. It was presented here for information.

VOICE COMBINED WITH FAX

BET-33 (I. Sebestyen, Siemens) raises the question of how to transmit voice and fax data over one single line. SG 8was invited to determine its strategy. Should voice be a new type of coding within a document? Should it betransmitted alternately with fax or by several channels simultaneously with fax? No answer was available during themeeting. Liaisons with SG 14 and SG 15 are necessary.

BET-18 (H. Silbiger, AT&T) describes the additions and modifications to Rec. T.30 Annex C needed to supportsimultaneous voice and facsimile operations using modulation techniques that are being standardized in SG 14. BET-23 (H. Silbiger, TR-29) describes the addition to Rec. T.30 Annex C to support duplex V.34 modem capabilities.



BET-54 contains proposed modifications of Annex C of Recommendation T.30, arising from the Q19/8 meeting.

TERMINAL SELECTION

There were two main items in this discussion. The first was an enhancement of Annex D to T.30. BET-37 (TR-29)proposes to allow DTMF signaling as an option to permit the caller to take direct control over the fax/tel switch, elim-inating unnecessary delays. The amendment was to detect DTMF signals just after off-hook. A human caller would beable to shorten the procedure by pressing a key on the keypad. The number of digits, as well as the actual pattern, isleft open to the manufacturer. BET-37Rev2 (L. McIntyre, Q5/8) contains the agreed revisions of Annex D ofRecommendation T.30.

BET-31 (L. Brown and L. Smith, TR-29) proposes a modification to Annex D of Recommendation T.30 to include anote providing for the initiation of OGM without delay where permitted under national regulations.

The silence period of 1.8 to 2.5 seconds is no longer necessary, and communication can start almost immediately afteroff hook (0.2 seconds, as in V.34). The group agreed to delete the delay in T.30.

NEW NEGOTIATION PROCEDURE

TR-29 introduced BET-28 (J. Rafferty) which is based on former German and French contributions. The idea is tointroduce a 2-step negotiation with new frames. The long term target is to supersede the present procedure. Theprinciples are order independence and bit efficiency. It could be one-pass or two-pass. This proposal was welcome andreceived good support; however, some compatibility problems may be encountered since a new signal (DES, DigitalExtend Signal) is sent, without prior negotiation, by the called machine.

NEW PAPER FORMATS

Two contributions, BET-19 (Y. Yoshiura, Canon) and BET-36 (L. McIntyre, TR-29), propose to redefine the twonew bits in the DIS/DTC/DCS table, in order to accommodate letter and legal paper sizes. They were combined intoBET-19 rev1 and agreed upon by the group. This feature will be introduced for Resolution #1 next March.

MOBILE FAX

A problem has occurred in digital cellular network (GSM, Europe); however, it may also appear elsewhere. In thecase of GSM to GSM calls, the network (i.e., the interworking facilities) must know that the remote terminal is alsoconnected on GSM. To make that possible, it was proposed that the interworking facilities remove the NSF (iftransmitted) and insert a specific NSF code to identify GSM. The information can be ignored by the remote terminal,but will be useful to the remote interworking facilities. BET-21 (H. Hertlein, Deutsche Bundespost Telekom, andDeTeMobile) clarifies the technical problem and presents information on the specific non-standard capabilities (NSF,NSC, NSS) for the GSM network. BET-26 (H. Hertlein, Deutsche Bundespost Telekom) proposes amendments toT.35 to allow network identification in facsimile communication links. In addition to country codes, T.35 woulddefine network codes.

Objections were raised that other networks and transition devices would remove the NSF/NSC/NSS. SG 1 complainedthat network equipment was unable to carry the real NSF. FAX PADs, as well as PCMEs and DCMEs, remove NSFbecause this equipment remodulates the facsimile signals and cannot support other modulations and coding schemes.

It was agreed that, due to standardized network codes in T.35, manufacturers of network equipment (i.e., FAX PAD,PCME, DCME) could design their equipment so that they do not remove network NSF. Finally, the proposal toamend T.35 was accepted. T.35 will be introduced in Resolution #1 in March 1995.

NEW FEATURES (T.ROUTING)

In June, the group accepted the principle of T.routing, which aims at defining the content of SUB frame. BET-38 (J.Rafferty, Editor) is the T.routing baseline document as agreed from the last SG 8 meeting.

BET-20 (J. Rafferty, TR-29) proposes edits to the T.routing baseline document. With some modifications thedocument was agreed and the editor will produce an amended Draft Recommendation for the next meeting. In case thereceiving terminal does not handle SUB frames, the sending terminal may decide to disconnect or to send the documentanyway (This feature is up to the manufacturer.). The efficiency of T.routing will be limited by the length of SUBframe (20 digits at present). The SUB extension to 40 digits would lead to compatibility problems and was stillrefused.



A more reliable way to transmit SUB, SEP and PWD was proposed during the June SG 8 meeting (using the DCS toindicate that the PWB/SEP/SUB are sent during Phase B). BET-35 (Y. Mori, Ricoh, Japan) contains the surveyresults on the proposed modification of PWD/SEP/SUB usage (see TD-3126). No compatibility problems weredetected in Japan. This feature will be introduced in Resolution #1 next March.

SECURITY

Security was discussed jointly by Q5/8 and Q9/8. At the June SG 8 meeting, 13 questions were proposed (COM-8-R-30) for a secure facsimile encryption system. At this meeting, three contributions were submitted in response:

• BET-27 (A. Pugh, MG Ltd., UK) proposes both an algorithm (HFX) and a key management system (HKM). Itprovides a system that is rather simple to implement, but limited to communication between partners that havemade prior arrangement and prior exchange of keys. Also included in the contribution is brief descriptions of theRSA Key Management System and the double Diffie-Hellman Key Management system.

• BET-5 (B. Kowalski, Deutsche Bundespost Telekom) and BET-7 (J-L. Grimault and G. Boulay, France Telecom)do not propose specific algorithms. They both put forward general positions. They are based upon public keys andtrusted third parties (TTP), and allow for a wider range of services (i.e., non-repudiation, non-replay, authentication,integrity). They do not assume prior arrangement and can be used to prove the fax exchange in front of a thirdparty.

The group did not try to reply precisely to the list of 13 questions established during the June meeting. Consequently,the target (level of security services to offer) remains unclear.

Supporters of one principle did not manage to convince the opposing faction. The conclusions of a lengthy discussionwere:• The group should define a default cipher carrier; optional ones can be negotiated. Both the default and the optional

ones should be defined.• Other services (supported by France and Germany) should also use algorithms selected from a default and several

options.• The group should amend T.30 to carry security elements.

Some delegates wanted to push the UK proposal, as it is the most precise today. However, other delegates objected toit being a proposal that solves only part of the problem. The robustness of the HFX was questioned by somemembers. This algorithm is not standardized or referenced by ISO.

BET-24 (T. Yamamoto, Nippon, Japan) provides questions for discussion of HKM and HFX40. HKM and HFX40were proposed at the last Study Group 8 meeting (as D-152 and D-153 , respectively) as the security system forGroup 3 facsimile.

Passwords can be used to fit basic security needs, such as those presented by BET-4 (R. Maddeaux, Canada). Itproposes to modify the meaning of subaddress.

BET-6 (J-L. Grimault and G. Boulay, France Telecom) provides general considerations of security in facsimile. Italso contains an analysis of the UK proposal made in the June 1994 meeting.

BET-25 (T. Sayama, KDD, Japan) presents the results of a Japanese manufacturers’ review for the introduction ofsecurity features to facsimile based upon TD-3140 .

Three short documents were provided by the informal ad hoc group on security, which met prior to this meeting.BET-47 provides targeted application scenarios for security in facsimile. BET-48 provides security requirements forfacsimile messages and documents. BET-49 provides technical requirements for security mechanisms in facsimile.

RESOLUTION #1

During the next meeting in March 1995, Q5 will announce Resolution #1 for the following subjects (whitecontributions are expected):• T.class1• T.class2• T.routing• T.35 (modifications)• T.4 and T.30 (new paper formats)



M ISCELLANEOUS

BET-43 (J. Decuir, Microsoft) proposes work on a voice-PCI interface between a DTE and a DCE including voicehandling facilities. This matter was felt important for future business of SG 8; however, Q5 (responsible for fax) didnot seem the most appropriate place for such a subject. During the March 1995 SG 8 meeting, the contribution willbe raised to SG level for allocation to the most appropriate Question.

Compatibility with existing machines is always a concern of SG 8 members. Although the principle of a goodimplementation of the standard is that the machine should discard any ignored signals and proceed with known signals,experts were afraid of problems that could arise from bad implementations. It was agreed that bad implementationsshould not slow down the progress expected by users.

BET-9 is a liaison statement from Q2/2 to Q5/8 and Q10/1 regarding post dialing delay information collected byQSDG (Q2/2) noting that only 1 to 3% of calls had a delay of greater than 30 seconds.

BET-10 is a liaison statement from Q2/2 to Q5/8 and Q10/1 containing a pareto chart of causes of fax faultscompiled over one month. It notes that incorrect settings of fax machines service parameters and fax hardware are themajor components of fax faults.

BET-52 is a liaison statement from Q5/8 to SG 14/1 and SG 15/2 requesting action on the proposed simultaneousfacsimile and voice operation in Group 3 facsimile.

ITEMS COMMON TO Q4/15 & Q5/8

Th joint meeting between Q4/15 and Q5/8 was chaired by M. Sherif (AT&T, U.S.). T. Shah (BT, UK) acted astechnical secretary.

The group discussion centered primarily on two documents. BET-30 (SG 15, WP 2/15, and Q4/15) providesinformation for SG 8 and SG 2 regarding the effect of network propagation delays and echoes on the quality of faxcommunication, especially cut-offs. BET-29 (A. Giuseppini, ISPT, same as TD-3174) is a response to SG 15from SG 8 (discussed during the June meeting) regarding information on echo and delay with respect to Group 3facsimile performance. This meeting was the first occasion for SG 15 and SG 8 to consider this topic jointly.

BET-30 provides information on the tests done by COMSAT between pairs of terminals (dedicated or PC add-onboards) using different network parameters (echoes and delays). As pointed out in BET-29, the high failure rate ispartly due to the presence of some PC add-on boards of questionable quality. In addition, SG 8 wondered if the testswere run with “typical” network parameters. SG 15 experts indicated that there are no typical conditions, since net-works around the world have different characteristics. Some delegates were convinced that the failure rates are lower inreality than BET-30 indicates (even if the bad results introduced by some PC cards are discarded). Network operatorsreceive complaints from users; the ability to distinguish between terminal-originated problems and network-originatedproblems is impossible. It appears that the implementations–rather than T.30 itself– have the bugs. However, theidea of developing a conformance testing recommendation in SG 8 did not receive much support. M. Sherif (AT&T,U.S.) indicated that the tradition is for SG 15 to provide a conformance testing recommendation (which is not the casein SG 8), and ITU should make the knowledge available to everyone. However, some delegates questioned whether thefailure rate would justify such a work.

It was agreed that there is a problem in facsimile communication over new networks with high propagation delaywhich can only be solved by a combination of manufacturers and network providers. The group agreed:• SG 8 members will estimate the network characteristics (echoes and delays) in which T.30 works satisfactorily, and

report to SG 15 in order to ask operators if their network fulfills these conditions.• SG 15 will provide information on parameters (echoes, delays, distortions, noise modulation, bandwidth and signal

level) that can actually be found in networks.• SG 8 will produce some guidelines for implementers of T.30 (to be added to T.30).• All of the above will be available by March 1995.

BET-42 is a liaison statement from Q5/8 to Q4/15 regarding impact of delay on Group 3 facsimile.

Q19/8 MODULATION TECHNIQUES FOR TELEMATIC SERVICES

The Rapporteur, G. Griffith (Rockwell, U.S.) was assisted by J. Decuir (Microsoft, U.S.) as technical secretary.

L. Brown volunteered to prepare the “V.34 annex” to T.30, and to provide it to A. Pugh (MGCS, UK), editor of T.4and T.30.



BET-8 is a liaison from SG 1 Q10. It requests the introduction of higher data rates (higher than 14.4 kbit/s) andwants to make ECM mandatory at rates above 9600 bit/s. The group agreed that the Telefax 3 ServiceRecommendation should be amended to allow data signaling rates higher than 14.4 kbit/s.

SG 1 is considering mandating ECM for all Group 3 facsimiles. They believe that ECM is not expensive, but thegroup contested this view. Low cost terminals (for home application) should remain available. The group decided toapply ECM with V.34 at any rate (for simplicity), but rejected the idea of making it mandatory for V.17 which isalready standardized.

The group considered four documents regarding the technical aspects of V.34:• D-161 (K. Hayashi, Toshiba, from the June SG 8 meeting) promotes the use of V.8.• BET-23 (TIA TR-29) proposes a full duplex procedure for V.34, based upon present T.30 Annex C.• BET-32 (TIA TR-29) proposes a half duplex procedure, with minor changes in the bodies of T.4 and T.30.• BET-34 (Canon and Matsushita) proposes another half duplex procedure, which reduces complexity and improves

the reliability of discrimination between primary channel signals and control channel signals.

The group agreed that a new T.30 annex should define the procedures for half-duplex V.34 facsimile. The annexproposed in BET-32 was revised to reflect decisions made, and it will be used as the baseline. The group also agreedto the proposed editing changes in the main bodies of T.4 and T.30 that were proposed in BET-32.

The group agreed that T.30 Annex C procedures will be used for duplex V.34 facsimile. The proposals for changes toAnnex C were referred to Q5/8 (BET-54) and Q13/8, Telematics on the ISDN.

The group agreed to limit the use of ANSam in T.30 to the same timing defined for CED, 2.6 seconds to 4.0 seconds.It was acknowledged that this is a deviation from V.8, and a liaison to this effect will be sent to the December WP1/14meeting.

BET-46 (Q19/8 Ad Hoc Group) proposes a procedure for recovering from missed ANSam that results from a late starton a manually dialed call. It proposes the definition of a new DIS bit to indicate V.8 capability. The calling terminal,after receiving the DIS frame, can determine that the ANSam signal has been missed. It can then re-initiate V.8procedures by sending the call indicator (CI). The answering terminal will then respond by sending a second ANSam.The group agreed to this proposal. However, the repeat of the ANSam signal was not specifically defined in Rec. V.8,so a liaison will be sent to SG 14 and SG 15.

BET-46 also contains recommendations that were agreed upon in the group. The DIS and DTC bit 11-14 definitions(specifying modulation capabilities) will remain the same as defined in the current T.30. DCS bits 11-14 will bemarked as reserved, set to 0000 by the transmitter, and ignored by the receiver. A note (or notes) to this effect will beadded to Table 2 of T.30. Also, a note will be added stating that bits marked reserved shall be set to 0. Bits 11-14 inDTC will be used in an identical manner to the way they are used in DCS.

The group agreed that if DCS is received in error, the response will be repetition of DIS or DTC, as specified in thecurrent T.30.

The group agreed that the initial image transmission direction (either normal or polling) is negotiated using V.8. TheCM call function will identify either the calling terminal or the answering terminal as the message source.

The group agreed that if the source changes during the session, such as in turn-around polling, the network needs to benotified. Therefore, they agreed that V.8 should be used for any subsequent direction re-negotiation. In addition theyagreed that, for any re-entry into V.8 procedures, the CM signal shall be generated by the calling terminal only. Thisinformation will be included in a liaison to SG 14 and SG 15.

BET-34 (Canon and Matsushita) proposes that the source terminal acknowledge the last control frame, prior to thetransition to high speed mode, with at least 40 bits of 1s. The recipient terminal will then respond by transmittingsilence. When the silence (or absence of flags) is detected, the source terminal will then transition to sending highspeed message data as defined in Recommendation V.34. The group agreed to this proposal, but acknowledged thatthey are paying the price of another round trip delay.

It was agreed that Tone A or Tone B retrain requests, as defined in V.34, may be used during message transmission, butthis is an optional capability for both the source and the recipient terminals.

Two methods were being considered to re-enter V.8 procedures for the purpose of turn-around polling after messagetransmission in the normal direction. One method, after a 6 second time-out, negotiates the polling mode via DIS andDTC prior to re-entering the V.8 mode. The other method re-enters the V.8 mode immediately after receipt of MCF.



The proper procedure to follow after retraining the primary channel was not yet defined.

V.8BIS

Upon request of the group, L. Brown, Rapporteur of Q1/14, explained the current situation of V.8bis. SG 14 ispreparing a Rec. V.8bis that will provide a better identification of calls by the receiving terminal. V.8bis would givemore priority to human beings than to machines. It is not clear whether V.8bis would replace V.8 or would be aseparate Recommendation. Presently, a draft of V.8bis is available, but not stable. The December Rapporteursmeeting and WP1/14 meeting should progress the work for a Resolution #1 announcement in December and anapproval by SG 14 in April. SG 8 would like to be officially informed about the status of work on V.8bis and havereasonable time to consider it before Resolution #1 is started. If SG 8 has no time to comment, it may be impossibleto use V.8bis in fax.

BET-45 (L. Brown, Assoc. Rapporteur on V.8bis) lists the V.8bis issues and action items. Because V.8bis has notbeen agreed, and because there will be a V.8bis rapporteurs meeting and WP1/14 meeting in December, it was decidedto accept this contribution as a liaison statement from SG 14.

The group provisionally agreed to the use of V.8 procedures for starting up V.34 facsimile operations with somedeviations from the original V.8 text. A flow diagram, such as that proposed in BET-23, will be included in the bodyof T.30. The group left open the possibility of using the V.8bis Recommendation, currently under development byQ1/14, instead of V.8.

BET-53rev1 is a liaison statement on use of V.8 for facsimile from Q19/8 to WP 1/14 (V.8), Q9/15 (PCME), andQ13/15 (DCME).

ROSTER OF Q5/8, Q9/8 AND Q19/8 RAPPORTEUR’S MEETING, NOVEMBER 14 – 18, 1994,BETHESDA, MD

Bernard Revillet (Canon CRF, France) Q5/8 RapporteurGlen Griffith (Rockwell, U.S.) Q19/8 RapporteurHost: Comsat

AT&T Mostafa Sherif Microsoft Joe DecuirAT&T Herman Silbiger Motorola (Canada) Les BrownBritish Telecom Tushar Shah National/Panasonic (Japan) Yoshinori AokiCanon (France) Bernard Revillet National/Panasonic (Japan) Mikio MizutaniCanon (Japan) Toru Maeda NCS (US) Dennis BodsonChantilley Corp. (UK) W.M. Hawthorne NTT (Japan) Takashi YamamotoChantilley Corp. (UK) Pul Hendrickx OKI (Japan) Hiroshi EndoCOMSAT Spiros Dimolitsas Ricoh (Japan) Yukikazu MoriCOMSAT Rod Ragland Rockwell Glen GriffithDBT Harald K. Hertlein Rockwell (Japan) Stephen PalmDBT Bernd Kowalski SAGEM (France Philippe CharbonnierDelta Info. Systems Stephen Urban SEPT-SCE (France) Jean Luc GrimaultHuman Comm. James Rafferty Siemens (Germany) Istvan SebestyenIntelsat Robert Pham Voice & Data (Canada) Don MactaggartKDD (Japan) Toshiya Sayama Xerox Lloyd McIntyreMGUK Ltd (UK) Alan Pugh

THE CSR LIBRARY

Copies of documents shown in boldface type can be ordered from Communications Standards Review,where not prohibited by copyright.We have a large library of standards work in process and can help youlocate other information you may need.



REPORT OF TR-45.5, WIDEBAND SPREAD SPECTRUM DIGITALTECHNOLOGIES, NOVEMBER 14 – 18, 1994, CORONADO, CA

• PN-3290, Recommended Minimum Performance Standard for Digital Cellular Wideband Spread Spectrum SpeechService Option 1 (IS-125) has been sent to TIA for publication.

• It is anticipated that TSB-58 (Administration of Parameter Value Assignments for Wideband Spread SpectrumSystems) will be ready in January or February 1995.

• The EVRC will need re-scheduling, due to the Plenary Meeting dates for 1995.

• Over-The-Air (OTA) Activation is presently under discussion.

R. Walton (GTE) presented four papers. Each was remanded to WG I and WG III for review and response:

• TR-45.5/94.11.14.04© Service Option Evolution and Related System Capacity Issues• TR-45.5/94.11.14.05© Reverse Link Receiver Sensitivity Issues• TR-45.5/94.11.14.06© Reverse Link Modulation and Coding Parameter Selection for Increased Data Rates• TR-45.5/94.11.14.07© Forward Link Modulation and Coding Parameter Selection for Increased Data Rates

TR-45.5/94.11.18.03© (WG III TG 4 and TG 5) identifies text changes to IS-97 (Minimum Performance Standards forBase Stations) and IS-98 (Minimum Performance Standards for Mobile Stations). These were approved.

WG I TG V is developing a standard for IS-95 packet mode data services. It defines formats and procedures for a packetdata bearer service utilizing IS-95 traffic channels between a mobile station and a BS/MSC. The Task Group requesteda project number (TR-45.5/94.11.18.05 ) and provided the latest draft text (TR-45.5/94.11.18.07©). The textneeds to be aligned with the IWF document (below) for correlation of references to common wording.

WG I TG V is also developing the standard for an open Interworking Function (IWF) interface (“L” interface in thenetwork reference model). It defines formats and procedures for the interface between a BS/MSC and an interworkingfunction for both circuit and packet mode communications and references IS-99 (PN-3140, Data Services Option forWideband Spread Spectrum). The Task Group requested a project number (TR-45.5/94.18.11.06 ) and provided thelatest draft text (TR-45.5/94.11.18.08©).

TR-45.5/94.11.18.10© (TR-45.5.2) is the working copy of PN-3423, Short Message Services for Wide Band SpreadSpectrum Cellular Systems (IS-637).

During open discussion, M. Epstein (Qualcomm) reported that the position in Canada, to date, has been to adopt onlyone standard. However, last week, Cantel agreed to accept the reality of more than one standard. As a result, theRADC Cellular System Plan now includes both TDMA and CDMA, but it does not include NAMPS.

M. Epstein also reported that a TIA Mobile and Personal Communications Division (M&PCD) meeting was to beheld during the following week. One of the purposes of this meeting was to begin integration of standards from thevarious standards organizations such as TIA, ITU, ETSI, etc.

Also, it was reported that TR-45 and TR-46 will begin to coordinate efforts, so as to avoid duplication.

PN-3421, IS-95-A, M OBILE STATION-BASE STATION COMPATIBILITY – DUAL MODE

A line-by-line review of the V&V version of IS-95-A, Mobile Station-Base Station Compatibility Standard for DualMode Wideband Spread Spectrum Cellular System(PN-3421) took place two weeks before this meeting.

TR-45.5/94.11.14.02 summarizes all the DDRs for PN-3421. The intent of this meeting was to close the entirebalance of DDRs, starting from 112. WG I had nine DDRs, and WG II had forty. In addition, approximately thirty-five new DDRs were received from the JTC. They are working on the PCS parallel of IS-95-A (Mobile Station-BaseStation Compatibility Standard for Wideband Spread Spectrum).

TR-45.5/94.11.18.01 is the DDR list as of November 17. In spite of some very late evening sessions, the DDRswere not completed. 393 were completed, so far, with an almost equal number of JTC DDRs outstanding. Qualcommexpressed that the expectation was to have all of these completed by the December meeting. Motorola suggested a“Candidate Document,” but it appears that the best the group can hope for is an Opening Plenary Text. The focus wasfor all of the Analog DDRs to be completed on this date. E. Chou (NTI), the V&V Chair, stated that many of theseanalog items are CDMA-specific, as opposed to merely being IS-553-related. Fundamentally, these are part of theDual-Mode scheme and, therefore, fall under the responsibility of TR-45.5 until IS-95-B is generated.



WG II reported that it hopes to have final resolution of the remaining four DDRs at the December meeting.

JEM – INTERNATIONAL ROAMING

TR-45.5/94.11.14.03© (E. Tiedemann, Qualcomm) is a presentation on Mobile Station Identities. It was generatedfor presentation at the Joint Experts Meeting on International Roaming Issues. The original intent of the JEM was toresolve the philosophical differences in approaches to IMSI by TR-45.3, TR-45.5, and TR-45.1. An additionalobjective was to make the industry aware of the numbering requirements to support IMSI.

The two ITU numbering standards under consideration are E.164, an ISDN-compatible scheme, and E.212, an IMSIscheme. TR-45.1 was said to be doing nothing about IMSI at this time. TR-45.2 felt that this is an issue to be ad-dressed in IS-41-B (Cellular Radio Telecommunications Intersystem Operations). TR-45.3 and TR-45.5 had alreadyconsidered using E.212. Later, it was discovered that the translations were too cumbersome under E.212, so E.164will be re-visited. E. Tiedemann said that the problem with using the MIN is that it uses the NANP, and the CountryIdentifier covers the MIN. With the changes in Area Codes planned for release in 1995 (digits 1 & 0 are no longer ex-clusively centered), this problem becomes worse.

In short, the process had slowed considerably; there was no consensus; and a decision needed to be made to use eitherE.164 or E.212. After considerable discussion, E.164 appeared to be technically appropriate. Since E.212 was thefirst TR-45 directive, both IS-95-A and IS-136 (Revision of IS-54 Dual-Mode Mobile Station-Base StationCompatibility to add Digital Control Channels) will need significant changes.

The proposal for adoption of E.164 will be addressed in December along with final approval of Baseline Text for SMSand Broadcast SMS. In addition, the AHAG Liaison reported approval of the revised Appendix “A,” pending finalapproval by NSA.

WG I USER NEEDS AND SERVICES

TR-45.5.1/94.11.15.04© (S. Thomas, AirTouch) proposes changes and additions to the draft text of TSB-58. Itincludes proposed text to support band class (Wideband spread spectrum standards use band class to designate aparticular CDMA frequency band) and multiplex option. Wideband spread spectrum standards provide the ability for themultiplex sublayer to be tailored to provide special capabilities. These changes had all been previously discussed orare editorial; however, it was decided that section 6.2, Proprietary Band Class, be removed. The rest will be integratedinto TSB-58.

TR-45.5.1/94.11.15.10© (E. Chao and C. Huang, Northern Telecom) is a liaison report on the October TR-45.1meeting. It addresses use of illegal MINs, IS-94/IS-91 consolidation, IMSI, and ESN-extension.

TR-45.5 .1 /94 .11.15.11 , TR-45.5 .1 /94 .11.15.15 , and TR-45.5 .1 /94 .11.17.01 are DDRs (PN-3421, IS-95-A) assigned to WG 1. TR-45.5 .1 /94 .11.15.11 (S. Thomas, Chair TR-45.5.1) contains all of the AnalogDDRs. TR-45.5 .1 /94 .11 .15 .15 is a Qualcomm DDR regarding SMS. TR-45.5.1/94.11.17.06© recommendsdisposition of the remanded DDRs. Some of the rejections were considered as being technically substantive, but couldbe held for IS-95-B. In addition, some of the DDRs were accepted by the V&V Group, but later rejected by the TG.

WG I TG I SPEECH SERVICES

The main item for discussion was the EVRC test issues, in particular, the changes in meeting dates for 1995.

EVRC TEST ISSUES

The Chair advised that funding had been confirmed as paid in full by three organizations, that we were awaiting bankconfirmation of a wire transfer from a fourth, and that two more companies had yet to advise disbursement of the finalfunding.

AT&T shipped the Speech Database on 11/8/94. The two Japanese EVRC participants were to receive their copies viaexpress carrier.

AT&T has also offered to send an executable version of a 16K LDCELP that is presently available to EVRC Codecparticipants only. Sony Corporation objected to the restrictive nature of this distribution; however, any non-participants certainly have the prerogative of contacting AT&T directly, as opposed to pursuing it through the TIA.

Qualcomm agreed to release copies of the IS-96-A source code contained in the Minimum Performance specification IS-125. This was made available on diskettes for distribution to the EVRC participants.



As a result of the meeting dates planned for 1995, the milestones identified in the EVRC Test Plan requiredmodification. The proposed changes are shown below (TR-45.5.1.1/94.11.16.01©):

July 17, 1995 Preliminary Listening Test Report delivered to TR-45.5.1.1July 21, 1995 Codec SelectionAug. 14, 1995 Detailed Codec description delivered to TR-45.5.1.1Nov. 17, 1995 Speech codec baseline text adopted by TR-45.5

Toshiba and Matsushita objected to moving out the last four completion dates of the schedule without moving the startof the Host Lab activity as well. Both companies gave the late delivery of the Speech Database as the reason for theirobjection and requested as much as a two-month schedule delay. There was considerable discussion about whether thedelay was needed at all, and some significant resistance was shown to moving the last four schedule dates out an entiretwo months, as that would delay the EVRC specification.

A compromise was suggested by AT&T to slip the start of the Host Lab activity by three weeks. This would agreewith the three week slip of the Preliminary Listening Lab results that was previously suggested to accommodate thechanges in the TIA meeting schedule. After discussion, the AT&T proposal was adopted unanimously by the group.Comsat Labs confirmed that the Host and Listening Lab schedule changes were acceptable to them.

AirTouch noted that another industry group, the CDMA Development Group, is discussing whether to ask TR-45.5 tomake all future voice codecs (13 kbit/s, in particular) backwards-compatible with IS-96-A. It was the quick consensusof the group that this was impossible.

Qualcomm will present a contribution for higher bit-rates at the January meeting.

WG I TG II ANALOG ISSUES

TR-45.5 .1 .2 /94 .11 .15 .03 (S. Dennett and J. Jayapalan, Motorola) provides text for extended protocol in IS-91teleservice and analog mode SMS. It attempts to ensure interoperability between Extended Protocol Enhanced Servicesof IS-91 and CDMA and Analog SMS of IS-91. It was deferred until the December joint meeting with WG II TG III.

TR-45.5.1.2/94.11.15.04© (F. Quick, Qualcomm) is proposed draft text for PN-3423, Short Message Services forWide Band Spread Spectrum Cellular Systems (SMS). It was also deferred until the joint meeting.

TR-45.5.1/94.11.15.12© (H. Newman, AT&T) contains SMS comments and questions on Sections 1, 2, and 4 ofPN-3423 Version 0.06.

TR-45.5.1/94.11.15.13© (H. Newman, AT&T) is a comparison of TDMA and CDMA message formats in the SMSTeleservice Layer. It attempts to illustrate the relatively large number of differences between the two.

TR-45.5.1/94.11.15.14© (H. Newman and S. Mizikovsky, AT&T) proposes reformatting the Alert with Info SMSmessage words.

Over the Air (OTA) Activation was deferred until December.

The group spent the majority of their time resolving the remaining 41 DDRs (see TR-45.5 .1 .2 /94 .11 .15 .05 andTR-45.5 .1 .2 /94 .11 . 15 .06 ).

WG I TG IV FEATURE REQUIREMENTS

TR-45.5.1.4/94.11.15.04© (E. Tiedemann and P. Yegani, Qualcomm) proposes modifications to IS-95-A to supporthigher rate (14.4 kbit/s) services. The modifications include addition of Rate Set 2 to physical layer, a new multiplexsublayer, enhanced service negotiation, and enhanced status messaging. The Plenary characterized it as a “pre-cursor” offurther modifications to IS-95-A using higher rates. E. Tiedemann advised that the JTC has already developed text inthese areas, and the group noted that TR-46 adopted two different rates as service options. This was left as an openitem for a future meeting.

TR-45.5.1.4/94.11.15.05© (J. Tomcik, Qualcomm) proposes requirements for enhancing mobile station security inIS-95. Many of the requirements can be satisfied by use of TMSIs. The rationale discussed during this sessionincluded:• A situation where the user wishes to hide his identity from eavesdropping listeners• Prevention of fraud by hiding the MIN



TR-45.5 .1 .4 /94 .11 .15 .03 (R. Dean and D. Dudich, NSA, and A. Levesque, GTE) is a re-numbered contributionregarding the STU III synchronous data discussion from the October meeting. The general opinion was to wait untilthe Carriers assign a priority to development of a Synchronous Data service (to support U.S. government needs forsecure telephone applications) before expending a lot of effort on it.

TR-45.5 .1 .4 /94 .11 .17 .01 (D. Dudich, NSA, and D. Weissman, GTE) proposes the development of synchronousdata in WG I TG V. S. Thomas (AirTouch) stated that this would be taken under consideration when developing the1995 Work Plan.

WG I TG V DATA SERVICES

TR-45.5.1.5/94.11.15.03© (F. Quick and J. Tomcik, Qualcomm) is revised draft text for CDMA packet data services.It suggests changes to the handling of virtual connections by the BS/MSC and IWF. It was forwarded to WG 1 forinformation. TG V expects to consider adoption of baseline text at the December meeting.

TR-45.5.1.5/94.11.15.04© (R. Ejzak, AT&T) is the latest version of proposed draft text for a CDMA IWF interfacestandard. It was forwarded to WG 1 for information.

TR-45.5.1.5/94.11.15.05© (R. Ejzak, AT&T) describes some of the problems uncovered while investigating theproper application of flow control on the L interface during dormant mode for packet data.

TR-45.5 .1 .5 /94 .11 .16 .02 (J. Jayapalan, Motorola) contains comments on open interface to IWF Version 5. Itincludes some additional clarification on usage of LAPD and Ethernet.

TG V intends to resolve the remaining outstanding issues on the IWF interface standard at the December meeting.

WG II SIGNALING PROTOCOLS

TR-45.5.2/94.11.15.01© (S. Chander and S. Mizikovsky, AT&T) proposes an alternative to the use of the GeneralPage Message (GPM). It recommends using the dedicated paging slot for Broadcast SMS and informing mobiles aboutservice availability in an Extended System Parameters Message (ESPM). It was remanded to TG III.

TR-45.5.2/94.11.15.02© (J. Tomcik, Qualcomm) recommends actions for the IS-95-A DDRs regarding Set 2 (i.e.,DDRs numbered 291, 304, 315, 316, 37, 38, and 51).

TR-45.5.2/94.11.15.03© (F. Quick, Qualcomm) recommends actions for some of the PN-3421 DDRs assigned to WGII.

TR-45.5.2/94.11.15.04© (F. Quick, Qualcomm) proposes changes to IS-95-A to clarify the digits encoding forauthentication signature calculations. This was approved.

WG II TG III CALL PROCESSING, SIGNALING FORMATS, AND PROTOCOLS

TR-45.5 .2 .3 /94 .11 .16 .04 contains DDRs for PN-3421. TR-45.5.2.3/94.11.17.01© (F. Quick, Qualcomm)proposes resolution of DDRs 347 and 348 with a set of text changes for PN-3421.

TR-45.5.2.3/94.11.16.05© (F. Quick, Qualcomm) discusses some remaining issues in broadcast paging proceduresand recommends resolutions for these issues.

TR-45.5.2.3/94.11.16.07© (F. Quick, Qualcomm) is proposed draft text for PN-3423 presented on November 16.TR-45.5.2.3/94.11.17.02© (F. Quick, Qualcomm) is the revision of PN-3423 (IS-637) presented on November 17. Itincludes broadcast paging and message delivery procedures, including IS-91 extended protocol text based upon aproposal by Motorola and corrections based upon comments from AT&T.

TR-45.5 .2 .3 /94 .11 .16 .08 (S. Dennett and J. Jayapalan, Motorola) proposes text for extended protocol in IS-91teleservice and analog mode SMS. It attempts to ensure interoperability between Extended Protocol Enhanced Servicesof IS-91 and CDMA and Analog SMS of IS-95.

WG III PHYSICAL LAYER

WG III spent most of its time working on the completion of IS-95-A.

S. McConoughey (Panasonic), Chair WG III will serve as editor for changes to IS-97 (Recommended MinimumPerformance Standards for Base Stations Supporting Dual-Mode Wideband Spread Spectrum Cellular Mobile Services)



and for IS-98 (Recommended Minimum Performance Standards for Dual-Mode Wideband Spread Spectrum CellularMobile Stations). All changes will be held until the next revision of IS-97 and IS-98.

TR-45.0.A AD HOC AUTHENTICATION GROUP

(Ediotr’s Note: The documents in this section are not available for distribution from CSR.)

The expansion of the ESN from 32 bits to 56 bits was discussed. It was generally felt that this will not cause aproblem, as it does not impact the Common Cryptographic Algorithms. However, it was agreed that this couldinvolve numbering changes with the FCC.

U.S. Bill HR-4922 was discussed. Fundamentally, it has a provision for serving prison time at a Federal Penitentiaryfor tampering with ESNs, but it also includes a provision for authorized government wire-tapping. It is not specific asto whether this occurs at the switch or at the Air-Interface, and it provides for reimbursement of any involved costs tothe Carriers.

Two-Tier Security was then discussed. It was not clear whether TR-45.3 has formally adopted the Two-Tier approach.AHAG (Ad Hoc Authentication Group) has opted for the One-Tier System. Under Two-Tier, the U.S. would have themost secure system, but the exportable version would be less secure. The MS would have both capabilities, under thedetermining control of the BS.

A brief discussion ensued regarding various algorithms. The original CAVE Algorithm is for Authentication.However, when the TR-45.3 Data Working Group discovered that the privacy mask was easily penetrated, the ORYXand BRAID algorithms were proposed for data usage. The BRAID Algorithm is a Motorola hardware proposal that wasdropped in favor of the AT&T ORYX software proposal.

TR-45.0 .A/94.11.16.04 (L. Owens, Chair) contains excerpts from the Export Control talk provided by M. Koro(NSA) at the April AHAG meeting. Slide #4 explains Controlled Commodities. It was presented for information.

TR-45.0 .1 /94 .11.16.07 (L. Owens, Chair) is a list of security-relevant documentation developed by the TIA andits formulating groups. It was provided to assist T1S1 and any other standards committees in their work on privacy,data confidentiality, and authentication. It was presented for information.

TR-45.0.A/94.11.16.08© (L. Owens, GTE) is an article from the December 1993 issue of IEEE Micro entitled “ASurvey of Encryption Standards.” It is very comprehensive and contains important information about cryptography. Itwas presented for information.

TR-45.0.A/94.11.16.09© (TR-45.5 Liaison) covers Over-The-Air Activation (OTA), Stage 1. A general overview ofOTA work in TR-45.5 was presented by S. Thomas (AirTouch). The Stage 1 Service Description has been approvedby WG I; WG II will develop signaling. The A-Key is not encrypted, but is derived through an exchange of messages,as it is centered around the Diffie-Hellman Algorithm (see TR-45.0.A/94.11.16.08©). This meets most securityrequirements; however, it is not a definite selection and does not preclude the use of other algorithms. Nocontributions have been received with any specific alternatives. OTA could become a TSB for IS-95-A, but this hasnot yet been determined. If it is the case, then the TSB will eventually be folded into IS-95-B.

TR-45.0.A/94.11.16.10©, Requirements for the HOOK Variable (F. Quick, Qualcomm), proposes changes to“Common Cryptographic Algorithms, Revision 1” to clarify proper use of the HOOK variable for data encryption inmask generation. TR-45.0.A/94.11.16.16© is a revised version.

TR-45.0.A/94.11.16.11© (F. Quick, Qualcomm) is Revision 1 of the Common Cryptographic Algorithms (ITARDocument); TR-45.0.A/94.11.16.12© (F. Quick, Qualcomm) is a draft of the Interface Specification for the CommonCryptographic Algorithm, Revision 1.

TR-45.0.A/94.11.16.13© (F. Quick, Qualcomm) provides a draft Appendix A for PN-3421 (IS-95-A). It incorporatestext changes for encryption of continuous DTMF orders, references IS-95-A instead of IS-95, and references CommonCryptographic Algorithms, Revision 1.

TR-45.0.A/94.11.16.14© (S. Mizikovsky and S. Chander, AT&T) provides text for inclusion of the Alert With InfoSMS message in the Appendix A of IS-95-A.

TR-45.0.A/94.11.16.15© (F. Quick, Qualcomm) contains information about data security for CDMA packet dataservices that is either ITAR-controlled or has restricted distribution under the TIA Technology Transfer Plan. It is pro-posed as baseline text for Appendix A of the proposed packet data standard (PN number not yet assigned).



TR-45.0.A/94.11.16.17© is a draft of IS-95-A Appendix A, “Message Encryption and Voice Privacy,” dated October20, 1994.

John Gabor

REPORT OF RAPPORTEUR’S MEETING OF Q1/8 APPLICOMNOVEMBER 17 – 18, 1994, SUNNYVALE. CA

SG 7 MEETING RESULTS ON T.611

The report from the Study Group 7 meeting was not available, since the meeting ended one week prior to this meeting.Study Group 7 did discuss T.611. It was mentioned that a statement from the Rapporteur has been sent from Q14/7 toQ1/8 asking for the postponement of Resolution 1 to the E-Mail enhancements to T.611.

SCSA PRESENTATION

S. DeLateur (Gammalink) presented SUN-7 , SCSA (Signal Computing System Architecture) FAX System ServiceAPI. SCSA is a comprehensive hardware and software architecture for building call processing systems. The softwarearchitecture supports a number of system services with a client-server orientation. The fax system is based on T.611.

Some of the T.611 functions have been adapted for use within SCSA FAX System Service API. A cross referencebetween T.611 terms and the equivalent terms used in SCSA FAX System Service API is provided.

SCSA is an open standard. SCSA can be considered as an input for future work on a High Level Interface forTelecommunications based on T.611 framework.

FURTHER WORK ON T.611

It was decided to progress T.611 by providing a general overview to T.611 for the next SG 8 meeting (March 1995).This document will be a stand-alone Recommendation. The extended T.611 model as provided in SUN-9 (Extensionof T.611 for client/server applications, J. Rafferty, Human Communications) will be integrated as an example in theoverview document. The T.611 editor (R. Grundmann) is appointed as editor for this document.

New procedures for new extensions will also be created. It was agreed to create a open forum where the extensions willbe defined. The aim is to agree upon these extensions before standardization. K. Krechmer (ACTION Consulting) wasappointed to set up a reflector forum to discuss:• Run-time access

–voice–interactive file transfer–directory

• Integration of lower interface facilities (run-time aspects relating to TR-29 Class 2, CAS, ISDN-ProgrammableCommunications Interface, etc.)

• Provision for intercommunication between different CAs• Provision for multiple attachments with regards to E-Mail

MAPPING OF T.611 TO MAPI, VIM, CMC

The intention of the group is not to compete with other standards (VIM, MAPI or CMC) regarding E-Mail interfacefacilities, but to show that the design of T.611 allows the access to these E-Mail interface facilities.

SUN-2 , T.611 Mapping to standard E-Mail (J. P. Dick, France Telecom), was presented for information. This paperspecifies the mapping of ITU-T Rec. T.611 to widely available standard E-Mail interfaces (CMC, MAPI, and VIM).The group decided to revise the abstract of SUN-2 , and to include TDD mapping to MAPI, VIM and CMC as well.

The implementation of the specification is still not completed for:• Access to directory services,• Directions on how to handle attachments depending on the underlying E-Mail engine.Delegates are requested to provide contributions.



EDITORIAL COMMENTS ON T.611

The editorial corrections to T.611 proposed by Germany in SUN-4 were agreed. The Q1/8 chair will forward thesecorrections to Mr. Zhao, ITU SG 8 representative.

T.611 E-MAIL IMPLEMENTATION OMISSIONS

During the implementation of T.611 to E-Mail, some omissions in handling the Interpersonal Notification, DeliveryReports and Non-Delivery Report have appeared. SUN-8 (R. Grundmann, DBT, Germany) proposes a solution tothis problem. The group agreed to postpone the decision to the next meeting.

RUN-TIME ASPECTS

In discussion it was felt that the word “Run-time” seems more appropriate than “Real-time” where used in SUN 3 .

It was agreed to take SUN-3 , T.611 Extensions – Exchange Mechanisms, as a basis for a future RecommendationT.61x. However, before defining a technical specification, it was agreed to provide an overview, with the help of thereflector. The topics to be addressed include:• Complete handling of the buffering• Interactive file transfer• Fax to a remote server• V.34 modulation and negotiation• Directory management

These standards can be considered as inputs:• IS 101• SCSA

ONGOING WORK IN EUROPE

For information: ETSI (the European Telecommunications Standardization Institute) has approved a conformancetesting specification for Recommendation T.611 (1992).

ROSTER OF Q1/8 RAPPORTEUR’S MEETING, NOVEMBER 17 – 18, 1994, SUNNYVALE, CA

Jean-Paul Dick, France Telecom - S.E.P.T. Q1/8 Rapporteur

ACTION Consult. (U.S.A.) Ken KrechmerBvrp Software (France) Roger PolitisDBT-FTZ (Germany) Ralf GrundmannDBT-FTZ (Germany) Günther StoyeF&P (Germany) Matthias FreyFirst Telecom (France) Rodolphe GoldsteinFrance Telecom Alain ChaillatFrance Telecom-SEPT Jean-Paul DickGammalink (U.S.A.) Stephen DeLateurGammalink (U.S.A.) Mark RollinsGammalink (U.S.A.) Eric TannenbaumHuman Comm. (U.S.A.) James P. RaffertyMT & I Assoc. (U.S.A.) H. S. MagnuskiTelino (France) Mr. Nguyen



REPORT OF Q3/15 RAPPORTEURS’ MEETING ON AUDIO VISUAL–MULTIMEDIA SYSTEMS, NOVEMBER 28 – 30, 1994, MIDDLETOWN, NJ

The objective of this meeting was to discuss enhancements to multipoint recommendations H.231 and H.243(Rapporteur: D. Skran, AT&T) and the other H-series system recommendations H.221, H.230, H.242, and H.244(Rapporteur: N. Kenyon, BT). There was also a short discussion of the B-ISDN draft recommendations H.24X andH.23X.

Major points of discussion at the meeting were the procedures for dealing with restricted networks (H.320 terminals,H.243 multipoint control units, and interworking with unrestricted networks) and the enhancement of multipointworking to Continuous-Presence-Multipoint. In addition, a large number of minor points of correction andimprovement of the drafts were agreed.

The output documentation from the meeting is as follows• Corrections to H.221, H.230 and H.224 (which were frozen in May 1994 and will be voted for Res. 1 in February

1995) will be introduced at the February Study Group meeting by means of a Rapporteur’s TD;• New material for future enhancement of H.221 and H.230 will be put forward to SG 15 as a delayed contribution;• Revisions to H.231, H.242 and H.243 were prepared and sent to Geneva as white documents for the February SG

15 meeting; further corrections will be submitted in Rapporteurs’ TDs.

All the above documents will be made available by e-mail when finalized (contact [email protected] [email protected]).

RAPPORTEUR REPORTS

N. Kenyon (Rapporteur, BT) reported that H.221, H.230, H.244, and H.233 were frozen at the May 1994 meeting,with intent of putting them to Resolution 1 at the February 1995 SG I5/WP1 meeting.

D. Skran (Rapporteur, AT&T) reported that H.281 and H.224, which had been put to Resolution I at the May 1994SG 15/WP I meeting, have been distributed by the ITU-T under the Resolution 1 guidelines. This was announced in acircular letter from the Secretariat in November 1994.

S. Okubo (Rapporteur, GCL) reported on the results of the Singapore ATM expert’s meeting. H.262 has manychanges, thus a need exists to make input to the February 1995 meeting. S. Okubo will prepare a delta document ofchanges. H.262 and H.222.0 are approved by ISO-IEC, with ITU-T approval scheduled for February 1995.

H.222.X covers multiplexing and synchronization for MPEG2 on ATM. H.222.0 will be common text with MPEG2;H.222.1 will be a subset of H.222.0. The following are scheduled for a February 1995 text freeze:• H.32X: MPEG2 on ATM• H.32Y: H.320 on ATM• H.32Z: H.320 on LANsTechnical trials will be in 1995. Steady progress is being made; the next meeting will be January 1995 in Tokyo.

S. Okubo reported that only a few changes in H.320 were called for, but that in the area of audio level setting, a strongneed exists for input and ideas.

GENERAL

MID-45 (D. Zeck, VideoServer) is a presentation on the ANSI standardization process for North American standardsequivalent to ITU-T H.221, H.230, H.231, H.242, H.243, and H.320.

MID-9 (France Telecom) provides general comments on the need for new BAS codes and the desirability of usingSBEs rather than MBEs. It note some issues And it discusses proposed additions to H.243 to better support Multi-MCU configurations with interworking between H.AGG (for AV requirements) and ISO Bonding (for datarequirements).

MID-40 (M. Yamashita) is a preliminary discussion on Questions for the next study period. It notes that there areprocedures in Res. 1 for introducing new questions during a Study Period.

RESTRICTED NETWORKS

Discussion was based on a summary of restricted network issues as developed in the USA, presented in MID-6 (D.Hein, VTEL). MID-2 (N. Kenyon and N. Towers, BT) provided a separate analysis of the problem, reaching similar



conclusions. Further comments and description of practical problems were provided by Japan in MID-14 (Commentson Restricted Network Operation) and MID-15 (Problems in the actual Restricted Network Environment).

As a result of discussions it was agreed that three new capability codes would be introduced into H.221, identifying twodistinct restricted modes and also a negative capability (for the case of a terminal on an unrestricted network which isnot equipped to deal with restricted interoperation). There will be no new commands. To deal withintercommunication between two MCUs, three new SBE symbols are to be included in H.230. MID-3, Capture ofNetwork Addresses (N. Kenyon and T. Midwinter, BT), proposes a solution for the situation where a calling terminalhas established an initial connection to a destination via a supplementary service (such as call transfer), and cannotreadily infer the network address for requesting any additional calls.

New material will be introduced into the revision of H.242 to clarify the use of these new codes in the expected varietyof terminal/network configurations, included the “bottleneck” situation when both terminals are on unrestricted net-works but the connection chain includes a restriction.

Existing terminals and MCUs cannot use or recognize these new codes: this will be taken into account in the text,though precise rules for new/old interworking will not be laid down. MID-21© (ANSI H.242) includes a proposedmethod of achieving interworking in cases where absence of network timing at a terminal prevents direct identificationof stuffed bits. Essentially, the method employs digital loopback at the remote end and adjustment of the bit orien-tation of transmitted signals until correct destuffing is achieved. This method will be included as an option in H.242rev. MID-22 lists the substantive changes to ANSI H.242 since the first ballot.

CONTINUOUS PRESENCE MULTIPOINT

The meaning of “continuous-presence multipoint” is that at each videoconference terminal one may see pictures fromall the other sites (ideally all, but at least several). It is not the aim of SG 15 to standardize all methods of doing this,but to provide a standardized infrastructure whereby a variety of such services may be harmoniously provided.

There were several contributions on this interesting topic:• “Continuous presence video bridging based on H.261” (MID-1, T. C. Chen, Bellcore)• “Video rate control for multipoint conferences” (MID-7, D. Hein, VTEL)• “Continuous presence for H.320 multipoint conferences” (MID-8, PictureTel)• “Continuous presence videoconferencing methods” (MID-29, F. Schmidt, AT&T)• “Reduction of the bit rate of compressed video while in its coded form” (MID-30, BT)• “Low-delay center-bridged and distributed combining schemes for multipoint videoconferencing” (MID-44, T.C.

Chen, Bellcore)

From the contributions, the meeting distinguished three general approaches:

a) Video mixing (for example, four equal pictures combined into one) without modification to existing terminals;

b) Video mixing involving video flow control: terminals must be modified on their transmit side;

c) Transmission of multiple video streams to each terminal: terminals must have multiple decoders.

It was felt that (b) and (c) are not yet mature enough for standardization, and will be reconsidered at future meetings.Method (a) requires little new standardization, and may proceed immediately.

The term “picture composition” was introduced to refer to the size and disposition of multiple pictures on a mixed-video stream conforming to H.261. It should be possible for an MCU to provide a choice of compositions, and foreach terminal independently to make its own selection. There is a need then for• Controls to offer and make these choices, and• Indication as to the actual picture composition in force.Given the wide range of possibilities, it was agreed that the T.120 protocol should be the principal vehicle for this,though a small number of standard compositions could be indicated to any terminals not having T.120 protocol byusing an expansion of the VIN* symbol defined in H.230. Members undertook to confirm that the forthcomingT.AVC draft (under ITU SG 8 Question 10) would contain the necessary provisions. It was also agreed that SG 15itself should be responsible for the “application” of CP (continuous presence) multipoint, which would reside aboveT.AVC.

The revision of H.243 (MID-17) will take into account the above conclusions.



H.221, FRAME STRUCTURE

Corrections agreed to:• Clarification of audio mode when switching from unrestricted to restricted operation• Addition of MLP-8k capability and command• New Restrict capabilities as above• Clarification of reasons for bit allocation for ISO audio (Figure 5)• Bit sequence for combining MLP and H-MLP (High speed MLP)• Escape table for conveyance mode preferences.

MID-27© is a draft copy of ANSI H.221. MID-28 lists the substantive changes to ANSI H.221 since the firstballot. MID-35© is a marked up copy of Draft Rev. H.221, dated 9-94.

MID-10 (D. Lindbergh, PictureTel) suggests that the MLP-8k codepoint in bit 7 was inadvertently left out of therevised H.221. MID-11 (T. Nakai, OKI, Japan) also suggests corrections to H.221.

H.230, FRAME SYNCHRONOUS CONTROL AND INDICATION

Corrections agreed to:• Clarification of scheme for capturing network addresses• Code points for restricted MCU-MCU use• Clarification of use of loopback codes.

MID-25© is a draft copy of ANSI H.230. MID-26 lists the substantive changes to ANSI H.230 since the firstballot. MID-36© is a marked up copy of Draft Rev. H.230, dated 9-94.

MID-31 (D. Skran, Rapporteur) is a revision of the mode preference proposal.

H.244, SYNCHRONIZED AGGREGATION

Corrections agreed to:• Clarification of fault types• Correction to section 6, to refer to ISO/IEC13871 “signals”, rather than “framing”• Clarification to rules for substitution of “null” capabilities.

It was noted that, as presently worded, ISO/IEC13871 (BONDING) does not allow selection of the audiovisual modewhen both endpoints are capable of doing so; members will approach their NSOs to request a modification in thisrespect.

A Rapporteur’s TD will be brought in to the February meeting with the above changes.

MID-16 (Japan) comments on draft Rec. H.244. MID-37© is a marked up copy of Draft Rev. H.244, dated 9-94.MID-38 (E. Gonfia, France Telecom CNET) proposes automatic detection of BONDING or H.244 framing and NIA(Network Indicate Address) messages in TAC (Terminal-Aggregator Communication) case communications. MID-9was presented by Y. Robin-Champigneul (France Telecom). Section II comments on H.AGG were discussed; allcomments have been taken account by the revised H.244 .

H.242, PROCEDURES FOR ESTABLISHING COMMUNICATIONS

MID-4 summarizes proposed revisions to Rec. H.242 made by various members to the May SG 15 meeting; thesewere accepted.

Corrections agreed to:• Further adjustments are made to Section 9 on data channel procedures (clarification and initialization of Mode 0

forcing, data channel procedures, transmission of network addresses)• Addition of a procedure for expressing preference as to which mode should be sent from the remote end point• Restricted network operation (see above)• Capset organization for terminals having some real and some dummy data capabilities.

MID-13 (K. Sakai, Fujitsu, Japan) provides comments on draft Rev. H.242.

MID-21© is a draft copy of ANSI H.242. MID-22 lists the substantive changes to ANSI H.242 since the firstballot.



H.231, MULTIPOINT CONTROL UNIT (MCU)

Editorial changes only were made. MID-23© is a draft copy of ANSI H.231. MID-24 lists the substantive changesto ANSI H.231 since the first ballot.

H.243, PROCEDURES FOR ESTABLISHING MULTIPOINT

Corrections agreed to:• Clarification of initialization procedures: continuous-presence (as above)• Clarification of assignment of master MCU• User-initiated connection establishment• Provision for restricted network operation• Opening/closing/rate changing the MLP data channel• Clarification of terminating a conference• MCU loopback procedures• Numerous lesser and editorial clarification points.

MID-19© is a draft copy of ANSI H.243. MID-20 lists the substantive changes to ANSI H.243 since the firstballot.

H.24X, MULTIMEDIA SYSTEM CONTROLH.32X, MPEG2 ON ATMH.32Z, H.320 ON LANS

Drafts were presented in MID-5 (H.24X), MID-42 (Draft H.32X) and MID-43 (Draft H.32Z), but little timeremained for discussion; comments on these are to be sent to the Rapporteur S. Okubo.

MID-41 (S. Dunstan, Siemens) is a draft of H.222.1 created from the Singapore ATM expert’s meeting.

H.320, NARROW-BAND VISUAL TELEPHONE

A proposal in MID-46 (S. Okubo, GCL, Japan) proposes procedures for audio level setting in H.320 terminals; thismust be given further consideration. MID-18© is a draft copy of ANSI H.320.

TD-48 is the draft H.32Y (H.320 on ATM) from the Editor; H. Radha (AT&T Bell Labs).

Norman D. Kenyon, British Telecom

Q3/15 RAPPORTEUR’S MEETING ROSTER, NOVEMBER 28 – 30, 1994, M IDDLETOWN, NJ

Dale Skran, AT&T Rapporteur, H.231 and H.243Norman Kenyon, BT Rapporteur, H.221, H.230, H.242, and H.244

Host: AT&T Global Business Communication Systems

AT&T John Biggs Logicon John BurkeAT&T Gary Corcoran CLI Dan KlenkeAT&T Dave Horn NCS Gary RekstadAT&T Vinnie Paterno NTT, Japan Hiroshi KoteraAT&T Bob Reynolds NTT, Japan Makoto YamashitaAT&T Tony Schiano PictureTel Steve BorzkoAT&T Fred Schmidt PictureTel Dave LindberghAT&T Li Yan Teleos Chip SharpBellcore T.C. Chen Televerkets forskinings- Helge SandgrindBellcore Sien Chow institutt, NorwayDelta Info. Systems Neil Randell US Dept. of Defense Ralph LiguoriDelta Info. Systems Dick Schaphorst VideoServer Dan ZeckFrance Telecom - CNET Yves Robin-Champigneul VTEL Dave HeinGCL, Japan Sakae Okubo



REPORT OF TR-30.1, MODEMS, DECEMBER 9, 1994, ORLANDO, FLEditor’s note: The reports of TR-30.2, TR-30.3 and TR-30.4 meetings December 5 – 8 will be in the next issue ofCommunications Standards Review.

LIAISON

TR-30.1/94-12-093 is a detailed report of the V.8bis Rapporteur’s meeting in Juan les Pins, France, November 7 -10, 1994.

G. Griffith (Rockwell) gave a brief report on items to be included in a liaison to be presented to the SG 14 WorkingParty 1 meeting December 12 – 16, 1994.

COMPRESSION OF SYNCHRONOUS DATA

TR-30.1/94-12-095 (K. Schneider, Adtran) is an overview of the status of the of the ad hoc group on datacompression in digital DCEs. The consensus position is to use the Point-to-Point Protocol (PPP) with extensions forterminal adaption (based on T.120) and PPP LZS-DCP (Data Compression Protocol based on Stacker LZS). The goalis to have a document ready for ANSI ballot out of the February TR-30.1 meeting.

TR-30.1/94-12-096 , TR-30.1/94-12-097 , and TR-30.1/94-12-098 (ad hoc Committee on Compression ofSynchronous Data for DSUs) provide the technical details of the proposed Compression of Synchronous Data for DSUsstandard. They are available as Internet drafts.

V.34

TR-30.1/94-12-099 (B. Betts, AT&T) presents test results for a V.34 modem operating at a duplex data signalingrate of 33600 bit/s. The results indicate satisfactory operation (<10 block errors per 10k blocks) when tested on asimulated line including mild loops with 1 µ-law PCM link. This document will be presented as D-68 at theupcoming Working Party meeting.

B. Betts noted that adaptive precoding was active; precoding and constellation shaping were not used. In response toquestions about performance on actual connections, it was reported that there is currently insufficient data to draw anyconclusions.

TR-30.1/94-12-094 is a proposed TIA project request for a domestic standard for error control on cellular links.After some discussion it was decided to expand this work to include modulation. It was also agreed that this workwould be closely tied to the ongoing work on cellular in SG 14.

Dick Brandt, dB Consulting

TR-30.1 MEETING ROSTER, DECEMBER 9, 1994, ORLANDO, FL

Les Brown, Motorola TR-30.1 Chair

Adtran Kevin Schneider Intel King ChangAMP Jack Bradbury Intel Barry O’MahonyAT&T Bill Betts Radish Ken KrechmerAT&T Dick Brandt Microsoft Charlie GarthwaiteAT&T Fred Burg Motorola - ISG Les BrownAT&T John Scaramalis Motorola - ISG Jack DouglassBellcore Wes Henry Multi-Tech Systems Tim GunnBellcore Fred Link Penril Datability Netwks Dick StuartDigital Equipment Corp Remi Lisee Primary Access John RosenlofDSP Group Ron Richter Primary Access Richard WilliamsGDC Yuri Goldstein PCSI/RSA Paul SawyerGDC Fred Lucas Rockwell Glenn GriffithHayes Dave Rife US Robotics Chris CoffinIBM Ramin Nobakht



REPORT OF Q1/14 ASSOCIATE RAPPORTEURS MEETING FOR V.8BISDECEMBER 9 – 11, 1994 ORLANDO, FL

SAVD-94-068 is the report of the V.8bis Rapporteurs meeting in Juan les Pins, France, Nov 7 - 10, 1994. Itsummarizes the progress and open issues to date.

SAVD-94-069 (K. Krechmer, on behalf of Radish Communications) proposes that the single dual tone approach issuperior to the multiple dual tone approach in that it uses less processing power and superior immunity to talk-off.During the discussion, AT&T noted that the multiple tone proposal does not require the detection of more than twodual tones at any given time. K. Krechmer countered with the case of a call transferred from agent to agent. In thiscase, the AT&T proposal would require sensing of all four dual tones.

SAVD-94-070 (K. Krechmer, on behalf of Radish Communications) addresses the frequencies proposed by AT&Tfor the dual tones. Frequencies were evaluated with the following considerations:• Interference with in-band signaling systems• Interference with V.21• Dynamic range at the receiver• The need to avoid tones close to the ratio of two small integers.SAVD-94-070 quotes as its source a Bell System Technical Journal (January 1960). It concludes that the tonesproposed in SAVD-94-034 (VoiceView partners) will perform better that those in the multi dual tone approach.

SAVD-94-071 (K. Ko, AT&T) addresses concerns over potential interworking problems with existing terminalconfigurations created by the introduction of V.8bis. A wide range of scenarios are examined. The paper concludesthat no significant case would be adversely affected by the introduction of V.8bis.

Discussion addressed other scenarios not covered by the paper. Specifically, the “late connect” scenario was raised, butafter some discussion, it appeared to be less of a problem than with existing data calls.

SAVD-94-072 (K. Ko, AT&T) proposes two possible methods of encoding manufacturer-specific modes ofoperation in V.8bis. One requires the establishment of a V.8bis branch (requires registering once under V.8bis). Theother uses the X.208 methodology. The former requires much less information to be exchanged at the expense ofrequiring a new registration authority to be created.

The group broke into a smaller session to review the various scenarios. The major problems are still between thosewho favor up-front negotiation and those who prefer to wait until a higher speed link is established. Those who favorup-front negotiation see the major benefit as minimizing the interruption of the voice call. Those who favor the latterapproach prefer the benefits of higher speed and minimal change to V.8.

SAVD-94-073 (K. Ko, AT&T) is an updated version of the draft recommendation V.8bis. K. Ko highlightedSection 9, Operating Procedures . The section contains the details of the signal exchanges associated with each ofthe scenarios. He gave a detailed presentation covering all of the scenarios, and emphasized that the set of signals andsequences could be used to support a wide range of scenarios.

During the discussion, a question was raised about the use of CL (Capabilities List) in Figure 12. It was clarified thatthe author assumed that a general capabilities exchange would be more appropriate after the call was established. It wasalso clarified that this scheme relies on the detection of signals in the presence of other signal (e.g., CNG) and thereforedoes not provide the customary silent periods for detection.

SAVD-94-074 (K. Krechmer, on behalf of Radish Communications) is a proposed draft V.8bis submitted by Radishas an alternative to SAVD-94-073 . This paper expands V.8bis to encompass provisions for upgrading pre-existingequipment. Capability exchanges for AVD are also included.

It was clarified that the terms calling, originating and answering, should be considered to mean either initiating andresponding (whichever is appropriate). Figure 24 appears to not wait for an ACK or NAK. It was clarified that thereis a 2 second response timeout that could be bypassed with a priori knowledge. If the 2 second timeout is used,however, it appears that this proposal would exceed the maximum 2 second interruption criteria. It was also pointedout that the use of 2750 Hz (one tone in ADSI CAS [CPE Alerting Signal] dual tone) could cause problems in theleased line environment as a commonly used NCTE (AT&T 829) in North America loops the circuit in response to a2713 Hz tone. However, the leased line environment is recognized as a small application for V.8bis. There was alsodiscussion about Analog Display Services Interface (ADSI) and its possible impact on this proposal which uses thesame CAS tone for ADSI interworking. A concern was raised over both ADSI and V.8bis. W. Henry (Bellcore) notedthat there is work in progress to standardize ADSI in several parts of the world including an active project in ETSI.



There were questions about the use of modulated 2100 Hz without the knowledge that the terminals are V.8bis-compatible. It was noted that this is done only when a priori knowledge is available.

At the request of C. Garthwaite (Microsoft), the group reviewed the Capabilities Exchange and Selection ProtocolObjectives (SAVD-94-27 , appendix to the September 12 - 16 Vienna meeting report) with the proposed changespresented in SAVD-94-36 by the VoiceView Partners. It was agreed to add the objective to allow upgrading ofexisting systems where possible.

The Rapporteur tried to get the group to examine SAVD-94-073 and SAVD-94-074 and come up with acombined document. Rockwell suggested considering V.8 as the primary document to be considered in this discussion.This led to a discussion about how to accomplish this combining without a document proposing specific solutionswithin the V.8 structure. It was agreed to break into two drafting groups at the upcoming WP meeting: one onintegrating SAVD-94-073 and SAVD-94-074 chaired by L. Brown (Motorola), and the other to expand V.8 toaccomplish the needs of the SAVD work chaired by G. Griffith (Rockwell).


Q1/14 V.8BIS RAPPORTEURS MEETING ROSTER, DECEMBER 9–11, 1994, ORLANDO, FL

Klaus Kern, DBP-Telekom Chairman SG 14Dick Brandt, AT&T Chairman WP 14/1John Magill, Cray Communications Rapporteur Q1/14 V.savdLes Brown, Motorola - ISG Associate Rapportuer V.8bis

AMP Jack Bradbury Intel Barry O’MahonyAT&T Dick Brandt Intel King ChangAT&T Mike Buckley Integrated Info. Tech. Ping DongAT&T Fred Burg Microsoft Charlie GarthwaiteAT&T Ken Ko Motorola - ISG Les BrownAT&T Larry Smith Motorola - ISG Jack DouglassAT&T John Scaramalis Motorola - ISG Chip GuslarBellcore Wes Henry Multi-tech Systems Tim GunnBellcore Fred Link PCSI/RSA Paul SawyerCompaq Computer Bob Watts Penril Datability Netwks Dick StuartCray Communications John Magill Primary Access John RosenlofDBP-Telekom Klaus Kern Primary Access Richard WilliamsDSP Group Yair Be’ery Radish Comm. Systems Ken KrechmerGDC Fred Lucas Rockwell Bernard DebbaschGDC Yuri Goldstein Rockwell Tom GearyHayes Dave Rife Rockwell Glenn GriffithIBM Ramin Nobakht US Robotics Chris CoffinIBM Ali Sadin



REPORT OF SG 14 WORKING PARTY 1 , DATA COMMUNICATIONS OVERTHE GSTN, DECEMBER 12 – 16, 1994, ORLANDO, FL

Q1/14 V.34

The Rapporteur is R. Stuart (Penril, USA).

DT/13 , a liaison from SG 1, requests the consideration of an alternative startup for V.34 when used in a videotelephone application. The suggestion is to startup in voice mode and accomplish some of the training of V.34 in thebackground and then switch to voice data.

DT/5 is a patent statement from Rockwell.

D.67 (AT&T) contains a proposal for increasing the data signaling rates of V.34 to 33,600 bit/s; D.68 contains testresults. The proposal is a simple method for increasing the bit rate by increasing the number of encoded bits from 9bits/symbol to 10 bits/symbol. The test results indicate good performance over a channel with a single codec and mildanalog loops.

Discussion clarified that this new rate, if accepted, would have to be optional. It was also suggested that the bitassignments be changed to allow for a more logical addition of other rates in the future. A caution was raised that bitsbetween 30-34 in the INFO 1 sequence may be used in a proprietary implementation which may not ignore these bits.No final decision was made at this point.

Q1/14 V.SAVD

DT/21(J. Magill, Cray, UK) outlines the SAVD progress to date. It indicates the various subcategories into whichthe work has been broken:• Overall start-up procedure (V.8bis)• Alternating voice data (no proposals to date)• Analog simultaneous voice/data (ASVD)• Digital voice and data (DSVD)

–Multiplexing–Digital voice coding

• DTE-DCE interface configurations.

Motorola requested changes to both DT/21 and DT/15 (Vienna meeting report) to reflect that the AT&T proposal forV.asvd was only baseline text not the agreed basis for the work.

DT/29 is the report of the November Rapporteur’s meeting on V.8bis.

W. Pechey (Hayes, UK) gave a verbal report of the progress to date on the multiplexing work. Two proposals arebeing considered, one based on a packet-mode technique and the other based on LAPM. It appears that SG 14’srequirements differ from those of SG 15. No decisions have been made.

The group agreed that the work on V.8bis has the highest priority in that it impacts other SGs as well as both aspectsof SVD. The second priority is the choice of a speech coder. Next is the progression of the ASVD work. J. Magillidentified the need for liaison with SG 15 and SG 12.

A question was raised about the need to modify V.34 to accommodate V.8bis. The group generally concluded that itwas not clear that V.34 would need to be modified.

AVD

D.60 (M. Winseck, representing Ameritech, USA) is a collection of four TR-30 papers addressing the issues relatingto alternating voice data. The first paper recommends a common methodology for switching between the variousmodes (e.g., voice, data, fax). The second presents criteria for voice/data multiplexing, the third is a copy of a Bellcorepresentation on caller ID, and the last paper provides guidance on the selection of tones.

D.61 (M. Winseck, representing Ameritech, USA) describes applications for alternating voice data.

In response to a question from the Rapporteur, M. Winseck indicated that a more complete proposal for AVD would beprovided to a future meeting.



ASVD

DT-9 (K. Ko, AT&T, USA) is a revised Draft Recommendation V.asvd, created from the baseline text at theSeptember Rapporteurs meeting. K. Ko gave a short overview of framed Quadrature Audio/Data Modulation (QADM),prior to going into the details of the document. QADM combines an audio signal component with the data signalcomponent. When voice and data are sent simultaneously, the data signaling rate is 4800 bit/s; however, the effectivethroughput for an average call was approximately 9600 bit/s due to the ability to switch to 14,400 bit/s during silentperiods.

Motorola suggested that the title should be Draft Proposed Recommendation. It was also made clear that the proposalis not limited to V.32bis technology. The decision to use V.32bis and no trellis coding was made for reasons ofsimplicity.

D.66 (G. Bremer, AT&T) is the first of three documents which present test results for V.asvd. D.66 presents resultsof live tests using an audiographic conference with V.asvd (as defined in DT/9). In this test, standard bridges wereused for the voice path, some users were voice only, and the parties were widely separated geographically. The durationof the conferences were ~ 40 minutes. The results indicate no perceptible degradation of the voice path due to the useof V.asvd. Mean Opinion Score tests were not conducted.

D.64 (G. Bremer, AT&T) measures the audio path in the presence of impairments. Results are provided for theASVD and Telephony modes. The results indicate that in most cases ASVD has little detrimental effect and in somecases improves some aspects of the connection.

D.65 (G. Bremer, AT&T) was augmented by the playing of audio recordings of the actual tests. The tests are brokendown into three parts: the first two parts use human voices with and without severe interference conditions, the lastuses music in a non-errored condition. (To the ear of this writer, the ASVD was in most cases clearer, with lessbackground noise.) The tests with 32 kbit ADPCM and high noise showed some interference specifically with thefemale voice (however in the case of the high SNR, the background noise was reduced).

Silence detection (not defined in the Recommendation) was disabled during these tests. The higher symbol rate wasalways used.

D.69 (R. Brandt, AT&T, USA) outlines the urgent need of SVD capability by the deaf community and encouragesrapid approval of a low complexity solution.

D.71 (G. Griffith, Rockwell, USA) raises concerns about the confusion to the market and concludes that ASVD offersno long term benefits over DSVD.

It was mentioned that in H.32P, video is also an option, so there are four possible Recommendations for voice/databeing developed.

D.72 (S. Olafsson, Rockwell, USA) proposes that V.34 instead of V.32bis be used as the basis for V.asvd.

D.73 (C. Gusler, Motorola, USA) proposes that a single symbol rate be used in V.asvd.

DT/14 is an IPR statement from AT&T relating to V.8bis and V.asvd.

D.79 (I. Sebestyen, Siemens, FRG) is concerned about a possible overlap between the work in SG 15 on H.32P andthe DSVD work in SG 14. It recommends that the work maintain the highest possible level on commonality. Itplaces a high level of urgency on the completion of work on V.8bis. Lastly it recommends that SG 14 become in-volved with the JCG (Joint Coordination Group) on Audio Visual and Multimedia Services (AVMMS).

MULTIPLEXING/CODING

TD-36 , the report of the November meeting, was briefly reviewed by the associate Rapporteur, W. Pechey (Hayes,UK).

After some discussion about the status of work on multiplexing in SG 15, it was decided to convene a small ad hocgroup. The associate Rapporteur reported that they had gained a more complete understanding of the two proposals(H.32P based and LAPM based).

DT/41 (T. Geary, Rockwell) is a liaison from SG 15 supporting V.dsvd as a subset of the SG 15 work. This waspreviously considered at the November Rapporteurs meeting.



DT/42 is a liaison from SG 8 Question 10 (B. DeGrasse, Rapporteur) describing the audio and modem requirementsof a audiographic conference. This was previously considered at the November Rapporteurs meeting.

J. Magill related that SG 14 had started out attempting to be closely aligned with the work of SG 15; however, as thework progressed, the requirements of the work in the two SGs seemed to diverge.

SPEECH CODERS

DT/22 (J. Magill, Rapporteur Q1/14) is a useful summary of speech coders which might be available for use by SG14 for the DSVD application. See Table 1, below.

The discussion that followed ranged from the need for DSVD to SG 14 picking their own speech coder. For the mostpart, the discussion was circular. Finally, the Rapporteur set a goal of the group to define the requirements for aspeech coder and for the SAVD work itself. In further discussion, it became clear that SG 14 could probably onlychoose between the GSM coder and the SG 15 coder. It was suggested that SG 14 could adopt the GSM coder withoutSG 15’s approval, but that there may be problems in balloting.

An ad hoc group on coders met and decided that the SG 15 coder may have been too bit-rate constrained and thereforemay be more complex and may have more delay than necessary. A liaison to SG 15 will be drafted which willdelineate the requirements.

Identification Technique Res 1 bit rate (kbit/s) delay(ms)G.728 low delay CELP approved 16 2G.728 low delay CELP 1996 9.6/12.8 2G.8kbit/s ? 1996 8 ?G.4kbit/s ? 1997 4 <20GSM RPE-LTP ETSI std. 13 20modified GSM(IBM)

vector quantized RPE-LTP

N/A 9.4 20

TrueSpeech 8.5(DSP Group)

Multipulse LPC N/A 8.53 100

Table 1. Speech Coder Summary

V.8 / V.8BIS

DT/57 reports on the output of two ad hoc groups, one working on the two competing drafts of Rec. V.8bis, and theother addressing changes to V.8. L. Brown (Motorola) reported on the V.8bis activities. Working from theRapporteur Group papers SAVD-94-073 (AT&T) and SAVD-94-074 (Radish), agreements were reached to use theSAVD-94-074 escape signal and HDLC framing, the SAVD-94-073 MR (Mode Request) and CR (CapabilitiesRequest) dual tones and X.208 non-standard capabilities structure. Support for ADSI was left for further study.Although details need to be worked out, the only point of disagreement that remains is the method of error recovery(return to voice versus recovery). G. Griffith (Rockwell, USA) reported on the V.8 group’s deliberations. The goal ofthis group was to define a way in which V.8 could be used to support SAVD without modification. CI (Call Indicateor calling tone) is used as the escape signal to move from the voice mode to the SAVD mode. A call function forDSVD was added.

At this point, several participants debated the merits of the two approaches. The point of error recovery from collisionwas raised; both groups indicated that they were addressing the issue.

DT/61 is the report of the Orlando Q1/14 Rapporteur meeting December 9 - 11, 1994. It includes the revisedCapabilities Exchange and Selection Protocol Objectives. (See the report in this issue of CSR, page 37.)

DT/58 is a proposed Draft Recommendation V.8bis, that is the output of the V.8bis ad hoc group. K. Ko (AT&T)gave a detailed presentation of the provisions of this proposed Recommendation, highlighting the scope and scenariossupported.

GENERAL DISCUSSION ON V.8BIS

There was a question of how long the V.8bis procedure could take, in reference to meeting the 2 second guideline. Itwas clarified that all standardized procedures would be accomplished in the 2 second time frame. In response to a ques-



tion about the possibility of reducing the amount of time necessary to connect when a common mode existes, it wasreported that the goal was to not extend the time significantly.

The issue of negotiating after train-up was also brought up. The total time would not be extended if one takes intoaccount answering on the first ring. Many other schemes (e.g., faxtel) rely on multiple rings. It was suggested thatthe exchange of the manufacturer’s specific functionality would require 35 additional octets (under 1 second). Therewas a proposal to split off the capabilities exchange from the negotiation. J. Magill reminded the group of the originalobjectives which he felt were met by DT/58 . A prolonged discussion followed in which the proponents of the twosides of the issue (V.8 modification versus V.8bis) were unsuccessful in their attempts to move the other parties.

At this point the associate Rapporteur asked the ad hoc group on V.8 to briefly discuss their report in DT/57 . TheV.8 extensions do not address the objectives stated to support voice initiated calling.

At the last meeting of the group, support for V.8bis included: AT&T, GDC, Penril, DBP-Telekom, Cray, Microsoft,and Telia (Sweden). Opposition was expressed by Rockwell, US Robotics, and France Telecom. Rockwell tried toblock the move to Resolution 1. However, it was agreed to announce for Resolution 1.

LIAISONS

The response to DT/2 (SG 8 liaison on V.8 modes which notes the use of V.29 for T.104) will be developed off-line.

It was decided to send a copy of DT/58 (draft V.8bis) to SG 15 and SG 8.

DT/20 is a request from SG 8 to shorten the ANSam (currently 4-6 sec.) to the same length as CED (2.6-4.0 sec.) inT.30. It was decided to defer a response until the next meeting.

Q1/14 RAPPORTEUR’S FINAL MEETING

MULTIPLEXER

No decisions were taken in the Multiplexing meeting .

CODER

DT/74 (K. Murti, AT&T, USA) contains the summary of the discussions in the speech coder ad hoc group. Thegroup decided that two coders are required by the applications considered. Their proposal is that both a low complexity(10 MIPS fixed point in a 16 bit DSP) and high complexity coder be specified; the low complexity would be thedefault; the high complexity would be optional. A response from SG 15 is expected by 4Q95 or at the latest 1Q96.

A question was raised relative to the use of V.32bis for DSVD with silence detection. It was suggested that the speechactivity could not be used to accomplish this.

DT/75 is a proposed liaison to SG 15 requesting assistance with the selection of the coder. This liaison was modifiedto reflect the discussions above, stating that there was a desire to use V.32bis for this application. R. Cox, theRapporteur, had indicated that the projected dates were reasonable.

AVD

Further work is required.

ASVD

The Rapporteur pointed out the V.asvd draft (DT/9) had been available for some time and that it appeared to meet therequirements of the deaf community, and those of SG 8. He noted that DSVD will not be available until 1996. TheRapporteur suggested that the ASVD proposal be considered for Resolution 1. Support was expressed by GDC, Telia,PictureTel, Microsoft, Siemens, Racal, AT&T, and Penril. BT, Rockwell, and US Robotics expressed opposition tothis on the basis that this will result in two Recommendations. During discussion, C. Firth (Racal Datacomm, UK),the Rapporteur on Wireless DCEs, mentioned that ASVD appeared to offer a benefit in terms of security for analogcellular even if it weren’t used with data. It was decided to announce this document for Resolution 1 at the WorkingParty meeting. Although Motorola did not vote NO, they expressed strong reservations about the process.

SAVD OVERVIEW

It was decided that an interim Rapporteurs Group meeting would be held during the spring.



LIAISONS

DT/80 is a proposed liaison to the JCG on Audiovisual and Multimedia.

DT/81 is a proposed liaison to Q2/15 which explains the differences in the application for SAVD and theVideotelephony work. It was accepted with minor editorial changes.

DT/82 is an update to a previous liaison to SG 8 to reflect the status of the work on DSVD.

Q2/14 DTE-DCE PROTOCOLS

DT/30 is the report of the Rapporteurs meeting in Vienna in September.

DT/6 (ISO/IEC JTC1/SC6) is a liaison (from technical report TR 10171) to SG 7, 8, 11, 14 and 15 and the IETF. Itlists the various HDLC data link layer protocols and the applications of HDLC Classes of Procedures implemented inITU Recommendations and the Internet. The liaison requests that each standards body update SC6 with any newprotocol information.

DT/7 (ISO), a liaison to SG 7, 11, 13, 14, provides information on the present status and the work in progress onHDLC. It includes texts for ISO/IEC 4335 DAM (Draft Amendment) 6, ISO/IEC 7809 DAM 10, ISO/IEC 8885DAM 9, all covering extension of HDLC sequence number modulus beyond 128 and ISO/IEC 4335 DAM 7 enhancedmulti-selective reject option.

DT/8 , a liaison from ISO/IEC JTC1/SC6/WG3, was presented by R. Damm DBT. Points of interest include:• In a joint session with WG1, they agreed that the incorporation of a synchronous protocol in the DTE would be

desirable; a new work proposal was drafted.• ISO/IEC 13575 (used by V.hssi/ V.12), 50 pole interface connector mateability dimensions and contact number

assignments, has been approved (copy attached to DT/8).• WG 3 is proceeding with revisions to ISO 2110 (25 pin connector) to support the V.34 requirements for use of

V.10 or a mixture of V.10 and V.11.• Technical report ISO/TR 7477 Data Communications - Arrangements for DTE to DTE physical connection using

V.24 circuits, is soon to be published.

DT/49 (W. Pechey, Rapporteur) provides a list of editorial errors in the 1993 version of Recommendation V.42discovered by the editor (F. Burg, AT&T).

DT/45 (W. Pechey, Rapporteur) contains a proposal from F. Burg for V.gmux. These extensions to V.42 provide forthe multiplexing of different types of data streams. This work is also being considered under Q1/14 in the SAVDwork. It was decided to annex this document to the Q2/14 meeting report.

DT/31 (W. Pechey, Rapporteur) is the living list for V.42ter (synchronous data compression). It includes agreementsalready made and where work is still needed.

DT/32 is a skeleton draft of Recommendation V.42ter.

There was a brief discussion of flow control although this work has been moved to Q6/14.

D.76 (D. Daulasim, TRT, France) provides suggested text for some open sections in the Draft Recommendation.

The Rapporteur used D.76 to gain additional agreements. Agreements were reached on the text supplied for sections6.2.1, The Determination of Frame Boundaries; 6.2.2, the encoding of the FCS in the payload; and 6.2.3, the recon-struction of the DTE frame.

M. R. Wade (DBP-Telekom, Germany) provided a short tutorial on the Tecomac 2-stage data compression techniquefirst introduced in the September Rapporteur’s meeting. D.80 , the paper, which was not presented, reports on how acustomer’s problem was solved using the two-stage technique. Tecomac promised to bring a detailed proposal,including their algorithm descriptions, to a future meeting. Anti-expansion mechanisms are active in both dictionaries.It was clear that the group needs to find appropriate files to compare candidate proposals. Tecomac also agreed toprovide some candidate test files (live data captures).

DT/48 (M. Herrera, Royal PTT, Netherlands) proposes consideration of an adaptive compression technique in Layer 3.This is based on an implementation on an X.25 switch. The document presents the perceived benefits of the use ofLayer 3 over Layer 2 (e.g., reduction in the number of packets sent and easier network management). More



information on the details of implementation was promised for a future meeting. It was reported that the Royal PTTholds IPR on this technique. Each logical channel has its own dictionary. Headers are not compressed.

Q5/14 ISDN TERMINAL ADAPTERS

DT/25 is a revision of Draft Rec. V.130, ISDN Terminal Adapter Framework (formerly V.taf).

Q6/14 DTE-DCE INTERFACES

DT/37 is the report of the Q6/14 Vienna Rapporteur’s meeting in September. Points of interest include:• Approval of redefinition of circuit 102 (signal ground) and deletion of circuits 102a and 102b in V.24. This will

require changes in V.10 figures.• Create a guidelines document (joint ISO/IEC/ITU Technical Report if possible) on flow control across synchronous

and asynchronous interfaces.

DT/38 , the latest version of Draft Recommendation V.12 (V.hssi with maximum signaling rate of 52 Mbit/s), wasagreed.

R. Damm, Rapporteur, distributed a working paper (Working paper V.10) in which he outlined the proposedchanges necessary to V.10 that he has identified. He proposed that this be discussed further by appropriate nationalstandards bodies.

D.77 (K. Daulasim, TRT, France) proposes the addition of two new circuit definitions (CT114bis and CT115bis) toV.24 to accommodate synchronous variable signal rate timing.

R. Damm reviewed DT/35 , a proposed liaison to ISO/IEC JTC1/SC6 WG3. The group accepted this direction whichsupports the requests of WG3. DT-35-rev was created which also notes the addition of two new opcodes intoV.25bis for the encapsulation of V.25ter messages.

Q7/14 V.25TER

DT/21 is the summary of the Q1/14 V.savd work. L. Brown, the Q7 Rapporteur, brought the group’s attention tothe fact that the V.savd group sees the need for AT commands to control the SAVD process.

DT/52 is a proposed liaison to SG 8 asking SG 8 to support extended commands from V.25ter and some otherchanges.

DT/53 includes two documents from the November V.savd Rapporteur’s meeting, SAVD-94-054 and SAVD-94-055 , regarding DSVD interface functionality. Both are from J. Decuir (Microsoft).

No companies indicated that they hold IPR on V.25ter.

DT/51 is the report of the Vienna Rapporteurs meeting.

DT/19 is a draft of V.25ter. The editor, J. Decuir (Microsoft, USA) reviewed this version, noting each of thechanges. He gave the rationale for each.

A question was raised about the inability of V.32bis automode modems to disable a modulation mode (Table13/V.25ter). It was recognized that the automode would override this setting if it created a gap. The +MA parameterwas modified to prevent “notching out” carrier modes in the middle of the normal sequence. The group accepted thedraft subject to revision at this meeting.

DT/58 (J. Decuir, Microsoft, USA) is a proposal to add country of installation codes. There is provision for multiplecountry codes for mobile modems. This proposal was accepted.

DT/40 is a proposal for the establishment of a registration body for the + commands. It proposes that ITU-T SG 14be this body. It also proposes that the assignments to date be listed in an appendix. These proposals were accepted.Organizations outside of the ITU and ISO will be referenced by a supplement. K. Kern (Chair SG 14) will pose theassignment of this registration authority to SG 14 to the TSAG meeting in January.

D.70 (R. Brandt, AT&T, USA) proposes the addition of commands to control the probing sequences specified inRecommendation V.18. R. Brandt stated that the need for another command to control the order of probes in the V.18answer mode was recently brought to his attention. The group approved the proposals contained in D.70 ; it wasagreed to work offline on the specific way to accommodate the second point for final approval at the WP meeting.



DT/53 , presented by J. Decuir (Microsoft, USA), raises the issues related to SAVD when the voice coding andmultiplexing are accomplished in the DTE. It was suggested that SG 14 should form a liaison with the SG 15 ad hoccommittee working on DTE-DCE interface issues. It was also suggested that if this work were undertaken, the issueof partitioning the work within SG 14 (Q1, 6. and 7/14) would need to be addressed.

The Rapporteur briefly reviewed DT/52 , the proposed liaison to SG 15 concerning changes in V.25ter. The groupagreed to this liaison and asked that it also be sent to SG 8. The liaison will be combined with that of Question 1/14.A portion of this document will also be included in the general liaison to ISO/IEC JTC1/SC6/WG3.

Q10 V.56 NETWORK TRANSMISSION MODEL FOR EVALUATING PERFORMANCE OVER 2-WIREVOICE GRADE CONNECTIONS

DT/26 is the draft Recommendation V.56 bis. L. Brown (Motorola, USA) briefly reviewed the paper, highlightingthe following changes:

• Changes to Table 1A to include A-law companding, ETSI defined lines and 60 Hz phase jitter frequency to 50 Hz(international requirements).

• Addition of V.56bis Table 1B (with international requirements noted above); delete TSB-37A Annex D.• Changes to Figure 2, Table 2 and Annex A to include international requirements.

The Rapporteur (G. List, Austria) briefly reviewed the major editorial changes to DT/26 . There was a concern thatmodems that work well on the simulator might not perform well on circuits conforming to ITU-T Recommendation(e.g. M.1040). It was generally agreed that the concept of this Recommendation was not to provide guarantees ofperformance.

DT/33 is the report of the November Q10/14 meeting.

DT/39 (G. List, Austria) summarizes the differences between TIA TSB-37A and Draft Recommendation V.56bis. Itwas not presented.

WORKING PARTY PLENARY

The plenary meeting approved V.8 bis, V.12, V.25ter, and V.56bis for Resolution 1. It rejected V.asvd and V.mux.

During the discussions on Multiplexing, W. Pechey proposed that the SG 14 HDLC multiplexer go forward forResolution 1. The rationale was that SG 15 would go forward in any case on their own scheme. SG 14, at their nextmeeting, could then decide whether to reference the SG 15 mux or apply Resolution 1. Opposition was expressed byRockwell, BT and Motorola; as the decisions on the voice coder had already delayed the work on DSVD until 1996, itwas decided not to push for Resolution 1 at this time. During the debates, the delegates from BT and PictureTel readlong, prepared scripts as part of their opposition to the multiplexing work. The PictureTel representative challengedSG 14’s right to develop Recommendations for Multiplexers when voice was involved, stating that this was whollythe province of SG 15 (see the Commentary below).

The Rapporteur proposed Resolution 1 treatment for ASVD based on:

• The text has been stable since November;• Test results indicate good performance;• It appears to meet all of the requirements of SG 8 (low delay);• It appears to meet all of the requirements of the deaf community which has an urgent need for a low cost solution.

Opposition was expressed by Rockwell, US Robotics, BT, TRT, and Motorola. Motorola claimed that there had notbeen adequate time to assess the document and therefore it couldn’t be considered stable. Rockwell stated that the con-tributions to this work had not been given adequate consideration. Rockwell and US Robotics proposed delaying thework by starting it over and basing it on V.34. After it was decided to delay the ASVD Recommendation until 1996(at a minimum), the Working Party Chairman expressed his disappointment in this decision, stating that the real losersare the deaf community who must now turn to a proprietary solution to solve their problem




COMMENTARY BY DICK BRANDT

Readers of CSR know that this writer does not normally editorialize but in this case I feel something must be said. Inmy many years of experience, I have never before witnessed a group of members from one SG coming to another SGwith the sole purpose of delaying or derailing its work. This was clearly the case with at least two of therepresentatives of SG 15 who attended this meeting of Working Party 1 of SG 14. They made no secret of theirintentions, stating many times that this was their work and that SG 14 should stop their efforts. They were successfulin delaying the DSVD work until 1996. Normally any concern over overlap of responsibilities is handled by theChairs of the SGs involved. The concern I have is that this sort of behavior can lead to retaliation (e.g., an unofficialgroup of people from SG 14 could show up at the next SG 15 and try to cause similar havoc). I sincerely hope thatthis does not happen as I believe harm could be done to a process which is already fighting against the quick-fixconsortiums which seem to be springing up each day.

SG 14 WP 1 ROSTER, DECEMBER 12 – 16, 1994, ORLANDO, FL

Klaus Kern, Deutsche Bundespost Telekom, Germany SG 14 ChairDick Brandt, AT&T SG 14 Working Party 1 Chair

Ameritech Services M. Winseck Microsoft C.GarthwaiteAMP J. Bradbery Motorola Les BrownAT&T Bill Betts Motorola Jack DouglasAT&T Dick Brandt Motorola V. EyubogluAT&T Mike Buckley Motorola Chip GuslerAT&T Fred Burg NEC (Japan) Y. ActaniAT&T Ken Ko Nokia (Finland) L. RantanenAT&T Krishna Murti NTT(Japan) H. KimachiAT&T Larry Smith NTT(Japan) K. MurataAT&T R.K. Smith OKI (Japan) T. ChigamaAustria Gerhardt List Penril Datability Dick Stuart,Bellcore Wes Henry Philips (Netherlands) S. LozachBritish Telecom plc B. Welsh PictureTel Dave LindberghCray Comm.LTD- (UK) J. Magill Rockwell S. DebbaschDBP-Telekom (FRG) Ralf-Rainer Damm Rockwell Tom GearyDBP-Telekom (FRG) Klaus Kern Rockwell Glen GriffithFrance Telecom J-P, Dick, Rockwell Sverrir OlafssonFrance Telecom G. Sebek Royal PTT (Netherlands) M. HerreraFujitsu (Japan) H. Murata Siemens (Germany) I. SebestyenGDC Fred Lucas Telefonica de Espana (Spain) A. Martin de la CruzGDC Yuri Goldstein Telefonica de Espana (Spain) J. OrtizHayes (UK) W. Pechey Telia (Sweden) Gunnar HellstromIBM R. Nobakht TRT (France) K. DaulasimIBM A. Sadin US Robotics Andy NorrellIntel King Cheng, US Robotics Dale WalshIsrael Y. Beery



ACRONYM DEFINITIONS

ADPCM Adaptive Differential PCMADSI Analog Display Services Interface (Bellcore)AHAG Ad Hoc Authentication Group (TR-45)APCO Assoc. Public Safety Communications OfficersAPI Application Programming InterfaceASVD Analog SVDATM Asynchronous Transfer ModeAV AudioVisualAVD Alternating Voice DataBAS Bit rate Allocation SignalBRI Basic Rate InterfaceBS Base StationCAPI Common APICDMA Code Division Multiple AccessCED Called Station Identification (T.30)CM Call MenuCMC Common Messaging CallCPAP Customer Premises Access ProfileCPE Customer Premise EquipmentDCE Data Circuit Terminating EquipmentDCME Digital Circuit Multiplication EquipmentDCS Digital Command Signal (T.30)DDR Document Discrepancy ReportDECT Digital European Cordless TelephoneDIS Digital Identification SignalDLC Dynamic Load ControlDSVD Digital SVDDTC Digital Transmit CommandDTE Data Terminal EquipmentDTMF Dual Tone Multi FrequencyECM Error Correction ModeESN Electronic Serial NumberETSI European Telecom. Standards InstituteEVRC Enhanced Variable Rate CodecFCC Federal Communications Commission (U.S.)FPLMTS Future Public Land Mobile Telephone SystemsFT Fixed radio TerminalGAP Generic Access ProfileGSM Groupe Speciale MobileH-MLP High Speed Multi Layer ProtocolHDLC High Level Data Link ControlHLR Home Location RegisterIMSI International Mobile Station IdentityIPR Intellectual Property RightsIS Interim StandardISDN Integrated Services Digital NetworkISO International Standards OrganizationIWF Inter-Working FunctionJCG Joint Coordination GroupJEM Joint Experts MeetingJTC Joint Technical CommitteeLAPD Link Access Protocol D (ISDN-D Channel)LAPM Link Access Protocol Modem (V.42)

LCAP Large Cell Access Profile

LDCELP Low Delay CELPMAC Medium Access (layer)MAPI Messaging APIMBE Multi-Byte ExtensionMC Message CenterMCF T.30 Message ConfirmationMCU Multipoint Control UnitMIN Mobile Identification NumberMLP MultiLayer ProtocolMMAP Mobility Management Application Protocol (T1S1)MOU Memorandum of UnderstandingMS Mobile StationMSC Mobile Switching CenterNAMPS Narrowband AMPS



NANP North American Numbering PlanNASNA National Association of State 9-1-1 AdministratorsNCTE Network Ciruit Terminating EquipmentNENA National Emergency Number AssociationNSC Non Standard Facilities CommandNSF Non Standard FacilitiesNSS Non Standard SetupOCDMA Orthogonal CDMAODA Open Document ArchitectureOGM Out-Going MessageOTA Over-the-Air ActivationP&A Privacy and AuthenticationPAC-U Personal Access Communications System, Unlicensed BandPACS Personal Access Communications System, Licensed BandPBX Private Branch ExchangePC Personal ComputerPCI Personal Communications InterfacePCI Programmable Communications InterfacePCIA Personal Communications Industry AssociationPCME Packet Circuit Multiplication EquipmentPCN Personal Communications NetworkPCS Personal Communication ServicesPCSC Personal Communications Switching CenterPIN Personal Identification NumberPS PCSC ISDN SwitchPT Portable radio TerminalPWD Password (T.30)QSIG Requirements specified by the ITU Q series recommendationsRF Radio FrequencyRFP Request for ProposalRLR Receive Loudness RatingROLR Receive Objective Loudness RatingRS Radio SystemRSSI Received Signal Strength IndicationSAVD Simultaneous or Alternating Voice DataSBE Single Byte ExtensionSCSA Signal Computing System ArchitectureSEP Selective Polling (T.30)SG Study Group (ITU, CCITT)SLR Send loudness ratingSMD Short Message DeliverySMS Short Message Service

SMSA Standard Metropolitan Statistical Area

SNR Signal to Noise RatioSPINI Subscriber Personal Identification Number InterceptSSN SubSystem NumberSUB Subaddress (T.30)SVD Simultaneous Voice DataTAG Technical Advisory GroupTD Temporary Document (ITU, CCITT)TDD Task Data Descriptions (T.611 E-Mail)TDMA Time Division Multiple AccessTMSI Temporary Mobile Station IdentityTOLR Transmit Objective Loudness RatingTSAG Telecommunication Standardization Advisory Group (ITU)TSB Telecommunication Systems Bulletin (TIA)V&V Validate and verifyVIM Vendor Independent MessagingVLR Visited Location RegisterWCPE Wireless CPEWP Working Party (ITU)WUPE Wireless User Premises Equipment (TR-41.6)



1995 MEETING SCHEDULES AS OF DECEMBER 19, 1994Subject to Change without Notice

TR-46 Jan 9 - 11 Boca Raton, FL TR-46 Jun 26 - 30 Vancouver, BCSG15 LBC Jan 9 - 12 Netherlands TR-30 Jul 10 - 14 Baltimore, MDT1A1 Jan 9 - 13 Altamonte Spngs, FL TR-45.2 Jul 10 - 14 Montreal, QueTR-45.2 Jan 16 - 20 San Diego, CA T1P1 Jul 31 - Aug 4 ---TR-45.4 Jan 23 - 27 Orlando, FL TR-29 Jul 31 - Aug 3 Quebec City, CanadaT1P1 Jan 30-Feb 3 Orlando, FL TR-46 Jul 31 - Aug 4 Calgary, Alb.TR-41.6 Jan 30 - Feb 3 New Orleans, LA T1A1 Aug 7 - 11 Boston, MATR-29 Feb 6 - 9 Newport Beach, CA TR-45.4 Aug 7 - 11 Beaver Creek , COTR-30 Feb 6 - 9 Ft. Lauderdale, FL TR-45.2 Aug 14 - 18 Toronto, OntTR-45 Feb 6 Atlanta, GA TR-41.6 Aug 15 - 17 ---SG 15 Feb 6 - 17 Geneva T1E1 Aug 21 - 25 ---TR-46 Feb 13 - 17 Houston, TX TR-46 Aug 28 - Sep 2 Monterey, CAT1S1 Feb 20 - 24 Dallas, TX TR-45 Sep 4 Denver, COTR-45.2 Feb 20 - 24 Phoenix, AZ TR-30 Sep 11 - 15 Portland, ORT1E1 Feb 27-Mar 3 Richardson, TX TR-41 Sep 11 - 15 Edmonton, ABTR-45.4 Feb 27-Mar 3 San Antonio, TX T1S1 Sep 18 - 22 New Jersey areaTR-41 Mar 6 - 10 San Francisco, CA TR-45.2 Sep 18 - 22 San Antonio, TXTR-46 Mar 13 - 17 Atlanta, GA TR-45.4 Sep 18 - 22 St. Louis, MOSG 8 Mar 14 - 23 Geneva TR-46 Oct 2 - 6 Orlando, FLSG 15 LBC Mar 27 - 29 Switzerland TR-45.2 Oct 16 - 20 Tampa, FLTR-30 Mar 27 - 31 Norcross, GA TR-29 Oct 23 - 26 San Diego, CATR-45.2 Mar 27 - 31 Philadelphia, PA TR-45.4 Oct 23 - 27 ---TR-45.2 Apr 3 - 7 Balitmore (tentative) SG 15 Nov 13 - 24 GenevaTR-45.4 Apr 10 - 14 Charlotte, NC T1P1 Nov 6 - 10 ---T1P1 Apr 17 - 21 --- T1E1 Nov 13 - 17 Orlando, FLTR-46 Apr 17 - 21 Kansas City, MO TR-30 Nov 13 - 17 Orlando, FLSG 14 Apr 19 - 27 Geneva TR-45.2 Nov 13 - 17 Colorado Springs, COTR-45 May 1 Chicago, IL TR-45.5 Nov 13 - 17 Colorado Springs, COT1A1 May 1 - 5 Boulder, CO TR-46 Nov 13 - 17 San Antonio, TXTR-29 May 8 - 11 Lexington, KY TR-45 Nov 27 Dallas, TXTR-41.6 May 8 - 12 Long Brach, NJ T1S1 Dec 4 - 8 ---TR-45.2 May 8 - 12 Hilton Head, GA TR-41 Dec 4 - 8 Fort Meyers, FLTR-45.5 May 8 - 12 Hilton Head, GA TR-45.4 Dec 4 - 8 Phoenix, AZTR-30 May 15 - 19 Toronto, Ont T1A1 Dec 11 - 15 San Jose, CATR-45.4 May 15 - 19 Albuquerque, NM TR-45.2 Dec 11 - 15 Atlanta, GATR-46 May 22 - 26 Boston, MAT1E1 Jun 5 - 9 New Jersey areaTR-45.2 Jun 5 - 9 Calgary, ABTR-45.4 Jun 5 - 9 Lake Tahoe, NVT1S1 Jun 12 - 16 Washington, DC areaTR-41 Jun 12 - 16 Kansas City, KSTR-45.4 Jun 19 - 23 Durango, CO

Communications Standards Review (ISSN 1064-3907) is published about 11 times per year, within days afterthe latest, related standards meetings. Editor: Elaine J. Baskin, Ph.D. Technical Editor: Ken Krechmer. Copyright© 1994, Communications Standards Review. All rights reserved. Copying of individual articles for distributionwithin an organization is permitted. Subscriptions: $795.00 per year worldwide. Corporate subscriptions areavailable. Submit articles for consideration to: Communications Standards Review, 757 Greer Road, Palo Alto, CA94303-3024 U.S.A. Tel: +1-415-856-9018. Fax: +1-415-856-6591. e-mail: [email protected]. 15911


COMMUNICATIONS STANDARDS REVIEW · COMMUNICATIONS STANDARDS REVIEW Volume 5, Number 11 December...

Documents

Transcript of COMMUNICATIONS STANDARDS REVIEW · COMMUNICATIONS STANDARDS REVIEW Volume 5, Number 11 December...