Jaroslava Fiedlerova
5312e9e43b
Convert physim testcases defined in cmake_targets/autotests/test_case_list.xml into CTest based tests. These test are activated when '-DENABLE_PHYSIM_TESTS=ON' CMake flag is set. Note: Tests for dlsim_tm4 are excluded, due to compilation issues. CTest evaluates success based on return code: '0' = pass, non-zero = fail. The following table outlines the physim executables, their success expressions (`expr_true`), and the return codes for success (`ret_success`) and failure (`ret_fail`). The `expr_true` is used in test_case_list.xml to check for test results. | test_exec | expr_true | ret_succ | ret_fail | | ------------- | -------------- | --------------- | ----------------- | | dlsim | passed | 0 | -1 | | ulsim | passed | 0 (ret) | 1 (ret) | | ldpctest | BLER 0.000000 | 0 | 1 | | polartest | BLER= 0.000000 | 0 | 1 | | nr_pbchsim | PBCH test OK | 0 | 1 | | nr_dlsim | PDSCH test OK | 0 | 1 | | smallblocktest| BLER= 0.000000 | 0 | 1 | | nr_ulschsim | PUSCH test OK | 0 (n_errors) | n_errors | | nr_pucchsim | PUCCH test OK | 0 | 1 | | nr_ulsim | PUSCH test OK | 0 (ret) | -1 (ret) | | nr_prachsim | PRACH test OK | 0 (prach_errors)| > 0 (prach_errors)| | nr_psbchsim | PSBCH test OK | 0 (errors) | > 0 (errors) | Add CMake flag "ENABLE_PHYSIM_TESTS=ON" when building OAI with "-P" or "--phy_simulators" option. This allows physim-related ctest to be executed from build directory. Add dependency on coding lib for all 4G physims
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.