How intel/flexran works
Project type and purpose
• This is Intel’s FlexRAN 5GNR Reference PHY project, providing a real‐time Layer-1 (L1) implementation (l1app) and a Test MAC application (testmac) for functional and performance validation of 5GNR PHY features on Intel® Xeon® platforms.
• It also includes a FAPI interface container (oran-fapi) for O-RAN integration.
File structure
• Top-level directories:
• docker/ → Dockerfile, build scripts, Kubernetes pod manifest (multi-container Pod: l1app, oran-fapi, testmac)
• l1/ →
– bin/nr5g/gnb/l1/ → L1 binaries, XML configs, lookup tables
– bin/nr5g/gnb/testmac/ → testmac binaries and configs
– source/ → C/C++ headers and code implementing PHY and API layers
• libs/cpa/ → DPDK BBDev drivers (cpa_drv.ko, mmwcpa_drv.ko) for SW/FPGA FEC offload
• sdk/ → prebuilt phy algorithm libraries with lookup-table binaries (e.g., ce_type1_w_sinc.bin)
• testcase/ → reference IQ samples and XML config files for DL, UL, FD test cases
• Key patterns:
• Layered modular code (hardware interface → PHY algorithms → API → test orchestration)
• Containerized deployment with shared volumes (HugePages, DPDK socket)
• Kubernetes resource isolation for real-time tasks
README for insights
• L1 application supports private and FAPI interfaces (FAPI v222.10.02).
• Testmac application orchestrates DL/UL/FD tests: feeds UL IQ to PHY, receives DL IQ, compares results.
• Deployment modes: bare-metal (real-time tuned CentOS 7 + hugepages + DPDK) or containerized (Docker + Kubernetes).
• Resource requirements: l1app (16 GiB + 2 GiB 1GiB hugepages), oran-fapi (4 GiB + 4 GiB hugepages), testmac (4 GiB).
Detail
• Entrypoint scripts (l1.sh, oran_5g_fapi.sh, l2.sh)
• Lookup-table directories under sdk/ and l1/bin
• Resource limits (Memory, HugePages)
• SW vs FPGA FEC offload path via DPDK BBDev driver