SCTE 24-19 : 2004

1 SCOPE
   1.1 Purpose of document
   1.2 Document Scope
   1.3 Requirements
2 REFERENCES
   2.1 Normative References
   2.2 Informative References
   2.3 Reference Acquisition
3 TERMS AND DEFINITIONS
4 ABBREVIATIONS
5 BACKGROUND
   5.1 Service Goals
   5.2 IPCablecom Reference Architecture
   5.3 Components and Interfaces
   5.4 Components
        5.4.1 Back-office OSS (Service Provider Business and
              Service Management Systems)
        5.4.2 Provisioning Server
        5.4.3 CMS
        5.4.4 MTA
        5.4.5 TFTP
        5.4.6 CMTS
        5.4.7 Network
   5.5 Interface Descriptions
        5.5.1 Pkt-p1
        5.5.2 Pkt-p4
        5.5.3 Pkt-prov-p1
6 ASSUMPTIONS
7 SUBSCRIBER PROVISIONING
   7.1 Customer Records (Billing)
   7.2 Equipment Setup and Configuration
        7.2.1 CMS Basic POTS Provisioning (BPP)
        7.2.2 CMS Call Feature Provisioning (CFP)
   7.3 Static Versus Dynamic Subscriber Provisioning Data
8 REQUIREMENTS
   8.1 General Requirements
   8.2 Transport Requirements
9 DATA MODEL
   9.1 Overview
        9.1.1 PcspService Object
        9.1.2 PcspMta Object
        9.1.3 PcspEndpoint Object
        9.1.4 PcspCMS Object
        9.1.5 Inter Object Relationships
   9.2 Relations are encoded using the PcspRelation
        entity.XML Encoding
        9.2.1 The PCSP XML Schema
        9.2.2 Sample PCSP Entity Encodings
        9.2.3 Object Extensions
10 MESSAGING
   10.1 Overview
   10.2 CMS and PS Messaging Role Requirements
   10.3 WSDL Specification
11 SECURITY
APPENDIX I - SAMPLE ENTITY ENCODINGS
APPENDIX II - SAMPLE OBJECT EXTENSION
APPENDIX III - DATA ENCODING EVALUATION
APPENDIX IV - TRANSPORT PROTOCOL EVALUATION

Defines the interface used between the CMS and Provisioning Server for the exchange of service provisioning information.