Sign in Subscribe

TR-369 USP Notification Types

Last updated on 
TR-369 USP Notification Types
"A bird informs teddy bear about all events" by DALL-E

Understanding TR-369 USP (User Services Platform) and its notification types is crucial for effective IoT (Internet of Things) device management. The protocol, managed by the Broadband Forum, outlines several types of notifications that are crucial for the operation and maintenance of IoT devices.

Here, we will delve into the specifics of these notification types: ValueChange, ObjectCreation, ObjectDeletion, OperationComplete, OnBoardRequest, and Event.

1. ValueChange Notification

The ValueChange notification is essentially a signal that tells a Controller that a change has occurred in the value of one or more parameters to which it has subscribed. This notification is triggered any time the defined change occurs, regardless of whether it was instigated by the subscribing Controller or another entity. This allows the Controller to keep tabs on crucial parameter states and act accordingly when changes are identified.

2. ObjectCreation and ObjectDeletion Notifications

The ObjectCreation and ObjectDeletion notifications signal when an instance of the subscribed Multi-Instance Objects is either added to or removed from the Agent’s Instantiated Data Model. Like the ValueChange notification, these notifications are triggered regardless of whether the subscribing Controller initiated the creation or deletion process. Notably, the ObjectCreation notification includes unique key parameters and their associated values, providing comprehensive details about the created object.

3. OperationComplete Notification

OperationComplete notification provides a status update when an asynchronous object-defined operation finishes. This operation can end successfully or unsuccessfully. In either case, a notification is sent, ensuring the Controller is kept informed about the status of operations, a crucial factor for monitoring and troubleshooting.

4. OnBoardRequest Notification

The OnBoardRequest notification comes into play when an Agent needs to communicate with a Controller that can provide onboarding procedures. Triggered by an external source, it's primarily used when the Agent communicates with the Controller for the first time. The Agent is required to send an OnBoardRequest notification under two circumstances: when the SendOnBoardRequest() command is executed and when directed by internal application policy.

5. Event Notification

The Event notification is used to signify that an Object-defined event was triggered on the Agent. These events are defined in the data model and can vary significantly, depending on the parameters that were returned as part of the notification. This notification type helps track occurrences in the system that could potentially influence performance or operation.

In conclusion, understanding TR-369 USP Notification Types is integral to ensuring the smooth operation and management of IoT devices. By effectively managing these notifications, organizations can promptly respond to changes in system parameters, operations, and events, ultimately maximizing the performance and reliability of their IoT systems.

  1. Broadband Forum, "User Services Platform (USP)", TR-369 Issue 1 Amendment 2, January 2022, p. 125-132. https://www.broadband-forum.org/tr-369
  2. USP Record Definitions, GitHub Repository, https://github.com/BroadbandForum/usp