1、 International Telecommunication Union ITU-T J.177TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (11/2005) SERIES J: CABLE NETWORKS AND TRANSMISSION OF TELEVISION, SOUND PROGRAMME AND OTHER MULTIMEDIA SIGNALS IPCablecom IPCablecom CMS subscriber provisioning specification ITU-T Recommendation J.177
2、 ITU-T Rec. J.177 (11/2005) i ITU-T Recommendation J.177 IPCablecom CMS subscriber provisioning specification Summary This Recommendation defines the interface used between the Call Management Server (CMS) and Provisioning Server (PS) for the exchange of service provisioning information. The interfa
3、ce employs a Web Service model. Specified in Web Service Description Language 1.1 (WSDL 1.1), the interface transports XML encoded objects within Simple Object Access Protocol 1.1 (SOAP 1.1) encoded messages over an HTTP 1.1 transport. This interface is secured via IPSec. Source ITU-T Recommendation
4、 J.177 was approved on 29 November 2005 by ITU-T Study Group 9 (2005-2008) under the ITU-T Recommendation A.8 procedure. ii ITU-T Rec. J.177 (11/2005) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecom
5、munication Standardization Sector (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 Ass
6、embly (WTSA), which meets every four 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 wh
7、ich fall within ITU-Ts purview, the 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
8、this Recommendation is voluntary. 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 lang
9、uage such as “must“ and the negative 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
10、Recommendation may involve the use 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 o
11、f approval of this Recommendation, 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 th
12、e TSB patent database. ITU 2006 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.177 (11/2005) iii CONTENTS Page 1 Scope 1 1.1 Purpose of this Recommendation. 1 1.2 Scope of this Recommendation 1 2
13、References. 1 2.1 Normative references 1 2.2 Informative References 2 2.3 Reference acquisition . 2 3 Terms and definitions . 2 4 Abbreviations, acronyms and conventions. 2 4.1 Abbreviations and acronyms 2 4.2 Conventions 4 5 Background. 4 5.1 Service goals. 4 5.2 IPCablecom reference architecture.
14、4 5.3 Components and interfaces. 5 5.4 Components 6 5.5 Interface descriptions 6 6 Assumptions . 6 7 Subscriber provisioning 7 7.1 Customer records (billing) 7 7.2 Equipment set-up and configuration 7 7.3 Static versus Dynamic Subscriber Provisioning Data 7 8 Requirements 8 8.1 General requirements
15、8 8.2 Transport requirements. 8 9 Data model 9 9.1 Overview 9 9.2 Relations are encoded using the PcspRelation entity.XML encoding . 11 10 Messaging. 12 10.1 Overview 12 10.2 CMS and PS messaging role requirements 12 10.3 WSDL specification . 13 11 Security. 13 Annex A PCSP XML schema. 14 Appendix I
16、 Sample entity encodings 34 I.1 PcspService object example . 34 I.2 PcspEndpoint object example. 35 iv ITU-T Rec. J.177 (11/2005) Page I.3 PcspMta object example. 36 I.4 PcspCms object example 36 I.5 PcspRelation example 36 Appendix II Sample object extension . 37 II.1 Extended PcspService object ex
17、ample . 37 II.2 The extension schema. 38 Appendix III Data encoding evaluation 38 III.1 XML . 38 III.2 ASN.1/BER 39 III.3 Proprietary ASCII. 39 III.4 SDP (Session Description Protocol). 39 III.5 RADIUS . 39 III.6 SQL. 39 III.7 Options summary 39 III.8 Recommendation: XML. 40 Appendix IV Transport pr
18、otocol evaluation . 40 IV.1 TFTP with IPSec 40 IV.2 Batched RADIUS Multiple records in single request via event messages 40 IV.3 Diameter . 41 IV.4 Distributed object systems 41 IV.5 HTTP 42 IV.6 Options summary 42 IV.7 Recommendation: HTTP 1.1 43 BIBLIOGRAPHY 44 ITU-T Rec. J.177 (11/2005) 1 ITU-T R
19、ecommendation J.177 IPCablecom CMS subscriber provisioning specification 1 Scope 1.1 Purpose of this Recommendation This Recommendation defines the interface used between the Call Management Server (CMS) and Provisioning Server (PS) for the exchange of service provisioning information. The interface
20、 employs a Web Service model. Specified in Web Service Description Language 1.1 (WSDL 1.1), the interface transports XML encoded objects within Simple Object Access Protocol 1.1 (SOAP 1.1) encoded messages over an HTTP 1.1 transport. This interface is secured via IPSec. The data model transported up
21、on this interface is specifically designed to be extensible, allowing incorporation of as yet undefined IPCablecom features and specific vendor extensions. 1.2 Scope of this Recommendation The scope of this Recommendation is limited to the provisioning of an IPCablecom CMS by a single service provid
22、er. Additionally: The CMS provisioning interface is limited to the exchange of service activation data between the CMS and the PS. The interface between the PS and the back-office Operations Support System (OSS) is out of scope. CMS element management and network element provisioning (dial plans, et
23、c.) are out of scope. Customer record creation/billing is considered part of the back-office OSS application and is currently out of scope. 2 References 2.1 Normative references The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constit
24、ute provisions of this Recommendation. At the time of publication, the editions indicated 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 Reco
25、mmendations and other references listed below. A list of the currently valid ITU-T Recommendations 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. ITU-T Recommendation J.161 (2001), Audio code
26、c requirements for the provision of bidirectional audio service over cable television networks 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.
27、170 (2005), IPCablecom security specification. IETF RFC 1123 (1989), Requirements for Internet Hosts Application and Support. XML Protocol. http:/www.w3.org/2000/xp. 2 ITU-T Rec. J.177 (11/2005) 2.2 Informative References ITU-T Recommendation J.160 (2005), Architectural framework for the delivery of
28、 time-critical services over cable television networks using cable modems. ITU-T Recommendation J.167 (2005), Media terminal adapter (MTA) device provisioning requirements for the delivery of real-time services over cable television networks using cable modems. IETF RFC 3588 (2003), Diameter Base Pr
29、otocol. Simple Object Access Protocol. http:/www.w3.org/TR/SOAP. Web Services Description Language. http:/www.w3.org/TR/wsdl. 2.3 Reference acquisition IETF RFCs: Internet Engineering Task Force (IETF) Secretariat c/o Corporation for National Research Initiatives, 1895 Preston White Drive, Suite 100
30、, Reston, VA 20191-5434, Phone 703-620-8990, Fax 703-620-9071, internet: www.ietf.org/. 3 Terms and definitions This Recommendation defines the following terms: 3.1 active: A service flow is said to be “active“ when it is permitted to forward data packets. A service flow must first be admitted befor
31、e it is active. 3.2 endpoint: A Terminal, Gateway or Multipoint Conference Unit. 3.3 Internet key exchange: A key-management mechanism used to negotiate and derive keys for SAs in IPSec. 3.4 local number portability: Allows a customer to retain the same number when switching from one local service p
32、rovider to another. 3.5 media gateway: Provides the bearer circuit interfaces to the PSTN and transcodes the media stream. 3.6 pre-shared key: A shared secret key passed to both parties in a communication flow, using an unspecified manual or out-of-band mechanism. 3.7 registration, admissions and st
33、atus: RAS Channel is an unreliable channel used to convey the RAS messages and bandwidth changes between two H.323 entities. 4 Abbreviations, acronyms and conventions 4.1 Abbreviations and acronyms This Recommendation uses the following abbreviations: AAA Authentication, Authorization and Accounting
34、 BPP Basic POTS Provisioning CFP Call Feature Provisioning CID Circuit ID CM DOCSIS Cable Modem CMS Cryptographic Message Syntax ITU-T Rec. J.177 (11/2005) 3 CMS Call Management Server CMTS Cable Modem Termination System Codec COder-DECoder CSR Customer Service Representative DOCSIS Data-Over-Cable
35、Service Interface Specifications DQoS Dynamic Quality of Service ESP IPSec Encapsulating Security Payload FQDN Fully Qualified Domain Name HTTP Hypertext Transfer Protocol IC Inter-exchange Carrier IETF Internet Engineering Task Force IKE Internet Key Exchange IP Internet Protocol IPSec Internet Pro
36、tocol Security ITU International Telecommunication Union ITU-T International Telecommunication Union Telecommunication Standardization Sector LNP Local Number Portability MC Multipoint Controller MG Media Gateway MGC Media Gateway Controller MGCP Media Gateway Control Protocol MIB Management Informa
37、tion Base MTA Multimedia Terminal Adapter NCS Network Call Signalling OSS Operations Support System PCM Pulse Code Modulation PCSP IPCablecom CMS Subscriber Provisioning PS Provisioning Server PSTN Public Switched Telephone Network QCIF Quarter Common Intermediate Format RAS Registration, Admissions
38、 and Status RFC Request for Comments SDP Session Description Protocol SNMP Simple Network Management Protocol SOAP Simple Object Access Protocol STP Signalling Transfer Point 4 ITU-T Rec. J.177 (11/2005) TD Timeout for Disconnect TFTP Trivial File Transfer Protocol TLV Type-Length-Value UDP User Dat
39、agram Protocol VoIP Voice over Internet Protocol 4.2 Conventions Throughout this Recommendation, words that are used to define the significance of particular requirements are capitalized. These words are: “MUST“ This word or the adjective “REQUIRED“ means that the item is an absolute requirement of
40、this Recommendation. “MUST NOT“ This phrase means that the item 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 understoo
41、d 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 behaviour is acceptable or even useful, but the full implications should be understood and the case carefully weighed bef
42、ore implementing any behaviour described with this label. “MAY“ This word 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 omi
43、t the same item. 5 Background 5.1 Service goals Text deleted. 5.2 IPCablecom reference architecture Figure 1 shows the reference architecture for the IPCablecom Network. Refer to the IPCablecom Architecture Recommendation, ITU-T Rec. J.160, for more detailed information on this reference architectur
44、e. ITU-T Rec. J.177 (11/2005) 5 Figure 1/J.177 IPCablecom 1.0 network component reference model (partial) 5.3 Components and interfaces Provisioning is defined as the operations necessary to provide a specified service to a customer. IPCablecom service provisioning can be viewed as two distinct oper
45、ations: MTA provisioning and CMS subscriber provisioning. Figure 2 presents the provisioning-related interfaces maintained by the Provisioning Server (PS) and other authorized back-office components to various IPCablecom elements. Interfaces not explicitly labelled are undefined and out of scope for
46、 IPCablecom. This Recommendation is intended to set the requirements for the provisioning interface between the CMS and the PS or, optionally, other authorized back-office components (Pkt-prov-p1). J.177_F02PSMTACMTSCMS TFTPNetworkBack-office OSSPkt-prov-p1Pkt-p1Pkt-p4Figure 2/J.177 Provisioning com
47、ponent interfaces 6 ITU-T Rec. J.177 (11/2005) 5.4 Components 5.4.1 Back-office components (Service Provider Business and Service Management Systems) These are the back-office components that a service provider uses to manage customers and other components that make up their business. These systems
48、provide the IPCablecom provisioning process with service orders or, optionally, individual workflow tasks to activate services for customers. These systems may also receive accounting or usage data used to create customer-billing events. 5.4.2 Provisioning Server This system forms the interface betw
49、een the providers back-office components and some or all of the IPCablecom elements. IPCablecom does not address the implementation of this system or its relationship to other OSSs that a service provider might employ. The Provisioning Server is defined in ITU-T Rec. J.167 as consisting of a provisioning application that contains provisioning logic and a provisioning SNMP entity that provides access to active components. Here we will refer to the Provisioning Server without distinguishing betw
