Follow Me Cloud and Virtualization of (Multimedia) Services and Applications: Challenges and Possible Solutions

Size: px

Start display at page:

Download "Follow Me Cloud and Virtualization of (Multimedia) Services and Applications: Challenges and Possible Solutions"

Sophie Jenkins
5 years ago
Views:

Liebsch (3), Álvaro Rodríguez (4), Paolo Comi (5) (1) University of Bern, Switzerland (2) University

1 Follow Me Cloud and Virtualization of (Multimedia) Services and Applications: Challenges and Possible Solutions André Gomes (1), Torsten Braun (1), Georgios Karagiannis (2), Morteza Karimzadeh (2), Marco Liebsch (3), Álvaro Rodríguez (4), Paolo Comi (5) (1) University of Bern, Switzerland (2) University of Twente, the Netherlands (3) NEC Laboratories Europe, Germany (4) Soft Telecom, Spain (5) ITALTEL, Italy

2 Outline Introduction Services/Applications Virtualization Content Distribution, Caching and Relocation Follow-Me Cloud Digital Signage Service Rating, Charging Billing Conclusions & Future Work MCN. All rights reserved. / Page 2

Introduction How do we access content and services

8 Services/Applications Virtualization General Challenges How to virtualize specific hardware while meeting the same performance requirements? How to virtualize certain services and applications? How can they support it? Which should be the billing model? Who charges who? Who can profit? What kind of mechanisms should be used to make services and applications follow the users seamlessly? In a cloud environment, how do services integrate between each other? MCN. All rights reserved. / Page 8

9 Mobile Content Delivery Networks (MCDNs) CDN: Content Distribution Networks Aim at improving the latency and bandwidth usage to access content by distributing caches of the content across multiple geographic locations Mobile CDNs: CDNs extension inside the mobile networks Enable and maintain short paths for mobile content delivery Objectives: Integration and inter-working of Mobile CDN southbound interface with virtualized Evolved Packet Core (EPC) of the Long-Term Evolution (LTE) Gain advantage from Cloud to add value / optimize Mobile CDN operation Analyze challenges in the virtualization of Mobile CDN and Mobile CDN Frontend; Integration and inter-working with a virtualized Evolved Packet Core; add value (low costs content delivery, high QoE, advanced use cases) by conceptual extensions; use of SDN to integrate and operate Cloud CDN MCN. All rights reserved. / Page 9

10 Mobile Content Delivery Networks (MCDNs) Key Challenges: Instantiation of CDN Serving Points in Cloud networks (Runtime) Relocation of CDN Serving Point instances Alignment with distributed mobility management (relocation of Local Gateway) and IP address continuity Flexible routing/switching of content request and content delivery traffic Support of Cloud control for Context migration and continuity of transport connection Provide transparency of access to the content. CDN EPC/CDN Interworking EPC MCN. All rights reserved. / Page 10

Content-Centric Networking (CCN) / Information-

host-to-end host communication Client/Server-based networking No

efficiently End host-to-content communication

11 Content-Centric Networking (CCN) / Information- Centric-Networking (ICN) In the Current Internet: End host-to-end host communication Client/Server-based networking No multicasting In the CCN/ICN Used to distribute contents very efficiently End host-to-content communication Location-independent content-oriented networking Multicasting effects MCN. All rights reserved. / Page 11

12 Interest Processing in CCN/ICN Three main data structures in CCN/ICN protocol Content Store (CS) : buffer organized for retrieval by prefix match lookup on names. The Least Recently Used (LRU) or Least Frequently Used (LFU) may use as a replacement policy Forwarding Information Base (FIB) : list of information to where the interest packets should be forwarded. A FIB may points to multiple faces Pending Interest Table (PIT) : used to keep track of interest packets forwarded upstream. A PIT may points to multiple sources Processing Interest Messages It means that an equivalent Interest Message has already been forwarded and is pending. Identifying the arrival face of the Interest Message The message is transmitted according to the strategy rules to one or more of the outbound faces registered for the prefix in the FIB MCN. All rights reserved. / Page 12

13 Integration of CCN/CDN Benefits Best of caching, replication and distribution mechanisms. No needs for TCP/IP session continuity. CCN provides reliable mechanisms for content migration/movement. It is very transparent for the end users: Content request by provider (eg. Youtube) and name of the content. The source does not matter and does not need to be known by the end users. Challenges How to integrate the CCN with CDNs? What to use from each of them? What kind of support is needed by the other components in the network? How to get the best from virtualization and cloud principles? How to integrate inside the mobile networks without violating communication standards? (eg. 3GPP) How to deal with user mobility? MCN. All rights reserved. / Page 13

15 Follow-Me Cloud (FMC) Key Concepts When users move, content moves with them to the new location. Such principle may also be applied to service instances. Monitoring can trigger reactive content relocation Proactive content relocation is the most desired scenario Mobility prediction based Not always accurate Challenges How can resources be virtualized in order to allow such relocation? What is the role of caching? Can it be used as a mechanism to avoid full content relocation? What to relocate? Private data is a logical choice, but what about public data? When should relocation be performed? On which conditions? MCN. All rights reserved. / Page 15

16 Follow-Me Cloud (FMC) Where should the relocation take place to? Somehow clear answer when triggering is reactive (and dealing with private content) No clear answer as for now regarding the remaining cases. How to deal with content relocation? Read-only data vs Read-write data Consistency needs to be ensured How to move the content? Chunks along time (as needed)? All at once? What should be used to deal with session continuity? ICN/CCN is not always a reality, so: SDN techniques? NAT? ICN/CCN mechanisms? MCN. All rights reserved. / Page 16

17 So far Mobile CDNs ICN/CCN Follow-me Cloud What happens when you combine them? Service to deal with content distribution, caching and relocation Uses the cloud principles and virtualization to be able to deal with dynamically changing environments Can act as a normal CDN and distribute content (also inside mobile networks) Inserts a new paradigm (ICN/CCN) that creates more transparency for the user and avoid session continuity issues Automatically deals with user mobility and adapts itself to provide the best Quality of Experience (QoE) possible Service that also can be used to provide all the placement logic to other services: More, it can help support them: ICN to relocate services/associated content Distributed content stores and caches MCN. All rights reserved. / Page 17

Digital Signage Service (DSS) Service that enables the distribution of multimedia content over mobile networks Main objective: Re-design the Digital Signage Service (DSS) to exploit the Mobile Cloud

18 Digital Signage Service (DSS) Service that enables the distribution of multimedia content over mobile networks Main objective: Re-design the Digital Signage Service (DSS) to exploit the Mobile Cloud Networking Platform All Digital Signage Service Components (DSS Central Server, DSS Main Content Repository and DSS Content Cache Repositories) should be re-built to be able to be deployed, in a cloud environment, on-demand. Can make extensive use of Mobile CDNs, ICN/CCN and FMC MCN. All rights reserved. / Page 18

19 Digital Signage Service (DSS) Orchestration components will be developed as a control layer for managing the service scalability: Service Components instances will be scaled in/out (horizontally or vertically) depending on the service requirements. Multimedia contents and Service functions will be reallocated closer to the user depending on the user context exploiting MCN Service Migration Capabilities. Advanced monitoring will be developed to improve the Service by reacting to the current context state: Mobility prediction information for interacting with the DSS service dynamically changing the contents in the DS players. Bandwidth prediction for selecting lighter multimedia contents. Better QoS assurance opens new possible video sources which are not usually related to DSS, like CDN contents MCN. All rights reserved. / Page 19

20 Digital Signage Service (DSS) One of the most challenging research issues is the integration of the DSS and the EPC. Part of the re-design of the DSS components will be based on using the supporting services of the envisioned platform and the common interfaces: Load Balancing as a Service Database as a Service Monitoring as a Service DNS as a Service Integration with end-to-end AAA, SLA management and rating, charging and billing will be also applied to exploit the pay-as-you-go concept MCN. All rights reserved. / Page 20

21 Charging as a Service Charging as a service provides charging services to the MCN services. Implemented by the Routing, Charging, Billing as a service (RCBaas) functional block is offered in as a service way: on-demand, elastic, pay-as-you-go. Supports the concept of charging both the service and the platform resources used for providing the service itself. Service Operator charged for the usage of MCN service as a service Service Operator plays different roles: requires MCN service as a service operates MCN service is charged for the MCN service resources provided in as as service way charges its subscribers End User uses the service operates MCN service MCN service (as a service) Cloud platform service monitoring RCBaaS platform monitoring Rating, Charging and Billing of the MCN service, Charging information is generated by platform monitoring and service specific monitoring MCN. All rights reserved. / Page 21

22 Charging as a Service Challenges Define the accounting information flow generated towards the RCBaaS functional box Common metrics provided by the monitoring system of the cloud platform Service specific parameters for each MCN service Design a general model that can be applied to any service realized upon a cloud infrastructure Current Research Activities Telco and cloud perspectives harmonization 3GPP Diameter based charging mechanism Openstack infrastructure, e.g. Celiometer Generalization of the concept for any cloud service charging MCN. All rights reserved. / Page 22

23 Conclusions & Future Work Virtualization can be considered the solution to some challenges towards services integration, mainly to achieve cloudification of resources. Challenges exist to virtualize services themselves, and these must be addressed specifically for each service. Still, the biggest challenge is not to virtualize but rather TO INTEGRATE. Integration is only part of the work. With new capabilities, a new world of research demanding new functionalities and paradigms arise. EC IP FP7 Mobile Cloud Networking to tackle all the referred challenges and achieve concrete solutions MCN. All rights reserved. / Page 23

24 THANK YOU!

25 MCN. All Rights Reserved The information in this document is provided "as is", and no guarantee or warranty is given that the information is fit for any particular purpose. The above referenced consortium members shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials subject to any liability which is mandatory due to applicable law. Copyright by MCN Consortium MCN. All rights reserved. / Page 25

2015 Autumn Semester Seminar ICN in the Cloud

2015 Autumn Semester Seminar ICN in the Cloud André Gomes Universität Bern 2015-11-16 Outline > Introduction and Motivation > Requirements > Architecture and Design > Evaluation and Improvements > Conclusions