ITU-T J 360-2006 IPCablecom2 architecture framework《个人间电缆通信(IPCablecom)2的架构框架》.pdf

《ITU-T J 360-2006 IPCablecom2 architecture framework《个人间电缆通信(IPCablecom)2的架构框架》.pdf》由会员分享，可在线阅读，更多相关《ITU-T J 360-2006 IPCablecom2 architecture framework《个人间电缆通信(IPCablecom)2的架构框架》.pdf（126页珍藏版）》请在麦多课文档分享上搜索。

1、 International Telecommunication Union ITU-T J.360TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (11/2006) SERIES J: CABLE NETWORKS AND TRANSMISSION OF TELEVISION, SOUND PROGRAMME AND OTHER MULTIMEDIA SIGNALS IPCablecom IPCablecom2 architecture framework ITU-T Recommendation J.360 ITU-T Rec. J.360

2、(11/2006) i ITU-T Recommendation J.360 IPCablecom2 architecture framework Summary ITU-T Recommendation J.360 provides the architectural framework and technical overview for the expansion of IPCablecom into multimedia. Source ITU-T Recommendation J.360 was approved on 29 November 2006 by ITU-T Study

3、Group 9 (2005-2008) under the ITU-T Recommendation A.8 procedure. ii ITU-T Rec. J.360 (11/2006) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanen

4、t 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 four years, establishes

5、 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, the necessary standards

6、 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. However, the Recommen

7、dation 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 negative equivalents are us

8、ed 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 use of a claimed Intelle

9、ctual 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 Recommendation, ITU had not received

10、 notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/.

11、ITU 2007 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.360 (11/2006) iii CONTENTS Page 1 Scope and overview 1 1.1 Scope 1 1.2 IPCablecom2 overview 1 2 References. 2 2.1 Normative references 2 2.2

12、 Informative references 2 3 Terms and definitions . 3 4 Abbreviations and acronyms 3 5 IPCablecom2 5 5.1 Relationship with the 3GPP IMS . 5 5.2 Overview 6 5.3 IPCablecom releases and organization. 10 5.4 IPCablecom2 design considerations. 13 6 IPCablecom functional components. 16 6.1 Local network.

13、16 6.2 Access network. 16 6.3 Edge 16 6.4 Core 17 6.5 IPCablecom multimedia . 19 6.6 Application . 19 6.7 Interconnect 20 6.8 Operational support systems. 20 7 Protocol interfaces and reference points. 22 7.1 Signalling and service control 22 7.2 Subscriber data . 23 7.3 Quality of service . 24 7.4

14、Network address translation (NAT) and firewall traversal 26 7.5 Media coding and transport 28 7.6 Provisioning, activation, configuration and management 28 7.7 Network accounting and usage. 30 7.8 Security. 32 7.9 Lawful intercept 34 7.10 Control point discovery 36 Appendix I SIP signalling overview

15、 . 37 I.1 Introduction and purpose 37 I.2 References 38 I.3 Terms and definitions. 39 I.4 Abbreviations and acronyms 40 iv ITU-T Rec. J.360 (11/2006) Page I.5 IPCablecom2 SIP signalling. 40 I.6 IPCablecom2 IMS requirements 46 Appendix II Quality of service architecture technical overview . 66 II.1 I

16、ntroduction 66 II.2 References 66 II.3 Terms and definitions. 67 II.4 Abbreviations and acronyms 67 II.5 QoS requirements and scope 67 II.6 QoS architecture framework. 68 II.7 Architecture description . 71 II.8 Example procedures . 74 Appendix III IPCablecom2 security overview 77 III.1 Introduction

17、77 III.2 References 77 III.3 Terms and definitions. 78 III.4 Abbreviations and acronyms 78 III.5 IPCablecom2 security. 78 III.6 IPCablecom security requirements. 89 Appendix IV IPCablecom2 home subscriber server (HSS) overview 105 Appendix V IPCablecom2 NAT and firewall traversal overview 105 V.1 In

18、troduction 105 V.2 References 105 V.3 Terms and definitions. 105 V.4 Abbreviations and acronyms 106 V.5 IPCablecom2 NAT requirements and scope 106 V.6 NAT background 107 V.7 IPCablecom2 NAT architecture . 110 V.8 Architecture description . 112 Appendix VI IPCablecom2 IPv6 and IPv4 strategy overview

19、. 117 ITU-T Rec. J.360 (11/2006) 1 ITU-T Recommendation J.360 IPCablecom2 architecture framework 1 Scope and overview 1.1 Scope The initial release of IPCablecom ITU-T J.160-J.178 provides for telephony. IPCablecom multimedia ITU-T J.179 creates a bridge that allows for the expansion of IPCablecom i

20、nto a full range of multimedia services. This Recommendation provides the architectural framework, technical background and project organization for the second release of the IPCablecom family of Recommendations providing for the extension into the multimedia domain. 1.2 IPCablecom2 overview IPCable

21、com2 is a cable industry effort designed to support the convergence of voice, video, data and mobility technologies. There are tens of millions of cable broadband customers, and the capability of the network to provide innovative services beyond high-speed Internet access is ever-increasing. In part

22、icular, real-time communication services based on the IP protocols, such as Voice over Internet Protocol (VoIP), are rapidly evolving and consumers are embracing a wide-range of client devices and media types. It is expected that new technologies, such as Video over IP communications and the ability

23、 to display voice and video mail message notifications on a TV-set, will change the way communication and entertainment services are offered. These cutting edge technologies will present exciting new opportunities for cable operators to offer high-value services to consumers in a cost-effective mann

24、er. IPCablecom2 defines an architecture and a set of open interfaces that leverage emerging communications technologies, such as the IETF session initiation protocol (SIP) IETF RFC 3261, to support the rapid introduction of new IP-based services onto the cable network. A modular approach allows oper

25、ators to flexibly deploy network capabilities as required by their specific service offerings, while maintaining interoperability across a variety of devices from multiple suppliers. Intentionally non service-specific, the platform should provide the basic capabilities necessary for operators to dep

26、loy services in areas such as: Enhanced Residential VoIP and IP Video Communications Capabilities such as video telephony; call treatment based on presence, device capability, identity; and Click to dial type of features. Cross Platform Feature Integration Capabilities such as callers name and numbe

27、r identification on the TV and call treatment from the TV. Mobility services and Integration with Cellular and Wireless Networks Capabilities such as call handoff and roaming between IPCablecom VoIP over WiFi and wireless-cellular networks; voice-mail integration; and single E.164 number (e.g., tele

28、phone number). Multimedia Applications Capabilities such as QoS-enabled audio and video streaming. Commercial Services Extensions Capabilities such as PBX extension; IP Centrex Services to small to medium-sized businesses; and VoIP trunking for enterprise IP-PBXs. Residential SIP Telephony Extension

29、s Capabilities such as traditional telephony features (e.g., call waiting, caller ID), operator services, and emergency services. As noted above, the architecture is designed to support a broad range of services. The IPCablecom2 set of Recommendations define a base architecture, and the components a

30、nd generic requirements necessary to meet a large number of applications and services. Specific applications and services 2 ITU-T Rec. J.360 (11/2006) rely on this base architecture, but are specified in separate releases. The base specifications should be able to accommodate different applications

31、and services with very few, if any, changes. This release of IPCablecom is based on Release 6 of the IP multimedia subsystem (IMS) as developed by the 3rd generation partnership project (3GPP). The IMS is a SIP-based architecture for providing multimedia services. IPCablecom2 defines enhancements to

32、 the IMS in order to ensure IPCablecom addresses requirements that are not already addressed by the IMS. It is an important objective of this work that interoperability between IPCablecom 2.0 and 3GPP IMS is provided. IPCablecom 2.0 is based upon 3GPP IMS, but includes additional functionality neces

33、sary to meet the requirements of cable operators. Recognizing developing converged solutions for wireless, wireline, and cable, it is expected that further development of IPCablecom 2.0 will continue to monitor and contribute to IMS developments in 3GPP, with the aim of alignment of 3GPP IMS and IPC

34、ablecom 2.0. IPCablecom2 leverages other open standards and specifications wherever possible. 2 References 2.1 Normative references None. 2.2 Informative references ITU-T J.160 ITU-T Recommendation J.160 (2005), Architectural framework for the delivery of time-critical services over cable television

35、 networks using cable modems. ITU-T J.170 ITU-T Recommendation J.170 (2005), IPCablecom security specification. ITU-T J.171.1 ITU-T Recommendation J.171.1 (2005), IPCablecom trunking gateway control protocol (TGCP): Profile 1. ITU-T J.178 ITU-T Recommendation J.178 (2005), IPCablecom CMS to CMS sign

36、alling. ITU-T J.179 App.I ITU-T Recommendation J.179 (2005), IPCablecom support for multimedia. Appendix I: Background information. ITU-T J.361 ITU-T Recommendation J.361 (2006), IPCablecom2 codec media. ITU-T J.362 ITU-T Recommendation J.362 (2006), IPCablecom2 control point discovery. ITU-T J.363

37、ITU-T Recommendation J.363 (2006), IPCablecom2 data collection to support accounting. ITU-T J.364 ITU-T Recommendation J.364 (2006), IPCablecom2 provisioning, activation, configuration and management. ITU-T J.365 ITU-T Recommendation J.365 (2006), IPCablecom2 application manager interface. ES-DCI Pa

38、cketCable Electronic Surveillance Delivery Function to Collection Function Interface Specification, PKT-SP-ES-DCI-I01-060914 (2006), Cable Television Laboratories, Inc. ES-INF PacketCable Electronic Surveillance Intra-Network Functions Specification, PKT-SP-ES-INF-I01-060406, 6 April 2006, Cable Tel

39、evision Laboratories, Inc. IETF RFC 3261 IETF RFC 3261 (2002), SIP: Session Initiation Protocol. ITU-T Rec. J.360 (11/2006) 3 TS 23.002 3GPP 23.002 v6.10.0, Network Architecture, December 2005. 3 Terms and definitions This Recommendation uses the following terms and definitions: 3.1 contact address:

40、 The URI of a user agent on the network. Contact addresses, in the context of IPCablecom are often, but not always, addresses used to deliver requests to a specific user agent. 3.2 E.164: E.164 is an ITU-T Recommendation which defines the international public telecommunication numbering plan used in

41、 the PSTN and other data networks. 3.3 headend: The central location on the cable network that is responsible for injecting broadcast video and other signals in the downstream direction. 3.4 IMS delta specifications: Suite of 3GPP IMS specifications modified to reflect cable-specific deltas necessar

42、y to comply with IPCablecom. 3.5 IPCablecom multimedia: An application agnostic QoS architecture for services delivered over DOCSIS networks. 3.6 private identity: See private user identity. 3.7 private user identity: Used, for example, for registration, authorization, administration and accounting

43、purposes. A private user identity is associated with one or more public user identities. 3.8 public identity: See public user identity. 3.9 public user identity: Used by any user for requesting communications to other users. 3.10 SIP user agent: Same as user agent. 3.11 server: A network element tha

44、t receives requests in order to service them and sends back responses to those requests. Examples of servers are proxies, user agent servers, redirect servers, and registrars. 3.12 subscriber: An entity (comprising one or more users) that is engaged in a subscription with a service provider. 3.13 su

45、bscription: A contract for service(s) between a user and a service provider. 3.14 user: A person who, in the context of this Recommendation, uses a defined service or invokes a feature on a UE. 3.15 user agent (UA): A SIP user agent as defined by IETF RFC 3261. 3.16 multimedia session: A set of mult

46、imedia senders and receivers and the data streams flowing from senders to receivers. A multimedia conference is an example of a multimedia session. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: 3GPP 3rd Generation Partnership Project ALG Application

47、Layer Gateway AM Application Manager AS Application Server BGCF Breakout Gateway Control Function CDF Charging Data Function CDR Call Detail Record 4 ITU-T Rec. J.360 (11/2006) CM Cable Modem CMS Call Management Server CMTS Cable Modem Termination System CPE Customer Premises Equipment CSCF Call Ses

48、sion Control Function DHCP Dynamic Host Configuration Protocol DNS Domain Name System DOCSIS Data-Over-Cable Service Interface Specification EMS Element Management System E-MTA Embedded Multimedia Terminal Adapter ENUM E.164 Number Mapping ESP Encapsulating Security Payload FQDN Fully Qualified Doma

49、in Name FW Firewall GRUU Globally Routable User Agent URI HSS Home Subscriber Server HTTP Hyper Text Transfer Protocol ICE Interactive Connectivity Establishment I-CSCF Interrogating Call Session Control Function IMS IP Multimedia Subsystem IP Internet Protocol IPSec Internet Protocol Security MG Media Gateway MGC Media Gateway Controller NA(P)T Network Address and Port Translation; used interchangeably with NAT NAT Network Address Translation NCS Network-based Call Signalling NMS Network Managemen