d relative to the start of the slot boundary regardless of the start of data transmission in the slot. This mapping type is primarily intended for the cases where the data occupies most of the slot. The mapping type B is used when the first DM-RS is located in the first symbol of the data allocation, that is, the DM-RS location is not given relative to the slot boundary, rather relative to where the data is located. This mapping is intended for transmissions over a small fraction of the slot to support very low latency and other transmissions that cannot wait until a slot boundary starts regardless of the transmission duration. 400 Chapter 3 When the UE is configured with pdsch-AggregationFactor > 1, the same symbol allocation is applied across the pdsch-AggregationFactor consecutive slots that have not been defined as uplink by the SFI. Fig. 3.53 illustrates time-domain and frequency-domain resource allo- cation procedure for PDSCH and demonstrates how the above parameters are used to locate the user allocation. In the uplink, when a UE is scheduled to transmit a transport block on PUSCH by a DCI with or without CSI report(s), the time domain resource assignment field of the DCI pro- vides a row index to a table defined in [15], where the indexed row defines the slot offset K2, the start and length indicator SLIV, or directly by the start symbol S and the allocation length L, and the mapping type to be used in PUSCH transmission as shown in Fig. 3.53. The slot where the UE transmits the PUSCH is determined by parameter K2 as K2 where n is the slot with the scheduling DCI, K2 is based on the numerology of PUSCH, UPUSCH and UPDCCH are the subcarrier spacing configurations for PUSCH and PDCCH, respectively. The starting symbol S relative to the start of the slot, and the number of consecutive symbols L counting from the symbol S allocated for the PUSCH are determined from the start and length indicator SLIV of the indexed row as fol- lows. If (L - 1) < then SLIV = 14(L-1) + S; otherwise SLIV = 14(14 - + 1) + (14 -s