Communication between ACS and CPE is defined via Remote Procedure Call (RPC)
methods. TR-069 defines a generic mechanism by which an ACS can read or write
parameters to configure a CPE and monitor CPE status and statistics. It also defines the
mechanism for file transfer and firmware/software management. However, it does not
define individual parameters; these are defined in separate documents, as described
below.
Some of the RPC methods are Configuration File Download, Firmware upgrade, Get
Parameter Value, Set Parameter Value, Reboot, and the upload and download files.
TR-106 defines the “data model” template for TR-069 enabled devices. The Data Model
consists of objects and parameters hierarchically organized in a tree with a single Root
Object, typically named Device. Arrays of objects are supported by appending a numeric
index to the object name (e.g. ABCService.1 in the example below); such objects are
called “multi-instance objects”.
Figure 9-2: TR-069 Model Data Example
Below is a list of some of the TR-069 methods:
CPE Methods:
• GetRPCMethods: Used by the CPE or ACS to discover the set of methods
supported by the Server or CPE it is in communication with.
• SetParameterValues: Used by the ACS to modify the value of CPE parameter(s).
• GetParameterValues: Used by the ACS to obtain the value of CPE parameter(s).
• GetParameterNames: Used by the ACS to discover the parameters accessible on
a particular CPE.
To Next Page
Loading...
