Cisco Headend System Release 2.7
Decide Binding Type
736107 Rev D
25
Autobinding in SR 4.2 and Earlier
Autobinding is a process that allows the CableCARD module to bind to a two-way
Autobinding is a process that allows the CableCARD module to bind to a two-way
host. The procedure with SR 4.2 (and earlier) is as follows.
1 When the CableCARD module is inserted into a two-way host, the host and the
1 When the CableCARD module is inserted into a two-way host, the host and the
CableCARD module exchange keys to authenticate each other.
2 After the keys are verified and the host goes into two-way mode, the
CableCARD module sends an upstream message to the DNCS that includes the
CableCARD ID and the Host ID.
3 The DNCS looks up the Host ID in the CRL. Based on the information in the
CRL, the DNCS takes one of the following actions:
If the host is in the list, the DNCS does not allow the CableCARD module to
bind to the host.
If the host is not in the list, the DNCS continues with the next step.
4 The DNCS looks up the CableCARD module/Host in its database to determine if
a Host Bound value has been defined for this pair. Based on this information, the
DNCS takes one of the following actions:
If the pair is in the list, and the Host Bound value is Yes, the DNCS allows
binding for this CableCARD/host pair.
If the pair is in the list, and the Host Bound value is No, the DNCS does not
allow binding for this CableCARD module/host pair.
If the CableCARD module is in the list with a different host, the DNCS
allows binding for this CableCARD module/host pair.
If the pair is not in the list, the DNCS allows binding for this CableCARD
module/host pair.
5 The DNCS sends the podData file containing the binding permissions to the BFS
for those pairs that are allowed to bind (based on the above criteria).
Note: The CableCARD module/host pairs denied binding are not placed in the
Note: The CableCARD module/host pairs denied binding are not placed in the
podData file.
6 The CableCARD module reads the podData file on the BFS.
If the CableCARD module finds its pairing in the podData file, the
CableCARD module authorizes the binding between itself and the host.
If the CableCARD module does not find its pairing in the podData file, the
CableCARD module does not authorize the binding.