Simple understanding of the TR069 protocol

Full document Download: http://download.csdn.net/source/410669

In fact, tr069 and SNMP function Almost, is the remote device management, such as remote configuration Ah what ..., now people are very lazy, it is best to move around at home lip things are done, the method is to find a person to help him pass, such as small A to small B a computer but he will not pretend Ah, He did not want to go out and spend money to hire small c to help him ask, so small B to ask the matter wrote a letter to small C, small c ran to small a home, see the letter after small a wrote a reply to small C, small C and ran back to small B, small B in accordance with the reply to the computer installed. By the way, maybe Little b doesn't want others to see the contents of the letter put the letter in a locked iron box, only small A and he himself has the key to open.

The CPE in the tr069 (that is, small B) serves as a client for HTTP (that is, small c) (which is a variety of terminals on the network), and ACS (that is, small a) acts as an HTTP server (it is responsible for managing the various terminals on the CPE), and the content of the communication uses the SOAP packets (that is, the

The interactive process uses RPC mechanism, in fact it works and the example I said at the beginning of the same, the following is

Copy the instructions from the Internet.

How RPC Works

The essence of RPC mechanism is to implement the session layer function in OSI seven layer model. It establishes a logical channel (that is, a session connection) between the two field points attempting to communicate, and uses this channel to exchange information and release the connection when not in use. Let's take a look at the RPC communication model (Figure 2 below):

Client side:

1) Send the message of the remote procedure call (in the form of a message packet) to the remote server side;

2) Wait until the server-side response to the request is received;

3) After receiving the return execution result from the server side, proceed to the subsequent program.

Server side:

1) Listen to the status, waiting for the client to send a process call message;

2) Once the procedure call message is received, the server extracts the parameters and parses it, then executes the requested procedure;

3) Send the execution results back to the client as a message packet.