General Information
O-RAN Distributed Unit Low Layers ( |
|---|
...
O-DU LOW) | |
|---|---|
PTL | |
...
@Farias Luis | |
Summary | Focus on L1 functional |
...
Quick Explore
General Introduction
The project include two parts contributions
part 1: O-RAN FH interface lib,
...
Weekly Meetings
...
FAPI TM lib and WLS lib. O-RAN FH interface lib which follow O-RAN WG4 interface to implement O-RAN radio interface from DU end, WLS and FAPI TM is the interface implementation between O-DU low and O-DU High.
part 2: L1 binary along with one set of uses cases which were performed with test MAC application.
With above parts, below O-RAN network functions can be verified with different data flow to meet your different purpose:
data flow 1: FH lib UT, FH lib had it's own test framework, which includes one test app to simulator the l1 and test RU to simulator the RU, between test app and test RU, data was exchanged follow O-RAN WG4 C/U/S plane spec. there are multiple use cases that are defined with variant numerology and bandwidth.
data flow 2: RRU interface UT, the test app and FH lib can also be used to test real RRU with simulated L1 data connecting to SA/SG
data flow 3: testmac timer: L1 binary and test mac timer mode was provided to verify the FAPI interface with full L1 pipeline/functionalities , it also can be used to verify the HW platform supportive of the L1 SW with proper capabilities.
data flow 4: testmac radio: With full L1 pipeline integrated FH lib, this data flow can be used to verify the RRU with full L1 pipeline.
data flow 5: E2E open source: together with other open source project in OSC, E2E data flow can be verified, please go to Integration and Testing and Requirements and Software Architecture Committee Home for detail E2E integration current status and plan.
below picture shows the architecture and the interface of O-DU low. this project
...
mainly focus on the open interface development so far, three interfaces will be involved to interact with
...
L1.
Interfaces:
Interface between L1 and Front haul, it will adopt the WG4 specification for the CUS plane communication.
Interface between O-DU Low and O-DU High, FAPI interface will be adopt according to WG8 AAL specification.
Interface between O-DU Low and accelerator, it's the hot topic in WG6 now, DPDK BBDev was adopted as
...
current design, it
...
follow the
...
For amber release, O-RAN FH library was contributed by Intel as seed code, BBDev API was already open source in DPDK community, please find detail API information in http://doc.dpdk.org/api/rte__bbdev_8h.html, FAPI API is under development.
O-RAN FH Lib is developed according to the O-RAN WG4 specification. It performs communication between the lower-layer split Central Unit (lls-CU) and RU and consists of multiple HW and SW components. Logical representation of HW and SW components is shown as below diagram:
From the hardware perspective, two networking ports are used to communicate to the Front Haul and Back (Mid) Haul network as well as to receive PTP synchronization. The system timer is used to provide “sense” of time to the gNB application.
From Software perspective the following components are used:
...
- Ptp4l is used to synchronize oscillator on Network Interface Controller (NIC) to PTP GM.
- Phc2sys is used to synchronize system timer to oscillator on NIC.
...
O-RAN WG6 specification.