Introduction

RDK-B was designed to support any wide area network (WAN). Gateways using RDK-B may provide a DOCSIS interface, but that DOCSIS code is typically tied to a particular piece of silicon and may even be provided by that silicon vendor. And the core philosophy of RDK-B was to be hardware independent.

To address this situation, RDK-B does not include DOCSIS. It only includes components that provide an abstraction layer software interface to third party WAN. For the DOCSIS WAN, this component is known as the Cable Modem (CM) Agent. CM Agent provides interfaces for integrating WAN interfaces with RDK-B. RDK-B is not tied to DOCSIS and may be used with any WAN interface. Other RDK-B software components can be created that provide interfaces to other WANs.

Objects

CMAgent has three objects in its DML layer:

Device.DeviceInfo.
Device.X_CISCO_COM_CableModem.
Device.X_RDKCENTRAL-COM_CableModem.

CM HAL

This hardware abstraction layer (HAL) concept is used for every interface. The CM HAL provides a well-defined software interface that cable modem software developers can use to interface to RDK-B.

cm_hal.c provides function call prototypes and structure definitions used for the RDK-Broadband CM HAL.

Some example APIs are listed below:

cm_hal_InitDB
docsis_InitDS
docsis_InitUS
cm_hal_GetCPEList
docsis_GetCertStatus
docsis_getCMStatus
docsis_GetDOCSISInfo
cm_hal_GetDHCPInfo