TR-069 defines the CPE WAN Management Protocol (CWMP). TR-369 defines the User Services Platform (USP). For an operator, the procurement decision is whether a specific device and firmware work with the management system and operational processes in use.
What changes with USP?
CWMP uses a CPE and Auto Configuration Server relationship. USP describes Agents and Controllers and supports multiple Controllers with permissions. USP messages can use supported message-transfer protocols, including MQTT and WebSockets. It should not be described simply as a REST API. Both technologies use Broadband Forum data-model concepts, but a shared model name does not guarantee identical object coverage or implementation.
Coexistence is a valid migration strategy
The Broadband Forum describes USP as designed to coexist with TR-069 and support migration. There is no general requirement to replace every CWMP device immediately. Inventory the installed base, current ACS integrations and essential operations before deciding which devices require USP.
Protocol support must be confirmed for the exact CPE model, firmware and licensed feature set. Do not assume that every Honlly product supports both protocols, automatic protocol discovery or an interruption-free migration. The HL-850UE product specification lists TR-069 management; a USP requirement needs separate written confirmation.
Compare implementation evidence
| Question | Evidence to request |
|---|---|
| Which model and firmware are supported? | A versioned capability statement and a reproducible demonstration. |
| Which management operations work? | The supported objects, parameters, events and commands needed by the operator. |
| How is trust established? | Certificate provisioning, identity validation, roles and credential-rotation procedures. |
| What happens during a failed update? | Recovery steps, retained configuration, logging and rollback evidence. |
| Can current systems integrate? | A test against the intended ACS or USP Controller, rather than a generic protocol logo. |
Run a staged operator pilot
- Record the baseline configuration and the functions currently used through the ACS.
- Test onboarding, telemetry, diagnostics and configuration changes on the proposed build.
- Exercise loss of WAN service, controller unavailability and certificate expiry in an agreed test environment.
- Check upgrade recovery and any coexistence behaviour without assuming both systems can change the same parameters safely.
- Define escalation, rollout gates and a supported recovery route before expanding the deployment.
Measure management traffic and response behaviour under the same workload if these are procurement criteria. A universal percentage reduction cannot be inferred from the protocol name.
Prepare the management brief
Provide the target controller, required operations, fleet size, telemetry policy and update workflow. Separate mandatory functionality from future roadmap requests. Confirm support and ongoing maintenance in the project agreement.
