Professional Documents
Culture Documents
Cpe Wan Management Protocol (CWMP) : Adam Rozumek Interoperability Lab University of New Hampshire 2007
Cpe Wan Management Protocol (CWMP) : Adam Rozumek Interoperability Lab University of New Hampshire 2007
Cpe Wan Management Protocol (CWMP) : Adam Rozumek Interoperability Lab University of New Hampshire 2007
Adam Rozumek
InterOperability Lab
University of New Hampshire
2007
What is TR-069?
From the TR-069 Amendment 1 document:
http://upload.wikimedia.org/wikipedia/en/f/fa/Remote_CPE_Controle_via_TR-069.jpg
TR-069 CPE/ACS Interaction Model:
CPE ACS
Open connection
SSL initiation
HTTP post
Inform request
HTTP response
Inform response
HTTP post
HTTP response
GetParameterValues request
HTTP post
GetParameterValues response
HTTP response
SetParameterValues request
HTTP post
SetParameterValues response
HTTP response
Close connection
Service Providers can, through TR-069, use one common platform to manage,
through the Internet, all of their Customer Premise Devices, no matter the device nor
the manufacturer.
This common application has never been achieved before due to CPE vendors
creating proprietary mechanisms for management, and not wanting to expose those
mechanisms to their competitors.
Regional
ACS Broadband LAN
Network Managed
BRAS DSLAM CPE (B-NT)
Managed CPE
(LAN Device)
• Enables service providers to offer dynamic services such as home networking, security,
Voice over IP, centrally managed by a TR-069 ACS
-No matter how well the specification is written, there is room for interpretation and
error during implementation.
-SOAP implementation: TR-069 requires that all communications between the CPE (client) and ACS
(server) be done via a persistent, bi-directional connection. However SOAP was designed for
transitory, one-way communications where the roles of client and server are clearly defined. By
requiring a persistent connection, TR-069 is switching these roles during communications, something
SOAP wasn't designed to do and introducing complexity to a "simple" protocol.
Has to cross several layers of protocols and methods that must interoperate:
Layer Description
CPE/ACS Application The application uses the CPE WAN Management Protocol on the CPE and ACS,
respectively. The application is locally defined and not specified as part of the CPE WAN
Management Protocol.
RPC Methods The specific RPC methods that are defined by the CPE WAN Management Protocol.
SOAP A standard XML-based syntax used here to encode remote procedure calls. Specifically
SOAP 1.1
SSL/TLS The standard Internet transport layer security protocols. Specifically, either SSL 3.0 (Secure
Socket Layer), or TLS 1.0 (Transport Layer Security)
SNMP is a technology that is tried and true, but each company has it's own MIB
(management information base), and SNMP has been known to have security flaws. TR-069
was created to be device agnostic, meaning that all CPE devices can be managed by one TR-
069 Auto Configuration Server (ACS) no matter the manufacturer etc.
Privacy Concerns:
Although it may seem invasive and insecure to have devices able to be accessed
without active consent, there are many security protocols included in the TR-069
documents.
These capabilities are provisioned by TR-069 and its extensions (TR-098, TR-
104, TR-106, TR-110, TR-111)
TR-069 Extensions:
TR-098 - data model for internet gateway devices (DSL modems with built in routers)
TR-104 - data model and any specific items for VoIP devices