29. M. Gudgin et al., SOAP Version 1.2 Part 1: Messaging Framework, Recommendation, W3C, June 2003. 30. R. Fielding et al., Hypertext Transfer Protocol-HTTP/1.1, RFC 2068, IETF Network Working Group, January 1997. Chapter 3 Moving the SDP to the Cloud Luis Angel Galindo Sánchez and Joaquín Salvachúa Rodríguez Contents Introduction WIMS 2.0 Initiative 3.2.1 What Is WIMS 2.0? 3.2.2 WIMS 2.0 Strategic Lines 3.2.3 WIMS 2.0 SDP 3.2.4 Web 2.0 Technologies in the WIMS 2.0 SDP 3.2.5 Key Entity in the WIMS 2.0 SDP 3.2.6 WIMS 2.0 SDP Deployment SDP in the Cloud WIMS 2.0 SDP in the Cloud 3.5 Conclusions References 3.1 Introduction A Service Delivery Platform (SDP) usually refers to a set of components within telecom operator service architecture that manages easing service creation, deploy- ment, and execution utilizing enablers (network capabilities) and service capabili- ties. The keystone objective of a SDP would be to reduce the time taken to market Service Delivery Platforms of a service and the key characteristic for an SDP is thus, the ability to ease the integration task of application logic with the enablers and capabilities in the tele- com service architecture for the delivery of a service to users. The SDP thus enables the rapid transformation of a service concept into a full product including all the related service life cycle management and commercial interactions. There is no global standard for SDP implementation, although there are some industrial de facto conventions. Four interfaces can be considered for describing SDP following a compass-inspired interpretation, as it is depicted in Figure 3.1. North interface: An SDP provides clear service interfaces for exposing telecom capabilities, both for in-house development as well as enabling external agents to develop services and applications using the operator as the platform. In this case, operators open APIs of internal features/capabilities. South interface: It is where the SDP simplifies the process of integrating an application container with the network