An error occurred fetching the project authors.
- 25 Oct, 2023 2 commits
-
-
Robert Schmidt authored
-
Robert Schmidt authored
-
- 02 Oct, 2023 1 commit
-
-
Robert Schmidt authored
- Currently no fields to store DRB release: need persist in ASN structure - This will be revisited once there is E1 bearer release release
-
- 22 Sep, 2023 9 commits
-
-
Robert Schmidt authored
-
Robert Schmidt authored
- store the assoc ID of a UE at the RRC - if F1 receives an SCTP shutdown, it removes the endpoint - F1 will also send an "F1 Lost Connection" message to the RRC - it is not yet possible to reconnect a DU after it had already been connected at the CU, since the CU F1AP task will try to rebind GTP, which fails
-
Robert Schmidt authored
- Forward UE capabilities in F1 handlers - Store at MAC - Update CellGroupConfig with UE Capabilities of the UE
-
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
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
- 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
-
Robert Schmidt authored
-
- 14 Aug, 2023 1 commit
-
-
Robert Schmidt authored
-
- 12 Aug, 2023 2 commits
-
-
Robert Schmidt authored
-
Robert Schmidt authored
This commit repairs the reestablishment after the introduction of the CU UE ID in the CU, different from the DU UE ID. Now, the CU uses an identifier different from the RNTI, used in the MAC, to refer to UEs. To repair the reestablishment, a number of changes needed to be introduced: - Handle old_gNB_DU_UE_id in MAC The MAC handles the old_gNB_DU_UE_id field in the DL RRC Message. The commit adds encoding/decoding of the field. The MAC will drop the old UE, but retain the CellGroup of the corresponding UE(!). Because a UE releases the spCellGroup on reestablishment, the MAC does the same; it needs to reapply the old configuration after a reconfiguration. For the latter, introduce new variables to keep a "future" CellGroupConfig to be applied (reconfigCellGroup) and a flag (expect_reconfiguration) that applies the CellGroupConfig if a DL RRC Message transfer on DCCH, which is assumed to be the reconfiguration. - Add RNTI change in RLC The RLC needs to reuse the old UE context. Hence, we simply change the RNTI in the old context, and delete the new one. - No PDCP UE ID change The previous implementation of the PDCP used the RNTI; hence, the ID needed to be switch (as above for the RLC). Since the PDCP now also uses the CU UE ID, no identifier change is needed, and we remove all corresponding code. - No MAC modifications/update from CU As foreseen by the spec, the CU does not modify or change the cellGroupConfig in the RRC during reestablishment. This change will be generalized in the future to all of the RRC. Also, the nr_rrc_mac_remove_ue() function has been removed: the MAC handles any UE changes autonomeously, without being triggered from the RRC explicitly. - Remove reestablish_rnti_map The RRC does not use RNTIs for UE identification. Hence, a reestablish_rnti_map to link two UEs to each other is not necessary anymore.
-
- 11 Aug, 2023 4 commits
-
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
The RRC uses gNB_ue_ngap_id as its primary ID; the following commits will introduce the usage of the (F1) gNB CU UE ID. This commits renames the gNB_ue_ngap_id to rrc_ue_id to better reflect its usage as the RRC's primary UE ID. It will be used as the NGAP and F1 (CU) UE IDs.
-
Robert Schmidt authored
-
- 28 Jul, 2023 1 commit
-
-
Cedric Roux authored
-
- 26 Jul, 2023 1 commit
-
-
Cedric Roux authored
-
- 08 Jul, 2023 1 commit
-
-
Laurent THOMAS authored
-
- 13 Jun, 2023 1 commit
-
-
General ABS authored
-
- 29 May, 2023 1 commit
-
-
laurent authored
-
- 26 May, 2023 1 commit
-
-
Robert Schmidt authored
-
- 25 May, 2023 2 commits
-
-
Robert Schmidt authored
There are a number of timers in RRC. Those are not or only partially implemented, and certainly don't work in F1. Hence, remove them to replace with a better implementation later.
-
Robert Schmidt authored
-
- 08 May, 2023 1 commit
-
-
francescomani authored
-
- 03 May, 2023 1 commit
-
-
Robert Schmidt authored
-
- 28 Apr, 2023 1 commit
-
-
laurent authored
-
- 11 Apr, 2023 3 commits
-
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
- 05 Apr, 2023 1 commit
-
-
Angelo Athanassopoulos authored
-
- 03 Apr, 2023 1 commit
-
-
Angelo Athanassopoulos authored
Added struct member to gNB_RRC_UE_t to store the established DRBs for a UE, this can be used to generate ASN1 structs, during RRCReconfiguration
-
- 23 Mar, 2023 1 commit
-
-
Robert Schmidt authored
-
- 10 Mar, 2023 1 commit
-
-
Luis Pereira authored
-
- 09 Mar, 2023 1 commit
-
-
laurent authored
-