
TR-069 Specification for CPE Management
I tried to find articles on this subject on Habré. But, strangely, I did not find any mention. Then I will share my knowledge about this. This is my second attempt to write an article on Habré.
So. Over the past few years, there has been a tendency to shift the control and configuration functions of end network devices from users to providers. They take care of the configuration and updating of devices, and the user receives just a box of equipment that is enough to turn on to start working.
Modern manufacturers understand this and provide their own protocols for management. But not every operator will allow himself to work with only one vendor and depend almost entirely on it.
To manage thousands of subscriber devices, you need a flexible mechanism that is not tied to a specific manufacturer. This mechanism should be universal and fairly simple to implement for manufacturers of network equipment.
So in 2004, TR-069 was published - a technical specification that describes the protocol for managing subscriber equipment through the global network -CWMP (CPE WAN Managmet Protocol). CWMP is an application layer protocol that uses SOAP (Service Oriented Protocol), an add-on over HTTP, as a tool for transmitting information. All data is transmitted in XML format. The standard is being promoted by the dslforum consortium. The goal is the standardization and unification of principles and approaches to the management of subscriber equipment of various manufacturers.
The protocol involves the location of an autoconfiguration server (ACS) on the territory of the provider, which organizes interaction with subscriber equipment, processes requests from devices and is able to connect additional services, depending on the chosen policy.
A session can be initiated by both the CPE and the ACS.
In order to be able to control the device, it must have an IP address regardless of the type of device (Bridge, Router, IP-Phone). To provide a secure connection, TR-069 uses SSL and TLS.
TR-069 supports the following functions
1. Configuration. We are talking about both the initial configuration and the autoconfiguration of an already working device or making changes to the settings.
2. Management of software versions and its updating.
3.Analysis of log files, performance and device diagnostics.
4. Fulfillment of stored procedures.
The choice of CPE for maintenance can be carried out under various conditions. For example, a specific device, by vendor, model or software version.
It is possible to use autoconfiguration with any method of acquiring devices:
1. Equipment is provided upon signing the contract.
2. The equipment is bought by the subscriber in the form of a set of connection to the operator’s network.
3. The equipment is bought by the subscriber independently and does not have preliminary settings for the operator’s network.
I work in a new WiMAX provider and, possibly, we will have this mechanism implemented in the future. If everything works out, I can talk about this in more detail.
UPD Specification in pdf format
PS For this topic I received an invite. Thank you kind man!
So. Over the past few years, there has been a tendency to shift the control and configuration functions of end network devices from users to providers. They take care of the configuration and updating of devices, and the user receives just a box of equipment that is enough to turn on to start working.
Modern manufacturers understand this and provide their own protocols for management. But not every operator will allow himself to work with only one vendor and depend almost entirely on it.
To manage thousands of subscriber devices, you need a flexible mechanism that is not tied to a specific manufacturer. This mechanism should be universal and fairly simple to implement for manufacturers of network equipment.
So in 2004, TR-069 was published - a technical specification that describes the protocol for managing subscriber equipment through the global network -CWMP (CPE WAN Managmet Protocol). CWMP is an application layer protocol that uses SOAP (Service Oriented Protocol), an add-on over HTTP, as a tool for transmitting information. All data is transmitted in XML format. The standard is being promoted by the dslforum consortium. The goal is the standardization and unification of principles and approaches to the management of subscriber equipment of various manufacturers.
The protocol involves the location of an autoconfiguration server (ACS) on the territory of the provider, which organizes interaction with subscriber equipment, processes requests from devices and is able to connect additional services, depending on the chosen policy.
A session can be initiated by both the CPE and the ACS.
In order to be able to control the device, it must have an IP address regardless of the type of device (Bridge, Router, IP-Phone). To provide a secure connection, TR-069 uses SSL and TLS.
TR-069 supports the following functions
1. Configuration. We are talking about both the initial configuration and the autoconfiguration of an already working device or making changes to the settings.
2. Management of software versions and its updating.
3.Analysis of log files, performance and device diagnostics.
4. Fulfillment of stored procedures.
The choice of CPE for maintenance can be carried out under various conditions. For example, a specific device, by vendor, model or software version.
It is possible to use autoconfiguration with any method of acquiring devices:
1. Equipment is provided upon signing the contract.
2. The equipment is bought by the subscriber in the form of a set of connection to the operator’s network.
3. The equipment is bought by the subscriber independently and does not have preliminary settings for the operator’s network.
I work in a new WiMAX provider and, possibly, we will have this mechanism implemented in the future. If everything works out, I can talk about this in more detail.
UPD Specification in pdf format
PS For this topic I received an invite. Thank you kind man!