Ravi Ravindran, Prakash Suthar, G.Q.Wang, Dirk Trossen

Transcription

1 Enabling ICN in 3GPP s 5GC Architecture (draft draft-ravi ravi-icnrg icnrg-5gc 5gc-icn icn-01) Ravi Ravindran, Prakash Suthar, G.Q.Wang, Dirk Trossen Ravi.Ravindran@Huawei.com psuthar@cisco.com Dirk.trossen@interdigital.com IETF/ICNRG, March, 2018, London

2 Draft Outline

3 Draft Updates New co-author Dirk Trossen Update to the 5G/ICN architecture We call ICN-AP as ICN-GW to avoid misinterpretation as anchor point function in current 5GC network. Discussion on various considerations related to leveraging non- PDU provision for ICN in 5G Discussion on -o-icn realizations over 5GC Use Case Scenario Smart Mobility using -o-icn Multiuser VR Use Case

4 Draft Objectives Motivate the benefits of enabling ICN in 5G ICN enabled session-less transport, edge Computing, Storage/Caching, Seamless Mobility to handle several high bandwidth and low latency applications (embb, MMTC and URLLC) Propose architectural control and user functions to enable ICN in 5GC taking advantage of flexibility of the design considering network slicing, NFV/SDN principles Using the non- PDU for native deployment of ICN in 5G Use case Scenarios Smart Mobility Multi-viewer VR Seamless Mobility

5 Enabling ICN in 5GC ICN Service Orchestrator NSSF: Network Slice and Selection Function PCF : Policy Control Function UDM: Unified Data Management AMF : Authentication and Management Function SMF : Session and Management Function ICN-DN : ICN Data Network ICN-AF : ICN Application Function ICN-GW : ICN Gateway UL-CL : Uplink Classifier UPF : User Plane Function RAN : Radio Access Network ICN-UE 5G[[ICN]] N1++ 5G[non-[ICN]] RAN NSSF N2 AMF++ UPF ICN-GW PCF/U DM N11++ N4++ Npcf++/Nudm++ SMF++ N4 Naf++ N4 ICN-AF ICN-SMF [ICN] N3 UL-CL (Uplink Classifier/Branchin N9 g Point) N9 Classification Rule: { Flow ICN Slice N9} NIcn ICN-GW + UPF Local ICN-DN ICN Service/Network Controller [ICN] or Eth[ICN] N6 ICN-DN (ICN Naming, Security, Mobility, Trust) ICN can be transported over or as non- PDUs towards ICN-DN ICN-SMF handles session management of ICN-AP NF. AMF++/SMF++ enforce functions to allow UE subscription authentication to ICN DN, and provision rules in RAN, UL-CL and other intermediate UPFs to enable UE-ICN to anchor to ICN-AP. ICN-AF can push ICN PDU session requirements to PCF/UDM for slice selection or session management functions between the RAN and the ICN-AP

6 Non- PDU Provision Considerations In this mode, the ICN-UE will operate without any configuration For maximum efficiency, the ICN-GW can be realized in the RAN. Caching and Mobility can enabled in the RAN Following are considerations to allow ICN as one of the non- PDU types which 5G can support. Attach Procedures/Control Plane for UE with non- PDN Extended Mechanisms required to authenticate/authorize ICN UEs at device or service level This can be extended to authorize service access, as ICN is about networking services. Mechanisms described in TS using existing AUSF/UDM/PCF functions can be potentially extended towards this. Can be extended to include ICN specific authentication function (ICN-AF) AMF++/SMF++ and ICN-SMF functions to support non- PDU management Current LTE identifies the connectivity type using PCO-IE, i.e. versus non- PDU, could be used for control plane session management User Plane for UE with non- PDN Requires mechanism to identify ICN PDUs for policing, charging or legal interception A flat ICN realization requires a distributed mechanism to handle these functions ICN by design doesn t include consumer identity, lower layer identities (e.g. PDCP/MAC) can be used towards this. Further Slice-ID (from NSSAI) could be used in the UPF to map ICN flows to appropriate ICN slice

7 Non- PDU Provision Considerations Mobility Handling Involving networking between the RAN and the UPF is inefficient Efficient handling by collocating ICN-GW with RAN Requires integration with 5G and ICN CP/UP functions Routing Considerations 5GC follows LTE s centralized session management and routing approach using the SMF Scalability challenges in a flat ICN realization where multi-source and multipath routing can be taken advantage of Explore feasibility of distributed routing approaches within the 5GC framework Mobile Edge Computing ICN level service orchestration to exploit services deployed in network [1] or using innetwork approach like NFN. Routing challenge, to direct ICN service flows to closest service or in-network compute instance [1] Ravindran, R., Liu, X., Chakraborti, A., Zhang, X., and G.Wang, "Towards software defined ICN based edge-cloud services", IEEE, CloudNet, 2013.

8 Realization of -over over-icn Architectures: Example of IDCC s Flexible Services (FLS) -only Server PCE: path computation element SR : service router SDN technology IDCC overicn FLS SR ICN F SDN Switch S 1 Surrogate Mgr S 2 ICN F ICN SP PCE L2 SDN Switch S 1 Monitoring ICN F L2 FLS Border GW (BGP) NAP technology ICN F ICN PP SDN Controller -only Sender & Receiver UE FLS SR [1] Trossen, D., Reed, M., Riihijarvi, J., Georgiades, M., and G. Xylomenos, " Over ICN -The Better?", EuCNC, European Conference on Networks and Communications, July, only Sender & Receiver UE

9 Realizing -o-icn ICN in 5GC UDM/PCF ICN-AF ICN Service Controller APP 5G-NR N1 AMF++ SMF++ ICN-SMF N4++ N4 N4 Nicn N2++ TM SDN Controller RVZ Monitoring RAN FLS SR UPF N3 UPF (UL-CL) N9 Flips SR+ UPF SDN Sw. SDN Sw. SDN Sw. Surrogate Mgr. Interne t SDN technology IDCC overicn TM : topology manager RVZ: rendezvous point NAP: Network attachment point The proposed 5GC extensions shall allow realization of ICN architectures such as PURSUIT over 5GC -o-icn adaptation user plane functions (FLS-NAP) can be realized in the RAN or as DN service.

10 Native -over over-icn: A Terminal Version Implementing SR functionality Dual-stack or pure ICN stack UE ICN SDN technology F 5G AN ICN F SDN Switch Surrogate Mgr ICN F SDN ICN F (BGP) Switch ICN SP PCE L2 S 1 Monitoring L2 FLS Border GW NAP IDCC overicn ICN S 1 S 2 technology F SDN Controller ICN ICN PP F Dual-stack or pure ICN stack UE 5G AN Dual-stack UEs implement the original SR functionality as part of the convergence layer -only Server

11 Native -o-icn ICN in 5GC UDM/PCF ICN-AF ICN Service Controller N1 AMF++ SMF++ ICN-SMF N4++ N2++ Nicn SDN Controller TM RVZ Monitoring Dual-stack or pure ICN stack UE RAN UPF SDN Sw. N9 Local ICN-DN SDN Sw. SDN Sw. SDN Sw. Surrogate Mgr. Interne t In this realization, ICN frames are handled as non- PDUs, which are then networked to the edge ICN-local DN instance The SDN switch in the RAN can be another forwarding function to enable this ICN architecture.

12 Smart Mobility using -o-icn ICN Discussion of this scenario over -o-icn architecture Assumes operation of -based MEC application over an ICN bearer ICN based methods used for Service Registration ensuring service requests reach the closest service instance Path Updates at the CNS end point used for mobility With -o-icn, the TM-E instance can return a single L2 level multicast to reach multiple CNS at the same time ICN based registration also allows secure content delegation to in-network caching points, with HTTP requests being directed to the secure content edge server, avoiding any triangular routing issues.

13 Multi-user VR use case Scenario: multi-user virtual reality content delivery Spatial and temporal correlation, e.g., joint event delivery such as for sports or education content around (e.g., historical) storyline Observation: overlap in retrieval pattern from various VR users Temporal correlation makes this obvious Spatial correlation results in segments being pulled quasi-synchronously, too Window of opportunity to deliver VR content to more than one user Window might be small due to required low latency but still exists Multicast relations vary per request (due to likely slight differences in retrieval patterns from previous request) Purely realized via L2 path-based forwarding This can also realized within 5GC setting through a ICN-MEC framework to serve locations as in stadiums, educational or tourism purposes, utilizing native ICN applications deployed on UEs InterDigital, Inc. All Rights Reserved.

14 Next Steps The draft explores the opportunities to leverage the flexibility of 5GC architecture to enable ICN to meet serveral 5G application requirements difficult in current setup. 5G commercial deployment still 4-5yrs out. Could influence Rel-16 and beyond. Potential Next Steps for this draft. ICN Multicasting over Radio Access (interim presentation) [1] Details on 5G/ICN functional support (non- PDU provision) Separate discussions for ICN Applications (IoT versus Smart devices) Mobility handling over ICN in 5GC Managing QoS for heterogeneous applications Distributed policy/charging mechanisms Would like to see the interest in the group to take it up as a RG item [1] Enabling Receiver oriented ICN multicast in Cellular Radio Access, icnrg-01-sessa-enabling-cross-layer-receiver-oriented-dynamic-multicast-in-cellular-access-ravi-ravindran/