An error occurred fetching the project authors.
- 20 Jan, 2021 6 commits
-
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
According to SCF222, a single PDCCH allocation groups DCIs that are within the same BWP and CORESET. Therefore, if we want to allocate multiple DCIs, we need to decouple PDCCH allocation and DCI (previously jointly done in nr_configure_pdcch()), especially to be forward compatible. ***Note that as of this commit, we would still allocate different PDCCH PDUs for multiple UEs (which we do not support yet, anyway)*** nr_configure_pdcch(): simply take out DCI allocation. nr_generate_Msg2(): separately allocate dci_pdu in common RA SS, and rename DCI payload variable. Also, reorganize the function so that it is first checked for CCE allocation and messages nFAPI messages are allocated afterwards. nr_schedule_ue_spec(): separately allocate dci_pdu in UE-specific SS. Rename DCI payload variable. nr_schedule_ulsch(): separately allocate dci_pdu in UE-specific SS. Rename DCI payload variable.
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
SCF222 says that dci_pdu in PDCCH PDU (nfapi_nr_dl_tti_pdcch_pdu_rel15_t) should be an array, and not its members.
-
- 04 Dec, 2020 2 commits
-
-
Robert Schmidt authored
-
Robert Schmidt authored
-
- 02 Dec, 2020 6 commits
-
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
- 24 Nov, 2020 1 commit
-
-
Francesco Mani authored
-
- 23 Nov, 2020 2 commits
-
-
Francesco Mani authored
-
Francesco Mani authored
-
- 18 Nov, 2020 2 commits
-
-
Thomas Schlichter authored
-
Laurent authored
-
- 11 Nov, 2020 2 commits
-
-
Khodr Saaifan authored
-
Khodr Saaifan authored
-
- 03 Nov, 2020 2 commits
-
-
Robert Schmidt authored
-
Robert Schmidt authored
-
- 28 Oct, 2020 1 commit
-
-
Florian Kaltenberger authored
-
- 23 Oct, 2020 1 commit
-
-
Raymond Knopp authored
-
- 21 Oct, 2020 1 commit
-
-
Cedric Roux authored
The T tracer macpdu2wireshark has been modified to handle the new traces. The usage is the same as for LTE. In NR the RACH is logged as an LTE RACH. Maybe we'll change that in the future. Looking at the source code of wireshark, I could not find any way to report NR RACH. Maybe they forgot it. Or I did not search correctly...
-
- 19 Oct, 2020 1 commit
-
-
Francesco Mani authored
-
- 15 Oct, 2020 1 commit
-
-
kn.raju authored
-
- 12 Oct, 2020 1 commit
-
-
Sakthivel Velumani authored
-
- 06 Oct, 2020 1 commit
-
-
Francesco Mani authored
-
- 05 Oct, 2020 7 commits
-
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
The name NR_UE_list_t is misleading: beyond being a simple "list", this structure carries all/most UE-related MAC information. If at all, it is a container for multiple lists. The next commit introduces a NR_UE_list_t structure that organizes UEs in lists such that it is easier to go through the UEs.
-
Robert Schmidt authored
nr_configure_pdcch() allocates the CCE, but this is not wanted, e.g., in multi-user scheduling, since it might not be possible to allocate the CCEs for these UEs. This commit makes the following changes: - remove CCE allocation in nr_configure_pdcch() - remove coreset search in nr_configure_pdcch() - add functions get_coreset() and get_searchspace() to retrieve coresets and search spaces easily - in nr_fill_nfapi_dl_pdu(), add extra parameters for aggregation level and CCE indices and the searchspace and coreset of a UE, which might be different for each UE - allocate CCEs manually in phytest, RA, and DLSCH schedulers
-
- 30 Sep, 2020 3 commits
-
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-