TR069 (CPE Wan Management Protocol)
TR-069 protocol is a terminal-Oriented Network Management Protocol (cwmp) developed by the DSL (Digital Subscriber's line, digital user line) forum ).It providesGeneral framework, message specification, management method, and data model for configuration management. TR-069 protocol is an application layer protocol located on the IP layer, which makes the Protocol has a wide range of applicability, there is no limit on access methods.
ACS has two interfaces at a macro level. One is the Northbound Interface (ACS Northbound Interface) That completes service configuration delivery from a business or service provider to ACS ), the other is the southbound interface (ACS southbound Interface) [1] That completes configuration management from ACS to CPE. The TR-069 protocol mainly defines the standard of the southbound interface.
TR069Defines a general method that can be applied to any CPEDevice
TR98In tr69Internet gateway device data model is defined.
If TR-069 defines the generic methods for any device, other documents (such as this one) Specify the managed objects, or data models, which are collections of objects and parameters on which the generic methods act to configure, diagnose, and monitor the state of specific devices and services.
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 between des interoperability-related clarifications and errata. Amendment 2 extends des extensions to enable multi-cast and autonomous file downloads, especially important for Audio Video environments. |
The 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 varous 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 mechanic 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 in0000ated 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 cocould 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. |