Endtoend Network Slicing Training Course Outline Concept of

End-to-end Network Slicing Training Course

Outline • • Concept of Slicing • • Architecture Management Slice overview Po. C by Openstack • • Terminologies mapping Management & Orchestration Experiments • • • Exercise 1 – Setup Openstack with Tacker Exercise 2 – Deploy OAI-CN by Tacker and make UE attachment successful Detail about ITRI’s testbed Setup of e. MBB experiment Setup of m. MTC experiment Setup of URLLC experiment 2

Concept of Slicing – Architecture • • Network Slice • A logical end-to-end network • 5 G Core. Network (CP & UP) • 5 G Radio Access Network • Interworking Functions to non-3 GPP Access Networks • UE connects • Max 8 slices in parallel • Common Access Management Function (AMF) for one UE in all slices • Dynamically created • Event-driven • Time-driven Different slices for different services types • Committed services – slice types • Enhanced Mobile Broadband (e. MBB) • Ultra Realizable Low Latency Communication (URLLC) • Massive Mechanic Type Communication (m. MTC) • Dedicated customers • Verticals • Tenants 3

Concept of Slicing – Management • Network slicing is about • transforming the system from a static “one size fits all” paradigm, • • • to a new paradigm where logical networks/partitions are created, with • appropriate isolation, resources and optimized topology • to serve a particular purpose or service category • or individual customers 3 GPP identified related use cases, potential requirements and potential solutions for • lifecycle management • • fault management configuration management performance management policy management 3 GPP has identified and describes the following management functions • the Communication Service Management Function • the Network Slice Management Function • the Network Subnet Slice Management Function 4

Slice overview (1/2) 5

Slice overview (2/2) • • • Joint Computing and Communication resource § Computing Resource (Central Office, Mobile Edge), § Network Resource (Transport Network, Radio Access Network) Upper resource bond for each slice Multiple services on a slice 6

Po. C by Openstack – Architecture 7

Po. C by Openstack – Terminologies mapping • VIM ID, Tenant ID, VIM Name 8

Po. C by Openstack – Terminologies mapping 9

Project/Tenant (Vertical/Tenant) 10

Service (server/vnf) 11

Service of individual customers 12

Network (Slice) 13

Service of Slice 14

Flavor (Resource Template) 15

Resource Monitoring (1/3) 16

Resource Monitoring (2/3) 17

Resource Monitoring (3/3) 18

Exercise 1 Setup Openstack with Tacker • Openstack PIKE • • https: //docs. openstack. org/pike/install/ Tacker • https: //wiki. openstack. org/wiki/Tacker/Installation 19

Exercise 2 Deploy OAI-CN by Tacker and make UE attachment successful • Deploy by Tacker • • OAI-CN • • https: //github. com/openstack/tacker/tree/master/sample s https: //gitlab. eurecom. fr/users/sign_in Next. EPC • https: //github. com/acetcom/nextepc 20

Experiment setup for Magazine paper – Detail about the testbed 21

Experiment setup for Magazine paper – Setup of e. MBB experiment • • • Scenario: Video start up time Required delay: 10000 ms (10 s) Total: 10 video streams Cases (C/E): 10: 0, 9: 1, 7: 3, 5: 5, 3: 7, 1: 9, 0: 10 Video server setup: • vb=1024 • • ab=128 fps=60 Capacity of instance: 1 Core, 2 G RAM 22

Experiment setup for Magazine paper – Setup of m. MTC experiment • • • Scenario: Smart factory Required delay: 100 ms Total: 500 connections Cases (C/E): 10: 0, 9: 1, 7: 3, 5: 5, 3: 7, 1: 9, 0: 10 Io. T client setup: • message size: 100 bits Capacity of instance: 1 Core, 2 G RAM 23

Experiment setup for Magazine paper – Setup of URLLC experiment • • • Scenario: V 2 X Required delay: 25 ms Total: 10000 frames Cases (C/E): 10: 0, 9: 1, 7: 3, 5: 5, 3: 7, 1: 9, 0: 10 V 2 X client setup: • message size: 160 bits • Time interval: 1 ms Capacity of instance: 1 Core, 2 G RAM 24