Metadata for the Cloud Telco Motivation presentation to ISO/IEC JTC1 SC32 WG2

1. ISO/IEC JTC1/SC32/WG2 N1606 Metadata for the CloudTelco Motivationpresentation to ISO/IEC JTC1 SC32 WG2 Ewelina Szczekocka, Orange Labs Poland, Telekomunikacja Polska S.A. 25th October 2011

2. Cloud – Introduction and characteristic Origin in technology: virtualisation Now: perceived as a business model virtual resource storage + virtual access to resources for the users + pay model) Resources can be products, services, content, applications, data, bandwidth, amount of disk space, CPU ... Disruption of traditional computing model Cloud offers the models: of using the Cloud resources „any time any place, whenever You want” of paying: „pay-per-use” or „pay as you go”

3. Cloud service Cloud Service evolved from Software-as-a-Service model which is an „online” service running on a Service Provider server, available typically through Internet access and charged per usage basis presently extended to other services (not only software): Platform-as-a-Service (PaaS), Infrastructure-as-a-Service (IaaS), CaaS (Communication & Collaboration Services) and in general XaaS = „Everything-as-a-Service”

4. Telco Potential in the Cloud Strength: modern, intelligent scalable networks with huge bandwidth possibilities, strong relationships with TV and content providers (online streaming services), good and stable relationships with clients managed via CRM systems, providing services with respect to QoS and SLA, big experience in services charging/provisioning and assurance (OSS/BSS systems), big experience with service reputation (nature of communication services) Challenges: providing appropriate data centres, envision of new services, interoperability, security, privacy, legal aspects Service candidates to be considered in Cloud model: Services that join communication (audio/video) aspect and IT aspect (business applications) On line multimedia content in form of different services Application stores Storage and computing, smart pipes

5. The Role of Telco in the Cloud Telecommunication network is a central part of cloud architecture aiming at delivery of multi-services for multi-users with high QoS and optimal resource allocation Anticipated main Telco role in Cloud Computing: Network control to achieve cloud services delivery with high QoS thanks to experience in End-to-End SLA management Offering expertise in area of OSS/BSS thanks to big experience in Operation and maintenance (OSS/BSS) for large scale Offering expertise in area of CRM (Customer Relationship Management) thanks to experience with CRM systems on a large scale and good relations to customers Trusted partner – long term experience with high level reputation, security, integrity of privacy while offering communication services (successful implementations of ISO and ITU-T standards) Cloud Intermediary – control the delivery of cloud services offered in federation by different partners

6. Potential Benefits of „being in Cloud” Users: drivers for using Cloud solutions: lower cost (pay-per-use pricing), simplicity (anyway with any device, the same lay out), low migration costs (flexibility and scalability with no complex projects and investments), better availability and QoS, secure important data Cloud Providers and partners: added valued services thanks to engaging different partners (using strength of particular partners) and support from an Internet community Telco/ICT: Cloud delivery model as a converged platform of IT and communication services (fixed, mobile, worldwide) used by any end users’ devices (PC, TV, Smart Phone, M2M...) Rich set of communication services to offer mixed (mashups) with Web 2.0 collaborative services to be CaaS Network services as „smart pipes” (guarantee of security level, performance level, QoS for end users)

7. Telco standardisation interests Standardisation interests (Cloud) Cloud reference architecture, eco-system, use cases (ITU-T, ISO, DMTF) OSS/BSS, Frameworx, SES MS – Software Enabled Services Management Solution (TeleManagement Forum) OVF – Open Virtualisation Format, Virtualisation Management, WS-Management (DMTF) CDNi – Content Delivery Network Interconnect (IETF) Interoperability (ISO/IEC JTC1 SC32, OMG)

8. Limitations concerned with Cloud • Lack of standards • Interoperability and portability issues • Security and privacy issues • Legal issues (licences, sensitive data location) • Costs of storage/data centres

9. Motivation for the Study Limitation issues should be solved to allow achieving prospective benefits for both: users and providers Interoperability aspect is crucial not only at the network and protocols level, but primarily at the service level Cloud will be a place for interoperating between different partners, third parties etc. A huge number of available resources and services should involve advanced techniques of searching, discovering and matching components from the Cloud (e.g. service composition) that is not possible without metadata and semantic level There is already a lot of metadata at candidate Cloud Providers incl. Telco

10. Telco expectations /Questions to reflect ICT in considering Cloud model and cloud interoperability to achieve interoperability on resource level like service, content (multimedia content) that not only enables required exchange of components and communication between providers, but offers opportunities for new kind of services. We see a strong need of simplifying search of the different assets available in the “Cloud” for different kinds of users (e.g. developers, end users). We see also a strong need to receive a functionality of simple matching or composing different components, e.g. discovering similarities and at least suggest which components can be used together for some reason. The idea is to reuse some building blocks that can form more composed functionalities (like services, application components etc).

11. Telco expectations /Questions Question 1: Is Metadata the technology able to address those needs? What is the role for semantics? How those both can be applied to enable interoperability of resources and services? Question 2: Is it necessary to introduce into the Cloud architecture a dedicated layer for interoperability on metadata and semantics level