23.01.2013 Views

communications standards review - Linda Hall Library

communications standards review - Linda Hall Library

communications standards review - Linda Hall Library

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

COMMUNICATIONS STANDARDS<br />

REVIEW<br />

TELECOMMUNICATIONS<br />

Volume 9, Number 8 November-December 1998<br />

In This Issue<br />

The following reports of recent <strong>standards</strong> meetings represent the view of the reporter<br />

and are not official, authorized minutes of the meetings.<br />

ITU-T SG16, Multimedia, September 14 – 25, 1998, Geneva, Switzerland....................................................2<br />

WP 1 Report..........................................................................................................................5<br />

WP 2 Report..........................................................................................................................5<br />

WP 3 Report..........................................................................................................................6<br />

Q1/16 WP2, Audiovisual/Multimedia Services................................................................................6<br />

Q2/16 WP2, Interactive Multimedia Information Retrieval Services (MIRS)...........................................7<br />

Q3/16 WP2, Data Protocols for Multimedia Conferencing.................................................................7<br />

Q4/16 WP1, Modems for Switched Telephone Network and Telephone Type Leased Lines..........................9<br />

Q5/16 WP1, ISDN terminal adapters, and interworking of DTEs on ISDNs with DTEs on other networks........10<br />

Q6/16 WP1, DTE-DCE Interchange Circuits...................................................................................11<br />

Q7/16 WP1, DTE-DCE Interface Protocols.....................................................................................12<br />

Q8/16 WP1, DCE-DCE Protocols................................................................................................13<br />

Q9/16 WP1, Accessibility to Multimedia for People with Disabilities..................................................13<br />

Q10/16 WP1, Modem Testing....................................................................................................15<br />

Q11/16 WP2, Circuit Switched Network (CSN) multimedia systems and terminals....................................16<br />

Q12/16 WP2, B-ISDN Multimedia Systems and Terminals.................................................................18<br />

Q13/16 WP2, Packet Switched Multimedia Systems and Terminals.......................................................19<br />

Q14/16 WP2, Common Protocols, MCUs and Protocols for Interworking with H.300-series Terminals.........24<br />

Q15/16 WP3, Advanced Video Coding..........................................................................................26<br />

Q16/16 and Q17/16, Multimedia Harmonization and Coordination......................................................28<br />

Q18/16 WP1, Interaction of high-speed voiceband data systems with signal processing............................30<br />

Q19/16 WP3, Extension to existing ITU-T speech coding <strong>standards</strong> at bit rates below 16 kbit/s..................31<br />

Q20/16 WP3, Audio and Wideband Coding in Public Telecommunication Networks..................................32<br />

Q21/16 WP3, Encoding of Speech Signals at Bit Rates Around 4-kbit/s................................................35<br />

Q22/16 WP3, Software and Hardware Tools for Standardization of Speech and Audio Coding Algorithms........37<br />

Q23/16 WP1, PCM Modems......................................................................................................38<br />

Meeting Roster of Study Group 16, September 14 – 25, 1998, Geneva, Switzerland..................................49<br />

ETSI TM6 Access Transmission Systems On Metallic Cables, September 21 – 25, 1998, Vienna, Austria............43<br />

HDSL (High-rate Digital Subscriber Loop).....................................................................................44<br />

ANAI (Access Network Architecture and Interfaces)..........................................................................44<br />

SDSL...................................................................................................................................45<br />

ADSL..................................................................................................................................47<br />

VDSL..................................................................................................................................48<br />

Working Party 1/15, Network Access, October 12 – 23, 1998, Geneva, Switzerland.......................................51<br />

WP1/15 Recommendations Approved at SG15................................................................................51<br />

WP1/15 Recommendations Determined at SG15..............................................................................51<br />

Q1/15, Access Network Transport...............................................................................................51<br />

Q2/15, Characteristics of Optical Systems in Local Access Networks...................................................54<br />

Q3/15, DCEs for Digital Leased Circuits.......................................................................................55<br />

Q4/15, DCEs for Subscriber Access Systems..................................................................................55<br />

WP1/15 Partial Meeting Roster, October 12 – 23, 1998, Geneva, Switzerland........................................64<br />

Acronym Definitions.....................................................................................................................68<br />

1998 and 1999 Standards Committee Meeting Schedules.........................................................................71<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 1


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

REPORT OF ITU-T SG16, MULTIMEDIA, SEPTEMBER 14 – 25, 1998,<br />

GENEVA, SWITZERLAND<br />

APPROVED RECOMMENDATIONS OF SG16<br />

The following Recommendations, ordered by Recommendation, were approved by Resolution 1 (Decision) at this<br />

meeting.<br />

Q Decided Recommendation Document(s)<br />

Q19 G.729, Coding of speech at 8 kbit/s using conjugate-structure algebraic-code-excited COM 16-45 +<br />

linear-prediction, Annex C, Floating point<br />

TD-16(PLEN)<br />

Q19 G.729, Coding of speech at 8 kbit/s using conjugate-structure algebraic-code-excited<br />

linear-prediction, Annex D, 6.4 kbit/s extension<br />

TD-43(PLEN)©<br />

Q19 G.729, Coding of speech at 8 kbit/s using conjugate-structure algebraic-code-excited<br />

linear-prediction, Annex E, 12 kbit/s extension, 11.8-kbit/s CS-ACELP speech coding<br />

algorithm<br />

TD-44(PLEN)<br />

Q12 H.222.0|ISO/IEC 13818-1 Amendment 5, Information Technology -- Generic Coding of<br />

Moving Pictures and Associated Audio Information: Systems<br />

COM 16-67<br />

Q13 H.225.0 Annex I, H.263+ Video Packetization COM 16-70<br />

Q11 H.226, H.multilink, Channel Aggregation Protocol for Multilink Operation on Circuit<br />

Switched Networks<br />

COM 16-62<br />

Q14 H.245v4, Control Protocol for Multimedia Communication: Support for H.multilink COM 16-59<br />

Q12 H.247, H.bmultipoint, Multipoint Extensions for Broadband Audiovisual Communication<br />

Systems and Terminals<br />

COM 16-69<br />

Q12 H.310 Version 2, Broadband Audiovisual Communication Systems and Terminals COM 16-68, +<br />

TD-15(PLEN)<br />

Q13 H.323 Annex D, Real Time Facsimile over H.323 COM 16-60 +<br />

TD-54(PLEN)<br />

Q11 H.324 Annex F, v2, Multilink Operation COM 16-61<br />

Q13 H.332, H.323 Extended For Loosely-Coupled Conferences COM 16-41 +<br />

TD-14(PLEN)<br />

Q4 V.8bis revised, Procedures for the Identification and Selection of Common Modes of COM 16-63 +<br />

Operation Between Data Circuit-Terminating Equipment (DCEs) and Between Data<br />

Terminal Equipment (DTEs) over the Public Switched Telephone Network and on Leased<br />

Point-To-Point Telephone-Type Circuits<br />

TD-58(PLEN)<br />

Q23 V.90, A Digital Modem and Analogue Modem Pair For Use on the Public Switched COM 16-64 +<br />

Telephone Network (PSTN) at Data Signalling Rates of up to 56 000 bit/s Downstream<br />

and up to 33 600 bit/s Upstream<br />

TD-6(PLEN)<br />

Table 1. Recommendations Approved (Decided) at SG16, September 1998.<br />

DETERMINED RECOMMENDATIONS OF SG16<br />

The following recommendations, ordered by Recommendation, were Determined at this meeting. Determination is<br />

the first step of the approval process. Determined recommendations are expected to be proposed for approval at the<br />

next SG16 meeting (May, 1999).<br />

Q Determined Recommendation Document(s)<br />

Q1 F.700 Annex B.2, Communication task conferencing TD-50(PLEN)<br />

Q1 F.700 Annex C.1, Control and processing element Conference control TD-50(PLEN)<br />

Q19 G.728 Annex H Corrigendum, Variable Bit Rate TD-CELP Operation Mainly for DCME at<br />

Rates Less Than 16 kbit/s<br />

TD-49(PLEN)<br />

Q19 G.728, Annex I, Frame or Packet Loss Concealment for the LD-CELP Decoder TD-48(PLEN)<br />

Q11 H.221, revised, Frame structure for a 64 to 1920 kbit/s channel in audiovisual teleservices TD-23(PLEN)<br />

Q12 H.222.0|ISO/IEC 13818-1 Amendment 6, Information technology – generic coding of<br />

moving pictures and associated audio information: systems<br />

TD-30(PLEN)<br />

Q11 H.223, Annex D, Optional multiplexing protocol for low bit rate multimedia<br />

communication over highly error prone channel<br />

TD-37(PLEN)<br />

Q13 H.225.0 Annex G, Gatekeeper to Gatekeeper Communications (Communication between<br />

Administrative Domains)<br />

TD-61(PLEN)<br />

Q11 H.230, revised, Frame-synchronous control and indication signals for audiovisual systems TD-20(PLEN)<br />

2 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

Q11 H.242, revised, System for establishing communication between audiovisual terminals<br />

using digital channels up to 2 Mbit/s<br />

TD-22(PLEN)<br />

Q14 H.245v5, Control protocol for multimedia communication TD-39(PLEN) +<br />

TD-28(PLEN)<br />

Q15 H.262, Amendment #5: Generic coding of video, High level for the 4:2:2 profile TD-26(GEN)<br />

Q3 H.282 (ex V.RDC), Remote device control protocol for multimedia applications TD-24(PLEN)<br />

Q14 H.283, (ex H.RDC) - Remote Device Control – Specific for H series recommendations<br />

requirements<br />

TD-38(PLEN)©<br />

Q11 H.320, revised, Narrow band visual telephone systems and terminal equipment TD-21(PLEN)<br />

Q13 H.323 Annex E (Call Connection over UDP) TD-47(PLEN)<br />

Q13 H.323 Annex F (Single Use Terminal) TD-51(PLEN)<br />

Q14 H.341, (ex H.Media MIB) - Multimedia management information base TD-27(PLEN)©<br />

Q13 H.450.4, Call Hold supplementary service for H.323 TD-34(PLEN)<br />

Q13 H.450.5, Call Park and Call Pickup supplementary services for H.323 TD-35(PLEN)<br />

Q13 H.450.6, Call Waiting supplementary service for H.323 TD-36(PLEN)<br />

Q13 H.450.7, Message Waiting Indication supplementary service for H.323 TD-40(PLEN)<br />

Q3 T.123rev, Network specific data protocol stacks for multimedia conferencing TD-26(PLEN)©<br />

Q3 T.136 (ex T.RDC), Remote device control application protocol TD-25(PLEN)<br />

Q8 V.14 Corrigendum , Transmission of Start-Stop Characters over Asynchronous Bearer<br />

Channels<br />

TD-32(PLEN)<br />

Q23 V.91 (V.adm), A digital modem for use on a switched digital network at data signalling<br />

rates of up to 64000 bit/s.<br />

TD-72(PLEN)<br />

Q5 V.120 Corrigendum, Support by an ISDN of DTEs with V-series type interfaces with<br />

provision for statistical multiplexing.<br />

TD-53(PLEN)<br />

Q7 V.250 revised, Serial Asynchronous Automatic Dialing and Control TD-56(PLEN)<br />

ADDITIONAL APPROVALS<br />

Table 2. Recommendations Determined at SG16, September 1998.<br />

The following documents were also approved by the SG16 Plenary. Approval of these documents does not involve<br />

the full Resolution 1 procedures, which are required for Recommendations.<br />

Q Approvals Document(s)<br />

Q11 H.223 Implementor Guide, Multiplexing protocol for low bit rate multimedia<br />

TD-41(PLEN) +<br />

communication: Support of Annex C ((??))<br />

TD-55(PLEN)<br />

Q13 H.323 Implementors Guide for the ITU-T H.323, H.225.0, H.245, H.246, H.235, and<br />

H.450 Series Recommendations – Packet based multimedia communication systems<br />

TD-60(PLEN)<br />

Q11 H.324 Implementor Guide, Terminal for low bit rate Multimedia communication:<br />

Support of Annex D<br />

TD-29(PLEN)<br />

Q4 V.8 Addendum (additional codepoints), Procedures for Starting Sessions of Data<br />

Transmission over the PSTN<br />

TD-59(PLEN)<br />

Q4 V.17 Corrigendum (technical error), A 2-wire Modem for Facsimile<br />

Applications with Rates up to 14400 bit/s<br />

TD-33(PLEN)<br />

Q9 V.18 Appendix 3, Connection Procedures for Terminals Including V.18<br />

Functionality<br />

TD-73Corr(PLEN)<br />

Q9 V.18 Appendix 4, Specification of V.18 Implementation Tests TD-75(PLEN)<br />

Q9 V.18 Implementors Guide, Operational and Interworking Requirements for DCEs<br />

Operating in the Text Telephone Mode<br />

TD-74Corr(PLEN)<br />

Q23 V.90 Appendix, Typical Network Configuration TD-45(PLEN)<br />

Q7 V.250 Supplement, Serial Asynchronous Automatic Dialing and Control TD-57(PLEN)©<br />

Table 3. Additional Approvals at SG16, September 1998.<br />

SG16 GENERAL ISSUES<br />

SG16 has three Working Parties (WPs):<br />

WP Title Chair Mtg. Report<br />

WP1/16, Low Rate Systems J. Magill, Lucent (UK) TD-76(PLEN)<br />

WP2/16, Services & High Rate Systems F. Tosco, CSELT (Italy) TD-66(PLEN)<br />

WP3/16, Signal Processing S.F. Campos Neto, Comsat (US) TD-62(PLEN)<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 3


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

Questions 16/16 and 17/16 are under SG16, not associated with a specific Working Party.<br />

SOFTWARE COPYRIGHT ISSUES<br />

Background - February 1998 meeting of SG16<br />

At the February 1998 meeting of SG16, the subject of the ownership of software copyright arose in relation to<br />

speech coding Recommendations. In particular, G.729 Annex C was to be approved at that meeting, but during the<br />

SG16 plenary, Germany opposed approval, and requested a further four weeks to consider their position, as allowed<br />

by Resolution No. 1 procedures. They had concerns about the procedures being used for the release of the C-code<br />

prior to approval. The C-code was only released to ITU members wishing to evaluate the code and who had signed a<br />

Software Release Letter (SRL). In the case of G.729 Annex C, there had been further administrative errors and<br />

Germany had only received the final code during the meeting. However, Germany’s prime concern was that the<br />

copyright for the C-code included in the Annex was retained by the authors rather than being transferred to the ITU.<br />

In view of the difficulties arising at the SG16 meeting, the Chairman of WP3/16, S. Campos Neto, led an e-mail<br />

discussion group on this subject in the interim period between SG16 meetings.<br />

During the four week period after the meeting, Germany confirmed their objection and the approval of G.729 Annex<br />

C failed. Their stated reasons were:<br />

• The copyright of the C-code is retained by the authors;<br />

• The need for a Note saying that the definition of the Voice Activity Detection (VAD) is for further study;<br />

• The need for text clearly stating that the C-code takes precedence over the text.<br />

Interim Period<br />

Some exchange of e-mail took place during the interim period but no conclusion was reached. Germany confirmed<br />

their position. This was followed by views from France, the UK, the University of Sherbrooke/Sipro Labs, and PictureTel.<br />

These were broadly in line and proposed that the ITU have a copyright policy similar to the existing patent<br />

policy, i.e., authors would not be required to transfer the copyright to the ITU, but could license free or on fair,<br />

reasonable and non-discriminatory terms. During this period it also became clear that the subject would be addressed<br />

the ITU-T TSAG (Tele<strong>communications</strong> Standardization Advisory Group).<br />

Meeting of TSAG (Tele<strong>communications</strong> Standardization Advisory Group)<br />

There were contributions to TSAG from Germany, UK, France, and the USA. These were in line with the positions<br />

discussed above, with the USA also supporting a copyright policy similar to the patent policy. The issue was addressed<br />

by an ad-hoc group chaired by the Director of the ITU TSB, Dr. T. Irmer. There was considerable discussion,<br />

but no support for the German position. The ITU Legal Department confirmed that they did not require transfer of<br />

copyright, but only a license to copy, distribute, sell, etc., and indeed would prefer not have the copyright to avoid<br />

any possible legal implications. The conclusion was a first draft of an ITU copyright policy which permitted free<br />

licensing, and licensing on fair, reasonable and non-discriminatory terms (as for the patent policy), with the<br />

additional option of transfer of the copyright to the ITU. The policy also defined other obligations for the copyright<br />

holder, i.e., granting the ITU a royalty-free license to reproduce, publish, sell, and distribute the software; and<br />

granting users a free license for evaluation and test purposes; it was stated that the addition of other obligations was<br />

for further study. With this compromise in place, although it was recognized further work was required to complete<br />

the copyright policy, the Chairman of TSAG indicated his belief that there should now be no barrier to the approval<br />

of Recommendations because of copyright issues. This was endorsed by the TSAG meeting. TD-12(PLEN) is<br />

the report of the TSAG meetings on copyright and patents September 8 - 10, 1998.<br />

SG16 Plenary<br />

The approval of Recommendations, including G.729 Annexes C, D, and E, was considered at the SG16 opening<br />

Plenary session (September 15, 1998). The Recommendations were taken in Working Party order, thus the G.729<br />

annexes were at the end of the list (in WP 3). The French Administration was concerned that, despite the progress<br />

made at TSAG, the issue of copyright would still arise. They felt that it was not appropriate for SG16 to address,<br />

and would result in SG16 being inconsistent in its approach to the approval of Recommendations. As a result,<br />

when approval of the first Recommendation on the list was requested, France requested four weeks for further<br />

consideration, and noted that this applied to all Recommendations for approval. When approval of the G.729<br />

Annexes was requested, as expected by France, Germany requested delaying approval until the closing Plenary such<br />

that the TSAG compromise could be developed to define further obligations for copyright holders, i.e., the issue left<br />

for further study by TSAG. France strongly opposed this on the grounds that this was outside the scope of SG16<br />

considerations. After much debate, a compromise was reached in which words would be added to the Annexes stating<br />

simply that the issue of copyright for the C-code might be revised after TSAG had completed its work. On this<br />

basis, the Annexes were approved with France revoking its four week request for all the Recommendations.<br />

4 Vol. 9.8 Copyright © CSR 1998 November-December 1998


LIAISONS<br />

COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

The next SG13 plenary meeting will take place February 15-26, 1999 in Geneva.<br />

TSAG guidelines on interoperability experiments are provided in TD-10(PLEN). This is a draft supplement<br />

laying out how the administrative procedures for interoperability testing should be carried out on a per<br />

recommendation basis.<br />

PRESS OFFICER<br />

M. Buckley (Lucent Technologies, “elemedia” Business Unit) was appointed to the new post of Press Officer for<br />

SG16.<br />

NEXT SG16 MEETING<br />

Study Group 16 received an invitation from the University of Chile and the Chilean Administration to hold the next<br />

meeting of SG16 in Santiago, Chile, May 18-28, 1999. This will follow a Multimedia seminar at this location on<br />

May 17, 1999, which is World Tele<strong>communications</strong> Day.<br />

SG16 agreed to accept this invitation subject to confirmation being received by the SG16 management team that the<br />

necessary meeting facilities will be available. The Study Group also agreed that, as an exception, this meeting could<br />

take place in English without simultaneous translation into the other working languages. Translation into Spanish<br />

may be available during some sessions for the benefit of local attendees.<br />

If any problem arises such that the meeting in Chile cannot take place, the SG16 meeting will revert to the original<br />

dates, April 19-30, 1999, in Geneva.<br />

WP 1 REPORT<br />

The WP 1 report for this meeting is TD-76(PLEN). The WP 1 liaison statements are in TD-77(PLEN), the<br />

status report for WP 1 Recommendations in TD-78(PLEN), and a list of proposed WP 1 interim meetings is in<br />

TD-79(PLEN).<br />

REVISIONS TO QUESTIONS IN WP1/16<br />

The WP 1 Chairman (J. Magill, Lucent) pointed out the need to <strong>review</strong> the text of the Questions under study by<br />

WP1/16, considering the overlap in the studies of Q4/16 and Q23/16, and that some Questions received very few<br />

contributions. The following was proposed for consideration prior to the next SG16 meeting:<br />

• Combine all modem modulation issues in Q23/16, i.e., move the modulation study item from Q4/16 to Q23/16<br />

• Retain the other study items in Q4/16<br />

• Add to Q4/16 the responsibility for coordinating work on modem managed objects<br />

• Revise the titles of Q4/16 and Q23/16 accordingly<br />

Additionally, consideration should be given to whether the study of issues arising from the use of modems and ISDN<br />

TAs for connection to IP networks need to be added to Questions in WP1/16, and whether other existing Questions<br />

could be combined.<br />

WP 2 REPORT<br />

The WP 2 report of this meeting is contained in TD-66(PLEN), TD-67(PLEN) and TD-68(PLEN). TD-<br />

65(PLEN) is a list of documents composing the WP 2 report, TD-69(PLEN) are liaison statements, TD-<br />

70(PLEN) lists the WP 2 planned rapporteur meetings, and TD-71(PLEN) is the status report for WP 2<br />

Recommendations.<br />

WP 3 REPORT<br />

TD-62(PLEN) is the WP 3 report of this meeting; TD-63(WP3/16) lists the WP 3 liaison statements, and<br />

TD-64(WP3/16) is the WP 3 status report.<br />

AD-HOC GROUP ON TRUNKING/PACKETIZATION MATTERS<br />

A number of coded speech trunking and packetization activities are going on in different standard development<br />

organizations (SDOs); WP 3/16 established an ad-hoc group at this meeting to deal with the matter.<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 5


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

The trunking/packetization ad-hoc group’s main action was to <strong>review</strong> the text of I.TRUNK, AAL type 2 service<br />

specific convergence sublayer for trunking, (I.366.2 developed under Q5/13, see TD-2(WP3/16)), where a number<br />

of packetizations were checked, and the necessary definitions for G.729 Annexes D (6.4 kbit/s) and E (11.8 kbit/s)<br />

which were approved at this meeting were identified. The suggested changes were provided in a liaison statement to<br />

SG13.<br />

TD-31(WP2/16) from the ATM Forum, which includes BTD-SAA-RMOA-01.04, H.323 media transport over<br />

ATM, was <strong>review</strong>ed. This liaison also clarifies an earlier liaison from the ATM Forum. The ATM Forum’s<br />

method of transporting H.323 over ATM is intended to cover the typical scenario where the endpoints are on non-<br />

ATM IP networks as well as the scenario where the endpoints are on ATM networks. As this method is independent<br />

of the underlying network, it is the intention of the ATM Forum TC to not request any modifications to the H.245<br />

protocol.<br />

After <strong>review</strong> of TD-31(WP2/16), SG16 WG3 requested that a clarification be added in the opening paragraph of<br />

Annex A, Guidelines for choosing voice packet sizes, clarifying that the considerations in Annex A address efficiency<br />

aspects, which should be counterbalanced by the impact of packetization choice on the end-to-end delay. The group<br />

would also like to note that the packetization considerations could also be made for G.726 and G.727. Additionally,<br />

the embedded scheme available in G.727 could be efficiently used for network congestion control. TD-<br />

25(WP3/16) has the text of the proposed communication to the ATM Forum.<br />

Q1/16 WP2, AUDIOVISUAL/MULTIMEDIA SERVICES<br />

The Rapporteur of Q1/16 is Y. Robin-Champigneul (FT/CNET, France). The report of Q1/16 going into this<br />

meeting is TD-33(WP2/16). A rapporteur’s meeting is planned with Questions 16-17 in January 1999 in Tokyo.<br />

The ITU Reflector for Q1/16 is tsg16q1@itu.int<br />

RECOMMENDATION F.700 - FRAMEWORK RECOMMENDATION ON MULTIMEDIA SERVICES<br />

The list of control and processing elements (CPEs) was <strong>review</strong>ed and slightly amended. The example of CPE<br />

description on conference control provided in D.182© (Y. Robin-Champigneul, France Telecom) was accepted and<br />

will be added to F.700 as a new Annex C.1. Its structure will be used for other CPE descriptions. Annex B.2 on<br />

the communication task conferencing has been revised accordingly. Final versions which were Determined appear in<br />

TD-50(PLEN).<br />

Amendments to Sections 1 and 3 of F.700 will be drafted before the next meeting in order to include the CPEs in the<br />

reference model.<br />

Section 2 (application scripts) was <strong>review</strong>ed in the light of the amendments proposed in TD-24(WP2/16) (Y.<br />

Robin-Champigneul, France Telecom). The revised text of this Section is now complete and will be further<br />

discussed by correspondence if needed. The revised version of F.700 is planned for Determination at the next SG16<br />

meeting.<br />

Work on the Guide for Recommendation F.700 will be continued. Other CPEs descriptions will be drafted,<br />

beginning with Search control, Resource allocation, Call control and a CPE on security.<br />

DRAFT RECOMMENDATION F.MRS - MULTIMEDIA RETRIEVAL SERVICES<br />

The Editor for this recommendation has resigned because he is not able to attend the meetings any more. No other<br />

expert on retrieval services was present, so that the drafting is halted until a new editor can be found.<br />

APPLICATION SCRIPTS FOR MULTIMEDIA RETRIEVAL SERVICES<br />

The new application script provided by the Associate-Rapporteur was examined and accepted; it was decided to retain<br />

also the previous one because they are complementary.<br />

GII PROJECTS<br />

Question 1/16 will participate in the new GII Project M.3, Technical framework for electronic commerce, for which<br />

SG16 is now the lead SG. Electronic commerce is an application that mainly uses retrieval services. A document<br />

will be drafted describing the application. Its nature and relation to service descriptions will be decided later on.<br />

Question 1/16 will also participate in GII Project F.4, End-to-end interoperability, for which it is proposed to<br />

provide scenarios for interoperability of services and interoperability profiles.<br />

6 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

Additionally, the description of the CPE Conference control will be provided to GII Project M.4, Middleware for<br />

Multimedia, as a possible example of service-oriented middleware. See the Q16/17 report below for additional<br />

details.<br />

JOINT MEETING WITH QUESTION 9/16<br />

A joint meeting of Questions 1/16 and 9/16 examined the various cases of using multimedia conversational services<br />

for hearing impaired or visually impaired people. An application script will be drafted in order to show their<br />

particular needs. It will be taken into account in the drafting of the future Recommendation F.MCVS, Multimedia<br />

Conversational Services.<br />

Drafting of Recommendation F.MCVS - Multimedia Conversational Services, will start using the contents of<br />

Recommendation F.720 on the videotelephony service, and will take into account the script that will be provided by<br />

Question 9/16.<br />

Q2/16 WP2, INTERACTIVE MULTIMEDIA INFORMATION RETRIEVAL SERVICES (MIRS)<br />

The Q2/16 Rapporteur is M. Blaschitz (INFONOVA, Austria). No interim meetings are scheduled for Question 2.<br />

TD-83(WP2/16) is the Q2/16 meeting report.<br />

MODIFIED WORK PLAN FOR GII-PROJECT M.4<br />

TD-5(PLEN) is a report on the GII developments since the last SG16 meeting (see GII report above). A revised<br />

work plan was created which takes the middleware-related work of SG10 and SG13 into account and focuses on the<br />

areas which are not covered by these groups.<br />

Two liaisons (to Q24/13 and JRG on GII, SG10, SG13) noting the work in Q2/16 on the GII project M.4 were<br />

approved.<br />

MULTIMEDIA MIDDLEWARE<br />

TD-20(GEN) is a liaison from SG10 to JRG on GII and relevant SGs. It provides a detailed report on the<br />

middleware standardization activities in ITU-T SG4, SG7, SG10, SG13 and SG16 also ETSI, OMG (CORBA),<br />

ACTS, TINA-C, and EURESCOM.<br />

Q2/16 acknowledges the request, TD-19(GEN), from SG10 to focus on the definition of requirements for<br />

Multimedia Middleware. TD-42(PLEN) is a requirements document concerning the M.4 Project “Middleware for<br />

multimedia.” It is technically aligned with the DAVIC Specification 1.4 part 1 (Description of digital audio-visual<br />

functionalities, available at www.davic.org). It specifies required functions to implement different categories of<br />

multimedia systems supporting specific applications. It was approved to be sent as part of the liaison to JRG GII,<br />

SG10 and SG13.<br />

Q3/16 WP2, DATA PROTOCOLS FOR MULTIMEDIA CONFERENCING<br />

The Q3/16 Rapporteur is B. DeGrasse (DataBeam, USA). TD-56(WP2/16) is the agenda. TD-69(WP2/16) is<br />

the meeting report. Q3/16 plans to meet once in the interim, January 19-21, 1999 in California. TD-<br />

19(WP2/16) is the Q3/16 status report of the work since the last SG16 meeting.<br />

T.120 SECURITY REQUIREMENTS<br />

TD-25(WP2/16)©, Draft Rec. T.123, network-specific data protocol stacks for multimedia conferencing of the<br />

T.120- series of data protocols. The networks currently identified are:<br />

ISDN Integrated Services Digital Network<br />

CSDN Circuit Switched Data Network<br />

PSDN Packet Switched Data Network<br />

PSTN Public Switched Telephone Network<br />

B-ISDN Broadband ISDN<br />

LAN Local Area Network<br />

Communication profiles are specified which provide reliable point-to-point connections between a terminal and a<br />

multipoint control unit, between pairs of terminals, or between pairs of MCUs. In some cases, a lower protocol<br />

layer allows the multiplexing of audio, video signals in addition to data connections. In other cases, separate calls,<br />

over the same or a different network, may be established to carry audio or video signals.<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 7


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

In addition, Annex B of T.123rev (Extended transport connections) specifies a protocol (based on X.224.0) that may<br />

be used to negotiate connection devices beyond reliable data transfer (e.g., security options). This protocol also<br />

provides for the use of alias lists when making a connection. Alias lists will allow proxy services for T.120<br />

<strong>communications</strong> to be created and used.<br />

TD-44(WP2/16) (P. Murphy, DataBeam) contains proposed changes to the Annex B ASN.1 by importing ASN.1<br />

structures it shares with other protocols rather than replicating them. It was accepted.<br />

TD-45(WP2/16) (P. Murphy, DataBeam) contains a method for performing segmentation and reassembly for the<br />

unreliable PSTN profile described in section 8.2.2 of T.123rev Annex B. It was accepted.<br />

Q3/16 discussed additional security requirements for the T.120 series of recommendations. An ad hoc group met, and<br />

made recommendations. Q3/16 then proposed a three step, phased approach for addressing the security issues of<br />

T.120 series recommendations.<br />

Phase 1: Securing T.120 entities against outsiders attacking from the network. This first phase security provides<br />

security countering the most crucial network security threats. Phase one focuses on the lower T.120 communication<br />

layers (T.123) and attempts to provide at least some solutions in particular cases by using available security<br />

<strong>standards</strong> as appropriate for securing T.120 conferences (e.g., IETF’s Transport Layer Security Protocol TLS for<br />

unicast Internet IP). Thus, basic security is provided to protect T.120 conferences against intruders attacking a<br />

conference from the outside.<br />

Phase 2: Securing the T.120 infrastructure target (MCS, GCC and MAP) countering weaknesses within a node and<br />

inside a conference.<br />

Phase 3: Security for and within the T.120 applications and security against insider attackers (e.g., securing T.128).<br />

Contributions are requested.<br />

T.123rev was Determined as TD-26(PLEN)©.<br />

REMOTE DEVICE CONTROL<br />

D.207©, V.RDC (A. Woollett, ImageCom), describes the core services and protocol for performing configuration<br />

and control of a remote device during a multimedia conference. This recommendation does not specify the use of a<br />

particular transport protocol.<br />

D.208©, T.RDC (A. Woollett, ImageCom), describes how remote device control may be performed using T.120 as<br />

the transport protocol. The core remote device control services and protocol are described in D.207©.<br />

TD-22(WP2/16), H.RDC (M. Duckworth, PictureTel), describes how the core remote device control services<br />

work with systems using packet switched networks. It defines a new Data Link Protocol to carry Common RDC<br />

(that part of RDC common to both T.120 and H.323) within UDP over an H.245 logical channel.<br />

Q3/16 accepted D.207© and D.208© with minor editing changes and agreed to submit them for Determination.<br />

These draft recommendations with the agreed to editing changes were Determined as H.282, TD-24(PLEN)<br />

(V.RDC), and T.136, TD-25(PLEN) (T.RDC).<br />

BINTERMS CONSORTIUM PRESENTATION<br />

J. Korinthios (Teletel, Greece), on behalf of the BINTERMS Consortium, made a presentation about the activities<br />

carried out in the BINTERMS (Basic Interoperability of Terminals for Telematic Services) Project.<br />

This Project, supported by the European Union ISIS (Information Society Initiatives in Standardization) Program,<br />

validates key components of the T.120 protocol specifications for functional and syntactic completeness, using an<br />

SDL representation of the MCS (Multipoint Communication Service) and GCC (Generic Conference Control). It<br />

also produces detailed test specifications (ATS–Abstract Test Suite) for MCS and GCC, using TTCN (Tree and<br />

Tabular Combined Notation). The BINTERM web site (www.solinet.com/binterms) provides copies of the<br />

deliverables including a report of the T.120 aspects of unsuccessful and/or illegal behavior. TD-66(WP2/16)<br />

contains a draft liaison to the BINTERM project thanking them for their excellent presentation and their deliverables.<br />

Q3/16 members are asked to <strong>review</strong> the deliverables with the view to improving the current work.<br />

8 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

VIRTUAL MEETING ENHANCEMENTS<br />

No contributions were received on this issue.<br />

Q4/16 WP1, MODEMS FOR SWITCHED TELEPHONE NETWORK AND TELEPHONE TYPE LEASED<br />

LINES<br />

The Rapporteur for Q4/16, D. Stuart (3Com), had to leave the meeting early due to other work; L. Brown<br />

(Motorola), Rapporteur for Q23/16, agreed to chair the Q4/16 sessions.<br />

As D. Stuart is also Rapporteur for Q4/15 (DSL) which is a very active Question, he felt no longer able to continue<br />

as Rapporteur for Q4/16. WP1 agreed that B. Adams (Hayes, USA) would take over as Rapporteur for Q4/16. With<br />

the revisions to the scope of Q4/16 (see WP1 Report, above), it would include the responsibility for<br />

Recommendations V.8, V.8bis, V.70 and V.75, thus eliminating the need for the Associate Rapporteurs L. Brown<br />

and C. Hansen (Intel).<br />

L. Brown (Motorola ISG, USA) is the Q4/16 Associate Rapporteur for V.8 and V.8bis. The V.8-V.8bis agenda is<br />

TD-18(WP1/16). TD-16(WP1/16) is the report of the Red Bank, New Jersey, V.8/V.8bis interim Rapporteur<br />

meeting, May 1998. One interim Rapporteur’s meeting is planned for December 7-10, 1998 in California to<br />

progress the work on a draft Appendix to V.8bis on V.8/V.8bis interworking, and to progress the work on managed<br />

objects for modem diagnostics.<br />

REVISIONS TO V.8<br />

TD-2(WP1/16) is a liaison from SG8 requesting the assignment of a V.8 information category for their use,<br />

similar to the existing SG8 codepoint category in V.8bis. The group agreed to assign a new information category to<br />

SG8 for their use. The assignment of this new information category is included in an Addendum to V.8, TD-<br />

59(PLEN), that ws approved by the SG16 plenary. The liaison reply is in TD-60(WP1/16).<br />

REVISIONS TO V.8BIS<br />

Q4/16 held a joint meeting with Q9/16. See the Q9/16 report for further discussion. The group considered the<br />

following documents:<br />

D.153©, Comments on V.8 and V.8bis Related to V.18 (A. Farquharson, BT)<br />

TD-25(WP1/16), Proposals for Changing the Way V.18 uses V.8 and V.8bis (A. Farquharson, BT)<br />

TD-28(WP1/16), Modification Proposals to V.8bis COM 16-63 (G. Hellström, Q9/16 Rapporteur)<br />

TD-29(WP1/16), Use of V.8bis for Multifunction Terminals (G. Hellström, Q9/16 Rapporteur)<br />

As a result of discussion in the joint meeting, the group approved a minor clarifying editorial amendment to the draft<br />

of V.8bis (COM 16-63); it was approved (Decided) at the SG16 closing plenary. These amendments are detailed in<br />

TD-58(PLEN). The group also agreed to work on an Appendix for V.8bis describing interworking scenarios for<br />

multifunction devices that support V.8 and/or V.8bis.<br />

RECOMMENDATIONS V.70 AND V.75<br />

There were no contributions on this topic and no discussion. No interim meetings are required.<br />

MODEM MANAGED OBJECTS<br />

D.210© (F. Lucas, USA) proposes that SG16 define a set of managed objects for modem diagnostics, and asks under<br />

which Question the work should be progressed. The group agreed that this work should progress primarily under<br />

Q4/16. K. Chu (Rockwell, USA) was appointed as the editor for this work. D.198©, Managed Objects for Modem<br />

Diagnostics (K. Chu, Rockwell), provides an initial basis for discussion.<br />

V.17 CORRECTIONS<br />

D.218 points out two typographical errors in Recommendation V.17: one in Table 3 bridge signal/resync and one in<br />

para 3.7 circuit 109 off threshold. The group generated a corrigendum, in TD-33(PLEN). TD-54(WP1/16) is a<br />

liaison to SG8 informing them of the corrections to V.17. The corrections were approved by the SG16 plenary.<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 9


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

Q5/16 WP1, ISDN TERMINAL ADAPTERS, AND INTERWORKING OF DTES ON ISDNS WITH<br />

DTES ON OTHER NETWORKS<br />

The Q5/16 rapporteur is J. Moughton (Hayes, UK). TD-27(WP1/16) is the Q5/16 Agenda. The main activity of<br />

the meeting consisted of <strong>review</strong>ing the proposed revisions to V.110, which resulted from problems of interpretation<br />

of the existing text. In addition there was continued liaison with SGs 11 and 13 in order to maintain the alignment<br />

of various V-series Recommendations with those that are the responsibility of the other study groups. Also, it was<br />

agreed to update V.130 (ISDN terminal adaptor framework) to add information on interworking with DTEs on other<br />

networks, in particular those connected to PCM digital networks.<br />

TD-1(WP/1) is a liaison statement from SG13. It notes that the revisions requested by SG16 for Recs. I.460<br />

(ISDN user-network interfaces - Multiplexing, rate adaption and support of existing interfaces) and I.464 (ISDN usernetwork<br />

interfaces - Multiplexing, rate adaption and support of existing interfaces for restricted 64 kbit/s transfer<br />

capability) had been incorporated into the Recommendations which were Determined at the SG13 meeting in June<br />

1998.<br />

TD-11(GEN) is a liaison from SG11. SG11 had made some of the requested amendments to Q.931 (ISDN usernetwork<br />

interface layer 3 specification for basic call control). However, the request for new modem type code points<br />

had not been implemented, apparently due to the belief that new user rate code points (in short supply) were also<br />

needed. The meeting drafted TD-26(WP1/16) in reply.<br />

TD-26(WP1/16) explains that the addition to Q.931 of new modem type code points does not necessarily imply<br />

the addition of new user rate codepoints and so the present shortage of the latter need not delay the allocation of the<br />

former. It repeats the request for code points for V.32bis, V.18 and V.90 (analog and digital) modems.<br />

V.110 - PROPOSED REVISION<br />

V.110 is titled, Support of data terminal equipments with V-series type interfaces by an integrated services digital<br />

network. TD-8(WP1/16), V.24 control circuit handling in V.110-based products (J. Moughton, UK), discusses<br />

some problems that have been encountered (by Vodafone in the UK) in the interpretation of V.110, both in<br />

implementations and in derivative GSM <strong>standards</strong>. These problems cause unexpected and unwanted clearing of<br />

mobile data calls. TD-9(WP1/16), Draft revised Recommendation V.110 (J. Moughton, UK), is a proposed<br />

revised text of V.110 in which the areas of confusion are clarified. In order to allow members to examine the text<br />

and consider the impact on compatibility with existing equipment, it is proposed that Determination of any revisions<br />

should take place at the next meeting of SG16. In the interim, the work will be progressed by correspondence. In<br />

addition to the changes proposed in TD-9(WP1/16), it was suggested that the structure of the document should be<br />

brought more into line with current ITU-T practice.<br />

V.120 PROPOSED AMENDMENT<br />

Q5/16 accepted D.147© (D. Moughton, UK), a proposal that the lists of modem type and user rate code points in<br />

V.120 (Support by an ISDN of data terminal equipment with V-series type interfaces with provision for statistical<br />

multiplexing) should be replaced by references to Q.931, thus ensuring consistency with any future revisions of<br />

Q.931. The changes will be published as a corrigendum (TD-53(PLEN)). TD-53(PLEN) was Determined by<br />

SG16.<br />

V.130 PROPOSED REVISION<br />

Q5/16 agreed that V.130 should be revised to add information on interworking between DTEs attached to the ISDN<br />

and DTEs on other networks, in particular those connected to PCM digital networks.<br />

V.140 - ALIGNMENT OF FRENCH AND ENGLISH TEXTS<br />

The Rapporteur informed Q5/16 that the French text for V.140 (Procedures for establishing communication between<br />

two multiprotocol audiovisual terminals using digital channels at a multiple of 64 or 56 kbit/s) differed in some<br />

details from the original English text. The TSB has been notified and the errors in translation will be corrected.<br />

Q6/16 WP1, DTE-DCE INTERCHANGE CIRCUITS<br />

The Q6/16 Rapporteur is R.R. Damm (Deutsche Telekom, German). TD-20(WP1/16) is the agenda.<br />

Q6/16 and Q7/16 had been given permission to hold up to four interim meetings to define new interface<br />

Recommendations in support of the work on xDSL equipment under Q4/15. The Rapporteur for Q4/15 gave a<br />

10 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

verbal update on this issue to the WP1 Plenary. He thanked the Rapporteurs for Q6/16 and Q7/16 for attending the<br />

meetings of Q4/15, and reported that SG15 had concluded that no new interface Recommendations were required at<br />

this time. As a result no interim meetings of Q6/16 and Q7/16 took place.<br />

DTE-DCE INTERFACES FOR XDSL MODEMS<br />

The Rapporteur reported that he had participated in four Q4/15 Interim Meetings on behalf of Q6/16. He had<br />

submitted to Q4/15 a contribution summarizing candidate interfaces for xDSL equipment, but it was decided by the<br />

Q4/15 group not to reference any particular type of DTE-DCE interface in draft Recommendations G.lite and G.dmt.<br />

FUNCTIONAL DESCRIPTION OF INTERFACES<br />

D.172© (G. Sebek, France Telecom) expresses concern that the necessary functional description of adaptation<br />

functions associated with a number of increasingly used interfaces like G.703 (Physical/electrical characteristics of<br />

hierarchical digital interfaces, supporting PDH/SDH/ATM structures), G.703/G.704 (Synchronous frame structures<br />

used at 1544, 6312, 2048, 8488 and 44736 kbit/s hierarchical levels), 10BASE-T, 100BASE-T (ISO/IEC 8802-3),<br />

ATMF 25.6 are not dealt with in present ITU-T work. Such work should include, according to France Telecom:<br />

• Physical aspects<br />

• Functional aspects (including timing, control, protocol and maintenance requirements such as control of test<br />

loops)<br />

• Necessary primitives from/to core or transmission functions of the DCE<br />

• End-to-end aspects (e.g., Quality of Service [QoS] checking and report)<br />

It was further suggested that SG16 define an action plan to cover the necessary specification for a number of<br />

additional DTE-DCE interfaces like the ones mentioned above.<br />

Q6/16 feels that such work would involve not only SG16 but also other Study Groups, e.g., those dealing with<br />

QoS, and that some sort of coordination or supervision would be necessary. The discussion was inconclusive; it was<br />

noted that the contribution also addressed Questions 7/16 and 8/16. Further contributions were invited.<br />

REVISION OF RECOMMENDATION V.24<br />

D.167© and D.167 Amendment 1 (R.R. Damm, Deutsche Telekom) contain a proposal for a substantial revision of<br />

Recommendation V.24, including, among other things, the deletion of a number of interchange circuits, the addition<br />

of statements as to the sensitivity of control and indication circuits and a restructure of the Recommendation. One of<br />

the circuits proposed for deletion was cct. 128 (Received signal element timing [DTE source]). After a short<br />

discussion, it was decided that this be retained, and its definition be expanded so as to include its application for data<br />

flow control, specified in the new Recommendation V.43 (Data flow control).<br />

Given the amount of other changes, it was decided that the proposals be discussed in the National Standardization<br />

Bodies with the intention to Determine a revised Recommendation V.24 at the next meeting of SG16.<br />

J. P. Blin (France Telecom) suggested one new interchange circuit to be included in V.24, tentatively referred to as<br />

“Transmitted character timing (DTE source)”. One application of this circuit, for which there is already a need, is for<br />

video conferencing equipment. J.P. Blin envisaged a contribution from France Telecom to be submitted to the next<br />

meeting, wherein the requested functionality of the circuit would be specified. It was noted that<br />

• The definition of a complementary circuit, i.e., cct. 131 “Received character timing,” where the DCE is the<br />

source, already exists and has been in Recommendation V.24 for a long time,<br />

• It may be worthwhile to define one more complementary circuit, “Transmitted character timing (DCE source)” in<br />

order to be prepared for future needs,<br />

• The work should be completed at the next meeting of SG16 in order to be able to Determine a revised version of<br />

V.24 at that time.<br />

ADDITIONAL HIGHLIGHTS<br />

It was noted that a liaison statement requesting a similar circuit in Rec. X.24 (like the one requested by France<br />

Telecom) had been sent to SG7 from the last meeting of SG16, but that no response had been received. It was the<br />

feeling of the group that there might be no more experts on interfaces in SG7. The Rapporteur questioned whether it<br />

should be proposed to SG7 to transfer the responsibility for interface related X.-series Recommendations, i.e., X.20,<br />

X.20bis, X.21, X.21bis, X.24 and X.150 to Q6/16, so as to maintain maintenance of these Recommendations in<br />

future. There was support for the proposal and no objection.<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 11


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

Q7/16 WP1, DTE-DCE INTERFACE PROTOCOLS<br />

The Q7/16 Rapporteur is F. Lucas (3Com, USA). TD-10(WP1/16) is the Q7/16 agenda. Q7/16 had been<br />

authorized to hold four interim meetings with Q4/15 and Q6/16, to progress work on interfaces for xDSL DCEs.<br />

These meetings were not held after Q4/15 decided not to include specific DCE-DTE interfaces in their draft<br />

Recommendations (TD-3(WP1/16)).<br />

REVISION OF V.250 (EX V.25TER, AT COMMANDS)<br />

Q7/16 met jointly with Q9/16 to consider two contributions to Q7/16 which also concerned Q9/16. See also the Q9<br />

report for additional details. D.211© (R. Brandt, US) proposes the addition of a third variable, Initiate probing,<br />

under the probing_en subparameter in the +MV18S command. The joint meeting discussed this proposal and<br />

accepted it. D.211© also proposes the addition of a new +MV18PS command to provide for the storing of the V.18<br />

probing message. It was pointed out that the +MV18AM command is already used for this function. The group<br />

agreed that, since it was not obvious that this command is used for the probing message, clarification of the wording<br />

of the Description and Defined values were needed. In addition, the value of the +MV18AM parameter was changed<br />

from to for clarity. The specific changes to V.250 are found in TD-36(WP1/16).<br />

D.149©, V.250 Supplement - Summary of Dial Modifier Characters (J. Moughton, Hayes), points out that the S<br />

dial modifier, referred to in the +ASTO command, is not defined in V.250. TD-12(WP1/16) (F. Lucas, Q7/16<br />

Rapporteur) provides the text for the S dial modifier that was originally presented at the September 1997 WP 1/16<br />

meeting in Sunriver, OR. The group agreed to add this text to V.250. TD-12(WP1/16) also suggests a correction<br />

to the +MR command and clarifications to the +ASTO command. Both of these suggestions were accepted.<br />

D.168© (R.R. Damm, Deutsche Telekom) proposes to look at the basic commands in V.250 and consider<br />

new/replacement commands which conform to the format of the newer, more complex command structure. There<br />

was discussion both in favor of and against this proposal; no decision was taken at this time.<br />

The latest published version of V.250 is V.25ter (07/97) which includes Annex A. At the January - February, 1998,<br />

Study Group 16 meeting, it was agreed to renumber V.25ter as V.250 and Annex A (DTE control of V.8/V.8bis) as<br />

V.251. The group agreed that it was time to incorporate the existing V.25ter Implementor’s Guide into a new<br />

V.250 and include the additions and changes considered at this meeting. The changes to V.250 are found in TD-<br />

36(WP1/16). Revised V.250 was Determined as TD-56(PLEN).<br />

REVISION OF THE SUPPLEMENT TO V.250<br />

D.149© (J. Moughton, Hayes) suggests the inclusion of a table for dial modifiers in the Supplement to V.250. The<br />

group agreed to add the dial modifiers.<br />

D.150© (J. Moughton, Hayes) provides the AT commands which were recently adopted by ETSI SMG. It was<br />

agreed to add these commands to the other GSM commands contained in the Supplement to V.250.<br />

TD-32(WP1/16), Draft 3, Revision of the Supplement to V.250, contains revisions from D.149© and D.150©.<br />

One editorial change was made to correct the title of the +MV18AM command in 4.7 to V.18 Answering Message<br />

editing. With this change, the Supplement to V.250 was approved as TD-57(PLEN)©.<br />

V.25I ISDN TA COMMANDS<br />

No contributions were submitted for consideration on this new draft Recommendation. The group agreed that a<br />

thorough <strong>review</strong> of the first draft, which was presented at the January- February 1998 meeting of Study Group 16 (as<br />

D.134, J. Moughton, Hayes), was needed. Comments and contributions were solicited by the Rapporteur with the<br />

desire to have the draft ready for Determination at the 1999 meeting of Study Group 16.<br />

FUTURE INTERFACES<br />

D.172© (G. Sebek, France Telecom) suggests that Study Group 16 consider the development of new DTE-DCE<br />

interfaces which might be subsets of such existing interfaces as 10BASE-T, ATMF 25.6, etc. The group considered<br />

this proposal and concluded that, since contributions are the driving force for progressing work, future contributions<br />

could initiate work on a new interface protocol.<br />

Q8/16 WP1, DCE-DCE PROTOCOLS<br />

The Q8/16 Rapporteur is W. Pechey, (Hayes, UK). TD-31(WP1/16) is the agenda.<br />

12 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

TD-23(GEN) from ITU-R (Y. Nakata, Fuji Television Network) provides a tutorial on the use of computer<br />

technology in television broadcasting applications and the potential integration of PCs and TVs. It discusses<br />

receiving equipment, broadcasting services, current display technology (e.g., WebTV), APIs, ISDN, NTT Open<br />

Computer Network, FTTH, NTT Pi system and MPEG standardization activities.<br />

D.172© (G. Sebek, France Télécom) had been considered at length in the Q6/16 meeting. It was not entirely clear<br />

what Q8/16 could do to help with the proposed work although G. Sebek explained that, for example, there would be<br />

a need to provide a data channel for management purposes in conjunction with various new types of DCE. The<br />

Rapporteur expressed doubts that the group had the skills necessary but it was agreed to wait for more specific contributions<br />

on the topic and then re-assess the situation.<br />

D.148© (J. Moughton, UK) points out that Recommendation V.14 specifically limits its use to rates not greater<br />

than 19.2 kbit/s. This is inappropriate now that V.14 is used in V.34 modems and ISDN TAs. It was agreed to remove<br />

the two references to the maximum rate as proposed in D.148©. The Rapporteur agreed to draft a<br />

Corrigendum. TD-32(PLEN) was approved by WP1 and SG16.<br />

It was agreed that maintenance of Recommendation V.14 be included in the list of Recommendations which are the<br />

responsibility for Q8/16.<br />

Q9/16 WP1, ACCESSIBILITY TO MULTIMEDIA FOR PEOPLE WITH DISABILITIES<br />

The Q9/16 Rapporteur is G. Hellström (Sweden). Q9/16 met not only individually, but in many joint sessions with<br />

different groups. TD-50(WP1/15) is the Q9/16 report of this meeting.<br />

V.18<br />

A test specification for the V.18 text telephone interworking modems was accepted. The procedures for using V.8<br />

and V.8bis for initial start-up of a text telephone session were clarified and documented. That means that it is now<br />

easier to merge text telephony and other multimedia features. Minor corrections to V.18 are now documented in a<br />

V.18 implementer’s guide. Specification of text conversation through diverse multimedia systems have made<br />

progress. It was agreed to work on text through H.320 with Q11/16 and on H.323 with Q13/16.<br />

The following documents were submitted to and approved by the SG16 final plenary:<br />

TD-73Corr(PLEN), V.18 Appendix 3: Connection procedures for terminals including V.18 functionality<br />

TD-75(PLEN), V.18 Appendix 4: Specification of V.18 implementation tests. Based on D.144© from BT, this<br />

document contains a set of tests for verification of a V.18 implementation.<br />

TD-74Corr(PLEN), V.18 Implementer’s guide, contains a number of corrections to V.18.<br />

DRAFT DOCUMENT INTENDED TO BE AN H.263 SUPPLEMENT<br />

TD-35(GEN), Draft H.263 Supplement, Application Profile: Sign Language and Lip-reading real time<br />

conversation usage of low bitrate video communication (G. Hellström, Q9/16 Rapporteur), is an informative guide<br />

for implementers who want to make video communication systems usable for sign language and lip-reading. The<br />

document will be proposed for approval at the next Study Group 16 meeting.<br />

SERVICE DESCRIPTION FOR MULTIMEDIA CONVERSATION SERVICES<br />

The theme of F.700 type service definitions was discussed jointly with Q1/16. The concept seems useful and<br />

needed, and Q9/16 would like to see Q1/16 activities used to create service descriptions. TD-30(GEN) (G.<br />

Hellström, Q9/16 Rapporteur) is a brief prose description of Multi-modal conversation. It was presented as a<br />

starting point for the general multimedia conversation service including features that make it accessible and valuable<br />

to people with disabilities.<br />

Application scripts for disability specific applications was discussed. G. Kelley (US) took on the task to produce a<br />

first proposal before mid November.<br />

TEXT CONVERSATION IN H.320, H.323, H.324, T.120 AND MOBILE<br />

Mobile The Liaisons to ETSI and a US group on mobile data asking to include V.18 in the mobile services<br />

interworking units to enable harmonized and interworking mobile text services have not been answered. A further<br />

opportunity to promote V.18 exists at an ETSI SMG 4 meeting directly after the SG16 meeting.<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 13


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

The request for codepoint for V.18 in Q.931 mainly for mobile was answered negatively by SG11. Q5/16 handled<br />

the repetition of the request (TD-26(WP1/16)). H.324/M or H.323/M are feasible protocols for future mobile<br />

text conversation. These protocols can be used without video to give simultaneous text and voice.<br />

Q9/16 had the opportunity to describe to ETSI SMG what is needed to make UMTS (Universal Mobile<br />

Tele<strong>communications</strong> System) multimedia services accessible. A draft document was released that describes the<br />

requirements for successful application in the area of video communication for sign language and lip reading. It is<br />

called an application profile and is a joint action with Q15/16.<br />

In a meeting of ETSI SMG 1, 4, and 12, the Q9/16 Rapporteur presented an overview of accessibility to UMTS<br />

services, indicating a need and solutions for text conversation, video quality of service for sign language and lip<br />

reading, retrieval services with alternative presentation forms and call control procedures with alternative presentation<br />

forms.<br />

R. Cox (AT&T) presented a method to transmit data in the voice channel of mobile systems by using an extension<br />

to the audio coding packet. Q9/16 found it valuable to know that this opportunity exists if needed when designing<br />

the text conversation in mobile systems.<br />

H.320: A simple channel for text conversation is needed in H.320. Therefore, description of a channel for T.140<br />

text conversation through H.320 is now included in the plans of Q9/16 and Q11/16. Initial investigations indicate<br />

that a H.224-based channel seems suitable. See also the Q11/16 report, below.<br />

H.323: The modifications to H.245 already done for T.140 text conversation through H.324 makes a simple<br />

channel for text nearly ready through H.323. A description of the setup of the T.140 channel may be needed. This<br />

is to be taken into the plan for Q9/16.<br />

One item that may be the most important decision in the meeting was to start work on a simple IP text telephone<br />

for text and voice. That work is to take place in Q13/16 as an extension to work with a simple IP voice phone.<br />

TD-31(GEN) (G. Hellström, Q9/16 Rapporteur) proposes an IP text telephone to be included in the plans of<br />

Q13/16. It was accepted by Q13/16. TD-48(WP2/16) is Draft Annex F of H.323: Single Use Devices. It<br />

specifies a simple H.323 voice phone. A future expansion to a simple H.323 text and voice telephone is indicated in<br />

this document; the work will build on this document.<br />

V.8BIS PROCEDURES FOR H.324 AND V.18 IN MULTI -FUNCTION TERMINALS<br />

V.8bis contains unclear statements in sections 10.2.1 and 10.2.2 that can make it give up the V.8bis negotiation on<br />

first reception of a V.25 or V.8 signal that may come from a V.8bis-capable device. Such implementations of<br />

V.8bis must be avoided.<br />

D.153© (A. Farquharson, BT) brings up the question of how to start up the communication when both V.18 and, as<br />

an example, H.324 is available in the same terminal and the user can accept the call to be set up with any of them<br />

but prefers one. V.8bis is supposed to support function and capability negotiation. V.8 does not, and is therefore<br />

unsuitable. But some V.8 or V.25 signals must be transmitted and monitored so that connection also can take place<br />

when the other terminal does not support V.8bis.<br />

The topic was discussed with Q4/16, which took on the task to straighten up the sections in V.8bis, noting that it is<br />

necessary to try once with a V.8bis transaction even if a V.8 or V.25 signal has been received. An interworking<br />

guideline for V.8bis was agreed to be completed by Q4/16. V.18 usage of V.8bis is documented in V.18 Appendix<br />

3 (TD-73Corr(PLEN)).<br />

TD-25(WP1/16) (A. Farquharson, BT) proposes a new requirement on text telephony for V.18. The network may<br />

need to identify when the call is in text mode in order to give network information in text and to offer value added<br />

services. Strict use of V.8 and V.8bis signals might be a component to serve that need.<br />

The group agreed that the contents of V.18 Appendix 3 that specifies connection procedures for V.18 original, for<br />

V.8 and V.8bis first will be issued as a corrected Appendix 3 from this meeting (TD-73Corr(PLEN)), and then<br />

will be made normative in the next revision of V.18.<br />

V.250 DTE CONTROL OVER V.18<br />

D.211© (R. Brandt, USA) suggests two modifications to the DTE control commands for V.18 as specified in<br />

V.250. This request and a comment in TD-22(WP1/16) (G. Hellström, Q9/16 Rapporteur) was considered in a<br />

joint meeting with Q7/16.<br />

14 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

• Enter a command that starts probing. This was regarded as against the procedures and introduces a risk of<br />

connection in the wrong mode if it is used in the general case when answering, but can be of interest in a case<br />

when the V.18 already has been in the automode monitoring state and the user wants to test if there is a text<br />

phone at the other end. Therefore, the proposal was accepted with the addition that it must be made clear which<br />

of the +MV18S commands have immediate action and which are only mode-setting to influence the action of the<br />

A and D commands.<br />

• Command for modifying probe message. This is already in V.250, under the name of “+MV18AM . The lack of correlation between the terms “answer message”, and “probe message” is a source of<br />

confusion and the Q7 rapporteur edited V.250 for better clarity (TD-36(WP1/16)).<br />

T.134 TEXT CHAT APPLICATION ENTITY MAINTENANCE<br />

A few factors hinder wide uptake of T.134 as a general protocol for text conversation in all environments. T.120 is<br />

not foreseen to be an environment in small dedicated devices, where the inclusion of standardized text conversation is<br />

very important. T.134 is still important for the multi-point conference environment, but there is an apparent need to<br />

complement it with specific, simple procedures for channeling the T.140 text conversation in each multimedia<br />

environment.<br />

THE FUTURE VIDEO CODING<br />

H.26L requirements mention goals for sign language and lip-reading in many places. This is very satisfying from<br />

the Q9/16 perspective. Since the last meeting, a test scene with natural speed of signing and finger spelling called<br />

“Irene” has been entered and will be used by Q15/16 for tests during the H.26L work.<br />

VIDEO DELAY<br />

The video delay is one area where many of the current video communication implementations do not fully meet the<br />

needs of the hearing impaired. SG12 specifies an upper limit of 0.4 s end-to-end for usability in conversation. A<br />

delay model for documenting video coder delay is included in H.26L. Q9/16 would like to know whether this model<br />

also covers multiplexing and transmission to a suitable level of detail. If not, additions for such systems aspects<br />

would be needed. Q9/16 would also like to see an analysis of the opportunities to meet the delay requirements with<br />

a set of different situations and system protocols.<br />

Q10/16 WP1, MODEM TESTING<br />

The Q10/16 Rapporteur is G. List (Austria). An interim meeting is planned for December 7-10, 1998 in San Diego,<br />

California.<br />

D.197©, Telephone network transmission model for evaluating analog modem performance, was presented by L.<br />

Brown (Motorola). This document (draft 11 SP-3459), is on the way to become an ANSI/TIA/EIA standard,<br />

replacing TSB-37-A which in turn was the basis for V.56bis. It was forwarded to Q10/16 for consideration for<br />

revision of V.56bis. Because the network has continued to evolve towards an all-digital network, the updating of the<br />

network parameters was necessary. In the discussion, two major points were identified that could not be resolved<br />

within the group:<br />

• The internationalization of the inter-LATA and intra-LATA network model<br />

• Whether the international network model in V.56bis can be replaced by that in D.197©<br />

The group therefore proposes that, unless there will be contributions to updating the network model in V.56bis from<br />

an European, Asian, etc. point of view, D.197© will editorially be reworked to become a replacement for V.56bis.<br />

D.170© (L. Brown, US) is a draft of the North American Telephone Network Transmission Model for Evaluating<br />

PCM Modem Performance (PN-3857). As was true for D.197©, the related network model for testing PCM<br />

modems also needs input from other parts of the world. For such testing, questions of digital impairments (like the<br />

use of analog or digital pads in the switches, the use of RBS, a-law / µ-law conversion) need to be considered in<br />

detail as they have more influence on the performance of PCM modems than slight deviations of analog impairments<br />

in analog network models.<br />

Because contributions are needed for more accurately modeling networks in several regions of the world, the group<br />

agreed to split the future recommendation into a multi-part document with the principal network representations,<br />

simulation set up, necessary parameters and ranges in a baseline part; the detailed parameters will be dealt with in<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 15


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

normative annexes, so that at any time the Recommendation can be refined by adding other networks parameters as<br />

they become available.<br />

It was emphasized that the network model already has been revised in the US and a new contribution will be prepared<br />

for a future Q10/16 meeting. At any rate, D.170© shall be treated as a working text for drafting a new<br />

Recommendation on PCM modem testing.<br />

Q11/16 WP2, CIRCUIT SWITCHED NETWORK (CSN) MULTIMEDIA SYSTEMS AND TERMINALS<br />

The Q11/16 Rapporteur is T. Geary (Rockwell International, USA). TD-7(PLEN) provides the Q11/16 status at<br />

the start of this meeting. Q11/16 plans two interim Rapporteur meetings: November 17-20, 1998, in Torino, Italy<br />

(joint meeting with Q12, 13 and 14/16); and February 23-26, 1999 in New Jersey (joint meeting with Q12, 13, 14,<br />

and 15/16). Q11/16’s informal e-mail reflector is sg16.lbc@research.kpn.com. The Q11/16 meeting report is TD-<br />

86(WP2/16).<br />

The following two Recommendations were Decided at the SG16 opening plenary:<br />

• H.226 (H.multi-link), COM16-62<br />

• H.324 Annex Fv2 (multilink operation), COM16-61<br />

H.320 SYSTEMS: H.263V2 IN H.320<br />

To support H.263v2 (video codec) in the H.320 series Recommendations, the following revisions were Determined<br />

by SG16:<br />

Recommendation Original TD Final TD<br />

H.320 revised, Narrow band visual telephone systems and TD-34 TD-21<br />

terminal equipment<br />

(WP2/16) (PLEN)<br />

H.221 revised, Frame structure for a 64 to 1920 kbit/s channel in TD-35 TD-23<br />

audiovisual teleservices<br />

(WP2/16) (PLEN)<br />

H.230 revised, Frame-synchronous control and indication signals TD-36 TD-20<br />

for audiovisual systems<br />

(WP2/16) (PLEN)<br />

H.242 revised, System for establishing communication between TD-37 TD-22<br />

audiovisual terminals using digital channels up to 2 Mbit/s (WP2/16) (PLEN)<br />

OTHER H.320 SYSTEM ACTIVITY : ADDITION OF T.140 (T.CHAT) TO H.320<br />

It was suggested by the Q9/16 Rapporteur that T.140 be included in the current revision of H.320. An ad hoc was<br />

established to <strong>review</strong> the magnitude of this change and advise Q11/16 of the practicality of making this addition at<br />

this time. This group recommended the addition of a code point to H.224 (A Real Time Control for Simplex<br />

Applications using the H.221 LSD/HSD/MLP Channels). Contributions are expected at subsequent meetings. It<br />

was noted that a reference may be needed in the current revision of H.320 to the effect that support for T.140 is under<br />

study.<br />

H.324 SYSTEMS/MUX/MOBILE<br />

H.324 Implementors Guide<br />

TD-59(WP2/16), H.324 Implementors Guide in support of Annex D, Supplementary Services (T. Geary, Q11/16<br />

Rapporteur), was <strong>review</strong>ed and approved (as TD-29(PLEN)).<br />

H.223 Annex D Optional multiplexing protocol for low bit-rate multimedia mobile<br />

<strong>communications</strong> over high error rate channels<br />

TD-41(WP2/16), Draft H.223 Annex D (H. Tanaka, Toshiba, editor), was <strong>review</strong>ed and approved. The final text<br />

for the Annex appears in TD-37(PLEN). It was noted that this would require signaling in H.245; an ad hoc was<br />

established to define the needed code points. They were <strong>review</strong>ed and approved by the joint Q11-14 meeting. These<br />

additions appear in TD-37(PLEN), issued by the H.245v5 editor on behalf of the Q14/16 Rapporteur.<br />

H.223 Annex C Multiplexing protocol for low bit-rate multimedia mobile <strong>communications</strong><br />

over high error rate channels<br />

D.166© (T. Kawahara, Japan) presents a number of editorial errors noted in files for H.223 Annex C,<br />

36_e_64824.doc and td55.doc. The group obtained the latest text for H.223 Annex C from the TSB. Some of the<br />

noted errors still existed so an ad hoc was set up to prepare a corrigendum or H.223 Implementer’s Guide. The group<br />

16 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

reported that three of the sixteen items noted as editorial were agreed to be changed before H.223 Annex C is<br />

published. The group recommended that the remaining thirteen editorial items plus the two clarification items be<br />

included in an H.223 Implementer’s Guide (issued as TD-41(PLEN)).<br />

MPEG-4 in H.324<br />

D.206© (Y. Kikuchi, T. Kawahara, Japan) proposes changes and additions to H.245v5 in support of ISO 14496<br />

(MPEG-4). TD-22(GEN) is a liaison from MPEG to SG16 (it supersedes TD-10(GEN)). There was general<br />

discussion on the proposal. Upon <strong>review</strong> of the proposed H.245v5 code points, it was agreed that<br />

IS14496VisualProileAndLevel will be changed to “::CHOICE” - (was “::SEQUENCE”). With this change and the<br />

clarification that this would be added to H.245v5, the group accepted the proposal of D.206©. TD-28(PLEN) is<br />

the proposed revision. Q11/16 requested that Q14/16 add this functionality to proposed draft text for H.245v5. The<br />

Senior Editor of H.245 and proponent of D.217© (Object Oriented Approach to H.245 Extension, P. Cordell, BT),<br />

and the proponents of D.206© agreed to use the signaling defined in D.206© as a test case for the D.217© proposal<br />

and report the progress to the joint Q11-Q14 meeting.<br />

Mobile Terminals for IMT-2000<br />

D.163© (B. Wimmer, Siemens) proposes use of H.324/M terminals for IMT-2000. Participants asked if this was to<br />

be the only terminal identified for use in IMT-2000; it was stated that the proposal was not mandating H.324/M.<br />

Further work was called for on assessing and enhancing the capabilities of H.324/M mobile terminals. In particular<br />

there is a need for a good simulator of the H.324/M mobile mux. This work will continue in Q11/16 and further<br />

contributions are solicited. It was noted that TD-05(WP2/16), liaison from TG8/1 on suitability of H.323<br />

protocols for mobile services based on IP, also addresses this issue; it will be coordinated in the joint Q11-Q14<br />

meetings. It was agreed that a liaison to ITU-R TG8/1 ad SG11 were in order; this liaison is TD-72(WP2/16).<br />

JOINT Q11, Q12, Q13, Q14 AND Q15/16<br />

The status of the H.263++ video codec work was <strong>review</strong>ed with Q15/16. There was agreement that the next<br />

versions of video codecs should represent significant improvement over H.263v2 before they are standardized. The<br />

work should focus mainly on maintenance of current Recommendations rather than development of new<br />

Recommendations.<br />

Revision of H.245 (version 5)<br />

The group <strong>review</strong>ed the intended inputs from Q11/16 regarding addition of signaling for proposed H.223 Annex D<br />

and inclusion of MPEG-4 Visual Standard in H.324 as it will appear in H.245v5. The group agreed with the work.<br />

The Senior Editor for H.245 noted that the work in support of including MPEG-4 Visual Standard signaling in<br />

H.245v5 had revealed that more work may be required on D.217© (Object Oriented Approach to H.245 Extension,<br />

P. Cordell, BT); he recommended that D.217© not be included in H.245v4. It was agreed that the code points<br />

supporting MPEG-4 Visual Standard in H.245v5 would appear in ASN.1 notation for the purposes of approval at<br />

this meeting.<br />

Q11/16 AD-HOC GROUPS<br />

Q11/16 plans to continue the following ad-hoc groups:<br />

Committee Name Chairperson<br />

System/H.324 & H.320 M. Nasiri, Ericsson, Sweden<br />

Mobile B. Wimmer, Siemens, Germany<br />

Non-Conversational Services C. Quist, KPN, Netherlands<br />

H.263+ in H.320 Terminals S. Gupta, VTEL, USA<br />

Interoperability Experiments (for H.324M Mobile Terminals) M. Luomi, Nokia, Finland<br />

TD-17(WP2/16), Comments on MPEG-4 DMIF (Delivery Multimedia Integration Framework) is a liaison from<br />

MPEG. In response to a liaison from SG16 which raised concerns about the “architectural mixing” of H.323 and<br />

DMIF, MPEG has decided to remove all H series text from DMIF. Then DMIF will interact directly with ATM and<br />

IP and use its default signaling for all aspects related to end-to-end control.<br />

Q12/16 WP2, B-ISDN MULTIMEDIA SYSTEMS AND TERMINALS<br />

The Q12/16 Rapporteur is S. Okubo (Tele<strong>communications</strong> Advancement Organization of Japan). TD-<br />

47(WP2/16) is the meeting agenda. TD-27(WP2/16) is the Q12/16 status report at the start of this meeting.<br />

TD-28(WP2/16) is the report from the two interim Rapporteur meetings. K. Sakai (Fujitsu) was the Acting<br />

Rapporteur during the final plenary sessions of WP2/16 and SG16. Q12/16 will meet twice before the next SG16<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 17


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

meeting jointly with Q11/16, Q13/16, Q14/16 (and possibly Q15/16): November 17-20, 1998, Torino, Italy, and<br />

February 23-26, 1999, New Jersey, USA. TD-77(WP2/16) is the Q12/16 meeting report.<br />

DRAFT RECOMMENDATIONS FOR APPROVAL<br />

The following three Recommendations were approved (Decided) by SG16:<br />

• H.222.0|ISO/IEC 13818-1 Amendment 5: COM 16-67,Information Technology - Generic Coding of Moving<br />

Pictures and Associated Audio Information: Systems<br />

• H.310 Version 2: COM 16-68, Broadband audiovisual <strong>communications</strong> systems and terminals, with correction of<br />

typographical errors in TD-15(PLEN) (same as TD-18(WP2/16))<br />

• H.247 (H.bmultipoint): COM 16-69<br />

DRAFT RECOMMENDATIONS FOR DETERMINATION<br />

TD-26(WP2/16), draft H.222.0|ISO/IEC 13818-1 Amendment 6, was Determined as TD-30(PLEN). This<br />

amendment adds the splice parameters for 4:2:2 Profile @ High level and the buffer model for AAC (Advanced Audio<br />

Coding) audio. It supports synchronized approval between ITU-T and ISO/IEC JTC1.<br />

MPEG PACKETIZATION STUDY<br />

TD-39(WP2/16), Study on MPEG Stream Packetization (S. Okubo, Q12/16 Rapporteur), was recognized at the<br />

Cannes meeting in June 1998. This document gives some information regarding the media packetization work by<br />

other groups. In the IETF: RFC2250 RTP payload format for MPEG1/MPEG2 video and RFC2343 RTP payload<br />

format for bundled MPEG” (MPEG-2 video and audio in a packet). DAVIC is currently working on IP-based audiovisual<br />

systems whose specification are planned to be fixed in December 1998 as DAVIC 1.5. DAVIC 1.0-1.4<br />

address ATM and other QoS guaranteed networks. The Rapporteur encouraged members to provide further<br />

information of relevant activities outside SG16 and to discuss objectives of and requirements for this study.<br />

Related to this topic, two different formats for MPEG-2 storage were mentioned: ATM Forum and Bellcore<br />

specifications. Exact information is to be obtained; distinction between storage and transmission formats may be<br />

necessary.<br />

CLOCK SOURCE CONTROL<br />

TD-10(WP2/16), DSS2 protocol provision for carriage of adaptive timing recovery used for transmit (TX) clock<br />

information in the support of AAL5 carriage of voice, is a liaison from SG11-WP1/11-Q20.<br />

Q12/16 agreed to accept the use of Broadband Report Type IE instead of Notification Indicator IE for controlling<br />

transmission clock source, and confirmed that one way indication is sufficient without the need of acknowledgment.<br />

Q12/16 will issue an H.321 Implementers Guide to resolve the forward referencing as agreed at the last SG16<br />

meeting in January - February 1998. As H.310 refers to Annex C/H.321 in this respect, it requires no action.<br />

Q12/16 <strong>review</strong>ed the proposed text for Annex to Q.2931, comparing it with the corresponding wording in H.321,<br />

and produced suggested changes. It also recognized that specific code value for inclusion in the Implementors Guide<br />

are needed.<br />

TD-78(WP2/16) is a liaison reply to SG11 regarding the transmit clock.<br />

END STATION IDENTIFIERS OF H.310 AND H.321<br />

TD-11(WP2/16) is a Reply from SG11 to a liaison from Q12/16 on H.310 and H.321 End Station Identifiers in<br />

DSS2 draft Recommendation Q2941.2. Q12/16 welcomed the definition of End Station Identifier in projected<br />

Q2941.2. TD-79(WP2/16) is the liaison reply providing the exact references to H.321 and H.310 and a brief<br />

description of the End Station Identified for Clause 5.2 as requested.<br />

FUTURE DIRECTIONS<br />

Q12/16 <strong>review</strong>ed the current situation which indicates reduced interest in ATM-based systems, and felt that initiation<br />

of new study items needed input based on implementation of the basic set of Recommendations (H.310, H.321,<br />

H.247). However, incremental improvements to existing Recommendations are always welcome. Broadband<br />

supplementary services were mentioned as a possible future work item.<br />

18 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

At the joint Q11-14 session, the need for a study on the future system was identified. The future system may be<br />

built on any network and converge current H-series systems and terminals. This discussion was a continuation of<br />

the one opened at the previous SG16 meeting in January - February 1998.<br />

Q13/16 WP2, PACKET SWITCHED MULTIMEDIA SYSTEMS AND TERMINALS<br />

The Q13/16 Rapporteur is D. Skran (Ascend Communications, USA). TD-58(WP2/16) is the meeting agenda.<br />

TD-54(WP2/16) is the Q13/16 status report at the beginning of this meeting. TD-66(PLEN), the WP2/16<br />

report, includes the report of this meeting. Q13/16 will meet twice before the next SG16 meeting jointly with<br />

Q11/16, Q12/16, Q14/16 (and possibly Q15/16): November 17-20, 1998, Torino, Italy, and February 23-26, 1999,<br />

New Jersey, USA.<br />

REPORTS/LIAISONS<br />

An ATM Forum report was given by F. Audet (Nortel, US). It noted that the ATMF did not want to request<br />

modifications of H.245, and that they are focused on mixed environments (IP to ATM to IP). They requested<br />

clarification on deadlines for input, i.e., if H.245 will be Determined in April 1999.<br />

J. Ott (Teles) reported on the IETF. He will prepare a simple list of areas of overlap/ cooperation so that Q13/16<br />

can focus on issues. TD-29(GEN) (J. Magill, Lucent WP1 Chair) provides a catalog of the <strong>standards</strong> work in each<br />

organization involved in multimedia over IP (TIPHON, IETF, ISO/IEC, ATM Forum, DAVIC, IMTC, ECMA and<br />

other ITU SGs). TD-93(WP2/16) from the Rapporteur provides details on areas of overlap or complementary<br />

interest between Q13/16 and the IETF, noting the following working groups: MMUSIC, IPTEL, PINT, AVT<br />

(audio-visual transport) and two BOFs (“pre Working Groups”) SS7 and E.164. J. Ott was approved as the liaison<br />

rapporteur to the IETF.<br />

TD-14(GEN) is a liaison from SG15 regarding multimedia on ADSL. Q13/16 has decided to study the operation<br />

of H.323 over xDSL and cable modems; TD-62(WP2/16) is a reply liaison. Contributions on this topic are<br />

solicited.<br />

TD-18(GEN), Voice over IP Voice Quality (Nortel), is a liaison from Q18/12 providing E-model predicted voice<br />

quality. The short haul case (Internet now typical, end-to-end delay 200 ms and 2% packet loss) voice quality is estimated<br />

to be less than 70% Good-or-Better (high dissatisfaction). The equivalent future case (end-to-end delay 70 ms<br />

and 0% packet loss) voice quality is estimated to be less than 90% Good-or-Better (some dissatisfaction). The Emodel<br />

(voice quality estimation model) appears as G.107 from SG12. The attention of the delegates was called to<br />

this document as it is especially relevant to H.323.<br />

TD-5(WP2/16), Liaison Response on the Suitability of H.323 Terminals for Mobile Devices Based on IP, is<br />

from Task Group 8/1. TD-1(WP2/16), another liaison from TG8/1 on support of Mobile Multimedia services by<br />

IMT-2000, is related, but with H.324 substituted for H.323. This led to a debate between the advocates of H.323<br />

(and IP systems) vs. H.324 (and frame systems). Matters of efficiency and robustness were key in this discussion.<br />

TD-72(WP2/16) is the reply liaison, requesting information on the expected bit rate(s); it indicates that Q13/16,<br />

with the bit rate information, will study the issues and provide a report hopefully in time for the TG8/1 meeting<br />

which ends November 20. The report will include QoS, BER, bit rate, delay requirements, etc., and sharing of cells<br />

with other applications.<br />

TD-14(WP2/16), Proposal on GII Responsibilities regarding Integrated Management of Telecom Networks and IP<br />

Networks, is from SG4. A liaison will be prepared indicating that IP is managed via SNMP. The goal of unified<br />

management is important, but recognition of the existing SNMP must be recognized and they must<br />

interwork/manage it, including Q14/16 MIB work. TD-80(WP2/16) is the reply, sent jointly with<br />

Q11/Q12/Q13/Q14.<br />

H.323 IMPLEMENTERS GUIDE<br />

Changes to H.323, H.255.0, H.235, and H.450.x recommendations are all included in a single implementers guide<br />

so that implementors need look in only one place for all corrections to documents related to H.323.<br />

TD-6(WP2/16), Draft H.323 Implementors Guide V2 (J. Toga, Intel, Editor) was presented; it was noted that the<br />

ICV (Integrity Check Value) issue is unresolved and will not be included in this revision of the Implementors Guide.<br />

An intervention called attention to some additional concerns related to Master/Slave determinations. These will be<br />

considered for the next version of the implementors guide as consensus did not exist that the solution suggested was<br />

the correct one.<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 19


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

Another issue was raised concerning the need to clarify that multiple call proceedings can be sent (or not). It should<br />

be clarified that call proceeding can only be sent once in “pure (non-H.323)” Q.931. It was agreed that the usage of<br />

proceeding for fast start was a mistake, and Facility should be used. This will be put in the implementors guide<br />

with a note that the usage of proceeding was simply an error if it is used in the case where proceeding has already<br />

been sent. Fast Start will be added to the Facility message ASN.1. A further issue was raised on how long one<br />

should wait for a Fast Start element to get back to them. This was added to the implementors guide.<br />

It was mentioned that section 8.1.7 on the refusal of fast start was ambiguous. It was agreed that the Fast Start<br />

element is not in any and ALL messages.<br />

Further clarifications arose out of the Annex E (Call Connection over UDP) /Annex F (single use device) work; they<br />

are described in TD-91(WP2/16), and will be put toward the next version of the implementors guide.<br />

The H.323 Implementors Guide was approved as it appears in TD-60(PLEN).<br />

D.187© (T. Taylor, Canada) is a Clarification of H.323 Call Takedown Procedures. It notes three problems.<br />

1. Clearing of Call Signaling Channel by Gatekeeper: D.187© proposes to require that V3 Gatekeepers keep the<br />

channel open, or to send a new ReleaseCompleteReason to cover the situation when the channel is closed; neither<br />

proposal was accepted. It was agreed that additional text needs to be added to say that the channel can be re-opened<br />

later.<br />

2. Race Condition During Call Takedown: the point was accepted; Editor G. Thom (Delta Information Systems)<br />

will work with V. Kumar (Intel) to include it in the Implementors Guide.<br />

3. Proper Cleardown at the Transport Level: D.187© proposes a more graceful closing of TCP. Q13/16 will add<br />

to the implementors guide a reference to the appropriate RFC and a recommendation to use “graceful” shutdown<br />

rather than “Abort.”<br />

TD-60(WP2/16) (H.225 editor, G. Freundlich, Lucent) contains 14 editorial changes and minor corrections to the<br />

H.323v2 Implementer’s Guide. Each point was addressed, requiring multiple changes to the implementors guide<br />

draft.<br />

H.332<br />

H.332 (ex H.loosely coupled) was approved by the SG16 Plenary as COM-16-41 plus the single change (Session<br />

Description Protocol is RFC2327) in TD-14(PLEN). H.332 had not been Decided at the previous SG16 meeting<br />

as the RFC number to reference was not available.<br />

H.323 ANNEX D FOR REAL TIME FAX<br />

H.323 Annex D was presented as COM-16-60; various editorial changes were agreed. H.323 Annex D uses H.323<br />

procedures to transfer T.38 (real time fax) packets. T.38 Annex B describes a T.38-only-capable terminal that<br />

supports a subset of H.245 messages using H.245 tunneling. However, the T.38 Annex B terminal can interwork<br />

with an H.323 Annex D terminal using the H.323 Fast Connect (8.1.7) and Encapsulation of H.245 messages in<br />

Q.931 messages (8.2.1) procedures. H.323 Annex D was approved at the SG16 plenary. The changes appear as TD-<br />

70(WP2/16)©. The changes to be applied to COM-16-60 appear in TD-54(PLEN).<br />

TD-4(WP2/16), Liaison to SG16 on Draft Annex D to H.323, is from SG8. It presents a range of issues for<br />

resolution. The reply liaison is in TD-92(WP2/16), which was sent with the final text of H.323 Annex D<br />

attached. Although some complex issues were raised, TD-92(WP2/16) documents a compromise satisfactory to<br />

all.<br />

D.159© (D. Duehren, Brooktrout, US) proposes revisions to draft H.323 Annex D to Support T.38. The following<br />

were agreed:<br />

• In the H.323 options section, a reference would be added to T.38.<br />

• With regard to DTMF, RTP DTMF is removed, and will require tunneled H.245 in H.323 Annex D. This will<br />

also have to be done in T.38 Annex B.<br />

• It appears that the maxBitRate text from the previous liaison was lost by accident; the editor will add it back<br />

in.<br />

• The editor will adopt other changes such as removal of references to T.38 voice.<br />

20 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

D.212© (Eight Japanese companies) proposes Corrections to H.323 Annex D. The changes were accepted; the editor<br />

will make appropriate changes to indicate that the things specified (RTP/DTMF, non-fast start) don’t apply to<br />

interworking with T.38.<br />

D.213© (Eight Japanese companies) proposes TCP Support on H.323 Annex D. This document calls for TCP to<br />

be mandatory, with UDP optional, and makes suggestions for when each should be used. A compromise was<br />

adopted where TCP is mandatory in H.323 Annex D and UDP may be used as described in T.38.<br />

H.263+ (H.225.0 ANNEX I ) H.263+ VIDEO PACKETIZATION<br />

COM 16-70, H.225.0 Annex I, describes an RTP payload format for video data encoded according to the H.263v2<br />

(H.263+). This was approved without change.<br />

H.323 ANNEX F “SINGLE USE TERMINAL”<br />

TD-48(WP2/16) (J. Ott, Teles) is Draft H.323 Annex F, “Single Use Devices.” This document defines in<br />

particular Single Use Audio Devices that operate using H.323 protocols (are interoperable with H.323v2 devices) and<br />

are well suited for IP telephony applications. A number of changes were made including:<br />

• Fax is explicitly a possible future SUD<br />

• RTP DTMF was removed and H.245 tunneling inserted instead<br />

• H.323v3 will be modified to require support for Audio SUDs in MCUs and Gateways.<br />

TD-31(PLEN) is the initial text. It was <strong>review</strong>ed and replaced by TD-51(PLEN). This Annex was Determined.<br />

H.323 ANNEX E “CONNECTION OVER UDP”<br />

TD-46(WP2/16) (D. Gurle, VocalTec, editor) is H.323 Annex E, “Call Connection over UDP.” H.323v2<br />

introduces the concept of Fast Connect which allows media cut-through in as little as two round-trips from callee to<br />

caller (including TCP messages) and in 2.5 round-trips from caller to callee. Using UDP instead of TCP, this can be<br />

reduced to one round-trip and 1.5 round-trips, respectively. By adding slightly to the call setup procedure over UDP,<br />

a full range of call-signalling messages may be supported. This is especially important when using the Gatekeeper-<br />

Routed-Model. It was <strong>review</strong>ed, aligned with related work and modified. The first revision text appears in TD-<br />

19(PLEN). It was decided to put this document forward for Determination after further work. It was agreed that<br />

Section E.5 (specifics) would be an informative appendix and that new text would be provided prior to Decision.<br />

The final text for Determination appears as TD-47(PLEN). It was Determined.<br />

H.225.0V3 ANNEX G (GK TO GK COMMUNICATIONS)<br />

TD-42(WP2/16) (G. Freundlich, Lucent, Editor) is Draft H.255.0 Annex G - GK to GK Communication. This<br />

Annex describes <strong>communications</strong> between administrative domains in H.323 systems for the purpose of completing<br />

calls between the administrative domains. An administrative domain exposes itself to other administrative domains<br />

through a border, or edge, element. Annex G does not require an administrative domain to reveal details about its<br />

organization or architecture. Annex G does not mandate a specific system architecture within an administrative<br />

domain. Annex G supports the use of any call model (gatekeeper routed or direct endpoint).<br />

An extensive discussion was held and the following agreements reached:.<br />

a) It is a requirement to provide the endpoint type information to the caller, but this must be done in a scalable<br />

fashion, i.e., with some roll-up of endpoint type as in “here are 360,000 endpoints, they are all voice only.”<br />

Concern was expressed about duplicate listings of the same endpoint as a scaling problem.<br />

b) There will be push procedures, and they will be added using the Zone Update. These procedures will cover size of<br />

packets, number of templates that can be sent, and frequency of such updates.<br />

c) There are 3 kinds of mobility<br />

i) IP mobility – this will just happen, and is compatible with Annex G<br />

ii) H.323 address mobility – this may require some scheme of home GKs/foreign GKs<br />

iii) home environment mobility (future definition) [IP home environment & H.323 home environment]<br />

There is no need to make H.323 mobility a part of this determination.<br />

d) It is OK to call the zone request a zone request even though it sometimes does not describe a real zone.<br />

e) The scope of the document should reflect the requirements more but not limit the scope for all time. The focus of<br />

the scope is on address resolution. This would affect the title “Inter-Domain Relationships.”<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 21


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

f) Signaling is really in H.246.<br />

g) Multi-casting for usage with the inter-domain protocols will be <strong>review</strong>ed. This will be an option, as SLP<br />

(Service Location Protocol) is not very mature in the IETF. Multi-cast will be added as “for further study” and also<br />

based on proposals at the next experts’ meeting.<br />

i) The protocol is based on “rollup” and thus assumes non-random distribution. Thus, it is not reasonable to have<br />

“complete” freedom of number assignment in a non-clearinghouse environment. Of course, a universal number<br />

space can be provided by a clearing house, but this leads to issues related to the control of the clearing house. Thus<br />

the protocol will support both a fully flexible number scheme and non-fully flexible numbering scheme as chosen<br />

by the service provider.<br />

j) It was agreed to proceed with Annex G as SLP will not be sufficiently timely.<br />

k) Requirements for inter-zone<br />

i) predictable encoding size (not true for ASN.1)<br />

ii) very compact<br />

There were three proposals:<br />

i) templates in BER, with binary wrapper<br />

ii) binary wrapper, octet strings for templates<br />

iii) wrapper in BER, octet strings for templates<br />

The agreement is to propose that one of these three be chosen at the November experts’ meeting based on inputs.<br />

The protocol will be specified in ASN.1, then converted as needed when the white paper is issued.<br />

l) Future development of this annex will consider intra-domain (or GK to GK) <strong>communications</strong> and further develop<br />

this, either as part of this annex or as a new annex. The work may include specification of interface B (border<br />

element to gatekeeper) in Figure 1.<br />

D.164©, InterGK Communications with Distributed GK Architecture of Multiple Zones (R. Roy, AT&T), presents<br />

a method of extending H.323 to do address routing and caching.<br />

Text for Determination appears as TD-82(WP2), with a final version Determined as TD-61(PLEN).<br />

H.450.X IMPLEMENTORS GUIDE<br />

D.214 (Japan) provides editorial comments on Rec. H.450.1 (Generic Functional Protocol, QSIG based), H.450.2<br />

(Call Transfer), and H.450.3 (Call Diversion). All of these comments were accepted and will be put in the<br />

Implementors Guide, for version 2 of these Recommendations.<br />

H.450.4 (CALL HOLD)<br />

TD-49(WP2/16), “Call Hold Supplementary Service for H.323” (M. Korpi, Editor), notes that it appears that<br />

music on hold was always supplied; the text will be changed to indicate that music/video on hold may be supplied,<br />

but is not required. A number of other editorial comments were accepted. TD-34(PLEN) is the final text as<br />

Determined by SG16.<br />

H.450.5 (CALL PARK AND CALL PICKUP)<br />

TD-50(WP2/16) (M. Korpi, Editor) is draft Rec. H.450.5, Call Park and Call Pickup Supplementary Services for<br />

H.323. A number of changes were made. TD-35(PLEN) is the Determined text.<br />

H.450.6 (CALL WAITING)<br />

TD-51(WP2/16) (M. Korpi, Editor) is H.450.6, Call Waiting Supplementary Service for H.323.<br />

In section 5/7.1.1, mention is made of a subscription option; this needs to be explained as a local terminal<br />

configuration matter.<br />

G. Freundlich pointed out that if the GK knows that endpoint B does not provide supplementary services, the GK<br />

can provide the indications on the endpoint’s behalf; this will be added to section 7.3.<br />

These and other changes were made; TD-36(PLEN) is the Determined text.<br />

22 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

H.450.7(MESSAGE WAITING)<br />

TD-52(WP2/16) is H.450.7, Message Waiting Indication Supplementary Service for H.323. In section 7.5,<br />

procedures when the GK is not available to cache the messages need to be described. There are not any new<br />

messages needed, but some text was added. TD-40(PLEN) is the Determined text.<br />

H.450.8 (CALL IDENTIFICATION)<br />

TD-53(WP2/16) (G. Freundlich, Lucent, editor) is H.450.CallID, Call Identification Services for H.323. A<br />

discussion ensued, where it was held that not all of these features should be in H.450.x, and that perhaps this work<br />

should be split, with the number identification being part of the basic call, and the name being an H.450.x<br />

supplementary service. This work will continue toward modification of H.255.0v3, with focus on full ISDN<br />

transparency across H.323 networks.<br />

H.323 ANNEX I (H.323 OVER N-ISDN)<br />

D.171© (J.P. Blin, France Telecom) proposes H.323 draft Annex I, Point-to-Point H.323 Over ISDN. D.173©<br />

(J.P. Blin, France Telecom) proposes requirements for using H.323 on ISDN. See also the Q14/16 report below.<br />

The position of PictureTel was that H.323 terminals on ISDN should have a mandatory H.320 fall-back mode. The<br />

view was expressed that H.323 could and should be used over all network types. The main issue seemed to be<br />

whether it was necessary to standardize Annex I.<br />

Q13/16 considered this vision of universal usage of H.323, and breaking with H.320 over a period of time. It was<br />

suggested that this long term vision be considered part of the future work, especially toward a joint project for<br />

Questions 11, 12, 13, and 14/16. Among the ideas suggested for part of this work were:<br />

• A common upper layer, such as H.245, with different lower layers, perhaps as options.<br />

• A common core for all parts of the protocol that is tightly packed and can work well at a low bit rate, but with a<br />

set of layers that add quality up to much higher bit rates. This might include:<br />

– A layered audio coder<br />

– A layered video coder (possibly H.263+)<br />

– A layered control system<br />

The key idea in this approach is rather than creating a series of systems targeted at different transports, instead a<br />

single system would be designed to work over all transport systems and bit rates, including xDSL and cable<br />

modems. This work might replace or become H.24L.<br />

Although general enthusiasm was expressed for this idea, and it will be added to the work program, some voices<br />

urged caution given the number of new terminals that have been introduced by the ITU-T over the last five years.<br />

Contributions on this topic are solicited. The Q11/12/13/14 rapporteurs met with S. Campos Neto (WP3/16 chair)<br />

on this topic (layered audio/video coders) and conveyed the desire of the relevant Questions to work with WP3 on<br />

this new project.<br />

Annex I of H.323 was not brought forward for Determination due to the lack of consensus.<br />

D.156©, Comments on the Projected Annex/Appendix for H.323 over N-ISDN (H. Harasaki, NEC), examines the<br />

various options for interworking among current H.323 terminal types.<br />

H.323V3<br />

D.160© (USA) proposes the study of highly available H.323 networks. That is, how can H.323 networks recover<br />

when a gatekeeper and gateway (possibly supporting many active calls) fails. It was agreed that considerations of<br />

reliability, load balancing, and duplication are within the scope of Q13/16 insofar as they are reflected in the protocol<br />

itself. The rapporteur cautioned that although this was a worthy goal for H.323v3, the protocol should not become<br />

too burdensome, especially on a simple endpoint.<br />

TD-8(WP2/16), Use of High Layer Information (HLI) Information Element (SG11/Q20) seeks to correct the<br />

usage in H.323 Annex C of the BHLI (Broadband HLI), and contains a proposal for using the Generic identifier<br />

transport (GIT) information element. It was agreed that using the GIT was the appropriate way forward, but that a<br />

“pre-GIT” ATM system would require some special methods such as user-to-user information. This change will be<br />

made in H.323v3 and in the H.323 implementors guide. H.323v2 to H.323v3 interoperability will have to be taken<br />

into account. The new text will be sent to SG11 and the ATM Forum. TD-76(WP2/16) is the proposed reply<br />

liaison. This was re-written; TD-88(WP2/16) is the final liaison.<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 23


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

TD-31(WP2/16), H.323 Media Transport over ATM (P.A. Probst, ATM Forum), contains a proposal for a new<br />

ATM Forum recommendation for carrying H.323 over ATM networks, especially in the context of IP to ATM to IP<br />

networks. It proposes a new type of gateway, an H.323 to H.323 “gateway” which does not affect the media stream,<br />

but does affect the control stream. It was noted that Figure 2-2 is very similar to Annex C, and could be adopted<br />

into Annex C. It is the intent of Q13/16 to adopt some of these ideas to enhanced Annex C to H.323v3. TD-<br />

87(WP2/16) is the response to the ATM Forum.<br />

TD-39(WP2/16) is a report from Q12/16 Rapporteur S. Okubo on efforts related to MPEG2 packetization, and<br />

also to multiplexing audio/ video in the same packet. This report covers the work of DAVIC, the IETF, and other<br />

groups. The need to evaluate the quality/focus on the existing IETF RFCs was mentioned as a major goal of this<br />

work. See also the Q12/16 report above for additional information.<br />

TOPICS FOR FUTURE WORK<br />

TD-31(GEN), Proposal to specify H.323 text conversation terminal (G. Hellström, Q9/16 Rapporteur), requests<br />

that Q13/16 take up the SUD (single use devices) (and non-SUD) H.323 text conversation terminal work as a<br />

follow-on to Annex F. The work will be taken up and contributions are solicited.<br />

Q14/16 WP2, COMMON PROTOCOLS, MCUS AND PROTOCOLS FOR INTERWORKING WITH<br />

H.300- SERIES TERMINALS<br />

The Q14/16 Rapporteur is G. Thom (Delta Information Systems, USA). TD-29(WP2/16) is the Q14/16 status<br />

report at the beginning of this meeting. TD-28(WP2/16) is the report of the previous interim rapporteurs<br />

meetings. TD-75(WP2/16) is the report of this Q14/16 meeting. Two interim meetings are planned jointly with<br />

Q11/16, Q12/16, Q13/16 and Q15/16: November 17-20, 1998, Torino, Italy, and February 23-26, 1999, New<br />

Jersey, USA.<br />

H.245 VERSION 4 APPROVAL<br />

COM16-59 contains H.245v4, Control protocol for multimedia <strong>communications</strong>. D.217© (P. Cordell, BT)<br />

proposes an object oriented approach to H.245 extension. This concept was previously presented in Cannes 8-11<br />

June, 1998 (See APC-1402, CSR-T Vol. 9.5) and was supported. However, it was determined at this meeting that<br />

D.217© was not ready to be included in H.245v4 and it should be deferred to H.245v5 (see below). It was agreed<br />

that COM16-59 as originally published should be put forward for Decision without the inclusion of D.217©.<br />

H.245v4 was approved (Decided) at the SG16 plenary.<br />

H.245 VERSION 5 DETERMINATION<br />

Q11/16 agreed to incorporate MPEG-4 video as a video codec in H-series terminals. The additions which need to be<br />

made to H.245 (originally contained in D.206©, Y. Kikuchi, T. Kawahara, Japan) are in TD-28(PLEN). Q11/16<br />

also approved H.223 Annex D (Optional multiplexing protocol for low bit rate multimedia communication over<br />

highly error prone channel) which requires additional support in H.245. These additions are contained in TD-<br />

39(PLEN).<br />

D.217©, Object Oriented Capability Sets (P. Cordell, BT) was not ready to be included in H.245v4 for Decision at<br />

this meeting. This will be studied during the interim meetings. It was agreed that the current text should be<br />

included in H.245v5 for Determination at this meeting. The revised text is in TD-39(PLEN).<br />

TD-39(PLEN) plus the additions in TD-28(PLEN) are the text of H.245v5 as Determined at the SG16 plenary.<br />

H.341 (H.MEDIAMIB) DETERMINATION<br />

TD-55(WP2/16) are the minutes of the H.Multimedia MIB BOF (Management Information Base Birds of a<br />

Feather), 8/25/98. Q14/16 discussed the relationship of H.341, Multimedia management information base, and the<br />

IETF. The IETF RTP (Real Time Protocol) MIB activities are within the Audio-Video Transport WG. The MIB is<br />

on <strong>standards</strong> track and should go to Last Call for Proposed Standard in 1998 or early 1999. Q14/16 will be able to<br />

reference it by RFC #. There was some question as to the best way to progress H.341. There are two approaches to<br />

moving forward with H.341:<br />

1. Develop the MIBs in Q14/16 (H.341) and attempt to get technical support from SNMP experts.<br />

2. Have the IETF develop the MIBs and Q14/16 develop H.341 which references them.<br />

24 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

The consensus of the group was to produce the multimedia MIBs in Q14/16, incorporate them in H.341, find SNMP<br />

experts in our organizations to <strong>review</strong> the work and provide technical assistance, and begin to sample implementations<br />

to verify the MIB process. This plan was communicated to the IETF in a liaison statement contained in TD-<br />

67(WP2/16).<br />

TD-23(WP2/16)©, draft H.341, was presented and discussed. Some editorial changes were identified. It was agreed<br />

that it was technically stable, there were no known flaws, and the draft should be moved forward for Determination at<br />

this meeting. It was pointed out that as a result of compilation and testing, some of the ASN.1 may change, but the<br />

content and structure was stable. H.341 (H.MediaMIB) was Determined by the SG16 plenary as TD-27(PLEN)©.<br />

TD-7(WP2/16) is a liaison from SG4 in response to the Q14/16 liaison in TD-28(WP 2/16) Annex 2-4<br />

(report of the interim rapporteurs meetings). This liaison had three points:<br />

• SG4 did not have time to <strong>review</strong> and comment on Q14/16’s MIBs<br />

• SG4 notes Q14/16’s use of SNMP and directs Q14/16 to their other liaison on management of IP based networks<br />

• SG4 provided information on fitting the multimedia tree into the TMN object identifier.<br />

TD-14(WP2/16), TD-5(GEN), TD-6(GEN), and TD-25(GEN), additional liaisons from SG4, were also<br />

<strong>review</strong>ed. It was agreed that Q14/16 would send them another liaison acknowledging their interest in the<br />

management of IP-based networks, informing them of Q14/16’s work in this area, and recommending that they<br />

attempt to be interoperable (or at least be compatible) with SNMP. This liaison is contained in TD-80(WP2/16).<br />

REMOTE DEVICE CONTROL H.283 (H.RDC), H.282 (V.RDC) AND T.136 (T.RDC) DETERMINATION<br />

D.207©, H.282, V.RDC (A. Woollett, ImageCom), and D.208©, T.136, T.RDC (A. Woollett, ImageCom), are<br />

drafts of V.RDC (set of services and protocol for RDC) and T.RDC, respectively. T.RDC describes how to utilize<br />

V.RDC using T.120 as the lower layer protocol. Future recommendations may describe how to utilize V.RDC<br />

using other lower layer protocols. Editorial changes were identified. TD-22(WP2/16) (M. Duckworth,<br />

PictureTel) is draft H.283, H.RDC. H.RDC is a data link protocol to carry Common RDC (that part of RDC<br />

common to T.120 and H.323) protocol over UDP. The editor was directed to consider the use of the reliable UDP<br />

method of H.323 Annex E. If necessary, the method in H.323 Annex E should be extended so that there is a single<br />

reliable UDP protocol for use in H.323. Several editorial changes were identified. It was indicated that the use of<br />

H.283 in GW to GW <strong>communications</strong> needs more investigation. This will be indicated as an open issue. It was<br />

noted that this draft recommendation was more complete than anticipated. It was agreed that H.283 should be put<br />

forward for Determination at this meeting. The revised text, TD-38(PLEN)©, was Determined at the SG16 plenary.<br />

The revised text for Determination of H.282 (V.RDC) is contained in TD-24(PLEN) and for T.136 (T.RDC) in<br />

TD-25(PLEN). Both were Determined.<br />

H.246 ANNEX B (INTERWORKING)<br />

There has been little contribution to this work and the editor suggested that Determination be deferred until there is<br />

more support for this draft recommendation. This was agreed. TD-12(WP2/16), Liaison from Q11/11 on<br />

interoperability of H.series multimedia terminals with voice-only terminals on switched circuit networks, and liaison<br />

from Q7/15 on speech quality aspects of internet telephony, were <strong>review</strong>ed. TD-12(WP2/16) notes that Q.699<br />

(DSS1/ISUP) provides some interworking descriptions. TD-13(WP2/16) notes that G.131 specifies the<br />

relationship between delay and talker echo that is acceptable. In general, an end-to-end one-way delay of 25 ms or<br />

more will require echo cancellation. The H.246 editor will take these issues into consideration for further<br />

development of Annex B.<br />

OTHER H.246 ANNEXES<br />

D.171© (J.P. Blin, France Telecom) is draft H.323 Annex I, Point-to-Point H.323 Over ISDN. D.173© (J.P. Blin,<br />

France Telecom) provides requirements for using H.323 on ISDN. D.156© (H. Harasaki, NEC) comments on the<br />

projected Annex/Appendix for H.323 over N-ISDN. In discussion, it was suggested that Q14/16 develop an Annex<br />

to H.246 which defines an H.323 to N-ISDN Gateway (GW) which does not convert to H.320 on the N-ISDN side.<br />

This would be used to allow H.323 terminals to connect via N-ISDN through the GW to an IP network. It would<br />

also allow efficient GW to GW connection using N-ISDN without the protocol conversion required to go to H.320.<br />

It was indicated that these exist today in the form of IP routers. No further action is indicated at this time. See also<br />

the Q13/16 report above.<br />

TD-31(WP2/16), H.323 Media Transport for ATM (P.A. Probst, ATM Forum), suggests an H.323 to H.323<br />

Annex C (H.323 on ATM) Gateway. It was determined that this was an ATM switch issue. No further action is<br />

indicated at this time.<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 25


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

The following documents were discussed:<br />

D.188©, Media Control Aspects of the Proposed Gateway Device Control Protocol<br />

D.191©, Signalling Transport Aspects of the Proposed Gateway Device Control Protocol<br />

D.192©, Framework for the Proposed Gateway Device Control Protocol V4.2<br />

D.193©, Connection Control Aspects of the Proposed Gateway Device Control Protocol<br />

D.194©, Device Management Aspects of the Proposed Gateway Device Control Protocol<br />

D.195©, IPDC Base Protocol (all from Nortel, Canada)<br />

D.158©, Functional Partitioning of SCN/Packet Gateway (G. Freundlich, Lucent)<br />

Many concerns were noted. It was decided that a small group would draft a terms of reference for the Gateway<br />

Control Protocol stating the problem to be solved, requirements of a candidate solution, and restrictions on overlap<br />

with existing H.323 concepts. The result of this effort, TD-89(WP2/16), Terms of reference for additional study<br />

of H.323 gateways interworking with SCN, forms the basis for work on an Annex to H.246. To achieve greater<br />

scalability, the H.323 Gateway function may be further decomposed, and sub-functions contained within the H.323<br />

Gateway may be placed in different physical devices. This shows the possible arrangements of sub-functions and the<br />

resulting interfaces that may be of interest to standardize.<br />

FUTURE TERMINAL TYPE<br />

There was a general discussion during the joint Q11/16, Q12/16, Q13/16, and Q14/16 session on the subject of a<br />

unifying terminal type which would be applicable to a wide variety of networks with various levels of quality of<br />

service. It was suggested that this terminal would use layered coding techniques for the audio, video and control<br />

streams. These streams would then be carried on different networks in a manner appropriate for that network and in a<br />

way that would enhance interoperability between terminals on different networks. Terms of reference for this work<br />

will be developed during the interim rapporteur meetings.<br />

Q15/16 WP3, ADVANCED VIDEO CODING<br />

The Q15/16 Rapporteur is G. Sullivan (PictureTel/USA). TD-16(WP3/16) is the report of the Q15 Rapporteur’s<br />

meeting in Whistler, British Columbia July 21-23, 1998. TD-19(WP3/16) is the status report of Q15/16<br />

activities. TD-17(WP3/16) is the Q15/16 agenda. TD-30(WP3/16) is the Q15/16 report of this meeting.<br />

Q15/16 has planned two interim meetings, November 3-6 in Seoul, Korea, and February 23 - 26, 1998 in New<br />

Jersey, with Qs 11/16 through 14/16.<br />

Q15/16, the video coding area within WP3, currently has two significant ongoing activities, H.263++ and H.26L.<br />

The H.263++ development effort is for near-term standardization of enhancements to produce a third version of the<br />

H.263 video codec for real-time telecommunication and related non-conversational services. The H.26L development<br />

effort identifies new video coding technology beyond the capabilities of incremental enhancements to H.263, for<br />

longer-term standardization. In addition to this focus on future needs, Q15/16 is tasked with maintaining the<br />

existing prior video coding <strong>standards</strong> (H.261, H.262, and H.263, and presumably H.120) as necessary.<br />

The primary means of document distribution within the Q15/16 Video Coding Experts Group is electronic, and<br />

Q15/16 documents are on an ftp site maintained by G. Sullivan of PictureTel: ftp://standard.pictel.com/video-site<br />

The group conducts its e-mail conversations over an e-mail reflector that is maintained by M. Zeug of Iterated<br />

Systems: itu-adv-video@listserv.iterated.com<br />

Requests for subscriptions and “unsubscriptions” for this e-mail reflector should be sent to the list manager: itu-advvideo-request@listserv.iterated.com<br />

H.262, AMENDMENT 5 DETERMINATION<br />

H.262, Amendment #5: Draft Amendment 5 (High Level for 4:2:2 Profile) to common text recommendation H.262 |<br />

IS 13818-2 (MPEG-2 video), was Determined as TD-26(GEN).<br />

JOINT DISCUSSIONS WITH QS 11/16, 12/16, 13/16, AND 14/16<br />

A joint session was held with Q11/16, Q12/16, Q13/16, Q14/16 and Q15/16 to discuss coordination issues. See the<br />

Q11, Q12, Q13 and Q14/16 reports for additional information.<br />

Common Text Document Handling for H.262 (MPEG-2 video) and H.222.0 (MPEG-2 system)<br />

The group discussed the coordination of scheduling of amendments to H.262 and H.222.0 with ISO/IEC JTC1 as<br />

addressed in TD-15(GEN), liaison from MPEG, ISO/IEC JTC1/SC29/WG11. A significant delay had been<br />

experienced in the publication of the amendments approved at the January/ February SG16 meeting (Amendments 3<br />

26 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

and 4 to H.262 and Amendments 3 and 4 to H.222.0), but it appears that the future work on these recommendations<br />

is synchronized well in SG16 and JTC1 (as long as the time between Decision and publication can be kept to a<br />

minimum). In particular, Amendment 5 to H.222.0 was Decided (as COM16-67), and Amendment 5 to H.262 and<br />

Amendment 6 to H.222.0 were Determined (as TD-26(GEN) and TD-30(PLEN), respectively) at this SG16<br />

meeting. TD-32(GEN) a liaison statement to ISO/IEC JTC1/SC29/WG11 (MPEG) was drafted and approved<br />

regarding publication of the common text <strong>standards</strong> H.222.0 | IS 13818-1 and H.262 | IS 13818-2 (a joint issue for<br />

Q12/16 and Q15/16). Q15/16 noted their efforts to facilitate timely publication of updates to these common text<br />

<strong>standards</strong>.<br />

Future Work Items<br />

The status of the Q15/16 H.263v3 and H.26L projects were discussed, and Q11/16 reported on its plan for an H.32L<br />

terminal project with a similar schedule. Q13/16 reported its work on “single use device” specifications in H.323<br />

(not at present including video use).<br />

PLANNING AND WORK ON H.263++<br />

The current workplan of the H.263++ project is provided in Annex Q15.A of TD-62(PLEN), the WP3/16 report.<br />

Decision is planned for 2002 (see also CSR-T Vol. 9.2 for the work plan).<br />

The group discussed the current status of work on H.263++ and recalled the eight key technical areas that appear to<br />

be promising for further investigation:<br />

1. Error resilient data partitioning<br />

2. 4x4 motion compensation and DCT<br />

3. Adaptive quantization<br />

4. Reference picture selection enhancement<br />

5. Scalability enhancement<br />

6. IDCT mismatch reduction<br />

7. Deblocking and deringing filters (normative or informative)<br />

8. Error concealment (normative or informative)<br />

However, although these areas appear worthwhile for investigation, none of them have appeared to be fully mature<br />

yet in terms of having both a sufficiently stable technical content proposal and a high level of proven effectiveness<br />

and necessity confirmed by an independent implementation experiment. Thus Q15/16 has not yet created a draft for<br />

H.263v3 technical content.<br />

PLANNING AND WORK ON H.26L<br />

The current workplan of the H.26L project is provided in Annex Q15.A of TD-62(PLEN), the WP3/16 report (see<br />

also CSR-T Vol. 9.2 for the work plan). The H.26L project appears to be on track, and will continue to be led by<br />

the Q15/16 Associate Rapporteur, K. Hibi. A significant milestone for this project is scheduled for the next Q15/16<br />

Rapporteur’s meeting (Nov. 3-6, Seoul, Korea), at which technical proposals are expected for H.26L.<br />

FUTURE WORK<br />

Q11/16 has asked to collaborate closely with Q15/16 regarding the use of video communication on mobile networks.<br />

Progress is expected at the joint rapporteurs meeting in February 1999.<br />

The experts agreed to further consider the needs of video coding for sign language and lip reading communication, and<br />

in particular to <strong>review</strong> TD-35(GEN) provided by the Q9/16 rapporteur.<br />

Q16/16 AND Q17/16, MULTIMEDIA HARMONIZATION AND COORDINATION<br />

M. Matsumoto (Japan) is the Rapporteur of Q16/16 and Q17/16. T. Taylor (Nortel, Canada) is the assistant<br />

Rapporteur. The meeting agenda is TD-27(GEN). The Q16-17/16 meeting report is TD-81(PLEN).<br />

LIAISONS<br />

Some SG16 Rapporteurs complained that the volume of liaison documents directed to all Questions is excessively<br />

large, and liaisons in general require a substantial amount of time. They asked that Q16-17/16 get involved in<br />

document management to cut down the volume.<br />

TD-2(PLEN) is a request from ITU ICG (Intersector Coordination Group) SAT for a progress report on work<br />

related to satellite transmission. The liaison response notes that the only specifically satellite-related work in Study<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 27


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

Group 16 is the recently Decided (2/98) H.324 Annex E (COM 16-R37), Initialization of acknowledgment timer<br />

T401 to allow operation over geostationary satellite channels. Because Working Party 1/16 takes account of channel<br />

worst-case characteristics when defining modem operation, the liaison requests that WP1/16 be informed if any new<br />

Recommendation modifies satellite transmission channel characteristics.<br />

TD-8(PLEN) (TSAG) is a description of procedures for coordination between the ITU-T and the IETF. It requires<br />

that Study Group 16 appoint one or more official contact persons to the IETF and notify the ISOC Vice President of<br />

Standards accordingly. J. Ott (Teles) and T. Taylor (Nortel) were nominated as contact points for SG16.<br />

TD-10(PLEN) is a TSAG contribution on interoperability testing. The nature of the desired response to this<br />

document was unclear and remains an open item. The document is related to GII project F.4 (see below).<br />

A New Joint Task Group On Multimedia Broadcast Evolution and Common Content Format has been established.<br />

SG16 will be asked to appoint a liaison officer to represent the Study Group on this Joint Task Group.<br />

THE NATURE OF Q16-17/16’S COORDINATION TASK<br />

Discussion resulted in enumeration of the aspects of the coordination task.<br />

It was noted that Q16-17/16 has two generic mechanisms for coordination: the framework Recommendation H.200,<br />

which must be revised to make it current, and the summaries of work status prepared by the Secretariat.<br />

PROMOTION OF THE WORK DONE ON MULTIMEDIA COMMUNICATIONS<br />

TD-28(GEN) (I. Sebestyen, Associate Q16-Q17/16 Rapporteur) recalls previous measures put in place to advertise<br />

the work of SG16, and notes that no contributions have been received for this purpose. Concern was expressed that<br />

MPEG-4 in particular is promoting its product far more vigorously than SG16. It was noted that, at the January<br />

meeting, each Working Party had prepared such a contribution describing the results of its work, but this material<br />

has apparently disappeared.<br />

The question of appropriate procedures for authorization of press releases was raised. Any press release should be<br />

made by agreement of the SG16 management team.<br />

REVISED SG16 SEMINAR ON MULTIMEDIA<br />

Chile has proposed that the spring, 1999 meeting of Study Group 16 be held at the University of Chile in Santiago.<br />

Because of the timing of the school year, space would be available only in the middle of May. The Study Group<br />

would have to assess whether the University’s facilities would meet the requirements for the meeting.<br />

The SG16 Chairman had proposed that a seminar on multimedia be held in conjunction with the meeting. M.<br />

Matsumoto (Q16-17/16 Rapporteur) has been working on details of this proposal, and presented them. The seminar<br />

would be held on World-Wide Tele<strong>communications</strong> Day, 17 May 1999, with the Study Group meeting starting on<br />

the following day.<br />

The meeting generally approved M. Matsumoto’s proposals as the basis for further work.<br />

GLOBAL INFORMATION INFRASTRUCTURE (GII) PROJECTS<br />

TD-24(GEN) from JRG (Joint Rapporteur Group) on GII, July 20-24, 1998, Geneva, is the report on the third<br />

meeting of the JRG on GII. This includes reports on both the PINT and TIPHON activities.<br />

TD-5(PLEN) from Y. Robin-Champigneul as SG16 liaison on JRG/GII and TD-2(GEN) from SG13 are<br />

liaisons received on the GII project. SG13, the lead SG on GII, at their plenary meeting in June produced three<br />

Recommendations Y.100 (GII: General overview), Y.110 (GII: Principals and framework architecture), and Y.120<br />

GII: Scenario methodology. Y.110 defines four GII blocks, GII service packaging and cooperation service components,<br />

Middleware support components, Application/service creation support and GII interworking service<br />

components. Table 4 notes the accepted proposals from SG16 to participate in the GII projects.<br />

GII<br />

project<br />

No.<br />

Project name Project leader Collaborating Bodies<br />

F.3 Information appliance SG16 (Q2, 11, 12, 13, 17)<br />

T. Taylor<br />

SG8 (Q1, 3, 4), SG9 (Q17, 19, 20,<br />

24, 25, 27, 28), DAVIC, IEC<br />

TC100, JTC1<br />

28 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

F.4 End-to-end<br />

interoperability<br />

I.1 IP and<br />

tele<strong>communications</strong><br />

networks<br />

interrelationships<br />

SG16 (Q1, 2, 3, 12, 13, 14, 15,<br />

16, 17, 18)<br />

M. Matsumoto<br />

SG13 (SG11, 16 & IETF will<br />

lead the development of the<br />

resulting protocols.) M.<br />

Vandenameele, C.S. Lee<br />

SG8 (Q4, 6, 7, 9), SG9 (Q19, 24,<br />

29), SG12 (Q16, 18, 21) DAVIC,<br />

IEC TC 100, JTC1<br />

SG2, 3, 7, 9, 10, 11, 12, 15, 16,<br />

IETF, W3C, JTC1, ATM Forum,<br />

DAVIC, TIPHON<br />

I.2 Multimedia over IP SG16 J. Magill SG2, 3, 7, 8, 9, 10, 11, 12(Q16, 18,<br />

21), 13, 15, JTC1, IETF, IMTC,<br />

TIPHON, DAVIC<br />

M.3 Technical framework for SG16 (Q1 + tbd) SG13<br />

electronic commerce<br />

M.4 Middleware for<br />

multimedia<br />

Project I.2, Multimedia Over IP<br />

SG16 (Q16, 17)<br />

M. Blaschitz<br />

Table 4. SG16 Participation in GII Projects<br />

SG7(Q24), SG10, OMG, TINA-C,<br />

DAVIC, Open Group<br />

The GII project I.2 (TD-29(GEN), Review of Multimedia over IP Standards, J. Magill, WP1/16 chair) reports<br />

findings on IP-related work in progress in a number of <strong>standards</strong> bodies. It was not clear what, if any, additional<br />

work should be done under project I.2. See the Q13/16 report above for additional details.<br />

Project M.4, Middleware For Multimedia<br />

The key point in this project collaboration is that Study Group 16 has the view of the end-to-end services to be<br />

provided. Study Group 10 is responsible for the network operating system which will support the implementation<br />

of those services. See Q216 report above for details.<br />

Project F.4, End-To-End Interoperability<br />

TD-21(GEN) (Q16-17/16 Rapporteur) reports on Project F.4, End-To-End Interoperability. Discussion revealed<br />

four possible views of interoperability which might be considered within the project. These views were discussed at<br />

length. It was agreed that the drafters of the GII project intended as an ultimate goal that any two terminals operating<br />

anywhere on the global network would be able to interoperate when accessing/providing the same service.<br />

It was noted that another GII project on network interworking exists. Thus project F.4 should focus on application<br />

interworking between the terminals, but should also feed requirements into the network interworking project, and in<br />

turn should take account of the results of the latter study.<br />

Further discussion concerned how to move forward in the project. The two possibilities might be to work with<br />

reference scenarios or to continue work on a general methodology for <strong>standards</strong> development. Another suggestion<br />

was to start with service descriptions and move down to scenarios and protocol profiles after that. It was pointed out<br />

that the service description for multimedia conferencing has already been standardized as Rec. F.702. This could be<br />

the starting point for scenario development.<br />

A modified version of TD-21(GEN) was subsequently <strong>review</strong>ed and approved. TD-82(PLEN) is the liaison<br />

report from SG16 to JRG-GII for F.4. It defines Interoperability as the information exchange between service/<br />

application entities.<br />

Project M.3, Electronic Commerce<br />

A draft of the project plan for project M.3 was presented with the proposal that Study Group 16 accept leadership of<br />

this project (Annex 1 to TD-81(PLEN), the Q16-17/16 meeting report). Extensive discussion resulted on whether<br />

Study Group 16 has the necessary resources and expertise to take on the project. It was agreed that we should be<br />

guided by the response to a call for interested persons to contribute to the work. Y. Robin-Champigneul<br />

(FT/CNET, France) accepted the task of project coordination for project M.3.<br />

It was agreed that the project plan should make reference to the extensive work on this topic in various working<br />

groups of the IETF and to the work of other bodies where this information is available. TD-85(PLEN) is the<br />

modified draft of the M.3 project plan.<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 29


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

E-Mail Discussion Lists<br />

It was noted that the e-mail discussion lists which were to be set up for discussion of the different GII projects had<br />

not materialized. The meeting agreed that all discussion should go through the same list: the one allocated for discussion<br />

of Questions 16 and 17 at the TSB-SG16 site. M. Matsumoto will submit the names and e-mail addresses<br />

of all participants to the TIES Help-Desk personnel to enroll them as list subscribers.<br />

DRAFT OF THE MULTIMEDIA RECOMMENDATION MODEL<br />

A draft of the new MM Recommendation model was presented. The new draft presented an inventory of existing<br />

series of Recommendations rather than the desired framework. It was therefore rejected with instructions to the<br />

drafter (T. Taylor, Nortel) to seek instead to extend the framework provided in the original document. Suggestions<br />

were presented for the proposed Appendices listing current Recommendations in force; these lists should crossreference<br />

between the individual Recommendations and the systems to which they are applicable.<br />

Q18/16 WP1, INTERACTION OF HIGH-SPEED VOICEBAND DATA SYSTEMS WITH SIGNAL<br />

PROCESSING<br />

There were no contributions on this topic and no discussion. No interim meetings are required.<br />

At the WP1 plenary, the WP1 Chairman reported that the Rapporteur for Q18/16, M. Sherif (AT&T), was no longer<br />

able to continue as Rapporteur as his work area had changed and he is no longer involved in <strong>standards</strong> activities. The<br />

WP1 chair thanked M. Sherif for his contribution to the work of Working Party 1/16.<br />

D.174© (France Telecom) proposes the transfer of Question 18/16 to Study Group 15 where the work may be more<br />

appropriate, and where more of the relevant experts are participating.<br />

WP1 agreed with the France Telecom proposal and accordingly TD-56(WP1/16), a Liaison Statement to SG15,<br />

was prepared proposing that they consider taking over this Question.<br />

Q19/16 WP3, EXTENSION TO EXISTING ITU-T SPEECH CODING STANDARDS AT BIT RATES<br />

BELOW 16 KBIT/S<br />

S. Hayashi (NTT/Japan) is the Q19/16 Rapporteur. TD-20(WP3/16) is the Q19/16 agenda and prior meeting<br />

report; TD-32(WP3/16) is the Q19/16 meeting report. No interim meetings are planned.<br />

ANNEX C TO G.729 APPROVAL<br />

The work on G.729 (CS-ACELP) Annexes C, D and E took place in the WP 3/16 meeting.<br />

The technical content of G.729 Annex C (Floating point specification for G.729 and G.729 Annex A) was <strong>review</strong>ed<br />

based on COM16-45, as revised by SG16 during the January-February meeting of SG16 (see COM16-R29, pp. 2-4,<br />

with updated file sizes), on Annex 2 to TSB Circular Letter 101, and on D.185© (FT/CNET), Bug correction in<br />

G.729 Annex C. The group unanimously agreed to incorporate the suggested technical changes, as summarized in<br />

TD-16(PLEN). G.729 Annex C was approved (Decided) by SG16 as COM 16-45 plus TD-16(PLEN).<br />

ANNEX D TO G.729 APPROVAL<br />

COM16-65 presents the text of new Annex D to G.729, - 6.4 kbit/s CS-ACELP. The characterization test<br />

methodology was drafted at the SG16 February meeting and revised and approved in SQEG (speech quality experts<br />

group Q22/12) in March 1998. FT/CNET and NTT performed the characterization tests of Version 1.2 of the<br />

algorithm and presented the test results. All the requirements were met in both laboratories except for the DCR<br />

(Degradation Category Rating) test method under high levels of car noise. It was explained by speech assessment<br />

experts present at the meeting that there was not sufficient evidence to conclude whether or not G.729 Annex D has<br />

problems with car noise. The group agreed to add a note warning of potential performance limitations with high<br />

levels of car noise and unanimously agreed that G.729 Annex D should be approved by SG16. It was Decided as<br />

TD-43(PLEN)©.<br />

ANNEX E TO G.729 APPROVAL<br />

D.186© (France Telecom/University of Sherbrooke) presents design considerations on the test vectors for Annex E<br />

to Recommendation G.729; this was recognized as useful information.<br />

30 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

COM16-66 presents the draft text of Annex E to Recommendation G.729 - 11.8-kbit/s CS-ACELP speech coding<br />

algorithm, which is the higher bit-rate extension designed to accommodate a wide range of input signals such as<br />

speech with various background noise and music. This coder was developed by France Telecom/CNET and<br />

University of Sherbrooke, and was originally submitted to the Q19/16 Rapporteur’s meeting in September 1997.<br />

The design of test vectors for verification or correct implementation of this algorithm was presented by University of<br />

Sherbrooke. The characterization test methodology was drafted in the SG16 February meeting and revised and<br />

approved in SQEG/SG12. Ericsson, FT/CNET and NTT performed the characterization tests of version 1.2 of the<br />

algorithm and presented the test results. All the requirements were met in all the laboratories and some objectives<br />

were also met. The group unanimously agreed that the algorithm has adequate performance and that it should be<br />

approved by SG16. It was Decided as TD-44(PLEN).<br />

CORRIGENDUM FOR ANNEX H TO G.728 APPROVAL<br />

Annex H of G.728 (Variable bit rate LD-CELP operation mainly for DCME at rates less than 16 kbit/s) lacked the<br />

detailed description on the modified pseudo-code to be used in the calculation of log-gain (GSTATE(1)). The<br />

corrigendum proposed in D.215© (Mitsubishi) provides the additional description on the calculation of GSTATE(1)<br />

and the additional values for codebook-related arrays. Q19/16 agreed that the corrigendum should be published in an<br />

Implementer’s Guide. It was approved as TD-49(PLEN).<br />

ANNEX I - G.728 DETERMINATION<br />

Proposed Annex I to G.728 (extensions for robust performance in the presence of frame erasures) used to be an<br />

extension of the LD-CELP codec that modified the decoder algorithm to be operated under burst error conditions of<br />

mobile radio channels. This extension was suspended because some quality loss was previously found in subjective<br />

tests performed with Japanese sentences. D.107 (R. Cox, AT&T) from the January 1998 SG16 meeting presented<br />

an improved frame-erasure concealment algorithm that intends to overcome the quality loss in the previous proposal.<br />

The meeting agreed that this algorithm is valuable not only at 16 kbit/s but also at 12.8 and 9.6 kbit/s under<br />

variable-rate operation. The terms of reference for this extension algorithm is attached as Annex B to TD-<br />

32(WP3/16), the Q19/16 meeting report. The test methodology for this extension was drafted in February 1998<br />

meeting and approved by SQEG/12 March 1998.<br />

AT&T tested this algorithm in North American English and NTT tested it in Japanese. The results from both test<br />

laboratories were <strong>review</strong>ed at this meeting (D.155© and D.203©, respectively). All the requirements were met<br />

except for a few conditions that were unique to each of the two languages and were recognized to have little statistical<br />

significance. The group unanimously agreed that this proposal should be submitted for Determination at this<br />

meeting. G.728 Annex I was Determined as TD-48(PLEN).<br />

VBD CAPABILITY FOR THE 40-KBIT/S EXTENSION OF G.728<br />

Although the final version of the test methodology of voice-band data (VBD) capability was finalized in February<br />

1998, no action was taken by the proponent of the candidate algorithm (ECI/MOC Israel) to start testing. No<br />

progress was made during this meeting. The group <strong>review</strong>ed the schedule and would like to come to closure on the<br />

issue at the next meeting. The rapporteur will personally contact the proponent to clarify the situation. The terms<br />

of reference for this extension algorithm is attached as Annex A to TD-32(WP3/16), the Q19/16 meeting report.<br />

PROPOSAL OF IMPROVING VAD<br />

D.145© (CSELT) is a new algorithm to improve VAD (Voice Activity Detector) performance when it is used with a<br />

digital speech coding algorithm. This new VAD was developed by the University of Catania and is based on an<br />

improved (adaptive) version of the Fuzzy VAD presented (as AH-Q19-06) in September, 1997 at the Bethesda, MD,<br />

Q19/16 meeting. Performance evaluation with both subjective and objective measures was presented in comparison<br />

with Annex B to G.729 identifying the improvement over G.729 Annex B. The meeting thanked CSELT for the<br />

information and suggested that a concrete proposal be submitted via contribution for the establishment of a new<br />

work item.<br />

LIAISON STATEMENTS<br />

TD-28(WP3/16) from Q19/16, Q20/16 and Q21/16 to both SQEG/12 and ITU-R TG8/1 notifies them of the<br />

approval of Annexes C, D, and E to Recommendation G.729 and of the Determination of Annex I to<br />

Recommendation G.728. SG16 thanks SQEG/12 for elaborating the characterization test methodology and analyzing<br />

the test results for both draft Annexes D and E to G.729. It also thanks SQEG/12 for <strong>review</strong>ing the<br />

evaluation test methodology for the proposed Annex I to G.728. WP3/16 would like to ask SQEG/12 and Q14/12<br />

to consider the identification of proper methods for the assessment of VAD/CNI/DTX (discontinuous transmission)<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 31


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

algorithms in particular in the presence of background noise, which will be part of future standardization work in<br />

SG16.<br />

Q20/16 WP3, AUDIO AND WIDEBAND CODING IN PUBLIC TELECOMMUNICATION<br />

NETWORKS<br />

R. Drogo De Iacovo (CSELT/Italy) is the Q20/16 Rapporteur. TD-8(WP3/16) is the meeting agenda. TD-<br />

9(WP3/16) is the Q20/16 progress report. TD-29(WP3/16) is the report of this meeting. The current<br />

objectives of Question 20/16 are to evaluate the results of the selection test and plan for future activities.<br />

WIDEBAND CODEC TEST RESULTS<br />

COM16-71 (PictureTel) is a detailed description of the PictureTel candidate algorithm for the wideband (50 - 7000<br />

Hz) audio coder for multimedia <strong>communications</strong> with a 16 kHz sample rate.<br />

TD-10(WP3/16) (Rapporteur) contains version 1.2 (May 1998) of the Subjective Selection Test Plan for the ITU-<br />

T Wideband codec. Five listening laboratories participating in the selection listening tests (DT Berkom, FT/CNET,<br />

FUB, NORTEL and NTT-AT) and presented their results. All of them were judged compliant in meeting its<br />

deliverables according to the contents of the signed Memorandum of Understanding. This work was funded by<br />

PictureTel, who provided the candidate algorithm, at the 50% level. Each of the listening laboratories are expected to<br />

send a bill for the balance to ITU-T TSB for payment.<br />

D.146© CSELT - FUB<br />

D.151© Deutsche Telekom Berkom GmbH<br />

D.184© France Telecom/CNET<br />

D.190© Nortel<br />

D.204© NTT/NTT-AT<br />

TD-12(WP3/16) (Q22/12/SGEQ/12 Chairman, P. Usai, CSELT) presents a global analysis of the wideband codec<br />

selection tests. From the global analysis it was shown that the codec under test (CuT) has very good performance<br />

with music signals and with background noise at 32 kbit/s. In the presence of clean speech, however, the CuT<br />

doesn’t provide the required performance in many cases. An overview of the selection test results is included in<br />

Annex Q20.A of the Q20/16 meeting report, TD-29(WP3/16) which also includes Terms of Reference and<br />

associated time schedules.<br />

The following areas were identified as clearly needing improvement before the terms of reference can be said to be<br />

met:<br />

• Clean speech with frame erasures - performance at the three bit rates<br />

• Tandem clean speech performance for 24 and 32 kbit/s<br />

• Two and three tandem performance with office noise at 16 kbit/s<br />

• Three tandem performance with frequency harmonic noise at 16 kbit/s.<br />

It was concluded that the measured performance of the tested algorithm does not satisfy all the terms of reference, in<br />

particular for speech signals in (a) tandem connections and in (b) connections with 3% random frame erasure.<br />

After the discussion on the selection test results, it was agreed to restart the competition for a 24, 32 kbit/s wideband<br />

algorithm for speech and music signal with a very short time schedule. D.196© (Canada) raises the need to consider<br />

new standardization of a 7-kHz codec at 16 kbit/s and below devoted for speech signals.<br />

TEST RESULTS AND ORGANIZATION OF FUTURE ACTIVITIES<br />

D.161© (Lucent) expresses concern on the present state of the standardization activities with regards to wideband<br />

speech coding. It requests that no further compromises be made in the relaxing of requirements.<br />

As a first way forward, Q20/16 discussed the possibility of considering specific applications and, taking into account<br />

the conditions with requirement met, starting an optimization phase. Due to the number of failures in meeting the<br />

requirements and the lack of organizations willing and able to enter this optimization phase in order to improve the<br />

codec performance, it was decided to explore other ways to go forward.<br />

Taking into account the need to proceed rapidly towards an ITU-T wideband standard and, at the same time, noting<br />

the state of the art in wideband coding, Q20/16 agreed to proceed with a very short time schedule for a 24, 32 kbit/s<br />

wideband algorithm capable of coping with speech and music signals; it was agreed to leave the wideband 16 kbit/s<br />

(and around) bit-rate(s) as a longer new project activity mainly focused on speech signals.<br />

32 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

For the 24 and 32 kbit/s algorithms this assures fair competition; it allows other candidates to participate in the<br />

selection process.<br />

Consequently, the Terms of Reference and time schedule were revised (Annex Q20.B to TD-29(WP3/16)) and the<br />

following agreements were reached. The aim is to have the standard algorithm at the end of the very short time<br />

schedule:<br />

1. The qualification phase is not performed and no qualification test is required of the candidate proponents; they<br />

have to sign a Letter Of Intent (LOI) and send it to ITU-T TSB (F. Bigi). The LOI represents a commitment for<br />

the proponents to enter the selection phase and share the cost of the subjective tests. The total amount to be<br />

shared will be known when the MoUs (Memoranda of Understanding) are prepared by ITU-T TSB and sent to the<br />

interested parties.<br />

Editor’s note: On October 7, 1998, an e-mail from S. Campos-Neto noted that the Letter of Intent is now available<br />

from the ITU at:<br />

ftp://account@ties.itu.int/u/tsg16/sg16/wp3/loi.rev1.doc<br />

where “account” is a valid TIES account with access to the SG16 Informal FTP area.<br />

The Rapporteur for Q20/16 will also be informed by the candidate proponents of their intentions and the<br />

Rapporteur will notify the Q20/16 reflector of candidate submissions.<br />

2. Two MoUs will be prepared by ITU-T TSB, as in the previous wideband exercise: MoU “A” between ITU-T and<br />

candidate proponents, MoU “B” between ITU-T and listening laboratories.<br />

3. Each candidate proponent will perform the fixed-point software host laboratory processing for its own candidate<br />

conditions. As done in the previous wideband selection test, the candidate proponent will process the candidate<br />

conditions, and the listening laboratories will provide pre-processing of the source material and processing of<br />

reference conditions utilizing the ITU-T Software Tool <strong>Library</strong>.<br />

Spot checking of the processing done at the proponent laboratories will be performed; the procedure will be<br />

coordinated by the Rapporteur for Q20/16. The spot checking will be started after the end of the host laboratory<br />

sessions and will require that each candidate proponent check the processing performed by another proponent.<br />

With this aim, each candidate proponent shall receive, under NDA (Non Disclosure Agreement), the executable<br />

code and batch files to perform the spot checking activity. CD-ROM is the preferred media to exchange files<br />

(unless differently agreed) in DOS format and executables for a Pentium Windows 95 platform. Moreover, a<br />

similar spot checking activity should be performed by listening laboratories as regards the pre-processed source<br />

material and processing of the reference conditions using the same exchange media and platform as agreed for the<br />

above-mentioned spot checking activity carried out at the host laboratories.<br />

4. The time schedule for wideband coding at 24 and 32 kbit/s (see Annex Q20.B of TD-29(WP3/16)) was<br />

prepared, planning for Determination in May 1999 and Decision in September 1999 (co-located meeting with<br />

SG12).<br />

5. The Terms of Reference (ToR) were <strong>review</strong>ed and it was agreed to leave the 16 kbit/s for a subsequent new<br />

standardization activity. The 16 kbit/s compared to G.722 at 48 kbit/s (one third of bit-rate reduction) is not<br />

achievable with the current state of the art. Moreover, looking at the results gained in the testing of ITU-T<br />

wideband coding during the past five years, it was concluded from the test results that the state of the art likely<br />

allows a reduction of 24 kbit/s while maintaining the same performance of G.722 for speech and music. Based<br />

on actual test results, the ToR were revised, calling for an algorithm at 24, 32 kbit/s that matches the G.722<br />

performance at 48, 56 kbit/s, respectively, whereas the objective, that will be tested in the selection phase,<br />

remains matching G.722 performance at 56, 64 kbit/s.<br />

6. The Rapporteur will also send the Liaison Statement originated by Q20/16 to the SQEG/SG12 e-mail reflector<br />

and directly to the SQEG Chairman to minimize the risk of delay in the wideband time schedule.<br />

Q20/16 specifically addressed the issue of sharing 100% of the total cost of the subjective tests among candidate<br />

proponents. If PictureTel is a candidate proponent, it should be taken into account that they already paid for the<br />

previous selection exercise and a compensation mechanism should be adopted to equally distribute the final<br />

expenditure.<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 33


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

The feeling of many potential candidates present at the meeting was that it would be very difficult for them to gain<br />

acceptance of this proposal by their respective managements. For that reason they did not accept this compensation<br />

mechanism and asked to share 100% of the new costs among proponents, including PictureTel.<br />

Nevertheless, when the actual set of candidate proponents is known, the question can then be decided by the<br />

proponents.<br />

Editor’s note: As of October 28, LOIs from PictureTel and NTT have been received and accepted by the ITU.<br />

Lucent Technologies previously notified the Rapporteur that they do not wish to participate in this phase.<br />

Q20/16 also addressed the issue of C-source code availability and proper distribution. It was agreed that an escrow<br />

copy of the C-source code will be sent by each of the proponents to the ITU-T TSB (deadline is two months before<br />

the SG16 meeting). No software distribution will take place before the SG16 meeting. At the next SG16 meeting,<br />

if a Determination occurs, the issue of software distribution will be addressed and the guidelines that are expected<br />

from TSAG on the subject will be properly considered.<br />

Starting from the considerations contained in D.196 (Canada), it was agreed to request contributions for a new<br />

wideband (7 kHz) coding activity around 16 kbit/s with focus on speech. An Annex to TD-29(WP3/16) contains<br />

a summary of possible applications and technical features for the new wideband algorithm as discussed within<br />

Q20/16. These include: ISDN videotelephony on Basic Rate Access, ISDN wideband telephony (e.g., for<br />

multichannel applications), wideband transmission over Internet, packet applications (B-ISDN with ATM, PCME,<br />

DCME), wideband over indoor wireless and cellular, and PSTN applications (e.g., point-to-point links for business<br />

applications).<br />

LIAISON STATEMENTS<br />

TD-01(WP3/16) is a liaison from Task Group 8/1 on Speech and Multimedia coding for IMT-2000. It requests<br />

continuing information on the performance of the extension to G.729 at 11.8 kbit/s, and other candidate set(s) of<br />

video and audio codecs for IMT-2000 applications.<br />

TD-04(WP3/16) is a reply from Q22/12 (February 1998 meeting) on the progress of speech coding testing and<br />

related issues. BT, France Telecom, Nortel, NTT and Rockwell have identified themselves as provisionally able to<br />

conduct the tests. However the issue of funding will need to be addressed by SG16.<br />

TD-06(WP3/16) is a liaison from MPEG with comments on audio coding and audio verification tests, and a copy<br />

of MPEG-4 Audio Verification Test Specifications - NADIB (Narrow Band Digital Broadcasting) Part. This liaison<br />

notes that MPEG-4 is focused on narrow band audio broadcasting, music on the Internet and mobile video<br />

transmission; verification testing will be aimed at evaluating the performance in these specific application areas.<br />

TD-28(WP3/16) contains all the output liaison statements from Q19/16, Q20/16 and Q21/16 regarding Progress<br />

on Speech Coding Issues. Included in TD-28(WP3/16) is a liaison to inform SQEG (Q22/12) about the updated<br />

Terms of Reference and time schedule for ITU-T wideband coding at 24, 32 kbit/s. It also asks support in<br />

developing an appropriate selection test plan. The liaison requests to have the selection test plan for wideband<br />

coding at 24, 32 kbit/s ready at the end of next SG12 meeting (December 4, 1998).<br />

TD-28(WP3/16) also includes two other liaisons to ITU-R TG 8/1 and SG11 asking advice on foreseen<br />

applications and related requirements for the new wideband coding activity around 16 kbit/s started at the present<br />

SG16 meeting.<br />

Q21/16 WP3, ENCODING OF SPEECH SIGNALS AT BIT RATES AROUND 4-KBIT/S<br />

The Q21/16 Rapporteur is P. Barrett (BT, UK). The Q21/16 agenda is TD-21(WP3/16); the report of interim<br />

activities is TD-22(WP3/16). TD-23(WP3/16) is the report of this Q21/16 meeting. No interim meetings are<br />

planned.<br />

The current objective of Q21/16 is to select an algorithm or algorithms that are likely to meet the terms of reference<br />

for the future ITU-T 4-kbit/s speech coding standard (G.4k). Candidate proposals are assessed on the basis of<br />

subjective test results produced according to the 4-kbit/s qualification test plan.<br />

SUMMARY<br />

Q21/16 <strong>review</strong>ed qualification results from eight organizations. However, none of the proposals fully met the<br />

requirements necessary to enter the selection phase; further submissions will be <strong>review</strong>ed in September, 1999. A<br />

34 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

new qualification procedure has been defined whereby the subjective tests for all 4-kbit/s candidates will be performed<br />

using a common laboratory (or laboratories). The terms of reference (ToR) for speech coding at 4-kbit/s remain<br />

unchanged. The revised target for approval of G.4k is the first quarter of 2001.<br />

RESULTS<br />

During the WP3/16 Plenary in February 1998, it was agreed that organizations submitting candidates to Q21/16<br />

would be required to provide demonstration speech material as a qualification deliverable. A procedure for the<br />

production and distribution of the demonstration material, based on the use of common unprocessed speech, was<br />

agreed by correspondence during July and August 1998. The Rapporteur received processed material from all eight<br />

candidate proponents by the agreed deadline of 2 September. This was placed on the ITU-T ftp server using a<br />

filename mapping known only to the Rapporteur.<br />

The Rapporteur stressed that the purpose of this demonstration material was to provide WP3/16 with an indication of<br />

the current performance of 4-kbit/s speech coding technology, and that although the demonstration material might<br />

contribute to the decision over whether to begin the 4-kbit/s selection phase, it would not be considered when<br />

deciding which particular algorithms could go forward.<br />

Q21/16 agreed that the demonstration material would be removed from the ITU-T ftp server after this Study Group<br />

meeting, and that the filename mapping would remain secret.<br />

CANDIDATE PROPOSALS<br />

Candidate proposals were presented by COMSAT, Fujitsu, Matsushita, Mitsubishi, NTT, Rockwell/Nortel, Toshiba<br />

and Voxware. A summary of the algorithms and qualification results is given in Annex Q21.A to the Q21/16<br />

meeting report, TD-23(WP3/16). Input documents are shown in Table 5.<br />

SCHEDULE<br />

Q21/16 <strong>review</strong>ed the qualification results with respect to the ToR (Terms of Reference) for 4-kbit/s speech coding.<br />

Although it was acknowledged that further delay in Q21/16 could lead to G.4k missing some windows of opportunity,<br />

the consensus of the meeting was that the ITU-T 4-kbit/s speech codec should deliver the performance reflected<br />

in the ToR. Given that none of the candidates passed all of the requirements, Q21/16 decided to postpone the<br />

deadline for candidate submissions.<br />

It was agreed that the next Q21/16 qualification tests will be coordinated by SG16, and performed at a common<br />

laboratory (or laboratories). The main disadvantages of this approach are the need for candidate proponents to pay<br />

external organizations to perform the subjective tests, and the additional delay incurred by the use of a small number<br />

of laboratories. However, these factors were felt to be outweighed by the advantage of removing variables such as<br />

source material, test language and replay equipment from the qualification phase. The number of listening laboratories<br />

and languages has yet to be agreed, but at least two listening laboratories (COMSAT and Nortel) stated that, in<br />

principle, they were interested in participating. BT provisionally stated that it could act as host laboratory.<br />

Organizations wishing to submit a 4-kbit/s speech coding algorithm to Q21/16 must make a verbal declaration of<br />

intent during the next SG16 meeting, otherwise their candidate will not be included in the qualification phase.<br />

Organizations wishing to act as a laboratory for the qualification phase should provide the following information to<br />

the Rapporteur not later than six weeks before the SG16 meeting in May 1999:<br />

1. The cost per candidate, per experiment;<br />

2. The maximum number of candidates that can be accommodated;<br />

3. The time required to perform the listening phase for different numbers of candidate algorithms (one to the<br />

maximum number inclusive);<br />

4. Whether the laboratory will perform the host laboratory function.<br />

Number Source Title<br />

D.152© Mitsubishi High Level description of Mitsubishi 4 kbit/s codec and test results<br />

D.154 Matsushita High Level description of Matsushita 4 kbit/s codec and test results<br />

D.157© COMSAT Qualification test results of COMSAT 4 kbit/s codec<br />

D.165© COMSAT High Level description of COMSAT 4 kbit/s codec<br />

D.175© Rockwell High Level description of Rockwell/Nortel 4 kbit/s codec<br />

D.176© Rockwell Qualification test results of Rockwell/Nortel 4 kbit/s codec<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 35


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

D.177© Rockwell IPR statement<br />

D.178© Voxware High Level description of Voxware 4 kbit/s codec<br />

D.179© Voxware Qualification test results of Voxware 4 kbit/s codec<br />

D.180© Voxware IPR statement<br />

D.201© Fujitsu High Level description of Fujitsu 4 kbit/s codec and test results<br />

D.205© NTT High Level description of NTT 4 kbit/s codec and test results<br />

D.209© Toshiba High Level description of Toshiba 4 kbit/s codec and test results<br />

Table 5. Input Documents for ITU-T 4-kbit/s speech coding standard (G.4k).<br />

In order to keep the cost of the qualification phase to a minimum, it was agreed that the experiments funded by the<br />

candidate proponents will only be performed in a single language (which will be the same for both qualification<br />

experiments). Proposals from laboratories wishing to repeat the qualification experiments in a second or third<br />

language will be considered if they incur little or no extra cost to the candidate proponents.<br />

The cost per candidate, per experiment is expected to be in the order of US$10K (i.e., US$20K per candidate).<br />

The schedule was revised such that the new target date for Decision of the ITU-T 4-kbit/s speech coding<br />

recommendation (G.4k) is the first quarter of 2001. The revised schedule is in Annex Q21.C to TD-23(WP3/16),<br />

the Q21/16 meeting report.<br />

TERMS OF REFERENCE AND QUALIFICATION TEST PLAN<br />

TD-13(WP3/16) (Q21/16 Rapporteur, P. Barrett) is the subjective qualification test plan for 4-kbit/s coding.<br />

There were no contributions on the ToR, although Voxware noted that in their qualification tests the provisional<br />

requirement for random bit errors (G.729 at a BER of 0.1%) gave better performance than G.726. The Rapporteur<br />

invited contributions on this topic, and stated that he would investigate the possibility of obtaining bit error patterns<br />

from Q11/16. The performance requirements for random bit errors and bursty detected frame erasures remain for<br />

further study.<br />

The requirement to pass DTMF signals was questioned, because systems using low bit-rate speech codecs<br />

increasingly send this information by means of signaling. A note was added to the ToR to reflect this fact, but the<br />

need to pass DTMF tones remains a requirement.<br />

One of the candidate proponents stated that they were unable to find a telephone handset meeting the specification in<br />

P.830. It was agreed that a liaison statement will be sent to Q22/12 (SQEG) requesting clarification on the use of<br />

headphones in future 4-kbit/s subjective tests (contained in TD-28(WP3/16), draft liaison statements from Q19,<br />

20 and 21/16).<br />

Finally, it was also suggested that the processing diagrams in the qualification test plan are unclear with respect to<br />

the inclusion of G.711 stages. New diagrams will be prepared for approval by SQEG.<br />

LIAISON STATEMENTS<br />

A liaison statement was drafted to inform SQEG of the revised 4-kbit/s schedule and qualification procedure, and to<br />

request guidance on the use of headphones in future 4-kbit/s qualification and selection tests.<br />

A liaison statement was drafted to ITU-R TG 8/1 to inform them of the revised 4-kbit/s schedule and terms of<br />

reference.<br />

Q22/16 WP3, SOFTWARE AND HARDWARE TOOLS FOR STANDARDIZATION OF SPEECH AND<br />

AUDIO CODING ALGORITHMS<br />

The Q22/16 Rapporteur is S. F. Campos-Neto (COMSAT/USA). TD-18(WP3/16) is a report of the interim<br />

activities. The Q22/16 meeting report is contained in the WP3/16 report, TD-62(PLEN). No interim meetings<br />

of Q22/16 are planned.<br />

Currently Q22/16 is dealing with the maintenance and future enhancements of the STL96 (Software Tool <strong>Library</strong>96).<br />

At the last SG16 meeting, an “unofficial” update (evolving STL, eSTL) was made available (the evolving STL<br />

released in January 1998 [eSTL9801] is available to ITU-T members under request from the Rapporteur) and the list<br />

of action points (see TD-62(PLEN), Annex Q22.A) was revised.<br />

36 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

Little progress was performed in this period (see TD-18(WP3/16), the report of the interim activities), although<br />

some minor bugs were corrected and identified, and some preliminary studies were performed.<br />

On the investigation of the alternative calculation of the active level method proposed by Prof. Kabal (COM 16-<br />

R28), preliminary comparison showed almost identical measurements when the speech files had been pre-equalized to<br />

-26 dBov. Further tests will investigate the effect for a range of input speech level files. When finalized, the results<br />

will be posted to the WP 3/16 reflector.<br />

The modified (to fix the bugs identified) demo programs will be uploaded to the ITU-T informal FTP area for SG16<br />

under the WP3 Q22 directory. Editor’s note: an e-mail from S. Campos-Neto on October 5, 1998 noted that these<br />

files have been uploaded to:<br />

ftp://account@ties.itu.ch/u/tsg16/sg16/wp3/q22/new-9809/new9809.zip<br />

where “account” (without quotes) is a valid TIES account and password.<br />

LIAISON STATEMENTS<br />

Q22/16 <strong>review</strong>ed TD-3(WP3/16), a Liaison Statement from Q13/12 on the PSQM (P.861, Objective quality<br />

measurement of telephone-band [300-3400 Hz] speech codecs, 2/98) software and from Q14/12 on speech voltmeter<br />

aspects (P.56, Objective measurement of active speech level) related to software tools.<br />

The group noted the guidelines on the use of test vectors for testing the PSQM implementation, but the Rapporteur<br />

reported that the reference implementation of the PSQM software has been taken out of circulation by the TSB, due<br />

to IPR issues related to P.861. As a consequence, this work was temporarily halted.<br />

Regarding the speech voltmeter, the group created an action item to identify and implement optional filter programs<br />

to band-limit the input signals used by the speech voltmeter demo programs.<br />

Q23/16 WP1, PCM MODEMS<br />

The Q23/16 Rapporteur is L. Brown (Motorola ISG, USA). The agenda for the meeting is TD-24(WP1/16).<br />

TD-14(WP1/16) is the report of the Red Bank, New Jersey, Q23/16 Rapporteur meeting (May 1998); TD-<br />

15(WP1/16) is the report of the Quebec City, Canada, Q23/16 Rapporteur meeting (July 1998). An interim<br />

Rapporteurs meeting is planned for December 7-10, 1998 in San Diego, California.<br />

LIAISON<br />

TD-4(WP1/16) is a liaison from SG15 concerning voice-band data over ATM networks. It recognizes the<br />

concerns of Q23/16 regarding adaptive build-out delay. Q8/15 added text noting the use of a fixed (300 μs - 2 ms<br />

network operator set) build-out buffer to delay playout of the packet/cells. The approved liaison reply (TD-<br />

39(WP1/16)) thanks Q8/15 for their work but raises the issue of when adaptive delay is used. It notes that a<br />

statement in I.741 specifying a means to disable adaptive build-out in the case of a data call might be helpful.<br />

TD-6(WP1/16) is a liaison from Q4/15 to multiple SGs concerning identification and characteristics of PSTN<br />

signals that may interfere with splitterless ADSL (G.lite). The liaison reply, in TD-52(WP1/16) notes the<br />

possibility of billing tones (see ETS 300 001) as signals outside the 4 kHz band.<br />

TD-13(GEN) is a liaison from SG15 requesting comment and identification of contacts pertaining to their draft<br />

ANT (access network transport) standardization plan; Q23/16 approved a liaison reply, indicating that they should add<br />

the V-series Recommendations from SG16 and delete the cited H.2xx documents, which do not relate to access<br />

transport. The liaison is in TD-44(WP1/16).<br />

RECOMMENDATION V.90, PCM MODEM<br />

Q23/16 agreed to the editorial changes to draft Recommendation V.90 (COM 16-64) given in TD-6(PLEN) items<br />

2-5. They also considered and approved, with revision, the proposed Appendix I (example network configuration) for<br />

V.90 contained in TD-6(PLEN). The updated text for the Appendix is contained in TD-45(PLEN).<br />

PROPOSED RECOMMENDATION V.ADM<br />

TD-23(WP1/16) is the updated issues list for the ongoing work on PCM modems as updated at the Q23/16<br />

Rapporteur meeting in Quebec City. This was revised to TD-40(WP1/16), which was then approved by Q23/16.<br />

TD-19(WP1/16), the proposed baseline text for V.adm, based on the agreements reached at the Quebec City<br />

meeting (July 1998), was approved with minor revision.<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 37


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

D.162© (B. Barazesh, Lucent) proposes work on the definition of Phase 1 of the handshake for V.adm, in particular<br />

on the detection of “clear” channels, i.e., channels with no digital impairments. D.199© (K. Chu, Rockwell, US)<br />

addresses several of the open issues on V.adm. D.200© (T. Liau, Rockwell, US) raises concern regarding the use of<br />

a DC offset for the V.adm digital connectivity probing sequence. TD-33(WP1/16) is a compilation of the<br />

contributions from the Quebec City meeting addressing open issues for V.adm.<br />

TD-41(WP1/16) is the report of an ad hoc session that reached agreement on open issues for V.adm. The revised<br />

report is in TD-51(WP 1/16). It reports that one proposed set of DCP (Digital connectivity probing) signals<br />

(repeating octets) would be before CM and after optional CI in Phase 1 or alternatively a DC offset could be added to<br />

CM and JM Phase 1 signals.<br />

During the deliberations, the group also approved the following:<br />

• Inclusion of an Appendix discussing the typical network configuration for V.adm<br />

• Optional support of V.8bis ahead of Phase 1 startup for V.adm<br />

• The use of the signal point represented by Ucode 66 for SCR in Phase 3<br />

• Handling of interchange circuits 104 and 106 during resynchronization and retrain, and circuits 107 and 109 during<br />

disconnect (after a 6 second timeout).<br />

The Rapporteur will update the issues list to reflect all of the agreements reached during this meeting.<br />

TD-46(PLEN) is the revised text for proposed Recommendation V.adm incorporating all of the agreements.<br />

The remaining open issues for V.adm are:<br />

• Finalization of the provisional agreement on the structure of Phase 1 of the startup procedure, which depends on<br />

the definition of robust DCPc (calling) and DCPa (answering) signals<br />

• Further consideration of test loops (section 9)<br />

• Clarifications to the Scope and the Title of the Recommendation pertaining to the definition of switched digital<br />

network, and type(s) of network over which V.adm is intended to operate<br />

• Work on Appendix describing typical network configurations for V.adm<br />

These issues will be addressed at the interim Rapporteur’s meeting.<br />

Q23/16 agreed that proposed Recommendation V.adm is sufficiently mature to be forwarded to SG16 for<br />

Determination. V.91 (former V.adm) was Determined at the closing plenary as TD-72(PLEN).<br />

V.ADM INTELLECTUAL PROPERTY<br />

To date, the following companies have indicated verbally that they may have Intellectual Property pertaining to<br />

proposed Recommendation V.adm: Lucent Technologies, Rockwell, 3Com, Motorola, Matsushita, and Lake<br />

Datacomms.<br />

38 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

MEETING ROSTER OF STUDY GROUP 16, SEPTEMBER 14 – 25, 1998, GENEVA, SWITZERLAND<br />

Pierre-André Probst, Swisscom, Switzerland SG16 Chair<br />

George Helder, PictureTel, US SG16 Vice Chair<br />

John Magill, Lucent, UK SG16 Vice Chair<br />

Federico Tosco, CSELT, Italy SG16 Vice Chair<br />

Country Company Name<br />

ETSI Gur Kimchi<br />

ETSI Paolo Usai<br />

INMARSAT Eyal Trachtman<br />

INTELSAT Andrew C. Lee<br />

TSB Fabio Bigi<br />

Austria Gerhard List<br />

Austria Post und Telekom Austria Michael Blaschitz<br />

Austria Post und Telekom Austria Paul Muzak<br />

Austria Post und Telekom Austria Klaus Sambor<br />

Brazil Georges Claessen<br />

Canada Redwan Salami<br />

Canada Thomas Taylor<br />

Canada Mitel Dave Walker<br />

Canada Nortel (Canada) Nicole Gallant<br />

Canada Nortel (Canada) Peter Yue<br />

Chile Eduardo Vera<br />

China Yu Hong Bin<br />

China Fei Wen Duan<br />

China Jiang Lin Tao<br />

China Xu Yun Tao<br />

China Dai Xiao Hui<br />

China Lin Xin Yue<br />

Finland Helsinki Telephone Co. Markus Backstrom<br />

Finland Helsinki Telephone Co. Juha Kauppi<br />

Finland Helsinki Telephone Co. Teemu Varonen<br />

Finland Nokia Matti Alkula<br />

Finland Nokia Ari Heikkinen<br />

Finland Nokia Harri Honko<br />

Finland Nokia Marko Luomi<br />

Finland Nokia Lippo Rantanen<br />

Finland Nokia Pekka Rissanen<br />

France Daniel Battu<br />

France Jean Pierre Blin<br />

France Lucien Bourgeat<br />

France Pierre Combescure<br />

France Yves Robin-Champigneul<br />

France France Telecom Gerard Dupin<br />

France France Telecom Isabelle Haignere<br />

France France Telecom Claude Lamblin<br />

France France Telecom Franck Lelong<br />

France France Telecom Catherine Quinquis<br />

France France Telecom Georges Sebek<br />

France MATRA Tele<strong>communications</strong> Francois Capman<br />

France MATRA Tele<strong>communications</strong> Carlo Murgia<br />

France MATRA Tele<strong>communications</strong> Didier Rocchia<br />

France SAGEM Gerard Lachaussee<br />

Germany Manfred Magele<br />

Germany Rolf Ruggeberg<br />

Germany Istvan Sebestyen<br />

Germany Alcatel SEL Klemens Adler<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 39


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

Germany Deutsche Telekom Ralf-Rainer Damm<br />

Germany Deutsche Telekom Siegfried Rausch<br />

Germany Deutsche Telekom Joachim Stegmann<br />

Germany Siemens Robert Callaghan<br />

Germany Siemens Martin Euchner<br />

Germany Siemens Gerard Hofer<br />

Germany Siemens Karl Klaghofer<br />

Germany Siemens Markku Korpi<br />

Germany Siemens Gerald Meyer<br />

Germany Siemens Imre Varga<br />

Germany Siemens Bernard Wimmer<br />

Germany TELES Jorg Ott<br />

Germany TELES Stephen Wenger<br />

Hungary MATAV Hungarian Telecomm Tivadar Szabo<br />

Ireland Lake Datacomms Michel McLaughlin<br />

Israel Ami Amir<br />

Israel Philippe Klein<br />

Israel Goory Ronen<br />

Israel Sasha Ruditiski<br />

Israel Uzi Shalev<br />

Italy Giuseppe Rinaldo<br />

Italy Mauro Falcone<br />

Italy CSELT Rosario Drogo De Iacovo<br />

Italy CSELT Federico Tosco<br />

Italy Italtel Renata Guarneri<br />

Japan Mitsuji Matsumoto<br />

Japan Junichi Nakazawa<br />

Japan Sakae Okubo<br />

Japan Akihiko Tsukui<br />

Japan Canon Masao Hosaka<br />

Japan CIAJ Keiichi Hibi<br />

Japan Fujitsu Yasuji Ota<br />

Japan Fujitsu Kiyoshi Sakai<br />

Japan KDD Shigeyuki Sakazawa<br />

Japan KDD Hideaki Yamada<br />

Japan Matsushita Electric Industrial Akira Atsuta<br />

Japan Matsushita Electric Industrial Hioryuki Ehara<br />

Japan Mitsubishi Electric Yushi Naito<br />

Japan Mitsubishi Electric Hirohisa Tasaki<br />

Japan NEC Yoshihisa Aotani<br />

Japan NEC Hidenobu Harasaki<br />

Japan NEC Masahiro Serizawa<br />

Japan NTT Shiji Hayashi<br />

Japan NTT Naoki Kobayashi<br />

Japan NTT Hiroshi Koyano<br />

Japan NTT Kazunori Mano<br />

Japan NTT Takahiro Muraki<br />

Japan NTT Shigeaki Sasaki<br />

Japan NTT Mobile Comm Network Toshiro Kawahara<br />

Japan NTT Mobile Comm Network Takashi Suzuki<br />

Japan Oki Electric Industry Yasuo Aoyagi<br />

Japan Oki Electric Industry Yasubumi Chimura<br />

Japan Oki Electric Industry Minoru Miyazaki<br />

Japan Toshiba Masimi Akamine<br />

Japan Toshiba Barry Aronson<br />

Japan Toshiba Eizo Fujisawa<br />

Japan Toshiba Yoshihiro Kikuchi<br />

Japan Toshiba Kimio Miseki<br />

40 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

Japan Toshiba Hirokazu Tanaka<br />

Japan Toshiba Toshiaki Watanabe<br />

Korea Don Whan Hyun<br />

Korea Samsung Yong Duk Cho<br />

Morocco Driss Lamsane<br />

Poland Andrzej Wykrota<br />

Slovak Republic Slovak Telecom Aljosa Salgovic<br />

Spain Enrique Berrojalvis<br />

Sweden Gunnar Hellstrom<br />

Sweden L.M. Ericsson Bo Burman<br />

Sweden L.M. Ericsson Eric Ekudden<br />

Sweden L.M. Ericsson Magnus <strong>Hall</strong>enstal<br />

Sweden L.M. Ericsson Jan Holm<br />

Sweden L.M. Ericsson Mickey Nasiri<br />

Sweden L.M. Ericsson Anders Svennevik<br />

Sweden Telia Annika Kilegran<br />

Switzerland Armin Blum<br />

Switzerland Rene Koch<br />

Switzerland Siemens Schweiz Rudolph Hasler<br />

Switzerland Swisscom Pierre-André Probst<br />

Syrian Arab Republic Souad Dahdal<br />

Syrian Arab Republic Mohamed Rafic Ghannam<br />

Syrian Arab Republic Nabil Kisrawi<br />

Syrian Arab Republic Bassema Koueder<br />

Thailand Somyot Tanapirunthorn<br />

The Netherlands KPN Jeroen De Muijnck<br />

The Netherlands KPN Cor Quist<br />

UK William Pechy<br />

UK BT Paul Barrett<br />

UK BT Alistar Farquharson<br />

UK BT Mike Nilsson<br />

UK BT Joseph Pointer<br />

UK BT Andrew Woollett<br />

UK GPT Nicholas Winch<br />

UK Hayes Microcomputer Products John Moughton<br />

UK Lucent Mike Buckley<br />

UK Lucent John Magill<br />

UK MADGE Michele Bozier<br />

UK MADGE Andrew Draper<br />

UK Panasonic Standards Europe Alan Pugh<br />

UK Racal Datacom Chris Firth<br />

Ukraine Igor Usov<br />

Ukraine Mykola Vakulenko<br />

Ukraine Alexander Varnosov<br />

USA An Nguyen<br />

USA Andrea Saks<br />

USA Bruce Degrasse<br />

USA Gary Fereno<br />

USA Granger Kelley<br />

USA Mark Neibert<br />

USA Patrick Murphy<br />

USA Paul Jones<br />

USA Radhika Roy<br />

USA 3-COM Fred Lucas<br />

USA 3-COM Richard Stuart<br />

USA 3-COM Richard Williams<br />

USA Analog Devices Rao Nuthalapati<br />

USA Ascend Comm Dale Skran<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 41


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

USA AT&T Richard Cox<br />

USA Bell Atlantic Katrina Hopkins<br />

USA Bellcore Raymond Hapeman<br />

USA Bellcore Ralph Jensen<br />

USA Bellcore Hong Liu<br />

USA Cirrus Logic Vedavalli Krishnan<br />

USA Cisco Systems Rich Bowen<br />

USA COMSAT Corp. Simao Campos-Neto<br />

USA COMSAT Corp. Suat Yeldener<br />

USA Databeam Neil Starkey<br />

USA Delta Information Systems Gary Thom<br />

USA ESS Technology Jordan Cookman<br />

USA Hayes Microcomputer Products Bruce Adams<br />

USA IBM Ali Sadri<br />

USA Intel Narjala Bhasker<br />

USA Intel Vineet Kumar<br />

USA Lucent Carle G. Wray<br />

USA Lucent Glen Freundlich<br />

USA Lucent Sean Ramprashad<br />

USA Lucent Zhongjin Yang<br />

USA Microsoft Jane Dailey<br />

USA Microsoft Toby Nixon<br />

USA Motorola Info. Systems Les Brown<br />

USA Nokia Senthil Sengodan<br />

USA Nortel (USA) Francois Audet<br />

USA Nortel (USA) Slobodan Jovanovic<br />

USA PictureTel Antony Crossman<br />

USA PictureTel Mark Duckworth<br />

USA PictureTel Kaynam Hedayat<br />

USA PictureTel George Helder<br />

USA PictureTel David Lindbergh<br />

USA PictureTel Patrick Luthi<br />

USA PictureTel Marshall Schachtman<br />

USA PictureTel Gary Sullivan<br />

USA Polycom Matt Collier<br />

USA Qualcom Amitav Das<br />

USA Qualcom Peter Jackson<br />

USA Rockwell International Keith T. Chu<br />

USA Rockwell International Tom Geary<br />

USA Rockwell International Thomas C. Liau<br />

USA Sun Microsystems Jenn Yeh<br />

USA Videoserver Georges Kajos<br />

USA Videoserver Mark Reid<br />

USA Videoserver Irina Suconick<br />

USA Voxware Robert Zopf<br />

USA VTEL Smita Gupta<br />

USA VTEL Joon Maeng<br />

42 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

REPORT OF ETSI TM6 ACCESS TRANSMISSION SYSTEMS ON METALLIC<br />

CABLES, SEPTEMBER 21 – 25, 1998, VIENNA, AUSTRIA<br />

Note: As of November 1, 1998, any user can now access, free of charge, the complete range of ETSI Publications,<br />

including European Standards in the tele<strong>communications</strong> series (EN, ETS, I-ETS, TCR-TR, AN, EG, ES, ETR,<br />

GTS, NET, SR, TBR, TR, TS). Use the Publications Download application located at<br />

http://webapp.etsi.org/publicationssearch to download individual copies of ETSI Publications in Adobe Acrobat<br />

Reader format (.pdf).<br />

H.-J. Frizlen (ETSI STF, Ericsson) is the TM6 Chair. Sixty-two delegates, representing fifteen countries including<br />

Slovenia and the Czech Republic and including new delegates from the former TM3 Working Party A, were<br />

registered.<br />

Documents TD-1 and TD-2 are the agenda and summary of work items extracted from the ETSI database. TD-0 (A.<br />

Carrick, ASCOM and acting TM6 secretary) is the updated list of abstracts received at the start of the meeting.<br />

The new group ANAI (Access Network Architecture and Interfaces), formerly TM3 Working Party A, now takes part<br />

in the TM6 work; it will hold fewer meetings than TM6, roughly one meeting of ANAI for two TM6 meetings. B.<br />

Orth (DTAG) is the temporary rapporteur of ANAI.<br />

Except for the ISDN-BA rapporteur, whose work is completed, the TM6 rapporteurs (ADSL, VDSL and<br />

HDSL/SDSL) were confirmed. Two new rapporteurs were appointed within ANAI: A. Profumo (ITALTEL) is<br />

rapporteur of the RTR/TM-03075, “Broad-band access digital section and NT functional requirements”; P. Battistello<br />

(France Telecom) is rapporteur of REN/TM-03086, “Cell based UNI for 155 Mbit/s and 622 Mbit/s”.<br />

An editing group, chaired by Mr. Gindle (Austrian Telecom), will establish a list of definitions and abbreviations<br />

relating to TM6 documents. This is not a rapporteur group because of the short duration of its task, and no work<br />

item was created within TM6.<br />

The TM6 Chair attended the TM meeting held in Helsinki September 14-18. The terms of references of TM6 have<br />

been changed because of the merger with the former TM3 working group; TM6 number remains TM6 because of its<br />

relations to T1E1 and ITU-T.<br />

FSAN (FULL SERVICE ACCESS NETWORK) LIAISON<br />

D. Clark (British Telecom) gave a presentation (WD-23) of the activity of FSAN and invited manufacturers to<br />

participate in the FSAN Boston meeting, October 7-8, 1998. FSAN, a telco oriented body, was convened to define<br />

the system requirements (especially spectral compatibility issues) for VDSL as an integral part of a full service<br />

access network. Since the work of FSAN is vital to TM6, some members felt that this work should be done within<br />

ETSI. The TM6 Chair stated that collaboration with FSAN has been good and did not see any reason why it should<br />

not continue.<br />

T1E1 LIAISON<br />

There are no formal liaison officers from T1E1 to TM6, and the TM6 Chair regrets that situation. L. Humphrey<br />

(Nortel) read a liaison statement from E. Eckert (Chair, T1E1) to the TM6 Chair indicating completion of work on<br />

ADSL document issue 2 and gave a verbal report of the last T1E1 meeting. All letter ballot comments on T1.413<br />

issue 2 have been resolved; it should now be moving to publication. ANSI will most likely recommend that work<br />

on xDSL (all the different Digital Subscriber Line services) be started within ITU-T, especially when dealing with<br />

spectral compatibility; the work within T1E1 on spectral compatibility has not been very successful and has led<br />

more to a spectral incompatibility. The RADSL (Rate-Adapting ADSL) document has been sent to vote as a<br />

Technical Report, not a Standard.<br />

ADSL FORUM LIAISON<br />

B. Dugerdil (Motorola), the official liaison between TM6 and ADSL, was unable to attend the last ADSL Forum<br />

meeting.<br />

Liaison statements WD-01 (transmittal document requesting ETSI comment on WD-02) and WD-02 (working text<br />

for ATM over ADSL Recommendation) were received from ADSL. They were assigned to ANAI for study and<br />

reply.<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 43


TM LIAISON<br />

COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

At the instigation of British Telecom in the TM meeting, TM approved a liaison statement to ITU-T SG15 Q4<br />

stating that ITU-T should not start work on VDSL (Very high speed ADSL) as long as the regional standard bodies<br />

have not completed their work. TM6 was asked to endorse liaison statement WD-05 (from Deutsche Telekom AG,<br />

France Telecom, Telia, Sagem, Nokia and Sonera in support of the earlier BT position) and to add names to the list<br />

of members supporting those liaison statements; TM6 drafted a similar liaison statement concerning SDSL (WD-06,<br />

source BT, Deutsche Telekom AG, France Telecom, Telia and Sagem). Some members feel that ITU-T should be<br />

kept aware of the progress of the work within ETSI; others feel the contrary.<br />

Also at the instigation of British Telecom in the TM meeting, two working documents (WD-03 and WD-04) were<br />

liaised to TM6 concerning potential problems raised by the application of the just-approved CTR (Common<br />

Technical Requirements) 21; one problem is that a non-voice TE (Terminal Equipment) approved to CTR 21 (TBR<br />

[Technical Basis for Registration] 21, Requirements for pan-European approval for connection to the analog PSTN)<br />

may generate noise above 200 kHz which will disturb ADSL and other xDSL TEs; another problem is that CTR 21<br />

cannot be applied to G.lite-like TEs and/or to other TEs specified by the Home Appliance Association and which use<br />

the non-voice part of the available line spectrum; there is a gap in the pan-European approval requirements for that<br />

equipment. An ad-hoc group was constituted under the responsibility of K. Foster (BT); the conclusions of that<br />

group are contained in WD-13. WD-13 notes that TBR-21 is technically flawed and should be fixed quickly. It is<br />

primarily deficient in the lack of sending level limits above 200 kHz. Liaisons were drafted to TRAC (Technical and<br />

Regulatory and Approvals Committee responsible for pan-European approval of TE) and the ETSI Board to<br />

determine whether a new TBR is required for DSL.<br />

ISDN TRANSPORT<br />

HDSL (HIGH-RATE DIGITAL SUBSCRIBER LOOP)<br />

After some periods of instability, the HDSL document (issue 5 of TS 152) is finally stable. TD-52, Request for<br />

Clarification of Subclause 7.7.3.2 (C. Heidelberger, Schmid Telecom AG), gives a minor editorial comment<br />

concerning the application of the scrambler only to the ISDN bits and not to synchronization and to the justification<br />

bits. With this agreed modification, the issue 5 of now TS 101 135 will go to TM for approval and publication.<br />

S. Schmoll (Alcatel) indicated that the ITU Recommendation G.991.1 on multi-pair HDSL, based on TS 101 135,<br />

is likely to be approved at the October SG15 meeting. WD-21, the Living List of HDSL, has therefore been closed<br />

after six years of work.<br />

HDSL2<br />

A T1E1.4 working draft of the HDSL2 Standard from ADC Tele<strong>communications</strong> was tabled as WD-07; no<br />

discussion took place on this document, which is not on the present list of work items of TM6.<br />

ANAI (ACCESS NETWORK ARCHITECTURE AND INTERFACES)<br />

Two work items are assigned to ANAI:<br />

RTR/TM-03075, Broad-band access digital section and NT functional requirements (Rapporteur, A. Profumo)<br />

REN/TM-03086, Cell based UNI for 155 Mbit/s and 622 Mbit/s/s (Rapporteur, P. Battistello)<br />

It is assumed that another work item will be phasing out DTS/TM03024 revisions to TS 101 272 (Requirements of<br />

Optical Access Networks for evolving services). WD-16 gives part of the preceding meeting (May, 1998) report. B.<br />

Orth (DTAG), coordinator of ANAI, presented the report of ANAI activity (Vienna Sept. 21-25, 1998) in WD-17.<br />

TS 101 272, REQUIREMENTS OF OPTICAL ACCESS NETWORKS FOR EVOLVING SERVICES<br />

TD-6 (S. Webster, NEC) is the second version of items for the possible revision of TS 101 272 V1.1.1 (the former<br />

DTS/TM-03024). Agreements reached at the final TM3 meeting in Sophia Antipolis, May 1998, have been<br />

incorporated.<br />

At the last meeting of the FSAN OAN group, a document with the required editorial changes to the draft<br />

recommendation G.983 (G.983.1, G.PONB for ATM-PON System) was provided for the next ITU-T SG15 meeting<br />

in October 1998. TD-9, Proposals for the Living List of TS 101 272 (I. Marlow, Deutsche Telecom AG), provides<br />

a part of the ITU-T document, including all those changes which had not been submitted to ETSI before this<br />

meeting. The remaining part of the ITU-T document was already incorporated in TS 101 272 during the TM<br />

approval. In sum, these changes are to maintain alignment of G.983 and TS 101 272.<br />

44 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

REN/TM-03086 (REVISION OF ETS 300 299)<br />

TD-7, Simulation result on the simplified mechanism proposed for DSS synchronization process (P. Battistello,<br />

FranceTelecom-CNET), was presented for information. It provides simulation results based on real implementation<br />

for the simplified DSS synchronization mechanism which was proposed in ETSI TM3 Bern meeting (TD-02) and<br />

which is still in the Living List as “Under Study.” These simulation results confirm the theoretical analysis detailed<br />

in previous contribution.<br />

TD-8, ANAI Technical Comments on ETS 300 299 (P. Battistello, FranceTelecom-CNET), addresses three technical<br />

points that should be clarified during the next revision of ETS 300 299. These technical points are:<br />

1) Applicability of HEC (header error control) single bit error correction mode (§10.3.1)<br />

2) HEC regeneration and header scrambling (§10.5.3.3)<br />

3) Automatic scrambling detection (§10.5.3.3)<br />

WD-20 includes for information the latest text of the ITU-T I.432.1 Recommendation.<br />

BROAD-BAND ACCESS DIGITAL SECTION AND NT FUNCTIONAL REQUIREMENTS (DTR/TM-03007)<br />

TD-18, Proposed Methodology for xDSL NT1 Functional Specification (R. Boden, Philips), suggests a possible<br />

way to specify NT (Network Termination) functionality by using a functional modeling approach; this specification<br />

method is based on functional decomposition of the equipment into atomic functions. The equipment is then<br />

described by its P2S Equipment Functional Specification which lists the atomic functions, their interconnection and<br />

any overall performance objectives.<br />

WD-18 is the reply to WD-1 received from ADSL, which accepts that the final version of the TR shall include<br />

comments regarding VB56 usage, F4 flows, and the inconsistency to route a single path via different links.<br />

The following were presented for information:<br />

WD-11 (NEC, Functional architecture for xDSL Dual Latency)<br />

WD-14 (Nortel to the ADSL Forum, a simple device protocol)<br />

WD-15 (Nortel to the ADSL Forum, a new NT type between NT1 and NT2)<br />

MISCELLANEOUS<br />

TD-20, Application of DTM in Access Network (M. Meninger, SPT TELECOM), summarizes basic properties of a<br />

new transfer mode (DTM [Dynamic Transfer Mode]) and asks if TM6 should consider its applicability in access<br />

network.<br />

The forthcoming ANAI meeting will be held the last week of November. J. Besseyre (Consultelecom) asked if the<br />

ANAI meeting might be not be held in Sophia Antipolis at the same time as the SDSL/VDSL meeting, 24-27<br />

November, 1998; since ANAI is now part of TM6, some delegates agreed that it should meet at the same time to<br />

profit from the synergism between the former TM3 and TM6 and to avoid unnecessary travel.<br />

SDSL<br />

The SDSL session was chaired by S. Schmoll (Alcatel). S. Schmoll highlighted first the difference between the US<br />

requirements and the European operator-expressed requirements in terms of transport of ISDN, reach, remote<br />

powering, latency, and power available/needed to/by the SDSL equipment.<br />

The operator requirements are dealt with first.<br />

• TD-51, Functional Requirements for SDSL (C. Pellicer Losato, Telefonica), expresses Telefonica’s functional<br />

requirements. It suggests that narrowband services (e.g., telephony) should be transported in the digital core<br />

frame to avoid the requirement for a splitter and that remote power feeding should be optional.<br />

• TD-45 (L. Tempestilli, Telecom Italia and L. Magnone, CSELT) indicates the requirements for SDSL seen by<br />

Telecom Italia; the existing solutions for HDSL (2B1Q and CAP) should be investigated first before looking into<br />

new modulation solutions.<br />

• TD-37, Further Requirements on SDSL (T. Stefansson, Telia Research AB), presents their requirements based on<br />

a target application of SOHO IP applications.<br />

• WD-08 presents a late contribution on the requirements for SDSL as seen by France Telecom. It suggests reach<br />

of 4.5 km at 384 kbit/s and 3 km at 2.048 mbit/s on 0.4 mm wires.<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 45


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

Once those later requirements were known, as well as some changes expressed by BT, the discussion concentrated on<br />

TD-4, Requirements for a SDSL Transmission System (S. Schmoll, Alcatel): Five operators (BT, Deutsche<br />

Telekom, Finnet Group, PT Austria, and Telia) presented a list of their requirements for a SDSL transmission<br />

system. These requirements are taken from the report of the Luleå meeting, sub-clause 4.4.<br />

A lengthy discussion took place; the most controversial topics were splitter versus in-frame transmission of the<br />

POTS/ISDN services, need for remote powering of the “lifeline” service, and of the SDSL modem in part or in<br />

totality. “Range is more important than bit rate.” Bit rate is defined as the actual data rate available to the SDSL<br />

data user. It does not include the overhead for framing, signaling and management and may be quite different for<br />

splitter vs. non-splitter solutions. The SDSL user data bit rate does not assume any baud rate on the line. As a<br />

result of this discussion, there were a few conclusions agreed by all delegates, contained in WD-24:<br />

• Data bit rate 384 kbit/s/s to 2.304 kbit/s/s<br />

• Reach of 3 kms at 2.048 kbit/s/s and reach of 4.7 kms at 384 kbit/s/s (same reach as basic rate ISDN)<br />

• Granularity nx64 kbit/s (user bit rate)<br />

• A management channel (which may be a logical channel) is needed with a bit rate of up to 64 kbit/s<br />

• No handshaking; no rate adaptation but fixed rates at installation time.<br />

Items for further study are: remote powering numbers (POTS power) and splitter vs. in-frame solutions.<br />

TD-25, Central Office Powering for SDSL (M. Sorbara, GlobeSpan), describes some power budgeting guidelines for<br />

SDSL system dissipation supporting lifeline applications via the NTU. To provide the associated lifeline service for<br />

the voice channel, the NTU (network termination unit) would need to be powered from the central office. Depending<br />

on the power dissipation of the components in the NTU, the reach of SDSL may be limited by either NTU power<br />

dissipation or core modem transmission capability. This contribution recommends that power budgeting be<br />

incorporated in the SDSL report. As a result of this TD, an ad-hoc group was formed; the conclusions are given in<br />

the full meeting report and in WD-19. WD-19 contains conclusions that were not agreed by some delegates and that<br />

are different from the conclusions reached by the ad-hoc meeting. Operators are invited to contribute on the power<br />

needs of a POTS telephone; the figure of 450 mW seems overoptimistic.<br />

TD-39, Remote Powering (M Kempe, Siemens) addresses the issue of remote powering in SDSL. Its conclusions<br />

come very close to TD-25 and were also considered by the ad-hoc group on powering budget.<br />

TD-26, Customer Premises Wiring for SDSL (M. Sorbara, GlobeSpan) describes various premises wiring scenarios.<br />

One of the key requirements for SDSL is to simultaneously provision a data channel along with either a telephone or<br />

ISDN channel. If SDSL service is to be provisioned in the residential environment (for either business or consumer<br />

applications), then the impact on premises wiring must be considered. This contribution recommends that premises<br />

wiring be included in the Living List and in the SDSL report.<br />

TD-12, SDSL: POTS Splitter Considerations (A. Carrick, Ascom AG), proposes various items for addition to the<br />

Living List for SDSL for further study, based on the results of laboratory tests of simple proof-of-concept POTS<br />

splitters tested with existing TS 101 135 HDSL systems. While most operators initially had put in their<br />

requirements of no splitter and imbedded transmission, this presentation asks the questions in terms of performance<br />

and challenges the actual requirements for no-splitter operation.<br />

For maximum reach at minimum power, the POTS splitter band offers excellent SNR (Signal to Noise Ratio)<br />

which cannot be easily recovered elsewhere in the spectrum. TD-38, Capacity and POTS Splitters (M. Kempe,<br />

Siemens), shows that, from a capacity point of view and for both PAM (Pulse Amplitude Modulation) and<br />

CAP/QAM (Carrier-less Amplitude Modulation Phase Modulation/Quadrature Amplitude Modulation) modulation<br />

formats, there is a clear advantage in carrying POTS in a digital form via in-band transport rather than using an<br />

analog form via a POTS splitter.<br />

TD-30 on mixed crosstalk issues from Lucent and Cicada Semiconductor was postponed to the next meeting because<br />

it proposes line coding considerations. It notes that ANSI T1E1.4 chose the OPTIS (Overlapped PAM Transmission<br />

with Interlocking Spectra) line code for HDSL2.<br />

TD-3, SDSL Spectral Compatibility Issues (A. Carrick, Ascom AG), presents a summary of the signal spectra that<br />

could be expected in the access environment, and illustrates the possible cross-talk into SDSL. The artificial shaped<br />

noise model used previously to represent crosstalk in the local network is inadequate for this new environment, and a<br />

new test noise model must be developed. It should be based upon an agreement as to the other systems with which<br />

SDSL is expected to share the network, and the amount of performance degradation that existing systems can tolerate<br />

when SDSL is added to the network. While this presentation was well received, some delegates felt that it gives an<br />

unfair representation of the actual OPTIS performance in a European environment.<br />

46 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

TD-10, SDSL: Baseline Proposals for Performance Requirements (A. Carrick, Ascom AG), presents proposals for<br />

baseline performance requirements as a starting point for the design of the new optimum line code for SDSL. It presents<br />

performance curves for the HDSL systems of TS 101 135, and it proposes that the new optimum SDSL<br />

system should be designed to outperform the first generation HDSL systems by the order of 6 dB, with an additional<br />

4 dB improvement gained by optimizing the test noise.<br />

TD-11, SDSL: Proposed Requirements for Bit Rate Granularity (A. Carrick, Ascom AG, Study Point 3 of the<br />

Living List for DTS / TM-06011-1, Functional requirements for SDSL), proposes a bit rate granularity of n x 128<br />

kbit/s for SDSL systems. This contribution is based on the analysis of existing HDSL systems, although a<br />

granularity of n x 256 kbit/s should be for further study for line rates exceeding 1536 kbit/s. While this<br />

contribution was well received by the manufacturers, the operators seemed to keep their requirement for a granularity<br />

of n x 64 kbit/s.<br />

TD-43, Noise Model Wish List for SDSL Performance Test (R. Van den Brink, KPN), provides a wish list of<br />

information required to generate a comprehensive noise model for the SDSL tests. The contribution uses the<br />

existing VDSL noise specification and points out areas that need to be investigated. WD-27 provides a copy of the<br />

foils presented by R. Van den Brink in relation to the content of TD-27, presented in the VDSL discussion but also<br />

applicable to SDSL.<br />

LIVING LIST<br />

The following Living List (WD-25) was established by the rapporteur:<br />

SP1-1 Functional requirements<br />

SP1-2 Investigation of an optimal line code<br />

SP1-3 Rate Adaptation<br />

SP1-4 Asymmetric transmission methods<br />

SP1-5 Creation of an appropriated noise model<br />

SP1-6 Network Termination functions of sub-channels (new)<br />

SP1-7 Feasibility of defining a suitable reference point MIB (new)<br />

SP1-8 Management of link failure (new)<br />

SP1-9 Power budget for remote power feeding (new)<br />

SP1-10 Transport of narrow-band signals (new)<br />

SP1-11 POTS premises wiring considerations (new)<br />

Even though the noise model for SDSL is not yet defined (see discussion on VDSL, below), contributions are<br />

invited on transmission and electrical characteristics.<br />

COEXISTENCE WITH ISDN<br />

ADSL<br />

TD-5 (G. Rose, ETSI Secretary) contains results and comments from TM6 approval for DTS/TM-06006 (ADSL:<br />

Coexistence of ADSL and ISDN BA on the same pair and ADSL extended bit-rates). In order to achieve consensus,<br />

the rapporteur and the TM6 Chair asked to resolve the “no” vote from BT (British Telecom). A new point was added<br />

to the ADSL living list to study the ADSL performance on test loops. The TM delegates also decided to open a new<br />

work item to issue a new document corresponding to the new T1E1 ADSL issue 2 document. A discussion followed<br />

as to which document should be the base for ETSI’s new document: G.lite, T1E1, or UAWG documents, none of<br />

which are compatible with each other. The T1E1 document was agreed to be the base for any new ETSI document.<br />

TD-49 (P. Reusens, Alcatel) suggests corrections to some of the time-outs in the diagrams; the corrections were<br />

accepted for the ADSL over ISDN document.<br />

TD-47, Definition of the C-TONE for ADSL over ISDN (P. Reusens, Alcatel), was accepted. The sets of tones used<br />

in ETSI TM6 DTS/TM-06006 do not include the C-TONE (defined in ANSI T1.413 issue 2 for ADSL above<br />

POTS). Within G.dmt, C-TONE disappears completely, because it is replaced by G.handshake (G.hs). However, in<br />

the (unlikely) case that a purely tone-based activation of the ADSL over ISDN is defined, we still need to define C-<br />

TONE. The proposal is to put it on tone 82, which is an even carrier, and not a multiple of 8. (Multiples of 8 are<br />

now accepted for the carriers used by downstream in G.hs for G.dmt.) A new study point was added to the ADSL<br />

Living List and a note in the document will be added.<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 47


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

WD-10 and TD-48, Safety of ADSL above POTS or ISDN according to IEC 950 (P. Reusens, Alcatel), raises the<br />

issue that when one adds the DC voltage, the ISDN voltage, and the ADSL voltage, one comes out with a voltage<br />

across the line which exceeds the IEC limit of 120V. According to the (rigorous) interpretation of the IEC 950<br />

regulations, the sum of all signals of the telephone line must be considered “dangerous”, when the ISDN battery<br />

(nominally above 90 V DC) and both the ISDN and the ADSL AC signals are present on the line. It appears that<br />

the IEC 950 regulation is not aware of xDSL technology and is applying unnecessarily strict rules. It seems<br />

necessary to study the safety of the xDSL products in the IEC and to specify new rules for these xDSL cases above<br />

ISDN. One delegate from Alcatel Germany is attending the IEC conference in Toronto and this establishes an<br />

informal link to IEC; S. Schmoll (Alcatel) will inform TM6 delegates of the result of that discussion in the<br />

forthcoming meeting of TM6.<br />

TD-46, Framework Proposal for Revision of ETSI ADSL Technical Specs (L. Magnone, CSELT, rapporteur of<br />

ADSL), proposes a revision to ETR 328 (ADSL technical report based on T1.413 issue 1) as well as a revision to<br />

the just approved TS-06006 (Asymmetric Digital Subscriber Line (ADSL) - Coexistence of ADSL and ISDN BA on<br />

the same pair and ADSL extended bit-rates [revision of T1.413]). TM6 delegates agreed to create a new work item<br />

(European-specific ADSL requirements based on ANSI T1.413 issue 2) to be drafted by G. Rose (ETSI Secretariat).<br />

This is contained in WD-26 and was approved by TM6. All other work items in ADSL are closed.<br />

TD-50, G.lite: bit-swap (P. Reusens, Alcatel), states that different standardization bodies are involved in the G.lite<br />

variant of ADSL; in G.lite bit-swap is proposed but is not yet agreed; technically, bit-swap is judged a necessary element<br />

in protecting DMT transmission against varying noise sources. This contribution presents its technical<br />

merits and encourages European manufacturers and operators to endorse bit-swap, to make it mandatory in any ETSI<br />

document and to vote in favor in the ITU-T. The meeting agreed that bit-swap should be mandatory in Europe;<br />

individual members are asked to contribute into the ITU-T. (See also the discussion on bit swap in the WP1/15<br />

report in this issue of CSR-T.)<br />

TD-27, Proposal for SDSL performance tests (R. Van den Brink, KPN), is a detailed proposal for test loops, noise<br />

models and test requirements on SDSL. The framework of this text is mainly based on the VDSL performance tests,<br />

but dedicated to the SDSL frequency band. It enables well-defined performance simulations on SDSL to support the<br />

future definition of realistic SDSL requirements such as spectral masks, bit rates, loop length, etc. While TD-27<br />

was presented in the ADSL session and the VDSL session, it also applies to SDSL. The TM6 chair proposed to<br />

make an ETSI Technical Report out of this document; however, R. Van den Brink did not agree to become the<br />

rapporteur for this ETR, so TD-27 will become a permanent TM6 document instead; this vital document needs to<br />

have inputs for SDSL which are encouraged for the forthcoming TM6 meeting. The set of foils that were presented,<br />

which are somewhat different from the content of TD-27, were tabled as WD-22.<br />

VDSL<br />

This VDSL session did not have any document for approval. B. Waring, rapporteur for VDSL, asked delegates for<br />

more participation between meetings so as to move the work faster. The session consisted of a presentation of most<br />

of the contributions and a discussion on how to advance the VDSL specification.<br />

TD-34, TC Sublayer-ATM Transport Protocol Specific TC (V. Oaxman, Lucent technologies for VDSL Coalition),<br />

proposes a specification of the ATM Transport Specific Transmission Convergence sublayer (ATM-TC) which describes<br />

the ATM-based service transmission over VDSL system. This document defines a minimum set of<br />

requirements to deliver an ATM service from the ONU to the customer premises.<br />

TD-41, ATM-TC for VDSL (L. Humphrey, Nortel/Bay Networks), outlines an ATM TC for VDSL which<br />

accommodates power saving and crosstalk saving modes by allowing the transmitter to enter a low power state<br />

during transmission of idle cells. This proposal was not yet accepted by the VDSL Alliance and may be subject to<br />

reconsideration if dynamic power saving becomes relevant.<br />

TD-33, VDSL Payload Rates for Symmetric Services (V. Oaxman, Lucent technologies for VDSL Coalition),<br />

proposes a new set of payload bit-rates for performance evaluation of VDSL link transporting symmetric services.<br />

The document is based on previous contributions to TM6. The new definition of evaluation rates provides an<br />

effective usage of VDSL payload for symmetric services, the main component of which is SDH. The proposed<br />

approach is independent of the line coding and of the modulation technology.<br />

TD-40, VDSL Frame-OAM and Narrow-Band Service Delivery (L. Humphrey, Nortel), proposes a format for a<br />

generalized clear Embedded Operations Channel (EOC) channel which supports transmission of network timing reference<br />

and maintenance indicator bits. The method also supports the in-band transmission of n x 64 kbit/s telephony<br />

48 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

channels and multiple plesiochronous independent streams. TD-40 was accepted as input to study points SP1-14 and<br />

SP 1-20.<br />

TD-28 (K. Jacobsen, Amati/TI) is the latest draft of the VDSL Alliance’s DMT proposal for VDSL. The proposal<br />

specifies both a time-division duplexed (TDD) and frequency-division duplexed (FDD) system. In both cases,<br />

compliant modems support both symmetric and asymmetric transmission. Support of 1:1, 2:1, 3:1, 4:1, 6:1 and<br />

8:1 transmission is mandatory, as is rate adaptivity at start-up. Support of ATM is also required. TD-28 is to be<br />

incorporated into the draft of TM 06 003-2.<br />

TD-31 (V. Oaxman, Lucent technologies for VDSL Coalition) proposes line coding, modulation and duplexing<br />

methods for VDSL systems using single carrier technologies (CAP and QAM). It specifies a PMD sub-layer for<br />

both NT and LT which complies with the VDSL system requirements as specified in DTS/TM-06003-1. The<br />

proposal supports all the ETSI downstream rates with either symmetric or asymmetric upstream rates. The proposed<br />

coding and modulation methods provide full interoperability between CAP and QAM transceivers. This document<br />

was accepted for draft TM6 003-2.<br />

TD-32 (V. Oaxman, Lucent technologies for VDSL Coalition) proposes a specification for the VDSL transmission<br />

frame format, frame delineation algorithm, randomization and FEC methods. The proposed frame format optionally<br />

contains Fast and Slow virtual data channels and provides both for single and dual latency operations. The<br />

transmission frame header bears frame alignment, NTR and control information. The proposed methods are<br />

independent of the line coding modulation technology. This document was accepted for draft TM6 003-2.<br />

TD-17 (K. Foster, BT) summarizes the progress in resolving the following VDSL Living List items : SP1-1, SP1-<br />

2, SP1-20, SP2-9. It collates the e-mail discussion which has occurred since the last TM6 meeting and makes some<br />

proposals to progress the work.<br />

TD-13, Editor’s report on the ANSI VDSL System Requirements (J. Cioffi, Stanford University, Editor for the<br />

VDSL ANSI) attaches Rev 16a of the ANSI VDSL System Requirements. It differs from the Rev 16 official liaison<br />

only in the correction of some typographical errors found after the San Antonio meeting and posted on the T1E1.4<br />

web page. Also included here for information is the editor’s summary of differences with ETSI TM6 Phase I<br />

technical report for VDSL. These are probably of a nature that a single implementation could be designed that will<br />

comply with both specifications.<br />

TD-14, Mixed Loading for Splitterless DSL Operation (J. Cioffi, Stanford University), describes a method for<br />

recovering from abrupt line changes, like off-hook impedance changes in splitterless operation, without service disruption.<br />

The method allows a guarantee of a fixed high-quality continuous service on the line that is augmented by a<br />

rate-adaptive non-guaranteed data rate. This method would allow the option of not using any fast-training in<br />

splitterless DSL operation, thus preserving quality of service for DSL even when operating without splitters.<br />

TD-15, Further Results on Peak-to-Average Ratio Reduction (J. Cioffi, Stanford University), shows that if PAR<br />

reduction is done on these Nyquist rate samples, the PAR of the continuous time wave form can increase significantly,<br />

but if we extend the tone-reservation and tone-injection algorithms to reduce the PAR at twice the Nyquist<br />

rate, the continuous time PAR can be efficiently reduced. Moreover, for the tone-injection method we can extend<br />

our previous algorithms to include the effects of the transmit filter, which leads to PAR reductions of more than 5<br />

dB at the AFE input.<br />

TD-16, Mitigation of DSL Crosstalk via Multi-user Detection and CDMA (J. Cioffi, Stanford University), presents<br />

fundamentals of multi-user detection and multi-user information theory to suggest that the current DSL approach to<br />

modeling and specification of DSL spectral compatibility are overly pessimistic. Some examples and fundamental<br />

information-theoretic results suggest that crosstalk can be substantially mitigated without coordination or access to<br />

inputs or outputs of crosstalking pairs, depending on the level of background additive white Gaussian (AWG) noise.<br />

TD-19, A Request for Clarification from the Telcos on the VDSL Requirements (M. Kempe, Siemens/Savan), raises<br />

five issues for clarification of the requirements as part of the feedback from the equipment suppliers to the Telcos,<br />

prior to the definition of Part 2 of the VDSL specification.<br />

TD-21, Throughput of Short Range VDSL Services (A. Kliger, Metalink), corrects the results of a former<br />

contribution. The former contribution considered the transport of S3 with transmitted mask M1. This contribution<br />

take the slow decline of mask M1 between 10 MHz and 20 MHz into account. It also considers a flat PSD mask of<br />

-70 dBm/Hz and -75 dBm/Hz between 10 and 20 MHz. It concludes that with those modifications, the performance<br />

of S3 and S4 services are improved significantly.<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 49


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

TD-42, Specification of crest distribution mask for noise in performance test (R. Van den Brink, KPN), states that<br />

the current VDSL performance test puts insufficient requirements on the nature of the noise signals to be used in the<br />

performance test. It proposes to use a mask for the crest distribution function of the test noise. As the shape of the<br />

mask is not yet defined, this document did not convince all delegates.<br />

TD-35, Achievable bit rates with the constant power back-off method (T. Kessler, DTAG), notes that the achievable<br />

upstream bit rates of VDSL with NTs distributed along a cable have been calculated for different maximum distances.<br />

For a maximum distance of 1.5 km, a bit rate of 13 Mbit/s upstream and 13 Mbit/s downstream cannot be achieved<br />

with FSAN-noise and constant power back-off. The required dynamic range depends on the maximum distance and<br />

the reference frequency. It is suggested that only a management system can set optimal power back-off for all VDSL<br />

systems within a cable.<br />

TD-17 from the Luleä meeting describes various power backoff methods to reduce the effect of FEXT coupling from<br />

short lines into long lines in the distributed cable topology. The contribution examined three alternatives. TD-29,<br />

Proposal to Use Frequency-Dependent Upstream Power Backoff (K. Jacobsen, Amati/TI), examines the<br />

implementation complexities of the constant power backoff and reference length methods. It concludes that the<br />

reference length method should be used by VDSL systems to maximize performance. TD-29, together with TD-35,<br />

was added to study point 1-18 of the VDSL Living List.<br />

TD-36, VDSL Deployment, Services, and Customers, Part 2: Shared access with flexible symmetry (D. Bengstrom,<br />

Telia Research AB), introduces the fact that customer initiatives regarding VDSL deployment reveal potent nichemarkets<br />

for VDSL and raise technical issues as well. The concept of “Shared access” business case is discussed, as<br />

well as the corresponding network structure and the requirements it puts on VDSL. The new application is a<br />

building LAN shared among several tenants and communicating with the outside building world through VDSL.<br />

TD-36 was added to the Living List study point 1-20 and was sent to ADSL Forum as a liaison (WD-28).<br />

TD-44, Noise model Wish List for VDSL Performance Test (R. Van den Brink, KPN), addresses the information<br />

that is required to complete the VDSL noise model. Although much progress has been made, there are still areas<br />

where operator input is required to generate a noise model that is representative of the VDSL reality.<br />

As a result of these contributions, the VDSL Living Lists (for part 1 and part 2) will be updated; some study points<br />

will be deleted due to lack of contributions.<br />

Jacques Besseyre, Consultelecom<br />

COMMUNICATIONS STANDARDS REVIEW ALSO PUBLISHES:<br />

Communications Standards Summary (ISSN 1075-5721), a quarterly publication reporting on all<br />

active projects and recently completed <strong>standards</strong> of the TIA’s (Tele<strong>communications</strong> Industry Association’s)<br />

TR-committees. Authorized by TIA.<br />

For more details visit http://www.csrstds.com. To receive a complimentary issue of<br />

either of CSR’s technical journals, please contact Elaine Baskin, tel +1 650 856-9018,<br />

fax +1 650 856-6591, e-mail: ebaskin@csrstds.com<br />

50 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

REPORT OF WORKING PARTY 1/15, NETWORK ACCESS<br />

OCTOBER 12 – 23, 1998 GENEVA, SWITZERLAND<br />

The Working Party 1/15 (Network Access) chair is A. Nunn (UK). COM 15-R 9 is the previous meeting report.<br />

TD-38(PLEN) is the report of this meeting. TD-40(PLEN) is the status of the WP1/15 Recommendations.<br />

TD-41(PLEN) contains the liaison statements sent from this meeting.<br />

The Working Party proposed the ITU TSAG a new standardization area, Access Networks, and requested the TSAG<br />

allocate an appropriate code (TD-41(PLEN), WP1/15 liaisons, Annex 12).<br />

The questions currently allocated to WP 1/15 are:<br />

Q Title Rapporteur<br />

1/15 Access Network Transport R. Feigel, Bosch<br />

2/15 Characteristics of Optical Systems in Local Access Networks T. Finegan, BT<br />

3/15 DCEs for Digital Leased Circuits G. Sebek, France Telecom<br />

4/15 DCEs for Subscriber Access Systems R. Stuart, 3Com<br />

TD-51(WP1/15) contains proposed revisions to the Questions in WP1/15. The titles and text of Q2/15 and<br />

Q4/15 were revised to reflect the requirements of networks optimized for the transport of IP and IP-based services.<br />

The new titles are:<br />

Q2/15 Characteristics of Optical Systems in Local Access Networks for Transport and Distribution<br />

Q4/15 Transceivers for Subscriber Access Systems<br />

The text of the revised Questions is in TD-72(PLEN).<br />

WP1/15 RECOMMENDATIONS APPROVED AT SG15<br />

Q Approved Recommendations Document(s)<br />

2/15 G.983.1, G.PONB for ATM-PON (Asynchronous Transfer TD-26(PLEN 2/98), TD-39<br />

Mode - Passive Optical Network) System<br />

(WP1/15 2/98) + COM 15-110<br />

4/15 G.991.1 (G.hdsl) High Bitrate Digital Subscriber Line (HDSL) TD-38(PLEN 2/98) + COM 15-<br />

Transmission System on Metallic Local Lines<br />

123<br />

Table 1. Recommendations Approved (Decided) at Working Party 1/15, October 1998.<br />

WP1/15 RECOMMENDATIONS DETERMINED AT SG15<br />

Q Determined Recommendation Document(s)<br />

3/15 V.300, ex V.144K, A 144 kbit/s Data Circuit Terminating Equipment<br />

Standardized for Use on Digital Point-to-Point Leased Circuits<br />

TD-43 (PLEN)<br />

4/15 G.992.1 (G.dmt) Asymmetrical Digital Subscriber Line (ADSL) Transceivers TD-44 (PLEN)©<br />

4/15 G.992.2 (G.lite) Splitterless Asymmetrical Digital Subscriber Line (ADSL)<br />

Transceivers<br />

TD-45 (PLEN)©<br />

4/15 G.994.1 (G.hs) Handshake Procedures for Digital Subscriber Line (DSL)<br />

Transceivers<br />

TD-46 (PLEN)©<br />

4/15 G.995.1 (G.ref) Overview of Digital Subscriber Line (DSL) Recommendations TD-47 (PLEN)©<br />

4/15 G.996.1 (G.test) Test Procedures for Digital Subscriber Line (DSL) Transceivers TD-48 (PLEN)©<br />

4/15 G.997.1 (G.ploam) Physical Layer Management for Digital Subscriber Line<br />

(DSL) Transceivers<br />

TD-49 (PLEN)©<br />

Table 2. Recommendations Determined at Working Party 1/15, October 1998.<br />

Q1/15, ACCESS NETWORK TRANSPORT<br />

The Question 1/15 Rapporteur is R. Feigel, (Bosch, Germany). The agenda is TD-23(WP1/15). The report on<br />

the interim activities prior to this meeting is TD-21(WP1/15). TD-33(WP1/15) is the report of Q1/15 from<br />

the SG15 February 1998 Meeting. TD-35(WP1/15) is the list of input documents at this meeting. No interim<br />

meetings are scheduled.<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 51


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

ANT STANDARDIZATION<br />

The feedback received from the various Standardization Groups to whom the initial draft of ANT (Access Network<br />

Transport) Standardization (TD-17 WP1/15)) was sent for comment, additions and contact has been positive and<br />

constructive. The feedback was incorporated into the final draft of the Standardization Plan, which was completed at<br />

this meeting of SG15. TD-54(PLEN) provides the ANT model, ANT scenarios (including wireless, satellite and<br />

cable) and an extensive overview of existing <strong>standards</strong> activity. An initial draft of the Work Plan was also prepared<br />

(TD-55(PLEN)) and should be further developed. The Work Plan continues coordination and liaison with other<br />

<strong>standards</strong> bodies to maintain the Standardization Plan.<br />

TD-18(WP1/15) (R. Feigel, Bosch Telecom) is a table of ETSI radio related Standards for inclusion in the<br />

Standardization Plan.<br />

TD-19(WP1/15) (R. Feigel, Bosch Telecom) contains a table of Standards from several bodies (mostly ITU-R) for<br />

inclusion in Standardization plan.<br />

With the completion of the Standardization plan covering the work of both the ITU-T and ITU-R, Q1/15 plans to<br />

establish contact with the relevant external <strong>standards</strong> bodies so that details of their <strong>standards</strong> can be incorporated into<br />

the plan.<br />

Both the ANT Standardization Plan and Work Plan will be “living” documents, since they will require continued<br />

updating. Hence it is envisaged they will be published in the COM 15-R series of documents. TD-20(WP1/15)<br />

(R. Feigel, Bosch Telecom) is a proposal for a web-based ANT Standardization Plan. Once the presentation<br />

methodology for these documents is finalized, it is hoped that the Standardization Plan and the Work Plan will be<br />

migrated to a web site.<br />

TD-18(PLEN) (Chair, WP1 SG15) reports activities and achievements of Q1/15 as the core Question supporting<br />

SG15’s role as Lead Study Group for ANT. It reflects the objectives for this meeting.<br />

INPUT DOCUMENTS TO Q1/15 REGARDING THE ANT STANDARDIZATION PLAN<br />

TD-1(GEN) (ICG for IMT-2000, R. Blane, Inmarsat) reports on the progress of the Intersector Coordination<br />

Group for IMT-2000. The list of Standards in this liaison was incorporated in the ANT Standardization Plan, A2.3.<br />

This list has to be revised, as not all listed Standards seem to belong to ANT.<br />

TD-6(GEN) (ITU-T SG4, M. Klerer, AT&T) is a proposal for integrated management of telecom networks and IP<br />

networks. SG4 notes its responsibility in GII for integrated management of telecommunication networks and IP<br />

networks. The issue was incorporated in the ANT Work Plan as well as the Standardization Plan.<br />

TD-13(GEN) (ITU-R WP 9B, Y. Schifres, TRT Lucent) is a liaison that notes the responsibility of WP9B for<br />

technical studies on Fixed Wireless Access (FWA) and points to a first revision of the Hybrid Fiber Radio<br />

Recommendation ITU-R F.1332. The Recommendation was added to the Standardization Plan; a liaison with the<br />

attached new ANT Standardization Plan was sent as a reply (TD-41(PLEN) Annex 2).<br />

TD-16(GEN) (ITU-T SG4, D. Sidor, Nortel) notes that SG4 as the lead Study Group for Tele<strong>communications</strong><br />

Management Network (TMN) has installed a Project Management Team (PMT) for TMN. A list of TMN-related<br />

Recommendations is included. Q1/15 asks in a liaison reply (TD-41(PLEN) Annex 3) if they would prepare a list<br />

of ANT-related TMN documents for inclusion in the ANT Standardization Plan.<br />

TD-3(WP1/15) (ITU-T SG5, J. Erreygers, Raychem) contains a well-prepared table of K.series Recommendations<br />

for inclusion in the ANT Standardization Plan. A reply (TD-41(PLEN) Annex 6) with the ANT Standardization<br />

Plan attached was sent asking for further contact.<br />

TD-6(WP1/15) (ITU-T SG12, C. Dvorak, AT&T) confirms SG12’s expertise on transmission delay and echo<br />

control and proposes the inclusion of G.114 and G.131 in the ANT Standardization Plan. A liaison (TD-<br />

41(PLEN) Annex 7) with the ANT Standardization Plan attached was sent back asking for further close<br />

cooperation.<br />

TD-8(WP1/15) (ITU-T SG13, T. Kent, BT, R. Townsend, Lucent, Y. Maeda, NTT, and D. Cooper, Nortel) is a<br />

liaison that contains several comments and suggestions from various Questions in SG13 on the ANT Standardization<br />

Plan, especially on the use of the interface point XNI between access and customer premises networks. Some<br />

issues like the presentation of the scenario figures need further consideration. A liaison (TD-41(PLEN) Annex 11)<br />

was sent back asking for further close cooperation; it notes that the ANT Standardization Plan is a living document.<br />

52 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

TD-11(WP1/15) (ITU-R WP 8A, J. Costa, Nortel) gives information about the task of a JRG of WP8A and<br />

WP9B. Attached is a draft on “Performance and availability requirement an objectives for FWA” and a list of<br />

frequency band allocations used in several countries. Both issues were added to the ANT Work Plan and the<br />

Standardization Plan. A liaison (TD-41(PLEN) Annex 14) was sent back containing the new Standardization Plan<br />

and asking for further close cooperation.<br />

TD-12(WP1/15) (ITU R Task Group 8-1 J. Costa, Nortel) notes that Task Group 8-1 is working on radio aspects<br />

of IMT-2000; they consider the IMT-2000 radio interface as equivalent to the XNI (Customer Network Interface) in<br />

the ANT model, and the Radio Access Network (RAN) interface to the SNI (Service Node Interface). A list of<br />

relevant M.series Recommendations is recommended for inclusion into the ANT Standardization Plan. The<br />

Recommendations were included in the plan, and a liaison (TD-41(PLEN) Annex 8) was sent back asking for<br />

further cooperation.<br />

TD-13(WP1/15) (ITU-R Task Group 8-1 A. Kumar, Tele<strong>communications</strong> Engineering Centre) contains a<br />

working document on “proposed FWA (Fixed Wireless Access).” The issue of FWA was added to the ANT issues<br />

list in the ANT Work and Standardization Plan. A liaison (TD-41(PLEN) Annex 9) was sent back asking for<br />

further cooperation.<br />

TD-14(WP1/15) (ITU-T SG9, R. Catchpole, Nortel ) gives comments and information in the field of CATV<br />

(Cable Television). It proposes the inclusion of J.112 (Transmission systems for interactive cable television<br />

systems) and other Recommendations in the Standardization Plan. The Recommendations were included, J.series<br />

Recommendations references were updated, and a liaison (TD-41(PLEN) Annex 1) was sent back asking for further<br />

cooperation.<br />

TD-16(WP1/15) (ITU-R JRG 8A-9B, Y. Schifres, Lucent) informs Q1/15 of the JRG 8A-9B’s work on a new<br />

analog user/network (UNI) interface for FWA. A draft of the electrical requirements is attached. The issue was included<br />

in the ANT Work and Standardization Plan; a responsible SG in ITU has yet to be identified. A liaison (TD-<br />

41(PLEN) Annex 2) was sent back. An ETSI draft has been identified dealing with this issue.<br />

TD-36(WP1/15) (ITU-T SG16, L. Brown, Motorola) notes the approval of Recommendation V.90, defining<br />

modems for Internet access. V.90 has been included in the ANT Standardization Plan. A liaison (TD-41(PLEN)<br />

Annex 10) was sent back asking for ongoing cooperation; the new ANT Standardization Plan was attached.<br />

TD-17(PLEN) (SG15 representatives to ICG IMT-2000) reports of the third meeting of ICG IMT-2000. The<br />

issue of standardization of satellite transmission-related access networks was added to the issues list in the ANT<br />

Work and Standardization Plan.<br />

ADDITIONAL INCOMING DOCUMENTS AND LIAISONS<br />

TD-1(PLEN) (ITU-T SG2) contains a questionnaire on the Year 2000 Millennium Compliance. It was provided<br />

for information.<br />

TD-9(PLEN) (ITU-T TSAG, F. Brett, Nortel) contains information for the collaboration between ITU-T and the<br />

Internet Society (ISOC) and the Internet Engineering Task Force (IETF). The issue is incorporated in the ANT<br />

Work and Standardization Plan. Q1/15 will contact the bodies via their web pages, and results will be reported to<br />

TSAG.<br />

TD-10(PLEN) (ITU-T TSAG, K. Park, ETRI, Rep. of Korea) informs Q1/15 about the ITU’s pre-publication<br />

policy (Recommendations appear on the web 4 weeks after SG approval), the informal FTP areas (IFTP),<br />

publication of Formal Language Descriptions, and document submission formats.<br />

TD-16(PLEN) (ITU-T SG13) reports the June meeting of Intersector Coordination Group (ICG) SAT. It includes<br />

consideration for the future collaboration between ITU-T and ITU-R on satellite matters as well as a work plan<br />

related to satellite issues.<br />

TD-7(GEN) (SG4, M. Klerer, AT&T, and T. Rutt, Lucent) contains updated information on SG4’s<br />

responsibilities for GII projects.<br />

TD-12(GEN) (ITU-T SG13, H. Schink, Siemens) contains the allocation of Work on the GII Standardization<br />

Projects and their description. Q1/15 covers the Project N.1, Architecture and layer 1 aspects of narrowband/<br />

broadband access infrastructures for GII.<br />

TD-2(WP1/15) (ITU-T SG4, A. Gillespie, BT) comments on the presentation of management interfaces in the<br />

ANT Standardization Plan and proposes to show clearer distinction between management interfaces and OAM<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 53


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

(Operations, Administration, and Maintenance) flows which are embedded in the transmission flows between network<br />

elements (e.g., the F1, F2 and F3 flows of SDH and the F4 an F5 flows of ATM). Since there is not enough expertise<br />

on OAM flows in the group, a liaison (TD-41(PLEN) Annex 13) was sent back asking for further<br />

clarification and a suitable diagram.<br />

TD-5(WP1/15) (ITU-T SG11, R. Pandya, Nortel) asks for information about updated work schedules in field of<br />

IMT-2000.<br />

REVISION OF Q1/15 WORKPLAN<br />

The updated Q1/15 workplan is in Annex 3 of TD-38(PLEN), the WP1/15 report. There were only minor<br />

changes to the Q1/15 Work Plan. Q1/15 will not longer produce Recommendations. The area of related <strong>standards</strong><br />

was expanded to full services access networks. Some information about the issue of several Standards Organizations<br />

was added to Table 1, Phased Approach to ANT Coordination with Critical Organizations.<br />

REVISION AND UPDATE OF THE ANT WORK PLAN<br />

TD-55(PLEN) is the Access Network Transport Work Plan dated October 20, 1998.<br />

The list of contacts was restructured to show all presently known contact persons with names and addresses.<br />

Additional/ supplemental contacts will be obtained via correspondence. Results will be reported to the TSB.<br />

The list “ANT Issues identified” was expanded. Gaps and open issues were added from the input documents to this<br />

meeting and from those identified in the meeting discussions.<br />

No progress was made on prioritization, plan for missing <strong>standards</strong>, and plan for conflicting <strong>standards</strong>.<br />

The liaison tracking list has yet to be updated.<br />

The installation of an interactive Web Page for Q1/15 ANT Standardization activities should be pursued in the near<br />

future.<br />

REVISION AND UPDATE OF DRAFT ANT STANDARDIZATION PLAN<br />

TD-54(PLEN) is the Access Network Transport Draft Standardization Plan, dated October 20, 1998. It is based on<br />

the draft ANT Standardization Plan from the February 1998 SG15 meeting. All changes –even those of the Tel<br />

Aviv interim meeting– are identified by change marks; only the figures of the Scenarios do not show all the change<br />

marks. A clean copy will be provided in the Q1/15 IFTP area (ANTPL1098.DOC)<br />

The main results from this meeting are<br />

• Insertion of the expanded “ANT Issues identified” list from the ANT Work Plan in 6.1.3<br />

• A2.2, a list of Standards not assigned up to this meeting, has been completed, but changes were not incorporated<br />

in ANNEX 2.1. Liaisons (TD-41(PLEN) Annex 4 and Annex 5) to ANSI, ATMF, EIA/TIA, ETSI, ADSL<br />

Forum, DAVIC and ITU-T SG5 were sent asking for help in revising A2.2 in order to have the correct<br />

assignments.<br />

• A2.3 was added. It contains a list of all <strong>standards</strong> which were added in this meeting. A2.3 needs a careful check,<br />

to verify whether all listed documents relate to ANT. This check should be done by correspondence.<br />

It was agreed to advance the draft ANT Standardization Plant to “Issue 1” status.<br />

Q2/15, CHARACTERISTICS OF OPTICAL SYSTEMS IN LOCAL ACCESS NETWORKS<br />

The Question 2/15 Rapporteur is T. Finegan (BT, UK). An interim meeting will be held January 27-29, 1999, in<br />

USA (hosted by Lucent Technologies).<br />

Recommendation G.983.1, G.PONB for ATM-PON (Asynchronous Transfer Mode - Passive Optical Network)<br />

System, was approved (Decided) at the opening Plenary, as TD-26(PLEN 2/98), TD-39 (WP1/15 2/98) +<br />

COM 15-110.<br />

Following the approval of G.983.1, the Q2/15 objective was to focus on a draft new Recommendation covering the<br />

management and control of ATM-PON.<br />

Following the <strong>review</strong> of documents in the WP1/15 plenary, only four documents remained for consideration in<br />

Q2/15. TD-6(PLEN) (P. Wery, Nortel) ADSL Forum Request, TD-17(PLEN) (SG15 Representative to ICG<br />

54 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

IMT-2000) Summary of Third Meeting of ICG IMT-2000, and TD-22(PLEN), List of White Contributions, were<br />

taken for information; it was agreed that no further action was required.<br />

The text of Question 2/15 was <strong>review</strong>ed in connection with the transport of IP and some modifications were agreed.<br />

The revised text is given in TD-72(PLEN).<br />

DRAFT RECOMMENDATION G.983.2<br />

The main focus of the meeting was D.457 (Y. Maeda, NTT), Proposed ONT/NT (ONU [optical network unit] in<br />

the FTTH configuration/NT [network termination] in the FTTB, FTTC and FTTCab configuration) Management and<br />

Control Interface (omci) specifications for a new draft Recommendation G.983.omci. The experts agreed that the<br />

work in the next eight months should concentrate on the development of a draft new Recommendation G.983.2 -<br />

“ONT/NT management and control interface specifications.” The target for this draft new Recommendation is<br />

Determination at the June/July 1999 meeting of SG15.<br />

D.457 provides the initial text to be considered. It was agreed to use this document as a basis for this work and that<br />

Y. Maeda (NTT) will be the editor. Some minor editorial items were pointed out in this text and these will be<br />

updated. In particular, it was agreed that in Table 6 of this document, the primary rate 2 Mbit/s E1 should be<br />

included, consequently Table 9 will be updated with the 2M REC and 2M AIS.<br />

The UPC function, which is not included in this document, should be the subject of future contributions.<br />

In order to achieve the challenging target of Determination at the next meeting of SG15, an interim meeting will be<br />

held January 27-29, 1999, in the USA hosted by Lucent Technologies. At this meeting it is intended to:<br />

• Consider the contributions and changes to the clauses in this document;<br />

• Agree to a stable document;<br />

• Prepare a white contribution for the June/July 1999 meeting of SG15.<br />

Although this is a very challenging target, it is essential that this document be available at this stage of the ATM-<br />

PON development; it is unlikely to be of benefit a year later. The Agenda for the interim meeting is given in Annex<br />

4 to TD-38(PLEN).<br />

The status of the Q2/15 Recommendations included in the WP1/15 Work Plan was <strong>review</strong>ed and updated.<br />

Q3/15, DCES FOR DIGITAL LEASED CIRCUITS<br />

Because there were no contributions addressed to this Question, it was agreed to deal with any Q3/15 matters during<br />

the WP1/15 plenary sessions.<br />

The text of draft new Recommendation V.300 (ex V.144k, TD-43(PLEN), A. Nunn) was <strong>review</strong>ed; it was agreed<br />

to forward it to the SG15 plenary for Determination. This DCE is intended for use on 128 kbit/s (or 144 kbit/s)<br />

digital point-to-point leased circuits other than ISDN. The DCE specified includes rate adaption, end-to-end<br />

signaling, testing and multiplexing features. However, the line signal and the signaling rate is considered a national<br />

matter and is not specified. It was noted that some further editorial work is required on this draft new<br />

Recommendation and it was agreed that the Rapporteur would submit a white contribution containing the revised<br />

text to the next SG15 meeting.<br />

Q4/15, DCES FOR SUBSCRIBER ACCESS SYSTEMS<br />

R. Stuart (3Com) is the Q4/15 Rapporteur. TD-15(WP1/15) is a report from the four Interim Rapporteurs<br />

meetings. Three interim meetings were approved for 1999: Jan. 18 - 22, Portland, OR; Mar 29 - Apr. 2,<br />

Melbourne, Australia; and May 10 - 14, Boston, MA. TD-40(WP1/15) is the proposed Q4/15 agenda.<br />

Recommendation G.991.1, High speed Digital Subscriber Line (HDSL) Transceivers, was approved (Decided) at the<br />

opening Plenary, as TD-38(PLEN 2/98) + COM 15-123.<br />

Q4/15 agreed to new titles for the Q4/15 Recommendations as follows:<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 55


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

Rec. No. Rec. Name Recommendation Title<br />

G.990 General<br />

G.991.1 G.hdsl High Speed Digital Subscriber Line (HDSL) Transceivers<br />

G.991.2 Reserved for possible future HDSL Recommendations<br />

G.992.1 G.dmt Asymmetric Digital Subscriber Line (ADSL) Transceivers<br />

G.992.2 G.lite Splitterless Asymmetric Digital Subscriber Line (ADSL) Transceivers<br />

G.993 Reserved for possible future VDSL Recommendations<br />

G.994.1 G.hs Handshake Procedures for Digital Subscriber Line (DSL) Transceivers<br />

G.995.1 G.ref Overview of Digital Subscriber Line (DSL) Recommendations<br />

G.996.1 G.test Testing Procedures for Digital Subscriber Line (DSL) Transceivers<br />

G.997.1 G.ploam Physical Layer Management for Digital Subscriber Line (DSL)<br />

Transceivers<br />

Q4/15 agreed to plan for second generation versions of all Recommendations; the present Editors will maintain the<br />

Issues List for the second generation versions, at least until final approval of the present Recommendations. The<br />

Rapporteur will select new Editors, as appropriate, for second generation Recommendations. C. Hansen (Intel)<br />

indicated he plans to hand over the editorship of G.992.2 after Decision (final approval).<br />

INTELLECTUAL PROPERTY RIGHTS (IPR)<br />

32 companies have indicated IP interest in the xDSL G.series Recommendations. All listed below except Lucent<br />

have provided notification by either contribution or a letter to the TSB:<br />

3Com Compaq Paradyne<br />

Alcatel Fujitsu PC-Tel<br />

Altocom GDC Racal Datacom<br />

Amati GlobeSpan Rockwell<br />

AMD Itex SAS<br />

Aware Lucent Stanford Univ.<br />

Analog Devices Matsushita Sumitomo<br />

Bell Atlantic Mitsubishi Texas Instr.<br />

Centillium Motorola VoCAL Tech.<br />

Cirrus Logic NEC Siemens AG<br />

Cisco PairGain<br />

All companies which have made an indication have done so indicating they will be in accordance with 2.2 of the ITU<br />

Patent Policy. The Rapporteur reminded the meeting that for those companies which had only provided a<br />

contribution, that it was necessary that they also provide a letter to the ITU Director indicating their IP position.<br />

NEW WORK ON VDSL, HDSL, AND SDSL<br />

D.333C1 (R. Hamdi, Compaq, USA) proposes that SG15 start work on enhancements to G.lite to provide longer<br />

loop reach, and higher performance after G.lite is Determined. D.408 (Y. Okamura, NEC, Japan) proposes<br />

continuation of the work on Annex C (Japanese TCM ISDN) of G.dmt to reduce latency after G.dmt is Determined.<br />

The contributions note a goal of Determination for these follow-on Recommendations in 2000.<br />

D.279 (K. Foster, BT, UK) proposes that the work on G.vdsl be deferred until work has progressed in the Regional<br />

Standards bodies. D.326 (G. Zedler, Deutsche Telekom) and D.343 (A. Johansson, Ericsson, Sweden) essentially<br />

echo D.279.<br />

D.330 (T. Starr, Ameritech, USA) proposes that, immediately following the finalization of the present set of<br />

Recommendations, work proceed on G.vdsl and G.hdsl2. It recommends that the initial focus be on spectral<br />

compatibility, defining international system requirements, and the feasibility of common handshake procedures.<br />

D.406 (S. Palm, Matsushita, Japan, representing multiple Japanese manufacturers) essentially echoes D.330.<br />

D.328 (G. Zedler, Deutsche Telekom) proposes that work on G.sdsl and G.hdsl2 be deferred until the work has been<br />

progressed in the Regional Standards bodies.<br />

During the discussion, BT explained that their concern mainly centered on the availability of enough human<br />

resources to track this work in multiple forums. In the end, the Rapporteur ended the discussion by stating that the<br />

56 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

SG15 management team had directed him to proceed with work on these Recommendations. Using this as<br />

justification, the Rapporteur obtained the group’s agreement to proceed with the work on G.vdsl and G.hdsl2.<br />

Q4/15 agreed to commence work on a VDSL (G.vdsl) and an HDSL2/SDSL (G.shdsl) Recommendation. In making<br />

this agreement, Q4/15 recognized the guidance provided by the SG15 management team as presented in Section 6,<br />

Guidelines for the meeting of Working Parties, of TD-5(PLEN). Q4/15 determined to take every advantage of the<br />

good work already started or published by ETSI TM-6, ANSI T1E1.4, the ADSL Forum and other regional standard<br />

groups in regard to this work. This should be done by encouraging the member companies to contribute to the work<br />

of the ITU and to encourage close and frequent liaison on the work by each committee. Concerning the timing of<br />

this new work however, it is understood by all that Q4/15’s first priority will be to complete the editorial work on<br />

the Determined Recommendations at the January 1999 Rapporteurs Meeting. Accordingly, it is not expected that<br />

serious consideration of the new Recommendations will be practical until the proposed March/April 1999 meeting in<br />

Australia. An initial focus on the International Requirements, on Spectral Compatibility Issues (particularly for<br />

VDSL), and the integration/application of G.hs/G.994.1 to these Recommendations was agreed.<br />

Q4/15 agreed that liaison person(s) should be appointed to provide improved <strong>communications</strong> between regional<br />

<strong>standards</strong> groups. This person(s) should carry unbiased <strong>communications</strong> between the groups and should not therefore<br />

hold a position in either group. The Rapporteur requested candidate(s) for such positions.<br />

The new Recommendation development work will be conducted under the following designated names:<br />

Rec. Name Recommendation Title<br />

G.shdsl Single pair High speed Digital Subscriber Line (SHDSL) Transceivers<br />

G.vdsl Very high speed Digital Subscriber Line (VDSL) Transceivers<br />

G.LITE<br />

C. Hansen (Intel) is the editor of G.992.2, G.lite, Splitterless ADSL Transceivers.<br />

D.419 (F. Van der Putten, Alcatel, Belgium) proposes changes to the text of G.dmt and G.lite to bring them into<br />

alignment with T1.413.<br />

D.284 (G. Sebek, France Telecom) proposes that specific statements should be included in G.lite and G.dmt to<br />

clarify that interworking with T1.413 issue 2 is possible. It proposes that this interworking should not require<br />

changes to the hardware. Appropriate text will be added to G.ref.<br />

D.445 (T. Starr, Ameritech, USA) provides a pointer to ANSI T1.413 Issue 2 for information only.<br />

D.467 (R. Townsend, Lucent, USA) proposes that the present text of G.lite be Determined at this meeting.<br />

D.334 (L. Brown, Motorola, USA) proposes that the entire suite of xDSL recommendations be Determined at this<br />

meeting.<br />

D.407 (S. Palm, Matsushita, Japan, representing Multiple Japanese Companies) proposes that the SG15 Determine<br />

the present texts for xDSL Recommendations and proceed immediately with work on newer versions.<br />

D.325 (R. Hamdi, Compaq, USA) proposes two additional table rows in G.lite. It also provides a simple home<br />

wiring model. The group accepted the additional test cases proposed. It was proposed that a section be added entitled<br />

“acoustic levels” which would contain the values to reflect the points raised in TD-7(WP1/15) from SG12. This<br />

liaison provides guidance from SG12 on acceptable levels of interference from ADSL systems into POTS. After<br />

some discussion, it was decided to include this sort of information in either G.lite or G.test.<br />

D.420 (F. Van der Putten, Alcatel, Belgium) proposes additional code points (with supporting text) for G.hs<br />

(standard information field), G.dmt and G.lite (identification filed); it notes the need to specify how G.dmt and G.lite<br />

are supposed to handle information conveyed in G.hs.<br />

D.333C1 (R. Hamdi, Compaq, USA) proposes that work immediately start on enhancements to G.lite after<br />

Determination of the present text. A question was raised as to whether starting work on the next generation of a<br />

Recommendation before it was even approved was in conflict with ITU rules. There was no resolution of this issue.<br />

Bit-swap<br />

D.281 (F. Van der Putten, Alcatel, Belgium) and D.311 (S. Cascelli, Alcatel, Italy) provide a rationale for making<br />

bit swap mandatory in G.lite. They claim the benefits of improved performance and more reliable fast-retrain<br />

operation. D.337 (G. Joncour, FranceTelecom) supports the position in D.281.<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 57


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

D.327 (G. Zedler, Deutsche Telekom) reports that the majority of ETSI members would require that bit-swap be<br />

made a mandatory requirement in European implementations. D.338 (A. Johansson, Ericsson, Sweden) and D.430<br />

(R. Feigel, Bosch, Germany) support the position in D.327.<br />

D.331 (T. Starr, Ameritech, USA) proposes that bit-swap be made optional in G.lite.<br />

D.431 (R. Venkatraman, Silicon Automation Systems, India) proposes that bit-swap be made optional. Opponents<br />

of mandatory bit-swap based their arguments on the premise that the protocol has not been shown to be robust.<br />

Proponents stated that their tests did not show any problems with robustness. It was also proposed that a code point<br />

could be added to G.hs to provide early identification of bit-swap. An ad hoc group was formed to look into this<br />

issue.<br />

No agreements were reached at the first ad hoc on bit swap but several “compromises” were tabled. The following<br />

proposals were made:<br />

• Optional<br />

• Mandatory<br />

• Optional with Auto-adaptation (new)<br />

• Rate Adaption (RA) mandatory<br />

• RA optional<br />

• RA mandatory with recommendation to use bit swap if a splitter is present<br />

• Mandatory, with Auto-disabling (new)<br />

• Optional, with a recommendation to use bit swap when splitters are used (new)<br />

The auto-adaptation proposal received the most discussion. It was decided to convene another ad hoc group to “flesh<br />

out” the proposals.<br />

TD-46(WP1/15) (J. Mueller, 3Com) is the report of the second bit-swap ad hoc group. Most of the meeting was<br />

spent addressing two of the alternatives, specifically, “the Addition of Rate Adaptive Capability (bit-swap optional)”<br />

and “Adding Auto Disabling (bit-swap mandatory).” In line with the group’s charter, no recommendation was made.<br />

It does however, recommend the adding of a specific time interval (within 400 ms) for the response to the bit-swap<br />

request message to Section 11.2.7 of G.dmt.<br />

An informal paper developed during the meeting (WD-bit-unn, F. Van der Putten, Alcatel, Belgium, with France<br />

and Italy) offered a compromise which essentially proposes that bit-swap be made optional. It proposes that bitswap<br />

text (lifted from G.dmt) be added to G.lite. It further proposes that the transmitter be allowed to respond with<br />

either an ACK (acknowledge) or an UTC (Unable to Comply) and that it recommend (but not mandate) that an ACK<br />

be sent if the environment includes an in-line filter or a POTS splitter. It also proposes text, which includes the 400<br />

ms value proposed above. After conferring in delegations outside of the meeting, the group accepted this proposal.<br />

Transfer Delay<br />

D.339 (A. Johansson, Ericsson, Sweden) proposes the specification of a single transfer delay with a value of 10<br />

ms. It was clarified that this was proposed as a test value. Sweden later accepted the compromise reached below as<br />

also satisfying their requirements.<br />

D.317 (S. Abbas, Centillium Technology, USA, representing Multiple US Companies) proposes a general formula<br />

for guidance in computing the max payload transfer delay. It also provides a value of 14 ms that should be met under<br />

a given set of circumstances. D.391 (R. Venkatraman, Silicon Automation Systems, India) proposes that the<br />

delay not be specified in the Recommendation. D.397 (G. Reina, Orckit Communications, Israel) agrees with<br />

D.391 based on the premise that it is not practical to measure.<br />

There was considerable discussion following these papers. It was finally decided to accept the proposal in D.317<br />

with the first number in the formula changed from “6.25” to “4.00” and the required value changed to “10 + (S x<br />

D)/4 ms” from “14 ms when (S x D)


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

D.418 (F. Van der Putten, Alcatel, Belgium) proposes the addition of provision for power management initiation<br />

by the ATU-C. This paper was addressed in the power control ad hoc group.<br />

D.421 (D. Van Bruyssel, Alcatel, Belgium) proposes solutions for problems identified in the transition from the L3<br />

to the LO state. Proposals are identified with escaping from a failed fast retrain, escaping to fast retrain from full<br />

initialization and going to fast retrain from the idle state.<br />

The group agreed to the “fast retrain truncate” proposal (which addresses the escape from a failed fast retrain) made in<br />

Annex A to D.421. In line with the second proposal, the group agreed that the ATU-C not be allowed to NAK a<br />

request for fast retrain issued by the ATU-R. The mechanism of using a code point in G.hs. to initiate this escape<br />

was agreed (see D.420, F. Van Der Putten, Alcatel). The exact placement of the code point was put off for further<br />

discussion. The decision on the proposals in Annex C (proposed text for fast retrain initiated from idle state) and<br />

Annex E (proposed text for state diagrams) of D.421 was deferred pending discussion in an ad hoc session on “fast<br />

retrain/power management.”<br />

TD-47(WP1/15) (R. Hamdi, Compaq, USA) is the report of the report of the Fast Retrain/ Power Management<br />

Ad hoc. It includes proposed revised text for Annexes A through D:<br />

A - Proposed Text for Fast Retrain Truncate<br />

B - Proposed Text for Transition from L3 to L0<br />

C - Proposed Text for Fast Retrain Initiated From Idle State<br />

D - Proposed Text for Escape to Fast Retrain<br />

D.423 (D. Van Bruyssel, Alcatel, Belgium) proposes that the PSD levels for C-PILOT-FR1 and R_RECOV be<br />

maintained at the level of preceding signals rather than allowing them to be dropped to a vendor discretionary level as<br />

presently specified. The group agreed to the proposal in Annex A (proposed changes to fast retrain procedures) of<br />

D.423.<br />

D.466 (K. Cone, Lucent) examines the impact on ATM of the L0 to L1 transition and concludes that this will not<br />

cause a problem. It also concludes that the L1 state must support a minimum ATM data rate of 32 kbit/s in order to<br />

support ATM signaling protocols. No text changes are proposed.<br />

D.368 (J. Carlo, TI) proposes changes in values of the R-LINE PROBE and C-REVERB-FR6 signals used in fast<br />

retrain. The meeting agreed to the new value of 512 ms for R-LINE PROBE. It also agreed to an exact value of 400<br />

ms for C-REVERB-FR6.<br />

D.366 (F. Van der Putten, Alcatel, Belgium) analyzes the timing recovery procedures in G.dmt and G.lite and<br />

concludes that they are adequate to work with G.hs.<br />

TD-43(WP1/15) (T. Cole, AMD) is the report of the ad hoc group on Power Management. This report proposes<br />

replacement text. It recommends the removal of the L2 state (and reserving it for future use by the ITU-T), and<br />

reserving the Power Management states 128 through 255 for vendor-specific use. The group accepted the report and<br />

the proposals.<br />

European Performance Requirements<br />

WD-12(WP1/15) is a report of the ad hoc group on European performance Requirements for G.dmt and G.lite. It<br />

was clarified that the Europeans would require in-line filters in any installations. The group accepted the technical<br />

proposals. These include having separate regional performance requirements (Annexes) in both G.lite and G.dmt,<br />

revising the European G.lite and G.dmt test cases (to include longer loops and increased data rates with lower noise)<br />

and to rename Kirkby noise to Euro-K noise.<br />

Trellis Coding, 1-bit Constellations, and Improved Efficiency Framing<br />

D.392 (R. Venkatraman, Silicon Automation Systems, India) proposes that the one-bit constellation be mandatory<br />

in both G.lite and G.dmt.<br />

D.332 (R. Hamdi, Compaq, USA) proposes that Trellis coding, 1-bit constellation, and efficiency framing not be<br />

included in G.lite at this time.<br />

D.342 (A. Johansson, Ericsson, Sweden) proposes to include a Trellis coding option. Later in the meeting,<br />

Sweden offered a compromise which would involve putting information on Trellis coding in an Appendix which<br />

would be purely informative. Deutsche Telekom and France expressed support for this compromise. The editor<br />

obtained the groups’ agreement to the wording below for the text of the proposed Appendix:<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 59


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

“In anticipation of future revisions of this Recommendation manufacturers are encouraged to implement and<br />

investigate implementing the performance of Trellis coding in a splitterless environment as specified in<br />

Recommendation 992.1. Implementers wishing to investigate the use of Trellis coding should negotiate its use<br />

via the non-standard facilities capabilities of G.hs.”<br />

D.400 (G. Reina, Orckit, Israel) proposes to include a Trellis coding option.<br />

D.316 (S. Abbas, Centillium, USA, representing Multiple US Companies) proposes 1-bit constellations for future<br />

versions of G.lite.<br />

D. 396 (G. Reina, Orckit, Israel) proposes including a 1-bit constellation option.<br />

D.392 (R. Venkatraman, Silicon Automation Systems, India) proposes a mandatory 1-bit constellation.<br />

D.318 (S. Abbas, Centillium, USA, representing Multiple US Companies) proposes increased framing efficiency<br />

for G.lite-bis.<br />

D. 398 (G. Reina, Orckit, Israel) proposes an optional efficient framing mode.<br />

The group agreed to study the inclusion of trellis coding, 1-bit constellation and increased efficiency framing in<br />

future issues of G.lite. Eventually it was agreed to leave trellis coding (see wording above), 1-bit constellations and<br />

increased efficiency framing for further study.<br />

Miscellaneous<br />

D.388 (A. Verme, Silicon Automation Systems, India) describes what is characterized as a low complexity method<br />

for reducing Peak-to-Average (PAR) power.<br />

D.389 (A. Verme, Silicon Automation Systems, India) notes that, as it is possible to design PAR power reduction<br />

schemes that are totally transparent to the receiver, no provision for PAR management needs to be specified in the<br />

Recommendation.<br />

D.340 (A. Johansson, Ericsson, Sweden) proposes the inclusion of an echo canceling option in G.lite. There was<br />

no discussion as G.lite presently specifies an echo canceling option.<br />

D.399 (G. Reina, Orckit Communications, Israel) notes a flaw in the formula used to compute the power constraint<br />

and recommends that it either be modified or removed.<br />

Resolution and Final G.lite Agreements<br />

WD-4(WP1/15) (C. Hansen) is an interim version of the G.lite Recommendation. During the meeting the editor<br />

<strong>review</strong>ed the changes to this document point-by-point, obtaining agreement to the changed items. The accuracy of<br />

the power formula in Annex A and Annex B was again brought up. Annex B - An issue relating to the use of a100<br />

ohm impedance for the 0-4 kHz measurement was raised. In the tables in Annex B it was agreed to replace the term<br />

“FDM G.lite” with “Annex A G.lite”<br />

TD-44(WP1/15) (C. Hansen, Intel, USA) proposes revised text for sections 11.2 and 11.3, (Handshake ATU-C<br />

and Handshake ATU-R, respectively) which incorporates the agreements made at this meeting. It was accepted.<br />

Eventually all open issues were resolved; TD-45(PLEN)© (C. Hansen, Intel, USA) is the final text of G.992.2<br />

(G.lite) which was Determined by SG15.<br />

G.DMT<br />

S. Palm (Matsushita) is the editor of G.992.1, G.dmt, ADSL Transceivers.<br />

TD-26(WP1/15) (S. Palm, Matsushita, Japan) is the Issues List for G.dmt<br />

TD-07(WP1/15) (S. Palm, Matsushita, Japan) is a liaison from SG12 responding to a request for information on<br />

ADSL interference into POTS.<br />

TD-37(WP1/15) (L. Brown, Motorola, USA) from SG16 provides a pointer to where information on billing<br />

tones could be obtained.<br />

TD-10(WP1/15) (T. Geary and G. Sullivan, SG16 Q11 and Q15 Rapporteurs) provides characteristics of various<br />

multimedia applications which could be provided over xDSL facilities.<br />

60 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

TD-27(WP1/15) (T. Geary, SG16 Q11 Rapporteur) identifies some possible approaches to multimedia<br />

applications:<br />

• Entire xDSL capacity is devoted to delivery of IP without any special QoS support<br />

• Some of the xDSL capacity is devoted to baseband voice and some to IP.<br />

• A QoS aware protocol (“probably ATM”) is used to convey voice and IP.<br />

TD-28(WP1/15) (G. Sullivan, Q15/16 Rapporteur) provides information on the video coding work in SG16.<br />

TD-36(WP1/15) (L. Brown, Motorola, USA) reports on the progress of Rec. V.90. It offers L. Brown as a<br />

liaison officer.<br />

TD-06(GEN) from SG4 provides a proposal for integrated management of telecom and IP networks; it requests<br />

comments.<br />

TD-08(GEN) from SG12 Q18 reports on their study on voice quality over IP.<br />

TD-09(GEN) (S. Palm, Matsushita, Japan) from SG12 reports on the acoustical properties of “hands free”<br />

modems contained in P.30 Group audio terminal, P.340 Transmission characteristics of hands-free telephones, P.341<br />

Transmission characteristics for wideband (150-8000 Hz) digital hands-free telephony terminals, and P.342<br />

Transmission characteristics for telephone-band (300-3400 Hz) digital loud-speaking and hands-free telephony<br />

terminals.<br />

TD-24(GEN) (L. Brown, Motorola, USA) from SG16 discusses modem testing and requests information from<br />

SG15 on the digital network characteristics.<br />

Interworking with T1.413 issue 2<br />

D.284 (G. Sebek, France Telecom) proposes that specific statements should be included in G.lite and G.dmt to<br />

clarify that interworking with T1.413 issue 2 is possible. It proposes that this interworking should not require<br />

changes to the hardware.<br />

D.341 (A. Johansson, Ericsson, Sweden) proposes that an Annex be added to G.dmt (or G.hs as verbally amended<br />

by the presenter) which would provide a pointer to T1.413.<br />

D.419 (F. Van der Putten, Alcatel, Belgium) proposes changes to G.dmt to further align it with T1.413 issue 2. It<br />

further proposes that if these changes are accepted into G.dmt, they should also be incorporated into G.lite. The<br />

group generally accepted all of the proposals in this contribution.<br />

After discussion, it was finally decided that the interworking issue would be discussed under G.hs (see below).<br />

European Performance Requirements<br />

D.424 (D. Van Bruyssel, Alcatel, Belgium) proposes performance requirements for the European loops to be<br />

included in G.dmt. D. Van Bruyssel stated that the information in this document was superseded by WD-<br />

12(WP1/15), a report of the Ad Hoc group on European Performance Requirements for G.dmt and G.lite. A final<br />

decision on the status of the proposals in WD-12(WP1/15) was deferred in response to a request from France.<br />

N. Billington (BT) reported on the recommendations of the European test case ad hoc. The proposal is to modify<br />

Annex G by deleting section 3.1 and to use the tables in WD-12(WP1/15). The group accepted this proposal<br />

pending agreement on final text.<br />

Transfer Delay<br />

D.339 (A. Johansson, Ericsson, Sweden) proposes the specification of a single transfer delay with a value of 10<br />

ms. The proposal was to incorporate this value into the appropriate Annex. It was clarified that this test would<br />

only be related to the crosstalk tests (not the impulse noise tests). The final decision was deferred pending the<br />

development of text in the editing group. It was later agreed to include the 10 ms limit in Annex F, ATU-x<br />

Classification and Performance for Region A (Other than Europe). However, concerns were expressed when it was<br />

proposed to add this to Annex G, ATU-x Classification and Performance for Region B (Europe).<br />

D.408 (Y. Okamura, NEC, Japan) proposes the continued study of a means to reduce the latency figure for Annex<br />

C (Specific Requirements for an ADSL System Operating in the Same Cable as ISDN) with the goal of closing this<br />

issue at the January Rapporteurs’ meeting. The group agreed to this work plan.<br />

D.448 (W. Matsumoto, Mitsubishi, Japan) proposes the Low Payload Transfer Delay method as one of the latency<br />

reduction methods in a revised G.dmt Annex C.<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 61


Miscellaneous<br />

COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

D.376 (J. Torres and V. Demjanenko, VoCAL Technologies, USA) proposes that an optional Serial Concatenated<br />

Convolutional coder be included in future versions of G.dmt.<br />

D.420 (F. Van der Putten, Alcatel, Belgium) proposes code points, and was discussed under G.hs. The group,<br />

however, gave its endorsement to the proposals contained in Section 3.2 as they applied to G.dmt.<br />

G.dmt Final Text<br />

TD-44(PLEN)© (S. Palm, Matsushita, Japan) is the final text for G.992.1 (G.dmt) Asymmetrical Digital Subscriber<br />

Line (ADSL) Transceivers. It was Determined at the SG15 plenary.<br />

G.REF<br />

S. Abbas, Centillium Technologies) is the editor of G.995.1, G.ref, Overview of DSL Recommendations.<br />

TD-24(WP/15) (S. Abbas, Centillium Technologies, USA) is the draft Recommendation G.ref as input to this<br />

meeting. However, as WD-05(WP1/15) represented an update to this, it was not presented. A detailed <strong>review</strong> of<br />

WD-05(WP1/15) was made.<br />

TD-38(WP1/15) (S. Abbas, Centillium Technologies, USA) is the G.ref issues list.<br />

TD-47(PLEN)© (S. Abbas, Centillium Technologies, USA) is the final text for G.995.1 (G.ref), Overview of<br />

Digital Subscriber Line (DSL) Recommendations. It was Determined at the SG15 plenary.<br />

G.HS<br />

L. Brown (Motorola) is the editor of G.994.1, G.hs, Handshake Procedures for DSL Transceivers.<br />

D.293 (S. Palm, Matsushita, Japan representing multiple Japanese comapnies) proposes adding the tone index 64<br />

to indicate incompatibility with Annex A.<br />

D.329 (T. Starr, Ameritech, USA) proposes a mechanism for initiating a connection with legacy equipment<br />

(T1.413).<br />

D.404 (S. Palm, Matsushita, Japan) proposes refinements to G.hs. The proposals were broken down into “editorial<br />

matters,” “completion of open items and text deficiencies,” and “configuring xTU-R G.hs using G.ploam.” The<br />

editorial proposals in section 2 were accepted.<br />

D.414 (F. Van der Putten, Alcatel, Belgium) proposes changes to G.hs to help clarify the text. The proposal for a<br />

modulation formula was accepted; editorial changes will be made to clarify Octet transparency and parsing of data<br />

blocks.<br />

WD-hs(WP1/15) (L. Brown, Motorola, USA) is the report of the G.hs ad hoc group. Agreements reached:<br />

• New text for T1.413 interworking<br />

• Flag corruption, the length of Message Type and Revision<br />

• The structure of the Vendor ID field<br />

• The maximum transmit power<br />

• Adding tone index 64 to Table 1<br />

• Adding an appendix for provider code information<br />

• The inclusion of sample sessions in an appendix<br />

• Moving the Level 2 and lower PARS back to G.hs<br />

• Moving the spectral coding information to the standard information field<br />

GS-016R2(WP1/15) (L. Brown, Motorola, USA) is the updated Issues List for G.hs. The editor briefly <strong>review</strong>ed<br />

the changes to this document, obtaining agreement to the changed items. He then got the agreement of the group to<br />

close the majority of the open issues. The proposals in D.420, code points for G.hs (F. Van der Putten, Alcatel,<br />

Belgium), were addressed. It was agreed to accept the tables proposed in section 3.1.<br />

TD-31(WP1/15)© (L. Brown, Motorola, USA) is the draft Recommendation G.hs and the Issues List. There was<br />

considerable discussion about the provision of a feature for indicating that the xTU-C is connected but not ready to<br />

start a G.hs session. It was decided to put a placeholder here and address this at the January Rapporteurs meeting. It<br />

was agreed to assign the fast retrain code point as a level 2 PAR. Conversely, C-TONE was moved up to a level 1<br />

PAR. The group also agreed that there would only be three levels of parsing.<br />

62 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

GS-006(WP1/15) (L. Brown, Motorola, USA) is the final text of G.994.1 (G.hs) proposed for Determination.<br />

During the point-by-point <strong>review</strong> of the text, the French delegation once again raised the issue of the need for a more<br />

definitive specification of the support of interworking with T1.413 issue 2. With the caveat that some text would be<br />

developed to satisfy the French concern, the group accepted the document for Determination. G.994.1 (G.hs)<br />

Handshake Procedures for Digital Subscriber Line (DSL) Transceivers, was Determined as TD-46(PLEN)© at the<br />

SG15 plenary.<br />

G.TEST<br />

M. Tzannes (Aware) is the editor of G.996.1, G.test, Test Procedures for DSL Transceivers.<br />

D.314 (T. Cole, AMD, USA, representing Multiple US Companies) proposes a modification to the test procedures<br />

in G.test to take into account that in-line filters might be used in the field, by allowing the use of in-line filters in<br />

the tests if appropriate.<br />

D.443 (K. Kikushima, NTT, Japan) proposes revisions to the section of G.test that relates to testing G.lite in the<br />

presence of TCM-ISDN disturbers. The in-home wiring models were accepted.<br />

D.444 (K. Kikushima, NTT, Japan) proposes simple models for off-hook, on-hook impedances, which could allow<br />

repeatability of testing.<br />

D.416 (F. Van der Putten, Alcatel, Belgium) proposes to use appropriate values and formulas from T1.413 issue 2<br />

to further align the work.<br />

WD-POTS-QOS(WP1/15) (M. Tzannes, Aware) is the output of the POTS QoS ad hoc. It contains some<br />

minor text modifications to clearly specify where an in-line filter would be inserted in the test set if it were<br />

appropriate.<br />

TD-48(PLEN)© (M. Tzannes, Aware) is the final text of G.test proposed for Determination. Draft Recommendation<br />

G.996.1 Test Procedures for Digital Subscriber Line (DSL) Transceivers, was Determined at the SG15 plenary.<br />

G.PLOAM<br />

A. Johansson, Ericsson) is the editor of G.997.1, G.ploam, Physical Layer Management for DSL Transceivers.<br />

WD-01R1© (A. Johansson, Ericsson, Sweden) is the text of draft Recommendation G.ploam including the changes<br />

given in TD-22(WP1/15).<br />

D.417 (F. Van der Putten, Alcatel, Belgium) proposes clarifying text changes to sections 7, 8, and the Appendix of<br />

the Draft Recommendation. The group accepted the proposed changes.<br />

TD-49(PLEN)© (A. Johansson, Ericsson, Sweden) is the final text of G.997.1 (G.ploam) Physical Layer<br />

Management for Digital Subscriber Line (DSL) Transceivers proposed for Determination. It was Determined at the<br />

SG15 plenary.<br />

Dick Brandt dB Consulting<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 63


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

WP1/15 PARTIAL MEETING ROSTER, OCTOBER 12 – 23, 1998, GENEVA, SWITZERLAND<br />

Peter Wery, Nortel, Canada SG15 Chair<br />

Gastone Bonaventura, Telecom Italia, Itay SG15 Vice Chair<br />

Makoto Yamashita, NTT, Japan SG15 Vice Chair<br />

Andrew Nunn, BT, UK WP1/15 Chair<br />

Austria Post und Telekom Austria Gunter Reisinger<br />

Belgium Frank Van Der Putten<br />

Belgium Alcatel Bell Jan De Groote<br />

Belgium Alcatel Bell Danny Van Bruyssel<br />

Canada Peter Wery<br />

Canada Mitel Gordon Reesor<br />

Canada Mitel Silvana Rodrigues<br />

Canada Newbridge Networks F. Tian<br />

Canada Nortel Christian Bourget<br />

Canada Teleglobe Canada Surendra Sharma<br />

China Chen Yun Zhi<br />

China He Yida<br />

China Jiang Jing<br />

China Mao Qian<br />

China Peng Yang<br />

China Ren Shun Yao<br />

China Wang Jun Hua<br />

China Wei Le Ping<br />

China Zhang Zhi Yi<br />

Denmark Danish Electronics Industry Flemming Gerdstrom<br />

Denmark Tele Danmark Rune Hylsberg Jacobsen<br />

Finland Eino Jauhiainen<br />

Finland Vesa H. Kaiharju<br />

Finland Helsinki Telephone Co. Pasi Poikolainen<br />

Finland Helsinki Telephone Co. Seppo Tormala<br />

Finland Nokia Jouko Tormenen<br />

Finland Nokia Leif Wikberg<br />

France Gilles Joncour<br />

France Alain Lhermitte<br />

France Luc Peyrat<br />

France EUTELSAT Malcom Jones<br />

France France Telecom Georges Sebek<br />

France IBM Europe Sedat Oelcer<br />

France T.R.T. Yannik Schifres<br />

Germany Hans L. Koffler<br />

Germany Gunther Zedler<br />

Germany Alcatel SEL Seigfried Schmoll<br />

Germany Alcatel SEL Karl-Albert Turban<br />

Germany Bosch Walter Bourdon<br />

Germany Bosch Reinhold Feigel<br />

Germany Deutsche Telekom Ralf-Rainer Damm<br />

Germany Deutsche Telekom Andreas Templin<br />

Germany Siemens Paul Drugh<br />

Germany Siemens Franz Fimpel<br />

Germany Siemens Neal King<br />

Germany Siemens Hans-Joerg Thaler<br />

Germany Siemens Peter Wildenauer<br />

Germany Wandel und Goltermann Wolfgang Miller<br />

Great Britain Andrew Nunn<br />

Great Britain BT Nigel Billington<br />

Great Britain BT Tim Finegan<br />

64 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

Great Britain BT Ian Mann<br />

Great Britain BT Jerry Skorkowski<br />

Great Britain Cable & Wireless Philip King<br />

Great Britain GPT Ghani Abbas<br />

Great Britain Lucent Technologies John Magill<br />

Great Britain Racal Datacom Chris Firth<br />

Great Britain Tektronix UK Mark Lum<br />

Greece OTE Harris Katopodis<br />

Hungary MATAV Hungarian Telecomm Laszlo Barna<br />

India Surinder Kumar Malhotra<br />

India Silicon Automation Systems T. Arvind<br />

India Silicon Automation Systems Rajagiopalan Venkatraman<br />

Israel Reina Guy<br />

Israel Amir Ilevitzky<br />

Israel Ken Krechmer<br />

Israel Ilan Sharfer<br />

Israel National Semiconductor Avraham Gal<br />

Israel National Semiconductor Salvatore Napolitano<br />

Italy Sergio Cascelli<br />

Italy Marconi Massimiliano Amirfeiz<br />

Italy Marconi Davide Pagnotta<br />

Italy Pirelli Cavi e Sistemi Paolo Boero<br />

Italy Telcom Italia G. Bonaventura<br />

Japan Seiichi Takagi<br />

Japan Toshiro Kato<br />

Japan DDI Koichiro Tahara<br />

Japan Fujitsu Yutaka Awata<br />

Japan Fujitsu Akinori Kamijo<br />

Japan Fujitsu Ryoji Okita<br />

Japan Fujitsu Haruo Yamashita<br />

Japan Hitachi Tohru Kazawa<br />

Japan KDD Yoshinori Namihira<br />

Japan Matsushita Electric Industrial Stephen Palm<br />

Japan Mitsubishi Electric Wataru Matsumoto<br />

Japan Mitsubishi Electric Yushi Naito<br />

Japan NEC Yoshiyuki Moriguchi<br />

Japan NEC Yusaku Okamura<br />

Japan NTT Koji Kikushima<br />

Japan NTT Yoichi Maeda<br />

Japan NTT Kazuhiro Oda<br />

Japan NTT Masaharu Ohashi<br />

Japan NTT Makoto Yamashita<br />

Japan Oki Electric Industry Kazuho Kawagushi<br />

Japan Oki Electric Industry Yoshihiro Kondo<br />

Japan Oki Electric Industry Akihiro Takahashi<br />

Japan Sumitomo Electric Industries Kazuya Matsumoto<br />

Japan Toshiba Hiroshi Fukinuki<br />

Japan Toshiba Yasumasa Kikunaga<br />

Japan Toshiba Takeshi Sugoh<br />

Korea Yun Bin-Yeong<br />

Korea Korea Telecom Myung-Jun Kim<br />

Mexico Lucio Adame<br />

Netherlands KPN Stefan Op De Beek<br />

Netherlands Lucent Technologies Netherlands Peter Stassar<br />

Norway Jarle Kiil<br />

Norway Telenor AS Vidar Skovli<br />

Russia Yuri Alekseev<br />

Singapore Singapore Telecom Herjit Singh<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 65


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

Slovak Republic Slovak Telecom Jozef Nosik<br />

Spain Telefonica de Espana Gonzalo Sanchez Gilo<br />

Sweden Anders Hoglund<br />

Sweden Jorgen Karlsson<br />

Sweden L.M. Ericsson Albin Johansson<br />

Switzerland Hassane Makki<br />

Switzerland AscomTech Angus Carrick<br />

Switzerland AscomTech Kurt F. Gfeller<br />

Switzerland Swisscom Yu Wang<br />

Switzerland TSB Paolo Rosa<br />

Syrian Arab Republic Siba Attasi<br />

Syrian Arab Republic Kamal Awad<br />

Syrian Arab Republic Roula Massouh<br />

Ukraine Tetyana Andrushko<br />

Ukraine Mykola Biryukov<br />

Ukraine Anatoly Glushkovskyy<br />

Ukraine Viktor Katok<br />

Ukraine V. Victor Panteleev<br />

Ukraine Vartan Saroyan<br />

USA Elaine Baskin<br />

USA Steven Blackwell<br />

USA John Chen<br />

USA Marcos Maranhao<br />

USA James E. Matthews<br />

USA John McDonough<br />

USA Soching Tsai<br />

USA Benson Wang<br />

USA 3-COM Joseph Mueller<br />

USA 3-COM Richard Stuart<br />

USA Advanced Micro Devices Terry Cole<br />

USA Ameritech Services Tom Starr<br />

USA Analog Devices Rao Nuthalapati<br />

USA AT&T Deborah Brungard<br />

USA AT&T D. Sparrell<br />

USA Aware Marcos Tzannes<br />

USA Bay Networks Aleksandar Purkovic<br />

USA Bellcore Zhi-Wei Lin<br />

USA Centillium Technology Syed Abbas<br />

USA Centillium Technology Guozhu Long<br />

USA CIENA Corporation Jerry Shrimpton<br />

USA CIRRUS Logic Mandayam Krishnan<br />

USA Cisco Systems Amir Hindie<br />

USA Cisco Systems John Joyce<br />

USA COMPAQ Rabah Hamdi<br />

USA Corning Mark Soulliere<br />

USA Corning Steven E. Swanson<br />

USA ESS Technology Yuanjie Chen<br />

USA ESS Techonology Ping Dong<br />

USA General DataCom Yri Goldstein<br />

USA GlobeSpan Technologies Daniel Battu<br />

USA GTE BD&I Gary McAninch<br />

USA Intel Chris Hansen<br />

USA Intel Barry O'Mahony<br />

USA Level One Hanan Herzberg<br />

USA Lucent Technologies Subramanian Ambati<br />

USA Lucent Technologies Randall Brown<br />

USA Lucent Technologies Kevin Cone<br />

USA Lucent Technologies John Eaves<br />

66 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

USA Lucent Technologies Song Jiang<br />

USA Lucent Technologies Hing-Kam Lam<br />

USA Lucent Technologies Rick Townsend<br />

USA MCI Tele<strong>communications</strong> Daryl C. Tannis<br />

USA Motorola Information Systems Richard Brandt<br />

USA Motorola Information Systems Les Brown<br />

USA Motorola Information Systems Ken Cavanaugh<br />

USA Motorola Information Systems Bernard Dugerdil<br />

USA Pair Gain George Zimmerman<br />

USA Paradyne Corp. R.K. Smith<br />

USA PC-TEL Gary Anwyl<br />

USA PC-TEL Enrico Cadorin<br />

USA Pulsecom Dennis Rauschmayer<br />

USA Rockwell International Glen Griffith<br />

USA Rockwell International Ragnar Jonsson<br />

USA RSA Communications Raymond Chen<br />

USA SBC Technology Resources Richard McDonald<br />

USA SBC Technology Resources John Roquet<br />

USA Texas Instruments James Aslanis<br />

USA Texas Instruments James Carlo<br />

USA VoCAL Technologies Joan Alberto Torres<br />

Communications Standards Review – Tele<strong>communications</strong><br />

regularly covers the following committee meetings:<br />

TIA TR-29 Facsimile<br />

TR-30 Modems<br />

TR-41 User Premises Equipment<br />

ITU-T SG8 Telematic Terminals<br />

SG15 WP1 Network Access<br />

SG16 Multimedia<br />

ETSI ATA Analog Terminal Access<br />

DTA Digital Terminal Access<br />

MTA Multimedia Terminals<br />

TC SP Speech Processing<br />

TC STQ Speech Transmission Quality<br />

TIPHON Voice Over Internet<br />

TM6 Transmission & Multiplexing<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 67


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

ACRONYM DEFINITIONS<br />

AAL ATM Adaptive Layer<br />

ACELP Algebraic Code Excited Linear Predictor<br />

ACTS Advanced Communications Technology Satellite<br />

ADSL Asymmetric Digital Subscriber Line<br />

AFE Analog Front End<br />

AIS Alarm Indication Signal<br />

ANAI Access Network Architecture and Interfaces<br />

ANSI American National Standards Institute<br />

ANT Access Network Transport (Q1/15)<br />

API Application Programming Interface<br />

ASN Abstract Symbol Notation<br />

ATM Asynchronous Transfer Mode<br />

B-ISDN Broadband ISDN<br />

BER Bit Error Rate<br />

BOF Birds of a Feather<br />

CELP Code Excited Linear Prediction<br />

CI Call Indicator (V.8)<br />

CM Call Menu<br />

CNI Calling Number Identification<br />

CORBA Common Object Request Broker Architecture<br />

CPE Customer Premise Equipment<br />

CS-ACELP Conjugate Structure -Algebraic Code Excited Linear Predictive<br />

DAVIC Digital Audio-Visual Council<br />

DC Direct Current<br />

DCE Data Circuit Terminating Equipment<br />

DCME Digital Circuit Multiplication Equipment<br />

DCT Discrete Cosine Transform<br />

DMT Discrete Multi-tone Carrier<br />

DSS1 Digital Subscriber Signaling 1<br />

DTE Data Terminal Equipment<br />

DTMF Dual Tone Multi Frequency<br />

ETSI European Tele<strong>communications</strong> Standards Institute<br />

EURESCOM European Inst. for Research & Strategic Studies in Tele<strong>communications</strong><br />

FEC Forward Error Control<br />

FEXT Far End Cross Talk<br />

FSAN Full Service Access Networks<br />

FTTB Fiber to the Building<br />

FTTC Fiber to the Curb<br />

FTTCab VDSL to the cabinet<br />

FTTH Fiber to the Home<br />

FWA Fixed Wireless Access<br />

GII Global Information Infrastructure<br />

GK GateKeeper<br />

GSM Global System for Mobile Communications<br />

HSD High Speed Data Channel<br />

ICG Intersector Coordination Group<br />

IDCT Inverted Discrete Cosign Transform<br />

IE Protocol Discriminator Information Element<br />

IEC International Electrotechnical Committee<br />

IETF Internet Engineering Task Force<br />

IFTP Informal FTP area<br />

IMT International Mobile Tele<strong>communications</strong> (IMT-2000)<br />

IP Internet Protocol<br />

IPDC IP Device Control<br />

IPR Intellectual Property Rights<br />

iptel Internet Protocol Telephony (IETF Working Group)<br />

ISDN Integrated Services Digital Network<br />

68 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

ISDN-BA ISDN basic access<br />

ISOC Internet Society<br />

ISUP ISDN User Part<br />

JM Joint Menu<br />

JRG Joint Rapporteurs Group<br />

LATA Local Access Transport Area<br />

LD-CELP Low Delay CELP<br />

LOI Letter of Intent<br />

LSD Low Speed Data channel<br />

LT Line Termination<br />

MAP Mobile Application Part<br />

MCS Multi-point Control Services (T.122)<br />

MCU Multi-point Control Unit<br />

MIB Management Information Base<br />

MLP Multi-Layer Protocol<br />

MMUSIC Multiparty Multimedia Session Control (WG)<br />

MOU Memorandum of Understanding<br />

MPEG Motion Picture Experts Group<br />

N-ISDN Narrowband ISDN<br />

NT Network Termination<br />

NTR Network Timing Reference marker<br />

OAM Operations, Administration, and Maintenance<br />

OAN Optical Access Network<br />

OMG Object Management Group<br />

ONU Optical Network Unit<br />

OPTIS Overlapped PAM Transmission with Interlocking Spectra<br />

PAM Pulse Amplitude Modulation<br />

PAR Peak to Average Ratio<br />

PCM Pulse Code Modulation<br />

PCME Packet Circuit Multiplication Equipment<br />

PDH Packet Digital Hierarchy<br />

PINT PSTN Interworking (IETF)<br />

PMD Physical Media Dependent Layer<br />

PON Passive Optical Network<br />

POTS Plain Old Telephone Service<br />

PSD Power Spectral Density<br />

PSQM Perceptual Subjective Quality Measure<br />

PSTN Public Switched Telephone Network<br />

QoS Quality of Service<br />

RBS Robbed-bit signaling<br />

RDC Remote Device Control<br />

REC RECeive alarm<br />

RFC Designation for an Internet Standard<br />

RTP Real Time Transport Protocol<br />

SAT Satellite<br />

SCN Switched Circuit Network<br />

SCR Selective Call Rejection<br />

SDH Synchronous Digital Hierarchy<br />

SDL Specification and Description Language<br />

SDSL Symmetrical high bit rate Digital Subscriber Line<br />

SG Study Group (ITU, CCITT)<br />

SLP Service Location Protocol<br />

SMG Special Mobile Group<br />

SNMP Simple Network Management Protocol<br />

SOHO Small Office Home Office<br />

SUD Single Use Device<br />

TA Terminal Adapter<br />

TBR Technical Basis for Regulation (ETSI standard)<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 69


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

TC Technical Committee<br />

TC Transmission Convergence Layer<br />

TCP Transmission Control Protocol<br />

TINA Tele<strong>communications</strong> Information Networking Architecture<br />

TSAG Telecommunication Standardization Advisory Group<br />

TSB Tele<strong>communications</strong> Standardization Board (ITU)<br />

UDP User Datagram Protocol<br />

UMTS Universal Mobile Tele<strong>communications</strong> System<br />

UNI User-Network Interface<br />

UPC Usage Parameter Control<br />

VAD Voice Activity Detector<br />

VDSL Very high speed ADSL<br />

WG Working Group<br />

xDSL all the different Digital Subscriber Lines<br />

XNI Customer Network Interface<br />

THE CSR LIBRARY<br />

Subscribers may order copies of documents shown in boldface type<br />

from Communications Standards Review, where not controlled.<br />

Documents listed with © are controlled documents. These documents are not for sale, but we<br />

can provide you with the author’s contact information.<br />

-e means we have electronic copy only; +e means we have electronic<br />

and hard copy available. We have a large library of <strong>standards</strong> work in process and can help<br />

you locate other information you may need.<br />

The next issue of Communications Standards Review – Tele<strong>communications</strong> (Vol. 10 #1) is scheduled for<br />

January 1999.<br />

70 Vol. 9.8 Copyright © CSR 1998 November-December 1998


COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS<br />

1998 STANDARDS COMMITTEE MEETING SCHEDULES<br />

AS OF NOVEMBER 4, 1998<br />

Subject to Change without Notice<br />

Committee Date(s) Location<br />

Q1/8, Q3/8, Q4/8<br />

Rapporteur<br />

Nov 2 - 6 UK<br />

Q15/16 Rapp. Nov 3 - 6 Seoul, Korea<br />

TR-29 Nov 9 - 13 Arlington, VA<br />

TR-30 Nov 9 - 13 Clearwater, FL<br />

ETSI DTA Nov 16 - 18 Berlin, Germany<br />

TR-41 Nov 16 - 20 Palm Springs, CA<br />

Committee Date(s) Location<br />

Q11-14/16 Rapp. Nov 17 - 20 Torino, Italy<br />

ETSI TM6 (only Nov 24 - 27 Sophia Antipolis,<br />

VDSL and SDSL)<br />

France<br />

T1E1 Nov 0-Dec 4 Texas<br />

ETSI ATA Dec 7 - 11 South Africa<br />

Q4/16, Q10/16,<br />

Q23/16 Rapp.<br />

Dec 7 - 10 San Diego, CA<br />

1999 STANDARDS COMMITTEE MEETING SCHEDULES<br />

AS OF NOVEMBER 4, 1998<br />

Subject to Change without Notice<br />

Committee Date(s) Location<br />

Q1/16 Rapp. January Tokyo<br />

ETSI TIPHON Jan 11 - 15 S. Antipolis, Fr.<br />

Q4/15 Rapp. Jan 18 - 22 Orlando<br />

Q3/16 Rapp. Jan 19 - 21 California<br />

TR-29 Feb 8 - 10 Newport Bch, CA<br />

TR-30 Feb 8 - 11 ---<br />

TR-41 Feb 21 - 26 Sarasota, FL<br />

ETSI TM6 Feb 22 - 26 Tel Aviv, Israel<br />

Q11-15/16 Rapp. Feb 23 - 26 New Jersey, US<br />

ETSI TIPHON March New Jersey, USA<br />

T1E1 Mar 8 - 12 ---<br />

ITU-T SG8 Mar24-Apr 1 Geneva<br />

Q4/15 Rapp. Mar29-Apr 2 Melbourne<br />

TR-30 Apr 12 - 15 ---<br />

ETSI TIPHON May Belgium<br />

ETSI TM6 May 3 - 7 Grenoble, France<br />

Q4/15 Rapp. May 10 - 14 Boston, MA<br />

T1E1.4 Interim May 17 - 18 Boston, MA<br />

Committee Date(s) Location<br />

TR-41 May 17 - 21 ---<br />

ITU-T SG16 May 18 - 28 Santiago, Chile<br />

T1E1 Jun 7 - 11 ---<br />

TR-30 Jun 14 - 17 California<br />

ITU-T SG15 Jun 21-Jul 2 Geneva<br />

Q15/16 Rapp. July ---<br />

ETSI TIPHON July Manchester, UK<br />

TR-30 Aug 9 - 12 Quebec City, PQ<br />

TR-41 Aug 23 - 27 ---<br />

T1E1 Aug 22 - 23 ---<br />

ETSI TM6 Sep 20 - 24 UK<br />

TR-30 Oct 11 - 14 Baltimore, MD<br />

Q15/16 Rapp. November<br />

TR-41 Nov 15 - 19 Reno, NV<br />

TR-30 Nov29-Dec 2 ---<br />

ETSI TM6 Nov29-Dec 3 Netherlands<br />

T1E1 Dec 6 - 10 ---<br />

Visit the CSR Web Pages: http://www.csrstds.com<br />

The Web Pages include an updated Telecom Acronym Definitions list, updated meeting schedules, a list of web sites<br />

and ftp sites as listed in all issues of CSR journals, background material on telecom <strong>standards</strong> and CSR (the<br />

company), data sheets on both CSR technical journals, and more.<br />

Communications Standards Review –Tele<strong>communications</strong> (ISSN 1081-4655) is published<br />

8 - 9 times per year, within days after the latest, related <strong>standards</strong> meetings. Editor: Elaine J. Baskin, Ph.D.<br />

Technical Editor: Ken Krechmer. Copyright © 1998, Communications Standards Review. All rights reserved.<br />

Copying of individual articles for distribution within a subscriber organization is permitted. Subscriptions: $695.00<br />

per year worldwide, $795.00 in electronic format. Corporate Intranet subscriptions (site license for multiple copies)<br />

are available. Submit articles for consideration to: Communications Standards Review, 757 Greer Road, Palo Alto,<br />

CA 94303-3024 U.S.A. Tel: +1-650-856-9018. Fax: +1-650-856-6591. e-mail: ebaskin@csrstds.com. WWW:<br />

http://www.csrstds.com. 19908<br />

November-December 1998 Vol. 9.8 Copyright © CSR 1998 71

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!