02) End-to-end system performance testing and functional sub-system pairing testing of Baicells 5G NR O-RU and QCT/Wind River/Altran 5G NR O-DU/O-CU in connection

Companies Participating
in this Scenario

Baicells provided 5G NR O-RU (hardware and software) and High-PHY (a portion of physical layer (layer 1) on O-DU side).

QCT provided server (HW) for O-DU/O-CU.

Wind River provided the cloud platform for O-DU and O-CU.

Altran provided 5G NR standalone O-DU and O-CU (layers 2 and higher).

VIAVI Solutions provided 5G NR Core emulator and UE emulator


Testbed setup

The connection details of the hardware in the lab are in the network topology diagram below.


Device Under Test
Baicells 5G NR pico O-RU

  • Radio: 5G NR TDD
  • Model: Gama-632
  • Antenna: 4T4R (2x2 / 4x4 MIMO)
  • Output power: 250mW (single channel)
  • Management plane: Netconf/YANG (M-plane/O1 not supported)
  • Fronthaul Interface: O-RAN 7-2x split (Cat A)
  • External Interface: NA
  • Channel Bandwidth: 100MHz
  • Frequency bands: n41, n77, n78 (FR1)
  • Frequency Synchronization: PTP (IEEE1588v2)
  • Dimensions: 280 x 280 x 60 mm, <4kg

Baicells/Altran 5G NR O-DU/O-CU (software)

  • Management plane: Netconf/YANG (O1 not supported)
  • Fronthaul Interface: O-RAN 7-2x split (Cat A)
  • Channel Bandwidth: 100MHz

QCT BBU Edge Server QuantaGrid D52Y-2U

  • Radio: QuantaGrid D52Y-2U
  • Model: QuantaGrid D52Y-2U
  • Chassis: 2RU
  • Processor: 2 x Intel Xeon-Gold 624820c
  • Memory: 8 x 32GB DDR4-2666 (256GB in total)
  • Storage: 2 x 960GB SSD
  • Network (NIC):
    • 2 x Intel X710-DA2
    • 1 x Intel X710-DA4
    • 1 x Baicells TAC (Timing and Acceleration Card)
  • Dimensions: 447.8 x 420 x 86.3 mm

Baicells Timing and Acceleration Card

  • PCI Express full-height and 3/4 length card
  • Power supply: 6-pin power connector, 12V DC input
  • Ports:
    • 6 x 25G SFP28 connectors
    • PCIe Gen3 x 16 edge connectors

Wind River Cloud Platfrom (CaaS software)

  • Software version: Wind River Cloud Platform 20.06
  • Real time/low latency OS: CentOS 7 tuned kernel as part of StarlingX open source project
  • Kubernetes version: 1.18
  • Storage SW: Ceph
  • O-Cloud deployment: Kubernetes controller, worker and storage functions all hosted on a single QCT QuantaGrid D52Y-2U server providing HW acceleration and suitable resource allocation for the O-CU and O-DU applications from Altran and Baicells.

Test scenarios introduction

End-to-end testing of Baicells 5G NR O-RU connected over O-RAN Open Fronthaul (7-2x split) to Baicells/QCT/Wind River/Altran O-DU/O-CU using VIAVI 5G NR core emulator, VIAVI E500 UE emulator, and Smartphone Huawei P40 Pro (as real test UE). The setup is based on 5G NR standalone architecture (using 5G network for both signalling and data transfer).

UE E2E multiple attach/detach with Physical Handset (5 times)

The purpose of this test is to validate that UE can register to the network via O-RU and O-DU/O-CU, and the 5G NR core emulator assigns an IP address after the successful RRC and NAS messages exchanges. The UE detaches in cases where UE must leave the cell area due to any possible reasons, for example, turn on airplane mode.

Testing Results/Summary

In this test, Baicells O-RU connects over O-RAN Open Fronthaul 7-2x split to Baicells/QCT/Wind River/Altran O-DU/O-CU. The scenario focuses on the end-to-end 5G NR signal call flow.

Based on the logs from real test UE, the UE can attach to the network, sets the PDU session up, and transfer data in uplink as well as in downlink directions.

Benefits for the Industry

  • The validated end-to-end interoperable O-RAN O-RU/O-CU/O-DU with Baicells, QCT, Wind River and Altran solutions.
  • The validated multi-vendor solution in the case of O-RAN Open Fronthaul 7-2x split (Cat A).
  • The validated COTS hardware with the hardware acceleration for both O-CU and O-DU on a real time O-Cloud (CaaS) SW platform.
  • The validated VIAVI UE emulator for the end-to-end O-RAN performance tests.
  • The validated real commercial 5G SA UE for the end-to-end O-RAN performance tests.
  • The validated remote integration in Berlin lab without on-site support from any of the O-RU, O-DU and O-CU provider.