5g移動(dòng)通信-無線架構(gòu)-rapp-code-ran-architecture

1、5G for people and things,Key to the programmable world,,HOME,,i,5G RAN ArchitectureOverview,February 25th, 2016,Main drivers and use casesKey conceptsOverall architectureUser- and control-plane architectureLTE-5

2、G and multi-RAT integrationMulti-connectivity optionsMobility concepts,Outline,Main drivers and use cases,,5G for people and things – diversity of use cases and requirements,,,,ExtremeMobile Broadband,Critical mach

3、ine type communication,Massive machine type communication,Some push for centralization, other for distribution,Diversity of Requirements,,Front and backhaul requirements,how separate entities need to collaborate (eCoMP,

4、dual connectivity, etc.),Coordination among small cells and with macro,Shorter TTI and Shorter TTI and functionalities “in the box” grow beyond basic eNB functionality (e.g. core functions, …),,,,,distribution,distribut

5、ion,centralization,centralization,,,,,,,,,,,Mobile Network Topology,Larger European operator,macro,macro,pre-aggregation,small cells,small cells,macro,x10.000 macro sites,x100.000 small cells,x1.000 pre-aggregation s

6、ites,central gateways,CN functions,x100 aggregation sites,x10 central gateways,aggregationsite,Internet,Operator services,edge cloud,edge cloud,star,chain,tree,Internet,ring,,= potential site for data center/agg

7、regation/local breakout point,RRHs,?Diverse x-haul, network topologies, aggregation scenarios,macro,,Distance and latency to radio access increases,Local breakoutand functions,,5G,,,,,,,Core network,LTE,5G,LTE,5G,,LTE,5

8、G,5G anchored in LTE(LTE-5G Dual Connectivity),5G and LTE stand-alone,LTE anchored in 5G(5G-LTE Multi-Connectivity),5G,,,5G with multi-hopself-backhaul,5G,,RAN cloud,virtualized hardware,,5G with D2D and local switch

9、ing,5G,,MEC,Local GW,RAN functions,LTE air interface,5G air interface,Fronthaul interface,RAN-CN interface,Self-backhaul interface,RAN interface,Device to device,Sensor/IoT device,Overall view,Key concepts and objectives

10、,,5G Radio Architecture and network design principles,Flexibility and scalability of functions: C/U Plane, Cell/UE relatedLoad-adaptive scaling,Centralized architecture allows better view to take better decision (e.g. c

11、entral scheduler, traffic steering),diverse deployment scenarios depending on available xhaul,Optimization of control plane and user plane entities,,Elasticity,Any xhaul,Integrated Control,Multi connectivity,Lean functio

12、nal architecture,,,UE,,,,,,,,,,,,cmW,mmW,,,Objectives,,Top-4 Objectives 5G Common ArchitectureDesign cmW, mmW, WA common higher layer architecture and protocol stacks. Considering multi-layer and IRAT: 5G, LTE, W

13、iFi, LAAMulti-connectivity by designRAN architectural options for spotty 5G coverage and multi-connectivity use cases. Support for central and distributed functions. Support for high throughput and robustness use c

14、ases.Native Cloud RANDesign interfaces and protocol stack to allow flexible functional split acc. to Fronthaul and data center capabilities. Support Cloud implementation, scaling, and dynamic resource allocation. Cl

15、oud-friendly protocol design.Network flexibilitySupport network slicing, and functional allocation acc. to end-to-end services. Consider SDN approaches by design with c-plane and u-plane separation and acc. interfa

16、ces,Scenarios5G only: WA, cmW, mmWInter-RAT: 5G + LTE + WiFi + LAAany xhaul Deployment studies,SpectrumFocus is both licensed (and non-shared) and non licensed (WiFi) spectrum cases.,Key concept: Network Converg

17、ence Sublayer,Single layer for all RATs and Multi-Connectivity,NCS,IP,Ethernet,New services,LTE,5GWA, cmW, mmW,WiFi,LAA,,Tight integrationand control,,Support for all services and use cases,Key concept: Flexible Fronth

18、aul Split,From ideal to non-ideal Fronthaul,,,C-RAN(BB-pooling),Distributed(LTE),Executed at BS,Centrally executed,Centrally executed,Executed at RRH,Centralized NCS,Centrlized L1H,Flexible Functional Split,Ideal Fr

19、onthaul,Non-ideal Fronthaul,,,,,Key concept: Topological Flexibility,Adapt to operator infrastructure and network topology,,,,3.) Centralized Scenario,C/U-plane aggregation in the same site (LTE Dual Connectivity baseli

20、ne)Issues: U-Plane capacity (processing and fronthaul/backhaul) in macro eNodeB,small cells,macro,,,,2.) Dedicated aggregation for small cells,,,,1.) Macro-cell as aggregation point,macro,,U-plane aggregation nodes for

21、 reduced x-haul requirements distributed processing load,Cloud-RAN scenario with centralized U-plane and C-plane,,macro,small cells,5G, WiFi, LAA,WiFi,Overall architecture concept,,,,Core network,1. Integrated base sta

22、tion,,5G-nrtL2,5G-rtL2,5G-L1,5G-CP,,5G-nrtL2,5G-CP,5G-RF,5G-rtL2,5G-L1,5G-nrtL2,,2. C-RAN,,3. Flexible Fronthaul Split,,4. Distributed C/U-Plane,BTS,BTS,RRH,RRH,Base Band,DU,DU,CU,CU (UP),CU (CP),DU,RRH,BTS,Flexible,U-Pl

23、ane,C-Plane,Flexible RAN Architecture,MSM: Mobility and Session Management Entity uGW: User-plane GateWay 5G-NB: 5G-NodeB, radio, 5G-Uu terminationX2*:Interface between 5G-NodeBsS1*-U: Interface for user-plane da

24、ta towards uGWS1*-C: Enhanced control-plane interfaceFor a detailed functional split description see [1] and [2],Basic RAN architecture,Functional split,,Basic architecture,,Logical architecture with Fronthaul Split,

25、Distributed 5G-NB configuration,Fronthaul Interface is transparent to NW and UE:MNC is visible as 5G-NB from NW perspectiveMNC manages and controls 5G-RAPsS1 and X2 interfaces are per MNC, not per 5G-RAPs5G-RAPs c

26、an be macro, small cell, pico cell, mmW, …NCS in MNC is responsible for multi-connectivity features: aggregation, steering, robustness,Support for Fronthaul Split and non-co-located User-plane offload,Logical architect

27、ure,Sidehaul Interface is transparent to network and UESi needs to support for U-Plane configuration and dataThere is a logical 1:many relation between MNC-C and MNC-U5G-RAP may have interfaces to MNC-C and to one or

28、 more MNC-UMNC-U terminates S1*-U and X2*-U interfaces towards uGW, 5G-NBNCS in MNC-U supports split SF to different radio legssplit SF over Si interfacesplit SF to radio leg of associated MNC-U,,Co-located or non

29、-co-located,,Evolved Core Cloud,5G-NB,Dedicated node for U-Plane functions,For scaling, offload support,MSM,uGW,S1*-C,5G-RAP,PHY,MAC,RCS,LegacyLTE eNB,C-plane,U-plane,S1*-U,Si,Fs-C,Fs-U,UE,Uu*,Uu,MNC-U,NCS,X2-AP,X2-U,MN

30、C,RRC,NCS,,,WLAN AP,TWAG,WLAN AC,Support for Cloud RAN,,,One-tier vs. two-tier Cloud-RAN Scenarios,,,,,,,,,Radio units,Centralized/virtualizedhardware,Upper protocol stack,NW interfaces (S1/X2),,,,,,,,,Remote Radio Head

31、s,Centralized/virtualizedhardware,L2+ - L3,NW interfaces (S1/X2),L1-L2,,Fronthaul,,Midhaul,Core Network,Backhaul,Core Network,Backhaul,,Fronthaul,One tier,Two tier,L1-L2,L1-L2,RRH,Interface options for Fronthaul Split,,

32、5G should be deployable supporting different infrastructure characteristics.Optimal functional split may depend on the available Fronthaul characteristics for latency and capacity.5G radio specifications should consi

33、der functional split and not limit deployments.,5G Logical Architectural Framework for Fronthaul,Split to Higher Layer and Lower Layer,,,,,RF+BB1,BB2,BB3,5G-NB,Fs-U-L,Fs-U-H,Fs-C-L,Fs-C-H,Fs-OM-L,Fs-OM-H,S1, X2 …,5G-Uu,H

34、igher Layer Split,Lower Layer Split,,Support for flexible functional split,Flexibility for Fronthaul and Service Requirements,,T1 aggregation,T2 aggregation,,Core network,,MNC,Ideal FH,RCS,MAC,L1H,NCS,RRC,uGW/MSM,Local u

35、GW,,MNC,NCS,RRC,Non-ideal FH,X2*,S1*,Fs-H,S1*,,Distance and latency to radio access increases,Low latency services,L1L,L1L,RCS,MAC,L1,RCS,MAC,L1,Fs-L,Multi-Service Support,Multi-service Multi-Connectivity support,Scenari

36、o: Inter-5G-NB with Fronthaul Split,Split bearer at secondary node,May be located in RAN cloud,MNC can act as master and secondary node from UE perspectiveNCS in MNC responsible for: aggregation, steering, robustness

37、,Multi-connectivity features:NCS can route to 5G-RAPs over Fs and other 5G-NBs over X2RRC-M can be dislocated from NCS user plane anchor,Locally Switched Any-to-Any Connectivity Services below the uGW,5G-NB Modeled w

38、ith integrated Packet Data Switch,A group of UEs connected to a locally switched service instance e.g. VLAN,Note! Only User PlaneConnectivity is shown,Hosts in a Locally Switched Service assign their IP Addresses from t

39、he uGW (Default Router),Local Switching is executed in the 5G-NB integrated Packet Data Switch functions,Protocol Architecture,Key concept: Unified protocol stack for 5G air interface,PHYMacro optimized (below 6 GHz),P

40、HYEnhanced SC (cmW),PHYUltra Broadband(mmW),Lower MAC/RRM,Lower MAC/RRM,Lower MAC/RRM,5G Convergence Layer – Common Functionalities(NCS and RRC),Unified Upper Layers – Independent of 5G radio interfaces,,Parameteriz

41、ation, configuration, and implementation optimized for specific radio interfaces,Unified upper protocol stack for all radio interfaces,,RCS,RCS,RCS,IP,Ethernet,Any protocol,Single common protocol for all radios: NCS (Net

42、work convergence sublayer)Flexible location, depending on deployment and requirementsMulti-connectivity traffic handling for U-Plane and C-Plane: routing, splitting, duplicationCommon RRC for centralized control of m

43、ulti-connectivity functionsReduce signaling and coordination complexityFlexibility for different multi-connectivity scenariosNCS as transport layer for signaling service flowsRadio Convergence Sublayer (RCS) and Uni

44、fied MAC Parameterizeable for 5G use cases and requirements basedOptimized for parallel processing in CloudApplication control scheduling for QoE management and enforcement,Main Principles,NCS Key Functionality and A

45、rchitecture Characteristics,Participate in leg addition/deletionPartition traffic across multi-connectivity legs,Multi-connectivity anchor,On-the-fly, identify sub-flows within SFAt receiver, re-ordering per-sub-flow,I

46、n-Service-Flow Differentiation,Allows granular handling of UE traffic and multi-connectivity per-SF – e.g. different locations for high- and low-latency SFs,Allow Multiple NCS instances per UE – one per Service Flow,NCS

47、 location in network can be based on QoS, network topology, multi-connectivity state, processing loadNetwork-topology awareness using e.g. SDN,Flexible selection of NCS placement,Flexible adaptation to change in flow ch

48、aracteristics, multi-connectivity, processing overload,NCS can be relocated,Awareness of state of lower-layer buffers, path and queueing delays, etc. on each multi-connectivity leg,On DL, Flow Control aids partitioning o

49、f traffic,Multi-connectivity,QoS,Topological flexibility,PHY,MAC,RCS,NCS,Service flow,NCS-FCP,5G-UE: 5G User Equipment5G-NB: 5G NodeB,Protocol stack,,,,User plane,Control plane,,NCS: Network Convergence SublayerRCS: Ra

50、dio Control Sublayer,NCS: Network Convergence SublayerRCS: Radio Control Sublayer5G-UE: 5G User Equipment5G-NB: 5G NodeBNCS-FCP: NCS Flow Protocol (interface AP),Protocol stack,With support for Multi-Connectivity,,,U

51、ser plane,Control plane,MSM: Mobility and Session Management EntityuGW: User-plane GateWayNCS-SRF: NCS instantiated for an SRF,,,User plane protocol architecture,NCS: Common convergence layer for UP, CP, traffic; Split

52、ting, selection, duplication of packets; selection of radio legs; within the network, may not be co-located with RCS.Radio Flow: RFL is the service provided by the Layer 2 for transfer of data between User Equipment an

53、d 5G-RAN.Radio Sub Flow: The service provided by NCS layer for transfer of data between UE and 5G-RAN mapped to a specific QoS Queue.RCS: Buffering, Segmentation, ARQ, re-orderingMAC: Multiplexing to transport chan

54、nels, radio/QoS scheduling,,QoS Architecture,Service flow (SF) provides end to end connectivity between the UE and the Service edge S1* connection delivers service flow packets between the RAN and the uGWRadio Flow and

55、 Radio Sub-Flows (RSFL) transport SF packets between the 5G-NB and the UE. The data packets of the SF can be mapped to multiple RSFLs, each representing a radio level QoS class. A radio link transports RSFL packets betw

56、een the UE and the AP. There is one to one relationship between the RSFL and the radio link in single connectivity case.In the case of multi-connectivity, RSF can be mapped to multiple radio links each belonging to di

57、fferent radio.,QoS Architecture,,Confidential,AS classifies application flows into sub-service flows (SSFs) and performs schedulingThe AS informs the 5G-NB about the specific service attributes and the identification of

58、 SSFs. Based on the received SSF level information, 5G-NB configures its radio stack The RFL split function of the AP maps data packets to RSFL based on the SSF information.,Application scheduler (AS),,Confidential,QoE

59、 Management and control close to RAN or in CN,Basic principles:One NCS entity serves one Service Flow (radio flow)One RCS entity serves one NCS entityMultiple RCS entities can serve the same NCS entityConfiguration,

60、 setup and operation:During setup, at least one RCS entity is configured for the setup NCS entity with default configuration and QoS.The setup and termination of radio (sub-)flows is performed by RRC.NCS can route pa

61、ckets to multiple RCS entities in different radio legs belonging to the same Radio Service.Radio scheduler/MAC has no visibility to application flows or a radio services but sees the RCS entities/buffers,Mapping from N

62、CS to RCS and QoS queues,Example of with two radio legs (multi-connectivity) and two service flows,,Control Plane - RRC,Control-Plane principles,,,RRC,NCS,,X2*,,To Core (S1*-C),,5G-UE,,RCS,MAC,PHY,RRC,,RCS,MAC,PHY,RRC,,,

63、,5G-uU,cmWave radio leg,Wide area radio leg,mmWave radio leg,X2* or Fs,RRC-Master RRC-S coordination UE state management,Local RRC (transparent) implements configuration by RRC masterNot visible by UE,NCS Routing of

64、RRC and user-plane messages Selection of radio legs, implementation of reliability schemes,Logical view:One RRC entity in UE communicates with RRC-M over different radio legs,Transport view:NCS performs message routin

65、g for RRC from and to different radio legs,Key concept: Separation of logical from transport plane for control messages,RRC in UE Single RRC entity for all radio legs Single state machine,RCS,MAC,PHY,RRC,,,,,Signallin

66、g radio flow (SRF),Baseline: Multi-connectivity with signalling reliability,Single RRC,,Motivation:- Multi-connectivity control based on Dual Connectivity principles- Support for signalling robustness by using multi-

67、connectivityPrinciples:-M5G-NB hosts RRC-Master and is the mobility anchor.One or more S5G-NBs provide additional resources (i.e. radio legs) to the UE S5G-NB hosts a transparent RRC entity invisible to UEhandles

68、radio parameters for S5G-NB Addition Request maintains a local UE contextRadio leg 1 and Radio leg 2 provide diversity for RRC signalling,,Option: RRC-M and RRC-S,Direct message transfer from RRC-S,Motivation:Avoid si

69、gnaling to M5G-NB and CN for path switchFast reconfiguration of S5G-NB radio legs (e.g., intra-S5G-NB HO)Termination of measurements at S5G-NBRole of RRC-M:-All RRC services and functions (including UE state assign

70、ment)-Coordination with RRC-SRole of RRC-S:Configuration S5G-NB radio legs and resources (pre-agreed with RRC-M)Termination of SRFMeasurement processing for S5G-NBIntra-S5G-NB Hand-Over controlNotes:One or mor