...

RDK-B devices provide multiple interfaces like MoCA, WiFi, Ethernet and so on for the clients to get connected. LMLite, a component within RDK-B, does the job of updating the Host tables (Host table is a table containing the data of connected clients over various interfaces) based on the devices connected over MoCA, WiFi and Ethernet.

High Level Architecture

Image Modified

Figure 1 - LMLite High Level Architecture

...

LMLite interacts with other components of RDK-B stack over DBUS. Each of these components registers a "callback" function with respective HAL. The HAL performs a “callback” whenever there is an update in connected clients. This triggers a DBus call to LMLite with the necessary data. LMLite receives this data and adds it to a the Host tables.

Notifications

LMLite notifies the Notification component which in turn tells the interested PAs about the connection and disconnection of the connected devices.

There are three types of notification messages for the connected clients to work.

NotifyMsg 1

Notification Message from the individual interface component to LMLite about any update of the existing connected devices or any new connections.

In the first type of notification message(NotifyMsg 1), the connected device components like WiFi, MoCA, Ethernet sets a dedicated parameter of LMLite. As and when this notify message comes from a component to LMLite, the dedicated parameter is parsed and the host table is updated accordingly.

Example: For WiFi the dedicated parameter is
“Device.Hosts.X_RDKCENTRAL-COM_LMHost_Sync_From_WiFi”.
This parameter is of string type and contains values for fields phyAddr, ssid, status and so on.

NotifyMsg 2

Notification Message from LMLite to the Notify component

NotifyMsg 3

Notification message from Notify component to the PA’s who have registered for notifications for connected device.

Objects

LMLite has three objects in its DML layer:

...