TR-069 Annex N and TR-369 defined an HTTP based bulk data collection mechanism to allow agents to push lightweight TR-181 information to data collectors for AI, machine learning, and statistics monitoring of broadband and home networks. Here's how it works, and how to configure it using an ACS or Controller. Keep reading

Flexible create, update, and delete with allow_partial There are three USP messages that are used to change the state of an Agent’s service elements: Add, Set, and Delete. Since these messages can be used for a number of different use cases, they contain mechanisms to ensure that the Controller is able to configure service elements through the Agent in a way that guarantees the state it is trying to achieve. Keep reading

The IoT enhanced Connected Home presents service providers with unparalleled opportunities and challenges. In this Broadband Forum whitepaper, learn how the evolution of TR-069 sets clear path forward. Keep reading

The Add Message in USP is used to create new instances of multi-instance objects in the Agent’s instantiated data model. This is used for a wide variety of service configurations such as creating new Wi-Fi networks. In USP, perhaps the most critical use of the Add message is with the Device.LocalAgent.Subscription. table, which lets a controller manage the notifications it wishes to receive from the Agent. The Add Request The protocol buffers definition of the Add Request, described in the usp-msg. Keep reading

Communications between a USP Controller and USP Agent are delivered using two separate constructs: the USP Message, and its container, the USP Record. Both the USP Record and the USP Message are encoded in transit using “protocol buffers”. Protocol buffers is a standard developed by Google to allow protocol endpoints to easily understand the fields and values of messages transported between them using a clearly defined schema. Keep reading

Service Elements that are defined in the USP Data Model are addressed in USP Messages with a particular syntax called Path Names. Path Names are called such because they describe the “path” within the data model’s tree of objects used to reference a particular object or elements of that object to operate upon. Addressing Objects Object Paths directly address objects in the Agent’s Instantiated or Supported Data model. Keep reading

In alignment with the release of TR-069 Amendment 6 and the User Services Platform/TR-369, the Broadband Forum updated its comprehensive data model that describes CWMP endpoints or USP agents. There’s a number of new features, some of which are tied to updates to CWMP, as well as new interfaces and applications that are managed by CWMP or USP. Here’s a short overview of the changes in Device:2.12. How do data models work? Keep reading

The functions of service elements are described in a set of xml documents known as the USP data model. A data model describes how things like network interfaces, device functions, IoT objects, and more are exposed to controllers. You can find the USP data models at: https://usp-data-models.broadband-forum.org The current root USP data model is known as “Device:2”, otherwise known as TR-181. The earliest version of Device:2 that supports USP is Device:2. Keep reading

USP (TR-369) protocol is an evolution of TR-069 (the CPE WAN Management Protocol, CWMP), that is faster, more scalable, and can apply to new devices and new deployment use cases. Here's a quick overview. Keep reading

The User Services Platform is a system for managing, monitoring, deploying, troubleshooting, and controlling any kind of network connected electronics or virtual services. Developed by the Broadband Forum in TR-369, it’s intended for application developers, consumer electronics and networking manufacturers, and service providers to deploy on end-user devices including: Broadband gateways, virtual gateways, and uCPE Wi-Fi APs and other consumer networking gear Set-top-boxes, voice endpoints, and other communication applications Smart devices and smart hubs that enable the Internet of Things Using USP, connected devices can be deployed and onboarded without the need for on-site support. Keep reading

There are two kinds of endpoints in USP: Agents, and Controllers. A USP Agent is an Endpoint that exposes functions represented by a set of service elements. It is mostly designed to receive and respond to messages from a USP Controller, or send Notifications about activity that the Controller has subscribed to. A USP Controller allows users and applications to manipulate the functions exposed by an Agent. Keep reading

CDRouter release 11.0 includes new test capability for USP implementations, IPv6 VPN tunnels, improved SNMP testing, and support for the TR-069 Device:2.12 data model. Keep reading