Broadband Forum TR-369 USP Consultancy
From the team that built a USP controller and runs TR369.org
USP, the Broadband Forum's TR-369, is what replaces TR-069 for managing broadband devices. It is a good protocol and a large specification, and the number of people who have implemented it end to end is small.
We are some of them. We built the Techufy USP controller, we test it against OB-USP-Agent on every release, and we wrote down what we learned on TR369.org. Our consultancy is that experience, available by the day.
Contact usWhat we know from doing it
How the pieces fit
Agents, controllers, the TR-181 model, the three transports, records versus messages, end-to-end security. Where the specification is precise and where it leaves you to decide.
What a controller has to handle
Reconnect storms, agents that half-implement a message type, brokers under load, and the data model growing every amendment. We have built for all of it.
Onboarding and agent testing
Getting devices enrolled with the right credentials and roles, and checking a vendor's agent against the specification before ten thousand of them ship.
Diagnosing a live deployment
Messages that go missing, notifications that never arrive, brokers that fall behind. We read the traffic and find it.
Coming from TR-069
We built an ACS before the controller. We can plan a migration that keeps both running and moves fleets when their firmware allows.
What an engagement can be
Design help
Reviewing your USP architecture, transport choices and integration design before you build, or before you buy.
Building or adapting a controller
Extending our controller for your needs, or building components of your own. We have the code and the scars.
A diagnostic review
A few days looking at a running deployment, with a written list of what is wrong and what to do about it, in order.
Training and standby
Our TR-369 course for your team, and a retainer if you want someone to call when something odd happens.
Why us
We implemented it
Reading TR-369 is one thing. Making a controller pass every message type against a real agent is another.
We answer your question
Not a generic USP briefing. The specific problem you brought, with your devices and your systems.
Any stage
Deciding whether to adopt USP, designing it, debugging it in production, or teaching the team. Same people throughout.
We publish what we know
TR369.org is free. If our written answer to your question is already there, we will send you the link instead of an invoice.
Write to us with the question. Include which agents and transports you are using if you know.