TR069 protocol wizard-A Concise tutorial to help you understand the TR069 protocol (2)

You can also download this article through the following link:

Http://download.csdn.net/source/994937

 

Connect to the "TR069 protocol wizard (1 )"

6. RPC functions of the TR069 protocol (or RPC method)
As mentioned above, ACS and CPE communicate with each other through the RPC method specific to the TR069 protocol.
The CPE function is called by ACS to manage the CPE, such as setting the CPE parameter, obtaining the CPE parameter, upgrading the hardware, and restarting the equipment;
The ACS function is called by CPE to report status information to ACS, and request hardware image files to be downloaded (used to upgrade hardware.
Some of these methods are required and some are optional (required/optional)

 

7. CPE function parameters (Data Model of TR069 Protocol)
The Network Architecture contains two device types, so it contains two sets of data models:
(1) Internet gateway device, such as a router, abbreviated as IgD DM (Data Model)
(2) a lan device under a gateway, such as a videophone, abbreviated as device DM (Data Model)
The TR069 Protocol defines the data model of the gateway device.
Parameter Name: uses a tree-like hierarchical relationship between points. The trunk is the object to be configured, and the leaf is the specific configuration parameter. All configuration parameters have the read/write attribute.
For example, internetgatewaydevice. ippingdiagnostics. Interface
Parameter type: Soap-based Data Type

8. Specific functions of the function (Functions of the TR069 Protocol)
(1) auto-configuration and dynamic service provisioning)
The TR069 Protocol specifies that ACS can be configured at any time after the first or after the CPE goes online. For example, ACS uses the Set Method in the CPE function to configure the CPE.
(2) software/firmware image management)
The TR069 Protocol specifies the software and hardware version number authentication mechanism, and the download trigger mechanism (both CPE and ACS can actively initiate the download), and the notification mechanism after the download fails.
For example, ACS uses the download and upload methods in the CPE function to download a new version for upgrading devices or Uploading software image files of the current version.
(3) status and performance monitoring)
The TR069 Protocol specifies a mechanism by which the CPE is reported at any time (in some cases translated as "dynamic") to the ACS (in some cases translated as "notification ").
For example, CPE uses the inform method of the ACS function: CPE periodically calls the inform method of ACS to report hardware status information.

[Inform soap package information]

DeviceID identifies CPE
The reason for this inform event is as follows: 2 Periodic CPE periodic Initiation
Inform call, reporting status
Maxenvelopes HTTP Response portable soap package (envelope)
Currenttime current CPE time
Retrycount the maximum number of repeated connections in this session
Parameterlist parameters used by this inform Function

[Example of an Inform soap package]

<SOAP-ENV: envelope xmlns: SOAP-ENV = "http://schemas.xmlsoap.org/soap/envelope/" xmlns: SOAP-ENC = "http://schemas.xmlsoap.org/soap/encoding/" xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance" xmlns: XSD = "http://www.w3.org/2001/XMLSchema" xmlns: cwmp = "urn: dslforum-org: cwmp-1-0 ">
<SOAP-ENV: Header>
<Cwmp: Id SOAP-ENV: mustunderstand = "1">
Inform
</Cwmp: Id>
</SOAP-ENV: Header>
<SOAP-ENV: Body SOAP-ENV: encodingstyle = "http://schemas.xmlsoap.org/soap/encoding/">
<Cwmp: Inform>
<DeviceID>
<Manufacturer>
Xxxxxxxxxx
</Manufacturer>
<Oui>
Xxxxxxxxxx
</OUI>
<Productclass>
Xxxxxxxxxx
</Productclass>
<Serialnumber>
000000000001
</Serialnumber>
</DeviceID>
<Event xsi: TYPE = "SOAP-ENC: array" SOAP-ENC: arraytype = "cwmp: eventstruct [1]">
<Eventstruct>
<Eventcode>
2 Periodic
</Eventcode>
<Commandkey>
</Commandkey>
</Eventstruct>
</Event>
<Maxenvelopes>
1
</Maxenvelopes>
<Currenttime>
2009-01-15t06: 28: 06
</Currenttime>
<Retrycount>
0
</Retrycount>
<Parameterlist xsi: TYPE = "SOAP-ENC: array" SOAP-ENC: arraytype = "cwmp: parametervaluestruct [7]">
<Parametervaluestruct>
<Name>
Internetgatewaydevice. deviceinfo. specversion
</Name>
<Value xsi: TYPE = "XSD: string">
4.0
</Value>
</Parametervaluestruct>
</Parameterlist>
</Cwmp: Inform>
SOAP-ENV: Body>
SOAP-ENV: envelope>

(4) Diagnosis)
Supports diagnostics from ACS to CPE to solve connectivity or business problems, or perform predefined diagnostic tests.
For example, ACS uses the get method in the CPE function: first, ACS calls the Set Method of CPE. Set some diagnostic requirements such as ipping, such as internetgatewaydevice. ippingdiagnostics. interface.
CPE is required to diagnose itself, and ACS obtains the diagnosis result through the get method of CPE.

9. TR069 Protocol Security
The TR069 protocol supports certificate authentication using "SSL/TLS". The CPE must use the certificate provided by ACS for authentication.
Permission ACS.
If the CPE has not been SSL/TLS certified, ACS must use HTTP to authenticate the CPE. If the CPE has been "SSL/TLS, ACS can use "HTTP basic" authentication or "HTTP Digest" authentication.