Chapter 22: Channel Bonding
STANDARD Revision 1.0
C4® CMTS Release 8.3 User Guide
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
695
known as non-verbose RCPs) or through a verbose reporting of Receive Channel Profile(s) for both standard and vendor-
specific profiles. The MAC domain descriptor (MDD) directs the CMs how to message their RCPs.
Verbose RCP Reporting
Use the following two commands to enable verbose RCP reporting and dynamic RCC selection:
configure interface cable-mac <mac> cable verbose-cm-rcp
configure interface cable-mac <mac> cable dynamic-rcc
When configured to enable verbose RCP reporting, the C4/c CMTS tells the CM to provide verbose reporting of Receive
Channel Profile(s) for both standard and vendor-specific profiles.
The C4/c CMTS processes these RCPs and selects one that will be used to configure the cable modem. A Receive Channel
Configuration (RCC) is communicated from the C4/c CMTS to the CM to inform the CM how it is to configure its Receive
Channels (RCs) and Receive Modules (RMs) to communicate with the CER. This CER-resident RCP selection process is a
complex, multi-stage algorithm. To aid the C4/c CMTS software in supporting an increasing number of arbitrarily complex
RCPs, the DOCSIS specification defines the notion of standard RCPs. Each standard RCP is represented by a unique RCP-ID
and is a well-known model of a multiple-channel subscriber device. The RCC selection process in the C4/c CMTS will
process these verbose RCPs to exclude non-conforming RCPs. It then considers configured RCCs and dynamic RCCs (in that
order) to build a set of candidate RCCs, ultimately settling upon a single suitable RCC.
Conforming verbose RCPs satisfy the following criteria:
Nx1 receive channel configuration where all receive channels connect to a single receive module, where N > 1.
Nx1 receive channel configuration where all receive channels connect to a single receive module with unlimited
capture bandwidth (adjacent channels parameters omitted), where N > 1.
NxN receive channel configuration with receive channel connectivity, where N > 1
Rx channel 1 -> Rx Module 1
Rx channel 2 -> Rx Module 2
Rx channel 3 -> Rx Module 3
Rx channel N -> Rx Module N
They do not require common PHY parameter checks
They do not specify multiple frequency blocks per module
They do not specify any module-to-module connectivity requirements
They do not support module resequencing subset limitations