An error occurred fetching the project authors.
- 15 Apr, 2024 3 commits
-
-
Robert Schmidt authored
Some reasoning as in previous commit.
-
Robert Schmidt authored
Same reasoning as in the previous commit. Remove filling of broadcast_plmn, which does not exist in the configuration.
-
Robert Schmidt authored
-
- 13 Apr, 2024 1 commit
-
-
Robert Schmidt authored
After the last commit, it is not possible to bind on separate interfaces for F1-C and F1-U. In other words, it is for instance not possible to have the F1-C on one subnet on one physical interface, and F1-U on another subnet on another physical interface. This commit introduces a second option MACRLCs.[0].local_n_address_f1u to allow to bind F1-U on an alternative address; if it is not specified, the interface of F1-C is reused. The above only works for the DU; no corresponding option exists for the CU. For the CU, use separate CU-CP and CU-UP. Use it in the CI.
-
- 08 Mar, 2024 1 commit
-
-
Rúben Soares da Silva authored
- Aerial config file - Changes for ARC1.1. Change config file to max MCS 25. Fixed pdu size errors. - Remove taskset from Dockerfile.gNB.aerial.ubuntu20 after changing isolated CPUs - removed the USRP from Docker file Co-authored-by:
Florian Kaltenberger <florian.kaltenberger@eurecom.fr> Co-authored-by:
Fredrik Molander <fmolander@nvidia.com> Co-authored-by:
Reem Bahsoun <reem.bahsoun@openairinterface.org>
-
- 06 Mar, 2024 1 commit
-
-
Laurent THOMAS authored
-
- 08 Feb, 2024 1 commit
-
-
francescomani authored
-
- 23 Jan, 2024 1 commit
-
-
Robert Schmidt authored
For 7.2 FH, some RUs do phase compensation, whereas for others, the DU does it. In fact, this can be "negotiated" using the M plane. Since we don't have the M plane yet, add a configuration option to set where phase compensation is performed.
-
- 18 Jan, 2024 2 commits
-
-
Giulio Carota authored
RRC Version is a required IE. Hence, implement the encoder and decoder for this message. At the DU and CU, read the RRC Version we use and fill the corresponding field. Co-authored-by:
Robert Schmidt <robert.schmidt@openairinterface.org>
-
Robert Schmidt authored
In NSA, we don't have SIB1. However, the DU system information requires both MIB and SIB1, but is itself optional. So, in NSA, don't fill the DU system information.
-
- 17 Jan, 2024 1 commit
-
-
Teodora authored
-
- 17 Dec, 2023 1 commit
-
-
francescomani authored
-
- 12 Dec, 2023 1 commit
-
-
francescomani authored
-
- 30 Nov, 2023 5 commits
-
-
Robert Schmidt authored
The node ID (which corresponds to the gNB ID) should be read in all cases of execution, not only CU.
-
Robert Schmidt authored
The macrlc_has_f1 (static) variable was introduced to signal when we use F1 in the configuration. It is superfluous: the node_type already passes this information in a unique manner; hence, remove.
-
Robert Schmidt authored
This commit introduces an additional (implicit) option that signals if the E2 agent is to be activated or not. When reading the configuration, we now check if all fields are set, and activate the E2 agent only if this is the case. If not, we only print a warning and start the gNB without the agent. Note that previously, if not all fields are set correctly, the gNB stopped. To implement this behavior, it is necessary to change the defaults of the RIC IP and the directory for SMs to a (non-NULL) default value. Otherwise, the configuration system would not consider the field to be set to the default, and wrongly assumes the field is set, even though it is not; at least, this change is necessary to make config_isparamset() return NULL if the configuration is not set.
-
Robert Schmidt authored
3GPP has the concept of a gNB-DU ID and a (separate) gNB ID (for gNB, CU). This commit introduces the gNB-DU as a separate ID that has to be set in the configuration file. It is necessary, as some entities, e.g., the e2 agent, need to signal both IDs, e.g., to reconcile a CU and (multiple) DU(s) belonging together.
-
Robert Schmidt authored
-
- 20 Nov, 2023 1 commit
-
-
luis_pereira87 authored
-
- 10 Nov, 2023 1 commit
-
-
Laurent THOMAS authored
-
- 31 Oct, 2023 2 commits
-
-
Sakthivel Velumani authored
-
Sakthivel Velumani authored
The NSSAI of PDU sessions coming from AMF are stored in RRC to be sent to lower layers
-
- 27 Oct, 2023 2 commits
-
-
rmagueta authored
-
Robert Schmidt authored
Until this commit, the SIB1's PDCCH_configCommon was set (via a pointer, i.e., an indirection) to the one of the ServingCellConfigCommon (SCC). Afterwards, the SIB1 code further populated this PDCCH configCommon, indirectly populating the one of the the SCC, on which code later depends. Not only did this create possibilities for double-frees (since freeing the memory of SIB1, then SCC would free the PDCCH configcommon twice), but also it makes it harder to track where certain structures are populated. Hence, this commit solves both issues: - The SCC is correctly populated on initialization of the SCC - The SIB1 makes a deep copy of the SCC' PDCCH configCommon This resolves the two issues above.
-
- 25 Oct, 2023 2 commits
-
-
Robert Schmidt authored
-
Robert Schmidt authored
-
- 22 Sep, 2023 12 commits
-
-
Robert Schmidt authored
-
Robert Schmidt authored
In NSA case: do not send SIB1
-
Robert Schmidt authored
!SIB1 is not correctly filled! This commit does not work with COTS UEs! The next commit fixes this. - Move radio config (e.g., minRXTXTIME, SIB1 TDA, do_SRS, etc) down to MAC. - Some parameters in MAC are redundant: delete them. - Remove call to nr_mac_config_scc() from RRC and simulators, the MAC initialization routine calls it implicitly
-
Robert Schmidt authored
Previously, filling of F1 Setup Request depended on reading the RRC; hence, for timing reasons, we only initialized and sent the F1 Setup Request once the MAC and RRC are ready. After moving SCC, SCD, MIB, and SIB1 to MAC, the MAC does not depend on an RRC being present anymore, and hence, the F1 Setup Request does neither. In this commit, we read the F1 Setup Request after initializing the MAC.
-
Robert Schmidt authored
The SystemInformationBlock 1 is handled at the DU and sent to the CU in the F1 Setup Request. Hence, move it down to the MAC.
-
Robert Schmidt authored
The MasterInformationBlock is handled at the DU and sent to the CU in the F1 Setup Response. Hence, move it down to the MAC. Furthermore: - Change type because MIB_PDU_t is 4G type - Simplify schedule_nr_mib()
-
Robert Schmidt authored
-
Robert Schmidt authored
As with the ServingCellConfigCommon, the ServingCellConfigDedicated is a radio-related structure to be handled at the DU.
-
Robert Schmidt authored
Note: the reestablishment is broken, and a later commit fixes it. The ServingCellConfigCommon is an inherently radio-related configuration. As such, it should be handled by the DU, not the CU. Therefore, move it "down" to the MAC.
-
Robert Schmidt authored
The PCI is given to the CU from the DU in the F1 Setup Request message. It is a part of the DU, so move it "down".
-
Robert Schmidt authored
The F1 Setup Response contains the cell(s) to activate. Hence, prevent the radio from starting by waiting for the F1 Setup Response before continuing.
-
Robert Schmidt authored
- send F1 Setup using callback - store f1 setup req locally for reference - check F1 Setup Req against RRC data structures: * if matches: send F1 Setup Response using callback * if not matching: send F1 Setup Failure using callback - don't send CU config update by default, we don't need this - if the Setup Response does not contain a cell, don't activate. It is possible the CU sends a gNB-CU configuration update, which will initialize the structures
-
- 21 Sep, 2023 2 commits
-
-
Robert Schmidt authored
Use a struct to initialize the RRC at the beginning, and remove the NRRRC_CONFIGURATION_REQ. This message is not necessary; the RRC/CU should be initialized from the F1 Setup Request, coming from the DU.
-
Robert Schmidt authored
-