ETSI ES 203 312 V1.1.1 (2015-03)

Integrated broadband cable telecommunication networks (CABLE); Cabinet DOCSIS (C-DOCSIS) System Specification

DES/CABLE-00019

General Information

• Status: Published
• Publication Date: 22-Mar-2015
• Technical Committee: CABLE WG1 - Architecture, Interfaces, protocols
• Current Stage: 12 - Completion
• Due Date: 03-Apr-2015
• Completion Date: 23-Mar-2015

Standards Content (Sample)

Final draft ETSI ES 203 312 V1.1.1 (2015-01)

ETSI STANDARD
Integrated broadband cable
telecommunication networks (CABLE);
Cabinet DOCSIS (C-DOCSIS) System Specification

2 Final draft ETSI ES 203 312 V1.1.1 (2015-01)

Reference
DES/CABLE-00019
Keywords
access, broadband, cable, CMTS, data, DOCSIS,
HFC
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
The present document can be downloaded from:
http://www.etsi.org
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (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 or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2015.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI 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 Final draft ETSI ES 203 312 V1.1.1 (2015-01)
Contents
Intellectual Property Rights . 7
Foreword . 7
Modal verbs terminology . 7
1 Scope . 8
2 References . 8
2.1 Normative references . 8
2.2 Informative references . 9
3 Definitions and abbreviations . 9
3.1 Definitions . 9
3.2 Abbreviations . 10
4 Requirements . 12
5 Overview . 12
6 System Definition and Characteristics . 14
6.1 System Definition and Description. 14
6.2 Characteristics . 14
7 Modules and Interfaces . 15
7.1 Functional Modules . 15
7.2 Interfaces on Functional Modules . 16
7.2.1 Radio Frequency Interface (RFI) . 16
7.2.2 Network Side Interface (NSI) . 16
7.2.3 Operation and Management Interface (OMI) . 16
7.2.4 C-DOCSIS Data Tag (CDT) . 17
7.2.5 C-DOCSIS Management Message (CDMM) . 17
7.2.6 Control and Classifier Interface (CCI) . 17
7.2.7 Main Path Interface (MPI) . 17
7.3 Data Packet Processing . 17
8 System Requirements and Devices . 18
8.1 System Requirements . 18
8.1.1 Data Forwarding Requirements . 18
8.1.2 QoS Requirements . 19
8.1.3 Security Requirements . 20
8.2 C-DOCSIS I System and Devices . 20
8.3 C-DOCSIS II System and Devices . 21
8.4 C-DOCSIS III System and Devices. 21
Annex A (normative): Service Flow Mapping to VLAN . 23
Annex B (normative): CDMM and CDT . 24
B.1 C-DOCSIS Tagging (CDT) . 24
B.2 C-DOCSIS Management Messaging (CDMM) . 25
B.2.1 CDMM Overview. 25
B.2.2 CDMM encapsulation . 25
B.2.2.1 Encapsulation Format . 25
B.2.2.2 Encapsulation with OAM Transport Layer . 25
B.2.2.2.1 Frame Structure . 26
B.2.2.2.2 Transport Layer Header . 26
B.2.2.2.3 PDU. 27
B.2.2.2.4 Acknowledgement. 27
B.2.2.2.5 Protocol . 28
B.2.2.3 Encapsulation with TCP/IP Transport Layer . 28
ETSI
4 Final draft ETSI ES 203 312 V1.1.1 (2015-01)
B.2.3 CDMM Message Contents . 28
B.2.3.1 Overview . 28
B.2.3.2 CDMM Message Index . 29
B.2.3.3 CDMM Message Specification . 33
B.2.3.3.1 DOCSIS Downstream Configuration . 33
B.2.3.3.1.1 SET DOWNSTREAM CONFIG REQUEST (0x01) . 33
B.2.3.3.1.2 SET DOWNSTREAM CONFIG RESPONSE (0x02) . 34
B.2.3.3.1.3 GET DOWNSTREAM CONFIG REQUEST (0x03). 34
B.2.3.3.1.4 GET DOWNSTREAM CONFIG RESPONSE (0x04). 34
B.2.3.3.2 DOCSIS Upstream Configuration . 35
B.2.3.3.2.1 SET UPSTREAM CONFIG REQUEST (0x05) . 35
B.2.3.3.2.2 SET UPSTREAM CONFIG RESPONSE (0x06) . 36
B.2.3.3.2.3 GET UPSTREAM CONFIG REQUEST (0x07) . 36
B.2.3.3.2.4 GET UPSTREAM CONFIG RESPONSE (0x08) . 36
B.2.3.3.3 Move CM Downstream . 37
B.2.3.3.3.1 SET MOVE CM DOWNSTREAM REQUEST (0x09) . 37
B.2.3.3.3.2 SET MOVE CM DOWNSTREAM RESPONSE (0x0a) . 38
B.2.3.3.3.3 GET MOVE CM DOWNSTREAM REQUEST (0x0b) . 38
B.2.3.3.3.4 GET MOVE CM DOWNSTREAM RESPONSE (0x0c) . 38
B.2.3.3.4 Move CM Upstream . 38
B.2.3.3.4.1 SET MOVE CM UPSTREAM REQUEST (0x0d) . 38
B.2.3.3.4.2 SET MOVE CM UPSTREAM RESPONSE (0x0e) . 39
B.2.3.3.4.3 GET MOVE CM UPSTREAM REQUEST (0x0f) . 39
B.2.3.3.4.4 GET MOVE CM UPSTREAM RESPONSE (0x10) . 39
B.2.3.3.5 Load Balancing . 39
B.2.3.3.5.1 SET CREATE/DESTROY LOAD BALANCING GROUP REQUEST (0x15) . 39
B.2.3.3.5.2 SET CREATE/DESTROY LOAD BALANCING GROUP RESPONSE (0x16) . 40
B.2.3.3.5.3 GET LOAD BALANCING GROUPS REQUEST (0x17) . 40
B.2.3.3.5.4 GET LOAD BALANCING GROUPS RESPONSE (0x18) . 40
B.2.3.3.5.5 SET ADD/REMOVE DOWNSTREAMS TO/FROM LOAD BALANCING GROUP
REQUEST (0x19) . 40
B.2.3.3.5.6 SET ADD/REMOVE DOWNSTREAMS TO/FROM LOAD BALANCING GROUP
RESPONSE (0x1a) . 41
B.2.3.3.5.7 GET LOAD BALANCING GROUP DOWNSTREAMS REQUEST (0x1b) . 41
B.2.3.3.5.8 GET LOAD BALANCING GROUP DOWNSTREAMS RESPONSE (0x1c) . 41
B.2.3.3.5.9 SET ADD/REMOVE UPSTREAMS TO/FROM LOAD BALANCING GROUP REQUEST
(0x1d) . 42
B.2.3.3.5.10 SET ADD/REMOVE UPSTREAMS TO/FROM LOAD BALANCING GROUP
RESPONSE (0x1e) . 42
B.2.3.3.5.11 GET LOAD BALANCING GROUP UPSTREAMS REQUEST (0x1f) . 42
B.2.3.3.5.12 GET LOAD BALANCING GROUP UPSTREAMS RESPONSE (0x20) . 43
B.2.3.3.5.13 SET ADD/REMOVE CM TO/FROM LOAD BALANCING GROUP REQUEST (0x21) . 43
B.2.3.3.5.14 SET ADD/REMOVE CM TO/FROM LOAD BALANCING GROUP RESPONSE (0x22) . 43
B.2.3.3.5.15 GET LOAD BALANCING GROUP CM CONFIGURATION REQUEST (0x23) . 43
B.2.3.3.5.16 GET LOAD BALANCING GROUP CM CONFIGURATION RESPONSE (0x24) . 44
B.2.3.3.5.17 GET LOAD BALANCING GROUP ACTIVE CM REQUEST (0x25) . 44
B.2.3.3.5.18 GET LOAD BALANCING GROUP ACTIVE CM RESPONSE (0x26) . 44
B.2.3.3.5.19 SET EXCLUDE CM FROM LOAD BALANCING REQUEST (0x27) . 44
B.2.3.3.5.20 SET EXCLUDE CM FROM LOAD BALANCING RESPONSE (0x28) . 45
B.2.3.3.5.21 GET EXCLUDED CM CONFIGURATION REQUEST (0x29) . 45
B.2.3.3.5.22 GET EXCLUDED CM CONFIGURATION RESPONSE (0x2a) . 45
B.2.3.3.5.23 GET EXCLUDED ACTIVE CM REQUEST (0x2b) . 45
B.2.3.3.5.24 GET EXCLUDED ACTIVE CM'S RESPONSE (0x2c) . 46
B.2.3.3.5.25 SET FULL LOAD BALANCING GROUP REQUEST (0x2d) . 46
B.2.3.3.5.26 SET FULL LOAD BALANCING GROUP RESPONSE (0x2e) . 47
B.2.3.3.5.27 GET FULL LOAD BALANCING GROUP REQUEST (0x2f) . 47
B.2.3.3.5.28 GET FULL LOAD BALANCING GROUP RESPONSE (0x30) . 47
B.2.3.3.6 DOCSIS Upstream Input Power Level . 48
B.2.3.3.6.1 SET UPSTREAM INPUT POWER REQUEST (0x31) . 48
B.2.3.3.6.2 SET UPSTREAM INPUT POWER RESPONSE (0x32) . 48
B.2.3.3.6.3 GET UPSTREAM INPUT POWER REQUEST (0x33) . 48
B.2.3.3.6.4 GET UPSTREAM INPUT POWER RESPONSE (0x34) . 49
ETSI
5 Final draft ETSI ES 203 312 V1.1.1 (2015-01)
B.2.3.3.7 CM Arrival, Departure and Deletion . 49
B.2.3.3.7.1 CM ARRIVAL REQUEST (0x300) . 49
B.2.3.3.7.2 CM ARRIVAL RESPONSE (0x301) . 49
B.2.3.3.7.3 CM DEPARTURE EVENT (0x302) . 50
B.2.3.3.7.4 SET CM DELETE REQUEST (0x303) . 50
B.2.3.3.7.5 SET CM DELETE RESPONSE (0x304) . 50
B.2.3.3.8 QoS and Dynamic Services . 51
B.2.3.3.8.1 SET SERVICE CLASS NAME REQUEST (0x350) . 51
B.2.3.3.8.2 SET SERVICE CLASS NAME RESPONSE (0x351) . 51
B.2.3.3.8.3 SERVICE FLOW RESERVATION REQUEST (0x352) . 52
B.2.3.3.8.4 SERVICE FLOW RESERVATION RESPONSE (0x353) . 52
B.2.3.3.8.5 CDMM REGISTRATION REQUEST (0x354) . 52
B.2.3.3.8.6 CDMM REGISTRATION RESPONSE (0x355) . 53
B.2.3.3.8.7 CDMM REGISTRATION ACKNOWLEDGE (0x356) . 54
B.2.3.3.8.8 MULTICAST JOIN AUTHORIZATION REQUEST (0x357). 55
B.2.3.3.8.9 MULTICAST JOIN AUTHORIZATION RESPONSE (0x358). 55
B.2.3.3.8.10 SECURITY ASSOCIATION AUTH REQUEST (0x359) . 55
B.2.3.3.8.11 SECURITY ASSOCIATION AUTH RESPONSE (0x35A) . 56
B.2.3.3.8.12 CDMM DSA-REQ CM-INITIATED (0x360), CDMM DSC-REQ CM-INITIATED (0x361),
CDMM DSD-REQ CM-INITIATED (0x362) . 56
B.2.3.3.8.13 CDMM DSA-RSP CM-INITIATED (0x363), CDMM DSC-RSP CM-INITIATED (0x364),
CDMM DSD-RSP CM-INITIATED (0x365) . 57
B.2.3.3.8.14 CDMM DSA-ACK CM-INITIATED (0x366), CDMM DSC-ACK CM-INITIATED (0x367) . 58
B.2.3.3.8.15 CDMM DSA-REQ CMTS-INITIATED (0x368), CDMM DSC-REQ CMTS-INITIATED
(0x369), CDMM DSD-REQ CMTS-INITIATED (0x36A) . 59
B.2.3.3.8.16 CDMM DSA-RSP CMTS-INITIATED (0x36B), CDMM DSC-RSP CMTS-INITIATED
(0x36C), CDMM DSD-RSP CMTS-INITIATED (0x36D) . 60
B.2.3.3.8.17 CDMM DSA-ACK CMTS-INITIATED (0x36E), CDMM DSC-ACK CMTS-INITIATED
(0x36F) . 61
B.2.3.3.9 CM and RFI Module Statistics . 61
B.2.3.3.9.1 GET CM STATUS REQUEST (0x701) . 61
B.2.3.3.9.2 GET CM STATUS RESPONSE (0x702) . 62
B.2.3.3.9.3 GET RF INTERFACES REQUEST (0x703) . 63
B.2.3.3.9.4 GET RF INTERFACES RESPONSE (0x704) . 63
B.2.3.3.9.5 GET RFI MAC STATISTICS REQUEST (0x705) . 63
B.2.3.3.9.6 GET RFI MAC STATISTICS RESPONSE (0x706). 63
B.2.3.3.9.7 GET SERVICES STATISTICS REQUEST (0x707) . 64
B.2.3.3.9.8 GET SERVICES STATISTICS RESPONSE (0x708) . 64
B.2.3.3.9.9 GET SIGNAL QUALITY REQUEST (0x709) . 64
B.2.3.3.9.10 GET SIGNAL QUALITY RESPONSE (0x70a) . 65
B.2.3.3.9.11 GET RF INTERFACE STATISTICS REQUEST (0x70b) . 65
B.2.3.3.9.12 GET RF INTERFACE STATISTICS RESPONSE (0x70c) . 65
B.2.3.3.9.13 GET DOWNSTREAM BONDING GROUPS REQUEST (0x70d) . 66
B.2.3.3.9.14 GET DOWNSTREAM BONDING GROUPS RESPONSE (0x70e) . 66
B.2.3.3.9.15 GET UPSTREAM BONDING GROUPS REQUEST (0x70f) . 67
B.2.3.3.9.16 GET UPSTREAM BONDING GROUPS RESPONSE (0x710) . 67
B.2.3.3.9.17 VENDOR-SPECIFIC MESSAGE (0x0F01) . 67
B.2.3.3.9.18 RFI SYSTEM EVENT MESSAGE (0x1001) . 68
B.2.4 CDMM Message Functional Flow . 68
B.2.4.1 RFI Module Initialization . 68
B.2.4.1.1 OAM Control Channel Startup . 68
B.2.4.1.2 TCP/IP Control Channel Startup . 69
B.2.4.2 CM Initialization and Registration . 69
Annex C (informative): Dynamic Service Operations . 72
C.1 Dynamic Service Operations Overview . . 72
C.2 Session Setup . 72
C.3 Session Maintenance . 74
C.4 Session Termination . 76
ETSI
6 Final draft ETSI ES 203 312 V1.1.1 (2015-01)
C.5 Control Point Discovery Mechanism . 77
Annex D (informative): Bibliography . 79
History . 80

ETSI
7 Final draft ETSI ES 203 312 V1.1.1 (2015-01)

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://ipr.etsi.org).
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 final draft ETSI Standard (ES) has been produced by ETSI Technical Committee Integrated broadband cable
telecommunication networks (CABLE) and is now submitted for the ETSI standards Membership Approval Procedure.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "may not", "need", "need not", "will",
"will not", "can" and "cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms
for the expression of provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
8 Final draft ETSI ES 203 312 V1.1.1 (2015-01)
1 Scope
The present document describes a method for distributed deployment and centralized control of a DOCSIS cable
broadband access system in which the cable network equipment is used in a plant where fibre is run to the cabinet (e.g.
in the basement of a customer's multiple dwelling unit) and coax to each customer. This architecture is collectively
referred to as Cabinet DOCSIS or "C-DOCSIS". It has been developed to meet the operability and manageability
requirements for cable networks that offer a variety of high-bandwidth services and provide QoS guarantees for these
services in a distributed architecture. This architecture applies to the operations, administration and management
(OAM) of cable broadband access networks.
The present document defines optional implementation architectures for CMTS equipment intended for use in
distributed deployments. It defines the functional modules within the CMTS, three different system architectures
utilizing the functional modules and the data and control interfaces between these modules for each of those
architectures. It also defines general device requirements for the different distributed CMTS architectures.
The present document corresponds to the CableLabs C-DOCSIS specification [i.4].
NOTE: DOCSIS® is a registered Trade Mark of Cable Television Laboratories, Inc., and is used in the present
document with permission.
2 References
2.1 Normative 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.
The following referenced documents are necessary for the application of the present document.
[1] IEEE Std 802.1Q (August 2011): "IEEE Standard for Local and metropolitan area networks -
Media Access Control (MAC) Bridges and Virtual Bridged Local Area Networks".
[2] CableLabs DHCP Options Registry: "CL-SP-CANN-DHCP-Reg-I10-130808", August 8, 2013,
Cable Television Laboratories, Inc.
[3] Control Point Discovery Interface Specification: "PKT-SP-CPD-C01-140314", March 14, 2014,
Cable Television Laboratories, Inc.
[4] ETSI TS 101 909-5: "Access and Terminals (AT); Digital Broadband Cable Access to the Public
Telecommunications Network; IP Multimedia Time Critical Services; Part 5: Dynamic Quality of
Service for the Provision of Real Time Services over Cable Television Networks using Cable
Modems".
[5] ETSI EN 302 878-3: "Access, Terminals, Transmission and Multiplexing (ATTM); Third
Generation Transmission Systems for Interactive Cable Television Services - IP Cable Modems;
Part 3: Downstream Radio Frequency Interface; DOCSIS 3.0".
[6] ETSI TS 102 879: "Access, Terminals, Transmission and Multiplexing (ATTM); IPCablecom
Services for delivering multimedia and voice over DOCSIS network infrastructure".
[7] ETSI EN 302 878-4: "Access, Terminals, Transmission and Multiplexing (ATTM); Third
Generation Transmission Systems for Interactive Cable Television Services - IP Cable Modems;
Part 4: MAC and Upper Layer Protocols; DOCSIS 3.0".
ETSI
9 Final draft ETSI ES 203 312 V1.1.1 (2015-01)
[8] ETSI EN 302 878-2: "Access, Terminals, Transmission and Multiplexing (ATTM); Third
Generation Transmission Systems for Interactive Cable Television Services - IP Cable Modems;
Part 2: Physical Layer; DOCSIS 3.0".
[9] IETF RFC 2236: "Internet Group Management Protocol", Version 2", November 1997.
[10] IETF RFC 2710: "Multicast Listener Discovery (MLD) for IPv6", October 1999.
[11] IETF RFC 2748: "The COPS (Common Open Policy Service) Protocol".
[12] IETF RFC 3376: "Internet Group Management Protocol, Version 3".
[13] IETF RFC 3810: "Multicast Listener Discovery Version 2 (MLDv2) for IPv6", June 2004.
[14] ETSI EN 302 878-5: "Access, Terminals, Transmission and Multiplexing (ATTM); Third
Generation Transmission Systems for Interactive Cable Television Services - IP Cable Modems;
Part 5: Security Services; DOCSIS 3.0".
2.2 Informative 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.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
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] IEEE Std 802.3-2012: "IEEE Standard for Ethernet, Section Five".
[i.2] IETF RFC 791/STD0005: "Internet Protocol". J. Postel. September 1981.
[i.3] IEFT RFC 793/STD0007: "Transmission Control Protocol". J. Postel. September 1981.
[i.4] Cable Television Laboratories: "Inc. C-DOCSIS System Specification, CM-SP-CDOCSIS-I01-
140829", August 29, 2014.
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
Access Control: process for connecting CMCs and controlling data communication
NOTE: Used to control the cable modems defined in the present document to access networks.
aggregation and forwarding: an aggregation network device, such as a PON optical line terminal (OLT), a router, or
a switch, receives data from CMCs and forwards the data to different uplinks for transmission based on the preset QoS
priorities
CDMM: used for exchanging configurations, status and management information between the system control module
and the radio frequency interface (RFI) module
C-DOCSIS CM: cable modem that complies with the requirements of DOCSIS 3.0
NOTE: See [5], [7], [8] and [14].
ETSI
10 Final draft ETSI ES 203 312 V1.1.1 (2015-01)
C-DOCSIS CMTS: CMTS that complies with the CMTS requirements of DOCSIS 3.0
NOTE 1: See [5], [7], [8] and [14].
NOTE 2: In the context of the present document, it consists of a CMC Controller and a CMC or multiple CMCs
operating together.
C-DOCSIS Data Tags (CDTs): used to identify a service flow to which each data packet belongs
C-DOCSIS System: method for distributed deployment and centralized control of a DOCSIS cable broadband access
system
NOTE: The C-DOCSIS system consists of the CMC Controller, CMC and CMs. It implements broadband data
access and forwarding, service configuration, as well as management and maintenance of coaxial cable
networks. It is synonymous with the term "distributed system architecture" which separates and
distributes the components of a CMTS in the various parts of the HFC network.
classified mapping: mapping process during which data packets are classified according to preset rules, CDTs are
added to the Ethernet frame header of the data packets to identify the service flows to which they belong and the
classified forwarding module maps the CDTs to the service flags, such as service VLAN (S-VLAN), IP ToS and
EPON Logical Link ID (LLID), supported by the aggregation network
CMC controller: forwards upstream and downstream service data and manages the configuration of the Cable Media
Converter
Coax Media Converter (CMC): converts data from a coaxial cable network to a digital optical packet network (such
as PON or Ethernet)
NOTE: The CMC connects to a cable modem through the coaxial cable network in the downstream direction and
to the CMC Controller through the digital optical packet network in the upstream direction.
data encapsulation and decapsulation: data processing method for converting data from one format to another
where the conversion is implemented by adding or deleting data for identification in the header or tail of the original
data packets
Dynamic QoS (DQoS): Quality of Service mechanism which dynamically creates, modifies and deletes DOCSIS
service flows based on call signalling to ensure the QoS for multimedia sessions, such as voice sessions
NOTE: With this mechanism, the system provides guaranteed bandwidth resources during a session and releases
the resources when the session ends.
management control: process for CMC Controllers and CMCs to manage the access, data, status and configurations
of CMCs and CMs
NOTE: The management control is based on the network architecture in distributed deployment mode defined in
the present document.
physical framing: process of collating data according to the fixed data encapsulation format to meet the requirements
of data transmission on the physical layer
service flow: transmits services at the MAC layer
NOTE: The system shapes and polices traffic and classifies traffic priorities based on QoS parameters defined in
the service flow.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ATDMA Advanced Time Division Multiple Access
BPI+ Baseline Privacy Interface Plus
BPKM Baseline Privacy Key Management
CCI Control and Classifier Interface
CDMM C-DOCSIS Management Message
C-DOCSIS Cabinet DOCSIS
ETSI
11 Final draft ETSI ES 203 312 V1.1.1 (2015-01)
CDT C-DOCSIS Data Tag
CFI Canonical Format Indicator
CLI Command Line Interface
CM Cable Modem
CMC Coax Media Converter
CMTS Cable Modem Termination System
COPS Common Open Policy Service
CoS Class of Service
CPD Control Point Discovery
CPE Consumer Premises Equipment
CRC Cyclic Redundancy Check
DEPI Downstream External PHY Interface
DHCP Dynamic Host Configuration Protocol
DNS Domain Name System
DOCSIS Data-over-Cable Service Interface Specification
DQoS Dynamic QoS
DS Downstream
DSA Dynamic Service Addition
DSC Dynamic Service Change
DSD Dynamic Service Deletion
DSID Downstream Service Identifier
DSx Dynamic Service Operations
EAE Early Authentication and Encryption
eDVA Embedded Digital Voice Adapter
eMTA Embedded Media Terminal Adapter
EPON Ethernet Passive Optical Network
FTTx Fibre To The "x"
NOTE: "x" includes node (FTTN), premise (FTTP), cabinet (FTTC), home (FTTH).
GCP Generic Control Plane
GE Gigabit Ethernet
GPON Gigabit-capable Passive Optical Network
HFC Hybrid Fibre-Coaxial
IEEE Institute of Electrical and Electronics Engineers
IGMP Internet Group Management Protocol
IMS IP Multimedia Subsystem
IP Internet Protocol
LLC Logical Link Control
LLID Logical Link IDentifier
MAC Media Access Control
MAN Metropolitan Area Network
MDD MAC Domain Descriptor
MLD Multicast Listener Discovery
MPI Main Path Interface
MTU Maximum Transmission Unit
MULPI MAC and Upper Layer Protocols Interface
NAT Network Address Translation
NLS Network Layer Signalling protocol
NMS Network Management System
NSI Network Side Interface
OAM Operations, Administration and Maintenance
OLT Optical Line Terminal
OMCI ONT Management and Control Interface
OMI Operation and Management Interface
ONU Optical Network Unit
OSSI Operations Support System Interface
OTT Over-the-Top
OUI Organizationally Unique Identifier
PCMM IPCablecom Multimedia
PCP Priority Code Point
PDU Protocol Data Unit
ETSI
12 Final draft ETSI ES 203 312 V1.1.1 (2015-01)
PHY Physical Layer
PON Passive Optical Network
QoS Quality of Service
RCC-ID Receive Channel Configuration Identifier
RCP Receive Channel Profile
RCP-ID Receive Channel Profile Identifier
RCS Receive Channel Set
RF Radio Frequency
RFI Radio Frequency Interface
RSP Response
SCDMA Synchronous Code Division Multiple Access
SFID Service Flow Identifier
SID Service Identifier
SNMP Simple Network Management Protocol
SNR Signal-to-Noise Ratio
STB Set-top Box
S-VLAN Service Virtual Local Area Network
TCP Transmission Control Protocol
TCS Transmit Channel Set
TFTP Trivial File Transfer Protocol
TLV Type Length Value
ToS Type of Service
TPID Tag Protocol IDentifier
UCID Upstream Channel IDentifier
UDP User Datagram Protocol
UEPI Upstream External PHY Interface
US Upstream
VID VLAN ID
VLAN Virtual Local Area Network
4 Requirements
In the present document, the following words are used to define the significance of particular requirements:
"shall" This word means that the item is an absolute requirement of the present document.
"shall not" This word means that the item is an absolute prohibition of the present document.
"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 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 before implementing any behaviour 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 the same item.
5 Overview
C-DOCSIS is based on proven DOCSIS3.0 technology and with the objectives of carrying high bandwidth services and
enabling cost effective system operation. C-DOCSIS presents a logical architecture of distributed deployment and
centralized management for the cable broadband access system. It defines the logical functional modules of the system
as well as related interfaces and protocols that support the architecture, through different combinations of the logical
functional modules; it specifies three different system implementations and the corresponding systems devices.
ETSI
13 Final draft ETSI ES 203 312 V1.1.1 (2015-01)
As the key to implementing the architecture of distributed deployment and centralized management, C-DOCSIS defines
the CMTS with a Coax Media Converter (CMC) and the CMC Controller to achieve the DOCSIS CMTS functionality,
as shown in figure 1. The CMC Controller implements the Metropolitan Area Network (MAN) interfaces and the CMC
implements the RF interfaces specified in [5], [7], [8] and [14], which are a part of C-DOCSIS. The CMC Controller
and CMC can be interconnected via a layer-2 or layer-3 network, such as digital optical packet network.

Figure 1: C-DOCSIS CMTS Network Diagram
The CMC Controller is deployed in the central office or headend to realize the centralized system management,
configuration and scheduling, thus enabling the distributed CMTS to inherit the advantages of a centralized DOCSIS
CMTS system. The CMC itself is distributed; it is deployed in the optical node, enabling the CMTS to introduce the
space-division multiplexing on top of the time-division multiplexing and frequency-division multiplexing utilized by
the centralized DOCSIS CMTS to achieve higher access bandwidth per user, which is highly desirable for the
applications with large upstream bandwidth consumption. With the distributed deployment of CMC and coupled with
the technical advantages of the digital optical packet network, the system can fully utilize the resources of the HFC
network and existing CMs to realize a cost-effective system deployment and operation, it reduces the return noise and
enhances the CMTS downlink channel SNR and is thus able to implement a higher order modulation scheme to obtain
higher bandwidth.
The present document describes three different types of CMC controllers and CMCs to implement the distributed
CMTS:
• Type I CMC implements all the DOCSIS CMTS functions and Type I CMC controller implements high-level
and partial-system management and configuration functions.
• Type II CMC implements the data forwarding and CM access functions and Type II CMC controller
implements the system management, configuration and scheduling functions.
• Type III CMC only implements the CMTS PHY function and the Type III CMC controller implements the rest
of the functions of the CMTS.
The distributed CMTS architecture is an open architecture, which nicely aligns with the traditional DOCSIS
architectures and with the HFC migration toward the FTTx network. The implementation of the various system
components is flexible. The CMC controller and CMC can be realized as stand-alone devices in accordance with the
provisions of the specification, or they can be integrated with other existing devices to meet the needs of future
development, such as the combination of CMC Controller with OLT, router and switches and the combination of CMC
with ONU, light stations and IP QAMs.
ETSI
14 Final draft ETSI ES 203 312 V1.1.1 (2015-01)
6 System Definition and Characteristics
6.1 System Definition and Description
The C-DOCSIS system defined in the present document consists of CMTSs and CMs. CMTSs consist of CMC
Controllers and CMCs
...

ETSI STANDARD
Integrated broadband cable
telecommunication networks (CABLE);
Cabinet DOCSIS (C-DOCSIS) System Specification

2 ETSI ES 203 312 V1.1.1 (2015-03)

Reference
DES/CABLE-00019
Keywords
access, broadband, cable, CMTS, data, DOCSIS,
HFC
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
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (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:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2015.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI 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 ES 203 312 V1.1.1 (2015-03)
Contents
Intellectual Property Rights . 7
Foreword . 7
Modal verbs terminology . 7
1 Scope . 8
2 References . 8
2.1 Normative references . 8
2.2 Informative references . 9
3 Definitions and abbreviations . 9
3.1 Definitions . 9
3.2 Abbreviations . 10
4 Requirements . 12
5 Overview . 12
6 System Definition and Characteristics . 13
6.1 System Definition and Description. 13
6.2 Characteristics . 14
7 Modules and Interfaces . 15
7.1 Functional Modules . 15
7.2 Interfaces on Functional Modules . 16
7.2.1 Radio Frequency Interface (RFI) . 16
7.2.2 Network Side Interface (NSI) . 16
7.2.3 Operation and Management Interface (OMI) . 16
7.2.4 C-DOCSIS Data Tag (CDT) . 17
7.2.5 C-DOCSIS Management Message (CDMM) . 17
7.2.6 Control and Classifier Interface (CCI) . 17
7.2.7 Main Path Interface (MPI) . 17
7.3 Data Packet Processing . 17
8 System Requirements and Devices . 18
8.1 System Requirements . 18
8.1.1 Data Forwarding Requirements . 18
8.1.2 QoS Requirements . 19
8.1.3 Security Requirements . 20
8.2 C-DOCSIS I System and Devices . 20
8.3 C-DOCSIS II System and Devices . 20
8.4 C-DOCSIS III System and Devices. 21
Annex A (normative): Service Flow Mapping to VLAN . 23
Annex B (normative): CDMM and CDT . 24
B.1 C-DOCSIS Tagging (CDT) . 24
B.2 C-DOCSIS Management Messaging (CDMM) . 25
B.2.1 CDMM Overview. 25
B.2.2 CDMM encapsulation . 25
B.2.2.1 Encapsulation Format . 25
B.2.2.2 Encapsulation with OAM Transport Layer . 25
B.2.2.2.1 Frame Structure . 26
B.2.2.2.2 Transport Layer Header . 26
B.2.2.2.3 PDU. 27
B.2.2.2.4 Acknowledgement. 27
B.2.2.2.5 Protocol . 28
B.2.2.3 Encapsulation with TCP/IP Transport Layer . 28
B.2.3 CDMM Message Contents . 28
ETSI
4 ETSI ES 203 312 V1.1.1 (2015-03)
B.2.3.1 Overview . 28
B.2.3.2 CDMM Message Index . 29
B.2.3.3 CDMM Message Specification . 32
B.2.3.3.1 DOCSIS Downstream Configuration . 32
B.2.3.3.1.1 SET DOWNSTREAM CONFIG REQUEST (0x01) . 32
B.2.3.3.1.2 SET DOWNSTREAM CONFIG RESPONSE (0x02) . 33
B.2.3.3.1.3 GET DOWNSTREAM CONFIG REQUEST (0x03). 33
B.2.3.3.1.4 GET DOWNSTREAM CONFIG RESPONSE (0x04). 33
B.2.3.3.2 DOCSIS Upstream Configuration . 34
B.2.3.3.2.1 SET UPSTREAM CONFIG REQUEST (0x05) . 34
B.2.3.3.2.2 SET UPSTREAM CONFIG RESPONSE (0x06) . 35
B.2.3.3.2.3 GET UPSTREAM CONFIG REQUEST (0x07) . 35
B.2.3.3.2.4 GET UPSTREAM CONFIG RESPONSE (0x08) . 35
B.2.3.3.3 Move CM Downstream . 36
B.2.3.3.3.1 SET MOVE CM DOWNSTREAM REQUEST (0x09) . 36
B.2.3.3.3.2 SET MOVE CM DOWNSTREAM RESPONSE (0x0a) . 37
B.2.3.3.3.3 GET MOVE CM DOWNSTREAM REQUEST (0x0b) . 37
B.2.3.3.3.4 GET MOVE CM DOWNSTREAM RESPONSE (0x0c) . 37
B.2.3.3.4 Move CM Upstream . 37
B.2.3.3.4.1 SET MOVE CM UPSTREAM REQUEST (0x0d) . 37
B.2.3.3.4.2 SET MOVE CM UPSTREAM RESPONSE (0x0e) . 38
B.2.3.3.4.3 GET MOVE CM UPSTREAM REQUEST (0x0f) . 38
B.2.3.3.4.4 GET MOVE CM UPSTREAM RESPONSE (0x10) . 38
B.2.3.3.5 Load Balancing . 38
B.2.3.3.5.1 SET CREATE/DESTROY LOAD BALANCING GROUP REQUEST (0x15) . 38
B.2.3.3.5.2 SET CREATE/DESTROY LOAD BALANCING GROUP RESPONSE (0x16) . 38
B.2.3.3.5.3 GET LOAD BALANCING GROUPS REQUEST (0x17) . 39
B.2.3.3.5.4 GET LOAD BALANCING GROUPS RESPONSE (0x18) . 39
B.2.3.3.5.5 SET ADD/REMOVE DOWNSTREAMS TO/FROM LOAD BALANCING GROUP
REQUEST (0x19) . 39
B.2.3.3.5.6 SET ADD/REMOVE DOWNSTREAMS TO/FROM LOAD BALANCING GROUP
RESPONSE (0x1a) . 39
B.2.3.3.5.7 GET LOAD BALANCING GROUP DOWNSTREAMS REQUEST (0x1b) . 40
B.2.3.3.5.8 GET LOAD BALANCING GROUP DOWNSTREAMS RESPONSE (0x1c) . 40
B.2.3.3.5.9 SET ADD/REMOVE UPSTREAMS TO/FROM LOAD BALANCING GROUP REQUEST
(0x1d) . 40
B.2.3.3.5.10 SET ADD/REMOVE UPSTREAMS TO/FROM LOAD BALANCING GROUP
RESPONSE (0x1e) . 41
B.2.3.3.5.11 GET LOAD BALANCING GROUP UPSTREAMS REQUEST (0x1f) . 41
B.2.3.3.5.12 GET LOAD BALANCING GROUP UPSTREAMS RESPONSE (0x20) . 41
B.2.3.3.5.13 SET ADD/REMOVE CM TO/FROM LOAD BALANCING GROUP REQUEST (0x21) . 42
B.2.3.3.5.14 SET ADD/REMOVE CM TO/FROM LOAD BALANCING GROUP RESPONSE (0x22) 42
B.2.3.3.5.15 GET LOAD BALANCING GROUP CM CONFIGURATION REQUEST (0x23) . 42
B.2.3.3.5.16 GET LOAD BALANCING GROUP CM CONFIGURATION RESPONSE (0x24) . 42
B.2.3.3.5.17 GET LOAD BALANCING GROUP ACTIVE CM REQUEST (0x25) . 43
B.2.3.3.5.18 GET LOAD BALANCING GROUP ACTIVE CM RESPONSE (0x26) . 43
B.2.3.3.5.19 SET EXCLUDE CM FROM LOAD BALANCING REQUEST (0x27) . 43
B.2.3.3.5.20 SET EXCLUDE CM FROM LOAD BALANCING RESPONSE (0x28) . 43
B.2.3.3.5.21 GET EXCLUDED CM CONFIGURATION REQUEST (0x29) . 43
B.2.3.3.5.22 GET EXCLUDED CM CONFIGURATION RESPONSE (0x2a) . 44
B.2.3.3.5.23 GET EXCLUDED ACTIVE CM REQUEST (0x2b) . 44
B.2.3.3.5.24 GET EXCLUDED ACTIVE CM'S RESPONSE (0x2c) . 44
B.2.3.3.5.25 SET FULL LOAD BALANCING GROUP REQUEST (0x2d) . 44
B.2.3.3.5.26 SET FULL LOAD BALANCING GROUP RESPONSE (0x2e) . 45
B.2.3.3.5.27 GET FULL LOAD BALANCING GROUP REQUEST (0x2f) . 45
B.2.3.3.5.28 GET FULL LOAD BALANCING GROUP RESPONSE (0x30) . 46
B.2.3.3.6 DOCSIS Upstream Input Power Level . 46
B.2.3.3.6.1 SET UPSTREAM INPUT POWER REQUEST (0x31) . 46
B.2.3.3.6.2 SET UPSTREAM INPUT POWER RESPONSE (0x32) . 46
B.2.3.3.6.3 GET UPSTREAM INPUT POWER REQUEST (0x33) . 47
B.2.3.3.6.4 GET UPSTREAM INPUT POWER RESPONSE (0x34) . 47
B.2.3.3.7 CM Arrival, Departure and Deletion . 47
ETSI
5 ETSI ES 203 312 V1.1.1 (2015-03)
B.2.3.3.7.1 CM ARRIVAL REQUEST (0x300) . 47
B.2.3.3.7.2 CM ARRIVAL RESPONSE (0x301) . 48
B.2.3.3.7.3 CM DEPARTURE EVENT (0x302) . 48
B.2.3.3.7.4 SET CM DELETE REQUEST (0x303) . 48
B.2.3.3.7.5 SET CM DELETE RESPONSE (0x304) . 49
B.2.3.3.8 QoS and Dynamic Services . 49
B.2.3.3.8.1 SET SERVICE CLASS NAME REQUEST (0x350) . 49
B.2.3.3.8.2 SET SERVICE CLASS NAME RESPONSE (0x351) . 49
B.2.3.3.8.3 SERVICE FLOW RESERVATION REQUEST (0x352) . 50
B.2.3.3.8.4 SERVICE FLOW RESERVATION RESPONSE (0x353) . 50
B.2.3.3.8.5 CDMM REGISTRATION REQUEST (0x354) . 50
B.2.3.3.8.6 CDMM REGISTRATION RESPONSE (0x355) . 51
B.2.3.3.8.7 CDMM REGISTRATION ACKNOWLEDGE (0x356) . 52
B.2.3.3.8.8 MULTICAST JOIN AUTHORIZATION REQUEST (0x357). 53
B.2.3.3.8.9 MULTICAST JOIN AUTHORIZATION RESPONSE (0x358). 53
B.2.3.3.8.10 SECURITY ASSOCIATION AUTH REQUEST (0x359) . 53
B.2.3.3.8.11 SECURITY ASSOCIATION AUTH RESPONSE (0x35A) . 54
B.2.3.3.8.12 CDMM DSA-REQ CM-INITIATED (0x360), CDMM DSC-REQ CM-INITIATED (0x361),
CDMM DSD-REQ CM-INITIATED (0x362) . 54
B.2.3.3.8.13 CDMM DSA-RSP CM-INITIATED (0x363), CDMM DSC-RSP CM-INITIATED (0x364),
CDMM DSD-RSP CM-INITIATED (0x365) . 55
B.2.3.3.8.14 CDMM DSA-ACK CM-INITIATED (0x366), CDMM DSC-ACK CM-INITIATED
(0x367) . 56
B.2.3.3.8.15 CDMM DSA-REQ CMTS-INITIATED (0x368), CDMM DSC-REQ CMTS-INITIATED
(0x369), CDMM DSD-REQ CMTS-INITIATED (0x36A) . 57
B.2.3.3.8.16 CDMM DSA-RSP CMTS-INITIATED (0x36B), CDMM DSC-RSP CMTS-INITIATED
(0x36C), CDMM DSD-RSP CMTS-INITIATED (0x36D) . 57
B.2.3.3.8.17 CDMM DSA-ACK CMTS-INITIATED (0x36E), CDMM DSC-ACK CMTS-INITIATED
(0x36F) . 58
B.2.3.3.9 CM and RFI Module Statistics . 59
B.2.3.3.9.1 GET CM STATUS REQUEST (0x701) . 59
B.2.3.3.9.2 GET CM STATUS RESPONSE (0x702) . 59
B.2.3.3.9.3 GET RF INTERFACES REQUEST (0x703) . 60
B.2.3.3.9.4 GET RF INTERFACES RESPONSE (0x704) . 60
B.2.3.3.9.5 GET RFI MAC STATISTICS REQUEST (0x705) . 61
B.2.3.3.9.6 GET RFI MAC STATISTICS RESPONSE (0x706). 61
B.2.3.3.9.7 GET SERVICES STATISTICS REQUEST (0x707) . 61
B.2.3.3.9.8 GET SERVICES STATISTICS RESPONSE (0x708) . 62
B.2.3.3.9.9 GET SIGNAL QUALITY REQUEST (0x709) . 62
B.2.3.3.9.10 GET SIGNAL QUALITY RESPONSE (0x70a) . 62
B.2.3.3.9.11 GET RF INTERFACE STATISTICS REQUEST (0x70b) . 62
B.2.3.3.9.12 GET RF INTERFACE STATISTICS RESPONSE (0x70c) . 63
B.2.3.3.9.13 GET DOWNSTREAM BONDING GROUPS REQUEST (0x70d) . 63
B.2.3.3.9.14 GET DOWNSTREAM BONDING GROUPS RESPONSE (0x70e) . 64
B.2.3.3.9.15 GET UPSTREAM BONDING GROUPS REQUEST (0x70f) . 64
B.2.3.3.9.16 GET UPSTREAM BONDING GROUPS RESPONSE (0x710) . 64
B.2.3.3.9.17 VENDOR-SPECIFIC MESSAGE (0x0F01) . 65
B.2.3.3.9.18 RFI SYSTEM EVENT MESSAGE (0x1001) . 65
B.2.4 CDMM Message Functional Flow . 65
B.2.4.1 RFI Module Initialization . 65
B.2.4.1.1 OAM Control Channel Startup . 66
B.2.4.1.2 TCP/IP Control Channel Startup . 66
B.2.4.2 CM Initialization and Registration . 66
Annex C (informative): Dynamic Service Operations . 69
C.1 Dynamic Service Operations Overview . 69
C.2 Session Setup . 69
C.3 Session Maintenance . 71
C.4 Session Termination . 73
ETSI
6 ETSI ES 203 312 V1.1.1 (2015-03)
C.5 Control Point Discovery Mechanism . 74
Annex D (informative): Bibliography . 76
History . 77

ETSI
7 ETSI ES 203 312 V1.1.1 (2015-03)
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://ipr.etsi.org).
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 ETSI Standard (ES) has been produced by ETSI Technical Committee Integrated broadband cable
telecommunication networks (CABLE).
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
8 ETSI ES 203 312 V1.1.1 (2015-03)
1 Scope
The present document describes a method for distributed deployment and centralized control of a DOCSIS cable
broadband access system in which the cable network equipment is used in a plant where fibre is run to the cabinet
(e.g. in the basement of a customer's multiple dwelling unit) and coax to each customer. This architecture is collectively
referred to as Cabinet DOCSIS or "C-DOCSIS". It has been developed to meet the operability and manageability
requirements for cable networks that offer a variety of high-bandwidth services and provide QoS guarantees for these
services in a distributed architecture. This architecture applies to the operations, administration and management
(OAM) of cable broadband access networks.
The present document defines optional implementation architectures for CMTS equipment intended for use in
distributed deployments. It defines the functional modules within the CMTS, three different system architectures
utilizing the functional modules and the data and control interfaces between these modules for each of those
architectures. It also defines general device requirements for the different distributed CMTS architectures.
The present document corresponds to the CableLabs C-DOCSIS specification [i.4].
NOTE: DOCSIS® is a registered Trade Mark of Cable Television Laboratories, Inc., and is used in the present
document with permission.
2 References
2.1 Normative 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.
The following referenced documents are necessary for the application of the present document.
[1] IEEE Std 802.1Q (August 2011): "IEEE Standard for Local and metropolitan area networks -
Media Access Control (MAC) Bridges and Virtual Bridged Local Area Networks".
[2] CableLabs DHCP Options Registry: "CL-SP-CANN-DHCP-Reg-I10-130808", August 8, 2013,
Cable Television Laboratories, Inc.
[3] Control Point Discovery Interface Specification: "PKT-SP-CPD-C01-140314", March 14, 2014,
Cable Television Laboratories, Inc.
[4] ETSI TS 101 909-5: "Access and Terminals (AT); Digital Broadband Cable Access to the Public
Telecommunications Network; IP Multimedia Time Critical Services; Part 5: Dynamic Quality of
Service for the Provision of Real Time Services over Cable Television Networks using Cable
Modems".
[5] ETSI EN 302 878-3: "Access, Terminals, Transmission and Multiplexing (ATTM); Third
Generation Transmission Systems for Interactive Cable Television Services - IP Cable Modems;
Part 3: Downstream Radio Frequency Interface; DOCSIS 3.0".
[6] ETSI TS 102 879: "Access, Terminals, Transmission and Multiplexing (ATTM); IPCablecom
Services for delivering multimedia and voice over DOCSIS network infrastructure".
[7] ETSI EN 302 878-4: "Access, Terminals, Transmission and Multiplexing (ATTM); Third
Generation Transmission Systems for Interactive Cable Television Services - IP Cable Modems;
Part 4: MAC and Upper Layer Protocols; DOCSIS 3.0".
ETSI
9 ETSI ES 203 312 V1.1.1 (2015-03)
[8] ETSI EN 302 878-2: "Access, Terminals, Transmission and Multiplexing (ATTM); Third
Generation Transmission Systems for Interactive Cable Television Services - IP Cable Modems;
Part 2: Physical Layer; DOCSIS 3.0".
[9] IETF RFC 2236: "Internet Group Management Protocol", Version 2", November 1997.
[10] IETF RFC 2710: "Multicast Listener Discovery (MLD) for IPv6", October 1999.
[11] IETF RFC 2748: "The COPS (Common Open Policy Service) Protocol".
[12] IETF RFC 3376: "Internet Group Management Protocol, Version 3".
[13] IETF RFC 3810: "Multicast Listener Discovery Version 2 (MLDv2) for IPv6", June 2004.
[14] ETSI EN 302 878-5: "Access, Terminals, Transmission and Multiplexing (ATTM); Third
Generation Transmission Systems for Interactive Cable Television Services - IP Cable Modems;
Part 5: Security Services; DOCSIS 3.0".
2.2 Informative 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.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
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] IEEE Std 802.3-2012: "IEEE Standard for Ethernet, Section Five".
[i.2] IETF RFC 791/STD0005: "Internet Protocol". J. Postel. September 1981.
[i.3] IEFT RFC 793/STD0007: "Transmission Control Protocol". J. Postel. September 1981.
[i.4] Cable Television Laboratories: "Inc. C-DOCSIS System Specification, CM-SP-CDOCSIS-I01-
140829", August 29, 2014.
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
access control: process for connecting CMCs and controlling data communication
NOTE: Used to control the cable modems defined in the present document to access networks.
aggregation and forwarding: an aggregation network device, such as a PON optical line terminal (OLT), a router, or
a switch, receives data from CMCs and forwards the data to different uplinks for transmission based on the preset QoS
priorities
CDMM: used for exchanging configurations, status and management information between the system control module
and the radio frequency interface (RFI) module
C-DOCSIS CM: cable modem that complies with the requirements of DOCSIS 3.0
NOTE: See [5], [7], [8] and [14].
C-DOCSIS CMTS: CMTS that complies with the CMTS requirements of DOCSIS 3.0
NOTE 1: See [5], [7], [8] and [14].
ETSI
10 ETSI ES 203 312 V1.1.1 (2015-03)
NOTE 2: In the context of the present document, it consists of a CMC Controller and a CMC or multiple CMCs
operating together.
C-DOCSIS Data Tags (CDTs): used to identify a service flow to which each data packet belongs
C-DOCSIS System: method for distributed deployment and centralized control of a DOCSIS cable broadband access
system
NOTE: The C-DOCSIS system consists of the CMC Controller, CMC and CMs. It implements broadband data
access and forwarding, service configuration, as well as management and maintenance of coaxial cable
networks. It is synonymous with the term "distributed system architecture" which separates and
distributes the components of a CMTS in the various parts of the HFC network.
classified mapping: mapping process during which data packets are classified according to preset rules, CDTs are
added to the Ethernet frame header of the data packets to identify the service flows to which they belong and the
classified forwarding module maps the CDTs to the service flags, such as service VLAN (S-VLAN), IP ToS and
EPON Logical Link ID (LLID), supported by the aggregation network
CMC controller: forwards upstream and downstream service data and manages the configuration of the Cable Media
Converter
Coax Media Converter (CMC): converts data from a coaxial cable network to a digital optical packet network (such
as PON or Ethernet)
NOTE: The CMC connects to a cable modem through the coaxial cable network in the downstream direction and
to the CMC Controller through the digital optical packet network in the upstream direction.
data encapsulation and decapsulation: data processing method for converting data from one format to another
where the conversion is implemented by adding or deleting data for identification in the header or tail of the original
data packets
Dynamic QoS (DQoS): Quality of Service mechanism which dynamically creates, modifies and deletes DOCSIS
service flows based on call signalling to ensure the QoS for multimedia sessions, such as voice sessions
NOTE: With this mechanism, the system provides guaranteed bandwidth resources during a session and releases
the resources when the session ends.
management control: process for CMC Controllers and CMCs to manage the access, data, status and configurations
of CMCs and CMs
NOTE: The management control is based on the network architecture in distributed deployment mode defined in
the present document.
physical framing: process of collating data according to the fixed data encapsulation format to meet the requirements
of data transmission on the physical layer
service flow: transmits services at the MAC layer
NOTE: The system shapes and polices traffic and classifies traffic priorities based on QoS parameters defined in
the service flow.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ATDMA Advanced Time Division Multiple Access
BPI+ Baseline Privacy Interface Plus
BPKM Baseline Privacy Key Management
CCI Control and Classifier Interface
CDMM C-DOCSIS Management Message
C-DOCSIS Cabinet DOCSIS
CDT C-DOCSIS Data Tag
CFI Canonical Format Indicator
CLI Command Line Interface
CM Cable Modem
ETSI
11 ETSI ES 203 312 V1.1.1 (2015-03)
CMC Coax Media Converter
CMTS Cable Modem Termination System
COPS Common Open Policy Service
CoS Class of Service
CPD Control Point Discovery
CPE Consumer Premises Equipment
CRC Cyclic Redundancy Check
DEPI Downstream External PHY Interface
DHCP Dynamic Host Configuration Protocol
DNS Domain Name System
DOCSIS Data-Over-Cable Service Interface Specification
DQoS Dynamic QoS
DS Downstream
DSA Dynamic Service Addition
DSC Dynamic Service Change
DSD Dynamic Service Deletion
DSID Downstream Service Identifier
DSx Dynamic Service Operations
EAE Early Authentication and Encryption
eDVA Embedded Digital Voice Adapter
eMTA Embedded Media Terminal Adapter
EPON Ethernet Passive Optical Network
FTTx Fibre To The "x"
NOTE: "x" includes node (FTTN), premise (FTTP), cabinet (FTTC), home (FTTH).
GCP Generic Control Plane
GE Gigabit Ethernet
GPON Gigabit-capable Passive Optical Network
HFC Hybrid Fibre-Coaxial
IEEE Institute of Electrical and Electronics Engineers
IGMP Internet Group Management Protocol
IMS IP Multimedia Subsystem
IP Internet Protocol
LLC Logical Link Control
LLID Logical Link IDentifier
MAC Media Access Control
MAN Metropolitan Area Network
MDD MAC Domain Descriptor
MLD Multicast Listener Discovery
MPI Main Path Interface
MTU Maximum Transmission Unit
MULPI MAC and Upper Layer Protocols Interface
NAT Network Address Translation
NLS Network Layer Signalling protocol
NMS Network Management System
NSI Network Side Interface
OAM Operations, Administration and Maintenance
OLT Optical Line Terminal
OMCI ONT Management and Control Interface
OMI Operation and Management Interface
ONU Optical Network Unit
OSSI Operations Support System Interface
OTT Over-the-Top
OUI Organizationally Unique Identifier
PCMM IPCablecom Multimedia
PCP Priority Code Point
PDU Protocol Data Unit
PHY Physical Layer
PON Passive Optical Network
QoS Quality of Service
RCC-ID Receive Channel Configuration Identifier
ETSI
12 ETSI ES 203 312 V1.1.1 (2015-03)
RCP Receive Channel Profile
RCP-ID Receive Channel Profile Identifier
RCS Receive Channel Set
RF Radio Frequency
RFI Radio Frequency Interface
RSP Response
SCDMA Synchronous Code Division Multiple Access
SFID Service Flow Identifier
SID Service Identifier
SNMP Simple Network Management Protocol
SNR Signal-to-Noise Ratio
STB Set-Top Box
S-VLAN Service Virtual Local Area Network
TCP Transmission Control Protocol
TCS Transmit Channel Set
TFTP Trivial File Transfer Protocol
TLV Type Length Value
ToS Type of Service
TPID Tag Protocol IDentifier
UCID Upstream Channel IDentifier
UDP User Datagram Protocol
UEPI Upstream External PHY Interface
US Upstream
VID VLAN ID
VLAN Virtual Local Area Network
4 Requirements
In the present document, the following words are used to define the significance of particular requirements:
"shall" This word means that the item is an absolute requirement of the present document.
"shall not" This word means that the item is an absolute prohibition of the present document.
"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 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 before implementing any behaviour 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 the same item.
5 Overview
C-DOCSIS is based on proven DOCSIS3.0 technology and with the objectives of carrying high bandwidth services and
enabling cost effective system operation. C-DOCSIS presents a logical architecture of distributed deployment and
centralized management for the cable broadband access system. It defines the logical functional modules of the system
as well as related interfaces and protocols that support the architecture, through different combinations of the logical
functional modules; it specifies three different system implementations and the corresponding systems devices.
As the key to implementing the architecture of distributed deployment and centralized management, C-DOCSIS defines
the CMTS with a Coax Media Converter (CMC) and the CMC Controller to achieve the DOCSIS CMTS functionality,
as shown in figure 1. The CMC Controller implements the Metropolitan Area Network (MAN) interfaces and the CMC
implements the RF interfaces specified in [5], [7], [8] and [14], which are a part of C-DOCSIS. The CMC Controller
and CMC can be interconnected via a layer-2 or layer-3 network, such as digital optical packet network.
ETSI
13 ETSI ES 203 312 V1.1.1 (2015-03)

Figure 1: C-DOCSIS CMTS Network Diagram
The CMC Controller is deployed in the central office or headend to realize the centralized system management,
configuration and scheduling, thus enabling the distributed CMTS to inherit the advantages of a centralized DOCSIS
CMTS system. The CMC itself is distributed; it is deployed in the optical node, enabling the CMTS to introduce the
space-division multiplexing on top of the time-division multiplexing and frequency-division multiplexing utilized by
the centralized DOCSIS CMTS to achieve higher access bandwidth per user, which is highly desirable for the
applications with large upstream bandwidth consumption. With the distributed deployment of CMC and coupled with
the technical advantages of the digital optical packet network, the system can fully utilize the resources of the HFC
network and existing CMs to realize a cost-effective system deployment and operation, it reduces the return noise and
enhances the CMTS downlink channel SNR and is thus able to implement a higher order modulation scheme to obtain
higher bandwidth.
The present document describes three different types of CMC controllers and CMCs to implement the distributed
CMTS:
• Type I CMC implements all the DOCSIS CMTS functions and Type I CMC controller implements high-level
and partial-system management and configuration functions.
• Type II CMC implements the data forwarding and CM access functions and Type II CMC controller
implements the system management, configuration and scheduling functions.
• Type III CMC only implements the CMTS PHY function and the Type III CMC controller implements the rest
of the functions of the CMTS.
The distributed CMTS architecture is an open architecture, which nicely aligns with the traditional DOCSIS
architectures and with the HFC migration toward the FTTx network. The implementation of the various system
components is flexible. The CMC controller and CMC can be realized as stand-alone devices in accordance with the
provisions of the specification, or they can be integrated with other existing devices to meet the needs of future
development, such as the combination of CMC Controller with OLT, router and switches and the combination of CMC
with ONU, light stations and IP QAMs.
6 System Definition and Characteristics
6.1 System Definition and Description
The C-DOCSIS system defined in the present document consists of CMTSs and CMs. CMTSs consist of CMC
Controllers and CMCs as shown in figure 2. The present document defines the functional modules, interface and
requirements of CMTSs in detail, which are implemented by the CMC Controllers and CMCs.
ETSI
14 ETSI ES 203 312 V1.1.1 (2015-03)
A C-DOCSIS CMTS shall comply with [5], [7], [8] and [14]. C-DOCSIS CMs are compliant with the requirements in
[5], [7], [8] and [14].
In this distributed system architecture, the CMC Controller manages the configuration of the CMC and/or forwards
upstream and downstream service data. The CMC converts and forwards the upstream and downstream service data and
the management and configuration data of the CMs. The CM terminates the upstream and downstream service data, as
well as receiving and responding to management and configuration data. The CMC Controller connects to the CMC
through a digital optical packet network. The CMC connects to the CMs through a coax RF network.
The configuration system configures services and devices on the distributed system architecture. It generates and issues
configuration files and upgrades the software of the CMs. The configuration system consists of the DHCP server,
configuration file server, software downloading server and time protocol server. The NMS consists of the SNMP
management system and the Syslog server.

Figure 2: C-DOCSIS System
6.2 Characteristics
The present document introduces several features based on a traditional DOCSIS system, as listed below:
• Distributed architecture for deep-fibre network: The present document introduces a three-level distributed
architecture including the CMC Controlle
...