An error occurred fetching the project authors.
- 12 Feb, 2021 7 commits
-
-
kn.raju authored
-
kn.raju authored
-
kn.raju authored
* add the RA process to handle to command parameters * Do not create the RAR_pdu into an intermediate array, but directly into the nFAPI TX_req * Slightly restructure nr_generate_Msg2() to first make AssertFatal() checks, then proceed allocating
-
kn.raju authored
-
kn.raju authored
-
kn.raju authored
-
kn.raju authored
-
- 07 Feb, 2021 8 commits
-
-
Robert Schmidt authored
-
Robert Schmidt authored
-
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. nr_fill_nfapi_dl_sib1_pdu(): separately allocate dci_pdu in common SS.
-
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.
-
- 11 Jan, 2021 1 commit
-
-
cig authored
- enhancement of DL indication flow for Msg2 (RAR) - merging interface procedures to handle DLSCH and RAR together - better separation of MAC and PHY functionalities - cleanup of double ambiguous functions to process RAR - merging functions to process TA command into the ue_ta_procedures function - enhancement of logging and formatting in the process
-
- 27 Dec, 2020 1 commit
-
-
cig authored
- as defined by clause 12 "BWP Operation" TS 38.213 - cleaned up hardcoded usage
-
- 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
-