CSR Volume 10 #6, July 1999

COMMUNICATIONS STANDARDS REVIEW

Volume 10, Number 6 July1999

In This Issue

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

Report of ITU-T SG16, Multimedia, May 17 - 28, 1999, Santiago, Chile ...... 2 Documents Approved by Resolution No. 1 Process...... 2 Other Documents Approved by the Study Group ...... 3 Documents Determined (i.e., First Part of the Resolution No. 1 Approval Process)...... 4 WP1, Low Rate Systems ...... 5 WP2, Services and High Rate Systems...... 7 WP3, Signal Processing...... 8 Q1/16 WP2, Audiovisual/multimedia Services...... 10 Q2/16 WP2, Interactive Multimedia Information Retrieval Services (MIRS)...... 11 Q3/16 WP2, Data Protocols for Multimedia Conferencing...... 11 Q4/16 WP1, Modems for Switched Telephone Network and Telephone Type Leased Lines...... 12 Q5/16 WP1, ISDN Terminal Adapters, and Interworking of DTEs on ISDNs with DTEs on Other Networks...... 14 Q6/16 WP1, DTE-DCE Interchange Circuits...... 14 Q7/16 WP1, DTE-DCE Interface Protocols...... 15 Q8/16 WP1, DCE-DCE Protocols...... 16 Q9/16 WP1, Accessibility to Multimedia for People with Disabilities...... 16 Q10/16 WP1, Modem Testing...... 18 Q11/16 WP2, Circuit Switched Network (CSN) Multimedia Systems and Terminals...... 18 Q12/16 WP2, B-ISDN Multimedia Systems and Terminals...... 21 Q13/16 WP2, Packet Switched Multimedia Systems and Terminals...... 23 Q14/16 WP2, Common Protocols, MCUs & Protocols for Interworking with H.300-series Terms.... 31 Q15/16 WP3, Advanced Video Coding...... 36 Q16/16 and Q17/16, Multimedia Harmonization and Coordination...... 40 Q19/16 WP3, Extension to Existing ITU-T Speech Coding Standards at Bit Rates Below 16 kbit/s 41 Q20/16 WP3, Audio and Wideband Coding in Public Telecommunication Networks...... 43 Q21/16 WP3, Encoding of Speech Signals at Bit Rates around 4-kbit/s...... 47 Q22/16 WP3, Software and Hardware Tools for Standardization of Speech and Audio Coding Algorithms ...... 50 Q23/16 WP1, PCM Modems...... 52 ITU-T SG/16 Meeting Roster, May 17 - 28, Santiago Chile...... 54 Acronym Definitions ...... 58 1999 and 2000 Standards Committee Meeting Schedules as of June 25, 1999 ...... 62

REPORT OF ITU-T SG16, MULTIMEDIA, MAY 17 - 28, 1999, SANTIAGO, CHILE DOCUMENTS APPROVED BY RESOLUTION NO. 1 PROCESS

Q Title Documents 1 F.700 Annex C.1, Control and processing elements descriptions COM 16-R 41© 1 F.700 revised Annex B.2, Communication task conferencing COM 16-R 41© 19 G.728 Annex I, Frame or packet loss concealment for the LD-CELP COM 16-R 44©, TD- decoder 25(PLEN) 19 G.728 Annex H, Corrigendum Variable bit rate LD-CELP operation COM 16-R 44© mainly for DCME at rates less than 16 kbit/s 11 H.221 revised, Frame structure for a 64 to 1920 kbit/s channel in COM 16-83© audiovisual teleservices 12 H.222.0 Amendment 5, ISO/IEC 13818-1, Information technology - COM 16-76© generic coding of moving pictures and associated audio information: systems 12 H.222.0 Amendment 6, ISO/IEC 13818-1, Information technology - COM 16-77©, TD- generic coding of moving pictures and associated audio information: 28(PLEN) systems 11 H.223 Annex D, Optional multiplexing protocol for low bit rate mobile COM 16-81©, D.308© multimedia communication over highly error-prone channels 13 H.225.0 Annex G*, Communication between administrative domains COM 16-75©, TD- 32(PLEN), TD-53(PLEN) 11 H.230 revised, Frame-synchronous control and indication signals for COM 16-84©, TD- audiovisual systems 18(PLEN) 11 H.242 revised, System for establishing communication between COM 16-85©, TD- audiovisual terminals using digital channels up to 2M kbit/s 19(PLEN) 14 H.245 version 5 Control protocol for multimedia communication COM 16-79©, TD- 54(PLEN) 15 H.262 Amendment 5, ISO/IEC 13818-2, Generic coding of video, high COM 16-82© level for the 4:2:2 profile 14 H.282 (ex-V.RDC), Remote device control protocol for multimedia COM 16-R 41© applications 14 H.283 (ex-H.RDC), Remote device control logical channel transport COM 16-78©, TD- 27(PLEN) 11 H.320 revised, Narrow-band visual telephone systems and terminal COM 16-86©, TD- equipment 17(PLEN) 13 H.323 Annex E, Framework and wire-protocol for multiplexed call COM 16-74©, TD- signaling transport 33(PLEN), TD-53(PLEN) 13 H.323 Annex F, Simple Endpoint Types (SET) COM 16-73©, TD- 52(PLEN) 14 H.341 (ex-H.media MIB), Multimedia management information base COM 16-80©, TD- 55(PLEN), TD-55Att© 13 H.450.4, Call hold supplementary service for H.323 COM 16-87© 13 H.450.5, Call park and call pickup supplementary services for H.323 COM 16-88© 13 H.450.6, Call waiting supplementary services for H.323 COM 16-89© 13 H.450.7, Message waiting indication supplementary service for H.323 COM 16-90© 3 T.123 revised, Network specific data protocol stacks for multimedia COM 16-R 41©, TD- conferencing 5(PLEN), TD-35(PLEN) 3 T.136 (ex-T.RDC), Remote device control application protocol COM 16-R 41© 4 V.8 Addendum, Modem handshake TD-39(PLEN) 23 V.91 (ex-V.adm), All digital modem (adm) operating at data signaling COM 16-72©, TD- rates of up to 64 000 bit/s for use on a 4-wire circuit switched connection 38(PLEN) and on leased point-to-point 4-wire digital circuits 5 V.120 Corrigendum, Support by an ISDN of DTEs with V-series type COM 16-R33© interfaces with provision for statistical multiplexing 7 V.250 revised, Serial asynchronous automatic dialing and control COM 16-R33©

* The USA Administration applied the 4-week rule (i.e., requested a further 4 weeks for consideration) on this Recommendation. However, it is expected to pass. (See Q14/16 report, below.)

OTHER DOCUMENTS APPROVED BY THE STUDY GROUP

Q Title Documents 19 Implementors Guide for G.723.1 Annexes A, B and G.729 Annex E TD-26(PLEN) 11 H.223 Implementors Guide Update TD-16(PLEN) 11 H.324 Implementors Guide Update TD-15(PLEN) 13 Implementors Guide for ITU-T H.323, H.225.0, H.245, H.246, H.235 and H.450 TD-37(PLEN), TD-56(PLEN) 9 & 15 Supplement to H.series Recommendations on Sign Language and Lip Reading D.290©* 3 Implementor’s Guide for T.120, T.124, T.127 TD-6 (PLEN) 4 Implementors Guide for V.8bis, Modem handshake TD-40(PLEN) 9 Implementors Guide for V.18, Operational and interworking requirements for TD-8(PLEN) DCEs operating in the text telephony mode

* A copyright statement regarding the video material supplied with this Supplement is available in TD- 75(PLEN). In concurrence with ISO/IEC JTC1/SC29 (MPEG), ITU-T SG16 agrees to publish an integrated edition of common text Recommendations including the following texts: 1) ITU-T Rec. H.222.0 | ISO/IEC 13818-1, Information technology - generic coding of moving pictures and associated audio information: systems

Pub. Date Q12 ITU-T Rec. H.222.0 | ISO/IEC 13818-1 07/95 Q12 ITU-T Rec. H.222.0 | ISO/IEC 13818-1 / Amd.1 11/96 Q12 ITU-T Rec. H.222.0 | ISO/IEC 13818-1 / Amd.2 11/96 Q12 ITU-T Rec. H.222.0 | ISO/IEC 13818-1 / Amd.3 02/98 Q12 ITU-T Rec. H.222.0 | ISO/IEC 13818-1 / Amd.4 02/98 Q12 ITU-T Rec. H.222.0 | ISO/IEC 13818-1 / Amd.5 05/99 Q12 ITU-T Rec. H.222.0 | ISO/IEC 13818-1 / Amd.6 05/99 Q12 ITU-T Rec. H.222.0 | ISO/IEC 13818-1 / Amd.7 to be 02/00 Q12 ITU-T Rec. H.222.0 | ISO/IEC 13818-1 / Corr.1 03/97

2) ITU-T Rec. H.262 | ISO/IEC 13818-2, Information technology - generic coding of moving pictures and associated audio information: video

Pub. Date Q15 ITU-T Rec. H.262 | ISO/IEC 13818-2 07/95 Q15 ITU-T Rec. H.262 | ISO/IEC 13818-2 / Amd.1 11/96 Q15 ITU-T Rec. H.262 | ISO/IEC 13818-2 / Amd.2 11/96 Q15 ITU-T Rec. H.262 | ISO/IEC 13818-2 / Amd.3 02/97 Q15 ITU-T Rec. H.262 | ISO/IEC 13818-2 / Amd.4 02/97 Q15 ITU-T Rec. H.262 | ISO/IEC 13818-2 / Amd.5 05/99 Q15 ITU-T Rec. H.262 | ISO/IEC 13818-2 / Amd.6 to be 02/00 Q15 ITU-T Rec. H.262 | ISO/IEC 13818-2 / Corr.1 06/96 Q15 ITU-T Rec. H.262 | ISO/IEC 13818-2 / Corr.2 06/96

DOCUMENTS DETERMINED (I.E., FIRST PART OF THE RESOLUTION NO. 1 APPROVAL PROCESS)

Q Title Documents 1 F.700, Audiovisual/multimedia services TD-73(PLEN), TD- 74(PLEN) 20 G.722.1 (ex G.WB1), 7 kHz Audio-coding at 24 and 32 kbit/s for hands-free TD-21(PLEN), TD- operation in systems with low frame loss 51(PLEN) 19 G.728 Annex J, 40 kbit/s codec extension TD-67(PLEN) 12 H.222 - ISO/IEC 13818-1 Amendment 7 for MPEG-4 carriage over MPEG- TD-23(PLEN) 2 Transport Stream 14 H.224 (A real time control protocol for simplex applications using the TD-11(PLEN) H.221 LSD/HSD/MLP channels) added codepoint for T.140 13 H.225.0v3, Call signaling protocols and media stream packetization for TD-68(PLEN)© packet based multimedia communication systems 14 H.243, Procedures for establishing communication between three or more TD-20(PLEN) audiovisual terminals using digital channels up to 1920 kbit/s 14 H.245v6, Control protocol for multimedia communication TD-14(PLEN), TD-22( PLEN), TD-24(PLEN), TD-69(PLEN) 14 H.246 Annex C, ISUP - H.225.0 interworking TD-34(PLEN) 15 H.262 Amendment 6 (Number of lines in all profiles of high level) TD-3(PLEN) 13 H.323 Annex G, Text communication in H.323 & Text SETs D.282© 13 H.323v3, Packet based multimedia communication systems TD-57(PLEN)© 11 H.324 Annex F - Support of ISO/IEC 14496-1 codecs TD-13(PLEN) 13 H.450.8 - (ex H.450.10) Name identification services TD-30(PLEN) 14 H.GCP, Gateway control protocol TD-29(PLEN)© 9 T.140 Addendum, Addition of a marker for missing text TD-10rev(PLEN) 3 T.MRM, Meeting room management TD-7(PLEN) 6 V.24 Revised, List of definitions of interchange circuits between DTE and TD-4(PLEN) DCE 5 V.110 Revised, Support by an ISDN of data terminal equipment with V- TD-9(PLEN)© series type interfaces

SG16 GENERAL ISSUES Study Group 16 held its fourth meeting at the University of Chile in Santiago, at the invitation of the Chilean Administration and the University. SG16 has three Working Parties (WPs):

WP Title Chairman Report WP1/16 Low Rate Systems John Magill, Lucent (UK) TD-42 (PLEN) WP2/16 Services and High Rate Systems Federico Tosco, CSELT (Italy) TD-59 (PLEN) WP3/16 Signal Processing Simao Campos Neto, Comsat (US) TD-48 (PLEN)

The activities of these Working Parties are reported below.

WORKSHOP ON MULTIMEDIA A successful workshop on Multimedia Application and Network was held on May 17, 1999, the first day of SG16. The program is in Annex 3 to TD-70(PLEN). The presentations from the workshop are available at: • http://www.ict.uchile.cl/itut.sg16/workshop.html • http://www.itu.int/ITU-T/com16/santiago/index.html

LIAISONS TD-21(GEN) reports that Q4/4 has Determined (Approval 2/2000) the new X.700 series technical corrigenda which provide guidance in the use of the new ASN.1 Recommendations. New ITU-T recommendations are no longr able to reference ASN.1 1990. The new reference is to X.680-1997 | ISO/IEC 8824-1:1998.

TD-4(GEN) from SG11 provides the IMT-2000 preliminary consolidated work plan. Activities of SG2: TD-22(GEN) reports on the study of the expansion of E.164 (PSTN numbering) from 3 to 4 digit country codes. Q1/2 anticipates exhaustion of 3 digit country codes in 10-15 years. TD-24(GEN) provides a very preliminary draft of E.MM, Routing of multimedia connections when interworking with PSTN, ATM and IP networks. TD-25(GEN) notes the establishment of a fraud prevention coordinator in SG2 and provides a list of six other organizations dealing with fraud prevention. WD2-20 is the Q13/Q14 response to this liaison. The response discusses the capabilities of H.235. Activities of SG10 on Formal Description Languages: • Q2/10 has developed the ITU-T Object Definition Language Z.130 (TD-7(GEN). • SG10 is updating Recommendation Z.110-1996, Criteria for use of formal description languages by the ITU-T (TD-8(GEN)). WD2-05 is Q13/16’s response to the Questionnaire for ASN.1 and SDL. • TD-11(GEN) reports that new versions of Recommendations Z.100 (State Description Language) and Z.120 (Message Sequence Chart [MSC]) were Determined in February, 1999; Approval is planned for November, 1999. Tool vendors are expected to support the new versions shortly after final approval. TD-27(GEN) reports that SG12 is developing three recommendations relating to end-to-end performance: • G.108, Application of the E-Model (G.107) - a planning guide • G.109, definition of categories of speech transmission quality • G.177, transmission planning for voiceband services over hybrid internet/PSTN connections The activities of SG13 on the GII Project plan, IP Project coordination (SG13 is the Lead SG), IETF coordination (listing of all IETF WGs related to ITU SGs) and multimedia coordination (status of activities in SGs 2, 12, 16) are reported in TD-13(GEN), TD-14(GEN), TD-15(GEN), and TD-16(GEN), respectively. TD-17(GEN) is the Report on SG13 Plenary Meeting and on GII Issues, February 15-26, 1999. (See the Q16/17 report, below.) TSAG Matters are reported in TD-18(GEN), ITU internal liaison procedures; TD-19(GEN), guidelines for ISOC/IETF collaboration (includes referencing guidelines); and TD-20(GEN), EDH information.

FUTURE MEETINGS A half day meeting of Study Group 16 is planned for September 30, 1999, for the purposes of approving appropriate texts, particularly Determined Recommendation G.722.1. This opportunity will also be used to approve outputs from the interim meeting of Q16/16 and Q17/16 e.g., for input to the October meeting of ITU-T TSAG. The next full meeting of SG16 is scheduled for February 7-18, 2000. WP1, LOW RATE SYSTEMS The Rapporteur for WP1 is J. Magill (Lucent, UK). The agenda for the meeting, together with meeting schedule and document allocation table is in TD-24(WP1/16). The Working Party 1 report of this meeting is comprised of TD-41(PLEN) through TD-47(PLEN). The updated status report for Recommendations that are the responsibility of WP1 is published in TD- 46(PLEN). The questions currently allocated to WP1 (and respective Rapporteurs) are: Q4 Modems for Switched Telephone Network and Telephone Type Leased Lines (B. Adams, Motorola, USA) Q5 ISDN terminal adapters, and interworking of DTEs on ISDNs with DTEs on other networks (J. Moughton, UK) Q6 DTE-DCE Interchange Circuits (R-R Damm, Deutsche Telekom, Germany) Q7 DTE-DCE Interface Protocols (F. Lucas, 3Com, USA) Q8 DCE-DCE Protocols (W. Pechey, UK)

Q9 Accessibility to Multimedia for People with Disabilities (G. Hellström, Ericsson, Sweden) Q10 Modem Testing (G. List, Austria) Q23 PCM Modems (L. Brown, Motorola, USA) The Q5 session was chaired by the WP1 Chair as J. Moughton has changed companies and is no longer able to continue as Rapporteur. Because the Rapporteur for Q8 was not available to attend the meeting, the Q8 session was also chaired by the WP1 Chair.

FUTURE OF Q18/16 No further contributions have been received for Q18/16 Interaction of high-speed voiceband data processing systems with signal processing, so in accordance with the proposal at the Sept. 1999 meeting of SG16, WP1 agreed to request deletion of Q18 and transfer of the work to SG15. SG15 indicated in a Liaison in TD-6(WP1/16) that they are revising the current Q8/15 to include general aspects of interactions among signal processing elements.

REVISIONS TO QUESTIONS IN WP1/16 In preparation for the next study period, WP1 reviewed the text of the current Questions and current activity, and agreed to the changes shown below. Initial draft text for these new Questions is contained in TD-47(PLEN).

PROPOSED QUESTIONS FOR THE NEXT STUDY PERIOD Q1A/16 WP1, Voice-band Modems: Specification and Performance Evaluation, proposed as a continuation of existing Q4/16, Q10/16 and Q23/16. This work is planned to lead to new recommendations for: • Enhancements to Recommendation V.90 (1998). • Enhancements to Recommendations V.8 and V.8bis. • A network model and test procedures for the evaluation of V.9x series modem performance. Q1B/16 WP1, DCE-DCE Protocols for the PSTN and ISDN, is proposed as a continuation of existing Q5/16 and Q8/16. This study includes the work on HDLC-based protocols for both modem-based communication, i.e., V.42 and V.75, and ISDN-based communication, i.e., V.120. Also, data compression on top of these protocols will be addressed. Continued study is necessary on issues arising from new applications (e.g., IP networks). Q1C/16 WP1, DTE-DCE Interfaces and Protocols, is proposed as a continuation of existing Q6/16 and Q7/16. The need for the continued study of DTE-DCE interfaces and protocols to keep pace with changing modem and DTE technologies remains of high importance. Q1D/16 WP1, Accessibility to Multimedia for People with Disabilities, is proposed as a continuation of existing Q9/16. This work produces and maintains Recommendations for multimedia systems and services of specific interest to people with disabilities. The focus of the new Question is on the establishment of recommendations for Total Conversation services. Total Conversation is a concept for standardized communication in video, text and voice simultaneously. While applications include conversation with sign language, lip-reading, text and other alternative communication means, emphasis in the new question is to be placed on design suitable for all. Recommendation V.18 is the platform for plain text telephony in the PSTN. Recommendation T.140 is the common text conversation presentation protocol used in all Total Conversation environments. Total Conversation is the extension of text conversation from videotelephony to all networks. The new question will also address the selection of any perceivable media presentation, and to activate media conversions to get intelligible presentation of media.

HOME PHONELINE NETWORKING The meeting was made aware that some companies intend to request initiation of work in the ITU-T on local networking devices that use existing telephone wiring in the home to connect PCs in the home. While WP1 believes that SG16 could undertake this work, it is understood that a

proposal will be made to do the work in SG15. No further action was taken. (See Q4/15 report in CSR Vol. 10.5.) WP2, SERVICES AND HIGH RATE SYSTEMS The WP2 reports of this meeting are contained in TD-58(PLEN) through TD-64(PLEN). The Rapporteur for Q14/16, G Thom (Delta Information Systems), informed WP2 that, due to the assumption of a new responsibility in his company, he would not be able to remain as Rapporteur for Q14/16. WP2 thanked G. Thom for the work he has done. SG16 appointed G. Freundlich (Lucent Technologies) as new Rapporteur for Q14/16. The questions currently allocated to WP2 (and respective Rapporteurs) are: Q1 Audiovisual/multimedia Services (Y. Robin-Champigneul, FT/CNET, France) Q2 Interactive Multimedia Information Retrieval Services (MIRS) (M. Blaschitz, Infonova, Austria) Q3 Data Protocols for Multimedia Conferencing (B. DeGrasse, DataBeam, USA) Q11 Circuit Switched Network (CSN) Multimedia Systems and Terminals (T. Geary, Conexant, USA) Q12 B-ISDN Multimedia Systems and Terminals (S. Okubo, TAO, Japan) Q13 Packet Switched Multimedia Systems and Terminals (D. Skran, Ascend, USA) Q14 Common Protocols, MCUs and Protocols for Interworking with H.300-series Terminals (G. Freundlich, Lucent, USA)

QUESTIONS FOR THE NEXT STUDY PERIOD An ad hoc drafting group consisting of S. Okubo, D. Skran, T. Geary, and Y. Robin-Champigneul discussed issues relating to preparation of questions for the next study period. The result of that work is an initial draft, Annex 2 of the WP2 report (TD-59(PLEN). The plan is to provide an updated version of the questions at the Sept. 1999 SG16 meeting, then finalize the work at the Feb. 2000 SG16 meeting. Based on the general migration toward more private packet oriented networks which are interconnected with the present Internet, the following organization is suggested: Potential new work areas beyond those for the current study period for SG16: Question A: H.NewTerminal The goal of this question is to specify a new H.xxx terminal with the following goals: • Operate above transport layers • Used generally over IP, over all kind of physical layers (cable, xDSL, mobile, etc.) • Optionally negotiate more optimal transport mechanisms, such as H.223 or H.323 Annex C. • Operate in the same fashion in both public and private networks • Make use of H.323 infrastructure such as Gatekeepers • Would not be for either very high or very low bit rates, but would have other goals (see audio/video/data questions). • It might or might not be fully backward compatible with H.323. A minimum goal would be backward compatibility via a GK/MCU. Question B: Video for H.NT The goal of this work is to specify a new video coder, H.x264 with the following characteristics: • Very low delay (<100 msec coder delay) • Good image performance in the range of 384 kbit/s to 1000 kbit/s • Very good robustness to packet loss, including layering methods • A general assumption is that operation in sub 384 kbit/s ranges would require H.263+ and over 1M would require H.262. • Low complexity would be of lesser importance • Consideration should be given to the usage of object modeling techniques to achieve these ends

Question C: Audio for H.NT (G.NT) A general assumption is that a wide range of good audio coders already exist. H.NT would have as a common set of mandatory coders G.711 and G.NT. G.4KBPS would be a major/preferred option, or might be mandatory. A major obstacle to the widespread usage of G.729 and G.723.1 has been the complex intellectual property environment. The time has come to specify a new ITU-T coder G.NT with the following goals: • Either no currently valid patents are used, or the patent holders sign in advance a special contract stating that the specific technology offered to the ITU-T can be licensed for a nominal fee, defined as a fixed one time fee per patent. A statement to this effect will be part of each contribution to this question. • Minimal complexity • Toll quality • Low delay • Robustness in the face of packet loss • Support for layering • Minimal bit rate is not critical Question D: H.NT and H.323 (Mobile Aspects) In recognition of the importance of mobility issues, a question should be devoted to them, including terminal, user, and service mobility. This work should complement IMT-2000 rather than duplicate it. Question E: H.NT (Data Aspects) This question should take a fresh look at data conferencing in the context of H.NT. Particular focus should be placed on using web and Internet technology. This should be done as part of H.NT rather than as a separate work item as with T.120. A key goal is total multimedia integration. Question F: H.NT Infrastructure This question would look at infrastructure for H.NT and H.323, including: MCUs, GKs, GWs, including H.GCP and H.246, MIBs, Management tools and methods, including H.341 and comments regarding work of other SGs. Maintenance work items for the next study period may be reorganized into different Questions such as outlined below. Question G: Maintenance of T.series & H.series recommendations This question (which might be split into two questions), would look after the on-going maintenance of the following documents: T.120, H.320, H.321, H.322, H.310, H.324, H.224/H.231/H.243, H.224, H.242, H.244, H.221, H.223, H.226 Question H: Continuation of Q13/Q14 (H.323 & related work) This question would continue the work of Q13/Q14. Note that the older common work (Q14) is proposed to be moved to Question G (maintenance) and some of the newer work to Question F. This question would cover on-going work in: H.323, H.225.0, H.450.x, H.245, H.235. It is clear that H.323 work will continue into at least the first half of the next study period, so this question needs to continue. Work has already been identified that will not be completed by Feb. 2000. Currently image coding work spans multiple SGs with ITU. All image coding work, including JPEG from SG14, should be moved to SG16. WP3, SIGNAL PROCESSING The Rapporteur for WP3 is S. F. Campos Neto (COMSAT). The agenda and work schedule for WP3/16 are in TD-24R1(3/16). The WP3 meeting report is comprised of TD-48(PLEN), TD- 49(PLEN) and TD-50(PLEN). The questions currently allocated to WP3 (and respective Rapporteurs) are:

Q15 Advanced Video Coding (G. Sullivan, Microsoft, USA) Q19 Extension to existing ITU-T speech coding standards at bit rates below 16 kbit/s (S. Hayashi, NTT, Japan) Q20 Audio and wideband coding in public telecommunication networks (R. D. de Iacovo, CSELT, Italy) Q21 Encoding of speech signals at bit rates around 4 kbit/s (P. Barrett, BT, UK) Q22 Software and hardware tools for signal processing standardization activities (S. F. Campos- Neto, COMSAT, USA)

PROPOSED NEW QUESTION ON VBR VOICE CODING D.229© (Qualcomm) proposes the immediate creation of a new Question to focus on Multimode Variable Bit Rate (VBR) Speech Coding. This new Question would focus on the design of a new low-bit-rate VBR speech coding standard with application in IMT-2000, packetized voice communication networks (such as VoIP), and speech storage and other voice compressing applications. By employing different “rate-mixing” schemes, the VBR speech-coding framework can offer a set of virtual speech codecs or a set of “operating points” on a quality-rate curve. As CDMA systems can vary transmission energy as a function of the coding rate, VBR coding fits CDMA systems very well. An ad hoc group was established under the chairmanship of A. Crossman (PictureTel, USA) to define terms of reference for the work. TD-48(PLEN) Annex B, the draft produced, was reviewed by WP3. A key issue is the design of new coding technology which can best exploit the properties of wireless/IP networks to provide efficient use of bandwidth and minimize the need for transcoding. Traditional coding technologies have not been designed to specifically meet the joint needs of such networks. The group agreed to progress the text for the next SG16 meeting, and to hold an ad hoc meeting in September 1999. Contributions were invited on the current study topics, in particular for the definition of application areas.

OVERVIEW OF EXISTING QUESTIONS FOR THE NEXT STUDY PERIOD WP3 reviewed the text of the current questions allocated to WP3. Preliminary views were as follows: • For Q15, the work should continue for improvements in H.263 (“H.263++”) and for the new H.26L work. Both are works in progress forecast to bear fruit in 2001-2002. • Q19 has been very active in this Study Period with the extension and maintenance of existing recommendations. It was suggested that the work area of this question might be split into a maintenance question (possibly merging with the current Q22), and into a question dedicated to extensions of existing standards (but not limited to bit rates under 16 kbit/s). Possible areas of activity for the latter are VAD/CNI, noise suppression, and frame erasure concealment. • Q20 is about to complete a major milestone with the planned Decision of G.722.1 in Sep. 1999. Work remains for G.WB2, at or around 16 kbit/s, as well as for enhancement of frame erasure performance of G.722 and G.722.1. • Q21 should continue the current work, with views to select a 4 kbit/s codec in 2001-2002. Additionally, bitrate extensions and VAD activities should be pursued once the main rate codec is defined. • Q22 should continue its work on the software tool area, but discontinue activities in the hardware tools area. The latter became less important as host processing laboratory activities became predominantly software-based. It was suggested that the maintenance aspect of the current Q19 might be incorporated into the continuation of Q22. A general question was raised, as to whether frame erasure concealment techniques should deserve a separate question. Finally there was a general remark that all questions should have their background section updated to reflect the need to support packet networks (IP in particular) and wireless (third generation) networks.

LIAISON WP3 considered TD-36(GEN), liaison from Q4/15 on voice over xDSL, and concluded that the systems aspects would be better addressed by Q13/16. The group felt, however, that Q4/15 could benefit from some general information on existing ITU-T voice codecs, as illustrated in Table 1. WP3 highlighted that the effect of delay variation, if it not properly compensated by system, is usually reflected as packet losses, which may adversely affect codec performance.

Recommendation Frame length (Look ahead) One-way delay time G.711 Sample by sample - G.726 Sample by sample - G.727 Sample by sample - G.722* Sample by sample 3 ms G.722.1* 20 ms (20 ms) 60 ms G.723.1 30 ms (7.5 ms) 67.5 ms G.728 0.625 ms 1.5 ms G.729 10 ms (5 ms) 25 ms G.4k 20 ms (15 ms)** 55 ms

* Sampling frequency is 16 kHz ** This value is tentative Table 1. Frame length and one-way delay of existing ITU-T audio codec recommendations. Q1/16 WP2, AUDIOVISUAL/MULTIMEDIA SERVICES

The Rapporteur for Q1/16 is Y. Robin-Champigneul (FT/CNET, France). The status report of Q1/16 is TD-33(WP2/16). (See also the Q16-Q17/16 report, below.) Q1/16’s meetings had to be canceled for lack of participants when it conflicted with meetings of other Questions. However, two joint meetings took place with Q16/16 on Project M.3 (electronic commerce) and with Q9/16 on draft Recommendation F.MCVS. Recommendation F.700, Annexes B.2, Communications tasks descriptions, and C.1, Control and processing elements, was Decided by SG16 as COM 16-R41©. The draft revised text for Recommendation F.700, Framework recommendation for audiovisual/multimedia services, was accepted for Determination with the proposed modifications in TD-24(WP2/16). It contains the changes decided at the last meeting and general updating of the various sections. F.700 was Determined as TD-73(PLEN) and TD-74(PLEN). WD-01(WP2/16) (Q1/16 Rapporteur) and one other working document on electronic commerce were examined; a brief presentation of electronic commerce was drafted (TD-70(WP2/16)). The first draft of the new Recommendation F.MCVS, Multimedia conversational services, was examined and various amendments were made; their main purpose was to include the Total Conversation and the Text Telephony services. The revision of the Q1/16 for the next study period was discussed and some proposals were made; in particular it was suggested to extend the scope of Q1/16 towards the general applications and possibly towards the future architecture for the provision of services, and to add some parts of Q2/16. It had been proposed to close Q1/16 due to the lack of contributions, but some work on the subject is considered to be necessary, in particular taking into account the evolution in the technology and in the environment, and for the maintenance of the existing recommendations. On-going work also includes revision of Recommendation F.702, Multimedia conference services; further work on Recommendation F.MRS, Multimedia Retrieval Services, is dependent upon finding an editor. A joint rapporteurs’ meeting with Q16/16 will be held in September 1999 on Projects M.3 and F.4 (end-to-end interoperability).

Q2/16 WP2, INTERACTIVE MULTIMEDIA INFORMATION RETRIEVAL SERVICES (MIRS) The Q2/16 Rapporteur, M. Blaschitz, could not participate in this SG16 meeting. The group, chaired by K Sambor (Post und Telekom Austria), met to review the contributions received, and to consider the closure of Question 2/16. The meeting report is TD-61(WP2/16).

MULTIMEDIA MIDDLEWARE In the last SG16 Meeting (Sept. 1998), the workplan for the GII project M.4 (Multimedia Middleware) was modified. The modifications are not reflected in TD-10(GEN) (Liaison from SG10 on middleware standardization) and TD-13(GEN) (Liaison to ITU SGs on the GII project). (See also the Q16-17 report, below.) According to the modified workplan, “Phase 2, 2.1: receive information about MM-Middleware solutions fulfilling the requirements,” SG10 has responded to Q2/16’s draft report on “Requirement for multimedia middleware.” However, SG10 stated that the current work on Object Definition Language (ODL) and Distributed Processing Environment (DPE) can satisfy only a limited number of these multimedia middleware requirements. In addition, this group wanted to state that the SG16 draft report covers only a certain part of necessary requirements, because only the following categories of multimedia systems have been considered: • Enhanced Digital Broadcast • Interactive Digital Broadcast • Institutional Multimedia Retrieval Considering that only a certain part of the requirements are given and no new contributions were received, after a short discussion, Q2/16 proposed: • To accept the “Report on Middleware Standardization” of SG10 as the current status and provide additional information to JRG on GII only if substantial new information is received. • To stop the work on M.4 in SG16, because there is not sufficient support for this work in Q2/16. It was agreed that maintenance of the T.170 Series recommendations should be carried out in Q1/16. These proposals were in line with the views of the Rapporteur, who was contacted by telephone during the meeting. Q3/16 WP2, DATA PROTOCOLS FOR MULTIMEDIA CONFERENCING The Rapporteur for the Q3/16 is B. DeGrasse (DataBeam, USA). TD-15(WP2/16) is the report of the Q3/16 Rapporteur’s meeting January, 1999, in Monterey, CA. TD-16(WP2/16) is the status report of Q3/16. TD-57-(WP2/16) is the Q3/16 meeting report.

T.123 REV FOR SECURITY, FOR DECISION TD-35(PLEN) contains changes to the Determined version of T.123 rev (Network specific data protocol stacks for multimedia conferencing) to support the security framework of the IETF Generic Security Service Application Programming Interface (GSS-API, RFC-2078). T.123rev as in COM 16-R41©, with the changes contained in TD-35(PLEN) and TD-5(PLEN) was Decided by SG16.

T.136 (EX T.RDC) AND H.282 (EX V.RDC), FOR DECISION No contributions were received on these draft recommendations. It was noted that TD- 35(PLEN) refers to the companion Remote Device Control draft Recommendation H.283. This document was reviewed and it appeared not to have any impact on T.136 (Remote device control application protocol) or H.282 (Remote device control protocol for multimedia applications). It was agreed that T.136 and H.282 should be submitted for Decision.

T.MRM (MEETING ROOM MANAGEMENT), FOR DETERMINATION TD-19(WP2/16), Draft Rec. T.MRM (Meeting Room Management) was reviewed. This Recommendation provides extensions to the Generic Conference Control (T.124) functionality to

support the specification and management of virtual meeting spaces (meeting rooms) within a conference. This work is expected to find application in the provision of commercial audio- graphics conferencing services. Procedures are defined for arbitrating use of real time media services such as telephony, for advertising those services to participating nodes and for managing and controlling those services once they are activated. These services include the following: • Virtual meeting rooms - creation, entering, leaving, destroying • MRM management roles - convener, chair, secretary, and user defined • MRM framework • Audio management - mixing, channels • Groups • Channels and token T.MRM also defines a Conference Server that takes responsibility for the running of the MRM Conference and a service access channel for communication between the clients and server. T.MRM was Determined by SG16 as TD-7(PLEN).

T120 IMPLEMENTORS GUIDE UPDATE The T120 Implementors Guide was updated and approved by SG16 as TD-6(PLEN). It contains information regarding T.120 (Data protocols for multimedia conferencing), T.124 (GCC) and T.127 (Multipoint binary file transfer protocol) Recommendations as indicated below: • T.120: Table of the MCS static channel assignments for GCC, SI (Still Image), MBFT (Multipoint Binary File Transfer), Application Sharing and Chat Recommendations. • T.124: Comments and ASN.1 modifications for Unicode support of conference names and passwords. • T.127: ASN.1 additions for File-OfferPDU, resolves omissions discovered during interoperability testing.

CURRENT STATUS OF WORK IN PROGRESS

Draft Rec. SG16 May 1999 Next SG16 Feb. 2000 T.123 Rev D T.136 (T.RDC) D H.282 (V.RDC) D T.MRM d D (d = Determine, D = Decide) With the completion of work at this meeting, Q3/16 feels that sufficient specification is now in place to support the present generation of data conferencing. This body of work will support the development and continuing growth of data conferencing in conjunction with out-of-band audio conferencing. The need for this style of conferencing will continue until sufficient bandwidth and quality of service is available to support fully integrated multimedia solutions on IP networks. Q4/16 WP1, MODEMS FOR SWITCHED TELEPHONE NETWORK AND TELEPHONE TYPE LEASED LINES The Rapporteur for Q4/16 is B. Adams (Motorola), previously with Hayes. TD-13(WP1/16) is the agenda. TD-11(WP1/16) is the report of the interim Q4/16 meeting in San Diego, California, USA, December, 1998. TD-6(GEN), a liaison statement from SG4 requesting information on multimedia management activities, was discussed. As Q4/16 has undertaken V.mmo, managed objects for modem diagnostics, it was decided to inform SG4 of this work as it is related to their work. A response liaison was approved (see TD-44(PLEN)). TD-1(WP1/16), a liaison statement from SG8, concerns a recent problem seen with V.21 modulation and network echo cancellers. During the discussion of this issue, it became clear that

this problem could have far-reaching implication for many devices using V.21 without disabling network echo cancellers. This problem appears in part to be caused by a new generation of echo cancellers which notch out one of the frequencies in the high band of V.21 (a modulation used in V.8). Therefore an informative note was approved for inclusion in Recommendation V.8 suggesting use of the phase reversal option of ANSam to disable echo control devices (TD- 39(PLEN)). An outgoing liaison to SG8 informing them of this action (WD 1-05) was approved. TD-44(PLEN) provides the liaison to inform SG15 of the V.21/V.8 problem and requests SG15 look into this phenomenon and report back their findings. Q4/16 also asked that SG15 copy them on any replies made to SG8 regarding this issue.

V.8 ADDENDUM, FOR DECISION COM16 R-33© contains a Determined revision to Table 2/V.8. At the interim Q4/16 meeting, several other changes were approved and are contained in TD-14(WP1/16). The additional changes include removal of the octet allocated to the TIA (USA). A V.91 code point was added. The name of the “V.90 availability” category octet was also changed to “PCM modem availability,” noting that Recommendations V.90 and V.91 now exist and both need to make use of this category. Several other places in the text of V.8 also required changing as a result. It was noted that Recommendation T.35 has been revised requiring a change to the non-standard facilities section of Recommendation V.8, because T.35 country codes may now contain more than one octet. The references section was updated to include Recommendation V.91 and the revision to Recommendation T.35. All the changes to Recommendation V.8, as contained in TD-39(PLEN), Addendum to Recommendation V.8, fwas Decided by SG16.

REVISIONS TO RECOMMENDATION V.8BIS, FOR APPROVAL At the interim Q4/16 meeting, several minor revisions, described below, were approved for V.8bis and are contained in TD-15(WP1/16). • An addition to Table 6-3/V.8bis indicating Recommendation V.91. • Recommendation T.35 has been revised (COM 8-85©) requiring a change to the non-standard facilities section of Recommendation V.8bis because T.35 country codes may now contain more than one octet. • The references section of V.8bis has been updated to reflect these changes as well. All these changes are shown in TD-40(PLEN), Implementors Guide to Recommendation V.8bis.

V.MMO - MODEM MANAGED OBJECTS Due to the changing employment circumstances of the Rapporteur, the stated goal of Determination for V.mmo was not achieved at this meeting of SG16. TD-12(WP1/16) is the V.mmo issues list as amended, reflecting the agreements from the interim Q4/16 meeting. TD-16(WP1/16)© is draft working text for V.mmo. It contains all the gross, mid- level and low-level objects currently under discussion for V.mmo. It also contains many placeholders for definitions, use and other items discussed in this work to date. It is to be used as a starting place for further work on V.mmo. The document is classified only as working text and has not yet been approved. Discussions brought about changes to many of the objects as presented. The editor will prepare a revision to the working text reflecting the results of these discussions. The issues list will also be updated to reflect these changes. The new goal for Determination of V.mmo is set for the February 2000 meeting of SG16.

OTHER HIGHLIGHTS TD-17(WP1/16) is a re-presentation of a Q4/16 document presented in San Diego, December 1998, which proposes additions to V.250 for the use of V.mmo. Since this document addresses additions to Recommendation V.250, this item was forwarded to Q7/16 for further consideration.

As no further contributions concerning the proposed V.8lite project were received, V.8lite was dropped as a work item. Q5/16 WP1, ISDN TERMINAL ADAPTERS, AND INTERWORKING OF DTES ON ISDNS WITH DTES ON OTHER NETWORKS J. Moughton (UK) was the Rapporteur of Q5/16, however, he has changed companies and can no longer participate as Rapporteur. J. Magill (Lucent, UK, WP1/16 chair) chaired the meeting. The meeting report is included in the WP1 report, TD-42(PLEN).

INCOMING LIAISON STATEMENTS TD-2(WP1/16) from SG11 concerns codepoints in Q.931 “Modem type” field of the Bearer capability and Low layer compatibility information elements, and informs SG16 that four requested codepoints (V.90 analog, V.90 digital, V.18 and V.32bis) have been inserted in Q.931, and related clarifications added. No further action is proposed at this time. TD-10(WP1/16) from ISO/IEC JTC1 provides the text for ISO/IEC DTR 10171 “List of Standard Data Link Layer Protocols that Utilize High-Level Data Link Control (HDLC) Classes of Procedures and List of Standardized XIC Format Identifiers and Private Parameter Identification Values.” This is relevant to Q5/16 in that it includes Recommendation V.120. It was noted that the deadline for immediate comment had already passed, so delegates were invited to study the document further and bring any comments to the next meeting of SG16.

REVISIONS TO RECOMMENDATION V.110 TD-18(WP1/16) is a revised version of Recommendation V.110 (Support by an ISDN of DTE with V-series type interfaces). While this version contains a number of corrections and improvements, it was noted that some editorial improvements, etc., identified at the previous meeting had not yet been incorporated. SG16 Determined this version (TD-9(PLEN)©). R-R. Damm (Germany) will complete the editorial amendments to the document before the White Document deadline for the February 2000 meeting of SG16. Q6/16 WP1, DTE-DCE INTERCHANGE CIRCUITS The Q6/16 Rapporteur is R-R Damm (Deutsche Telekom). TD-19(WP1/16) is the agenda. TD- 42(PLEN) includes the meeting report.

REVISION OF RECOMMENDATION V.24, FOR DETERMINATION The proposed considerable revision of Recommendation V.24 (D.237©) was accepted for Determination without the inclusion of statements specifying the sensitivity (state or transition) of control circuits and indication circuits. The new version includes two new interchange circuits, viz. 137 “Transmitted character timing (DTE source)” and 138 “Transmitted character timing (DCE source)”. These two interface circuits were created in order to accommodate, jointly with the already existing (but rarely used) Circuit 131 (received character timing- DCE source) H.320 video codec equipment which need to exchange byte (or octet) timing information and circuit 131 alone is not sufficient. V.24 revised was Determined by SG16 as TD-4(PLEN). D.292© (UK) recommends that progression of V.24 be delayed until there is more certainty that the DTE manufacturers find the changes acceptable. Concern over the inclusion of statements specifying the sensitivity (state or transition) of control circuits and indication circuits was raised. D.299© (France Telecom) recommends that the information in COM 16-R 22, Annex 23© be used as a basis to extend the current V.24 or X.24 to support via X.21 a H.320 codec on ATM networks. With ATM, the synchronization type (async or sync) is not fixed, so a synchronization remote control is needed. TD-3(WP1/16) is a liaison from ISO/IEC JTC1/SC6/WG3 noting that, because there are no DTE manufacturers in SC6/WG3, they cannot comment on the proposed changes to V.24. TD-

44(PLEN) provides a return Liaison Statement describing the Determined version of V.24 from this meeting. The Rapporteur plans to attend the next SG7 meeting (June 7-17, 1999 in Geneva) to discuss the proposed transfer of responsibility for interface-related Recommendations X.20, X.20bis, X.21, X.21bis, X.24 and X.150 from SG7 to SG16. TD-20(WP1/16) is the liaison to SG7 noting this. Q7/16 WP1, DTE-DCE INTERFACE PROTOCOLS The Rapporteur of Q7/16 is F. Lucas (3Com, USA). TD-26(WP1/16) is the agenda. The objectives of this meeting were to review Recommendation V.250, which was for Decision at this meeting, to consider future V.250 commands in support of V.mmo, and to consider future work on V.25i, draft Recommendation for ISDN TA commands.

INCOMING LIAISON TD-22(GEN), a liaison from SG2 Q1/2, asks if a proposed change to Recommendation E.164 would cause changes to Recommendation V.250. Q1/2 is considering a change to E.164 which would increase the County Code format from 3 to 4 digits. Q7/16 reviewed V.250 and concluded that no change would be necessary in V.250 as a result of the proposed change to E.164. TD- 44(PLEN) contains the return liaison to Q1/2 informing them of this.

RECOMMENDATION V.250, FOR DECISION Q7/16 reviewed the draft for the revision of V.250 contained in COM16-R33©. This draft was Determined at the last Study Group 16 meeting. No contributions had been received on the Determined draft. The group agreed that the draft remains ready for Decision. It was Decided by SG16. The group was made aware of a recent change to Recommendation T.35 which could cause a change to the +GCI command. It was agreed that until such time as the revised T.35 is available no change should be made to V.250. This could be included in a future V.250 Implementors Guide.

ADDITIONAL V.250 COMMANDS IN SUPPORT OF V.MMO TD-17(WP1/16) proposes possible V.250 commands to support V.mmo (modem managed objects). The Q4/16 Rapporteur indicated that the structure of V.mmo has changed since this document was created. As a result, the proposed commands would require some modifications when V.mmo is finalized. (See the Q4/16 report above for additional information on V.mmo.) D.269© (USA) recommends that a V.250 command be created which is similar to the #UD command being used by some modems today to retrieve management information. The group considered this work and agreed that until V.mmo has become stable text it was not practical to develop appropriate V.250 commands. It is expected that this can be done via a V.250 Implementors Guide at the February 2000 SG16 meeting.

V.25I ISDN TA COMMANDS J. Moughton, the editor of the new draft Recommendation V.25i, ISDN TA Commands, unfortunately had to resign the position. Q7/16 expressed its appreciation to J. Moughton for his work on this draft Recommendation. Q7/16 considered the future of this work and concluded that, from a practical viewpoint, this Recommendation was no longer needed, so it was agreed that work on V.25i would be terminated.

FUTURE OF Q7/16 The group considered the future of Q7/16 for the next study period. Considering that the workload in Q7/16 is greatly reduced, the group recognized that a consolidation of Questions was a logical step.

Q8/16 WP1, DCE-DCE PROTOCOLS The acting Q8/16 Rapporteur was J. Magill (Lucent), as B. Pechey (UK), the Rapporteur, could not attend. Q8/16 considered one incoming liaison statement, TD-10(WP1/16), from ISO/IEC JTC1, which provides the text for ISO/IEC DTR 10171 “List of Standard Data Link Layer Protocols that Utilize High-Level Data Link Control (HDLC) Classes of Procedures and List of Standardized XIC Format Identifiers and Private Parameter Identification Values.” This is relevant to Q8/16 in that it includes Recommendations V.42 and V.75. It was noted that the deadline for immediate comment had already passed, and so delegates were invited to study the document further and bring any comments to the next meeting of SG16.

DATA COMPRESSION D.251© (Hughes Network Systems) proposes a new data compression algorithm (Lempel-Ziv- Heath, LZH) offering improved data compression performance (10%-35%) over Recommendation V.42bis. Following discussion, the meeting concluded that it was an appropriate time to initiate work on a new data compression Recommendation. A Liaison Statement (contained in TD-44(PLEN)) was generated informing ITU-T SG7, 9 and 15 as well as IEEE, IETF, ITU-R and ETSI of the new work item on data compression and inviting comments on requirements. Preliminary discussions identified the need for the following work items: • Update the “test files” to include typical Internet traffic - for completion at the first interim meeting • Define algorithm selection criteria on issues such as: - Compression ratio (improvement over V.42bis) - Complexity (MIPS & memory) - Code re-use with V.42bis - Improved functionality over V.42bis, e.g. accommodation of other character lengths - Algorithm learning ability - Latency • Liaison with other bodies for the purposes of collecting “requirements” information Additionally the following agreements were reached: • The deadline for submission of candidate algorithms shall be the February 2000 meeting of SG16; • The resulting Recommendation shall define the algorithm mathematically in text and shall not include normative c-code; • Companies proposing algorithms shall make c-code implementations available for evaluation purposes to any interested ITU-T member. Q9/16 WP1, ACCESSIBILITY TO MULTIMEDIA FOR PEOPLE WITH DISABILITIES The 9/16 Rapporteur is G. Hellström, (Ericsson, Sweden). TD-25(WP1/16) is the agenda. TD- 29(GEN) is the Q9/16 status report. In addition to the Q9/16 meeting, the experts of Q9/16 participated in joint sessions with other groups. Question 17/2 liaison TD-9(WP1/16) contains answers to Q9/16’s earlier liaison to Q17/2. It comments on the efforts of Q1/16 and Q9/16 to establish a service description for multimodal conversation - Total Conversation. It notes their concern that terminals for multimodal service may be complicated to operate. Experience from Total Conversation implementations appears to contradict this concern. The liaison also comments that Total Conversation terminals may be expensive. That may be initially true, but should not hold Q9/16 back from completing a service description. Q9/16 will encourage Q1/16 to continue work on conversation services including text, video and voice.

T.140 ADDENDUM, TEXT CONVERSATION PRESENTATION PROTOCOL , FOR DETERMINATION The work with text conversation in IP has given rise to a need to define an indicator for missing text in T.140. This indicator will be used by a receiving channel that discovers that data is missing and cannot be recovered. D.288© (Ericsson) is a proposal for this indicator. A plain Unicode character “Lightning” was selected. D.288© was accepted, with editorial enhancements. The result, proposed as a T.140 Addendum, TD-10(PLEN)rev, was Determined by SG16.

INTERWORKING OF TEXT CONVERSATION IN DIFFERENT NETWORKS Since text conversation is now defined in many networks, the next important topic is to make sure that interworking is achieved between them. Work should go into H.246, IETF MEGACO and H.GCP. Informal contributions have been accepted from MEGACO (see D.286©, Media Gateway Control Protocol Architecture and Requirements). No formal contributions have arrived for this topic in this meeting. The topic is being handled by Q14/16. Text conversation is introduced in the H.GCP structure for gateways in TD-58(WP2/16) (Q14/16 Rapporteur). Media conversion between text and voice is also specified. Continued work in this area from Q9/16 is urgently needed and is included in the workplan.

SIGN LANGUAGE AND LIP READING APPLICATION PROFILE, FOR APPROVAL D.290© is a Supplement to the H.series Recommendations proposed for approval by SG16. It is a common requirement and information document based on the test sequence “Irene” created with Q15/16. It reports that usability is good for sign language and lip reading at 20 frames re second (fps) and possible with constraints at 12 fps. A copyright statement for a digital video sequence to be published together with it is in TD-75(PLEN). SG16 approved D.290©.

V.18 AND H.324 IN MULTI FUNCTION TERMINALS (V.8 AND V.8BIS, WITH Q4/16) There was much discussion in the last SG16 meeting on small deficiencies in V.8bis that makes it hard to design devices with both V.18 and H.324 functionality. Clarifications were expected to this meeting, but no contributions have been received. This should be a joint issue with Q4/16.

MULTI MODAL CONVERSATIONAL SERVICE DEFINITION CONTAINING VIDEO, TEXT AND VOICE, (F.MVCS WITH Q1/16) Q1/16 has now put priority on the work with conversation service descriptions F.MVCS. In a joint meeting, a draft multimedia conversation service description was reviewed. Details for Total Conversation, video requirements for sign language and lip-reading and for text telephony will be proposed by the Q1/16 rapporteur assisted by Q9/16. The goal is Determination in February 2000.

TEXT TELEPHONE ISSUES : V.18 MAINTENANCE D.289© proposes minor modifications to two areas of V.18 Interworking procedures for modems in the text telephone mode: (1) a few corrections of the codes in the conversion table between 5-bit and T.50; and (2) a corrected byte in the initialization of Minitel. An unresolved problem was uncovered with some plain Minitel terminals (the NON text telephone types of Minitel). There is a need to modify the XCI signal of V.18, but there is not yet a firm proposal. The current XCI does not stimulate all Minitels to respond. This has been reported in a problem report. The modifications in D.289© were accepted by the group, and were included in the revised V.18 Implementors Guide, TD-8(PLEN), which was approved by SG16.

PREPARATIONS FOR THE NEXT STUDY PERIOD The Rapporteur announced that he has an agreement to continue this task on behalf of LM Ericsson until Feb. 2000. No commitment for following period can be given at this time. The group agreed that a continuation of actions for accessibility to multimedia for people with disabilities is important and should be proposed to the study group planning.

A supportive letter from Gallaudet University (a university for audio impaired students in USA) commended the work done by SG16 and announced the university’s intent to contribute to the work. Current work items are: 1. Completion of text conversation in H.323 (See Q13/16 report, H.323 Annex G) 2. Completion of text conversation in H.320 (See Q11 report, H.320 Determination) 3. Completion of Sign Language and Lip Reading application Profile document 4. Maintenance on established text conversation modem Recommendation V.18, and related V.8bis, V.8 and V.25x. A revision should be produced soon. 5. Maintenance of text presentation protocol T.140. 6. Conversation service definition containing Video, Text and Voice F.MVCS (with Q1/16). 7. End to end interworking of Total Conversation including Video, Text and Voice (with Q14/16) 8. Any other accessibility issue (e.g., IMT-2000) related to SG16 issues Q10/16 WP1, MODEM TESTING The 10/16 Rapporteur is G. List (Austria). The meeting report is included in TD-42 (PLEN). TD-5(WP1/16) is a liaison statement from SG15 on “network characteristics” for information. Two major points are addressed: CME (circuit multiplication equipment) from Q6/15, and Interworking from Q8/15. (See Q23/16 report, below.) D.271© (TIA PN 3509 draft 8, Test procedure for evaluation of DCE performance), and D.272© (TIA PN 3857 draft 11, Telephone network transmission model for evaluating analog client to digitally connected server [V.90] modem performance), present information on the latest status of the work on these matters in the TIA (USA). After some discussion on how to handle these documents, it was agreed to rework them simply by producing a cover sheet only for the TIA documents or referring to the TIA documents. TIA TR-30.3 members are encouraged to internationalize their standards on modem testing (including D.197© from the September 1998 SG16 meeting which refers to V.56bis) and forward them as contributions to the February 2000 SG16 meeting for possible Determination. As, during the study period, contributions to Q10/16 were received only from the USA, the Chair suggested that Q10/16 does not need to continue into the next study period. Considering the reorganization of WP1, it was suggested that a study item be added to one of the new questions, so that contributions on modem testing can still be addressed. This was agreed. Q11/16 WP2, CIRCUIT SWITCHED NETWORK (CSN) MULTIMEDIA SYSTEMS AND TERMINALS The Rapporteur for Q11/16 is T. Geary (Conexant, USA). TD-14(WP2/16) is the report of the Q11/16 Rapporteur’s meeting, November 1999 in Torino, Italy. TD-27(WP2/16) is the report of the Q11/16 Rapporteur’s meeting, February 1999 in Monterey, CA. TD-26(WP2/16) is the status report of Q11/16. TD-65(WP2/16) is the Q11/16 meeting report. The informal Q11/16 reflector is . Q11/16 met with the following objectives: • Review the proposed changes to draft text for revision of H.320, H.221, H.230, H.242, H.243 and H.224 • Changes to proposed text for H.223 Annex D • Review of proposed changes for addition of MPEG-4 visual standard in H.245v5 • Discussion of inclusion of MPEG-4 System capability in H.324/H.245 • Discussion of inclusion of MPEG-4 Audio capability in H.32x • Discussion of inclusion of non-ITU-T codecs in H.3xx and H.245 • Multilink functionality for H.324 Mobile terminals • Review of proposed revisions to the Implementors Guide for H.324 and H.223 • Discussion on the proposed future activities and SG organization with Q1, Q3, Q12, Q13, Q14 and Q15/16

LIAISONS TD-8(WP2/16) and TD-9(WP2/16) were superseded by TD-10(WP2/16). These liaisons are all from ISO/IEC JTC 1/SC29 and relate to MPEG-4 support in H.324 systems. TD-10(WP2/16) supports the proposed generic format mechanism and associated Annexes. (See Q11-14/16 reports below for additional details.)

H.320 SYSTEMS FOR DECISION H.221rev, Frame Structure H.221 (Frame structure) revision was Decided by SG16 as COM16-83©. H.230rev, Frame sync control and indication H.230 (Frame sync control and indication) revision was presented as COM16-84©. D.219© (PictureTel) provides editorial clarifications needed for H.320-suite adoption of H.263v2 (video codec) enhancements in H.320 Annex A (Optional enhanced video algorithms for H.320 systems), H.230, and H.242 (audiovisual communications establishment). There is a problem with the H.243 mechanism for broadcasting a still image (H.261 Annex D). There is no reliable means for a terminal to know when its video signal is being broadcast to all remote sites, so there is a risk that transmission may begin before all sites are ready to receive the still image. The MIV indication is only an “on-air” signal indication that one or more sites are ready to receive the still image. D.220© (USA) proposes three new H.230 C&I BAS codes: MVA (multipoint visualization achieved) and MVR (multipoint visualization refused/revoked), and an associated MVC (multipoint visualization capability) to resolve the problem. TD-36(WP2/16) (Q14/16 Rapporteur) integrates the proposed solution into the documents. The group accepted the content of D.219© and D.220© relative to H.230 (taking note of the effect on H.243). The agreed text to support the additional changes to H.230 are in TD-18(PLEN). SG16 Decided the H.320 revision as COM16-84© plus TD-18(PLEN). H.242rev, 2M kbit Digital Channel for AV H.242 revision, System for establishing communication between audiovisual terminals using digital channels up to 2M kbit/s, was presented as COM16-85© and D.219©. Q11/16 accepted the content of D.219© relative to H.242. The agreed text to support this change is in TD- 19(PLEN). SG16 Decided the H.242 revision as COM16-85© plus TD-19(PLEN). H.320rev, T.140 Text Conversation Transport In H.320 multimedia systems for ISDN, a text conversation transport for T.140 is in preparation in the form of a new Client ID in H.224. H.320 revision was presented as COM16-86©, D.219© (H.320 suite clarifications, PictureTel) and TD-32(GEN). TD-32(GEN) defines what is needed for addition of T.140 to H.320 Systems to support Text Conversation. The group noted that COM16-86© already contains the changes necessary to support the proposal of TD-32(GEN). The group also accepted the content of D.219© relative to H.320; the agreed text to support this change is in TD-17(PLEN). SG16 Decided H.320 revision as COM16-86© plus TD-17(PLEN).

H.324 SYSTEMS FOR DECISION AND APPROVAL H.223 Annex D H.223 Annex D (Optional multiplexing protocol for low bit rate mobile multimedia communication over highly error-prone channels) was presented as COM16-81© and D.308© (Toshiba), Proposed Editorial Changes for H.223 Annex D. SG16 approved H.223 Annex D as presented. H.324 Implementors Guide D.276© is a small revision to the H.324 Implementors Guide from the editor M. Luomi (Finland). The mobile interoperability test group identified an inconsistency in H.324. Q11/16 agreed to a note at the end of H.324 Annex C that after changing from level 0 to some higher levels MUX- PDU octet alignment shall be preserved. SG16 approved the revised H.324 Implementors Guide as TD-16(PLEN).

H.223 Implementors Guide TD-46(WP2/16) is the incoming draft H.223 Implementors Guide. It provides a compilation of reported defects with the 1997-2000 editions of H.223. Sg16 approved the H.223 Implementors Guide as TD-15(PLEN).

H.320 SYSTEMS (H.224 AND H.243), FOR DETERMINATION TD-32(GEN) proposes revision of H.224 (A real time control protocol for simplex applications using the H.221 LSD/HSD/MLP channels) in support of Text Conversation in H.320 terminals. It was agreed in the joint Q/11-14 meeting. SG16 Determined the proposed draft revision of H.224 as presented in TD-11(PLEN). (See Q14/16, H.224, below.) SG16 Determined the proposed draft revision of H.243 presented in TD-20(PLEN). (See the H.320 Systems report, above.)

H.324 ANNEX F, FOR DETERMINATION D.267© (Robert Bosch GmbH) provides corrections to transport of MPEG-4 systems content over H.324. TD-10(WP2/16), MPEG-4 Audio capabilities and MPEG-4 System model in H.324 (liaison from SC 29/WG 11), proposes addition of an MPEG-4 Audio Capability Definition Annex to H.245v6 for the MPEG-4 Audio capabilities and for transport of MPEG-4 Systems along with relevant codepoints, as well as the addition of an Annex and informative Appendix to H.245v6. Q11/16 felt that reference to “working titles” such as “MPEG-4 Audio” were not appropriate for use in the ITU Recommendations and agreed that the appropriate ISO/IEC references should be utilized. Q11/16 supported the concept of addition of MPEG-4 Systems (ISO/IEC 14496-1) in H.324 as proposed in TD-10(WP2/16) and modified by D.267©. However, it was noted that further work is needed to fully define the proposed text necessary for an Annex to H.324. An editor, J. Vollmer (Germany), generated the necessary text, considering the use of formal ISO/IEC specification numbering and the work to add of the generic capabilities. The group reviewed proposed draft text for the new Annex to H.324 and, with minor revision regarding requirements for support of mandatory codecs in H.324. SG16 Determined the revised text in TD-13(PLEN) as Annex F to H.324. It was noted that an informative Appendix concerning this subject will also be prepared for approval concurrent with the final Decision of this Annex.

H.245V 6, FOR DETERMINATION (Q14/16) Q11/16 reviewed the proposed draft text to be added to H.245v6 in support of MPEG-4 Audio (ISO/IEC 14496-3). The group noted that the final text for inclusion in H.245v6 should utilize generic capabilities; that text is included in TD-22(PLEN). It was given to Q14/16 to include in H.245v6 for Determination. Q11/16 reviewed the proposed draft text to be added to H.245v6 in support of MPEG-4 Systems. The group noted that the final text for inclusion in H.245v6 should only make reference to generic capabilities and the sections requesting the addition of codepoints directly in H.245 should be deleted. With this change and alignment of syntax with the new generic capability sample defined in H.245v5, the group approved TD-14(PLEN), and requested Q14/16 to include it in the proposed draft text for H.245v6 for Determination. (See Q14/16 H.245v6 report, below.) H.320 D.299© (France Telecom) proposes an amendment to V.24 or X.24 to support Network timing (for H.320). In the Joint WP meeting, it was agreed that Q6/16 will take it under study. TD- 38(GEN) is a liaison to ISO/IEC asking for cooperation. It was noted that the final state and timing requirements will have to be made in the terminal Recommendation; input for an appropriate Annex to H.320 is solicited. H.324 D.263©, Synchronization of Multiple Logical Channels in H.324 (Siemens), was reviewed. New coding algorithms (e.g., H.263v2 Annex O) may specify layered coding schemes, however H.223

does not guarantee synchronized delivery to support such layered coding schemes. Q11/16 agreed to take this item under study for possible addition to future revisions of H.324 and H.245.

OUTGOING LIAISONS TD-62(WP2/16) is a liaison to ISO/IEC noting that Q11/16 and Q14/16 have supported the proposals from ISO/IEC JTC1/SC29/WG11 on the MPEG-4 inclusion in H.324 and H.245.

Q11/16 WORKPLAN Table 2 present the Q11/16 workplan.

Item Editor Schedule Status Comment H.245v6 M. Nilsson, UK 2/00 For Decision Support to Q14/16 H.243 (revision) P. Luthi, USA 2/00 For Decision Support to Q14/16 H.224 (revision) M. Nasiri, USA 2/00 For Decision H.324 Annex J. Vollmer, Germany 2/00 For Decision MPEG-4 System H.mml G. Roth, Sweden 11/00 In work see Q13, H.323 mobile annex future work H.32L Not yet assigned 2003 Under study Joint with Q11, Q12, Q13, Q14, JQG1/11, ITU-R TG8/1

Table 2. Q11/16 Workplan as of May 1999.

WORK ITEMS FOR THE NEXT STUDY PERIOD The following items of work are envisioned going forward within Q11/16: 1) Work on terminals to support IMT-2000 network (“Media 2000”) as it relates to the network architecture of 3G wireless and GII in general 2) Support the work on higher quality lower delay audio and video codecs for multimedia applications Q12/16 WP2, B-ISDN MULTIMEDIA SYSTEMS AND TERMINALS The Rapporteur for Q12/16 is S. Okubo (Telecommunications Advancement Organization, Japan). TD-32(WP2/16) is the report of the Q12-14/16 interim Rapporteur’s meetings (November 1999 in Torino, Italy, and February 1999 in Monterey, CA). TD-31(WP2/16) is the status report of Q12/16. The Q12/16 meeting report is TD-59(WP2/16). Q12/16 met with the following objectives: • Decision of H.222.0 | ISO/IEC 13818-1 Amendment 5 and Amendment 6 • Determination of H.222.0 | ISO/IEC 13818-1 Amendment 7 • Discussion on other technical items • Discussion on future direction including the questions for the next study period

H.222.0 | ISO/IEC 13818-1 AMENDMENT 5, FOR DECISION No comments were received on COM 16-76©, Information technology - generic coding of moving pictures and associated audio information: systems. This amendment defines a set of syntax and semantics extensions to cover the recently standardized high quality audio coding ISO/IEC 13818-7 (AAC - Advanced Audio Coding). After Amendment 5 to ITU-T Recommendation H.222.0 | ISO/IEC 13818-5 had been approved in September 1998, an error was found in the technical specification at the October 1998 meeting of ISO/IEC JTC 1/SC 29/WG 11. Accordingly the publication was suspended to avoid confusion. This contribution proposes that the error be corrected and the text contained here be approved and published instead. SG16 Decided H.222.0 | ISO/IEC 13818-1 Amendment 5 as COM 16-76©.

H.222.0 | ISO/IEC 13818-1 AMENDMENT 6, FOR DECISION TD-28(WP2/16) (Q12/16 Rapporteur) proposes modifications and editorial corrections to COM 16-77©, H.222.0 | ISO/IEC 13818-1 Amendment 6 based on the agreements from the March 1999 ISO/IEC JTC1/SC29/WG11 meeting. This amendment adds the splice parameters for the 4:2:2 profile@high level and the buffer model for AAC (advanced audio coding) audio. SG16 Decided H.222.0 | ISO/IEC 13818-1 Amendment 6 as COM 16-77© plus TD-28(PLEN).

H.222.0 | ISO/IEC 13818-1 AMENDMENT 7, FOR DETERMINATION TD-29(WP2/16) (Q12/16 Rapporteur) proposes a new Amendment 7 to H.222.0 | ISO/IEC 13818-1, Information technology - generic coding of moving pictures and associated audio information: video, to carry ISO/IEC 14496 (MPEG-4) content over H.222.0 | ISO/IEC 13818-1 (MPEG-2) System streams. Q12/16 confirmed that there is no direct impact on H.310 at this moment. If any market need is identified, H.310 will be amended with a description of how to use MPEG-4, referring to this Amendment 7 to H.222.0. It was pointed out that addition of H.245 codepoints for MPEG-4 coding is on-going and H.310 can use them. With the clarification above, SG16 Determined H.222.0 | ISO/IEC 13818-1 Amendment 7 as TD-23(PLEN).

TECHNICAL ISSUES Issue of Integrated Edition For Common Text Recommendations TD-28(GEN), Integrated edition of ITU-T Recommendation H.222.0 | ISO/IEC 13818-1 (Amendments 1-7 and Corr. 1) and ITU-T Recommendation H.262 | ISO/IEC 13818-2 (amendments 1-6 and Corr. 1 and 2) from the Q12/16 and Q15/16 Rapporteurs, was presented at the joint WP meeting. It was confirmed that there is no need for additional procedures for integrating already approved texts with minor editorial amendments. TD-38(GEN) is the liaison statement to MPEG providing the approval of SG16 to publish the joint text Recommendations. (See also Q15/16 report, below, re: H.262.) H.321 Implementors Guide TD-13(WP2/16), DSS2 protocol provision of adaptive timing recovery used for transmitting clock (Q20/SG11), had been discussed at the Monterey Rapporteurs meeting (February, 1999, CSR Vol. 10.3). TD-30(WP2/16) provides draft text for the H.321 Implementors Guide. Q12/16 agreed to the text, which should be approved at the next SG16 meeting after Decision of the Q.2931 revision by SG11 (expected December 1999). End Station Identifiers of H.310 and H.321 TD-12(WP2/16) (SG11) indirectly indicates that the definition of end station identifier in DSS2 information elements had been finalized in Q.2941.2. SG11 provisionally agreed on the assignment of codepoints within the GIT (generic identifier transport) information element in order to transfer the 16 bit port number to identify an RTP stream. In response to this, Q12/16 should produce texts for the H.310 and H.321 Implementors Guides. This will be worked out before the next meeting with confirmation of the Q.2941.2 status.

LIAISONS TD-16(GEN) (SG13) is the multimedia coordination “Status of Activities.” Q12/16 agreed that H.310, H.321, and H.247 should be included in the Q12/16 entry of the “status of activities” table.

WORK PLAN Table 3 presents the Q12/16 Workplan. Q12/16 future work includes: • Incremental improvements to and maintenance of existing Recommendations; H.310, H.321, H.247, H.222.0, H.222.1 • High quality audiovisual services over the packet based (IP) network jointly with Q13/16

Study subject Editor Det. Dec. H.222.0 | ISO/IEC 13818-1 Amendment 7 S. Okubo (TAO, Japan) 05/99 02/00 H.321 v2 Implementors Guide S. Okubo (TAO, Japan) - 02/00 H.310 v2 Implementors Guide K. Sakai (Fujitsu, Japan) - 02/00 Security for broadband systems {solicited} TBD TBD VBR aspects M. Nilsson (BT, UK) TBD TBD H.246 Annex (Broadband system {solicited} TBD TBD interworking) High quality video transmission over IP {solicited} TBD TBD including MPEG-2 packetization (with Q13/16) Table 3. Q12/16 Workplan as of May 1999. Q13/16 WP2, PACKET SWITCHED MULTIMEDIA SYSTEMS AND TERMINALS The Q13/16 Rapporteur is D. Skran (Ascend). TD-32(WP2/16) is the report of the Q12-14/16 interim Rapporteur’s meetings (November 1999 in Torino, Italy, and February 1999 in Monterey, CA). TD-44(WP2/16) is the status report of Q13/16. TD-23(WP2/16) is the agenda for this meeting. TD-66(WP2/16) is the Q13/16 meeting report.

LIAISONS TD-4(WP2/16), Support of IN services for H.323 and other IP Network-based terminals (SG11), presents the work that SG11 Q5 has done on the requirements for functional architecture (using PINT servers) in support of IP networks. Q13/16 produced a draft liaison (WD2-06) which notes the differences between the SG16 and SG11 (TIPHON-based) architectures and proposes a combined architecture. Due to the complex nature of the issues involved, it was agreed to defer a response until the next rapporteurs meeting. TD-5(GEN) notes that Q9/11 is beginning work on a new recommendation (Q.ELINT) defining echo control logic for voice calls via an internet. Because of the time varying nature of an internet (IP network), network-based echo cancellers will not work and echoes must be canceled locally. Q.ELINT is intended to be used in harmony with Q.115, Logic for the control of echo control devices in telephone networks. The Rapporteur is L. Forni (Lucent Technologies). Q13/16 prepared a return liaison (WD2-17) noting the work being done in SG16 on echo control. TD-22(GEN), Study of the expansion of the Rec. E.164 country code format to 4 digits (SG2/WP1/Q1), anticipates exhaustion of 3 digit country codes in 10-15 years. Q13/16 noted that this would affect H.225.0v3/H.323v3; Q13/16 must examine the support for 4 digit country codes in the H-32x related documents. The editor for H.323 reported that H.225.0 and H.245 will not be affected by this change. Other H-Series documents inherit definitions from H.225.0. Currently, all E.164 numbers are contained in an IA5String that is of size 1..128. TD-23(GEN), Liaison relating to IMT-2000 Numbering (Chair WP1/2), will be considered as part of on-going work. TD-36(GEN) is a liaison on Voice over xDSL from Q4/15. The Q13/16 rapporteur will write a liaison with information related to topics such as data rate, number of channels of voice, etc.; it also will address H.323 Annex C if ATM is used over xDSL. Lifeline service is not critical as it is assumed to be provided at a lower lever. The number of channels should be a user-level trade-off. A major decision is “Looks like a LAN” vs. “Looks like ATM” vs. “Looks like ISDN.” It was noted that PPP over ATM obscures the ATM features. SG15 maintains a series of recommendations on voice quality, and ETSI TIPHON does also at the applications layer (TR 101 329). P. Barrett of WP3 is also preparing a liaison. This liaison appears with the meeting report (TD-66(WP2/16)).

H.323 IMPLEMENTORS GUIDE (See also Q14/16 report, Implementers Guide, below.) D.236©, Proposed Clarification of Alternate Gatekeeper Mechanism (Databeam/IBM), provides proposals for both the Implementors Guide and for H.323/H.225.0v3 to clarify the usage of the “alternative gatekeeper” mechanism. The proposals were handled as follows: • Rejects without Redirects: Accepted. • Handling multiple lists of alternate gatekeepers: Accepted. • Registering with an alternate gatekeeper: This was not accepted although it was agreed to continue to work toward clarifying this point, but perhaps with an alternative mechanism. • Registration with a gatekeeper that is not permanent: Also not accepted; further contributions are solicited. D.240©, Usage of T.35 codes for non-standard facilities in protocols of H-Series Recommendations (FRG), provides information about work in SG8. It was noted that the ITU-T would not become involved in how local authorities allocate manufacturer codes. It was decided to try to use the same codes in both the T and H series. This issue will be considered as part of H.323v3/H.225.0v3. Reports from other countries on how these matters are handled are requested. The editors will be looking at this issue; this may affect the Implementors Guide and/or H.246 (H.323 to H.320). Q13/16’s plan is to align, but based on contributions to the August Rapporteurs meeting, as this issue is not critical to the Determination of H.323. The editor for H.323 reported that currently the ASN.1 has one byte for the country code and one byte that is a “T.35 extension assigned nationally.” The H.323 editor believes that this is not compliant with the new T.35 and that changes are necessary in the next revision of H.225 and H.245 to correct this problem. D.280©, Open Logical Channel Signaling (Mitel, Canada), outlines a means by which H.245 signaling can be used for early establishment of media channels and so obviates the need to expand traditional Fast Connect into a general purpose mechanism. The introduction of the Fast Connect procedure into H.323v2 provided a means of allowing media channel establishment at the earliest point in a call. More recent developments have suggested expanding the scope of this procedure to be allowed at any point in a call, thus evolving into a mechanism that fully parallels H.245 Open Logical Channel (OLC) signaling. The advantage to such an evolution is that it permits endpoints to dispense with H.245 signaling, both via tunneling and via separate connection. A disadvantage is that endpoints implementing the Fast Connect procedures must normally also support H.245 signaling for a variety of reasons, in which case they must support two different semantic interpretations of the OLC structures depending on the means of transport. This is an undesirable burden on endpoints which presents few benefits. This concept was supported: Section 2 (Logical channel alternatives): Will become an informational appendix of H.323v3. Section 3 (Open logical channel signaling procedures): This was not accepted. Section 4 (Transport addresses): The change to H.323 section 8.3 was accepted, with a small modification, as was the change to H.245v3 section 7.3.2. It was also agreed to accept the change to H.245v3 section 7.3.1. TD-54(WP2/16) (corrected version in WD2-08) is the Implementors Guide for the ITU-T H.323, H.225.0, H.245, H.246, H.235, and H.450 Series Recommendations - Packet-Based Communications Systems. D.307©, Exceptional Procedure for H.450.2 Implementers Guide (Canada(Mitel), was accepted with “should” changed to “shall” in Section 6. This enables a H.450.2 Call Transfer without Consultation even if the transferred-to endpoint is not capable of H.450.2. It was added to the Implementors Guide which appears in TD-37(PLEN). A number of small changes were made. (See also Q13 H.225v3, below.) With these changes the H.323, H.225.0, H.245, H.246, H.235, and H.450 Implementors Guide was approved by SG16 as TD-37(PLEN) plus TD-56(PLEN).

H.323 ANNEX E, FRAMEWORK AND WIRE-PROTOCOL FOR MULTIPLEXED CALL SIGNALING TRANSPORT, FOR DECISION H.323 Annex E, Framework and wire-protocol for multiplexed call signaling transport, was Decided by SG16 as COM16-74©, TD-33(PLEN) and TD-53(PLEN). D.252© (Motorola, Cisco) discusses potential design flaws with H.323 Annex E; TD-20(WP2/16), Comments on D.252 (Editor), is a rebuttal noting the need for predictive provisioning of call- signaling performance (not possible using TCP) and the real world experience behind Annex E (based on VocalTec iPhone Protocol). These were not presented; but results from them were reflected in the discussion. TD-53(WP2/16), Draft Annex E changes, was presented by the editor G. Kimchi (VocalTec). It was agreed to remove multi-homing and the INFO message and to consider adding them in a future version of Annex E. Various other editorial changes were made. WD2-10 is a revision of TD-53(WP2/16). It was mentioned that E.2.2 must reflect the agreed changes. TD-33(PLEN) contains nearly final changes against COM16-74©. It was noted that port 2517 was named “signaling transport” and this should be changed by the editor to “h323annexE.” This was agreed. It was noted that we should investigate possible ITU- T ownership of these ports. It was noted that this port and all the other H.323 ports are technically not “well known ports” but are actually “registered ports.” This will be investigated by the editors. RFC 1700 is the relevant reference.

H.323 ANNEX F, SIMPLE ENDPOINT TYPE, FOR DECISION SG16 Decided H.323 Annex F as COM16-73© plus TD-52(PLEN). The editorial and minor technical changes proposed in D.285©, Updated Draft Recommendation H.323 Annex F (Israel), resulted in the creation of WD2-14 and WD2-26. They were accepted. D.291© (Ericsson) also presents editorial modifications to H.323 Annex F. It was accepted.

H.225.0 ANNEX G, INTER-DOMAIN COMMUNICATIONS, FOR DECISION H.225.0 Annex G was provisionally Decided by SG16 as COM16-75©, TD-32(PLEN) and TD- 53(PLEN). The USA head of delegation (G. Fereno) invoked the 4 week rule based on the number of changes since the white document was issued. Technical editor’s note: Everyone seems to be confident that Annex G will pass after the 4 week period. D.273©, Modifications to H.225.0 Annex G (VocalTec, Israel), proposes a set of changes to Annex G relating to placing calls between administrative domains: • Allowing a domain to verify that a call derives from a trusted domain • Usage reporting • Security matters These changes were accepted with minor editorial changes. Some confusion exists about how the OID is to be defined for Annex G. A section on H.323 related OIDs was added to the Implementors Guide. It was agreed to change the name of the state “call not commenced” to “pre-connect.” TD-40(WP2/16) (Rapporteur) provides editorial changes to H.225.0 Annex G. The changes to section 1.8.2 relating to retransmission times were not accepted; it was agreed that a more flexible formula that takes into account network delay is desired. Certain items in the Appendix will be moved to the main text (well known port, TPKT) and references to RFCs left in the appendix. With these exceptions, the changes in TD-40(WP2/16) were accepted. A full set of changes against COM16-75© appears as TD-32(PLEN).

H.450.4, CALL HOLD, FOR DECISION There were no submissions against COM 16-87©, Call Hold Supplementary Service for H.323. SG16 Decided H.450.4.

H.450.5, CALL PARK AND PICKUP, FOR DECISION There were no submissions against COM 16-88©, Call Park and Call Pickup Supplementary Services for H.323. SG16 Decided H.450.5.

H.450.6, CALL WAITING, FOR DECISION There were no submissions against COM 16-89©, Call Waiting Supplementary Service for H.323. SG16 Decided H.450.6.

H.450.7, MESSAGE WAITING, FOR DECISION There were no submissions against COM 16-90©, Message Waiting Indication Supplementary Service for H.323. SG16 Decided H.450.7.

H.225.0V 3, FOR DETERMINATION It was agreed to put H.225.0v3 forward for Determination. TD-50(WP2/16) is the incoming draft of H.225.0v3, which is comprised of changes to Decided draft Recommendation H.225.0v2. Final Text appears as TD-68(PLEN)©. It was also agreed to request the permission of SG16 to Determine H.225.0v4 in 02/00 due to the increased pace of standardization and strong market requests for additional work. D.264©, Q.931 Presentation and Screening Indicators in H.225.0 (Cisco), was superseded by APC-1527 (Caller ID Support, Lucent). This was agreed to be added to the Implementors Guide at Monterey (February 1999). This material was approved as part of the Implementors Guide at this meeting.

H.323V 3, PACKET-BASED MULTIMEDIA COMMUNICATION SYSTEMS H.323v3, Packet-Based Multimedia Communication Systems, was Determined by SG16 as TD- 57(PLEN)©. H.323v3 Annex C, V2/ATM/MPEG2 Related Matters D.244© (Hitachi) is a proposal for new standardization of H.262 layered video stream transmission with the Internet Protocol. It was agreed that the kind of system described, H.262/H.222 over IP and satellite/terrestrial networks, would be useful to standardize. It was agreed to pursue the following items: • Layered H.262 packetization • Changes to H.323 to support this layering • Possible application related changes D.305© (Nortel [ATM Forum]) presents the final version of AF-SAA-0124.000, “Gateway for H.323 Media Transport Over ATM.” The H.323 terminal can be on a variety of network technologies, including non-native ATM IP-based (Ethernet, etc.) and native ATM. This document is in final ballot in the ATM Forum. It will be final by the February 2000 meeting, and can be referred to in H.323v3, H.246, etc. These references will be added by the respective editors to both H.323v3 (for Determination) and to the Implementors Guide for H.246. H.323 Annex D, Real Time Facsimile over H.323 D.255©, A method for switching to Fax/Modem over Existing Voice Channels (Ascend), is a proposed update to H.323/Annex D for describing the use of H.245 RequestMode messages to indicate and negotiate T.38 for real-time facsimile communications over IP networks using existing H.225 voice channels between H.323 gateways. A suggestion was made that this may be a candidate for using the H.245 generic capability set. Also, the ASN.1 for UDP/TCP is incorrect. Concern was raised about how clean the switch was on the RTP level. Concern was

expressed that request mode needed to be combined with replace mode to create a clean switch. It was noted that a code would be needed to identify T.38 in RTP, or some examination of the data stream. This will be further developed for possible inclusion in H.323v3. TD-1(WP2/16), Recommendation T.38 Indications in Recommendation H.245 (SG8), notes errors in the ASN.1 encoding in H.245. It was agreed (jointly with Q14/16) that: 1) A true error has occurred. 2) The T.38 facsimile profile in H.245 should correspond to the actual profile as specified in T.38 Annex B. 3) Q13/16 will investigate whether this raises any interoperability issues. TD-3(WP2/16), Draft T.38 Appendix II: Call Sequence Examples using T.38 Annex B (SG8), requests Q13/16’s review of some interoperability message sequences. WD2-19, Q13/16 liaison to SG8, identifies four corrections; WD2-18, T.38 Appendix II with change marks, attached to it. TD-6(WP2/16), Additional Questions Regarding T.38 Annex B (SG8), contains the final T.38 Annex B, and a SG8 liaison related to it. SG8 raises concerns about the difficulty firewalls will impose on T.38 Annex B devices, particularly Internet access facsimile devices, and proposes some solutions using a “well known port.” H.323 & QoS Related D.222©, An enhancement mechanism for differentiation of H.323 Quality-of-Services (QoS) (AT&T), describes a general signaling scheme without reference to implementation of QoS signaling. It was noted that the ASN.1 redefines “Bandwidth” which already exists. It was agreed that many errors exist in the ASN.1 that need to be fixed. Support for including this as part of the Determination was weak. D.300©, A Framework for QoS for H.323 (VocalTec, Israel), compares Intserv and Diffserv approaches, and recommends Diffserv. A general framework for applying this to H.323 is presented. It was agreed that this was a good approach to H.323 QoS, and would be the basis of on-going work. The relationship of this work to H.323 Annex C (ATM) must be clarified. D.230©, Issues relating to Quality of Service for Internet Telephony and suggested approaches (India), is a tutorial paper reviewing the general problem of QoS for VoIP, noting the two emerging different IP telephony deployment models. However, no specific proposal related to H.323 is made: • Entente Model, characterized by the continued existence of the PSTN as a core network to which the IP network provides access • Integrated Model, characterized by the exclusive uses of IP as the transport and switching technology Both D.300© and D.222© had support, and appear to have merits, but there was not definitive conclusion at this meeting. Both will be considered further at future meetings. H.323v3 Considerations It was agreed to put H.323v3 forward for Determination. Final text appears as TD-57(PLEN)©. It was also agreed to request the permission of SG16 to Determine H.323v4 in 02/00 due to the increased pace of standardization and strong market requests for additional work. D.225©, Framework for Reliable H.323 Gatekeeper Architecture (AT&T, USA), provides a good tutorial on methods of backing up gatekeepers in different ways, but it was agreed that it is outside of the scope of standardization at this time. It was agreed that standardization would focus on the relationship of endpoints to alternate GKs, not on the relationship between a GK and its backup. Proposals on the following topics are solicited for the August rapporteurs meeting: • The assumptions held by an endpoint about the relationship between a GK and its backup • How this might affect switching in the protocol

D.226©, Enhancement of ARQ/ACF/ARJ, Setup, RAI, and RAC Messages (AT&T), calls for enhancing the reporting of capacity-related information from GWs to GKs. It was noted that sections 1 through 4 are related to D.262©, and sections 5 and 6 to D.258©. Sections 1 through 4 propose that the initial dialed number in two stage dialing be passed to the GK. Discussion on Sections 1 through 4 was inconclusive. Sections 5 and 6 propose that additional capacity information be passed to the GK. It was agreed that some enhancement to GW capacity reporting would be added to H.323v3/H.225.0v3. (See also the discussion on D.258©, below.) D.253© (Ascend, USA) calls for the study of the usage of CPL (Call Processing Language, IETF IPTEL) in H.323. It was agreed that the work as it relates to browsers is mainly outside of Q13/16’s scope, but that much work is needed to make CPL supportive of H.323. Consideration of the direct vs. GK-routed model is needed, and perhaps CPL scripts should be supported in the endpoints as part of the direct call model. The need to consider other CPL-like protocols such as WAP (Wireless Access Protocol) was mentioned, with the suggestion that a generic mechanism is important. Concern was raised that any CPL-like situation would have limited extensibility and might limit service extensibility. The next rapporteurs meeting will review CPL related to H.323. WD2-12 is a more refined proposal, from the Q13/16 Rapporteur, for a “Generic Service Transport Channel” that would transport CPL as well as WAP in a general fashion. This will be developed further with two goals: 1, A possible appendix or annex to H.323, and 2, Small ASN.1 changes to H.323v3 to support this channel. D.258©, Gateway call capacity as viewed by the Gatekeeper (Ascend), presents another method of allowing the GK to find out more about call capacity in a GW. A suggestion was made to report percent (%) resource remaining rather than an absolute number as being more multimedia friendly. It was noted that BRQ/DRQ go both ways, and this must be dealt with. A suggestion was made to add capacity to SETUP for the pre-granted ARQ case. It must always be possible to offer a call to seek the edge of full capacity. It was agreed to add call capacity with an extension for different numbers of calls at different rates. It was agreed to add a new method such as one of those mentioned here: • Add percent capacity remaining to BRQ/DRQ. • Report an array of capacity levels for each media type. It was agreed to add some method of reporting more detail on GW call capacity to the GK to H.323v3. D.259©, Tone and Announcement Control via RAS (Ascend), proposes a method of controlling announcements via RAS. Comments included: • G.729 should not be required for compressed voice in RAS messages. • AnnIdentifier should have a repeat and an off time. • This proposal is complementary to the usage of a large announcement server distinct from the GW. • The study should cover a separate announcement server. • Transport via RAS was not a good idea due to message size limits. • A URL should allow the GW to talk to a variety of servers to get announcements. • The interaction between the GW/GK should be extended to include more exchanges. • Video announcements and conversational text announcements should be included. • A need exists to apply announcement during a call at any time, and to control their direction. The agreements of the meeting were:

• Compressed voice should not be passed via RAS. • It is important for the GK to control the playing of announcement and related matters, but in a higher level fashion than in this proposal. • Provision should be made for at least two architectures: - Announcements in the GW - Announcements in a separate announcement server - Consideration should be given to announcements in terminals Overall, it was agreed that the control of announcements is a valid work item for H.323v3. Consideration should also be given to coordination with H.GCP. D.260©, Gatekeeper-Based Telephone Number Translations for PSTN Gateways (Ascend), proposes a solution to some of the ramifications of widely differing dialing plans. For example, a telephone number needed to route a call internationally would not necessarily be dialable at the far end PSTN gateway. It was noted that GWs sometimes have different lines so that some of this kind of processing must be done in the ingress GW, i.e., differently for each line. It was suggested that GWs should be sending partyNumbers to GKs, not false E.164 numbers. It was noted that the ACF and ARQ were switched in section 8.1.8.1. This proposal mixes dialing plan and numbering plan. It was agreed that GKs need to be involved in this process. It was agreed that the GK should convert a dialed number to a party number (E.164 number or private number). There was a proposal to change the names of the ASN.1 to be more accurate in usage of the terms party number, dialed number, and E.164 number. It was agreed by the meeting that the general direction of D.260© is not correct, and instead points 1-5 below should be followed: 1) The implementors guide for H.225.0 needs to be clarified with regard to the naming issues mentioned above. 2) It needs to be clearly defined that the endpoint (GW, Terminal) shall accept numbers being passed to it in an ACF. 3) Additional work is needed to define the cases where the GW must transform the number by itself. 4) This work should be done as part of H.323v3. 5) Network transport should be party number, and the ingress/egress number transformation may be shared between GW & GK. D.261©, RTCP (IETF real time control protocol) Reporting to the GK (Ascend), suggests that RTCP information gathered by the H.323 endpoint should be communicated to the Gatekeeper for use in guiding future call routing decisions. It was agreed that it was important to pursue this work, with a goal of possible inclusion in H.323v3. The main purpose of D.262©, Circuit Identification Codes in H.323 Networks (Ascend), is to allow CIC information to be provided to a GK so that billing records could contain this sort of information. It was suggested that circuitID should be optional in all cases. An indication of which country the GW is in should be added to allow the CIC to be interpreted, probably during registration. A suggestion was made that point codes should also be reported for SS7 connected GWs, or a pseudo-point code reported where the GWs are not SS7 terminated, resulting in a CHOICE in the ASN.1. Consideration should also be given to ATM VPI/VCI. It should be considered how this would be used with pre-granted ARQs, probably implying that the information must be in SETUPs. It was noted that the assigning of a CIC defeats ISDN alternate channel selection as a feature; this should at least be documented. It was suggested that if this is mainly used in a non-SS7 case, something other than a CIC might be used. The entire usage of ACF requires re-thinking in this proposal; it is probably more appropriate to manage this on a per trunk group/route basis. It was agreed that it is important to pursue this work, with a goal of possible inclusion in H.323v3. D.265©, Consideration of Additional Methods of Transporting User Input (Cisco), considers the usage of non-H.245 transport of DTMF signals, mainly RTP-based. There was no objection per se to the development of these methods; however, specific applications should be part of future proposals. It was noted that two other user input methods are on the way: T.140 and generic service transport control channel.

D.313© (Lucent) proposes that Q13/16 study lower level call signaling protocol based on information elements in Q.931 and Q.932. This notes the problems with the H.450.x series support of supplementary services: lengthy to standardize, no differentiation among implementations, complex, and may not be needed in all architectures. A suggestion was made to use stimulus-based feature key signaling without a strict emulation or recapitulation of ISDN signaling. It was agreed to continue this work. It was agreed that it was too early to decide whether this would result in an Annex, changes to H.323v3, or a new recommendation. It was noted that this protocol is not intended to be used over very long ranges as human response times are involved. It was also noted that a strict following of a pure stimulus model is not required or even a good idea. A clear requirement is that adding a new service shall not require (generally speaking) an upgrade to the client. Application to SETs will be considered. D.256©, A method for real-time modem transmission over H.323 (Ascend), proposes a method of sending modem signals via “demod-remod” or complete termination of the modem in a GW, with passing of data over TCP. A key requirement is to differentiate between voice, modem, and fax. Note the called terminal is the one generating the tone. H.324 differentiation may be important. The following comments were raised: • CNG (calling tone) appears in data modems in Europe, and cannot be used as a marker for a fax modem. • Coordination of data rates is required. • How long should the data be buffered? • Is V.42 end to end or link by link? • How is data compression negotiated? • Is speed negotiated end to end, or link by link? A view was expressed that the link-by-link would give better results. • How is modem re-negotiation handled? • Is it clear that V.90 is even possible in this configuration? (Some say yes.) - There are flow control issues, with V.90 downstream and V.34 upstream. - There may be a way around this (from A. Draper, Madge). • What about synchronous vs. asynchronous modem? • Break handling end to end needs to be confirmed. • The relationship to text telephony was raised. It was suggested that UDP should not be used for a variety of reasons. Consideration should be given to usage of any existing RFCs. The usage of TCP is a key assumption of this work. It was agreed that this work should be pursued. It was noted that an H.246 H.323 to PSTN annex might be a place for this work. It was suggested that the work should be joint between Q23/16, Q13/16 and Q14/16. The terms of reference will be worked via correspondence between the respective experts’ meetings. The target is Determination in Feb. 2000, with most probably an H.323 Annex and possibly a Q23/16 document.

H.450.8, CONFERENCE OUT OF CONSULTATION, FOR DETERMINATION TD-18(WP2/16) is draft Recommendation H.450.8. It was agreed to withdraw this from Determination, and to incorporate the features of H.450.8 into the main text of the Determined H.323v3, as section 8.4.3.8. This text appears as WD2-16.

H.450.9, CALL COMPLETION ON BUSY SUBSCRIBER, FOR DETERMINATION It was agreed to not Determine H.450.9 (Call Completion on Busy Subscriber) at this meeting; volunteers are solicited to continue this work.

H.450.10, NAME IDENTIFICATION SERVICES, FOR DETERMINATION TD-51(WP2/16) is draft Name Identification Services (Editor G. Freundlich, Lucent). It was Determined by SG16 as H.450.8 rather than H.450.10, as the original H.450.8 was withdrawn, and incorporated into H.323v3. Final text is in TD-30(PLEN).

H.323 ANNEX F, SECURITY SET, FOR DETERMINATION WD2-03 contains a proposed H.323 Annex F for a security SET based on the IMTC security profile and also on similar ETSI TIPHON work. There are no new changes with respect to H.235. It was not agreed to recommend Determination. M. Euchner (Siemens) will be the editor.

H.323 ANNEX G, TEXT CONVERSATION AND TEXT SET, FOR DETERMINATION In H.323 multimedia systems, a text conversation transport for T.140 is in preparation in the form of a channel set up by H.245. The additions to H.323, formed into H.323 Annex G, Text Conversation, were up for Determination at this meeting. This Annex G also contains a simple IP textphone description called “Text SET,” based on the principles from H.323 Annex F. D.282©, H.323 Annex G: Text Conversation (Editor G. Hellström, Ericsson), was Determined by SG16 at this meeting; it describes text SET. It needs to be checked to sync up with the Decided H.323 Annex F. It was noted that UDP should only be used for H.332 or multicast. The title will be changed to “Text Conversation and Text SET.”

H.323 MOBILE ANNEX, FUTURE WORK It was agreed during the joint meeting with Q11/16 to create a mobile Annex for H.323. This would take the form of a document or documents that address mobility issues, including: • Mobility, including user and service mobility • Mobile issues including - Layer 2 issues & timers - Header compression - Handoffs and the H.323 system architecture A general goal is to apply H.323 systems to mobile systems being defined elsewhere, such as IMT-2000. This annex would consider the possibility that a packet layer other than TCP/UDP/RTP might be used for mobile applications. The tentative plan is to work toward a February 2000 Determination. Q14/16 WP2, COMMON PROTOCOLS, MCUS AND PROTOCOLS FOR INTERWORKING WITH H.300-SERIES TERMINALS

The new Q14/16 Rapporteur is G. Freundlich (Lucent, USA). TD-32(WP2/16) is the report of the Q12-14/16 interim Rapporteur’s meetings (November 1999 in Torino, Italy, and February 1999 in Monterey, CA). TD-47(WP2/16) is the status report of Q14. TD-69(WP2/16) is the Q14/16 meeting report.

LIAISONS TD-1(GEN) reports on SG4, the lead SG for Telecommunications Managed Networks (TMN); SG4 maintains the Documentation Plan (Attachment 2 of TD-1(GEN)). TD-6(GEN) from SG4 provides M.3010-1996 which describes the TMN architecture and layering approach. Management layers are: business management, service management, network management and network element management. Also attached to TD-1(GEN) is M.3400-1997 which describes TMN management functions and function sets. Management functions are categorized into: fault, configuration, accounting, performance and security. The reply (WD2-21) contains responses to the specific questions in the liaison, and describes the relevant work in H.341, H.235, and H.225.0 Annex G. TD-2(WP2/16), Media Gateway Control (Q4/8), indicates problems with fax support in the proposed IETF MGCP protocol. The response, WD2-23, mentions the H.GCP work in SG16, but states that comments on IETF protocols should be sent to the IETF. The suggested requirements from the liaison will be added to the requirements maintained by the IETF MEGACO group (these requirements serve as a basis for H.GCP work). A draft of H.GCP will be attached to WD2-23.

TD-11(WP2/16), Response to Liaison Statement from SG16 Regarding the H.323 MIB and TMN (WP5/4), describes some management work in SG4 Working Party 5, and requests information on the H.341 (media management) work. The response, WD2-22, includes an early draft of the H.341 work (April 1998).

IMPLEMENTORS GUIDE FOR H.245, H.235, FOR APPROVAL The issue of section 6.5.8 (H.235 Annex A) corrections was reviewed. The Implementors Guide approved at the September 1998 SG16 meeting introduced a new field (tokenOID) to the beginning of the ASN.1-defined ClearToken structure. A subsequent draft of the Implementors Guide moved the field to another location in the structure. Many vendors implemented according to this draft. The draft was compatible with the original H.235 ASN.1 definition, while the change that was approved in the Implementors Guide was not compatible with the original H.235 ASN.1 definition. D.293©, Comments on H.235 Clear Token (Israel), suggests moving the field after the original structure, and defining the field as optional. The resolution of this issue is to leave the definition as it was approved after the September 1998 meeting, meaning that the tokenOID field will remain at the beginning of the ClearToken with some clarifying text concerning when a dummy token id should be passed. The Implementors Guide for H.323, H.225.0, H.245, H.246, H.235, and H.450 was approved by SG16 as TD-37(PLEN) and TD-56(PLEN). (See also Q13/16 Implementers Guide, above.)

H.245V 5 CONTROL PROTOCOL, FOR DECISION Q11/16 reviewed the proposed editorial changes to COM16-79©, H.245v5 Appendix VII, in D.243© (Toshiba, NEC, NTT DoCoMo) required to correct the description of codepoints supporting ISO/IEC 14496-2 (MPEG-4 visual standard). The group agreed to the revised text which supports a generic capability control using OIDs and requested Q14/16 to include this change in H.245v5 for Decision. There is general agreement on the described changes with the modifications to the OID definition so that the OID for a particular generic capability is not tied to a particular version of H.245. This document also proposes an informative appendix containing procedures for creating generic capabilities and documenting the capabilities in H.245 or other standards documents. An ad hoc group met and drafted a solution, which appears in TD- 64(WP2/16). COM 16-79©, H.245v5, states that the MPEG-4 visual codepoint appendix should be removed if the generic capability mechanism is accepted. H.245v5 was Decided by SG16 as COM 16-79© plus TD-54(PLEN).

H.341, MULTIMEDIA MANAGEMENT INFORMATION BASE, FOR DECISION TD-37(WP2/16)© (G. Kajos, editor H.341) is the incoming Recommendation Multimedia Management Information Base. COM 16-80© is the Determined text. TD-39(WP2/16) shows the changes to COM 16-80©. There were no comments or reservations stated. TD-55(PLEN)©, a change document, shows the changes to the Determined draft. It was noted that the RTP MIB may change at some point in the future. If this happens, the Implementors guide for H.341 could capture the changes. H.341, formerly H.mediaMIB, was Decided by SG16 as COM 16-80© plus TD-55(PLEN)©.

H.283, REMOTE DEVIDE CONTROL LOGICAL CHANNEL TRANSPORT, FOR DECISION TD-35(WP2/16) shows changes to Recommendation H.283 (M. Duckworth, editor H.283), Remote device control logical channel transport (ex-H.RDC), against COM 16-78©. There were no comments on this document. Note that H.283 has a dependency on H.282 and the GenericCapability of H.245, so these items must also be Decided for H.283 Decision to proceed. The final changes against the COM 16-78© appear in TD-27(PLEN). H.283 was Decided by SG16 as COM 16-78© plus TD-27(PLEN).

H.282, REMOTE DEVIDE CONTROL FOR MULTIMEDIA, FOR DECISION There were no contributions against H.282, Remote device control protocol for multimedia applications (ex V.RDC). It was Decided as COM 16-R41©.

H.GCP, FOR DETERMINATION D.247©, Proposed Additions to the H.GCP Requirements (Telcordia), notes that the stated requirements appear to be addressed in MEGACO requirements. If MEGACO requirements are used for development of H.GCP, then there is no need to explicitly propose these requirements. D.257© (Ascend) proposes several Protocol Requirements for H.GCP. The first requirement is to support SCN call signaling in the media GW. There was no general consensus on this request. Suggestions were that this requirement might be addressed with event notification packages, signaling might be transported according to sigtran, or that SG11 should be consulted regarding messages to pass between MG and MGC to support SCN signaling in the MG. D. Skran (Ascend) and C. Groves (Ericsson) agreed to provide some clarifying text. D.257©’s second requirement is to support H.323 call signaling in the media GW. There was no general consensus on this request. A concern was that the basic protocol should remain unchanged. The presenters were asked to provide additional clarification. The third requirement is for the protocol to support H.245 in the media GW. This request was accepted. The final requirement, for the protocol to support call by call mode switching, was also accepted. It was noted that this requirement might also apply to other types of mode changes. In light of a potential agreement to cooperate more closely with the IETF on the definition of a gateway control protocol, the MEGACO requirements presented in D.286©, Media Gateway Control Protocol Architecture and Requirements (ISOC/IETF), bear careful consideration. There appears to be an agreement in principal to apply the MEGACO requirements to H.GCP. Interested parties were asked to review the MEGACO requirements and provide comments. These (lengthy) comments have been compiled into TD-36(PLEN) and will be presented to the MEGACO group, but not as an official SG16 position. TD-42(WP2/16)© is draft Recommendation H.GCP (B. Hill, editor, VideoServer). The purpose of this recommendation is to achieve greater scalability by decomposing the H.323 Gateway into functional sub-components - Media Gateway and Media Gateway Controller and defining the protocol these components use to communicate. Note that a MG could be an IP terminal, then the H.GCP protocol would replace the H.323 protocols. A number of issues were identified that required resolution: • Multimedia vs. linked mono-media contexts: The so-called connection model for the media gateway affects the definition of the protocol. The decomposed gateway must support multimedia, so modeling multimedia support is a critical issue. A breakout group was formed to address this issue. The results appear in TD-58(WP2/16), and have been incorporated into the draft text. It was agreed to use the multimedia context model proposed by J. Segers (Eindhoven University of Technology), with some extensions and amendments. TD- 58(WP2/16) also includes the proposal from B. Rosen (FORE Systems) for linking mono-media contexts to create a multimedia context model for H.GCP. • There is a need to express a media gateway’s capabilities and to describe, on a per call basis, the coders and addresses used. Current ideas include a modified SDP or something that can express the description capabilities found in H.245 (though not strictly H.245). This needs further work. • Encoding: Possibilities appear to be binary (e.g., similar to Q.931), text, or ASN.1. This is an issue that can be left until later. • Semantics of terminations: There is some concern that the “termination” object cannot adequately model the various types of endpoints/users (e.g., DS0 vs. a multiplex such as H.221 vs. bonded DS0, etc.). Some resolution was reached. Text appears in the H.GCP draft. Text to define the concept of a multiplex needs to be added to the definition of a termination. • Termination class: The termination classes should be defined. A preliminary superset of parameters exists in the document, but specific termination classes are needed. • Semantic content of names still needs discussion. • Backhaul Facility Associated Signaling (see discussion on D.233©, below, under Tunneling)

Draft H.GCP discusses required and optional support for the signaling interfaces in the MG and MGC. It was felt there is a need to reflect an MG’s support for signaling interfaces over interface A (i.e., the MG should indicate the signaling interfaces it supports). The B1 interface (to support H.245 signaling in MG) is included in the Determination of H.GCP. The B2 (H.225) and C (signaling from SCN) interfaces between MG and MGC are for further study. There appears to be a need for signaling to set up interface D (SCN signaling transport termination). Any MGC should be able to interoperate with any MG. The combined MG(s) and MGC shall operate together as a composed gateway. Discussion of Network Access Server support needs to be added. Definitions are needed for command and transaction. The concepts of command, transaction, and message should be presented before getting into command and transaction details. Otherwise, the discussion of commands, transactions, and messages is in good shape. “Object oriented” language should be replaced. The definition of the command application programming interface seems to generally be in good shape, but more work is needed in these areas: error codes, security, MG-MGC control model, naming conventions. There are some good examples (which should be moved to an appendix), but they are lacking details. Some ideas exist for a transport mechanism, but this topic also needs more work. H.GCP was Determined by SG16 as TD-29(PLEN)©. D.248©, Media Gateway Control Protocol (Telcordia), was submitted for information but was not be reviewed. D.287©, Media Gateway Control Protocol (ISOC/IETF), was submitted primarily for information and comparison with H.GCP, and was not be reviewed. This is a useful input for further work on the H.GCP document. D.246©, Media Gateway Control Protocol Call Flows for H.323 Systems (Telcordia), was presented for information (the content was originally targeted for discussion against the H.GCP draft from the Monterey meeting). The call flows illustrate some useful information. It should be noted that operation with the fast start procedure was much cleaner. Normal setup (not fast start) caused some problems.

H.246 ANNEX C, CONTROL PROTOCOL, FOR DETERMINATION TD-21(WP2/16) is draft H.246 Annex C (C. Groves, editor). The purpose of this document is to define the interworking between Call Signaling Protocols and Media Stream Packetization for packet based multimedia communications systems and the ISDN User Part functions and protocol of Signaling System No. 7. It is based on ISUP 1997 and Q.931 1993. This annex is modeled somewhat after Q.699. A subsequent draft with corrections and modifications was presented as WD2-11. SG16 Determined H.246 as TD-34(PLEN). WD2-25 is a liaison to SG11; it describes the work in H.246 Annex C and solicits SG11’s opinion. It was felt that better alignment of H.225 with Q.931 would ease interworking between ISUP and H.323. This work toward alignment might have some problems, so should proceed with caution. This liaison notes that H.246 Annex C should align with the features of H.323/H.225v3. There are some concerns about H.320-H.323 interworking using this annex.

H.245V 6, FOR DETERMINATION Contributions Related to New Coder Support New coder support was discussed during the joint WP1, 2, and 3 meeting, with both supporters and opponents. The GenericCapability and NonStandard (proprietary) constructs were discussed as possibilities for bringing support for non-standard (non-ITU) coders. A key point was made that this is not simply a matter of adding codepoints, but that a total system view

should be considered. Additional contributions are solicited to provide information regarding system issues and justifications for supporting non-ITU coders. D.277© (Nokia, Ericsson, Siemens) proposes to add AMR speech codec support in H.245. The AMR (8 bit rates, adaptive multi-rate) speech codec is the GSM codec to be used in future releases of GSM terminals and networks. Supporting 4.75 to 12.2 kbit/s, it is expected to be widely deployed. D.294© (Siemens) has the same intent. D.296© (Germany) recommends support of non-ITU media-codecs in the H.3xx recommendations. It was noted that in the future, the definition of bit streams may be made in ETSI or other standards bodies; in this case, the text of such documents may be referenced and thus not be fully contained in H.245. With this understanding, Q11/16 agreed to the proposal of D.277© and requested that Q14/16 include the text in H.245v6. TD-60(WP2/16) is the revised text. At the joint Q11-14/16 meeting, it was agreed that the GSM Adaptive Multi Rate Capability Definitions would be included in H.245v6. TD-24(PLEN) shows the revised Annex text. The following proposals are to be represented as a GenericCapability. The descriptions of each should be considered for an annex to H.245. This Annex should be Determined at this meeting so that it can be Decided along with H.245v6. The annex will be provided during a rapporteur’s meeting for inclusion in the white document. Packetization provided in the proposals will appear in H.225.0 Annex F. • D.223©, ANSI-136 ACELP Enhanced Full Rate and ANSI-136 US1 Full Rate Voice Coding for H.323 (AT&T) • D.224©, ANSI-136 Codec for H.323 (AT&T) • D.231©, Inclusion of the North American CDMA Wireless Coder IS-733 in H.323 Recs. H.245 and H.225 (Lucent) • D.268©, Inclusion of the North American CDMA Wireless Coder IS-733 in H.323 Recs. H.245 and H.225 (Qualcomm) It was agreed that the codecs defined in D.224©, D.231© and D.268© would be reviewed for potential inclusion in H.245v6 in generic capability format at the next experts meeting. Changes to H.245v6 are reflected in TD-22(PLEN) and TD-14(PLEN), which were accepted. TD-22(PLEN) addresses the MPEG-4 audio capability description. TD-14(PLEN) addresses the MPEG-4 system control capability description. (See also the discussion under H.245v6 in the Q11/16 report, above.) H.245v6 was Determined by SG16 as TD-14(PLEN), TD-22(PLEN), TD-24(PLEN), and TD-69(PLEN).

H.243, FOR DETERMINATION TD-36(WP2/16), Correction of Problems Related to MCV in H.243 (P. Luthi, PictureTel), was presented along with D.220© (Corrections of problems related to MCV, USA) and accepted. (See Q11/16 H.320 Systems report, above.) Final text for H.243 appears in TD-20(PLEN); SG16 Determined this version of H.243.

H.224, FOR DETERMINATION TD-32(GEN) (G. Hellström, acting as editor) is a revision of H.224 (A real time control protocol for simplex applications using the H.221 LSD/HSD/MLP channels) to include a T.140 code point in H.224. SG16 Determined the changes to H.224 as identified in TD-11(PLEN).

TUNNELING D.233©, Proposal of a New Annex in H.246 (Motorola, Cisco), addresses two issues: 1) Definition of a reliable transport mechanism useful for tunneling or “backhaul” signaling information, and 2) Suggestion for providing Intelligent Network (IN) services in H.323 systems. It is referred to as backhaul because the gateway terminates the lower layers of the protocol (i.e., layer 1 & 2) and backhauls the other layers to the MGC and/or Gatekeeper. The transport mechanism might be used between GKs and MGCs, signaling gateways and MGCs, signaling gateways and GKs, and also as a generic tunneling protocol - these uses were proposed but not agreed. Concerns included scaling issues (need to set up pipe between ends on a per call basis), ramifications on

high end, what SG11’s involvement should be (e.g., specification of MTP layer content). The use of this transport mechanism is interesting and should be studied in more detail for its applicability to H.323. The proposal for providing IN services in H.323 systems appears valuable and should be pursued further, possibly resulting in another annex to H.246. Future contributions should address use in direct endpoint as well as gatekeeper routed models, and should study the role of the border element. A liaison should be sent to SG11 to engage their expertise on interworking between IN and the packet network. A liaison to ETSI TIPHON WG2 might also be appropriate.

TOPICS FOR FUTURE WORK IN Q14/16 • New annexes in H.246 for data support (demod-remod for transit networks), including text telephony (total conversation) • H.341 support for H.GCP and other features • H.235 support for profiles • H.246 annex for gateway for H.323 over ATM (ATM Forum AF-SAA-0124.000) - need reference in H.246 to point to ATMF document • H.235v2 • Better consideration of firewall and proxy issues • Repairs • Security issues in gateways • Use of IPSEC • Back-end services, accounting, charging • Security profiles proposed by other bodies • Securing IP fax • Security in H.324 Q15/16 WP3, ADVANCED VIDEO CODING The Rapporteur of Question 15/16 is G. Sullivan (Microsoft, USA). TD-27(WP3/16) is the status report and agenda for this meeting. TD-14(WP3/16) and TD-15(WP3/16) are the reports of the interim meetings in Seoul (Nov. 1998) and in Monterey (Fe.b 1999), respectively. Nearly all of the documents from the Q15/16 interim meetings are available on-line at the Q15 external informal ftp site . TD-30(WP3/16) is the Q15/16 report of this meeting. The Q15/16 e-mail reflector is hosted by PictureTel (itu-adv- [email protected]) which is managed by automatic majordomo software . The primary Q15/16 goals for this meeting were: 1) Coordination with Q11/16 regarding Decision adoption of H.263v2 into H.320 suite (COM-16- 83©, COM-16-84©, COM-16-85©, COM-16-86©, D.219©) 2) Coordination with Q9/16 regarding progressing the work on Sign Language and Lip Reading Application Profile (D.290©) 3) Progress the work on H.262 | ISO/IEC 13818-2 in cooperation with ISO/IEC JTC1 SC29/WG11: • Decision of Amendment 5, High level for 4:2:2 profile (COM 16-82©) • Determination of Amendment 6, Number of lines in all profiles of high level (TD- 19(WP3/16)) • Consideration of plan to issue a revised edition incorporating prior and in-progress approved amendments and corrigenda (TD-28(GEN)) The video coding area (Q15/16) within WP3/16 currently has two significant on-going activities: H.263++ and H.26L. The H.263++ development effort is toward near-term standardization of enhancements to the H.263 video codec for real-time telecommunication and related non- conversational services. The H.26L development effort identifies new video coding technology beyond the capabilities of incremental enhancements to H.263, for longer-term standardization. In addition, Q15/16 supports any needs regarding the existing prior video coding standards (H.261, H.262, and H.263, and presumably H.120, as necessary).

H.262 AMENDMENT 5, HIGH LEVEL 4:2:2 PROFILE, FOR DECISION SG16 Decided the text of Recommendation H.262 | ISO/IEC 13818-2 (Information technology - generic coding of moving pictures and associated audio information: video) Amendment 5 as COM-16-82©. This amendment defines the addition of high level for the 4:2:2 profile. The 4:2:2 profile was added with Amendment 2 (11/96), but only main level was defined at that time.

H.262 AMENDMENT 6, NUMBER OF LINES IN ALL PROFILES OF HIGH LEVEL, FOR DETERMINATION SG16 Determined the text of Recommendation H.262 | ISO/IEC 13818-2 (Information technology - generic coding of moving pictures and associated audio information: video), Amendment 6 as submitted in TD-19(WP3/16) and forwarded to the Study Group as TD-3(PLEN). This amendment provides new upper bounds on the number of vertical lines in all profiles at High and High-1440 levels to reflect the agreement of the square pixel common image formal for HDTV systems in ITU-R BT.709-3 Part II. The value is changed from 1152 to 1088.

RE-ISSUANCE OF H.262 TO INCORPORATE ALL PRIOR AND IN-PROCESS ALTERATIONS Q15/16 recommends that an integrated version of Recommendation H.262 (Information technology - generic coding of moving pictures and associated audio information: video) be issued which consolidates together all of the previously-approved and in-process changes for editorial improvement (Integrated edition of ITU-T Recommendation H.222.0 | ISO/IEC 13818-1 and ITU- T Recommendation H.262 | ISO/IEC 13818-2) as proposed in TD-28(GEN). (See the Q12/16 report above regarding H.222.)

COORDINATION REGARDING ADOPTION OF A SIGN LANGUAGE AND LIP-READING APPLICATION PROFILE FOR VIDEO COMMUNICATION The Q15/16 experts were pleased to see the proposal by Q9/16 for the adoption of the draft sign language and lip-reading application profile for video communication, as submitted in D.290©. They agreed to support the adoption of the draft application profile as a supplement of H-series recommendations, which falls under the responsibility of Q9/16. (See the Q9/16 report above for additional details.)

COORDINATION REGARDING ITU-T IP-PROJECT TD-14(GEN) is a liaison statement from SG13, on the ITU IP Project. While the IP-based application is recognized to be a very important target of the video coding standards, the Q15/16 experts believe that the existing and future video coding standards developed by Q15/16 are generic and already provide significant support for IP environments. Q15/16 will continue to address this important application in its future work, as well as other applications. TD- 15(GEN) is another liaison from SG13 on IETF working groups. Q15/16 work is potentially related to the activity of the AVT WG, since no activity on video codec development is found in IETF WGs.

TECHNICAL PROPOSALS FOR H.263++ AND H.26L PROJECTS: CONTENT-BASED COEFFICIENT MAPPING D.281©, Proposal: Content-Based Coefficient Mapping for Recommendation H.26L (Siemens), proposes a feature to be added in a future video codec design. It describes an ability to define a specific “zone” subset of DCT coefficients which limits the coding of macroblocks in background regions of the picture by using only this subset of coefficients. It also defines a “zero-tree” means of sending the zone coefficients for these regions marked as background. A demonstration showed an ability to preferentially enhance the quality of foreground regions while lowering the fidelity of the less important changing background regions. The method is intended to provide a benefit in such cases having changing “background” regions of lesser importance in addition to a changing “foreground” region of greater interest. Such applications especially include scenes viewed from a moving camera (such as a hand-held camera or a mobile video terminal). The demonstration, using one sequence (“car phone”) on a laptop PC, showed some visible improvement in the foreground region and some degradation of fidelity in the background region, with an encoder performing a foreground/background classification based on a nominal flesh-tone color detection.

The benefit was shown relative to an encoder which made no distinction between foreground and background regions. Some comments noted that the benefit shown using this method should be compared against the benefit that can be obtained using a well-designed encoder-only region-of-interest enhancement method requiring no syntax modification. For example, the reference encoder could use manipulation of DQUANT step-size changes as defined in H.263 Annex T (along with encoding otherwise according to the test model also using Annexes D, F, I, and J). It was therefore suggested that the proponent bring such a demonstration in the future to Q15/16. It was agreed that the technology areas of work designated for the H.263++ and H.26L projects be modified to add mention of an investigation of this technology proposal.

PLANNING AND WORK ON H.263++ The H.263++ Workplan follows:

Mtg Dates Type Milestone Q15-H Aug ‘99 Experts Last Formal Draft Adoptions SG16-5 Sep ‘99 SG Q15-I Nov ‘99 Experts Final Draft for Determination SG16-6 Feb ‘00 SG Determination Q15-J May ‘00 Experts Bug-checking Q15-K Aug ‘00 Experts Final Draft for Decision Jan ‘01 SG Decision

The group discussed the current status of work on H.263++. The five previous and one new key technical areas that appear to be promising for further investigation: 1. Enhanced reference picture selection (adopted as a draft for future Determination as Annex U) 2. Error resilient data partitioning (adopted as a draft for future Determination as Annex V) 3. Affine motion compensation (in collaborative proposal development) 4. IDCT mismatch reduction (one proposal previously received) 5. Error concealment (normative or informative, no formal proposals yet received) 6. Content-based coefficient mapping (proposal received at this SG16 meeting)

PLANNING AND WORK ON H.26L The current workplan of the H.26L project is provided in TD-48(PLEN) Annex Q15.A, and is shown below:

Mtg Dates Type Milestone Q15-H Aug 99 Experts First Formal Draft Adoptions SG16-5 Sep 99 SG Q15-I Nov 99 Experts SG16-6 Feb 00 SG Q15-J May 00 Experts Q15-K Aug 00 Experts Final Major Feature Adoptions Jan 01 SG Apr 01 Experts Jul 01 Experts Aug 01 SG Determination Oct 01 Experts Bug-Checking Jan 02 Experts White Document Generation May 02 SG Decision

The H.26L project appears to be on track, and will continue to be led by Associate Rapporteur K. Hibi (CIAJ). A significant milestone for this project was reached at the Nov. 1998 Rapporteur’s group meeting, at which the first full algorithm technical proposals were evaluated for H.26L.

Significant progress was made, in particular, in the coding efficiency area, at the two interim Rapporteurs group meetings. Q15/16 decided to move forward in expectation of achieving the goals of H.26L with further improvement by collaborative effort, although no particular proposal fully meets all the requirements for H.26L at this time. According to the discussion on the similarities in technical natures of H.26L proposals, H.26L Key Technical Areas of interest were identified: Inter frame prediction coding (1) Variable-size block-based segmentation - Quad-tree like decomposition of frame - Small block size to 8x8, 4x4 (2) Long-term memory - Increase candidates of reference materials for prediction - Combination with other prediction scheme (e.g., affine warping) (3) Affine motion model - Adoption of six parameter affine motion model - Coding method and syntax of affine motion parameters - Searching of affine motion parameters Inter frame residual coding (also applicable to Intra texture coding) (4) 16-sampled waveform coding (4x4) - Coding with smaller block size than 8x8 DCT (5) VQ, EZW with DCT, multiple waveform coding - Adoption of (variable-dimension) VQ scheme - Embedded EZW structured coding - Selection from multiple coding modes - Zero-tree structured coding of subset of coefficients Intra frame coding (6) Directional (pixel-prediction) Intra coding - Improvement of prediction in Intra coding - Consideration of activity direction of picture The current technical work of H.26L seems to mainly focus on coding efficiency improvement; all functionalities listed in the H.26L requirement document should be finally supported. Q15/16 agreed upon the following functionality areas for the H.26L development process: (a) High compression performance - Capable of 50% or greater bit rate savings relative to ‘98 H.263v2 (DFIJT) at all bit rates (b) Simplification “back to basics” approach - Adoption of a generally simple, straightforward design using well-known building-blocks - For example, use of one VLC for all parameters to be coded (c) Flexible application to delay constraints appropriate to a variety of services - Low delay (e.g., no B pictures) for real-time conversational services - Moderate delay usage appropriate for sever-based streaming application (d) Error resilience - Packet loss resilience - Mobile channel corruption resilience (e) Complexity scalability in encoder and decoder - Asymmetry of encoder and decoder processing complexity - Scalability between amount of encoder processing and achievable quality (f) Full specification of decoding (no mismatch) - Resolve mismatch problem (e.g., integer transform, VQ, et al) (g) High quality application - Performance improvement in higher bitrate - Applicability to entertainment-quality applications (h) Network friendliness - Ease of packetization - Information priority control

As a next step, since H.26L should move into a collaboration phase as soon as possible, proponents of H.26L technical content are asked to seek common ground. For maximizing an effectiveness of collaborative effort, the test model for H.26L and relevant core experiments should be defined in later stage.

LIAISON STATEMENTS TD-06(WP3/16) is a liaison from ITU-T TG 8/1 regarding Multimedia coding for IMT-2000. It requests that Q15/16 keep them informed on work related to H.263++ and H.26L. The reply, in TD-49(PLEN), discusses H.263 in detail. TD-09(WP3/16), a liaison from ITU-T SG12 regarding A/V Quality Assessment, notes that Q10/12 and Q11/12 are planning to address perceptual video quality assessment methods for video with transmission errors, and requests any related information from Q15/16. TD- 49(PLEN) contains the reply. A liaison to ISO/IEC JTC1 SC29 WG11 (in TD-49(PLEN)) notes the work in Q15/16 and requests collaboration with WG11 in video coding development. TD-38(GEN), an output liaison statement to ISO/IEC JTC1 SC29 WG11, was generated jointly with Q12/16 regarding publication of an integrated version of Recommendation H.262. Q16/16 AND Q17/16, MULTIMEDIA HARMONIZATION AND COORDINATION The Question 16-17/16 Rapporteur is M. Matsumoto (Japan), assisted by T. Taylor (Nortel, Canada). The agenda is in TD-30(GEN). The meeting report is TD-70(PLEN). Some progress was made on the GII Projects. Projects F.3 (Information Appliances) and M.4 (Multimedia Middleware) have been closed for lack of interest. Work on Projects F.4 (End to End Interoperability) and M.3 (E-Commerce) continues and will be progressed at an interim meeting August 25-27, 1999 in Geneva. A report of the joint meeting of Q1 and Q16 on Project M.3 is in Annex 3 of TD-59(PLEN), the WP2 meeting report. (See also the Q1/16 and Q2/16 reports, above.) No substantive activity occurred. A new project, Mediacom 2004, was started to introduce the role and responsibility of each SG in the multimedia environment. The first draft of this work is in Annex 1 of TD-70(PLEN).

LIAISONS TD-2(GEN) and TD-3(GEN) from JQG1/11 (Joint Question Group created by SG11 for IMT- 2000 layer 2 coordination) discusses IMT-2000 multimedia requirements and Layer 2 radio interface work. They are in response to the SG16 liaison and request additional information on acceptable error rates, H.323 and H.324 requirements. Draft Recommendation Q.1732.1, Functional specifications and requirements for IMT-2000 layer 2 radio interface, is attached to TD-3(GEN). TD-67(WP2/16) is the reply by the Rapporteurs for Questions 11/16 and 13/16, noting new work in SG16. TD-10(GEN) is progress on work related to middleware from SG10. SG10 is asking for comments to the report if necessary. On this issue, it was reported that the work of GII M.4 on Middleware for Multimedia was closed recently. No action was needed. (See also Q2/16, above.)

TD-13(GEN) (SG13) is a copy of the GII Project plan prepared by SG13 at its meeting in February. As a result of the establishment of a new “ITU-T IP Project,” the GII Projects no longer include I.1 and I.2. These have been incorporated into the new IP Project. However, SG13 will continue its own studies on GII and will continue to monitor the work on the GII Projects in the other Study Groups. In this regard, SG13 is planning to hold a short meeting to review the GII work in association with an “IP Experts Meeting” in September. Q16-17/16 felt that the current activities in SG16 should be input to the planned meeting. The deadline for the Input is before the end of July. Q16-17/16 thought that the GII Project, Project F.3 on Information Appliance and Project M.4 on Middleware for Multimedia had finished. However it was decided that Projects F.4 on end-to-end interoperability and M.3 on electric commerce will continue. The F.4 Project draft will be updated, and will be submitted to the next

GII meeting. Annex 2 (to TD-70(PLEN)) is proposed information from the Rapporteur to this GII meeting in September. (See also Q2/16, above.) TD-14(GEN) (SG13) introduces the newly established IP Project. In particular, in order to progress rapidly, the project will be discussed at the IP Experts meeting in September; TD- 14(GEN) is also an invitation to join the meeting. (See also Q15/16, above.) TD-15(GEN) (SG13) lists the relationship between ITU-T Study Groups and IETF Working Groups. The information was preliminary and comments on the document were requested. TD-16(GEN) (SG13) is the multimedia coordination “Status of Activities.” The current recommendation status was requested. TD-72(PLEN) is the return liaison. MEDIACOM 2004 Q16-17/16 felt that it was time to develop Multimedia Project, which will introduce the role and responsibility of each Study Group in the multimedia environment. It was confirmed that the work on the update of Rec. H.200 should be the umbrella of the MEDIACOM 2004 Project. The title for the project as “MEDIACOM 2004” was proposed and agreed in the meeting. The Rapporteur prepared the first draft Multimedia Project, version 0.1. An interim meeting on this issue is planned for August 25-27 in Geneva. The first draft is in Annex 1 of TD-70(PLEN). Q19/16 WP3, EXTENSION TO EXISTING ITU-T SPEECH CODING STANDARDS AT BIT RATES BELOW 16 KBIT/S The Q19/16 Rapporteur is S. Hayashi (NTT, Japan). The agenda is TD-1(WP3/16). The meeting report is TD-35(WP3/16).

CORRIGENDUM FOR ANNEX H TO G.728, FOR DECISION The Corrigendum for Annex H to G.728 (Variable bit rate LD-CELP operation mainly for DCME at rates less than 16 kbit/s), published in COM16-R44©, was Decided by SG16 without changes. (See CSR Vol. 9.8.)

ANNEX I - G.728 EXTENSIONS FOR ROBUST PERFORMANCE IN THE PRESENCE OF FRAME ERASURES, FOR DECISION COM16-R44© is input text of Annex I to G.728. The correspondence group discovered a number of needed clarifications and typographical corrections. The Rapporteur presented the proposed modifications in TD-25(PLEN) (same as TD-2(WP3/16)). SG16 Decided Annex I to G.728 as COM 16-R44© plus TD-25(PLEN).

VBD CAPABILITY FOR THE 40-KBIT/S EXTENSION OF G.728 ANNEX J, FOR DETERMINATION Q19/16 is currently testing the performance of a 40 kbit/s extension to G.728. The extension is aimed at DCME applications mainly for data transmission. The test methodology for voice-band data (VBD) capability assessment of a 40 kbit/s extension to G.728 was finalized in Feb. 1998. COMSAT performed VBD tests on the candidate algorithm submitted by MOC Israel using this test methodology. D.278© (MOC Israel) is test results for non-voiced performance assessment of algorithm operating at 40 kbit/s mainly for DCME application. In the course of data performance measurement of the proposed 40 kbit/s extension, a problem was found with V.23 modulation while in character mode. ECI investigated the problem, and introduced modifications mainly in the gain adaption mechanism. With these modifications, D.279© (MOC Israel) is a detailed description of the candidate algorithm to Annex J to G.728. After revision of the test results, Q19/16 was satisfied with the performance and decided that the candidate should be Determined as the draft Annex J (Variable bit-rate operation of LD-CELP mainly for VBD applications in DCME) to G.728 with the following conditions:

• The text of the draft Annex J should be corrected by the editing group, taking into account the Errata presented by Mitsubishi in the September SG16 meeting in 1998; • Test reports on the DTMF capability should be presented at the next Rapporteurs meeting, although performance with DTMF signals is an objective. The test will be performed by the proponent. • Test vectors (used to certify an implementation) should be made available before Decision (scheduled for September 1999) • In case any algorithmic modification is made after the Determination, data performance tests should be performed to ensure that either bit exactness is achieved, or that no degradation in non-voice performance is observed. G.728 Annex J was Determined by SG16 as TD-67(PLEN).

IMPLEMENTORS GUIDES AND CORRIGENDA Problem and their fixes in Annexes A and B to G.723.1 and Annex E to G.729 were reported (D.301© and D.302©, both from FT/CNET). D.301© reports a slight bug (affecting frame erasure recovery for highly stationary signals) in the ANSI-C software of the higher bit rate extensions fixed point of G.729 Annex E, version 1.2 delivered to the ITU-T in May, 1998. D.302© reports a bug (during the generation of comfort noise) in the ANSI-C software of the fixed- point version of G.723.1 Annex A version 5.0 delivered to the ITU-T in 1996. Q19/20 agreed that the proposed bug-fixes should be in a new Implementors guide, which was approved as TD- 26(PLEN). The Rapporteur reported receiving a number of written communications indicating possible problems in the text of Annex G (16 kbit/s fixed point) to G.728. Although the current technical content of the Annex is believed to be correct, there may still be a few editorial errors in G.728 Annex G. The Rapporteur will prepare a list of the possible errors and make it available to the experts via correspondence. A Corrigendum will be proposed at the next SG16 meeting if deemed necessary.

PACKETIZATION FOR G.729 ANNEXES C, D AND E IN H.225.0 The recently approved Annexes D (6.4 kbit/s CS-ACELP speech coding algorithm) and E (11.8 kbit/s CS-ACELP speech coding algorithm) to Rec. G.729 provide variable bit rate operation capability to G.729 (Coding of speech at 8 kbit/s using conjugate-structure algebraic-code-excited linear-prediction, CS-ACELP) and G.729 Annex A (Reduced complexity 8 kbit/s CS-ACELP speech codec) codecs. Annex C specifies a floating point version of these two algorithms. TD- 28(WP3/16) (Q19/16 Rapporteur) defines packetization for each of these codec extensions. In particular, these definitions are consistent with the packetization adopted in I.TRUNK (I.362.2, AAL Type 2 service specific convergence sublayer for trunking). This material was provided to Q13/16 for incorporation in H.225.0 version 3, Section F.3.

TEST VECTORS FOR ANNEX C TO G.729 AT&T and FT/CNET worked together to produce test vectors for the floating-point version of G.729 (Annex C, Reference floating-point implementation for G.729 CS-ACELP 8 kbit/s speech coding). D.298© reports that the test vectors for the fixed-point version (main body and Annex A to G.729) work well in many platforms if double precision is employed in a G.729 Annex C implementation. This result gives good prospect of building the test vectors for floating point. However, Q19/16 felt that it would be preferable to have verification of these results by other organizations. The objective of this activity is to produce a non-normative document (White contribution, Report, or Appendix to G.729 Annex C); the target date to complete the technical work is September 1999. FRAME ERASURE CONCEALMENT FOR G.711 Recently there has been much interest in using G.711 on packet networks without QoS to support POTS. When packet loss (frame erasure) occurs on these networks, concealment techniques are required. D.249© (AT&T) presents an algorithm for packet-loss concealment (or FEC, Frame erasure concealment) for waveform-based speech coding such as G.711 (PCM). Q19/16

recognized that quality improvement is possible with this algorithm and encouraged independent quality verification tests of the current algorithm, or alternative methods or variations. Contributions on how to extend the algorithm for ADPCM coding such as G.726 are also encouraged. The initial target of this work will be to produce an Appendix to G.711, possibly extending support for other waveform based coding. The target date to complete the technical work is Sept. 1999. LIAISONS TD-8(WP3/16) is a liaison from SG12. Q14/12 notes Q19/16’s request for methodologies required to test VAD (voice activity detection), CNI (comfort noise insertion), DTX (discontinuous transmission) and similar algorithms. Information may appear at the next SG12 meeting. TD-49(PLEN) includes a liaison to ITU-R TG8/1, regarding the formal approval of Annex I to G.728 (Frame Erasure Concealment for LD-CELP at 16, 12.8 and 9.6 kbit/s), and of a Corrigendum for Annex H to G.728. It also reports the progress of the work on frame erasure concealment techniques for waveform-based speech coding such as G.711. TD-4(WP3/16) is a liaison from Q6/15 noting that G.767 (Digital circuit multiplication equipment using 16 kbit/s LD-CELP, digital speech interpolation and facsimile demodulation/remodulation) was Decided, and that G.767 expects to use the VBD-optimized coding algorithm from G.728 Annex J. The reply to ITU-T SG15 is in TD-49(PLEN); it announces that a Corrigendum to Annex H to G.728 was formally approved, and that Annex J to G.728 was Determined by SG16.

FUTURE WORK Q19/16 will hold a Rapporteurs meeting September 27-29 1999 in Geneva, subject to the submission of contributions. The issues to be addressed are: • Contributions addressing the Decision of Annex J to G.728, • Extension of Annex C to G.729 to include Annexes B, D, and E (floating point), • Approval of the frame erasure concealment algorithm as an Appendix to G.711, • Test vectors for Annex C to G.729, • Maintenance of existing speech coding recommendations. Q20/16 WP3, AUDIO AND WIDEBAND CODING IN PUBLIC TELECOMMUNICATION NETWORKS The Q20/16 Rapporteur is R. D. De Iacovo (CSELT/Italy). TD-11(WP3/16) is the meeting agenda; TD-12(WP3/16) is the Q20/16 progress report. TD-38(WP3/16) is the meeting report. The Q20/16 objectives were to evaluate the results of the selection test for wideband coding at 24 and 32 kbit/s and define the Terms of Reference for wideband coding at bit-rates around 16 kbit/s.

PRESENTATION OF SELECTION TEST RESULTS AT 24 AND 32 KBIT/S The six listening laboratories participating in the selection listening tests presented their respective results: • D.238©, Subjective selection test results for the ITU-T wideband (7 kHz) Speech Coding Algorithm at 24 and 32 kbit/s (Deutsche Telekom) • D.241©, Quality assessment results by NTT-AT for 7-kHz band audio coding algorithm (NTT) • D.303©, Results of listening tests carried out in support of the ITU-T wideband speech codec selection (Nortel Networks) • D.309©, Results of selection tests for the ITU-T wideband (7 kHz) speech coding algorithm: experiments #2A (music) (FUB CSELT) • D.310©, Subjective results of selection test plan for the ITU-T wideband (7 kHz) speech coding algorithm at 24 and 32 kbit/s - Experiments performed by FT/CNET (France Telecom) • D.311©, Subjective selection test results for the ITU-T wideband (7 kHz) speech coding algorithm at 24 and 32 kbit/s (BT)

All of them were judged compliant in meeting their deliverables according to the contents of the signed Memorandum of Understanding. As a consequence, the listening laboratories are expected to send a bill to ITU-T TSB for payment. The global analysis of the wideband codec selection tests (24/32 kbit/s) was presented by the Rapporteur. COM16-91© (PictureTel) and COM16-92© (NTT) contain detailed descriptions of the two candidate algorithms (B and A, respectively). Annex A to TD-38(WP3/16) presents the results for each laboratory and global (normalized by MOS) results. On the basis of the measured performance of the tested algorithms, the following main conclusion were drawn: 1. EXP1: requirements were not met by both candidates in connections with 3% random frame erasure conditions. Candidate A met requirements and objectives in clean speech conditions (1, 2 and 3 tandems). Candidate B met requirements in clean speech conditions at 24 kbit/s (1, 2 and 3 tandems) and the requirement at 32 kbit/s in 1 tandem. 2. EXP2: requirements and objectives were met by candidate A except in random frame erasure conditions (1%, 3%, 5%). Requirements and objectives were met by candidate B. 3. EXP3: requirements (except one case) and objectives were met by candidate A. Requirements and objectives (except two objectives) were met by candidate B.

DISCUSSION OF TEST RESULTS TD-13(WP3/16) contains the version 2.0 (December 1998) Selection Test Plan for the ITU-T Wideband (7 kHz) Speech Coding Algorithm at 24 and 32 kbit/s. TD-20(WP3/16) (Q20/16 Rapporteur with SQEG/12 chair) is a global analysis of the wideband codec selection test. Starting from the subjective test results obtained in the selection phase, Q20/16 discussed how to progress in the activity of wideband coding at 24 and 32 kbit/s. Requirements on Quality In 3% random frame erasure condition, with speech as input signal, the requirements were not met by both candidates. One party wanted to stick to the requirements and objectives as they are in the actual Terms of Reference for wideband coding. The majority, however, expressed the desire to select one of the two candidate algorithms on the basis of their performance results and complexity. To substantiate a decision, the group started considering several aspects, as follows. Quality in frame erasure conditions As regards the robustness of the candidate algorithms in error prone environments (especially in conditions with frame erasure conditions), both proponents declared that improvements are possible in their respective algorithms; a common feeling of Q20/16 was that a viable approach is to defer to a subsequent study the inclusion of those improvements in an Annex, if a Recommendation is Determined at this meeting. Applications Following the reasoning above, it was attempted to define the applications that can be accommodated by each candidate algorithm, on the basis of their performance and characteristics. The definition of the area of applicability was considered important, whatever candidate will be chosen. As preliminary indication, the first four applications of the Terms of Reference were listed: 1. ISDN videotelephony on Basic Rate Access (Note 1) 2. ISDN video-conferencing on Basic Rate Access (Note 1) 3. ISDN wideband telephony (e.g., for multichannel applications) (Note 2) 4. Wideband transmission over Internet (Note 3)

Note 1: One of the envisaged scenario is hands-free communication in presence of background noise, even if a wider range of environments is possible. Note 2: Both hands-free and handset communications are envisaged. Note 3: The range of applicability is restricted to the applications where error protection is accomplished using appropriate protocols. At the same time, the issue of complexity was raised; Q20/16 considered this to be of prime importance. Complexity The computational complexity and memory requirements of the NTT candidate algorithm (A) are reported in Table 4. A bit-exact, fixed-point descriptive approach was followed using the G.729 basic operations. The implementation details of the PictureTel candidate algorithm (B) are reported in Table 5 for both fixed and floating point implementations.

WMOPS ROM/kword RAM/kword 24 kbit/s encoder 170 87 15 24 kbit/s decoder 56 64 13 32 kbit/s encoder 100 91 12 32 kbit/s decoder 62 63 11

Arithmetic Host DSP or Encoder Decoder Total MIPS RAM/kword used CPU MIPS or MIP or or resources resources resources fixed-point TMS320C50 5.99 7.91 13.9 3.681 floating-point TMS320C31 4.76 4.49 9.25 floating-point Pentium P90 ~8% ~8% 16% of CPU cycles

Table 5. Computational complexity and memory requirement (PictureTel candidate algorithm, from COM16-91©) Decision The following four possible scenarios were discussed: 1. Select no candidate, since not all requirements are met. 2. Select the codec with lower complexity (which has some problems in clean speech conditions) for hands-free operation. 3. Select the codec which has better clean speech performance but higher complexity. 4. Consider both codecs for different sets of applications as appropriate. While scenarios 1 and 4 had no or little support, the majority favored the scenario 2. On that basis, Q20/16 agreed to pursue scenario 2 and select candidate B for Determination at the present SG16 meeting. It was felt that the coder met the need of the hands-free applications outlined in section 0. As confirmed by a letter signed by AT&T (the third party laboratory in the blinding procedure), Candidate B is the PictureTel candidate algorithm. TD-21(PLEN) is G.722.1 (ex-G.WB1) proposed for Determination: 7 kHz Audio Coding at 24 and 32 kbit/s for hands free operation in systems with low frame loss. It was Determined by SG16, with changes in TD-51(PLEN). Other Issues: C-code and Test Vectors Some organizations requested to have, at the Decision meeting, the C-code based on the library of basic operations that is under definition in Q22/16 (a superset of the G.729 basic operations).

PictureTel declared that work will be started in that direction and that collaboration with organizations that have experience in the field would be helpful. PictureTel also asked for collaboration in the preparation of an appropriate set of test vectors for the wideband algorithm. The question was raised: Should the C-code contained in a Recommendation for speech/audio coding be used just as a reference, and should different implementations be allowed, or should it be mandatory? It was agreed that a global answer, valid for all the Recommendations under study in WP3, should be given. The provisional contact person in case problems are revealed by third parties in the C source code is Antony Crossman, PictureTel, Phone : +1 978 623 4557, Fax : +1 978 749 2804, E-mail: [email protected] Other Issues: Characterization Test Plan It was agreed to ask SG12 for guidance in preparation of a characterization test plan for the wideband algorithm at 24 and 32 kbit/s. It must take into consideration the scope of the Recommendation and test results already obtained in the previous selection test phase. Funding has not yet been identified for the Characterization Tests. Other Issues: Annex Robust Under Frame Erasure Conditions Contributions are solicited for the next Rapporteur’s meeting from the interested organizations on the possible techniques to be used to increase robustness in frame erasure conditions. An appropriate way forward will be planned on the basis of those contributions. TERMS OF REFERENCE FOR WIDEBAND CODING AT AROUND 16 KBIT/S D.266© (Deutsche Telekom) is a list of applications for a wideband (7 kHz) speech coder at bit rates around 16 kbit/s. This includes: ISDN videotelephony and video-conferencing, Voice over IP and Internet applications, PSTN high quality audio conferencing, mobile (3G), ISDN wideband telephony, messaging and voice mail. D.304© (Canada) proposes Terms of Reference for the new activity of wideband speech coding at bit rates around 16 kbit/s. D.312© (Lucent) proposes requirements for a wideband coding effort at bit rates close to 16 kbit/s. The following general guidelines were discussed and considered relevant for this wideband activity: • Input and output audio signals should have a bandwidth of 7 kHz at a sampling rate of 16 kHz. • Primary signals of interest are clean speech and speech in background noise. Music performance requirements set at higher bit-rates (24 kbit/s). • High speech quality with the objective of equivalence to G.722 at 56/64 kbit/sec. • 16 kbit/s is the main bit-rate. The candidate is required to be able to scale in bit rate to lower bit-rates (less then 16 kbit/s) and up to 24 kbit/s with no fundamental changes in either the technology or the algorithm used. • Robustness to frame erasures and random bit errors. • Low algorithmic delay (frame size of 20 ms or integer sub-multiples) Based on the above, the Terms of Reference for a new wideband (7 kHz) coding activity at around 16 kbit/s, with focus on speech, were prepared as contained in Annex 20.B to TD-48(PLEN). Q20/16 is considering adopting the fixed-point description based on the library of basic operations, under study in Q22/16, and some inputs on this Q22/16 action point are expected from organizations involved in the wideband activity (see the Q22/16 report, below). The discussion was held on the time schedule and T0 time (starting point in time of the standardization process). It was generally agreed that if frozen Terms of Reference and a corresponding Qualification test plan are ready at the next Rapporteur’s meeting (September 1999), the possibility of having T0 time at the next SG16 meeting (February 2000) will be

considered. Moreover, Q20/16 briefly addressed how to proceed in testing the candidate algorithms. Some views were expressed in favor of a centralized host lab approach (same approach followed in the 4 kbit/s effort) even if a firm decision was not reached. The matter will be addressed at the next Rapporteur’s meeting.

LIAISON STATEMENTS TD-03(WP3/16) is a liaison from SG15. Q6/15 (CME) noticed that there is an objective for variable bit-rate compatibility in the Q20/16’s terms of reference for Speech Coding Algorithm at 24, 32 kbit/s referring to the capability of easy adaptation for packet and DCME applications. Q6/15 does not currently plan to use a 24, 32 kbit/s variable bit rate wideband speech codec in CME applications, such as DCMEs or ATM Voice CLAD (Cell Assembly/Disassembly). TD-5(WP3/16) is a liaison from ITU-R Task Group 8/1, noting applications they foresee for the Q20/16 wideband coder for videotelephony and audio conferencing in IMT-2000. Another reply liaison was drafted to inform ITU-R TG8/1 of continuing activities on the wideband coding activities (TD-40(WP3/16)). TD-7(WP3/16) is a liaison from ISO/IEC JTC1/SC29/WG11 on the MPEG-4 audio verification test results: audio on the Internet. Attached are the details of MPEG’s multi-language MOS verification tests referenced to existing codecs: • Audio tools in MPEG-4 on speech applications (16 to 56 kbit/s) • Digital audio broadcasting on AM modulated bands (16 to 24 kbit/s) • Internet audio applications (6 to 56 kbit/s) TD-8(WP3/16), a liaison from SG12, notes that the final test plans and laboratory allocations with be provided to Q20/16 after the next SG12 meeting. TD-39(WP3/16), a liaison to SQEG/SG12, informs them about the new Determined ITU-T Recommendation on wideband coding at 24, 32 kbit/s, asks support in developing an appropriate characterization test plan, and asks which listening laboratories are available for testing. It also requests them consider the preparation of a qualification test plan for wideband coding around 16 kbit/s, based on the ToR as defined in the present meeting. The aim is that if minor refinements are made to the ToR during the September 1999 meeting, they should be easily incorporated in the final version of the Qualification test plan.

FUTURE WORK The tentative schedule for Decision of the 24, 32 kbit/s algorithm is planned at the September 1999 meeting in Geneva. A Q20/16 Rapporteur’s meeting is also planned during September 27- 29, 1999. Q21/16 WP3, ENCODING OF SPEECH SIGNALS AT BIT RATES AROUND 4-KBIT/S The Q21/16 Rapporteur is P. Barrett (BT, UK). TD-23(WP3/16) is the report of the previous Q21/16 meeting (September 1998). TD-25(WP3/16) is the agenda and objectives for this meeting. TD-34(WP3/16) is the report from this meeting. The objective of this meeting was to prepare for the Coordinated Qualification Phase of the ITU-T 4-kbit/s speech coding work (G.4k). Declarations of intent were submitted for sixteen candidate speech coding algorithms. The meeting approved the schedule for the qualification phase and addressed outstanding issue. The results of the qualification experiments will be reviewed at a Rapporteur’s meeting September 27-29, 1999.

QUALIFICATION PHASE: CANDIDATE PROPONENT DECLARATIONS Fifteen candidate proponents identified their intent to submit candidate algorithms to the ITU-T 4-kbit/s qualification phase. Ascend Communications declared their intention to submit (and fund the testing for) two codecs, making a total of sixteen candidate algorithms. All fifteen candidate proponents confirmed that they would abide by item 2.2 of the ITU patent policy with respect to their ITU-T 4-kbit/s candidate submission. The candidate proponents (and documents of intent submitted to this meeting) are listed in Table 6 (see also Annex Q21.A of TD-48(PLEN)).

Ascend Communications Inc.* D.254© AT&T D.250© COMSAT Corporation D.227© Conexant Systems D.228© Ericsson --- Fujitsu Limited D.239© Matra Nortel Communications D.284© Matsushita Electric Industrial Co. D.232© Mitsubishi Electric Corporation D.235© Nokia --- NTT D.242© Samsung Electronics Co. (SEC)/SAIT D.274© Siemens D.295© Texas Instruments Inc. D.245© Toshiba Corporation D.234©

* Ascend Communications Inc. declared the intent to submit two candidate algorithms. Table 6. List of 4-kbit/s speech codec proponents.

QUALIFICATION PHASE: LABORATORY BIDS Q21/16 reviewed three bids for the laboratory functions of the qualification phase (TD- 16(WP3/16)). ARCON and COMSAT submitted bids for both the host laboratory and listening laboratory functions; DYNASTAT submitted a bid for the listening laboratory function only. The Rapporteur confirmed that these bids had been received by the April 19, 1999 deadline announced on the WP3 and SQEG/22 e-mail reflectors. In light of the large number of candidate algorithms and the short period available to perform the qualification phase, the three laboratories agreed to share the workload: ARCON stated that they could process the speech material for both qualification experiments at a cost of US$4,000 per candidate; DYNASTAT stated that they could perform Experiment 1 (ACR test) at a cost of US$7,500 per candidate; COMSAT stated that they could cross-check the processing of the speech material and perform Experiment 2 (CCR test) at a cost of US$10,000 per candidate. Q21/16 agreed upon this subdivision of the work for the costs stated. DYNASTAT stated that they would also provide previously unused North American English speech material for both qualification experiments; ARCON stated that they would provide suitable background noise material for Experiment 2 and process the demonstration material.

QUALIFICATION PHASE: MOU MATTERS The Rapporteur proposed the process contained in TD-17(WP3/16) as the basis for the management of the legal aspects of the 4-kbit/s qualification phase. This process is based on the procedure used for the ITU-T Q20/16 wideband selection phases, whereby the ITU acts as a central agent between the candidate proponents and the laboratories. The ITU charges a 5% administration fee in addition to the laboratory costs. Q21/16 agreed that this procedure would be adopted for the 4-kbit/s qualification phase. The total cost of the qualification phase will therefore be US$22,575 per candidate algorithm. The fifteen candidate proponents and the three laboratories stated that they agreed to versions 1.1 of the MoU and NDA distributed in TD-17(WP3/16). The necessary editorial changes will be made to accommodate the cross-checking function and the use of two listening laboratories.

QUALIFICATION PHASE ISSUES ARCON and COMSAT confirmed that they could support a number of processing platforms, and it was agreed that candidate proponents could submit their executables for the platform of their choice. The Rapporteur undertook to compile a list of platform requirements.

Q21/16 agreed that demonstration material would be provided for each candidate algorithm presented for further consideration in September 1999. The demonstration material will be supplied using a blind mapping (different to that used between the host and listening laboratories). The mapping of the demonstration material will not be disclosed. DYNASTAT agreed to provide additional sentences from the speech corpus used for the qualification experiments for the demonstration material. It was agreed that the background noise material used in Experiment 2 would be used for the demonstration material. The processed speech material will be provided to the listening laboratories for each experiment using a blind candidate mapping. Candidate proponents will only see the qualification test results for their own codec algorithms(s) prior to the September Q21/16 meeting. Proponents will be given the opportunity to withdraw their candidate(s) prior to this meeting, under which circumstances the qualification test results and the demonstration material for the candidate in question will be kept in confidence by the listening and host laboratories. The qualification results of the remaining candidate algorithms will be presented to the Q21/16 meeting in September 1999 on the basis of one document per candidate algorithm. The name of the candidate proponent will be clearly stated in each set of qualification results submitted to Q21/16.

REVIEW OF 4-KBIT/S QUALIFICATION TEST PLAN ARCON and COMSAT agreed to an annex to the Qualification Test Plan describing the cross- checking procedure. The annex, TD-48(PLEN) Annex Q21.E, was originally submitted as TD- 18(WP3/16). A further annex (TD-48(PLEN) Annex Q21.F) will be added to the test plan specifying the format of the executable code to be delivered by candidate proponents to the host laboratory. The G.711 processing stages will comprise A-law codecs preceded by 16 to 13 bit rounding. The listening laboratories agreed that no fewer than 10 male or 10 female subjects will be used in any experiment. After a discussion on the relative merits of handset or headset testing, it was agreed to adopt the use of headsets as specified in version 2.3 of the test plan.

REVIEW OF SCHEDULE Q21/16 agreed upon the ITU-T 4-kbit/s Qualification Phase Schedule in TD-48(PLEN) Annex Q21.B. This schedule plans to complete the qualification testing by September, 1999. Q21/16 also modified the main 4-kbit/s Schedule (TD-48(PLEN) Q21.D) for the ITU-T 4-kbit/s standardization program. The revisions were the use of wMOPS rather than a DSP simulation for the selection phase complexity evaluation, and a clarification of the qualification deliverables with respect to noise suppression technology. The overall schedule proposed for the development of a 4-kbit/s speech-coding algorithm is shown in Table 7.

Start time Item Estimated calendar time T0 Submission of qualification deliverables 9/99 during SG12 T0 + 4 months Commence selection testing T0 + 9 months Selection of one candidate for further consideration (the selected mid 2000, during candidate not necessarily identical to one of the source candidates SG12 due to possible compromise mixture); T0 + 12 months Determination of Recommendation and C-source code 9/00 SG16 WP3 T0 + 13 months Final text of Recommendation and C-source code available for TSB T0 + 18 months Approval (Decision) of Recommendation. Q1, 2001 SG16

Table 7. Development Schedule for 4 kbit/s Speech Coding Algorithm.

REVIEW OF TERMS OF REFERENCE (TOR) Noise Suppression Q21/16 discussed a request for clarification on the use of noise suppression in candidate codec algorithms, since this is not addressed in the ToR (TD-48(PLEN) Annex Q21.C). A number of delegates felt that it was difficult to specify what does, and does not, constitute a noise suppression algorithm, because some techniques are essentially embedded in the codec

architecture. Other delegates felt that separate pre-processing stages should be excluded. Concerns were also expressed over the use of the CCR (Comparison Category Rating) method of speech quality assessment for algorithms utilizing noise suppression techniques. Given the July 5, 1999, deadline for the delivery of qualification executables, Q21/16 agreed not to add any restrictions in the ToR with respect to noise suppression. A liaison will be sent to SQEG asking them to consider the possibility of noise suppression algorithms existing in candidate algorithms when preparing the ITU-T 4-kbit/s Selection Test Plan. Complexity There was a request to clarify the complexity requirement in the ToR. The Rapporteur drew Q21/16’s attention to fact that the objective for complexity is “as low as possible” and that complexity had been an important factor in the selection of the wideband codec by Q20/16 at this SG16 meeting.

BASIC OPERATORS D.275© (BT) is a proposal for an STL (software tool library) Basic Operators Module. It further proposes that this module should be used as the basis for the fixed-point description of the ITU-T 4 kbit/s speech coding algorithm. D.306© (Canada) provides comments on the fixed-point basic operators used for defining future speech coding standards. Considering that most new DSPs have an accumulator of 40 bits, D.306© proposes to add 40 bit operators to the list. Q21/16 agreed that the STL basic operators module proposed to Q22/16 should be used to define the fixed-point algorithms for the selection phase. The Rapporteur encouraged participation in the Q22/16 discussion on basic operators on the Q19-22/16 reflector [email protected] prior to September 1999.

WORK FOR THE NEXT STUDY PERIOD The Rapporteur stated that Q21/16 had clear goals for the first part of the next Study Period, and reminded the meeting of the work items on voice activity detection and higher and lower bit- rate extensions in the ToR. The text of Q21/16 will be distributed on the WP3/16 reflector for comment prior to the next SG16 meeting.

LIAISON STATEMENTS TD-8(WP3/16) is a liaison from SG12. It notes that a revised section on listening methods for use in the 4 kbit/s qualification was prepared and included in the Qualification Test Plan Rev 2.30. Subjective testing labs were informed of the Q21/16 desire to have a single lab conduct qualification tests and have been invited to contact the Q21/16 Rapporteur. TD-10(WP3/16) is a liaison from ITU-R TG 8/1, noting the upcoming revision of Rec. ITU-R M.1079, Speech and voiceband data performance requirements for IMT-2000. It requests information concerning applicable existing or forthcoming recommendations. A liaison statement was drafted to inform SQEG of the progress in Q21/16, and to inform SQEG that the selection phase may contain algorithms that utilize noise suppression technology. A liaison was also drafted to ITU-R TG 8/1 to inform them of the number of candidates algorithms to be evaluated in the qualification phase. Both are contained in TD-37(WP3/16). Q22/16 WP3, SOFTWARE AND HARDWARE TOOLS FOR STANDARDIZATION OF SPEECH AND AUDIO CODING ALGORITHMS The Q22/16 Rapporteur is S. F. Campos-Neto, COMSAT). TD-22(WP3/16) provides a report of the interim activities. Currently Q22/16 is dealing with the maintenance and future enhancements of the ITU-T Software Tool Library, release 1996 (STL96). Q22/16 reviewed and approved the maintenance work performed by correspondence; it also agreed to add existing basic operators to the ITU-T software tool library (STL), and to discuss by correspondence the definition of new operators as well as a revision of the weights currently associated with the existing basic operators. Little progress was made in this period, although some minor bugs were corrected and identified.

Q22/16 also agreed to work towards Determination of a new release of the ITU-T STL at the next SG16 meeting, code-named STL2000.

SOFTWARE TOOLS: MAINTENANCE AND REVISIONS A problem was identified at the last meeting: files in some instances were processed for less samples than the total specified by the user when the file size was not a multiple of the block size. This problem has been fixed in g726demo.c, filter-d.c, g722demo.c (originally reported for sv56demo.c and actlevel.c). Additionally, the header file ugstdemo.h preamble was changed to define MS-DOS for the gcc compiler under Win95/CYGWIN32 as well as for the MS Visual C compiler. FIR. The receive side of the modified IRS filter (provided by Voxware) has not yet been implemented in the STL. An optional sample delay was implemented in the demo program filter.c when the asynchronization option is selected. This was done in response to the fact that filtering by itself by the wideband asynchronization filter in the STL introduces only a very small amount of asynchronization, in the order of a few samples. For the wideband exercise, a value of 160 was chosen and set as default. This change was incorporated in a “sister” version of filter.c, called filter-d.c in order to avoid confusion in the wideband selection exercise as to which version of the tool should be used. The filter-d.c was checked in HPUX, DJGPP, and TCC. Two new processed files were produced, tst-asyd.flt and tst-asys.flt. Appropriate portability tests were added to the makefiles. Q22/16 agreed to replace eSTL9801’s filter.c with the new version. Q22/16 also agreed with the principle to include the ETSI MSIN filter characteristic into the FIR module. G.726. DSPC provided a fix for g726.c that is supposed to fix the long-standing problem with one test vector for the 40 kbit/s rate. Verification of the impact of the change remains to be checked. EID. A bug was fixed in gen-patt.c when the option to skip some bits or frames was selected for bit error/frame erasure: • It was saving 0x007F to file when the skip option was enabled for (B)FER mode when it should be 0x6B21 • It was saving the wrong number of bits or frame flags • It was computing the BER/(B)FER based on the ratio of disturbed bits over processed bits. This is OK for skip==0, but for skip>0, the proper ratio is disturbed/generated (generated is processed plus skipped). The problem was corrected and tested under HPUX. The change needs to be verified in other platforms, but should not present any problems. Still in the EID module, Q22/16 removed cosmetic compilation warning in file save_EID_to_file(), which affects compilation of files eiddemo.c and eid_io.c. SVP56. No further investigation has been done on a proposed modification on the calculation of active levels (to postpone active level calculation until all the samples in the file have been processed, as proposed in COM 16-R28©, report of the Jan.-Feb. 1998 SG16 meeting). Preliminary comparisons reported last meeting indicated almost identical measurements when the speech files had been pre-equalized to -26 dBov. Further tests will investigate the effect for a range of input speech level files. When finalized, the results will be posted to the WP3/16 reflector. Unsupported Tools. In support for the wideband selection tests cross-check activity, a portable 32-bit CRC calculation tool was made available. The reported number of comparisons performed in compfile.c, which was incorrectly reported when file sizes were not a multiple of block size, has been corrected. Information regarding usage of the delay option was improved. In oper.c, modified formatting of usage information was modified, and the confusing message “trimming by the size of ... file” when files are of the same size was removed.

NEW WORK ITEMS D.275© (BT) proposes that an updated version of the basic operators used in G.729 should be added to the ITU-T STL. In addition, D.275© proposes that the weights associated with each basic operator should be reviewed, and that new operators might need to be added. D.306© (Canada) proposes that some 40-bit basic operators should be added to the STL, as well as three basic operators used in G.723.1 which are not present in the set of basic operators used by G.729. During discussion, it was clarified that the main purpose of the basic operators is to emulate instructions available in current digital signal processors; the basic operator definition will benefit future standardization efforts. Q22/16 agreed to incorporate the updated G.729 operators into the STL, together with the three G.723.1 basic operators not present in G.729. More discussion is necessary on the definition of new basic operators. Q23/16 WP1, PCM MODEMS The Rapporteur for 23/16 is L Brown (Motorola, USA). The agenda for the meeting is TD- 21(WP1/16). TD-22(WP1/16) is the report of the San Diego, California, Q23/16 Rapporteur meeting in December, 1998.

LIAISONS TD-1(WP1/16), a liaison from SG8 concerns connection problems with some V.34 half-duplex modems; Q23/16 agreed that Q4/16 should address the issue. (See the Q4/16 report, above.) TD-4(WP1/16), a liaison reply from SG15 provides the ANT (Access Network Transport) standardization plan issue 1, October, 1998. TD-44(PLEN) includes Q23/16’s reply. It provides modifications to the entry pertaining to Rec. V.90 and notes that V.91 is now Approved. TD-5(WP1/16) is a liaison statement from SG15 on “network characteristics” for information. Two major points are addressed: CME (Circuit Multiplication Equipment) from Q6/15, and Interworking from Q8/15. Q6/15 is currently studying the method to convey higher-bit-rate modem signals, such as V.34 or V.90. There are two methods envisaged. The first is to use 64 kbit/s clear channels for VBD signals instead of 40 kbit/s coded channel, with an attendant sacrifice of CME channel efficiency. The second method is to discriminate incoming higher-bit-rate modem signals from conventional lower-bit-rate modem signals and assign 64kbit/s clear channels only for the higher-bit-rate signals. Q8/15 notes the widespread use of digital pads on the order of 3-6 dB on virtually every inter- switch call and the attendant degradation this causes V.90 modems. It also notes that many PT&Ts have chosen to implement the digital trunk connections between the local switching office and the ISP without digital padding. TD-44(PLEN) provides the Q23/16 liaison response to Q6/15 supporting the discrimination of higher-bit-rate modems. TD-7(WP1/16) is a liaison reply from SG15 responding to the Q23/16 request to clarify the adaptive component of build-out delay. Delays in PCME (G.764 and G.765) consist of mainly two components: a fixed delay and a variable delay. The fixed delay arises from signal propagation on the transmission link and fixed processing delays. Variable delays result primarily from the queuing and processing of packets. The maximum allowable variable delay for a virtual path or virtual circuit is specified as the build-out. The terminating endpoint must therefore store the voice band packets (data or speech) that arrive before their scheduled play-out time and play them at regular intervals. Packets exceeding the build-out delay are considered late and are dropped. The build-out delay is added only once at the terminating endpoint. Therefore the build- out delay is a fixed delay. In order to avoid future confusion, clarifying text was added noting that build-out delay can be set by the operator in accordance with I.356 to a value between 300 microsec. and 3 millisec. in 100 microsec. steps. Q23/16 agreed that no further liaison is necessary at this time.

TD-8(WP1/16) from Q5/SG2 raises questions on the operation of V.34 and the operation of V.34 for fax. Attached is draft E.hispeed (10/11/98), Measurements and metrics for monitoring the performance of V.34 G3 facsimile. The liaison reply (in TD-44(PLEN)) provides the requested information on V.34, noting that it is feasible to demodulate the control channel; it notes that the V.34 MPh sequence can occur during initial start-up, inter page data rate signaling changes, and control channel retrains.

PCM MODEM ISSUES LIST Q23/16 approved TD-23(WP1/16), the issues list for the on-going work on PCM modems updated to reflect the agreements reached at the Q23/16 Rapporteur meeting in San Diego, California.

PROPOSED RECOMMENDATION V.91 Q23/16 approved D.221©, a contribution from the USA proposing a correction to draft Recommendation V.91. D.221© notes that during start-up turning ON circuit 107 V.24 (Data set ready) has not been specified. It was agreed to add the following sentence to V.91 8.2.1.6: “After

transmitting Eu, the modem shall turn ON circuit 107.” D.297© (Siemens) addresses an issue pertaining to the V.91 start-up procedure. It proposes to modify the V.91 start-up procedures such that INFO' is repeated until an INFO' is received from the remote end. After a detailed discussion of the V.91 start-up procedure, Q23/16 agreed to some minor enhancements. COM 16-72© is the Determined draft Recommendation V.91. Several errors due to conversion from Microsoft Word’97 to Word’95 were identified. TD-38(PLEN) reflects approved additions and changes to the Determined draft text for Recommendation V.91. SG16 Decided V.91 as COM 16-72© plus TD-38(PLEN).

V.90 - ISSUE 2 D.270© (Motorola) addresses applications for V.90 - Issue 2 and proposes that Pulse Code Modulation (PCM) be used in the upstream direction. Applications noted for higher speed upstream include: multimedia access to the Internet or conferencing bridges, Internet gaming, telecommuting, and server maintenance. Although Q23/16 did not approve this technical proposal, it felt that V.90 - Issue 2 should be progressed, and therefore requested two interim Rapporteur meetings.

OTHER ISSUES D.256© (Ascend Communications) proposes a method for real-time modem transmission over H.323. Detailed discussion of this contribution was deferred to a joint Q13/16-Q23/16 session. (See the Q13/16 report, above.)

INTELLECTUAL PROPERTY (IP) The following companies indicated verbally that they may have IP pertaining to draft Recommendation V.91 and either have submitted or plan to submit patent statements: Conexant, 3Com, Lucent Technologies, Motorola and MGCS Panasonic. The following companies have made similar verbal statements at previous meetings: Matsushita and Lake Datacomms.

FUTURE MEETINGS Two interim Rapporteur meetings are planned to progress the work of Q23/16. These meetings will be held jointly with the Q8/16 and Q23/16 Rapporteur Groups. The meetings are scheduled for Sept. 13-17, 1999 in Belgium, and for Jan. 10-14, 2000 in Ft. Lauderdale, FL.

ITU-T SG/16 MEETING ROSTER, MAY 17 - 28, SANTIAGO CHILE P.A. Probst (Switzerland) SG16 Chair G. Helder (USA) SG16 Vice-Chair J. Magill (UK) Chair, WP1/16 F. Tosco (Italy) Chair, WP2/16 S. F. Campos Neto (USA) Chair, WP3/16

Austria Gerhard List Austria Telekom Austria Bernard Handl Austria Telekom Austria Klaus Sambor Austria Telekom Austria Andreas Steiner Austria Telekom Austria Michael Welser Belgium Telindus NV Paul Aerts Brazil Georges Claesson Brazil Maximiliano Martinh˜ño Canada Roch Lefebvre Canada Redwan Salami Canada Tom Taylor Canada Mitel David Walker Canada Nortel Networks (Canada) François Audet Canada Nortel Networks (Canada) Peter Yue Chile Entel, S.A Mauricio Castillo Rebolledo Chile Entel, S.A Mauricio Andres Grandon Aravena China Xiao Hui Dai China Lin Tao Jiang China Xing Ming Li China Xin Yue Liu China Guo Wen Song China Yuezheng Wen China Yun Tao Xu China Hong Bin Yu Finland Marko Luomi Finland Helsinki Telephone Co. Juha Kauppi Finland Nokia Ari Heikkinen Finland Nokia Kim Nordlund Finland Nokia Pekka Rissanen Finland Tellabs Oy Jerry Skene France Jean Pierre Blin France Yves Robin-Champigneul France Alcatel CIT Bahman Mobasser France Alcatel CIT Nicolas Tran France France Telecom Claude Lamblin France France Telecom Franck Lelong France Matra Nortel François Capman Germany Rolf Rôggeberg Germany Istvan Sebestyen Germany Bosch Jens Vollmer Germany Deutsche Telekom Ralf-Rainer Damm Germany Deutsche Telekom Joachim Stegmann Germany Siemens Gero Base

Germany Siemens Robert Callaghan Germany Siemens Martin Euchner Germany Siemens Neal King Germany Siemens Karl Klaghofer Germany Siemens Juha Korpi Germany Siemens Markku Korpi Germany Siemens Bernard Wimmer Germany TELES Jorg Ott India Pradeep Kumar Agarwal Israel Meir Agassy Israel Orit Levin Israel Boaz Michaely Israel Lior Moscovici Israel Sasha Ruditski Israel Uzi Shalev Italy Mauro Falcone Italy Roberto Flaiani Italy CSELT Rosario Drogo De Iacovo Italy CSELT Livio Lambarelli Italy CSELT Federico Tosco Japan Kouichi Iida Japan Mitsuji Matsumoto Japan Sakae Okubo Japan Canon Masao Hosaka Japan CIAJ Keiichi Hibi Japan Fujitsu Yasuji Ota Japan Fujitsu Kiyoshi Sakai Japan Hitachi Toshiaki Suzuki Japan KDD Hideaki Yamada Japan Matsushita Electric Industrial Akira Atsuta Japan Matsushita Electric Industrial Hiroyuki Ehara Japan Mitsubishi Electric Kazuhiro Matsuzaki Japan Mitsubishi Electric Yushi Naito Japan NEC Hidenobu Harasaki Japan NEC Masahiro Serizawa Japan NTT Shinji Hayashi Japan NTT Naoki Kobayashi Japan NTT Kazunori Mano Japan NTT Shigeaki Sasaki Japan OKI Electric Industry Yasuo Aoyagi Japan OKI Electric Industry Yasubumi Chimura Japan OKI Electric Industry Minoru Miyazaki Japan Toshiba Barry Aronson Japan Toshiba Yoshihiro Kikuchi Japan Toshiba Masahiro Oshikiri Japan Toshiba Hirokazu Tanaka Korea Don-Whan Hyun Korea Samsung Electronics Doh-Suk Kim Netherlands John Segers

Netherlands Royal KPN Jeroen De Muijnck Sweden L.M. Ericsson Robert Bauml Sweden L.M. Ericsson Christian Groves Sweden L.M. Ericsson Roar Hagen Sweden L.M. Ericsson Gunnar Hellström Sweden L.M. Ericsson Goran Roth Sweden Telia Research Annika Kilegran Switzerland Swisscom Pierre-André Probst UK John Magill UK Joseph Pointer UK BT Paul Barrett UK BT John Boucher UK BT Morgan Potter UK Lucent Technologies Mike Buckley UK Lucent Technologies Brian Moore UK Madge Networks Andrew Draper USA Bruce De Grasse USA Gary Fereno USA Jeff Heath USA Granger Kelley USA James Lord USA An Nguyen USA Radhika Roy USA Andrea Saks USA Alan Sharpley USA John Tardelli USA Benjamin Walston USA 3-COM Fred Lucas USA Alcatel, USA Clifford Thomas USA Ameritech Services Fred Kujawski USA Analog Devices Joshua Kablotsky USA Ascend Communications Gerard J. Aguilar USA Ascend Communications Dale Skran USA Ascend Communications Robert Zopf USA AT&T David Kapilow USA Cisco Systems Richard Bowen USA Cisco Systems Hascall Sharp USA COMSAT Corporation Simao Campos-Neto USA COMSAT Corporation Suat Yeldener USA Conexant Systems Keith T. Chu USA Conexant Systems Tom Geary USA Conexant Systems Jes Thyssen USA Databeam Paul Jones USA Databeam Patrick Muphy USA Delta Information Systems Paul Randall USA Dialogic Corporation Steven Magnell USA ESS Technology Jordan Cookman USA Intel Vineet Kumar USA Intel Gregory Meyer

USA Intel Mark R. Walker USA Lucent Technologies Robert Abrams USA Lucent Technologies Rex Coldren USA Lucent Technologies Glen Freundlich USA Lucent Technologies Milo Orsic USA Lucent Technologies Sean Ramprashad USA Microsoft Gary Sullivan USA Motorola Info. Systems Bruce Adams USA Motorola Info. Systems Les Brown USA Motorola Info. Systems Edgar Martinez USA Motorola Info. Systems William Schmidt USA Motorola Info. Systems Randall Stewart USA Motorola Info. Systems Qiaobing Xie USA PictureTel Antony Crossman USA PictureTel Kaynam Hedayat USA PictureTel George Helder USA PictureTel Patrick Luthi USA Qualcomm, Inc. Amitav Das USA Qualcomm, Inc. Peter Jackson USA Tekelec Virgil Long USA Telcordia Technologies Hong Liu USA Telcordia Technologies Michael Ramalho USA Telcordia Technologies Richard Rubin USA Texas Instruments Jacek Stachurski USA Texas Instruments Vishu Viswanathan USA Videoserver Bryan Hill USA VTEL Smita Gupta USA WorldCom Douglas Clowes ITU-TSB Fabio Bigi ITU-TSB Gabrielle Regan

The next issue of Communications Standards Review - Telecommunications (Vol. 10 #7) is scheduled for August 1999.

COMMUNICATIONS STANDARDS REVIEW ALSO PUBLISHES:

Communications Standards Summary (ISSN 1075-5721), a quarterly publication reporting on all active projects and recently completed standards of the TIA’s (Telecommunications Industry Association’s) TR-committees. Authorized by TIA. For more details visit http://www.csrstds.com. To receive a complimentary issue of either of CSR’s technical journals, please contact Elaine Baskin, tel +1 650 856-9018, fax +1 650 856-6591, e-mail: [email protected]

ACRONYM DEFINITIONS

ACELP Adaptive CELP ACF Authentication Control Function ACR Absolute Category Rating AM Amplitude Modulation AMR Adaptive MultiRate ANSI American National Standards Institute ARQ Automatic Repeat Request ASN Abstract Symbol Notation ATM Asynchronous Transfer Mode ATMF ATM Forum AV AudioVisual AVT Audio/Visual Transport BAS Bit rate Allocation Signal BER Bit Error Rate (B)FER Burst Frame Error Rate BRQ Bandwidth Request C&I Commands and Indications CCR Comparison Category Rating CDMA Code Division Multiple Access CELP Code Excited Linear Prediction CIC Carrier Identification Code CME Circuit Multiplication Equipment CNI Comfort Noise Insertion CRC Cyclic Redundancy Code CS-ACELP Conjugate Structure ACELP DCE Data Circuit terminating Equipment DCME Digital Circuit Multiplication Eqpt. DCT Discrete Cosine Transform DQUANT Field for modified quantization mode (H.263+) DRQ Disengage Request DS0 64 kbit/s Channel DSP Digital Signal Processing DSS2 Digital Subscriber Signaling 2 DTE Data Terminal Equipment DTMF Dual Tone Multi Frequency EDH Electronic Document Handling EID Equipment Identifier FIR Finite Impulse Response GII Global Information Infrastructure GK GateKeeper GSM Global System for Mobile Communications GW GateWay HDLC High Level Data Link Control HDTV High Definition Television HSD High Speed Data Channel IDCT Inverted Discrete Cosine Transform IETF Internet Engineering Task Force IMT International Mobile Telecommunications (IMT-2000,) IMTC International Multimedia Teleconferencing Consortium IN Intelligent Network IP Internet Protocol IPSEC IP Security (IETF) IPTEL Internet Protocol Telephony (IETF Working Group) IRS Intermediate Reference System ISDN Integrated Services Digital Network ISOC Internet Society ISP Internet Service Provider ISUP ISDN User Part

ITU Int’l Telecommunication Union JRG Joint Rapporteurs Group LD CELP Low Delay CELP LSD Low Speed Data channel MCS Multi-point Control Services (T.122) MCU Multi-point Control Unit MCV Multipoint Command Visualization MEGACO MEdia GAteway COntrol MG Media Gateway MGC Media Gateway Controller MGCP Media Gateway Control Protocol MIB Management Information Base MIPS Million Instructions Per Second MIV Multipoint Indication Visualization MLP Multi-Layer Protocol MOS Mean Opinion Score MOU Memorandum of Understanding MPEG Motion Picture Experts Group MTP Multicast Transport Protocol MUX Multiplexer OID Object Identifier PCM Pulse Code Modulation PCME Packet Circuit Multiplication Eqpt. PDU Protocol Data Unit PINT PSTN Interworking (IETF) POTS Plain Old Telephone Service PSTN Public Switched Telephone Network PT&T Public Telephone and Telegraph QOS Quality of Service RAS Registration, Admission, and Status RFC Designation for an Internet Standard RTCP Real-time Transport Control Protocol RTP Real Time Transport Protocol SCN Switched Circuit Network SDP Session Description Protocol SET Simple Endpoint Types SG Study Group (ITU, CCITT) SQEG Speech Quality Expert Group SS7 Signaling System 7 STL Software Tool Library TA Terminal Adapter TCP Transmission Control Protocol TIPHON Telecommunications and Internet Protocol Harmonization Over Networks (ETSI Project) TOR Terms of Reference TPKT Transport Packet (T.123) TSAG Telecommunication Standardization Advisory Group (ITU) TSB Telecommunications Standardization Board (ITU) UDP User Datagram Protocol URL Uniform Resource Locator VAD Voice Activity Detector VBD Voice Band Data VBR Variable Bit Rate VCI Virtual Channel Identifier VLC Variable Length Codeword VoIP Voice Over Internet Protocol VPI Virtual Path Identifier WAP Wireless Application Protocol WG Working Group

WMOPS Weighted MOPS WP Working Party (ITU) xDSL all the different Digital Subscriber Line equipment

THE CSR LIBRARY Subscribers may order copies of documents shown in boldface type from Communications Standards Review, where not controlled. $50.00 for the first document in any order, $40.00 for the second, and $25.00 for each additional document in any order. Volume discounts available. Please contact CSR to order.

Documents listed with © are controlled documents. These documents are not for sale, but we can provide you with the author’s contact information. ETSI meeting documents are also not for sale, but we can provide you with the author’s contact information.

We have a large library of standards work in process and can help you locate other information you may need.

CSR recommends that you obtain published standards from Global Engineering Documents. Tel: 800 854-7179, +1 303 792-2181, Fax : +1 303 397-7935, http://global.ihs.com

Visit the CSR Web Pages: http://www.csrstds.com

The Web Pages include an on-line store (order subscrptions and reports, an updated Telecom Acronym Definitions list, updated meeting schedules, a list of web sites and ftp sites as listed in all issues of CSR journals, background material on telecom standards and CSR (the company), data sheets on both CSR technical journals, and more.

Communications Standards Review formerly Communications Standards Review-Telecommunications regularly covers the following committee meetings:

TIA TR-29 Facsimile Systems & Equipment TR-30 Data Transmission Systems & Equipment TR-41 User Premises Telephone Equipment Requirements ITU-T SG8 Telematic Terminals SG15 WP1 Network Access SG16 Multimedia ETSI ATA Analog Terminal Access DTA Digital Terminal Access TM6 Transmission & Multiplexing

1999 STANDARDS COMMITTEE MEETING SCHEDULES AS OF JUNE 25, 1999 Subject to Change without Notice

Committee Date(s) Location Committee Date(s) Location ITU-T SG15 Jun 21 -Jul 2 Geneva, ETSI TM6 Sep 20 - 24 Edinburgh, Scot. ETSI ATAc WG Jun 29 - 30 Sophia Antipolis Q19-21/16 Rapp. Sep 27 - 29 Geneva ETSI TIPHON Jul 19 -23 Amsterdam, NL ITU-T SG16 Sep 30 Geneva ETSI DTA Jul 20 - 21 Sophia Antipolis ETSI TIPHON Oct 4 - 8 Berlin, Germany Q4/15 Rapp Aug 2 - 6 Nuremberg, Ger. TR-30* Oct 11 - 14 Baltimore, MD Q11-15/16 Rapp. Aug 2 - 6 Berlin, Germany ETSI ATA Oct 11 - 15 Vienna, Austria TR-29 Aug 9 - 11 West Coast ETSI DTA Oct 26 - 28 Sophia Antipolis TR-30* Aug 16 - 18 Quebec City, PQ Q4/15 Rapp. Nov 1 - 5 Nashville, TN TR-41 and TR-42 Aug 16 - 20 Ottawa, Ont Q11-15/16 Rapp. Nov 1 - 5 New Jersey Q16-17/16 Rapp. Aug 25 - 27 Geneva TR-29 (proposed) Nov 2 - 4 Southeast US T1E1 Aug 23 - 27 Baltimore, MD TR-41 and TR-42 Nov 8 - 12 Reno, NV Q5/8 Rapp. Aug - Sept Japan TR-30* Nov 29-Dec2 Clearwater, FL SG16 Rapp: Q4, Sep 13 – 16 Belgium ETSI TM6 Nov 29-Dec3 Amsterdam, NL Q8, Q23 ETSI TIPHON Dec 6 - 10 San Diego, CA SG8 Interim, Sep 20 Maidenhead, UK T1E1 Dec 6 - 10 Clearwater, FL Q1/8 , Q4/8 Rapp * TR-30.3 meets jointly with T1E1.4 ad hoc for 1 1/2 days.

YEAR 2000 STANDARDS COMMITTEE MEETING SCHEDULES AS OF JUNE 25, 1999 Subject to Change without Notice

Committee Date(s) Location Committee Date(s) Location SG16 Rapp: Q4, Jan 11 – 14 Ft. Lauderdale, TR-41 May Tyson Crnrs, VA Q8, Q23 FL ETSI TM6 May 22 - 26 --- Q4/15 prop. Rapp. Jan 31-Feb 4 --- TR-30 (Proposed) Jun 12 - 15 --- TR-41 February Maui, HI Q15/16 Rapp. July ITU-T SG8 Feb 2 - 10 Geneva TR-41 August Vancouver, BC TR-30 (Proposed) Feb 7 - 10 --- TR-30 (Proposed) Aug 7 - 10 --- ITU-T SG16 Feb 7 - 18 Geneva ETSI TM6 Sep 18 - 22 --- T1E1 Feb 21 - 25 --- TR-30 (Proposed) Oct 9 - 12 --- ETSI TM6 Feb 28-Mar3 --- TR-41 November New Orleans LA Q15/16 Rapp. April ITU-T SG16 November Geneva ITU-T SG15 Apr 3 - 14 Geneva ETSI TM6 Nov 27-Dec1 --- TR-30 (Proposed) Apr 10 - 13 --- TR-30 (Proposed) Dec 4 - 7 ---

Communications Standards Review -Telecommunications (ISSN 1081-4655) is published 8 - 9 times per year, within days after the latest, related standards meetings. Editor: Elaine J. Baskin, Ph.D. Technical Editor: Ken Krechmer. Copyright © 1999, Communications Standards Review. All rights reserved. Copying of individual articles for distribution within a subscriber organization is permitted. Subscriptions: $695.00 per year worldwide, $795.00 in electronic format. Corporate Intranet subscriptions (site license for multiple copies) are available. Submit articles for consideration to: Communications Standards Review, 757 Greer Road, Palo Alto, CA 94303-3024 U.S.A. Tel: +1-650-856-9018. Fax: +1-650-856-6591. e-mail: [email protected]. WWW: http://www.csrstds.com 10906.