TR-369
TR-369, also called User Service Platform (USP), like its predecessor TR-069, is a protocol standard developed by Broadband-Forum for the management and analysis of devices connected to a network. This technical standard defines the protocol, architecture and data model of the application layer for communication between provider / customer and one or more devices.[1]
Origin[edit]
Since the old model (created in 2004) was no longer sufficient, due to the increasing number of communication-capable devices per household, an update was necessary. In 2018 the new protocol, based on the old model, was published with a larger variety of functions. These functions make it possible to analyze and manage several devices at the same time.
Architecture[edit]
The USP consists of a network of controllers and agents that communicate with each other via Message Transfer Protocol (MTP). The communication between the respective endpoints is permanently established (always-on) in order to minimize the connection-establishment messages and networkutilization.
An agent consists of an Instantiated Data Model (IDM) and a Supported Data Model (SDM)[2]. The IDM combines all service elements that are connected to the agent. It contains status, objects, sub-objects, parameters, events and commands of the service elements that were selected during configuration. The SDM, on the other hand, contains all objects, sub-objects, parameters, events and commands of the service elements that are available to the agent. For example, two identical devices have the same SDM, but can have different IDMs depending on the configuration.
An agent is addressed by one or more controllers in order to perform a service on one or more service elements. The controller consist of an application/policy logic with different settings and can have a database with the connected agents, as well as their capabilities and status. It acts as an interface for user applications, who want to gain access to the service elements via the user service platform.
The strength of TR-369[edit]
Efficient message flow[edit]
Due to the always-on connection between the controller and agent, the number of messages in the network is minimized. Binary data processing and the use of relative paths of directories reduce the size of the transmitted data.
Secured messages[edit]
With the end-to-end (E2E) messaging feature, it is possible to store a session context that enables rights, security and segmentation of the messages.[3]
Multi-stakeholder architecture[edit]
The protocol enables several users to have access to different service elements. For example, two companies with different permissions could be assigned to manage the devices of one household.
Device lifecycle management[edit]
The protocol makes it possible to influence the entire life cycle of a device. This could be, for example, service provision, device authentication or -configuration.
Multiple communication protocols[edit]
By using MTPs as a flexible transport layer, the agent and controller can agree on the optimal communication protocol for the respective application. MTPs are currently specified for the following protocols: STOMP, CoAP, MQTT and WebSockets.[4]
Downward Compatibility[edit]
In order to be able to continue to use the old TR-069 protocol, the Device: 2 data model was adopted and expanded from its predecessor. TR-369 can therefore act in parallel to TR-069.[5]
Notifications[edit]
Controllers are able to subscribe to certain events. They will be notified when the event occurs and can act immediately.
References[edit]
- specification Broadband-Forum (PDF File)
- specification Broadband-Forum (weblink)
- What is TR-369? (USP) I Axiros
- USP architecture and use cases I QA Cafe
- original text written in german
Footnotes[edit]
- ↑ Heyward, Nicole: Minim, January 2020
- ↑ Broadband-Forum, User Services Platform (USP), ISSUE DATE: October 2019, paragraph 4.1: Endpoints
- ↑ Broadband-Forum, User Services Platform (USP), ISSUE DATE: October 2019, paragraph 4: Architecture
- ↑ Broadband-Forum, User Services Platform (USP), ISSUE DATE: October 2019, paragraph 6: Message Transfer Protocols
- ↑ Broadband-Forum, User Services Platform (USP), ISSUE DATE: October 2019, paragraph 4.2.1: Data Models
Draft Review[edit]
This article "TR-369" is from Wikipedia. The list of its authors can be seen in its historical and/or the page Edithistory:TR-369. Articles copied from Draft Namespace on Wikipedia could be seen on the Draft Namespace of Wikipedia and not main one.
