IMS capabilities using the appropriate protocol (SIP or XCAP). Obviously, the interactions on each side must be properly inter- related. It can be clearly seen that it is actually a gateway between HTTP and IMS protocols. The WIMS 2.0 holds the IMS Exposure Layer as a major axis for the architecture. IMS 2.0 PSEs Platform: This entity holds and serves the operator's PSEs to be incrusted into the Web 2.0 sites. PSEs implement the required logic to inter- act with a specific group of open IMS APIs (the ones considered above). Access control entity: To secure the use of the operator's APIs, this entity performs the required access control mechanisms. The entities for the exchange of multimedia content and events, and their functionalities, are the following: Subscription Management enabler: It subscribes to content and events of any kind generated in Web 2.0 services. Subscriptions may be made on behalf of the operator or directly on behalf of the final user. This entity talks with the Moving the SDP to the Cloud Content and Events Distribution enabler to inform about the existence of new content/events to be obtained. Content and Events Distribution enabler: It downloads, adapts, and transmits content and events from Web 2.0 services to Telco users. User-Generated Content enabler: It receives content from terminals and, after adapting its format, it uploads this content to Web 2.0 services. IDs and Preferences: Database that stores the relationships between Telco identities and the identities used by Web 2.0 services. The other entities of this group consult this database to perform the conversion of identities when using the Web 2.0 services APIs. Finally, we find an individual entity for the provision of Telco online applications. On one side, this entity interacts with IMS& Telco capabilities, acting as the final Telco client. On the other side, it shows a rich multimedia Web interface to the user, according to the service being provided. This entity must also handle a con- tinuous media interface toward the use