CONFIG Control Plane Architecture for 5G Systems Riccardo Trivisonno, Huawei Technologies

Transcription

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 6 th and 7 th, 2017

2 Presentation Outline Project Objectives Project Achievements and Relationship to Network Slicing Open Issues and Next Steps Slide 2 CONFIG

3 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) Slicing Concept Looming Slide 3 CONFIG

4 Project Objectives: Architecture Modularisation Zooming-in the Control Plane Modularisation as design principle, allowing flexibility and Verticals integration Key Network Slicing enabler Slide 4 CONFIG

5 Presentation Outline Project Objectives Project Achievements and Relationship to Network Slicing Open Issues and Next Steps Slide 5 CONFIG

6 Project Achievements: 5G Modularised Architecture, Supporting Network Slicing Network Functions and Interfaces Context Awareness Framework Slide 6 CONFIG

7 Relationship to Network Slicing Definitions and Lifetime Consolidated Definitions, NGMN, Jan 16 Control/User Plane Logical Architecture Infrastructure Management 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 Slide 7 CONFIG

8 Relationship to Network Slicing: Example: miot Network Slice C-plane Architecture C-plane Procedures PhD1 ViD 1 PhD2 AN CM/FM SAM DPG PhD1 ViD 1 PhD2 AN CM/FM SAM DPG 1. Connection Request 2. Connection Ack 3. Connection Complete 4. Connectivity Request Fwd 5. Credential Verification 6. Credential Verification OK 7. VD ADD allocation 8. VD ADD to Ext Add Translation Rule 9. Aggregate CN Bearer Establishment 10. Connectivity Request Ack 11. Connection Reconfiguration 12. Connection Reconfiguration Ack 1. Connection Request 2. Connection Ack 3. Connection Complete 9. Connection Reconfiguration 4. Connectivity Request Fwd 5. Credential Verification 6. Credential Verification OK 7. ViD Add association 8. Connectivity Request Ack 10. Connection Reconfiguration Ack PhD1 ViD 1 PhD2 AN CM/FM SAM DPG PhD1 ViD 1 PhD2 AN CM/FM SAM DPG 1. Data Received 3. Data Ready 4. Ready to Receive 2. Data Packet Fwd 1. Data To Send 2. UL Data Token Grant 3. Data Packet 5. Data Transmission 4. Data Packet Fwd Slide 8 CONFIG

9 Relationship to Network Slicing: Standardisation (3GPP SA2 Perspective) A Network Slice is a complete logical network made up of Access and Core Network Components UE 1 UE 1 NSS AI NG1 RAN CCNF AMF RA N NG2 RAN SLICE Common NFs {CCNF) NG smf NG3 NSI SM F UP UP F NG4 NF1 NF1 NF1 UP NF1 UP UP NF1 NF1 NG6 DN NFn NFn NFn UP NFn UP NFn UP NFn 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 9 Slide 9 CONFIG

10 Relationship to Network Slicing: Standardisation (3GPP SA2 Perspective) Network Slicing was NOT the focus of SA2 118 bis Network Slicing embedded in other procedures UE 1 NF_A instance NG 1 CCNF AMF NSSF 4. NF Access NF Repository Function Determine to access the function of NF_B 1. NF Discovery Request (Function type of NF_B, service related parameters) 3. NF Discovery Response 2. Check whether the request is allowed NF_B instance 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 Slicerelated 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 Slide 10 CONFIG

11 Thank You! Riccardo Trivisonno, PhD