to support competitive multimedia services from the Internet [13]. 9.4.1 Proposed Service Delivery Platform for Inter-Working between IMS and WS SIP-based Micro Service Orchestration and Web service bus are used to seamlessly integrate IMS, WS and the underlying services. The design objectives of the SDP for inter-working between IMS and WS are To be transparent to services it controls. For example, it enables users to select, invoke, and compose services and services can be added, deleted, and moved without knowing the underlying network architecture. To enable network service blending, for example, fast and effective way to combine (compose) two or more services (both local and remote), and handle SIP messages originated from services and AS under its control, and routing of SIP messages among services and AS. To ease Internet service mash-up, for example, availability, accessibility of services via WS SOA with effective SOAP-SIP/ISC mapping "intermediaries" (e.g., JSR-116/289). Design and Implementation of an IMS-Based Testbed To enhance IMS service triggers and to enhance IMS initial filter criteria (iFC) with customization and interactive user triggers and controls. To inter-work with legacy services, for example, Customized Applications for Mobile networks Enhanced Logic (CAMEL) [22] and Open Software Architecture (OSA) based inter-working via SIP "intermediaries" (e.g., mes- sage adaptation, charging event generation, etc.). To provide policy management by following unified service and resource man- agement and the IETF Common Open Policy Service (COPS) framework. Figure 9.6 shows the architecture of the proposed SDP architecture for inter- working between IMS- and WS-based services. The architecture is a collection of different services from IMS (lower half of Figure 9.6) and WS applications (upper half of Figure 9.6), linked (indicated by solid arrow lines) to the proposed SIP- based microservice orchestration layer by standardized signaling protocols such as SIP and DIAMETER [23]. Notice that both the l