Managing O-RAN Networks: xApp Development from Zero to Hero

TL;DR

This paper addresses the complexity and fragmentation surrounding xApp development in O-RAN by delivering the first comprehensive theory-to-practice guide focused on the OSC Near-RT RIC. It combines a rigorous theoretical foundation of O-RAN and Near-RT RIC components with practical, step-by-step instructions for xApp design, configuration, lifecycle management, and implementation using the OSC tooling (dms_cli, Helm, RMR, SDL) and the E2Sim testing environment. Core contributions include a detailed description of xApp descriptors and schemas, Docker/CI/CD workflows, and end-to-end patterns for communication (RMR/A1), storage (SDL), and E2 subscriptions, complemented by debugging, best practices, and end-to-end testing guidance. The work enables reproducible xApp development for academia and industry, highlights current open challenges (AI/ML integration, security, cross-framework compatibility), and points to a public repository with descriptors, schemas, and example code to accelerate adoption and validation in real networks.

Abstract

The Open Radio Access Network (O-RAN) Alliance proposes an open architecture that disaggregates the RAN and supports executing custom control logic in near-real time from third-party applications, the xApps. Despite O-RAN's efforts, the creation of xApps remains a complex and time-consuming endeavor, aggravated by the sometimes fragmented, outdated, or deprecated documentation from the O-RAN Software Community (OSC). These challenges hinder academia and industry from developing and validating solutions and algorithms on O-RAN networks. This tutorial addresses this gap by providing the first comprehensive guide for developing xApps to manage the O-RAN ecosystem from theory to practice. We provide a thorough theoretical foundation of the O-RAN architecture and detail the functionality offered by Near Real-Time RAN Intelligent Controller (Near-RT RIC) components. We examine the xApp design and configuration. We explore the xApp lifecycle and demonstrate how to deploy and manage xApps on a Near-RT RIC. We address the xApps' interfaces and capabilities, accompanied by practical examples. We provide comprehensive details on how xApps can control the RAN. We discuss debugging strategies and good practices to aid the xApp developers in testing their xApps. Finally, we review the current landscape and open challenges for creating xApps.

Figures (11)

• Figure 1: The xApp development cycle and the tutorial paper organization. Sections \ref{['sec:theo']}--\ref{['sec:tech']} provide developers with theoretical and technical background for getting started in O-RAN, Sections \ref{['sec:prep']}--\ref{['sec:debug']} detail the xApp development cycle accompanied of practical examples, and Sections \ref{['sec:good']}--\ref{['sec:outl']} contain lessons learned, with good practices and current open challenges.
• Figure 2: Comparison between the conventional, monolithic RAN and the O-RAN paradigm, showing the latter's decomposition of the RAN into functional components running in software, interconnected using open interfaces, and orchestrated by a common control and management overlay.
• Figure 3: Logical architecture of O-RAN, showing the RIC and their interfaces for managing the RAN and its E2 Nodes, i.e., OCU, ODU, and ORU. The dashed lines indicate interfaces standardized by the 3GPP, whereas the solid lines indicate new interfaces introduced by the O-RAN Alliance.
• Figure 4: The internal components of the nearrtric and how they communicate with other O-RAN entities using different interfaces. The xApps reside inside the nearrtric and interact with its components to leverage their capabilities to perform actions, e.g., subscribe to information from the RAN.
• Figure 5: The layers of abstraction for running xApps, showing their Kubernetes pods, which include one or more Docker containers with the complete environment to run the xApp source code, and the underlying nearrtric cluster, running on the host OS of a virtual machine of baremetal server.