TR-069 specification for CPE control
I tried to find articles on this topic on Habré. But, strangely, I did not find any references. Then I will share my knowledge about it. This is my second attempt to write an article on Habré.
So. Over the past few years, there has been a trend towards shifting monitoring functions and configuring end network devices from users to providers. They take care of the configuration and updating of devices, and the user simply receives a box with 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 almost completely depend on him.
To control 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 describing the subscriber equipment management protocol via the global network -CWMP (CPE WAN Managmet Protocol). CWMP is an application layer protocol that uses SOAP (Service Oriented Protocol) information as an add-on over HTTP as a transmission tool. All data is transmitted in XML format. The standard is promoted by the dslforum consortium. The goal is standardization and unification of principles and approaches to the management of subscriber equipment of various manufacturers.
The protocol assumes the location of an autoconfiguration server (ACS) on the territory of the provider, organizing interaction with subscriber equipment, processing requests from devices and capable of connecting additional services, depending on the selected policy.
A session can be initiated either by the CPE or by the ACS.
In order to manage the device, it must have an IP address regardless of the type of this device (Bridge, Router, IP-Phone). SSL and TLS are used to provide a secure connection to TR-069.
')
TR-069 supports the following features.
1. Configuration. We are talking about both the initial configuration and the autoconfiguration of an already operating device or the introduction of changes to the settings.
2. Software version management and update.
3. Analysis of log files, performance and device diagnostics.
4. Execution of stored procedures
The choice of CPE for maintenance may be subject to various conditions. For example, a specific device, vendor, model or software version.
Autoconfiguration is possible with any method of acquiring devices:
1. Equipment is provided when signing the contract.
2. The equipment is purchased by the subscriber in the form of a set of connection to the operator’s network.
3. The equipment is purchased by the subscriber independently and has no preliminary settings for the operator’s network.
I work in a new WiMAX provider and, perhaps, we will have the introduction of this mechanism in the future. If everything works out, then I can tell about it in more detail.
UPD. Specification in pdf format
PS For this topic I received an invite. Thank you good man!
So. Over the past few years, there has been a trend towards shifting monitoring functions and configuring end network devices from users to providers. They take care of the configuration and updating of devices, and the user simply receives a box with 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 almost completely depend on him.
To control 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 describing the subscriber equipment management protocol via the global network -CWMP (CPE WAN Managmet Protocol). CWMP is an application layer protocol that uses SOAP (Service Oriented Protocol) information as an add-on over HTTP as a transmission tool. All data is transmitted in XML format. The standard is promoted by the dslforum consortium. The goal is standardization and unification of principles and approaches to the management of subscriber equipment of various manufacturers.
The protocol assumes the location of an autoconfiguration server (ACS) on the territory of the provider, organizing interaction with subscriber equipment, processing requests from devices and capable of connecting additional services, depending on the selected policy.
A session can be initiated either by the CPE or by the ACS.
In order to manage the device, it must have an IP address regardless of the type of this device (Bridge, Router, IP-Phone). SSL and TLS are used to provide a secure connection to TR-069.
')
TR-069 supports the following features.
1. Configuration. We are talking about both the initial configuration and the autoconfiguration of an already operating device or the introduction of changes to the settings.
2. Software version management and update.
3. Analysis of log files, performance and device diagnostics.
4. Execution of stored procedures
The choice of CPE for maintenance may be subject to various conditions. For example, a specific device, vendor, model or software version.
Autoconfiguration is possible with any method of acquiring devices:
1. Equipment is provided when signing the contract.
2. The equipment is purchased by the subscriber in the form of a set of connection to the operator’s network.
3. The equipment is purchased by the subscriber independently and has no preliminary settings for the operator’s network.
I work in a new WiMAX provider and, perhaps, we will have the introduction of this mechanism in the future. If everything works out, then I can tell about it in more detail.
UPD. Specification in pdf format
PS For this topic I received an invite. Thank you good man!
Source: https://habr.com/ru/post/75707/
All Articles