1 / 39

WP2 Service Requirements and Overall Architecture CONTENT Y1 EC Review, January, 2014

WP2 Service Requirements and Overall Architecture CONTENT Y1 EC Review, January, 2014. Outline. Concepts and Objectives Work Plan and Deliverables Delivered Work, and Achievements Future Work. 1 2 3 4 . WP2 Concept and Objectives. Concepts.

anoush
Download Presentation

WP2 Service Requirements and Overall Architecture CONTENT Y1 EC Review, January, 2014

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WP2Service Requirements and Overall ArchitectureCONTENT Y1 EC Review, January, 2014

  2. Outline • Concepts and Objectives • Work Plan and Deliverables • Delivered Work, and Achievements • Future Work

  3. 12 3 4 WP2Concept and Objectives

  4. Concepts • WP2 aims to identify the requirements of the CONTENT platform, define use case scenarios and business models and finally specify the overall system architecture.

  5. Objectives • [O1] Identification of the stakeholders involved in the CONTENT platform and specification of Service Requirements • [O2] Business model development • [O3] Use case scenarios definition & early Platform Evaluation plan • [O4] Overall CONTENT Architecture • [O5] Detailed System Architecture Modelling and Evaluation

  6. WP2 Impact on CONTENT WP1 – Project Management WP2 – Service Requirements & Overall Architecture WP3 – Development of the Integrated solution WP5- System Integration & proof of principle demonstration WP4 – Infrastructure virtualization & provisioning of end-to-end services WP6 – Dissemination & exploitation

  7. 12 3 4 WP2Work Plan, Deliverables, Milestones

  8. WP2 @ Glance • Start: M1 End: M24 • Total effort: 69PM • Dividedintothreetasks Research Centres Academia Industry

  9. Tasks • Task 2.1: Capturing of Service Requirements • This task aims to capture and define the service requirements of the potential CONTENT platform. • Task 2.2 Use Case Scenarios and Business Models Specification • This task aims at defining the use case scenarios that will fully demonstrate and evaluate the CONTENT platform and finally identify the exploitable output of the project. • Task 2.3 Overall System Architecture and Specifications • This task aims to specify and define the CONTENT platform architecture.

  10. Deliverables & Milestones • D2.1 Service Requirements (M3) • D2.2 Use Case Scenarios and Business Models (M9) • D2.3 Overall System Architecture Definition and Specifications (M12) • D2.4 Detailed System Architecture Modelling and Evaluation (M24)

  11. Gantt (Original) • Involvedpartners: JUN (10), UNIVBRIS(5), AIT (18),i2CAT (5), NXW (6), UTH (5), PTL (20) • Start: M1 End: M24 D2.1 D2.2 D2.4 D2.3 No deviations!

  12. 123 4 WP2Delivered Work and Achievements

  13. Main Achievements • CONTENT roles definition • Service requirements specification • Use Case definition • MOVNO Business Model • Early Platform Evaluation • Overall architecture specifications methodology • Development of modelling tools • Initial modelling results for the CONTENT architecture evaluation • Definition of the CONTENT generic architecture

  14. CONTENT Roles (I) The following roles have been defined within the CONTENT framework: • Physical Infrastructure Provider (PIP) • The PIP is further divided into: • Optical Infrastructure Provider (OIP) • Wireless Infrastructure Provider (WIP) • DataCentre Infrastructure Provider (DIP) • Virtual Operator (VO) • Service Provider (SP)

  15. Emerging Stakeholder: Mobile-Optical Virtual Network Operator • Extends the operating range of MVNO to “own” and operate virtual resources in the optical metro. • Utilizes converged virtualization architecture of wireless and wired networks and IT resources. • Extends its service portfolio and provides new high-value services to its customers.

  16. CONTENT Service Requirements • High-level Business Requirements • Service Requirements • Integrated Service Network Requirements • Physical Infrastructure Requirements

  17. Use cases Infrastructure and network sharing Cloud service provisioning on top of virtual infrastructures

  18. MOVNO Business Model (I) The PIP provides the VO with logical resources and composes virtual infrastructures on top of its physical resources. The VO is then able to provide SPthe ability to provide services to its customers.

  19. MOVNO Business Model (II) • The PIP will establish pay-as-you-go contract and an SLA agreement with the VO in order for the VO to spread its reach, whilst the VO will provide the SP the ability to increase its business opportunities through contracts that will be established with new customers. • The MOVNO will pay the PIP per usage e.g. per access, per user and avoid the flat rate per period. • The SP will pay the MOVNO depending on the network usage.

  20. Early Platform Evaluation Plan • 2 use cases were selected as potential candidates to demonstrate and evaluate the CONENT during the trials and evaluation period: • Mobile Optical Virtual Network Operator (MOVNO) in a multi-operator environment • Mobile broadband-enabled cloud services by MOVNO • The selection took into consideration: • The technical innovation • The possibility to deploy the components required by the use case on a test bed for demonstrations • The capability to provide wide support for a variety of services, in order to allow the validation of the CONTENT solution in different contexts and conditions • The requirements described in D2.1

  21. CONTENT Architecture (II) • Layered architecture : • cross-technology virtualization to support optimised, seamless and coordinated cloud and mobile cloud service provisioning across heterogeneous network domains

  22. Physical Infrastructure Layer - TSON • The Time Shared Optical Network (TSON) data plane consists of FPGA nodes for high speed processing at 10Gb/s per wavelength data rate • The operational architecture of the TSON nodes involves three layers: • Routing and resource allocation • TSON Layer 2 functions • TSON Layer 1 functions TSON network interconnecting DC and wireless access networks

  23. Physical Infrastructure Layer - Wireless Network Architecture • Basic components of the NITOS Platform • NITOS Bridge: point where VLAN network connections through the GEANT network terminate • Openflow based wireless Backhaul network • WiFi/LTE Access network • Control network • Details of the NITOS testbedare provided in D4.1 NITOS testbed architecture

  24. Heterogeneous Physical Infrastructure • Heterogeneous Physical Infrastructure Layer: including a hybrid wireless access network (LTE/WiFi) domain, and an optical metro network domain (TSON) interconnecting geographically distributed data centres • Interfaces performing: • Scheduling • Aggregation/De-Aggregation • Traffic adaptation • QoS Mapping

  25. Infrastructure Management • Infrastructure Management Layer: is overall responsible for the management of the network infrastructure and the creation of virtual network infrastructures over the underlying physical resources.

  26. Converged Service Orchestration • Control Layer: responsible to provision IT and (mobile) connectivity services in the cloud and network domains respectively. • Service Orchestration Layer: responsible for efficient coordination of the cloud and network resources to enable end-to-end composition and delivery of integrated cloud, mobile cloud and network services in mobile environments with guaranteed QoE.

  27. CONTENT architecture evaluation • Objective: a dynamically reconfigurable, energy efficient virtual infrastructure • VI planning: designing the virtual infrastructures and mapping the virtual to physical resources • Considering: • Energy consumption of wireless, optical and DC domains through relevant models • Mobility of end users • A stochastic mobility model has been adopted to predict mobile users’ locations and ensure seamless service provisioning across the various network segments • The problem has been described through suitable mathematical formulation

  28. Comparison between Mobile Cloud Solutions • Cloudlet Approach: Small DCs in the wireless access and large DCs in the core to support mobile and fixed cloud traffic • CONTENT Approach: DCs fully converged with the broadband wireless access and the metro optical network

  29. Performance Comparison: Delay • Comparison in terms of delay between the CONTENT architecture and the cloudlet: • Considering that the minimum packet delay in LTE networks is measured to be of the order of 100ms the additional 2ms delay of the CONTENT solution is negligible • The additional delay, can be compensated by allocating extra resources in the DC domain

  30. Performance Comparison: Power • Impact of traffic load on power consumption for the CONTENT and the Cloudlet scheme • the wireless access technology is responsible for 43% of the overall power consumption • the optical network consumes less than 7% of the energy

  31. Impact of Mobility • Service-to-Mobility Factor: fraction of the service holding time over the cell residence time • Power consumption increases with mobility.

  32. 1234 WP2Future Work [Plan for Year 2]

  33. Future Work • Detailed System Architecture Modelling and Evaluation • D2.4 (M24) • Report the refined CONTENT architecture together with a detailed evaluation of its performance through modelling and simulations. • RemainingEffort per partner: JUN (7), UNIVBRIS(1), AIT (6.1),i2CAT (0.65), NXW (1.74), UTH (3.24), PTL (5.3)

  34. Conclusions WP2 • Identified the CONTENT stakeholders • Specified of Service Requirements • Developed the MOVNO Business model • Defined the CONTENT use case scenarios • Outlined an early Platform Evaluation plan • Defined the overall CONTENT Architecture

  35. Dora Christofi PrimeTel Anna Tzanakaki AIT Thank You Ευχαριστώ

  36. Dora Christofi PrimeTel Anna Tzanakaki AIT Backup slides

  37. Integration of Technology Domains • TSON nodes receive the Ethernet frames and arrange them to different buffers that are part of the node. • The Ethernet frames are aggregated into TSON frames, which are then assigned to a suitable time-slot and wavelength for further transmission in the network on a First In First Out (FIFO) basis. • When these frames reach the interface between the optical and the DC domains the reverse function takes place

  38. Network Power Consumption • The overall network power consumption model considers: • The active elements of the WDM metro network, based on the Time Shared Optical Network (TSON), supporting frame-based sub-wavelength switching granularity • A cellular LTE system for the wireless access domain and a collection of wireless microwave links for the interconnection of the LTE-enabled based stations • Linear power consumption for the DCs • 100% power overhead due to cooling

  39. Numerical Results & Comparisons • The wireless access technology consumes 50%, while the optical network less than 10% of the total energy • There is a trade-off between mobility and utilization of physical resources: • For high mobility additional resources are required to support the VI in the wireless access domain • This additional resource requirement also propagates in the optical metro network and the IT domain

More Related