 infrastructure and enablers. Thus, the SDP provides abstractions for invoking telephony, media, and other service features. West and East interfaces: It is the way where the SDP simplifies the integration of a new application toward the commercial and operation systems of the company. The SDP includes connectors to the OSS and BSS systems of the operator, as well as for other back-office applications. By means of this connection to OSS/BSS, the services deployed over the SDP can be inte- grated into the company service and product life cycle management, includ- ing operations like provision and activation of services; supervision and failure management, administrative validations, billing, and QoE measurement. In-house Third party services services Enablers Networks Figure 3.1 SDP interfaces. Moving the SDP to the Cloud Nevertheless, the SDP typically provides a service creation environment for service design, and a service orchestration and execution environment, which rep- resents the core of the SDP. Together with this core functions, there is a set of components in the SDP to enable policy control, security, user directories, and other functions for business/operation process adherence and integration. One of the most common situations in the SDP deployments is the adoption of Service Oriented Architecture (SOA) {SOA} in the SDP. SOA simplifies enabler deployment and facilitates other SDP requirements for composition, reuse, delega- tion, orchestration, policy enforcement, and business/operation process adherence and integration. SDP and the election of SOA for its implementation have been deemed necessary in order to cope with a series of business drivers; in particular, the SDP focuses on the reduction of time-to-market for new services, as already men- tioned. It is also expected that the SOA-based SDP allows the creation of a wider range of value-added services in a cost-efficient way, the implementation of an open-service marketplace for third-party interactions, and the efficient integration with OSS/B