Laurent THOMAS
d57ea715c0
- Ensure packed struct through bitfield - decoder tree buffer increase: i don't find evidence in the 3GPP standard of the max size of polar coded PDU. even with this max size, the way this tree is built is not trivial. so, it is hard to predict, i just put 8 system pages (32KB) that looks enough [1] - a lot of reformatting [1] https://arxiv.org/pdf/1804.04389 according to this paper, the largest polar code in 5G is in UL, so likely the biggest problem will be in gNB, not the UE. in DL, the max output coded block is 512, in UL 1024. probably the tree we discuss is related to this size. "frozen bits" means only bits we don't encode/decode because polar code size is only by power of 2. We see this in OAI code: NR_POLAR_PUCCH_N_MAX is 10, so 2^10 is 1024, that is the maximum size for 5G polar code length. in the code, we assert if N > 512: "N = %d, not done yet\n", polarParams->N". so, the today OAI code can't do PUCCH large blocks. using current oai limitation of 2⁹ max code size, we can create up to 2^9+2⁸... nodes, so 1023 nodes in the tree. the problem then is that each node have variable size, depending on the 'level' (the power of 2 we are currently). the algo provision large alpha and beta to be able to store all lower levels in the tree (int leaf_sz = 1 << level) therefore upper tree nodes are large (the top level for n=9 uses about 1.5KB) and the bottom nodes uses 64 bytes. if all nodes are populated, the size will be very large: 1.5KB + 2 * 800 + .... but, we create nodes in the tree only for the "information bits", so the payload, that is limited to 128 bits (else we assert, the code is not "finished"). 1.5KB * 128 is >> 8KB i allocated. but, we can't create more than one mode at top level, so there is maximum 1.5KB + 2 * 800, + 4 * 400 + 8 * 200 + 16 * 100 + remaining of 128-32 nodes of 64 bytes. about 14KB. i allocated 1024*sizeof(__m256i) bytes = 32KB that looks good.
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.