ETSI TS 103 161-3-2011 Access Terminals Transmission and Multiplexing (ATTM) Integrated Broadband Cable and Television Networks IPCablecom 1 5 Part 3 Audio Codec Requirements for t.pdf

《ETSI TS 103 161-3-2011 Access Terminals Transmission and Multiplexing (ATTM) Integrated Broadband Cable and Television Networks IPCablecom 1 5 Part 3 Audio Codec Requirements for t.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 103 161-3-2011 Access Terminals Transmission and Multiplexing (ATTM) Integrated Broadband Cable and Television Networks IPCablecom 1 5 Part 3 Audio Codec Requirements for t.pdf（46页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 103 161-3 V1.1.1 (2011-04)Technical Specification Access, Terminals, Transmission and Multiplexing (ATTM);Integrated Broadband Cable and Television Networks;IPCablecom 1.5;Part 3: Audio Codec Requirements for the Provision ofBi-Directional Audio Service over CableTelevision Networks using C

2、able ModemsETSI ETSI TS 103 161-3 V1.1.1 (2011-04)2Reference DTS/ATTM-003011-3 Keywords access, broadband, cable, IP, multimedia, PSTN ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association

3、but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceive

4、d difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be a

5、ware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services:

6、http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2011. All rights reserved. DEC

7、TTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. LTE is a Trade Mark of ETSI currently being regis

8、tered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 103 161-3 V1.1.1 (2011-04)3Contents Intellectual Property Rights 5g3Foreword . 5g31 Scope 7g32 References 7g32.1 Normative refe

9、rences . 7g32.2 Informative references 9g33 Definitions and abbreviations . 10g33.1 Definitions 10g33.2 Abbreviations . 11g34 Void 12g35 Background 12g35.1 IPCablecom Voice Communications Quality Requirements 13g35.2 Network Preparation for Codec Support 13g35.2.1 Packet Loss Control 13g35.2.2 Laten

10、cy Control 13g35.2.2.1 Latency Control: Buffering . 14g35.2.2.2 Latency Control: Optimal Framing/Packetization . 14g35.2.2.3 Latency Control: Packet Timing Optimization . 14g35.2.3 Codec Transcoding Minimization . 14g35.2.4 Bandwidth Minimization 15g36 Device Requirements for Audio codec support 15g

11、36.1 Dynamic Update Capability . 15g36.2 Maximum Service Outage 15g36.3 Minimum Processing Capability 15g36.4 Minimum Audio Codec Storage Capability . 16g37 Audio Codecs Specifications 17g37.1 Feature Support 17g37.1.1 DTMF Support 17g37.1.2 Fax and Modem Support . 17g37.1.3 Echo Compensation Suppor

12、t. 18g37.1.4 Asymmetrical Services Support 18g37.1.5 Hearing-impaired Services Support 18g37.1.6 A-law and -law Support 19g37.1.7 Packet Loss Concealment . 19g37.1.8 Fax Relay 19g37.1.8.1 T.38 Over UDPTL 19g37.1.8.2 T.38 Over RTP 20g37.1.9 DTMF Relay . 20g37.1.10 V.152 Transmission 21g37.1.10.1 V.15

13、2 Transition Triggers . 21g37.1.10.1.1 Considerations for Simultaneous T.38 and Voice Band Data Support 22g37.1.11 Security Considerations 23g37.2 Mandatory Codecs 23g37.2.1 G.711 23g37.3 Recommended Codecs . 23g37.3.1 iLBC . 23g37.3.2 BV16 . 24g37.4 Optional Codecs . 24g37.4.1 G.728 24g37.4.2 G.729

14、 Annex E . 24g37.4.3 G.722 24g37.5 Optional Features . 24g3ETSI ETSI TS 103 161-3 V1.1.1 (2011-04)47.5.1 Wideband Codecs . 24g37.5.2 Optional Codecs 24g37.5.3 Voice Activity Detection (VAD) 25g37.6 Session Description of Codecs . 25g37.6.1 iLBC Session Description . 28g37.6.2 BV16 Session Descriptio

15、n 28g37.6.3 G.722 Session Description 28g38 Video Requirements . 29g38.1 Overview 29g38.2 IPCablecom Video Devices 29g38.3 Video Encoder Requirements . 29g38.4 Video Format Requirements. 30g38.5 H.263 Annexes . 31g38.6 Multipoint Conferencing Support . 33g38.6.1 Freeze Picture Request 33g38.6.2 Fast

16、 Update Request . 33g38.6.3 Freeze Picture Release 33g38.6.4 Continuous Presence Multipoint (CPM) . 34g38.7 Signalling Messages . 34g39 RTCP Requirements and RTCP Usage 35g39.1 RTP Requirements . 35g39.2 RTCP Requirements . 35g39.2.1 General Requirements of the IPCablecom RTCP Profile . 35g39.2.2 Se

17、curity Requirements for RTP and RTCP in IPCablecom 37g39.2.3 Extended RTCP Reports . 37g39.2.3.1 Reporting Call Quality Metrics using RTCP XR 37g39.2.3.1.1 RTCP XR VoIP Metrics Requirements . 37g39.2.3.1.2 Definition of Metrics related to Packet Loss and Discard . 37g39.2.3.1.3 Definition of Metrics

18、 Related to Delay . 38g39.2.3.1.4 Definition of Metrics related to Signal 38g39.2.3.1.5 Definition of Metrics related to Call Quality . 38g39.2.3.1.6 Definition of Parameters related to endpoint configuration 40g3Annex A (informative): Codec Comparison Tables 42g3Annex B (informative): Bibliography

19、. 45g3History 46g3ETSI ETSI TS 103 161-3 V1.1.1 (2011-04)5Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, a

20、nd can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp).

21、Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present

22、 document. Foreword This Technical Specification (TS) has been produced by ETSI Technical Committee Access, Terminals, Transmission and Multiplexing (ATTM). The present document is part 3 of a multi-part deliverable covering Access, Terminals, Transmission and Multiplexing (ATTM); Integrated Broadba

23、nd Cable and Television Networks; IPCablecom 1.5, as identified below: Part 1: “Overview“; Part 2: “Architectural framework for the delivery of time critical services over cable Television networks using cable modems“; Part 3: “Audio Codec Requirements for the Provision of Bi-Directional Audio Servi

24、ce over Cable Television Networks using Cable Modems“; Part 4: “Network Call Signalling Protocol“; Part 5: “Dynamic Quality of Service for the Provision of Real Time Services over Cable Television Networks using Cable Modems“; Part 6: “Event Message Specification“; Part 7: “Media Terminal Adapter (M

25、TA) Management Information Base (MIB)“; Part 8: “Network Call Signalling (NCS) MIB Requirements“; Part 9: “Security“; Part 10: “Management Information Base (MIB) Framework“; Part 11: “Media Terminal Adapter (MTA) device provisioning“; Part 12: “Management Event Mechanism“; Part 13: “Trunking Gateway

26、 Control Protocol - MGCP option“; Part 14: “Embedded MTA Analog Interface and Powering Specification“; Part 15: “Analog Trunking for PBX Specification“; Part 16: “Signalling for Call Management Server“; Part 17: “CMS Subscriber Provisioning Specification“; Part 18: “Media Terminal Adapter Extension

27、MIB“; ETSI ETSI TS 103 161-3 V1.1.1 (2011-04)6Part 19: “IPCablecom Audio Server Protocol Specification - MGCP option“; Part 20: “Management Event MIB Specification“; Part 21: “Signalling Extension MIB Specification“. NOTE 1: Additional parts may be proposed and will be added to the list in future ve

28、rsions. NOTE 2: The choice of a multi-part format for this deliverable is to facilitate maintenance and future enhancements. ETSI ETSI TS 103 161-3 V1.1.1 (2011-04)71 Scope The present document specifies the media aspects of the interfaces between IPCablecom client devices for audio and video commun

29、ication. Specifically, it identifies the audio and video codecs necessary to provide the highest quality and the most resource-efficient service delivery to the customer. The present document also specifies the performance required in client devices to support future IPCablecom codecs, describes a s

30、uggested methodology for optimal network support for codecs. The present document also extends the existing IPCablecom 1.0 Codec specification by introducing two new low-bit codecs, ITU-T Recommendation T.38 20 fax relay for reliable fax transmission, RFC 2833 24 DTMF Relay for reliable DTMF transmi

31、ssion and metrics to measure voice quality. 2 References References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referen

32、ce document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee

33、 their long term validity. 2.1 Normative references The following referenced documents are necessary for the application of the present document. 1 PKT-TR-ARCH1.5-V02-070412: “PacketCable 1.5, Architecture Framework Technical Report“, April 12, 2007, Cable Television Laboratories, Inc. 2 PKT-SP-DQOS

34、1.5-I04-090624: “PacketCable 1.5 Specifications, Dynamic Quality-of-Service“, Cable Television Laboratories, Inc. 3 PKT-SP-NCS1.5-I03-070412: “PacketCable 1.5 Specifications, Network-Based Call Signaling Protocol“, April 12, 2007, Cable Television Laboratories, Inc. 4 ATIS-0152100-2005(R2010): “Pack

35、et Loss Concealment for Use with ITU-T Recommendation G.711“. NOTE: Available at http:/webstore.ansi.org/RecordDetail.aspx?sku=ATIS-0100521.2005(R2010). 5 Voice-Over-IP Forum Service Interoperability Implementation Agreement 1.0, December 1, 1997. 6 “Current Methods of Speech Coding.“ R.V. Cox. Inte

36、rnational Journal of High Speed Electronics consequently T.38 sessions using UDPTL will not have secure media at the transport level. T.38 Annex D describes the set of attributes to be used when setting up a T.38 UDPTL session. For more information on the use of these attributes refer to 3. To contr

37、ol the T.38 UDPTL session, the FXR package will be used and all endpoints shall support this package as described in 3. ETSI ETSI TS 103 161-3 V1.1.1 (2011-04)20The MTA shall be prepared to receive a T.38 UDPTL fax packet of at least 160 bytes in the downstream. This is based on 40 ms packetization

38、period and a 14 400 bps data rate. It includes the UDPTL datagram without the IP and UDP headers. Upon transition to UDPTL T38, MTAs and media gateways should immediately send T.38 “No signal“ indicator packets if the MTA or media gateway would not otherwise be sending signal or data packets. For DQ

39、oS considerations, T.38 fax packets should use the same port used by the voice packets for the connection. In addition, MTAs and media gateways shall send T.38 fax packets at a default 20 ms packetization period in the upstream unless directed by the CMS via the packetization period to use a differe

40、nt packet rate (10 ms / 20 ms / 30 ms). Table 4 shows the DQoS flowspec parameters for 10 ms / 20 ms / 30 ms T.38 sessions (with redundancy of 1 for the T.4 data) that can be used in the least-upper-bound calculations for Authorization and resource requests. If the fax session is performed using the

41、 fxr/gw mode, then the data flow shall fit within the DQoS flow characteristics described above. 7.1.8.2 T.38 Over RTP T.38 running over the RTP protocol as described in 20 is currently out of scope. 7.1.9 DTMF Relay RFC 2833 24 specifies in-band RTP payload formats and usage to carry DTMF, modem an

42、d fax tones, line states, and call progress tones across an IP network either as recognized “telephone events“ or as a set of parameters defining a tone by its volume, frequency, modulation and duration of its components. Besides the transport of tones across an IP network, 24 also allows for the re

43、mote collection of DTMF digits by a media gateway to relieve an Internet end system (e.g. media server) of having to do this. Other advantages of 24 include inherent redundancy to cope with packet loss and the means to allow IP phones to generate DTMF digits when signalling to the PSTN without requi

44、ring DTMF senders. The use of RTP payloads in RFC 2833 24 to carry telephone events, states and telephony tones represents an in-band means of signal transmission as opposed to an out-of-band path via the CMS. For DTMF, IPCablecom endpoints shall support transmission and reception of RFC 2833 24 DTM

45、F telephone-events 0-15 which represents the minimum level required for compliance with the RFC. IPCablecom endpoints may support other telephone-events. If negotiated for a call, these events shall be transferred via RFC 2833 telephony event packets regardless of the codec specified for the speech.

46、 In addition as an RTP payload type, DTMF relay shall be secured through the IPCablecom bearer encryption and authentication mechanisms defined in i.1, if these are active on a call. MTAs and MGs shall support the mandatory security options listed in i.1 for DTMF relay and additionally, if the optio

47、nal encryption algorithms are supported for audio codecs, then these shall also be supported for DTMF relay. RFC 2833 24 references ITU-T Recommendation Q.24 i.13 in defining the minimum DTMF tone duration of 40 ms. Additionally, ITU-T Recommendation Q.24 i.13 includes a duration range lower than 40

48、 ms when the DTMF tones may be accepted as DTMF digits (as low as 20 ms). For North American networks, Telcordias LSSGR 25 specifies that tone durations greater than 40 ms must be accepted (subject to rise/fall times of less than 5 ms) and tones between 23 ms and 40 ms may be accepted by receivers.

49、However generators should provide 50 ms minimum tone duration (with a rise/fall time The media attribute line(s) (a) are of the form: a=: A typical IP-delivered voice communication would be of the form: m=audio 3456 RTP/AVP 0 a=ptime:10 On the transport address line (m), the first term defines the media type, which in the case of an IP voice communications session is audio. The second term defines the UDP port to which the media is sent (port 3456). The third term indicates that this stream is an RTP Audio/Video profile. Finall