Integration: `2026.w22` * !4140 Fix evaluation of PMI and CQI report when there is no RI report * !4125 fix(phy): prevent division by zero in nr_csi_rs_pmi_estimation * !4134 Add SRS LS and RSRP measurement logging for indoor positioning research * !4086 vrtsim: Refactor peer antenna configuration and taps_client * !4108 XNAP: Add encode/decode+unit tests for Xn HO Ack, Prep Failure, SN Status Transfer, UE Context Release * !4096 O-RU fronthaul library * !4147 1-port CQI report * !4133 fix(config): fix memory safety, memory leaks, and add unit test coverage * !4084 gold_cache: replace linear search with open-addressing hash table * !4150 fix a few issues with unit tests * !3827 Antenna port indexing of txdataF using FAPI spatial stream indices * !4138 \[FHI72\] \[M-plane\] Implement dynamic compression * !4144 fix(fhi72): Fix use-after-free bug in fhi_72 lib * !3890 Fixes for multiplexing pattern 3 operations in FR2 * !4145 fix(vrtsim): handle CLOCK_REALTIME jump after PTP sync * !4151 minor: fix nr rlc test make-based compilation * !4141 wrong usage of extern declaration in C files, header cleanup * !4153 doc: update 7.2 tutorial hardware and os configuration and add a doc to list supported hardware and OS * !4066 Separate nfapi_p5.c into LTE and NR implementations * !4098 \[CI OAI-FlexRIC\] Improve CI pipeline * !3723 Support for aperiodic SRS at gNB * !4076 Fix imscope and tracy build * Fix the undefined `res` parameter if not defined K_RELEASE * CI: Adjust timing thresholds in RAN-gNB-N300-Timing-Phytest-LDPC * !3553 Add automated FHI72 4x4 nightly testing * !4142 CI: Cleanup of Jenkinsfiles and parameters * Adjust do_SRS after merge of !3723 Closes #1086, #1097, #1022, and #1076 See merge request oai/openairinterface5g!4146
OpenAirInterface License
The source code is distributed under CSSL v1.0. Some files, such as for orchestration, are distributed under MIT license(MIT.txt). Documentation is distributed under Creative Commons Attribution 4.0 International license.
All the files without an explicit copyright header have an implicit "Copyright of OpenAirInterface Authors".
Please see NOTICE for other licenses which are used in the software.
In the past OAI source code has been re-licensed sometimes, here is the history:
- CSSL v1.0 starting tag 2026.w14
- OAI Public License v1.1 starting tag v1.0 till
af4b0d53 - OAI Public License v1.0: starting tag v.04 till v1.0
- GPL 3: starting tag v.0 till v.04 (only initial implementation of 4G)
Where to Start
- General overview of documentation
- The implemented features
- System Requirements for Using OAI Stack
- How to build
- How to run the modems
Not all information is available in a central place, and information for specific sub-systems might be available in the corresponding sub-directories. To find all READMEs, this command might be handy:
find . -iname "readme*"
RAN repository structure
The OpenAirInterface (OAI) software is composed of the following parts:
openairinterface5g
├── charts
├── ci-scripts : Meta-scripts used by the OSA CI process. Contains also configuration files used day-to-day by CI.
├── CMakeLists.txt : Top-level CMakeLists.txt for building
├── cmake_targets : Build utilities to compile (simulation, emulation and real-time platforms), and generated build files.
├── common : Some common OAI utilities, some other tools can be found at openair2/UTILS.
├── doc : Documentation
├── docker : Dockerfiles to build for Ubuntu and RHEL
├── executables : Top-level executable source files (gNB, eNB, ...)
├── maketags : Script to generate emacs tags.
├── nfapi : (n)FAPI code for MAC-PHY interface
├── openair1 : Layer 1 (3GPP LTE Rel-10/12 PHY, NR Rel-15 PHY)
├── openair2 : Layer 2 (3GPP LTE Rel-10 MAC/RLC/PDCP/RRC/X2AP, LTE Rel-14 M2AP, NR Rel-15+ MAC/RLC/PDCP/SDAP/RRC/X2AP/F1AP/E1AP), E2AP
├── openair3 : Layer 3 (3GPP LTE Rel-10 S1AP/GTP, NR Rel-15 NGAP/GTP)
├── openshift : OpenShift helm charts for some deployment options of OAI
├── radio : Drivers for various radios such as USRP, AW2S, RFsim, 7.2 FHI, ...
├── targets : Some configuration files; only historical relevance, and might be deleted in the future
└── tools : Tools for use by the developers/ci machines: code analysis and formatting
How to get support from the OAI Community
You can ask your question on the mailing lists.
Your email should contain below information:
- A clear subject in your email.
- For all the queries there should be [Query] in the subject of the email and for problems there should be [Problem].
- In case of a problem, add a small description.
- Do not share any photos unless you want to share a diagram.
- OAI gNB/DU/CU/CU-CP/CU-UP configuration file in
.confformat only. - Logs of OAI gNB/DU/CU/CU-CP/CU-UP in
.logor.txtformat only. - In case your question is related to performance, include a small description of the machine (Operating System, Kernel version, CPU, RAM and networking card) and diagram of your testing environment.
- Known/open issues are present on GitLab, so keep checking.
Always remember a structured email will help us understand your issues quickly.
