t mandatory but is usually present in most XMLP management frameworks (see Figure 18.3). Fundamentals of EMS, NMS and OSS/BSS Management application Web-based server that supports UDP Adapter framework Third-party applications XMLP-UDP FCAPS management Code agents Data conversion/ XML parser Figure 18.3 XMLP management framework. The data derived can be sent out via an adapter framework to feed third-party management applications. An example of this would be CORBA IDL, which is supported by most third-party management applications. Before XML became popular, CORBA was the interface of choice for most management applications. This is quite evident even in standards defined by bodies like TMF, where the MTNM (multitechnology network management) definitions mapped to CORBA. Later the working group of MTNM merged with MTOSI (multitechnology operations system interface) where the mapping is using SOAP, which is an XML based protocol. Using a Web server this information can also be passed to the WWW pool. Any queries from the www pool can also be managed with the framework. An example of such a Web server that can support UDP is the Windows Media Server that does data streaming. There could also be a stand-alone XMLP management application that takes the FCAPS information, processes the information, and represents the information in a GUI (graphical user interface). The XMLP agent that runs on the network element has a set of distinct modules (see Figure 18.4). Consider the scenario in which XML protocol needs to be used on a network element where SNMP was previously used. This means that an SNMP MIB was used to store management data. An SNMP MIB to XMLP schema con- verter should then be available in the agent to make the initial conversion to XML and make the protocol stack a drop in for SNMP. This would not be present in an XML-based agent for which support for SNMP is not required. The data upon con- version is stored in a XML data structure, which can then spread from a flat MIB XML-Based Protocols to an object-ori