mework and Adoption Strategy types of networks. The generic framework and functionalities designed SO far can be used with different kinds of networks and not just for IMS. 34.5.3 Specialized Functions In this report a sample application for IMS network is considered to detail a special- ized application. Now it is time to add the IMS specific functions as part of phase 3 of the NGNM solution development. One of the functionalities required for an IMS network is provisioning of the subscriber database residing on the HSS. Figure 34.4 in this section on subscriber provisioning shows how the HSS provisioning is imple- mented in the NMS framework. An HSS provisioning agent sends SOAP triggers to HSS and also updates a common subscriber store based on a generic user profile for a converged network. The interface used is SOAP over HTTP, SO it is standardized to use any agent. Messaging is based on XML schema files for HSS IMS GUP components. This uses the SOAP protocol as defined by 3GPP for subscriber provisioning with http for Web interfacing. The common subscriber store helps in managing multiple HLR and HSS. "3GPP TS 29.240" Release 7 can be referred to for identifying the IMS GUP components. The use of SOAP in the design of HSS subscriber provisioning is also recommended in this 3GPP document. It can be seen that SOAP is also the suggested protocol for implementation in the MTOSI interface. Another NMS function that can be added is charging management based on 3GPP guidelines. The 3GPP specifications on IMS and OAM&P can be referred to at www.3gpp. org and www.3gpp2.org for more functionality specific to IMS that can be added in the NMS. OSS/BSS /http HSS provisioning agent NMS server Common subscriber trigger store (GUP) SOAP client Figure 34.4 HSS subscriber provisioning. Fundamentals of EMS, NMS and OSS/BSS 34.5.4 Customization for a Specific Network The final phase of the NGNM solution development that involves customization for a specific network whenever required is discussed next. The previous discussion o