1 / 13

E2E NW Slicing Architecture Yusuke Nakano , KDDI TSG37_005

E2E NW Slicing Architecture Yusuke Nakano , KDDI TSG37_005. TSG 11.09.2019 Bangkok. Agenda. Introduction Future Network NEST NEST – WP1 Next Steps. Introduction. Part of Future Network Programmes Started in 2017, still growing with 40 member companies

balvin
Download Presentation

E2E NW Slicing Architecture Yusuke Nakano , KDDI TSG37_005

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. E2E NW Slicing ArchitectureYusuke Nakano, KDDITSG37_005 TSG 11.09.2019 Bangkok

  2. Agenda Introduction Future Network NEST NEST – WP1 Next Steps

  3. Introduction • 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)

  4. Network Slicing Taskforce (NEST) Structure WAS/WSOLU NG/5GJA FASG/5GSTF NEST – plenary (CK Hutchison) TSG WP6: PoC (GSMA) WP4: Roaming (Deutsche Telekom) WP5: External interactions (GSMA) WP3: Isolation (CMCC) WP2: Business aspects (Verizon) WP1: E2E architecture (KDDI) 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

  5. NEST WP overview WP2: Business aspects • 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 WP3: Isolation • 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 WP4: Roaming WP5: External interactions • 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 WP6: PoC

  6. WP1:E2E architecture

  7. Introduction 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 guaranteedservices* 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

  8. End to End Architecture E2E Management System O&M Mobile Core Access NW MS RAN MS IP Core/SDN MS Mobile Core MS NEF SMF APIfor #2 RAN NRF PCF AMF Data NW 2 RAN Slice #2 (S-NSSAI#2) RAN UPF Application Server on #2 C/U-Planefor #2 APIfor #1 NRF SMF PCF Device AMF Data NW 1 RAN Slice #1 (S-NSSAI#1) UPF C/U-Planefor #1 Application Server on #1 Transport Provided by KDDI Access Network IP Core Network

  9. Timeline of WP1 work 2019 2020 2021 Feb Oct Feb Apr Feb June Oct June NEST WP1 Work Completion SDOs Specifications (e.g. 3GPP Rel.17) • Gap Analysis • Requirements and LS (if needed) Kickoff

  10. Current status : Device • 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 UE Apps Apps Apps OS URSP Chip No awareness of NW slice from the application point of view

  11. Discussion

  12. Discussion • 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

  13. Any question? Thank you Yusuke Nakano: you-nakano@kddi.com Sandra Ondrusova: sandra.ondrusova@hwleurope.com

More Related