Contact Book a demo

TR-069 vs TR-369 (USP): what changes, and what stays

TR-369 is not a replacement for TR-069 so much as a redesign of its transport and topology. Both address the same data model. Here is what actually differs in operation.

Articles Edgera Engineering Reviewed by Principal Architect, Device Management 9 min read

TR-069 is session-based and CPE-initiated over HTTP. TR-369, the User Services Platform, is message-based over MQTT, WebSocket, STOMP or CoAP, and allows multiple controllers to address the same agent.

The practical differences

USP gives you near-real-time control, granular per-controller permissions, and a far lighter transport for constrained IoT endpoints. TR-069 remains the installed base, and will be for years.

Running both

A fleet migrates one model at a time. The management platform has to speak both protocols against one data model and one workflow engine, or operations fragment along protocol lines.

Get the next one by email

Roughly monthly. Confirmed opt-in, unsubscribe in one click.

Sign up for the briefing

Related reading

Case studies

Cutting truck rolls with remote diagnostics at a regional ISP

A broadband operator moved first-line diagnosis from the field to the support desk by giving agents the same device tel…

Articles

What a self-organising network actually optimises in the home

Channel, band, power and steering decisions taken continuously from standards telemetry, not from a technician's judgem…

Technical guides

Zero-touch provisioning for FTTx rollouts

Activation time is the first thing a new subscriber measures. This guide covers building a provisioning path where the …

See it against your own fleet

Bring your CPE models, your protocol mix and your integration constraints. A solutions engineer will show you what the platform does with them — no slides.

Book a working session Ask a question first