Supported TRs
On this page, we'll describe the TR protocols supported by Cpehub
If your ISP needs a TR that isn't described here, talk to our development team — we can likely build it for you!
Are there other TRs besides TR-069?
It's become common to associate the ACS server with TR-069, but there are many other TRs, each with a specific function.
TR-069 itself is just the description of the communication protocol, which is used by other TRs.
Support table
Below we describe the main TRs used by ISPs and supported by Cpehub
| TR | Supported | Description |
|---|---|---|
| TR-069 | Communication between the ACS server and CPEs via CWMP | |
| TR-098 | Data model for internet gateway devices | |
| TR-104 | Roadmap* | Data model for voice services, including configuration and management of phone lines, quality of service (QoS), and advanced telephony features. |
| TR-143 | Specifies methods and metrics for testing network performance, such as bandwidth and latency. | |
| TR-181 | Advanced, expandable data model for modern network devices |
- Roadmap items may have their development accelerated based on customer ISP demand
Which TRs do CPEs support?
When it comes to TR support in CPEs, it's important to understand that compatibility and functionality can vary by device model and manufacturer. Here are some key points to clarify this:
Variation in Support by Device Model and Manufacturer
Each CPE manufacturer defines which TRs their devices support and which specific features are implemented. This means two devices from different manufacturers, or even different models from the same manufacturer, may offer different levels of support for the same TRs.
Examples of TR Support
TR-069: This is the base protocol for communication between the ACS server and CPEs via CWMP. All devices that support TR-069 can be managed remotely, but the supported data models can vary. TR-098: Some devices that support TR-069 use the TR-098 data model, designed for older internet gateways. TR-181: Other devices that support TR-069 use the TR-181 data model, which is more advanced and expandable, suited for modern devices.
Variation Within the Same TR
Even within the same TR, specific features can vary by device. For example:
TR-143: This TR specifies methods and metrics for testing network performance, but the implementation can vary: Some devices may support Ping, Tracert, Upload, and Download diagnostics. Other devices that support TR-143 may only offer Ping and Tracert features.
Conclusion
TR compatibility and support in CPE equipment depend heavily on the manufacturer and device model. This means that when choosing equipment, it's crucial to check which TRs are supported and which specific features are available. This variation allows devices to be tailored to specific network needs, but it also means careful analysis is necessary to ensure all desired features are covered.