The following reports of recent standards meetings represent the view of the reporter and are not official, authorized minutes of the meetings.
TR-41, User Premises Telecom Requirements, March 6 – 10, 1995, San Francisco, CA.................................... 3Special Joint Meeting between TR-41.1 and ETSI Committee BTC2..................................................... 3TR-41.1 Multi-Line Telecommunications Systems.......................................................................... 4TR-41.1.1 Multi-Line Telecommunication Systems (MLTS) / Transmission........................................... 6TR-41.1.9 Multi-Line Telecommunication Systems Support of Enhanced 911 Service............................... 6TR-41.2, Conformity Assessment............................................................................................... 7TR-41.3, Telephones and Acoustic Terminals................................................................................. 9TR-41.4 Network Channel Terminating Eqiuipmnt (NCTE)................................................................ 11TR-41.5 Premises Distribution for Multimedia............................................................................... 11TR-41.6, Wireless User Premises Equipment (WUPE)....................................................................... 13TR-41.6.1, North American Wireless Customer Premises Equipment (NA/WCPE)..................................... 13TR-41.7, Safety and Environmental Considerations......................................................................... 15TR-41.7/.9 Ad Hoc Committee, Power and Lightning Surge Issues....................................................... 16TR-41.7.1 North American Telecommunication Equipment Safety....................................................... 16TR-41.7.3 Electromagnetic Compatibility Considerations................................................................ 17TR-41.8. Commercial and Residential Premises Wiring.................................................................... 17TR-41.8.1, TIA-568-A Commercial Building Telecommunications Cabling........................................... 17TR-41.8.2 EIA-570-A Residential and Light Commercial Telecommunications Cabling............................ 18TR-41.8.3 TIA-569-A Telecommunications Pathways and Spaces........................................................ 19TR-41.8.4 Outside Plant........................................................................................................... 19TR-41.9, Regulatory Considerations........................................................................................... 20TR-41 Partial Meeting Roster, March 6 – 10, 1995, San Francisco, CA................................................. 22
Sg 15 Experts Group Meeting On G.Dsvd, March 28 – 30, 1995, Geneva, Switzerland.................................... 23G.DSVD Experts Meeting Roster, March 28 – 30, 1995, Geneva, Switzerland......................................... 25
REPORT OF TR-41, USER PREMISES TELECOM REQUIREMENTSMARCH 6 – 10, 1995, SAN FRANCISCO, CA
On May 1, 1995, TIA announced that the new chair of TR-41 is Chuck Berestecky of AT&T. He takes over thechairmanship of the largest TIA committee from Vic Boersma, who recently retired. C. Berestecky was previouslychair of both TR-41.2 and TR-41.9; he has informed CSR that the new chair of TR-41.2 is P. Adornato, NorthernTelecom, and that the new chair of TR-41.9 is A. Wride, Communication Certification Laboratory. CSRcongratulates all three on their new appointments.
TR-41 RESTRUCTURING
During the TR-41.9 meeting (March 1995), C. Berestecky (AT&T) provided an overview of the discussions that aretaking place concerning the restructuring of TR-41 and its sub-committees due to the recent growth in attendance atTR-41. The tentative plan includes the formation of four supergroups under the TR-41 Chair:• TR-41.2, TR-41.7, TR-41.9 – Standards Related Matters (SRM)• TR-41.5, TR-41.8, TR-41.7 (Bonding and Grounding) – Technical Requirements-Multimedia Distribution Systems
Each supergroup would have a Vice Chair who would report to the TR-41 Chair. The supergroups would meetindependently, but the entire TR-41 committee would meet at least once a year. Another possibility being discussed isthe formation of two TR committees.
SPECIAL JOINT MEETING BETWEEN TR-41.1 AND ETSI COMMITTEE BTC2
This was the first of what is expected to be a series of meetings between TIA TR-41.1 (Multi-Line TelecommunicationSystems) and ETSI BTC2 (Sub-Technical Committee for Private Network Performance and Complex Installations) forthe purpose of working towards global harmonization of MLTS (Multi-Line Telecommunications Systems) standards.
The meeting started with five informative, background presentations:
• Overview of TIA, by R. Breden, TIA (unnumbered TR-41.1 document)• North American Standards Setting, by V. Boersma, TR-41 Chair• ETSI Standards Development Process, by J. Horrocks, BTC2 chair (TR-41.1/95-03-013)• European Approval Process, by J. Horrocks (TR-41.1/95-03-014)• Overview of Regulatory Requirements in the U.S. and Canada, by C. Berestecky, TR-41.9 Chair and P. Adornato,
TR-41.9.2 Chair (TR-41.1/95-03-012 , parts A and B)
The material in the TIA, North American Standards, and North American Regulatory presentations should be fairlyfamiliar to most CSR readers. However, some words on the ETSI presentations may be useful:
ETSI (European Telecommunications Standards Institute) was formed by CEPT in 1988. Although CEPT is anorganization of PTTs, ETSI membership includes administrations, public network operators, manufacturers, users,private service providers, and others. ETSI generates standards (ETSs), technical reports (ETRs) and technical bases forregulations (TBRs). TBRs may later become CTRs.
ETSI views standards setting on three levels: global, European, and national.
CEPT (Conference of European PTTs) has been the source of standards in the past, but it is now mainly concernedwith regulatory standards for radio and telecommunications. For the latter, ECTRA (European Commission ofTelecommunications Regulatory Authorities) oversees licensing, numbering, testing & certification, mobilecommunications, accounting principles, and interconnection issues. Directives from this Commission are orders thatmember states must implement. The commission also issues decisions, recommendations, and resolutions. These donot have to be implemented.
The new approach (initiated by CEPT in 1985) is not to generate highly detailed regulations. Details are to be includedin voluntary standards. This started with the “liberalization” of terminal equipment testing and approvals. The firstphase directive addressed the recognition of testing based on NETs (“Norme Européenne de Telecommunication”) asmutual recognition of the results of terminal conformity testing (“One stop testing, national approval”). The secondphase directive (1991) addresses mutual recognition of approvals based upon CTRs (Common Technical Regulations).
In other words, equipment receiving approval in one member country is then approved for use in other membercountries (“One stop approvals for the whole European market”).
The major push in the 1990’s is for services and infrastructure liberalization. It is expected that this will be realized in1998.
The work of ETSI is carried on in technical committees and project teams. Of specific interest to TIA TR-41 is BTC(Technical Committee on Business Telecommunications) and their sub-technical committee, BTC2, that is responsiblefor the transmission performance of private networks and complex apparatus, Synchronization, ONP (Open NetworkProvision) leased lines, and approval standards for complex apparatus.
Other technical committees of interest to TIA are ETSI TE (Terminal Equipment) and ECMA (EuropeanCommunications Manufacturers Association) TC32 (Communication, Networks, and System Interconnection,responsible for OSI and PSS1, including QSIG (requirements from the ITU Q. series recommendations). ECMAinteracts with ETSI through JEEC (Joint ETSI/ECMA Committee), and ECMA standards are voted on by ETSI and, ifnecessary, revised after ETSI comments and vote.
JOINT STANDARDS HARMONIZATION
The activities and efforts which led to this joint meeting were discussed and candidate areas for cooperation wereidentified. It was agreed that the focus should be on transmission performance. Cooperation on interface specificationswould not be practical under existing regulatory and operational environments and will not be attempted at this stage.
The meeting felt that the comparison of PBX transmission parameters in TR-41.1/95-03-011 (J. Schick, NorthernTelecom) between ETSI Standard BT-02048, “Transmission Characteristics of Digital Private Automatic Branch Ex-changes (PABXs),” and TIA-464B was a good beginning towards harmonization. This comparison should be updatedwith respect to the most recent issue of the ETSI standard.
The reference model and terminology are other areas for harmonization and alignment. Both BT-02048 and TIA-464-Bcontain PBX reference models. They are different because of the differences in connection categories between NorthAmerica and Europe. In general, the ETSI model is simpler. Near term efforts will focus on the formulation of acommon reference model and joint TIA/ETSI work to coordinate the development of a North American/European cross-reference of terminology for PBX, private networks, and transmission.
The longer-range goals identified were the formulation of common methods of testing and the development of aguideline document on transmission planning for future transatlantic private networks (once current restrictions on pri-vate international circuits are removed). This latter activity could also address future broadband (e.g., ATM) networks.
At the conclusion of the meeting, a Scope of Future Cooperation paper was generated by J. Horrocks (TR-41.1/95-03-016).
The next joint meeting is expected to be in October 1995 in conjunction with a regular BTC2 meeting at ETSIheadquarters in France.
TR-41.1 MULTI-LINE TELECOMMUNICATIONS SYSTEMS
T1E1 LIAISON
Liaison letters were exchanged between TR-41.1 and T1E1.1 regarding the deletion of “immediate dial” and “delay dial”as requirements in the T1.405 standard (Loop Reverse Battery) and transferring these requirements to an annex. Thiswould make wink start the preferred outpulsing control mechanism. TR-41.1/95-03-001 is the letter from R.Frank, TR-41.1 Chair, and TR-41.1/95-03-002 is the response from J. Smith, T1E1 Chair. For more on thisissue, see loop reverse battery supervision, below.
TR-41.1/95-03-007 is a liaison by R. Frank to T1E1.1 regarding Off Premise Station (OPS) supervision. Itprovides the text added to TIA-464-B (PBX) to cover the transmission of disconnect signals (i.e., addition of a LoopCurrent Feed Open state) between a PBX and an OPS termination. It also requests that the next issue of the T1E1standard ANSI T1.407 (OPS) include a similar addition.
TR-41.1/95-03-008 (R. Frank) is a liaison to T1E1.2 regarding digital signaling and supervision of OPS. Itprovides the digital signaling requirements (A, B bits) table that was added to TIA-464-B to cover the transmission ofdisconnect signals (i.e., addition of a Loop Current Feed Open state) between a PBX and an OPS termination over
digital network facilities. It also requests that the next issue of the T1E1 standard ANSI T1.403 (DS1 Interface)include a similar table.
UPDATE/RESTRUCTURE OF TIA-464
TR-41.1/95-03-009 is Draft 1.0 of TIA-464-B (SP-2396, Requirements for Private Branch Exchange [PBX]Switching Equipment), dated March 1995. It was distributed by J. Schick (NTI, editor) for review. This draft isintended to be the letter ballot-ready copy of the update for approval by TR-41, processing by TIA, and 60-day ANSIletter ballot.
This draft incorporates all the technical changes agreed to at the December meeting as well as non-technical commentsand corrections provided to the editor subsequent to the December meeting. This included conformance to current stylesfor fonts and for the use of symbols as provided in TR-41.1/95-03-005 (R. Frank, Siemens). All of the editingchanges are listed in an “Editorial Comment” sheet provided in TR-41.1/95-03-010 (J. Schick, Editor).
A review during the meeting identified a number of additional non-technical and editorial modifications which should bemade to the draft standard prior to distribution for letter ballot. This final editing will be done subsequent to TR-41approval of the draft.
After agreeing that the title of the standard should be changed from “Private Branch Exchange (PBX) SwitchingEquipment for Voiceband Applications” to “Requirements for Private Branch Exchange (PBX) Switching Equipment”,it was agreed to forward the draft to TR-41 for approval for letter ballot.
TR-41 subsequently approved the draft for letter ballot. However, in order for there to be even a possibility ofcompleting the letter ballot before the June 12-16 TR-41 meeting, the draft would have to be sent to TIA by March 10(the day after the meeting). It was decided to forego any final editing (as noted above) that could not be accomplishedby March 10, in favor of expediting the document to TIA for letter ballot processing.
(Note: The letter ballot was issued on March 14, and the comment period expires on June 13.)
T1E1 has proposed eliminating standards for “immediate dial” and “delay dial,” but operating companies could notguarantee that CPE would not be required to interoperate with central offices (COs) providing only immediate dial ordelay dial. It is the position of TR-41.1 that, if CPE must operate with COs providing only immediate dial or delaydial, then these methods of supervision should be covered by a T1E1 standard. The TR-41.1 Chair will write a letter tothe T1E1 Chair to that effect; meanwhile, TIA will retain the current requirements.
FUTURE ACTIVITIES
With the completion of the TIA-464-A update, the following candidates for future activities (and contributions) wereidentified in addition to the joint work with ETSI BTC2:
• More interaction with N-ISDN (Narrowband-Integrated Services Digital Network) with inputs to Bellcore on CPEneeds
• CPE interconnection to broadband networks; in particular, transmission impairments for ATM connectivity• Proposals to TIA to restructure and modernize standards titles to be in harmony with T1 standards titles and global
TR-41.1.1 MULTI-LINE TELECOMMUNICATION SYSTEMS (MLTS) / TRANSMISSION
T1A1 LIAISON
A liaison had been sent by R. Frank to T1A1.7 requesting review of the loss treatment of Enhanced 911 (E911) accesslines (TR-41.1.1/95-03-002). T1A1.7’s response, TR-41.1.1/95-03-003 , states that after reviewing thematter in light of ANSI Standard T1.508 (Network Performance-Loss Plan for Evolving Digital Networks), T1A1.7concurs in the TR-41.1 assessment that E911 access lines should receive analog access line loss treatment (from thePublic Switched Telephone Network, PSTN); however, they are not familiar with the implementation of this losstreatment in E911 switches.
ETSI L IAISON
The ETSI members present for the joint TR-41.1/BTC2 meeting also participated in this meeting. TR-41.1.1/95-03-008 , “Transmission Planning for the Liberalisation of Voice Telephony” by ETSI BTC2, TE4 and TM3, was dis-tributed for information. This paper raises the issues associated with transmission planning after liberalisation oftelephony services in 1998. It suggests three different Category of calls: Expected Quality (A), Reduced Quality (B)and Mobile Quality (C). Category A would support fax at 9600 bit/s. The ETSI members stressed the need forcontinued cooperation and liaison for international transmission planning.
LOSS CONSIDERATIONS FOR WIRELESS USER PREMISES EQUIPMENT (WUPE)
The conclusions and recommendations made at the December meeting (see CSR 6:1) were sent to TR-41.6 (WUPE)via liaison from the TR-41.1 chair (TR-41.1.1/95-03-001).
TR-41.1.1/95-03-006 (C. Sacco, Bellcore) addresses the WUPE echo/delay. A major issue is the control of far-endecho when the near-end (WUPE) adds significant delay (e.g., DECT [Digital European Cordless Telephone] or WCPE[Wireless CPE] up to 27 ms). One approach is echo cancelers looking towards the network with up to 48 ms tail-enddelay. Questions that need resolution are whether there is any degradation due to tandem echo cancelers and, therefore,whether such echo cancelers need to be switched in/out depending on connection.
TR-41.1.1/95-03-004 (S. Whitesell, AT&T) discusses aspects of transmission performance parameters,specifically, the correspondence between the IEEE Objective Loudness Rating (OLR) and the ITU Loudness Rating(LR). It was emphasized that the conversion factors, especially for receive loudness, are highly dependent on handsetgeometry. TR-41.1.1/95-03-004 is the same as TR-41.3/95-01-001 . See the TR-41.3 report for additionalinformation.
AT&T TRUE VOICE
K. Stewart (AT&T) gave a presentation on the AT&T “True Voice” enhancement. Although he did not go intospecific technical details, he did acknowledge that there has been some compatibility problems with this service (notspecified). K. Krechmer (ACTION Consulting) noted possible problems associated with data modem operation whenthe level is increased, especially over AMPS cellular networks. K. Stewart also emphasized that AT&T did try topublicize the offering before introduction and also provided a telephone number for future technical contact. TR-41.1.1stressed the need for AT&T to notify the CPE industry, via the TIA, of future modifications in network transmissioncharacteristics prior to deployment.
TR-41.1.9 MULTI-LINE TELECOMMUNICATION SYSTEMS SUPPORT OF ENHANCED 911 SERVICE
A brief background of Enhanced 911 was provided for the ETSI participants and referenced to European equivalents.(For example, in the UK, “999” is used for emergency service.)
It was noted that several smaller firms are entering the market for adjuncts to work with E911. Two such examples areillustrated in literature from “Tel-Alarm” (TR-41.1.9/95-03-001) and the “911 Emergency Locator System” (TR-41.1 .9/95-03-002 ). Both units monitor the line for 911 DTMF after going off-hook, and both provide a localalarm.
FCC NOTICE OF PROPOSED RULE MAKING (NPRM 8143) ON ENHANCED 911
TR-41.1.9/95-03-003 is a discussion outline for comments on FCC RM 8143 (Rules to Ensure Compatibilitywith Enhanced 911 Emergency Calling Systems). Using this outline, the Chair reviewed the “comments” filed by allparties that responded to the FCC Enhanced 911 NPRM. Over 100 comment responses were received from users,vendors, and service providers. Most of the responses agreed with those provided by TIA. These include limits onlocation granularity, less stringent standards for small PBX/KTS (Key Telephone System), negotiated rule making forstation number identification signaling (Caller Emergency Station Identification, CESID), phasing out of CAMA/MF(Centralized Automatic Message Accounting/Multi-tone Frequency) signaling, and inappropriateness of grade of servicerequirements. TIA also recommends splitting the rule making into “wired” and “wireless” parts.
On the other hand, public safety agency organizations (and certain jurisdictions) presented counter-positions. Forinstance, they would like to prohibit “pseudo” numbers for callback, and some urged that PBX manufacturers should bemade liable for providing all needed E911 capabilities.
The intent at this meeting was to file TIA reply comments before the extended deadline, approximately March 17. Anupdate from the FCC industry meeting during the week of March 13 will be provided to the TR-41.1.9 members.
TR-41.1.9/95-03-004 (R. Frank, Siemens) provides additional detail on some of the comments on the NPRM.
MLTS ENHANCED 911 SUPPORT (911-CAMA TRUNK STANDARD)
The Chair expects a draft of the MLTS standard for support of Enhanced 911 at the next meeting. A concern wasexpressed over the number of types of interfaces which need to be specified.
A brainstorming session will take place at the next meeting to discuss some “forward looking” network architecturepossibilities for support of Enhanced 911 by CPE. One obvious direction is an ISDN Enhanced 911 interface, andalthough TR-41.1.9 cannot write such a standard for the network, the interfaces can be proposed to T1E1. The Chairintends to generate a draft for discussion at the next meeting.
John Schick, Northern Telecom
TR-41.2, CONFORMITY ASSESSMENT
MUTUAL RECOGNITION UPDATE
TR-41.2/95-03-09 is a report of the U.S.-EU (European Union) negotiations on mutual recognition of producttesting and certification. The European Commission does not want to have individual sectorial Mutual RecognitionAgreements (MRAs). Instead, it wants a single MRA covering many sectors. While the signing of MRAs wasdelayed, progress continued in identifying the technical basis for mutual recognition product testing, qualityregistration, and product approvals in industry sectors for a complex array of regulatory elements.
Conformity assessment (CA) was also addressed in the form of accreditation systems. The use of ISO (InternationalStandards Organization), OECD, and other international testing and accreditation standards to manage MRAs werediscussed. The U.S. suggested that joint annual inspections of Accreditors be a part of the MRAs. The next round oftalks will be scheduled for the spring of 1995.
There was some activity on the MRA for non-CTR (Common Technical Requirements) equipment. However, aconsensus was not reached during the December 20, 1994, meeting of the European 113 committee. This status isgiven in TR-41.2/95-03-10 .
CCT/NAFTA (NORTH AMERICAN FREE TRADE AGREEMENT)
The CCT (Consultative Committee - Telecommunications) recommends that Canada, Mexico, and the U.S. should allminimize the scope of their mandatory standards to improve market access. Terminal Attachment (TA), Electro-magnetic Compatibility (EMC), Mobile Services (MS) equipment, and product safety (PS) requirements were discussedwith respect to conformity assessment.
It is understood that, as of January 1, 1995, Canada, Mexico, and the U.S. have procedures in place that allow for theacceptance of TA, EMC, and MS test data from each other. PS is still an issue for Mexico and the question wasraised, “Is there a process by which the SECOFI can accredit Canadian and U.S. laboratories to text Mexican PSrequirements?” No answer was provided.
TR-41.2/95-03-13 and TR-41.2/95-03-14 contain CCT Conformity Assessment Working Group (CAWG)meeting reports for the November 1994 and December 1994 meetings, respectively.
LAB ACCREDITATION/MULTISECTORIAL
S. Baldwin (Hewlett Packard) gave a U.S. Working Group presentation on Conformity Assessment (TR-41.2/95-03-02). The ACIL (Association of Independent Scientific, Engineering and Testing Firms) petitioned the FCC (TR-41.2/95-03-05 ) to include mandatory NVLAP (National Voluntary Laboratory Accreditation Program from NIST)EMC test laboratory accreditation as part of the FCC’s drive to move from personal computer and peripheral equipment(digital devices) certification to suppliers Declaration of Conformity (DOC). This move has drawn praise from the testhouses who already have NVLAP accreditation but overwhelming disapproval from both the computer andtelecommunications industries and from non-NVLAP accredited test labs who are incensed over the increasing numberof accreditations they are required to obtain. The telecommunications industry looks at FCC 95-46 on this issue as aprecedence setting NPRM.
Early replies indicate that the computer industry finds the NVLAP proposal unacceptable as it does not increasenational or global confidence in the test results. The computer industry has suggested that “the FCC should continueto accept the familiar FCC Test Site Listing process.” If the FCC finds that this is an unacceptable alternative, theFCC may press the industry to provide a more rigorous solution to the issue of lab accreditation. TR-41.2/95-03-06 is the NPRM, FCC 95-46, that proposes to amend Parts 2 and 15 of the Commission’s rules to deregulate theequipment authorization requirements for digital devices.
C. Berestecky, the Chair, and S. Crosby, the Secretary, are looking for corporations to form a Lab Accreditation WGto develop a global position for lab accreditation. The Chair suggested that the group may want to build on the IEC(International Electrotechnical Committee) policy on CA as a means to acquire results quickly.
NVCASE (NATIONAL VOLUNTARY CONFORMITY ASSESSMENT SYSTEM EVALUATION) RECOGNITIONOF ACCREDITORS
ANSI has requested that NIST (National Institute of Standards and Technology) recognize ANSI’s accreditation programfor certification programs and that NIST recognize ANSI as competent to satisfy conformity assessment requirements.ANSI details their position, particularly with respect to the EU Directives and Mexican NOMs (Mexican CertificationMarks) in TR-41.2/95-03-03 .
IEC POLICY ON CONFORMITY ASSESSMENT
TR-41.2/95-03-08 is the IEC’s Policy Group proposal on CA (PCA). It concludes that a market demand for thecontinued operation of global conformity assessment schemes in the electrotechnical sector exists but that expansion ofCA activity and CA management structure reorganization is necessary to achieve synergy and economy.
TR-41.2/95-03-12 is the ISO Policy Orientations’ agenda item 8.1 on CA suppliers declarations.
TR-41.2/95-03-17 is ISO/CASCO 261, Draft - General Criteria for Supplier’s Declaration of Conformity.
OSHA ACTIVITIES
The Chair noted that OSHA (Occupational Safety and Health Administration) indicated it will permit manufacturers totest their products under the NRTL (National Registered Test Lab) program. The NRTLs will still be responsible forevaluating the data and certifying products. This change does not require any changes to the NRTL regulations.OSHA will publish this change in the Federal Register soon.
One other change OSHA is proposing is that products approved by NRTLs be marked with a NRTL mark to becopyrighted by OSHA. Such a change will probably require formal rulemaking.
The Chair indicated that effective April 1, 1995, Canada will require specific labeling of products for EMC compliance.TR-41.2/95-03-15 (CAWG) describes these requirements. While this rule is being challenged by the Canadianindustry, it appears at best the only change will be in the effective date.
The principle issue here was the need to examine how the move can be made from multiple labels for a countrytowards a single label or mark for a country (or maybe a region). At minimum, it was agreed that a work plan needs tobe established for having a mark of a NAFTA country accepted by other NAFTA countries. A subgroup was laterformed on Marks and Labeling that will be addressing this issue.
GENERAL
The Chair requested that subgroups be formed to prepare a series of white papers on:• Lab Accreditation• Suppliers Declaration• Marks and Labeling• Third Party AccreditationTR-41.2/95-03-18 contains a list of related topics for each of the above subgroups.
TR-41.3, TELEPHONES AND ACOUSTIC TERMINALS
This joint meeting of TIA TR-41.3 and CSA T510/T515 was convened by the TR-41.3 Chair, D. Rittenhouse (Univ.of Waterloo).
LIAISON REPORTS
IEEE
J. Bareham (Consultant) reported that the IEEE Subcommittee on Telephone Instrument Testing was continuing itsrewrite of the IEEE-1027 magnetic field measurement standard. They hope to ballot it following their next meeting.They are also continuing work on a handsfree telephone measurement standard and expect to have a draft to share withTR-41.3 by the September meeting. It will include multiple test signals and guidance on how to choose which one touse. The subcommittee intends to have its next meeting co-located with the TR-41 June meetings.
T1E1
T1E1.1 subcommittee Chair, G. Tennyson, will reply to the liaison letter on the 40 volt minimum battery supply fol-lowing the T1E1.1 meeting to be held the week of February 27 to March 3, 1995. A draft copy of that reply isprovided in TR-41.3/95-03-013 . It responds to the question of whether off-hook current would be affected bychanging to a 40 volt minimum battery supply by indicating that T1.401 presently allows a minimum loop current of18 mA during AC power failure. T1E1.1 has no plans to modify the V-I curves. Since TR-41.3 has previouslyinformed T1E1.1 that it considers operation of terminal equipment on 20 mA of current as mandatory and operation on18 mA as desirable, TR-41.3 will draft a letter that reiterates this position and asks whether the network’s ability toprovide a minimum of 20 mA of current into a 430 customer installation (400 for the terminal equipment plus 30for the inside wiring and any series devices) during normal operation (i.e., not during an AC power failure) would beaffected by the 40 volt minimum battery proposal.
ANSI S3 .48
J. Bareham (Consultant) indicated that the ANSI S3.48 committee was interested in reviewing ITU-T RecommendationP.37 (Magnetic Field Stremgth Around the Earcap of Telephone Handsets which Provide for Coupling to HearingAids) and that he would send them Draft 3 of PN-3399 (Requirements for Handset Telephones Intended for Use by theHard of Hearing). Since J. Bareham generally attends the S3.48 meetings and sometimes attends ours, he agreed totake on the liaison role but indicated some of it may have to be done by correspondence.
ITU
The next meeting of ITU-T SG 12 will be held in Geneva during September 1995. The second week of the meetingwill conflict with the TR-41 meetings.
V. Boersma had announced his retirement from Northern Telecom, and he will be stepping down as Chair of TR-41.His guidance and sense of humor will be greatly missed. His proposal to restructure TR-41 into supergroups will beput on hold so that whoever succeeds him as chair can have a significant say in how it is done.
WUPE TRANSMISSION PARAMETERS
S. Whitesell (Vice Chair, AT&T) prepared a draft contribution (TR-41.3/95-01-001) to TR-41.6 entitled,Recommendations Concerning Transmission Performance Parameters. This tutorial paper provides backgroundinformation on the transmission parameters and their values being considered by TR-41.6 for WUPE (Wireless UserPremise Equipment). Transmission parameters reviewed are: frequency response, loudness rating, Sidetone, terminalcoupling loss, distortion, noise, acoustic shock and ambient noise rejection. However, R. Britt (Northern Telecom)suggested adding a caution to Appendix A (Nominal Frequency Response Characteristics and Loudness Rating Calcula-tions) indicating that the results shown therein were for the nominal frequency response curves provided and that theconversion factors for specific products may differ depending on their individual characteristics. R. Britt agreed to draftthe text for this note.
S. Wellspring (CSA) took detailed notes for CSA of the resolution of each comment in TR-41.3/95-03-010 andTR-41.3/95-03-011 . Five action items were assigned as a result of this review. Because technical changes weremade to the T-510 document, it must undergo a second round of balloting. This also raised a question on how TIAshould proceed with the balloting of PN-2892 (Revision of EIA-470-A, Telephone Instrument with Loop Signaling forVoiceband Applications). The text of PN-2892 as approved by TR-41 for letter ballot was intended for use in bothT510 and the revision of EIA-470-A. If the text is now changed in T510 and if the approved version of T510 is to beused in the balloting of the 470-A revision, does it need to come back to TR-41 for approval first? S. Whitesell (ViceChair) will discuss this with the TIA secretariat.
PN-3399, CRITERIA FOR TELEPHONE COMPATIBILITY WITH HEARING AIDS
TR-41.3/95-03-009 is the third draft of PN-3399 for revising TIA/EIA 504 and CSA T515. It incorporatescomments from the last meeting and uses a reference sound pressure from the receiver of -14 dBPa (80 dBSPL). It wasagreed that the 600 termination should be deleted in Figure 2. The words “magnetic field intensity frequency response”will be changed to “magnetic field intensity vs. frequency” wherever they occur in the document. It was also agreedthat only the more stringent frequency response template will be included and that all references to two allowed levelsdepending on frequency response shape will be eliminated. S. Whitesell will provide wording that grandfathers the U-type receiver. Finally, Section 4.4 (magnetic field intensity frequency response) needs to be clarified to indicate that itonly applies to the axial field.
ADDITIONAL HIGHLIGHTS
D. Dulmage (Certelecom Labs) reported that he had been able to reduce his system noise level and improve the S/N(Signal to Noise) ratio for the magnetic field measurements. R. Magnuson (Siemens Rolm) also reported being ableto carry out the proposed measurements successfully. In light of this, it was agreed that PN-3399 could proceed withusing a sound pressure reference of 80 dBSPL to harmonize with ITU-T Recommendation P.37. However, it wassuggested that the group may want to include a requirement in the document to make a noise floor measurement.
The following contributions were provided by Northern Telecom for information. Time did not allow for theirdiscussion during this meeting. R. Britt (Northern Telecom) will review the documents to see if any of them need tobe considered during the June meeting.• TR-41.3/95-03-002 (G. Boudreau, Northern Telecom) proposes a draft text for Section 8, Speech Coding and
Telephony, of the PCI standard for the unlicensed PCS (Personal Communications Services) band. It proposes theuse of G.721 for the speech coder and contains the same draft Appendix A as was provided in TR-41.3/95-01-001 .
• TR-41.3/95-03-003 is the third draft of DE/TE 04093 (ETSI), Telephony for the hearing impaired; Electricalcoupling of telephone sets to hearing aids, dated January 1995.
• TR-41.3/95-03-004 (G. Hellstrom, G. Hellstrom Data, Stockholm, Sweden) contains scope statements,definitions, user requirements, and discussion of text telephony standardization in PSTN, ISDN GSM and UMTS(future Universal Mobile Telephone Service).
• TR-41.3/95-03-005 (G. Hellstrom) is a paper from ETSI TS TE STC TE4 containing background andpreliminary conclusions for text telephony. It also includes the first draft of Human Factors (HF), Text telephonyfacilities, User requirements, dated January 1995.
• TR-41.3/95-03-006 (G. Hellstrom) contains Version 0.1 of Audiovisual Services, Text telephone equipmentworking in the PSTN, dated January 1995.
Technical editor’s note: Documents 004, 005 and 006 above address issues related to V.18 (Operational andinterworking requirements for modems operating in the text telephony mode) and therefore will be of interest to TR-30.1.• TR-41.3/95-03-007 (ETSI TC TE STC TE4) is a liaison statement to ETSI STC HF2 regarding symbol
allocation for availability of functions in a telephone.• TR-41.3/95-03-008 (ETSI TC TE STC TE4) is a liaison statement to ETSI STC HF2 regarding connector
type for electrical connection from a telephone to a hearing aid. The paper notes that such a connector might offer atemporary solution to the TDMA interference problem by allowing the telephone to be a distance away from thehearing aid.
• TR-41.5 agreed to NT/BNR’s recommendation to follow the basic TIA-570 structure for all residential distributionschemes (including coax).
• AT&T’s inputs on a possible premises architecture is fully consistent with the TR-41.5 Entrance Unit concept.
• TR-41.5 liaison established with joint EIA/NCTA on broadband consumer electronics/cable TV wiring relatedmatters through G. Hanover (EIA)
• Two new TR-41.5 Working Groups were formed:– TR-41.5.1 Residential Premises Telecom Systems Protocol– TR-41.5.2 Uninterrupted Powering for Residential Premises Telecom Networks
DAVIC’S PREMISES DISTRIBUTION REQUIREMENTS
The joint NT/BNR and Stentor contribution (TR-41.5/95-03-003) on interpreting DAVIC’s multimedia servicesdemands on premises distribution and how both the narrowband and broadband services could be accommodated in aTIA-570 based distribution structure, was well received and accepted. Currently EIA-570 only supports twisted pairwhile DAVIC interface options include coax and fiber. To ensure convergence of key standards activities, TR-41.5acknowledged the recommendation to collaborate closely with both DAVIC and IEEE 802.14 by assigning N. Smith(Stentor) as the DAVIC liaison and S. Godo as the IEEE 802.14 liaison. The homework assignment to T. Toher(IBM) to provide similar inputs from the ATM-Forum is pending.
ISSUES WITH FUTURE PREMISES ARCHITECTURE
TR-41.5/95-03-004 , Possible Multimedia Residential Premises Architecture (AT&T), proposes the EIA CEBusprotocol for device to device communication using a home controller. CE-Bus allows up to two coax cables and oneUTP Category 3 cable to each telecommunications outlet. Alternately, a single coax could carry the upstream traffic,while downstream traffic could be carried over Category 3 UTP. This paper is an excellent tutorial on the home of thefuture network architecture .
The AT&T premises distribution architecture makes the case for a Home Network Controller (i.e., Node ‘0’ or Class 7switch) equivalent to the Entrance Unit concept of TR-41.5 to suppport existing and future network services frommultiple providers
In summary, the contribution and the subsequent discussion raised the following key premises wiring concerns andactions:
• Support needed for disabled people• Emphasis in standards that avoid making existing customer equipment obsolete• Re-use of existing wiring to the extent possible• Applicability of CEBus (EIA IS-60) to existing wiring• Migration plan from existing wiring to full configuration for MM services• Education of consumers on the lower cost open architecture solutions• Lack of CPE-CPE cooperation/ interoperability on premises today• Interworking between Network and Home Automation protocols is needed• Migration path from analog to future all-digital premises network• Provisions to protect personal information, security and consumer privacy assurance• Consumer physical interconnection complexities to access provider of choice• Avoid consumer confusion from transport schemes deployed to the premises by access provider (e.g., 64 QAM, 16
VSB, QPSK, ADSL)• Enhancements to/evolution of current network signaling multimedia services• Need for Network Interface Units to assure proper/standard termination of access provider’s network to support
legacy and future CPE, and for maintenance/diagnostic tests independent of the premises• Lifeline powering during commercial power failure• Access to secure/tamperproof electric utility telemetry interface unit• Support of low-cost wireline operation from the home for wireless terminals• Need for communication protocol between existing multimedia services/ access devices (e.g., using DTMF, ADSI
or terminal emulation), and enhanced services (e.g., abstract access device with minimal I/O capabilities)
EIA/NCTA/FCC MULTIMEDIA WIRING RELATIONSHIPS
G. Hanover (EIA) informed about the following related premises distribution activities:• EIA is working with SCTE (Society of Cable Television Engineers) in developing specifications for splitters.• Two subcommittees on standards between TV components (i.e., VCRs, set-tops, TV receiver) and the network, are
being created by the joint EIA/NCTA(National Cable Television Association) Advisory Group named Cable-Consumer Electronics Compatibility Advisory Group (C3AG). The FCC directed the executives from bothindustries to form C3AG:1. Interface between digital TV and digital VCR (based on existing IEEE-P1394 (time multiplexed bus) and IEEE-
P1395/Europe standards on variable high speed systems and a general proposal submitted by CSF Thompsonon high speed digital audio/ video bus). Its focus is to accommodate room type equipment clusters.
2. Analog audio/video bus is an off-shoot of the CEBus structure (this work is almost finished)• The above activities are behind the schedule agreed to with the FCC, mainly due to disagreements between the
Cable and Consumer representatives on protocol and business related issues. No new date has been set yet. TheFCC is soon set to release an NPRM on Open Set-Top interfaces, with expected high impact on consumerelectronics as well as premises distribution designs. G. Hanover will be acting as the liaison between theseactivities and TR-41.5.
NEW WORKING GROUPS
Based on a proposal by the TR-41.5 chairman (TR-41.5/95-03-002), the following two working groups were formed.Their proposed scope and mission statements are:
TR-41.5 .1 Res ident ia l Premises Telecom Systems Common ProtocolMISSION: To promulgate enduring cross-industry standards for multimedia residential telecom services.SCOPE: TR-41.5.1 will investigate application and operating system communication among internal residential
telecom systems and external service providers. These systems may include, but are not limited to: audio, voice,data, video, and multimedia applications. They encompass industry segments such as telecom, computer, DBS,CATV, and Home Automation. TR-41.5.1 will recommend protocol(s) that will accommodate the identifiedrequirements.
M. Jones (Elcom) agreed to chair the group. Elcom Industries, a Philadelphia based company, is pursuing a premisesdistribution method using the AC wiring. G. Hanover (EIA) is vice-chairman/secretary.
TR-41.5.1 started to define the different “channels” that will be used for transport of multimedia in premisesenvironments. These channels include:• Category 5 UTP• 75 ohm Coax• 62.5/125 micron fiber• AC wiring
TR-41.5.2 Uninterrupted Powering for Residential Premises Telecom NetworksMISSION: To make recommendations to TR-41.5.1SCOPE: TR-41.5.2 will investigate requirements and develop powering recommendations for continuity of operation
for residential equipment and services. These systems may include, but are not limited to: audio, voice, data, video,and multimedia applications. These encompass industry segments such as telecom, computer, DBS, CATV, andHome Automation. TR-41.5.2 will recommend powering parameters and protocols that will allow users to set ap-propriate levels of equipment and service availability.
J. Romlein (MIS Labs) agreed to be a temporary chair of the WG2 activity.
Severin Godo, Northern Telecom/BNR
TR-41.6, W IRELESS USER PREMISES EQUIPMENT (WUPE)
In TR-41.6, work is active on PACS (a variation on the Japanese Personal Handy Phone) led by Panasonic, OCDMA(Orthogonal Code Division Multiple Access, a variation of CDMA) led by Stanford Telecom, and a variation of DECTfor North America which has the broadest range of supporters.
TR-41.6/95-03-264 is the TIA Project Request and Authorization form for the OCDMA WUPE InteroperabilityStandard. The scope, liaison, and schedule were updated from a previous submittal. There was some discussion aboutwhether or not this document implies the inclusion of ETSI source documentation. The OCDMA sponsors intend tocreate the OCDMA ANSI standard. Ability to include ETSI copyright material is subject to approval by TIA.
TR-41.6/95-03-265 is a Project Initiation Notification System (PINS) Form for the same project. It will bepassed on to TR-41 for project approval and assignment of project number.
TR-41.6/95-03-266 (P. Weismantel, NEC America) provides WUPE definitions for Interworking, for thesupporting Interworking Functions (IWF), and for the relationship to Interoperability and Services. This definition isbased on Recommendation I.500.
TR-41.6/94-12-241 is a liaison letter from WINForum offering the services of WINTest on Spectrum Etiquette V&Vfor any proposed standard.
There were no new contributions on Conformance Test Requirements and V&V. The Chair recommended that eachproject chair provide an overview of the V&V process in the May meeting.
TR-41.6/95-03-263 (J. Hoffmeyer, NTIA/ITS) presents a summary of requirements from the anticipated federalusers of commercially-based wireless products and services. These requirements include both licensed and unlicensedproducts and services; services would include leased or subscribed services such as cellular, personal communicationservices (PCS), mobile satellite, and enhanced special mobile radio. It also discusses products such as wireless localarea networks (WLAN), wireless PBXs, and personal digital assistants (PDAs). Further contributions are expected onthe issue of wireless PBXs.
TR-41.6/95-03-262 (R. Dean and D. Dudich, NSA, and A. Levesque, GTE) describes Synchronous Data Servicesthat will support wireless interoperability with government-standard secure telephones (STU-IIIs) as well as provide auniversal transport mechanism that will support other applications based upon end-to-end protocols. It providesrecommendations for both the Air Interface and for added functionality within the Mobile Switching Center.
TR-41.6.1, NORTH AMERICAN WIRELESS CUSTOMER PREMISES EQUIPMENT (NA/WCPE)
The project with the largest attendance in TR-41.6 is PN-3400, the WUPE work based on DECT (ETSI 300 175).TR-41.6.1 documents may be found on the WWW, ftp://ftp.ti.org/pub/tr41.
TR-41.6.1/95-02-11B is the February 7, 1995 draft from AT&T of the WCPE Interoperability Standard. ETSI andTIA are coordinating their work to minimize functional differences. While the WUPE physical layer is different (re-flecting the different frequency allocations), the MAC and DLC layers are practically the same; identities and codes aresupported by a common ETSI-maintained database, and authentication and encryption (cipher) are also supported bycommon algorithms.
TR-41.6.1/95-03-037 (G. Norgett, Symbionics) is an overview of the Digital European CordlessTelecommunications (DECT) Type approval process in the European Community. While this is not a regulatoryrequirement in the U.S., it is of considerable interworking interest that everyone follow the same test script as if itwere regulated. CTR6 (Common Technical Regulation Physical layer) and possibly CTR10 (Speech) will beincorporated into Part 10 of PN-3400 (WCPE Interoperability Standard) by Symbionics, with review by NTI andAT&T. Type Approval of CTR6 and CTR10 is now operational in Europe. The new TBR22 (Technical Basis forRegulation Protocol, a TBR precedes CTR) is under discussion in TR-41.6.1 with regard to its applicability to NorthAmerica. TR-41.6.1/95-01-028 from ETSI consists of tables extracted from the maintenance lists for ETSI 300175 TBR6 and TBR8. The change requests which have the status accepted will be incorporated into the second editionof ETSI 300 175 TBR6 or TBR10.
TR-41.6.1/95-03-038 (G.J. Wimpenny, Symbionics) proposes a new method for measuring modulation accuracy.It suggests that a new modulation metric, Differential Vector Error Magnitude (DVEM), is more appropriate for usewith systems employing non-coherent demodulators.
V&V FOR PN-3400
TR-41.6.1/95-01-021 (T. Sterkel, AT&T) provides the common structure and procedures for preparing review,V&V, and balloting drafts. It was decided that the document should be more explicit regarding page numbering andthat a Table of Contents style was needed. T. Sterkel (AT&T) will add the Table of Contents style guide. AMicrosoft Word for Windows 2.0 template (Part “0”) was created and provided in soft copy to all Editors andFacilitators and other interested members.
TR-41.6.1/95-01-022 (T. Sterkel, AT&T) proposes a V&V work plan for PN-3400. It was revised during themeeting, and soft copies were distributed. In addition, an Excel 4.0 spreadsheet was developed as a format for the V&Vdiscrepancy reports. T. Sterkel (AT&T) was asked to update the plan to explicitly include the new Special TopicGroups (STGs).
OVERVIEW (WCPE 1)
The Overview, Part 1 (TR-41.6.1/95-03-01.2) was reviewed and changes were made. A revision C will be needed forV&V.
PHYSICAL LAYER (WCPE 2)
TR-41.6.1/95-03-02.2 is the current version of Part 2, Physical Layer. Updates to revision C are needed for V&V.
TR-41.6.1/95-03-036 (G.J. Wimpenny, Symbionics) provides a list of comments on release B of the WCPEphysical layer specification, TR-41.6.1/95-01-002B. Revisions will be incorporated into revision C.
TR-41.6.1/95-01-025 (Ericsson) suggests a new normative Annex defining an extended preamble (supported in thetransmitter) which allows the receiver to select one of several antennas to utilize for the next transmission.
MAC LAYER (WCPE 3)
Part 3, MAC Layer (TR-41.6.1/95-003-003 Rev2) was reviewed. Changes were made mostly due to the need forincorporating the new CRFP (Cordless Radio Fixed Part, e.g., base station) in Part 12.
LINK LAYER (WCPE 4)
Part 4, Link Layer (TR-41.6.1/95-03-04.2) was reviewed and changes were made regarding ETSI maintenance.
NETWORK LAYER (WCPE 5)
Part 5, Network Layer (TR-41.6.1/95-03-05.2) was reviewed. Various changes were made to ensure inclusion ofCPAP/DSAP (Customer Premises Access Profile/Data Services Access Profile) WCPE profiles and to add Latin-2 andU.S. code pages. In addition, most figures need to be redrawn.
Speech Coding, Part 8 (TR-41.6.1/95-03-08.2) was reviewed. Several small explanations and changes were made.
ACCESS PROFILE (WCPE 9A)
TR-41.6.1/95-01-029 (ETSI) is Version 2.00 of Radio Equipment and Systems (RES) DECT Data ServicesProfiles, Profile Overview, dated January 1995. Six principal service types are envisioned:1. Low speed frame relay, throughput up to 24 kbit/s2. High performance frame relay, throughput up to 552 kbit/s3. LAP-based non-transparent connections (overlay on 1 and 2 above)4. Transparent and isochronous service5. Short message transfer or paging6. Teleservices (e.g., fax) application profile (overlay on 1, 2, or 3 above)
TR-41.6.1/95-03-039 (N. King, Siemens Rolm) provides a decision tree for use in working through a decision onthe indefinite duration DTMF feature in CPAP. The issue is whether or not to support various existing CPE deviceswhich require in-band DTMF signaling. The problem is complicated by the possibility in the PSTN network ofadditional voice coders. There was a discussion about indefinite DTMF, but no changes were made other thanclarifying notes to the tables.
Part 9A, Access Profile (TR-41.6.1/95-03-09.2) was reviewed. Changes were made in accordance with the jointETSI/TIA Joint Experts Meeting (JEM) on GAP (Generic Access Profile)/CPAP. TR-41.6.1/95-01-024 (R.Sagers, Motorola) contains the results of the CPAP JEM held on January 11, 1995. There was also discussion onchanges made in the latest GAP.
Administrative Agreements, Part 11 (TR-41.6.1/95-03-11.2) was reviewed. The issues of Identities, Addressing, andSecurity were discussed. It was decided that the best approach is to have ETSI acknowledge WCPE as a “DECT-derivative” at the Technical Assembly in March. It was also decided to incorporate an informative annex in Part 1showing the differences between WCPE and DECT. The group agreed that the information in Part 11 is a livingdocument that is informative and thus is not appropriately ballotable. The most likely vehicle may be the TechnicalBulletin (TB). This will be addressed further.
TR-41.7, SAFETY AND ENVIRONMENTAL CONSIDERATIONS
ESD REQUIREMENTS
TR-41.7/94-12-22 contains the basis of changes to the ESD (Electrostatic Discharge) section of ANSI/TIA/EIA-571. It will be reformatted and expanded to include all of section 4.2.7 and the informative appendix containing thestatistical methodology being proposed in some bodies. This will be done by C. Tenorio (AT&T), D. Smith (AT&T),and G. Wong (Northern Telecom). E. Eckert (Northern Telecom) will provide a soft copy of ANSI/TIA/EIA 571.That will complete the ESD proposal except for examples of failure modes for different types of CPE which will becontained in an informative annex.
IEC-TC-74
USAG (United States Advisory Group) is showing some interest in the inter-connection of cable television. Intel hasproposed a program to determine what problems, if any, exist in this application.
T1E1.5
The liaison to T1E1.5 that was agreed to be written by the Chair and E. Eckert (Northern Telecom) at the last meetingwas delayed at the plenary so that a coordinated TR-41 liaison could be written. E. Eckert and the Chair were not ableto complete the assignment before this meeting.
The default T1 ballot on the Electrical Protection for Network Operator-Type Equipment Positions closed on January6, 1995. There were zero No votes, and all comments were resolved. It will be published. The Protection ofTelecommunications Links from Physical Stress ballot still has some unresolved comments. The comments areexpected to be resolved at the June meeting.
A review of the Central Office ESD document has begun. The first proposal, TR 41.7/95-03-02 (J. Brunssen,Bellcore) was provided for information. It proposes revisions to T1.308-1990 (Central Office Equipment - ESDRequirements) to include the “contact” method of system-level ESD immunity testing and to reference IEC 801-2,Second Edition, 1991-04 for the test methodology. There was no discussion. The next T1E1 meeting will be theweek before this group’s next meeting.
IEEE-1100
There have been no contributions from the IEEE 1100 (Emerald Book on powering and grounding sensitive electronicequipment) group. It was intended to cover computer equipment but has been used by some adminstrations to defineinstallation of telecommunications equipment. Since it was never intended to cover such equipment, it does a poorjob. IEEE 1100 will reissue the Emerald Book with telecommunications equipment included plus a new chapterspecifically for telecommunications equipment. It is understood that all the telecommunication requirements will be inChapter 10. When contributions are available, they will be brought to this subcommittee. W. Bush (independent con-sultant) has been requested to be the TIA TR-41 liaison to IEEE 1100.
SP-3210, I MMUNITY STANDARD
Draft 8 is going out as SP-3210-A for ballot this week. During the Working Group meeting, editorial changes werereviewed. There were two visitors from the FCC. They asked for input of ways to promote the document and getindustry support for it. During the subcommittee meeting, a motion was approved to add an agenda item to the JuneTR-41.7.3 meeting to discuss petitioning the FCC to adopt SP 3210.
TR-41.7/.9 AD HOC COMMITTEE, POWER AND LIGHTNING SURGE ISSUES
POWER SURGE ISSUES
Equipment failure due to power surges between the power input and the telecommunication network, an FCC concern,was discussed at length. The group concluded that the present surge tests in Part 68 would not detect these problems.An additional power surge test was proposed for Part 68 that would stress this interface and ensure that the equipmenthad sufficient isolation between the tip and ring and the power line. Changes to Part 68 will be addressed in TR-41.9at a later meeting. C. Berestecky (AT&T) will submit a contribution on this subject that will be sent to bothcommittees to be considered for inclusion into ANSI/TIA/EIA-571 and submitted to the FCC for inclusion into Part68. The group also recommended that the power line surge in Part 68 be changed to the same surge specified in IEEEand IEC standards.
This ad hoc group will no longer meet. Its job is finished. Continuing work will be done in TR-41.7 and TR-41.9.
TR-41.7.1 NORTH AMERICAN TELECOMMUNICATION EQUIPMENT SAFETY
Final approval of R. Ivans (UL) as the Working Group Chair is expected by the June meeting.
BI-NATIONAL TASK GROUP
The Bi-National Task Group (BNTG) has almost completed its work developing a U.S./Canada safety standard based onIEC 950 for the computer and telephony industry (Information Technology). There will be a final review meeting onMay 10 after which the Third Edition of UL-1950 and CSA 950 are expected to be released. UL-1459 will be activeuntil the year 2000 and equipment grandfathered until the year 2005.
UL provided TR 41.7.1/95-03-03 , containing the pertinent information from the impact statements written byseveral WG members. TR 41.7 .1/95-03-03 describes the changes manufactures will be required to make toproducts which presently meet UL-1459 in order for them to meet the new Bi-National Standard, UL-1950 3rd edition.UL-1950 3rd edition is termed UL 2950 in this document. These changes were reviewed in detail, and severalhomework assignments were made that should allow this work to be completed at the June meeting. Some of thechanges included adding a separate section for Restricted Access Location (RAL) with more information, having thetesting section reviewed, removing the “no impact” sections, and adding details where needed.
There was a brief report on the several proposals presented and discussed at the last meeting. It was expected that theoutcome of these proposals at the WG 7 and WG 8 meetings will be provided at the June meeting since both will havemet before the June meeting.
The Third Amendment of IEC-950 has been published.
CONSULTATIVE COMMITTEE ON TELECOMMUNICATIONS (CCT)
TR 41.7.1/95-03-04 will be available at the next meeting. It reports on the deviations to IEC 950 that the MexicanOfficials proposed in the February meeting. These would result in requirements close to those in the present U.S. andCanadian Standards.
UL
UL has had requests from several companies to evaluate multi-media equipment located on the side of the house,connected to the CATV coax and feeding the home with twisted pair and drop coax. The equipment provides a telecominterface derived from the CATV coax. UL will be providing an Interim Standard for this purpose to satisfy these shortterm industry requests. There may be an industry group in the future involved with this. UL is looking for people tosubmit contributions for requirements and for a longer term Standard.
An IAC (Industry Advisory Committee) for UL-1459 will be activated, possibly in the third quarter to consider theeffect of UL-1950 Third Edition and other issues. Those involved in UL-1459 IAC in the past can continue toparticipate. Those interested should contact UL in Santa Clara, CA.
TR-41.7.3 E LECTROMAGNETIC COMPATIBILITY CONSIDERATIONS
SP-3210, RADIO FREQUENCY IMMUNITY REQUIREMENTS FOR (TELEPHONE TERMINAL) EQUIPMENTHAVING AN ACOUSTIC OUTPUT
The first ballot closed during the last TIA meeting. The changes agreed to at the last meeting were incorporated intodraft 8, TR-41.7.3/95-03-03 . It was given a final review at this meeting and will be sent out for default ballotsoon. There were no changes recommended by the WG. It was later learned that the default ballot of SP-3210-A willclose June 13, the day before the next meeting. There were no issues brought before the WG which would preventapproval of the default ballot at the next meeting.
The FCC continues with their position of not adopting SP-3210 into their Rules and giving the Standard a chance toprove its worth as a voluntary standard. Previously the FCC had given some indication that they would support SP-3210 inclusion. There was a request from the WG to the FCC for help in promotion activities for the Standard whenapproved.
LeRoy Baker, Reliance Comm/Tec
TR-41.8. COMMERCIAL AND RESIDENTIAL PREMISES WIRING
Editor’s note: Committee document numbers are not available in all cases. Where needed for clarity, CSR hasindicated its own document numbers.
TR-41.8.1, TIA-568-A C OMMERCIAL BUILDING TELECOMMUNICATIONS CABLING
The status of the default ballot (SP-2840A) containing errata items was discussed. It is expected that TIA-568-Ashould be published soon after this default ballot is completed, sometime in the June-July 1995 time-frame.
The task group on PN-2948 (Additional Connector Specifications for Unshielded Twisted Pair [UTP] Cable Networksfor Unshielded Twisted Pair Cables: Non-Destructive Performance Characteristics) reported progress in the developmentof patch cord qualification procedures (proposed changes are attached to TR-41.8.1/95-03-A). Good correlationwith the de-embedding procedure and direct measurement of crosstalk was confirmed in two independent laboratories.
The PN-3398 (Open Office Cabling) task group presented draft 8. The group reached a consensus to send thisdocument out for a TSB letter ballot. The document was reorganized to include only the cabling portion and all of the
supporting infrastructure material was moved to an informative annex. Draft 9, dated March 7, will be submitted toTIA for a TSB letter ballot.
The fiber optic task group, working on centralized optical fiber cabling, presented the document reformatted as a TSB.Siemon Company was opposed to the architecture because it conflicted with TIA-568-A. Northern Telecom wanted torecommend that an interconnect be used instead of a splice in the telecommunications closet. Most members did notsupport these changes. The document was not approved for procedural reasons at the TR-41 plenary to be sent out fora TIA TSB letter ballot (TR-41.8.1/95-03-P).
The task group working on Screened Twisted Pair (ScTP) cabling is close to sending out their draft in a committeeletter ballot, as a TSB. The major outstanding issue is the method to quantify shielding effectiveness for connectinghardware to cable interfaces. As part of this task group, IBM and Thomas & Betts made a presentation on the physicalaspects of the proposed alternate connector for ScTP (TR-41.8.1/95-03-B). Samples of the mated plug andreceptacle were passed around.
AMP Inc. showed that the existing modular connector specified in TIA-568-A could be improved by modifying theplug (TR-41.8.1/95-03-C). The modified plug had Terminated Open Circuit (TOC) values ranging from 50 dB to56 dB at 100 MHz. With the improved modular plug, the mated plug and jack connection, when measured at 100MHz, indicated NEXT as high as 55 dB. The point was made that the existing physical interface for the 8-positionmodular connector can still be used to obtain better transmission performance.
TR-41.8.1/95-03-I (CommScope) presents Longitudinal Conversion Loss (LCL) data measured with the same testmethod used by AT&T, except that the cable was coiled in spools rather than stretched out in aerial spans or onconcrete floors. Twelve samples of category 5 plenum cable and 12 samples of category 5 non-plenum cable each hada worst case LCL around 35 dB with an average around 45 dB. The applicability of LCL at high frequencies is beingreviewed; other methods of characterizing balance are under investigation in various TIA task groups.
The task group on PN-3287 (Link Performance Transmission Specification for Field Testing of UTP CablingSystems, TSB-67) met to resolve outstanding technical comments and review Draft 10 of PN-3287. The problem ofcertain far end connectors influencing NEXT for short links is under investigation jointly by the PN-3287 and PN-2948 connecting hardware task groups. This issue was brought up at BICSI (Building Industry Consulting ServicesInternational), where concern had been raised about the possibility of having cable and connectors which separately“meet” TIA-568 standards but when attached together do not. The document now specifies that the accuracy level oftest instruments must be verifiable by a third party. The document also requires that several sanity checks beperformed on a routine basis and that NEXT be verified from both ends of the cabling under test. The document wasapproved to be sent out for a second TSB letter ballot. An interim meeting was scheduled for May 22-23 to reviewballot responses. It is very likely that the document will be approved for publication in June 1995.
Masood Shariff, AT&T
TR-41.8.2 EIA-570-A R ESIDENTIAL AND LIGHT COMMERCIAL TELECOMMUNICATIONSCABLING
The meeting was chaired by R. Provost (RJP Consulting). TR-41.8.2 is in the process of laying out the wiringrequirements for different applications and generating a minimum set. In order to accomplish this, they plan to nego-tiate and take over wiring sections from other standards. As such, TR-41.8.2 has reached an agreement with the EIAgroup responsible for CE-Bus to take over the wiring section and incorporate these into the revision of TIA-570.
Current work included:• Page-by-page review of TIA-570 (Res. Wiring Standard)• Update TIA-570 with architecture based on three grades of service
Technical editor’s note: AT&T distributed in advance of the June meeting TR-41.8 .2 /95-06-CSR-1 which is aninitial draft of EIA-570-A.
S. Godo (NT/BNR) expressed the following premises broadband wiring concerns to be addressed in the residentialwiring standard:
• Separate, multiple in-home wiring architectures (CATV, Telco, Home Automation) have distribution topologydifferences that does not meet the single plant installation favored by consumers. This makes it difficult for theconsumer to use existing wiring (e.g., coax) for his/her telecommunications services, regardless of service provider.
• Coax distribution ownership issues (e.g., consumer adds, moves, alters installations at own will, creatingmaintenance problems)
• Lack of coax drop demarcation (i.e., the drop today includes premises distribution)
• Sharing vs. full use of coax distribution by service provider (e.g., maintenance issues)
• Inferior quality of consumer installed additions
• Multi-dwelling issues–Interconnection and access to home-drops–Need for parallel in-building telco cabling–Lack of common telco/CATV equipment rooms–Conduit space limitations in existing buildings–Surface mounting cabling and distribution equipment issues
• Many coax premises installations will not meet current telco broadband requirements–Near 1 GHz of bandwidth needed–Inability to carry some digital services
As a result of the above input and the discussions that followed, homework was assigned on the following subjects:• Grades-of-service division• Demarcation• Premises distribution (spaces, backbone, topology, etc.)• Media• Light Commercial (topology, media, etc.)• White paper - marketing strategy (el. contractors, building contractors, architects, etc.)
Severin Godo, Northern Telecom/BNR
TR-41.8.3 TIA-569-A T ELECOMMUNICATIONS PATHWAYS AND SPACES
TR-41.8.3 reviewed TR-41.8.3/95-03-CSR-1 , Draft 2 of the Testing Methods document for Coupling ofElectrical Disturbances from Power Lines to Data Lines in Close Proximity. This document explains test proceduresto those companies planning on collecting data. Part of the document, or all of it, may be included in the nextrevision of TIA-569, as an Annex.
The PN-3398 work on open office cabling was reviewed. The group reached a consensus to include the relevantsections from this document into chapter 6 of the TIA-569-A revision. Hence, the open office concept andspecifications are now incorporated into TIA-569-A, instead of being published as a TSB.
A contribution (TR-41.8.3-03/95-CSR-2) on terminology from Nelson Firestop on Annex A regardingFirestopping specifications was reviewed and accepted. TR-41.8.3-03/95-CSR-3 from D. Ballast (BICSI), tostandardize on equipment rack sizes based on EIA 310D (supports all common rack sizes) with M6 (metric) hardware,was distributed; discussion was postponed until the next meeting.
Masood Shariff, AT&T
TR-41.8.4 O UTSIDE PLANT
The meeting was chaired by D. Ballast, University of Texas. The group has started organizing the contents and layoutof a target standard. AT&T suggested that the contents follow the typical organization of material in any outside planthandbook for ease of reference and correlation. IBM distributed its outside plant handbook to about 20 members of thisgroup. AT&T will need to follow suit and make available its Outside Plant Engineering Handbook(ref. #900-200-318available from AT&T, 1-800-432-6600, $146.00). As a first cut, the working group agreed to skim through bothdocuments and pull out “standards level” statements and specifications and incorporate these into a strawman documentfor the next meeting.
The current work item is to develop a standard for customer owned outside plant facilities for premises in campusenvironment based on the REA standard.
A review was made of the Table of Contents of the REA standard, and the following Table-of-Contents was agreed asthe basis for the TR-41.8.4 draft standard:
1. Planning2. Transmission Design3. Aerial Plant4. Buried Plant5. Underground Plant6. Building Plant7. Conduit8. Electrical Protection9. Terminals and Interfaces10. Closures11. Cable and Splicing12. Clearances and Separation13. Cable Pressurization14. Switchroom Design15. Switchroom Environment16. Fiber Optic Design17. Microwave Design18. Network Design with Twisted Pair Media19. Coaxial System Design20. Testing21. Safety and Quality Assurance22. Symbols23. Drawings and Records24. Permits and Right-of-Way
Detailed inputs on this draft standard are expected to be presented, starting at the next meeting.
Severin Godo, Northern Telecom
TR-41.9, REGULATORY CONSIDERATIONS
LIAISON REPORT
H. Mar (Industry Canada) reported on TAPAC (Terminal Attachment Program Advisory Committee), TTF (TechnicalTask Force), and ATF (Administrative Task Force). TAPAC met on February 21, 1995. The major discussionsincluded the following:• The progress and schedule for the adoption of the harmonized CS-03• The disclosure and network change process• Hearing Aid Compatibility (HAC) and Personal Communication Service (PCS) issues
FCC/IC ACTIONS
The FCC has released an NPRM relating to Part 15 Class B devices that looks at manufacturer certification byapproved labs (see TR-41.2 report above for additional details).
The Canadian Interference Causing Equipment Standard (CICES) has been revised to require labeling on devices as ofApril 1, 1995.
TR-41.9/95-03-06 is an FCC Public Notice regarding gold equivalency for Part 68 connectors. Berg Electronicshas submitted test reports on its non-gold 30 micro-inch GTX plating system. These reports demonstrate meeting thetest requirements of TSB-31 and therefore the gold equivalency requirements of Section 68.500 of Part 68.
FCC/IC REQUESTS
B. von Alven (FCC) had inquired about the registration of HDSL/ADSL (High-rate Digital SubscriberLoop/Asymmetric Digital Subscriber Loop) equipment. TR-41.9 agreed that there were no rules applicable to thisequipment. The consensus of the group was that this is an administrative issue and should be referred to the FCC AdHoc Administrative Committee.
TR-41.9/95-03-02 is incoming correspondence from J. Bipes (Mobile Engineering) responding to a request from B.von Alven for an opinion on whether or not the Part 68 Loop Simulators are adequately defined. The opinion givenwas that it is adequate as is and that no action is required.
TR-41.9/95-03-04 is a response letter to B. von Alven, FCC, resulting from last meetings regarding thelongitudinally balanced DC feed issue. It recommends no changes to the figures in Subpart A and no changes tospecify use of balanced feed inductors in Subpart D, Part 68.
PART 68 HARMONIZED PETITION/CS-03 S TATUS
CanadaH. Mar (Industry Canada) reported that a letter ballot is planned for April with comments returned in June. Upon theresolution of the comments, the proposal will be published in the Gazette with adoption by the end of the year.
United StatesR. Provost (RGP Consulting) and C. Berestecky (AT&T) reported on the progress of the document. The document isready for filing with minor editorial corrections. These will be done after the filing so as not to prolong getting thedocument to the FCC.
TR-41.9/95.03.07 is Parts I, II, and VII of CS-03, Harmonized Requirements for Terminal Equipment, TerminalSystems, and Certified Protection Circuitry, dated February 7, 1995.
TR-41.9/95-03-15 is Draft 3 of Part IV, Glossary of Terms, of CS-03, dated January 11, 1995.
TR-41.9/95-03-10 contains a table that provides a cross reference between CS-03 Part VII, Part 68, and TSB-31 forLDM (Limited Distance Modems, the CS-03 term equivalent to LADC, Local Area Data Channels) and substraterequirements.
TRILATERAL/CCT
C. Berestecky (AT&T) reported that the CCT (Consultative Committee - Telecommunications) met in Mexico City.The Terminal Attachment Working Group (TAWG) has received a firm commitment from the Mexican delegation toprovide input on their rules for technical damage to the network as required by NAFTA in Section 13. The TAWG hasagreed to discuss the termination point (demarcation point) at the next meeting.
TR-41.9/95-03-08 is the November meeting report for the CCT TAWG. This report notes differences betweenmandatory requirements (NOMs) of Mexico and mandatory (Part 68 and CS-03) requirements of the USA and Canada:• NOMs exist for specific products (telephone, PBX, modem) rather than as interface specifications• NOMs include performance requirements.A specific NOM (standard telephone set) will be analyzed to technically compare it to the U.S. and Canadian mandatoryand voluntary requirements. The Mexican delegation stated that Mexico could convert to NOMs for terminalattachment based on interface standards.
EU MRA
C. Berestecky (AT&T) reported that no meeting had been scheduled since the last TR-41 meeting. However, the U.S.and Canadian delegations plan to meet to discuss issues of mutual concern. (See also TR-41.2 report, above.)
ENERGY EFFICIENCY
There has been no change in the Energy Efficiency initiative involving telecommunications. It appears that thisactivity may be curtailed due to budget cuts by the government.
E-911 PETITION UPDATE
TIA has filed in the E-911 docket. There is little involvement with the Part 68 rules. It appears that the majority ofthe work will be in other parts of the rules.
BELL TAP/CROSSTALK
A. Daughtry (Bellcore) presented a tutorial on the Bell Tap and crosstalk problems (TR-41.9/95-03-16). Thepresentation describes Automatic Line Insulation Tests (ALIT) used by telcos to identify future line problems. Thesetests are responsible for many cases of “pinging telephones”. AT&T 5ESS ALIT cards operate at ±100VDC.Northern Telecom DMS 100 Line test Unit uses -48VDC and Multiple Test Unit uses ±50VDC. EIA-470-A specifies
that telephones should not respond to voltages from 0 to 202VDC. AT&T is bringing out a new ALIT card thatoperates at 50VDC and 25 ms rise time. It may also be desirable to lower the DC threshold to 100VDC in EIA 470A.TR-41.9 discussed the need for revisions to Part 68 to alleviate these problems. However such revisions move towardequipment testing.
COMPONENT REGISTRATION
G. Slingerland (Mitel) reviewed his proposal for component registration (TR-41.9/95-03-13). Componentregistration lends itself to a product consisting of generic PC host computer, multi circuit PSTN interface card andcontrolling software produced by different companies. There were no comments on the technical content; this proposalwill be finalized at the Ad Hoc Administrative WG meeting.
TR-41.9 WORK ON REVISIONS TO TSB-31-A
The work program for the revisions of TSB-31-A, Part 68 Rationale and Measurement Guide, has been formed. Eachteam will be responsible for reviewing their assigned sections and drafting updates. The teams were charged to try tocomplete work on each section by the next meeting.
Team 1, Sections 5, 6, and 7: J. Christiano (Inchcape Labs) and D. Moon (General DataComm)Team 2, Sections 8 and 9 C, D, and E: J. Bipes (Mobile Engrg.), S. Crosby (AT&T), and A. Daughtry (Bellcore)Team 3, Sections 10, 11, and 14: D. Hays (AT&T), D. Dulmage (Certelecom), and E. Guevara (Stentor)Team 4, Section 13 F and other digital sections: P. Adornato (Northern Telecom), A. Wride (CCL), and B. Corey(Industry Canada)
TR-41.9/95-03-05 (D. Moon, General DataComm) is a summary of the changes required in TSB-31-A to reflectthe Harmonized requirements for Leakage and Hazardous Voltage.
Work on Sections 1, 2, 3, 4, A, B, 12, 15, G, and H has been postponed to a later date.
G. Slingerland (Mitel) has accepted the role of editor for the revision.
TR-41.9/95-03-09 contains Section 9, Transverse Balance Limitations, of TSB-31-A. TR-41.9/95-03-11contains a table that determines the appropriate action for corresponding sections of the existing TSB-31-A documentin order to reflect the requirements of the harmonized Part 68 standard as they pertain to 1.544 Mbps digital interfaces.TR-41.9/95-03-12 (D. Hays AT&T) describes the changes required in section 10 (on hook impedance) of TSB-31-A.
TR-41 PARTIAL MEETING ROSTER, MARCH 6 – 10, 1995, SAN FRANCISCO, CA
REPORT OF THE SG 15 EXPERTS GROUP MEETING ON G.DSVDMARCH 28 – 30, 1995, GENEVA, SWITZERLAND
This was the first meeting of this Experts group which was established at the ITU-T Study Group 15 meeting inFebruary 1995. The purpose of this group is to address the need for a new speech coder for digital simultaneous voiceand data (DSVD) applications in Study Group 14. The work is being handled under Q12/15.
TERMS OF REFERENCE
DSVD-95-02 is the Terms of Reference for the work, including requirements for the coder and schedule of activities.The original key requirements were :
Speech quality in error free conditions Not worse than G.726 at 32 kbit/sOne way coder/decoder algorithmic delay ≤20 msGross bit rate 13 kbit/sComplexity approx. 10 MIPS
≤ 2k words RAM≤ 8k words ROM
The target is to have the coder selected and the draft Recommendation ready for determination by SG 15 at the meetingin November 1995.
DSVD-95-03 is a liaison from the Q1/14 V.savd Rapporteur from their meeting in Oxford, UK, March 1995. Theyhad reviewed the Terms of Reference and concluded that a lower bit rate would be required for some applications. Theliaison requests the lowest possible bit rate, and indicates that the maximum acceptable would be in the range of 11 to12 kbit/s.
DSVD-95-06 (Rockwell) provides additional information on acceptable speech bit rates, considering the framingoverhead.
These issues were reviewed; the Terms of Reference were amended to specify the gross bit rate as a maximum of 11.2kbit/s.
DSVD-95-04 (AT&T, Intel) suggests that the group extend the work to include the definition of an interoperablefloating point version of the coder, particularly for host CPU implementation. It was proposed that this work wouldbe done after the completion of the fixed point specification. This proposal was agreed
The Terms of Reference suggest that, because of the time constraints, the group first consider extensions to existingor imminent ITU-T coders. DSVD-95-05 (AT&T) proposes a way of defining what is meant by an “extension”based on the attributes of the G.723, G.728, and G.729 coders. This contribution stimulated considerable discussion,and widely varying views were expressed. Some felt that this definition of an extension was too relaxed, but noagreement was reached. It was noted during the second session, that full information is not yet available for theproposed G.729 coder, which limits the opportunity for experts not involved with this work to propose an extension oradaptation of this particular technology.
TEST PLAN
There was some discussion on the test plan at the first session although there were no contributions. Delegates wereleft to ponder the issue further before the second session. At that time DSVD-95-16 (Rockwell) was introduced. Itproposes that, in view of the similar time constraints, the test plan be based on that for the speech coder for the VeryLow Bit Rate Video Telephone (LBC). Further it was proposed that there would be no qualification test phase. Thiswas agreed, although further work is still required to generate suitable amendments to the LBC test plan.
ALGORITHMIC COMPLEXITY
There was a short discussion on algorithmic complexity which included a review of part of DSVD-95-11 (Universityof Sherbrooke). DSVD-95-11 proposes the same measurement method as was used on the half-rate GSM coder.This was rejected as being too demanding on time and effort, and this difficult subject was left open.
CANDIDATE ALGORITHMS
The following is a summary of the coders for which high level descriptions were presented.
Two rates 11.2 kbit/s & 8.0 kbit/s - CELP - 15 ms frame size.
University ofSherbrooke:DSVD-95-11
Coder based on the G.729 8 kbit/s coder - dual rate 9.6 kbit/s & 13kbit/s.
DSP Group &AudioCodes Ltd:DSVD-95-17
Based on the G.723 coder - dual rate 8.0 kbit/s & 11.0 kbit/s - 10ms frame size.
In view of the recently agreed change to the Terms of Reference, it was agreed that the cut-off date for submission ofhigh level descriptions for candidate algorithms would be 14 April 1995. While there had been no agreement on thedefinition of an extension to an existing coder, it was also agreed that new proposals which went outside the definitionof an extension given in DSVD-95-05 would not be accepted.
(Author’s Note : Since the meeting, two further proposals have been received, both before the 14 April cut-off. Thefirst , from IBM, proposes a modified version of the RPE-LTP coder used on GSM networks, which has very lowcomplexity. The second, from Specom Technologies, is an 8.5 kbit/s CELP-based coder.)
LIAISONS
A liaison statement to Study Group 14 was generated (DSVD-95-15) which informs them of the progress to date.As it was expected that the decision process would be difficult to say the least, it was considered useful to ask SG 14for their views on the relative importance of some of the factors which may be used in the decision process, e.g., bitrate, complexity, quality, etc. This question was also included in the liaison statement, together with a request formore information on applications for the DSVD system.
WORK PROGRAM
The schedule for this work is very aggressive and much work is still to be done. The Chair (J. Magill, ProbeCommunications, UK) expressed that it would be necessary to consider in detail the decision-making process inadvance of the availability of test results. Also, further consideration is required on the test plan, the definition ofalgorithmic complexity, etc.
To help progress the work by correspondence, Rockwell has established an e-mail reflector. The address of the reflectoris “[email protected]”, and applications to join the reflector should be sent to “[email protected]”.
Additionally there is still a need to find test labs for the evaluation of candidates, and this may prove to be a significantproblem.
The next meeting of the G. DSVD Experts group is June 13 - 17, 1995 in Montreal, Canada, in conjunction withother meetings of ITU-T SG 15 speech coding Rapporteur Groups and the SG 12 Speech Quality Experts Group(SQEG).
John Magill, Probe Communications, UK Chair of Expert Group
Apple Computers, USA Katherine WangAT&T, USA Mike BuckleyAT&T, USA Richard CoxAT&T, USA Dror NahumiAVC Technology , USA Bob WooDeutsche Thomson - Brandt, Germany Imre VargaDSP Group, Israel Yair Be’eryFrance Telecom / CNET Claude LamblinFrance Telecom / CNET, Jean-Pierre PetitIntegrated Info. Tech., USA Paul VaisIntel Corporation, USA Thomas R. GardosKNK Consulting, USA Kristine KneibMotorola, USA Cheung AuyeungNTT, Japan Takehiro MoriyaNat’l Semiconductor, USA X ‘Shawn’ RanPhilips, France Estelle SonnicRockwell, USA Tom GearyRockwell, USA Albert HsuehRockwell, USA Jim JohnstonSamsung Adv. Inst. of Tech., Korea Nam Kyu HaSamsung Electronics Co Ltd, Korea Jaebum HongSamsung Electronics Co Ltd, Korea Young Jin KimSiemens, Germany Istvan SebestyenSpecom Technologies, USA Yuhai MaoWintec Corp, USA Peter H Hsieh
Communications Standards Reviewregularly covers the following committee meetings:
REPORT OF THE VERY LOW BITRATE VISUAL TELEPHONY RAPPORTEUR’SMEETING (Q2/15), MARCH 27 – 30, 1995, GENEVA, SWITZERLAND
The primary purpose of this meeting was to edit the five draft Recommendations that were determined at the FebruarySG 15 meeting:• H.324-System• H.263-Video• G.723-Speech• H.245-Control• H.223-MultiplexThe resultant draft Recommendations are electronically available at the following FTP site:ftp://ftp.std.com/vendors/picturetel/h324.
LBC-95-117 is a status report for Recommendations under the responsibility of SG 15.
The Rapporteur, R. Schaphorst, presented a report that was submitted to SG 15 summarizing the work of the LBCExperts Group (LBC-95-100). It addresses H.32P (Multimedia Telecommunications Terminal Operating over theGSTN), AV.25Y (Speech Coder for Multimedia Telecommunications Transmitting at 5.3/6.3 kbit/s), H.26P (VideoCoding at Rates Less Than 64 kbit/s), H.24P (Control of Communications Between Multimedia Terminals), H.22P(Multiplexing Protocol for Low Bit Rate Multimedia Terminals), Extension of H.32P to Mobile Radio, andrequirements.
LBC-95-130 (Rapporteur), regarding Intellectual Property Rights for the H.324 Recommendations, includes patentinformation and a list of patents from 45 companies previously received for H.262 and H.220 (of the H.320Recommendations).
The Rapporteur requested that all organizations who have participated in the development of these Recommendationssubmit information on IPR whether in process patent or final patent. The Rapporteur will gather the patent informa-tion, pass it on to the ITU, and report on the status of the collection. It is important that this information be receivedno later than May 29, 1995, so it can be presented at the June LBC Experts meeting in Boston.
VIDEO CODER: H.263
LBC-95-090 (K. Rijkse, KPN Research) contains the report on video. Draft Recommendation H.263, LBC-95-083 (K. Rijkse, KPN Research), was reviewed and editorial changes were made. The table for chroma motion vectorsin Annex F (Advanced Prediction mode) was slightly adapted. An end-of-sequence code was introduced in H.263 afterwhich non-valid bits must be ignored until a new picture start code is detected. This code can be used in case of database access. It was agreed that the bit stream verification should be continued. LBC-95-098 (NSC) summarizes thestatus of TMN5 bitstream exchange.
CODING ALGORITHM TMN5
PB-Frames
Several companies reported the same results on PB-frames as did Telenor Research (LBC-95-122 and LBC-95-124 ). LBC-95-134 (M. Frater, Univ. of New South Wales) concludes that implementation of PB-frames can beused to gain a considerable improvement in the objective quality for certain types of sequences and that theimprovement tended to be greater at low bit rates. LBC-95-136 (NSC) reports on a comparison between H.263 withPB-frames and H.263 with interpolation at the decoder only. For sequences with moderate motion, the results wereequally good. However, the delta vectors technique that significantly improves the PB-frames technique had not yetbeen included. It is expected that, especially for sequences with more motion, the PB-frames technique will besuperior. It was decided to keep the PB-frames option (Annex G) in H.263.
The performance of PB-frames at very low frame rates was investigated for the sequences Miss American andMother&Daughter (LBC-95-124). However, the delta vector technique had not yet been included in this experiment.It seems that PB-frames without delta vectors should not be used below about 6.25 Hz even for simple sequences.However, the delta vector technique improved the performance of PB-frames at lower frame rates.
The restrictions on backward prediction inside the macroblock were removed. Per macroblock, all coefficients for thesix P-blocks will be transmitted first and then all coefficients for the six B-blocks. Only one delta vector for B-blockswill be used per macroblock, even when four vectors per macroblock are present.
It was mentioned that a buffer regulation using frame skipping does not work well with PB-frames because the numberof bits for the B-frames significantly increases when the frame rate drops. However, another company reportedrelatively good results when using a slightly adapted version of the TMN5 buffer regulation. Furthermore, it wasmentioned that a comparison of H.263 with and without PB-frames should be performed with accompanying audio. Itwas mentioned that mainly the higher frame rate is noticed, and not higher delay.
LBC-95-123 (Telenor) is a proposal for changes to PB-frame coding.
Other Issues
• It is up to the encoder to insert GOB headers or not;• The table for DBQUANT, indicating the more coarse quantization of B-pictures compared to P-pictures, was
modified by choosing values for DBQUANT from a smaller and more useful range.
LBC-95-135 (X. Ran, NSC) provides a comparison between H.263 using Annex D, E, and F and H.261 with CIFsize pictures at 12.5 frames per second at a bitrate of 116 kbit/s. A gain for H.263 was found of about 3 dB comparedto H.261. Similar results (gains of 2 to 3 dB) were reported verbally for lower rates.
Further Study
It was proposed to continue the Video Ad Hoc committee. Further study will be done on three issues:• The changes in Annex G require some changes to be made in Annex E of H.263 (Syntax-based Arithmetic Coding).• The PB-frames technique will be compared for two situations: 1) backward prediction only taken from current P-
macroblock and 2) backward prediction taken from the decoded part of the complete P-picture.• The need for intra B-blocks in the case of intra P-blocks. This influences the Variable Length Codeword (VLC)
table for Macroblock mode for B-blocks (MODB).
SPEECH CODER (G.723)
LBC-95-093 (R.V. Cox, AT&T) contains the report on speech coding. A report on capability to pass DTMFsignals is provided in LBC-95-148 (R.V. Cox, AT&T). The results of AT&T’s testing show that the coder iscapable of passing DTMF signals under certain conditions. Of primary importance is that the duration of the tonesmust be long enough, preferably 90 ms or greater in length. Many autodialers generate tones of approximately 50 msin length, and these will not pass reliably. The coder is also sensitive to “twist,” which means that one frequency’samplitude is higher than the other. The higher rate coder is generally more capable of passing DTMF signals.
Draft Recommendation G.723, LBC-95-085 (R.V. Cox, AT&T), was extensively reviewed. Many editingcorrections were made. The majority of the editing corrections were made in order to bring the text into alignmentwith the C code. This was possible, in part, because about 40 organizations have received the bit-exact fixed-point Ccode. The group agreed that further editing should continue via correspondence. Much of the activity will focus onstrengthening the links between the text and the C code. Specifically, the following two actions will be taken:
• A glossary of symbols and variables will be added to the end of the text document. It will contain the mathematicalsymbols used in the text, the names of the corresponding variables in the C code, a brief description of what thevariables are, and the fixed-point representation of the variable.
• Cross references between the C code and the text will be inserted. At the end of each section in the text, a referencewill be given to the C functions that implement this part of the coder. In the C code, comments will be inserted toindicate which section of the text is being implemented by each of the functions.
It was agreed that the high rate coder will run at 6.3 kbit/s rather than 6.4 kbit/s. This can be accomplished by moreefficient packing of some of the excitation bits. The additional 3 bits will be available for signaling as needed. Twobits are available for signaling at the 5.3 kbit/s rate. The final version of the draft with these changes will be ready forthe June meeting.
VOICE ACTIVITY DETECTION AND DISCONTINUOUS TRANSMISSION
Traditionally, the ITU does not specify voice activity detectors (VAD). Rather, it specifies how well VAD must work.It was not the intention of the group to change this policy. No VAD will be specified. The proponents have experi-mented with discontinuous transmission. LBC-95-150 (FT/CNET/ACL/USH/DSPG) provides an overview ofdiscontinuous transmission (DTX) control and operation for the LBC G.723 speech coder. The most pressing need isfor a means to generate satisfactory comfort noise. The experiments of France Telecom indicate that for some non-stationary background noises, particularly babble, it is sufficient to update the LPC (Linear Predictive Coding) infor-mation on a frame-by-frame basis. Using the complete 24 bits/frame LPC quantizer and 4 bits of gain information,
satisfactory subjective performance was found. The speech group realized that transmitting 4 bytes of informationevery 30 ms is inefficient when the overhead of the MUX is 3 bytes. The MUX group indicated that the MUXprotocol could manage such a method. Both the speech group and the MUX group are interested in finding a moreefficient method. One possibility is to combine several frames into one transmission packet. Other, more efficientmethods will also be investigated. The speech group promised to prepare a proposal for the MUX group and informthem by May 31. The speech group also agreed to use the first 2 bits of each frame for signaling the nature of theframe (i.e., the bit rate and whether it is a comfort noise will be provided in an Annex to the Recommendation).
INTELLECTUAL PROPERTY CONCERNS
It was pointed out that when the draft recommendation is sent to the ITU for distribution prior to the ballot, theproponents should include the C code because it is an integral part of the Recommendation (see section 1.5). Theprocedure for distribution of the C code will be further investigated.
DIGITAL TEST SEQUENCES
At the present time, the C code is distributed with a limited amount of speech material and the corresponding singleencoding bit stream and decoder values. The group agreed that it is necessary to provide a larger set of test sequences sothat implementers will be able to test more fully both the C code and their implementations. It will still be necessaryfor implementers to produce much more processed files of their own for comparison between their implementation andthe C code in order to detect any errors. Assistance is needed from within the speech group to produce these additionalsequences.
AVAILABILITY OF REAL-TIME IMPLEMENTATIONS FOR AUDIO/VISUAL TESTING
The proponents currently had available real-time implementations of the coder which could be loaned out for combinedaudio-visual testing. However, the group expressed the need for caution in such testing, since many other variablessuch as the type of microphone and the listening device (loudspeaker, headphones, or handset) can and will effect theresults of this test.
OTHER ISSUES
Some members of the group expressed the need for an interoperable floating point specification for the coder. This isneeded for host CPU implementations of H.324. The speech group invites organizations that have attempted to makeinteroperable floating point simulations to submit contributions.
The group discussed the special requirements for the speech coder imposed by mobile telephony. The speech coder fora mobile videophone will require channel coding to protect the bitstream from random bit errors. The coder containsprovisions for frame erasure concealment. It is requested that an organization perform bit error sensitivity studies ofG.723. Channel models are available from the Mobile group and can be used to formulate a channel coder.
MULTIPLEX: H.223
LBC-95-094 (V. Eyuboglu, Motorola) contains the report on multiplex. The Multiplex Ad Hoc committeereviewed draft Recommendation H.223 provided in LBC-95-084 (V. Eyuboglu, Editor). The Editor presented indetail the changes made to the draft since the SG 15 meeting in February. A few further editorial corrections were madeduring the presentation.
There was a proposal to remove the sequence number that is currently included in MUX-PDUs (Protocol Data Units).The purpose of this sequence number is to (optionally) support multilink operation. It was noted that multilink op-eration is a very desirable feature, but a number of system issues related to its operation were still open. M. Whybray(British Telecom) indicated that BT will try to work out these issues before the June LBC meeting. LBC-95-125from BT suggests that MUX_PDU Sequence Number should not just be indicated by H.24P but also at the H.223layer. Therefore, it was decided not to delete the sequence number at this time.
The group reviewed Annex A of the draft, where the syntax for multiplex tables are described. The general sentimentof the group was that it was desirable to reduce the complexity of the mandated MUX table syntax. It was agreed thatreceivers that support three or less logical channels should not be required to receive custom tables. The editors of theMultiplex and System recommendations were asked to develop a complete proposal for complexity reduction withinthe next few weeks for review by the MUX and System group experts. There was also a proposal to use ASN.1 forthe MUX table syntax. The decision on this proposal was left to the discretion of the editors of the Multiplex andSystem recommendations.
The Multiplex group held a joint meeting with the Voice group to discuss the impact of Discontinuous Transmission(DTX) on the multiplexer. A DTX scheme proposed in LBC-95-150 uses 5 octet 30 ms frames to “encode” silence.MUX experts indicated a preference for a DTX scheme that uses silence frames that are of the same length as speechframes, but are transmitted less frequently. The voice experts from FT/CNET agreed to do further experiments todetermine the feasibility of such an approach and make the results available to the Multiplex group experts before theend of May. The MUX experts indicated that they could support shorter silence frames should this become necessary.
The Multiplex group also held a joint session with the Video group to review the parts of H.223 that affect videotransmission. It was decided to mandate a 7-bit sequence number in AL-PDUs and make the use of 15-bit sequencenumbers an option. A proposal was made to allow transmitters to refuse to retransmit a frame based on thesignificance of video information in that frame. No agreement could be reached on this proposal, however, since thiswould have made retransmission entirely optional.
The editor of the Multiplex recommendation will prepare a revised draft Recommendation H.223 based upon LBC-95-084 and the decisions reached at this meeting. This will be made available on the LBC FTP site within two weeks.
MUX REFLECTOR
B. Welsh, Chair of the Control Ad-Hoc group, kindly agreed to merge the MUX reflector (currently “owned” by R.Brainard, AT&T Consultant) with the reflector used by the Control group. R. Brainard will announce the change onthe current MUX reflector. Everyone on the current MUX reflector will automatically be transferred. After the change,all e-mail related to MUX or control should be sent to the following address of the control reflector:[email protected]. Anyone who wants to join the MUX/Control reflector should contact B. Welsh.
COMMUNICATION CONTROL: H.245
LBC-95-097 (B. Welsh, British Telecom) contains the report on Communication Control H.246. LBC-95-126 isa proposal for harmonizing H.246 with the corresponding Recommendation for ATM Multimedia, H.245, as requestedby SG 15.
LBC-95-086 (B. Welsh, Chair and Editor) is a revision of the H.246 document that was determined by SG 15. Itincludes material that was omitted from that document as well as some editorial changes. Several suggestions weremade on ways to improve the presentation of the material as well as some technical corrections. It was proposed that alist of these technical points be produced and distributed to the Ad-Hoc group for checking before further editorialchanges are made. This list was provided in LBC-95-127 (B. Welsh, Editor) A particularly important point wasraised by K. Tewani (AT&T), who suggested that we should use a special value of the Format Indicator used withinXID frames. K. Tewani will forward information on which Format Indicator (FI) values have previously been allocatedin order that the group may select a new value. He will also inform the group of the name of the Rapporteur ofISO/IEC JTC1/SC6/WG1, to whom the request for a new FI value must be sent.
LBC-95-131 (F. Lecanu, LEP/Philips) is a proposal for widescreen support including a message within H.245 forsignaling an option of using a 16:9 aspect ratio for the display. Although this stimulated some discussion within thegroup, the Chair decided to postpone the discussion of this proposal to the System Session.
M. Nilsson (BT) presented LBC-95-126 which contains information relevant to the proposed harmonization ofH.245 and H.246. LBC-95-128 is the initial draft of the harmonized document. It is proposed within this documentto use the ASN.1 notation for the messages rather than that defined in H.246. After a detailed presentation of thedocument, it was generally felt by the group that it offered a good approach to harmonization, and that the ASN.1notation has a more logical structure and appears to be more flexible and extensible. However, one of the main caveatswas the possible increase in complexity involved in parsing the ASN.1 generated messages, which might be a burdenfor a cheap terminal. M. Nilsson does not believe that the use of ASN.1 would increase the complexity of a terminal.D. Lindbergh (PictureTel) believes that the use of the ASN.1 Pack Encoding Rules would actually produce messagesshorter than those generated by the current H.246 message structure. However, it was felt that more investigation ofASN.1 was necessary before irrefutably committing the PSTN case to this route.
Towards the end of the available time for the session, the Chair expressed his opinion that it was necessary for thegroup to decide whether or not to adopt the harmonized proposal. Despite having come into the meeting with theproposal that the two documents, H.246 and H.245, could continue to run until the June meeting when a decision hadto be made, he now felt that it was necessary to make the decision now in order to ease the problems of implementerswishing to begin their work. Also, the requirement to work with a single document would ease the burden on theEditors and, hopefully, lead to a better job of editing.
A proposal was put forward to go ahead with the harmonized document and to curtail further work on H.246 but tokeep it available as a fall-back until the June meeting. The Editors will work to ensure that all of the technical contentof H.246 is transferred into the harmonized document, including the technical points raised in the first part of themeeting. The Editors will produce a new version of the draft harmonized document in the near future for distribution tothe Ad-Hoc group.
The consensus of the group was to accept the proposal to adopt H.245 and shelve H.246 with a view to deleting H.246at the June meeting. It was also necessary to ask the Plenary to confirm the decision. The Chair was concerned thatthis decision might discourage SG 14 from adopting the Control Recommendation for V.dsvd since they mightinterpret the use of ASN.1 as being too complex for a cheap terminal. The group proposed to send a liaison to SG 14,informing them of the decision and reassuring them that the adoption of the ASN.1 syntax will not add significantly tothe complexity of an implementation. It was also agreed to put across a message that the group is keenly interested ina harmonized solution across the board.
• Section 5.1.3 (Required Elements): It was agreed that H.324 terminals offering real-time audiographics conferencingshould (not “shall”) support the T.120 protocol suite.
• Section 6.1 (Modem): It was agreed that support of the V.34 administration channel is not required, but that itspossible use is for further study. However, H.324 terminals shall not use the administration channel for non-standardized purposes.
• Section 6.1 (Modem): The requirement for V.34 slave clocking was dropped, since it was agreed that this is notnecessary for H.320 interworking. (Also in section 8.2.)
• Section 8.1 (Speech Only Terminals): Interoperation with analog telephone terminals is to be mandatory.• Section 9.1 (Data Facilities): External DTE/ DTE interfaces will not be mentioned here, but this topic will instead
LBC-95-140 (D. Lindbergh, PictureTel) proposes a generic rate control mechanism for H.324. It suggests a newH.246 command be defined that instructs the far-end to limit its transmission rate.
It was agreed that the Editor would make editorial changes to complete the document, to implement the agreed changesand additions, and to further clarify the existing text where needed. In particular, the Editor expressed his intent, and thegroup agreed, to make the following more significant changes:
• Change references from “V.42” to “LAPM/V.42” to reflect use of V.42 subset only• Add text on interruptability status of video, data, and audio logical channels, per H.223• Note that sequence numbers for multilink are for further study (Contributions on this were promised.)• Add text about maximum audio delay jitter (10 ms, negotiable), per H.245• Add text explaining how LC 0 is pre-opened for control channel• Add text explaining use of audio/video skew message for multipoint use (optional equalization of delays at MCU)• Add text clarifying that G.723 audio rate may change “on the fly” without H.245 negotiation
LBC-95-095 (T. Geary, Rockwell) contains the report on DTE/DCE. Minor editing work had been accomplishedprior to this meeting.
STARTUP PROCEDURES
LBC-95-096 (I. Sebestyen, Siemens) contains the report on V.8. It states that no work has been done since the lastQ2/15 Rapporteurs meeting. There was discussion of the startup procedures in section 7 of the draft. The Editorrequested contributions and input on resolving the remaining questions. A liaison was sent to SG 14 with a copy ofsection 7, requesting their input on the best use of V.8, V.8bis, and V.34 procedures.
LBC-95-101 (J. Brownlie) is a liaison from SG 14 that includes draft Recommendation V.8. LBC-95-102 (J.Magill, Q1/14 Rapporteur) is a liaison from Q1/14 that includes draft Recommendation V.8bis. LBC-95-155 (R.Schaphorst, Rapporteur) is a response to this liaison urging that work on V.8bis be completed and issues resolved assoon as possible or by June 1995 at the latest. It also addresses codepoints, concerns, and alternatives.
LBC-95-132 (B. Welsh, BT Labs) suggests dropping use of V.8bis in favor of V.8 initially. This was discussed,and it was decided to await further input from SG 14 on this issue and to make a decision at the June LBC meeting.
There was discussion of defining seven operational “modes” for H.324 that might or might not correspond toV.8/V.8bis codepoints:
There might be more than one logical channel of each type, necessitating modes 6 and 7. No decision was reached onthis idea, and additional comments and proposals were solicited for the LBC email reflector.
OTHER AGREEMENTS
The group agreed to include, as optional, standardized data protocols, T.120, T.84, and T.434, in addition toLAPM/V.42, per the liaison received from SG 8 WP C (LBC-95-108).
It was agreed to include a control channel option using V.42 I-mode (sliding window) instead of XID frames, to allowstreaming of control messages. The H.245 editor will draft text.
It was agreed that receipt of downloaded multiplex tables for terminals supporting two or less logical channels (notincluding the control channel) should be optional. Downloadable tables shall remain mandatory for 3+ channelterminals. The H.324 and H.223 Editors will draft text.
H.26P/L
The mandate for the H.26P/L Ad Hoc Committee was to contribute to the definition of requirements and objectives ofH.26P/L that will become the long term video coding algorithm for Video Telephony. The plan is to align activitieswith ISO MPEG4 as much as possible in order to utilize resources as efficiently as possible.
The group discussed requirements for the long term and how these would be communicated to ISO MPEG4. It wasrecognized that ITU-T requirements were all based on communications applications. However, multimedia databaseswill play an important part, especially remote real-time interactive databases.
It was agreed that the new standard should be optimized at low bitrates (i.e., less than 64 kbits/sec) and should achievesignificant improvements in delay, efficiency, error robustness, and random access. In addition, it should becompatible with the emerging H.263 standard.
A few audio items were also mentioned, including low rate stereo speech coding for video teleconferencing. G.723should be used as a reference for comparison in the long term audio standardization.
PROGRESS IN ISO MPEG4
Over the past many months, the AOE Committee of ISO SC 29 WG 11 has been discussing the possible applicationsfor an advanced audio/data/ video coding standard. From a rather large list, eight functionalities have been distilled forstandardization. These have been further clustered into three general areas for testing, Content Based Interactivity,Compression, and Universal Access.
A call for proposals has gone out, and a Proposal Package Description (PPD) has been through several versions. Pre-registration of proposals is required before July 21, 1995, and submission of proposals plus D1 videotapes, if any, isrequired before September 15, 1995.
FUTURE ACTIVITIES
Between the March and June meetings, the group intends to communicate by email. A liaison to MPEG4 will beprepared in Boston and sent to the July MPEG meeting in Tokyo.
LBC-95-088 (D. Lappe, Robert Bosch) contains the report on mobile.
LIAISON
LBC-95-105 (R.L. Blane, INMARSAT) is a liaison statement from ITU-T SG 1 for information. It describes theservice objectives and principles for Future Public Land Mobile Telecommunication Systems (FPLMTS),Recommendation F.115. FPLMTS and UMTS (Universal Mobile Telecommunications System) provide a good basisfor the mobile work. F.115 provides a useful compilation of related ITU-R and T Recommendations.
LBC-95-115 (C. Englund, Rapporteur Q20/1) is a liaison statement from SG 1. It is noted with satisfaction thatthe LBC group has established a Mobile Ad Hoc group to facilitate smooth evolution from PSTN to mobile. Thedocument includes the request for additional guidance on the following items:
• Technical constraints affecting start up time• Suitability of T.120 protocol series for system management and transfer of data
The draft supplement to recommendation F.720 (Version 4), Videotelephone Service General for MobileTelecommunications Network, is included in LBC-95-115 for information.
LBC-95-116 (R. Schaphorst, Delta Information Systems) is a reply to the liaison statement of SG 1 in LBC-95-115 . It states that the schedule to extend the H.32P Recommendations to the mobile network environment hasaccelerated, with the target date for determination to be November 1995. The response addresses start up time, T.120protocol, and the draft supplement to F.720.
LBC-95-147 (R. Brainard, AT&T Consultant) questions the plans of the mobile radio experts group with regard toPSTN videophone for mobile networks, raising concerns about different videophones for PSTN and mobile, lack ofinput or requirements from carriers and end users and issues associated with interworking units. There was a discussionon the need for a global mobile videotelephone standard. It was noted that the GSM (Groupe Speciale Mobile) speechcoder may be taken as an example that global standardization of different types of media codecs is an essential issue.
MOBILE NETWORK CHARACTERISTICS
It was agreed to develop a document for the next meeting that describes basically the mobile networks to be addressed(Network Characteristics Document). Volunteers were found to provide the descriptions for DECT (Digital EuropeanCordless Telephone), GSM, TETRA, AMPS-D, IS-54, Inmarsat, PDC, UMTS, and FPLMTS. The document willinclude the following chapters:
1.0 Introduction2.0 Terminology3.0 Mobile Network Classification4.0 Network Description5.0 Comparison of Key Parameters6.0 Characteristics of AV.32M7.0 Interworking8.0 Possible Applications
REQUIREMENTS
LBC-95-92 , “Ad Hoc Work on Requirements for Very Low Bitrate Visual Telephony (Mobile Draft 1.0)” (F.Huffman, MCI), was discussed in detail in a joint session with the Video group. Several remarks were made, and F.Huffman provided a revised version (LBC-95-92R1) after discussions with the multiplex, speech. and systemsgroups. The major outcome of the discussions is summarized as follows:
• It is a basic requirement for the mobile videotelephone to provide a PSTN/Mobile network transition.• The mobile requirements document must be improved in such a way that it is valid especially for mobile. All parts
of the document that are PSTN only shall be dropped.• The network characteristics document will serve as a basis to deal with several open issues in the requirements
document (e.g., for the definition of the communication interface[s]).• The mobile to ISDN transition issue has been addressed. It was pointed out that there may be the need to have an
MPU (multiple port unit) that combines more than one mobile connection via the ISDN network. This issue is for
further study. More information may be available from SG 15 WP 1. It was decided that this technical questionwill be formulated in more detail and put forward with a request for more information to SG 15 WP 1.
• A system diagram is needed that describes the possible scenario of a mobile videotelephone in the networks to beaddressed.
• It was noted that the packet loss and HDLC (High Level Data Link Control) stuffing at the multiplexer may causeproblems in the case of erroneous channels. This issue needs further study.
• There was a general feeling that the requirements document provided by F. Huffman (MCI) is a very good startingpoint for proceeding toward a final document in November 1995.
R. Schaphorst (Delta Information Systems) presented a general view of possible audio-visual standards for very lowbitrates in different kinds of networks (LBC-95-159). It will be included in the mobile requirements document.
AV.26M
B. Haskell (AT&T) presented an outcome of MPEG 2 that is important for the error control of H.263 (LBC-95-154 ). He proposes that two extra bits be provided just after the GOB-Header in the draft proposal for AV.26M. Theywill be used to indicate that coding parameters have changed in the most recent picture header.
LBC-95-133 (T. Nakai, OKI) proposes a syntax modification of TMN2 to utilize the self synchronization propertyof the VLC (Variable Length Code) code for DCT (discrete cosine transform) coefficients and to minimize the discardedpart of the bit stream. Long and interesting discussions occurred about this document and it was decided to perform acore experiment to test the OKI proposal. The core experiment will be performed by T. Nakai (OKI), G. Bjontegaard(NTR) and M. Frater (University of New South Wales).
LBC-95-144 (R. Mann Pelz and R. Fischer, Robert Bosch) shows the performance of an Unequal Error ProtectedTMN5 video codec in a mobile environment. Aspects concerning interleaving in conjunction with unequal error pro-tection through the application of RCPC (Rate Compatible Punctured Convolutional) codes are addressed. A gain ofapproximately 2 dB in SNR (Signal to Noise Ratio) can be obtained by applying UEP (Unequal Error Protection) in-stead of EEP (equal error protection).
LBC-95-145 (D. Lappe, Robert Bosch and K. Illgner, IENT, RWTH Aachen) is a revision of LBC-95-003(Robert Bosch and IENT, RWTH Aachen) addressing video coding in mobile environments. It is a proposal forrecommendation AV.26M. The main difference from H.263 is that error handling is part of the video coder and that thesyntax is modified.
It was discussed whether chapter 5 (Error Control) of the draft AV.26M is needed to be part of the videorecommendation. It may be possible to have the FEC (Forward Error Control) as part of the adaptation layer which ispart of AV.22M. For the moment, it was decided to keep the FEC in the video. Whether or not it finally will belocated in AV.22M will be decided later.
It was pointed out that several core experiments are necessary. Participants in the experiments will be T. Nakai (OKI),G. Bjontegaard (NTR), M. Frater (University of New South Wales), B. Haskell (AT&T), R. Fischer (Bosch), and D.Lappe (Bosch).
AV.22M, AV.24M, AV.25M
The modifications necessary to make H.22P error robust are described in detail in LBC-95-001 (Robert Bosch). Thiscould be taken as draft AV.22M. The approach needs to be tested in case of bit errors. Input from multiplex is needed.
There was no document available for AV.24M. This led to a request to the control/supervision group to provide inputfor mobile in this area.
Input was also needed from the speech group about error robustness in case of errors. It appears that the current speechcoder can be error protected by an unequal error protection as is used for the GSM speech coder. In any case, a proposalis needed for speech, and it must be discussed in detail at the June meeting.
CORE EXPERIMENTS
It was decided to perform core experiments for the mobile transmission. A basic model (Mobile Test Model No. 1,MTM 1) was defined for comparisons in the experiments. It is the TMN 5 with the following additional parameters:
• Equal error protection• GOB-headers at every Macroblock row• 3 blocks intra update per frame for refresh
• Picture Start Code is not corrupted by bit errors• 2 bits GOB-frame-OD are assumed (refer to LBC-95-154 , AT&T)• 6.25 Hz frame rate (every 4th frame)• Sequences “Mother and Daughter”• No interleaving is used• Each sequence will not be repeated for the experiment (“one experiment”)• The first frame is assumed error free• No options are included
C1: This model is the core experiment 1 (C1) and will be used as the basis for comparisons with the other definedcore experiments.• Participants: AT&T, Bosch, NTR, OKI, University of New South Wales
C2: “OKI - Experiment,” performing the experiment based on LBC-95-133 (OKI)• Participants: Bosch, OKI, University of New South Wales
C3: “Bosch - Experiment,” performing the experiment based on LBC-95-144 (Robert Bosch) and LBC-95-145 (Robert Bosch and IENT, RWTH Aachen)• Participants: Bosch, NTR
C4: “Combination of OKI and Bosch”• Participants: Bosch, OKI
C5: Error concealment• Participants: AT&T, Bosch, NTR, University of New South Wales
In all experiments, the same bitrate and frame rate as for experiment C1 shall be used. For C1 through C5, thefollowing error models will be applied:
• Error patterns for DECT (error rates 10-2 and 10-3) at 32 kbit/s, which are available at the mobile FTP side• Binary Symmetric Channel (BSC) error rates 10-2 and 10-3
• It will be tried to obtain an agreement to use the C-program for testing error robustness proposed in MPEG 4.• Error patterns of the PDC (11.2 kbit/s) will be put forward to the mobile and ad hoc FTP side by NTT .• Motorola will kindly provide a C-program to emulate bit error sequences.
A C-program will be provided on the FTP side to apply the bit error patterns on the standards bitstream exchangeformat of the LBC group.
A proposal for the buffer regulation for the experiments (C1-C5) will be sent to the mobile reflector by Bosch. Alongwith this information, a proposal for the BCH-codes to be used for the core experiments will be sent.
For comparisons of results, the following measurements have been decided upon:
• SNR• Standard Deviation of SNR• Subjective quality
The different experiments must be checked in terms of complexity and delay.
There was a strong request that the final video digital sequences for the June meeting be collected and presented on onetape by one company. A possibility would be that all final video results will be put on the FTP server for the col-lection. Whether that procedure is possible or not will be answered the week after the meeting by Bosch.
The expected outcome of the experiments is:
• Improved quality• Comparisons with MTM 1• Approval of single proposals by other companies
The question was raised on whether or not arithmetical coding provides sufficient error robustness in the case of biterrors. It was mentioned by Bosch that, in the MAVT HW-demonstrator, arithmetical coding is applied. Due to theclass/header structure, a stable decoding is not much more difficult for that demonstrator than for Huffman code. In anycase, arithmetical coding is an option and may be switched off if it will not work over mobile channels.
It was decided, for the moment, not to have a bitstream exchange for the experiments.
SIMULATION RESULTS
Two videos were shown. One from OKI demonstrated the subjective gain possible to be achieved by modification ofsyntax (LBC-95-133 , OKI). The second, from Bosch, showed the results of an experiment performed as described inLBC-95-144 (Bosch). It was demonstrated that the depth of the interleaver has a major impact on the picture quality.The optimum interleaver depth for the AV.26M needs to be carefully defined. A significant gain in subjective qualitywas shown in the case of unequal error protection.
AD HOC COMMITTEES
Thirteen Ad Hoc Committees were established to continue the work until SG 15 meets in Boston in June.Richard Schaphorst, Delta Information Systems
LBC Q2/15 MEETING ROSTER, MARCH 27-30, 1995, G ENEVA, SWITZERLAND
Richard Schaphorst, Delta Information Systems LBC Rapporteur
AustraliaUniv. of New South Wales Michael FraterUniv. of Sydney Marwan Jabri
FinlandVistaCom Erkki Tanskanen
FranceFrance Telecom/CNET Jacques GuichardFrance Telecom/CNET Isabelle HaignereFrance Telecom/CNET Jean-Pierre PetitFrance Telecom/CNET Claude LamblinLab. d’Elec. Philips Franck LecanuLab. d’Elec. Philips Philippe PerrotLab. d’Elec. Philips Philippe RigletLab. d’Elec. Philips Estelle SonnicMatra Comm. Philippe Camus-MartinThomson CERDF Michel Kerdranvat
GermanyDeutsche Telekom Peter ListDeutsche Thomson Brandt Imre VargaRobert Bosch Ralf FischerRobert Bosch Dirk LappeSiemens Istvan SebestyenSiemens AG Fritz SeytterUniv. of Wurzburg Oliver Rose
IsraelDSP Group, Tel Aviv U. Yair Be’eryNat’l Semiconductor Matthias Wenzel
JapanGraphics Comm. Lab. Sakae OkuboMatsushita Comm. Yutaka MachidaNTT Takehiro MoriyaNTT Co Do Mo Tomoyuki OhyaOKI Electric Toshihisa NakaiSharp Keiichi Hibi
KoreaDaewoo Electronic Hae-Mook JungHyundai Electronics Joo-hee MoonKorea Telecom Joon-Hyeon JeonKorea Telecom Jin-Soo ParkLG Electronics Jungsoo ParkSamsung Nam Kyu HaSamsung Jaebum HongSamsung Young Jin KimSamsung Il-Hyun NamSamsung Kyu-Hwan Sim
NetherlandsKPN Research Karel Rijkse
NorwayTelenor Research Gisle BjontegaardTelenor Research Karl Lillevold
SwedenTelia Research AB Leif Bengtsson
UKBritish Telecom Mike NilssonBritish Telecom Bill WelshBritish Telecom Michael W. WhybrayProbe Comm. John Magill
USAApple Computer Kathy WangApple Computer Hsi-Jung WuAT&T Consultant Ralph BrainardAT&T Bell Labs Richard CoxAT&T Mich BuckleyAT&T Paul CrouchAT&T John HartungAT&T Bell Labs Barry HaskellAT&T Dror NahumiAT&T Robert ReynoldsAT&T Kamles TewaniAVC Technology B.Y. WooCirrus Logic Narayanan RamCreative Labs Corey GatesCreative Labs David WangCreative Labs Lung YehDavid Sarnoff Research Ya-Qin ZhangIBM Research Marc Willebeek-LeMairIIT Paul VooisIntel Tom GardosIntel Mike KeithIterated Systems Richard IvyKNK Consulting Kristine KneibMCI Fred HuffmanMotorola Cheung AuyeungMotorola Jeff SmolinskeMotorola ISG Vedat EyubogluNat’l Semiconductor Ziaonong RanPictureTel David LindberghRockwell Int’l. Tom GearyRockwell Int’l. Albert HsuehRockwell Int’l. James JohnstonSpecom Technologies Yuhai MaoTexas Instruments Karen OehlerTexas Instruments Raj TalluriTexas Instruments Fritz WhittingtonToshiba Faramarz AzadeganWintec Peter Hsieh
REPORT OF TR-30.2, DATA TRANSMISSIONMARCH 31, 1995, NORCROSS, GA
Note: The reports from the March TR-30.1, TR-30.3, and TR-30.4 meetings were published in CSR-T Vol. 6 #3,April, 1995.
ISO/IEC JTC1/SC6/WG3
ISO/IEC JTC1/SC6/WG3 sent a liaison to ITU-T Study Group 14 (TR-30.2/95-03-009). Some of the items inthe liaison are of interest to TR-30.2. The liaison indicates acceptance by JTC1/SC6/ WG3 of the Study Group 14changes to the definitions of V.24 circuits 102, 102a, and 102b with respect to multiple signal commons.JTC1/SC6/WG3 has proposed that the definition of circuit 102 be further changed to indicate that this circuit should bebrought to one point in the DTE (Data Terminal Equipment), not the DCE (Data Circuit Terminating Equipment). Itis their opinion that modern day DCEs are primarily found in plastic cases with wall mount power transformers,making a signal common point with frame ground impractical. The liaison also recommends the deletion of all of the200 series circuits in V.24. They feel that there is no longer a need for parallel control of dialing in DCEs sincetoday’s DCEs make use of the “AT” command set for the transfer of dial information.
TR-30.1/95-03-011 is the latest revision of ISO/IEC 2110, “Data communication - 25-pole DTE/DCE interfaceconnector and contact number assignments.” It is a copy of the ballot which will require a TR-30.2 response at itsMay meeting; it was distributed to TR-30.2 members for review. It includes the connector contact assignments for theinternational equivalent to the TIA/EIA-530-A interface that was previously in ISO 2110 Amendment 1. Initialobservations of the latest draft indicate a need to remove all references to the now inactive ITU-T V.35Recommendation and to clarify operating data rates for the interfaces recommended in ITU-T Recommendation V.34.TR-30.2 will be including these and other comments in their response to the formal ballot.
TR-30.2/95-03-010 is ISO/IEC CD 8481:1995, “Information Technology - Telecommunications and InformationExchange between Systems - DTE to DTE direct connections.” This document defines the interconnection of X.24interfaces (used on X.25 data networks) over a 15 pin connector. TR-30.2 has seen this document a number of timesin the past and has made no comments. It is expected that TR-30.2 will recommend an affirmative ballot with nocomment at its May meeting.
DTE/DCE INTERFACE FOR DIGITAL CELLULAR (PN-3138)
Very little progress was made towards the completion of the draft standard PN-3138, Miniature DTE/DCE Interface forDigital Cellular Equipment. Representatives of AMP, Inc. attended the last TR-45.3.2 meeting and presented the newproposed connector which TR-30.2 had seen at its December 1994 meeting. A. Sacuta (TR-45.3.2 Chair) attended thisTR-30.2 meeting and reported that although TR-45.3.2 has yet to reach a conclusion with regard to this new connector,he sensed a high degree of acceptance. The major area of interest was the ability to provide a multiple function withinthe connector shell, both data and RF interfaces. A question was raised with respect to TR-30.2 continuing support ofthis work if it becomes a cellular specific interface since it will no longer provide general purpose DTE/DCEfunctions. This is an issue which TR-30.2 will need to address if the final decision by TR-45.3.2 is to recommend themultiple function connector. At this point it is difficult to predict the outcome.
REVISION OF EIA-404-A (PN-2797)
The ballot on the revision of EIA-404-A, Standard for Start-Stop Signal Quality for Non-Synchronous Data TerminalEquipment, to be published as TIA/EIA-404-B, has finally been clarified. Due to the move of TIA headquarters inDecember, some of the ballots had been misplaced. It was confirmed that the ballot did pass and “camera ready” copywill be forwarded to TIA for publication. TIA/EIA-404-B should be available within the next few months.
VERY HIGH SPEED INTERFACE, ELECTRICAL CHARACTERISTICS (SP-3357)
SP-3357, Very High Speed Interface, Electrical Characteristics, is out for ANSI industry ballot. The ballot closes onMay 16, 1995, which will permit TR-30.2 to resolve any ballot comments at the May meeting.
MEDIUM SPEED DTE/DCE INTERFACE (PN-3416)
Some progress was made towards the completion of PN-3416, Medium Speed DTE/DCE Interface. The outstandingissue is to determine if the standard should recommend a capacitive connection between signal common and frameground. J. Moran (Motorola ISG) provided an analysis of the issue (TR-30.2/95-03-008). He suggests that bothMains safety and EMI/RFI (Electromagnetic Interference/Radio Frequency Interference) can be achieved by connecting a
capacitor from signal common (CKT-102) and Frame Ground. He also suggests that, if necessary, multiple capacitorsbe used (connected in parallel) to achieve a low impedance path to Frame Ground over a very large frequency bandwidth.No final conclusion was reached; however, an additional paper is expected from J. Moran at the May meeting. It isexpected that the draft standard could be finalized at that time for industry ballot.
ITU-T STUDY GROUP 14
F. Lucas (General DataComm) provided TR-30.2/95-03-007 as a proposed contribution to ITU-T Study Group 14.It proposes additional changes to V. series recommendations, specifically V.36 and V.37, to delete references to thenow inactive Recommendation V.35. Because of the timing of the meeting, it was not possible to receive U.S. StudyGroup D approval of this paper in time for the April Study Group 14 meeting. Since TR-30.2 had forwarded a similarpaper to the Study Group 14 meeting recommending deletion of V.35 references in V.10 and V.24, it was felt thatthese additional references could also be covered during the discussions at the Study Group 14 meeting.
Fred Lucas, General DataComm
TR-30.2 MEETING ROSTER, MARCH 31, 1995, NORCROSS, GA
Fred Lucas, General DataComm TR-30.2 Chair
AMP, Inc. George LawrencedB Consulting (for AT&T) Dick BrandtDigital Equipment Corp. Remi LiseeEricsson Al SacutaHayes Microcomputer David RifeMotorola ISG Les BrownMotorola ISG Jack DouglassMotorola ISG Jack MoranTexas Instruments Kevin Gingerich
COMMUNICATIONS STANDARDS REVIEW ALSO PUBLISHES:
Communications Standards Review–Radiocommunications (ISSN 1081-6852), a technical journalthat reports on U.S. (TIA) Standards Committee meetings in wireless WAN data communications. CSR-R ispublished six to eight times per year
Communications Standards Summary (ISSN 1075-5721), a quarterly publication reportingon all active projects and recently completed standards of the Telecommunications Industry Association’s (TIA’s)TR-committees. Authorized by TIA.
Fiber Optics Standards Summary (ISSN 1081-6844), a quarterly publication reporting on all activeprojects and recently completed standards of the Telecommunications Industry Association’s (TIA’s) FO-committees. Authorized by TIA.
To receive a complimentary issue of any of CSR’s technical journals, please contact Elaine Baskin, tel +1 415856-9018, fax +1 415 856-6591, e-mail [email protected]
REPORT OF STUDY GROUP 14APRIL 18 – 27, 1995, GENEVA, SWITZERLAND
TD-10add is the list of documents for the SG 14 meeting. The Study Group approved:• The appointment of J. Magill (AT&T, UK) as the SG 14 representative to the JCG (Joint Coordination Group) on
Audio Visual Multimedia Service• An interim Rapporteurs meeting in the U.S. in July• A Working Party 1 meeting in Munich, Germany during the week of October 9-13.
Q1/14, V.34
TD-91 is the report of the meeting from the Rapporteur (R. Stuart, Penril, USA).
TD-13 (G. Griffith, Rockwell, USA) is a liaison from SG 8 requesting input from SG 14 regarding changes to V.34that would facilitate its use in facsimile applications. The first change proposed is that an explicit asymmetricalcontrol channel mode be defined so that it would only be allowed when requested. Specifically, setting bit 50 of theMPh to “ONE” would enable the asymmetrical mode. SG 8 does not plan to utilize this capability in the near term.The second change was clarification of what should happen in cases where specific sequences are not detected. SectionD of TD-65 proposes that if any of these sequences are not detected, a control channel retrain be initiated. The thirdchange was clarification of the condition of 106 during primary channel retrain. The solution proposed in TD-65 is tostate that it should be turned OFF if it is ON. In response to the SG 8 questions, a proposed new Annex 1 to Rec.V.34 (TD-65) was briefly presented. TD-64 is the proposed response to SG 8 reflecting these proposed changes.Both TD-65 and TD-64 were approved.
TD-58 (T. Geary, Rockwell, USA) is liaison from SG 15 requesting information on the status of the seamless ratechange facility in Rec. V.34. TD-58 describes several most probable implementations of H.324 with modem andPC, and derives the communications requirements. The response to TD-58 is contained in TD-93 (D. Stuart, Penril,USA). Although there is no active study on this subject in SG 14, discussion could be started based on thisrequirement at the October 1995 WP 1/14 meeting.
D.110 (L. Brown, Motorola, USA) highlights a potential problem with SS#5 (Signaling System 5) and providessuggested solutions. It has been discovered that the Phase 2 Tone A signal (section 10.1.2.1 of V.34), when the roundtrip delay is greater than or equal to 100 ms, causes SS#5 facilities to falsely detect Tone A as a disconnect request.D.110 proposes changes that would increase the 1800 Hz Guardtone from -7 dB to 0 dB only during Tone A or ToneA bar. J. Moran (Motorola, USA) proposed a second solution that changes the level relationship of the 1800 Hz guardtone to the 2400 Hz tone so that the Guardtone level will always be the higher signal. The advantage is that Guardtonelevel does not change the power on the line during the sequence. Cornel Electronics (Ireland) expressed support for theproposal in D.110 because it provides, in their opinion, greater protection from echo. It was finally agreed to send aliaison (TD-92) to SG 11 to get their input on these two proposals.
COM 14-R 5-E , Annex 12 (B. Betts, AT&T, USA) describes the implementation of two new optional data rates,31200 bit/s and 33600 bit/s, which are compatible with ITU Recommendation V.34. The proposal for anaugmentation to the supported signal rates in V.34 had already been accepted at the December 1994 WP1/14 meetingand was only introduced here for information.
This revision to V.34 was determined for Resolution 1. It was decided that the choice between the two fixes for theSS#5 problem be deferred until the October Working Party meeting.
Q1/14, V.SAVD
J. Magill Rapporteur (AT&T, UK) started this meeting by emphasizing that the approval of V.8bis is the mostimportant goal of this meeting. Completion of the work on V.asvd, multiplexing, control, and the system documentswere identified as other high priority items. TD-101 is the Rapporteur’s report.
LIAISONS
TD-3 is a liaison from SG 15 indicating their intention to develop a recommendation(s) that would specify amethodology for separating (demuxing) multi-media bit streams within the network to allow for different routing orhandling of the steams within the network.
TD-8 is a liaison from SG 8 in response to an earlier liaison from SG 14 to SG 8 requesting specific delayrequirements for audio-graphic conferencing. TD-8 suggests that the desirable range for a one-way delay is 50-100msec, and that 100 msec or greater is undesirable.
TD-17 is a liaison from SG 8 that addresses the issue of simultaneous voice and facsimile (SVF). Both analog anddigital approaches are being considered. It asks whether an auxiliary control channel will be available for analog SVFand whether the use of H.24P and/or V.8bis would be preferred for the digital SVF case.
TD-20 is a proposed response to TD-17 suggesting the use of V.8bis for negotiating. It states that no advantage isseen using the auxiliary channel over the use of XID (eXchange IDentification). SG 14 is presently contemplating theuse of a two-stage negotiating procedure (initially with V.8bis and then refinement with the control channel).
AVD (ALTERNATING VOICE DATA)
D.98 (M. Winseck, Radish, for Ameritech, USA) outlines the potential applications and the requirements for anAlternating Voice/Data (AVD) Recommendation. This methodology is highly usable for short bursts of data. Unlikeother SVD applications, the voice connection would not be lost in the event of a system shut down. On therequirements side, D.98 states that, in any AVD Recommendation, the upgrade process for existing equipment mustbe easy and inexpensive, that existing data pumps must be usable with little or no change, that information transfermode must be supported and compatible with analog, digital, and cellular phones, and that there must be a minimumtransfer time between modes (3 seconds or less to transfer 25 by 80 character lines).
During the discussion, it became clear that this work would also impact the requirements for V.42 (i.e., resurrectingthe half-duplex work) as well as V.8bis.
ASVD (ANALOG SVD)
D.111 (L. Brown, Motorola, USA) proposes that, pending the resolution of technical issues, the determination forV.asvd be made at this meeting. It also proposes that V.asvd and DSVD are two complementary technologies and thatV.asvd better serves the following requirements:• Audio delay• Data delay• Multiple speakers and arbitrary audio sources• Cross-tandem performance• Degraded lines• Complexity
In response to questions, it was clarified that the outstanding technical issues were contained in D.73 (Motorola) fromthe December 1994 WP 1/14 meeting. During discussion, BT stated that they now support the approval of V.asvd andwere, therefore, in support of the U.S. proposal.
As neither the draft Recommendation, TD-37 , nor D.73 were available at the first session, further discussion was putoff until a later session. (TD-37rev is Version 1.4 of draft Recommendation V.asvd.)
D.73 (J. Moran, Motorola, USA) proposes a simplified approach to framed QADM (Quadrature Audio DataModulation). Each point was presented to clear any open issues. The first point was the choice of a symbol rate foruse with limited bandwidth ADPCM. 2743 Hz was suggested as a replacement for 2800 based upon better conformitywith V.32bis. K. Ko (AT&T, USA) responded that the symbol rate was chosen specifically to allow the use of a 10-bit side channel for side information. Changing the symbol rate would require a complete redesign of the Rec-ommendation. Additionally, 3200 Hz was suggested as an alternative for 3000 Hz for similar reasons. Again, K. Kosuggested that this would also require a re-design. There were suggestions that the Recommendation allow for possibleexpansion to three symbol rates in the future. It was decided that the current Recommendation did not preclude adding athird symbol rate in the future.
The next point was a suggestion to use the V.32bis training sequence in place of the one in the Recommendation. Theproposal was modified to specify the use of some other up-front automoding protocol (e.g., V.8 or V.8bis) to avoidincorrect connection. A discussion of V.8 versus V.8bis took place. There was no resolution.
The last point was a suggestion that V.32bis coded constellations be used. It was answered that V.asvd constellationswere based on V.34 constellations to take advantage of the knowledge gained in that work. Motorola withdrew theirconstellation proposal.
There was also some discussion of how a V.18, V.asvd multi-mode terminal would work. The conclusion was thatV.18 would have to be modified to reference V.8bis.
The issue of whether a code point needs to be added to V.8 or V.8bis to identify V.asvd will be addressed at the OctoberWP 1/14 meeting. It was decided that V.asvd was mature and that it should be determined for Resolution 1 at thismeeting. This was later approved at the SG 14 Plenary.
TD-53 (J. Magill, AT&T, UK) is a report on the activities of the Joint Coordination Group on Audio VisualMultimedia Service (JCG-AVMMS). J. Magill highlighted the perceived overlap between SG 14 and SG 15 work onvoice data applications. He also highlighted the “Framework for Multimedia Standards”(see CSR-T 6:2 page 33-36 fordetails of this framework). A liaison (TD-102) was approved to this JCG. The liaison includes an update of the SG14 work on ASVD.
DSVD (DIGITAL SVD) CONTROL
D.120 is a multi-company proposed draft Recommendation for DSVD Control. C. Hansen (Intel, USA) brieflyhighlighted the important features of this proposal, noting that is based upon the use of V.42 (Link Access Procedurefor Modems, LAPM) frames. D.120 only addresses the audio channel control. Control of functions that are notclearly audio or data are left for further study. This proposal envisions the use of only one audio and one data channel(since this is the present scope of DSVD). The work on H.246 and/or H.245 was not considered in this proposal asthey were undergoing a harmonization process. However, D.120 does propose to consider it in future versions.
D.85rev is a set of comments on D.120 . It was very briefly introduced by F. Burg (AT&T, USA) and includes bothtechnical and editorial comments.
TD-54 is a liaison from SG 15/Q2 that describes the harmonization going on between H.246 and the correspondingcontrol Recommendation for ATM Multimedia, H.245, which will result in a revised H.245. It suggests that SG 14might want to consider its application for the DSVD control procedures. A copy of the latest version of H.245 isattached for information (also available at ftp://ftp.std.com/vendors/PictureTel/h324).
It was decided that this work would have to be progressed at an interim Rapporteurs meeting with the goal of having itdetermined at the October WP 1/14 meeting.
DTE-DCE INTERFACE
TD-2, a liaison from SG 15 (N. Kenyon, BT Labs), addresses the requirements for connecting a PC to avideotelephone. Three point-to-point scenarios are considered: use of T.120, use of an emulation of V.14/V.24, anduse of non-standard (manufacturer-specific) protocol stacks. (See CSR-T 6:2 page 32 for additional information.)
TD-25 is a liaison from SG 8/Q10 to both SG 15 and SG 14. It also addresses the definition of the dataport of avideophone as was raised in TD-2. Q10/8 needs to define the dataport interface in the next draft of T.123. (SeeSpeech Coding below for the response.)
TD-58 is a liaison from the SG 15 LBC group (Low Bitrate Video Coding). It addresses a broad range of interfaceissues related to the implementations of GSTN Visual Telephony. They request SG 14 experts’ help and advice indeveloping appropriate definitions. They anticipate further extensions to V.25ter with appropriate responses if thecapability is not supported. During discussion, it was suggested that an ad hoc group be set up in SG 14 to addressthis issue and that this group would work closely with the SG 15 Experts. TD-96 is the liaison to SG 15 Q2(videophone) noting that a joint meeting of Q1/14, Q6/14, Q7/14 and interested SG 15 experts will be held August 7,1995 in Portland, OR, USA.
SPEECH CODING
TD-5, a liaison from SG 15, provides a status report on the voice coder work. SG 15 believes that the only feasibleway to develop a new, low complexity voice coding standard in an accelerated time frame is to modify or adapt one ofits existing (or about to be approved) standards. They also note that G.AV25Y (G.723) and G.8kbps meet or surpassmost SG 14 requirements except for complexity.
D.88 (A. Sadri, IBM, USA) describes the embedded signaling capabilities of the GSM and GSM/VQ (vectorquantization) bit streams. It states that GSM and GSM/VQ can be used on DSVD voice channels without an audioheader and without an HDLC control field (assuming the formats described in V.dsvd). As a result, the gross bit rate ofa GSM or GSM/VQ channel would be equal to that of the coder output plus whatever is employed for error detection.
During the discussion, it was clear that this coder achieves its benefits of reduced complexity through a lowering ofvoice quality.
An ad hoc group was formed to draft a response to TD-25 (Q12/15) which requested more information relating to SG14’s priorities for the new speech coder. D .82 (BT, Motorola and PictureTel) requests that G.723 and G.728 (16kbit/s) be considered for DSVD rather than a new voice coder. This was not supported. TD-95 , the response toQ12/15, confirms that SG 14 wishes SG 15 to proceed with the voice coder work. It provides a ranking of voice coderfactors for SG 14:1. Bit rate2. Complexity (MIPS)3. RAM4. ROM5. Coder delay6. Voice quality (unranked): agree with SG 15’s view (G.726 or better) but do not consider improvement over G.726
important.7. Closeness to existing coder standards: not a SG 14 priority8. Dual-rate coder: not a high priority (should be left for further study)
TD-95 also includes a listing of 31 applications for SVD systems.
SYSTEM
TD-79 is a first draft of V.dsvd System Recommendation. It was briefly introduced by J. Magill (editor). This draftincludes a block diagram similar to the H.324 block diagram and uses a V.24 interface for the data port. The editorsolicited contributions and email correspondence to get this work in shape for determination at the October meeting.
Q1/14, V.8BIS
TD-104 is the Rapporteur’s report (L. Brown, Motorola, USA). TD-35 is the report of the April 5-7, 1995Rapporteurs meeting on V.8bis. TD-60 is a revised draft Recommendation V.8bis reflecting the agreements fromthat meeting. Revision marks indicate changes from COM 14-R 6-E , draft Recommendation V.8bis, datedDecember 1994.
D.83 (J. Brownlie, BT, UK) provides a point-by-point discussion of what V.8 does and what V.8bis is intended to do.It raises some concerns:• V.8bis may interfere with existing terminals• The need for 2-tiered negotiation procedures has not been validated• It is too complicated• The error recovery procedures are not fully defined.It proposes that Resolution 1 procedure for proposed draft V.8bis not be accepted. .
D.84 (J. Brownlie, BT, UK) suggests a way of accommodating Terminal Selection and change of call function duringa call using V.8 signals. It proposes that the length of CI (call indicator in V.8) be manually controlled (i.e., CIwould stay on the line as long as “the button” is pushed) to handle the detection in the presence of voice (if you waitlong enough there will always be some gaps in the voice) and/or “glare” (one party will press the button longer)conditions.
D.92 (L. Smith, AT&T, USA) was introduced by M. Buckley (AT&T, USA). It provides an overview of thecapabilities claimed by V.8bis, highlighting its flexibility and user friendliness.
D.99 (Ameritech, Intel, Microsoft, Motorola and MCI) was introduced by M. Winseck (Ameritech, USA). Thesource companies do not support Version 1 of the proposed draft Recommendation V.8bis. D.99 identifies ninetechnical deficiencies in the ballot text of V.8bis. It raises concerns about the ability to reliably detect the ES (EscapeSignal), MR (Mode Request), and CR (Capabilities Request) signals, its compatibility with existing equipment, lackof flexibility in the capabilities exchange, the length of and format of the capabilities exchange, the inclusion of anexplicit ACK (Acknowledgment), the lack of specification of NAK (Negative Acknowledgment) scenarios, and errorhandling and the possible problem with SS#5.
D.95 (L. Smith, AT&T, USA) proposes the use of a single tone appended to a dual tone (DT) to increase reliabilityof detection. D.96 (L. Smith, AT&T, USA) proposes that only two DT signal pairs need to be defined: one for aninitiating signal and the other for a responding signal. It also proposes that different tone segments appended to theinitiating dual tone signal be used to distinguish the functions of CR, MR, and ES. D.93 (L. Smith, AT&T, USA)
proposes the use of 1269 + 1989 Hz and 1402 + 2198 Hz as the two DT signals. This is based upon an examinationof the slope of the local loops, the spectrum of vowels, and the sensitivity of the human ear.
D.94 (L. Smith, AT&T, USA) proposes the use of different signal levels during the call and at setup: lower power inthe ambiguous situation where a call may be answered and higher power during a call when the users are expecting asignal. It also proposes that the transmission of initiating signals MR and CR be required to precede the initiation ofan OGM (On-Going voice Message) when an OGM is transmitted.
D.87 (A. Sadri, IBM, USA) proposes simplification of V.8bis by reducing the number of DTMF tones andeliminating incompatibility problems between the Initiating station and the Responding station. Specifically, itrecommends deleting sections 9.1.1.2 and 9.2.1.2.
D.100 (M. Winseck, Ameritech, USA) proposes that the ES signal be used to initiate all V.8bis transactions both atthe beginning of a call and throughout the entire duration of a call. It also proposes that both the MR and CR signalsbe changed to the ES signal followed by a second dual tone signal. D.101 (M. Winseck, Ameritech, USA)recommends the use of a new dual tone signal called CQ, the incorporation of an express mode for quick return tovoice, and a change in the coding structure. D .100 and D.101 recommendations are claimed to offer improvedcompatibility with existing equipment.
D.108 (M. Winseck, Ameritech, USA) proposes the specification of an optional guardtone to address the potentialproblem of undesired network disconnect with SS#5. This optional guardtone is required because of the frequenciesused in the existing ES signal.
D.97 (L. Smith, AT&T, USA) proposes studying the possible omission of the V.8 CM/JM/CJ (Call Menu/JointMenu/CM terminator) signals when V.8bis is being used. It also proposes that a liaison be sent to SG 15 to see ifthis would cause any problems with the CME detection for demod/remod. It was clear that this would require amodification to V.8bis to also provide the modulation mode selection functionality. There was considerable discussionabout the impact on other Recommendations.
D.102 (M. Winseck, Ameritech, USA) proposes the addition of new capabilities exchange signals to be used toindicate the desire to respond and automatically return to voice. It also proposes that all of the coding be in HDLCformat.
D.103 (M. Winseck, Ameritech, USA) suggests keeping the MS (Mobile Station) signal as short as possible.Specifically, it proposes a method for shortening the V.8bis mode select by two octets.
D.104 (M. Winseck, Ameritech, USA) proposes a new format for exchanging capabilities that allows combining allof the pertinent data (related to a specific capability) in one sequence. The existing methodology uses a two stagemethod.
D.107 (M. Winseck, Ameritech, USA) proposes a method of error recovery for two of the possible error conditions inV.8bis. It provides text and figures that define failure handling scenarios.
D.105 (M. Winseck, Ameritech, USA) proposes the elimination of the implicit ACK (the detection of an appropriatecarrier being considered as an ACK). It proposes that the need for an explicit, or the allowability of an implicit, ACKbe defined in the selected mode rather than being tied to the receipt of ANS (Answer Tone) or ANSam (ANS amplitudemodulated) as presently specified.
D.106 (M. Winseck, Ameritech, USA) proposes text for Section 8.3, NAK Signal. The section currently has notext. It also proposes a specific use of the NAK to reject a requested mode.
Ameritech indicated that Radish Communications holds IPR on V.8bis and would consider submitting the appropriatestatement. Microcom indicated that they may hold IPR and submitted TD-69 as the required statement.
TD-15 is a liaison from SG 8 that proposes changes to the CF tables in V.8bis in order to introduce Videotext as afull communication function. Two ways of accomplishing this are proposed and an additional CommunicationsCapabilities sub-field for Videotex is proposed to support Duplex (T.101, F.300, F.301), V.29 short train (T.104), andV.27ter (T.104).
TD-14 (G. Griffith, Rockwell, USA) is a liaison from SG 8 that raises four questions about the use of V.8 versusV.8bis.• Should OGM be mandatory?• Does V.8bis justify the additional delay required (one sec. plus round trip)?• When is V.8 used versus V.8bis?
• Definition of recovery mechanisms in V.8bis?SG 8 requests a response for their September Rapporteurs’ meetings.
TD-48 (V.8bis Rapporteur) is a collection of documents from SG 8. The last document attempts to analyze theinterworking scenarios for T.30 Annex D and V.8bis. The discussion that followed continued on the “voice centric”concept; however, there appears to be no common understanding of the meaning “voice centric.” The discussion thenwandered off into the possibility of eliminating V.8 when V.8bis is present. This drifted into a discussion of how codepoints are assigned in Recommendation V.8. It was clarified that this process would take place outside of the normalmeeting cycle.
TD-75 (V.8bis Rapporteur) contains test results (previously presented by Radish) demonstrating the resistance totalkoff of 2312.5 Hz and 2912.5 Hz frequency detectors. Various interfering signals were used; the results indicate thatdetectors tuned to frequencies in the 2000-3000 Hz band have high resistance to talkoff. During the discussion,Bellcore raised points about what they considered to be a misapplication of Bellcore data.
TD-30 (R. Schaphorst, Q2/15 Rapporteur) was presented by J. Magill (AT&T, USA). It is a liaison from SG 15encouraging the rapid approval of V.8bis. The “when to use” V.8 as opposed to V.8bis was once again brought up.
TD-12 (G. Griffith, Rockwell, USA) is a liaison from SG 8. It was not presented, but the Rapporteur called themeeting’s attention to it. The liaison was provided for information and addresses the use of V.8 facsimile. It currentlyhas full SG 8 approval.
TD-16 is a liaison from SG 8 on amendments to and the use of T.35, “Procedure for the Allocation of CCITT definedCodes for non-standard Facilities.”
The rest of the session was spent in a series of ad hoc meetings in which all open technical items were resolved. Itwas decided to define two new dual tones, one of which would begin the initiating and the other the responding ES, CRand MR sequences. All the changes were incorporated into a revision of draft Recommendation V.8bis (TD-105) andwas presented at the SG 14 plenary. When the vote was taken, the UK asked for a 6 week period of evaluation toprovide the necessary time to go over the changes made at this meeting. This was followed by a request from the U.S.for a 6 week evaluation, but the representative stated that this was with the understanding that if a NO vote wasreceived, the text of this draft recommendation was to be considered re-affirmed for consideration at the next SGmeeting. France then also added its request for 6 weeks.
Q1/14, V.GMUX
TD-83 (B. Pechey, Hayes, UK) is the Rapporteur’s report.
D.86 (C. Firth, Racal Datacom, UK) supports the basic LAP (Link Access Protocol) but with the added emphasis tocomplete a higher efficiency mode by the next meeting of the Study Group. It provides some criteria with which tojudge the relative benefits of the various proposals. The basic concept of this paper was accepted.
D.112 (L. Brown, Motorola, USA) proposes that the work proceed on the basis of LAP and that a more efficientmode of operation be put off for further study. This proposal was accepted. The text for V.gmux will be as presentedin COM 14-R 5-E (with minor editorial changes) except for the replacement of the current Appendix II with the textcontained in TD-44 (F. Burg, AT&T, USA, Editor). V.gmux was later determined for Resolution 1 at the StudyGroup 14 plenary.
Subsequently, there was a prolonged discussion about whether the text from V.42 would be included or just referenced.It was finally decided to include all of the relevant V.42 text within V.gmux so that it would be a “stand-alone”document.
Q2/14, DCE-DCE PROTOCOLS
TD-82 (W.L. Pechey Hayes UK) is the Rapporteur’s meeting report. The Rapporteur mentioned that Mr. Herrera(Royal PTT Netherlands) had been in contact with SG 7 about his scheme for data compression in X.25 networks.
TD-40 is a liaison from ISO/IEC JTC 1/SC 6. Pages 2-12 report on the latest work in ISO on HDLC. F. Burg(AT&T, USA) introduced pages 2-12. Section 2.5 and the attachments address the issue of the NWI (New Work Item)in ISO that will incorporate the work of Q2/14 on the compression of synchronous data into an ISO Standard. R-R.Damm (Deutsche Telekom) introduced Section 2.5, R. Brandt (AT&T, USA) introduced the attachments. It wasdecided to draft an amendment to V.42 for updating the latest HDLC work and to consider this at a future meeting.
One of the items referred to in TD-40 concerns Multi-Selective Reject (MSR) using span-list encoding. It had beenagreed several years ago to include MSR in V.42 (error control), but text was never included. F. Burg explained thatISO/IEC has implemented MSR and he agreed to create text to be included in the latest revision to V.42. The plan isto have the draft revisions to V.42 available for determination at the October WP meeting.
TD-42 (W.L. Pechey, Q2/14 Rapporteur) is the V.42ter “living list” document. TD-32 (W.L. Pechey, Q2/14Rapporteur) is the latest version of V.42ter (Enhancements to V.42). These documents were not presented.
TD-52 (K. Holtz, Omni, USA) is a patent statement from Omni Dimensional Networks claiming IPR on V.42bis(compression).
There was a short discussion about work underway that will add an Annex to Recommendation V.120 incorporatingRecommendation V.42bis XID negotiation procedures.
Q3/14, DCE FOR DIGITAL CIRCUITS
TD-97 (G. Sebek, France Telecom) is the Rapporteur’s report.
TD-6 is a liaison from SG 15 requesting the development of a new DCE for data signaling rates between 128 kbit/sand 2048 kbit/s. One transmission technique suggested may be based on HDSL. (Technical editor’s note: in the U.S.the related standardfor this work is TIA-547 (Network Circuit Terminating Equipment for DS1) . It is currently beingrevised under PN-2349 in TR-41.4.)
D.91 (E. Hode, France Telecom) supports TD-6 requesting a 2048 kbit/s DCE. France Telecom, with E. Hode aseditor, plans to bring a draft Recommendation for this DCE, referred to as V.2m, to the next meeting. TD-98 is aresponse to TD-6 stating that SG 14 will undertake this work.
D.90 (G. Sebek, France Telecom) contains a number of proposals for a revision of Recommendation V.38(48/56/64kbit/s DCE for point-to-point leased circuits). The most significant of these is the addition of an equipmentmanagement function. An appendix of G.797 (flexible multiplexer) which references Recommendation V.38 toprovide 64kbit/s and lower tail circuit connectivity was also provided.
The proposal to manage DCEs from the network was the subject of considerable discussion. The inclusion of themanagement function to this document was questioned. The addition of a defined back-up procedure was proposed, butit was later suggested that this might be better treated in a stand-alone Recommendation. It became clear that theseproposals need to be clarified; G. Sebek agreed to provide a revision of Recommendation V.38 reflecting these proposedchanges for consideration at the next meeting.
D.89 (G. Sebek, France Telecom, France) proposes the development of a new DCE for data signaling rates up to 144kbit/s created by inverse multiplexing. The Rapporteur proposed to submit a draft Recommendation of what he calledV.144k to the next meeting.
Q4/14, NETWORK MANAGEMENT
TD-106 (L. Brown, Motorola, USA) is the Rapporteur’s report.
D.121 (H.S. Jeon, Korea Telecom) proposes the addition of a Reset command in draft Recommendation V.58(Network Management) for the DCE in the event of a fault condition. This request is based on their experience withtheir PSPDN (HiNET-P) which includes 17,000 DCEs. The proposal was accepted subject to a definition of the statethe DCE would assume after being reset.
Q5/14, ISDN TERMINALS ADAPTERS
TD-61 (J. Moughton, Cray, UK) is the meeting report from the Rapporteur.
V.130 ISDN TERMINAL ADAPTER FRAMEWORK
TD-24 (J. Moughton, Rapporteur) proposes editorial changes to V.130 (V.taf), the ISDN Terminal AdapterFramework. It includes both editorial and content changes to reflect the changing status of theStandards/Recommendations that are referenced.
This draft Recommendation subsequently received unopposed approval under Resolution 1 at the Study Group meeting.COM 14-R 10-E contains draft Recommendation V.130 (V.taf), ISDN Terminal Adapter Framework, dated De-cember 1994. TD-87 contains the text of COM 14-R 10-E including modifications made at this meeting.
TD-45 is a review of the issues involved with the use of V.42bis data compression over V.120. This paper concludesthat the best way to add V.42bis parameter negotiation is to use the XID exchange mechanism already in V.42 ratherthan try to extend the existing Q.931-based mechanism.
An off-line group drafted a new Annex to Recommendation V.120 that would add V.42bis capabilities. The result ofthis activity is in TD-86 , which was subsequently determined for Resolution 1.
ATM EFFECT ON VOICE-BAND DATA
COM 14-R 3 Annex 1 contains the responses from SG 13 on the questions raised by SG 14 regarding the effect ofcell loss on data modem transmission and the SG 14 preference for compensated cell loss. TD-46 from the Q5Rapporteur reports on recent work in SG 13 and SG 15 on voice band data transmission issues. In the draft I.356 (B-ISDN ATM Layer Cell Transport Performance), simulation results are shown which indicate a cell delay variation,(64kbit/s connection) for 20 concatenated STN-1 (155 Mbit/s) with 95% utilization, of .96 ms (source AT&T SG 13D.589).
Q6/14, DTE-DCE INTERCHANGE CIRCUITS
TD-71 (R.R. Damm, Deutsche Telekom, Germany) is the Rapporteur’s report.
TD-40 is a group of liaisons from ISO/IEC JTC 1/SC 6. They address a variety of subjects including compression ofsynchronous data, the deletion of the directional commons in Recommendation V.24, the revision of ISO-2110, theproposed deletion of the 200 series interchange circuits from Recommendation V.25, the proposal for a joint technicalreport on standard HDLC-based data link layer protocols, and a new work item on interconnection between V.24 andX.21 interfaces. The draft joint technical report lists the standard data link layer protocols that utilize HDLC-basedclasses of procedures as defined in ISO/IEC 7809 in their realization for 6 protocols:• ISO 7776• ISO 8802-2 (LLC type 1)• ISO 8802-2 (LLC type 2)• ITU-T G.764• ITU-T Q.921/I.441 (LAPD)• ITU-T T.90 (LAPX).
TD-2, a liaison from SG 15, addresses the interface between a PC and a videotelephone. During the discussion, it wasunclear to the group what, in fact, was being requested in this liaison since it was marked for action. On initialreview, it seemed that all of the functionality required could be met by the existing V.24 circuit definitions. TD-73 isthe liaison response.
V.10 UNBALANCED ELECTRICAL INTERFACE
There were no contributions on this subject, but there was a short discussion. Both Germany and the U.S. indicatedthat they might have contributions addressing the changes necessary to Recommendation V.10 to reflect the deletion of102a and 102b.
V.12 (V.HSSI)
COM 14-R 7-E is the latest version of draft Recommendation V.12 (previously V.HSSI, electrical characteristicsfor data rates to 52 Mbit/s). There were no other contributions. However, it was noted that the complementary ISOstandard has already been published as ISO/IEC 13575. The draft Recommendation subsequently received unopposedapproval under Resolution 1.
FLOW CONTROL
There is a need for a technical report on this subject. In TD-40 (above), ISO/IEC JTC 1/SC 6/WG 3 stated their needfor additional material from SG 14 on flow control. The Rapporteur will generate a document on flow control for thenext meeting that could also be submitted to WG 3.
D.81 (F. Lucas, General DataComm, USA) proposes changes to V.11 and V.24 to delete references to V.35, as it nolonger exists. During discussion, it was pointed out that the action had already been taken on V.24. It was furthernoted that the same types of changes would be required in Recommendations V.36 and V.37. This was supported.
A rephrasing of the definition of cct. 102 in Rec. V.24 with respect to the present requirement for a provision of ametallic connection between circuit 102 and protective earth in the DCE was discussed. In TD-40 , a similarsuggestion is made. No decision was taken, pending a contribution from the U.S. suggesting an alternative way ofproviding electromagnetic compatibility.
TD-40 proposes the possible deletion of the 200-series circuits, and this had received some initial discussion inQ7/14. The Rapporteur pointed out that the work would have to be started with the deletion of reference to the parallelACU (automatic calling unit) interface in Recommendation V.25. Therefore, no action was proposed at this time.(See the Q7/14 report below for their action on this point.)
X.21/V.24 I NTERCHANGE CIRCUIT DEFINITIONS
This work will be done here (ITU-T SG 14 Q 6) but published as a Technical Report in ISO/IEC JTC 1/SC 6/WG 3.However, since no text was available, it resulted in only a short discussion at this meeting.
Q7/14, DTE-DCE PROTOCOLS
TD-103 (L. Brown, Motorola, USA) is the Rapporteur’s report. The main subject of discussion was the decision tobe taken on V.25ter. Draft Recommendation V.25ter, as contained in COM 14-R 8-E , has been stable. It had beenagreed that a registration procedure based upon the one used for V.8 would be developed; this had not been done.
TD-38 is a patent statement from General DataComm for Recommendation V.25ter.
TD-40 is a liaison from ISO/IEC JTC 1/SC 6/WG 3. Q7/14 addressed the part of the liaison that proposes thepossible elimination of the 200 series circuits (the parallel ACU interface). During the discussion, it was proposedthat the first step in the process would be the deletion of the text addressing the parallel interface. It is anticipated thata contribution will be forthcoming to the next meeting suggesting how to accomplish this.
All of the following documents (through D.113 ) were presented by J. Decuir (Microsoft, USA), the editor forV.25ter.
D.109 (D. Sevik, L.M. Ericsson, Sweden) draws attention to what is perceived as a flaw in V.25ter and proposes areformulation of the +MA parameter to separate the call mode and auto answer modes. It was decided that it is notnecessary to provide separate configurations for auto-answer and originate, since most of the modem software in usetoday reconfigures the modem before placing a call and since this proposal was viewed as “one more way of doingsomething” as opposed to “fixing a flaw.”
D.114 proposes editorial changes to V.25ter to correct editorial errors and bring it into conformity with the proposalsin Recommendation A.15 (ITU style guide). TD-49 is the revised text of V.25ter illustrating the proposedcorrections. There was a considerable discussion about how and what SG 14 would do in connection with theassignment of the + extensions. Other editorial corrections were also made as a result of input from this meeting.
TD-11 is a liaison from SG 8 addressing the use of V.34 for facsimile applications. It proposes that the DTE be thedriver of the negotiation, and requests that V.25ter be extended to accommodate this. D.116 proposes that V.25ter bemodified to accommodate this request by adding a new annex in time for the final meeting of SG 14 for this studyperiod (in March 1996). TD-51 illustrates this proposal. After some discussion, it was agreed that this additionshould be considered for determination at the fall WP 1/14 meeting.
D.113 (K. Krechmer, Ameritech, USA) proposes a methodology for handling the assignment of the + extensions. Itrequests the recognition of TIA TR-30.4 as the registration authority for the U.S. There was a considerable discussionabout a registration process. It was agreed that this process would only address the supplement to V.25ter.
D.119 (J. Decuir, Microsoft, USA) is an “ITU-ized” version of ANSI/TIA/EIA-617, In-band DCE Control. It waspresented as proposed draft Recommendation V.ib. Questions were raised about the need for the this type ofRecommendation, and the possible use of X.21 to accommodate this need.
TD-58 is a liaison from SG 15 introduced by J. Magill (AT&T, UK). It considers the possible use of extensions toRecommendation V.25ter to address the scenarios that are envisioned when multimedia terminals (specifically V.dsvd
modems) are being used. It was suggested that this work should be discussed in the SAVD Rapporteurs group to helpfocus the requirements. It was further clarified that this work has a lower priority in SG 15 than the other work onvideotelephony, and, therefore, the urgency was not great on this item.
D.115 , D.118 and TD-50 were presented together by J. Decuir (Microsoft, USA). They address the proposedsupplement to Recommendation V.25ter that provides information on other standards that reference V.25ter. D.118 isthe proposed supplement, D.115 suggests changes to the supplement, and TD-50 is the marked-up copy of thesupplement. TD-50rev was accepted as a base document.
D.117 is an overview of the work going on in the U.S. on what is referred to as Voice DCE (TIA IS-101) which isaimed at combining the functions of a telephone, a facsimile, and a modem in a PC/modem terminal. To accomplishthis, it provides a set of commands and responses to be used on the local interface between the DTE and DCE tocontrol such things as:• Recording and playback of digitized voice• Generation and detection of DTMF tones• Switching between voice, facsimile, and data and related functions.This document had previously been submitted to SG 8, which felt that it belonged in SG 14. Q7/14 agreed to considerthis work further.
TD-90 contains a revised draft of Recommendation V.25ter. It is the result of editing at this meeting including editsfrom D.114 that are shown in TD-49 and edits from the discussion.
OUTGOING LIAISON
TD-59 is a proposed liaison to SG 8 that provides an update on the work of Question 7/14. It reports the status ofV.25ter, V.8 control, and the registration process. It was approved.
Draft Recommendation V.25ter subsequently received unopposed approval for decision under Resolution 1 at the StudyGroup meeting. The attachment will be published along with the Recommendation after it receives confirmation.
Q8/14, USE OF MODEMS IN COMMUNICATIONS WITH THE HEARING IMPAIRED
TD-74 (R. Brandt, AT&T, USA) is the meeting report from the Rapporteur. It includes a set of block diagrams ofsupported scenarios for single mode and multimode terminals. These drawings were provisionally accepted as a re-placement for the existing drawings in draft Recommendation V.18. In general, it was agreed that multimode operationwould best be supported via V.8 or V.8bis.
COM-14-14 is a contribution from Sweden provided for input as part of Sweden’s ballot response on RecommendationV.18. It proposes text to correct errors and also proposes an new Appendix to provide a guide to V.18 implementers.The corrections were accepted as well as the concept and some of the proposed text for the annex. More contributionsare expected from Sweden (on the appendix) and from those working on initial implementations of V.18, so it wasdecided to delay determination until the October WP 1/14 meeting.
Q9/14, WIRELESS DCES
Q9/14 did not meet, as there were no contributions submitted. C. Firth (Racal Datacom ,UK) is the rapporteur.
Q10/14, MODEM TESTING
TD-84 (G. List, Austria) is the Rapporteur’s report.
This session was devoted to the correction of editorial errors discovered by the editor in his examination of draftRecommendation V.56bis. COM 14-R 9-E contains draft Recommendation V.56bis, Network Transmission Modelfor Evaluating Modem Performance over 2-Wire Voice Grade Connections, dated December 1994. TD-99 containsthe revised draft of Recommendation V.56bis. The main differences, all editorial, between these two drafts are referredto in TD-84 and are marked in TD-99 with underline (insertions) and strikeout (deletions).
Draft Recommendation V.56bis (TD-99) subsequently received unopposed approval for determination underResolution 1 at the Study Group meeting.
The U.S. promised to circulate a draft of the “test methodology” Recommendation prior to the next meeting. The goalis to have this determined for Resolution 1 at the October meeting, if possible.
WORKING PARTY 2/14
TD-67 and TD-81 are the first and second reports of WP 2 by the Chairman, B. Korop (Ukraine). TD-89 is thedraft list of questions for the next study period.
Q11/14, MODEMS FOR TELEGRAPH TDM SYSTEMS
F. Lucas (General DataComm, USA) is the Rapporteur.
R.21
R.21 is a proposed Recommendation for a 9600 bit/s modem standardized for use in the telegraph TDM system. Thesemodems (a form of discrete multitone) utilize a total of 71 carriers, a subset of which (63) are modulated at 39.34 baud.This produces a line signaling rate of 9914.753 bit/s which allows for single error correction. TD-77 (F. Lucas,Rapporteur) is the revised draft Recommendation R.21. The meeting proposed some amendments to the introduction,to Table 3/R21, to Figure 1/R.21 and added a new section 12 on testing facilities. These changes are incorporated inTD-77rev which was accepted with some editorial corrections.
R.22
R.22 is proposed Recommendation for an asynchronous or synchronous subscriber line or dedicated line modemoperating up to 19,200 bit/s using FDM FSK channels (subscriber transmit mark 95 kHz, space 105 kHz; exchangetransmit mark 50 kHz, space 60 kHz). TD-66 contains proposed editorial corrections to draft Recommendation R.22.TD-76 is the revised draft Recommendation R.22.
R.21 and R.22 were subsequently determined for Resolution 1 at the Study Group meeting.
Q12/14, MULDEXES AND STATISTICAL MULDEXES FOR TELEGRAPHY AND DATA TRANSMISSIONUSING DIGITAL BEARER CHANNELS
The Rapporteur for the X/V series (Q12) is G. Sebek (France Telecom, France). A muldex is a multiplexer-demultiplexer.
TD-7 is a liaison from SG 15 in response to a previous liaison from Q12/14 requesting their input on theenhancement of X.50, X.51, and X.58 and the flexible multiplexing Recommendation being studied under Q13/14.SG 15 indicated that their work was too far along to consider changes to the X.series at this time and that they alreadyhad a flexible multiplexer specified in Recommendation G.797.
Q13/14, TELEGRAPH TDM SYSTEMS FOR USE ON TELEPHONE-TYPE BEARER CIRCUITS
The Rapporteur for the R series (Q13) is I. Oussov (Ukraine).
TD-68 proposes editorial corrections to draft Recommendation R.106. These were accepted without any presentation.R.106 defines a muldex that is used to send telegraph signals and low speed data using TDM bit-interleaving with anaggregate bit rate higher than 4800 bit/s on analog telephone type circuits or higher order TDM systems.
Draft Recommendation R.106 was subsequently determined for Resolution 1 at the Study Group meeting.
K. Kern, Deutsche Bundespost Telekom, Germany SG 14 ChairR.P. Brandt, dB Consulting, USA SG 14 Vice Chair
TD-100 (plus supplements) is the list of 61 participants.
Ameritech Services Mike WinseckAmeritech Services Ken KrechmerAT&T Bill BettsAT&T Gordon BremerAT&T Mike BuckleyAT&T Fred BurgAT&T Alain GeorgesAT&T Ken KoAT&T John Magill (UK)AT&T Larry SmithAustria G. ListBellcore Wes HenryBrazil Marcus TschoepkeBritish Telecom plc (UK) John BrownlieChina Chi-Wen ChenChina Xun-Sen WuCray Comm. (UK) John MoughtonDenmark K. GraversenDeutsche Telekom (Germany) Klaus KernFrance G. LaveauFrance Telecom G. SebekFujitsu (Japan) H. MurataGDC Fred LucasGDC Yuri GoldsteinGermany Ralf-Rainer DammIBM A. SadriIndia P. MittalIntel Chris HansenIsrael Yair Be’eryItaly P. MorelloJapan Y. Tawara
KDD (Japan) T.SatohMatsushita (Japan) R. ShirahamaMicrocom Greg PearsonMicrosoft Joe DecuirMicrosoft Charlie GarthwaiteMotorola Les BrownMotorola Jack DouglasMotorola Jack MoranNEC (Japan) Y. AotaniNokia (Finland) P. HeinonenNTT (Japan) M. IidaOKI (Japan) T. ChigamaPenril Datability Networks Dick StuartPhillips (Netherlands) S. LozachRacal Datacom (UK) Chris FirthRockwell Glen GriffithRoyal PTT (Netherlands) M. HerreraRussia I. BelozerkovskySAT (France) P. CreveuilSiemens (Germany) Istvan SebestyenSyria N. KisrawiT.R.T. (France) B. ChardonTelia (Sweden) Gunnar HellstromUkraine Boris KoropUkraine I. OussovUnited Kingdom Bill PecheyU.S. Nick AndreU.S. Elaine BaskinU.S. J. HarkinsU.S. Andrea Saks
The next issue of Communications Standards Review – Telecommunications (Vol. 6 #5) is scheduled for July-August 1995.
REPORT OF TR-29, FACSIMILE SYSTEMS AND EQUIPMENTMAY 8 – 11, 1995, LEXINGTON, KY
TR-29 reviewed TR-29/88-02 , the scope statement for TR-29. They revised the scope of TR-29.2 from FacsimileDigital Interfaces to Facsimile Programmable Interfaces and moved the work on commercial facsimile privacy fromTR-29.4 to TR-29.1.
TR-29.1/95-05-27 is a response to G. Fereno (U.S. Dept. of State) from TR-29 on V.8bis. It was approved withminor edits as agreed at the TR-29.1 meeting. It notes that TR-29 defers to TR-30 on the issue of V.8bis operationand is interested in utilizing V.8bis when it is technically sound.
S. Urban (Delta Information Systems, Chair TR-29) reported on JPEG (Joint Photographics Experts Group). JPEGpart 3 includes variable quantizations (currently fixed quantization is supported in JPEG) and simple file formats forcompression. It is currently in DIS (Draft International Standard) ballot. S. Urban noted that eight companies aresubmitting new lossy and lossless algorithms for JBIG (Joint Binary Image Group) to the July 1995 ISO meeting inFrance.
K. Krechmer (ACTION Consulting) agreed to distribute the login information for the T.611 reflector to the TR-29reflector.
S. Urban (Delta Information Systems) noted that T1A1 is continuing work on facsimile interaction in voice networks.K. Krechmer provided T1A1’s technical report (T1A1.7/95-24 , COMSAT, AT&T, and Compression Telecom). Itnotes four factors that contribute significantly towards reducing call retention rates:• Delay in the network due to DCE (Data Circuit Terminating Equipment) and propagation• Echo in the network due to echo canceler getting re-enabled and/or slow convergence• Conformance of protocol implementation to ITU Recommendations• Ambiguity in interpretation of ITU-T T.30 RecommendationSome information in this paper is based on a test of G3 facsimile devices. TR-29 considers that the sample of devicesused includes a larger number of poor implementations than actually exists in the G3 installed base.
NSF CODES
TR-29/88-04 is the current list of NSF code users and codes. The unique code for TR-29 is 29 hex. In 1992, T.Nixon (who worked for Hayes at that time) presented a paper that proposed how the use of this code would be handled(TR-29/92-11-61). There was interest at the current meeting in reviewing this paper and developing it further.
CONFORMITY TEST PROCEDURES
M. Moldovan (Genoa Technologies) presented TR-29/95-02-05R1 , the second draft of Conformity Test Proceduresfor G3 Facsimile Devices (PN-3194). Testing is described at a functional level and does not represent a simplepass/fail test. It includes full coverage of T.30 fax protocol aspects for which there are tests specified in ETS 300 242.The test procedures apply only to the facsimile message coding and facsimile message exchange protocol. The feelingof TR-29 was to have this document represent basic testing and not cover more extensive tests (e.g., delay, echo, color,etc.).
It was unanimously decided to send PN-3194 out for a letter ballot. This would allow TR-29 to review the results ofthe letter ballot at the August meeting. The plan would then be to bring the edited letter ballot to the Rapporteursmeeting in September.
COLOR FAX
S. Urban (Delta Information Systems) noted that SG 8 has interest in a new proposal for a multiple plane JBIG thatcould support color and computer generated images.
TEST CHARTS AND TEST IMAGES
The beta version of T.24, Electronic test images for facsimile, was distributed on CD ROM by the TR-29 Chair.Comments are desired. IEEE publishes test charts as IEEE 167. The revision of 167 – to become 167-A – will usethe same high contrast figures as ITU Recommendation T.24.
Several old EIA/TIA standards are being reviewed. TIA-536 and TIA-537, which are early versions of Group 4standards, are to be rescinded under projects PN-3551 and PN-3552. TIA-538, an early U.S. version of T.6, is to berevised and updated under project PN-3553.
TR-29/95-05-025 is a liaison to TR-30 transferring the work in PN-3131 (IS-101-A, Voice Control) to TR-30.4.It was approved with minor edits.
TR-29/95-05-21 (J. Rafferty, Human Communications) proposes the opening of a configuration managementproject for Fax and MFP (Multi-Function Peripheral) devices. It proposes the development of profiles and is based oninterest emerging from DMTF (Desktop Management Task Force) for management of MFP devices. It was noted thatTR-30 has developed SNMP (Simple Network Management Protocol) MIBs (Managed Information Bases) for modems(V.58). It was also noted that this project could be very complex. J. Rafferty may be interested in editing this projectbut could not commit at this time. TR-29 agreed to work this project in TR-29.2, but a project statement needs to besubmitted before it is authorized.
J. Rafferty (Human Communications) presented TR-29/95-05-27 , the project request for facsimile routing in TR-29.1 which would replace IS-141. It was supported.
TR-29.1 FACSIMILE AND FILE TRANSFER PROTOCOLS
D. Duehren (Brooktrout Technology) was elected Chair of TR-29.1, replacing P. Bogosian (ThoughtCommunications).
L. Brown (Motorola) reported on the discussions of V.8bis in SG 8 and presented TR-29.1/95-05-23 , the currentdraft Recommendation of V.8bis. He noted that editing changes have occurred which are not included in this draft.Considerable discussion occurred on the details of the draft.
TR-29.1/95-05-25 and TR-29.1/95-05-26 are reports from SG 8 regarding the activities on fax security issues.It was agreed that TR-29.1 should open a project on security. S. Urban (Delta Information Systems) agreed to beeditor of this project.
EXTENDED NEGOTIATIONS
TR-29.1/95-05-24 (D. Duehren, Brooktrout) contains comments on TR-29.1/95-05-22 , the New FaxNegotiations Ad Hoc Meeting Report from SG 8 (J. Rafferty, Human Communications). An ad hoc group at TR-29worked on ideas for efficient coding of the negotiating mechanism. Currently, the feeling was that the negotiationmechanism should be independent of the physical layer (i.e., work via a half or full duplex connection and at data ratesas low as 300 bit/s). D. Duehren agreed to develop additional papers on the coding of the negotiation mechanisms.
J. Rafferty (Human Communications) presented TR-29.1/95-05-28 , Draft Recommendation T.routing. It is basedupon IS-141 and earlier papers (TR-29.1/95-02-04). This version, without the mark-ups, will be used as the basisfor a White contribution to SG 8 in 1996 for determination. At SG 8, it was agreed to not include reference inT.routing to the 20 character subfield length to allow future use of longer fields when allowed in T.30. Discussionnoted that Novell’s announced fax sub-addressing approach is based upon a different mechanism using the TSI(transmitting subscriber identification) field.
For information, J. Rafferty noted that the ICFA (International Computer Facsimile Association) is now part of theEMA (Electronic Messaging Association) computer fax committee. Support is increasing for T.611 in the U.S.There is interest in TR-29 presenting a paper to SG 8 supporting the use of object IDs. The use of object IDs for filetransfer work was proposed previously by R. Goldstein (First Télécom, France) in SG 8. Given EMA’s expandinginterest in object IDs, J. Rafferty agreed to develop the contribution.
Ken Krechmer, ACTION Consulting
TR-29.2 FACSIMILE PROGRAMMABLE INTERFACES
The Chair, J. Decuir, announced that he has served nearly seven years as Chair and indicated that he will resign soon.He solicited a volunteer to serve as Chair.
TR-29.2/95-05-21 is the future agenda of TR-29.2. The chair suggested that ITU work on Class 1 and Class 2 faxmodems will be completed this year and that Voice DCE work will move over to TR-30.4 and ITU SG 14. This
leaves Class 3 and other related MFPI (Multi-Function Peripheral Interface) work. No decisions were made. (Note:TR-29 assigned to TR-29.2 ITU Q1/8 issues such as T.610-series APIs.)
LIAISON REPORTS
K. Krechmer (ACTION Consulting) reported on the March Q1/8, Q20/8, and Q21/8 meetings:• Q1/8 has made editorial changes to T.611. They plan to include an implementer’s guide in the future. New work
is focusing on email, phone access, and security. New recommendations in progress include T.610 (overview),T.612 (run time Application Programming Interface, API) and T.613 (interactive API).
• Q20/8 work on PCI (Programming Communications Interfaces) architecture did not progress at the meeting sincethe time was allocated to Q21/8 to resolve difficulties.
• Q21/8 has developed ISDN APIs, the draft T.200-series recommendations, based upon the French and ETSI(European Telecom. Standards Institute) Applicom model. The Germans have been in the minority, pushing CAPI(Common API) and CAPI 2.0. ETSI has now adopted a dual stack approach, supporting CAPI 2.0. The Germansvoted No on the T.200 series, pushing ITU-T determination back to 1996 at the earliest.
TR-29.2/95-05-17 is J. Decuir’s report on the March ITU Q5/8 meeting in Geneva. Attention was directed toseveral items:• T.class1 was approved for ballot as T.31.• T.class2 was approved for ballot as T.32, including addition of JPEG support.• T.31 Annex B, extensions for V.34, was determined for resolution 1 ballot in February 1996.• T.32 Annex C, extensions for V.34, was determined for resolution 1 ballot in February 1996.• The Overview of MFPI was received with interest, and a full contribution was invited.• The complete contribution on Voice DCE was received with concern. They decided that it would be better for it to
be progressed in SG 14, in conjunction with DSVD (Digital Simultaneous Voice and Data) and Videophones.
There will be a SG 8 Q4, Q5, and Q19 Rapporteurs’ meeting September 18-22, in Palo Alto, CA, hosted by HewlettPackard.
TR-30.4, DTE-DCE PROTOCOLS
J. Decuir reported on the March meeting of TR-30.4. He explained to TR-30.4 SG 8’s response to Voice DCE (PN-3131). TR-30.4 agreed that, if and when TR-29.2 is ready, TR-30.4 is willing to progress the work. A summary ofPN-3131 was sent to SG 14 for their information.
ITU SG 14, Q7, DTE-DCE CONTROL
J. Decuir presented TR-29.2/95-05-18 , his report on the April ITU Q7/14 meeting in Geneva. L. Brown, Q7/14Rapporteur, also reported verbally. Attention was directed to several items:• V.25ter (AT Commands) was decided (as needed for T.31 and T.32).• A supplement to V.25ter was approved that describes related standards including all of the work of TR-29.2 and TR-
30.4. TD-50rev1 was distributed as TR-29.2/95-05-19 .• Annex A, V.25ter, for V.8 DCE control, was determined for resolution 1 in March 1996. This is based on work
drafted in the U.S. and in SG 8.• The summary of PN-3131 was accepted with interest, and a complete contribution was invited.
DESKTOP MANAGEMENT TASK FORCE (DMTF)
R. Lutz (Cognisys) reported on the work of the DMTF. There is an MIF (Managed Information Files) for Facsimileand MFP devices. It was noted that TR-30.4 has just completed work on a related item, an MIB (Management Infor-mation Base) for modems, and that this should be within the scope of TR-29. It was deferred to TR-29, where TR-29.2/95-05-21 (TR-29.2 future agenda) would be presented. (Note: TR-29 subsequently referred this issue back toTR-29.2.)
AMENDMENTS TO ITU T.31 FOR V.34
J. Decuir (Microsoft) presented draft Annex B/T.31, which is an attachment to TR-29.2/95-05-17 . He noted that ithad been accepted and determined for resolution 1 procedures. Therefore, it is essential that TR-29.2 study this care-fully and forward any necessary technical or editorial changes in time for the rapporteur’s meeting in September. Thepaper was received favorably with modifications. TR-29.2/95-05-24 contains a revised version of the draft. High-lights include:
• Support for new V.34 rates: 31,200 and 33,600 bit/s (determined for resolution 1 in SG 14)• Specifying that FCS (Frame Check Sequence) octets are included in data delivered by the DCE to the DTE (such as
+FRH)• Harmonizing all three +F34 subparameters so that value 0 is ‘no preference specified, set by DCE,’ and that 0 is the
default for each subparameter• Addressing V.34 retrains as well as V.34 rate renegotiations• For use on IEEE-1284 interfaces, DC1/DC3 transparency may not be necessary• How should “DCE initiate rate renegotiation” be handled?
Important open issues include:
• What is the persistence of +F34? What if it is written while +FCLASS<>1?• Should +F34 be merged in as parameters to +FTF and +FRF?
Some other minor technical and editorial changes were agreed upon. These are also summarized in TR-29.2/95-05-24 . A group consisting of J. Decuir (Microsoft), L. Brown (Motorola), C. Sneed (Rockwell), and S. Myers (Delrina)will discuss the open issues in preparation for the subsequent meeting.
It was noted that Annex B could apply to use with V.32bis as well, but the use of V.32bis in T.30 is not defined.This was referred to TR-29.1. Another issue for TR-29.1 is: What happens if there is inconsistency between featuresnegotiated in V.8 and in T.30?
SG 8 also drafted Annex C/T.31 to control V.8 features in a DCE. However, TR-30.4 and ITU SG 14 have agreed toassume this work and progress it in a timely manner as Annex A/ V.25ter. TR-29.2 decided to trust them to do so.
AMENDMENTS TO ITU T.32 FOR V.34
J. Decuir (Microsoft) distributed draft Annex C to T.32, plus an attachment, as TR-29.2/95-05-17 . It is muchsimpler than Annex B/T.31 because Class 2 DCEs hide most of the T.30 detail from the DTE. It was not discussed,but J. Decuir volunteered to produce a revised draft based upon the ideas raised in discussion of draft Annex B/T.31.This was done and distributed as TR-29.2/95-05-25 . Highlights of the changes include:
• Support for new V.34 rates: 31,200 and 33,600 bit/s• In sample sessions, replace CI (Call Indicator) by CNG (T.30 Calling Tone), as per Annex F/T.30
PN-3130, SERVICE CLASS 4 FAX MODEMS
No papers were submitted. A new editor is needed. The Chair requested a volunteer. R. Lutz (Cognisys) noted thatthe structure may have utility in Class 3 (PN-2725). J. Decuir (Microsoft) noted that some of the material has beenused in T.31, T.32, and draft Annex B/T.31.
PN-3131, VOICE DCE CONTROL, CLASS 8
The Voice DCE Control editor, C. Garthwaite (Microsoft), presented TR-29.2/94-05-31R3 (PN-3131, Project tocomplete IS-101, Facsimile Digital Interfaces -- Voice Control Standard for Asynchronous DCE). TR-29.2/94-05-31R3 contains markups for all recent changes. They were reviewed and accepted.
C. Garthwaite also presented TR-29.2/95-05-22 , which proposes items for an Informative Annex on items reservedfor further study. It notes the major areas for future work:• Alternatives to Serial Asynchronous Connection• Call Discrimination, Distinctive Ringing, Caller ID, DID, etc.• Non-Standard (Manufacturer specific) Feature Codepoint Registration• Levels of Service Definition, ‘How to’ versus ‘What to’ Implement Role• Voice Data Stream Format: Speech Compression Method, Silence Compression, Timing Marks
The ideas were accepted, although it was felt that the text needed simplification. Other open issues that were notedinclude:
• There may be a need for an event report for incoming V.8 CI signals, as distinct from V.25 CNG for fax or data. Itwas agreed to reserve code 35 for this.
• It may be desirable to establish codepoints for several other standard voice coding schemes, including the G.711 andG.720 series standards and the TIA TR-45 digital cellular voice coders. TR-29.2 agreed to reorganize Table 18(compression method list) to show ITU Recommendations, TIA Standards, and ETSI Standards in separate sections
from the manufacturer-specific sections. It was further agreed to include an Appendix where references to the voicecoders noted would be contained.
• Table 1 and/or Table 10 need more footnotes to indicate the references for the various signals. The ‘bong tone’ itemwas cited as an example. A cite reference is Bellcore “Notes on the Network.”
The Chair asked if this was ready to ballot, to replace IS-101. It was noted that TR-30.4 and TR-30.1 have only a fewmonths to prepare U.S. contributions to the WP 1/14 meeting in October, so they need this as soon as possible. Itwas noted and agreed that PN-3131 is considered stable, since the current changes have only been to codepoints.Therefore, TR-29.2 agreed to forward this project to TIA TR-30.4 (and ITU SG 14) without sending it out for ballot.A liaison was later drafted and processed in TR-29 (TR-29/95-05-25), and sent to TIA, TR-30, and TR-30.4. Theliaison includes the open issues listed in TR-29.2/95-05-22 , notes the need for renewal or replacement of IS-101 inSeptember 1995, and expresses TR-29.2’s interest in voting on the next version.
PN-3294, FACSIMILE DCE APPLICATIONS NOTES
A previous contribution to PN-3294, TR-29.2/94-08-57 , on ECM (Error Correction Mode) with small memory,was discussed. The editor, H. Silbiger (AT&T), was asked to draft PN-3294. H. Silbiger prepared an application note,TR-29.2/95-05-26 , that incorporates the ECM contribution.
J. Decuir (Microsoft) distributed the 1994 document TR-29.2/94-02-27 from B. Boykin (DataRace). It is acontribution to PN-3294 on various applications issues using Class 1. It will be renumbered and considered at thenext meeting.
PN-2725, SERVICE CLASS 3
Editor, R. Lutz (Cognisys), presented TR-29.2/95-05-023 , Multi-Function Peripheral Facsimile Interface (MFP-Fax) Information and Operation Overview. It is the same as TR-29.2/95-02-13 with the addition of commentsfrom M. Shiels (Delrina). It outlines the information required to be passed from Host to Peripheral to managefacsimile sessions at a “Class-3” level (basically a lower level interface designed to minimize the complexity of theDCE. The comments from M. Shiels (Delrina) generally suggest that capabilities be provided in Class 3 that allow anegotiated interface between the DTE and the DCE. This interface would be useful for network-attached devices. R.Lutz (Cognisys) noted that the market appears to be interested in a higher layer interface that supports theimplementation of a network-attached device that supports additional facilities for queuing and scheduling.
FUTURE MFPI
During discussion of PN-2725, it was noted that the most important new work in Multi-Function Peripheral Interfacesis, in priority order:
• A networked MFP interface• Completion of IS-650 (PN-1906, MFPI Level 1) as an ANSI/TIA standard• Completion of PN-2725
R. Lutz (Cognisys) noted that the networked interface could be derived from ISO/IEC 10175-1-1993, DocumentPrinting Application (DPA) - Part 1 Abstract-Service Definition & Procedure (implemented at MIT as the Paladiumprint system). This document defines a way of controlling a print server and could be extended to include facsimile.Many components could also be derived from the MFPI 2.0 specification, TR-29.2/94-01-09R3 . Projectstatements are needed for the first two items. R. Lutz agreed to request inputs from the Multi-Function Peripheral As-sociation (MFPA) at their meeting on May 11. MFPA is planning a conference in San Diego in September.
OTHER BUSINESS
TR-29.2/95-05-20 (also numbered as TR-30.4/95-03-031) is a working document for sections of PN-2989. Itwas distributed for information. It is the successor to IS-131 (PN-3320, Extensions to Serial AsynchronousAutomatic Dialing and Control), including new AT commands for call control, non-volatile storage, line control, andmodem testing. It was not discussed, and no action was taken.
R. Lutz noted that the IEEE-1284.3 committee is interested in posting IS-650 on their FTP (File Transfer Protocol)site. He was referred to TIA.
Joe Decuir, Microsoft
TR-29.3 AUDIOGRAPHICS CONFERENCING
The TR-29.3 meeting was abbreviated since, following the SG 8 meeting, little remained of high priority.
TR-29 SECURE FACSIMILE
TR-29.4 did not meet. Their next meeting is scheduled for June 5, 1995, in Washington, DC.
TR-29 PARTIAL MEETING ROSTER, MAY 8 – 11, 1995, LEXINGTON, KY
Steve Urban, Delta Information Systems TR-29 ChairDavid Duehren, Brooktrout TR-29.1 ChairJoe Decuir, Microsoft TR-29.2 ChairBruce DeGrasse, BJ Communications TR-29.3 ChairBob Robinson, Ilex Systems TR-29.4 Chair
ACTION Consulting Ken KrechmerAT&T Herman SilbigerBrooktrout Technology David DuehrenCirrus Logic Michael WytyshynCognisys, Inc. Raymond LutzDelrina Steve MeyerDelta Information Sys. Stephen UrbanHewlett Packard Salvador PlasenciaKonica Bus. Machines Rich HollowayLanier Worldwide Gary LucasMicrosoft Joe DecuirMicrosoft Charlie GarthwaiteMotorola ISG Les BrownNational Semiconductor Yuval ShacharOkidata Ching-Kay ChowOmnifax Larry EngmanRicoh Kumar KumarappanRockwell International Chris SneedSignals and Systems Haroon AlviSTF Technologies Steve MyersTIA Roberta BredenU.S. Dept of Defense George ConstantinouXerox Lloyd McIntyre--- Fred Killmeyer--- Ken McConnell
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.
ACK AcknowledgementADPCM Adaptive Differential PCMADSI Analog Display Services Interface (Bellcore)ADSL Asymmetric Digital Subscriber LoopAMPS Advanced Mobile Phone ServiceANSI American National Standards InstituteAPI Application Programming InterfaceASVD Analog SVDATM Asynchronous Transfer ModeAVD Alternating Voice DataBCH Bose, Chaudhuri, and HocquenghamCAMA Centralized Automatic Message AccountingCAWG Conformity Assessment Working Group (Trilateral)CD ROM Compact Disk Read Only MemoryCDMA Code Division Multiple AccessCELP Code Excited Linear PredictionCEPT Conference of European PTTsCF Center FrequenciesCI Call Indicator (V.8)CME Circuit Multiplication EquipmentCNG T.30 Calling ToneCO Central OfficeCPAP Customer Premises Access ProfileCPE Customer Premise EquipmentCPU Central Processing UnitCR Capabilities Request (see CL)CSR Communications Standards ReviewDAVIC Digital Audio-Visual CouncilDBS Direct Broadcast SatelliteDCE Data Circuit Terminating EquipmentDECT Digital European Cordless TelephoneDID Direct Inward DialingDMTF Desktop Management Task ForceDS1 1.544 Mbit/s T1 InterfaceDSVD Digital SVDDTE Data Terminal EquipmentDTMF Dual Tone Multi FrequencyEIA Electronic Industry AssociationEMC Electromagnetic CompatibilityES Escape SignalESD Electrostatic DischargeETSI European Telecom. Standards InstituteEU European UnionFCC Federal Communications Commission (U.S.)FDM Frequency Division MultiplexingFSK Frequency Shift KeyingFTP File Transfer ProtocolGSM Global System for Mobile communications (formerly Groupe Speciale Mobile)GSTN General Switched Telephone Network (e.g., PSTN)HDLC High Level Data Link ControlHDSL High-rate Digital Subscriber LoopH W HardwareIEC International Electrotechnical Comm.IEEE Institute of Electrical and Electronic EngineersIPR Intellectual Property RightsISDN Integrated Services Digital NetworkISO International Standards OrganizationITU International Telecommunications UnionJBIG Joint Binary Image GroupJPEG Joint Photographics Expert GroupLAPM Link Access Protocol Modem (V.42)LBC Low Bit rate Coder
LC Logic ChannelMCU Multipoint Control UnitMFP Multifunction PeripheralMFPI Multifunction Peripheral InterfaceMIB Management Information BaseMIPS Million Instructions Per SecondMLTS Multi-Line Telecommunications SystemsMM MultimodeMPEG Motion Picture Experts GroupMR Mode RequestMRA Mutual Recognition AgreementsMTM Mobile Test ModelMUX MultiplexerNAFTA North American Free Trade AgreementNAK Negative AcknowledgementNCTA National Cable Television AssociationNEXT Near End Cross TalkNIST National Institute of Standards and TechnologyNOM Mexican National StandardsNPRM Notice of Proposed Rule Making (FCC)NSF Non Standard FacilitiesNVLAP National Voluntary Laboratory Accreditation ProgramOCDMA Orthogonal CDMAOGM Out-Going MessageOPS Off Premise StationOSI Open System InterconnectionPACS Personal Access Communications System, Licensed BandPBX Private Branch ExchangePC Personal ComputerPCI Personal Communications InterfacePSPDN Packet Switched Public Data NetworkPSTN Public Switched Telephone NetworkPTT Public Telephone and TelegraphQAM Quadrature Amplitude ModulationQPSK Quadrature Phase Shift KeyingRAM Random Access MemoryREA Rural Electrification AssociationRF Radio FrequencyROM Read Only MemorySNMP Simple Network Management ProtocolSNR Signal to Noise RatioSS#5 Signaling System 5SVD Simultaneous Voice DataTAWG Terminal Attachment Working GroupTDM Time Division MultiplexingTDMA Time Division Multiple AccessTIA Telecommunications Industry AssociationUTP Unshielded Twisted PairV&V Validate and verifyVSB Vestigial Side BandWCPE Wireless CPEWG Working GroupWUPE Wireless User Premises Equipment (TR-41.6)XID eXchange IDentification
1995 MEETING SCHEDULES AS OF MAY 26. 1995Subject to Change without Notice
SG 15 Rapp May 31-Jun 6 JapanU.S. SG D Jun 1 Washington, DCTR-29.4 Jun 5 Washington, DCJTC(Air) Jun 5 - 9 Nashua, NHT1E1 Jun 5 - 9 New Jersey areaTR-45.2 Jun 5 - 9 Calgary, AlbT1S1 Jun 12 - 16 Washington, DC
areaTR-41 Jun 12 - 16 Kansas City, MOTR-45.3 Jun 12 - 16 Montreal, QueTR-45.5 Jun 12 - 16 San Diego, CATR-45.4 Jun 19 - 23 Durango, COSG15 LBC Jun 20 - 23 Boston, MATR-46 Jun 26 - 30 Vancouver, BCTR-30.4ah Jul 6 - 7 Irvine, CATR-30 Jul 10 - 14 Irvine, CATR-45.2 Jul 10 - 14 Montreal, QueQ3/8 Rapp Jul 17 - 21 Dublin, IrelandTR-45.3 Jul 17 - 21 Ottawa, OntTR-45.5 Jul 17 - 21 Quebec City, QueQ11/8 Rapp Jul 24 - 28 Tokyo, JapanTR-45.4 Jul 24 - 28 Montreal, QueTR-46 Jul 24 - 28 Calgary, AlbJTC(Air) Jul 31-Aug 4 ---T1P1 Jul 31-Aug 4 ---TR-29 Jul 31-Aug 3 Quebec City, QueQ10/8 Rapp Jul 31-Aug 3 Quebec City, QueSG14 Rapp Aug 7 - 11 Portland, ORT1A1 Aug 7 - 11 Boston, MATR-45.3 Aug 7 - 11 Dallas, TXTR-8 Aug 14 - 17 Detroit, MITR-45.2 Aug 14 - 18 Toronto, OntTR-45.3 Aug 14 - 18 Richardson TXTR-45.5 Aug 14 - 18 Vancouver, BCTR-41.6 Aug 15 - 17 ---T1E1 Aug 21 - 25 ---TR-45.4 Aug 21 - 25 Vancouver, BCTR-46 Aug 28-Sep 1 Monterey, CATR-45 Sep 4 Denver, COJTC(Air) Sep 11 - 15 ---TR-30 Sep 11 - 15 Portland, OR
TR-46 Oct 2 - 6 Orlando, FLTR-29 Oct 16 - 19 San Diego, CATR-45.2 Oct 16 - 20 Tampa, FLTR-45.3 Oct 16 - 20 Toronto, OntTR-45.5 Oct 16 - 20 Seattle, WASG 15 LBC Oct 17 - 20 Darmstadt, GermanyTR-45.4 Oct 30-Nov 3 San Francisco, CAJTC(Air) Nov 6 - 10 ---T1P1 Nov 6 - 10 ---TR-45.4 Nov 6 - 10 El Paso, TXTR-46 Nov 6 - 10 San Antonio, TXSG 15 Nov 13 - 24 GenevaT1E1 Nov 13 - 17 Orlando, FLTR-30 Nov 13 - 17 Orlando, FLTR-45.2 Nov 13 - 17 Colorado Springs,
COTR-45.3 Nov 13 - 17 Orlando, FLTR-45.5 Nov 13 - 17 Colorado Springs,
COTR-45 Nov 27 Dallas, TXT1S1 Dec 4 - 8 ---TR-41 Dec 4 - 8 Fort Meyers, FLTR-45.4 Dec 4 - 8 Orlando, FLTR-45.5 Dec 4 - 8 San Diego, CAT1A1 Dec 11 - 15 San Jose, CATR-45.2 Dec 11 - 15 Atlanta, GATR-45.3 Dec 11 - 15 Maui, HITR-46 Dec 18 - 22 Cancelled
