TR -069 is a protocol for exchanging data between the server of a communications provider and an associated terminal to the customer. A typical application is the remote configuration of DSL routers through a broadband provider. Technically, it is a bi-directional SOAP protocol for HTTP-based communication between customer equipment ( CPE = Customer Premises Equipment) and Auto Configuration Servers (ACS). It is therefore also known as CPE WAN Management Protocol ( CWMP ).
Remote access to configuration
In the DSL broadband market provides TR -069 the dominant Anschaltstandard for access devices represents the technical specifications ( TR- 069) will be published by the Broadband Forum.
The protocol includes methods for secure auto-configuration as well as for the (An ) control of other CPE functions in a unified framework. A distinction is made between different types of CPEs. With basic type is Breitband-/DSL-Ausrüstung, such as DSL router.
In the course of the market success of broadband access to the Internet and the number of other access devices increases (eg next to modems and routers also residential gateways, set- top boxes, game consoles, IP phones and IP TV streaming solutions).
At the same time the complexity of the configuration of these devices increased to such an extent that the average user is often overwhelmed.
For this reason, a protocol was developed with TR -069, which provides the ability to automatically configure these devices. Via TR -069 devices can get in touch with Auto- Configuration Servers (ACS ) and are configured automatically. Other service functions can be dynamically provisioned in this way.
In addition to the TR -069 core standard itself, which primarily deals with DSL routers, there are still a number of side standards dealing with specific functionality from other terminals that are behind the NAT / Firewall this as a present presupposed DSL router - and the access to it. In addition, the Broadband Forum has set the goal to extend the standard to fiber optic and other broadband technologies. The new category of femtocell router also excluded.
TR -069 curtails the privacy and the privacy of the end user. It allows the provider einzuspielen automatic updates unnoticed and without the consent of the user in DSL router. This can even be set up targeted for specific users or user groups. Especially against the background of the " online searches " of listening powers and the like can the user have serious consequences.
It also enables TR -069 to configure other devices that are in the " safe area " behind the box or the modem, ie behind the firewall. Through remote access could thus also information on specific customer equipment to which the network operator has access, modify or delete. Through its operating principle provides TR -069 therefore represents a backdoor, the existence of as many consumers do not know about their options and they are not aware of.
On the other hand, the protocol allows the provider, for example, automatically einzuspielen security updates on a device, and so close security gaps for non-technical users, for a self -run by firmware upgrade would be too complicated.
From TR -069 supported functions
- Auto-configuration and dynamic service activation Initial CPE configuration
- Remote CPE configuration
- Version Management
- Update management
- Logdateiauswertung and dynamic messages
- Connectivity and service control
- 100% interoperability between management servers and CPEs.
In the future, TR -069 is controlled by pure Anschaltstandards addition, many additional functions of the CPEs, such as:
- Query the device functions
- Information retrieval, diagnostics, status, and power values
- Automatic event -triggered alarm functions
- Independent gateway data model; expandable in conjunction with TR -064, to include additional devices and functions
- The router front-end ( the user interface ) is not necessarily required for configuration, all functions can be monitored and controlled from the management server.
There are also first approaches (both are certain software standards ) the function of a TR -069 server with the possibilities of OSGi and / or OMA -DM combine. OSGi can for example serve as SOA, which forms the client framework on the router, on the TR -069 itself or other - possibly paid - ( value-added ) services can be dynamically installed and administered. This is particularly interesting when incremental updates to the router software should be possible, or if the remote maintenance of TR -069 are not sufficient. Since this is a framework based on Java with OSGi, there is also a natural relation to the object-oriented SOAP protocol.
The Broadband Forum already published adopted standards, known TRs ( Technical Reports ) on his website.
The designs are not public and are referred to as Working Text ( WT) or Proposed Draft ( PD). Working text are draft standards and are usually about TRs. Proposed Drafts are other working group documents, find internal use (eg, PD -128, Interoperability Test Plan for TR -069 plug tests), but they can also be a precursor to working text.
The numbering of the standards is three digits and linear, that is, it starts at 001 and counts up continuously. If a WT for TR, the numbering does not change. To some extent, supplements ( Amendments) under the same number with the suffix " Amendment" and another numbering (Amendment 1, ... ), which replace the previous document. For this can, for example, despite verabschiedetem TR, WT with the same number exist (eg TR -106 Amendment 1 and WT -106 for Amendment 2 (scheduled for November 2008) ).
Access to all drafts of new specifications of the TR -069 family is available free on the www.broadband -forum.org page.