We’ve already seen some of the TR069’s features, to access the content where we present what the TR069 is, read our first article, now we’ll see how this “magic” works.
TR-069 is based on SOAP/HTTP, where the connection between the CPE and the ACS is made.
Communication is done through remote procedure calls (RPC), this allows the CPE to forward the parameters, in addition to their current status, as well as firmware management to the ACS.
It is very important to remember that it is the CPE who initiates the connection, the first contact will come from it, and also the periodic reports to the ACS, because at each fraction of time the CPE sends a report to the ACS so that the ACS updates its status in the server.
The ACS will only initiate contact at specific times, such as: firmware update, or even an interaction initiated by the operator, but which must be accepted by the CPE for the action to be completed.
The image above shows the communication between the CPE and the ACS, where the CPE forwards a connection request to the ACS, notice that in this picture, the CPE is already known by the ACS, otherwise the communication would have some more fields, such as GetParamenterNames request, where this request departs from the ACS to the CPE, with the intention of knowing the parameters that can be delivered to the ACS.
- Open connection: the CPE informs that it wants to talk to the ACS
- SSL initiation: a certificate is added to the communication to protect the exchange of messages
- inform request: the CPE tells the ACS that it will inform its current status
- inform response: the ACS says that the CPE can forward the parameters to it
- HTTP post(empty): CPE says OK
- GetParameterValues request: request for CPE parameters
- GetParameterValues response: CPE response with parameters for ACS
- SetParameterValues request: the ACS informs that it now knows the parameters, and that it needs the values of the CPE parameters
- SetParameterValues response: the CPE informs the ACS of the parameter values requested by the ACS.
- HTTP response empty: the ACS informs that there is no more information to be exchanged between them, and that the communication can be ended.
- Close connection: The CPE closes the connection.
It is possible to have this functionality in your network in a simple way, which is through the TR069 module in Made4graph, where all the necessary information is within the software interface itself.