ap.
Back to Blogs
5G & O-RAN

Paper Review: ORANSlice: An Open-Source 5G Network Slicing Platform for O-RAN

By Apala Pramanik  ·  Cheng et al., ACM MobiCom 2024


What This Paper Does

Cheng et al. present ORANSlice, a software framework that adds network slicing capabilities to OAI (OpenAirInterface), an open-source 5G base station stack. The system has three components: a slice-aware two-tier MAC scheduler on the gNB, multi-PDU session support on the OAI softwarized UE, and an E2SM-CCC service model with a RAN slicing xApp running on the OSC Near-RT RIC. The paper validates the system on two hardware testbeds and one simulator.

Background: The Problem Being Addressed

A 5G network serves very different types of users on the same physical radio infrastructure. A hospital needs low latency. A streaming platform needs high throughput. Network slicing is the mechanism for partitioning radio resources among these different service types.

Radio resources are organized as a time-frequency grid. Each cell is a PRB (Physical Resource Block). Slicing means deciding how many PRBs go to each slice at each moment.

3GPP defines this through an RRM Policy with three parameters per slice:

Each slice carries an identity called S-NSSAI (SST + SD). SST is an 8-bit field identifying the service type; SD is a 24-bit optional field distinguishing slices of the same type.

O-RAN splits the base station into an RU (Radio Unit), DU (Distributed Unit), and CU (Central Unit), and adds a Near-RT RIC (RAN Intelligent Controller) that runs xApps to control the network through a standardized E2 interface. The service model defining slice control messages is called E2SM-CCC.

What Existed Before and Why It Was Insufficient

Several prior tools addressed parts of this problem.

SCOPE1 built a slicing xApp on srsRAN 4G. It uses custom service models that are not O-RAN E2SM-CCC compliant and does not follow the 3GPP RAN slicing model.

FlexSlice2 implemented a real-time slice-aware scheduler on OAI 5G but had no O-RAN E2 integration: no xApp, no standards-compliant control loop.

RadioSaber3 developed a channel-aware slicing scheduler but operated entirely inside an RF simulator, with no real hardware involved.

ProSlice4 built a customized E2SM and xApp for slicing but does not follow 3GPP slicing specifications, is not O-RAN E2SM-CCC compliant, and is not open-source.

Zipper5 implemented slicing on closed-source commercial protocol stacks, making it inaccessible to the research community.

The shared gap: no single open-source tool provided 3GPP-compliant slicing, O-RAN-compliant control, and support for multiple simultaneous slices on a single UE, all in one working system on real hardware.

The Three Components

Two-Tier MAC Scheduler

The stock OAI MAC layer uses a proportional-fair scheduler that divides PRBs among users without any awareness of slices or QoS requirements. ORANSlice replaces this with a two-tier approach:

One note: DedicatedRatio is not yet implemented (acknowledged in a footnote). Only MinRatio and MaxRatio enforcement is demonstrated.

Multi-PDU on OAI nrUE

A PDU session is a data connection between a UE and the core network, bound to a specific slice via its S-NSSAI and assigned an IP address. 3GPP allows up to 8 simultaneous PDU sessions per UE. OAI's softwarized UE previously supported only one active PDU session at a time. ORANSlice extends it to support multiple concurrent sessions, enabling a single device to carry traffic on two slices simultaneously. Commercial devices like the Sierra Wireless EM9191 already support this in firmware; this work brings OAI's software implementation to the same level.

E2SM-CCC and RAN Slicing xApp

The authors implement a simplified version of the O-RAN E2SM-CCC service model for the OSC Near-RT RIC. Only the RRMPolicyRatio configuration is supported. The RAN slicing xApp logic is straightforward: every 10 seconds it reads the last 5 seconds of KPM data from InfluxDB, identifies the slice with the lowest average downlink throughput, assigns it MaxRatio = 90%, and assigns the other slice MaxRatio = 10%. It sends this as an E2 Control message to the gNB.

The data flow is:

gNB → [E2 Indication] → KPM xApp → InfluxDB
                                        ↓
gNB ← [E2 Control]  ← RAN Slicing xApp ←

A separate KPM xApp handles metric collection and storage. The RAN Slicing xApp only handles decisions.

Testbeds

Experiments and Results

Experiment 1 tests the closed-loop control. Two slices, one UE each; the xApp toggles MaxRatio every 10 seconds. The result is an alternating PRB allocation pattern across all three environments, confirming the policy is enforced correctly. The xApp logic intentionally creates a self-reversing loop; whichever slice gets more PRBs gains higher throughput and becomes the "winner," so next round the other slice receives the 90% allocation. This oscillating behavior is the expected proof of correct operation, not an optimized outcome.

Experiment 2 tests MinRatio guarantees with multi-PDU. UE 1 runs two simultaneous PDU sessions (one per slice); UE 2 competes on Slice 1. With MinRatio = 0 on Slice 2, UE 2's competition starves Slice 2 throughput. Setting MinRatio to 80 restores it; reducing it to 40 reduces throughput proportionally. Results are consistent across all three environments.

Honest Assessment

The contribution here is integration, not algorithmic novelty. The two-tier scheduler is a clean but straightforward engineering decision. The xApp control logic (90%/10% toggle) is intentionally simple and would not be appropriate in a production deployment. The E2SM-CCC implementation is a simplified subset of the full specification.

That said, the paper's claim is specifically about building an open, standards-compliant foundation that others can extend. On that metric, it delivers. Prior tools forced researchers to choose between standards compliance, O-RAN integration, or open-source availability. ORANSlice provides all three together, on real hardware, with published code.

The portability demonstration across Arena, X5G, and RFSim is the most practically useful result. Identical behavioral patterns on two different hardware stacks confirm that the implementation does not rely on vendor-specific quirks.

The remaining gaps are worth noting for anyone planning to build on this work:


Paper Reference

Cheng, Hai, Salvatore D'Oro, Rajeev Gangula, Sakthivel Velumani, Davide Villa, Leonardo Bonati, Michele Polese, Gabriel Arrobo, Christian Maciocco, and Tommaso Melodia. "ORANSlice: An Open-Source 5G Network Slicing Platform for O-RAN." In Proceedings of the 30th Annual International Conference on Mobile Computing and Networking (ACM MobiCom '24), November 18–22, 2024, Washington D.C., USA. ACM, 2024. https://doi.org/10.1145/3636534.3701544


Footnotes

  1. Bonati, Leonardo, Salvatore D'Oro, Stefano Basagni, and Tommaso Melodia. "SCOPE: An Open and Softwarized Prototyping Platform for NextG Systems." In Proceedings of the 19th Annual International Conference on Mobile Systems, Applications, and Services (MobiSys), 415–426. ACM, 2021.
  2. Chen, Chieh-Chun, Chia-Yu Chang, and Navid Nikaein. "FlexSlice: Flexible and Real-Time Programmable RAN Slicing Framework." In IEEE Global Communications Conference (GLOBECOM), 3807–3812. IEEE, 2023.
  3. Chen, Yongzhou, Ruihao Yao, Haitham Hassanieh, and Radhika Mittal. "Channel-Aware 5G RAN Slicing with Customizable Schedulers." In 20th USENIX Symposium on Networked Systems Design and Implementation (NSDI 23), 1767–1782. USENIX Association, 2023.
  4. Kak, Ahan, Van-Quan Pham, Huu-Trung Thieu, and Nakjung Choi. "ProSLICE: An Open RAN-Based Approach to Programmable RAN Slicing." In IEEE Global Communications Conference (GLOBECOM), 197–202. IEEE, 2022.
  5. Balasingam, Arjun, Manikanta Kotaru, and Paramvir Bahl. "Application-Level Service Assurance with 5G RAN Slicing." In USENIX Symposium on Networked Systems Design and Implementation (NSDI), 841–857. USENIX Association, 2024.