Language:
    • Available Formats
    •  
    • Availability
    • Priced From ( in USD )
    • Printed Edition
    • Ships in 1-2 business days
    • $28.00
    • Add to Cart

Customers Who Bought This Also Bought

 

About This Item

 

Full Description

This Recommendation defines the requirements for the remote management of networked devices by a service provider in a consumer's home. It provides an overview of, and the necessary normative references to, a family of technical specifications (see Figure 1). It describes how the various technical specifications in this family are related.

CPE such as G-PON ONUs may be partially managed by OMCI, as specified in [b-ITU-T G.988]. [b-ITU-T G.988] defines options for shared management of such devices. These options, and the OMCI management of CPE, are outside the scope of this Recommendation.

The protocol is intended to provide flexibility in the connectivity model.

• The protocol allows both CPE and ACS initiated connection establishment, avoiding the need for a persistent connection to be maintained between each CPE and an ACS.

• The functional interactions between the ACS and CPE should be independent of which end initiated the establishment of the connection. In particular, even where ACS initiated connectivity is not supported, all ACS initiated transactions should be able to take place over a connection initiated by the CPE.

• The protocol allows one or more ACSs to serve a population of CPE. Each CPE can only be associated with one ACS, while each ACS may be associated with one or more service providers. However, a single physical device may present more than one logical CPE device, each of which may be associated with a different ACS.

• The protocol provides mechanisms for a CPE to discover the appropriate ACS for a given service provider.

• The protocol provides mechanisms to allow an ACS to securely identify a CPE and associate it with a user/customer.

Processes to support such association support models that incorporate user interaction as well as those that are fully automatic.

The protocol allows an ACS to control and monitor various parameters associated with a CPE. The mechanisms provided to access these parameters are designed with the following premises.

• Different CPE may have differing capability levels, implementing different subsets of optional functionality. Additionally, an ACS may manage a range of different device types delivering a range of different services. As a result, an ACS must be able to discover the capabilities of a particular CPE.

• An ACS must be able to control and monitor the current configuration of a CPE.

• Other entities besides an ACS may be able to control some parameters of a CPE's configuration (e.g., via LAN-side auto-configuration). As a result, the protocol must allow an ACS to account for external changes to a CPE's configuration. The ACS should also be able to control which configuration parameters can be controlled via means other than by the ACS.

• The protocol should allow vendor-specific parameters to be defined and accessed.

The protocol is intended to minimize implementation complexity, while providing flexibility in trading off complexity vs. functionality. The protocol incorporates a number of optional components that come into play only if specific functionality is required. The protocol incorporates existing standards where appropriate, allowing leverage of off-the-shelf implementations.

The protocol is agnostic to the underlying access network.

The protocol is also extensible. It includes mechanisms to support future extensions to the standard, as well as explicit mechanisms for vendor-specific extensions.

Any protocol describing remote configuration or software-/firmware modification of CPEs must provide the capabilities to comply with all applicable national and regional laws, regulations and policies. The implementation of mechanisms to ensure the explicit endorsement of the customer by means of opt-in permissions before remotely initiating any procedures on the CPE may be required by some specific national and regional laws, regulations and policies. Implementers and users of the described CWMP shall comply with all applicable national and regional laws, regulations and policies.

Implementers and users of all ITU-T Recommendations, including ITU-T G.9980 and the underlying techniques, shall comply with all applicable national and regional laws, regulations and policies.