The WTRU(s) may then in a third step choose as feedback information, based on WTRU(s)′ pre-configured parameters and/or broadcast message parameters, one or more of the following options: 1) the WTRU(s)′ I-RNTI(s) assigned during its(their) transition to “RRC Inactive” state or the WTRU(s)′ TMSI(s) in case of WTRU(s) in “RRC Idle” state; 2) a unique identifier that is compact in form which is obtained as a function of the WTRU(s) I-RNTI(s)/TMSI(s), where the function can be preconfigured at the WTRU or signaled during an “RRC Connected” state; 3) an identifier that is obtained as a function of the WTRU(s) I-RNTI(s) and/or its(their) IMSI(s)/TMSI(s); 4) a preamble that is chosen based on broadcast message parameters and/or as a function of the WTRU(s)′ I-RNTI(s)/TMSI(s)/IMSI(s); and 5) a generic identifier of the WTRU(s)′ EH capability.
The feedback information might or might not be appended by CRC bits to help the gNB(s) detect decoding errors and identify collisions. In a fourth step, the WTRU(s) determine the carrier frequency and time slot within the contention-based transmission window to be used for backscattering the feedback information randomly according to some distribution that is preconfigured at the WTRU(s) or configured using assisting information that is provided as part of the broadcast control message. As an alternative solution to minimize collisions when EH control and signaling are based only on WTRU(s) capability, WTRU(s) interested in EH related signaling will decode the feedback messages over all carriers and at all the time slots within the contention-based transmission window before its(their) randomly selected time slot, and if it(they) detect the same WTRU capability identifier they will refrain from feedback transmission. One example timeline for contention-based feedback transmission is shown in