An error occurred fetching the project authors.
- 11 Jun, 2024 1 commit
-
-
brobert authored
-
- 04 Jun, 2024 1 commit
-
-
brobert authored
-
- 28 May, 2024 1 commit
-
-
robert authored
-
- 21 May, 2024 1 commit
-
-
brobert authored
-
- 14 May, 2024 3 commits
- 17 Apr, 2024 1 commit
-
-
Nada Bouknana authored
-
- 08 Apr, 2024 1 commit
-
-
Robert Schmidt authored
-
- 04 Apr, 2024 1 commit
-
-
Robert Schmidt authored
- It is only a couple of bytes - It hid a bug: if two preambles, L1_nr_prach_procedures() overwrote the preamble of the first with the second one
-
- 12 Feb, 2024 4 commits
-
-
Robert Schmidt authored
PUSCH decoding is started multiple times in nr_ulsch_procedures() for each ULSCH segment, and stopped once inside phy_procedures_gNB_uespec_RX(). Not only is it not clear if that works with the API, it also might measure more than just PUSCH decoding. Remove the PUSCH decoding, it is misleading. Check L1 RX processing instead.
-
Robert Schmidt authored
-
Raymond Knopp authored
This commit introduces a separate thread (l1_tx_thread) that processes gNB DL/TX slots. It receives a message from the ru_thread when a new slot started, and starts processing. The DL part of the scheduler is run in the l1_tx_thread. Therefore, only call UL indication (for scheduler) in UL slots. The UL indication previously triggered the DL scheduler -- hence, it had to be called in every slot. Now, since the DL scheduler is moved into the DL thread, we don't have to call the scheduler in every slot anymore. The reorder thread is removed, as reordering with this scheme is not necessary anymore. The main advantage of this version is that the TX can be scheduled earlier (sl_ahead). Further, there can no longer be race conditions in the TX path, since the scheduler/L2, TX L1 processing and the RU tx function are all execute in the same thread (L1_tX_thread). Also, the scheduler prepares PRACH/PUSCH/PUCCH FAPI PDUs. As of this commit, the scheduler runs in the TX processing chain, whereas these PDUs are destined for RX processing. Thus, too avoid data races, instead of triggering the RX processing at the same time as TX processing in the RU thread, this commit changes the code to trigger RX processing after the scheduler has been run in TX processing to avoid data races. Finally, we synchronize RU and L1 threads. This is important for rfsimulator, since unlike most radios, rfsimulator can run slower or faster, depending on I/O and CPU (it does not have a stable "tick"). Co-authored-by:
kiran <saikiran@iitj.ac.in>
-
Robert Schmidt authored
The UL_INFO_mutex is used in only one place, and therefore useless. Also, the scheduler uses a lock internally to prevent concurrent access. Hence, the UL_INFO_mutex is not needed. Remove kill_gNB_proc(), as it is now dead code.
-
- 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.
-
- 19 Jan, 2024 1 commit
-
-
francescomani authored
-
- 07 Dec, 2023 1 commit
-
-
Quency Lin authored
-
- 29 Nov, 2023 1 commit
-
-
Robert Schmidt authored
-
- 28 Nov, 2023 2 commits
-
-
Jaroslava Fiedlerova authored
-
Jaroslava Fiedlerova authored
-
- 03 Nov, 2023 1 commit
-
-
francescomani authored
-
- 10 Oct, 2023 1 commit
-
-
Laurent THOMAS authored
-
- 06 Oct, 2023 1 commit
-
-
Laurent THOMAS authored
-
- 29 Sep, 2023 1 commit
-
-
Laurent THOMAS authored
-
- 25 Sep, 2023 5 commits
-
-
Tsung Yu Chan authored
- simplify the buffer alignment - add the comment for llr - clean unused variable
-
Tsung Yu Chan authored
-
Tsung-Yu Chan authored
-
Tsung-Yu Chan authored
- avoid the finction duplication - add the transform predoding to the nr_rx_pusch_tp - add the MMSE for 2 layer which modulation greater than 16 qam - can support to 256 qam for 1 layer and 2 layer
-
Tsung-Yu Chan authored
-
- 04 Sep, 2023 1 commit
-
-
rmagueta authored
-
- 10 Jul, 2023 1 commit
-
-
laurent authored
-
- 12 Jun, 2023 1 commit
-
-
Laurent THOMAS authored
-
- 15 May, 2023 1 commit
-
-
Raymond Knopp authored
Provides the backoff from full-scale output at the L1 entity (frequency-domain samples). Default is, 36 dBFS, which is the correct value when using the OAI RU entity. For O-RAN RU, this value should be set according to the O-RU manufacturer requirements. For example 12 would corresponding to 14-bit input level (6 dB/bit). Applies the TX amp backoff to PBCH, PDCCH and CSI
-
- 19 Apr, 2023 2 commits
- 17 Apr, 2023 1 commit
-
-
Raymond Knopp authored
-
- 05 Apr, 2023 1 commit
-
-
Cedric Roux authored
This commit fixes a bug caused by global variables in the gNB_MAC_INST structure used to transfer MAC scheduler's results to the PHY layer. When using several threads in the PHY layer, it may happen that the MAC scheduler is called a second time by the second PHY thread for the next slot before the content of the global variables in the gNB_MAC_INST structure used to store the result of the MAC scheduler for the current slot have been consumed by the first thread, leading to unpredictable results (all of them certainly wrong). The solution is to introduce a small memory management module for the interface between the PHY threads and the MAC scheduler. The MAC scheduler now fills the data structures passed to it, and not a global variable anymore. The PHY layer manages the structures and ensures that no data is overwritten before being fully consumed by the various threads of the PHY layer. Some care has to be taken because several PHY threads will access the same structures at the same time for a given slot (in read mode, so it's okay). A mechanism of reference counting has thus been introduced. Only one CC is supported. This restriction should not be too hard to remove if/when needed. (The code before this commit does not seem to work for more than one CC anyway.)
-
- 27 Mar, 2023 3 commits
-
-
francescomani authored
-
francescomani authored
-
Robert Schmidt authored
-