Romain Beurdouche
f3daf0ed83
1. nrLDPC_coding_segment_encoder: pointer not aligned on 64 bits An undefined behavior was happening because of a shift on a __m64 which was actually a uint32_t which was not aligned on 64 bits. This commit suggests a fix by properly loading into a __m64 with _mm_set_pi32 before performing the shift. 2. nr_rate_matching: Filler bits detection Previously, if the bit selection was reaching Ncb and restarting selection from the beginning of encoded data, the filler bits were detected by testing the bytes again NR_NULL which was equal to 2. But on this branch the bits of up to 8 segments are stored in one byte while doing rate matching so that one byte could be tested to be a filler while it is not. So this commit changes the way to test filler bits. Instead of relying on NR_NULL, bit selection now relies on the offset and size of filler bits. 3. nr_ulsch_coding: missing filling f with zeros The array `f` of the UE UL HARQ process was not filled with zeros between transmissions. This is a problem if the encoder does not properly overwrite its output. In order to avoid such situation, this commit adds a memset to fill `f` with zeros before passing it to the encoder. 4. nrLDPC_coding_segment_encoder: missing init of f to zeros In the encoder, `f` is not filled with zeros before being used. `f` is instead somehow filled with arbitrary values. When writing to `output` by 64 bit vectors, some arbitrary bits may be added after the segment. Then the arbitrary added ones are not overwritten when writing the next segment because of writing with a logical or. This commit properly fills `f` and `f2` with zeros. 5. nr_ulschsim & nr_dlschsim: Adapt modulation to new encoder output The QPSK symbols that are feed to the channel model of nr_dlschsim were determined based on the bytes of the encoder output. With the new output of the encoder, it had to be reworked to determine the QPSK symbols based on the bits of the encoder output.
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.