SMO enabling intelligent RAN operations



A1 Interface between non-RT RIC and RIC near RT to enable policy guidance of applications / functions of RIC near RT and support AI / ML workflow.

E2 Interface connecting the near RIC RT and one or more O-CU-CP, one or more O-CU-UP and one or more O-DU.

Near-RT RIC (O-RAN Almost Real-Time RAN Intelligent Controller) A logic function that enables near real-time control and optimization of RAN elements and resources through fine-grained data collection and actions (e.g. UE base, cell base) on the E2 interface.

RIC non RT (RAN non real time O-RAN intelligent controller) A logic function that enables non-real-time control and optimization of RAN elements and resources, AI / ML workflow, including training and model updates, and policy-based advice from applications / functionalities in an RIC close to RT.

O1 Interface between orchestration and management entities (orchestration / NMS) and O-RAN managed elements for operation and management, through which FCAPS management (fault, configuration, accounting, performance and security), software, file management and other similar functions must be performed.

O2 Interface to the O-Cloud to support the orchestration of the management of the O-Cloud infrastructure and the deployment of the O-RAN network functions on the O-Cloud.

O-Cloud O-RAN cloud computing platform comprising a set of physical infrastructure nodes that meet O-RAN requirements to host relevant O-RAN functions (such as RIC close to RT, O-CU-CP, O -CU-UP and O-DU, etc.), supporting software components (such as operating system, virtual machine monitor, container runtime environment, etc.) and functions appropriate management and orchestration.

O-CU-CP (O-RAN central unit – control plane) A logical node hosting the RRC and the control plane part of the PDCP protocol.

O-CU-UP (O-RAN central unit – user plane) A logical node hosting the user plane part of the PDCP protocol and the SDAP protocol.

O-DU (O-RAN distributed unit) A logical node hosting RLC / MAC / High-PHY layers based on a lower layer functional division.

R1 Interface composed of a set of services that facilitate interactions between rApps and the non-RT RIC framework.

rApp An application designed to run on the non-RT RIC. Such a modular application exploits the functionalities exposed by the non-RT RIC to provide value-added services with respect to the intelligent optimization and operation of the RAN. The rApps communicate with the platform via the R1 interface.


Leave A Reply

Your email address will not be published.