TR-369 USP Solution
The Techufy TR-369 USP Solution is a USP controller. It manages the devices on a broadband network using the Broadband Forum's TR-369 protocol: onboarding, configuration, firmware, diagnostics, notifications and bulk data collection, for single devices or whole groups at once.
We wrote it because the ACS products we had worked with were not going to survive the move to USP. It is built on Cassandra, Kafka and clustered MQTT and STOMP brokers, and we test every release against the Broadband Forum's reference agent, OB-USP-Agent.
What it does
Manages devices
Routers, gateways, set-top boxes, anything with a USP agent. Onboard it, read and write its TR-181 parameters, push firmware, run diagnostics. Do it to one device or to a group of fifty thousand.
Stays fast as the fleet grows
There is no central database server to outgrow and no broker to saturate. Add a node to the Cassandra ring or the broker cluster and carry on.
Shows you what is going on
Dashboards for message rates, transport health, device sessions and pending operations, plus per-device logs. When a support ticket comes in, the answer is usually on the first screen.
Fits into what you already run
REST APIs for data and management, Kafka topics for events, Camunda for workflows. Your provisioning, CRM and monitoring systems talk to it the same way they talk to everything else.
What makes it different
It is new code
Several products on the market are a TR-069 ACS with a USP adapter in front. Ours is not. We started from the TR-369 specification and wrote a controller for it.
Every layer is distributed
Cassandra for storage, clustered VerneMQ or Artemis for transport, Kafka between the core services. There is no component you cannot add a second instance of.
It speaks the whole protocol
All message types, all three transports, bulk data, notifications, the TR-181 profiles. We keep up with each amendment the Broadband Forum publishes.
You get straight answers
Ask us what it does not do yet. We will tell you, and we will tell you when it will. The people in the demo are the people who wrote it.
Watch it work
Screenshots only go so far. In an hour we can onboard an OB-USP-Agent, run Get, Set and Operate messages against it, show the notifications arriving, and open the dashboards. Bring your own questions and your own device if you have one.
Request a demoCompatibility features
- Broadband Forum TR-369 Issue 1 Amendment 2, backward compatible
- TR-106 and TR-181 data model compliance
- All required message transport protocols: MQTT 5.0 / 3.1.1, STOMP 1.2, WebSocket
- Full coverage of USP message types and bulk data operations
- Tested against OB-USP-Agent
Technical features
- Apache Cassandra core with peer-to-peer replication and no single point of failure
- Distributed MQTT (VerneMQ or Apache ActiveMQ Artemis) and STOMP transport layers
- Apache Kafka between core modules for consistent performance under load
- REST data and management APIs, Camunda 8 workflow automation
- Modern React administration interface with dashboards and logs
Why operators choose it
It works with the devices you have
If the agent follows the specification, the controller talks to it. We test against OB-USP-Agent, which is what most vendors start from.
It keeps up with the specification
New amendments and proto versions go into the controller as they are published. Older agents keep working, because the controller stays backward compatible.
It survives the reconnect storm
After a power cut or a firmware push every device comes back at once. The Kafka backbone and clustered brokers are sized for exactly that moment.
It can be changed
APIs and workflows cover most needs. When they do not, we change the product. We are small enough that this is a conversation, not a change request queue.
Still on TR-069?
Most operators are, and will be for a while. USP shares the TR-181 data model with CWMP, so the two can run side by side while fleets move over one firmware release at a time. We have built an ACS as well as a controller, and we can plan the migration with you.
ACS to USP transition