ented framework. The movement from flat MIB to object-oriented framework is a major requirement for making the system suitable for managing complex next generation networks and its elements. The SNMP MIB to XML schema conversion is a two-step process. In the first step the MIB definition is converted into a simple set of flat object definitions. This involves collecting all the scalar MIB variables under a module into a single object, and then modeling all the tables as contained objects. Each table would result in a separate object type or class. In the 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 M