O_RAN.pptxklllkioouuuuyyyvvvvvvccccgtyyybb

ORAN operation and implementation considering existing network

1. Confidential | DD.MM.YY | version # O RAN Study

2. O RAN O RAN Vision Confidential | DD.MM.YY | version # Classical Network Appliance Approach Network Functions Virtualisation Approach Fragmented, purpose-built hardware Physical install per appliance per site Hardware development: large barrier to entry for new vendors,constraininig innovation & competition Commercial Off-the-Shelf (COTS) hardware Allowed vendors to get standardized hardware/servers at much Lower cost, best quality to install Vendors could focus on softwares instead of purpose built hardware Competitive & innovative Open Ecosystem Automatic orchestration and remote installation

3. O RAN O RAN Vision Confidential | DD.MM.YY | version # Proprietary Hardware Proprietary Hardware + Proprietary Software Proprietary Interface

4. O RAN O RAN Vision Confidential | DD.MM.YY | version # Proprietary Hardware COTS Server + Proprietary Software with virtualized Functions Proprietary Interface vRAN is not Open RAN

5. O RAN O RAN Vision Confidential | DD.MM.YY | version # GPP based COTS Hardware Can be purchased from any ODM/ OEM/ RAN Hardware Vendor COTS Server + Proprietary Software with virtualized Functions Open Interface Any vendor software can work on this hardware

6. O RAN O RAN Ecosystem Confidential | DD.MM.YY | version # Multi-Vendor deployment Capable of reducing network CAPEX & OPEX Capable of improving network efficiency and performance Increases scalability Endless innovation and healthy competition among vendors aids overall development OpenRAN : Project Group that is part of Telecom Infra Project (TIP ). Main objective is the deployment of fully programmable RAN solution based on GPPs/COTS and disaggregated software so that operators and vendors can benefit from the flexibility and faster pace of the innovation capable with software-driven development. O RAN Ecosystem

7. O RAN O RAN Ecosystem Confidential | DD.MM.YY | version # Founded in Feb 2018, it now has around 26 MNOs as members including JIO & more than 160 RAN solution providers as contributers ORAN is about Operator Defined Next Generation RAN Architecture and Interface with key objective of Transforming Radio Access Networks open. Intelligent, virtualized and fully interoperable RAN Providing flexibility to the MNOs to choose the best breed of RAN Components

8. O RAN O RAN Evolution Confidential | DD.MM.YY | version # Source-VIAVI solutions ORAN

9. O RAN O RAN Overall Architecture Confidential | DD.MM.YY | version #

10. O RAN O RAN Overall Architecture Interfaces: A1 between SMO and near RT RIC E2 between near-RT RIC and O-RAN nodes(O-CU and O-DU) E1 between CU-CP and CU-UP F1 between O-CU and O-DU Open Fronthaul between O-DU and O-RU O1 supports typical FCAPS and other management functions between the ORAN components and the Service Management and Orchestration Framework O2 supports virtual resource management functions and other O-Cloud related management functions . Confidential | DD.MM.YY | version # O RAN Alliance defines the controller for the Intelligent RAN as RIC and divides it into non-Real Time(> 1s) and near-Real Time(< 1 s) layers . Near-RT RIC (< 1s) Near-RT RIC, O-CU-CP, O-CU-UP, O-DU, and O-RU are the network functions for the radio access side Near-RT RIC enables near real-time control and optimization of O-RAN (O-CU and O-DU) nodes and resources over the E2 interface with near real-time control loops (i.e., 10ms to 1s) The Near-RT RIC hosts xApps that use E2 interface to collect near real-time RAN information to provide value added services using these primitives, guided by the policies and the enrichment data provided by the A1 interface from the Non-RT RIC Service Management and Orchestration (SMO ) This framework contains the Non-RT RIC function (>1s ) which has the goal of supporting intelligent RAN optimization in non-real-time (> 1s) by providing policy-based guidance using data analytics and AI/ML training/inference. Multi-RAT CU Protocol Stack This function layer supports various protocol stacks including 4G and 5G Radio access Supports virtualization and consists of function that executes commands issued by non-RT RIC Supports F1/E1/E2/X2/ Xn interfaces specified by 3GPP O-DU and O-RAN Radio Unit(O-RU) O-DU and O-RU consists of real time L2 functions and functional group performing Baseband processing and radio signal processing Open Fronthaul are newly specified between O-DU and O-RU

11. O RAN O RAN Overall Architecture Confidential | DD.MM.YY | version # Exemplary use cases including : Context Based Dynamic Handover Management for V2X QoE Optimization Flight Path Based Dynamic UAV Resource Allocation . Use cases including Traffic Steering Massive MIMO Optimization Radio Resource Allocation for UAV Applications QoS Based Resource Optimization showcasing the generation of AI/ML models at Non-RT RIC using long term data gathered from both RAN and external sources, the deployment of these models and policies to Near-RT RIC to optimize and fine tune RAN in real time and the policy feedbacks to continuously update the AI/ML models use long term data analytics and specific triggers to request configuration changes along with policies to optimize RAN.

12. O RAN O RAN Work Groups Confidential | DD.MM.YY | version #

13. O RAN O RAN Split Architecture Confidential | DD.MM.YY | version # O-RAN has selected a single split point, known as “7-2x” to balance the following two competing interests in functional split defining Fronthaul interface: Keeping an O-RU as simple as possible, smaller, less power hungry Setting the interface at a higher level to reduce the interface throughput, but to increase the complexity of O-RU. Bandwidth requirement increases Low Latency Requirements increases

14. O RAN O RAN/3GPP/SCF/ eCPRI Function Split Architecture Confidential | DD.MM.YY | version #

15. O RAN O RAN Function split 7-2x Confidential | DD.MM.YY | version # Based on Split Option 7-2x O-DU is a logical node hosting RLC, MAC and High-PHY (including FEC, encode/decode, scrambling and modulation/demodulation ) O-RU is in charge of Low-PHY (FFT/ iFFT , digital beamforming, and PRACH extraction and filtering) and RF processing “ Category A ” O-RUs “ Category B ” O-RUs Precoding not done (Lower complexity) Precoding done (High complexity)

16. O RAN O RAN Function split 7-2x for DL NR Confidential | DD.MM.YY | version #

17. O RAN O RAN Function split 7-2x for DL NR Confidential | DD.MM.YY | version #

18. O RAN O RAN Function split 7-2x for UL NR Confidential | DD.MM.YY | version #

19. O RAN O RAN S-Plane Confidential | DD.MM.YY | version # O-DU acting as PTP and SyncE master to distribute network timing toward O-RU frequency and time distribution is made by the fronthaul network itself (not by the O-DU). That means that one or more PRTC/T-GM (acting as SYNCE+PTP master) is implemented in the fronthaul network to distribute network timing toward O-DU and O-RU. O-DU does not act as SYNCE and PTP Master towards the fronthaul interface. It can select its own synchronization from local or remote PRTC like in LLS-C1/LLS-C2 There could be some deployment use cases that prevent the fronthaul network (or only a section of the network) from being upgraded to G.8271.1 compliance and meeting the target performance at the O-RU O-RAN synchronization strategy allows local PRTC (typically GNSS) timing option at the O-RU.

20. O RAN O RAN S-Plane Confidential | DD.MM.YY | version # The O-RAN fronthaul network shall ensure O-RU meeting a +/-50ppb air interface frequency error requirement. 3GPP 24 TS 36.104 (for LTE macro cells) and TS 38.104 (for 5G macro ceO ) specify +/-50ppb as the short-term average error in 25 1ms duration applicable to both LTE and 5G technologies. Air Interface Frequency error Air Interface Time error

21. Back up slides Confidential | DD.MM.YY | version #

22. Back up slides Confidential | DD.MM.YY | version # ITU-T Rec. G.8272.1/Y.1367.1 Amendment 2 (08/2019) Timing characteristics of enhanced primary reference time clocks Amendment 2

23. Back up slides Confidential | DD.MM.YY | version # ITU-T Rec. G.8273.2/Y.1368.2 Amendment 1 (03/2020) Timing characteristics of telecom boundary clocks and telecom time slave clocks Amendment 1

24. Back up slides Confidential | DD.MM.YY | version # ITU-T Rec. G.8273.2/Y.1368.2 Amendment 1 (03/2020) Timing characteristics of telecom boundary clocks and telecom time slave clocks Amendment 1