1、 International Telecommunication Union ITU-T J.370TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (06/2008) SERIES J: CABLE NETWORKS AND TRANSMISSION OF TELEVISION, SOUND PROGRAMME AND OTHER MULTIMEDIA SIGNALS IPCablecom IPCablecom2 embedded user equipment provisioning data model specification Recom
2、mendation ITU-T J.370 Rec. ITU-T J.370 (06/2008) i Recommendation ITU-T J.370 IPCablecom2 embedded user equipment provisioning data model specification Summary Recommendation ITU-T J.370 presents the data element definitions and associated requirements for use with the IPCablecom2 embedded user equi
3、pment (E-UE) Provisioning Framework. Specifically, it defines data to be used for configuration and management of E-UEs, and associated users. Source Recommendation ITU-T J.370 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.3
4、70 (06/2008) FOREWORD The International 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 respons
5、ible 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 the topics for study by the ITU
6、-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 are prepared on a collaborative
7、 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 Recommendation may contain certain manda
8、tory 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 used to express requirements. The
9、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 Intellectual Property Right. ITU takes
10、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 notice of intellectual property
11、, 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/. ITU 2009 All rights reserved. No
12、 part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T J.370 (06/2008) iii CONTENTS Page 1 Scope 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 Ab
13、breviations, acronyms and conventions. 3 4.1 Abbreviations and Acronyms . 3 4.2 Conventions 3 5 Technical Overview 3 5.1 Embedded User Equipment (E-UE) . 4 5.2 E-UE Provisioning Framework 4 5.3 E-UE Provisioning Data Model 4 6 E-UE Provisioning MIBs Framework Requirements. 5 6.1 eCM MIB Requirements
14、 6 6.3 Configuration Data Element Requirements 10 6.4 Management Event Reporting Requirements. 11 Annex A IPCablecom eUE Common Modules 12 A.1 Textual Conventions MIB Module. 12 Annex B IPCablecom eUE Device Configuration Modules. 18 B.1 Device Configuration MIB Module . 18 B.2 User Configuration MI
15、B Module . 29 Annex C IPCablecom eUE Provisioning and Management Modules 40 C.1 Provisioning and Management MIB Module. 40 C.2 Management Event MIB Module. 46 Annex D IPCablecom eUE Additional Modules 49 D.1 Certificate Bootstrapping XML Schema 49 Appendix I Illustrative IPCablecom Deployment Exampl
16、es 51 I.1 Example 1: Deployment with multiple Users, and one IPCablecom Application . 51 I.2 Example 2: Deployment with multiple Users, and multiple IPCablecom Applications 52 Rec. ITU-T J.370 (06/2008) 1 Recommendation ITU-T J.370 IPCablecom2 embedded user equipment provisioning data model specific
17、ation 1 Scope This Recommendation presents the data element definitions and associated requirements for use with the IPCablecom2 E-UE Provisioning Framework. Specifically, it defines data to be used for configuration and management of E-UEs, and associated users. For more information on the IPCablec
18、om2 E-UE Provisioning Framework, please refer to PKT-EUE-PROV. This Recommendation does not consider IPCablecom2 application specific data within its scope. IPCablecom2 application specifications are expected to specify such data. It is an important objective of this work that interoperability betwe
19、en IPCablecom 2.0 and 3GPP IMS is provided. 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 IPC
20、ablecom 2.0 will continue to monitor and contribute 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
21、 style of ITU-T recommendations has not been 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 indica
22、ted were valid. All Recommendations and other 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 Rec
23、ommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. CL-MIB-BB Recommendation ITU-T J.199: Battery backup for cable-based devices. DOCSIS-RFI Recommendation ITU-T J.112: Transmission s
24、ystems for interactive cable television services. eDOCSIS Recommendation ITU-T J.126: Embedded Cable Modem device specification. PKT-EUE-PROV Recommendation ITU-T J.369: IPCablecom2 E-UE Provisioning Specification. PKT-SP-PROV1.5 Recommendation ITU-T J.167: Media terminal adapter (MTA) device provis
25、ioning requirements for the delivery of real-time services over cable television networks using cable modems. PKT-MEM1.5 Recommendation ITU-T J.172: IPCablecom management event mechanism. RFC2863 IETF RFC 2863, The Interfaces Group MIB, June 2000. RFC3410 IETF RFC 3410, Introduction and Applicabilit
26、y Statements for Internet Standard Management Framework, December 2002. 2 Rec. ITU-T J.370 (06/2008) RFC3412 IETF RFC 3412/STD0062, Message Processing and Dispatching for the Simple Network Management Protocol (SNMP), December 2002. RFC3413 IETF RFC 3413/STD0062, Simple Network Management Protocol (
27、SNMP) Applications, December 2002. RFC3414 IETF RFC 3414/STD0062, User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3), December 2002. RFC3415 IETF RFC 3415/STD0062, View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP),
28、December 2002. RFC3418 IETF RFC 3418, Management Information Base (MIB) for the Simple Network Management Protocol (SNMP). RFC3665 IETF RFC 3665, Definitions of Managed Objects for the Ethernet-like Interface Types, September 2003. RFC4113 IETF RFC 4113, Management Information Base for the User Data
29、gram Protocol (UDP), June 2005. RFC4293 IETF RFC 4293, Management Information Base for the Internet Protocol (IP), April 2006. IETF STD58 IETF RFC 2578/STD0058, Structure of Management Information Version 2 (SMIv2), April 1999. IETF STD62 IETF RFC 3411/STD0062, An Architecture for Describing Simple
30、Network Management Protocol (SNMP) Management Frameworks, December 2002. 2.2 Informative References This Recommendation uses the following informative reference. ARCH-FRM TR Recommendation ITU-T J.160: Architectural framework for the delivery of time-critical services over cable television networks
31、using cable modems. 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 Definitions This Recommendation uses the following terms: 3.1 eCM: The logical DO
32、CSIS CM component of a E-UE, complies with DOCSIS, eDOCSIS and IPCablecom requirements. 3.2 eUE: The logical IPCablecom UE component of an E-UE, complies with eSAFE and IPCablecom requirements. 3.3 embedded user equipment (E-UE): A single physical device embedded with an eDOCSIS-compliant DOCSIS Cab
33、le Modem and an IPCablecom eUE. 3.4 management information base: The description of the data items used by the Network Management for management and configuration of the IPCablecom compliant E-UE. Such description is done based on the formal meta-language SMI defined by the corresponding IETF standa
34、rds. 3.5 network management: The functions related to the management of data across the network. Rec. ITU-T J.370 (06/2008) 3 4 Abbreviations, acronyms and conventions 4.1 Abbreviations and Acronyms This Recommendation uses the following abbreviations: CM DOCSIS Cable Modem a DOCSIS-compliant devise
35、 which provides data transport connectivity from RFI to IP networks DOCSISData-Over-Cable Service Interface Specifications MIB Management Information Base OID Object Identifier. The sequence of integer positive numbers uniquely identifying the position of each MIB Object in the MIB Hierarchy RFC Req
36、uest for Comments. Technical policy documents approved by the IETF which are available on the World Wide Web at http:/ri.reston.va.us/rfc.html SNMP Simple Network Management Protocol UDP User Datagram Protocol. A connectionless protocol built upon Internet Protocol (IP) VACM View-based Access Contro
37、l Model 4.2 Conventions Throughout this Recommendation, the words that are used to define the significance of particular requirements are capitalized. These words are: “MUST“ This word means that the item is an absolute requirement of this Recommendation. “MUST NOT“ This phrase means that the item i
38、s 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 implications should be understood and the case carefully weighed before choosing a different course. “SHOULD NOT“ This phrase me
39、ans 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 case carefully weighed before implementing any behavior described with this label. “MAY“ This word means that this item is
40、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 Technical Overview IPCablecom2 is a cable industry specification effort designed to support the convergence
41、 of voice, video, data, and mobility technologies. This Recommendation is part of the IPCablecom2 set of specifications and technical reports that define the base architecture and specifies the data elements required to configure and manage E-UEs, associated users and applications, using the IPCable
42、com2 E-UE Provisioning Framework. For more information about IPCablecom2, please refer to the IPCablecom2 Architecture Framework Technical Report ARCH-FRM TR. For more information on the IPCablecom2 E-UE Provisioning Framework, please refer to PKT-EUE-PROV. 4 Rec. ITU-T J.370 (06/2008) The IPCableco
43、m2 E-UE Provisioning Framework relies on SNMP, as specified in IETF STD62, for configuration and management. The data is specified using Structure of Management Information, Version 2 (SMIv2) Management Information Bases (MIBs), as specified in IETF STD58. Thus, this Recommendation specifies the con
44、figuration and management MIBs for use with the IPCablecom2 E-UE Provisioning Framework. In this Recommendation, the term “DOCSIS“ is used to refer to DOCSIS version 1.1 or later, unless explicitly specified otherwise. Additionally, all references to IPCablecom within this Recommendation are assumed
45、 to be IPCablecom2, unless stated otherwise. 5.1 Embedded User Equipment (E-UE) The E-UE is a single physical device embedded with an eDOCSIS-compliant DOCSIS Cable Modem (eCM) and an eUE that complies with eDOCSIS eSAFE and IPCablecom UE requirements. For more information on E-UEs please refer to P
46、KT-EUE-PROV. 5.2 E-UE Provisioning Framework The E-UE Provisioning Framework is an IPCablecom2 configuration and management framework based on the IPCablecom 1.5 Device Provisioning specification. For more information on the E-UE Provisioning Framework, please refer to PKT-EUE-PROV. This Recommendat
47、ion is to be used in conjunction with the E-UE Provisioning Framework, and also relies on the IPCablecom 1.5 Device Provisioning specification. For more information on the latter, please refer to PKT-SP-PROV1.5. 5.3 E-UE Provisioning Data Model The E-UE Provisioning Data Model serves eCMs, eUEs, use
48、rs and associated applications. For the eCM component it borrows from the DOCSIS suite of specifications with no additional enhancements. The eUE, user and application data are logically separated, and specified in this Recommendation. Given the use of SNMP for configuration and management, the eUE
49、component is provided with data pertaining to itself, users and applications. The logical representation of the E-UE Provisioning Data Model is specified in Figure 1. Figure 1 E-UE Provisioning Data Model Rec. ITU-T J.370 (06/2008) 5 6 E-UE Provisioning MIBs Framework Requirements The E-UE MIBs framework provides the MIB module implementation requirements for the E-UE. An informative, logical framework depicting MIB modules in the E-UE components is presented in Figure 2. The rest of this clause presents
