CONFIG Control Plane Architecture for 5G Systems Riccardo - - PowerPoint PPT Presentation

config
SMART_READER_LITE
LIVE PREVIEW

CONFIG Control Plane Architecture for 5G Systems Riccardo - - PowerPoint PPT Presentation

CONFIG Control Plane Architecture for 5G Systems Riccardo Trivisonno, Huawei Technologies 5G-PPP WS, Network Slicing and C-Plane Architecture and SDN for 5G Athens, February 6 th and 7 th , 2017 Presentation Outline Project Objectives


slide-1
SLIDE 1

CONFIG

Control Plane Architecture for 5G Systems

Riccardo Trivisonno, Huawei Technologies

5G-PPP WS, Network Slicing and C-Plane Architecture and SDN for 5G Athens, February 6th and 7th, 2017

slide-2
SLIDE 2

Slide 2 – CONFIG

Presentation Outline

  • Project Objectives
  • Project Achievements and Relationship to Network Slicing
  • Open Issues and Next Steps
slide-3
SLIDE 3

Slide 3 – CONFIG

Slicing Concept Looming

Project Objectives

To build 5G on top of the key High Level Requirements at the time the project proposal was written (‘14) , CONFIG identified 4 key objectives:

Develop a 5G modular functional framework

(Architecture Flexibility / Vertical Integration)

Conceive an access-agnostic 5G Core Network

(Heterogeneous Access Integration)

Develop a Context Information framework

(Providing Smart/Tailored Connectivity)

Lead standardisation future paths, impacting on 3GPP, IETF, ONF

(Impact on Real Systems)

slide-4
SLIDE 4

Slide 4 – CONFIG

Key Network Slicing enabler

Project Objectives: Architecture Modularisation

Zooming-in the Control Plane Modularisation as design principle, allowing flexibility and Verticals integration

slide-5
SLIDE 5

Slide 5 – CONFIG

Presentation Outline

  • Project Objectives
  • Project Achievements and Relationship to Network Slicing
  • Open Issues and Next Steps
slide-6
SLIDE 6

Slide 6 – CONFIG

Project Achievements: 5G Modularised Architecture, Supporting Network Slicing

Network Functions and Interfaces Context Awareness Framework

slide-7
SLIDE 7

Slide 7 – CONFIG

Logical Architecture Management Control/User Plane Infrastructure

Consolidated Definitions, NGMN, Jan’16

 Network Slice Blueprint: A complete description of the structure, configuration and the plans/work flows for how to

instantiate and control the Network Slice Instance during its life cycle

 Network Slice Instance: a set of network functions, and resources to run these, forming a complete instantiated logical

network to meet certain network characteristics required by the Service Instance(s)

CONFIG Definition and Scope of Network Slicing:

 A network slice is an independent logical network, defined by the interconnection of a set of basic building blocks,

composing both C-plane and D-plane, and which can be independently instantiated and operated over a set of physical infrastructure, to support the communication service requirements of a particular or multiple use cases.

 End to End: a network slice spanning all the components of the communication system needed to provide devices with

the requested communication service

Relationship to Network Slicing Definitions and Lifetime

slide-8
SLIDE 8

Slide 8 – CONFIG

Relationship to Network Slicing: Example: mIoT Network Slice

PhD1 PhD2 AN CM/FM SAM DPG

ViD 1

  • 7. VD ADD

allocation

  • 1. Connection Request
  • 2. Connection Ack
  • 3. Connection Complete
  • 4. Connectivity Request Fwd
  • 5. Credential Verification
  • 6. Credential Verification OK
  • 9. Aggregate CN Bearer Establishment
  • 10. Connectivity Request Ack
  • 11. Connection Reconfiguration
  • 12. Connection Reconfiguration Ack
  • 8. VD ADD to Ext Add Translation Rule
PhD1 PhD2 AN CM/FM SAM DPG

ViD 1

  • 7. ViD Add

association

  • 1. Connection Request
  • 2. Connection Ack
  • 3. Connection Complete
  • 4. Connectivity Request Fwd
  • 5. Credential Verification
  • 6. Credential Verification OK
  • 8. Connectivity Request Ack
  • 9. Connection Reconfiguration
  • 10. Connection Reconfiguration Ack
PhD1 PhD2 AN CM/FM SAM DPG

ViD 1

  • 1. Data To Send
  • 2. UL Data Token Grant
  • 3. Data Packet
  • 4. Data Packet Fwd
PhD1 PhD2 AN CM/FM SAM DPG

ViD 1

  • 1. Data Received
  • 3. Data Ready
  • 2. Data Packet Fwd
  • 4. Ready to Receive
  • 5. Data Transmission

C-plane Architecture C-plane Procedures

slide-9
SLIDE 9

Slide 9 – CONFIG

Relationship to Network Slicing: Standardisation (3GPP SA2 Perspective)

9

A Network Slice is a complete logical network made up of Access and Core Network Components

Common CP NFs {CCNF)

CP NFn CP NF1

UP NFn UP NF1 UE 1 RAN

CP NFn CP NF1

UP NFn UP NF1

CP NFn CP NF1

UP NFn UP NF1

NSS AI

CP AMF

CP SM F UP UP F NG4 NGsmf NG3

RA N

UE 1 NG2 NG1 CCNF NSI DN NG6 RAN SLICE

  • Slices are selected based on NSSAI provided by the

UE

  • RAN selects a CCNF (AMF/NSSF) based on the

NSSAI

  • An NSSAI can generate multiple Network Slices
  • An AN can be common to all slices
  • The NSSAI includes at least: SST and SD
  • CCNF Redirection can be done at RAN or CCNF
  • SMF Selection is based on:
  • NSSAI (Provided by the UE), UE Subscription

Info, DNN and Local Operator policies

  • SM-NSSAI can be associated to an application
  • Data is routed to the PDU sessions associated to

the SM-NSSAI

slide-10
SLIDE 10

Slide 10 – CONFIG

Relationship to Network Slicing: Standardisation (3GPP SA2 Perspective)

Network Slicing was NOT the focus of SA2 118 bis … Network Slicing embedded in other procedures

  • It is not decided whether NSSF is a separate function or a

component within AMF

  • Slicing is not a mandatory feature, but AMF is always

required

  • NSSF can be accessed even before an AMF has been

selected

  • It is not decided whether Network Slicing should be

addressed as a separate feature or part of existing procedures

  • Should NS have its own clause within the TS?
  • To be determined during normative phase what Slice-

related info is to be used for NF selection

  • E.g., Is the NSSAI used as an input to NF selection?
  • It is not clear how Network Slicing is handled in a Roaming

scenario

CP AMF UE 1 NG 1

CCNF

CP NSSF

  • 4. NF Access

NF_A instance NF Repository Function

Determine to access the function of NF_B

  • 1. NF Discovery Request (Function type of NF_B,

service related parameters)

  • 2. Check whether the

request is allowed

  • 3. NF Discovery Response

NF_B instance

slide-11
SLIDE 11

Thank You!

Riccardo Trivisonno, PhD riccardo.trivisonno@huawei.com