...

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.
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.

NotifyMsg 1

In this type of notification message the 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 componentIn this type of notification message, LMLite monitors the values of all the connected clients. Whenever any connection/disconnection updates happen in host table, it updates the notify component. The data sent from LMLite to notify component is status, MAC, interface of the connected device.

NotifyMsg 3

Notification message from Notify component maintains a table of parameters for which PAs are interested to the PA’s who have registered for notifications for connected devicebe notified. Whenever the notify component receives a NotifyMsg 2 from LMLite, it search's this table and notifies the interested protocol agents.

Objects

LMLite has three objects in its DML layer:

Parameters supported by Object - Devcie.Hosts.

Device.Hosts.X_CISCO_COM_ConnectedDeviceNumber
Device.Hosts.X_CISCO_COM_ConnectedWiFiNumber
Device.Hosts.X_RDKCENTRAL-COM_HostVersionId
Device.Hosts.X_RDKCENTRAL-COM_HostCountPeriod
Device.Hosts.Host.{i}.PhysAddress
Device.Hosts.Host.{i}.IPAddress
Device.Hosts.Host.{i}.DHCPClient
Device.Hosts.Host.{i}.HostName
Device.Hosts.Host.{i}.LeaseTimeRemaining
Device.Hosts.Host.{i}.X_RDKCENTRAL-COM_DeviceType

Parameters supported by Object - Devcie.XHosts.

Device.XHosts.X_CISCO_COM_ConnectedDeviceNumber
Device.XHosts.XHost.{i}.Alias
Device.XHosts.XHost.{i}.PhysAddress
Device.XHosts.XHost.{i}.IPAddress
Device.XHosts.XHost.{i}.DHCPClient
Device.XHosts.XHost.{i}.HostName
Device.XHosts.XHost.{i}.LeaseTimeRemaining
Device.XHosts.XHost.{i}.X_RDKCENTRAL-COM_DeviceType

Parameters supported by Object - Devcie.X_RDKCENTRAL-COM_REPORT.

Device.X_RDKCENTRAL-COM_Report.NetworkDevicesStatus.Enabled
Device.X_RDKCENTRAL-COM_Report.NetworkDevicesStatus.ReportingPeriod
Device.X_RDKCENTRAL-COM_Report.NetworkDevicesStatus.PollingPeriod
Device.X_RDKCENTRAL-COM_Report.NetworkDevicesStatus.Default.ReportingPeriod
Device.X_RDKCENTRAL-COM_Report.NetworkDevicesStatus.Default.PollingPeriod
Device.X_RDKCENTRAL-COM_Report.NetworkDevicesTraffic.Enabled
Device.X_RDKCENTRAL-COM_Report.NetworkDevicesTraffic.ReportingPeriod
Device.X_RDKCENTRAL-COM_Report.NetworkDevicesTraffic.PollingPeriod
Device.X_RDKCENTRAL-COM_Report.NetworkDevicesTraffic.Default.ReportingPeriod
Device.X_RDKCENTRAL-COM_Report.NetworkDevicesTraffic.Default.PollingPeriod
Device.X_RDKCENTRAL-COM_Report.InterfaceDevicesWifiExtender.Enabled