Guido Casati
8209dcb5d9
RRC now builds F1AP paging messages directly by calling F1AP/direct callbacks and aligning the CU/DU intergace with the F1AP design in the CU. Messages are forwarded based on TAI-based cell matching across DUs. - Remove F1AP_PAGING_IND message def and f1ap_paging_ind_t. RRC no longer sends ITTI F1AP_PAGING_IND; it builds f1ap_paging_t and passes it to the DU path. - rrc_gNB_process_PAGING_IND: new signature (rrc, instance, msg) with const where appropriate; call in rrc_gnb_task() updated. - NGAP handler logic: For each TAI, match (PLMN + TAC) to rrc->configuration; collect matching TAIs. Build one f1ap_paging_t (5G-S-TMSI via nr_construct_5g_s_tmsi(), identity type F1AP_PAGING_IDENTITY_CN_UE, optional drx/priority/origin copied from ngap_paging_ind_t), call rrc_send_paging_to_dus(), then free_f1ap_paging(). Remove the previous AssertFatal stub, CC loop, NODE_IS_CU branch, and UE lookup logic: it is now handled by F1AP/direct CU callbacks. - rrc_gNB_du: Add rrc_send_paging_to_dus(rrc, tais, n_tai, msg). Iterate DUs with RB_FOREACH; for each DU, fill msg->cells from du->cells whose (PLMN + TAC) matches any requested TAI, set n_cells, then call rrc->mac_rrc.paging_transfer(du->assoc_id, msg). Skip DUs with no matching cells. Prevents duplicate paging when multiple TAIs map to the same PLMN.
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.