2/3/2020 W tein 5G NR gNB Architecture An Open-RAN (ORAN) Perspective Saidhiraj Amuru Overview + Evolution of RAN architectures + O-RAN Architecture + O-RAN functional splits + O-RAN FrontHaul Interface + O-RAN Transport Protocol + O-RAN C-Plane and U-Plane Protocol + O-RAN Delay Management(S-Plane)Wisic Traditional RAN Architecture w wee, @® Everything is co-located ARM: Remote Radia Head (RF Antennas) 800; Baseband Unit (Modem) CORE: Core Network Wisig Centralized RAN Architecture Networks| B seh pec rn i -- PRI: Common Public Racio Interface, ‘a protecol fori dat transmission between Radio Equipment RE, RRM) and Radio Equipment Controle (REC ie. BBU) ia teal five ‘Wastape of exourees constant CPR data steams ara exchanges even when no rai s present Fixed RRE-BBU mapping >not good fr viruslzed BL architec Highly inefficient ~ sales with numberof antennas, not data Requires very lou latency 20042 Optical trancpor BAN vendor proaritary format ie, 150M dat 2.5ebps CPR vaffie 2/3/2020PRI: enhanced Common Public Radio Interface, ceswerion ot CPR 1 Ethernet bases IP aches foun only when tic is present (na pint. t- point ike CPA) + BAU can be renning on COTS platforms Difco synchronise RRA and BEU due to bursty trafic Wisig Networks| Cloud RAN ~ Supports More Splits Further disaggregate BBU into real-time and non-real-time functions into DU & CU RU: Radio Unit Move away from vendor lock-in, DU: Distributed/Data Unit Reach out to open IP/Ethernet based technologies (CU: Control/ Centralized Unit w Wisig 2/3/2020Wisig Where to split CU-DU and DU-RU? Wises a =e ee ee sloelslslalelcli ‘BW requirement increases Low latency requirements Wisig Where to split CU-DU and DU-RU? WW eee es Assumations Cama enn INR perspective rs)*13 (OFDM. ms “350 Gb lumber af tranim 2/3/20202/3/2020 Enter X-RAN and O-RAN Wises + sRAN/O-RAN's background ‘+ Startedin June 2016 as xRAN Forum and later merged with C-RAN Allance to form ORAN allnce In February 2018, + Operator driven: ATAT, China Mobile, Deutsche Telekom, NTT DOCOMO and Orange + Drven by openness and intaligence + ORAN Is not justopen source software + Defines a whte-box architecture + Open aris + Open Architectures + open Hardware + Open interfaces + Advantages + Multivendor deployment + sneresees eealabilty 1+ Decrantes CAPEX 8 OPEX less innovations + Disedvantages + More effort in testing systems integration of mutt-vendor systems O-RAN Vision W BSS is + Two fold functional spit + Horizontal alt + Spits ati proteelstack—vaiou options + Vertical spit ‘Separates CP & UP functions + Interfaces ‘+ Open FH between O-DU and 0-RU + FLbetween O-DU and O-cU + exbetween CU-CP and CU-UP + Ebetween RICAT and CU/DU + AL between NMS and RIC RT ‘+ RAN Intelligent Controller (RT-RIC) + RRM, mobility real time operations + Uses'a machine learning modal trained in the non real ime RICORAN Standardization + Operator Working Group + Technical Steering Committee + Working Groups + WL Use Cases and Overall Architecture Workgroua, + WWG2= Non-res-time RIC and Al Interface Workgroup + WWG3_Negr Real-time RIC and €? interface Workgroup + WG6-Clousification and Orchestration Workgroup + WG7-White-box Hardware Workgroup + WGB- Stack Reference Design Workgroup + Focus Groups + OSFG -Open Source Focus Group + SDI Stondard Development Focus Group + TIEG “Test & integration Focus Group + O-RAN Software Community RAN W Wee al ORAN ORANAWG4.CUS.0-102.00 ‘ORAM Frontaul Working Group ‘Controt User ana Syrchronzaton Plane specication ‘ORAN.WOAM nteace Speciation. 0 ‘0AM Operstone a aintnancsneraceSpecietion O-RAN Split Architecture + O-RAN has selected a single spit point, known as “7-2x" bul {tallows a small variation. . HH * H . =e own =H | = bed Endo End Lata enya coz FHCs siveent ven hh Few Sons 236 Gos 2/3/2020O-RAN FrontHaul Interface Traffic is classified into two types: CUS-Plane and M-Plane CUS Plane: Control / User / Synchronization Plane ae a T + Covers realtime control plane communications between the DU and RU = + Covers user plane traffic in DL and UL between DU and RU = + Covers synchronization of the RU generally sources from the DU a + Uses Ethemet transport and eCPRI/IEEE 1914.3 aco application transport = |[a ‘M-Plane: Management Plane usta usw + Covers management ofthe Radio Unt (RU) as governed by the DU =e + Provides all non-real-time contol of the RU (Real time control uses the lane) C=] + Uses Ethemet(UDP/P] transport C=] CUS-Plane — Category A and Category 8 RUs ‘Two types of RU are considered Category A: lawtots ey ou + Preceding funebon an DU lowe the RU ero eng be spe + Te ioetace wl cary sata soeams inthe oo Dlumich ean large thon ere Te Category 8: + Precading sin RU which makes AU design complex 'Oeameretn +The Ftintrfae wil erry spatial ayers which Eas beless dats Pressro + Thisesepory allows modulation compression whch reaces the DI throughs much mare ony _Deiseeronns Desires 2/3/20202/3/2020 W Wikia Category B Radio Unit CUS-Plane — Split Point 7-2x in DL for NR Category A Radio Unit ‘WiSig CUS-Plane — Split Point 7-2x in UL for NR Networks| + nla inthe OL cate, the RU catagory me oe mo makes no ference in UL + FE CP removal and firing nthe O-RU oo + Rest ofall the PHY functions in the -DU en ary er ag cote) | oelts| | mttn (reser) rom RU a == ste! Cote | Cae2/3/2020 CUS-Plane — Encapsulation Ethernet isthe salected transport, and al radio application data is conveyed within the Ethernet Payload, ‘The radio transport header is used to convey some radio-specifc transport information, while the radio transport payload carries the CPlane & U-Plane information. wi CUS-Plane — Radio Transport Header Ww Nebr + There are tun posi aco trans] Massage Type ® | Neme ‘onal + For ease of implementation, these TO Date 1 eas possible + soth we Sbyte headers withthe ee only the fst two bytes ier ReabTime Conte Dats en eaeasi43 Remote Memory Access = (One-way Delay Messurement Remote Reset Eventinication = IVF StaeUp = INF Operation IWF Mapping IWF Delay Control Reserved (Ciszrrecs [arm 04-258 Vendor Spectic 4 ij2/3/2020 (Plane Specification — Section Types w WSs, eCPRI message type-2 maps to C-plante message in ORAN In general there are “data sections” which identify which symbols / portions of symbols (e.g. PRBS) are addressed, Plane: ‘+ sectionTyp2=0 : DL idle/guard periods - allows Tx blanking for power savings + sectionType=1 : DL/UL Channels - provides mapping af beamforming index or weights to REs + sectionType-3 : PRACH and mixec:numerolagy channels + sectionType=5 : UE scheduling Info - provides UE co-e RU sectionType + sectionType- ulin info allowing eal-time BF weight calculation on the UE channel info - provides UE channel info to gue real-time BF weight calculation on the RU LAA Support ~ provides information specific ta LAA especially isten-before-tak operation Example: C-Plane Section Type 0 W WS is Cont intormaton nee describes ety PBS allowing fhe nut Ban traem sn for eserves 10Example: C-Plane Section Type 1 mon ao apaton heat: udcomote U-Plane Data ‘The U-Plane is used to send ‘actual IQ data as arranged in seatial streams or layers already mapped into the resource Common radio spptestion hoader elements Same fo al U-lane massages Data is transported in compressed format if compression is enabled Data is transmitted symbol by symbol as U-Plane messages, There is no sectionType, reMask cor numberOfsections parameter for U-Plane messages; the sectionType and reMask values are inferred from the matching C-Plane Sectionld. 2/3/2020 12/3/2020 Use of data sections in PRBs (LTE example) w We stares es Bes iitinctccanctaneens Ges moNgustasoncm? ewe grec aeee ecco [Teste seme ofthose Res wil be zr, er ate Use of data sections in PRBs (LTE example) w wise ‘Sevatnen cations needed to spec these Pi: Secnis:Fevsk~ 11111211111 (breads beam for 5, SS, PBCH) ‘Setnld2:resk= 0141811124 (UCL Res, al REs ore data) Sectoid: revesk 0110301101 (UE Es numbered rombetom) Secon relsk= 10400100100 |CRSRE, comparetay eas) ‘Seton revvsk 3131811133 (UEm 3), Sectoni': rest 0110301101 (UES ES numbered rombctom) ‘Secnld: resk= 10100100100 [CRS RE, compara ete) ‘eons resk= 3013 1919 133 (UE RE) Secon? relish 331150000 (UEE RES) ‘etn 7: reveck= 000000171200 |6S-AS RE) et dna Sectors revesk= 0110301101 (UES ES, numbered rome) ‘Secnldrelfsk= 1010010010 [CRS AE, compara Ne) ‘eons resk= 3013 1910 13 (UE RE) ‘Scions resi lites res nimoered om coma) Sestoniac aan 111 11000011 (UES? RES) 19102 1011 es Fe mores terete) 008 20100100(CR5 Res complementary risk) uct ane 12U-Plane Da compression WW WSS is + The data rates increase linearly with spatial streams (or layers) in split option 7.2%. * Various compression methods are currently supported. + No Compression, lock Floating Pein, Block Scaling law compeesion, Meduaton Compresion + The block compression methods are performed on Physical Resource Black (PRB = 12 subcarriers) basis + Example! + 16bits and + 9bits mantissa ~ includes 1 sign bit + Shits exponent (4 for | and 4 for Q) ale [ole m2 +388 its + Without BFP compression + -LPRB= 12 (Subcarriers) * 16 (bits) * 2 and Q) =384 bits + With BFP compression + -LPRA~ 12 (Subcarriers) "8 (bits) *2(Iand Q) + 8 (exponent) = 224 bits + Compression Ratio = 0.5833 224 bie Wis C/U-Plane ~ message timing WW. BSS as + Ingeneral, C-Plane messages precede U-Plane messages, and a single C-Plane message may cover ‘multiple U-Plane messages. 2/3/2020 13IQ Data Transfer Procedure Delay Management (5-plane) + The transmission windows and reception windows are determined based on: + The processing time + Receiver buffer lengths + Transport network delay variation + In Downlink, the DU has to send data early enough to ensure the corresponding symbol time and also that it does not send data too early risking overflow of the RU buffers + In Uplink, the data must be received early enough to ensure the DU can process the data in time to meet HARQ, loop restrictions. + Not all U-Plane data is delay managed, + Non-Delay managed traffic such as SRS data are sent on “best-effort” basis, 2/3/2020 14Delay Management: DL Ww > 7 os S ei ee ee oe a Wisig ORAN Advantages and Summary + Interface simplicity: Transfer of user plane data is based on Resource Elements / Physical Resource Blocks, which reduces complexity + Transport Bandwidth Scalability + Lower split options (ea, spits 7-1 and 8) scale based on number of antennas, + In contrast, 72x interface scales based an “streams”, which allows using high rumber of antennas without higher transport bancwidt, + User data transfer can be optimized to send only PRBS that contain user data for purpose of reducing ‘tansport bandwicth [DMRS etc generated in RU) + Less user specific parameters are used at split 7-2x when compared to higher split options) > simplified design ‘+ Moves away from single-vendor design lock-in for operators + Several new companies can contribute to individual portions of the entire design + Better enhanced startup community 2/3/2020 15Back Up Slides W tein U-Plane Data: Modulation Compression + Toregresent tne consalation pains as ans values thatalse overlap allowing multe conteation ss tobe represented by single Word wid, the tertaatons ae “ehited to alow 358 fomplement| and value to represant any fonseston pon + Foe Decompression, un shift the constellation and Tulppiywrtn sale taerar bene on monlton ace + Agplicabieoniyto OL + Data rates almost sme a spit ontion 7.3 + Completlylessiesscompresion 2/3/2020 16WiSig U-Plane Data: Modulation Compression Networks| ‘Assumptions: 64 TRX, Max Qm = 256 QAM, 100 MHz, 16 Spatial streams + W/O modulation compression using block compression methods + -LPRA~ 122.8 bits mantissa + 8-bits exponent ~ 200 bits + DL data rate: 14 (symbols) «273 (PRBS) x200'x 16 (spatial streams) /0.5 ms ~ 24.48 Gbps + W/ modulation compression: + 1pRa=12 ¢8 bite 96 bite + DL data rate: 14 (symbols) «273 (PRB) x86 x26 (spatial streams) / 0.5 ms = 11.74 Gbps FH: eCPRI data rates + semana emer eae] comet [aaroae | carer [usr one | Corel | ur oma at 2/3/2020 17eCPRI W WSS. + Open protocol for fronthaul * Allows data transfer over packet based network: IP or ethernet + allows various split options option 7.1, 7.2, 8 ete + CBRI does only Option & + Analog hashigh BW requirement for 5G and hence CPR breaks + eCPRI based on split has data rate requirements ranging rom 106 to 2006 (Option 8) + eCPRI has C-plane, M-Plane, U-Plane, S-Plane + Control and management plane manage DU and RU -> Operation, maintenance, not time critical + Usplane carries SG NR control channels, ata channels + S-plane I for synch between DU and RU, fame and time alignment + eCPRI allows different message types + 256 message types + Packing of messages, forming of messages is where ORAN comes into picture Functional Decomposition (eCPRI) WW. Were ‘eble2: Fone equerents v8. sls RRR ie -2NB/ENB. | mi seamen i080 . sexes cone one “may Deen ‘Intra Phy splits ly ly ronal atncy Fequtrement 2/3/2020 18Functional Splits — 7.X Ww Wisig Delay Management: Model Ww Model uses reference points from CPRI delay model S Downline RL-Outransmt pr taRuvccan oon - Tia varsmasontime + oink ‘rns + Transport Variation in network (TL2max~T12ain) All transmit/ receive times relative to antenna ("Ra") + "Medel defines transmission reception in terms af symbel ime over the sir transmission time (T12/T3) wales, T2a/ Tos MUST vty 1 Receive window 2: 8U |123_ey3e~ 25min}; DU [Tatas Tate) ‘+ Tranemiasion Window: Earls latest Wansmt time to ensure reception in coresponding (OL UL reception window 2/3/2020 19