Jaroslava Fiedlerova
0ba31c0f89
Integration `2026.w12` * !3985 Fix XNAP to avoid recompilation and unnecessary includes * !3724 Better c style pss sss * !3972 Resolve "Demote AssertFatal `PUCCH list is full` message to a warning" * !3956 [FHI72] [xran F] Revert and simplify the code for Liteon FR2 interoperability * !3970 Fix for NTN phy-test mode * !3987 T: minor: remove target record_db from automatic building * !3993 UE: Derive Serving Network Name from SIB1 PLMN * !3997 vrtsim doc: clarify container requirements * !3935 [FHI72] Fix long PRACH format * !3998 Set rxgain to 0 in vrtsim * !3964 CI: Add FHI7.2 phytest pipeline * !4001 Remove unused ci-scripts/mysql4testresults/ dir and content * !3999 bugfix: use proper pointer * !3986 handle start symbol on non-zeroth downlink symbol for SIB1 for multiplexing pattern 3 configuration. * !3957 replace static allocation of max antennas in a dynamic structure for gnb rach * !3859 Delay compensation in SRS * !3909 Adjust ssPBCH_BlockPower in FHI7.2 configs Closes #1058 See merge request oai/openairinterface5g!3989
OpenAirInterface License
It is distributed under OAI Public License V1.1.
The license information is distributed under LICENSE file in the same directory.
Please see NOTICE file for third party software that is included in the sources.
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.