|
"Making the OpenRAN Truly Open."
- Introduction
- Interoperability Issue in FAPI Interface
- xFAPI Architecture
- Need of xFAPI
- Current Status
- Additional Features
- References
- Acknowledgements
- Build & Run
xFAPI is an intermediate component that facilitates interoperability between L1s and L2s from different vendors. xFAPI acts as a translator, providing interoperability between different IPC mechanisms, including shared memory (xSM) and sockets (nFAPI).
Note
xSM is a comprehensive shared memory library supporting various shared memory mechanisms, enabling L1 and L2 vendors to exchange messages on a common platform.
Interoperability between Layer 1 (L1) and Layer 2 (L2) components in Open RAN remains a significant challenge despite the existence of the FAPI specification.
While FAPI provides a standardized interface for communication, different vendors implement it with slight variations in message formats, timing requirements, parameter interpretations, and optional features.
Complex Integration: L2-L3 vendors aiming to demonstrate interoperability with different L1s face the challenge of managing multiple intermediary components and shared memory libraries, one for each L1 vendor.
These inconsistencies lead to failures in message exchange, synchronization issues, and incompatibilities between L1 and L2 components from different vendors. As a result, seamless integration of multi-vendor solutions in Open RAN is hindered, limiting the flexibility and scalability that Open RAN promises.
xFAPI is an interoperable component designed to enable seamless connectivity between Layer 1 (L1) and Layer 2 (L2) components from different vendors, which are not inherently interoperable.
It acts as a bridge by facilitating communication across various inter-process communication (IPC) mechanisms, such as sockets and shared memory, while also providing translation between different API standards.
By eliminating vendor lock-in associated with the FAPI interface, xFAPI ensures a vendor-agnostic Radio Access Network (RAN) stack, enhancing flexibility and interoperability within the ecosystem.
-
As OCUDU L1 and OCUDU L2, xFAPI enables a FAPI-split deployment of the OCUDU stack, achieving full end-to-end connectivity within a homogeneous OCUDU stack.
- Topology: 3GPP-Compliant 5G Core + OCUDU CU + modified OCUDU L2 + xFAPI + modified OCUDU L1 + LiteON + COTS UE
-
xFAPI has successfully achieved end-to-end (E2E) connection between OSC DU-High and FlexRAN versions
v22.11andv23.07.- Topology: 3GPP-Compliant 5G Core + modified OAI CU + modified OSC DU-High + xFAPI + FlexRAN v22.11/v23.07 + LiteON
-
xFAPI fully supports the nFAPI interface at the L1 side, enabling a complete end-to-end connection between OSC DU-High and OAI L1.
- Topology: 3GPP-Compliant 5G Core + modified OAI CU + modified OSC DU-High + xFAPI + OAI L1 + LiteON + COTS UE
-
Dashboard Support: xFAPI includes an advanced dashboard that provides detailed statistics, PDU analysis, and debugging tools. It offers seamless integration with various OpenRAN vendors on a unified platform.
-
Simulation Mode: Vendors can test their components for compatibility with any of the supported L1 or L2 implementations without requiring physical access to them. xFAPI's simulation mode enables comprehensive interoperability testing in a virtualized environment.
| Topic | Type | Links |
|---|---|---|
| xFAPI Release 2.1 | Video | Watch |
| Introduction to xFAPI | Video | Watch |
| xFAPI Proposal | Presentation | View |
| Recording | Watch | |
| xFAPI Blueprint | Presentation | View |
| Recording | Watch | |
| xFAPI with OCUDU | Video | Watch |
| Blog | Read | |
| Documentation | View | |
| xFAPI Deployment Guide – O-RAN-SC K-Release | Documentation | View |
| xFAPI Deployment in O-RAN-SC Lab, Taiwan | Video | Watch |
In addition, we would like to thank the open source projects that helped the development of xFAPI:






