Skip to content
Snippets Groups Projects
Commit ac5ac8dd authored by Robert Schmidt's avatar Robert Schmidt
Browse files

Clarify assumptions in nr_acknack_scheduling()

parent 1c75496f
No related branches found
No related tags found
8 merge requests!1757Draft: Use pMAX value in configuration file, instead of hardcoded '23' in asn1_msg.c,!1493fix DL arq errors in UE,!1093Issue in generating NR PRACH for High Speed case,!1074PBCH test case support for non-zero bchpyload,!1045Integration 2021 wk06 c,!1044Integration 2021 wk06 b,!1043Integration 2021 wk06,!1015Draft: Multi-UE + more slots
......@@ -445,9 +445,15 @@ bool nr_acknack_scheduling(int mod_id,
first_ul_slot_tdd,
tdd->nrofUplinkSlots);
/* FIXME: for the moment, we consider that
/* for the moment, we consider:
* * only pucch_sched[0] holds HARQ (and SR)
* * we do not multiplex with CSI */
* * we do not multiplex with CSI, which is always in pucch_sched[2]
* * SR uses format 0 and is allocated in the first UL (mixed) slot (and not
* later)
* * that the PUCCH resource set 0 (for up to 2 bits) points to the first N
* PUCCH resources, where N is the number of resources in the PUCCH
* resource set. This is used in pucch_index_used, which counts the used
* resources by index, and not by their ID! */
NR_UE_sched_ctrl_t *sched_ctrl = &RC.nrmac[mod_id]->UE_info.UE_sched_ctrl[UE_id];
NR_sched_pucch_t *pucch = &sched_ctrl->sched_pucch[0];
AssertFatal(pucch->csi_bits == 0,
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment