1、 International Telecommunication Union ITU-T J.460.4TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (06/2008) SERIES J: CABLE NETWORKS AND TRANSMISSION OF TELEVISION, SOUND PROGRAMME AND OTHER MULTIMEDIA SIGNALS IPCablecom2 residential SIP telephony: Embedded-user equipment provisioning specificatio
2、n Recommendation ITU-T J.460.4 Rec. ITU-T J.460.4 (06/2008) iRecommendation ITU-T J.460.4 IPCablecom2 residential SIP telephony: Embedded-user equipment provisioning specification Summary Recommendation ITU-T J.460.4 specifies how the IPCablecom2 E-UE provisioning framework can be used to configure
3、and manage embedded UEs (E-UEs) supporting the IPCablecom2 residential SIP telephony (RST) application. Source Recommendation ITU-T J.460.4 was approved on 13 June 2008 by ITU-T Study Group 9 (2005-2008) under Recommendation ITU-T A.8 procedure. ii Rec. ITU-T J.460.4 (06/2008) FOREWORD The Internati
4、onal Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operat
5、ing 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 the topics for study by the ITU-T study groups which, in turn, pro
6、duce 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 are prepared on a collaborative basis with ISO and IEC. NOTE In th
7、is 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 Recommendation may contain certain mandatory provisions (to ensure e.g. int
8、eroperability 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 used to express requirements. The use of such words does not suggest
9、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 Intellectual Property Right. ITU takes no position concerning the evidence
10、, 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 notice of intellectual property, protected by patents, which may b
11、e 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/. ITU 2009 All rights reserved. No part of this publication may be re
12、produced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T J.460.4 (06/2008) iii CONTENTS Page 1 Scope 1 1.1 Introduction and purpose 1 2 References. 1 2.1 Normative references 1 2.2 Informative References 2 2.3 Reference Acquisition 2 3 Terms and Definitions 2 4 Abbr
13、eviations, acronyms and conventions. 2 4.1 Abbreviations and Acronyms . 2 4.2 Conventions 3 5 Overview 3 5.1 Residential SIP Telephony . 3 5.2 E-UE Provisioning Framework 4 5.3 RST E-UE. 4 6 IPCablecom RST E-UE Architecture and Requirements . 4 6.1 eUE Provisioning Framework Architecture . 4 6.2 RST
14、 E-UE Provisioning Components 5 6.3 RST E-UE Provisioning Flows, Configuration and Management . 7 6.4 RST Data Models . 7 6.5 RST E-UE Additional Features 7 Annex A IPCablecom RST Configuration Modules. 8 A.1 RST. 8 Annex B IPCablecom EDVA Configuration Module. 47 B.1 E-DVA 47 Rec. ITU-T J.460.4 (06
15、/2008) 1 Recommendation ITU-T J.460.4 IPCablecom2 residential SIP telephony: Embedded-user equipment provisioning specification 1 Scope 1.1 Introduction and purpose This Recommendation specifies how the IPCablecom2 E-UE Provisioning Framework can be used to configure and manage Embedded UEs (E-UEs)
16、supporting the IPCablecom2 Residential SIP Telephony (RST) application. The IPCablecom2 architecture provides a generic Provisioning Framework for E-UEs, but requires IPCablecom2 application efforts such as RST to specify application-specific requirements and data models. This Recommendation specifi
17、es such requirements and the data model for the IPCablecom2 RST application. It also specifies the requirements and a data model for E-DVAs, a specific E-UE type specified by IPCablecom2. It is an important objective of this work that interoperability between IPCablecom 2.0 and 3GPP IMS is provided.
18、 IPCablecom 2.0 is based upon 3GPP IMS, but includes additional functionality necessary 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 co
19、ntribute to IMS developments in 3GPP, with the aim of alignment of 3GPP IMS and IPCablecom 2.0. NOTE The structure and content of this Recommendation have been organized for ease of use by those familiar with the original source material; as such, the usual style of ITU-T recommendations has not bee
20、n applied. 2 References 2.1 Normative 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 oth
21、er references are 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 re
22、ference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. E-DVA Recommendation ITU-T J.460.2: IPCablecom2 Residential SIP Telephony: Embedded Digital Voice Adapter (E-DVA) Specification. EUE-DATA Recommendation ITU-T J.370: IPCablec
23、om2 embedded user equipment Provisioning Data Model Specification. EUE-PROV Recommendation ITU-T J.369: IPCablecom2 E-UE Provisioning framework Specification. PKT24.229 Recommendation ITU-T J.366.4 (2006): IPCablecom2 IP Multimedia Subsystem (IMS): Session Initiation Protocol (SIP) and Session Descr
24、iption Protocol (SDP) Stage 3 specification. RSTF Recommendation ITU-T J.460.1: IPCablecom2 Residential SIP Telephony: Feature Specification. 2 Rec. ITU-T J.460.4 (06/2008) RFC2863 IETF RFC 2863, The Interfaces Group MIB, June 2000. 2.2 Informative References This Recommendation uses the following i
25、nformative reference ARCH-FRM Recommendation ITU-T J.360: IPCablecom2 architecture framework. 2.3 Reference Acquisition Internet Engineering Task Force (IETF) Secretariat, 46000 Center Oak Plaza, Sterling, VA 20166, Phone +1-571-434-3500, Fax +1-571-434-3535, http:/www.ietf.org/. 3 Terms and Definit
26、ions This Recommendation uses the following terms: 3.1 configuration: Configuration is the process of defining and propagating data to network elements for providing services. 3.2 data model: An abstract model that describes representation of data in a system. 3.3 embedded user equipment (E-UE): A s
27、ingle physical device embedded with an eDOCSIS-compliant DOCSIS Cable Modem and an IPCablecom eUE. 3.4 management: Management refers to the protocols, methodologies and interfaces that enable oversight services in a Service Provider Network. 3.5 eCM: The logical DOCSIS CM component of a E-UE, compli
28、es with DOCSIS, eDOCSIS and IPCablecom requirements. 3.6 eUE: The logical IPCablecom UE component of an E-UE, complies with eSAFE and IPCablecom requirements. 3.7 management information base (MIB): The description of the data items used by the Network Management for management and configuration of t
29、he IPCablecom compliant E-UE. Such description is done based on the formal meta-language SMI defined by the corresponding IETF standards. 3.8 network management: The functions related to the management of data across the network. 3.9 provisioning: Provisioning refers to the processes involved in the
30、 initialization of user attributes and resources to provide services to a User. This involves protocols, methodologies, and interfaces to network elements such as: Order Entry and Workflow Systems that carry out business processes, Operational Support Elements that handle network resources, Applicat
31、ion Servers that offer services and Use Equipment that offer services. 4 Abbreviations, acronyms and conventions 4.1 Abbreviations and Acronyms This Recommendation uses the following abbreviations and acronyms: CM DOCSIS Cable Modem. A DOCSIS compliant devise which provides data transport connectivi
32、ty from RFI to IP networks DOCSISData-Over-Cable Service Interface Specifications E-DVA Embedded Digital Voice Adaptor MIB Management Information Base Rec. ITU-T J.460.4 (06/2008) 3 RFC Request for Comments. Technical policy documents approved by the IETF which are available on the World Wide Web at
33、 http:/ri.reston.va.us/rfc.html RFI Radio Frequency Interface RST Residential SIP Telephony SNMP Simple Network Management Protocol 4.2 Conventions Throughout this Recommendation, the words that are used to define the significance of particular requirements are capitalized. These words are: “MUST“ T
34、his word means that the item is an absolute requirement of this Recommendation. “MUST NOT“ This phrase means that the item is an absolute prohibition of this Recommendation. “SHOULD“ This word means that there may exist valid reasons in particular circumstances to ignore this item, but the full impl
35、ications should be understood and the case carefully weighed before choosing a different course. “SHOULD NOT“ This phrase means that there may exist valid reasons in particular circumstances when the listed behavior is acceptable or even useful, but the full implications should be understood and the
36、 case carefully weighed before implementing any behavior described with this label. “MAY“ This word 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
37、the same item. 5 Overview IPCablecom2 is a cable industry specification effort designed to support the convergence of voice, video, data, and mobility technologies. The IPCablecom2 architecture describes a set of functional groups and logical entities, as well as a set of interfaces that support the
38、 information flows exchanged between entities. For more information about IPCablecom2, please refer to the IPCablecom2 Architecture Framework Technical Report ARCH-FRM. As part of these efforts, IPCablecom2 specifies applications built upon the IPCablecom architecture. One such application is RST. T
39、his Recommendation describes the configuration and management requirements applicable to Embedded User Equipment (E-UE) supporting the RST application. Within the context of this Recommendation, any reference to an E-UE (or eUE) needs to be interpreted as an E-UE (or eUE) that supports the RST appli
40、cation, sometimes referred to as an RST E-UE. For more information on the RST application, please refer to RSTF. Specifically, this Recommendation covers the following areas: Configuration and Management requirements for E-UEs supporting RST, including E-DVA specific requirements, The RST Applicatio
41、n Data Model, The E-DVA Data Model for Configuration and Management. 5.1 Residential SIP Telephony The IPCablecom2 RST Feature specification specifies an implementation of common residential telephony features in an IPCablecom network, including, but not limited to: called ID, call 4 Rec. ITU-T J.46
42、0.4 (06/2008) forwarding, hold, transfer, three-way calling, emergency calling, and operator service. For more information, please refer to RSTF. 5.2 E-UE Provisioning Framework The IPCablecom2 E-UE Provisioning Framework Specification EUE-PROV, together with the E-UE Provisioning Data Models Specif
43、ication EUE-DATA, specifies interfaces, protocols, and data models to support configuration and management of E-UEs in an IPCablecom network. Those documents require IPCablecom application specifications, such as RST, to utilize these interfaces and extend the data models as required to support the
44、specified features. 5.3 RST E-UE The E-UE, by definition, is an embedded IPCablecom2 device, as specified in EUE-PROV. The RST E-UE is an E-UE that supports the IPCablecom2 RST application. RST E-UEs require RST specific data to be configured, and have additional requirements, as specified in this R
45、ecommendation. 6 IPCablecom RST E-UE Architecture and Requirements This clause presents the normative requirements for RST E-UE Provisioning, using the IPCablecom E-UE Provisioning Framework. It includes references to the framework, and any necessary enhancements to support the RST application. For
46、more information on IPCablecom E-UE Provisioning Framework please refer to EUE-PROV. The E-UE consists of two components: the eCM and the eUE. For more information on the eCM configuration and management requirements for IPCablecom, please refer to EUE-PROV. The eUE Provisioning Framework Architectu
47、re, based on the Provisioning Framework is specified in Clause 6.1. The component requirements and other enhancements are listed in the following sub-clauses. 6.1 eUE Provisioning Framework Architecture Figure 1 represents the network components and interfaces that form the eUE Provisioning Framewor
48、k, the basis for RST eUE provisioning. Figure 1 E-UE Provisioning Components and Interfaces Rec. ITU-T J.460.4 (06/2008) 5 6.2 RST E-UE Provisioning Components This clause details the network components that utilize the interfaces specified in Clause 6.1, and the associated requirements. It also sum
49、marizes the additional requirements required by this framework for the DOCSIS elements to support the framework specified by this Recommendation. 6.2.1 RST E-UE The RST E-UE MUST comply with all the E-UE requirements specified in EUE-PROV. 6.2.1.1 eCM An eCM embedded within the RST E-UE MUST comply with all the eCM requirements specified in EUE-PROV and any additional requirements specified in this Recommendation, such as impact analysis reporting. 6.2.1.2 eUE For an eUE embedded within the RST E-UE, the following requireme
