Futurecom 2019 - NECOS
1 like217 views
This document discusses cloud network slicing and lessons learned from the NECOS project. It begins with an introduction to cloud network slicing and example use cases. It then describes the NECOS project, which aimed to address challenges in cloud network slicing such as slice lifecycle management across multiple domains, end-to-end multi-domain orchestration, and ensuring quality of service guarantees for slices. Some key lessons learned from NECOS include the need for marketplace functionality to request and provision slices, methods for vertical and horizontal slice elasticity triggered by slice performance metrics, and handling heterogeneity across virtual infrastructure managers and monitoring systems.
Futurecom 2019 - NECOS
- 1. Fábio Luciano Verdi UFSCar http://www.h2020-necos.eu/ Cloud Network Slicing: Challenges and Lessons learned from the NECOS Project
- 2. Agenda ● Introduction to cloud network slice ● Use cases ● The NECOS project ○ What is NECOS ○ Challenges and lessons learned
- 3. The journey
- 4. What is a cloud network slice? … 5G PPP Architecture Working Group View on 5G Architecture (Version 2.0) From network slicing to cloud network slicing
- 5. What is a cloud network slice? ● ● ● ● ●
- 6. Use cases ● Mission-critical Ultra low latency communication ● Massive-connectivity machine communication (e.g. Smart metering, Smart grid and sensor networks) ● Extreme QoS ● Independent QoS isolation design ● Independent operations and management ● Independent autonomic management functionality ● Independent cost and/or energy optimization ● Independent multi-topology routing ● Sharing Infrastructure: Enablers for sharing infrastructure safely and efficiently (Multi-tenant)
- 7. Roles ● Infrastructure Owner owns the physical infrastructure (network/cloud/datacentre) and leases them to operators. It becomes an infrastructure slice provider (ISP) if it leases the infrastructure in network slicing fashion. ● Infrastructure Slice Provider – An ISP, typically a telecommunication service provider, is the owner or tenant of the infrastructures from which network slices can be created. ● Infrastructure Slice Tenant – An infrastructure slice tenant (IST) is the user of specific network/cloud/datacentre slice, in which customized services are hosted. Infrastructure slice tenants can make requests for the creation of new infrastructure slice through a service model.
- 8. Types of slices and control responsibilities
- 9. Challenges ● Slice Life Cycle Management: ○ creation and connection of physical and virtual resources (computing, networking and storage); ○ activation / deactivation, protection, elasticity, extensibility, safety, and sizing of the slicing model per network and per network cloud for slices in access, core and transport networks; ○ different technological solutions / VIMs: Openstack, Kubernets, etc. ● E2E multi-domain Orchestration ○ autonomic control of slice life cycle management, including concatenation of slices in each segment of the infrastructure (in data, control, and management planes); ○ autonomic coordination and triggering of slice elasticity and placement; ● Network Slices with guaranteed QoS / KPIs characteristics - Precision Network Services
- 10. NECOS Resource Marketplace Tenant’s Domain Slice Activator Slice Domain Orchestrator Domain Mgm Domain Orchestrator Domain Mgm NECOS(LSDC) SliceProvider Net Central DC DCSlice Controller SliceAgent VIM 2 MonMonWIMVIM 1 Mon WANSlice Controller SliceAgent VIM / WIM specific Control Interface Slice Marketplace Interface Slicing Orchestrator Slice Builder Infr. & Mon. Abstraction Slice Broker Domain Orchestrator DCSlice Controller SliceAgent Domain Mgm Edge DC Resource & VM Mgmt Resource & VM Monitoring Adapters Slice Resource Orchestrator Slices Database Slice Spec. Processor Slice Description Resource Domains Service Orchestrator Slice Request Interface Client to Cloud Interface Service Orchestrator Adaptor Slice Runtime Interface VIM / WIM specific Monitoring Interface Service Level Monitoring CloudtoCloudInterface Slice Instantiation Interface
- 11. Lessons learned (so far) ● E2E Orchestration ○ Marketplace ● Elasticity ○ Vertical ○ Horizontal ○ Triggered by slice and service KPIs ● Heterogeneity ○ VIM on-demand ○ Elastic monitoring Core DC VIM 1 Slice Part Elasticity Physical Resources Service Elasticity Slice Physical Resources
- 12. Q&A Thanks to all the NECOS partners!!! www.dcomp.sor.ufscar.br/verdi http://www.h2020-necos.eu/