1、 International Telecommunication Union ITU-T J.160TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (11/2005) SERIES J: CABLE NETWORKS AND TRANSMISSION OF TELEVISION, SOUND PROGRAMME AND OTHER MULTIMEDIA SIGNALS IPCablecom Architectural framework for the delivery of time-critical services over cable t
2、elevision networks using cable modems ITU-T Recommendation J.160 ITU-T Rec. J.160 (11/2005) i ITU-T Recommendation J.160 Architectural framework for the delivery of time-critical services over cable television networks using cable modems Summary This Recommendation provides a high-level reference fr
3、amework that identifies the functional components and defines the interfaces necessary to provide digital voice and telephony services. A family of Recommendations (ITU-T Recs J.161-J.178) has been developed to implement this architecture. Source ITU-T Recommendation J.160 was approved on 29 Novembe
4、r 2005 by ITU-T Study Group 9 (2005-2008) under the ITU-T Recommendation A.8 procedure. ii ITU-T Rec. J.160 (11/2005) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector
5、 (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every f
6、our years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, t
7、he necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary.
8、 However, the Recommendation may contain certain mandatory provisions (to ensure e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the nega
9、tive equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the u
10、se of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendatio
11、n, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. ITU 2006
12、All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. ITU-T Rec. J.160 (11/2005) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Terms and definitions . 2 4 Abbreviations and conventions. 2 4.1 Abbreviations . 2 4.2 Co
13、nventions 4 5 IPCablecom 4 5.1 IPCablecom architecture framework 4 5.2 IPCablecom zones and domains. 5 5.3 IPCablecom Recommendations 6 5.4 IPCablecom design considerations. 7 6 IPCablecom functional components. 9 6.1 Media Terminal Adapter (MTA) 10 6.2 Cable Modem (CM) . 12 6.3 HFC access network.
14、12 6.4 Cable Modem Terminating System (CMTS) . 12 6.5 Call Management Server (CMS) 12 6.6 PSTN gateway 13 6.7 OSS back-office components . 15 6.8 Announcement Server (ANS). 16 7 Protocol interfaces 17 7.1 Call signalling interfaces 17 7.2 Media streams. 19 7.3 MTA device provisioning. 21 7.4 SNMP el
15、ement management layer interfaces. 22 7.5 Event messages interfaces 23 7.6 Quality of Service (QoS) 24 7.7 CMS subscriber provisioning. 27 7.8 Electronic surveillance . 28 7.9 Security. 29 8 Network design considerations. 35 8.1 Timekeeping and reporting issues 35 8.2 Timing for playout buffer align
16、ment with coding rate. 35 8.3 IP addressing 35 8.4 Dynamic IP addressing assignment 36 8.5 FQDN assignment 36 8.6 Priority marking of signalling and media stream packets 36 8.7 Fax support . 37 iv ITU-T Rec. J.160 (11/2005) Page 8.8 Analogue modem support. 37 Appendix I Glossary of terms . 38 I.1 De
17、finitions 38 I.2 Abbreviations . 40 BIBLIOGRAPHY 43 ITU-T Rec. J.160 (11/2005) 1 ITU-T Recommendation J.160 Architectural framework for the delivery of time-critical services over cable television networks using cable modems 1 Scope The IPCablecom project defines a family of Recommendations that can
18、 be used to develop interoperable equipment capable of providing packet-based voice, video and other high-speed multimedia services over hybrid fibre coax (HFC) cable systems utilizing cable modems per the DOCSIS family of Recommendations. Future work will extend this architecture to include multime
19、dia applications. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are
20、subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a docum
21、ent within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T Recommendation G.711 (1988), Pulse code modulation (PCM) of voice frequencies. ITU-T Recommendation J.83 (1997), Digital multi-programme systems for television, sound and data services f
22、or cable distribution. ITU-T Recommendation J.112 (1998), Transmission systems for interactive television services, plus Annex A (2001), Digital Video Broadcasting: DVB interaction channel for Cable TV (CATV distribution systems), Annex B (2004), Data-over-cable service interface specifications: Rad
23、io-frequency interface specification and Annex C (2002), Data-over-cable service interface specifications: Radio-frequency interface specification using QAM technique. ITU-T Recommendation J.161 (2001), Audio codec requirements for the provision of bidirectional audio service over cable television n
24、etworks using cable modems. ITU-T Recommendation J.162 (2005), Network call signalling protocol for the delivery of time-critical services over cable television networks using cable modems. ITU-T Recommendation J.163 (2005), Dynamic quality of service for the provision of real-time services over cab
25、le television networks using cable modems. ITU-T Recommendation J.164 (2005), Event message requirements for the support of real-time services over cable television networks using cable modems. ITU-T Recommendation J.166 (2005), IPCablecom management information base (MIB) framework. ITU-T Recommend
26、ation J.167 (2005), Media terminal adapter (MTA) device provisioning requirements for the delivery of real-time services over cable television networks using cable modems. ITU-T Recommendation J.170 (2005), IPCablecom security specification. ITU-T Recommendation J.171.0 (2005), IPCablecom trunking g
27、ateway control protocol (TGCP): Profiles overview. 2 ITU-T Rec. J.160 (11/2005) ITU-T Recommendation J.178 (2005), IPCablecom CMS to CMS signalling. ITU-T Recommendation Q.704 (1996), Signalling network functions and messages. ITU-T Recommendation T.38 (2005), Procedures for real-time Group 3 facsim
28、ile communication over IP networks. IETF RFC 1305 (1992), Network Time Protocol (Version 3) Specification, Implementation and Analysis. IETF RFC 1119 (1989), Network Time Protocol. IETF RFC 1889 (1996), RTP: A Transport Protocol for Real-Time Applications. IETF RFC 1890 (1996), RTP Profile for Audio
29、 and Video Conferences with Minimal Control. IETF RFC 2474 (1998), Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers. IETF RFC 3168 (2001), The Addition of Explicit Congestion Notification (ECN) to IP. IETF RFC 3260 (2002), New Terminology and Clarifications for
30、 Diffserv. IETF RFC 3261 (2002), SIP: Session Initiation Protocol. IETF RFC 3414 (2002), User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3). IETF RFC 3415 (2002), View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP). I
31、ETF RFC 3611 (2003), RTP Control Protocol Extended Reports (RTCP XR). 3 Terms and definitions This Recommendation defines the following terms: 3.1 IPCablecom: An ITU-T project that includes an architecture and a series of Recommendations that enable the delivery of real-time services over the cable
32、television networks using cable modems. 3.2 cable modem: A cable modem is a layer two termination device that terminates the customer end of the DOCSIS connection. 3.3 managed IP network: An IP network, managed by a single entity for the purpose of transporting IPCablecom signalling and media packet
33、s. 3.4 managed IP backbone: A Managed IP network that is used for interconnecting IPCablecom domains. 4 Abbreviations and conventions 4.1 Abbreviations This Recommendation uses the following abbreviations: ANC Announcement Controller ANP Announcement Player ANS Announcement Server CM Cable Modem ITU
34、-T Rec. J.160 (11/2005) 3 CMS Call Management Server CPE Customer Premises Equipment DHCP Dynamic Host Configuration Protocol DNS Domain Name System DTMF Dual Tone Multi-Frequency FQDN Fully Qualified Domain Name GC Gate Controller HFC Hybrid Fibre/Coax HTTP HyperText Transfer Protocol IEEE Institut
35、e of Electrical and Electronic Engineers IETF Internet Engineering Task Force IP Internet Protocol IPsec IP security ISTP Internet Signalling Transport Protocol ISUP Integrated Services Digital Network User Part MAC Media Access Control MF Multi-Frequency MG Media Gateway MGC Media Gateway Controlle
36、r MIB Management Information Base MMH Multilinear Modular Hash MTA Media Terminal Adapter MTP Message Transfer Part NAT Network Address Translator NCS Network-Based Call Signalling OSS Operations Support System PSTN Public Switched Telephone Network QoS Quality of Service RKS Record Keeping Server R
37、TP Real-Time Transfer Protocol SA Source Address SCCP Signalling Connection Control Part SG Signalling Gateway SID System IDentification number SNMP Simple Network Management Protocol TCAP Transaction Capabilities Application Part TFTP Trivial File Transfer Protocol 4 ITU-T Rec. J.160 (11/2005) TGCP
38、 Trunking Gateway Control Protocol TGS Ticket Granting Server ToS Type of Service UDP User Datagram Protocol 4.2 Conventions If this Recommendation is implemented, the key words “MUST“ and “SHALL“ as well as “REQUIRED“ are to be interpreted as indicating a mandatory aspect of this Recommendation. Th
39、e keywords indicating a certain level of significance of particular requirements that are used throughout this Recommendation are summarized. “MUST“ This word or the adjective “REQUIRED“ means that the item is an absolute requirement of this Recommendation. “MUST NOT“ This phrase means that the item
40、 is an absolute prohibition of this Recommendation. “SHOULD“ This word or the adjective “RECOMMENDED“ means that there may exist valid reasons in particular circumstances to ignore this item, but the full implications should be understood and the case carefully weighed before choosing a different co
41、urse. “SHOULD NOT“ This phrase means that valid reasons may exist in particular circumstances when the listed behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label. “MAY“ This wo
42、rd or the adjective “OPTIONAL“ means that this item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because it enhances the product, for example; another vendor may omit the same item. 5 IPCablecom 5.1 IPCablecom architecture framework At
43、a very high level, the IPCablecom architecture contains three networks: the “DOCSIS HFC access network“, the “Managed IP network“ and the PSTN. The Cable Modem Termination System (CMTS) provides connectivity between the “DOCSIS HFC access network“ and the “Managed IP network“. Both the Signalling Ga
44、teway (SG) and the Media Gateway (MG) provide connectivity between the “Managed IP network“ and the PSTN. The reference architecture for IPCablecom is shown in Figure 1. The DOCSIS HFC access network provides high-speed, reliable, and secure transport between the customer premise and the cable heade
45、nd. This access network provides all DOCSIS capabilities including Quality of Service. The DOCSIS HFC access network includes the following functional components: the Cable Modem (CM), the Multimedia Terminal Adapter (MTA), and the Cable Modem Termination System (CMTS). The Managed IP network serves
46、 several functions. First, it provides interconnection between the basic IPCablecom functional components responsible for signalling, media, provisioning, and the establishment of quality of service on the access network. In addition, the managed IP network provides long-haul IP connectivity between
47、 other Managed IP and DOCSIS HFC networks. The Managed IP network includes the following functional components: Call Management ITU-T Rec. J.160 (11/2005) 5 Server (CMS), several Operations Support System (OSS) back-office servers, Signalling Gateway (SG), Media Gateway (MG), and Media Gateway Contr
48、oller (MGC). The individual network components that are shown in Figure 1 are described in detail in clause 6. Figure 1/J.160 IPCablecom reference architecture 5.2 IPCablecom zones and domains An IPCablecom zone consists of the set of MTAs in one or more DOCSIS HFC access networks that are managed b
49、y a single functional CMS as shown in Figure 2. Interfaces between functional components within a single zone and between zones (e.g., CMS CMS) are defined in the IPCablecom Recommendations. 6 ITU-T Rec. J.160 (11/2005) Figure 2/J.160 Zones and administrative domains An IPCablecom domain is made up of one or more IPCablecom zones that are operated and managed by a single administrative entity. An IPCablecom domain may also be referred to as an administrative domain. 5.3 IPCablecom Recommendations Table 1/J.160 IPCablecom Recomme
