TECH TALK: Understanding Broadband Standards
Standards—the nuts and bolts of making technology manageable. Motive has a long history of leadership in industry organizations—such as the DSL Forum and the Home Gateway Initiative—that influences the development, communication and implementation of broadband standards. Motive is committed to furthering the cause of standards because true interoperability with device management specifications like TR-069 is pivotal to a service provider’s ability to roll out next-generation services.
The diagram below provides an overview of the technical requirements and working documents that relate to the broadband ecosystem. Each standard is explained below, and more information may be obtained by following the orange link in each definition.
Broadband Standards Explained
| TR-069 | CPE WAN Management Protocol |
| Describes a bi-directional remote management protocol for CPE, intended for communication between CPE and management entity known as an Auto-Configuration Server (ACS). It is intended to support a variety of functionalities to manage CPE, including auto-configuration and dynamic service provisioning, software/firmware image management, status and performance monitoring and diagnostics.
Amendment 1 includes interoperability-related clarifications and errata. Amendment 2 includes extensions to enable multi-cast and autonomous file downloads, especially important for many video environments. | |
| TR-098 | Internet Gateway Device Data Model |
| Defines the Internet Gateway Device (IGD) data model for managing various types of broadband CPE, or gateways, using TR-069. Includes functionality such as managing NAT, DHCP, WAN and LAN interfaces. | |
| TR-104 | Provisioning Parameters for VoIP CPE |
| Defines the data model required for managing a VoIP-capable device (including terminal adapters and VoIP endpoints) using TR-069. | |
| TR-106 | Data Model Template for TR-069-enabled Devices |
| Includes both common management objects for TR-069 managed end devices and rules for combining modular functionalities described in various specifications (e.g., how to combine TR-104 and TR-098 object for an ATA embedded in a gateway). | |
| WT-107 | TR-098 Issue 2 |
| Contains additional management objects and parameters for the gateway data model. | |
| TR-111 | Applying TR-069 to Remote Management of Home Networking Devices |
| Defines extensions to the TR-069 protocol and TR-098 IGD and TR-106 data models to enhance the ability of an ACS to manage devices in customer premises. Describes both a mechanism to enable IGD and end device association and the ability for an ACS to initiate a management session on a device behind a NAT gateway.
Note that the content originally specified in TR-111 has been incorporated into the Amendment 1 versions of TR-069, TR-106, and TR-098. | |
| PD-128 | Interoperability Test Plan for TR-069 Plugfests |
| Interoperability test plan used at plugfests for TR-069-capable ACSes and CPE. Defines interoperability tests at for the underlying protocols on which TR-069 is built, the TR-069 methods, as well as real-world application tests. | |
| WT-131 | ACS Northbound Interface Requirements |
| Requirements for an ACS northbound API to backend OSS/BSS, support and policy systems. | |
| TR-135 | Data Model for a TR-069-enabled STB |
| Defines the data model required for managing a set-top box (STB) using TR-069, including satellite, cable, terrestrial and IPTV STBs—with or without PVR and other optional functionality. | |
| TR-140 | Data Model for TR-069-enabled Network Attached Storage Device |
| Defines a TR-069 data model for provisioning and management of devices delivering content storage capabilities. Storage-enabled devices could include NAS, media servers, or PVR-related storage. | |
| WT-142 | Framework for TR-069-enabled PON Devices |
| Outlines a general framework for applying TR-069 to Optical Network Terminals (ONTs) in a fiber network. | |
| WT-143 | Network Service Provider Initiated Throughput Performance Test |
| Defines a data model to enable throughput testing for TR-069-enabled CPE. | |
| PD-154 | XML Data Model Definition |
| Defines XML schema for data models. Provides the architecture of expression of data model specifications in XML as well as a CPE's overall management capabilities in XML. | |
| PD-157 | TR-069 Data Model Common Objects |
| Contains additional common management objects and parameters for end devices. | |
| PD-158 | TR-069 Data Model for Email and Browser Services |
| Defines a data model to enable management of device email and browser services. | |
