- 06 May, 2024 1 commit
-
-
Jaroslava Fiedlerova authored
-
- 05 May, 2024 2 commits
-
-
Jaroslava Fiedlerova authored
-
Jaroslava Fiedlerova authored
-
- 03 May, 2024 7 commits
-
-
Laurent THOMAS authored
This has no meaning at a global level, we run several slots: one tx, several rx at same time. Some minor cleaning of C style
-
Laurent THOMAS authored
-
Laurent THOMAS authored
The external declarations were incorrect, leading to mismatching prototypes of config_ru and config_rru (true bug in OAI lte!).
-
rmagueta authored
-
rmagueta authored
-
rmagueta authored
-
Jaroslava Fiedlerova authored
-
- 02 May, 2024 2 commits
-
-
Jaroslava Fiedlerova authored
-
Jaroslava Fiedlerova authored
For docker version > 25.0.5, "version" field is not relevant and reported as obsolete.
-
- 01 May, 2024 2 commits
-
-
francescomani authored
-
francescomani authored
-
- 30 Apr, 2024 11 commits
-
-
Robert Schmidt authored
Integration `2024.w17` See merge request oai/openairinterface5g!2702 * !2659 NR bandwidth index fix * !2693 Harmonize frequency range structures * !2699 Add support for USRP X410 to run with 200 MHz bandwidth in FR2 at 120 kHz SCS * !2692 Fix for the overflow issue while processing GPS based timestamp from RU * !2665 NR UE improvements in handling RRC Release * !2682 dci11type0 * !2686 CI: Maintenance, fixes, improvements * !2677 NR UE trigger RA for SR failure * !2683 Ue small fixes * !2668 Refactor PDCP Reestablishment and introduce PDCP Suspend at gNB * Add rhel9.4 to the list of OAI supported distributions * !2673 speedup integrity computation * !2706 doc: Update of CI testbenches
-
francescomani authored
-
Robert Schmidt authored
-
Jaroslava Fiedlerova authored
-
Jaroslava Fiedlerova authored
-
Jaroslava Fiedlerova authored
-
Jaroslava Fiedlerova authored
-
Jaroslava Fiedlerova authored
-
Guido Casati authored
- according to clause 5.3.7.2 of 3GPP TS 38.331 PDCP Suspend is not required during RRCReestablishment
-
Guido Casati authored
- according to 5.3.7.4 of TS 38.331: 1> re-establish RLC for SRB1; - gNB: 1) re-establish RLC for SRB1 in nr_rlc_update_id 2) re-establish RLC for remaining RBs concurrently with RRCReconfiguration issue: gNB) in nr_rlc_update_id the gNB is re-establishing RLC for all RBs at the same time when receiving RRCReestablishmentRequest from UE UE) according to the specs, the UE is re-establishing RLC for SRB1 with RRCReestablishmentRequest the other RBs are re-established during RRCReconfiguration (in our case in nr_rrc_ue_process_RadioBearerConfig) when receiving reestablishRLC IE in rlc_BearerToAddModList RLC TX) this leads to RLC counters mismatch after re-establishment: control PDUs discarded until max nb of retx is reached and then UL failure occurs
-
Guido Casati authored
-
- 29 Apr, 2024 10 commits
-
-
Jaroslava Fiedlerova authored
- replace nrmodule2 by up2 - add matix in CI machines - add info about RAN-SA-2x2-Module-CN5G in list of pipeline - update of 5G OTA testbench image
-
Jaroslava Fiedlerova authored
-
Laurent THOMAS authored
-
francescomani authored
-
francescomani authored
-
francescomani authored
-
Jaroslava Fiedlerova authored
-
francescomani authored
-
Jaroslava Fiedlerova authored
Merge remote-tracking branch 'origin/implement-dci11-type0-contiguous-rbs' into integration_2024_w17
-
Jaroslava Fiedlerova authored
-
- 26 Apr, 2024 5 commits
-
-
Cedric Roux authored
By using a struct we may have warnings at compilation time in some cases if the type is not used properly. The type definition becomes a bit weird, so we need to properly comment. If too strange, we can revert to the classical "void" definition.
-
Cedric Roux authored
-
Cedric Roux authored
-
Cedric Roux authored
- rename "lib_ctx" to "mac_implementation" which is what is stored because of previous commit - rename "mac" to "mac_context" to be clearer with what is stored in this variable too
-
Cedric Roux authored
The main work of this commit is to rewrite cipher_aes_128_cbc_cmac() which was too slow and created issues when running the 4G eNB on some machines (LLL when using a b210). Instead of creating the security context, use it, and delete it, all in cipher_aes_128_cbc_cmac(), we introduce the function init_aes_128_cbc_cmac() to create it, and we change cipher_aes_128_cbc_cmac() to just use it, and we also adapt free_aes_128_cbc_cmac(). The function aes_128_cbc_cmac() is removed, it does not follow the new init/use/free API. Doing so, on the primary test machine used to do this work (a powerful and fast machine where it is possible to set the CPUs' frequencies) it was possible to limit the CPUs' frequencies to 500 MHz (it was not possible to go lower) without any LLL (using a b210, quectel UE in idle, no data traffic, only periodic measurement reports). Before this commit, it was necessary to set a frequency of at least 1.8 GHz otherwise some LLL would appear. Then we need to adapt the rest of the code to take into account those changes. A notion of security container (stream_security_container_t) containing ciphering and integrity contexts is introduced. And the code is harmonized for, hopefully, better readability. The (opaque) type stream_security_context_t is introduced, used by both integrity and ciphering contexts. The idea is to use a init()/use()/free() API for all the security procedures, identical for all the ciphering and integrity procedures.
-