rex, Unified Communications, etc.) should be supported. Extensive Protocol Support. Required in Convergent platforms, with the capacity to support traditional protocols-IN, MAP, SMS (SMPP, UCP), MMS, location, and SO on-and new or pure IP protocols and standards such as SIP, Presence, Web Services, LDAP, CTI APIs, and SO on, that is required for the development of different services. Convergent network adaptation supports hybrid networks allowing a smooth transition from IN services to rich, blended services while the network is evolved. Service Brokering for the combination of both internal and external services. Legacy services may have to be invoked in combination with new services in order to avoid their total replacement. For example, prepaid charging, num- ber translation, MultiSIM, and SO forth. This is used in transition processes to mitigate the impact of migration issues. Convergent charging. Should enable prepaid and postpaid charging and cost control, and should be available for any service. Services should be accessible from either the CS or PS network without the need to maintain two parallel service layer infrastructures. Web 2.0 integrations, SOA, mash-ups, revenue sharing, gaming, and SO on. A Network API exposure layer should provide a robust interface with third parties while maintaining full system integrity. 6.2.1 Overview Among APIS, the application aspect means basic and direct requirements of NGSDP, while performance and intelligence are advanced ones, and security is essential consideration. From the perspective of this chapter, when it comes to application, four aspects should be taken into consideration. Telecom Services and Operations: The ultimate goal of NGSDP is to help improve business services and further serve for better business operations and Quality of Experience (QoE) [11-12]. Detailed contents include IMS integra- tions and applications [13-17], telecom network infrastructures [18-19], rapid service creation environment [20-21], and actual converged applica- tions, such as i