Skip to main content
search
All Posts By

O-RAN SC

Mar 13
Love0

O-RAN-SC Demo Highlights from Paris

By Blog

The O-RAN ALLIANCE Face-to-Face Meeting, the first of 2025, took place in Paris. Members of OpenAirInterface Software Alliance (OAI), Nephio, and the O-RAN Software Community (O-RAN-SC), showcased new developments and demos around Service Management and Orchestration (SMO), the Non-RT RIC, Open Fronthaul, and more. Below is a quick walkthrough of the demos, the technology behind them, and why they matter.

1-1. Disaggregated 5G OAI gNB with O-RAN 7.2 Split & M-Plane (Presenter: Robert Schmidt)

Robert Schmidt from the OpenAirInterface (OAI) Software Alliance kicked off by showing a high-throughput, disaggregated 5G OAI gNB setup that uses:

  • O-RAN 7.2 interface (C-Plane, U-Plane, S-Plane, and now M-Plane).
  • SmallCellForum’s nFAPI split between O-DU-high (MAC) and O-DU-low (high-PHY).
  • 3GPP F1 and E1 splits to separate O-CU-CP (RRC) and O-CU-UP (SDAP, PDCP).
  • LDPC offload on the AMD T2 Accelerator card.
  • Benchmarked speeds up to ~1 Gbps DL.

Demo Highlights

  • Architecture:  OAI O-DU-high and above are deployed on one machine in docker containers. OAI O-DU-low with AMD T2 card runs on a bare metal on another server. OAI O-DU-low is further connected to the Benetel O-RU via 7.2 interface.
  • M-Plane Integration: The Benetel O-RU is automatically configured via M-Plane, setting the carrier frequency, bandwidth, MIMO mode, compression,…, without manual intervention.
  • Bandwidth Scaling: Robert showed switching from 100 MHz bandwidth to 40 MHz on the fly, verifying throughput changes (down from ~1 Gbps to ~200 Mbps range).
  • Full Pipeline: This setup includes F1 (CU ↔ DU), nFAPI(O-DU-high ↔ O-DU-low), O-RAN 7.2 fronthaul (O-DU-low ↔ O-RU), plus PTP synchronization.

Key Takeaways

  • OAI’s disaggregated stack can sustain high throughput while adhering to O-RAN’s 7.2 interface specs.
  • The M-Plane interface now supports automatic RU configuration, a big step toward “plug-and-play” for radios.

Watch the Video. 

1-2. O-RAN-SC Lab Access & Orchestration at Rutgers (Presenter: Ivan Seskar)

Context & Goals

Ivan described the new O-RAN-SC Lab co-located with the existing ORBIT and COSMOS testbeds at Rutgers. This environment provides remotely accessible servers, RUs, test equipment, and more for O-RAN-SC developers to run large-scale tests.

Demo Highlights

  • Physical Setup: The lab has low/medium/high-power O-RUs, test instruments, PTP distributions, plus a range of compute servers.
  • Access & Account Management: Users will register through a portal, deploy SSH keys, and be grouped into “projects.” However, the community still needs to decide who approves accounts, how to schedule test equipment, etc.
  • Resource Scheduling: In other testbeds (e.g., ORBIT/COSMOS), reservations are scheduled automatically for radio nodes, ensuring only one user at a time. The O-RAN-SC Lab can adopt a similar or more flexible approach.
  • Open Questions:
    1. Who approves new user accounts?
    2. How do we handle multi-tenant usage of RUs or test instruments?
    3. What is the scheduling policy for conflicting resource requests?

Key Takeaways

  • The O-RAN-SC Lab is “live,” but official policies (user roles, scheduling, ownership, etc.) need finalization.
  • Once policies are nailed down, community members can spin up remote tests or integrate new hardware, bridging real-lab experimentation with the O-RAN-SC codebase.

1-3. Nephio + O-RAN: Cluster Provisioning (Presenter: Sagar Arora)

Context & Goals

Sagar showcased how the Nephio project (under Linux Foundation Networking) can create and manage Kubernetes clusters for O-RAN-SC deployments. By taking an “intent-based” GitOps model, Nephio orchestrates O-Cloud resources and O-RAN workloads.

Demo Highlights

  • Nephio Architecture:
    • Kubernetes-based operators (known as “Focom Operator” and “O2 IMS Operator”) extend K8s with custom resource definitions.
    • Users define “cluster templates” and pass them as an O2-based orchestration request.
    • Nephio dynamically provisions a cluster with the specified configuration (e.g., K8s “kind” cluster).
  • Workflow:
    • SMO’s Focom sends a provisioning request (YAML) that references an O-Cloud and cluster template.
    • The O2 IMS operator instantiates a K8s cluster, returning a success/failure status.
    • The final outcome is a new “Edge” cluster that can host network functions (e.g., OAI components).
  • Roadmap:
    • Nephio aims to automate not just cluster creation but also NF instantiation and day-2 config changes.
    • Future demos will integrate Tacker or O2 DMS for deploying actual O-RAN workloads on these auto-provisioned clusters.

Key Takeaways

  • Demonstrates an end-to-end pipeline: SMO Focom → O2 IMS → K8s cluster provisioning.
  • Brings a straightforward GitOps approach for multi-cloud or multi-site RAN orchestration.
  • Positions Nephio as part of the O-RAN-SC SMO puzzle, handling the “how” of cluster creation, so that O-RAN workloads can be placed seamlessly.

Watch the Video.

1-4. OAI O-DU/O-CU with O1 & E2 Interfaces (Presenter: Teodora Vladic)

Context & Goals

Teodora closed out the session with a look at OAI’s support for O1 management (via NETCONF) and E2 (via FlexRIC, a nearRT-RIC + xApp framework). The goal: demonstrate real-time reconfiguration and performance reporting from a COTS UE, plus monitoring via E2-based xApps.

Demo Highlights

  • Testbed Setup:
    • A COTS UE sits in a Faraday cage → connected to OAI O-DU via USRP. OAI O-CU and OAI 5GC deployed one another machine.
    • SMO (ONAP/O-RAN-SC-based) communicates over O1 to read/write DU/CU settings (bandwidth changes, etc.).
    • The nearRT-RIC hosts an xApp implementing the RAN Control E2 service model.
  • Bandwidth Scaling:
    • The O-DU starts at 40 MHz, achieving ~127 Mbps DL.
    • SMO triggers a reconfig to 20 MHz on the O-DU, verified in logs. Throughput drops proportionally (~60–70 Mbps DL).
  • E2 Agent / xApp Observability:
    • The E2SM-RC xApp receives UE RRC messages, decodes and displays the RRC State Changes, periodically reported channel quality, as well as RRCReconfiguration message.
    • Periodic measurements reflect the behavior of the phone when inside and outside the Faraday cage.

Key Takeaways

  • OAI has a multi-interface approach: F1 (CU-DU), O1 (SMO-DU/CU), E2 (nearRT-RIC), plus 5GC for end-to-end service.
  • The O1 adapter for OAI extends the SMO’s netconf-based control to real radio parameters—illustrating dynamic bandwidth changes with minimal fuss.
  • The nearRT-RIC + E2SM RC xApp monitors and could eventually optimize RAN resource usage based on real-time channel conditions.

Watch the Video. 

2-1. Getting an O-RU Online with DHCP (Presenter: Alex Stancu)

What was shown?

Alex kicked off the demo session with a deep dive into how an O-RU can automatically discover its management-plane (M-Plane) endpoint using DHCP. According to the latest Open Fronthaul M-Plane specs (Release 16.0.1), DHCP can carry far more information than just an IP address—particularly, details about the SMO’s domain name and whether NetConf call-home should happen via SSH or TLS.

Why it’s important:

In real-world deployments, radios need a fast, standardized way to locate their controlling SMO (or OAM system). By embedding these parameters within DHCP, operators can streamline the “power-on” or “plug-and-play” workflow for large numbers of O-RUs. This demo clarifies how the RU can use DHCP Option 43 to retrieve not just its IP address, but also SMO’s FQDN, NetConf transport type, and even references to event-collector endpoints.

Key takeaways:

  • Alex and team used a Kea DHCP server in a container-based setup with two Docker networks (Macvlan for DHCP broadcast, Bridge for normal communication).
  • A python-based (PyNTS) RU simulator boots, asks DHCP for an IP, parses the extra “Option 43” details, and immediately calls home via NetConf over TLS.
  • With only minimal changes, a real RU could replicate that same automated discovery.

2-2. A Unified View of Network Topology & Inventory (Presenters: John Keeney & Jeff van Dam)

What was shown?

Next up, John Keeney and Jeff demonstrated how SMO can provide a high-level, consolidated view of all the network domains—like RAN, Cloud, OAM systems, and more—via the newly developed Topology Exposure & Inventory Service (TE&IV). They illustrated geographic queries, grouping of network entities (e.g., by location or by type), and dynamic group updates.

Why it’s important:

Most operators have many data sources—RAN inventory, physical sites, cloud infrastructure details, and so on. O-RAN Alliance Work Group 10 is defining an API so external applications (rApps, for example) can access an abstracted, cross-domain network view rather than piecing everything together themselves. This means your advanced analytics or optimization modules can fetch “just enough” topology info in a single call.

Key takeaways:

  • TE&IV uses a Yang-driven internal model and a REST API for clients.
  • Entities and relationships are typed (e.g., “Cell has this antenna,” “Antenna is physically at this site”).
  • John and Jeff showed a Manhattan use-case, filtering antenna modules by their location polygon and retrieving just the relevant attribute (e.g., electrical tilt).
  • Future releases will expand the data model further and integrate with other open-source projects.

Watch the Video.

2-3. SMO Roadmap: Federated Orchestration & Beyond (Presenter: Shashikanth)

What was shown?

Shashikanth gave a broader look at how the O-RAN-SC SMO project is evolving. Specifically, he presented the architecture where federated O-Cloud orchestration (FOCOM) works in tandem with a Network Function Orchestrator (NFO), with supporting modules like an Inventory Management Service (IMS) and a Deployment Management Service (DMS).

Why it’s important:

Operators often need to unify orchestration across multiple clouds (public, private, or on-prem). The SMO project is exploring new ways to fold in open-source orchestration tools (e.g., StarlingX, Tacker, Open MSA) and handle both VMs and container-based VNFs/CNFs.

Key takeaways:

  • K-release: used StarlingX for the O-Cloud platform and Tacker for VNF management.
  • L-release: evaluating multiple open-source orchestrators (Open MSA and others) and aiming to handle both VM-based and container-based network functions in a single SMO workflow.
  • This lays the groundwork for more robust end-to-end lifecycle management in O-RAN networks.

2-4. O-RAN-SC Components in India’s IOS-MCN Testbed (Presenter: Shridhar Rao)

What was shown?

Shridhar showcased how the IOS-MCN project in India (backed by the Government of India) is integrating key O-RAN-SC components—especially the OAM, Non-RT RIC, and RAN-PM modules—into their real-world lab. Their setup pairs O-RAN-SC containers with OpenAirInterface (OAI) gNBs and real mobile phones.

Why it’s important:

It’s a testament to how these open-source modules (OAM, RAN-PM, etc.) can be deployed “as is” into an external system. Having minimal code modifications means that community-driven solutions truly save time for integrators. In the demo, we see OAI gNBs come online, register through NetConf, and send PM (performance) data to Kafka and InfluxDB, where the SMO visualizes throughput, number of UEs, etc.

Key takeaways:

  • IOS-MCN found the OAM and Non-RT RIC code straightforward to deploy.
  • A real lab environment with actual phones and OAI gNB underscores the code’s maturity for real testing and demonstrations.
  • They plan next steps on E2 integration (for near-RT RIC apps) once some minor interface issues are resolved.

2-5. Synthetic DU Performance Data via PyNTS (Presenter: Alex Stancu)

What was shown?

Alex returned to spotlight a PyNTS-based DU simulator that produces synthetic 5G NR performance data in the 3GPP TS 28.532 (Release 18) XML format. This O-DU simulator periodically sends “file-ready” notifications, which the SMO retrieves using standard NetConf-based triggers (SFTP for the file itself) and then pushes into InfluxDB and Kafka.

Why it’s important:

While real DUs (or OAI-based setups) are great, they may be harder to come by in early testing, or you may want to scale up 1,000 DUs for performance benchmarking. A simulator that is fully compliant with the same file-based PM approach is invaluable. It confirms the entire chain—NetConf, file retrieval, PM data ingestion, and rApp consumption—runs smoothly before swapping in actual hardware.

Key takeaways:

  • The simulator’s JSON config lets you easily define measurement types, intervals, or arbitrary numeric values for PM counters.
  • The same RAN-PM pipeline that works with a “synthetic DU” will also function with OAI or a commercial DU.
  • Demonstrates how quickly one can test the entire pipeline without specialized hardware.

Watch the full Video on the O-RAN SC YouTube channel. 

Feb 10
Love0

Showcasing Next-Generation OAM Solutions for Distributed RAN: A Highlight from IMC 2024

By Blog

The O-RAN Software Community (SC) continues to push the boundaries in developing open source solutions for the next era of wireless communication. At the India Mobile Congress (IMC) 2024, O-RAN Software Community (SC) along with the India Open Source (IOS) for Mobile Communication Network (MCN) team showcased an innovative Operations, Administration, and Maintenance (OAM) solution designed to support the needs of Distributed RAN (Radio Access Network) systems. As networks grow more complex, reliable and intuitive OAM systems become essential for managing distributed infrastructure effectively and efficiently.

Demo Overview: Key Innovations in OAM for Distributed RAN

The demonstration was designed to highlight how a scalable and web-based interface could enhance operational insights and streamline maintenance across a distributed network architecture. The demonstration showcased the following core elements:

  1. Operator-Friendly Web Interface: The IOSMCN OAM solution is accessible through an intuitive, web-based interface that simplifies network monitoring and control, making it easier for operators to oversee distributed network components.
  2. Real-Time Operational Insights: The demo illustrated how the OAM solution provides real-time data and system alerts, enabling operators to swiftly identify and address network issues, thereby improving overall network uptime and reliability.
  3. Scalability for Future Network Demands: As the demand for data and connected devices grows, networks need OAM systems that can scale effortlessly. The OAM demo showcased features designed for scalability, emphasizing how the IOSMCN solution can evolve alongside the growth of RAN infrastructures.

What’s Next: The Future of OAM in Distributed RAN

The next phase of development promises even more advanced capabilities, including enhanced automation for fault management and predictive maintenance powered by AI. This roadmap reflects O-RAN Software Community (SC)’s commitment to staying at the forefront of RAN innovation by prioritizing network resilience and operational efficiency.

Join Us at the O-RAN F2F Meeting in Paris

An extended version of this demo will be presented at the upcoming O-RAN F2F meeting in Paris (February 2025), offering additional insights and enhancements. Don’t miss this opportunity to see the latest advancements in OAM solutions for Distributed RAN. To stay informed on the latest updates, visit our website and follow us on LinkedIn.

Feb 06
Love0

Title: RIC Testing as a Platform (RIC-TaaP): Advancing xApp/rApp Design and Testing towards Digital Twin network a Case Study with Orange and O-RAN Software Community (SC)

By Blog, Case Study

Author: Mina Yonan, Orange Innovation Egypt, mina.awadallah@orange.com

Problem 

The adoption of the RAN Intelligent Controller (RIC) in networks encounters several challenges that may impede its objective and efficiency. To enable efficient and plug-and-play use cases, we can categorize these challenges into two key areas:

  • Legacy SON Platform Limitations: The development and operational life-cycle of Self-Organizing Network (SON) modules is inherently slow due to the absence of a robust testing framework. The lack of a digital twin environment for network simulation and validation significantly hampers efficiency. Moreover, traditional SON platforms are not inherently designed to evolve with AI-driven methodologies, limiting their adaptability to dynamic network conditions and next-generation automation frameworks.
  • High Barriers to Entry for xApp/rApp Ecosystem: A fundamental advantage of RIC is its ability to foster an open, interoperable ecosystem where third-party applications can be seamlessly integrated through standardized interfaces. However, the high costs associated with xApp/rApp testing and certification present a major hurdle for independent software vendors (ISVs), researchers, and academia. While RIC has expanded the ecosystem beyond traditional network equipment vendors to include a diverse set of stakeholders—such as Communication Service Providers (CSPs) and academic institutions—the financial and technical burdens of testing remain a key inhibitor to broader adoption and innovation.

Action

To address the aforementioned challenges, Orange has announced the development of RIC Testing as a Platform (RIC-TaaP)—an open source initiative designed to streamline xApp/rApp functional and operational testing, fostering innovation in xApp/rApp design and provide a proven digital-twin networks.

Recognizing the need for a robust, fully open source testing environment, Orange Innovation Egypt (OIE) has focused on enabling system-level use cases by leveraging advanced open source components. To achieve this, OIE has integrated FlexRIC from EURECOM with the ns-O-RAN simulator, originally developed by the Institute for the Wireless Internet of Things (WIoT) ,University of Padova and Mavenir. The team has enhanced the simulator to ensure full compliance with E2AP v1.01, KPM v3, and RC v1.03 standards, providing a sophisticated 5G simulation environment for validating complex use cases.

Additionally, Orange Innovation Poland (OIP) has augmented the platform with a user-friendly dashboard, RIC-TaaP Studio, enabling intuitive test scenario design and incorporating a range of operational features. Across its innovation centers, Orange continues to integrate leading open source solutions, including the 5G-LENA module, developed by the OpenSim Research Unit at the Centre Tecnològic de Telecomunicacions de Catalunya (CTTC).

Committed to openness and accessibility, Orange ensures that RIC-TaaP remains an open source and user-friendly platform, making Open RAN research and development more accessible to a broader community of engineers and researchers.

Key Components of RIC-TaaP

To establish a fully capable platform for xApp/rApp design and testing, RIC-TaaP comprises nine key components. These elements collectively form a flexible and robust network simulation environment, enabling efficient xApp/rApp development, validation, and deployment.

  1. FlexRIC – the implementation of the Near-RT RIC functionality, developed by EURECOM under the Mosaic5G project.
  2. NONRTRIC – Represents the Non-RT RIC functionality, developed by the O-RAN Software Community (OSC).
  3. ns-O-RAN Simulator – OIE introduces an enhanced version of the ns-O-RAN simulator, originally developed by the WIoT at Northeastern University. This upgraded version now supports standardized E2AP (11 messages) and service models, including KPMv3 and RCv1.03. Additionally, the E2 termination has been optimized for full compliance with FlexRIC E2 termination, ensuring seamless interoperability.
E2APv1.01E2 SETUP REQUEST​
E2 SETUP RESPONSE​
RIC SUBSCRIPTION REQUEST​
RIC SUBSCRIPTION RESPONSE​
RIC SUBSCRIPTION FAILURE​
RIC INDICATION
RIC CONTROL REQUEST​
RIC CONTROL ACKNOWLEDGE​
RIC SUBSCRIPTION DELETE FAILURE​
RIC SUBSCRIPTION DELETE REQUEST​
RIC SUBSCRIPTION DELETE RESPONSE​
KPMv3List of KPIs supported by ns-O-RAN 
RCv1.03  – CONTROL Service Style 3 (Section 7.6)   – Connected Mode Mobility Management (Section 7.6.4)   – Control Action ID 1 (Handover Control) (Section 8.4.4.1)   – Control Action ID 2 (Conditional Handover Control) (Section 8.4.4.2)   – Control Action ID 3 (DAPS Handover Control) (Section 8.4.4.3)
  1. 5G-LENA NR module: To extend the simulation capabilities, the team integrates the 5G-LENA module that covers the SU-MIMO and Enhanced PHY/MAC layer capabilities.
  2. A1 Mediator:  OIP introduces a new version of OSC A1 mediator that can transfer A1 Policy Management (A1-P) into internal FlexRIC’xApps to smoothly transfer A1-P to xApp logic and operation.
  3. O1sim:  Represents the O1 termination of the ns-O-RAN-FlexRIC platform, enabling Performance Measurement (PM) and Configuration Measurement (CM) in O1 NETCONF format. This ensures smooth integration of Service Management and Orchestration (SMO).
  4. OSIRIS:  Moving towards a Digital Twin network, RIC-TaaP incorporates the OSIRIS tool, which enables vendor-specific KPI monitoring across different time frames. This tool—or any equivalent alternative—plays a key role in AI-driven rApp development, facilitating the exchange of control actions with twin networks via the ns-O-RAN-FlexRIC platform.
  5. RIC-TaaP Studio: RIC TaaP Studio allows users to run ns-3 simulations without needing a deep development background. It provides real-time monitoring of simulation status and key performance indicators (KPIs) for Cells and UEs, with more features planned for future releases. RIC TaaP Studio integrates a powerful combination of a graphical user interface (GUI), InfluxDB, and Grafana. The OIP team developed both the backend and frontend for the GUI and made enhancements to the ns-3 simulator to enable GUI interactions.  
  1. xApp/rApp Examples: The team provide a E2E Energy Saving usecase that include:
  • Control Actions: the team implemented the Mobility Management according RCv1.03 to initiate Hand Over (HO) commands.
  • Reported KPIs: the team extends the reported KPIs from the ns-3 simulator to support a wide number of KPIs suitable for different xApp usecases.
  • RIC-TaaP studio dashboards: The dashboard includes a new visualization tap for Energy Saving sub-usecase “cell/carrier switch ON/Off” in terms of the saving gain and performance KPIs to monitor the network before and after the xApp/rApp operation.  

Results

Use-case 21: Energy Saving under Cell Utilization “Cell on/off” as an example

The Energy Saving (ES) logic example in RIC-TaaP is driven by cell utilization, particularly Physical Resource Block (PRB) usage (%). The decision-making process follows a structured sequence, as illustrated in the diagram below:

Sequence of Operations After xApp Execution

  1. xApp Requests KPM Report
    • The xApp triggers a KPM Report (Style 4) request for UEs where PRB usage falls below the defined threshold.
  2. E2 Termination Processes KPM Report Request
    • The E2 termination at ns-O-RAN-FlexRIC prepares the KPM report and subscription request for the relevant UEs.
  3. xApp Analyzes SINR Map
    • The xApp evaluates the SINR map of surrounding cells to determine suitable candidates for handover.
  4. xApp Sends Handover (HO/CHO) Commands
    • The xApp initiates a Connected Mobility procedure by sending Handover (HO) or Conditional Handover (CHO) commands using RIC CONTROL Style 3.
  5. ns-O-RAN-FlexRIC Executes Handover
    • The handover is executed, and the E2 termination at ns-O-RAN-FlexRIC sends an acknowledgment to confirm the procedure.
  6. xApp Requests Updated KPM Report for SINR Map
    • The xApp requests another KPM Report (Style 4) to obtain an updated SINR map post-handover.
  7. E2 Termination Generates Updated KPM Report
    • The ns-O-RAN-FlexRIC prepares the requested KPM report based on the latest subscription request.
  8. xApp Analyzes UE SINR Post-Handover
    • The xApp evaluates the new SINR values for UEs after mobility decisions.
  9. xApp Modifies Energy State
    • Based on SINR and cell utilization, the xApp adjusts the Energy State of the Cell/Sector/Carrier to optimize power consumption.
  10. ns-O-RAN-FlexRIC Applies New Energy State
  • The ns-O-RAN-FlexRIC enforces the new Energy State configuration as requested by the xApp.

The Energy Dashboard in RIC-TaaP Studio provides real-time monitoring of network performance and energy efficiency metrics. It includes three key categories:

1. QoS Parameters

  • L3 SINR (dB): Displays the Signal-to-Interference-plus-Noise Ratio (SINR) for all UEs in the scenario, measured at Layer 3.
  • PRB Usage (%): Indicates the Physical Resource Block (PRB) utilization for each cell in the scenario.
  • Total Downlink Transport Block Errors (ErrTotalNbrDl): Represents the cumulative number of downlink transport block errors detected on the UE side.

2. Energy Consumption Metrics

  • Energy Consumption (J): Measures the total energy consumption before and after xApp execution, allowing for comparative analysis of energy efficiency improvements.
  • Average Power Consumption (W): Calculates the average power consumption across all cells in the scenario.

3. Energy State Mode

  • Cell Power-Off Flag: Displays an indicator for each cell, signaling whether it has been switched off as part of energy-saving mechanisms.

Orange Team Leaders & Members

Domain Leader:  Eric Hardouin, Orange Innovation, eric.hardouin@orange.com ​

Program Leader: Fabrice Guillemin, Orange Innovation, fabrice.guillemin@orange.com

Project Leader:  Alassane Samba​,Orange Innovation, alassane.samba@orange.com

Contributors

Project Links

Aug 31
Love4

O-RAN ALLIANCE Broadens Its Industry Collaboration with ETSI, Announces its 3rd Whitepaper, and 4th Release of Open Software

By News


• 3rd O-RAN whitepaper focuses on O-RAN Minimum Viable Plan and commercialization
• O-RAN ALLIANCE sets cooperation with ETSI and TSDSI
• New Open Test and Integration Centers approved in Europe and Taiwan
• New Standards Collaboration Copyright License to simplify the open source development
• “D” release of open software for the RAN developed by the O-RAN Software Community

“The “D” release delivers major enhancements including support for closed-loop processing use cases,
continued evolution of Non-Real-Time RAN Intelligent Control (Non-RT RIC) platform, new and
enhanced xApps for the Near-Real-Time Radio Intelligent Controller (Near-RT RIC), as well as new
performance monitoring and alarm support.”

Read more on O-RAN Alliance Release

Jul 01
Love4

O-RAN ALLIANCE Delivers New Specifications, “Bronze” Open Source Software and New Virtual Exhibits of O-RAN Solutions

By News
  • O-RAN has recently published 23 new or updated specifications and the O-RAN Use Cases and Deployment Scenarios white paper
  • The 2nd release of O-RAN software “Bronze” adds support for new key elements of the O-RAN architecture and updates aligned with the latest O-RAN specifications
  • O-RAN Virtual Exhibition adds more demonstrations of O-RAN based technologies

Bonn/Germany, July 1, 2020 – The O-RAN ALLIANCE has continued its progress towards making the Radio Access Networks (RAN) truly open, intelligent, virtualized and fully interoperable.

The O-RAN ALLIANCE welcomes TELUS Communications Inc. and U.S. Cellular as new operator members, bringing the total to 26 major carriers. O-RAN now has over 200 companies driving the definition and realization of O-RAN technology.

Recently Released Specifications and White Paper

Published in February 2020, the O-RAN Use Cases and Deployment Scenarios white paper introduces the initial set of O-RAN use cases and cloud native deployment support options.

O-RAN use cases drive the O-RAN architecture and demonstrate its unique benefits, including utilization of AI/ML modules to empower network intelligence through open and standardized interfaces in a multi-vendor network. The white paper also introduces the O-Cloud cloud computing platform that can host relevant O-RAN functions to enable flexible deployment options in virtualized telco clouds.

Recently published specifications bring new or updated features to all parts of the O-RAN architecture, allowing vendors to progress with improved O-RAN based implementations. For more details, please check this O-RAN Blog post.

O-RAN Software Community Bronze Release

On June 21, 2020, working with the Linux Foundation, the O-RAN SW Community published its second SW release dubbed “Bronze.” The software adds support for new key elements of the O-RAN architecture and provides updates to align with the latest O-RAN specifications:

  • The initial release of an A1 policy manager and an A1 controller that implements the Non-Real-Time Radio Intelligent Controller (Non-RT RIC) architecture.
  • The Near-Real-Time RIC updated to current O-RAN E2 and A1 specifications with 5 sample xAPPs.
  • Initial O-CU and O-DU Low/High code contributions that support a FAPI framework and integration between the O-DU and RIC with E2 functionality and subscription support.
  • A Traffic Steering and Quality Prediction use case leveraging an E2 interface data ingest pipeline to demonstrate the functionality of RAN traffic steering with an E2 interface KPI monitoring capability.
  • OAM use cases that exercise Health Check call flows including the Near-RT RIC and its O1 and A1 interfaces.

“The new use cases, the Bronze software release, and the new O-RAN ALLIANCE members are indications that this global forum is working exactly as intended, reaching across borders to drive innovation and build consensus,” said Andre Fuetsch, Chairman of the O-RAN ALLIANCE and Chief Technology Officer – Network Services, at AT&T. “As this coalition evolves, we look forward to seeing how it continues to broaden access to 5G and other new access technologies.”

“Over the past 6 months, O-RAN working groups and the O-RAN Software Community have extensively engaged to achieve tight alignment between the specifications and the Bronze release open source code,” said Chih-Lin I, the Co-Chair of O-RAN Technical Steering Committee. “Specific progress related to both the Non-RT-RIC and the Near-RT-RIC frameworks and associated key interfaces deserves special mention for its importance in enabling AI/ML capabilities in RAN. The O-RAN virtual showcase further demonstrates the growing momentum towards global adoption and deployment of O-RAN solutions.”

“Ericsson is actively engaged in shaping the future of the O-RAN initiative by enabling Non-RT RIC (Non-Real-Time RAN Intelligent Controller) and A1 interface to support fine-grained intelligent steering of the RAN,” said Per Beming, Head of Standards and Industry Initiative in Ericsson. “During OSC Bronze release, Ericsson continued as the key contributor to Non-RT RIC project by improving support for intent based intelligent RAN optimization using A1 interface. This specific capability allows operators to leverage both RAN and non-RAN data to enrich end user experience.”

“The work within the O-RAN ALLIANCE is a great example of how strong industry collaboration can help accelerate technology innovation,” said Udayan Mukherjee, Intel Fellow, Network Platforms Group and Chief Technologist, Wireless Infrastructure, at Intel. “As a major contributor to the FAPI library specifications, architectures and software in O-RAN, Intel is pleased to see how this work can enable an O-RAN Distributed Unit platform that is compliant with O-RAN standardized stack interfaces.”

“The O-RAN Software Community has reached an important achievement with its second software release. This milestone is the result of a tremendous effort from across the O-RAN community,” said Gil Hellmann, vice president, Telecom Solutions Engineering, Wind River. “As the lead for the INF project delivering the edge cloud infrastructure portion for the O-RAN workgroup based on the Yocto and StarlingX open source projects, Wind River looks forward to continuing our contributions to the community to accelerate the commercialization of 5G vRAN.”

To learn more about the O-RAN Software Community “Bronze” release please read this O-RAN Blog post, and to access the code, check out the O-RAN Software Community website.

The O-RAN Software Community has been open to any participants that want to get involved in the creation of software for future RAN – for more details please visit https://www.o-ran.org/software.

Expanded O-RAN Virtual Exhibition
With the cancelation of MWC-Barcelona, on April 21, 2020 the O-RAN ALLIANCE created an online showcase. The O-RAN Virtual Exhibition includes demonstrations of real O-RAN based equipment in the form of videos, animations, charts and text.

The Virtual Exhibition currently hosts 31 demos presented by 38 O-RAN companies. O-RAN plans to keep adding more content and features to make its virtual showcase a valuable tool for RAN industry players to present real-world solutions embodying O-RAN’s architecture and specifications.

In addition to previously announced demos, O-RAN member companies have recently created 12 new virtual demonstrations of real O-RAN technology:

The first demo sponsored by SageRAN demonstrates end to end high throughput traffic running over through SageRAN’s 5G Stand Alone Open RAN Stack. This demo includes both X86 and ARM based O-DU/O-CUs and an eCPRI based O-RU.

The second demo sponsored by Keysight demonstrates Keysight’s O-RAN Test Solution for O-RUs. This test suite enables NEM development/manufacturing, Operator, and OTIC Labs to accelerate O-RU conformance testing.

The third demo sponsored by VIAVI demonstrates VIAVI’s O-RAN validation Solution for O-CU subsystem test. This complete wraparound framework enables NEMs, Operators, OTIC Labs and integrators to ensure that the O-CU can be robustly tested and optimized for high-quality and performance.

The fourth demo sponsored by Benetel demonstrates a 5G Non Standalone (NSA) platform comprised of Benetel’s product family of 4G & 5G Remote Radio Units, developed in compliance with the O-RAN specification, and a O-CU & O-DU implementation that is based on the OAI software stack and supports O-RAN’s 7.2x open fronthaul specification.

The fifth demo sponsored by Parallel Wireless demonstrates a unified 2G through 5G cloud-native O-RAN solution. This makes Parallel Wireless’s software-based Open RAN stack easy to manage and delivers cost-savings to MNOs using it to modernize or expand their networks.

The sixth demo sponsored by ArrayComm showcases two O-RAN Whitebox demonstrations: The first demo is an end to end demo using an ARM Based Multi-vendor Whitebox 5G gNB. The second demo demonstrates a Whitebox’s FPGA real time downlink bit processing (CRC, FEC, RateMatching) and uplink bit (CRC, FEC, RateMatching, HARQ) processing throughput test.

The seventh demo sponsored by Lenovo and NTS demonstrates an integrated small cell solution based on cloudification and virtualization. This demo showcases the decoupling of hardware and software based on O-RAN architectural principles.

The eighth demo sponsored by NVIDIA demonstrates an O-RAN Open Fronthaul-based hyper converged 5G CloudRAN, Core Network and MEC solution for the edge. This demo showcases the value of NVIDIA GPU and Mellanox SmartNIC-based, cloud-native, and scalable NVIDIA EGX platform, that enables software-defined, high performance and low latency solution on COTS servers.

The ninth demo sponsored by Comba Telecom showcases macro open RAN high efficiency multi-RAT RRU solution fully compliant with the O-RAN architecture supporting Split 7-2x and Split 8 fronthaul interface to O-DU, as well as E2E 5G NR indoor Open RAN solution built upon Intel-based server platform and Intel FPGA.

The tenth demo sponsored by Baicells, QCT and Keysight demonstrates the 5G SA indoor pico cell solution with multiple O-RUs via Fronthaul Gateway based on Indoor Pico Cell (IPC) Hardware Reference Design (HRD). To verify the performance of IPC HRD, the multi-UE emulator is used to test the cell merging as well as active UE numbers.

The eleventh demo sponsored by Baicells, QCT, Wind River, Keysight and China Unicom demonstrates the E2E Indoor Pico Cell solution based on IPC HRD and Open Cloud platform. In addition, the co-platform for both O-CU/O-DU and 5GC are tested with multi-UE emulator to showcase the commercial readiness for practical deployment.

The twelfth demo sponsored by Ericsson illustrates how the OSC (O-RAN Software Community) A1 controller function supports QoE refinement in RAN through the use of A1 policies. This specific capability allows operators to implement policy aware service assurance, application aware QoE prioritization and perform continuous evaluation of current vs. target QoE. O-RAN’s Non-RT RIC function and A1 interface enable fine-grained and intelligent control of the RAN.

About O-RAN ALLIANCE
O-RAN ALLIANCE is a world-wide community of over 200 mobile operators, vendors, and research & academic institutions operating in the Radio Access Network (RAN) industry. As the RAN is an essential part of any mobile network, O-RAN ALLIANCE’s mission is to re-shape the industry towards more intelligent, open, virtualized and fully interoperable mobile networks. The new O-RAN standards will enable a more competitive and vibrant RAN supplier ecosystem with faster innovation to improve user experience. O-RAN-compliant mobile networks will at the same time improve the efficiency of RAN deployments as well as operations by the mobile operators. To achieve this, O-RAN ALLIANCE publishes new RAN specifications, releases open software for the RAN, and supports its members in integration and testing of their implementations.
For a short video describing O-RAN’s progress, see www.o-ran.org/videos
For more information please visit www.o-ran.org

For more information, contact:
O-RAN ALLIANCE PR Contact
Zbynek Dalecky
pr@o-ran.org
O-RAN ALLIANCE e.V.
Buschkauler Weg 27
53347 Alfter/Germany

Close Menu