e second step, the converter would undergo a process of "reverse normalization," where it would examine the table(s) indices in a MIB group and form parent-child (containment) relationships between the object classes formed in the first step. This step helps to ensure that a rich hierarchical information model is created as part of the transformation that can be examined and manipulated by management applications. The XMLP processor performs the operation of data creation, processing of data, and transfer and reception of XML data. The embedded network element applications is just a fancy term used to mean nonmanagement functional blocks in the network element (NE) performing the core functionality of the element. The NE specific applications can use the XMLP processor for creating management information and storing it into the XML database using a management interface. The NE core applications, for instance, can create performance records in the XML format and provide it to the processor. Once the message is ready the trans- port binding is performed in the UDP binder, followed by an engine that initiates transfer and reception. This section on mapping to SNMP is intended to make it comfortable for the reader to switch from the popular SNMP-based management Network element UDP and XMLP manager transfer/reception framework engine Embedded Management XMLP processor element interface/ - Path handle applications controller - Write handle - Read handle - Process info MIB to XML schema converter XML config file and data base SNMP MIB Figure 18.4 Block diagram of XMLP agent. Fundamentals of EMS, NMS and OSS/BSS to XML-based protocol for the network management. XML-based protocol is mostly linked with HTTP, but most of the concepts discussed here with UDP holds good. 18.6 SOAP SOAP (simple object access protocol) is a lightweight protocol that uses XML to define the messaging framework to generate messages that can be exchanged over a variety of protocols. SOAP provides a structured information exchange in a decentraliz