communications standards review - Linda Hall Library

COMMUNICATIONS STANDARDS

REVIEW

Volume 5, Number 2 February/March 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.

Telecom. Trilateral Meeting Between Canada, Mexico, and the U.S.,Dec. 9-11, 1993, Washington, DC..............3Telecommunications Trilateral Meeting Roster, December 7 – 9, 1994, Washington, DC..........................4

TR-41 User Premises Telecom Requirements, November 29 – December 3, 1993, Monterey, CA........................5TR-41.1 Multiline Telecommunication Systems.............................................................................5TR-41.1.1 MultiLine Telecommunication Systems – Transmission......................................................7TR-41.1.9, MultiLine Telecommunication Systems Support of Enhanced 911 Service...............................7TR-41.3 Telephones and Acoustic Terminals..................................................................................8TR-41.4, NCTE...... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9TR-41.7 Safety and Environmental Considerations..........................................................................11TR-41.7.1 North American Telecommunication Equipment Safety.......................................................12TR-41.7.3 Electromagnetic Compatibility Considerations................................................................12TR-41.9 Regulatory Considerations............................................................................................13Partial Roster of TR-41, November 30 – December 3, 1993, Monterey, CA............................................16

TR-45.4 PCS/Microsystems Standards, January 10 – 13, 1994, San Diego, CA.............................................17TR-45.4 Plenary..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17Working Group I, PCS Service Standards......................................................................................17Working Group II, MSC-BS A-Interface.......................................................................................17Working Group III, PCS/Microsystem..........................................................................................18TR-45.4 Roster, January 10 – 13, 1994, San Diego, CA...................................................................18

TR-45.3, TDMA Cellular, January 17 – 21, 1994, Banff, Alberta, Canada....................................................19TR-45.0.A, Ad Hoc Authentication Group.....................................................................................19TR-45.3, TDMA Cellular Subcommittee........................................................................................19TR-45.3.2, WG2, Data Services.................................................................................................20TR-45.3.3, WG3, Digital Standards............................................................................................21TR-45.3.3.1, Task Group 1, Matrix............................................................................................22TR-45.3.3.5, Task Group 5, MS/BS Requirements..........................................................................22TR-45.3.5, WG5, Speech Codecs...............................................................................................22TR-45.3.6, WG6, Enhanced Dual-Mode Standards...........................................................................22TR-45.3 Plenary Roster, January 17 – 21, 1994, Banff, Alberta, Canada...............................................23

TR-46 Mobile and Personal Communications 1800 MHz Standards, January 17 – 21, 1994, Phoenix, AZ............24TR-46 Mobile and Personal Communications 1800 MHz Committee....................................................24TR-46.1 Services...... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24Working Group I, Service Descriptions and System Requirements........................................................24Working Group II, Network Reference Models................................................................................25TR-46.2, InterSystem Operation.................................................................................................25WG I (Network Signaling).........................................................................................................26WG II, PCN-to-PCN Intersystem Operation....................................................................................26WG III, PCS to Non-PCS Networks..............................................................................................26TR-46 Roster, January 17 – 21, 1994, Phoenix, AZ.........................................................................27

TR-29 Facsimile Systems and Equipment, January 31 – February 4, 1994, Costa Mesa, CA..............................28

February/March 1994 Vol. 5.2 Copyright © CSR 1994 1

COMMUNICATIONS STANDARDS REVIEW

TR-29.1, Binary File Transfer....................................................................................................30TR-29.2 Facsimile Digital Interfaces...........................................................................................31TR-29.3 Audiographics Conferencing..........................................................................................35TR-29.4 Secure Facsimile.........................................................................................................38TR-29 Roster, January 31 – February 4, 1994, Costa Mesa, CA..........................................................40

TR-30.1, Modems, February 9 – 10, 1994, Plantation FL.......................................................................41TR-30.1 Ad Hoc on V.34 Start-Up...............................................................................................41TR-30.1, Modems...... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41TR-30.1 and TR-30.1 ad hoc Meeting Roster, February 9 – 10, 1994, Plantation, FL................................42

ITU-T SG 14 V.34 Rapporteurs Meeting, February 14 – 15, 1994, Plantation, FL..........................................42V.34 Rapporteurs Meeting Roster, February 14 – 15, 1994, Plantation, FL............................................43

Acronym Definitions.....................................................................................................................441994 Meeting Schedules as of February 28..........................................................................................46

2 Vol. 5.2 Copyright © CSR 1994 February/March, 1994


REPORT OF THE TELECOMMUNICATIONS TRILATERAL MEETINGBETWEEN CANADA, MEXICO, AND THE U.S.DECEMBER 7 – 9, 1993, WASHINGTON, DC

BACKGROUND AND INTRODUCTION

Interested parties from the United States, Mexico, and Canada met for the fourth time to discuss topics involvingtelecommunications, trade, and standards-related measures. The meetings were initially organized under the auspicesof the Standards Council of Canada (SCC), the American National Standards Institute (ANSI), and the CamaraNacional de la Industria de Transformacion (CANACINTRA). CANACINTRA could be equated to the equivalent ofa Mexican Chamber of Commerce, but it is not directly involved in Standards. Future standards-related activities ofthe Mexican Delegation would be directly under the auspices of Camara Nacional de la Industria Electronica Y deCommunicaciones Electricas (CANIECE). The objectives of the meetings are to promote and foster thedevelopment of a telecommunications environment that is conducive to:

• Harmonization of telecommunications standards• A forum for consultation and exchange of information, and• Support for the Telecommunications Standards Subcommittee required by Annex 913.5.a2 of the North American

Free Trade Agreement (NAFTA).

Although these meetings have been convened by the private sector, government participation is sought andwelcomed. The signing of NAFTA, and its January 1, 1994 effective date, provides a sense of urgency for theactivities of the group; however, the group is not confined to issues raised by NAFTA.

REPORT OF PREVIOUS MEETING

The previous meeting in Mexico on March 24, 1993, was attended by about 30 people (including three U.S.delegates, and three Canadian delegates). Ing. Sergio Viñals Padilla gave a presentation on the new Mexican law onMetrology and Standards. The new law requires a cost/benefit analysis of existing Telecom standards before mid-October (1993). On the Mexican side there would need to be substantial changes in light of the new Mexican law.Agenda topics for future meetings were discussed, including the need to have a Working Group on ConformityAssessment. Since there will also be a Trilateral Forum addressing Conformity Assessment, ANSI and SCCofficials felt Sectoral work could and should proceed, but in the context of the overall Conformity Assessmentactivity. A Harm-to-the-Network/Electromagnetic Compatibility (EMC) Working Group was formed, with theproviso that the group might split into two groups later. The emphasis for the next meeting would be an exchangeof information to understand the similarities and differences in each country.

A Working Group on Product Safety using IEC-950 as a basis was also agreed to. There was discussion of the needfor a Working Group on Building Wiring and activities based on the work of IEC/ISO JTC1 SC25 WG3.Intellectual Property Rights (IPR) were also agreed to be discussed at the next meeting. The date for the nextmeeting was set for July 12, 1993, but the meeting was subsequently rescheduled to December 1993.

ACTIONS TAKEN

• The Group adopted the terms of reference, and accepted the name Consultative Committee - Telecommunications(CCT).

• CCT agreed to meet in Mexico the week of February 7, 1994, hosted by CANIECE.

• It was also agreed to name chairmen at the CCT level for each country and to pick a lead facilitator. Theselections were:

Alberto Zetina, Mexico, ChairFil Diamente, Canada, Vice ChairChuck Berestecky, USA, Vice Chair

A. Zetina’s term of office is two years; Mexico will supply the Secretariat function during his term.

• It was agreed to form the following Working Groups and have them meet before the next CCT meeting:

1. Product Safety Working Group (PSWG) will base its work on IEC-950. Facilitators:Frank McCaughey, Canada, Lead FacilitatorVictor Perez, Mexico

February/March, 1994 Vol. 5.2 Copyright © CSR 1994 3


Chuck Tenorio, USA

If the same representation is used as was used for the BNTG, then there should be 18 people in the PSWG:six from each country, with two from Telecom, two from IT, and two Other.

2. Conformity Assessment Working Group (CAWG). Facilitators:

Victor Boersma, Canada, Lead FacilitatorArturo Leal, MexicoBill Hurst, USA

3. Harms/EMC Working Group. Facilitators:

Chuck Berestecky, USA, Lead FacilitatorFil Diamente, CanadaSergio Viñals, Mexico

4. Service Provider-focused Working Group (SPWG), which would focus on the Mandatory and Voluntarystandards-related measures in each country, including the measures of NAFTA that impact Service Providers,especially NAFTA Article 1302 . Facilitators:

Jose Tapia, Mexico, Lead FacilitatorArt Reilly, USAVictor Boersma (Temporary), Canada

TELECOMMUNICATIONS TRILATERAL MEETING ROSTER,DECEMBER 7 – 9, 1994, WASHINGTON, DC

CanadaPierre Adornato Northern TelecomDavid Bell EEMACVictor Boersma Northern TelecomFelice (Fil) Diamente Dept of IndustryPeter Ridout CSA

M e x i c oJose Juan Tapia Ortega Telefonos de MexicoRaul Ortega AT&T de MexicoVictor H. Perez Motorola/CANIECEManuel Rosales Instituto Mexicano de ComunicacionesSergio Viñals Instituto Mexicano de ComunicacionesAlberto Zetina Ericsson/CANIECE

USADan Bart TIAChuck Berestecky AT&TDavid L. George Unisys Corp.Bill Hanrahan CBEMAJulius Knapp FCCTricia Paoletta FCC/Int’l Comm.Ron Provost BellcoreBill von Alven FCC



REPORT OF TR-41 USER PREMISES TELECOM REQUIREMENTSNOVEMBER 29 – DECEMBER 3, 1993, MONTEREY, CA

TR-41.1 MULTILINE TELECOMMUNICATION SYSTEMS

T1E1 LIAISON

T1E1.1 work on line-side answer supervision (LSAS) requirements is nearing letter ballot stage. No contentiousissues remain. Line-side supervision is intended to provide answer supervision (i.e., indication of far-end answer oncalls from pay stations and PBX loop or ground-start lines. It is not intended that LSAS be compatible with CAMA(Centralized Automatic Message Accounting) operation.

T1E1.1 work on the CAMA trunk standard has produced tighter requirements on MF sender signal duration andinterdigit interval timing. The proposed requirement for both is 60 +/- 0.5 ms.

The T1E1.2 proposal that CPE present an idle signal on digital carrier facilities when the CPE is disconnected or hasa power failure (to which TR-41.1 objected) resulted in further T1E1.2 discussion with relatively little progress.However, T1E1.2 understands that provision of such a signal from a device external to the CPE – e.g., a “smartjack” or a Customer Service Unit (CSU) – is acceptable.

NIUF PBX COMMITTEE LIAISON

Upon review of the National ISDN User Forum (NIUF) PBX Committee’s concern that PBX/KTS equipment is notbeing adequately considered in the ongoing development of National ISDN (NISDN) definitions and standards,Bellcore committed to consider these concerns in terms of NISDN-3 as well as to ongoing discussions with theNIUF PBX Committee.

A subcommittee of the PBX Committee has been formed to address QSIG and the Bellcore Integrated CustomerAccess Network (I-CAN) proposal. The subcommittee’s purpose is to represent the views of users and of PBXmanufacturers in the I-CAN definition process.

PN-2396, UPDATE/RESTRUCTURE OF TIA-464-A, P RIVATE AUTOMATIC PBX

Work Plan: TR-41.1/93-12-051 (J. Schick, Northern Telecom) is a proposal for expeditiously completing thework of updating and reissuing TIA-464A. The key points of the proposal are as follows:

1. An ad hoc group to meet in February for a clause-by-clause review of current document; for each clause,recommending one of four actions:

• Deletion• Retention• Text update

• Numerical requirements modification (based on solicited contributions).

2. Distribute draft with ad hoc group recommendations at the March 1994 meeting; invite submissions andcomments.

3. Contributions and comments submitted for the June 1994 meeting, leading to second draft to be prepared inadvance of the September meeting.

4. Final review and discussion of all comments and technical submissions at the September 1994 meeting with thegoal to approve the update for letter ballot.

5. At the December 1994 meeting (subject to letter ballot timing), resolution of comments and negative votes.

Document Format: The matter of whether the reissue of TIA-464A as separate parts or volumes (as had beenagreed on earlier) or as one single document was raised. Arguments in favor of separate volumes are:

• With added material, the standard is becoming rather bulky.• The various parts would be ready for reissue at different times (e.g., work on the transmission part is nearly

complete).

Arguments for recombining the parts are:

• The “464” document number, which to many people is synonymous with the PBX standard, will be retained.



• Many requirements, specifically interface requirements, can now reference the standard from related forums (e.g.,T1E1); thus, the amount of text will be reduced.

• With an accelerated completion schedule (see above), there would not be as much time lag between sections of thedocument.

It was agreed that the update/reissue would be recombined into an eventual document which would likely benumbered TIA-464-B. However, so that availability of completed sections, such as the transmission part, would notbe delayed, these could be published as an addendum to the existing TIA-464-A.

Digital Interfaces Section: A revised outline was submitted for the Digital Interfaces portion of the TIA-464-A update (TR-41.1/93-12-054 , J. Needham, Mitel). A major feature of the outline is the proposed newsubsection on ISDN Primary Rate Interface; specifically, the electrical interface in conformance to T1.408. Detailsof the outline for this sub-section will be provided at the next meeting. A point was raised about the need forretaining existing digital interface requirements pertaining to various impairments (impedance matching, longitudinalbalance, jitter and wander).

PN-2396 – Signaling Section: The issue of call progress tone signal levels is addressed in TR-41.1/93-12-053 (R. Carsten and J. Schick, Northern Telecom), wherein it is noted that the current tight tolerances for theselevels appear to be derived from LSSGR (Bellcore’s LATA Switching System Generic Requirements) specificationsfor Central Offices. It is argued that there is generally no need for call progress tone levels at PBX ports to bespecified in an equally narrow range as long as limits are placed on the upper bound of the range to avoid overload ordistortion. The contribution proposes an upper limit of -16 dBm for all call progress tone levels at any interface,with the lower limit yet to be determined. It was also noted that ANSI T1.401 allows quite a wide range for callprogress tone levels appearing at customer interfaces; however, the range at PBX ports should not be as broad so asto prevent allowance for facility transmission loss.

TR-41.1/93-12-052 is the most recent T1E1.2 draft for the proposed T1.403 annex on robbed-bit signaling. Theannex provides the definitions and call state signaling for both the SF (superframe) and ESF (extended superframe)DS1 formats. No specific action was taken on this contribution; the material will either be referenced in or includedin the TIA-46A signaling section update.

PN-2396 – Transmission Section: See the TR-41.1.1 report on p. 5.

PRIVATE NETWORK SYNCHRONIZATION STANDARD

It had been agreed in principle that the TIA synchronization standard (TIA-594) would be rescinded upon the issuingof the ISO/IEC synchronization standard (ISO/IEC 11573, TR-41.1/93-12-049). However, TIA-594 containsguidelines specific to North American network design, specifically in Appendix B. In order that this material not belost, it was proposed (TR-41.1/93-12-055 , M. Green, Northern Telecom) that the material in Appendix B ofTIA-594 be retained as an informative annex of the reissue of TIA-464. This proposal will be acted on at the nextmeeting to allow members to review ISO/IEC 11753 in detail.

In any event, the rescission will not be enacted until ANSI takes action on the ISO standard (action options areendorsement, adoption, or adaptation) so as not to leave a “vacuum” for a North American synchronization standard.

PRIVATE NETWORK SIGNALING (QSIG)

QSIG is a peer-to-peer ISDN signaling interface, based on ITU Q.931; the “Q” refers to the Q-reference point where aVirtual Private Network (VPN) interfaces to the PSTN. The term originated with ECMA, was adopted by ETSI, andis now an ISO standard.

J. Needham (Mitel) gave an overview of VPNs in Europe, based on papers presented at a July 7, 1993 conference(TR-41.1/93-12-050©). The conference resulted from the formation of a group to study VPNs in Europe and torecommend standards and protocols for CPE interfaces. However, PTTs generally opposed this activity, since theywant to retain control over VPN, for example, via Centrex access. The lead paper in the conference defines VPNsand relates the history leading up to the development of VPN offerings by public network carriers. It also highlightsthe fact that PBX-accessed VPNs and Centrex are two separate entities, however competitive.

M. Zonoun, Northern Telecom, gave a slide presentation on QSIG (TR-41.1/93-12-057) and provided copies ofan ISO/IEC document on Telecommunication and Information Exchange between Systems (TR-41.1/93-12-056 ). The presentation explains how QSIG relates to the development of ISDN private networking over public



network facilities, traces the growing acceptance of QSIG as a worldwide standard, and promotes the desirability ofstandard QSIG interfaces for PBXs, which provide multivendor inter-operability.

In the ensuing discussion, it was generally agreed that TR-41.1 should not be formulating QSIG standards since thiswork is being done in several related forums. Rather, TR-41.1 should be a “clearing house” for such standards withrespect to CPE, as well as serve as a “sounding board” for such standards’ impact on CPE. As to whether a newworking group is needed to address QSIG will be decided at the next meeting. Meanwhile, members are to ascertainwithin their companies the interest in QSIG work and, if a working group is formed, interest in leadership andparticipation in such a group.

TR-41.1.1 MULTILINE TELECOMMUNICATION SYSTEMS – TRANSMISSION

PN-2396, UPDATE/RESTRUCTURE OF TIA-464-A, P RIVATE AUTOMATIC PBX – TRANSMISSION PARTDOCUMENT

Draft 0.3 (TR-41.1.1/93-11-022 , J. Schick, editor) represents a substantially complete draft of the PN-2396Transmission Part. Outstanding items include the updating of Annex B (Acoustic Reference Level Plan) to reflectthe access line terminology and the expansion of the index.

Certain sections were subject to significant editorial changes to reflect technical changes and additions agreed to inearlier meetings. For the benefit of reviewers, all sections with significant changes from Draft 0.2 or from texttaken from Section 4.8 of TIA-464A are identified in the cover sheet of the contribution.

The chair stressed the need for each working group member to carefully review the document within his or herorganization for agreement with requirements and for assurance that those requirements which were not specificallyaddressed in the contributions and discussions of the working group as part of this project remain valid.

The proposed completion schedule for the document is:

• March 1994: Completion of remaining items; comments and proposals for technical additions and/or revisions(via contributions).

• June 1994: Approval for letter ballot.• September 1994 (subject to letter ballot timing): resolution of comments and negative votes.

TR-41.1.9, MULTILINE TELECOMMUNICATION SYSTEMS SUPPORT OF ENHANCED 911 SERVICE

TECHNICAL BULLETIN

The Technical Bulletin describing present day MLTS support of Enhanced 911 Service has now been issued by TIAas TSB-103.

CAMA TYPE TRUNK STANDARD

Three T1E1.1 contributions concerning the T1E1.1 formulation of the Enhanced 911 Document were distributed:

TR-41.1.9/93-11-020 proposes a subsection on call states and process at the NI. Specifically, the contributiondenotes the on/off-hook signals applied by both the network and the CI (Customer Interface) during each call stateand the timing requirements for the CI to outpulse the called and calling number to the network.

TR-41.1.9/93-11-021 proposes a subsection on DC signaling specifications; specifically the electricalcharacteristics of CI and network supervisory signals at the NI.

TR-41.1.9/93-11-022 proposes text for the MF Signaling subsection. Specifically, the contribution proposesthe replacement of existing text with text suitable for an interface standard, including frequency and timingcharacteristics, NI signal powers, and outpulsing formats.

FUTURE ENHANCED 911 SERVICE PROVISIONS FOR MLTS USERS

TR-41.1.9/93-11-023 (J. Needham, Mitel) is a proposal for using ISDN calling line identification for Enhanced911 service. A significant point is that PBX extension for non-DID PBXs would be contained in the calling partysubaddress information element; presently, this element is not mandatory in NISDN-1 or NISDN-2. If ISDN callingline identification is to be a viable method, it must be made mandatory for NISDN-3.



A letter was sent by the TR-41.1 chair (TR-41.1.9/93-11-019 , R. Frank), inviting other interested standards,regulatory, and industry forums to submit 911 service concerns, compatibility needs, and suggestions for newcapabilities in order to assist in the formulation of the future TIA Enhanced 911 standard.

John Schick, Northern Telecom

TR-41.3 TELEPHONES AND ACOUSTIC TERMINALS

LIAISON REPORTS

ETSITR-41.3/93-11-30© is a proposed set of requirements from ETSI for the magnetic field strength of a telephonereceiver for hearing aid compatibility. The requirements in ANSI/EIA/TIA 504 are similar but there are enoughdifferences that TR-41.3 formed an ad hoc committee to generate a response back to ETSI before the March TR-41.3meeting.

IEEEActive Projects in the Telephone Instrument Testing Subcommittee were summarized. P-1206, StandardMeasurement Methods for Handsets/Headsets was balloted and has undergone extensive editorial changes. It is beingforwarded to the IEEE Standards Committee without resolving the single negative vote since the comment has nosupport within the Subcommittee. Project P-1329, Standard Measurement Methods for Handsfree Telephone Sets, isplanned for balloting in 1995. Limitations may be placed on the scope, if necessary to meet the requested deadline.Work will begin on P-1027, Measurements for Hearing Aid Magnetic Field, which has been out for trial use forseveral years. Comments on P-1027 are requested. The Subcommittee requested copies of drafts of P-1027 and P-1329.

T1E1In November, TR-41.3 informally presented the liaison from TR-41.3 to T1E1.1 concerning the proposed inclusionof a 5 millisecond response to an OCI (open circuit interval) and 20 mA as the minimum dc current in PN-2892,Revision of EIA-470-A, Telephone Instrument with Loop Signaling for Voiceband Applications. PN-2892 wasapproved at the TR-41 plenary in October. There was no action by T1E1.1 at the meeting except to ask members toconsider the items. The liaison will be formally sent to T1E1.1 before their next meeting in February.

TR-41.3 asked for copies of T1E1.1 contributions on class services, especially ringing and call waiting code timing.

SP-2431A, ADDENDUM TO EIA 470A CRITERIA FOR ISDN TELEPHONE COMPATIBILITY WITHHEARING AIDS

SP-2413-A amended ANSI/EIA/TIA 504-1 to include requirements for the ISDN digital telephone. The ANSIvoting period for SP-2431-1 was over in June 1993. During this meeting the file was reviewed at TIA headquartersand was found to be in order. The soft copy of the SP was located and the necessary documents will be generated andforwarded to ANSI.

PN-2892, REVISION OF EIA-470-A, T ELEPHONE INSTRUMENT WITH LOOP SIGNALING FORVOICEBAND APPLICATIONS

Review of TR-41.3/93-10-26, the third draft of PN-2892 was continued. The following changes were agreed to:

TR-41.3/93-11-28 (editor) contains updates to Draft 4 sections 4.5.5, 4.6.2, their corresponding Tables 9, 10,and 11 and Figures 46 and 47. Section 4.5.5.1 was changed to: “If the telephone dial or keypad is provided withalpha characters it shall be marked with numbers and letters as shown in Table 11.”

TR-41.3/93-11-32 (C. Chamney, Sprint) proposes changes to the transmit and receive frequency response in4.2.4.3 and 4.2.1.2.2. The proposal was accepted except that the receive response was changed by making the lowerlimit -3 dB per octave from 1000 to 3000 Hz and the upper limit -24 dB per octave from 4000 to 8000 Hz.

TR-41.3/93-11-27 (P. Coverdale, Northern Telecom) proposes an informative appendix that provides conversionfactors between the IEEE 269 loudness rating in PN-2892 and the ITU-T P.79 loudness ratings. Some errors werecorrected: The 5.7 km length should have been 4.57 km, and upper end of the transmit range increased 3 dB to 16,18, and 20 from 13, 15, and 17 respectively.



Appendix D.3.3 from ANSI/EIA/TIA-579 will be added as an informative appendix to PN-2892 to provide therational for the unsymmetrical transmit loudness ratings agreed to (from TR-41.3/93-10-19©).

There were some proposals made to improve the document editorially, by making the transmit and receive sectionsparallel. A new draft is expected for the March meeting.

ADSI

TR-41.3/93-11-31 (Bellcore) requests that work on Analog Display Services Interface (ADSI) be delayed until trialspresently underway are completed. TR-41.3/93-11-33 contains a listing of all related ADSI Bellcore documents.Bellcore will keep TR-41.3 informed of the progress.

LeRoy Baker, Reliance Comm/Tec

TR-41.4, NCTET1E1 LIAISON

Four papers from Inline Connection Corporation (D. Goodman) were distributed for information:

TR-41.4/93-12-020 , Using the IEEE LAN coding System to Communicate Bitstreams across Internal TelephoneWiring (in Coordination with Transmission of Analog Video) (T1E1.4/93-311), notes that Manchester Codingtechniques used in common IEEE LANs can be used to communicate over internal telephone wires. Therefore, thesame hardware used to implement 802.3 LANs appears to offer a simple solution to the requirements for premisedistribution set out by the T1E1.4 ADSL committee.

TR-41.4/93-12-021 , On 2-Way Broadband Communication over POTS Internal to the Residence (T1E1.4/93-266). This follow-on paper to TR-41.4/93-12-020 develops topology for premises networks and suggests thatanalog video distribution over the premises is most desirable.

TR-41.4/93-12-022 , Using the Telephone Wires to a Residence for the Distribution of Broadband Signals toSettops and Computers (T1E1.4/93-195R1), describes some basic principles and specific techniques ofcommunicating broadband signals over telephone wiring internal to a residence.

TR-41.4/93-12-023 , Transmission of Full-motion Analog and Digital Video and other Wideband Signals overthe Twisted Pair Wiring Internal to apartment and Office Buildings. This is a tutorial paper on the marketing andsystem level advantages of the system proposed.

Three additional papers were distributed from T1E1.4:

TR-41.4/93-12-025 , Method for Distribution of Broadband Signals in a Premises to Settops and Computers overExisting Telephone and/or Cable television Distribution Wire and Cable (M. Kelly, BS Enterprises), suggests theuse of a data over voice system to distribute digital signals over premise telco wiring.

TR-41.4/93-12-026 , T1E1.4 Ad Hoc Meeting Report on Intra-Premises signal Distribution Issues, November17, 1993 (T1E1.4/93-328).

TR-41.4/93-12-027 , Carriage of ATM-Based MPEG Signals on ADSL (T1E1.4/93-326), is a request forinformation to TR-41 from T1E1.4.

ISO/IEC JTC1/SC6/WG6 LIAISON

I. Heyward (AT&T, Chair TR-41.4) gave the ISO/IEC JTC1/SC6/WG6 liaison report. The TR-41.4 ChannelAggregation document has been accepted as a Committee Draft (CD) by WG6. Some issues were raised and ISOwill be sending liaisons to TR-41.4.

[Technical editor’s note: N. Kenyon (British Telecom) has suggested a harmonization of the U.S. ChannelAggregration approach and ITU-T SG 15 H.AGG, which he terms HB.AGG. If there is support in ISO/IEC forthis harmonization, HB.AGG could be considered at SG 15 in May.]

SP-3014, I NTEROPERABILITY REQUIREMENTS FOR NX 56/64 KBIT/S CALLS

The draft document is out for ballot with a closing date of December 28, 1993. The document has also been acceptedin ISO/IEC JTC1/SC6/WG6 as a baseline for an international standard and is in the Committee Draft (CD) stage.



PN-2349, REVISION OF EIA/TIA-547, NCTE FOR DS1 SERVICES

An editor is still needed for PN-2349. There are figures missing from the document. However, a hard copy draftwill be brought to the March 1994 meeting.

REVIEW OF FCC DOCUMENT FCC 93-4834

It was requested that TR-41.4 review and comment on the document FCC 93-484 (TR-41.4/93-12-024). This isa petition to amend Part 68 Rules to add ISDN BRA access, PSDS access and correct errors. The followingcomments were made: Section 14(h) (3) (iii), subsection (a) and (b), and Table V should be deleted becausescrambling is not an issue related to network harm.

FUTURE WORK DIRECTION FOR TR-41.4

The group had extensive discussions on new work items; primarily, the concept of a “Multimedia Router.”

Proposed Organization Items

V. Boersma (Northern Telecom) proposed several organizational items. Potential working groups include groupsfocused on:• Transmission media (Incoming from the network)• Transmission technologies• Architecture and service definitions• Transmission distribution• The multimedia “box” itself.

V. Boersma proposed that TR-41.4, TR-41.8.2, and TR-41.5 (Auxiliary Devices) all be involved in the work. TR-41.5 is currently not an active group. The proposals were discussed with no final resolutions being reached. Thegroup generally agreed that TR-41.8.2 would be involved in the customer premises distribution aspects of the work.

Technical Components and Associated Standards Work

The group discussed the various potential technical components and the other standards groups involved. Thefollowing categories were discussed:• Transport media (network side)• Transport technologies (network side)• Service, transport media (customer side)• Transport technologies (customer side)

There was discussion of the standards groups and industry forums that are addressing the various technologies,including T1E1, T1S1, EIA-CE, ISO/IEC JTC1/SC25, TR-41.8, CABA, T1A1, TR-29, TR-30, MMCF, MCCOI,ATM-F, IEEE SCC31, and IEEE 802. It was concluded that TR-41.4 needs better and more comprehensiveknowledge of the work being done in other standards groups. I. Heyward (AT&T, Chair TR-41.4) said she would tryto get some more information on this topic.

Issues

The group spent some time brainstorming which issues were important and would need to be addressed. Thefollowing issues were mentioned:

• Wiring considerations• Two-way versus one-way communication• Bandwidth requirements (upstream versus downstream)• Box functionality–Splitters–Intelligent devices• Other device definition• Types of input (what should be addressed first?)• Service providers – Telco versus Cable TV• Are there manufacturers for the devices?• Economics



TR-41.7 SAFETY AND ENVIRONMENTAL CONSIDERATIONS

BI-NATIONAL TASK GROUP

An impact statement defining the product changes required to meet the new Bi-National Standard was discussed inTR-41.7.1; assignments were made.

The next draft of the Bi-National Standard will be available to the four Bi-National Task Group (BNTG) members(CSA, UL, TIA and CBEMA) in December 1993. Comments will be resolved at the March 11, 1994 BNTGmeeting in Clearwater, Florida, followed by an expanded, by invitation only, BNTG and BNTF (Bi-National TaskForce, the formulating group for the BNTG) meeting in the Fort Lauderdale area on March 14 and 15.

TR-41.7.1/93-12-04 was discussed at length in TR-41.7.1. The incorporated changes are shown in TR-41.7/93-12-03 . The main proposal was changing the overvoltage testing in the Bi-National Standard by replacingthe MDQ 1.6 A fuse wiring simulator with a short section of 32 AWG wire. The I2t would be increased from 45 to80 with the rationale of protecting the line cord (I2t=320) with two devices in parallel instead of protecting thenetwork jack (I2t=400) and wiring with three devices connected in parallel. The proposal was contentious, and wasvoted down. There were other changes in the proposal that were not so contentious, but they were not consideredapart from the issue above.

SURGE PROPOSAL

There were no new contributions on this subject and no discussion.

ESD REQUIREMENTS

The Project number for the revision of ANSI/EIA/TIA-571-1991, Environmental Considerations for TelephoneTerminals, is PN-3283.

TR-41.7/93-12-04 is a revised proposed replacement for the ESD section in the ANSI/TIA 571-1991 Standard(PN-3283, Revision of EIA-571). The changes agreed to at the last meeting were incorporated. They includedmoving the section dealing with the statistical calculations to a normative annex, adding a statement that more testpoints are needed for large or complex equipment, and using the definitions in IEC 801.2 Second Edition for thefailure modes. An annex will be added with examples of what might constitute each type of failure for telephonesand PBXs; it awaits further input from contributions. The statistical methods in this proposal have been proposed toindustry but have not yet been adopted into any standards.

TR-41.7/93-12-05 objects to the proposal because of the high peak current and risetime seen using a 6 GHzoscilloscope produced by a commercially available ESD simulator. This ESD simulator met the waveformrequirements in IEC 801-2 Second Edition, the suitability of the discharge distribution for human body contact(severity level versus number of discharges) and the total number of discharges per test point. The waveformmeasurement issue will be addressed by the ESD Association at their February meeting. Further developments willbe reported to TR-41.7.

There was also concern expressed regarding the inclusion of some of the testing methods in Bellcore TR-1089. Itappeared that they were included but it will be studied further by the Bellcore representative. No resolution to theobjections was accepted.

LIAISONS

USAG IEC TC74The next meeting of USAG IEC TC74 will be in the Fort Lauderdale area on March 16 and 17. It is anticipated theover voltage issue will be agreed upon in the BNTG so it can be submitted as an in-country deviation for IEC 950.

T1E1.7The standard for Electrical Protection of Telcom Network Plant At Entrances To Customers Structures and Buildingshas been approved for T1 letter ballot. Work on the standards for Electrical Protection of Network Operator-TypeEquipment Positions and Protection of Telcom Links Against Physical Stress may be ready for T1E1 letter ballot inFebruary. The standard Basic Protection Against HEMP for Central Offices and Similar Facilities (An Above-Baseline Standard) completed T1E1 letter ballot and may be ready for T1 letter ballot in February.

IEEE STD 1100TR-41.7/93-12-06 , Liaison Report and Minutes of IEEE Std. 1100, was submitted for information only.



TR-41.7.1 NORTH AMERICAN TELECOMMUNICATION EQUIPMENT SAFETY

BI-NATIONAL TASK GROUP

An impact statement defining the product changes required to meet the new Bi-National Standard was discussed andassignments were made. This will allow the industry to set a realistic phase-out date for the present Standards suchas UL-1459 and CSA-225.

IEC/TC74/WG7

The ETSI ISDN safety requirements are going to be proposed to TC74. Some European countries have alreadyadopted these requirements.

There is a conflict between the Bellcore TR-1089 requirements and the proposal going forward in TC74. TheBellcore TR-1089 requirements do not allow inadvertent contact with uncadenced ringing voltage (typically 85 voltsrms) in a partially filled shelf where the ringing voltage may be located on the inside of the backplane at the rear ofthe shelf, on a pin of the vacant connectors on the backplane, or on a line card which has the adjacent slots vacant.TC74 allows inadvertent contact if the equipment is in a restricted access location (RAL) which restricts entrance totrained personnel. This is common industry practice in North America. Although it was discussed, no resolutionwas reached.

OVERVOLTAGE

TR-41.7.1/93-12-04 contains proposals for changes in the Overvoltage testing in the Bi-National Standard. Theproposals included adding a minimum metallic voltage, restricting the Type 2 tests to telephone linecords, clarifyType 4 testing, simplifying the line cord testing and replacing the MDQ 1.6 A fuse wiring simulator with a shortsection of 32 AWG wire. For the latter change the I2t for the test would be increased from 45 to 80 with the rationalof protecting the line cord (I2t=320) with two devices in parallel instead of protecting the network jack (I2t=400) andwiring with three devices connected in parallel. The Working Group cited examples of equipment failure duringType 2 testing so the proposal for changes to Type 2 was withdrawn. Other changes were recommended to furtherclarify and simplify the text. The proposal with the changes incorporated was resubmitted to TR-41.7 as TR-41.7/93-12-03 .

CSA CANADIAN ELECTRICAL CODE

TR-41.7.1/93-12-03 lists the main points of the CSA initiative to adopt international standards as alternativesto existing Canadian Electrical Code (CEC) Part 2 Standards. Deviations would be limited to conflicts with CECPart 1 and these differences would be introduced into the IEC forum. Manufacturers would be allowed to meet eitherthe existing standard or the adopted IEC standard. CSA and the Canadian industry would decide on the order in whichthe standards would be adopted. Since the BNTG is generating an IEC-based standard for telecommunication andinformation processing equipment, it will likely be the first one completed. This was presented for informationonly.

TRILATERAL COMMITTEE

(Please see the Trilateral Meeting report on page 1 of this issue)

The next Trilateral Telecommunications Sectorial meeting will be in Washington DC on December 7 – 9, 1993.Final presentation philosophy was completed. The goal for this meeting is to get to know the participants and tolearn what the current practices are in each country. This group of people may become the NAFTA Harmonizationof Standards for Telecommunication Products Working Group, as required in section 1304 E.

TR-41.7.3 E LECTROMAGNETIC COMPATIBILITY CONSIDERATIONS

The Susceptibility Bulletin, PN-3045 (TSB-52), is in publication at TIA.

EMC IMMUNITY

TR-41.7.3/93-11-20 is the second draft of PN-3210, Radio Frequency Interference Requirements and TestMethods For Telecommunications Terminals. The draft is based on the Bell Canada Technical Advisory Document8465, Electromagnetic Compatibility Requirements and Test Methods For Telecommunications Equipment andSystems. TR-41.7.3/93-11-21 (C. Tenorio, AT&T) contains comments on the draft.



The project was renamed “Requirements for RF Immunity in Telecommunications Terminal Equipment; Part 1:Equipment with acoustic specifications for RF immunity in the Frequency Band from 150 KHz to 200 MHz.”Throughout the standard, the term immunity will be used and susceptibility will not be used. In the Purpose section(1.1), the last paragraph was changed to read “In addition to specifying RFI immunity levels for equipment coveredunder this Scope, the RF environment described in the Standard pertains to all telecommunications terminalequipment (TTE). The standard provides information on testing apparatus, testing system arrangement and radiofrequencies of prime interest in TTE.” The Scope was changed to correspond to the new title by changing the firstsentence to “This standard contains RFI immunity performance criteria for TTE having acoustic output.” Thesechanges allow the pass/fail criteria to be limited to acoustic and functional criteria of telephone sets, therebyexpediting the standard without losing the usefulness of applying the standard to other TTE. The standard can beexpanded later when pass/fail criteria for other classes of TTE can be agreed upon.

The Standard will include two levels of radiated and conducted immunity, the first required and the second desirable oradvisory. The proposed required radiated immunity level is 3 volts per meter over the frequency range of 150 kHz to200 MHz. The proposed Advisory level is 10 volts per meter over the same range. Proposed levels for conductedimmunity have not been agreed to. The frequency range for conducted immunity will be 150 kHz to 30 MHz.

TR-41.7.3/93-11-24©, an article from Compliance Engineering on Performance Degradation due to EMI, and TR-41.7.3/93-11-25©, an article from EMC Test & Design, were for information only. The statistics of the interferingsources stated in TR-41.7.3/93-11-25 do not agree with inputs TIA has received from the FCC. The test results andconclusions seemed valid.

LeRoy Baker, Reliance Comm/Tec

Editor’s Note: The TR-41.8 report was not available as we went to press.

TR-41.9 REGULATORY CONSIDERATIONS

LIAISON REPORTS

TAPAC, TAPAC TTF, TAPAC ATF

The TAPAC meeting has been postponed until February 15 – 17, 1994, in Ottawa.

TR-41 .2 , Conformity Assessment L ia i son

The committee held its first meeting in Scottsdale. There were three speakers on conformity assessment. Issues andfuture work items were identified at the meeting. The main focus of the committee will be to facilitate internationaltrade.

TR-41 .1 L ia i son

The E-911 working group has produced a technical bulletin on the E-911 operations in the U.S. It is being printed.

HARMONIZATION REVIEW

TR 41.9/93-12-051 , Draft 2 Harmonized Subpart D; TR 41.9/93-12-052 , Draft CS-03 Part 2; and TR41.9/93-12-053 , Draft CS-03 Part 7, were each reviewed in-depth for technical content. It was agreed that aneditorial committee would meet in early January to review the Part 68 draft for editorial changes. Following thateditorial meeting, a copy of the document will be distributed to the committee for final committee comment prior tosending the proposal to TIA for industry distribution.

H. Mar (Industry Canada) indicated that PART I of CS-03 will be changed to follow the Part 68 changes that wereagreed to during the review. He also indicated that the through-gain table will probably be included in Section 1-10.The CS-03 equivalent of PSDS (Public Switched Digital Service) differs from that proposed in TR-41.9/93-12-049 , the FCC NPRM on ISDN, PSDS, and Corrections.

Draft CS-03 Part 7 does not include secondary channel rules and thus differs from Part 68. All references tolongitudinal balance will be changed to transverse balance.

Part 68 needs to be consistent in the use of TE (Terminal Equipment) and EUT (Equipment Under Test). The CS-03draft will be reviewed in TAPAC.



FCC NPRM ON ISDN AND PSDS

C. Berestecky (TR-41.9 chair) summarized the ISDN NPRM released by the FCC in docket 93-268 (TR-41.9/93-12-048 and TR-41.9/93-12-049). The comments of the committee are:

• TR-41.9 supports the ISDN proposal with change.• TR-41.9 will include ISDN in its Petition for Rulemaking as amended by its comments.• The encoded analog definition should include reference to U-255 law per the harmonized document.

• The ISDN PRA pulse template should be modified to agree with the industry standards as was done in the TR-41.9 harmonized document.

• The through-gain values for ISDN should be provided.

• The use of on-hook/off-hook terminology is not appropriate for ISDN. TR-41.9 will provide proposed wordingafter its March meeting.

• TR-41.9 had no comment regarding the need for PSDS rules; however, TR-41.9 questioned need for scramblingas specified here and did not think it necessary to consider other subrates to accommodate inverse multiplexingequipment.

• Several typos were noted.

C. Berestecky will provide this information to D. Bart (TIA) as a recommendation for TIA to file comments.

TOLL FR A U D

C. Berestecky reviewed the FCC news release (TR-41.9/93-12-047) regarding NPRM 93-292 proposing thatFCC registered equipment be required to include specific information for the consumer regarding toll fraud (PBX, payphone, and cellular). Since the actual NPRM was not available, TR-41.9 had no comments. C. Berestecky willprovide copies of the NPRM when available. Comments should be sent to D. Bart (TIA).

CANADIAN TELECOM POLICY

The Canadian Telecommunications Act became effective October 25, 1993. This piece of legislation, among otherthings, gives the Minister of Industry Canada the power to establish technical standards and require CRTC to enforcethem; it also gives CRTC the power to forbear from regulating. A brief introduction of the Act and the regulatoryprocess on telecommunications was given for information.

FCC MAKE BUSY REQUEST

The only FCC request (TR-41.9/93-12-050) was for TR-41.9 action on a make busy issue. W. von Alven(FCC) suggests adding a statement to Part 68 noting that requests for make busy are to be coordinated with the localtelco. Time was not adequate to review properly. C. Berestecky will advise B. von Alven (FCC) that we will placethe item on the agenda in March. D. Moon (GDC), R. Provost (Bellcore) and C. Berestecky (AT&T) will draft aproposal.

TRILATERAL CONFERENCE

C. Berestecky reviewed the agenda for the trilateral conference to be held in Washington, DC on Dec. 7, 8, and 9.He will provide the committee with the final trilateral agenda, the pertinent NAFTA chapters, and meeting report.(Please see the report of the Trilateral meeting on page 1 of this issue.)

MUTUAL RECOGNITION AGREEMENT WITH GERMANY

C. Berestecky reviewed the status of the U.S.-Germany discussion on a Mutual Recognition Agreement. In themeetings to date, agreements were reached on the principles for a memorandum of understanding (MOU). It wouldonly cover attachment rules for equipment not covered by CTRS and would be for mutual acceptance of test datafrom accredited laboratories. The U.S. will prepare the MOU and make it available to Germany by mid-January.Copies of MOU will be provided to TR-41.9 when available.

COPEE

C. Berestecky reviewed the status of COPEE on developing a consumer program for energy efficiency. The onlytelephone equipment on the priority list for this program are facsimile and PC peripherals. The EPA



(Environmental Protection Agency) is not happy with the progress of COPEE on developing the consumerinformation package and thus a working group has been formed by COPEE to address this issue.

OUTGOING CORRESPONDENCE

TR-41.9/93-12-037R1 is a letter to W. von Alven (FCC) in which TR-41.9 promises to address issues raisedby Mitel regarding registration issues for VAR-assembled systems. TR-41.9/93-12-038R1 is a letter to J.Dempsay (Teccor Electronics) affirming that the FCC rules are not intended to be quality and reliability standards forconsumers; they are rules for assessing network harm. TR-41.9/93-12-039R1 is a letter to W. von Alven(FCC) indicating that TR-41.9 recommends that all telephones be hearing-aid compatible regardless of theiroperating mode and whether the signal between the handset and base is scrambled or unscrambled. TR-41.9/93-12-040R1 , a letter to W. von Alven (FCC), states TR-41.9’s recommendation that Part 68 be changed to agreewith the ANSI standard T1.403-1989 DS1 Custom/Network Metallic Interface.

FCC/TIA SEMINAR

A seminar agenda outline was developed for the seminar on March 4 – 5 in Clearwater, Florida (TR-41.9/93-12-045 ). An FCC Part 68 Industry Meeting will be held on March 4 in the morning, and the FCC Administration ad-hoc group will meet on March 4 in the afternoon. The seminar will address the current Part 68 and CS-03 rules, testmethodology, application procedures, and the underlining philosophy for the rules. The second day will address whatis coming: harmonization, mutual recognition agreements, NAFTA, conformity assessment, and product typeapproval in Europe and Asia-Pacific. C. Berestecky and H. Mar, in conjunction with D. Bart, will develop a detailedagenda and will contact speakers.

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(CCITT) SG 14 (Formerly SGXVII)



PARTIAL ROSTER OF TR-41, NOVEMBER 30 – DECEMBER 3, 1993, MONTEREY, CA

Vic Boersma, Northern Telecom Chair, TR-41Richard Frank, Rolm Chair, TR-41.1Chuck Berestecky, AT&T Chair, TR-41.2Dennis Rittenhouse, U. of Waterloo Chair, TR-41.3Ilene Heyward, AT&T Chair, TR-41.4Leroy Baker, Reliance Comm/Tec Chair, TR-41.7George Lawrence, AMP, Inc. Chair, TR-41.8Chuck Berestecky, AT&T Chair, TR-41.9

ACTION Consulting Ken Krechmer Northern Telecom Pierre AdornatoAT&T Bell Labs Hernan Noguchi Northern Telecom André BeaudetAT&T Bob Renninger Northern Telecom Victor BoersmaAT&T Charles Berestecky Northern Telecom Severin GodoAT&T Chuck Tenorio Northern Telecom Tom KillamAT&T Douglas Smith Northern Telecom Marco RadojicicAT&T Ed Polansky Northern Telecom John SchickAT&T Steve Whitesell Northern Telecom Bao TranBell Atlantic Trone Bishop Northern Telecom Mo ZonounBellcore Bob Koester Pacific Bell Bob TraceyBellcore Jim Brunssen Reliance Comm/Tec Leroy BakerBellcore Rich Beckman Rolm Tailey TungBellcore Ron Provost Rolm Neal KingCSR Elaine Baskin Rolm Richard FrankEricsson Edwin Sandberg S.R.C.I. Murray VogtFujitsu Jay Farrell Scope Communications F. MlinarskyGeneral Datacom Dave Moon Sprint Local Div. Cliff ChamneyGTE Telephone Oper. Harry VanZandt Stentor Efrain GuevaraGTE Telephone Oper. Richard Panko Stentor Frank MccaugbryIndustry Canada Henry Mar Stentor Murray VogtIndustry Canada Robert Corey Stentor Terry GillMitel John Needham Teccor Elect. C. FrancisMitel Robert Hamilton Telecom Reliability Serv. William BushMobile Engineering John Bipes Telident Martin MoodyMotorola/Codex Don McChesney Thompson Cons. Elec. Tom RussellNISE West Hawaii Stephen Kuba UL Randy IvansNLD Mike Kelly Univ. of Waterloo Dennis Rittenhouse



REPORT OF TR-45.4 PCS/MICROSYSTEMS STANDARDSJANUARY 10 – 13, 1994, SAN DIEGO, CA

TR-45.4 PLENARY

TR-45 has taken over the responsibility of the definitions and acronyms in PCS. As a result, the project PN-3141is to be closed and used as input for the work in an Ad Hoc group in TR-45. TR-45.4 Working Group I wasdeactivated until such time as needed. It is expected that ballot responses for PN-3034 “PCS Service Descriptions”(TSB-104) will be directed to this group (expected in March, 1994).

TR-45.4/94.01.10.02 , PN-2977, Cellular Features Description, Base Line Text dated August 18, 1993. Thisdocument contains Stage 1 Service Descriptions for the features to be included in IS-53 Revision A. The documentwas transmitted to all sub-committees for their comments prior to being sent out for ballot.

TR-45.4/94.01.10.03 (J. Marinho, Chair TR-45) is a letter to the TIA requesting a 30-day ballot for PN-3034(Personal Communications Service Descriptions for Public 800 MHz), as TSB 104.

TR-45.4/94.01.10.04 (S. Jones, Chair TR-45.4 and T. Akers, Chair TR-45.1) requests that the TIA to issue a30-day letter ballot for PN-3165 (Mobile Station - Land Station Compatibility Specification for Analog CellularAuxiliary Personal Communication Service), as IS-94. The ballot will go to both TR-45.4 and TR-45.1 votingmembers.

TR-45.4/94.01.10.05 (S. Jones, Chair) is a response to J. Marinho, Chair TR-45.2, concerning implementationof PN-3142 (CMMRD) and its revision, PN-3277.

TR-45.4/94.01.10.06 (S. Jones, Chair) is a letter to L. Owens, Chair of the Ad Hoc Authentication Group,requesting their comments on PN-3142 (CMMRD) for implementation in PN-3277 (CMMRD, Rev. A).

TR-45.4/94.01.10.07 (S. Jones, Chair) is a response to J. Marinho (AT&T) regarding implementation ofMicrosystems public access capability into PN-3277 (CMMRD, Rev. A).

TR-45.4/94.01.10.08 is a copy of the Ballot for PN-3165 (Mobile Station Land Station CompatibilitySpecification for Analog Cellular Auxiliary Personal Communications Service) for publication as an InterimStandard (IS-94). The ballot had an error, listing the proposed standard as IS-95. It was corrected by a follow-upletter.

TR-45.4/94.01.10.10 is a Standards Project Request form for PN-3296 (MSC-BS Interface [A-Interface]) asdefined by the TR-45 Network Reference Model Requirements. The editor is M. Burke (Motorola).

TR-45.4/94.01.10.11 (D. DeVaney, Astronet) requests elimination of essential IPR in PN-3165 (MobileStation - Land Station Compatibility Specification, IS-94). The issue will be upgraded to the committee.

TR-45.4/94.01.13.01 is a PCS Standards Chart depicting the current status of the open projects in TR-45.4

WORKING GROUP I, PCS SERVICE STANDARDS

The PN-3034 (Personal Communications Service Descriptions for Public 800 MHz ,TSB-104) ballot will be sentout soon. Ballot responses will be handled by TR-45.4. The working group agreed that there was no need for TR-45.4.1 to remain active, and therefore requests TR-45.4 that it be deactivated.

WORKING GROUP II, MSC-BS A-I NTERFACE

The major actions of WG II centered around the development of PN-3296, the requirements document for the MSC-BS (A-Interface) as it is defined in the TR-45 Network Reference Model. Three documents were accepted for thedevelopment of proposed baseline text:

TR-45.4.2/94.01.11.03©� (A. Kwok, AT&T) provides additional A-Interface requirements text for consideration inthe development of the A-Interface (PN-3296).

TR-45.4.2/94.01.11.04©� (M. Burke and D. Wood, Motorola) proposes revised requirements for the development ofthe A-Interface standard.

TR-45.4.2/94.01.11.05©� (D. Kuenzer, DSC) presents the Standards Requirements Document for the A-Interface inthe form suggested by TR-45.4.2 in MSC - BS Interface (A-Interface) Requirements for Public 800 MHz.



WORKING GROUP III, PCS/M ICROSYSTEM

The PN-3165 (Mobile Station - Land Station Compatibility Specification) ballot is due on January 31, 1994. Aninterim TR-45.4 meeting on February 15–18, 1994 will handle the ballot responses.

A work plan was developed for PN-3277 (CMMRD, Rev. A).

TR-45.4 ROSTER, JANUARY 10 – 13, 1994, SAN DIEGO, CA

Stephen Jones, NEC Chair, TR-45.4P. J. Louis, Bellcore Vice-Chair, TR-45.4

ADC Kentrox Betsy SharpAstronet David DevaneyAT&T Alicia KwokAT&T Kimberly HarrisBellcore P. J. LouisEricsson Gains GardnerGTE Telecom. Sciences Jeff CrollickMcCaw Ming ZhangMotorola Mike BurkeNYNEX Erkin CubukcuNEC Stephen JonesNTI Chenhong HuangPacTel Corp Mike CostelloPacTel Corp. Huel HallibrutonQualcomm William BuckleyRogers Cantel Peter OldfieldRogers Cantel Watson ZanU. S. West New Vector Alan Johnson

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.3, TDMA CELLULARJANUARY 17 – 21, 1994, BANFF, ALBERTA, CANADA

TR-45.0.A, AD HOC AUTHENTICATION GROUP

Subject to the International Traffic in Arms Regulations (22 CFR 120 through 22 CFR 130), TR-45.0.A draftsprocedures related to the overall security of cellular telecommunications systems. This includes methods andalgorithms for authentication, encryption, and voice privacy. Much of the group’s material is only available to U.Scitizens, permanent legal residents of the U.S., Canadians, and others as authorized in an export license granted bythe U.S. Department of State.

TDMA SYSTEMS

TR-45.0.A/94.01.19.05 (TR-45.3) requests assistance from TR-45.0.A in three areas related to IS-54-C:authentication and privacy on the DCCH, privacy for short-message services, and privacy for data and fax services.The contribution includes copies of baseline text for IS-54.1-C and IS-54.2-C.

TR-45.0.A/94.01.19.06 (Motorola) proposes a pseudo-random bit generator for use in encrypting fax and dataservices. The contribution is ITAR-restricted under a 48-month license granted by the Department of State: licensenumber 586337. Organizations and individuals entitled to receive copies of the algorithm can obtain C code from L.Finkelstein at [email protected]. TR-45.0.A deferred the contribution to allow time for review.

ANALOG SYSTEMS

TR-45.1 appears to have balloted IS-91 without completing IS-91 Appendix A. (IS-91 is the new analog air-interface standard that incorporates authentication. IS-91 Appendix A should specify the authentication algorithms.)L. Owens (Chair, TR-45.0.A) will check whether the ballot is valid.

PCS SYSTEMS

TR-45.0.A/94.01.19.03, a letter to L. Owens (Chair, TR-45.0.A) from S. Jones (Chair, TR-45.4), forwards PN-3142, Cellular Microcell/Microsystem Requirements Document, for review and comment. TR-45.0.A will providecomments at a meeting to be held with TR-45.4 the week of March 7, 1994.

OTHER HIGHLIGHTS

Motorola indicated they are aware that U.S. patent 5060265 may be essential to standards under development by TR-45.0.A.

TR-45.0.A will try to have an NSA (National Security Agency) representative at the next meeting. The key topic ofdiscussion will be whether to use a single version of data encryption or two versions. The two-version schemewould provide a strong domestic algorithm and a weaker exportable algorithm.

TR-45.3, TDMA CELLULAR SUBCOMMITTEE

TR-45.3 develops TDMA standards IS-54, IS-55, IS-56, IS-7X, IS-85, and IS-130.

TSB-47, IS-54 I MPLEMENTATION ISSUES , PN-3160

TSB-47 identifies problems discovered in IS-54-B. Many of the problems result from supporting IS-54-B mobilestations on other base stations. The following contributions were adopted or adopted as amended:

TR-45.3/94.01.17.06, comprises TSB-47 ballot comments from Qualcomm that were inadvertently misplaced priorto the last meeting. The contribution recommends that § 2.21, Calling Number Identification, be amended to requirethat a second CNI be delivered using a Flash with Info message instead of an Alert with Info message. This avoidsunintentionally returning a mobile station to the Waiting for Answer state after it has entered the Conversation state.

TR-45.3/94.01.17.11, Further Revised PN-3160, “IS-54 Implementation Issues” (Editor, AT&T), is the latest draftof TSB-47, incorporating all adopted changes. TR-45.3 will distribute this draft for default ballot. Only changedsections are subject to the reballot.

TR-45.3 incorporated ballot replies into TSB-47 and distributed the TSB for default ballot (PN-3160 TSB-47 �).



CORRESPONDENCE

TR-45.3/94.01.17.04 contains letters to Bell Atlantic and Matsushita informing them that representatives have notattended the last three TR-45.3 meetings, and therefore, their membership status has been changed from voting tocopies to alternates.

CHANNEL MODEL

TR-45.3/94.01.17.08 (NovAtel) provides results of an experiment to measure joint correlations between fractional-symbol-time values of channel impulse responses. Although these correlations were predicted in previouscontributions from NovAtel, the experiment did not indicate their existence. TR-45.3 referred the contribution toTR-45.3.6.

TR-45.3/94.01.17.09 (NovAtel) discusses features of PCS (Personal Communications Service) channel modelsdeveloped by the T1P1/TR-46 Joint Technical Committee. The contribution recommends that TR-45.3 considerthese models in developing second-generation IS-54/55/56 standards. TR-45.3 referred the contribution to TR-45.3.6.

OTHER HIGHLIGHTS

TR-45.3/94.01.17.10 (TR-45.3.2) comprises comments from TR-45.3.2 concerning a proposed standard from thePCCA (Portable Computer and Communications Association). The proposed standard specifies wireless-modem ATcommands. These commands, which use the +W prefix, are extensions to the basic AT commands specified in TIA-602. TR-45.3/93.01.17.14 contains the adopted version forwarded to the PCCA.

TR-45.3/94.01.17.15 (Editor) is revision 14.1 of the Cellular Mobile Telephone Service Descriptions. The newrevision incorporates § 4.15, Multi-Level Precedence and Preemption, as adopted from TR-45.3/93.06.07.05. TR-45.3 forwarded the document to TR-45.2, Intersystem Operations.

TR-45.3 deactivated TR-45.3.3 and its task groups (at TR-45.3.3’s request) until there is sufficient interest in theworking group’s projects.

InterDigital indicated they are aware of patents that may be essential to standards under development by TR-45.3.

TR-45.3 appointed J. McQueen (SW Bell Mobile) as chair of TR-45.3.6.

TR-45.3 appointed T. Auchter (Motorola) and L. Finkelstein (Motorola) as liaisons to TR-45.0.A.

In response to a request from TR-45 on how to develop standards that support separation of subscriber and mobile-station identity, TR-45.3 will respond that it supports forming a JEM (Joint Experts Meeting) to develop stage-1(user perspective) requirements.

Since it received no further contributions on bit transmission order, TR-45.3 instructed TR-45.3.2 to choose atransmission order for RLP1.

TR-45.3 referred TR-45.3/94.12.13.16 to TR-45.3.1 for review and comment. TR-45.3/ 93.12.13.16, a memo to P.Nurse (Chair, TR-45.3) from J. Marinho (Chair, TR-45.2), provides baseline text and a work plan for IS-53-A,Cellular Features Descriptions. The letter makes two requests of TR-45.3. First, review the document and providecomments by March 14, 1994. Second, review the work plan to make sure TR-45.3’s timing supports the scheduledrelease of IS-53-A. July 1994 is the target publish date.

TR-45.3.2, WG2, DATA SERVICES

TR-45.3.2 develops recommendations for circuit-switched data services, with a focus on Async Data Service andGroup-3 Fax Service.

PROJECT PLAN

TR-45.3.2/94.01.17.04 (Ericsson) lists remaining activities, prioritizes the activities, and proposes a work schedule.The priority list, as adopted by TR-45.3.2, is as follows:

1. Finish SDL (Specification and Description Language) diagrams. Review the +W standard proposed by thePCCA.

2. Prepare new stage-2 call sequences based on the IS-54 call model.



3. Review IS-54.2-C. Propose changes to support data services.

4. Verify and validate IS-54-C.

5. Prepare supporting text for the SDL diagrams. Select the AT commands to be supported in PN-3123. AssignAT command functions to the MT2 (Mobile Termination) and IWF (Interworking Function). Prepare procedurestext for PN-3123.

6. Prepare overview text for IS-130. Verify and validate PN-3123 and IS-130.

IS-130, U M INTERFACE — RLP1, PN-3306

This standard specifies Radio Link Protocol 1, the air-interface link protocol that supports async-data and faxservices. TR-45.3.2 adopted SDL (Specification and Description Language) diagrams for IS-130:

TR-45.3.2/94.01.17.03, RLP1 SDL Diagrams and Variable List (Chair), comprises four D-size SDL (Specificationand Description Language) diagrams and a list of variables, primitives, and pass parameters used in the diagrams.TR-45.3.2 decided to try a simplified version of RLP1 that deletes the RR (Receiver Ready) and RNR (Receiver NotReady) supervision PDUs. The chair will archive diagrams for the existing protocol, as amended, and prepare SDLdiagrams for the new protocol.

TR-45.3.2/94.01.17.05, RLP1 Frame Format and Bit Order (Ericsson, Motorola), makes a number of proposals.First, RLP1 frames should be described using the bit numbering, octet numbering, and FCS (Frame CheckSequence) mapping of Q.921 and V.42. Second, compressed data should be mapped into RLP1 frames using theformat of V.42 bis. Third, to maintain octet alignment, the header should include five 0 bits. Fourth, the FCSshould be generated as per Q.921 and V.42. Finally, the bit order of transmission should allow for simultaneousFCS generation and FEC (Forward Error Correction). TR-45.3.2 adopted all proposals except the last, which itdeferred to allow time for review.

TR-45.3.2/94.01.17.07, Simulation Results for the CCITT-16 CRC (NTI), reports simulation results for theCCITT 16-bit CRC (Cyclic Redundancy Check). The following conditions were used for the simulation: 5 km/hvehicle speed, 17 dB SNR, IS-54 channel model. No undetected errors were recorded for the entire sample of 1million RLP1 frames. The contribution recommends that the RLP1 standard include the CCITT 16-bit CRC.

The working group discussed the merits of PDU-based (Protocol Data Unit) encryption and SDU-based (Service DataUnit) encryption. PDU-based encryption has four advantages. First, it spreads out processing load. Second, itlocalizes errors. An error in one PDU does not affect subsequent PDUs. Third, it works for acknowledged andunacknowledged data. Fourth, it has been licensed by the Department of State. SDU-based encryption has a singleadvantage: it keeps encryption separate from the ARQ process and therefore has no impact on the SDL diagrams.Due to the advantages of PDU-based encryption, TR-45.3.2 adopted this scheme. When constructing a PDU, thetransmission controller will pass a 32-bit number to the encryptor. The encryptor will return a mask that thetransmission controller will use to protect the user data within the PDU. The 32-bit number will contain a 7-bit or8-bit sequence count, one bit to indicate transmission direction, and the 1-bit SAPI (Service Access Point Identifier).The remaining bits will be overflow from the sequence count.

OTHER HIGHLIGHTS

TR-45.3.2/94.01.17.06 (Ericsson) and TR-45.3.2/94.01.17.08 (NTI) present stage-2 (network perspective) callsequences for data and fax services. The call sequences are based on an IS-54 call model. After the working groupreviewed these contributions, J. Michaelides (NTI) and H.P. Naper (Ericsson) agreed to prepare a mini stage-2description based on the IS-54-C call model.

TR-45.3.2/94.01.17.09 is the PCCA’s proposed standard for wireless-modem AT commands. TR-45.3.2 reviewedthe proposed standard and forwarded their comments to TR-45.3 as TR-45.3/94.01.17.10.

TR-45.3.3, WG3, DIGITAL STANDARDS

TR-45.3.3 develops the all-digital cellular standards.

TR-45.3.3.1 recommended that it be deactivated until there is sufficient interest in the task group’s projects. TR-45.3.3 adopted the recommendation.



TR-45.3.3.5 recommended that it be deactivated until there is sufficient interest in the task group’s projects. TR-45.3.3 adopted the recommendation.

TR-45.3.3.1, TASK GROUP 1, MATRIX

TR-45.3.3.1 compiles and evaluates proposals for the digital control channel (DCC). TR-45.3.3.1, TR-45.3.3.3,and TR-45.3.3.4 met jointly. The following report covers these joint meetings.

IS-75, UM INTERFACE — CALL CONTROL, PN-2969

TR-45.3.3 adopted TR-45.3.3.1/94.01.17.03, Updated baseline text for PN-2969 Call Control (NTI), latest versionof baseline text for IS-75. The contribution comprises 9 major sections.

TR-45.3.3.5, TASK GROUP 5, MS/BS REQUIREMENTS

TR-45.3.3.5 is responsible for PN-3185 and PN-3186. TR-45.3.3.5 passed its baseline documents and deferredcontributions to TR-45.3.6. It then asked TR-45.3.3 to deactivate the task group until there is sufficient interest inthe task group’s projects.

TR-45.3.5, WG5, SPEECH CODECS

TR-45.3.5 develops standards for speech codecs, including IS–85, IS-78, and IS-79. The working group did notmeet.

TR-45.3.6, WG6, ENHANCED DUAL-MODE STANDARDS

TR-45.3.6 is responsible for IS-54-C, IS-55-B, and IS-56-B.

M ISSION AND CHARTER

TR-45.3.6 adopted a scope and charter (TR-45.3.6/94.01.17.06, McCaw). Prior to June 1994, the working groupwill recommend IS-54-C to TR-45.3. The standard will support sleep mode, microcells, microsystems, eliminationof border issues, enhanced identity structures, short-message services, and establishment of async-data and fax callson digital traffic channels.

IS-54-C, DUAL-MODE MS-BS COMPATIBILITY , PN-3011

This standard adds DCCHs (Digital Control Channels) to IS-54-B. TR-45.3.6 adopted baseline text for IS-54.1-Cand IS-54.2-C:

TR-45.3.6/94.01.17.04, Updated proposal for Cellular System Dual-Mode Mobile Station – Base Station DigitalControl Channel (Ericsson, McCaw), proposes baseline text for IS-54.1-C. The contribution comprises 9 majorsections: terminology, general, optional mobile-station facilities, physical layer, layer-2 operation, layer-3 operation,SMS (Short Message Service) higher-layer operation, identification, and mobile-station-specific requirements.Change bars indicate revisions made to the first version, TR-45.3/93.12.13.13.

TR-45.3.6/94.01.17.05, Baseline Text for IS-54.2 (Ericsson, McCaw), proposes that IS-54-B be adopted as baselinetext for IS-54.2-C.

Condensed from Cellular TechNotes, January, 1994. Next Generation Information Consulting, Alan Sacuta,V:403 239–4089, F:403-239–4306



TR-45.3 PLENARY ROSTER, JANUARY 17 – 21, 1994, BANFF, ALBERTA, CANADA

Peter Nurse, AT&T Chair, TR-45.3

Astronet David DeVaneyBell Mobility Raymond SoBellSouth Cellular Thomas E. RichterEricsson Charlie ChinEricsson Eric TurcotteEricsson GE John DiachinaEricsson GE Krister RaithEricsson GE Al SacutaEricsson Research Hans Petter NaperHewlett Packard Tom YeagerHughes Network Sys. Dave WenkIFR Systems Lyndon ZielkeInterDigital Nick PineMcCaw Cellular David HolmesMcCaw Cellular Adrian SmithMotorola Tom AuchterMotorola Louis FindelsteinMotorola Bob GiomettiMotorola Eric SchormanNEC America Ed OrnelasNokia Mark WellsNovAtel Allan AngusNTI Kashore RajNTI Paul MecheOKI Telecom Steve HardinRogers Cantel P.F. NgSharp Rock ShihSony Electronics Simon MizikovskySouthwestern Bell Mob. John McQueenSouthwestern Bell Tech. Terry WattsTexas Instruments Elliott HooleToshiba John Gabor



TR-46 MOBILE AND PERSONAL COMMUNICATIONS 1800 MHZSTANDARDS, JANUARY 17 – 21, 1994, PHOENIX, AZ

Approximately 30 member companies participated in this meeting. There was a strong contingent suggesting GSMuse for PCS in North America.

TR-46 MOBILE AND PERSONAL COMMUNICATIONS 1800 MHZ COMMITTEE

TR-46/94.01.21.04 (S. Jones, Vice Chair) discusses the criteria for sponsoring a week-long TR-46 meeting(including computer, laser printer, and copy support).

TR-46/94.01.21.05 (Nokia) is Nokia’s patent licensing assurance. It will be forwarded to D. Bart of the TIA.

TR-46/94.01.21.06 (A. Dayton, NSTAC Wireless Service Task Force) is committee correspondence to A.Kripalani requesting National Security and Emergency Preparedness (NS/EP) requirements in PCS standards. AllTR-46 subcommittees will review this subject at their next meeting.

TR-46/94.01.21.07© (M. Woinsky, T1P1) is a copy of T1P1’s technical report on Network Capabilities,Architectures and Interfaces for Personal Communications. This is a good overview document of the referencearchitecture, information flows, nomenclature, interfaces, and physical architectures for PCS. TR-46.1 will considerthe review and report back to TR-46.

TR-46/94.01.21.08 (M. Hosford, Chair of the Ad Hoc Privacy and Authentication committee) is a meetingsummary concerning the use of synchronous mode encryption (requested by the Department of Defense).

TR-46.1 SERVICES

TR-46.1/94.01.17.04 (Bellcore) recommends ISDN call control procedures and protocols for an A Interface. Itwas submitted primarily to TR-46.2 (TR-46.2/94.01.17.09 ) and also to TR-46.1 for information.

TR-46.1/94.01.17.05© (Nokia) provides requirements for the interface between a radio system and PCSC. It wasremanded to Working Group I on requirements.

TR-46.1/94.01.17.06© (M. Hosford, AT&T) recommends that all Um Privacy and Authentication functions shouldbe located in the PCSC. This contribution was also submitted to TR-46.2 (TR-46.2/94.01.17.03©).

TR-46.1/94.01.21.01 (P.J. Louis, Chair) submits PN-3168 (Personal Communications Service descriptions for1800 MHz) to R. Amy, Chair T1S1. TR-46.1/94.01.21.03 is his response. Areas of concern include:multirate circuit mode unrestricted connection service description, number identification presentation, and placeswhere the standard differs from ANSI T1.625. The document is being used as comment input to the PN-3168 ballotresponses.

TR-46.1/94.01.21.02 (P.J. Louis, Chair) submits PN-3168 (Personal Communications Service descriptions for1800 MHz) to S. Engelman, Chair T1P1.

TR-46.1/94.01.21.05 is the Project Request and Authorization form for PN-3307 Radio System/ PCSC (AInterface) Requirements for 1800 MHz. This project develops requirements for the A Interface, as an internal referencefor TR-46. It will not become a standard in and of itself.

WORKING GROUP I, SERVICE DESCRIPTIONS AND SYSTEM REQUIREMENTS

TR-46.1.1/94.01.18.03© (A. Kwok, AT&T) proposes an outline and initial text for the A interface requirementsdocument. The document was used as input to the draft of the proposed baseline text.

TR-46.1.1/94.01.18.04© (M. Hosford, AT&T) states that the A Interface should support real-time air interfacecontrol signaling from the BTS and to the BSC. This is to be considered in the requirements development.

TR-46.1.1/94.01.18.05© (M. Hosford, AT&T) deals with secure interface requirements for PCS, and recommendssome modifications. They will be considered in the requirements development.

TR-46.1 .1 /94 .01.19.01 (S. Jones, NEC) is the edited revision 0.6 of PCS Requirements for 1800 MHz (PN-3167), dated December 10, 1993. It was modified during the meeting.



WORKING GROUP II, NETWORK REFERENCE MODELS

TR-46.1 .2 /94 .01.20.01 (V. Kripalani, AT&T) is the proposed baseline text for PCS Network reference modelsfor 1800 MHz (PN-3169), dated Jan. 17, 1994. The document was modified during the meeting. There was someconfusion regarding the interfaces to the DMH (I Interface). This interface will be studied further.

TR-46.2, INTERSYSTEM OPERATION

TR-46.2 revised its work plan. TR-46.2 reviewed the topics (table of contents) of PN-3212, PCN to PCNIntersystem Operations, to create a list that can be used for both GSM and IS-41 MAPs development.

TR-46.2 created separate projects for the following standards:

• Intersystem operations – PCN-to-PCN work plan based on the IS 41 MAP (TR-46.2/94.01.20.01 , in WGII, see below)

• Intersystem operations – PCN-to-PCN work plan based on the GSM MAP (TR-46.2/94.01.20.02 , in WGII, see below)

• Interworking/Interoperability between the PCN MAPs.

The companies involved in the work on GSM are Ericsson, NTI, Siemens, Nokia, and MCI. The companiesinvolved in the work on IS-41 are AT&T, Bell Atlantic, GTE, Bellcore, McCaw, Qualcomm, and Motorola. Arevised schedule work plan was created; it was accepted at the closing plenary of TR-46.

TR-46/94.01.21.03 (D. Rollender, Chair TR-46.2) lists the work plan highlights for PCN with Other Networks(WG III), PCN-to-PCN (WG II), and Signaling (WG I). WG III shows three projects of intersystem operationsbased on GSM MAP, IS-41 and interoperability/inter-working.

TR-46.2/94.01.17.02© (J. Laatu and E. Durchman, Nokia) describes Nokia’s concept of the overall structure of theA Interface.

TR-46.2/94.01.17.03© (M. Hosford, AT&T) recommends that all Um Privacy and Authentication functions shouldbe located in the PCSC. This contribution was also submitted to TR-46.1 (TR-46.1/94.01.17.06©).

TR-46.2/94.01.17.04© (J. Laatu, Nokia) provides a method to support multiplicity of PCS air interfaces over the AInterface.

TR-46.2/94.01.17.05© (E. Durchman, Nokia) proposes a work plan for the development of the A Interface standardfor PCS.

TR-46.2/94.01.17.06 (E. Figueras, Siemens Stromberg Carlson) suggests a modified contents for the TR-46.2.2 PCS to PCS Network Intersystem Operations document, to provide consistency between that document andPCS System Requirements, Service Descriptions and Network Reference Model as defined by TR-46.

TR-46.2/94.01.17.07 (E. Figueras, Siemens Stromberg Carlson) identifies a number of inconsistencies in the TR-46.2.2 Table of Contents.

TR-46.2/94.01.17.08© (M. Cobo, Ericsson) suggests modifications to the work plan for TR-46.2.2 WorkingGroup. Annex C is a list of topics and will be used instead of a table of contents for the work plan.

TR-46.2/94.01.17.09 (Bellcore) recommends ISDN call control procedures and protocols for an A Interface. Itwas also submitted to TR-46.1 for information (TR-46.1/94.01.17.04 ).

TR-46.2/94.01.17.10© (D. Moghe, NTI) proposes a methodology for capturing and maintaining agreements madeduring meetings.

TR-46.2/94.01.20.06 (H. Chu, Chair TR-46.2.1) lists three areas that TR-46.2.1 recommends for study:

• Multiple Um interface signaling protocols• Multiple MAP protocols• Interworking/interoperability



WG I (NETWORK SIGNALING)

As a result of TR-46.3.1 clarifying its charter as providing guidance and directions to JTC regarding support ofservices and requirement by layer 3 protocols, TR-46.2.1 modified its focus of work to the A Interface.

TR-46.2.1 withdrew the recommendation that call control for the A Interface be based on T1.607, since the workinggroup is reconsidering and refocusing the work plan. The working group also withdrew the recommendation forproducing separate documents on the A and Um Interfaces.

WG II, PCN-TO-PCN INTERSYSTEM OPERATION

TR-46.2/94.01.18.01 (M. Cobo, Chair TR-46.2.2) recommends the adoption of a modified work plan for TR-46.2.2. It was agreed that this document would be the working document.

PCN-TO-PCN BASED ON IS 41 MAP

TR-46.2/94.01.20.01 is the agreed work plan for PCN-to-PCN intersystem operations based on IS-41 MAP.The work plan is based on revision B of IS-41 and will incorporate the changes being made in TR-45.2 for revisionC before completion. Projected completion is September of 1994.

PCN-TO-PCN BASED ON GSM MAP

TR-46.2/94.01.20.02 is the agreed work plan for PCN-to-PCN intersystem operations based on GSM MAP.

It was agreed that E. Figueras would be the main editor for the PCN-to-PCN Intersystem Operations for the sectionbased on GSM MAP.

TR-46.2 .2 /94 .01.19.02 (E. Grasser, Siemens) makes changes to chapters 12 and 13 of the GSM MAP toconvert it to PCS MAP. This was needed because of the migration from CCITT TCAP to ANSI TCAP.

Several modifications were made to PN-3212, PCN-to-PCN Intersystem Operations baseline text, because of themigration from the CCITT TCAP to ANSI TCAP, all from E. Figueras (Siemens Stromberg Carlson):

• TR-46.2 .2 /94 .01.19.03 modifies chapter 5.• TR-46.2 .2 /94 .01.19.04 modifies chapter 4.• TR-46.2 .2 /94 .01.19.05 modifies chapter 11.• TR-46.2 .2 /94 .01.19.06 modifies chapter 15.

TR-46.2.2/94.01.19.07© (A. Lansisalmi and E. Durchman, Nokia) contains a transformation table from GSM toPCS terminology to be used for discussion. E. Figueras will be responsible for the updating of this table.

TR-46.2.2/94.01.19.08© (A. Ahtiainen, Nokia) contains draft baseline text for subsection 14.6.1 “Abstract syntaxof Mobile Service Operations.”

TR-46.2.2/94.01.19.09© (A. Ahtiainen, Nokia) contains draft baseline text for subsection 14.7.1 “Abstract syntaxof Mobile Service Data Types.” As documentation for PCS MAP, it will be used as input for ongoing discussion atsubsequent meetings.

A. Lansisalmi and E. Durchman (Nokia) proposed a number of changes and additions to MAP:• TR-46.2.2/94.01.19.10©: Chapter 21• TR-46.2.2/94.01.19.11©: Chapter 5• TR-46.2.2/94.01.19.12©: Chapter 6• TR-46.2.2/94.01.19.13©: Chapter 16.

In accordance with the agreed-upon aggressive scheduling, all contributors will have chapters of the document readyfor distribution and comment at the February meeting.

WG III, PCS TO NON-PCS NETWORKS

TR 46.2.3 held a meeting primarily to conduct verification and validation (V&V) of PN-3211, “PersonalCommunications Networks to Other Network Entities Interface Standard.” The stated purpose of this proposed IS(Interim Standard) is to enable a PCS carrier and an exchange carrier, interexchange carrier, international carrier,consolidated carrier or other carrier to provide interconnecting equipment that operates compatibly.



TR-46.2 .3 /94 .01.20.02 (P.J. Louis, Bellcore) is a draft of PN-3211. There were major disagreements on thetitle (not matching with contents described in the document). The entire document was reviewed. Participants wereasked to come up with contributions at the Vancouver meeting scheduled for the week of Feb. 28, 1994. At thatmeeting a decision, based on the contributions, will be made to continue with a true V&V of PN-3211.

TR-46 ROSTER, JANUARY 17 – 21, 1994, PHOENIX , AZ

Anil Kripalani, AT&T Chair, TR-46Stephen Jones, NEC Vice Chair, TR-46

AT&T Helen Chu NEC Stephen JonesAT&T Mark Hosford NEC R. RathnasabapathyAT&T Anil Kripalani Nokia Juho LaatuAT&T Vera Kripalani Nokia Atte LansisalmiAT&T Alicia Kwok Nokia Sanna MaenpaaAT&T Douglas Rollender Northern Telecom Ed EhrlichBell Atlantic Ed Moore Northern telecom Patrick JohnsonBell Mobility Hilbert Chan NYNEX Erkin ÇubukçuBellcore Cliff Halevi Omnipoint Gary JonesBellcore P. J. Louis Qualcomm Mark EpsteinBellSouth Don Zelmer Qualcomm Tom InklebargerEricsson Gilbert Chein Sharp Prem SoodEricsson Miguel Cobo Siemens Eric FiguerasEricsson Benard Jackson Siemens Stromberg Karl M. LouisEricsson Barry Kratz Southwestern Bell Rolyn CallahanEricsson Filip Lindell SSC Figueras EricMcCaw Ming Zhang Synacom Technology Randy SnyderMCI Wallace Chris TIA Eric SchimmelMotorola Dan Brown U. S. Intelco Networks Kenn MoiseyMotorola Dan Wood

The next issue of Communications Standards Review (Vol. 5.3)is scheduled for late March/early April 1994.



TR-29 FACSIMILE SYSTEMS AND EQUIPMENTJANUARY 31 – FEBRUARY 4, 1994, COSTA MESA, CA

LIAISONS

TR-30 and V.34 Work

L. Brown (Motorola) reported on TR-30.1. The work is now almost complete on the V.34 modem (“V.fast”) andstart-up procedure (V.8). J. Magill (Cray) was appointed editor but J. Brownlie (BT) has continued to create drafts(TR-29/94-01-16 dated Jan 21, 1994) that do not correspond to the direction of the Rapporteurs meeting. L. Brownnoted that he expects a draft from the editor at the February Rapporteurs meeting which would be more in line withthe direction of Rapporteurs meeting.

He noted that Japan currently has indicated that it will vote against V.8. L. Brown feels that this position maychange or that V.34 could be modified easily to include the necessary aspects of V.8.

Work is beginning in TR-30 on a standard for voice/data multiplexing in a modem. D. O’Connor has left RacalDatacom; therefore, there is no Rapporteur for modem management V.im.

TR-29/94-01-18 comprises extracts from the V.34 draft that relate to the start-up. L. Brown asked for commentsfrom the committee that he can pass to the Rapporteurs meeting in two weeks.

SG 8

In order for SG 8 to approve a variant of V.34/V.8 for fax, it would need to be submitted to the June 1994 SG 8meeting. While unlikely, this would make possible the approval of a new modem for fax at the March 1995 SG 8meeting.

TR-29/94-01-10 is a liaison to SG 14 from SG 8 Q10 and Q19. It requests a nondisruptive data rate changecapability. On the reverse of this document is another liaison from SG 8 (Q5 and Q19) noting concerns about V.8bit assignments and concern about the use of amplitude modulated answer tone and calling tone.

SG 8 and 14

TR-29/94-01-11 is a liaison from SG 8 Q5 & 19 to SG 14 Q1 requesting current drafts of V.8 and V.34 andraising concerns about IPR issues. It takes a strong tone about the lack of formal liaison from SG 14.

TR-29/94-01-12 is the response from the SG 14 Rapporteur to the SG 8 liaison. It does attempt to address someof the concerns raised by SG 8, but it does not provide significant detail and pushes aside the issue of nondisruptiverate changes. TR-29 indicated continued concern about the lack of responsiveness of SG 14 to their issues.

L. Brown (Motorola) noted (but did not recommend) that SG 14 could withdraw the half duplex start-up procedures inV.8 and wait for more detailed input from SG 8. Requests from SG 8 for implementation issues of MIPS andmemory size have not been supported because this information tends to be proprietary. He noted that the functionsto support duplex operation (i.e., echo canceling) are a small part of the total V.34 implementation cost.

H. Silbiger (AT&T) noted that there is interest in the UK in support of duplex operation using the procedures of G3Annex C (G3-64). J. Decuir (Microsoft) also noted interest in duplex operation. G. Griffith (Rockwell) indicatedthat there is not a significant time decrease achieved with a duplex G3 procedure versus half duplex procedures.

T1A1

There have been coordination problems between TR-29 and T1A1. TR-29/94-01-09 is the report of an ad hocteleconference between TR-29 members and T1A1 members to address coordination of T1A1.5 and TR-29.3(problems associated with H.DLL or MLP use and implementation of simplex fax operation), and of T1A1.6 andTR-29 (problems associated with G3 transmission in the face of delay).

TR-29/94-01-03 from T1A1 provides additional information on the problems identified with delay and echo.These were associated with a small number of facsimile boards from off-brand manufacturers where theimplementations did not work properly even without delay.

L. Brown reviewed the model described in the T1A1 paper versus TSB 37-A (PN-3064, PSTN Transmission Modelfor Evaluating Modem Performance, from TR-30.3). He noted that the model focuses on a small segment of thepossible networks. Using ERL of 18–24 dB is unrealistic (as this represents less than 0.3 percent of the U.S.network) He will produce a paper on this issue.



PCI

H. Magnuski (Gammalink) reported on the PCI ad hoc committee. They reviewed the minutes of Q1 SG 8 (TR-29/94-01-04) and the response to the U.S. submission to SG 8 (D-103, TR-29/94-01-05). Thanks to thepresence of the ETSI members at the last TR-29 meeting, the U.S. contribution was accepted almost in its entirety.

The PCI ad hoc committee is supportive of the improvements to enhance real-time operation. However, there isconcern about the proposed level of voice support. The user requirements for voice need further clarification. Thecommittee feels that the market requirements for voice functionality necessitate a rich interface. Therefore, voicefunctionality as described should not be proposed for Res. 1 in June 1994.

Revised TR-29-T.611/94-01-01 (see SG 8 D-121 , new draft T.611) was discussed. Several people noted that thisversion is considerably more usable than its predecessor.

T. Farlow (SpectraFax) noted that the delayed CA function does not appear to allow priority other than dates andtimes (last paragraph on page 20). This capability is needed.

TR-29-T.611/94-01-03 is SG 8 TD-2015 which provides extension mechanisms to enhance:

• The exchange mechanism between LA and CAs• The messages (TDDs)• The transfer formats while preserving compatibility with the baseline recommendation.

TD-2015 also includes a mapping of the TDD syntax for the C language.

COLOR FAX

G3 color attendees reported on the SG 8 meeting. The two U.S. contributions submitted were favorably received. Inorder to harmonize G3 and G4 color facsimile, it was agreed to make G4 Huffman tables mandatory. Agreement atthe SG 8 meeting was not reached on the issue of subsampling, and it was agreed to hold an interim meeting toresolve this issue. However, as a result of correspondence (mostly E-mail), it was agreed to support 4:1:1 color sub-sampling; this eliminated the need for the interim meeting.

The TR-29 Color Fax meeting discussed TR-29/94-01-06 , Proposed USA contribution to amend ITURecommendation T.4 to add optional continuous tone color image transmission capability to G3 fax (A. Mutz,Hewlett Packard), and TR-29/94-01-07 , Proposed USA contribution to amend ITU Recommendation T.30 to addoptional continuous tone color image transmission capability to G3 fax (D. Lee, Hewlett Packard). Editingcontinues on this work. It is planned to present these for Res. 1 procedures at the June SG 8 meeting. The goal isto finish the changes to T.4 and T.30 for support of color fax. Four companies will participate in the U.S. (AT&T,Human Communications, Hewlett Packard and Delta Information Systems).

TR-29 approved TR-29/94-01-14 , effect of chroma subsampling on image quality of uncompressed images at 200dpi (A. Mutz, Hewlett Packard), to be submitted via SG D to the June SG 8 meeting. This paper supports the useof default 4:1:1 subsampling.

TEST IMAGES

D. Bodson (NCS) is creating a CD ROM of T.test images (200–250 copies) to distribute to interested parties.

TIA-465-A (PN-2987, U.S. T.4 ) AND TIA-466-A (PN-2988, U.S. T.30 )

The TIA ballot for T.4 and T.30 has closed but additional review is necessary.

PN-2987, U.S. version of T.4, was approved. Eight ballot responses were received for PN-2988, U.S. Version ofT.30. Brooktrout voted no. The no vote and comments received identified a number of errors that need correction,but do not require technical changes.

H. Silbiger (AT&T) suggested that the U.S. submit the relevant parts of TIA-465-A and TIA-466-A to SG 8. J.Decuir (Microsoft) also suggested that the U.S. support the shorter frame size (bit 28) in SG 8. Although there wasopposition to this issue previously, it does assist operation in impaired environments. The U.S. versions also dropG1 and G2 backward compatibility.



PN-2731, FAX ROUTING

TR-29/93-01-17R3 , draft of PN-2731, Fax Routing, was edited to focus on the encoding and decoding of the FIFfield. It was revised to become TR-29/93-01-17R4 .

J. Rafferty (Human Communications) proposed TR-29/93-01-17R4 (Routing of G3 Messages Utilizing theSubaddress) as a committee letter ballot. This proposes a syntax for the subaddress FIF field utilizing the # key as adelimiter/terminator. This was supported. If this ballot is successful, then SP-2731 would stand for industry ballotand become a potential U.S. contribution to SG 8.

H. Silbiger proposed TR-29/94-01-17 , Minor revisions to the title of Annex C to Rec. T.30, as a U.S.submission to SG 8. It supports removing the note restricting the use of G3 Annex C over digital networks orduplex modems. This was supported.

TR-29/94-01-13 , Proposed Modifications to TIA-578 for Voice-Data Conferencing (B. Boykin, Data Race),presents a means to implement a voice to data switch for short data transfers using ECM. This is an alternative tothe Radish (Voiceview) approach that Microsoft is supporting. The committee suggested that this work could beconsidered in TR-30.1, under the broader voice/data work that TR-29 originally supported moving to TR-30. B.Boykin will draft a liaison to TR-30 requesting their support of this work.

Ken Krechmer, ACTION Consulting

TR-29.1, B INARY FILE TRANSFER

D. Duehren (Brooktrout) served as chair in place of P. Bogosian (Chair, TR-29.1, Thought Communications), whocould not attend.

J. Rafferty (Human Communications) reported on the developments in the EMA (Electronic Messaging Association)regarding file transfer and object ID registration.

H. Silbiger (AT&T) noted the interest of SG 8 in BFT and the requirement to include the diagnostic messages thatwere removed from T.434. Therefore, he wants to create a White contribution to SG 8 to add the diagnostic messagecapability as an annex, now that the ITU community understands the need for the diagnostic messages.

TR-29.1 is working on three projects. D. Duehren will file the Project Request and Authorization Forms with theTIA.

BFT CONFORMANCE TESTING

The editor for this project is P. Masters (Fisk Communications). The project develops guides for implementation ofT.434 style BFT and will define tests and files for checking conformance.

BFT PROFILES

The editor is D. Duehren (Brooktrout). This project will define one or more standard profiles of the BFT attributesfor various applications. The work of the EMA MAWG (Electronic Messaging Association Message AttachmentWork Group) will be used where appropriate. Feedback will be provided to the Enhanced BFT project as well.

TR-29.1/94-01-02 , File Transfer Body Part 15 Profile, Draft 6 (EMA Message Attachment Work Group), waspresented.

A formal liaison statement was sent to the EMA Message Attachment Work Group indicating our interest in theirwork and requesting to be kept informed of their progress, particularly with regard to the registration and publicationof Object IDs.

ENHANCED BFT

The editor is P. Bogosian (Thought Communications). The project will look into enhancing BFT, particularly fornegotiation of attributes in applications. The initial focus will be to review the current definition of the Diagnosticmessages.

It was noted that the Diagnostic messages are not in TIA-614 (BFT) Format for Group 3 Facsimile) nor in TIA-465(Group 3 Facsimile Apparatus For Document Transmission). TR-29.1 must resolve what to do about this situationat the May meeting and decide whether to make any modifications to the Diagnostic messages for submission to the



Study Group 8 meeting in June. A small group agreed to work on this before the next meeting, including D.Duehren, R. Lutz, P. Masters, Y. Shachar (National Semiconductor), and L. Nipko (STF Technologies).

Y. Shachar (National Semiconductor) indicated that they had problems when trying to implement the Diagnosticmessages . He volunteered to provide a paper at the next meeting on the problems.

H. Silbiger (AT&T) indicated that we need to find our whether the TIA is or will become a registration authority forregistering object IDs.

M ISCELLANEOUS

TR-29.1/94-01-01 , BFT Issues: Data Format, Compression, Extending Diagnostics (Cognisys). This papersuggests extensions to BFT. No action was taken.

TR-29.1/94-01-03, E. Ross (independent consultant), A Simple Data-Compression Technique. Reprint of article inC Users Journal, 10/92. No action was taken.

David Duehren, Brooktrout Technologies

TR-29.2 FACSIMILE DIGITAL INTERFACES

LIAISON REPORTS

ITU-T SG 8Previous contributions on T.class2 and proposed amendments were well received at ITU-T SG 8 Q5. There isinterest in a new draft of T.class2, for possible balloting at the June SG-8 meeting. There are some issues to beaddressed, summarized in TR-29.2/94-01-14 , correspondence between J. Decuir, H. Hertlein (DBP Telekom) andY. Mori (Ricoh). There is strong international interest in Class 2.0 although which new T.30 functions to beincluded are a subject of discussion. TR-29.2 agreed to generate and submit a new draft Recommendation T.class2(TR-29.2/94-01-19).

Since some ITU delegates object to the references to U.S. national standards like EIA/TIA-578, the committeeproposed to present Class 1 for international standardization, either as a stand-alone Recommendation or as part ofT.class2. TR-29.2 agreed to generate and submit a new proposed Recommendation T.class1 ( to become TR-29.2/94-01-17, see PN-2987 report, page 30 of this issue).

TR-45 .3 .2 .5 and TR-45 .5 .1 .5 , Dig i ta l Ce l lu lar Data Serv icesJ. Decuir reported on activities to support data communications in TR-45.3.2 (TDMA cellular) and in TR-45.5.1.5(CDMA cellular) on PN-3123 (MT2 Serial Asynchronous Control) and PN-3140 (Data Services Option Standard forWideband Spread Spectrum Digital Cellular System), respectively. Both groups are likely to ballot these documentsin late spring. Field trials of data transmission are also possible this year. J. Decuir noted that a firm position onthe Class 2-A changes is needed. Members requested a liaison from these committees.

TR-30.4, DTE-DCE ProtocolsL. Brown (Motorola Codex) and J. Decuir (Microsoft) reported on TR-30.4. L. Brown reported current status of PN-2989, Extensions to Asynchronous Serial Automatic Dialing and Control, which could result in an Interim Standardfor common modem commands for common functions (e.g., flow control, port rate, error correction, datacompression). He also reported on PN-3147, MIB for modem, done with IETF. The SNMP version of the modemMIB still does not contain any FAX services. There is a draft of V.at, but there is still no Rapporteur to completethe work in TR-30.4 or ITU-T SG 14. J. Decuir reported on PN-2812 (In-Band DCE Control for AsynchronousDTE-DCE Interfaces); the current draft (R7) was submitted to this meeting for liaison and possible use by TR-29.2(TR-29.2/94-01-22).

Portable Computer and Communications Association (PCCA)The PCCA is working on standards for Wireless network modems. J. Decuir summarized the contents of the draftMinimum Functional Specification: commands from TIA-592 for ID, new distinct commands for serial port control,and new global commands for selection of Wide Area Network (e.g., PSTN, private wireless, wireless packet,cellular), and Virtual Remote End System. The current draft will be taken to TR-30.4 in a liaison.

PN-1906, MULTIFUNCTION PERIPHERAL INTERFACE (FORMERLY FACSIMILE APPARATUS CONTROL)

R. Lutz (Cognisys, PN-1906 editor) presented a current project status report, TR-29.2/94-01-07 , which providesa good overview of the long history of this project. It was formerly called Facsimile Apparatus Control.



R. Lutz presented a new revised project statement, TR-29.2/94-01-08 , which proposes changing the title andscope of the project. The new project statement separates the physical and data-link layers from the project andsupports the development of a command response interface and protocol. It was accepted for submission to TIA.

R. Lutz presented TR-29.2/94-01-09 , Multifunction Peripheral Interface Standard or Interface (MFPI), PN-1906Strawman Working Document. This is a sizable document that supports host, scanner printer and memoryinterchanges. It also supports extensive format interworking including all the T.4 forms, PCL 4 & 5, Postscript I& II, JBIG, DCX (multipage PCX) Epson FX-80, and ODA text. The document was too extensive for muchcommittee comment at this meeting.

R. Lutz then presented TR-29.2/94-01-10 , a request to TR-29.4 for technical input and simple model to supportfacsimile encryption and authentication in PN-1906. TR-29.4 reported that they did not have specific knowledge inthese areas as government encryption is provided by NSA-supplied equipment.

R. Lutz presented two papers from an AIIM meeting January 10, 1994. The draft standards in these papers, presentedfor information, are of possible use in PN-1906. TR-29.2/94-01-11 is a Review of MS60 (Electronic FolderInterchange Datastream) for MFP. R. Lutz noted that the MS60 definitions are too specific for the MFPI work, butcan certainly be transported via BFT. TR-29.2/94-01-12 is a Review of Open Document Architecture and MS53(single-page subset of ODA specifying size, resolution, and compression) for Application to PN-1906 MFPIStandard, which includes multipage documents. MS53 could be extended to meet the needs of PN-1906. Nodecisions were made.

R. Lutz will organize at least one editing meeting in late February (Southern California), and publish the result as aworking draft at least 5 weeks before the next meeting (May 1994).

The MFPA (Multifunction Peripheral Association) was created to support the MFP market and promotenonproprietary solutions. It held its first meeting January 31, 1994. Discussion covered the needs of the MFPmarket and market segments. This is an industry group, not a standards body, chaired by R. Lutz (Cognisys), whois also the editor of PN-1906. Meetings will be held in conjunction with TR-29 meetings.

PN-2987, CLASS 1-A AND T.CLASS1

J. Decuir (Microsoft, editor of PN-2987, Asynchronous Facsimile DCE Control Standard, Service Class 1, Rev ofTIA-578) presented TR-29.2/94-01-15 , PN-2987, Project Status and Proposed Plans. In order for PN-2987 to beready for industry ballot as SP-2987, TR-29.2/94-01-16 , draft of TIA/EIA-578-A dated January 27, 1994, neededcommittee discussion of new material included in response to Rockwell’s no vote, and it needed new warnings (to bedrafted by B. Boykin of Data Race).

B. Boykin (Data Race) proposed including several parameters from the Class 4 draft, TR-29.2/93-10-67R1 ,including the +FCL, +FAA, +FCT, +FIT and +VPP parameters. He also proposed changing PN-2987 to representother parameters (+FLO and +FPR) in the same style. There was objection that some of these new parameters hadnot been seen. However, J. Decuir pointed out that these could still be studied and proposed for inclusion inT.class1, and that there was an international need for something like +FCL.

B. Boykin suggested that Class 1-A should not include language that prohibits the implementation of commandsfrom one service class in another (e.g., +FAA, +FPP, +VPR). The committee agreed with the principle. J. Decuirwill delete these prohibitions.

In TR-29.2/94-01-16 , §§ 8.5.1 and 8.5.2. are changes that include rules about parameters (e.g., +FLO) which aredefined in more than one service class. B. Boykin proposed that the basic concept be accepted, but that each standardshould not specify what happens in other service classes as it is outside the scope of the standard. He also proposedthat this material should be simplified, moved to a different section so that it applied generally. The committeeagreed to add to section 8 wording such as: “If a parameter is supported and defined in more than one Service Class,there shall be only one instance of that parameter.”

B. Boykin noted that some DCEs provide erroneous responses to command tests; he asserts that the DCE should notlie. The committee supported wording such as: “Responses for a parameter test command shall be accurate incontext of the current +FCLASS setting.”

With the above changes, even without the Annex B warnings, the committee agreed to send SP-2987 to IndustryBallot and to edit the work into ITU style (to become TR-29.2/94-01-17) and submit it (White contribution) asproposed Recommendation T.class1.



Note: After the meeting adjourned, draft warnings for Annex B were submitted as TR-29.2/94-02-27. TIA willdistribute it to TR-29.2, for possible inclusion in PN-2987.

PN-3129, CLASS 2-A AND T.CLASS2

J. Decuir, the editor, presented three papers:

• TR-29.2/94-01-18 , PN-3129, Project Status and Proposed Plans

• TR-29.2/94-01-19 , Revised Draft Rec. T.class2, created by combining the previous draft (SG 8 COM 8-26)with TR-29.2/94-01-20 , Revised Amendments to Proposed draft Rec. T.class2 to support T.30-1993 options

• TR-29.2/94-01-21 , Proposed Changes to Section 8.5.2.8 ECM Retry Count, +FRY (P. Sawyer, R ScottAssociates), as a response to discussion of TR-29.2/93-10-71 at the previous meeting.

The committee agreed to:

• Accept changes in TR-29.2/94-01-20• Include the changes to Section 8 about common parameters.• Accept the revised +FRY description from TR-29.2/94-01-21 for the new draft (excepting the use of

<DLE><“TBD”> as a keep alive indicator)• Have the editor make same changes to T.class2, and submit a new version via TR-29/SG D to SG 8 as a White

contribution• Accept the edited plan in TR-29.2/94-01-04 for PN-3129 as an Interim Standard• Have the editor create draft IS-class2.1 for Letter Ballot.

PN-3130, CLASS 4

B. Boykin (Data Race, editor of PN-3130) presented TR-29.2/93-10-67R1 , the revised draft of class 4. He notedthat we need to address the problems of carrier loss and carrier interruptions, as mentioned in the Adobe paper fromMay, TR-29.2/93-05-27 .

There is a conflict between the new TIA-615 standard (“Extended Command Syntax for Serial AsynchronousAutomatic Dialing and Control”) from TR-30.4 and all the TR-29.2 standards drafted to date. It concerns the DCEreporting +<parameter name>:< values> in response to read or test commands. The committee agreed that TR-29.2should stick to the style it has been using. The TR-29.2 chair will report this issue to TR-30.4, and request thatTIA-615 be modified to allow the reporting of the parameter name before the values to be optional.

No previous TR-29.2 standards reference the use of the S3 or S4 parameters (from TIA-602, “Serial AsynchronousDialing and Control”) used to select the characters for information text and result code reporting. It was agreed thatPN-3130 and PN-3131 (Class 4 and Voice DCE Control) should mandate support for S3 and S4, and that PN-2987and PN-3129 (Class 1-A and Class 2-A) should make this optional.

H. Magnuski (GammaLink) described the concepts of DCE report of Signal Quality, received signal power (units of0.1 dBm), and silence (noise) level on reception. He asked if this could be included in PN-3130. There was generalsupport for the idea, but no action was taken.

There are no current provisions made for manufacturer specific codes. Decuir suggested that ideas in PN-2812, In-Band DCE Control (TR-30.4 project), be considered for these hooks.

Question were raised about the function of Exit from Ready mode. Some members are interested in using Readymode but not AT mode. J. Decuir proposed using PN-2812/TIA-617 methods to encapsulate AT commands andresponses in Ready mode. This idea was tabled.

B. Boykin noted that he had created separate terminators: CST (control stream terminator) and DST (data streamterminator). This was supported.

L. Nipko (STF Technologies) noted that there is a requirement to test the range of argument values supported for thedirectives, while not in ready mode. AT mode commands with similar name? and name=? were suggested andtentatively supported.

B. Boykin proposed to rename the AK directive CT; this was supported.



B. Boykin proposed to harmonize and have only one time scale, instead of multiple time scales. H. Magnuskiinsisted that timer scales support exact timing, such as the T.30 75 ms timers. The committee agreed that timerarguments in Class 4 directives can be more than 0–255 in units of seconds or 0–65535 in units of milliseconds.Units are decimal, not hexadecimal.

There was interest in a proposed new directive CH (Compare HDLC), but a paper is needed.

B. Boykin will make the changes agreed to in PN-3130, and send out either a new working draft or a committeeletter ballot. Members should plan to prototype and test Class 4.

PN-3131, VOICE DCE CONTROL

W. Pitkin (Sierra Semiconductor, editor of PN-3131) presented a corrected summary of candidate voice compressionalgorithms for PN-3131, TR-29.2/93-10-79R1 . This was accepted.

W. Pitkin then presented TR-29.2/94-01-26 , objective technique for choosing a standard voice compression formodems, a paper coming out of the need of his company to define a selection criteria. His criteria focus oncompression efficiency (and therefore DTE-DCE data rate and subsequent storage requirements), DSP MIPs, DSPRAM, and DSP ROM; he discounted the other criteria. The result was a preference for GSM 6.10 or TrueSpeechTM.

It was moved that PN-3131 specify that the DCE shall support at least the IMA DVI ADPCM algorithm or theGSM 6.10 algorithm. The reasoning was that this looked like an adequate technical choice and a feasible politicalchoice. This motion passed, 8-4-3.

The chair asked the No voters for their reasons. These were as follows:• AT&T: there should be one algorithm, GSM 6.10.• Hayes: there should be one algorithm, TrueSpeech.• DSP Group: there could be several acceptable algorithms, including TrueSpeech.• Rockwell: there should be one algorithm, IMA DVI or something new from T1A1.

The committee’s decision was to include the requirement to support DVI or GSM 6.10 in the next draft.

H. Silbiger (AT&T) requested further information on conformance testing and other public documentation for IMADVI ADPCM. He also asserted that any mandatory algorithm should be subject to public revision control.

It was moved and passed unanimously that Table 18 of PN-3131 shall incorporate standard syntax to identify andselect at least all nine algorithms listed in TR-29.2/93-10-79R1 . The committee will form an ad hoc group todevise that methodology and syntax.

The committee was reminded that there was an agreement to incorporate support for the ADSI CAS signal detectionand reporting in PN-3131. The committee was also reminded that some of the commands in IS-101/PN-3131 aredefined in several standards (e.g., +FLO) and that there was a need for common specifications. W. Pitkin will edit inmaterial from previous meetings, TIA-615 harmonization, common command specifications, and off-line editorialcontributions, and produce a new draft for mailing by TIA by April 1.

There is interest to go for letter ballot after the May meeting, and industry ballot after the August meeting.

H. Silbiger (AT&T) prepared TR-29.2/94-01-25 , proposal to use object-IDs for naming compression algorithmsin the Voice Control standard, after the TR-29.2 meeting had adjourned. It was distributed at TR-29.

PN-3294, FACSIMILE DCE APPLICATIONS NOTES

There were no papers submitted. However, the editors of the current Service Class projects (PN-2987, PN-3129,PN-3130, and PN-3131) may contribute material on fax DCE. In particular, a chart should be created listing all the+F and +V commands and references.

PN-2812, I N-BAND DCE CONTROL (TR-30.4 PROJECT)

J. Decuir, the editor, presented TR-29.2/94-01-22 (In-band DCE Control for Asynchronous DTE-DCE Interfaces,revised after SP-2812 ballots from TR-30.4) for information. It has potential use in TR-29.2 standards projects,such as Class 4, etc. No action was taken.



PLUG AND PLAY FOR COM DEVICES

J. Decuir (Microsoft) presented TR-29.2/94-01-23 (Plug and Play COM Device Specification, January 28,1994). This specification supports automatic configuration of devices using the PC COM ports, which is a veryuseful concept. Identification is achieved via control lead operation and a 1200 bit/s interchange. This Microsoftapproach is now public information, open for comment and prototyping.

VOICE/DATA SWITCHING

D. Rife (Hayes) distributed TR-29.2/94-01-05 for information. It proposes several related projects in TR-30.1and TR-30.4 in support of Voice/Data Multiplexing over PSTN Channels.

Joe Decuir, Microsoft

TR-29.3 AUDIOGRAPHICS CONFERENCING

The TR-29.3 meeting was held jointly with SG 8 Q10 Rapporteurs Group.

P. Smith (Worldlinx) reported on the CATS meeting January 28–30. He is Chair of the Technical Committee. N.Starkey (Databeam) is the new President of CATS. Their goal is to enhance and accelerate the acceptance ofaudiographic conferencing. Currently 21 companies are members.

The committee informally discussed TR-29.3/94-01-31 , a news release dated January 10, 1994: Intel bringsgroups together to develop personal conferencing specification. Intel supports a proprietary video compression tech-nology, Indio, and proprietary communications protocols. P. Romano (Polycom) noted that they have discussedwith Intel the support of T.120. Currently Intel does not appear to have made a decision about how they willinterwork with T.120. It appears likely that Intel will support T.120, but less likely that they will support H.320recommendations because H.320 recommendations require support of H.261 video compression. It was noted thatthe T.120 bulletin boards are quite active, both inside TR-29.3 access and outside, with many contacts from outsideNorth America.

LIAISON T1A1

TR-29.3/94-01-16 is a letter to G. Williams acknowledging receipt of liaisons from T1A1.5. It is pointed outthat simplex communication lacks the flexibility to support full multipage facsimile operation in a multipointenvironment and that many enhanced facsimile features are not included in T1A1.5/93-073.

TR-29.3/94-01-18 (T1A1.5) is a report of the ad hoc meeting on division of work between T1A1 and TR-29. It wasagreed that each proposed application over MLP or H.DLL be studied on a case-by-case basis and, when necessary,teleconferences be used to ensure that the proper body is given responsibility and the best solution is specified.

LIAISON ITU-T

TR-29.3/94-01-32 comprises papers from the SG 1 Q20 meeting January 18–28, 1994, including the meetingreport, work plan, and reply to a misdirected liaison intended for WP 1/15 on the possible use of MLP for low bit-rate video coding.

TR-29.3/94-01-06 (AT&T) is H.22Z, a Data Link Layer protocol for simplex applications using the H.221LSD/HSD/MLP channels. This draft submission to SG 15 was introduced for information as a courtesy to Q10/8.It specifies how H.DLL may operate in an MLP channel in a way that does not interfere with T.120 protocols.

TR-29.3/94-01-36, use of packetized elementary stream as an interface point, is a document of the SG 15 expertsgroup for video coding and systems in ATM and other network environments.

T.120

TR-29.3/94-01-14 (BT), T.120, Conference establishment and termination, proposes that an MCU receiving anincoming call with null domain selector may connect the terminal to a unique private domain where onlyadministrative services are available.



T.123, AVPS

Since the time COM VIII-R 48 (April 1992, includes T.123) was submitted to the WTSC for approval, membershave become aware of gaps in T.123 (Protocol Stacks for Audiographic and Audiovisual TeleconferenceApplications) that must be filled to have a usable recommendation. Details on combining MLP and H-MLPchannels into a single serial stream were specified in COM VIII-216. A synchronization and convergencefunction for the dynamic assignment of Q.922 data link connection identifiers was proposed in COM 8-17 . ThePSTN protocol stack was reinterpreted for start-stop transmission to permit the use of serial ports on personalcomputers in D-123 (SG 8 November 1993).

The publication of T.123 has been postponed until these corrections can be adopted by Resolution 1 at the June1994 meeting of SG 8.

At the urging of members who feel it is time to deal substantively with B-ISDN, a nonbinding Appendix III hasbeen added, suggesting a possible profile. This is expected to stimulate further discussion by the June 1994meeting. It is a goal to include a final profile for B-ISDN in the body of the recommendation at an early date.However, some members have reservations about publishing a candidate profile now, noting that alternativearchitectures have been proposed in SG 15 and that as yet there is no broad agreement.

TR-29.3/94-01-03 (AT&T) is proposed text of a White contribution to be submitted as Draft Revised T.123.This text presents the material of TD-2063 (SG 8 November 1993) with editorial changes that clarify the structureof the document and eliminate redundancy.

As the result of discussion at the meeting, a number of additional improvements were applied. TR-29.3/94-01-04 (AT&T) is an additional figure for T.123 showing the architectural model of the SCF. This figure was adoptedas part of T.123 clause 9.1. TR-29.3/94-01-05 (AT&T) shows alternative sequences for N-CONNECT and N-DISCONNECT in T.123. Figures 14-A and 15-C were adopted in place of Figures 14 and 15. CONNECTACKNOWLEDGE is added to the minimal SCF message set but RELEASE is deleted, so the net complexity of theprocedures is unchanged.

TR-29.3/94-01-23 (Ricoh), Proposals and questions for draft T.123, discusses the functional model of caseC/Q.922 for the AGC application and gives an example of the complete protocol structure for AGC/AVC. Thispaper stimulated the revisions of TR-29.3/94-01-04 and TR-29.3/94-01-05 and a clarification of the need forNSAP addresses. TR-29.3/94-01-28 (PTT Nederland Research), Extension of T.123 with B-ISDN ATMprofiles, presents two profiles that could be incorporated in a future revision of T.123. This revision providesconnection-oriented transport services on top of ATM. TR-29.3/94-01-30 (Polycom), SAP address and qualifyof service ambiguities, raises issues concerning T.123 that are important for interoperable implementations. Severalof the points were clarified in TR-29.3/94-01-03rev .

The revised text was reviewed and accepted. With the acceptance of TR-29.3/94-01-03rev , members have agreedto stable normative text for the revision of T.123. The Rapporteur will submit this as a White contribution toarrive at Geneva in ample time to prepare translations for the application of Resolution 1.

T.124, DRAFT REC. T.GCC

TR-29.3/94-01-09 , Proposal for an MLP class 0 multipoint communications environment (DataBeam), proposesan interim conferencing framework that can serve one application per terminal per domain and be fully compliantwith T.122, T.123, T.125. Following discussion, this was revised to express a convention for the user data field ofMCS-CONNECT-PROVIDER that could distinguish between multiple standardized and non-standardized uses (TR-29.3/94-01-09rev). The capability to bring out T.120 products without waiting for T.124 (T.GCC) is verydesirable.

TR-29.3/94-01-10 (PictureTel) is the Draft Rec. T.GCC, Generic conference control for audiovisual andaudiographic terminals and multipoint control units. TR-29.3/94-01-11 (PictureTel) is a report of updated issuesregarding current draft of T.GCC. It includes issues, current status, and a description of the action taken. TR-29.3/94-01-26 (Japan) includes technical and editorial comments on draft Rec. T.124 (GCC). TR-29.3/94-01-29 , T.124 protocol examples of GCC-Conference-Create, Join, and Add for discussion (PTT Nederland Research),diagrams scenarios for the use of MCS primitives during the course of GCC operations among three nodes.

Tentative agreements reached at this meeting include the following:

• Name strings require a larger character set than T.50, possibly T.61.



• Conference IDs will be composed of conference name plus an optional disambiguating suffix, the result to beused locally as an MCS domain selector.

• To avoid duplication of effort, directory-like features (deferred path lookup) will be removed from GCC.• The concept of “ping” will be left for further study.• The need to reserve ports and other bridging resources as part of conference creation requires further discussion.• GCC should seek means of associating separate audio and data calls (for the PSDN and PSTN profiles) as

belonging to the same user.• There is an inclination to remove the idea of multiple application instances.• Remote actuation will be deleted from the first version of GCC and may be redesigned as a separate application.• Bandwidth control, in the sense of flow control for individual MCS channels, is not the proper responsibility of

GCC.• Although the topic has been severed from the core of GCC, there is an urgent need to specify high-level audio and

video controls to operate over MLP.• It is uncertain whether there is a need to retrieve registry entries based on keys that match a specified prefix.• The user data field of MCS-CONNECT-PROVIDER request and indication will begin with an encoding (to be

specified) of the object identifier for T.124.

T.125

TR-29.3/94-01-07 is SG 8’s approval of T.125 MCS protocol specification. The note reports that T.125 wassubmitted to the administrations for a vote by circular letter 48 dated January 7, 1994.

TR-29.3/94-01-27 , Proposal to improve T.125 regarding Detach-User (PTT Nederland Research), suggests thatthere may be advantages in alternative ways of processing the MCSPDUs DUrq and DUin. The possibility of alower subtree surviving MCS-DISCONNECT-PROVIDER is not allowed in the current MCS protocol.

T.SI, STILL IMAGE CONFERENCING APPLICATION

TR-29.3/94-01-12 (Polycom) is the Draft T.SI specification. This package contains the version of November1993, a tabular summary of issues, and a new PDU specification in ASN.1. TR-29.3/94-01-13 (Polycom) isthe T.SI issues list. It includes a Draft ASN/1 definition. TR-29.3/94-01-25 (Japan) contains comments ondraft proposal T.SI. The Japanese experts group on AGC and AVC offers technical comments, editorial proposals,and editorial comments.

TR-29.3/94-01-33 (Polycom) is the generalized T.SI workspace model. This paper justifies changes that allowmultiple annotation planes and support object-oriented operations with only minor impact on the protocol definitionand related data structures.

Tentative agreements reached at this meeting include the following:

• T.SI will count on GCC to collapse terminal-declared capabilities.• Profiles will be expressed through explicit capability sets; there will be no reference to profiles in PDUs.• Better ways are sought to implement image reception checkpointing, possibly with new assistance from GCC.• It is believed possible to refresh the shared display for the benefit of late joiners with no changes to the current

protocol.• The color space CMYK will be dropped.• The progress of workspace palettes will be: black/white/transparent, 16 fixed colors, 224 uniform colors

including gray scales, 24-bit CIELAB true color.• The workspace pixel aspect ratio will remain square at all times, though images with other aspect ratios may be

imported (CIF as baseline, others negotiated).• Pointers are controlled by special PDUs and constitute in effect a plane that lies in front of all the others.• Algorithms for drawing geometric elements need not be prescribed, because renderings in general are only

approximate at each receiver.• It is a transmitter option to send annotation data with uniform send or not.• Keystroke input will be based on the UNICODE character set.

T.RES, RESERVATION APPLICATION

TR-29.3/94-01-19 (Bellcore) is Draft Rec. T.RES, Reservation application service and protocol specification.There was some disagreement about whether the interface to reservation systems could or should be standardized.However, most applauded the author’s initiative and looked forward to a refined draft for the next meeting.



T.CFAX, FACSIMILE CONFERENCING APPLICATION

TR-29.3/94-01-15 (VideoServer), Draft Rec. T.CFAX – Facsimile conferencing application, attempts to keepthe spirit and most of the content of the SG 15 H.FAX proposal while tailoring it to the MLP environment.

TR-29.3/94-01-24 (Ricoh), Comments on T.CFAX, questions the need to use facsimile as an input/outputdevice for an AGC terminal. It recommends the document profile of G4 facsimile.

Although the draft appears to succeed with duplex messaging to manage flow control for multipage facsimile,members felt that a better solution would make more use of the T.SI protocol and fit into the framework of GCC.As the current editor must attend to other business, new contributions are sought regarding an application profile forusing T.SI to distribute facsimile-encoded bit maps.

WORK PLAN

Work proceeds at the highest priority on T.GCC and T.SI, with the objectives to submit stable white contributionsfor the June 1994 meeting of SG 8 and to announce then the intention to apply Resolution 1 with a vote at theMarch 1995 meeting of SG 8.

Members are asked to distribute documents electronically for review in advance of these meetings by electronic mailto Glenn Russell, [email protected], who will post them at the anonymous FTP site, ftp.cfer.com, subdirectoryConferTech, and will announce from time to time the arrival of new files. Files will also be posted to theWorldLinx bulletin board, which has moved to a new site and may be reached at (416) 350-1398 or -1399.

TR-29.4 SECURE FACSIMILE

JITC MIL-STD-188-161B/C C ONFORMANCE TEST PROGRAM

JITC has completed testing of submitted Ricoh facsimile equipment and has nearly completed testing of submittedIlex equipment. Test reports are being finished and will be on file with JITC. The test program is available to anyfacsimile vendor who contracts to have the testing performed. Successful machines will be listed in a data base thatis accessible to Government organizations.

JITC MIL-STD-188-161D T ESTING

JITC has completed testing two Ricoh facsimile machines with the 161D protocol and expects to publish a formalreport within two months. All known problems have been corrected and successful conformance and backwardinteroperability tests have been conducted. A second vendor’s machine with 161D was not available, sointeroperability testing between two vendors’ equipment could not be performed.

As a result of the 161C conformance testing, J. Tomko (Mantech/Interop, Fort Huachuca, AZ) suggested severalareas where the standard might be tightened up. Since these areas had no negative effect on interoperability, thecommittee recommendation was not to make any changes to the standard.

MIL-STD-188-161D R ELEASE SCHEDULE

The latest draft of MIL-STD-188-161D, § 5.2.5.4, is TR-29.4/94-01-01 . G. Constantinou (DoD/DISA-JIEO/Center for Standards) is sending the completed document out to the DoD mailing list for Governmentcoordination and anticipates official release and printing by June 1994.

CHANGES TO MIL-STD-188-161C

TR-29.4/94-01-02 contains changes that G. Constantinou is planning to make to MIL-STD-188-161C. TR-29.4 has recommended that Loss of Sync, Send Common, and Receive Common either be eliminated from Table Ion page 11, or that reference to MIL-STD-188-114A be included to show that these are nonmandatory circuits.Paragraph 5.2.4, Loss of synchronization, needs also to be reworded to indicate that it is nonmandatory. G.Constantinou will try to act on this recommendation before the May TR-29.4 meeting. JITC is currently notflunking vendors’ machines in the MIL-STD-188-161C conformance testing for lack of these circuits.

STANAG 5000 LIAISON

G. Constantinou and the U.S. Delegation have submitted the MIL-STD-188-161C recommended changes to theSTANAG 5000 working group and have received questions back for comment. The plan is to submit answers to the



questions along with the recommended MIL-STD-188-161D enhancements to the STANAG group at the nextmeeting to be held in March. TR-29.4/94-01-04 is a draft amendment to STANAG 5000, Interoperability ofTactical Digital Facsimile Equipment. The amendment covers multi-page transmissions (optional capability).STANAG will likely support both MIL-STD-188-161C and MIL-STD-188-161D.

TR-29.2 PN-1906 I NQUIRY

TR-29.4/94-01-03 is a request for information from TR-29.2 PN-1906 editor, R. Lutz (Cognisys). PN-1902,Multifunction Peripheral Interface, is defining and setting standards for the higher-level protocols to be used over thedigital connection between a fax and a PC to access the fax scanner, printer copier, and facsimile capabilities.

The request asks for information regarding security, encryption and authentication on the PSTN side of the facsimile,and the associated supporting functions that may be required on the connection between the fax and the PC. The PN-1906 project members can then use this information to make sure that the higher-level protocols are designed toincorporate these functions.

Since the activities of the TR-29.4 committee to date have not involved details of the encryption or key managementprocess, no direct information is available for response. The committee did recommend that PN-1906 contact thefollowing organizations, which may be good sources from which to collect data: AT&T...STU-III (Type 1 through4) group; Motorola...STU-III (Type 1 through 4) group; NSA; NIST; commercial encryption suppliers; theSkipjack/Clipper & Capstone program office; and Study Group 8 which is doing work in the privacy area.

GOVERNMENT DESIRED FUTURE FACSIMILE CAPABILITIES

A U.S. Government study (paid) of G4 versus G3-64 operation was done. Based on the conclusions presented, G.Constantinou is encouraging the Government to adapt the Group 3-64 standard as the primary facsimile machine foroperations at 56/64 kbps. Wherever possible, in the future the Government wants to use commercial standards. G.Constantinou will investigate to see whether MIL-STD-188-161D running at 56/64 kbps would be desired by theGovernment working group in order to provide interoperability with lower-speed, 161-compatible machines. If not,interoperability between Group 3-64 machines and MIL-STD-188-161/STANAG compatible machines will not existwithout running dual protocols in the Group 3-64 machines.

G. Constantinou presented additional inputs from the Marine Corps, Navy, and Army, which will be refined anddiscussed in more detail at the next meeting. All three services had some form of asynchronous protocol on their listfor interfacing with computers and packet/X.25 networks. G. Constantinou will determine whether the committeeshould work to establish an asynchronous standard and, if so, will define the parameters of the desired networkinterfaces. The asynchronous protocol currently in use by Ricoh, Cryptek, and Ilex can be used if it meets therequirements.

DIAGNOSTIC TEST

B. Trachy (ICE Communications) is going to submit a paper to the committee proposing a ping pong type ofdiagnostic which, if adopted, could be added to the MIL-STD-188-161 standard as an option.

GOVERNMENT SPONSORED COMMERCIAL TYPE ENCRYPTION STATUS

G. Weide (Boeing/NASA) gave a status report on the Government’s voluntary but still controversial “Clipper chip”program that creates a national encryption system for which U.S. law enforcement officials will keep the keys.

Mykotronx (a manufacturer of Capstone/Clipper chips) has delivered several hundred chips to the Government forprotecting the Defense Message Switch. This includes PCMCIA cards referred to as “Tessera cards.” There iscurrently a Government RFP for 10,000 to 75,000 Tessera cards for PC file encryption, and for use on the Internet,Milnet, Autodin, etc., to protect E-mail and other data.

Several commercial PC companies have ordered chips for use in ISDN applications. An estimated 5000 Clipperchips are to be delivered to the FBI and other Government agencies. The Clipper chip is currently about $30 and theCapstone chip is slightly under $100. Larger volumes will reduce the price substantially.

Reporter’s Note: The Commerce Department announced on February 4 that the Government was going ahead withthe Clipper chip program. Export and overseas issues are still being addressed.



COMMERCIAL FACSIMILE PRIVACY PROJECT

There is no progress in this area since no one has indicated a desire to initiate a project.

Bob Robinson, Ilex Systems

TR-29 ROSTER, JANUARY 31 – FEBRUARY 4, 1994, COSTA MESA, CA

Steve Urban, Delta Information Systems Chair, TR-29Philip Bogosian, Thought Communications Chair, TR-29.1Joe Decuir, Microsoft Chair, TR-29.2Bruce DeGrasse, BJ Communications Chair, TR-29.3Bob Robinson, Ilex Systems Chair, TR-29.4Meeting host: Rockwell International

ACTION Consulting Ken Krechmer ICE Communications Bob TrachyAT&T John D. Baker Joint Int. Test Ctr (JITC) Brad ClarkAT&T Terry Lyons Lanier Worldwide Gary LucasAT&T Herman Silbiger Mantech/Interop James TomkoAT&T Microelectronics Bill Sheehan Motorola Codex Les BrownAT&T Paradyne Joe Chapman Multilink Bruce AllenAT&T Paradyne Ken Ko National Semicon. Yuval SchacharBellcore Rand Sherman Okidata Nobu SatoBJ Communications Bruce DeGrasse Pacific Data Prod Brian SinofskyBoeing /NASA George Weide PictureTel Jeff BernsteinBrooktrout David Duehren PictureTel David LindberghBT Labs John Boucher Polycom Gil PearsonBT Labs Trevor Peers Polycom Pat RomanoCirrus Logic Mike Wytyshyn Polycom Dan YagusicCognisys Raymond Lutz PTT Research (NL) G.R. BinkhorstCompression Labs George Yu Ricoh Corporation Gene GavenmanConfertech Int'l Glenn Russell Ricoh Corporation Jim HamadaniCSR Elaine Baskin Ricoh Corporation Fusakichi OkouchiData Beam Neil Starkey Rockwell Int'l Scott BibandData Race Bob Boykin Rockwell Int'l Tom GearyDialogic Bill Tiso Rockwell Int'l Glen GriffithDoD/DISA-JIEO George Constantinou Rockwell Int'l Ny NguyeDSP Group Yigal Brandman Rockwell Int'l Chris SneedDSP Group Sandra Huang Rockwell Int'l Dianne SteigerFisk Comm. Paul Masters Rockwell Int'l Stewart YangFrance Telecom CNET Jean-Pierre Blin Sanyo Fisher Tsuyoshi KuroeGammalink Steve DeLateur Sharp Yoshi NekiGammaLink H. S. Magnuski Sierra Semicon Ward PitkinGPT Video Systems Loc-Kin Yuen STF Technologies Larry NipkoHayes Dave Rife UDS Fred KillmeyerHenderson Comm. Warren Henderson VideoServer Chuck GrandgentHewlett Packard Daniel Lee VTEL Bruce KravitzHewlett Packard Andy Mutz WorldLinx Steve MaddenHuman Comm. James Rafferty WorldLinx Philip SmithHydraTech Systems John Hyland Xerox Lloyd McIntyreHydraTech Systems Harrysen Mittler Xircom Ian Seacombe



TR-30.1, MODEMS, FEBRUARY 9 – 10, 1994, PLANTATION FL[Editor’s note: Reports of TR-30.2, TR-30.3, and TR-30.4 will be in the next issue of Communications StandardsReview.]

TR-30.1 AD HOC ON V.34 START-UP

TR-30.1ah/94-02-01 (A. Clark, Hayes) proposes an addition to V.8 to indicate the type of channel. Specificexamples called out were GSTN only, Cellular access to GSTN, PBX access, and half-duplex radio access. However,it would be difficult to specify what PBX access would mean in terms that would be meaningful to a modem. Someof these concepts were incorporated in the final V.8 draft.

TR-30.1ah/94-02-02 (D. Walsh, US Robotics) proposes guidelines for making textual changes to Draft Rec.V.34. Example text for Section 11 was provided. There was some discussion about the use of the “after” asopposed to “upon”. It was also suggested to use the common term “call modem” to designate the calling modem.There was also a suggestion to replace the letter “N” with “T” for timing sequences. It was also agreed thattolerances needed to be added to all times given. The group accepted the general guidelines of this proposal.

TR-30.1ah/94-02-03 (A. Norrell, US Robotics) addresses the issue of frequency offset measurements. Itsuggests the specification of a standard estimation technique. The present text allows the manufacturer to pick anytone(s) for this measurement, which could lead to confusion. The suggested procedure was to specify a specific tone(1050 Hz) and report the offset number. The group accepted this proposal.

TR-30.1ah/94-02-04 is a proposed revision of sections 10, 11 and 12 of V.34 that had been developed in aninformal editing group, to improve the readability of the document. MP sequences Types 1 and 2 were deleted andothers were redefined.

TR-30.1, MODEMS

TR-30.1/94-02-002 is a letter liaison from TR-29 (February 1994 meeting). It requests to be informed if TR-30intends to start a project on voice data switching/multiplexing. Since TR-30 had already agreed to start such aproject, R. Brandt (Chair, TR-30) will respond to S. Urban (Chair, TR-29).

TR-30.1/94-02-004 (A. Clark, Hayes) addresses various scenarios for the Voice Data Multiplexing application(one envisions the two modems communicating in background while the voice call is in progress). It also addressesthe selection of the compression algorithm(s), suggesting consideration of V.42bis as a starting point. However,TR-30.1/94-02-004 suggests that this work be separated from the main project and that work concentrate onreaching agreement on a multiplexing scheme and a capabilities exchange mechanism. During the extensivediscussion, it was agreed that there was an urgency to this work as many modem products with voice-datacompatibility will be appearing on the market within the next year.

TR-30.1/94-02-003 , Proposed Modifications to TIA-578 for Voice-Data Conferencing (Data Race), wasintroduced briefly by the chair; there was no discussion.

TR-30.1/94-02-005 , TR-30.3’s Network Model, was distributed for information only and was not presented.

TR-30.1/94-02-006 (V. Eyuboglu, Motorola Codex) presents two alternative proposals for the presentation ofthe encoder diagrams in Draft Rec. V.34. It proposes the use of the Trott-Sarvis encoder representation. After somediscussion, the group decided to use the Wei encoder representation; the revised figure was added to Draft Rec. V.34.

The remainder of the meeting was consumed with a line-by-line review of Draft Recommendation V.34.

Dick Brandt, dB Consulting



TR-30.1 AND TR-30.1 AD HOC MEETING ROSTER, FEBRUARY 9 – 10, 1994, PLANTATION, FL

Les Brown, Motorola - Codex Chair, TR-30.1Ken Jones , Telebit Acting Chair, TR-30.1 ad hoc

AMP Jack BradburyAT&T Bill BettsAT&T Dick BrandtAT&T Rick FlanaganAT&T Krishna MurtiAT&T Larry SmithBT John BrownlieGDC Dick DrakeGDC Fred LucasHayes Alan ClarkIBM Ken KlingerIntel Zee BrunIntel Barry O'MahoneyITT-Florian Michael ChenITT-Florian Ping DongMotorola - Codex Vedat EyubogluMotorola - UDS Richard GoodsonNational Semiconductor Ophir ShablayNCS Robert FenichelNEC Graham BrandPenril Datability Zoran MladenovicPenril Datability Alexsander PurkovicPenril Datability Dick StuartPrimary Access Chris HeegardPrimary Access John RosenlofRacal Datacom Vedavalli KrishnanRay Scott Associates Paul SawyerRockwell Glenn GriffithRockwell Joe HoangRockwell (Iceland) Sverrir OlafssonTelindus Danny Van BruysselU.S. Robotics Dale Walsh

ITU-T SG 14 V.34 RAPPORTEURS MEETINGFEBRUARY 14 – 15, 1994, PLANTATION, FL

K. Kern (Chair SG 14) briefly reported on the recent meeting with T. Irmer (Director ITU-T) and W. Staudinger(Chair SG 8). This meeting had been called because the TSB had received letters of complaint relative to the IPRissues on Draft Rec. V.34. T. Irmer reported that no definitive decisions had been taken but that he was planning tobring the proposal made by R. Brandt (to include a voluntary IPR statement on all contributions) to the nextmeeting of the TSAG.

Orlando-TD-24 and Orlando-TD-32, responses to SG 8 liaisons on Draft Rec. V.34 were approved.

A revised copy of the SG 15 Technical Report (Supplement to G.726 and G.727) was distributed forcomment. This report includes new information on the performance of voice band data modems over ADPCMservices. This information supports the desirability of increasing the symbol rate from 2400 to 2800.

Plantation-TD-04 (M. McLaughlin, Cornel Electronics) proposes a modification to the rate renegotiationsequence, and replacing the present scheme with a procedure based on detection of a pre-described tone. During thediscussion it became clear that this proposal did not provide a code violation to ensure proper operation of thedecoder. If this scheme were modified to include a violation, it could no longer be detected by a simple tonedetector. As this proposal appeared to have problems and as it was late in the process to consider changes, the groupdecided to not accept the proposal.



The rest of the meeting was spent in a line-by-line edit of V.34 (Plantation-TD-03) and V.8. Although noformal meeting had been called for V.8, it was clear that considerable work had to be done on the draft text if it wereto be acceptable for approval in June. Off line editing of V.8 was accomplished to finish the V.8 draft

By the end of the meeting, all the edits had been completed; and both V.34 and V.8 are now ready for submission toSG 14 for Res. 1 procedures in June, 1994.

[Editor’s Note: Copies of completed Draft V.34 and completed Draft V.8 are available from the CSR library inboth electronic and hard copy form.]

Dick Brandt, dB Consulting

V.34 RAPPORTEURS MEETING ROSTER, FEBRUARY 14 – 15, 1994, PLANTATION, FL

Dick Stuart, Penril Datability Rapporteur

AMP Jack Bradbury IIT Ping DongAT&T Bill Betts Intel King ChengAT&T Dick Brandt Intel Weiqiang MaAT&T Rick Flanagan Motorola Les BrownAT&T Krishna Murti Motorola Vedat EyubogluAT&T Larry Smith Motorola Richard GoodsonAT&T Jim Tomcik National Semiconductor Ophia ShabtayBritish Telecom plc John Brownlie NEC Electronics Graham BrandBritish Telecom plc Richard Williams Nokia Lippo RantanenCornel (Ireland) Michael Mc Laughlin Penril Datability Zoran MladenovicCornel (Ireland) Brian O’Sullivan Penril Datability Aleksander PurkovicCray Comm. Ltd. (UK) John Magill Matsushita Graphic Mikio MizutaniDBT (Germany) Klaus Kern R. Scott Raymond ChenDBT (Germany) Ralf-Rainer Damm Racal Datacom Vedavalli KrishnanDoD Jeff Fritz Racal Datacom (UK) Chris FirthGDC Fred Lucas Rockwell Glen GriffithGDC Yuri Goldstein Rockwell Sverrir Olafsson (Iceland)GDC Dick Drake Telindus Danny Van BruysselHayes Alan Clark Telebit Ken JonesHayes Mott Easley TRT-Phillips Jean-Luc BottoIBM Gottfried Ungerboeck U.S. Robotics Andy NorrellIBM Ramin Nobakht U.S. Robotics Dale Walsh



ACRONYM DEFINITIONS

ADSI Analog Display Services Interface (Bellcore)ADSL Asymmetric Digital Subscriber LoopAGC Audiographics ConferencingAIIM Ass’n for Information and Image MgtANSI American National Standards InstituteARQ Automatic Repeat RequestATF Administrative Task ForceATM Asynchronous Transfer ModeAVC Audiovisual ConferencingBFT Binary File TransferBNTF Bi-National Task ForceBNTG Bi-National Task GroupBRA Basic Rate AccessBSC Base Station ControllerBTS Base Transceiver SystemCA Communication Application (T.611)CAMA Centralized Automatic Message AccountingCANIECE Camara Nacional de la Industria Electronica Y de Communicaciones Electricas (Mexico)CAS CPE Aleting SignalCBEMA Computing Business Equipment Manufacturers AssociationCD Committee DraftCDMA Code Division Multiple AccessCEC Canadian Electric CodeCH *Compare HDLCCMMRD Cellular Microcell/Microsystem Requirements DocumentCOPEE Council on Office Products Energy EfficiencyCPE Customer Premise EquipmentCRC Cyclic Redundancy CodeCSA Canadian Standards AssociationCSR Communications Standards ReviewCSU Customer Service UnitDCC Digital Control ChannelDCCH Digital Control ChannelDCE Data Circuit Terminating EquipmentDID Direct Inward DialingDMH Data Message HandlerDSP Digital Signal ProcessingDTE Data Terminal EquipmentECM Error Correction ModeEIA Electronic Industry AssociationEMA Electronic Messaging AssociationEMC Electromagnetic CompatibilityEPA Environmental Protection AgencyERL Echo Return LossESD Electrostatic DischargeETSI European Telecom. Standards InstituteEUT Equipment Under TestFCC Federal Communications CommissionFCS Frame Check SequenceFEC Forward Error ControlFIF File Interchange FormatFTP File Transfer ProtocolGCC Generic Conference ControlGSM Groupe Speciale MobileHDLC High Level Data Link ControlHEMP High Energy Electromatnetic PulsesI-CAN Integrated Customer Access NetworkIEC International Electrotechnical Comm.IEEE Institute of Electrical and Electronic EngrsIMA Interactive Multimedia AssociationIPR Intellectual Property RightsIS Interim StandardISDN Integrated Services Digital NetworkISO International Standards OrganizationITU International Telecommunications UnionIWF Inter-Working FunctionJITC Joint Interoperability Test CenterJTC Joint Technical CommitteeKTS Key Telephone System



LA Local Application (T.611)LATA Local Access Transport AreaMAP Mobile Application PartMAWG Message Attachment Work GroupMCS Multipoint Control Services (T.122)MFP Multifunction PeripheralMFPI Multifunction Peripheral InterfaceMIPS Million Instructions Per SecondMLP MultiLayer ProtocolMLTS Multiline Telecommunications SystemsMOU Memorandum of UnderstandingMPEG Motion Picture Experts GroupNAFTA North American Free Trade AgreementNISDN National ISDNNIST National Institute of Standards and Tech.NIUF North American ISDN Users ForumNPRM Notice of Proposed Rule Making (FCC)NSA National Security AgencyNSAP Network Service Access PointNSTAC National Security Telecommunications Advisory CommitteePBX Private Branch ExchangePCCA Portable Computer Communications Ass’nPCI Programmable Communications InterfacePCN Personal Communications NetworkPCS Personal Communication ServicesPCSC Personal Comm. Switching CenterPDU Protocol Data UnitPOTS Plain Old Telephone ServicePRA Primary Rate AccessPSDN Public Switched Data NetworkPSDS Public Switched Digital ServicePSTN Public Switched Telephone NetworkPTT Public Telephone and TelegraphQSIG Requirements specified by the ITU Q series recommendationsRAL Restricted Access LocationRF Radio FrequencyRFI Radio Frequency InterferenceRFP Request for ProposalSAP Service Access PointSAPI Service Access Point IdentifierSCC Standards Council of CanadaSDL Specification and Description LanguageSDU Service Data UnitSMS Short Message ServiceSNMP Simple Network Management ProtocolSP- Standards Proposal (TIA Balloted version)TAPAC Terminal Attachment Program Advisory CommitteeTCAP Transaction Capabilities Application PartTDD Time Division DuplexingTDMA Time Division Multiple AccessTE ISDN TerminalTTE Telecommunications Terminal EquipmentTTF Technical Task ForceUL Underwriters LaboratoriesV&V Validate and verifyVAR Value Added ResellersVPN Virtual Private NetworkWTSC World Telecommunication Standardization Conference



1994 MEETING SCHEDULES AS OF FEBRUARY 28Subject to Change without Notice

TR-41 Mar 7 - 11 Clearwater, FL JTC(Air) Aug 1 - 5 ---TR-45.1 Mar 7 - 11 St. Louis, MO TR-30 Aug 8 - 12 Baltimore, MDTR-45.3 Mar 7 - 11 St. Louis, MO TR-45.2 Aug 15 - 19 Calgary, AlbTR-45.4 Mar 7 - 11 St. Louis, MO TR-45.4 Aug 15 - 19 Calgary, AlbTR-45.2 Mar 14 - 18 San Francisco, CA TR-46 Aug 22 - 26 Irvine, CATR-45.5 Mar 14 - 18 San Frandisco, CA

TR-45.3 Aug 29-Sep 2 Toronto, OntSG 8 Q 10 Mar 21 - 25 Vienna, AustriaTR-41 Sep 12 - 16 Ottawa, OntTR-46.3 Mar 21 - 25 ---TR-45.2 Sep 12 - 16 Boston, MAJTC(Air) Mar 21 - 25 ---TR-45.5 Sep 12 - 16 Boston, MAT1A1 Mar 28-Apr 1 Boulder, COT1E1 Sep 19 - 23 Boston, MATR-45.3 Apr 4 - 8 RTP, NCTR-46.3 Sep 19 - 23 ---TR-46 Apr 4 - 8 Reston, VA

T1S1 Apr 11 - 15 Eatontown, NJ JTC(Air) Sep 19 - 23 ---TR-45.2 Apr 11 - 15 Denver, CO TR-45.3 Sep 26 - 30 Chicago, ILTR-45.5 Apr 11 - 15 San Diego, CA TR-45.4 Sep 26 - 30 Tampa, FLT1A1 Apr 18 - 22 --- T1A1 Oct 3 - 7 San Jose, CATR-30 Apr 18 - 22 Huntsville, AL TR-30 Oct 3 - 7 Portland, ORTR-29 May 2 - 5 Norcross, GA

TR-46 Oct 3 - 7 Lake Tahoe, NVTR-45.3 May 2 - 6 Kirkland, WAT1S1 Oct 10 - 14 ---TR-45.4 May 2 - 6 Toronto, OntTR-30 Oct 10 - 14 Portland, ORT1P1 May 9 - 13 Dallas, TXTR-45.2 Oct 17 - 21 Tampa, FLJTC(Air) May 9 - 13 ---TR-45.5 Oct 17 - 21 Coeur d’Alene, IDTR-45.2 May 9 - 13 Savannah, GATR-45.3 Oct 24 - 28 San Diego, CATR-45.5 May 9 - 13 Savannah, GA

SG D May 11 Washington, DC TR-29 Oct 31-Nov 3 East CoastSG 15 May 16 - 27 Geneva TR-45.4 Oct 31-Nov 4 Walnut Crk, CATR-46 May 16 - 20 RTP, NC T1P1 Oct 31-Nov 4 ---T1E1 Jun 6 - 10 Kansas City, KS JTC(Air) Oct 31-Nov 4 ---TR-45.2 Jun 6 - 10 Montreal, Que TR-46 Nov 7 - 11 Austin, TXTR-45.3 Jun 6 - 10 Montreal, Que

TR-45.2 Nov 14 - 18 San Antonio, TXSG 14 Jun 1 - 9 GenevaTR-45.3 Nov 14 - 18 Colorado Spngs, COTR-45.5 Jun 13 - 17 Victoria, BCTR-45.5 Nov 14 - 18 San Diego, CATR-46 Jun 13 - 17 Toronto, OntT1E1 Dec 5 - 9 San Antonio, TXTR-41 Jun 20 - 24 Salt Lake City, UTTR-30 Dec 5 - 9 Orlando, FLTR-46.3 Jun 20 - 24 ---TR-45.5 Dec 5 - 9 Phoenix, AZJTC(Air) Jun 20 - 24 ---

SG 8 Jun 21 - 30 Geneva TR-46.3 Dec 5 - 9 ---TR-45.4 Jun 27 - 30 Albuquerque, NM JTC(Air) Dec 5 - 9 ---T1S1 Jul 11 - 15 --- TR-41 Dec 12 - 16 Santa Fe, NMTR-45.2 Jul 11 - 15 Vancouver, BC TR-45.2 Dec 12 - 16 Lake Tahoe, NVTR-45.3 Jul 11 - 15 Vancouver, BC TR-45.3 Dec 12 - 16 ---T1A1 Jul 18 - 22 Burlington, VT TR-45.4 Dec 12 - 16 San Antonio, TXTR-45.5 Jul 18 - 22 Quebec City, QueUSNC Jul 19 Washington, DCTR-46 Jul 25 - 29 San Antonio, TXTR-29 Aug 1 - 4 Seattle, WATR-45.3 Aug 1 - 4 Calgary, AlbT1P1 Aug 1 - 5 ---

Communications Standards Review (ISSN 1064-3907) is published about 10 times per year, within days after thelatest, 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 distribution within anorganization is permitted. Subscriptions: $795.00 per year worldwide. Corporate subscriptions are available. Submit



articles for consideration to: Communications Standards Review, 757 Greer Road, Palo Alto, CA 94303-3024 U.S.A. Tel:+1-415-856-9018. Fax: +1-415-856-6591. 15902

February/March, 1994 Vol 5.2 47

Documents

communications standards review - Linda Hall Library