Network Slicing Terms and Systems - PowerPoint PPT Presentation

Draft V5 - 12 th July 2017 Network Slicing Terms and Systems draft-galis-netslices-revised-problem-statement-01 draft-geng-netslices-architecture-02 draft-netslices-usecases-01 draft-qiang-netslices-gap-analysis-01 draft-flinck-slicing-management-00 Scope of the presentation: • What do I mean by network slicing? • What non-IETF work is relevant? • What IETF work is needed? On behalf of the 25 draft authors and proponents acknowledged in the last slide Prof. Alex Galis a.gais@ucl.ac.uk University College London, U.K.

What do I mean by network slicing? • “The service cannot provide optimal experience on a best-effort network”; • “It is inefficient and expensive to build a separate infrastructure for each service” . Network Slice - A Network slice is a managed group of subsets of resources, network functions / network virtual functions at the data, control, management/orchestration and service planes at a given time. Network slice is programmable and has the ability to expose its capabilities. The behaviour of the network slice realized via network slice instances (i.e. activated network slices; dynamically and non-disruptively reprovisioned)  A Network slice is supporting well at least one type of service.  A network slice may consist of cross-domain components from separate domains in the same/different administrations or components applicable to access network, transport network, core network and edge networks.  A resource only partition is one the components of a Network Slice, however on its own does not represent fully a Network Slice  Underlays / overlays supporting all services equally (‘best effort” support) are not representing fully a Network Slice Main SDOs relevant references: NGMN Slices (2016) - consist of 3 layers: 1) Service Instance Layer, 2) Network Slice Instance Layer, and 3) Resource layer. 3GPP - SA2 23.799 Study Item “Network Slicing’ ( 2016) ; SA5 TR 28.801Study Item “Network Slicing (2017) ITU-T IMT2020 - Recommendations: 5G Architecture, Management of 5G, Network Softwarisation and Slicing - (2016 – 2017) ONF - Recommendation TR-526 “Applying SDN architecture to Network Slicing” (2016) BBF - Requirements / architecture of transport network slicing SD-406: End-to-End Network Slicing (2017) ETSI - NFV priorities for 5G (white paper) (2017) IETF 99 – Network Slicing BoF Monday 17 th July 2017

Network Slicing is No1 Emerging Engineering Impactful Problem at IETF. “ A service cannot provide optimal experience on a best-effort network”; “It is inefficient and expensive to build a separate infrastructure for each service ”. Network Slices Key Characteristics: • mainly an embedded management concept supporting well of at least one service at a given time. It is also includes coordinating/orchestrating network functions and resources. • dynamically and non-disruptively reprovisioned . • is a dedicated network that is build on an infrastructure mainly composed of, but not limited to, connectivity, storage and computing. • concurrently deployed with isolation guarantees as multiple logical, self-contained and independent, partitioned network functions and resources on a common physical infrastructure in order to support well at least one service. • ability to dynamically expose and possibly negotiate the parameters that characterize an network slice. Network slices are configurable and programmable. • has its own operator that sees it as a complete network infrastructure and to use part of the network resources to meet stringent resource requirements. • supporting tenant(s) that are strongly independent on infrastructure. • introducing an additional layer of abstraction by the creation of logically or physically isolated groups of network resources and network function/virtual network functions configurations separating its behavior from the underlying physical network.  a number of related sub- problems need to be addressed by IETF IETF 99 – Network Slicing BoF Monday 17 th July 2017

What IETF work is needed? Proposed High Priority Problems to Resolve "Cross-Domain Coordination” Network Slicing Reference Architecture • Service/data model & mapping in a single domain and Cross-Domain Network Slice Network Slice Coordination Provider Tenant • Slice stitching / composition in a single domain and Cross-Domain Coordination "Network Slicing OAM” • Network Slice life cycle management • Network Slice Monitoring and Discovery • Autonomic slice management and operation • E2E Network Orchestration Network Infrastructure “Performance Guarantee and Isolation” • Guarantees for network slice isolation Control Plane Service Hosted Network Slice Network Slice Network Slice Adjustment Assurance Instantiation "Slicing Resource & Requirement Description” Data Plane • Uniform Reference Model Network Other • Slice Templates Connections Functions Resources • Capability exposure and APIs IETF 99 – Network Slicing BoF Monday 17 th July 2017

Proposed IETF Work Problems ( cntd ) : Network Slice Life Cycle Management; E2E Network Orchestration NS Life Cycle Manag: 1. The management plane creates the grouping of network resources (physical, virtual or a combination thereof), it connects with the physical and virtual network and service functions and it instantiates all of the network and service functions assigned to the slice. 2. Template/NS repository to assist life cycle management; 3. Resource Registrar to manage exposed network infrastructure capabilities; 4. NS Manager to oversee individual slice (capability exposure to NS Tenant ) Service Plane Embedded Softwarization Orchestration Slice Networking E2E Orchestration (1) Coordinate a Management Plane Control Plane Data Plane number of interrelated resources a Network (Virtual) Functions Network Infrastructure number of subordinate domains, and to Resource (Physical and Virtual) Instantiation assure transactional integrity as part of Instances (Service, Management, Control, and Data planes) the process; (2) Autonomically control Service Plane Service Plane Service Plane Service Plane of slice life cycle management , Orchestration Orchestration Orchestration Orchestration M M M M Slice Slice Slice Slice G G G G Networking Networking Networking Networking M M M M including concatenation of slices in each T T T T Control Plane Control Plane Control Plane Control Plane segment of the infrastructure (in data, Data Plane Data Plane Data Plane Data Plane control and management planes); (3) + ------------------------------------------------+ | Inter-Network Slice Orchestration | Autonomically coordinate and trigger +-------------------------------------------------+ | | | of slice elasticity and placement ; (4) +----------+ +-----------+ +----------+ | Network | | Network | | Network | Coordinates and (re)-configure | Slice 1 | | Slice 2 | | Slice N | | SEM |------| SEM |------ ... -- | SEM | +----------+ +-----------+ +----------+ resources by taking over the control of all | | | +-------------------------------------------------------------+ the network functions. | Resources / Network Functions | +-------------------------------------------------------------+ | | | | +--------+ : +--------+ : +--------+ : +--------+ | NE 1 |----- | NE 2 |----- | NE 3 |----...-- | NE n | +--------+ : +--------+ : +--------+ : +--------+ IETF 99 – Network Slicing BoF Monday 17 th July 2017