Section: 10.1.3.6 Mapping to physical resources
Content: Each NPUSCH codeword can be mapped to one or more than one resource units, , as given by clause 16.5.1.2 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ]  [4], each of which shall be transmitted times. The block of complex-valued symbols shall be multiplied with the amplitude scaling factor in order to conform to the transmit power specified in [4], and mapped in sequence starting with to subcarriers assigned for transmission of NPUSCH. The mapping to resource elements corresponding to the subcarriers assigned for transmission and not used for transmission of reference signals, shall be in increasing order of first the index , then the index, starting with the first slot in the assigned resource unit. After mapping to slots, the slots shall be repeated additional times, before continuing the mapping of to the following slot, where For NPUSCH Format 1 and 2 on frame structure type 2 with , - the NPUSCH transmission is carried out in the first set of slots spanning over two contiguous uplink subframes not overlapping with any uplink subframe configured as invalid; - for TDD configuration 1 and 4, if the starting position for the NPUSCH is indicated as the second of the two contiguous uplink subframes, the NPUSCH transmission is postponed until the start of two consecutive uplink subframes. If a mapping to slots or a repetition of the mapping contains a resource element which overlaps with - any configured NPRACH resource according to nprach-ParametersList in SystemInformationBlockType2-NB, or - any configured NPRACH resource according to nprach-ParametersList given by ul-ConfigList in SystemInformationBlockType22-NB and if the UE indicates multiCarrier-NPRACH as supported, or - any configured NPRACH resource according to nprach-ParametersList given by ul-ConfigListMixed in SystemInformationBlockType22-NB and if the UE indicates multiCarrier-NPRACH and mixedOperationMode as supported, or - any configured NPRACH resource according to nprach-ParametersListFmt2 in SystemInformationBlockType2-NB and if the UE indicates nprach-Format2 as supported, or - any configured NPRACH resource according to nprach-ParametersListFmt2 given by ul-ConfigList in SystemInformationBlockType23-NB and if the UE indicates multiCarrier-NPRACH and nprach-Format2 as supported, or - any configured NPRACH resource according to nprach-ParametersListFmt2 given by ul-ConfigListMixed in SystemInformationBlockType23-NB and if the UE indicates multiCarrier-NPRACH, mixedOperationMode and nprach-Format2 as supported, or - any configured NPRACH resource according to nprach-ParametersListTDD in SystemInformationBlockType2-NB, or - any configured NPRACH resource according to nprach-ParametersListTDD in SystemInformationBlockType22-NB and if the UE indicates multiCarrier-NPRACH as supported, or - any configured NPRACH resource configured for Early Data Transmission and if the NPUSCH transmission is during an Early Data Transmission procedure [12, Clause 7.3b], then, - for the NPUSCH transmission in overlapped slots is postponed until the next slots not overlapping with any configured NPRACH resource. - for the NPUSCH transmission in overlapped slots is postponed until the next slots starting with the first slot satisfying and not overlapping with any configured NPRACH resource. NPRACH gaps as defined in clause 10.1.6.1 are not part of the NPRACH resource. For frame structure type 2, the valid uplink subframes which are not used for NPRACH transmission when it is not possible to map G symbol groups back-to-back are not part of the NPRACH resource. The mapping of is then repeated until slots have been transmitted. After transmissions and/or postponements due to NPRACH of time units, for frame structure type 1, a gap of time units shall be inserted where the NPUSCH transmission is postponed. The portion of a postponement due to NPRACH which coincides with a gap is counted as part of the gap. When higher layer parameter npusch-AllSymbols is set to false, resource elements in SC-FDMA symbols overlapping with a symbol configured with SRS according to srs-SubframeConfig shall be counted in the NPUSCH mapping but not used for transmission of the NPUSCH. When higher layer parameter npusch-AllSymbols is set to true, all symbols are transmitted. If higher layer parameter resourceReservationConfigUL is configured, then in case of NPUSCH format 1 transmission associated with C-RNTI or SPS C-RNTI using UE-specific NPDCCH search space with the Resource reservation field in the DCI set to 1 including NPUSCH format 1 transmission without a corresponding NPDCCH, or in case of NPUSCH format 2 transmission associated with C-RNTI using UE-specific NPDCCH search space, - In a subframe for or a slot for that is overlapping with any fully reserved uplink subframe as defined in clause 16.5 in [4], - for , the NPUSCH transmission is postponed until the next NB-IoT uplink subframe that is not fully reserved. - for , the NPUSCH transmission in the slot is postponed until the next slot spanning over two contiguous uplink subframes not overlapping with any uplink subframe that is fully reserved. - In a subframe for or a slot for that is not overlapping with any fully reserved uplink subframe, any SC-FDMA symbols overlapping with reserved symbols shall be counted in the NPUSCH mapping but not used for transmission of the NPUSCH. For a UE communicating over NTN, after transmissions (and/or postponements due to NPRACH) of time units, for frame structure type 1, a transmission gap of time units shall be counted for the NPUSCH resource mapping but not used for transmission of the NPUSCH according to the UE capability ntn-SegmentedPrecompensationGaps-r17 as specified in 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ]  [9]. The quantity is provided by higher layers, and the quantity of is configured by higher layers based on the UE capability if signalled.