ETSI TS 102 879 V1.1.1 (2010-06)

Access, Terminals, Transmission and Multiplexing (ATTM); IPCablecom Services for delivering multimedia and voice over DOCSIS network infrastructure

DTS/ATTM-003007

General Information

• Status: Published
• Publication Date: 29-Jun-2010
• Technical Committee: ATTM AT3 - Integrated broadband cable and television networks
• Current Stage: 12 - Completion
• Due Date: 16-Jun-2010
• Completion Date: 30-Jun-2010

Standards Content (Sample)

Technical Specification
Access, Terminals, Transmission and Multiplexing (ATTM);
IPCablecom Services for delivering multimedia and voice
over DOCSIS network infrastructure

2 ETSI TS 102 879 V1.1.1 (2010-06)

Reference
DTS/ATTM-003007
Keywords
cable, IPCable, PSTN
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2010.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
LTE™ is a Trade Mark of ETSI currently being registered
for the benefit of its Members and of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 ETSI TS 102 879 V1.1.1 (2010-06)
Contents
Intellectual Property Rights . 7
Foreword . 7
1 Scope . 8
1.1 Purpose . 8
1.2 Relation to IPCablecom 1.x . 8
2 References . 9
2.1 Normative references . 10
2.2 Informative references . 10
3 Definitions and abbreviations . 11
3.1 Definitions . 11
3.2 Abbreviations . 11
4 Void . 13
5 Technical Overview . 13
5.1 QoS Background . 13
5.1.1 DOCSIS QoS Summary . 13
5.1.1.1 DOCSIS 3.0 Multicast QoS Framework . 15
5.1.2 IPCablecom 1.x QoS Summary . 15
5.2 Architecture . 16
5.2.1 Client Types . 17
5.2.2 IPCablecom Multimedia Devices . 17
5.2.2.1 Application Server (AS) . 19
5.2.2.2 Application Manager (AM) . 19
5.2.2.3 Policy Server (PS) . 19
5.2.2.3.1 Stateful and Stateless Policy Servers . 20
5.2.2.3.2 Modification of Requests and Responses by Policy Servers . 21
5.2.2.4 Cable Modem Termination System (CMTS) . 21
5.2.2.5 Record Keeping Server (RKS) . 21
5.2.3 IPCablecom Multimedia Interfaces . 21
5.2.3.1 Client and Application Manager Interface (mm-7) . 23
5.2.3.2 Application Manager and Policy Server Interface (pkt-mm-3) . 23
5.2.3.3 Policy Server and CMTS Interface (pkt-mm-2) . 23
5.2.3.4 Record Keeping Server and Policy Server Interface (pkt-mm-4) and Record Keeping Server and
CMTS Interface (pkt-mm-5) . 24
5.2.3.5 Client and Application Server Interface (mm-12) . 24
5.2.3.6 Application Server and Application Manager Interface (pkt-mm-11) . 24
5.2.4 State Information . 24
5.2.4.1 Application State . 24
5.2.4.2 QoS Resource State . 25
6 Authorization Interface Description . 25
6.1 Gates: The Framework for QoS Control . 25
6.1.1 Gate Identification (GateID) . 27
6.1.2 Application Manager Identification (AMID) . 27
6.1.3 Subscriber Identification (SubscriberID) . 28
6.1.4 Gate Specification (GateSpec) . 28
6.1.5 Classifier . 29
6.1.6 Traffic Profile . 31
6.1.6.1 FlowSpec . 32
6.1.6.2 DOCSIS Service Class Name . 32
6.1.6.3 DOCSIS Specific Parameterization . 32
6.1.6.4 Upstream Drop . 33
6.1.7 Event Generation Info . 33
6.1.8 Time-Based Usage Limit . 33
6.1.9 Volume-Based Usage Limit . 33
ETSI
4 ETSI TS 102 879 V1.1.1 (2010-06)
6.1.10 Opaque Data . 33
6.1.11 Gate Time Info . 33
6.1.12 Gate Usage Info . 33
6.1.13 User Identification (UserID) . 34
6.1.14 Shared Resource Identification (SharedResourceID) . 34
6.2 Gate Transitions . 34
6.2.1 Authorized . 35
6.2.2 Reserved . 36
6.2.3 Committed . 37
6.2.4 Committed-Recovery . 38
6.3 COPS Profile for IPCablecom Multimedia . 39
6.4 Gate Control Protocol Message Formats . 41
6.4.1 COPS Common Message Format . 41
6.4.2 Additional COPS Objects for Gate Control . 42
6.4.2.1 TransactionID . 43
6.4.2.2 AMID . 44
6.4.2.3 SubscriberID . 44
6.4.2.4 GateID . 44
6.4.2.5 GateSpec . 45
6.4.2.6 Classifiers . 46
6.4.2.7 Traffic Profiles . 50
6.4.2.7.1 Flow Spec . 50
6.4.2.7.2 DOCSIS Service Class Name . 51
6.4.2.7.3 Best Effort Service . 52
6.4.2.7.4 Non-Real-Time Polling Service . 53
6.4.2.7.5 Real-Time Polling Service. 54
6.4.2.7.6 Unsolicited Grant Service . 56
6.4.2.7.7 Unsolicited Grant Service with Activity Detection . 57
6.4.2.7.8 Downstream Service . 59
6.4.2.7.9 Upstream Drop . 60
6.4.2.8 Event Generation Info . 61
6.4.2.9 Volume-Based Usage Limit . 62
6.4.2.10 Time-Based Usage Limit . 62
6.4.2.11 Opaque Data . 63
6.4.2.12 Gate Time Info . 63
6.4.2.13 Gate Usage Info . 63
6.4.2.14 IPCablecom Error . 64
6.4.2.15 Gate State . 65
6.4.2.16 Version Info . 66
6.4.2.17 PSID . 66
6.4.2.18 Synch Options . 66
6.4.2.19 Msg Receipt Key . 67
6.4.2.20 UserID . 67
6.4.2.21 SharedResourceID . 67
6.4.3 Gate Control Messages . 67
6.4.3.1 Profile for Application Manager to Policy Server Interface . 68
6.4.3.2 Profile for Policy Server to CMTS Interface . 69
6.5 Gate Control Protocol Operation . 70
6.5.1 Initialization Sequence . 70
6.5.2 Operation Sequence . 71
6.5.3 Procedures for Validating Resource Envelopes . 72
6.5.3.1 Flow Spec . 73
6.5.3.2 DOCSIS Service Class Name . 73
6.5.3.3 DOCSIS Service Flow Parameters . 73
6.5.3.3.1 Upstream Encodings . 73
6.5.3.3.2 Downstream Encodings . 74
6.5.3.4 Upstream Drop . 74
6.5.4 Procedures for Authorizing Resources through a Gate . 74
6.5.4.1 Procedures for Authorizing Multicast Gates . 75
6.5.5 Procedures for Querying a Gate . 76
6.5.6 Procedures for Modifying a Gate . 76
6.5.6.1 Procedures for Modification of Multicast Gates . 77
ETSI
5 ETSI TS 102 879 V1.1.1 (2010-06)
6.5.7 Procedures for Supporting Usage Limits . 77
6.5.7.1 Procedures For Supporting Volume-Based Usage Limits . 78
6.5.7.2 Procedures For Supporting Time-Based Usage Limits . 78
6.5.7.3 Resource and Error Recovery . 78
6.5.7.4 Tracking Time-Based and Volume-Based Usage Limits . 79
6.5.8 Procedures for Deleting a Gate . 79
6.5.8.1 Procedures for Deleting Multicast Gates . 79
6.5.9 Procedure for Committing a Gate . 80
6.5.9.1 Procedure for Committing a Multicast Gate . 80
6.5.10 Termination Sequence . 80
6.5.11 Procedures for Multiple Grants Per Interval . 80
6.5.12 Procedures for Identifying a PDP to a PEP . 81
6.5.13 Procedures for Delivering Gate-Report-State Messages . 82
6.5.14 Procedures for Gate Control Operations Initiated by a Policy Server . 82
6.5.15 Procedures for State Synchronization . 82
6.5.15.1 Initiating State Synchronization . 83
6.5.15.2 Full Synchronization . 83
6.5.15.3 Incremental Synchronization. 83
6.5.15.4 Reporting Gate State Information . 84
6.5.15.5 Completing the Synchronization . 84
6.5.15.6 Relaying Out of Sync Data . 85
6.5.15.7 Synchronization with Stateless Policy Servers. 85
6.5.16 Procedures for Confirming PDP Receipt of Messages . 85
6.5.17 Procedures for Indicating Updated or Lost Shared Resource . 86
7 Event Messaging Interface Description. 86
7.1 Introduction . 86
7.2 Record Keeping Server Requirements . 88
7.3 General IPCablecom Multimedia Network Element Requirements . 88
7.3.1 Element ID . 88
7.3.2 Timing . 88
7.3.3 Primary and Secondary RKS Considerations . 88
7.3.4 Interaction with IPCablecom RKS . 89
7.4 Event Messages for IPCablecom Multimedia . 89
7.4.1 Policy Events . 89
7.4.1.1 Policy_Request . 90
7.4.1.2 Policy_Delete . 90
7.4.1.3 Policy_Update . 91
7.4.2 QoS Events . 92
7.4.2.1 QoS_Reserve . 92
7.4.2.2 QoS_Commit . 92
7.4.2.3 QoS_Release . 93
7.4.3 Time_Change . 93
7.5 Event Messaging Attributes for IPCablecom Multimedia . 94
7.5.1 EM_Header Attribute Structure . 96
7.5.2 Billing Correlation ID (BCID) Field Structure . 97
7.5.3 Status Field Structure . 98
7.5.4 QoS Descriptor Attribute Structure . 99
7.6 RADIUS Accounting Protocol . 99
7.6.1 Authentication and Confidentiality . 100
7.6.2 Standard RADIUS Attributes . 100
7.6.3 IPCablecom RADIUS Accounting-Request Packet Syntax . 101
8 Security Requirements . 101
8.1 CMTS - CM QoS Interface (pkt-mm-1) . 102
8.2 Policy Server - CMTS COPS Interface (pkt-mm-2) . 102
8.3 Application Manager - Policy Server COPS Interface (pkt-mm-3) . 102
8.4 Policy Server - RKS Event Message Interface (pkt-mm-4) . 103
8.5 CMTS - RKS Event Message Interface (pkt-mm-5) . 103
9 Mapping a FlowSpec Traffic Profile to DOCSIS . 103
9.1 Mapping FlowSpecs to DOCSIS Scheduling Types . 103
9.2 Mapping FlowSpecs to DOCSIS Traffic Parameters . 104
ETSI
6 ETSI TS 102 879 V1.1.1 (2010-06)
9.3 DOCSIS Upstream Parameters . 106
9.3.1 Unsolicited Grant Scheduling (UGS) . 107
9.3.2 Real-Time Polling Scheduling . 107
9.3.3 Best Effort Scheduling . 108
9.3.4 Upstream Packet Classification Encodings . 108
9.3.4.1 DOCSIS Upstream Packet Classification Requests . 108
9.4 DOCSIS Downstream Parameters . 109
9.4.1 Downstream QoS Encodings for Guaranteed Service . 109
9.4.2 Downstream QoS Encodings for Controlled Load Service . 110
9.4.3 Downstream Packet Classification Encodings . 111
9.4.3.1 DOCSIS Downstream Packet Classification Requests . 111
10 Message Flows . 112
10.1 Basic Message Sequence . 112
10.2 Detailed Message Sequence . 114
Annex A (informative): Guidelines for Version Number Assignment . 132
Annex B (informative): Bibliography . 134
History . 135

ETSI
7 ETSI TS 102 879 V1.1.1 (2010-06)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Access, Terminals, Transmission
and Multiplexing (ATTM).
ETSI
8 ETSI TS 102 879 V1.1.1 (2010-06)
1 Scope
The present document specifies IPCablecom, (also referred to as PacketCable) multimedia services over DOCSIS.
1.1 Purpose
The intent of the present document is to support the deployment of general Multimedia services by providing a
technical definition of several IP-based signalling interfaces that leverage core QoS and policy management capabilities
native to DOCSIS Versions 1.1 and greater. Throughout the present document, the term DOCSIS will be used to refer
to any DOCSIS version greater than or equal to 1.1. For the purposes of the present document, Multimedia services may
be defined as IP-based services (e.g. online gaming, video-conferencing, streaming media, etc.) requiring QoS-based
network resources (as contrasted with services such as web browsing, e-mail, instant messaging and file-sharing that are
commonly provided using best-effort flows). While telephony or voice-based services are not specifically excluded
from this definition, the IPCablecom 1.x set of specifications provide coverage specific to this type of service delivery,
and, therefore, those specifications should be consulted as appropriate.
IPCablecom Multimedia defines a service delivery framework that provides general-purpose QoS, event-based
accounting, and security functionality founded upon the mechanisms defined in IPCablecom 1.x. However, due to the
broader spectrum of applications and services addressed by this initiative, each of these functional areas has been
revisited and generalized for the present purposes. Telephony-specific requirements and interfaces (e.g. call signalling,
PSTN interconnection and electronic surveillance) are not part of IPCablecom Multimedia, while core functionality
such as QoS resource management mechanisms, has been enhanced. Throughout this process, one of the primary
objectives of this work has been to leverage and reuse as much of the existing body of IPCablecom 1.x investment,
knowledge base, and technical functionality as possible.
Key features of the described Multimedia service delivery framework include:
• Simple, powerful access to DOCSIS QoS mechanisms supporting both time and volume-based network
resource authorizations.
• Abstract, event-based network resource auditing and management mechanisms.
• A robust security infrastructure that provides integrity and appropriate levels of protection across all interfaces.
As outlined in the technical report [15], the current scope of the present document is limited to network-based QoS
resource management and usage auditing capabilities. This approach was motivated by several criteria, including rapid
time-to-market for QoS-enhanced Multimedia services (which may take the form of new applications or existing
applications retrofitted per the present document), the absence of QoS signalling requirements on CPE devices, and
security assurances provided by an absence of client-based QoS signalling.
In addition, the QoS signalling mechanisms outlined herein provide the foundation for client-based QoS signalling
mechanisms which may be defined in the future. As such scenarios have already been considered and documented in
the technical report, one of the secondary goals of the present document is to provide for smooth migration to a client-
based model as market and technology advances dictate. It should also be noted that the scope of the QoS framework
defined in the present document is limited to the access network and that the choice of specific backbone QoS strategies
is left as an administrative decision to be addressed by each service provider as it deems best.
1.2 Relation to IPCablecom 1.x
Since its inception the IPCablecom initiative has been positioned as an IP-based Multimedia service deployment
infrastructure, exploiting and enhancing the underlying QoS capabilities of the DOCSIS access network. Based on
market demand and technology readiness, VoIP was chosen as the first IP-based service to leverage these unique
broadband access network capabilities, as the IPCablecom 1.x suite of specifications simultaneously defines both a
general QoS-based service delivery framework and a number of telephony-specific functional elements and
mechanisms.
ETSI
9 ETSI TS 102 879 V1.1.1 (2010-06)
Specifically, the IPCablecom 1.x VoIP architecture provides specifications promoting multi-vendor interoperability and
CableLabs certification and qualification in the following key telephony areas:
• Network-based call signalling (NCS)
• Inter-domain call signalling (CMSS)
• PSTN gateway and interop functionality (TGCP, ISTP)
• Access-network and backbone QoS capabilities (DQoS, IQoS)
• Event messaging with telephony-specific extensions (EM)
• CPE endpoint provisioning and monitoring (Provisioning and SNMP MIBs)
• Comprehensive suite of interface security mechanisms (Security)
• Primary-line telephony characteristics
• Electronic surveillance
Since the intent of the present document is to extract the functional core of this architecture in support of the
enhancement and deployment of other Multimedia services, support for these telephony-specific features is not
required, while the core QoS, event messaging and security mechanisms are emphasized and generalized. The result is a
framework that provides IP-based access to DOCSIS access-network QoS mechanisms complemented by secure and
robust authorization and audit mechanisms.
In keeping with the IPCablecom 1.x Dynamic Quality of Service (DQoS) model, the primary logical construct in
support of QoS-based service delivery is a Gate (along with its accompanying authorization token). An IPCablecom
Gate represents a policy-based authorization for a specific envelope of network resources characterized by a suite of
QoS parameters, as well as classifiers for originating and terminating IP addresses and ports, which define and limit the
scope of the associated QoS-enhanced flow.
IPCablecom 1.x defines a pre-authorization model in which Gates are created and installed at policy enforcement points
(e.g. a CMTS) prior to actual network resource reservation or activation requests. This process, termed Gate Control, is
managed through a COPS-based policy interface on the CMTS. In the present document, this interface is generalized
and enhanced to allow for full lifecycle management of QoS-based service flows through this policy interface. That is,
Gate installation and management is supplemented with service flow creation, modification and deletion functions to
provide for network-based QoS service delivery.
To complement these enhanced QoS policy and signalling capabilities, the RADIUS-based event messaging
infrastructure of IPCablecom 1.x is carried over, but with telephony-specific primitives tagged as optional. Since the
EM protocol was designed with a considerable amount of generality and abstraction, this approach provides continuity
with existing protocol and Record Keeping Server (RKS) implementation while still allowing Multimedia vendors to
select from a set of supplementary protocol primitives on an as-needed basis. For example, if a QoS-based video
conferencing service were being developed based on the present document, a number of telephony-specific EM
message types (e.g. Call_Answer and Call_Disconnect) may map directly to the service's audit requirements.
Finally, in order to provide robust security for this Multimedia framework, IPsec will be applied to the COPS and
RADIUS interfaces in a manner analogous to the corresponding interfaces in the IPCablecom 1.x architecture.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
ETSI
10 ETSI TS 102 879 V1.1.1 (2010-06)
2.1 Normative references
The following referenced documents are necessary for the application of the present document.
[1] ETSI TS 102 639-4: "Access and Terminals, Transmission and Multiplexing (ATTM); Third
Generation Transmission Systems for Interactive Cable Television Services - IP Cable Modems;
Part 4: MAC and Upper Layer Protocols [ITU-T Recommendation J.222.2 (07/2007), modified]".
[2] IETF RFC 1305 (March 1992): "Network Time Protocol (Version 3) Specification,
Implementation and Analysis".
[3] IETF RFC 2205 (September 1997): "Resource ReSerVation Protocol (RSVP) - Version 1
Functional Specification".
[4] IETF RFC 2210 (September 1997): "The Use of RSVP with IETF Integrated Services".
[5] IETF RFC 2211 (September 1997): "Specification of the Controlled-Load Network Element
Service".
[6] IETF RFC 2212 (September 1997): "Specification of Guaranteed Quality of Service".
[7] IETF RFC 2474 (December 1998): "Definition of the Differentiated Services Field (DS Field) in
the IPv4 and IPv6 Headers".
[8] IETF RFC 4546: "Radio Frequency (RF) Interface Management Information Base for Data over
Cable Service Interface Specifications (DOCSIS) 2.0 Compliant RF Interfaces".
[9] IETF RFC 2748 (January 2000): "The COPS (Common Open Policy Service) Protocol".
[10] IETF RFC 2753 (January 2000): "A Framework for Policy-based Admission Control".
[11] IETF RFC 2866 (June 2000): "RADIUS Accounting".
[12] IETF RFC 3084 (March 2001): "COPS Usage for Policy Provisioning (COPS-PR)".
[13] ITU-T Recommendation J.163 (12/2007): "Dynamic quality of service for the provision of
real-time services over cable television networks using cable modems".
[14] ITU-T Recommendation J.164 (12/2007): "Event message requirements for the support of
real-time services over cable television networks using cable modems".
TM
[15] PKT-TR-MM-ARCH-V03-091029: PacketCable Technical Report "Multimedia Architecture
Framework", Cable Television Laboratories, Inc.
NOTE: Available at http://cablelabs.com/specifications/PKT-TR-MM-ARCH-V03-091029.pdf.
[16] ITU-T Recommendation J.170 (11/2005): "IPCablecom security specification".
[17] ETSI ES 201 488-3 (V1.2.2): "Access and Terminals (AT); Data Over Cable Systems;
Part 3: Baseline Privacy Plus Interface Specification".
[18] IETF RFC 2865: "Remote Authentication Dial In User Service (RADIUS)".
[19] IEEE 802.1D-1998: "IEEE Standard for Local Area Network MAC (Media Access Control)
Bridges".
2.2 Informative references
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] IETF RFC 2751 (January 2000): "Signaled Preemption Priority Policy Element".
[i.2] SCTE 159-2 2010: "Multimedia Application and Service Part 2: IPCablecom Multimedia Web
Services".
ETSI
11 ETSI TS 102 879 V1.1.1 (2010-06)
[i.3] IETF RFC 3168 (September 2001): "The Addition of Explicit Congestion Notification (ECN) to
IP".
[i.4] IETF RFC 3171 (August 2001): "IANA Guidelines for IPv4 Multicast Address Assignment".
[i.5] IETF RFC 4291 (February 2006): "IP Version 6 Addressing Architecture".
[i.6] IETF RFC 791: "Intern
...