![](https://csdnimg.cn/release/download_crawler_static/12881043/bg13.jpg)
CPE WAN Management Protocol TR-069 Issue Amendment 6 Corrigendum 1
June 2020 © Broadband Forum. All rights reserved. 19 of 276
Software/Firmware Image Management 1.1.2
The CPE WAN Management Protocol provides tools to manage downloading of CPE
software/firmware image files. The protocol provides mechanisms for version
identification, file download initiation (ACS initiated downloads and optional CPE
initiated downloads), and notification of the ACS of the success or failure of a file
download.
Software Module Management 1.1.3
The CPE WAN Management Protocol enables an ACS to manage modular software and
execution environments on a CPE. Capabilities provided include the ability to install,
update, and uninstall software modules as well as notification to the ACS of success or
failure of each action. The protocol also provides support to start and stop applications
on the CPE, enable and disable execution environments, and inventory the software
modules available on the device.
Status and Performance Monitoring 1.1.4
The CPE WAN Management Protocol provides support for a CPE to make available
information that the ACS may use to monitor the CPE’s status and performance statistics.
It also defines a set of mechanisms that allow the CPE to actively notify the ACS of
changes to its state.
Diagnostics 1.1.5
The CPE WAN Management Protocol provides support for a CPE to make available
information that the ACS may use to diagnose and resolve connectivity or service issues
as well as the ability to execute defined diagnostic tests.
1.2 Positioning in the End-to-End Architecture
The ACS is a server that resides in the network and manages devices in or at the
subscriber premises. The CPE WAN Management Protocol may be used to manage both
DSL B-NTs and other types of CPE, including stand-alone routers and LAN-side client
devices. It is agnostic to the specific access medium utilized by the service provider,
although it does depend on IP-layer connectivity having been established by the device.
Note – in the case of a B-NT, TR-046 [2] describes the overall framework for B-NT auto-configuration,
and TR-062 [3] and TR-044 [4] define the ATM layer and IP layer auto-configuration procedures.
Other types of broadband CPE should make use of the protocols appropriate to their network
architectures in order to obtain IP connectivity.
Note – where the CPE WAN Management Protocol is used to manage both a B-NT (or other Internet
Gateway Device), and a LAN-side client device operating behind that B-NT (or other Internet
Gateway Device), Annex F defines a mechanism to allow the ACS to associate the two so that they
may be managed together.
Note – CPE Implementations might exist where the CPE WAN Management Protocol contains more than
one CWMP Endpoint. Proxy management via the Virtual CWMP Device Mechanism is one such
case.