BBF.369 USP Certification
The User Services Platform (USP), defined in Broadband Forum TR-369, is a standardized architecture, protocol, and information model designed to allow applications to be developed for the connected home through the connected devices and applications available to the end-user.
Application providers, communication service providers (CSPs), and consumer electronics manufacturers can use USP for innumerable cases, including advanced analytics, broadband deployment, onboarding, managing Wi-Fi, security, and an interoperable Internet of Things.
Built as an evolution to TR-069 (the CPE WAN Management Protocol), USP represents a fully realized ecosystem for adding value to the connected home, and is designed to co-exist with, and easily migrate from, existing TR-069 deployments.
The Broadband Forum offers a comprehensive set of testing options for the USP Agent that span both Interoperability and a Certification Program.
The Interoperability aspects consist of Interoperability Plugfests and test results, while the Certification Program aspects consist of an official Certification and logo rights.
Implementers of USP Agents use certification to gain a higher level of confidence in their products and to offer proof that their implementations will work well within the USP ecosystem.
USP Agent Testing & Certification
USP provides a unique opportunity for service providers to manage and control devices deployed to their subscribers, while also providing similar capabilities to application providers and partners. USP is uniquely suited to serving Broadband and IoT deployments, as these solutions converge and become increasingly connected to each other and the Cloud.
The USP Agent Certification Program ensures USP Agents (the products being remotely controlled and managed) correctly implement the specification and base data models. Thorough testing reduces the complexity of integrating a new USP Agent with a USP controller, promoting agile rollouts of new services.
Resources for the USP Agenda Certification Program
How To Get Tested & Certified
The BBF.369 certification can be completed either via self-testing or in-lab testing via an Approved Testing Laboratory (ATL). Participants and ATLs must use an approved BBF.369 testing tool. If completed via self-testing, signed results must be submitted to an ATL for verification prior to certification.
Approved Testing Tools
| Tool Name | Tool Version* | Test Plan Version | Date Validated |
| QA Cafe CDRouter | Release 12.1 build 1 | TP-469, 1.0.2 | June 2020 |
| QA Cafe CDRouter | Release 12.8 | TP-469, 1.0.3 | 5 November 2020 |
| QA Cafe CDRouter | Release 12.24 | TP-469 1.1 | 9 February 2022 |
| QA Cafe CDRouter | Release 13.8 | TP-469 1.2 | 21 November 2022 |
*Future releases of the tool may also be used, provided they are released within 1 year of the validation and the changes do not alter the behavior of the USP testing.
Approved Testing Laboratories
- University of New Hampshire InterOperability Laboratory (https://www.iol.unh.edu)
Certified USP Products
| Company | Product Name | Software Version | TP-469 Version | Date Certified | Certification ID | Features |
| CommScope | ECO Envoy | 2.0 | 1.0.2 | 6/25/2020 | 2020062501 | 1, 3, 4, 5, 6, 10, 16, 17, 18, 31 |
| Broadcom Inc. | 963158REF | 5.04L03 | 1.1.0-18 | 3/31/2022 | 2022031401 | 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 17, 18, 25, 26, 27, 28, 29, 30, 31, 32, 34 |
| Calix | GS2028E | EXOS R22.2.0 | 1.1.0-18 | 6/17/2022 | 2022060701 | 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 15, 17, 18, 19, 26, 27, 28, 30, 31, 32, 34 |
| Sercomm | USP Gateway – RDKB SKU VD4224B | 2.0.301.0 | 1.2.0-20 | 5/30/2023 | 2023053001 | 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 15, 17, 18, 19, 25, 26, 27, 28, 30, 31, 32, 34, 35, 36 |
USP Features
USP applies to a number of different use cases, with different products implementing the features needed. To help users of the certification understand the details of each certification listing, TP-469 contains a list of product features (labeled with feature IDs) and the tests required to validate them. If a certified product includes one of these features in its listing, it means that the test associated with that feature ID were included in the test process and validated.
This table corresponds to the feature IDs listed in the last column of the certification listings above. As the test plan evolves, more feature IDs will be added and marked as “in-force”. See TP-469 for the complete version of this table and further details.
| Feature ID | Feature Name | Test Cases | Notes |
| 1 | At least one command | 1.61, 1.62 | |
| 2 | At least one command with input arguments | 1.79 | |
| 3 | At least one asynchronous command | 1.64, 1.65 | |
| 4 | Subscription.{i}.NotifExpiration parameter | 1.56 | An extension to the Subscription:1 profile |
| 5 | Controller: 1 profile | 1.59 | |
| 6 | Device.LocalAgent.Subscription.{i}.TimeToLive | 1.55 | |
| 7* | Controller:1 profile (writeable) | 1.78, 9.9 | EUT allows the creation of Device.LocalAgent.Controller.{i}. objects |
| 8 | Device.LocalAgent.Controller.{i}.SendOnBoardRequest() | 1.60, 4.1, 9.9 | |
| 9 | Device.LocalAgent.Controller.{i}.ScheduleTimer() | 1.63, 1.79, 9.1 | |
| 10 | Reboot:1 profile | 1.61, 1.62, 9.10 | |
| 11 | TraceRoute:1 profile | 1.64, 1.65, 1.92 | |
| 12 | ControllerTrust:1 profile | 2.9, 2.10 | |
| 13 | ControllerTrust:1 profile (writeable) | 2.11, 2.12, 2.13, 2.14, 2.15, 2.16, 2.17, 2.18, 2.19, 2.20, 2.21, 2.22 | Additionally supports at least one role that allows object creation, or supports writable parameters in Device.LocalAgent.ControllerTrust.{i}.Role.{i}. |
| 14 | Self-signed controller certificates | TBD | |
| 15 | TLS at the MTP Layer | 4.1 | |
| 16 | CoAP MTP | 5.*, 8.5 | |
| 17 | STOMP MTP | 6.* | Excludes 6.8 unless option 18 is supported |
| 18 | STOMPHeartbeat:1 profile | 6.8 | |
| 19 | WebSocket MTP | 7* | Excludes 7.3 unless option 20 is supported |
| 20 | TR-369 requirement R-WS.6 | 7.3 | |
| 21 | Discovery via DHCP Options | 8.1, 8.2, 8.3 | |
| 22 | Discovery via mDNS | 8.4, 8.5, 8.6, 8.7 | |
| 23 | Secure Message Exchange (TLS for USP Record Integrity) | 3.2, 3.3, 3.4, 3.5, 3.6, 3.7 | |
| 24 | USP session context | 2.6, 2.7, 2.8, 3.8, 3.9, 3.10, 3.11, 3.12, 3.13, 3.14, 3.15 | |
| 25 | Device.LocalAgent.AddCertificate() | 9.2 | |
| 26 | Firmware:1 profile | 9.3, 9.5, 9.6, 9.7 | |
| 27 | Firmware:1 profile (Activate) | 9.4, 9.5 | Supports Firmware:1 profile and additionally supports the Activate() operation |
| 28 | Device.LocalAgent.Request.{i}.Cancel() | 9.8 | Applies only if option 26 is supported |
| 29 | UntrustedRole disabled | TBD | The use of UntrustedRole must be either unsupported, or capable of being disabled, to run this test |
| 30 | Device.DeviceInfo.BootFirmwareImage | 3.2, 3.3, 3.4, 3.5, 3.6, 3.7 | |
| 31 | The product supports least one nested multi-instance object | 1.10, 1.71 | |
| 32 | HTTP bulk data collection with JSON encoding | 10.1, 10.2, 10.5, 10.6, 10.7, 10.8, 10.9 | |
| 33 | HTTP bulk data collection with CSV encoding | 10.3, 10.4, 10.5, 10.6, 10.7, 10.8, 10.9 | |
| 34 | Bulk data collection via the Push! Event | 10.10, 10.11, 10.12 |
Join the industry’s defining body for Broadband Networks
Find out the benefits of joining and how we work
Join Us