...

• Support for TR-069 active and passive notifications.
  • Dependency: notify_comp and its recipe.
  • Dependency: when using an older release of RDK-B, be sure to apply the following locking bug fix, which prevents a race condition on a bulk parameter value set that results in intermittent loss of notifications for some changed parameters.
  • Tr069PA support in notify_comp.

    Jira
    server RDK serverId 11deff04-0380-3a3d-a916-0849d4e573f7 key RDKB-346

  • No VALUE CHANGE notification may be sent to the ACS when the origin of the change is a SetParameterValues through TR-069. The TR-069 PA must discard value change events based on the event's origin.
    JiraserverRDKserverId11deff04-0380-3a3d-a916-0849d4e573f7keyRDKB-345
  • Reliable delivery of events across TR-069 agent restart. If a VALUE CHANGE notification is not delivered before restart, it must be retried until successful, even across reboots.
    JiraserverRDKserverId11deff04-0380-3a3d-a916-0849d4e573f7keyRDKBSUP-357
• Support for TR-069 diagnostics complete notifications.
  • Send 8 DIAGNOSTICS COMPLETE to the ACS only when the diagnostics test was initiated through TR-069. Supported for Device.IP.Diagnostics.TraceRoute and Device.IP.Diagnostics.IPPing.
    JiraserverRDKserverId11deff04-0380-3a3d-a916-0849d4e573f7keyRDKB-326
• Custom Mapper to translate the internal data model to a different one offered through TR-069. This can fix:
  • TR-069 data model violations such as Device.SelfHeal
  • CableLabs (CM-SP-eRouter) instance index standardisation, e.g. Device.WiFi.Radio.10000. and Device.WiFi.SSID.10001
  • MSO-specific data model object and parameter names
    JiraserverRDKserverId11deff04-0380-3a3d-a916-0849d4e573f7keyRDKBDEV-55

Enhancement under Consideration

...