THOMSON TR-069 - Event Subscription

E-DOC-CTC-20071119-0003 v1.0
57
4| Monitoring and Diagnostics
4.5 Event Subscription
Introduction
The ACS can subscribe to particular parameter change events. When the value of such a parameter changes,
the CPE must notify the change to the ACS.
Two types of event subscription exist:
 Passive change notification: whenever the parameter value changes, the CPE must include the new value
in the ParameterList argument of the Inform message that is sent the next time a session is established to
the ACS. For example, a periodic Inform or an Inform due to a Connection request.
 Active change notification: whenever the parameter value changes, the CPE must initiate a session to the
ACS and include the new value in the ParameterList argument of the sent Inform message.
RPCs for event subscription
Following ACS RPCs are relevant to event subscription:
 GetParameterAttributes RPC: the ACS can use this RPC to learn the event subscriptions associated with
one or more CPE parameters. The ParameterNames argument is a list of the names of the requested
parameters.
Example of the ParameterNames argument:
 SetParameterAttributes RPC: the ACS can use this RPC to modify the event subscriptions associated with
one or more CPE parameters. The ParameterList argument contains the list of changes to the event
subscriptions.
Example of the ParameterList argument:
Entry Value
1 InternetGatewayDevice.Layer2Bridging. (i.e. all parameters within this object)
2 InternetGatewayDevice.DeviceInfo.SerialNumber (i.e. this specific parameter)
Entry Field Value
1
Name InternetGatewayDevice.Layer2Bridging.
NotificationChange 1 (true)
Notification 1 (passive)
2
Name InternetGatewayDevice.DeviceInfo.SerialNumber
NotificationChange 1 (true)
Notification 2 (active)