When this is complete, the CPE is stimulated to initiate a CWMP session with the ACS as usual via HTTP. This Connection Request is simply an XMPP IQ Stanza containing a Connection Request message to its XMPP Server specifying the “to” address that matches the CPE where the Connection Request needs to be sent and a “from” address that matches one of the allowed Jabber IDs. From then on, the ACS can communicate a Connection Request via the XMPP Server to the Jabber ID of the CPE. The CPE then establishes a secure connection to the agreed upon XMPP server. The ACS makes a connection to an XMPP Server, and configures the CPE via TR-069 to use this XMPP Server for its Connection Requests. To use this feature, a CPE must support the XMPPBasic:1 and XMPPConnReq:1 profiles from the CWMP data model. This is now defined in Annex K of TR-069 Amendment 5. As newer protocols appeared, the Broadband Forum TR-069 developers looked towards a messaging bus solution using the eXtensible Messaging and Presence Protocol (XMPP) to allow Connection Requests to occur. For starters, it is UDP based, and the ACS cannot guarantee that its CRs have arrived. Since this was undesirable, Annex G of TR-069 specified a way to use STUN (Session Traversal Utilities for NAT) protocols to allow the devices to accept HTTP GET requests through the gateway. When successful, the device initiates a CWMP session with the 6 CONNECTION REQUEST event in the Inform method’s event list.Īs more devices became manageable by TR-069, however, devices that sat behind the gateway that was likely using Network Address Translation (NAT) could not simply expose a directly addressable URL without the CPE setting up a complex port mapping. The basic Connection Request is done via the HTTP GET method to the URL specified by the CPE (this URL is required to be sent in every Inform message to the ACS, so that the ACS always knows what the current URL is). Because these devices were directly addressable on the Internet, it was easy to deliver TR-069 Connection Requests to the device by having the device expose an accessable URL for the ACS to make such requests. When CWMP was originally designed, it focused on devices acting as gateways into the customer premises - commonly refered to as home gateways.

This is often used when the ACS must contact the CPE immediately, such as when configuring the device for a new service after it has already been bootstrapped by the system. Though one of the fundamental principles of CWMP (TR-069) is that the CPE endpoint is always the one to initiate a connection, Autoconfiguration Servers (ACS) can use the TR-069 Connection Request feature to stimulate a CPE to begin a session. Watch our training on connection request basics and XMPP connection requests in our TR-069 training series.

Shareaza connection test