te reasonable and sound over the different Web 2.0 start-ups and all the collaborative services that have shown up all along Internet. Cloud Computing is based on the virtualization of the resources, mainly computing power and storage. It allows using the resources in a very flexible way and being dynamically able to add new resource with a fine grain measure. It provides an elastic way of paying as you grow for the resources needed. This has been used into private clouds, where it virtualized all the resources available in the computer department in order to allow users to gain access exactly with the resources they need. Also, there have appeared public clouds where users may be able to buy, quite cheap, the resources needed on demand. This solution is useful for end-users, helping them in the implementation of new services in an important issue: how to dimension your computing resources. Most of the technologies in cloud computing are based on using virtual operat- ing system images into the cloud server and instantiate, with the proper parameters, an image of the operating system and services needed. This image is quite closer to the one provided by the SDP layer into IMS archi- tecture. In the SDP, there are different services available, usually by an API or Moving the SDP to the Cloud enablers, without need to care where are deployed or the real details for the configuration. Cloud computing has been deployed into three layers: Infrastructure as a Service (IaaS) Platform as a Service (PaaS) Software as a Service (SaaS) Most of the Internet Web 2.0 applications fall into the Software as a Service layer. Applying this model to the IMS architecture, it is possible to find similarities and, in the case of SDP, it can be considered as a PaaS or a SaaS, depending if the SDP services are taking into account like a final service. This approach may be quite convenient from the architectural perspective and provides a convergence of the Telco and Internet world. This proposal currently does not consider that any oper