TR-069 vs TR-369: Available CWMP and USP Guided Pilot
TR-069 available; USP guided pilot. Choose a CPE management path using device and firmware evidence, NAT behavior, operational needs, and a tested coexistence plan.
Qualify before rollout
Choose around your fleet and required workflows
TR-069, also called CWMP, connects customer premises equipment to an Auto Configuration Server (ACS). TR-369 defines the User Services Platform (USP), a guided-pilot path in ISPAgents, where a device Agent communicates with one or more authorized Controllers. Both are management protocols; neither name guarantees that a particular router exposes the parameters or operations you need.
The decision is usually which protocol to use for each device class, rather than whether to replace the entire fleet. Keep a working CWMP deployment where it meets your needs. Qualify USP in a guided pilot where the device's Agent, transport, permissions, and data model support an operational improvement. For protocol background before a USP pilot, read Broadband Forum’s TR-069 evolution overview.
Architecture and NAT behavior
CWMP path
CPE behind NAT -- outbound management session --> ACS
^ |
+-- next session carries pending work ----+
Prompt contact depends on supported
connection-request / traversal method
Example USP path using MQTT
CPE Agent -- outbound connection --> Broker <-- Controller
<---- authorized message exchange ---->
Alternative USP path using WebSocket
CPE Agent -- outbound persistent connection --> Controller
TR-069 sessions are initiated by the CPE, so periodic informs can reach an ACS through NAT without opening an inbound management port. An ACS connection request asks the device to start a session; reaching that request endpoint through NAT is a separate problem. Supported traversal mechanisms and the periodic-inform interval affect how quickly work can start. See the CWMP specification, session and connection-request procedures.
For the USP guided pilot, evaluate message transports such as MQTT and WebSocket. An Agent can establish an outbound connection and exchange messages over it, which is useful behind NAT. This still depends on firewall policy, connection lifetime, broker or Controller reachability, and reconnect behavior. A USP pilot must also validate subscriptions and permissions for Controller access. For the pilot, see the USP specification, transport and authorization sections.
Do not equate NAT-friendly management with a remote desktop, shell, or general tunnel into the subscriber network.
What to compare in a qualification plan
| Decision | CWMP evaluation | USP guided-pilot evaluation |
|---|---|---|
| Existing device support | Verify the deployed firmware's CWMP implementation and parameter tree. | Verify an actual USP Agent exists on the selected firmware. |
| Action timing | Measure periodic contact and supported connection-request behavior. | Measure transport reconnect, request delivery, and notification behavior. |
| Required operations | Test the specific read, write, diagnostic, or lifecycle action. | Test the specific data-model paths, operations, and subscriptions. |
| Control ownership | Define which ACS policy owns each setting. | Define authorized Controllers and which settings each may change. |
| Rollback | Preserve known working provisioning and recovery access. | Prove recovery before removing the existing management path. |
Use the same qualification questions for both paths: what is supported, what was tested, what failed, and what must an operator do when contact is lost? A successful device login or first inform is insufficient proof of an entire workflow.
Workflow example: qualify a new CPE without disrupting the fleet
Consider a lab with an existing CWMP device class and a candidate USP model for guided-pilot qualification. This is a qualification example, not a certified equipment list.
- Record the exact model, firmware, management protocol, data-model version, and subscriber-to-device mapping for each lab device.
- Keep CWMP responsible for the existing provisioning policy. On the USP pilot candidate, begin with inventory and parameter reads. Assign one writer per setting so two controllers cannot repeatedly undo each other's changes.
- Test one required diagnostic and one reversible configuration change. Record the parameter or operation, expected result, observed result, and recovery steps.
- Put the device behind the same kind of NAT used by subscribers. Interrupt connectivity, reboot it, and confirm that it reconnects with the expected identity and permissions.
- Exercise invalid credentials and disallowed operations. Verify that rejected requests do not modify device state.
- Promote only the proven model and firmware range to a bounded canary. Retain the old management path until recovery and ownership are clear.
Firmware changes and onboarding evidence
Treat onboarding as a sequence: establish trust, confirm the intended tenant and device identity, discover supported paths, read current state, then apply a small approved configuration. Keep unrecognized devices outside automatic provisioning until ownership is resolved. Record how an operator revokes trust or replaces a device without inheriting the old device's authority.
Before a firmware rollout, record the hardware revision, current version, approved image source, integrity checks, maintenance window, and recovery method. In the lab, verify download or transfer completion separately from boot success. After reboot, read back the running version, confirm management reconnects, and check subscriber service. A successful transfer alone is not a successful upgrade. These are qualification requirements, not a promise that every model supports an automated upgrade or rollback in ISPAgents.
Requalify data-model paths and permissions after an update. Stop expansion if a canary loses provisioning, reports a different identity, or cannot recover. Keep a route to physical recovery when the firmware cannot safely revert.
Operational risks
- Firmware variation: the same model name can behave differently after an update. Requalify changed behavior.
- Two writers: CWMP policy and USP pilot actions can conflict. Maintain explicit ownership of configuration paths.
- Stale observations: display when evidence was collected; a cached value is not proof of present connectivity.
- Transport interruption: test reconnect and expired requests so old operations do not execute unexpectedly later.
- Overbroad authority: restrict Controller permissions and broker access; protocol support alone does not establish isolation.
- Certification confusion: vendor protocol support, Broadband Forum certification, and ISPAgents qualification are distinct evidence. Record which one you actually have.
Implementation checklist
- Inventory deployed models and exact firmware ranges.
- List required workflows before selecting a protocol.
- Discover supported data-model paths and record unsupported operations.
- Test NAT, reconnect, reboot, credential failure, and operation timeout cases.
- Assign configuration ownership during coexistence.
- Preserve recovery access and a tested rollback procedure.
- Store qualification evidence per model, firmware, transport, and workflow.
- Review canary results before expanding the supported range.
Where ISPAgents fits
ISPAgents provides available TR-069/CWMP capabilities for informs, RPCs, parameter reads/writes, and diagnostics. Validate coverage against the actual model and firmware.
TR-069 backup scheduling, policy reconciliation, ACS trust/provisioning helpers, and NAT/connection-request services are guided pilot scope. Backup scheduling is tenant opt-in, and policy reconciliation is off by default. Backup-to-restore, reconciliation convergence, and NAT connection requests are not proven.
ISPAgents USP remains a guided pilot. Platform, simulator, tenant-isolation, and certification-workflow evidence exist, but no real customer CPE is certified yet. A guided pilot evaluation must name the model, firmware range, and workflows; it is not a universal USP compatibility commitment.
Related integrations and guides
Review TR-069 ACS for ISPs, TR-369 USP guided pilot for ISPs, the TR-069 device compatibility guide, and the USP device certification program before defining a rollout scope.
Frequently asked questions
Pilot scope: does TR-369 replace every TR-069 device?
No. Qualify the Agent, data model, transport, and required operations for each model and firmware range. Existing CWMP devices can remain on their qualified management path.
Pilot scope: is ISPAgents USP ready for any customer router?
No. USP is a guided lab/pilot qualification for a specific model and firmware range. No real customer CPE is certified yet.
Continue the operations map.
One Subscriber, One Device Identity
Available: The canonical identity foundation supports mapping protocol observations toward one device/customer path using strong serial/MAC evidence. It does not establish universal billing, RADIUS, or controller integration.
Open pageGuidesFair-usage policies for unlimited ISP plans
Keep access available after a usage threshold, explain the reduced speed before purchase, and give support a policy they can defend.
Open pageSolutionsAutomatic Internet Suspension Software — Guided pilot
Guided pilot: Preview, queued jobs, approvals, result recording, and a mock-safe worker can be evaluated in a guided pilot. Live router/RADIUS mutation remains gated; automated suspension and restoration are not a shipped promise.
Open pageSolutionsCustomer Self-Service Foundations — Guided pilot
Guided pilot: Field-job lifecycle, serialized stock, basic tickets and subscriber portal flows have narrow synthetic-data proof and remain guided pilots. Physical installs and invite email delivery are unproven. The technician PWA, dispatch board, dedicated stock workspace and IPAM remain roadmap.
Open page