name: CWMP
full_form: CPE WAN Management Protocol
context: The Itf-HNB Interface shall use the TR-069 CWMP for Configuration Management, Performance Management, and Fault Management. TR-069 CWMP perm Configuration Management interaction from the HMS to the HNB via either RPC Method calls or an XML File Format. For HNB-GW discovery, initial provisioning, and on-going configuration management of the HNB, the HMS shall support the two methods as defined in TR-069 CWMP for provisioning and configuration management which are as follows: 1. The HMS uses TR-069 RPC Methods, such as AddObject, SetParameterValues, and SetParameterAttributes, to directly provision the HNB Data Model parameter values. 2. The HMS uses TR-069 Download RPC Methods to request the HNB to download a configuration file to provision the HNB Data Model parameter values. The HMS provides the location of the file to be transferred by providing a URL to the HNB. A standard configuration file format has not been defined for the HNB. Consequently, the configuration file shall be
description: The CPE WAN Management Protocol (CWMP) is a protocol used for managing customer premises equipment (CPE) in a wide area network (WAN). It enables remote management of CPE devices, including configuration, performance monitoring, and fault management. CWMP uses TR-069, which defines the protocol's architecture, data models, and procedures for device management.
explanation: CWMP is classified as a Protocol because it establishes rules and standards for communication and interaction between network devices, specifically CPE devices in a WAN environment. The text emphasizes its role in managing CPE through configuration, performance monitoring, and fault handling, which are core functions of a protocol.
section_title: 5.2.3Itf-HNB Interface
biotag_Context: O,O,B-Interface,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,B-Protocol,O,B-Network Function,I-Network Function,O,O,O,B-Network Function,O,O,B-Network Function,O,O,B-Protocol,O,O,O,O,B-Technology,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Network Function,O,O,O,B-Protocol,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O
biotag_Description: O,B-Protocol,I-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O