ement Forum (TMF) can be referred to understand the requirements of next generation network management. The studies in this release of TMF also look into works from different standardizing bodies working on NGNM. Some of these organizations include ITU-T, 3GPP, OASIS, OIF, MEF, and SO on. The supporting document in TR133 of TMF lists the requirements from which the management functional modules to be implemented needs to be identified. The implementation of these functions should be in line with the existing frame- work. It should use an SOA based design and have support for common informa- tion and interface model. Sample architecture for developing an event engine based on standards is discussed next. One of the requirements for NGNM is the building of self-learning and sur- vivable networks. This is achieved in the proposed NMS framework by using the event driven architecture. EDA enables the NMS to have dynamic and automatic allocation of network resources. The network management systems built on this framework would be able to do proactive trend monitoring and build survivable networks. The architecture of such an event engine is shown in Figure 34.3. It can be seen that the architecture builds the event engine as an independent module that can collect data in a standard format or a legacy system. Another generic functionality that can be implemented in NMS is SSO (single-sign-on). TR133 can be referred to for a complete understanding. The generic NGNM framework in itself leads to satisfying some of the require- ments of NGNM. For example M.3060 of ITU-T recommends support for multiple Legacy event database External rule definition interface (xml) Open source/legacy Alarm Performance rule engine database database Resource and its attributes Event Event monitor Adaptor (Security, administration, formatter To NBI accounting..... Event Event Action handler storage processor Process To SBI handling Event bus Data from SOA and standards-based NMS (where events are aggregated and presented in a specific format) Fi