 and through standardized interfaces in the IMS, which ease the developers' responsibility in assembling and deployment of new services. Besides this advantage, the matter complicates through the possible vendor-selection for reusable components as well as through the demand to bring IT, Internet, and so-called Web 2.0 services that evolve from the "cloud" beyond an operator's boundaries into the new product and service assembly mix. This demand brought the need for new service broker technology to the light. 4.2.3.1 Network Service Brokering and Service Capability Interaction Management Service brokering as well as terms like Service Capability Interaction Management (SCIM), service chaining, and SO on, are aiming to describe the technology to cre- ate "blended services," "combinational services," and product assemblies up to "Telco 2.0 mash-ups," which are all targeting the mixing of multiple services together into new product offerings. All these terms are used slightly different in different consortia. The 3GPP [2] distinguishes the terms such that service broker- ing belongs to legacy networks while the new term of SCIM belongs rather to IMS. An IN service broker is a function in the legacy IN network which sits between the service/feature/application and the switch to overcome the SS7 signaling problem that only one service can control the call. This way, the service broker seems to be a Service Delivery Platforms single functional service control point but it actually coordinates the interaction between multiple services and features. Through the way to a centralized service trigger management, the evolutionary path to IMS was given where the service invocation takes place at the signaling core. The functional architecture for the management of the user's service-related information via the SCIM as been pro- posed by 3GPP for the IMS; details are given in TS 23.002 [2]. Hereby, an SIP AS may contain the SCIM functionality and other ASs. The SCIM functionality is an application which performs the role of in