![\"\"](\"https:\/\/www.made4it.com.br\/wp-content\/uploads\/2022\/06\/image-7.png\")
<\/a><\/figure>\n\nThe 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.<\/p>\n\n
- Open connection: the CPE informs that it wants to talk to the ACS<\/li>
- SSL initiation: a certificate is added to the communication to protect the exchange of messages<\/li>
- inform request: the CPE tells the ACS that it will inform its current status<\/li>
- inform response: the ACS says that the CPE can forward the parameters to it<\/li>
- HTTP post(empty): CPE says OK<\/li>
- GetParameterValues \u200b\u200brequest: request for CPE parameters<\/li>
- GetParameterValues \u200b\u200bresponse: CPE response with parameters for ACS<\/li>
- SetParameterValues \u200b\u200brequest: the ACS informs that it now knows the parameters, and that it needs the values \u200b\u200bof the CPE parameters<\/li>
- SetParameterValues \u200b\u200bresponse: the CPE informs the ACS of the parameter values \u200b\u200brequested by the ACS.<\/li>
- HTTP response is empty: ACS indicates that there is no more information to be exchanged between them, and that the communication can be terminated.<\/li>
- Close connection: The CPE closes the connection.<\/li><\/ul>\n\n
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.<\/strong><\/p>\n\n
For you to know <\/strong>Made4graph<\/strong><\/a>and the benefits of the tool you can access the <\/a>demo<\/a><\/strong>or schedule a demonstration with the commercial team \ud83d\ude01.<\/p>\n","protected":false},"excerpt":{"rendered":"
We\u2019ve already covered some of TR069\u2019s features. To access the content where we explain what TR069 is, read our first article. Now we\u2019ll see how this \u201cmagic\u201d 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 the CPE initiates the connection; it is the CPE that makes the first contact and also sends periodic updates to the ACS, since at regular intervals the CPE sends a notification to the ACS so that the ACS can update its status on the server. The ACS will only initiate contact at specific times, such as during a firmware update or an interaction initiated by the operator; however, these 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 \u200b\u200brequest: request for CPE parameters GetParameterValues \u200b\u200bresponse: CPE response with parameters for ACS SetParameterValues \u200b\u200brequest: the ACS informs that it now knows the parameters, and that it needs the values \u200b\u200bof the CPE parameters SetParameterValues \u200b\u200bresponse: the CPE informs the ACS of the parameter values \u200b\u200brequested by the ACS. HTTP response is empty: ACS indicates that there is no more information to be exchanged between them, and that the communication can be terminated. 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. For you to know Made4graphand the benefits of the tool you can access the demoor schedule a demonstration with the commercial team \ud83d\ude01.<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[31],"tags":[],"class_list":["post-19197","post","type-post","status-publish","format-standard","hentry","category-nao-categorizado"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t