E2E NW Slicing Architecture Yusuke Nakano, KDDI TSG37005 TSG 11.09.2019 Bangkok Agenda Introduction Future Network NEST NEST WP1 Next Steps Introduction 3 Part of Future Network Programmes Started in 2017, still growing with 40 member
"E2E NW Slicing Architecture Yusuke Nakano, KDDI" is the property of its rightful owner. Permission is granted to
download and print the materials on this website for personal, non-commercial use only, and to display it
on your personal computer provided you do not modify the materials and that you retain all copyright
notices contained in the materials. By downloading content from our website, you accept the terms of this
agreement.
Agenda Introduction
Future Network NEST
NEST – WP1
Next Steps<br>
03
Introduction 3 Part of Future Network Programmes
Started in 2017, still growing with 40 member companies
Multitude of activities to socialize network slicing
2 full papers and 3 booklets
Definition of network slicing from a customer point of view
Vertical customer requirements analysis
Characterization of network slices in a generic way
5 seminars held during Mobile World Congress events
Participation on many other events around network slicing
Generic network Slice Template (now NG.116)<br>
04
Network Slicing Taskforce (NEST) Structure 4 NEST – plenary
(CK Hutchison) WP1: E2E architecture
(KDDI) WP2: Business aspects
(Verizon) WP3: Isolation
(CMCC) WP4: Roaming
(Deutsche Telekom) WP5: External interactions
(GSMA) NG/5GJA WAS/WSOLU FASG/5GSTF Deliverables: each Work Package will develop recommendations, PRDs, papers for their areas
Participation: Regional points of presence Documents developed in:
WP2 will flow into WAS
WP3 will flow to 5GSTF and 5GJA
WP4 will flow to WAS and 5GJA TSG WP6: PoC
(GSMA)<br>
05
NEST WP overview 5 WP2: Business aspects WP3: Isolation WP4: Roaming WP5: External interactions WP6: PoC Business relationship analysis for nw slicing: identify current industry views; identify possible new relationships and roles
Identify aspects of Service Level Objective (e.g. evolution, verification, exposure) to support the business relationships of network slicing Analyse vertical requirements in terms of isolation
Analyse how different levels of isolation can meet verticals’ requirements Analysis of vertical requirements in terms of global slice availability
Slice treatment in VPLMN, e.g. LBO vs. HR Vertical engagement: Continuation of the dialogue with the vertical industries
Marketing: Advertising the output and achievements of the group
Cooperation: Continuing the discussions with other organizations, e.g. 5G-ACIA, 5GAA, etc. Bring the Network Slicing from theoretical level to practical implantation incorporation with key stake holders
Validate the key concepts of Network Slicing<br>
06
WP1:E2E architecture<br>
07
Introduction 7 Background
NW Slicing is one of the key functionalities of 5G. It is highly significant to meet diversifying needs of the times.
However, the specifications ever defined still remain intra-domain discussion, e.g., mobile core or transport. The discussion in the communities related to the management domain is just beginning.
The operators should be able to provide guaranteed SLA based on the customers’ requirements in the E2E manner.
High level Goal
Standardization of E2E Network Slicing which can provide guaranteed services* from end to end perspective
*defined in GSMA PRD NG.116 Generic Slice Template Attributes
Objective
Maximize value of network slicing to attract enterprise customers
Enable multi-vendor environment<br>
08
End to End Architecture 8 Slice #1
(S-NSSAI#1) Data NW
1 RAN Data NW
2 RAN Slice #2
(S-NSSAI#2) NEF API for #2 API for #1 IP Core Network Access Network RAN MS Access NW
MS IP Core/SDN
MS RAN Mobile Core
MS Application
Server on #2 Application
Server on #1 E2E
Management System UPF NRF AMF PCF NRF AMF SMF PCF UPF SMF C/U-Plane for #2 C/U-Plane for #1 O&M Mobile Core RAN Transport Provided by KDDI Device<br>
09
9 Oct Oct Feb June Feb June 2019 2020 NEST WP1 Work Feb 2021 Apr Completion
SDOs
Specifications
(e.g. 3GPP Rel.17) Kickoff Gap Analysis
Requirements and LS (if needed) Timeline of WP1 work<br>
10
Current status : Device 10 Specifications ever specified
Chipset/Terminal awareness of NW slice
Application-specific allocation of NW slice using UE Route Selection Policy (URSP)
KDDI’s observation: No awareness of NW slice from app…
Expected approach
Step 1: Identify requirements at TSG
Step 2: Solution mapping at TSG
Step 3: Discussion with OS vendors
Discussions so far in NEST WP1
Not yet identified any gaps related to devices
No device experts attend to call/E-mail discussion actively No awareness of NW slice
from the application point of view<br>
11
Discussion<br>
12
12 Is there a roadmap for NW slicing support in devices?
Is there a support for simultaneous use of multiple NW slices?
Has any analysis been done in TSG?
Can the results be shared with NEST-WP1?
NEST-WP1 and TSG/subgroups cooperation Discussion<br>
13
Any question? Thank you Yusuke Nakano: you-nakano@kddi.com
Sandra Ondrusova: sandra.ondrusova@hwleurope.com<br>
