AudioCodes MP-26 series, Руководство пользователя

Страница: 237 / 464

User's Manual 13. Remote Device Management
Version 4.4.0 237 MP26x/MP27x
13.4.2 TR-069 and TR-104 CPE WAN Management Protocol
TR-069 is a WAN management protocol intended for communication between Customer
Premise Equipment (CPE) or residential devices (such as the device), and an Auto-
Configuration Server (ACS), residing on the service provider's side. It defines a mechanism
that encompasses secure auto configuration of CPE, and also incorporates other CPE
management functions into a common framework. In simpler terms, TR-069 is a protocol
that enables remote server management of the device. Such a protocol is useful, for
example, for remotely and securely controlling the device by the CPE provider. The
standard is published by the DSL Forum. TR-069 runs over SOAP/HTTP and enables
device configuration, management (including firmware upgrade), and status monitoring.
TR-104 is an extension of TR-069 for VoIP configuration and monitoring.
The TR standards are published by the DSL forum:

TR-069: http://www.broadband-forum.org/technical/download/TR-069.pdf

TR-104: http://www.broadband-forum.org/technical/download/TR-104.pdf
Figure 13-11: TR-069 CPE WAN Management Protocol (e.g., MP-264)
The TR-069 protocol allows an ACS to provision a CPE or collection of CPE based on a
variety of criteria. The provisioning mechanism includes specific provisioning parameters
and a general mechanism for adding vendor-specific provisioning capabilities as needed.
The provisioning mechanism allows CPE provisioning at the time of initial connection to the
broadband access network, and the ability to re-provision at any subsequent time. This
includes support for asynchronous ACS-initiated re-provisioning of CPE. TR-069 defines
several Remote Procedure Call (RPC) methods, as well as a large number of parameters,
which may be set or read. Some of these methods and parameters are defined as
mandatory.
Notes:
•
The device was tested for interoperability with two ACS vendors – Motive
and FriendlyTR69. Working with other ACS types may require specific
interoperability effort.
•
The parameter values in the subsequent tables are sample values only
taken from an ACS.