FAQ

What is USP?

USP stands for the User Services Platform, a standardized platform to manage, monitor, update, and control connected devices, services and home networks. USP consists of an architecture, protocol, and set of data models that create a network of controllers and agents that allow applications to manipulate user service elements (network interfaces, consumer electronics platforms, smart objects, virtualized network functions, etc.).

What are the major features of USP?

The User Services Protocol is designed with four major features in mind:

Who makes the User Services Platform?

USP is developed by the Broadband Forum, an international standards organization of network service providers/MSOs, end user device manufacturers, government and university organizations, and test laboratories. It is developed in the “Broadband User Services” Work Area.

How does USP relate to TR-069?

USP is a natural evolution of the CPE WAN Management Protocol (more commonly known as TR-069). It was developed to improve on the use cases met by TR-069, expand the number and kinds of devices it can be deployed on, and leverage the lessons learned in the 15 years of TR-069 being deployed in real-world environments.

Is USP a replacement for TR-069?

While USP represents significant advancements in scalability and scope over TR-069, it is designed to co-exist with TR-069 and offer an easy migration path for those who want to make the switch.

Is the BBF deprecating or ending support for TR-069?

No. The TR-069 project is still accepting new contributions and has had its most recent version (Amendment 6, defining CWMP 1.5) published at the same time as USP.

Is BBF building a new data model for USP?

No. USP is designed to re-use the Device:2 data model and associated Service data models produced for TR-069. There are minor alterations to the way USP handles commands, events, and proxying, but it is otherwise identical. This helps those looking to migrate to USP make the change with little alteration to back-end services that rely on the Device:2 data model.

What sorts of devices can implement USP?

Any device capable of an IP connection can implement a USP Agent, including Wi-Fi, fixed wireline, and fixed wireless (i.e. 5G) devices. In addition, smart hubs that aggregate other connection schemes such as ZigBee, Zwave, Bluetooth, and others can be easily managed via USP’s proxy mechanism. USP Controllers can be implemented anywhere from large scale management servers (like TR-069 ACS) or to enable user applications on a smart phone or other user-facing interfaces.

Can USP be used to managed virtual network functions or containers?

USP objects can represent hardware-independent elements via either abstraction or proxy, and re-uses the Software Module Management mechanism designed for TR-069 to manage both execution and deployment units.

Do I need to support all of USP’s message transfer protocols to be compliant?

No. Each supported transport is meant for a different core use case. In addition, transport proxy functions are in development that will make co-existence and interoperability of implementations of different transports simple.

I’m building a USP Agent. How do I make sure it’s compliant?

A full compliance test suite for USP is in development. The Broadband Forum will operate an associated certification program for USP implementations when it is complete.

I have suggestions on USP or things that I would like to see added to the data models. How do I get involved?

Feedback and questions can always be given via GitHub. Due to the standards process adopted by the Broadband Forum, a contributing Broadband Forum member must adopt suggested changes and present them to the Forum as a contribution from their company. An even easier way is to become a member and contribute directly. The Broadband Forum has membership levels for large businesses, small businesses, and individuals.

Resources

The following resources are accessible to Broadband Forum members: