- 11 Sep, 2023 3 commits
-
-
Robert Schmidt authored
-
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
-
- 08 Sep, 2023 28 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
-
Robert Schmidt authored
-
Robert Schmidt authored
Before this commit, we did not read the ServingCellConfigCommon (SCC) completely at start; rather, we read most (but not all) of it, then also the minRXTXTIME, and at RRC initialization in openair_rrc_gNB_configuration(), we filled the pusch-TimeDomainAllocationList into the SCC, depending on the minRXTXTIME. The reason might be that we read part of the SCC, use that to fill the NRRRC_CONFIGURATION_REQ, read also the minRXTXTIME (part of the RRC config), and then we have all we need to "finalize the SCC". Since we move everything to the MAC, I avoid too much upfront code changes, hardcode the minRXTXTIME (and check with an assert), and undo this in a later commit when the "RRC config" relevant for radio parameters, e.g., minRXTXTIME, is moved to MAC. I verified the equality of the SCC before (at the end openair_rrc_gNB_configuration()) and after (at the end of get_scc_config()) this commit manually using a printf, assuming that after RRC initialization, we didn't do any further modifications to the SCC. But in fact, I cannot know that we don't do it...
-
Robert Schmidt authored
- Simplify code by reading the SCC in a separate function - Fill the F1 Setup Request message correctly in case of FDD, from SCC
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
This branch series implements the usage of the F1 Setup Request internally at the gNB, even if CU and DU run in the same process. Until now, the F1 Setup Request contained struct fields to pass IP configuration to the F1AP module; this information is not necessary in monolithic, nor should it be relevant when passing the information in F1 Setup Request. Therefore, this commit moves all IP connection-related information out of the F1 Setup Request and into a separate structure instead. In order to give the F1AP module the necessary connection information, the DU_REGISTER_REQ message is introduced that combines the F1 Setup Request and IP configuration, such that the F1AP module can setup the SCTP connection and then send the F1 Setup Request message. In a later commit, there will be a callback for F1 Setup Request at MAC to simply register the DU at the CU. The monolithic callback will simply forward the F1 Setup Request The F1AP callback will look up the IP configuration and create DU_REGISTER_REQ message containing IP configuration and F1 Setup Request, which is then handled by the F1AP module. To this end, a separate function in gnb_config.c allows to read IP information from configuration.
-
Robert Schmidt authored
-
Robert Schmidt authored
Instead of storing the F1 Setup Request implicitly in F1 context, we provide the F1 Setup Request message to be encoded explicitly to the encoding function.
-
Robert Schmidt authored
We ever only have one instance, so hard code that.
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
In the case of MIMO, we reused memory to point to the same PUCCH resource. This is problematic, since ASN_STRUCT_FREE() would try to free this resource twice. This commit changes to create distinct memory for the PUCCH resources, while putting the same configuration to still use the same PUCCH resource from a radio configuration point of view.
-
Robert Schmidt authored
-
- 30 Aug, 2023 1 commit
-
-
Robert Schmidt authored
integration_2023_w34 See merge request oai/openairinterface5g!2316 * !2283 going back to sync mode when cell is barred in MIB * !2290 fix gtp delete. we should not delete all bearer in case of dedicaded bearer release * !2299 fix-mem-overflow_64qam * !2288 NR UE avoid crashes upon renewal of SIB1 * !2279 web server enhancement and doc link fix * !2302 Tutorials: update links for Open Cells SIM Card programming tool and Ubuntu 22.04 LTS * !2303 NR gNB limit on PUCCH bits to be scheduled * !2207 Use F1 internally: UE Context Modification Required * !2315 Fix LCID to RB association, allow more than 8 LCIDs in the UE
-
- 29 Aug, 2023 3 commits
-
-
Robert Schmidt authored
Merge remote-tracking branch 'origin/fix-lcid2rb-index-error-and-missing-lcid-greater-than-8' into integration_2023_w34
-
Laurent THOMAS authored
-
Robert Schmidt authored
-
- 27 Aug, 2023 1 commit
-
-
Robert Schmidt authored
-
- 24 Aug, 2023 4 commits
-
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-