Architecture

The CPE communicates to a HTTP server, also called Auto Configuration Server (ACS), because instead of a normal client-server relationship between the device and the HTTP server, what happens is that the connection can be initiated from the server to the device.

TR-069 Issue Amendment 6 Corrigendum 1 - Section 3.7.3 - FIgure 3

As you can see above, the ACS and the CPE are at the same time a HTTP client and server, it's needed to exchange messages according to the CWMP protocol and because they're both a client and a server, must not exist NAT between the CPE and the ACS, they need to be directly accessible to each other.

Although there are some workarounds for the NAT problem as to use XMPP or STUN, the best option is still to install the ACS with direct connection to the CPE, this simplifies your deployment and ensures a smooth solution.

Messages

Here are the main messages you can send to a CPE and to interact with it. All of them are available in the Oktopus REST API > Device > CWMP Native Messages.

• GetParameterNames

• GetParameterValues

• GetParameterAttributes

• SetParameterValues

• AddObject

• DeleteObject

Data Model

The first Data Model created to be used with CWMP was the TR-098, after that came that the TR-181 which has more capabilities and possibilities than it's predecessor.

Encoding

The messages between the CPE and the ACS are exchanged using SOAP, that transfer messages in the format of XML, and contains structured data with RPC information.