In this blog post, Daniel Egger—Principal Software Engineer at Axiros and co-author of the USP standard—shares the story behind RUSP, Axiros’ Rust-based Open Source toolkit for USP, which has now reached version 1.0. As a key contributor to the USP standard and lead on Axiros’ USP products, Daniel walks you through RUSP’s evolution—from a holiday side project in 2018 to a powerful, scriptable toolkit used in production.

In CPE management, TR-069 has dominated for over 20 years, offering clear data handling but revealing flaws over time. Instead of reworking it, a new protocol—TR-369, or User Services Platform—was developed to address these issues and align with modern needs. Learn more in our new blog post: TR-069 Lessons Learned: Unlock Benefits with USP.

Providing customers, the ability to use and integrate any device which supports one or more of the many standardised device management and monitoring protocols is in Axiros’ DNA. The most utilised standard by our customers is still TR-069, but with the introduction of its successor USP, we’re seeing a major shift in aspects of the lower layers of communication in comparison to TR-069. The analysis of the actual device capabilities and the representation in the data they provide, is a process we call Interoperability Benchmarking. To learn more, check out our blog post.

In the previous blog, our Daniel Egger outlined some of the key differences between the TR-069 and USP (née TR-369) protocols and why USP provides a solid improvement. But (as you may have noticed), he also left a few strategic spoilers about some unique features which make USP truly awesome; and that’s what we’re going to address today.