7.3.1 DCI formats

38.2123GPPMultiplexing and channel codingNRRelease 17TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

The DCI formats defined in table 7.3.1-1 are supported.

Table 7.3.1-1: DCI formats

DCI format	Usage
0_0	Scheduling of PUSCH in one cell
0_1	Scheduling of one or multiple PUSCH in one cell, or indicating downlink feedback information for configured grant PUSCH (CG-DFI)
0_2	Scheduling of PUSCH in one cell
1_0	Scheduling of PDSCH in one cell
1_1	Scheduling of one or multiple PDSCH in one cell, and/or triggering one shot HARQ-ACK codebook feedback
1_2	Scheduling of PDSCH in one cell
2_0	Notifying a group of UEs of the slot format, available RB sets, COT duration and search space set group switching
2_1	Notifying a group of UEs of the PRB(s) and OFDM symbol(s) where UE may assume no transmission is intended for the UE
2_2	Transmission of TPC commands for PUCCH and PUSCH
2_3	Transmission of a group of TPC commands for SRS transmissions by one or more UEs
2_4	Notifying a group of UEs of the PRB(s) and OFDM symbol(s) where UE cancels the corresponding UL transmission from the UE
2_5	Notifying the availability of soft resources as defined in Clause 9.3.1 of [10, TS 38.473]
2_6	Notifying the power saving information outside DRX Active Time for one or more UEs
2_7	Notifying paging early indication and TRS availability indication for one or more UEs.
3_0	Scheduling of NR sidelink in one cell
3_1	Scheduling of LTE sidelink in one cell
4_0	Schedulng of PDSCH with CRC scrambled by MCCH-RNTI/G-RNTI for broadcast
4_1	Schedulng of PDSCH with CRC scrambled by G-RNTI/G-CS-RNTI for multicast
4_2	Schedulng of PDSCH with CRC scrambled by G-RNTI/G-CS-RNTI for multicast

The fields defined in the DCI formats below are mapped to the information bits to as follows.

Each field is mapped in the order in which it appears in the description, including the zero-padding bit(s), if any, with the first field mapped to the lowest order information bit and each successive field mapped to higher order information bits. The most significant bit of each field is mapped to the lowest order information bit for that field, e.g. the most significant bit of the first field is mapped to .

If the number of information bits in a DCI format is less than 12 bits, zeros shall be appended to the DCI format until the payload size equals 12.

The size of each DCI format is determined by the configuration of the corresponding active bandwidth part of the scheduled cell and shall be adjusted as described in clause 7.3.1.0 if necessary.

If a UE is configured with pdsch-HARQ-ACK-CodebookList-r16, pdsch-HARQ-ACK-Codebook is replaced by the relevant entry in pdsch-HARQ-ACK-CodebookList-r16 in this clause.

7.3.1.0 DCI size alignment

If necessary, padding or truncation shall be applied to the DCI formats according to the following steps executed in the order below:

Step 0:

– Determine DCI format 0_0 monitored in a common search space according to clause 7.3.1.1.1 where is the size of the initial UL bandwidth part.

– Determine DCI format 1_0 monitored in a common search space according to clause 7.3.1.2.1 where is given by

– the size of CORESET 0 if CORESET 0 is configured for the cell; and

– the size of initial DL bandwidth part if CORESET 0 is not configured for the cell.

– If DCI format 0_0 is monitored in common search space and if the number of information bits in the DCI format 0_0 prior to padding is less than the payload size of the DCI format 1_0 monitored in common search space for scheduling the same serving cell, a number of zero padding bits are generated for the DCI format 0_0 until the payload size equals that of the DCI format 1_0.

– If DCI format 0_0 is monitored in common search space and if the number of information bits in the DCI format 0_0 prior to truncation is larger than the payload size of the DCI format 1_0 monitored in common search space for scheduling the same serving cell, the bitwidth of the frequency domain resource assignment field in the DCI format 0_0 is reduced by truncating the first few most significant bits such that the size of DCI format 0_0 equals the size of the DCI format 1_0.

Step 1:

– Determine DCI format 0_0 monitored in a UE-specific search space according to clause 7.3.1.1.1 where is the size of the active UL bandwidth part.

– Determine DCI format 1_0 monitored in a UE-specific search space according to clause 7.3.1.2.1 where is the size of the active DL bandwidth part.

– For a UE configured with supplementaryUplink in ServingCellConfig in a cell, if PUSCH is configured to be transmitted on both the SUL and the non-SUL of the cell and if the number of information bits in DCI format 0_0 in UE-specific search space for the SUL is not equal to the number of information bits in DCI format 0_0 in UE-specific search space for the non-SUL, a number of zero padding bits are generated for the smaller DCI format 0_0 until the payload size equals that of the larger DCI format 0_0.

– If DCI format 0_0 is monitored in UE-specific search space and if the number of information bits in the DCI format 0_0 prior to padding is less than the payload size of the DCI format 1_0 monitored in UE-specific search space for scheduling the same serving cell, a number of zero padding bits are generated for the DCI format 0_0 until the payload size equals that of the DCI format 1_0.

– If DCI format 1_0 is monitored in UE-specific search space and if the number of information bits in the DCI format 1_0 prior to padding is less than the payload size of the DCI format 0_0 monitored in UE-specific search space for scheduling the same serving cell, zeros shall be appended to the DCI format 1_0 until the payload size equals that of the DCI format 0_0

Step 2:

– Determine DCI format 0_1 monitored in a UE-specific search space according to clause 7.3.1.1.2.

– Determine DCI format 1_1 monitored in a UE-specific search space according to clause 7.3.1.2.2.

– For a UE configured with supplementaryUplink in ServingCellConfig in a cell, if PUSCH is configured to be transmitted on both the SUL and the non-SUL of the cell and if the number of information bits in format 0_1 for the SUL is not equal to the number of information bits in format 0_1 for the non-SUL, zeros shall be appended to smaller format 0_1 until the payload size equals that of the larger format 0_1.

– If the size of DCI format 0_1 monitored in a UE-specific search space equals that of a DCI format 0_0/1_0 monitored in another UE-specific search space, one bit of zero padding shall be appended to DCI format 0_1.

– If the size of DCI format 1_1 monitored in a UE-specific search space equals that of a DCI format 0_0/1_0 monitored in another UE-specific search space, one bit of zero padding shall be appended to DCI format 1_1.

Step 2A:

– Determine DCI format 0_2 monitored in a UE-specific search space according to clause 7.3.1.1.3.

– Determine DCI format 1_2 monitored in a UE-specific search space according to clause 7.3.1.2.3.

– For a UE configured with supplementaryUplink in ServingCellConfig in a cell, if PUSCH is configured to be transmitted on both the SUL and the non-SUL of the cell and if the number of information bits in format 0_2 for the SUL is not equal to the number of information bits in format 0_2 for the non-SUL, zeros shall be appended to smaller format 0_2 until the payload size equals that of the larger format 0_2.

Step 3:

– If both of the following conditions are fulfilled the size alignment procedure is complete

– the total number of different DCI sizes configured to monitor is no more than 4 for the cell

– the total number of different DCI sizes with C-RNTI configured to monitor is no more than 3 for the cell

Step 4:

– Otherwise

Step 4A:

– Remove the padding bit (if any) introduced in step 2 above.

– Determine DCI format 1_0 monitored in a UE-specific search space according to clause 7.3.1.2.1 where is given by

– the size of CORESET 0 if CORESET 0 is configured for the cell; and

– the size of initial DL bandwidth part if CORESET 0 is not configured for the cell.

– Determine DCI format 0_0 monitored in a UE-specific search space according to clause 7.3.1.1.1 where is the size of the initial UL bandwidth part.

– If the number of information bits in the DCI format 0_0 monitored in a UE-specific search space prior to padding is less than the payload size of the DCI format 1_0 monitored in UE-specific search space for scheduling the same serving cell, a number of zero padding bits are generated for the DCI format 0_0 monitored in a UE-specific search space until the payload size equals that of the DCI format 1_0 monitored in a UE-specific search space.

– If the number of information bits in the DCI format 0_0 monitored in a UE-specific search space prior to truncation is larger than the payload size of the DCI format 1_0 monitored in UE-specific search space for scheduling the same serving cell, the bitwidth of the frequency domain resource assignment field in the DCI format 0_0 is reduced by truncating the first few most significant bits such that the size of DCI format 0_0 monitored in a UE-specific search space equals the size of the DCI format 1_0 monitored in a UE-specific search space.

Step 4B:

– If the total number of different DCI sizes configured to monitor is more than 4 for the cell after applying the above steps, or if the total number of different DCI sizes with C-RNTI configured to monitor is more than 3 for the cell after applying the above steps

– If the number of information bits in the DCI format 0_2 prior to padding is less than the payload size of the DCI format 1_2 for scheduling the same serving cell, a number of zero padding bits are generated for the DCI format 0_2 until the payload size equals that of the DCI format 1_2.

– If the number of information bits in the DCI format 1_2 prior to padding is less than the payload size of the DCI format 0_2 for scheduling the same serving cell, zeros shall be appended to the DCI format 1_2 until the payload size equals that of the DCI format 0_2.

Step 4C:

– If the number of information bits in the DCI format 0_1 prior to padding is less than the payload size of the DCI format 1_1 for scheduling the same serving cell, a number of zero padding bits are generated for the DCI format 0_1 until the payload size equals that of the DCI format 1_1.

– If the number of information bits in the DCI format 1_1 prior to padding is less than the payload size of the DCI format 0_1 for scheduling the same serving cell, zeros shall be appended to the DCI format 1_1 until the payload size equals that of the DCI format 0_1.

The UE is not expected to handle a configuration that, after applying the above steps, results in

– the total number of different DCI sizes configured to monitor is more than 4 for the cell; or

– the total number of different DCI sizes with C-RNTI configured to monitor is more than 3 for the cell; or

– the size of DCI format 0_0 in a UE-specific search space is equal to DCI format 0_1 in another UE-specific search space; or

– the size of DCI format 1_0 in a UE-specific search space is equal to DCI format 1_1 in another UE-specific search space; or

– the size of DCI format 0_0 in a UE-specific search space is equal to DCI format 0_2 in another UE-specific search space when at least one pair of the corresponding PDCCH candidates of DCI formats 0_0 and 0_2 are mapped to the same resource; or

– the size of DCI format 1_0 in a UE-specific search space is equal to DCI format 1_2 in another UE-specific search space when at least one pair of the corresponding PDCCH candidates of DCI formats 1_0 and 1_2 are mapped to the same resource; or

– the size of DCI format 0_1 in a UE-specific search space is equal to DCI format 0_2 in the same or another UE-specific search space when at least one pair of the corresponding PDCCH candidates of DCI formats 0_1 and 0_2 are mapped to the same resource; or

– the size of DCI format 1_1 in a UE-specific search space is equal to DCI format 1_2 in the same or another UE-specific search space when at least one pair of the corresponding PDCCH candidates of DCI formats 1_1 and 1_2 are mapped to the same resource.

7.3.1.0.1 DCI size alignment for DCI formats for scheduling of sidelink

If DCI format 3_0 or DCI format 3_1 is monitored on a cell, DCI size alignment for DCI format 3_0 and DCI format 3_1 is performed as described in this clause after performing the DCI size alignment described in Clause 7.3.1.0. The size(s) of the DCI formats configured to monitor for a cell in this clause refers to that after performing the DCI size alignment described in Clause 7.3.1.0.

If DCI format 3_0 or DCI format 3_1 is monitored on a cell and the total number of DCI sizes of the DCI formats configured to monitor for the cell and DCI format 3_0 or DCI format 3_1 is more than 4, zeros shall be appended to DCI format 3_0 if configured and DCI format 3_1 if configured, until the payload size of DCI format 3_0 or DCI format 3_1 equals that of the smallest DCI format configured to monitor for the cell that is larger than DCI format 3_0 or DCI format 3_1.

The UE is not expected to handle a configuration that results in:

– the total number of different DCI sizes configured to monitor for the cell and DCI format 3_0 or DCI format 3_1 is more than 4; and

– the payload size of DCI format 3_0 or DCI format 3_1 is larger than the payload size of all other DCI formats configured to monitor for the cell.

7.3.1.1 DCI formats for scheduling of PUSCH

7.3.1.1.1 Format 0_0

DCI format 0_0 is used for the scheduling of PUSCH in one cell.

The following information is transmitted by means of the DCI format 0_0 with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI:

– Identifier for DCI formats – 1 bit

– The value of this bit field is always set to 0, indicating an UL DCI format

– Frequency domain resource assignment – number of bits determined by the following:

– bits if neither of the higher layer parameters useInterlacePUCCH-PUSCH in BWP-UplinkCommon and useInterlacePUCCH-PUSCH in BWP-UplinkDedicated is configured, where is defined in clause 7.3.1.0

– For PUSCH hopping with resource allocation type 1:

– MSB bits are used to indicate the frequency offset according to Clause 6.3 of [6, TS 38.214], where if the higher layer parameter frequencyHoppingOffsetLists contains two offset values and if the higher layer parameter frequencyHoppingOffsetLists contains four offset values

– bits provide the frequency domain resource allocation according to Clause 6.1.2.2.2 of [6, TS 38.214]

– For non-PUSCH hopping with resource allocation type 1:

– bits provide the frequency domain resource allocation according to Clause 6.1.2.2.2 of [6, TS 38.214]

– If any of the higher layer parameters useInterlacePUCCH-PUSCH in BWP-UplinkCommon and useInterlacePUCCH-PUSCH in BWP-UplinkDedicated is configured

– 5+Y bits provide the frequency domain resource allocation according to Clause 6.1.2.2.3 of [6, TS 38.214] if the subcarrier spacing for the active UL bandwidth part is 30 kHz.

– 6+Y bits provide the frequency domain resource allocation according to Clause 6.1.2.2.3 of [6, TS 38.214] if the subcarrier spacing for the active UL bandwidth part is 15 kHz.

If the DCI format 0_0 is monitored in a UE-specific search space, the value of Y is determined by where is the number of RB sets contained in the active UL BWP as defined in clause 7 of [6, TS38.214]. If the DCI 0_0 is monitored in a common search space Y = 0.

– Time domain resource assignment – 4 bits as defined in Clause 6.1.2.1 of [6, TS 38.214]

– Frequency hopping flag – 1 bit according to Table 7.3.1.1.1-3, as defined in Clause 6.3 of [6, TS 38.214]

– Modulation and coding scheme – 5 bits as defined in Clause 6.1.4.1 of [6, TS 38.214]

– New data indicator – 1 bit

– Redundancy version – 2 bits as defined in Table 7.3.1.1.1-2

– HARQ process number – 4 bits

– TPC command for scheduled PUSCH – 2 bits as defined in Clause 7.1.1 of [5, TS 38.213]

– ChannelAccess-CPext – 2 bits indicating combinations of channel access type and CP extension as defined in Table 7.3.1.1.1-4, or Table 7.3.1.1.1-4A if channelAccessMode-r16 = "semiStatic" is provided, for operation in a cell with shared spectrum channel access in frequency range 1; 2 bits indicating channel access type as defined in Table 7.3.1.1.1-4B if ChannelAccessMode2-r17 is provided for operation in a cell in frequency range 2-2; 0 bit otherwise.

– Padding bits, if required.

– UL/SUL indicator – 1 bit for UEs configured with supplementaryUplink in ServingCellConfig in the cell as defined in Table 7.3.1.1.1-1 and the number of bits for DCI format 1_0 before padding is larger than the number of bits for DCI format 0_0 before padding; 0 bit otherwise. The UL/SUL indicator, if present, locates in the last bit position of DCI format 0_0, after the padding bit(s).

– If the UL/SUL indicator is present in DCI format 0_0 and the higher layer parameter pusch-Config is not configured on both UL and SUL the UE ignores the UL/SUL indicator field in DCI format 0_0, and the corresponding PUSCH scheduled by the DCI format 0_0 is for the UL or SUL for which high layer parameter pucch-Config is configured;

– If the UL/SUL indicator is not present in DCI format 0_0 and pucch-Config is configured, the corresponding PUSCH scheduled by the DCI format 0_0 is for the UL or SUL for which high layer parameter pucch-Config is configured.

– If the UL/SUL indicator is not present in DCI format 0_0 and pucch-Config is not configured, the corresponding PUSCH scheduled by the DCI format 0_0 is for the uplink on which the latest PRACH is transmitted.

The following information is transmitted by means of the DCI format 0_0 with CRC scrambled by TC-RNTI:

– Identifier for DCI formats – 1 bit

– The value of this bit field is always set to 0, indicating an UL DCI format

– Frequency domain resource assignment – number of bits determined by the following:

– bits if the higher layer parameter useInterlacePUCCH-PUSCH in BWP-UplinkCommon is not configured, where

– is the size of the initial UL bandwidth part.

– For PUSCH hopping with resource allocation type 1:

– MSB bits are used to indicate the frequency offset according to Table 8.3-1 in Clause 8.3 of [5, TS 38.213], where if and otherwise

– bits provide the frequency domain resource allocation according to Clause 6.1.2.2.2 of [6, TS 38.214]

– For non-PUSCH hopping with resource allocation type 1:

– bits provide the frequency domain resource allocation according to Clause 6.1.2.2.2 of [6, TS 38.214]

– If the higher layer parameter useInterlacePUCCH-PUSCH in BWP-UplinkCommon is configured

– 5 bits provide the frequency domain resource allocation according to Clause 6.1.2.2.3 of [6, TS 38.214] if the subcarrier spacing for the active UL bandwidth part is 30 kHz

– 6 bits provide the frequency domain resource allocation according to Clause 6.1.2.2.3 of [6, TS 38.214] if the subcarrier spacing for the active UL bandwidth part is 15 kHz

– Time domain resource assignment – 4 bits as defined in Clause 6.1.2.1 of [6, TS 38.214]

– Frequency hopping flag – 1 bit according to Table 7.3.1.1.1-3, as defined in Clause 6.3 of [6, TS 38.214]

– Modulation and coding scheme – 5 bits

– If the UE requests repetition of PUSCH scheduled by RAR UL grant [8, TS 38.321], 5 bits as defined in Clause 6.1.2.1 and Clause 6.1.4.1 of [6, TS 38.214];

– otherwise 5 bits as defined in Clause 6.1.4.1 of [6, TS 38.214].

– New data indicator – 1 bit, reserved

– Redundancy version – 2 bits as defined in Table 7.3.1.1.1-2

– HARQ process number – 4 bits, reserved

– TPC command for scheduled PUSCH – 2 bits as defined in Clause 7.1.1 of [5, TS 38.213]

– Padding bits, if required.

– UL/SUL indicator – 1 bit if the cell has two ULs and the number of bits for DCI format 1_0 before padding is larger than the number of bits for DCI format 0_0 before padding; 0 bit otherwise. The UL/SUL indicator, if present, locates in the last bit position of DCI format 0_0, after the padding bit(s).

– If 1 bit, reserved, and the corresponding PUSCH is always on the same UL carrier as the previous transmission of the same TB

Table 7.3.1.1.1-1: UL/SUL indicator

Value of UL/SUL indicator	Uplink
0	The non-supplementary uplink
1	The supplementary uplink

Table 7.3.1.1.1-2: Redundancy version

Value of the Redundancy version field	Value of to be applied
00	0
01	1
10	2
11	3

Table 7.3.1.1.1-3: Frequency hopping indication

Bit field mapped to index	PUSCH frequency hopping
0	Disabled
1	Enabled

Table 7.3.1.1.1-4: Channel access type & CP extension for DCI format 0_0 and DCI format 1_0 for frequency range 1

Bit field mapped to index	Channel Access Type	The CP extension T_"ext" index defined in Clause 5.3.1 of [4, TS 38.211]
0	Type2C-ULChannelAccess defined in [clause 4.2.1.2.3 in 37.213]	2
1	Type2A-ULChannelAccess defined in [clause 4.2.1.2.1 in 37.213]	3
2	Type2A-ULChannelAccess defined in [clause 4.2.1.2.1 in 37.213]	1
3	Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213]	0

Table 7.3.1.1.1-4A: Channel access type & CP extension if channelAccessMode-r16 = "semiStatic" is provided

Bit field mapped to index	Channel Access Type	The CP extension T_"ext" index defined in Clause 5.3.1 of [4, TS 38.211]	Initiator of the channel occupancy associated with the UL transmission as described in Clause x.x in TS 37.213
0	No sensing as defined in Clause 4.3 in TS 37.213	0	gNB
1	No sensing as defined in Clause 4.3 in TS 37.213	2	gNB
2	Sensing within a 25us interval as defined in Clause 4.3 in TS 37.213	0	gNB
3	Sensing as defined in Clause 4.3.1.2 in TS 37.213	0	UE
Note: Row index 3 is only applicable if ue-SemiStaticChannelAccessConfig is provided. Otherwise, the row is reserved.

Table 7.3.1.1.1-4B: Channel access type for DCI format 0_0 and DCI format 1_0 for frequency range 2-2

Bit field mapped to index	Channel Access Type
0	Type 1 channel access defined in clause 4.4.1 of 37.213
1	Type 2 channel access defined in clause 4.4.2 of 37.213
2	Type 3 channel access defined in clause 4.4.3 of 37.213
3	Reserved

7.3.1.1.2 Format 0_1

DCI format 0_1 is used for the scheduling of one or multiple PUSCH in one cell, or indicating CG downlink feedback information (CG-DFI) to a UE.

The following information is transmitted by means of the DCI format 0_1 with CRC scrambled by C-RNTI or CS-RNTI or SP-CSI-RNTI or MCS-C-RNTI:

– Identifier for DCI formats – 1 bit

– The value of this bit field is always set to 0, indicating an UL DCI format

– Carrier indicator – 0 or 3 bits, as defined in Clause 10.1 of [5, TS38.213]. This field is reserved when this format is carried by PDCCH on the primary cell and the UE is configured for scheduling on the primary cell from an SCell, with the same number of bits as that in this format carried by PDCCH on the SCell for scheduling on the primary cell.

– DFI flag – 0 or 1 bit

– 1 bit if the UE is configured to monitor DCI format 0_1 with CRC scrambled by CS-RNTI and for operation in a cell with shared spectrum channel access when the higher layer parameter cg-RetransmissionTimer is configured. For a DCI format 0_1 with CRC scrambled by CS-RNTI, the bit value of 0 indicates activating or releasing type 2 CG transmission and the bit value of 1 indicates CG-DFI. For a DCI format 0_1 with CRC scrambled by C-RNTI/SP-CSI-RNTI/MCS-C-RNTI and for operation in a cell with shared spectrum channel access, the bit is reserved.

– 0 bit otherwise;

If DCI format 0_1 is used for indicating CG-DFI, all the remaining fields are set as follows:

– HARQ-ACK bitmap – 16 bits , where the order of the bitmap to HARQ process index mapping is such that HARQ process indices are mapped in ascending order from MSB to LSB of the bitmap. For each bit of the bitmap, value 1 indicates ACK, and value 0 indicates NACK.

– TPC command for scheduled PUSCH – 2 bits as defined in Clause 7.1.1 of [5, TS38.213]

– All the remaining bits in format 0_1 are set to zero.

Otherwise, all the remaining fields are set as follows:

– UL/SUL indicator – 0 bit for UEs not configured with supplementaryUplink in ServingCellConfig in the cell or UEs configured with supplementaryUplink in ServingCellConfig in the cell but only one carrier in the cell is configured for PUSCH transmission; otherwise, 1 bit as defined in Table 7.3.1.1.1-1.

– Bandwidth part indicator – 0, 1 or 2 bits as determined by the number of UL BWPs configured by higher layers, excluding the initial UL bandwidth part. The bitwidth for this field is determined as bits, where

– if , in which case the bandwidth part indicator is equivalent to the ascending order of the higher layer parameter BWP-Id;

– otherwise , in which case the bandwidth part indicator is defined in Table 7.3.1.1.2-1;

If a UE does not support active BWP change via DCI, the UE ignores this bit field.

– Frequency domain resource assignment – number of bits determined by the following, where is the size of the active UL bandwidth part:

– If higher layer parameter useInterlacePUCCH-PUSCH in BWP-UplinkDedicated is not configured

– bits if only resource allocation type 0 is configured, where is defined in Clause 6.1.2.2.1 of [6, TS 38.214],

– bits if only resource allocation type 1 is configured, or bits if resourceAllocation is configured as ‘dynamicSwitch’.

– If resourceAllocation is configured as ‘dynamicSwitch’, the MSB bit is used to indicate resource allocation type 0 or resource allocation type 1, where the bit value of 0 indicates resource allocation type 0 and the bit value of 1 indicates resource allocation type 1.

– For resource allocation type 0, the LSBs provide the resource allocation as defined in Clause 6.1.2.2.1 of [6, TS 38.214].

– For resource allocation type 1, the LSBs provide the resource allocation as follows:

– For PUSCH hopping with resource allocation type 1:

– bits provide the frequency domain resource allocation according to Clause 6.1.2.2.2 of [6, TS 38.214]

– For non-PUSCH hopping with resource allocation type 1:

– bits provide the frequency domain resource allocation according to Clause 6.1.2.2.2 of [6, TS 38.214]

If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and if resourceAllocation is configured as ‘dynamicSwitch’ for the indicated bandwidth part, the UE assumes resource allocation type 0 for the indicated bandwidth part if the bitwidth of the "Frequency domain resource assignment" field of the active bandwidth part is smaller than the bitwidth of the "Frequency domain resource assignment" field of the indicated bandwidth part.

– If the higher layer parameter useInterlacePUCCH-PUSCH in BWP-UplinkDedicated is configured

– 5 + Y bits provide the frequency domain resource allocation according to Clause 6.1.2.2.3 of [6, TS 38.214] if the subcarrier spacing for the active UL bandwidth part is 30 kHz. The 5 MSBs provide the interlace allocation and the Y LSBs provide the RB set allocation.

– 6 + Y bits provide the frequency domain resource allocation according to Clause 6.1.2.2.3 of [6, TS 38.214] if the subcarrier spacing for the active UL bandwidth part is 15 kHz. The 6 MSBs provide the interlace allocation and the Y LSBs provide the RB set allocation.

The value of Y is determined by where is the number of RB sets contained in the active UL BWP as defined in clause 7 of [6, TS38.214].

– Time domain resource assignment – 0, 1, 2, 3, 4, 5, or 6 bits

– If the higher layer parameter pusch-TimeDomainAllocationListDCI-0-1 is not configured and if the higher layer parameter pusch-TimeDomainAllocationListForMultiPUSCH is not configured and if the higher layer parameter pusch-TimeDomainResourceAllocationListForMultiPUSCH-r17 is not configured and if the higher layer parameter pusch-TimeDomainAllocationList is configured, 0, 1, 2, 3, or 4 bits as defined in Clause 6.1.2.1 of [6, TS38.214]. The bitwidth for this field is determined as bits, where I is the number of entries in the higher layer parameter pusch-TimeDomainAllocationList;

– If the higher layer parameter pusch-TimeDomainAllocationListDCI-0-1 is configured or if the higher layer parameter pusch-TimeDomainAllocationListForMultiPUSCH is configured or if the higher layer parameter push-TimeDomainResourceAllocationListForMultiPUSCH-r17 is configured, 0, 1, 2, 3, 4, 5 or 6 bits as defined in Clause 6.1.2.1 of [6, TS38.214]. The bitwidth for this field is determined as bits, where I is the number of entries in the higher layer parameter pusch-TimeDomainAllocationListDCI-0-1 or pusch-TimeDomainAllocationListForMultiPUSCH or pusch-TimeDomainResourceAllocationListForMultiPUSCH-r17;

– otherwise the bitwidth for this field is determined as bits, where I is the number of entries in the default table.

– Frequency hopping flag – 0 or 1 bit:

– 0 bit if only resource allocation type 0 is configured, or if the higher layer parameter frequencyHopping is not configured and the higher layer parameter pusch-RepTypeIndicatorDCI-0-1 is not configured to pusch-RepTypeB, or if the higher layer parameter frequencyHoppingDCI-0-1 is not configured and pusch-RepTypeIndicatorDCI-0-1 is configured to pusch-RepTypeB, or if only resource allocation type 2 is configured;

– 1 bit according to Table 7.3.1.1.1-3 otherwise, only applicable to resource allocation type 1, as defined in Clause 6.3 of [6, TS 38.214].

– Modulation and coding scheme – 5 bits as defined in Clause 6.1.4.1 of [6, TS 38.214]

– New data indicator – 1 bit if the number of scheduled PUSCH indicated by the Time domain resource assignment field is 1; otherwise 2, 3, 4, 5, 6, 7 or 8 bits determined based on the maximum number of schedulable PUSCH among all entries in the higher layer parameter pusch-TimeDomainAllocationListForMultiPUSCH or pusch-TimeDomainResourceAllocationListForMultiPUSCH-r17, where each bit corresponds to one scheduled PUSCH as defined in clause 6.1.4 in [6, TS 38.214].

– Redundancy version – – number of bits determined by the following:

– 2 bits as defined in Table 7.3.1.1.1-2 if the number of scheduled PUSCH indicated by the Time domain resource assignment field is 1;

– otherwise 2, 3, 4, 5, 6, 7 or 8 bits determined by the maximum number of schedulable PUSCHs among all entries in the higher layer parameter pusch-TimeDomainAllocationListForMultiPUSCH or pusch-TimeDomainResourceAllocationListForMultiPUSCH-r17, where each bit corresponds to one scheduled PUSCH as defined in clause 6.1.4 in [6, TS 38.214] and redundancy version is determined according to Table 7.3.1.1.2-34.

– HARQ process number – 5 bits if higher layer parameter harq-ProcessNumberSizeDCI-0-1 is configured; otherwise 4 bits

– 1^st downlink assignment index – 1, 2 or 4 bits:

– 1 bit for semi-static HARQ-ACK codebook for unicast and multicast if pdsch-HARQ-ACK-Codebook-Multicast = semiStatic is configured and the higher layer parameter fdmed-Reception-Multicast is not configured; otherwise for semi-static HARQ-ACK codebook for unicast;

– 2 bits for dynamic HARQ-ACK codebook for unicast, or for enhanced dynamic HARQ-ACK codebook without UL-TotalDAI-Included configured;

– 4 bits for enhanced dynamic HARQ-ACK codebook and with UL-TotalDAI-Included = true.

When two HARQ-ACK codebooks are configured for the same serving cell and if higher layer parameter priorityIndicatorDCI-0-1 is configured, if the bit width of the 1^st downlink assignment index in DCI format 0_1 for one HARQ-ACK codebook is not equal to that of the 1^st downlink assignment index in DCI format 0_1 for the other HARQ-ACK codebook, a number of most significant bits with value set to ‘0’ are inserted to smaller 1^st downlink assignment index until the bit width of the 1^st downlink assignment index in DCI format 0_1 for the two HARQ-ACK codebooks are the same.

– 2^nd downlink assignment index – 0, 2 or 4 bits:

– 2 bits for dynamic HARQ-ACK codebook with two HARQ-ACK sub-codebooks for unicast, or for enhanced dynamic HARQ-ACK codebook with two HARQ-ACK sub-codebooks and without UL-TotalDAI-Included configured;

– 4 bits for enhanced dynamic HARQ-ACK codebook with two HARQ-ACK sub-codebooks and with UL-TotalDAI-Included = true;

– 0 bit otherwise.

When two HARQ-ACK codebooks are configured for the same serving cell and if higher layer parameter priorityIndicatorDCI-0-1 is configured, if the bit width of the 2^nd downlink assignment index in DCI format 0_1 for one HARQ-ACK codebook is not equal to that of the 2^nd downlink assignment index in DCI format 0_1 for the other HARQ-ACK codebook, a number of most significant bits with value set to ‘0’ are inserted to smaller 2^nd downlink assignment index until the bit width of the 2^nd downlink assignment index in DCI format 0_1 for the two HARQ-ACK codebooks are the same.

– 3^rd downlink assignment index – 0, 1 or 2 bits:

– 1 bit for semi-static HARQ-ACK codebook for multicast if the higher layer parameter fdmed-Reception-Multicast is configured;

– 2 bits for the dynamic HARQ-ACK codebook for multicast if the higher layer parameter pdsch-HARQ-ACK-Codebook-Multicast = dynamic is configured;

– 0 bit otherwise.

– TPC command for scheduled PUSCH – 2 bits as defined in Clause 7.1.1 of [5, TS38.213]

– Second TPC command for scheduled PUSCH – 2 bits as defined in Clause 7.1.1 of [5, TS38.213] if higher layer parameter SecondTPCFieldDCI-0-1 is configured; 0 bit otherwise.

– SRS resource set indicator – 0 or 2 bits

– 2 bits according to Table 7.3.1.1.2-36 if

– txConfig = nonCodeBook, and there are two SRS resource sets configured by srs-ResourceSetToAddModList and associated with the usage of value ‘nonCodeBook‘, or

– txConfig=codebook, and there are two SRS resource sets configured by srs-ResourceSetToAddModList and associated with usage of value ‘codebook‘;

– 0 bit otherwise.

– if UE supports operation with maxMIMO-Layers and the higher layer parameter maxMIMO-Layers of PUSCH-ServingCellConfig of the serving cell is configured, L_max is given by that parameter

– otherwise, L_max is given by the maximum number of layers for PUSCH supported by the UE for the serving cell for non-codebook based operation.

– bits according to Tables 7.3.1.1.2-32, 7.3.1.1.2-32A and 7.3.1.1.2-32B if the higher layer parameter txConfig = codebook, where is the number of configured SRS resources in the SRS resource set indicated by SRS resource set indicator field if present, otherwise is the number of configured SRS resources in the SRS resource set configured by higher layer parameter srs-ResourceSetToAddModList and associated with the higher layer parameter usage of value ‘codeBook‘.

– Second SRS resource indicator – 0, or bits,

– bits according to Tables 7.3.1.1.2-28/29A/30A/31A with the same number of layers indicated by SRS resource indicator field if the higher layer parameter txConfig = nonCodebook and SRS resource set indicator field is present, where is the number of configured SRS resources in the second SRS resource set, and

– if UE supports operation with maxMIMO-Layers and the higher layer parameter maxMIMO-Layers of PUSCH-ServingCellConfig of the serving cell is configured, L_max is given by that parameter

– otherwise, L_max is given by the maximum number of layers for PUSCH supported by the UE for the serving cell for non-codebook based operation.

– bits according to Tables 7.3.1.1.2-32, 7.3.1.1.2-32A and 7.3.1.1.2-32B if the higher layer parameter txConfig = codebook and SRS resource set indicator field is present, where is the number of configured SRS resources in the second SRS resource set.

– 0 bit otherwise.

– Precoding information and number of layers – number of bits determined by the following:

– 0 bits if the higher layer parameter txConfig = nonCodeBook;

– 0 bits for 1 antenna port and if the higher layer parameter txConfig = codebook;

– 4, 5, or 6 bits according to Table 7.3.1.1.2-2 for 4 antenna ports, if txConfig = codebook, ul-FullPowerTransmission is not configured or configured to fullpowerMode2 or configured to fullpower, transform precoder is disabled, and according to the values of higher layer parameters maxRank, and codebookSubset;

– 4 or 5 bits according to Table 7.3.1.1.2-2A for 4 antenna ports, if txConfig = codebook, ul-FullPowerTransmission = fullpowerMode1, maxRank=2, transform precoder is disabled, and according to the values of higher layer parameter codebookSubset;

– 4 or 6 bits according to Table 7.3.1.1.2-2B for 4 antenna ports, if txConfig = codebook, ul-FullPowerTransmission = fullpowerMode1, maxRank=3 or 4, transform precoder is disabled, and according to the values of higher layer parameter codebookSubset;

– 2, 4, or 5 bits according to Table 7.3.1.1.2-3 for 4 antenna ports, if txConfig = codebook, ul-FullPowerTransmission is not configured or configured to fullpowerMode2 or configured to fullpower, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameters maxRank, and codebookSubset;

– 3 or 4 bits according to Table 7.3.1.1.2-3A for 4 antenna ports, if txConfig = codebook, ul-FullPowerTransmission = fullpowerMode1, maxRank=1, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameter codebookSubset;

– 2 or 4 bits according to Table7.3.1.1.2-4 for 2 antenna ports, if txConfig = codebook, ul-FullPowerTransmission is not configured or configured to fullpowerMode2 or configured to fullpower, transform precoder is disabled, and according to the values of higher layer parameters maxRank and codebookSubset;

– 2 bits according to Table 7.3.1.1.2-4A for 2 antenna ports, if txConfig = codebook, ul-FullPowerTransmission = fullpowerMode1, transform precoder is disabled, maxRank=2, and codebookSubset=nonCoherent;

– 1 or 3 bits according to Table7.3.1.1.2-5 for 2 antenna ports, if txConfig = codebook, ul-FullPowerTransmission is not configured or configured to fullpowerMode2 or configured to fullpower, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameters maxRank and codebookSubset;

– 2 bits according to Table 7.3.1.1.2-5A for 2 antenna ports, if txConfig = codebook, ul-FullPowerTransmission = fullpowerMode1, maxRank=1, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameter codebookSubset;

For the higher layer parameter txConfig=codebook, if ul-FullPowerTransmission is configured to fullpowerMode2, maxRank is configured to be larger than 2, and at least one SRS resource with 4 antenna ports is configured in the SRS resource set indicated by SRS resource set indicator field if present, otherwise in an SRS resource set with usage set to ‘codebook’, and an SRS resource with 2 antenna ports is indicated via SRI in the same SRS resource set, then Table 7.3.1.1.2-4 is used.

For the higher layer parameter txConfig = codebook, if different SRS resources with different number of antenna ports are configured, the bitwidth is determined according to the maximum number of ports in an SRS resource among the configured SRS resources in all SRS resource set(s) with usage set to ‘codebook’. If the number of ports for a configured SRS resource in the set is less than the maximum number of ports in an SRS resource among the configured SRS resources, a number of most significant bits with value set to ‘0’ are inserted to the field.

– Second Precoding information – number of bits determined by the following:

– 0 bits if SRS resource set indicator field is not present;

– 0 bits if the higher layer parameter txConfig = nonCodeBook;

– 0 bits for 1 antenna port and if the higher layer parameter txConfig = codebook;

– 3, 4, or 5 bits according to Table 7.3.1.1.2-2C with the same number of layers indicated by Precoding information and number of layers field for 4 antenna ports, if SRS resource set indicator field is present, txConfig = codebook, ul-FullPowerTransmission is not configured or configured to fullpowerMode2 or configured to fullpower, transform precoder is disabled, and according to the values of higher layer parameters maxRank, and codebookSubset;

– 3 or 4 bits according to Table 7.3.1.1.2-2D with the same number of layers indicated by Precoding information and number of layers field for 4 antenna ports, if SRS resource set indicator field is present, txConfig = codebook, ul-FullPowerTransmission = fullpowerMode1, maxRank=2, transform precoder is disabled, and according to the values of higher layer parameter codebookSubset;

– 3 or 4 bits according to Table 7.3.1.1.2-2E with the same number of layers indicated by Precoding information and number of layers field for 4 antenna ports, if SRS resource set indicator field is present, txConfig = codebook, ul-FullPowerTransmission = fullpowerMode1, maxRank=3 or 4, transform precoder is disabled, and according to the values of higher layer parameter codebookSubset;

– 2, 4, or 5 bits according to Table 7.3.1.1.2-3 with the same number of layers indicated by Precoding information and number of layers field for 4 antenna ports, if SRS resource set indicator field is present, txConfig = codebook, ul-FullPowerTransmission is not configured or configured to fullpowerMode2 or configured to fullpower, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameters maxRank, and codebookSubset;

– 3 or 4 bits according to Table 7.3.1.1.2-3A with the same number of layers indicated by Precoding information and number of layers field for 4 antenna ports, if SRS resource set indicator field is present, txConfig = codebook, ul-FullPowerTransmission = fullpowerMode1, maxRank=1, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameter codebookSubset;

– 1 or 3 bits according to Table7.3.1.1.2-4B with the same number of layers indicated by Precoding information and number of layers field for 2 antenna ports, if SRS resource set indicator field is present, txConfig = codebook, ul-FullPowerTransmission is not configured or configured to fullpowerMode2 or configured to fullpower, transform precoder is disabled, and according to the values of higher layer parameters maxRank and codebookSubset;

– 2 bits according to Table 7.3.1.1.2-4C with the same number of layers indicated by Precoding information and number of layers field for 2 antenna ports, if SRS resource set indicator field is present, txConfig = codebook, ul-FullPowerTransmission = fullpowerMode1, transform precoder is disabled, maxRank=2, and codebookSubset=nonCoherent;

– 1 or 3 bits according to Table7.3.1.1.2-5 with the same number of layers indicated by Precoding information and number of layers field for 2 antenna ports, if SRS resource set indicator field is present, txConfig = codebook, ul-FullPowerTransmission is not configured or configured to fullpowerMode2 or configured to fullpower, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameters maxRank and codebookSubset;

– 2 bits according to Table 7.3.1.1.2-5A with the same number of layers indicated by Precoding information and number of layers field for 2 antenna ports, if SRS resource set indicator field is present, txConfig = codebook, ul-FullPowerTransmission = fullpowerMode1, maxRank=1, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameter codebookSubset;

For the higher layer parameter txConfig=codebook, if ul-FullPowerTransmission is configured to fullpowerMode2, maxRank is configured to be larger than 2, and at least one SRS resource with 4 antenna ports is configured in the SRS resource set indicated by SRS resource set indicator field, and an SRS resource with 2 antenna ports is indicated via Second SRS resource indicator field in the same SRS resource set, then Table 7.3.1.1.2-4B is used.

For the higher layer parameter txConfig = codebook, if different SRS resources with different number of antenna ports are configured, the bitwidth is determined according to the maximum number of ports in an SRS resource among the configured SRS resources in the second SRS resource set with usage set to ‘codebook’ as defined in Table 7.3.1.1.2-36. If the number of ports for a configured SRS resource in the set is less than the maximum number of ports in an SRS resource among the configured SRS resources, a number of most significant bits with value set to ‘0’ are inserted to the field.

– Antenna ports – number of bits determined by the following

– 2 bits as defined by Tables 7.3.1.1.2-6, if transform precoder is enabled, dmrs-Type=1, and maxLength=1, except that dmrs-UplinkTransformPrecoding and tp-pi2BPSK are both configured and π/2 BPSK modulation is used;

– 2 bits as defined by Tables 7.3.1.1.2-6A, if transform precoder is enabled and dmrs-UplinkTransformPrecoding and tp-pi2BPSK are both configured, π/2 BPSK modulation is used, dmrs-Type=1, and maxLength=1, where n_SCID is the scrambling identity for antenna ports defined in [Clause 6.4.1.1.1.2, TS38.211];

– 4 bits as defined by Tables 7.3.1.1.2-7, if transform precoder is enabled, dmrs-Type=1, and maxLength=2, except that dmrs-UplinkTransformPrecoding and tp-pi2BPSK are both configured and π/2 BPSK modulation is used;

– 4 bits as defined by Tables 7.3.1.1.2-7A, if transform precoder is enabled and dmrs-UplinkTransformPrecoding and tp-pi2BPSK are both configured, π/2 BPSK modulation is used, dmrs-Type=1, and maxLength=2, where n_SCID is the scrambling identity for antenna ports defined in [Clause 6.4.1.1.1.2, TS38.211];

– 3 bits as defined by Tables 7.3.1.1.2-8/9/10/11, if transform precoder is disabled, dmrs-Type=1, and maxLength=1, and the value of rank is determined according to the SRS resource indicator field if the higher layer parameter txConfig = nonCodebook and according to the Precoding information and number of layers field if the higher layer parameter txConfig = codebook;

– 4 bits as defined by Tables 7.3.1.1.2-12/13/14/15, if transform precoder is disabled, dmrs-Type=1, and maxLength=2, and the value of rank is determined according to the SRS resource indicator field if the higher layer parameter txConfig = nonCodebook and according to the Precoding information and number of layers field if the higher layer parameter txConfig = codebook;

– 4 bits as defined by Tables 7.3.1.1.2-16/17/18/19, if transform precoder is disabled, dmrs-Type=2, and maxLength=1, and the value of rank is determined according to the SRS resource indicator field if the higher layer parameter txConfig = nonCodebook and according to the Precoding information and number of layers field if the higher layer parameter txConfig = codebook;

– 5 bits as defined by Tables 7.3.1.1.2-20/21/22/23, if transform precoder is disabled, dmrs-Type=2, and maxLength=2, and the value of rank is determined according to the SRS resource indicator field if the higher layer parameter txConfig = nonCodebook and according to the Precoding information and number of layers field if the higher layer parameter txConfig = codebook.

where the number of CDM groups without data of values 1, 2, and 3 in Tables 7.3.1.1.2-6 to 7.3.1.1.2-23 refers to CDM groups {0}, {0,1}, and {0, 1,2} respectively.

If a UE is configured with both dmrs-UplinkForPUSCH-MappingTypeA and dmrs-UplinkForPUSCH-MappingTypeB, the bitwidth of this field equals , where is the "Antenna ports" bitwidth derived according to dmrs-UplinkForPUSCH-MappingTypeA and is the "Antenna ports" bitwidth derived according to dmrs-UplinkForPUSCH-MappingTypeB. A number of zeros are padded in the MSB of this field, if the mapping type of the PUSCH corresponds to the smaller value of and .

– SRS request – 2 bits as defined by Table 7.3.1.1.2-24 for UEs not configured with supplementaryUplink in ServingCellConfig in the cell; 3 bits for UEs configured with supplementaryUplink in ServingCellConfig in the cell where the first bit is the non-SUL/SUL indicator as defined in Table 7.3.1.1.1-1 and the second and third bits are defined by Table 7.3.1.1.2-24. This bit field may also indicate the associated CSI-RS according to Clause 6.1.1.2 of [6, TS 38.214].

– SRS offset indicator – 0, 1 or 2 bits.

– 0 bit if higher layer parameter AvailableSlotOffset is not configured for any aperiodic SRS resource set in the scheduled cell, or if higher layer parameter AvailableSlotOffset is configured for at least one aperodic SRS resource set in the scheduled cell and the maximum number of entries of AvailableSlotOffset configured for all aperiodic SRS resource set(s) is 1;

– otherwise, bits are used to indicate available slot offset according to Table 7.3.1.1.2-37 and Clause 6.2.1 of [6, TS 38.214], where K is the maximum number of entries of AvailableSlotOffset configured for all aperiodic SRS resource set(s) in the scheduled cell;

– CSI request – 0, 1, 2, 3, 4, 5, or 6 bits determined by higher layer parameter reportTriggerSize.

– CBG transmission information (CBGTI) – 0 bit if higher layer parameter codeBlockGroupTransmission for PUSCH is not configured or if the number of scheduled PUSCH indicated by the Time domain resource assignment field is larger than 1; otherwise, 2, 4, 6, or 8 bits determined by higher layer parameter maxCodeBlockGroupsPerTransportBlock for PUSCH.

– PTRS-DMRS association – number of bits determined as follows

– 0 bit if PTRS-UplinkConfig is not configured in either dmrs-UplinkForPUSCH-MappingTypeA or dmrs-UplinkForPUSCH-MappingTypeB and transform precoder is disabled, or if transform precoder is enabled, or if maxRank=1;

– 2 bits otherwise, where Table 7.3.1.1.2-25/7.3.1.1.2-25A and 7.3.1.1.2-26 are used to indicate the association between PTRS port(s) and DMRS port(s) when one PT-RS port and two PT-RS ports are configured by maxNrofPorts in PTRS-UplinkConfig respectively, and the DMRS ports are indicated by the Antenna ports field. When the SRS resource set indicator field is present and maxRank>2, this field indicates the association between PTRS port(s) and DMRS port(s) corresponding to SRS resource indicator field and/or Precoding information and number of layers field according to Table 7.3.1.1.2-25 and 7.3.1.1.2-26. When the SRS resource set indicator field is present and equals "10" and "11" and maxRank=2, the MSB of this field indicates the association between PTRS port(s) and DMRS port(s) corresponding to SRS resource indicator and/or Precoding information and number of layers field, and the LSB of this field indicates the association between PTRS port(s) and DMRS port(s) corresponding to Second SRS resource indicator field and/or Second Precoding information field, according to Table 7.3.1.1.2-25A.

If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and the "PTRS-DMRS association" field is present for the indicated bandwidth part but not present for the active bandwidth part, the UE assumes the "PTRS-DMRS association" field is not present for the indicated bandwidth part.

– Second PTRS-DMRS association – 2 bits if PTRS-DMRS association field and SRS resource set indicator field are present and maxRank>2; 0 bit otherwise. Table 7.3.1.1.2-25 and 7.3.1.1.2-26 are used to indicate the association between PTRS port(s) and DMRS port(s) corresponding to Second SRS resource indicator field and/or Second precoding information field when one PT-RS port and two PT-RS ports are configured by maxNrofPorts in PTRS-UplinkConfig respectively, and the DMRS ports are indicated by the Antenna ports field.

– beta_offset indicator – 0 if the higher layer parameter betaOffsets = semiStatic; otherwise 2 bits as defined by Table 9.3-3 in [5, TS 38.213].

When two HARQ-ACK codebooks are configured for the same serving cell and if higher layer parameter priorityIndicatorDCI-0-1 is configured, if the bit width of the beta_offset indicator in DCI format 0_1 for one HARQ-ACK codebook is not equal to that of the beta_offset indicator in DCI format 0_1 for the other HARQ-ACK codebook, a number of most significant bits with value set to ‘0’ are inserted to smaller beta_offset indicator until the bit width of the beta_offset indicator in DCI format 0_1 for the two HARQ-ACK codebooks are the same.

– DMRS sequence initialization – 0 bit if transform precoder is enabled; 1 bit if transform precoder is disabled.

– UL-SCH indicator – 0 or 1 bit as follows

– 0 bit if the number of scheduled PUSCH indicated by the Time domain resource assignment field is larger than 1;

– 1 bit otherwise. A value of "1" indicates UL-SCH shall be transmitted on the PUSCH and a value of "0" indicates UL-SCH shall not be transmitted on the PUSCH. If a UE does not support triggering SRS only in DCI, except for DCI format 0_1 with CRC scrambled by SP-CSI-RNTI, the UE is not expected to receive a DCI format 0_1 with UL-SCH indicator of "0" and CSI request of all zero(s). If a UE supports triggering SRS only in DCI, except for DCI format 0_1 with CRC scrambled by SP-CSI-RNTI, the UE is not expected to receive a DCI format 0_1 with UL-SCH indicator of "0", CSI request of all zero(s) and SRS request of all zero(s).

– ChannelAccess-CPext-CAPC – 0, 1, 2, 3, 4, 5 or 6 bits. The bitwidth for this field is determined as bits, where I is the number of entries in the higher layer parameter ul-AccessConfigListDCI-0-1 or in Table 7.3.1.1.1-4A if channelAccessMode-r16 = "semiStatic" is provided, for operation in a cell with shared spectrum channel access; otherwise 0 bit. One or more entries from Table 7.3.1.1.2-35 or Table 7.3.1.1.2-35A are configured by the higher layer parameter ul-AccessConfigListDCI-0-1.

– Open-loop power control parameter set indication – 0 or 1 or 2 bits.

– 0 bit if the higher layer parameter p0-PUSCH-SetList is not configured;

– 1 or 2 bits otherwise,

– 1 bit if SRS resource indicator is present in the DCI format 0_1;

– 1 or 2 bits as determined by higher layer parameter olpc-ParameterSetDCI-0-1 if SRS resource indicator is not present in the DCI format 0_1.

– Priority indicator – 0 bit if higher layer parameter priorityIndicatorDCI-0-1 is not configured; otherwise 1 bit as defined in Clause 9 in [5, TS 38.213].

– Invalid symbol pattern indicator – 0 bit if higher layer parameter invalidSymbolPatternIndicatorDCI-0-1 is not configured; otherwise 1 bit as defined in Clause 6.1.2.1 in [6, TS 38.214].

– Minimum applicable scheduling offset indicator – 0 or 1 bit

– 0 bit if higher layer parameter minimumSchedulingOffsetK2 is not configured;

– 1 bit if higher layer parameter minimumSchedulingOffsetK2 is configured. The 1 bit indication is used to determine the minimum applicable K2 for the active UL BWP and the minimum applicable K0 value for the active DL BWP, if configured respectively, according to Table 7.3.1.1.2-33. If the minimum applicable K0 is indicated, the minimum applicable value of the aperiodic CSI-RS triggering offset for an active DL BWP shall be the same as the minimum applicable K0 value.

– SCell dormancy indication – 0 bit if higher layer parameter dormancyGroupWithinActiveTime is not configured; otherwise 1, 2, 3, 4 or 5 bits bitmap determined according to the number of different DormancyGroupID(s) provided by higher layer parameter dormancyGroupWithinActiveTime, where each bit corresponds to one of the SCell group(s) configured by higher layers parameter dormancyGroupWithinActiveTime, with MSB to LSB of the bitmap corresponding to the first to last configured SCell group in ascending order of DormancyGroupID. The field is only present when this format is carried by PDCCH on the primary cell within DRX Active Time and the UE is configured with at least two DL BWPs for an SCell.

– Sidelink assignment index – 0, 1 or 2 bits:

– 1 bit if the UE is configured with pdsch-HARQ-ACK-Codebook = semi-static and, in addition, the UE is configured with a SL configured grant type 1 or to monitor DCI format 3_0 with CRC scrambled by SL-RNTI or SL-CS-RNTI;

– 2 bits if the UE is configured with pdsch-HARQ-ACK-Codebook = dynamic and, in addition, the UE is configured with a SL configured grant type 1 or to monitor DCI format 3_0 with CRC scrambled by SL-RNTI or SL-CS-RNTI;

– 0 bit otherwise.

– PDCCH monitoring adaptation indication – 0, 1 or 2 bits

– 1 or 2 bits, if searchSpaceGroupIdList-r17 is not configured and if pdcch-SkippingDurationList is configured

– 1 bit if the UE is configured with only one duration by pdcch-SkippingDurationList;

– 2 bits if the UE is configured with more than one duration by pdcch-SkippingDurationList.

– 1 or 2 bits, if pdcch-SkippingDurationList is not configured and if searchSpaceGroupIdList-r17 is configured

– 1 bit if the UE is configured by searchSpaceGroupIdList-r17 with search space set(s) with group index 0 and search space set(s) with group index 1, and if the UE is not configured by searchSpaceGroupIdList-r17 with any search space set with group index 2;

– 2 bits if the UE is configured by searchSpaceGroupIdList-r17 with search space set(s) with group index 0, search space set(s) with group index 1 and search space set(s) with group index 2;

– 2 bits, if pdcch-SkippingDurationList is configured and if searchSpaceGroupIdList-r17 is configured

– 0 bit, otherwise

A UE does not expect that the bit width of a field in DCI format 0_1 with CRC scrambled by CS-RNTI is larger than corresponding bit width of same field in DCI format 0_1 with CRC scrambled by C-RNTI for the same serving cell. If the bit width of a field in the DCI format 0_1 with CRC scrambled by CS-RNTI is not equal to that of the corresponding field in the DCI format 0_1 with CRC scrambled by C-RNTI for the same serving cell, a number of most significant bits with value set to ‘0’ are inserted to the field in DCI format 0_1 with CRC scrambled by CS-RNTI until the bit width equals that of the corresponding field in the DCI format 0_1 with CRC scrambled by C-RNTI for the same serving cell.

If the number of information bits in DCI format 0_1 scheduling a single PUSCH prior to padding is not equal to the number of information bits in DCI format 0_1 scheduling multiple PUSCHs for the same serving cell, zeros shall be appended to the DCI format 0_1 with smaller size until the payload size is the same for scheduling a single PUSCH and multiple PUSCHs.

For a UE configured with scheduling on the primary cell from an SCell, if prior to padding the number of information bits in DCI format 0_1 carried by PDCCH on the primary cell is not equal to the number of information bits in DCI format 0_1 carried by PDCCH on the SCell for scheduling on the primary cell, zeros shall be appended to the DCI format 0_1 with smaller size until the payload size is the same.

– If application of step 4C in clause 7.3.1.0 results in additional zero padding for DCI format 0_1 for scheduling on the primary cell, corresponding zeros shall be appended to both DCI format 0_1 monitored on the primary cell and DCI format 0_1 monitored on the SCell for scheduling on the primary cell.

– If the SCell is deactivated, the UE determines the number of information bits in DCI format 0_1 carried by PDCCH on the primary cell based on a DL BWP provided by firstActiveDownlinkBWP-Id for the SCell. If the active DL BWP of the SCell is a dormant DL BWP, the UE determines the number of information bits in DCI format 0_1 carried by PDCCH on the primary cell based on a DL BWP provided by firstWithinActiveTimeBWP-Id for the SCell.

Table 7.3.1.1.2-1: Bandwidth part indicator

Value of BWP indicator field	Bandwidth part
2 bits	Bandwidth part
00	Configured BWP with BWP-Id = 1
01	Configured BWP with BWP-Id = 2
10	Configured BWP with BWP-Id = 3
11	Configured BWP with BWP-Id = 4

Table 7.3.1.1.2-2: Precoding information and number of layers, for 4 antenna ports, if transform precoder is disabled, maxRank = 2 or 3 or 4, and ul-FullPowerTransmission is not configured or configured to fullpowerMode2 or configured to fullpower

Bit field mapped to index	codebookSubset = fullyAndPartialAndNonCoherent	Bit field mapped to index	codebookSubset = partialAndNonCoherent	Bit field mapped to index	codebookSubset= nonCoherent
0	1 layer: TPMI=0	0	1 layer: TPMI=0	0	1 layer: TPMI=0
1	1 layer: TPMI=1	1	1 layer: TPMI=1	1	1 layer: TPMI=1
…	…	…	…	…	…
3	1 layer: TPMI=3	3	1 layer: TPMI=3	3	1 layer: TPMI=3
4	2 layers: TPMI=0	4	2 layers: TPMI=0	4	2 layers: TPMI=0
…	…	…	…	…	…
9	2 layers: TPMI=5	9	2 layers: TPMI=5	9	2 layers: TPMI=5
10	3 layers: TPMI=0	10	3 layers: TPMI=0	10	3 layers: TPMI=0
11	4 layers: TPMI=0	11	4 layers: TPMI=0	11	4 layers: TPMI=0
12	1 layer: TPMI=4	12	1 layer: TPMI=4	12-15	reserved
…	…	…	…
19	1 layer: TPMI=11	19	1 layer: TPMI=11
20	2 layers: TPMI=6	20	2 layers: TPMI=6
…	…	…	…
27	2 layers: TPMI=13	27	2 layers: TPMI=13
28	3 layers: TPMI=1	28	3 layers: TPMI=1
29	3 layers: TPMI=2	29	3 layers: TPMI=2
30	4 layers: TPMI=1	30	4 layers: TPMI=1
31	4 layers: TPMI=2	31	4 layers: TPMI=2
32	1 layers: TPMI=12
…	…
47	1 layers: TPMI=27
48	2 layers: TPMI=14
…	…
55	2 layers: TPMI=21
56	3 layers: TPMI=3
…	…
59	3 layers: TPMI=6
60	4 layers: TPMI=3
61	4 layers: TPMI=4
62-63	reserved

Table 7.3.1.1.2-2A: Precoding information and number of layers for 4 antenna ports, if transform precoder is disabled, maxRank = 2, and ul-FullPowerTransmission = fullpowerMode1

Bit field mapped to index	codebookSubset = partialAndNonCoherent	Bit field mapped to index	codebookSubset= nonCoherent
0	1 layer: TPMI=0	0	1 layer: TPMI=0
1	1 layer: TPMI=1	1	1 layer: TPMI=1
…	…	…	…
3	1 layer: TPMI=3	3	1 layer: TPMI=3
4	2 layers: TPMI=0	4	2 layers: TPMI=0
…	…	…	…
9	2 layers: TPMI=5	9	2 layers: TPMI=5
10	1 layer: TPMI=13	10	1 layer: TPMI=13
11	2 layer: TPMI=6	11	2 layer: TPMI=6
12	1 layer: TPMI=4	12-15	Reserved
…	…
20	1 layer: TPMI=12
21	1 layer: TPMI=14
22	1 layer: TPMI=15
23	2 layers: TPMI=7
…	…
29	2 layers: TPMI=13
30-31	Reserved

Table 7.3.1.1.2-2B: Precoding information and number of layers for 4 antenna ports, if transform precoder is disabled, maxRank = 3 or 4, and ul-FullPowerTransmission = fullpowerMode1

Bit field mapped to index	codebookSubset = partialAndNonCoherent	Bit field mapped to index	codebookSubset= nonCoherent
0	1 layer: TPMI=0	0	1 layer: TPMI=0
1	1 layer: TPMI=1	1	1 layer: TPMI=1
…	…	…	…
3	1 layer: TPMI=3	3	1 layer: TPMI=3
4	2 layers: TPMI=0	4	2 layers: TPMI=0
…	…	…	…
9	2 layers: TPMI=5	9	2 layers: TPMI=5
10	3 layers: TPMI=0	10	3 layers: TPMI=0
11	4 layers: TPMI=0	11	4 layers: TPMI=0
12	1 layer: TPMI=13	12	1 layer: TPMI=13
13	2 layer: TPMI=6	13	2 layer: TPMI=6
14	3 layer: TPMI=1	14	3 layer: TPMI=1
15	1 layer: TPMI=4	15	Reserved
…	…
23	1 layer: TPMI=12
24	1 layer: TPMI=14
25	1 layer: TPMI=15
26	2 layers: TPMI=7
…	…
32	2 layers: TPMI=13
33	3 layers: TPMI=2
34	4 layers: TPMI=1
35	4 layers: TPMI=2
36-63	Reserved

Table 7.3.1.1.2-2C: Second precoding information, for 4 antenna ports, if transform precoder is disabled, maxRank = 2 or 3 or 4, and ul-FullPowerTransmission is not configured or configured to fullpowerMode2 or configured to fullpower

Bit field mapped to index	codebookSubset = fullyAndPartialAndNonCoherent	Bit field mapped to index	codebookSubset = partialAndNonCoherent	Bit field mapped to index	codebookSubset= nonCoherent
0	1 layer: TPMI=0	0	1 layer: TPMI=0	0	1 layer: TPMI=0
…	…	…	…	…	…
27	1 layer: TPMI=27	11	1 layer: TPMI=11	3	1 layer: TPMI=3
28-31	1 layer: reserved	12-15	1 layer: reserved	4-7	1 layer: reserved
0	2 layers: TPMI=0	0	2 layers: TPMI=0	0	2 layers: TPMI=0
…	…	…	…	…	…
21	2 layers: TPMI=21	13	2 layers: TPMI=13	5	2 layers: TPMI=5
22-31	2 layers: reserved	14-15	2 layers: reserved	6-7	2 layers: reserved
0	3 layers: TPMI=0	0	3 layers: TPMI=0	0	3 layers: TPMI=0
…	…	…	…	1-7	3 layers: reserved
6	3 layers: TPMI=6	2	3 layers: TPMI=2	0	4 layers: TPMI=0
7-31	3 layers: reserved	3-15	3 layers: reserved	1-7	4 layers: reserved
0	4 layers: TPMI=0	0	4 layers: TPMI=0
…	…	…	…
4	4 layers: TPMI=4	2	4 layers: TPMI=2
5-31	4 layers: reserved	3-15	4 layers: reserved

Table 7.3.1.1.2-2D: Second precoding information for 4 antenna ports, if transform precoder is disabled, maxRank = 2, and ul-FullPowerTransmission = fullpowerMode1

Bit field mapped to index	codebookSubset = partialAndNonCoherent	Bit field mapped to index	codebookSubset= nonCoherent
0	1 layer: TPMI=0	0	1 layer: TPMI=0
…	…	…	…
14	1 layer: TPMI=14	3	1 layer: TPMI=3
15	1 layer: TPMI=15	4	1 layer: TPMI=13
0	2 layers: TPMI=0	5-7	1 layer: reserved
…	…	0	2 layers: TPMI=0
13	2 layers: TPMI=13	…	…
14-15	2 layers: reserved	6	2 layers: TPMI=6
		7	2 layers: reserved

Table 7.3.1.1.2-2E: Second precoding information for 4 antenna ports, if transform precoder is disabled, maxRank = 3 or 4, and ul-FullPowerTransmission = fullpowerMode1

Bit field mapped to index	codebookSubset = partialAndNonCoherent	Bit field mapped to index	codebookSubset= nonCoherent
0	1 layer: TPMI=0	0	1 layer: TPMI=0
…	…	…	…
14	1 layer: TPMI=14	3	1 layer: TPMI=3
15	1 layer: TPMI=15	4	1 layer: TPMI=13
0	2 layers: TPMI=0	5-7	1 layer: reserved
…	…	0	2 layers: TPMI=0
13	2 layers: TPMI=13	…	…
14-15	2 layers: reserved	6	2 layers: TPMI=6
0	3 layers: TPMI=0	7	2 layers: reserved
…	…	0	3 layers: TPMI=0
2	3 layers: TPMI=2	1	3 layer: TPMI=1
3-15	3 layers: reserved	2-7	3 layers: reserved
0	4 layers: TPMI=0	0	4 layers: TPMI=0
…	…	1-7	4 layers: reserved
2	4 layers: TPMI=2
3-15	4 layers: reserved

Table 7.3.1.1.2-3: Precoding information and number of layers or Second Precoding information, for 4 antenna ports, if transform precoder is enabled and ul-FullPowerTransmission is either not configured or configured to fullpowerMode2 or configured to fullpower, or if transform precoder is disabled, maxRank = 1, and ul-FullPowerTransmission is not configured or configured to fullpowerMode2 or configured to fullpower

Bit field mapped to index	codebookSubset = fullyAndPartialAndNonCoherent	Bit field mapped to index	codebookSubset= partialAndNonCoherent	Bit field mapped to index	codebookSubset= nonCoherent
0	1 layer: TPMI=0	0	1 layer: TPMI=0	0	1 layer: TPMI=0
1	1 layer: TPMI=1	1	1 layer: TPMI=1	1	1 layer: TPMI=1
…	…	…	…	…	…
3	1 layer: TPMI=3	3	1 layer: TPMI=3	3	1 layer: TPMI=3
4	1 layer: TPMI=4	4	1 layer: TPMI=4
…	…	…	…
11	1 layer: TPMI=11	11	1 layer: TPMI=11
12	1 layers: TPMI=12	12-15	reserved
…	…
27	1 layers: TPMI=27
28-31	reserved

Table 7.3.1.1.2-3A: Precoding information and number of layers or Second Precoding information, for 4 antenna ports, if transform precoder is enabled and ul-FullPowerTransmission = fullpowerMode1, or if transform precoder is disabled, maxRank = 1, and ul-FullPowerTransmission = fullpowerMode1

Bit field mapped to index	codebookSubset= partialAndNonCoherent	Bit field mapped to index	codebookSubset= nonCoherent
0	1 layer: TPMI=0	0	1 layer: TPMI=0
1	1 layer: TPMI=1	1	1 layer: TPMI=1
…	…	…	…
3	1 layer: TPMI=3	3	1 layer: TPMI=3
4	1 layer: TPMI=13	4	1 layer: TPMI=13
5	1 layer: TPMI=4	5-7	Reserved
…	…
13	1 layer: TPMI=12
14	1 layer: TPMI=14
15	1 layer: TPMI=15

Table 7.3.1.1.2-4: Precoding information and number of layers, for 2 antenna ports, if transform precoder is disabled, maxRank = 2, and ul-FullPowerTransmission is not configured or configured to fullpowerMode2 or configured to fullpower

Bit field mapped to index	codebookSubset = fullyAndPartialAndNonCoherent	Bit field mapped to index	codebookSubset = nonCoherent
0	1 layer: TPMI=0	0	1 layer: TPMI=0
1	1 layer: TPMI=1	1	1 layer: TPMI=1
2	2 layers: TPMI=0	2	2 layers: TPMI=0
3	1 layer: TPMI=2	3	reserved
4	1 layer: TPMI=3
5	1 layer: TPMI=4
6	1 layer: TPMI=5
7	2 layers: TPMI=1
8	2 layers: TPMI=2
9-15	reserved

Table 7.3.1.1.2-4A: Precoding information and number of layers, for 2 antenna ports, if transform precoder is disabled, maxRank = 2, and ul-FullPowerTransmission = fullpowerMode1

Bit field mapped to index	codebookSubset= nonCoherent
0	1 layer: TPMI=0
1	1 layer: TPMI=1
2	2 layers: TPMI=0
3	1 layer: TPMI=2

Table 7.3.1.1.2-4B: Second precoding information, for 2 antenna ports, if transform precoder is disabled, maxRank = 2, and ul-FullPowerTransmission is not configured or configured to fullpowerMode2 or configured to fullpower

Bit field mapped to index	codebookSubset = fullyAndPartialAndNonCoherent	Bit field mapped to index	codebookSubset = nonCoherent
0	1 layer: TPMI=0	0	1 layer: TPMI=0
1	1 layer: TPMI=1	1	1 layer: TPMI=1
…	…	0	2 layers: TPMI=0
5	1 layer: TPMI=5	1	2 layers: reserved
6-7	1 layer: reserved
0	2 layers: TPMI=0
…	…
2	2 layers: TPMI=2
3-7	2 layers: reserved

Table 7.3.1.1.2-4C: Second precoding information, for 2 antenna ports, if transform precoder is disabled, maxRank = 2, and ul-FullPowerTransmission = fullpowerMode1

Bit field mapped to index	codebookSubset= nonCoherent
0	1 layer: TPMI=0
…	…
2	1 layer: TPMI=2
3	1 layer: reserved
0	2 layers: TPMI=0
1-3	2 layers: reserved

Table 7.3.1.1.2-5: Precoding information and number of layers or Second Precoding information, for 2 antenna ports, if transform precoder is enabled and ul-FullPowerTransmission is not configured or configured to fullpowerMode2 or configured to fullpower, or if transform precoder is disabled, maxRank = 1, and and ul-FullPowerTransmission is not configured or configured to fullpowerMode2 or configured to fullpower

Bit field mapped to index	codebookSubset = fullyAndPartialAndNonCoherent	Bit field mapped to index	codebookSubset = nonCoherent
0	1 layer: TPMI=0	0	1 layer: TPMI=0
1	1 layer: TPMI=1	1	1 layer: TPMI=1
2	1 layer: TPMI=2
3	1 layer: TPMI=3
4	1 layer: TPMI=4
5	1 layer: TPMI=5
6-7	reserved

Table 7.3.1.1.2-5A: Precoding information and number of layers, for 2 antenna ports or Second Precoding information, if transform precoder is enabled and ul-FullPowerTransmission = fullpowerMode1, or if transform precoder is disabled, maxRank = 1, and ul-FullPowerTransmission = fullpowerMode1

Bit field mapped to index	codebookSubset= nonCoherent
0	1 layer: TPMI=0
1	1 layer: TPMI=1
2	1 layer: TPMI=2
3	Reserved

Table 7.3.1.1.2-6: Antenna port(s), transform precoder is enabled, dmrs-Type=1, maxLength=1, except that dmrs-UplinkTransformPrecoding and tp-pi2BPSK are both configured and π/2-BPSK modulation is used

Value	Number of DMRS CDM group(s) without data	DMRS port(s)
0	2	0
1	2	1
2	2	2
3	2	3

Table 7.3.1.1.2-6A: Antenna port(s), transform precoder is enabled, dmrs-UplinkTransformPrecoding and tp-pi2BPSK are both configured, π/2-BPSK modulation is used, dmrs-Type=1, maxLength=1

Value	Number of DMRS CDM group(s) without data	DMRS port(s)
0	2	0, n_SCID= 0
1	2	0, n_SCID= 1
2	2	2, n_SCID= 0
3	2	2, n_SCID= 1

Table 7.3.1.1.2-7: Antenna port(s), transform precoder is enabled, dmrs-Type=1, maxLength=2, except that dmrs-UplinkTransformPrecoding and tp-pi2BPSK are both configured and π/2-BPSK modulation is used

Value	Number of DMRS CDM group(s) without data	DMRS port(s)	Number of front-load symbols
0	2	0	1
1	2	1	1
2	2	2	1
3	2	3	1
4	2	0	2
5	2	1	2
6	2	2	2
7	2	3	2
8	2	4	2
9	2	5	2
10	2	6	2
11	2	7	2
12-15	Reserved	Reserved	Reserved

Table 7.3.1.1.2-7A: Antenna port(s), transform precoder is enabled, dmrs-UplinkTransformPrecoding and tp-pi2BPSK are both configured, π/2-BPSK modulation is used, dmrs-Type=1, maxLength=2

Value	Number of DMRS CDM group(s) without data	DMRS port(s)	Number of front-load symbols
0	2	0, n_SCID= 0	1
1	2	0, n_SCID= 1	1
2	2	2, n_SCID= 0	1
3	2	2, n_SCID= 1	1
4	2	0, n_SCID= 0	2
5	2	0, n_SCID= 1	2
6	2	2, n_SCID= 0	2
7	2	2, n_SCID= 1	2
8	2	4, n_SCID= 0	2
9	2	4, n_SCID= 1	2
10	2	6, n_SCID= 0	2
11	2	6, n_SCID= 1	2
12-15	Reserved	Reserved	Reserved

Table 7.3.1.1.2-8: Antenna port(s), transform precoder is disabled, dmrs-Type=1, maxLength=1, rank = 1

Value	Number of DMRS CDM group(s) without data	DMRS port(s)
0	1	0
1	1	1
2	2	0
3	2	1
4	2	2
5	2	3
6-7	Reserved	Reserved

Table 7.3.1.1.2-9: Antenna port(s), transform precoder is disabled, dmrs-Type=1, maxLength=1, rank = 2

Value	Number of DMRS CDM group(s) without data	DMRS port(s)
0	1	0,1
1	2	0,1
2	2	2,3
3	2	0,2
4-7	Reserved	Reserved

Table 7.3.1.1.2-10: Antenna port(s), transform precoder is disabled, dmrs-Type=1, maxLength=1, rank = 3

Value	Number of DMRS CDM group(s) without data	DMRS port(s)
0	2	0-2
1-7	Reserved	Reserved

Table 7.3.1.1.2-11: Antenna port(s), transform precoder is disabled, dmrs-Type=1, maxLength=1, rank = 4

Value	Number of DMRS CDM group(s) without data	DMRS port(s)
0	2	0-3
1-7	Reserved	Reserved

Table 7.3.1.1.2-12: Antenna port(s), transform precoder is disabled, dmrs-Type=1, maxLength=2, rank = 1

Value	Number of DMRS CDM group(s) without data	DMRS port(s)	Number of front-load symbols
0	1	0	1
1	1	1	1
2	2	0	1
3	2	1	1
4	2	2	1
5	2	3	1
6	2	0	2
7	2	1	2
8	2	2	2
9	2	3	2
10	2	4	2
11	2	5	2
12	2	6	2
13	2	7	2
14-15	Reserved	Reserved	Reserved

Table 7.3.1.1.2-13: Antenna port(s), transform precoder is disabled, dmrs-Type=1, maxLength=2, rank = 2

Value	Number of DMRS CDM group(s) without data	DMRS port(s)	Number of front-load symbols
0	1	0,1	1
1	2	0,1	1
2	2	2,3	1
3	2	0,2	1
4	2	0,1	2
5	2	2,3	2
6	2	4,5	2
7	2	6,7	2
8	2	0,4	2
9	2	2,6	2
10-15	Reserved	Reserved	Reserved

Table 7.3.1.1.2-14: Antenna port(s), transform precoder is disabled, dmrs-Type=1, maxLength=2, rank = 3

Value	Number of DMRS CDM group(s) without data	DMRS port(s)	Number of front-load symbols
0	2	0-2	1
1	2	0,1,4	2
2	2	2,3,6	2
3-15	Reserved	Reserved	Reserved

Table 7.3.1.1.2-15: Antenna port(s), transform precoder is disabled, dmrs-Type=1, maxLength=2, rank = 4

Value	Number of DMRS CDM group(s) without data	DMRS port(s)	Number of front-load symbols
0	2	0-3	1
1	2	0,1,4,5	2
2	2	2,3,6,7	2
3	2	0,2,4,6	2
4-15	Reserved	Reserved	Reserved

Table 7.3.1.1.2-16: Antenna port(s), transform precoder is disabled, dmrs-Type=2, maxLength=1, rank=1

Value	Number of DMRS CDM group(s) without data	DMRS port(s)
0	1	0
1	1	1
2	2	0
3	2	1
4	2	2
5	2	3
6	3	0
7	3	1
8	3	2
9	3	3
10	3	4
11	3	5
12-15	Reserved	Reserved

Table 7.3.1.1.2-17: Antenna port(s), transform precoder is disabled, dmrs-Type=2, maxLength=1, rank=2

Value	Number of DMRS CDM group(s) without data	DMRS port(s)
0	1	0,1
1	2	0,1
2	2	2,3
3	3	0,1
4	3	2,3
5	3	4,5
6	2	0,2
7-15	Reserved	Reserved

Table 7.3.1.1.2-18: Antenna port(s), transform precoder is disabled, dmrs-Type=2, maxLength=1, rank =3

Value	Number of DMRS CDM group(s) without data	DMRS port(s)
0	2	0-2
1	3	0-2
2	3	3-5
3-15	Reserved	Reserved

Table 7.3.1.1.2-19: Antenna port(s), transform precoder is disabled, dmrs-Type=2, maxLength=1, rank =4

Value	Number of DMRS CDM group(s) without data	DMRS port(s)
0	2	0-3
1	3	0-3
2-15	Reserved	Reserved

Table 7.3.1.1.2-20: Antenna port(s), transform precoder is disabled, dmrs-Type=2, maxLength=2, rank=1

Value	Number of DMRS CDM group(s) without data	DMRS port(s)	Number of front-load symbols
0	1	0	1
1	1	1	1
2	2	0	1
3	2	1	1
4	2	2	1
5	2	3	1
6	3	0	1
7	3	1	1
8	3	2	1
9	3	3	1
10	3	4	1
11	3	5	1
12	3	0	2
13	3	1	2
14	3	2	2
15	3	3	2
16	3	4	2
17	3	5	2
18	3	6	2
19	3	7	2
20	3	8	2
21	3	9	2
22	3	10	2
23	3	11	2
24	1	0	2
25	1	1	2
26	1	6	2
27	1	7	2
28-31	Reserved	Reserved	Reserved

Table 7.3.1.1.2-21: Antenna port(s), transform precoder is disabled, dmrs-Type=2, maxLength=2, rank=2

Value	Number of DMRS CDM group(s) without data	DMRS port(s)	Number of front-load symbols
0	1	0,1	1
1	2	0,1	1
2	2	2,3	1
3	3	0,1	1
4	3	2,3	1
5	3	4,5	1
6	2	0,2	1
7	3	0,1	2
8	3	2,3	2
9	3	4,5	2
10	3	6,7	2
11	3	8,9	2
12	3	10,11	2
13	1	0,1	2
14	1	6,7	2
15	2	0,1	2
16	2	2,3	2
17	2	6,7	2
18	2	8,9	2
19-31	Reserved	Reserved	Reserved

Table 7.3.1.1.2-22: Antenna port(s), transform precoder is disabled, dmrs-Type=2, maxLength=2, rank=3

Value	Number of DMRS CDM group(s) without data	DMRS port(s)	Number of front-load symbols
0	2	0-2	1
1	3	0-2	1
2	3	3-5	1
3	3	0,1,6	2
4	3	2,3,8	2
5	3	4,5,10	2
6-31	Reserved	Reserved	Reserved

Table 7.3.1.1.2-23: Antenna port(s), transform precoder is disabled, dmrs-Type=2, maxLength=2, rank=4

Value	Number of DMRS CDM group(s) without data	DMRS port(s)	Number of front-load symbols
0	2	0-3	1
1	3	0-3	1
2	3	0,1,6,7	2
3	3	2,3,8,9	2
4	3	4,5,10,11	2
5-31	Reserved	Reserved	Reserved

Table 7.3.1.1.2-24: SRS request

Value of SRS request field	Triggered aperiodic SRS resource set(s) for DCI format 0_1, 0_2, 1_1, 1_2, and 2_3 configured with higher layer parameter srs-TPC-PDCCH-Group set to ‘typeB’	Triggered aperiodic SRS resource set(s) for DCI format 2_3 configured with higher layer parameter srs-TPC-PDCCH-Group set to ‘typeA’
00	No aperiodic SRS resource set triggered	No aperiodic SRS resource set triggered
01	SRS resource set(s) configured by SRS-ResourceSet with higher layer parameter aperiodicSRS-ResourceTrigger set to 1 or an entry in aperiodicSRS-ResourceTriggerList set to 1 SRS resource set(s) configured by SRS-PosResourceSet with an entry in aperiodicSRS-ResourceTriggerList set to 1 when triggered by DCI formats 0_1, 0_2, 1_1, and 1_2	SRS resource set(s) configured with higher layer parameter usage in SRS-ResourceSet set to ‘antennaSwitching‘ and resourceType in SRS-ResourceSet set to ‘aperiodic’ for a 1^st set of serving cells configured by higher layers
10	SRS resource set(s) configured by SRS-ResourceSet with higher layer parameter aperiodicSRS-ResourceTrigger set to 2 or an entry in aperiodicSRS-ResourceTriggerList set to 2 SRS resource set(s) configured by SRS-PosResourceSet with an entry in aperiodicSRS-ResourceTriggerList set to 2 when triggered by DCI formats 0_1, 0_2, 1_1, and 1_2	SRS resource set(s) configured with higher layer parameter usage in SRS-ResourceSet set to ‘antennaSwitching‘ and resourceType in SRS-ResourceSet set to ‘aperiodic’ for a 2^nd set of serving cells configured by higher layers
11	SRS resource set(s) configured by SRS-ResourceSet with higher layer parameter aperiodicSRS-ResourceTrigger set to 3 or an entry in aperiodicSRS-ResourceTriggerList set to 3 SRS resource set(s) configured by SRS-PosResourceSet with an entry in aperiodicSRS-ResourceTriggerList set to 3 when triggered by DCI formats 0_1, 0_2, 1_1, and 1_2	SRS resource set(s) configured with higher layer parameter usage in SRS-ResourceSet set to ‘antennaSwitching‘ and resourceType in SRS-ResourceSet set to ‘aperiodic’ for a 3^rd set of serving cells configured by higher layers

Table 7.3.1.1.2-25: PTRS-DMRS association or Second PTRS-DMRS association for UL PTRS port 0

Value	DMRS port
0	1^st scheduled DMRS port
1	2^nd scheduled DMRS port
2	3^rd scheduled DMRS port
3	4^th scheduled DMRS port

Table 7.3.1.1.2-25A: PTRS-DMRS association for UL PTRS port 0 or for the actual UL PT-RS port

Value of MSB	DMRS port	Value of LSB	DMRS port
0	1^st scheduled DMRS port corresponding to SRS resource indicator field and/or Precoding information and number of layers field	0	1st scheduled DMRS port corresponding to Second SRS resource indicator field and/or Second Precoding information field
1	2^nd scheduled DMRS port corresponding to SRS resource indicator field and/or Precoding information and number of layers field	1	2nd scheduled DMRS port corresponding to Second SRS resource indicator field and/or Second Precoding information field

Table 7.3.1.1.2-26: PTRS-DMRS association or Second PTRS-DMRS association for UL PTRS ports 0 and 1

Value of MSB	DMRS port	Value of LSB	DMRS port
0	1^st DMRS port which shares PTRS port 0	0	1^st DMRS port which shares PTRS port 1
1	2^nd DMRS port which shares PTRS port 0	1	2^nd DMRS port which shares PTRS port 1

Table 7.3.1.1.2-27: void

Table 7.3.1.1.2-28: SRI indication or Second SRI indication, for non-codebook based PUSCH transmission,

Bit field mapped to index	SRI(s),	Bit field mapped to index	SRI(s),	Bit field mapped to index	SRI(s),
0	0	0	0	0	0
1	1	1	1	1	1
		2	2	2	2
		3	reserved	3	3

Table 7.3.1.1.2-29: SRI indication for non-codebook based PUSCH transmission,

Bit field mapped to index	SRI(s),	Bit field mapped to index	SRI(s),	Bit field mapped to index	SRI(s),
0	0	0	0	0	0
1	1	1	1	1	1
2	0,1	2	2	2	2
3	reserved	3	0,1	3	3
		4	0,2	4	0,1
		5	1,2	5	0,2
		6-7	reserved	6	0,3
				7	1,2
				8	1,3
				9	2,3
				10-15	reserved

Table 7.3.1.1.2-29A: Second SRI indication for non-codebook based PUSCH transmission,

Bit field mapped to index	SRI(s),	Bit field mapped to index	SRI(s),	Bit field mapped to index	SRI(s),
0	0	0	0	0	0
1	1	1	1	1	1
0	0,1	2	2	2	2
1	2 layers: reserved	3	1 layer: reserved	3	3
		0	0,1	4-7	1 layer: reserved
		1	0,2	0	0,1
		2	1,2	1	0,2
		3	2 layers: reserved	2	0,3
				3	1,2
				4	1,3
				5	2,3
				6-7	2 layers: reserved

Table 7.3.1.1.2-30: SRI indication for non-codebook based PUSCH transmission,

Bit field mapped to index	SRI(s),	Bit field mapped to index	SRI(s),	Bit field mapped to index	SRI(s),
0	0	0	0	0	0
1	1	1	1	1	1
2	0,1	2	2	2	2
3	reserved	3	0,1	3	3
		4	0,2	4	0,1
		5	1,2	5	0,2
		6	0,1,2	6	0,3
		7	reserved	7	1,2
				8	1,3
				9	2,3
				10	0,1,2
				11	0,1,3
				12	0,2,3
				13	1,2,3
				14-15	reserved

Table 7.3.1.1.2-30A: Second SRI indication for non-codebook based PUSCH transmission,

Bit field mapped to index	SRI(s),	Bit field mapped to index	SRI(s),	Bit field mapped to index	SRI(s),
0	0	0	0	0	0
1	1	1	1	1	1
0	0,1	2	2	2	2
1	2 layers: reserved	3	1 layer: reserved	3	3
		0	0,1	4-7	1 layer: reserved
		1	0,2	0	0,1
		2	1,2	1	0,2
		3	2 layers: reserved	2	0,3
		0	0,1,2	3	1,2
		1-3	3 layers: reserved	4	1,3
				5	2,3
				6-7	2 layers: reserved
				0	0,1,2
				1	0,1,3
				2	0,2,3
				3	1,2,3
				4-7	3 layers: reserved

Table 7.3.1.1.2-31: SRI indication for non-codebook based PUSCH transmission,

Bit field mapped to index	SRI(s),	Bit field mapped to index	SRI(s),	Bit field mapped to index	SRI(s),
0	0	0	0	0	0
1	1	1	1	1	1
2	0,1	2	2	2	2
3	reserved	3	0,1	3	3
		4	0,2	4	0,1
		5	1,2	5	0,2
		6	0,1,2	6	0,3
		7	reserved	7	1,2
				8	1,3
				9	2,3
				10	0,1,2
				11	0,1,3
				12	0,2,3
				13	1,2,3
				14	0,1,2,3
				15	reserved

Table 7.3.1.1.2-31A: Second SRI indication for non-codebook based PUSCH transmission,

Bit field mapped to index	SRI(s),	Bit field mapped to index	SRI(s),	Bit field mapped to index	SRI(s),
0	0	0	0	0	0
1	1	1	1	1	1
0	0,1	2	2	2	2
1	2 layers: reserved	3	1 layer: reserved	3	3
		0	0,1	4-7	1 layer: reserved
		1	0,2	0	0,1
		2	1,2	1	0,2
		3	2 layers: reserved	2	0,3
		0	0,1,2	3	1,2
		1-3	3 layers: reserved	4	1,3
				5	2,3
				6-7	2 layers: reserved
				0	0,1,2
				1	0,1,3
				2	0,2,3
				3	1,2,3
				4-7	3 layer: reserved
				0	0,1,2,3
				1-7	4 layers: reserved

Table 7.3.1.1.2-32: SRI indication or Second SRI indication, for codebook based PUSCH transmission, if ul-FullPowerTransmission is not configured, or ul-FullPowerTransmission = fullpowerMode1, or ul-FullPowerTransmission = fullpowerMode2, or ul-FullPowerTransmission = fullpower and

Bit field mapped to index	SRI(s),
0	0
1	1

Table 7.3.1.1.2-32A: SRI indication or Second SRI indication, for codebook based PUSCH transmission, if ul-FullPowerTransmission = fullpowerMode2 and

Bit field mapped to index	SRI(s),
0	0
1	1
2	2
3	Reserved

Table 7.3.1.1.2-32B: SRI indication or Second SRI indication, for codebook based PUSCH transmission, if ul-FullPowerTransmission = fullpowerMode2 and

Bit field mapped to index	SRI(s),
0	0
1	1
2	2
3	3

Table 7.3.1.1.2-33: Joint indication of minimum applicable scheduling offset K0/K2

Bit field mapped to index	*Minimum applicable K0 for the active DL BWP, if minimumSchedulingOffsetK0* is configured for the DL BWP**	*Minimum applicable K2 for the active UL BWP, if minimumSchedulingOffsetK2* is configured for the UL BWP**
0	The first value configured by minimumSchedulingOffsetK0 for the active DL BWP	The first value configured by minimumSchedulingOffsetK2 for the active UL BWP
1	The second value configured by minimumSchedulingOffsetK0 for the active DL BWP if the second value is configured; 0 otherwise	The second value configured by minimumSchedulingOffsetK2 for the active UL BWP if the second value is configured; 0 otherwise

Table 7.3.1.1.2-34: Redundancy version

Value of the Redundancy version field	Value of to be applied
0	0
1	2

Table 7.3.1.1.2-35: Allowed entries for DCI format 0_1 and DCI format 0_2, configured by higher layer parameter ul-AccessConfigListDCI-0-1 and ul-AccessConfigListDCI-0-2, respectively, in frequency range 1

Entry index	Channel Access Type	The CP extension T_"ext" index defined in Clause 5.3.1 of [4, 38.211]	CAPC
0	Type2C-ULChannelAccess defined in [clause 4.2.1.2.3 in 37.213]	0	1
1	Type2C-ULChannelAccess defined in [clause 4.2.1.2.3 in 37.213]	0	2
2	Type2C-ULChannelAccess defined in [clause 4.2.1.2.3 in 37.213]	0	3
3	Type2C-ULChannelAccess defined in [clause 4.2.1.2.3 in 37.213]	0	4
4	Type2C-ULChannelAccess defined in [clause 4.2.1.2.3 in 37.213]	2	1
5	Type2C-ULChannelAccess defined in [clause 4.2.1.2.3 in 37.213]	2	2
6	Type2C-ULChannelAccess defined in [clause 4.2.1.2.3 in 37.213]	2	3
7	Type2C-ULChannelAccess defined in [clause 4.2.1.2.3 in 37.213]	2	4
8	Type2B-ULChannelAccess defined in [clause 4.2.1.2.2 in 37.213]	0	1
9	Type2B-ULChannelAccess defined in [clause 4.2.1.2.2 in 37.213]	0	2
10	Type2B-ULChannelAccess defined in [clause 4.2.1.2.2 in 37.213]	0	3
11	Type2B-ULChannelAccess defined in [clause 4.2.1.2.2 in 37.213]	0	4
12	Type2B-ULChannelAccess defined in [clause 4.2.1.2.2 in 37.213]	2	1
13	Type2B-ULChannelAccess defined in [clause 4.2.1.2.2 in 37.213]	2	2
14	Type2B-ULChannelAccess defined in [clause 4.2.1.2.2 in 37.213]	2	3
15	Type2B-ULChannelAccess defined in [clause 4.2.1.2.2 in 37.213]	2	4
16	Type2A-ULChannelAccess defined in [clause 4.2.1.2.1 in 37.213]	0	1
17	Type2A-ULChannelAccess defined in [clause 4.2.1.2.1 in 37.213]	0	2
18	Type2A-ULChannelAccess defined in [clause 4.2.1.2.1 in 37.213]	0	3
19	Type2A-ULChannelAccess defined in [clause 4.2.1.2.1 in 37.213]	0	4
20	Type2A-ULChannelAccess defined in [clause 4.2.1.2.1 in 37.213]	1	1
21	Type2A-ULChannelAccess defined in [clause 4.2.1.2.1 in 37.213]	1	2
22	Type2A-ULChannelAccess defined in [clause 4.2.1.2.1 in 37.213]	1	3
23	Type2A-ULChannelAccess defined in [clause 4.2.1.2.1 in 37.213]	1	4
24	Type2A-ULChannelAccess defined in [clause 4.2.1.2.1 in 37.213]	3	1
25	Type2A-ULChannelAccess defined in [clause 4.2.1.2.1 in 37.213]	3	2
26	Type2A-ULChannelAccess defined in [clause 4.2.1.2.1 in 37.213]	3	3
27	Type2A-ULChannelAccess defined in [clause 4.2.1.2.1 in 37.213]	3	4
28	Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213]	0	1
29	Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213]	0	2
30	Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213]	0	3
31	Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213]	0	4
32	Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213]	1	1
33	Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213]	1	2
34	Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213]	1	3
35	Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213]	1	4
36	Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213]	2	1
37	Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213]	2	2
38	Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213]	2	3
39	Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213]	2	4
40	Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213]	3	1
41	Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213]	3	2
42	Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213]	3	3
43	Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213]	3	4

Table 7.3.1.1.2-35A: Allowed entries for DCI format 0_1, configured by higher layer parameter ul-AccessConfigListDCI-0-1 in frequency range 2-2

Entry index	Channel Access Type
0	Type 1 channel access defined in clause 4.4.1 of 37.213
1	Type 2 channel access defined in clause 4.4.2 of 37.213
2	Type 3 channel access defined in clause 4.4.3 of 37.213

Table 7.3.1.1.2-36: SRS resource set indication

Bit field mapped to index	SRS resource set indication
0	SRS resource indicator field and Precoding information and number of layers field are associated with the first SRS resource set; Second SRS resource indicator field and Second Precoding information field are reserved.
1	SRS resource indicator field and Precoding information and number of layers field are associated with the second SRS resource set; Second SRS resource indicator field and Second Precoding information field are reserved.
2	SRS resource indicator field and Precoding information and number of layers field are associated with the first SRS resource set; Second SRS resource indicator field and Second Precoding information field are associated with the second SRS resource set.
3	SRS resource indicator field and Precoding information and number of layers field are associated with the first SRS resource set; Second SRS resource indicator field and Second Precoding information field are associated with the second SRS resource set.
NOTE 1: The first and the second SRS resource sets are respectively the ones with lower and higher srs-ResourceSetId of the two SRS resources sets configured by higher layer parameter srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, and associated with the higher layer parameter usage of value ‘nonCodeBook‘ if txConfig=nonCodebook or ‘codebook‘ if txConfig=codebook. When only one SRS resource set is configured by higher layer parameter srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, and associated with the higher layer parameter usage of value ‘codebook‘ or ‘nonCodeBook‘ respectively, the first SRS resource set is the SRS resource set. The association of the first and second SRS resource sets to PUSCH repetitions for each bit field index value is as defined in Clause 6.1.2.1 of [6, TS 38.214]. NOTE 2: For DCI format 0_2, the first and second SRS resource sets configured by higher layer parameter srs-ResourceSetToAddModListDCI-0-2 are composed of the first SRS resources together with other configurations in the first and second SRS resource sets configured by higher layer parameter srs-ResourceSetToAddModList, if any, and associated with the higher layer parameter usage of value ‘codebook‘ or ‘nonCodeBook‘, respectively, except for the higher layer parameters ‘srs-ResourceSetId’ and ‘srs-ResourceIdList’.

Table 7.3.1.1.2-37: SRS offset indicator

Bit field mapped to index	Available slot offset, K=2	Bit field mapped to index	Available slot offset, K=3	Bit field mapped to index	Available slot offset, K=4
0	The 1^st entry in AvailableSlotOffset, if configured for the aperiodic SRS resource set; 0, otherwise	0	The 1^st entry in AvailableSlotOffset, if configured for the aperiodic SRS resource set; 0, otherwise	0	The 1^st entry in AvailableSlotOffset, if configured for the aperiodic SRS resource set; 0, otherwise
1	The 2^nd entry in AvailableSlotOffset, if configured for the aperiodic SRS resource set; 0, otherwise	1	The 2^nd entry in AvailableSlotOffset, if configured for the aperiodic SRS resource set; 0, otherwise	1	The 2^nd entry in AvailableSlotOffset, if configured for the aperiodic SRS resource set; 0, otherwise
		2	The 3^rd entry in AvailableSlotOffset, if configured for the aperiodic SRS resource set; 0, otherwise	2	The 3^rd entry in AvailableSlotOffset, if configured for the aperiodic SRS resource set; 0, otherwise
		3	Reserved	3	The 4^th entry in AvailableSlotOffset, if configured for the aperiodic SRS resource set; 0, otherwise

7.3.1.1.3 Format 0_2

DCI format 0_2 is used for the scheduling of PUSCH in one cell.

The following information is transmitted by means of the DCI format 0_2 with CRC scrambled by C-RNTI or CS-RNTI or SP-CSI-RNTI or MCS-C-RNTI:

– Identifier for DCI formats – 1 bit

– The value of this bit field is always set to 0, indicating an UL DCI format

– Carrier indicator – 0, 1, 2 or 3 bits determined by higher layer parameter carrierIndicatorSizeDCI-0-2, as defined in Clause 10.1 of [5, TS38.213]. This field is reserved when this format is carried by PDCCH on the primary cell and the UE is configured for scheduling on the primary cell from an SCell, with the same number of bits as that in this format carried by PDCCH on the SCell for scheduling on the primary cell.

– if , in which case the bandwidth part indicator is equivalent to the ascending order of the higher layer parameter BWP-Id;

– otherwise , in which case the bandwidth part indicator is defined in Table 7.3.1.1.2-1;

If a UE does not support active BWP change via DCI, the UE ignores this bit field.

– Frequency domain resource assignment – number of bits determined by the following:

– bits if only resource allocation type 0 is configured, where is defined in Clause 6.1.2.2.1 of [6, TS 38.214]

– bits if only resource allocation type 1 is configured, or bits if resourceAllocationDCI-0-2-r16 is configured as ‘dynamicSwitch’, where is the size of the active UL bandwidth part, is defined as in clause 4.4.4.4 of [4, TS 38.211] and is given by higher layer parameter resourceAllocationType1GranularityDCI-0-2. If the higher layer parameter resourceAllocationType1GranularityDCI-0-2 is not configured, is equal to 1.

– If resourceAllocationDCI-0-2-r16 is configured as ‘dynamicSwitch’, the MSB bit is used to indicate resource allocation type 0 or resource allocation type 1, where the bit value of 0 indicates resource allocation type 0 and the bit value of 1 indicates resource allocation type 1.

– For resource allocation type 0, the LSBs provide the resource allocation as defined in Clause 6.1.2.2.1 of [6, TS 38.214].

– For resource allocation type 1, the LSBs provide the resource allocation as follows:

– For PUSCH hopping with resource allocation type 1:

– MSB bits are used to indicate the frequency offset according to Clause 6.3 of [6, TS 38.214], where if the higher layer parameter frequencyHoppingOffsetListsDCI-0-2 contains two offset values and if the higher layer parameter frequencyHoppingOffsetListsDCI-0-2 contains four offset values

– bits provide the frequency domain resource allocation according to Clause 6.1.2.2.2 of [6, TS 38.214]

– For non-PUSCH hopping with resource allocation type 1:

– bits provide the frequency domain resource allocation according to Clause 6.1.2.2.2 of [6, TS 38.214]

If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and if resourceAllocationDCI-0-2-r16 is configured as ‘dynamicSwitch’ for the indicated bandwidth part, the UE assumes resource allocation type 0 for the indicated bandwidth part if the bitwidth of the "Frequency domain resource assignment" field of the active bandwidth part is smaller than the bitwidth of the "Frequency domain resource assignment" field of the indicated bandwidth part.

– Time domain resource assignment – 0, 1, 2, 3, 4, 5 or 6 bits as defined in Clause 6.1.2.1 of [6, TS38.214]. The bitwidth for this field is determined as bits, where I is the number of entries in the higher layer parameter pusch-TimeDomainAllocationListDCI-0-2 if the higher layer parameter is configured, or I is the number of entries in the higher layer parameter PUSCH-TimeDomainResourceAllocationList if the higher layer parameter PUSCH-TimeDomainResourceAllocationList is configured and the higher layer parameter pusch-TimeDomainAllocationListDCI-0-2 is not configured; otherwise I is the number of entries in the default table.

– Frequency hopping flag – 0 or 1 bit:

– 0 bit if the higher layer parameter frequencyHoppingDCI-0-2 is not configured;

– 1 bit according to Table 7.3.1.1.1-3 otherwise, only applicable to resource allocation type 1, as defined in Clause 6.3 of [6, TS 38.214].

– Modulation and coding scheme –5 bits as defined in Clause 6.1.4.1 of [6, TS 38.214]

– New data indicator – 1 bit

– Redundancy version – 0, 1 or 2 bits determined by higher layer parameter numberOfBitsForRV-DCI-0-2

– If 0 bit is configured, rv_id to be applied is 0;

– 1 bit according to Table 7.3.1.2.3-1;

– 2 bits according to Table 7.3.1.1.1-2.

– HARQ process number – number of bits determined by the following:

– 5 bits determined by higher layer parameter harq-ProcessNumberSizeDCI-0-2-v1700 if configured;

– otherwise 0, 1, 2, 3 or 4 bits determined by higher layer parameter harq-ProcessNumberSizeDCI-0-2

– Downlink assignment index – 0, 1, 2 or 4 bits

– 0 bit if the higher layer parameter downlinkAssignmentIndexDCI-0-2 is not configured;

– 1, 2, 3, 4, 5 or 6 bits otherwise,

– 1^st downlink assignment index – 1 or 2 bits:

– 2 bits for dynamic HARQ-ACK codebook for unicast.

– 2^nd downlink assignment index – 0 or 2 bits

– 2 bits for dynamic HARQ-ACK codebook with two HARQ-ACK sub-codebooks for unicast;

– 0 bit otherwise.

– 3^rd downlink assignment index – 0, 1 or 2 bits

– 1 bit for semi-static HARQ-ACK codebook for multicast if the higher layer parameter fdmed-Reception-Multicast is configured;

– 2 bits for the dynamic HARQ-ACK codebook for multicast if the higher layer parameter pdsch-HARQ-ACK-Codebook-Multicast = dynamic is configured;

– 0 bit otherwise.

When two HARQ-ACK codebooks are configured for the same serving cell and if higher layer parameter priorityIndicatorDCI-0-2 is configured, if the bit width of the Downlink assignment index in DCI format 0_2 for one HARQ-ACK codebook is not equal to that of the Downlink assignment index in DCI format 0_2 for the other HARQ-ACK codebook, a number of most significant bits with value set to ‘0’ are inserted to smaller Downlink assignment index until the bit width of the Downlink assignment index in DCI format 0_2 for the two HARQ-ACK codebooks are the same.

– TPC command for scheduled PUSCH – 2 bits as defined in Clause 7.1.1 of [5, TS38.213]

– Second TPC command for scheduled PUSCH – 2 bits as defined in Clause 7.1.1 of [5, TS38.213] if higher layer parameter SecondTPCFieldDCI-0-2 is configured; 0 bit otherwise.

– SRS resource set indicator – 0 or 2 bits

– 2 bits according to Table 7.3.1.1.2-36 if

– txConfig = nonCodeBook, and there are two SRS resource sets configured by srs-ResourceSetToAddModListDCI-0-2 and associated with the usage of value ‘nonCodeBook‘, or

– txConfig=codebook, and there are two SRS resource sets configured by srs-ResourceSetToAddModListDCI-0-2 and associated with usage of value ‘codebook‘;

– 0 bit otherwise.

– SRS resource indicator – or bits, where is the number of configured SRS resources in the SRS resource set indicated by SRS resource set indicator field if present; otherwise is the number of configured SRS resources in the SRS resource set configured by higher layer parameter srs-ResourceSetToAddModListDCI-0-2 and associated with the higher layer parameter usage of value ‘codeBook‘ or ‘nonCodeBook‘, where the SRS resource set is composed of the first SRS resources together with other configurations in the SRS resource set, or in the SRS resource set with lower srs-ResourceSetId of two SRS resources sets, configured by higher layer parameter srs-ResourceSetToAddModList, if any, and associated with the higher layer parameter usage of value ‘codeBook‘ or ‘nonCodeBook‘, respectively, except for the higher layer parameters ‘srs-ResourceSetId’ and ‘srs-ResourceIdList’

– bits according to Tables 7.3.1.1.2-28/29/30/31 if the higher layer parameter txConfig = nonCodebook, where is the number of configured SRS resources in the SRS resource set indicated by SRS resource set indicator field if present, otherwise is the number of configured SRS resources in the SRS resource set configured by higher layer parameter srs-ResourceSetToAddModListDCI-0-2 and associated with the higher layer parameter usage of value ‘nonCodeBook‘, where the SRS resource set is composed of the first SRS resources together with other configurations in the SRS resource set, or in the SRS resource set with lower srs-ResourceSetId of two SRS resources sets, configured by higher layer parameter srs-ResourceSetToAddModList, if any, and associated with the higher layer parameter usage of value ‘nonCodeBook‘, except for the higher layer parameters ‘srs-ResourceSetId’ and ‘srs-ResourceIdList’, and

– if UE supports operation with maxMIMO-LayersDCI-0-2 and the higher layer parameter maxMIMO-LayersDCI-0-2 of PUSCH-ServingCellConfig of the serving cell is configured, L_max is given by that parameter

– otherwise, L_max is given by the maximum number of layers for PUSCH supported by the UE for the serving cell for non-codebook based operation.

– bits according to Tables 7.3.1.1.2-32 if the higher layer parameter txConfig = codebook, where is the number of configured SRS resources in the SRS resource set indicated by SRS resource set indicator field if present, otherwise is the number of configured SRS resources in the SRS resource set configured by higher layer parameter srs-ResourceSetToAddModListDCI-0-2 and associated with the higher layer parameter usage of value ‘codeBook‘, where the SRS resource set is composed of the first SRS resources together with other configurations in the SRS resource set configured by higher layer parameter srs-ResourceSetToAddModList, if any, and associated with the higher layer parameter usage of value ‘codeBook‘, except for the higher layer parameters ‘srs-ResourceSetId’ and ‘srs-ResourceIdList’.

– Second SRS resource indicator – 0, or bits,

– otherwise, L_max is given by the maximum number of layers for PUSCH supported by the UE for the serving cell for non-codebook based operation.

– bits according to Tables 7.3.1.1.2-32 if the higher layer parameter txConfig = codebook and SRS resource set indicator field is present, where is the number of configured SRS resources in the second SRS resource set.

– 0 bit otherwise.

– Precoding information and number of layers – number of bits determined by the following:

– 0 bits if the higher layer parameter txConfig = nonCodeBook;

– 0 bits for 1 antenna port and if the higher layer parameter txConfig = codebook;

– 4 or 5 bits according to Table 7.3.1.1.2-2A for 4 antenna ports, if txConfig = codebook, ul-FullPowerTransmission =fullpowerMode1, the values of higher layer parameters maxRankDCI-0-2=2, transform precoder is disabled, and according to the value of higher layer parameter codebookSubsetDCI-0-2;

– 4 or 6 bits according to Table 7.3.1.1.2-2B for 4 antenna ports, if txConfig = codebook, ul-FullPowerTransmission =fullpowerMode1, the values of higher layer parameters maxRankDCI-0-2=3 or 4, transform precoder is disabled, and according to the value of higher layer parameter codebookSubsetDCI-0-2;

– 3 or 4 bits according to Table 7.3.1.1.2-3A for 4 antenna ports, if txConfig = codebook, ul-FullPowerTransmission =fullpowerMode1, maxRankDCI-0-2=1, and according to whether transform precoder is enabled or disabled, and the value of higher layer parameter codebookSubsetDCI-0-2;

– 2 bits according to Table 7.3.1.1.2-4A for 2 antenna ports, if txConfig = codebook, ul-FullPowerTransmission =fullpowerMode1, transform precoder is disabled, the maxRankDCI-0-2=2, and codebookSubsetDCI-0-2=nonCoherent;

– 2 bits according to Table 7.3.1.1.2-5A for 2 antenna ports, if txConfig = codebook, ul-FullPowerTransmission =fullpowerMode1, maxRankDCI-0-2=1, and according to whether transform precoder is enabled or disabled, and the value of higher layer parameter codebookSubsetDCI-0-2.

For the higher layer parameter txConfig=codebook, if ul-FullPowerTransmission is configured to fullpowerMode2, the values of higher layer parameters maxRankDCI-0-2 is configured to be larger than 2, and at least one SRS resource with 4 antenna ports is configured in the SRS resource set indicated by SRS resource set indicator field if present, otherwise in an SRS resource set with usage set to ‘codebook’, and an SRS resource with 2 antenna ports is indicated via SRI in the same SRS resource set, then Table 7.3.1.1.2-4 is used.

– Second Precoding information – number of bits determined by the following:

– 0 bits if SRS resource set indicator field is not present;

– 0 bits if the higher layer parameter txConfig = nonCodeBook;

– 0 bits for 1 antenna port and if the higher layer parameter txConfig = codebook;

– 3 or 4 bits according to Table 7.3.1.1.2-2D with the same number of layers indicated by Precoding information and number of layers field for 4 antenna ports, if SRS resource set indicator field is present, txConfig = codebook, ul-FullPowerTransmission =fullpowerMode1, the values of higher layer parameters maxRankDCI-0-2=2, transform precoder is disabled, and according to the value of higher layer parameter codebookSubsetDCI-0-2;

– 3 or 4 bits according to Table 7.3.1.1.2-2E with the same number of layers indicated by Precoding information and number of layers field for 4 antenna ports, if SRS resource set indicator field is present, txConfig = codebook, ul-FullPowerTransmission =fullpowerMode1, the values of higher layer parameters maxRankDCI-0-2=3 or 4, transform precoder is disabled, and according to the value of higher layer parameter codebookSubsetDCI-0-2;

– 2, 4, or 5 bits according to Table 7.3.1.1.2-3 with the same number of layers indicated by Precoding information and number of layers field for 4 antenna ports, if txConfig = codebook, ul-FullPowerTransmission is not configured or configured to fullpowerMode2 or configured to fullpower, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameters maxRankDCI-0-2 and codebookSubsetDCI-0-2;

– 3 or 4 bits according to Table 7.3.1.1.2-3A with the same number of layers indicated by Precoding information and number of layers field for 4 antenna ports, if txConfig = codebook, ul-FullPowerTransmission =fullpowerMode1, maxRankDCI-0-2=1, and according to whether transform precoder is enabled or disabled, and the value of higher layer parameter codebookSubsetDCI-0-2;

– 2 bits according to Table 7.3.1.1.2-4C with the same number of layers indicated by Precoding information and number of layers field for 2 antenna ports, if SRS resource set indicator field is present, txConfig = codebook, ul-FullPowerTransmission =fullpowerMode1, transform precoder is disabled, the maxRankDCI-0-2=2, and codebookSubsetDCI-0-2=nonCoherent;

– 2 bits according to Table 7.3.1.1.2-5A with the same number of layers indicated by Precoding information and number of layers field for 2 antenna ports, if SRS resource set indicator field is present, txConfig = codebook, ul-FullPowerTransmission =fullpowerMode1, maxRankDCI-0-2=1, and according to whether transform precoder is enabled or disabled, and the value of higher layer parameter codebookSubsetDCI-0-2.

For the higher layer parameter txConfig=codebook, if ul-FullPowerTransmission is configured to fullpowerMode2, the values of higher layer parameters maxRankDCI-0-2 is configured to be larger than 2, and at least one SRS resource with 4 antenna ports is configured in the SRS resource set indicated by SRS resource set indicator field, and an SRS resource with 2 antenna ports is indicated via Second SRS resource indicator field in the same SRS resource set, then Table 7.3.1.1.2-4B is used.

For the higher layer parameter txConfig = codebook, if different SRS resources with different number of antenna ports are configured, the bitwidth is determined according to the maximum number of ports in an SRS resource among the configured SRS resources in the second SRS resource set with usage set to ‘codebook’ as defined in Table 7.3.1.1.2-36. If the number of ports for a configured SRS resource in the set is less than the maximum number of ports in an SRS resource among the configured SRS resources, a number of most significant bits with value set to ‘0’ are inserted to the field.

– Antenna ports – number of bits determined by the following:

– 0 bit if higher layer parameter antennaPortsFieldPresenceDCI-0-2 is not configured;

– 2, 3, 4, or 5 bits otherwise,

– 2 bits as defined by 7.3.1.1.2-6A, if transform precoder is enabled, and dmrs-UplinkTransformPrecoding and tp-pi2BPSK are both configured, π/2 BPSK modulation is used, dmrs-Type=1, and maxLength=1, where n_SCID is the scrambling identity for antenna ports defined in Clause 6.4.1.1.1.2, in [4, TS38.211];

– 4 bits as defined by Tables 7.3.1.1.2-7A, if transform precoder is enabled, and dmrs-UplinkTransformPrecoding and tp-pi2BPSK are both configured, π/2 BPSK modulation is used, dmrs-Type=1, and maxLength=2, where n_SCID is the scrambling identity for antenna ports defined in Clause 6.4.1.1.1.2, in [4, TS38.211];

where the number of CDM groups without data of values 1, 2, and 3 in Tables 7.3.1.1.2-6 to 7.3.1.1.2-23 refers to CDM groups {0}, {0,1}, and {0, 1,2} respectively.

If a UE is configured with both dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2 and dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2 and is configured with antennaPortsFieldPresenceDCI-0-2, the bitwidth of this field equals , where is the "Antenna ports" bitwidth derived according to dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2 and is the "Antenna ports" bitwidth derived according to dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2. A number of zeros are padded in the MSB of this field, if the mapping type of the PUSCH corresponds to the smaller value of and .

If a UE is not configured with higher layer parameter antennaPortsFieldPresenceDCI-0-2, antenna port(s) are defined assuming bit field index value 0 in Tables 7.3.1.1.2-6 to 7.3.1.1.2-23.

– SRS request – 0, 1, 2 or 3 bits

– 0 bit if the higher layer parameter srs-RequestDCI-0-2 is not configured;

– 1 bit as defined by Table 7.3.1.1.3-1 if higher layer parameter srs-RequestDCI-0-2 = 1 and for UEs not configured with supplementaryUplink in ServingCellConfig in the cell;

– 2 bits if higher layer parameter srs-RequestDCI-0-2 = 1 and for UEs configured with supplementaryUplink in ServingCellConfig in the cell, where the first bit is the non-SUL/SUL indicator as defined in Table 7.3.1.1.1-1 and the second bit is defined by Table 7.3.1.1.3-1;

– 2 bits as defined by Table 7.3.1.1.2-24 if higher layer parameter srs-RequestDCI-0-2 = 2 and for UEs not configured with supplementaryUplink in ServingCellConfig in the cell;

– 3 bits if higher layer parameter srs-RequestDCI-0-2 = 2 and for UEs configured with supplementaryUplink in ServingCellConfig in the cell, where the first bit is the non-SUL/SUL indicator as defined in Table 7.3.1.1.1-1 and the second and third bits are defined by Table 7.3.1.1.2-24;

– SRS offset indicator – 0, 1 or 2 bits.

– CSI request – 0, 1, 2, 3, 4, 5, or 6 bits determined by higher layer parameter reportTriggerSizeDCI-0-2.

– PTRS-DMRS association – number of bits determined as follows

– 2 bits otherwise, where Table 7.3.1.1.2-25/7.3.1.1.2-25A and 7.3.1.1.2-26 are used to indicate the association between PTRS port(s) and DMRS port(s) when one PT-RS port and two PT-RS ports are configured by maxNrofPorts in PTRS-UplinkConfig respectively, and the DMRS ports are indicated by the Antenna ports field. When the SRS resource set indicator field is present and maxRankDCI-0-2>2, this field indicates the association between PTRS port(s) and DMRS port(s) corresponding to SRS resource indicator field and/or Precoding information and number of layers field according to Table 7.3.1.1.2-25 and 7.3.1.1.2-26 field according to Table 7.3.1.1.2-25 and 7.3.1.1.2-26. When the SRS resource set indicator field is present and equals "10" and "11" and maxRankDCI-0-2=2, the MSB of this field indicates the association between PTRS port(s) and DMRS port(s) corresponding to SRS resource indicator field and/or Precoding information and number of layers field, and the LSB of this field indicates the association between PTRS port(s) and DMRS port(s) corresponding to Second SRS resource indicator field and/or Second Precoding information field, according to Table 7.3.1.1.2-25A.

– Second PTRS-DMRS association – 2 bits if PTRS-DMRS association field and SRS resource set indicator field are present and maxRankDCI-0-2>2; 0 bit otherwise. Table 7.3.1.1.2-25 and 7.3.1.1.2-26 are used to indicate the association between PTRS port(s) and DMRS port(s) corresponding to Second SRS resource indicator field and/or Second precoding information field when one PT-RS port and two PT-RS ports are configured by maxNrofPorts in PTRS-UplinkConfig respectively, and the DMRS ports are indicated by the Antenna ports field.

– beta_offset indicator – 0 bit if the higher layer parameter betaOffsets = semiStatic; otherwise 1 bit if 2 offset indexes are configured by higher layer parameter dynamicDCI-0-2 as defined by Table 9.3-3A in [5, TS 38.213], and 2 bits if 4 offset indexes are configured by higher layer parameter dynamicDCI-0-2 as defined by Table 9.3-3 in [5, TS 38.213].

When two HARQ-ACK codebooks are configured for the same serving cell and if higher layer parameter priorityIndicatorDCI-0-2 is configured, if the bit width of the beta_offset indicator in DCI format 0_2 for one HARQ-ACK codebook is not equal to that of the beta_offset indicator in DCI format 0_2 for the other HARQ-ACK codebook, a number of most significant bits with value set to ‘0’ are inserted to smaller beta_offset indicator until the bit width of the beta_offset indicator in DCI format 0_2 for the two HARQ-ACK codebooks are the same.

– DMRS sequence initialization – 0 or 1 bit

– 0 bit if the higher layer parameter dmrs-SequenceInitializationDCI-0-2 is not configured or if transform precoder is enabled;

– 1 bit if transform precoder is disabled and the higher layer parameter dmrs-SequenceInitializationDCI-0-2 is configured.

– UL-SCH indicator – 1 bit. A value of "1" indicates UL-SCH shall be transmitted on the PUSCH and a value of "0" indicates UL-SCH shall not be transmitted on the PUSCH. If a UE does not support triggering SRS only in DCI, except for DCI format 0_2 with CRC scrambled by SP-CSI-RNTI, the UE is not expected to receive a DCI format 0_2 with UL-SCH indicator of "0" and CSI request of all zero(s). If a UE supports triggering SRS only in DCI, except for DCI format 0_2 with CRC scrambled by SP-CSI-RNTI, the UE is not expected to recerive a DCI format 0_2 with UL-SCH indicator of "0", CSI request of all zero(s) and SRS request of all zero(s).

– ChannelAccess-CPext-CAPC – 0, 1, 2, 3, 4, 5 or 6 bits. The bitwidth for this field is determined as bits, where I is the number of entries in the higher layer parameter ul-AccessConfigListDCI-0-2 or in Table 7.3.1.1.1-4A if channelAccessMode-r16 = "semiStatic" is provided, for operation in a cell with shared spectrum channel access; otherwise 0 bit. One or more entries from Table 7.3.1.1.2-35 are configured by the higher layer parameter ul-AccessConfigListDCI-0-2.

– Open-loop power control parameter set indication – 0 or 1 or 2 bits.

– 0 bit if the higher layer parameter p0-PUSCH-SetList is not configured;

– 1 or 2 bits otherwise,

– 1 bit if SRS resource indicator is present in the DCI format 0_2;

– 1 or 2 bits as determined by higher layer parameter olpc-ParameterSetDCI-0-2 if SRS resource indicator is not present in the DCI format 0_2;

– Priority indicator – 0 bit if higher layer parameter priorityIndicatorDCI-0-2 is not configured; otherwise 1 bit as defined in Clause 9 in [5, TS 38.213].

– Invalid symbol pattern indicator – 0 bit if higher layer parameter invalidSymbolPatternIndicatorDCI-0-2 is not configured; otherwise 1 bit as defined in Clause 6.1.2.1 in [6, TS 38.214].

– PDCCH monitoring adaptation indication – 0, 1 or 2 bits

– 1 or 2 bits, if searchSpaceGroupIdList-r17 is not configured and if pdcch-SkippingDurationList is configured

– 1 bit if the UE is configured with only one duration by pdcch-SkippingDurationList;

– 2 bits if the UE is configured with more than one duration by pdcch-SkippingDurationList.

– 1 or 2 bits, if pdcch-SkippingDurationList is not configured and if searchSpaceGroupIdList-r17 is configured

– 2 bits if the UE is configured by searchSpaceGroupIdList-r17 with search space set(s) with group index 0, search space set(s) with group index 1 and search space set(s) with group index 2;

– 2 bits, if pdcch-SkippingDurationList is configured and if searchSpaceGroupIdList-r17 is configured

– 0 bit, otherwise

A UE does not expect that the bit width of a field in DCI format 0_2 with CRC scrambled by CS-RNTI is larger than corresponding bit width of same field in DCI format 0_2 with CRC scrambled by C-RNTI for the same serving cell. If the bit width of a field in the DCI format 0_2 with CRC scrambled by CS-RNTI is not equal to that of the corresponding field in the DCI format 0_2 with CRC scrambled by C-RNTI for the same serving cell, a number of most significant bits with value set to ‘0’ are inserted to the field in DCI format 0_2 with CRC scrambled by CS-RNTI until the bit width equals that of the corresponding field in the DCI format 0_2 with CRC scrambled by C-RNTI for the same serving cell.

For a UE configured with scheduling on the primary cell from an SCell, if prior to padding the number of information bits in DCI format 0_2 carried by PDCCH on the primary cell is not equal to the number of information bits in DCI format 0_2 carried by PDCCH on the SCell for scheduling on the primary cell, zeros shall be appended to the DCI format 0_2 with smaller size until the payload size is the same.

– If application of step 4B in clause 7.3.1.0 results in additional zero padding for DCI format 0_2 for scheduling on the primary cell, corresponding zeros shall be appended to both DCI format 0_2 monitored on the primary cell and DCI format 0_2 monitored on the SCell for scheduling on the primary cell.

– If the SCell is deactivated, the UE determines the number of information bits in DCI format 0_2 carried by PDCCH on the primary cell based on a DL BWP provided by firstActiveDownlinkBWP-Id for the SCell. If the active DL BWP of the SCell is a dormant DL BWP, the UE determines the number of information bits in DCI format 0_2 carried by PDCCH on the primary cell based on a DL BWP provided by firstWithinActiveTimeBWP-Id for the SCell.

Table 7.3.1.1.3-1: 1 bit SRS request in DCI format 0_2 and DCI format 1_2

Value of SRS request field	Triggered aperiodic SRS resource set(s) for DCI format 0_2 and 1_2
0	No aperiodic SRS resource set triggered
1	SRS resource set(s) configured with higher layer parameter aperiodicSRS-ResourceTrigger set to 1 or an entry in aperiodicSRS-ResourceTriggerList set to 1

7.3.1.2 DCI formats for scheduling of PDSCH

7.3.1.2.1 Format 1_0

DCI format 1_0 is used for the scheduling of PDSCH in one DL cell.

The following information is transmitted by means of the DCI format 1_0 with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI:

– Identifier for DCI formats – 1 bits

– The value of this bit field is always set to 1, indicating a DL DCI format

– Frequency domain resource assignment – bits where is given by clause 7.3.1.0

If the CRC of the DCI format 1_0 is scrambled by C-RNTI and the "Frequency domain resource assignment" field are of all ones, the DCI format 1_0 is for random access procedure initiated by a PDCCH order, with all remaining fields set as follows:

– Random Access Preamble index – 6 bits according to ra-PreambleIndex in Clause 5.1.2 of [8, TS38.321]

– UL/SUL indicator – 1 bit. If the value of the "Random Access Preamble index" is not all zeros and if the UE is configured with supplementaryUplink in ServingCellConfig in the cell, this field indicates which UL carrier in the cell to transmit the PRACH according to Table 7.3.1.1.1-1; otherwise, this field is reserved

– SS/PBCH index – 6 bits. If the value of the "Random Access Preamble index" is not all zeros, this field indicates the SS/PBCH that shall be used to determine the RACH occasion for the PRACH transmission; otherwise, this field is reserved.

– PRACH Mask index – 4 bits. If the value of the "Random Access Preamble index" is not all zeros, this field indicates the RACH occasion associated with the SS/PBCH indicated by "SS/PBCH index" for the PRACH transmission, according to Clause 5.1.1 of [8, TS38.321]; otherwise, this field is reserved

– Reserved bits – 12 bits for operation in a cell with shared spectrum channel access in frequency range 1 or when the DCI format is monitored in common search space for operation in a cell in frequency range 2-2; otherwise 10 bits

Otherwise, all remaining fields are set as follows:

– Time domain resource assignment – 4 bits as defined in Clause 5.1.2.1 of [6, TS 38.214]

– VRB-to-PRB mapping – 1 bit according to Table 7.3.1.2.2-5

– Modulation and coding scheme – 5 bits as defined in Clause 5.1.3 of [6, TS 38.214]

– New data indicator – 1 bit

– Redundancy version – 2 bits as defined in Table 7.3.1.1.1-2

– HARQ process number – 4 bits

– Downlink assignment index – 2 bits as defined in Clause 9.1.3 of [5, TS 38.213], as counter DAI

– TPC command for scheduled PUCCH – 2 bits as defined in Clause 7.2.1 of [5, TS 38.213]

– PUCCH resource indicator – 3 bits as defined in Clause 9.2.3 of [5, TS 38.213]

– PDSCH-to-HARQ_feedback timing indicator – 3 bits as defined in Clause 9.2.3 of [5, TS38.213]

– Reserved bits – 2 bits when the DCI format is monitored in common search space for operation in a cell in frequency range 2-2 and the number of bits for the field of ‘ChannelAccess-CPext’ is 0; 0 bits otherwise

The following information is transmitted by means of the DCI format 1_0 with CRC scrambled by P-RNTI:

– Short Messages Indicator – 2 bits according to Table 7.3.1.2.1-1.

– Short Messages – 8 bits, according to Clause 6.5 of [9, TS38.331]. If only the scheduling information for Paging is carried, this bit field is reserved.

– Frequency domain resource assignment – bits. If only the short message is carried, this bit field is reserved.

– is the size of CORESET 0

– Time domain resource assignment – 4 bits as defined in Clause 5.1.2.1 of [6, TS38.214]. If only the short message is carried, this bit field is reserved.

– VRB-to-PRB mapping – 1 bit according to Table 7.3.1.2.2-5. If only the short message is carried, this bit field is reserved.

– Modulation and coding scheme – 5 bits as defined in Clause 5.1.3 of [6, TS38.214], using Table 5.1.3.1-1. If only the short message is carried, this bit field is reserved.

– TB scaling – 2 bits as defined in Clause 5.1.3.2 of [6, TS38.214]. If only the short message is carried, this bit field is reserved.

– TRS availability indication – 1, 2, 3, 4, 5, or 6 bits, where the number of bits is equal to one plus the highest value of all the indBitID(s) provided by the TRS-ResourceSetConfig if configured; 0 bits otherwise.

– Reserved bits – (8 – M) bits for operation in a cell with shared spectrum channel access in frequency range 1 or for operation in a cell in frequency range 2-2; (6 – M) bits for operation in a cell without shared spectrum channel access, where the value of M is the number of bits for the field of ‘TRS availability indication’ as defined above.

The following information is transmitted by means of the DCI format 1_0 with CRC scrambled by SI-RNTI:

– Frequency domain resource assignment – bits

– is the size of CORESET 0

– Time domain resource assignment – 4 bits as defined in Clause 5.1.2.1 of [6, TS38.214]

– VRB-to-PRB mapping – 1 bit according to Table 7.3.1.2.2-5

– Modulation and coding scheme – 5 bits as defined in Clause 5.1.3 of [6, TS38.214], using Table 5.1.3.1-1

– Redundancy version – 2 bits as defined in Table 7.3.1.1.1-2

– System information indicator – 1 bit as defined in Table 7.3.1.2.1-2

– Reserved bits – 17 bits for operation in a cell with shared spectrum channel access in frequency range 1 or for operation in a cell in frequency range 2-2; otherwise 15 bits

The following information is transmitted by means of the DCI format 1_0 with CRC scrambled by RA-RNTI or MsgB-RNTI:

– Frequency domain resource assignment – bits

– is the size of CORESET 0 if CORESET 0 is configured for the cell and is the size of initial DL bandwidth part if CORESET 0 is not configured for the cell

– Time domain resource assignment – 4 bits as defined in Clause 5.1.2.1 of [6, TS38.214]

– VRB-to-PRB mapping – 1 bit according to Table 7.3.1.2.2-5

– Modulation and coding scheme – 5 bits as defined in Clause 5.1.3 of [6, TS38.214], using Table 5.1.3.1-1

– TB scaling – 2 bits as defined in Clause 5.1.3.2 of [6, TS38.214]

– LSBs of SFN – 2 bits for the DCI format 1_0 with CRC scrambled by MsgB-RNTI as defined in Clause 8.2A of [5, TS 38.213] if msgB-responseWindow is configured to be larger than 10 ms; or 2 bits for the DCI format 1_0 with CRC scrambled by RA-RNTI as defined in Clause 8.2 of [5, TS 38.213] for operation in a cell with shared spectrum channel access if ra-ResponseWindow or ra-ResponseWindow-v1610 is configured to be larger than 10 ms; 0 bit otherwise

– Reserved bits – (16 – A) bits for operation in a cell without shared spectrum access in frequency range 1 and frequency range 2-1, (18 – A) for operation in a cell with shared spectrum access in frequency range 1 or for operation in a cell in frequency range 2-2, where the value of A is the number of bits for the field of ‘LSBs of SFN’ as defined above

The following information is transmitted by means of the DCI format 1_0 with CRC scrambled by TC-RNTI:

– Identifier for DCI formats – 1 bit

– The value of this bit field is always set to 1, indicating a DL DCI format

– Frequency domain resource assignment – bits

– is the size of CORESET 0

– Time domain resource assignment – 4 bits as defined in Clause 5.1.2.1 of [6, TS38.214]

– VRB-to-PRB mapping – 1 bit according to Table 7.3.1.2.2-5

– Modulation and coding scheme – 5 bits as defined in Clause 5.1.3 of [6, TS38.214], using Table 5.1.3.1-1

– New data indicator – 1 bit

– Redundancy version – 2 bits as defined in Table 7.3.1.1.1-2

– HARQ process number – 4 bits

– Downlink assignment index – 2 bits, reserved

– TPC command for scheduled PUCCH – 2 bits as defined in Clause 7.2.1 of [5, TS38.213]

– PUCCH resource indicator – 3 bits as defined in Clause 9.2.3 of [5, TS38.213]

– PDSCH-to-HARQ_feedback timing indicator – 3 bits as defined in Clause 9.2.3 of [5, TS38.213]

Table 7.3.1.2.1-1: Short Message indicator

Bit field	Short Message indicator
00	Reserved
01	Only scheduling information for Paging is present in the DCI
10	Only short message is present in the DCI
11	Both scheduling information for Paging and short message are present in the DCI

Table 7.3.1.2.1-2: System information indicator

Bit field	System information indicator
0	SIB1 [9, TS38.331, Clause 5.2.1]
1	SI message [9, TS38.331, Clause 5.2.1]

7.3.1.2.2 Format 1_1

DCI format 1_1 is used for the scheduling of one or multiple PDSCH in one cell.

The following information is transmitted by means of the DCI format 1_1 with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI:

– Identifier for DCI formats – 1 bits

– The value of this bit field is always set to 1, indicating a DL DCI format

– Carrier indicator – 0 or 3 bits as defined in Clause 10.1 of [5, TS 38.213]. This field is reserved when this format is carried by PDCCH on the primary cell and the UE is configured for scheduling on the primary cell from an SCell, with the same number of bits as that in this format carried by PDCCH on the SCell for scheduling on the primary cell.

– Bandwidth part indicator – 0, 1 or 2 bits as determined by the number of DL BWPs configured by higher layers, excluding the initial DL bandwidth part. The bitwidth for this field is determined as bits, where

– if , in which case the bandwidth part indicator is equivalent to the ascending order of the higher layer parameter BWP-Id;

– otherwise , in which case the bandwidth part indicator is defined in Table 7.3.1.1.2-1;

If a UE does not support active BWP change via DCI, the UE ignores this bit field.

– Frequency domain resource assignment – number of bits determined by the following, where is the size of the active DL bandwidth part:

– bits if only resource allocation type 0 is configured, where is defined in Clause 5.1.2.2.1 of [6, TS38.214],

– bits if only resource allocation type 1 is configured, or

– bits if resourceAllocation is configured as ‘dynamicSwitch’.

– For resource allocation type 0, the LSBs provide the resource allocation as defined in Clause 5.1.2.2.1 of [6, TS 38.214].

– For resource allocation type 1, the LSBs provide the resource allocation as defined in Clause 5.1.2.2.2 of [6, TS 38.214]

– Time domain resource assignment – 0, 1, 2, 3, 4, 5 or 6 bits

– If the higher layer parameter pdsch-TimeDomainResourceAllocationListForMultiPDSCH is not configured and if the higher layer parameter pdsch-TimeDomainAllocationList is configured, 0, 1, 2, 3 or 4 bits as defined in Clause 5.1.2.1 of [6, TS 38.214]. The bitwidth for this field is determined as bits, where I is the number of entries in the higher layer parameter pdsch-TimeDomainAllocationList if the higher layer parameter is configured;

– if the higher layer parameter pdsch-TimeDomainResourceAllocationListForMultiPDSCH is configured, 0, 1, 2, 3, 4, 5 or 6 bits as defined in Clause 5.1.2.1 of [6, TS38.214]. The bitwidth for this field is determined as bits, where I is the number of entries in the higher layer parameter pdsch-TimeDomainResourceAllocationListForMultiPDSCH;

– otherwise I is the number of entries in the default table.

– VRB-to-PRB mapping – 0 or 1 bit:

– 0 bit if only resource allocation type 0 is configured or if interleaved VRB-to-PRB mapping is not configured by high layers;

– 1 bit according to Table 7.3.1.2.2-5 otherwise, only applicable to resource allocation type 1, as defined in Clause 7.3.1.6 of [4, TS 38.211].

– PRB bundling size indicator – 0 bit if the higher layer parameter prb-BundlingType is not configured or is set to ‘staticBundling’, or 1 bit if the higher layer parameter prb-BundlingType is set to ‘dynamicBundling’ according to Clause 5.1.2.3 of [6, TS 38.214].

– Rate matching indicator – 0, 1, or 2 bits according to higher layer parameters rateMatchPatternGroup1 and rateMatchPatternGroup2, where the MSB is used to indicate rateMatchPatternGroup1 and the LSB is used to indicate rateMatchPatternGroup2 when there are two groups.

– ZP CSI-RS trigger – 0, 1, or 2 bits as defined in Clause 5.1.4.2 of [6, TS 38.214]. The bitwidth for this field is determined as bits, where is the number of aperiodic ZP CSI-RS resource sets configured by higher layer.

For transport block 1:

– Modulation and coding scheme – 5 bits as defined in Clause 5.1.3.1 of [6, TS 38.214]

– New data indicator – 1 bit if the number of scheduled PDSCH indicated by the Time domain resource assignment field is 1; otherwise 2, 3, 4, 5, 6, 7 or 8 bits determined based on the maximum number of schedulable PDSCH among all entries in the higher layer parameter pdsch-TimeDomainResourceAllocationListForMultiPDSCH, where each bit corresponds to one scheduled PDSCH as defined in clause 5.1.3 in [6, TS 38.214].

– Redundancy version – number of bits determined by the following:

– 2 bits as defined in Table 7.3.1.1.1-2 if the number of scheduled PDSCH indicated by the Time domain resource assignment field is 1;

– otherwise 2, 3, 4, 5, 6, 7 or 8 bits determined by the maximum number of schedulable PDSCHs among all entries in the higher layer parameter pdsch-TimeDomainResourceAllocationListForMultiPDSCH, where each bit corresponds to one scheduled PDSCH as defined in clause 5.1.3 in [6, TS 38.214] and redundancy version is determined according to Table 7.3.1.1.2-34.

For transport block 2 (only present if maxNrofCodeWordsScheduledByDCI equals 2):

– Modulation and coding scheme – 5 bits as defined in Clause 5.1.3.1 of [6, TS 38.214]

– Redundancy version – number of bits determined by the following:

– 2 bits as defined in Table 7.3.1.1.1-2 if the number of scheduled PDSCH indicated by the Time domain resource assignment field is 1;

If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and the value of maxNrofCodeWordsScheduledByDCI for the indicated bandwidth part equals 2 and the value of maxNrofCodeWordsScheduledByDCI for the active bandwidth part equals 1, the UE assumes zeros are padded when interpreting the "Modulation and coding scheme", "New data indicator", and "Redundancy version" fields of transport block 2 according to Clause 12 of [5, TS38.213], and the UE ignores the "Modulation and coding scheme", "New data indicator", and "Redundancy version" fields of transport block 2 for the indicated bandwidth part.

– HARQ process number – 5 bits if higher layer parameter harq-ProcessNumberSizeDCI-1-1 is configured; otherwise 4 bits

– Downlink assignment index – number of bits as defined in the following

– 6 bits if more than one serving cell are configured in the DL and the higher layer parameter nfi-TotalDAI-Included is configured. The 4 MSB bits are the counter DAI and the total DAI for the scheduled PDSCH group, and the 2 LSB bits are the total DAI for the non-scheduled PDSCH group.

– 4 bits if only one serving cell is configured in the DL and the higher layer parameter nfi-TotalDAI-Included is configured. The 2 MSB bits are the counter DAI for the scheduled PDSCH group, and the 2 LSB bits are the total DAI for the non-scheduled PDSCH group;

– 4 bits if more than one serving cell are configured in the DL, the higher layer parameter pdsch-HARQ-ACK-Codebook=dynamic or pdsch-HARQ-ACK-Codebook-r16= enhancedDynamic, and nfi-TotalDAI-Included is not configured, where the 2 MSB bits are the counter DAI and the 2 LSB bits are the total DAI;

– 4 bits if one serving cell is configured in the DL, and the higher layer parameter pdsch-HARQ-ACK-Codebook=dynamic, and the UE is not provided coresetPoolIndex or is provided coresetPoolIndex with value 0 for one or more first CORESETs and is provided coresetPoolIndex with value 1 for one or more second CORESETs, and is provided ackNackFeedbackMode = joint, where the 2 MSB bits are the counter DAI and the 2 LSB bits are the total DAI;

– 2 bits if only one serving cell is configured in the DL, the higher layer parameter pdsch-HARQ-ACK-Codebook=dynamic or pdsch-HARQ-ACK-Codebook-r16=enhancedDynamic, and nfi-TotalDAI-Included is not configured, when the UE is not configured with coresetPoolIndex or the value of coresetPoolIndex is the same for all CORESETs if coresetPoolIndex is provided or the UE is not configured with ackNackFeedbackMode = joint, where the 2 bits are the counter DAI;

– 0 bits otherwise.

If the UE is configured with a PUCCH-SCell, the number of serving cells is determined within a PUCCH group.

If the UE is configured with a PUCCH-SCell, pdsch-HARQ-ACK-Codebook is replaced by pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup-r16 if present for the secondary PUCCH group.

If higher layer parameter priorityIndicatorDCI-1-1 is configured, if the bit width of the Downlink assignment index in DCI format 1_1 for one HARQ-ACK codebook is not equal to that of the Downlink assignment index in DCI format 1_1 for the other HARQ-ACK codebook, a number of most significant bits with value set to ‘0’ are inserted to smaller Downlink assignment index until the bit width of the Downlink assignment index in DCI format 1_1 for the two HARQ-ACK codebooks are the same.

– TPC command for scheduled PUCCH – 2 bits as defined in Clause 7.2.1 of [5, TS 38.213]

– Second TPC command for scheduled PUCCH – 2 bits as defined in Clause 7.2.1 of [5, TS 38.213] if higher layer parameter SecondTPCFieldDCI-1-1 is configured; 0 bit otherwise.

– PUCCH resource indicator – 3 bits as defined in Clause 9.2.3 of [5, TS 38.213]

If higher layer parameter priorityIndicatorDCI-1-1 is configured, if the bit width of the PDSCH-to-HARQ_feedback timing indicator in DCI format 1_1 for one HARQ-ACK codebook is not equal to that of the PDSCH-to-HARQ_feedback timing indicator in DCI format 1_1 for the other HARQ-ACK codebook on the same cell for PUCCH transmission, a number of most significant bits with value set to ‘0’ are inserted to smaller PDSCH-to-HARQ_feedback timing indicator until the bit width of the PDSCH-to-HARQ_feedback timing indicator in DCI format 1_1 for the two HARQ-ACK codebooks are the same.

If higher layer parameter pucch-sSCellDyn is configured, if the bit width of the PDSCH-to-HARQ_feedback timing indicator in DCI format 1_1 associated with one cell for PUCCH transmission is not equal to that of the PDSCH-to-HARQ_feedback timing indicator in DCI format 1_1 associated with the other cell for PUCCH transmision, a number of most significant bits with value set to ‘0’ are inserted to smaller PDSCH-to-HARQ_feedback timing indicator until the bit width of the PDSCH-to-HARQ_feedback timing indicator in DCI format 1_1 associated with the two cells are the same.

If the UE is configured with a PUCCH-SCell, pucch-sSCellDyn is replaced by pucch-sSCellDynSecondaryPUCCHgroup for the secondary PUCCH group.

– One-shot HARQ-ACK request – 0 or 1 bit.

– 1 bit if higher layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16 or pdsch-HARQ-ACK-EnhType3List is configured;

– 0 bit otherwise.

If the UE is configured with a PUCCH-SCell, pdsch-HARQ-ACK-EnhType3List is replaced by pdsch-HARQ-ACK-EnhType3SecondaryList for the secondary PUCCH group.

– Enhanced Type 3 codebook indicator – 0, 1, 2, or 3 bits.

– 0 bit if pdsch-HARQ-ACK-EnhType3DCI-Field is not configured;

– bits otherwise, where is the number of entries in the higher layer parameter pdsch-HARQ-ACK-EnhType3List.

If the UE is configured with a PUCCH-SCell, pdsch-HARQ-ACK-EnhType3DCI-Field is replaced by pdsch-HARQ-ACK-EnhType3DCI-FieldSecondaryPUCCHgroup for the secondary PUCCH group, and pdsch-HARQ-ACK-EnhType3List is replaced by pdsch-HARQ-ACK-EnhType3SecondaryList for the secondary PUCCH group.

– PDSCH group index – 0 or 1 bit.

– 1 bit if the higher layer parameter pdsch-HARQ-ACK-Codebook-r16= enhancedDynamic;

– 0 bit otherwise.

– New feedback indicator – 0, 1 or 2 bits.

– 1 bit if the higher layer parameter pdsch-HARQ-ACK-Codebook-r16= enhancedDynamic and the higher layer parameter nfi-TotalDAI-Included is not configured;

– 2 bits if the higher layer parameter pdsch-HARQ-ACK-Codebook-r16= enhancedDynamic and the higher layer parameter nfi-TotalDAI-Included=true; the MSB corresponds to the scheduled PDSCH group, and the LSB corresponds to the non-scheduled PDSCH group, as defined in [TS38.213] clause 9.1.3.3

– 0 bit otherwise.

– Number of requested PDSCH group(s) – 0 or 1 bit.

– 1 bit if the higher layer parameter pdsch-HARQ-ACK-Codebook-r16= enhancedDynamic;

– 0 bit otherwise.

– HARQ-ACK retransmission indicator – 0 or 1 bit.

– 1 bit if higher layer parameter pdsch-HARQ-ACK-Retx is configured.

– 0 bit otherwise.

If the UE is configured with a PUCCH-SCell, pdsch-HARQ-ACK-Retx is replaced by pdsch-HARQ-ACK-RetxSecondaryPUCCHgroup for the secondary PUCCH group.

– Antenna port(s) – 4, 5, or 6 bits as defined by Tables 7.3.1.2.2-1/2/3/4 and Tables 7.3.1.2.2-1A/2A/3A/4A, where the number of CDM groups without data of values 1, 2, and 3 refers to CDM groups {0}, {0,1}, and {0, 1,2} respectively. The antenna ports shall be determined according to the ordering of DMRS port(s) given by Tables 7.3.1.2.2-1/2/3/4 or Tables 7.3.1.2.2-1A/2A/3A/4A. When a UE receives an activation command that maps at least one codepoint of DCI field ‘Transmission Configuration Indication‘ to two TCI states, the UE shall use Table 7.3.1.2.2-1A/2A/3A/4A; otherwise, it shall use Tables 7.3.1.2.2-1/2/3/4. The UE can receive an entry with DMRS ports equals to 1000, 1002, 1003 when two TCI states are indicated in a codepoint of DCI field ‘Transmission Configuration Indication‘.

If a UE is configured with both dmrs-DownlinkForPDSCH-MappingTypeA and dmrs-DownlinkForPDSCH-MappingTypeB, the bitwidth of this field equals , where is the "Antenna ports" bitwidth derived according to dmrs-DownlinkForPDSCH-MappingTypeA and is the "Antenna ports" bitwidth derived according to dmrs-DownlinkForPDSCH-MappingTypeB. A number of zeros are padded in the MSB of this field, if the mapping type of the PDSCH corresponds to the smaller value of and .

– Transmission configuration indication – 0 bit if higher layer parameter tci-PresentInDCI is not enabled; otherwise 3 bits as defined in Clause 5.1.5 of [6, TS38.214].

If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part,

– if the higher layer parameter tci-PresentInDCI is not enabled for the CORESET used for the PDCCH carrying the DCI format 1_1,

– the UE assumes tci-PresentInDCI is not enabled for all CORESETs in the indicated bandwidth part;

– otherwise,

– the UE assumes tci-PresentInDCI is enabled for all CORESETs in the indicated bandwidth part.

– SRS offset indicator – 0, 1 or 2 bits.

– CBG transmission information (CBGTI) – 0 bit if higher layer parameter codeBlockGroupTransmission for PDSCH is not configured, otherwise, 2, 4, 6, or 8 bits as defined in Clause 5.1.7 of [6, TS38.214], determined by the higher layer parameters maxCodeBlockGroupsPerTransportBlock and maxNrofCodeWordsScheduledByDCI for the PDSCH.

If higher layer parameter priorityIndicatorDCI-1-1 is configured, if the bit width of the CBG transmission information in DCI format 1_1 for one HARQ-ACK codebook is not equal to that of the CBG transmission information in DCI format 1_1 for the other HARQ-ACK codebook, a number of most significant bits with value set to ‘0’ are inserted to smaller CBG transmission information until the bit width of the CBG transmission information in DCI format 1_1 for the two HARQ-ACK codebooks are the same.

– CBG flushing out information (CBGFI) – 1 bit if higher layer parameter codeBlockGroupFlushIndicator is configured as "TRUE", 0 bit otherwise.

If higher layer parameter priorityIndicatorDCI-1-1 is configured, if the bit width of the CBG flushing out information in DCI format 1_1 for one HARQ-ACK codebook is not equal to that of the CBG flushing out information in DCI format 1_1 for the other HARQ-ACK codebook, a number of most significant bits with value set to ‘0’ are inserted to smaller CBG flushing out information until the bit width of the CBG flushing out information in DCI format 1_1 for the two HARQ-ACK codebooks are the same.

– DMRS sequence initialization – 1 bit.

– Priority indicator – 0 bit if higher layer parameter priorityIndicatorDCI-1-1 is not configured; otherwise 1 bit as defined in Clause 9 in [5, TS 38.213].

– ChannelAccess-CPext – 0, 1, 2, 3 or 4 bits. The bitwidth for this field is determined as bits, where I is the number of entries in the higher layer parameter ul-AccessConfigListDCI-1-1 or in Table 7.3.1.1.1-4A if channelAccessMode-r16 = "semiStatic" is provided, for operation in a cell with shared spectrum channel access; otherwise 0 bit. One or more entries from Table 7.3.1.2.2-6 or Table 7.3.1.2.2-6A are configured by the higher layer parameter ul-AccessConfigListDCI-1-1.

– Minimum applicable scheduling offset indicator – 0 or 1 bit

– 0 bit if higher layer parameter minimumSchedulingOffsetK0 is not configured;

– 1 bit if higher layer parameter minimumSchedulingOffsetK0 is configured. The 1 bit indication is used to determine the minimum applicable K0 for the active DL BWP and the minimum applicable K2 value for the active UL BWP, if configured respectively, according to Table 7.3.1.1.2-33. If the minimum applicable K0 is indicated, the minimum applicable value of the aperiodic CSI-RS triggering offset for an active DL BWP shall be the same as the minimum applicable K0 value.

If one-shot HARQ-ACK request is not present or set to ‘0’, and all bits of frequency domain resource assignment are set to 0 for resource allocation type 0 or set to 1 for resource allocation type 1 or set to 0 or 1 for dynamic switch resource allocation type, this field is reserved and the following fields among the fields above are used for SCell dormancy indication, where each bit corresponds to one of the configured SCell(s), with MSB to LSB of the following fields concatenated in the order below corresponding to the SCell with lowest to highest SCell index

– Modulation and coding scheme of transport block 1

– New data indicator of transport block 1

– Redundancy version of transport block 1

– HARQ process number

– Antenna port(s)

– DMRS sequence initialization

– PDCCH monitoring adaptation indication – 0, 1 or 2 bits

– 1 or 2 bits, if searchSpaceGroupIdList-r17 is not configured and if pdcch-SkippingDurationList is configured

– 1 bit if the UE is configured with only one duration by pdcch-SkippingDurationList;

– 2 bits if the UE is configured with more than one duration by pdcch-SkippingDurationList.

– 1 or 2 bits, if pdcch-SkippingDurationList is not configured and if searchSpaceGroupIdList-r17 is configured

– 2 bits if the UE is configured by searchSpaceGroupIdList-r17 with search space set(s) with group index 0, search space set(s) with group index 1 and search space set(s) with group index 2;

– 2 bits, if pdcch-SkippingDurationList is configured and if searchSpaceGroupIdList-r17 is configured

– 0 bit, otherwise

– PUCCH Cell indicator – 0 or 1 bit.

– 1 bit if higher layer parameter pucch-sSCellDyn is configured.

– 0 bit otherwise.

If the UE is configured with a PUCCH-SCell, pucch-sSCellDyn is replaced by pucch-sSCellDynSecondaryPUCCHgroup for the secondary PUCCH group.

If DCI formats 1_1 are monitored in multiple search spaces associated with multiple CORESETs in a BWP for scheduling the same serving cell, zeros shall be appended until the payload size of the DCI formats 1_1 monitored in the multiple search spaces equal to the maximum payload size of the DCI format 1_1 monitored in the multiple search spaces.

For a UE configured with scheduling on the primary cell from an SCell, if prior to padding the number of information bits in DCI format 1_1 carried by PDCCH on the primary cell is not equal to the number of information bits in DCI format 1_1 carried by PDCCH on the SCell for scheduling on the primary cell, zeros shall be appended to the DCI format 1_1 with smaller size until the payload size is the same.

– If application of step 4C in clause 7.3.1.0 results in additional zero padding for DCI format 1_1 for scheduling on the primary cell, corresponding zeros shall be appended to both DCI format 1_1 monitored on the primary cell and DCI format 1_1 monitored on the SCell for scheduling on the primary cell.

– If the SCell is deactivated, the UE determines the number of information bits in DCI format 1_1 carried by PDCCH on the primary cell based on a DL BWP provided by firstActiveDownlinkBWP-Id for the SCell. If the active DL BWP of the SCell is a dormant DL BWP, the UE determines the number of information bits in DCI format 1_1 carried by PDCCH on the primary cell based on a DL BWP provided by firstWithinActiveTimeBWP-Id for the SCell.

Table 7.3.1.2.2-1: Antenna port(s) (1000 + DMRS port), dmrs-Type=1, maxLength=1

One Codeword: Codeword 0 enabled, Codeword 1 disabled
Value	Number of DMRS CDM group(s) without data	DMRS port(s)
0	1	0
1	1	1
2	1	0,1
3	2	0
4	2	1
5	2	2
6	2	3
7	2	0,1
8	2	2,3
9	2	0-2
10	2	0-3
11	2	0,2
12-15	Reserved	Reserved

Table 7.3.1.2.2-1A: Antenna port(s) (1000 + DMRS port), dmrs-Type=1, maxLength=1

One Codeword: Codeword 0 enabled, Codeword 1 disabled
Value	Number of DMRS CDM group(s) without data	DMRS port(s)
0	1	0
1	1	1
2	1	0,1
3	2	0
4	2	1
5	2	2
6	2	3
7	2	0,1
8	2	2,3
9	2	0-2
10	2	0-3
11	2	0,2
12	2	0,2,3
13-15	Reserved	Reserved

Table 7.3.1.2.2-2: Antenna port(s) (1000 + DMRS port), dmrs-Type=1, maxLength=2

One Codeword: Codeword 0 enabled, Codeword 1 disabled				Two Codewords: Codeword 0 enabled, Codeword 1 enabled
Value	Number of DMRS CDM group(s) without data	DMRS port(s)	Number of front-load symbols	Value	Number of DMRS CDM group(s) without data	DMRS port(s)	Number of front-load symbols
0	1	0	1	0	2	0-4	2
1	1	1	1	1	2	0,1,2,3,4,6	2
2	1	0,1	1	2	2	0,1,2,3,4,5,6	2
3	2	0	1	3	2	0,1,2,3,4,5,6,7	2
4	2	1	1	4-31	reserved	reserved	reserved
5	2	2	1
6	2	3	1
7	2	0,1	1
8	2	2,3	1
9	2	0-2	1
10	2	0-3	1
11	2	0,2	1
12	2	0	2
13	2	1	2
14	2	2	2
15	2	3	2
16	2	4	2
17	2	5	2
18	2	6	2
19	2	7	2
20	2	0,1	2
21	2	2,3	2
22	2	4,5	2
23	2	6,7	2
24	2	0,4	2
25	2	2,6	2
26	2	0,1,4	2
27	2	2,3,6	2
28	2	0,1,4,5	2
29	2	2,3,6,7	2
30	2	0,2,4,6	2
31	Reserved	Reserved	Reserved

Table 7.3.1.2.2-2A: Antenna port(s) (1000 + DMRS port), dmrs-Type=1, maxLength=2

One Codeword: Codeword 0 enabled, Codeword 1 disabled				Two Codewords: Codeword 0 enabled, Codeword 1 enabled
Value	Number of DMRS CDM group(s) without data	DMRS port(s)	Number of front-load symbols	Value	Number of DMRS CDM group(s) without data	DMRS port(s)	Number of front-load symbols
0	1	0	1	0	2	0-4	2
1	1	1	1	1	2	0,1,2,3,4,6	2
2	1	0,1	1	2	2	0,1,2,3,4,5,6	2
3	2	0	1	3	2	0,1,2,3,4,5,6,7	2
4	2	1	1	4-31	reserved	reserved	reserved
5	2	2	1
6	2	3	1
7	2	0,1	1
8	2	2,3	1
9	2	0-2	1
10	2	0-3	1
11	2	0,2	1
12	2	0	2
13	2	1	2
14	2	2	2
15	2	3	2
16	2	4	2
17	2	5	2
18	2	6	2
19	2	7	2
20	2	0,1	2
21	2	2,3	2
22	2	4,5	2
23	2	6,7	2
24	2	0,4	2
25	2	2,6	2
26	2	0,1,4	2
27	2	2,3,6	2
28	2	0,1,4,5	2
29	2	2,3,6,7	2
30	2	0,2,4,6	2
31	2	0,2,3	1

Table 7.3.1.2.2-3: Antenna port(s) (1000 + DMRS port), dmrs-Type=2, maxLength=1

One codeword: Codeword 0 enabled, Codeword 1 disabled			Two codewords: Codeword 0 enabled, Codeword 1 enabled
Value	Number of DMRS CDM group(s) without data	DMRS port(s)	Value	Number of DMRS CDM group(s) without data	DMRS port(s)
0	1	0	0	3	0-4
1	1	1	1	3	0-5
2	1	0,1	2-31	reserved	reserved
3	2	0
4	2	1
5	2	2
6	2	3
7	2	0,1
8	2	2,3
9	2	0-2
10	2	0-3
11	3	0
12	3	1
13	3	2
14	3	3
15	3	4
16	3	5
17	3	0,1
18	3	2,3
19	3	4,5
20	3	0-2
21	3	3-5
22	3	0-3
23	2	0,2
24-31	Reserved	Reserved

Table 7.3.1.2.2-3A: Antenna port(s) (1000 + DMRS port), dmrs-Type=2, maxLength=1

One codeword: Codeword 0 enabled, Codeword 1 disabled			Two codewords: Codeword 0 enabled, Codeword 1 enabled
Value	Number of DMRS CDM group(s) without data	DMRS port(s)	Value	Number of DMRS CDM group(s) without data	DMRS port(s)
0	1	0	0	3	0-4
1	1	1	1	3	0-5
2	1	0,1	2-31	reserved	reserved
3	2	0
4	2	1
5	2	2
6	2	3
7	2	0,1
8	2	2,3
9	2	0-2
10	2	0-3
11	3	0
12	3	1
13	3	2
14	3	3
15	3	4
16	3	5
17	3	0,1
18	3	2,3
19	3	4,5
20	3	0-2
21	3	3-5
22	3	0-3
23	2	0,2
24	2	0,2,3
25-31	Reserved	Reserved

Table 7.3.1.2.2-4: Antenna port(s) (1000 + DMRS port), dmrs-Type=2, maxLength=2

One codeword: Codeword 0 enabled, Codeword 1 disabled				Two Codewords: Codeword 0 enabled, Codeword 1 enabled
Value	Number of DMRS CDM group(s) without data	DMRS port(s)	Number of front-load symbols	Value	Number of DMRS CDM group(s) without data	DMRS port(s)	Number of front-load symbols
0	1	0	1	0	3	0-4	1
1	1	1	1	1	3	0-5	1
2	1	0,1	1	2	2	0,1,2,3,6	2
3	2	0	1	3	2	0,1,2,3,6,8	2
4	2	1	1	4	2	0,1,2,3,6,7,8	2
5	2	2	1	5	2	0,1,2,3,6,7,8,9	2
6	2	3	1	6-63	Reserved	Reserved	Reserved
7	2	0,1	1
8	2	2,3	1
9	2	0-2	1
10	2	0-3	1
11	3	0	1
12	3	1	1
13	3	2	1
14	3	3	1
15	3	4	1
16	3	5	1
17	3	0,1	1
18	3	2,3	1
19	3	4,5	1
20	3	0-2	1
21	3	3-5	1
22	3	0-3	1
23	2	0,2	1
24	3	0	2
25	3	1	2
26	3	2	2
27	3	3	2
28	3	4	2
29	3	5	2
30	3	6	2
31	3	7	2
32	3	8	2
33	3	9	2
34	3	10	2
35	3	11	2
36	3	0,1	2
37	3	2,3	2
38	3	4,5	2
39	3	6,7	2
40	3	8,9	2
41	3	10,11	2
42	3	0,1,6	2
43	3	2,3,8	2
44	3	4,5,10	2
45	3	0,1,6,7	2
46	3	2,3,8,9	2
47	3	4,5,10,11	2
48	1	0	2
49	1	1	2
50	1	6	2
51	1	7	2
52	1	0,1	2
53	1	6,7	2
54	2	0,1	2
55	2	2,3	2
56	2	6,7	2
57	2	8,9	2
58-63	Reserved	Reserved	Reserved

Table 7.3.1.2.2-4A: Antenna port(s) (1000 + DMRS port), dmrs-Type=2, maxLength=2

One codeword: Codeword 0 enabled, Codeword 1 disabled				Two Codewords: Codeword 0 enabled, Codeword 1 enabled
Value	Number of DMRS CDM group(s) without data	DMRS port(s)	Number of front-load symbols	Value	Number of DMRS CDM group(s) without data	DMRS port(s)	Number of front-load symbols
0	1	0	1	0	3	0-4	1
1	1	1	1	1	3	0-5	1
2	1	0,1	1	2	2	0,1,2,3,6	2
3	2	0	1	3	2	0,1,2,3,6,8	2
4	2	1	1	4	2	0,1,2,3,6,7,8	2
5	2	2	1	5	2	0,1,2,3,6,7,8,9	2
6	2	3	1	6-63	Reserved	Reserved	Reserved
7	2	0,1	1
8	2	2,3	1
9	2	0-2	1
10	2	0-3	1
11	3	0	1
12	3	1	1
13	3	2	1
14	3	3	1
15	3	4	1
16	3	5	1
17	3	0,1	1
18	3	2,3	1
19	3	4,5	1
20	3	0-2	1
21	3	3-5	1
22	3	0-3	1
23	2	0,2	1
24	3	0	2
25	3	1	2
26	3	2	2
27	3	3	2
28	3	4	2
29	3	5	2
30	3	6	2
31	3	7	2
32	3	8	2
33	3	9	2
34	3	10	2
35	3	11	2
36	3	0,1	2
37	3	2,3	2
38	3	4,5	2
39	3	6,7	2
40	3	8,9	2
41	3	10,11	2
42	3	0,1,6	2
43	3	2,3,8	2
44	3	4,5,10	2
45	3	0,1,6,7	2
46	3	2,3,8,9	2
47	3	4,5,10,11	2
48	1	0	2
49	1	1	2
50	1	6	2
51	1	7	2
52	1	0,1	2
53	1	6,7	2
54	2	0,1	2
55	2	2,3	2
56	2	6,7	2
57	2	8,9	2
58	2	0,2,3	1
59-63	Reserved	Reserved	Reserved

Table 7.3.1.2.2-5: VRB-to-PRB mapping

Bit field mapped to index	VRB-to-PRB mapping
0	Non-interleaved
1	Interleaved

Table 7.3.1.2.2-6: Allowed entries for DCI format 1_1 and DCI format 1_2, configured by higher layer parameter ul-AccessConfigListDCI-1-1 and ul-AccessConfigListDCI-1-2, respectively, in frequency range 1

Entry index	Channel Access Type	The CP extension Text index defined in Clause 5.3.1 of [4, TS 38.211]
0	Type2C-ULChannelAccess defined in [clause 4.2.1.2.3 in 37.213]	0
1	Type2C-ULChannelAccess defined in [clause 4.2.1.2.3 in 37.213]	2
2	Type2B-ULChannelAccess defined in [clause 4.2.1.2.2 in 37.213]	0
3	Type2B-ULChannelAccess defined in [clause 4.2.1.2.2 in 37.213]	2
4	Type2A-ULChannelAccess defined in [clause 4.2.1.2.1 in 37.213]	0
5	Type2A-ULChannelAccess defined in [clause 4.2.1.2.1 in 37.213]	1
6	Type2A-ULChannelAccess defined in [clause 4.2.1.2.1 in 37.213]	3
7	Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213]	0
8	Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213]	1
9	Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213]	2
10	Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213]	3

Table 7.3.1.2.2-6A: Allowed entries for DCI format 1_1, configured by higher layer parameter ul-AccessConfigListDCI-1-1 in frequency range 2-2

Entry index	Channel Access Type
0	Type 1 channel access defined in clause 4.4.1 of 37.213
1	Type 2 channel access defined in clause 4.4.2 of 37.213
2	Type 3 channel access defined in clause 4.4.3 of 37.213

7.3.1.2.3 Format 1_2

DCI format 1_2 is used for the scheduling of PDSCH in one cell.

The following information is transmitted by means of the DCI format 1_2 with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI:

– Identifier for DCI formats – 1 bits

– The value of this bit field is always set to 1, indicating a DL DCI format.

– Carrier indicator – 0, 1, 2 or 3 bits determined by higher layer parameter carrierIndicatorSizeDCI-1-2, as defined in Clause 10.1 of [5, TS38.213]. This field is reserved when this format is carried by PDCCH on the primary cell and the UE is configured for scheduling on the primary cell from an SCell, with the same number of bits as that in this format carried by PDCCH on the SCell for scheduling on the primary cell.

– if , in which case the bandwidth part indicator is equivalent to the ascending order of the higher layer parameter BWP-Id;

– otherwise , in which case the bandwidth part indicator is defined in Table 7.3.1.1.2-1;

If a UE does not support active BWP change via DCI, the UE ignores this bit field.

– Frequency domain resource assignment – number of bits determined by the following:

– bits if only resource allocation type 0 is configured, where is defined in Clause 5.1.2.2.1 of [6, TS 38.214];

– bits if only resource allocation type 1 is configured, or bits if resourceAllocationDCI-1-2-r16 is configured as ‘dynamicSwitch’, where , is the size of the active DL bandwidth part, is defined as in clause 4.4.4.4 of [4, TS 38.211] and is determined by higher layer parameter resourceAllocationType1GranularityDCI-1-2. If the higher layer parameter resourceAllocationType1GranularityDCI-1-2 is not configured, is equal to 1.

– If resourceAllocationDCI-1-2-r16 is configured as ‘dynamicSwitch’, the MSB bit is used to indicate resource allocation type 0 or resource allocation type 1, where the bit value of 0 indicates resource allocation type 0 and the bit value of 1 indicates resource allocation type 1.

– For resource allocation type 0, the LSBs provide the resource allocation as defined in Clause 5.1.2.2.1 of [6, TS 38.214].

– For resource allocation type 1, the LSBs provide the resource allocation as defined in Clause 5.1.2.2.2 of [6, TS 38.214]

If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and if resourceAllocationDCI-1-2-r16 is configured as ‘dynamicSwitch’ for the indicated bandwidth part, the UE assumes resource allocation type 0 for the indicated bandwidth part if the bitwidth of the "Frequency domain resource assignment" field of the active bandwidth part is smaller than the bitwidth of the "Frequency domain resource assignment" field of the indicated bandwidth part.

– Time domain resource assignment – 0, 1, 2, 3, or 4 bits as defined in Clause 5.1.2.1 of [6, TS 38.214]. The bitwidth for this field is determined as bits, where I is the number of entries in the higher layer parameter pdsch-TimeDomainAllocationListDCI-1-2 if the higher layer parameter is configured, or I is the number of entries in the higher layer parameter pdsch-TimeDomainAllocationList if the higher layer parameter pdsch-TimeDomainAllocationList is configured when the higher layer parameter pdsch-TimeDomainAllocationListDCI-1-2 is not configured; otherwise I is the number of entries in the default table.

– VRB-to-PRB mapping – 0 or 1 bit:

– 0 bit if the higher layer parameter vrb-ToPRB-InterleaverDCI-1-2 is not configured;

– 1 bit according to Table 7.3.1.2.2-5 otherwise, only applicable to resource allocation type 1, as defined in Clause 7.3.1.6 of [4, TS 38.211].

– PRB bundling size indicator – 0 bit if the higher layer parameter prb-BundlingTypeDCI-1-2 is not configured or is set to ‘static’, or 1 bit if the higher layer parameter prb-BundlingTypeDCI-1-2 is set to ‘dynamic’ according to Clause 5.1.2.3 of [6, TS 38.214].

– Rate matching indicator – 0, 1, or 2 bits according to higher layer parameters rateMatchPatternGroup1DCI-1-2 and rateMatchPatternGroup2DCI-1-2, where the MSB is used to indicate rateMatchPatternGroup1DCI-1-2 and the LSB is used to indicate rateMatchPatternGroup2DCI-1-2 when there are two groups.

– Modulation and coding scheme – 5 bits as defined in Clause 5.1.3.1 of [6, TS 38.214]

– New data indicator – 1 bit

– Redundancy version – 0, 1 or 2 bits determined by higher layer parameter numberOfBitsForRV-DCI-1-2

– If 0 bit is configured, rv_id to be applied is 0;

– 1 bit according to Table 7.3.1.2.3-1;

– 2 bits according to Table 7.3.1.1.1-2.

– HARQ process number – number of bits determined by the following:

– 0, 1, 2, 3, 4 or 5 bits determined by higher layer parameter harq-ProcessNumberSizeDCI-1-2-r17 if configured;

– otherwise 0, 1, 2, 3 or 4 bits determined by higher layer parameter harq-ProcessNumberSizeDCI-1-2

– Downlink assignment index – 0, 1, 2 or 4 bits

– 0 bit if the higher layer parameter downlinkAssignmentIndexDCI-1-2 is not configured;

– 1, 2 or 4 bits determined by higher layer parameter downlinkAssignmentIndexDCI-1-2 otherwise,

– 4 bits if more than one serving cell are configured in the DL and the higher layer parameter pdsch-HARQ-ACK-Codebook=dynamic, where the 2 MSB bits are the counter DAI and the 2 LSB bits are the total DAI

– 4 bits if only one serving cell is configured in the DL and the higher layer parameter pdsch-HARQ-ACK-Codebook=dynamic, and the UE is not provided coresetPoolIndex or is provided coresetPoolIndex with value 0 for one or more first CORESETs and is provided coresetPoolIndex with value 1 for one or more second CORESETs, and is provided ackNackFeedbackMode = joint, where the 2 MSB bits are the counter DAI and the 2 LSB bits are the total DAI.

– 1 or 2 bits if only one serving cell is configured in the DL and the higher layer parameter pdsch-HARQ-ACK-Codebook=dynamic, when the UE is not configured with coresetPoolIndex or the value of coresetPoolIndex is the same for all CORESETs if coresetPoolIndex is provided or the UE is not configured with ackNackFeedbackMode = joint, where the 1 bit or 2 bits are the counter DAI.

If the UE is configured with a PUCCH-SCell, the number of serving cells is determined within a PUCCH group.

If the UE is configured with a PUCCH-SCell, pdsch-HARQ-ACK-Codebook is replaced by pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup-r16 if present for the secondary PUCCH group.

If higher layer parameter priorityIndicatorDCI-1-2 is configured, if the bit width of the Downlink assignment index in DCI format 1_2 for one HARQ-ACK codebook is not equal to that of the Downlink assignment index in DCI format 1_2 for the other HARQ-ACK codebook, a number of most significant bits with value set to ‘0’ are inserted to smaller Downlink assignment index until the bit width of the Downlink assignment index in DCI format 1_2 for the two HARQ-ACK codebooks are the same.

– TPC command for scheduled PUCCH – 2 bits as defined in Clause 7.2.1 of [5, TS 38.213]

– Second TPC command for scheduled PUCCH – 2 bits as defined in Clause 7.2.1 of [5, TS 38.213] if higher layer parameter SecondTPCFieldDCI-1-2 is configured; 0 bit otherwise.

– PUCCH resource indicator – 0 or 1 or 2 or 3 bits determined by higher layer parameter numberOfBitsForPUCCH-ResourceIndicatorDCI-1-2

If higher layer parameter pucch-sSCellPattern or pucch-sSCellDynDCI-1-2 is configured, if the bit width of the PUCCH resource indicator in DCI format 1_2 associated with one cell for PUCCH transmission is not equal to that of the PUCCH resource indicator in DCI format 1_2 associated with the other cell for PUCCH transmission, a number of most significant bits with value set to ‘0’ are inserted to smaller PUCCH resource indicator until the bit width of the PUCCH resource indicator in DCI format 1_2 associated with the two cells for PUCCH transmissions are the same.

If the UE is configured with a PUCCH-SCell, pucch-sSCellPattern is replaced by pucch-sSCellPatternSecondaryPUCCHgroup for the secondary PUCCH group.

If higher layer parameter priorityIndicatorDCI-1-2 is configured, if the bit width of the PDSCH-to-HARQ_feedback timing indicator in DCI format 1_2 for one HARQ-ACK codebook is not equal to that of the PDSCH-to-HARQ_feedback timing indicator in DCI format 1_2 for the other HARQ-ACK codebook on the same cell for PUCCH transmission, a number of most significant bits with value set to ‘0’ are inserted to smaller PDSCH-to-HARQ_feedback timing indicator until the bit width of the PDSCH-to-HARQ_feedback timing indicator in DCI format 1_2 for the two HARQ-ACK codebooks are the same.

If higher layer parameter pucch-sSCellDynDCI-1-2 is configured, if the bit width of the PDSCH-to-HARQ_feedback timing indicator in DCI format 1_2 associated with one cell for PUCCH transmission is not equal to that of the PDSCH-to-HARQ_feedback timing indicator in DCI format 1_2 associated with the other cell for PUCCH transmision, a number of most significant bits with value set to ‘0’ are inserted to smaller PDSCH-to-HARQ_feedback timing indicator until the bit width of the PDSCH-to-HARQ_feedback timing indicator in DCI format 1_2 associated with the two cells are the same.

– One-shot HARQ-ACK request –0 or 1 bit.

– 1 bit if higher layer parameter pdsch-HARQ-ACK-OneShotFeedbackDCI-1-2 or pdsch-HARQ-ACK-EnhType3DCI-1-2 is configured;

– 0 bit otherwise.

– Enhanced Type 3 codebook indicator – 0, 1, 2, or 3 bits.

– 0 bit if pdsch-HARQ-ACK-EnhType3DCI-Field-1-2 is not configured;

– bits otherwise, where is the number of entries in the higher layer parameter pdsch-HARQ-ACK-EnhType3List.

If the UE is configured with a PUCCH-SCell, pdsch-HARQ-ACK-EnhType3List is replaced by pdsch-HARQ-ACK-EnhType3SecondaryList for the secondary PUCCH group.

– HARQ-ACK retransmission indicator – 0 or 1 bit.

– 1 bit if higher layer parameter pdsch-HARQ-ACK-retxDCI-1-2 is configured.

– 0 bit otherwise.

– Antenna port(s) – 0, 4, 5, or 6 bits

– 0 bit if higher layer parameter antennaPortsFieldPresenceDCI-1-2 is not configured;

– Otherwise 4, 5 or 6 bits as defined by Tables 7.3.1.2.2-1/2/3/4 and Tables 7.3.1.2.2-1A/2A/3A/4A, where the number of CDM groups without data of values 1, 2, and 3 refers to CDM groups {0}, {0,1}, and {0, 1,2} respectively. The antenna ports shall be determined according to the ordering of DMRS port(s) given by Tables 7.3.1.2.2-1/2/3/4 or Tables 7.3.1.2.2-1A/2A/3A/4A. When a UE receives an activation command that maps at least one codepoint of DCI field ‘Transmission Configuration Indication‘ to two TCI states, the UE shall use Table 7.3.1.2.2-1A/2A/3A/4A; otherwise, it shall use Tables 7.3.1.2.2-1/2/3/4.

– If a UE is configured with both dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2 and dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2 and is configured with higher layer parameter antennaPortsFieldPresenceDCI-1-2, the bitwidth of this field equals, where is the "Antenna ports" bitwidth derived according to dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2 and is the "Antenna ports" bitwidth derived according to dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2. A number of zeros are padded in the MSB of this field, if the mapping type of the PDSCH corresponds to the smaller value of and .

If a UE is not configured with higher layer parameter antennaPortsFieldPresenceDCI-1-2, antenna port(s) are defined assuming bit field index value 0 in Tables 7.3.1.2.2-1/2/3/4.

– Transmission configuration indication – 0 bit if higher layer parameter tci-PresentDCI-1-2 is not configured; otherwise 1 or 2 or 3 bits determined by higher layer parameter tci-PresentDCI-1-2 as defined in Clause 5.1.5 of [6, TS38.214].

If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part,

– if the higher layer parameter tci-PresentDCI-1-2 is not configured for the CORESET used for the PDCCH carrying the DCI format 1_2,

– the UE assumes tci-PresentDCI-1-2 is not configured for all CORESETs in the indicated bandwidth part;

– otherwise,

– the UE assumes tci-PresentDCI-1-2 is configured for all CORESETs in the indicated bandwidth part with the same value configured for the CORESET used for the PDCCH carrying the DCI format 1_2.

– SRS request – 0, 1, 2 or 3 bits

– 0 bit if the higher layer parameter srs-RequestDCI-1-2 is not configured;

– 1 bit as defined by Table 7.3.1.1.3-1 if the higher layer parameter srs-RequestDCI-1-2 = 1 and for UEs not configured with supplementaryUplink in ServingCellConfig in the cell;

– 2 bits if the higher layer parameter srs-RequestDCI-1-2 = 1 and for UEs configured with supplementaryUplink in ServingCellConfig in the cell, where the first bit is the non-SUL/SUL indicator as defined in Table 7.3.1.1.1-1 and the second bit is defined by Table 7.3.1.1.3-1;

– 2 bits as defined by Table 7.3.1.1.2-24 if the higher layer parameter srs-RequestDCI-1-2 = 2 and for UEs not configured with supplementaryUplink in ServingCellConfig in the cell;

– 3 bits if the higher layer parameter srs-RequestDCI-1-2 = 2 and for UEs configured with supplementaryUplink in ServingCellConfig in the cell, where the first bit is the non-SUL/SUL indicator as defined in Table 7.3.1.1.1-1 and the second and third bits are defined by Table 7.3.1.1.2-24;

– SRS offset indicator – 0, 1 or 2 bits.

– 0 bit if higher layer parameter AvailableSlotOffset is not configured or any aperiodic SRS resource set in the scheduled cell, or if higher layer parameter AvailableSlotOffset is configured for at least one aperodic SRS resource set in the scheduled cell and the maximum number of entries of AvailableSlotOffset configured for all aperiodic SRS resource set(s) is 1;

– DMRS sequence initialization – 0 or 1 bit

– 0 bit if the higher layer parameter dmrs-SequenceInitializationDCI-1-2 is not configured;

– 1 bit otherwise.

– Priority indicator – 0 bit if higher layer parameter priorityIndicatorDCI-1-2 is not configured; otherwise 1 bit as defined in Clause 9 in [5, TS 38.213].

– PDCCH monitoring adaptation indication – 0, 1 or 2 bits

– 1 or 2 bits, if searchSpaceGroupIdList-r17 is not configured and if pdcch-SkippingDurationList is configured

– 1 bit if the UE is configured with only one duration by pdcch-SkippingDurationList;

– 2 bits if the UE is configured with more than one duration by pdcch-SkippingDurationList.

– 1 or 2 bits, if pdcch-SkippingDurationList is not configured and if searchSpaceGroupIdList-r17 is configured

– 2 bits if the UE is configured by searchSpaceGroupIdList-r17 with search space set(s) with group index 0, search space set(s) with group index 1 and search space set(s) with group index 2;

– 2 bits, if pdcch-SkippingDurationList is configured and if searchSpaceGroupIdList-r17 is configured

– 0 bit, otherwise

– ChannelAccess-CPext – 0, 1, 2, 3 or 4 bits. The bitwidth for this field is determined as bits, where I is the number of entries in the higher layer parameter ul-AccessConfigListDCI-1-2 or in Table 7.3.1.1.1-4A if channelAccessMode-r16 = "semiStatic" is provided, for operation in a cell with shared spectrum channel access; otherwise 0 bit. One or more entries from Table 7.3.1.2.2-6 are configured by the higher layer parameter ul-AccessConfigListDCI-1-2.

– PUCCH Cell indicator – 0 or 1 bit.

– 1 bit if higher layer parameter pucch-sSCellDynDCI-1-2 is configured.

– 0 bit otherwise.

If DCI formats 1_2 are monitored in multiple search spaces associated with multiple CORESETs in a BWP for scheduling the same serving cell, zeros shall be appended until the payload size of the DCI formats 1_2 monitored in the multiple search spaces equal to the maximum payload size of the DCI format 1_2 monitored in the multiple search spaces.

For a UE configured with scheduling on the primary cell from an SCell, if prior to padding the number of information bits in DCI format 1_2 carried by PDCCH on the primary cell is not equal to the number of information bits in DCI format 1_2 carried by PDCCH on the SCell for scheduling on the primary cell, zeros shall be appended to the DCI format 1_2 with smaller size until the payload size is the same.

– If application of step 4B in clause 7.3.1.0 results in additional zero padding for DCI format 1_2 for scheduling on the primary cell, corresponding zeros shall be appended to both DCI format 1_2 monitored on the primary cell and DCI format 1_2 monitored on the SCell for scheduling on the primary cell.

– If the SCell is deactivated, the UE determines the number of information bits in DCI format 1_2 carried by PDCCH on the primary cell based on a DL BWP provided by firstActiveDownlinkBWP-Id for the SCell. If the active DL BWP of the SCell is a dormant DL BWP, the UE determines the number of information bits in DCI format 1_2 carried by PDCCH on the primary cell based on a DL BWP provided by firstWithinActiveTimeBWP-Id for the SCell.

Table 7.3.1.2.3-1: Redundancy version

Value of the Redundancy version field	Value of to be applied
0	0
1	3

7.3.1.3 DCI formats for other purposes

7.3.1.3.1 Format 2_0

DCI format 2_0 is used for notifying the slot format, COT duration, available RB set, and search space set group switching.

The following information is transmitted by means of the DCI format 2_0 with CRC scrambled by SFI-RNTI:

– If the higher layer parameter slotFormatCombToAddModList is configured,

– Slot format indicator 1, Slot format indicator 2, …, Slot format indicator N,

– If the higher layer parameter availableRB-SetsToAddModList is configured,

– Available RB set Indicator 1, Available RB set Indicator 2, …, Available RB set Indicator N1,

– If the higher layer parameter co-DurationsPerCellToAddModList is configured

– COT duration indicator 1, COT duration indicator 2, …, COT duration indicator N2.

– If the higher layer parameter switchTriggerToAddModList is configured

– Search space set group switching flag 1, Search space set group switching flag 2, …, Search space set group switching flag M.

The size of DCI format 2_0 is configurable by higher layers up to 128 bits, according to Clause 11.1.1 of [5, TS 38.213].

7.3.1.3.2 Format 2_1

DCI format 2_1 is used for notifying the PRB(s) and OFDM symbol(s) where UE may assume no transmission is intended for the UE.

The following information is transmitted by means of the DCI format 2_1 with CRC scrambled by INT-RNTI:

– Pre-emption indication 1, Pre-emption indication 2, …, Pre-emption indication N.

The size of DCI format 2_1 is configurable by higher layers up to 126 bits, according to Clause 11.2 of [5, TS 38.213]. Each pre-emption indication is 14 bits.

7.3.1.3.3 Format 2_2

DCI format 2_2 is used for the transmission of TPC commands for PUCCH and PUSCH.

The following information is transmitted by means of the DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI or TPC-PUCCH-RNTI:

– block number 1, block number 2,…, block number N

The parameter tpc-PUSCH or tpc-PUCCH provided by higher layers determines the index to the block number for an UL of a cell, with the following fields defined for each block:

– Closed loop indicator – 0 or 1 bit.

– For DCI format 2_2 with TPC-PUSCH-RNTI, 0 bit if the UE is not configured with high layer parameter twoPUSCH-PC-AdjustmentStates, in which case UE assumes each block in the DCI format 2_2 is of 2 bits; 1 bit otherwise, in which case UE assumes each block in the DCI format 2_2 is of 3 bits;

– For DCI format 2_2 with TPC-PUCCH-RNTI, 0 bit if the UE is not configured with high layer parameter twoPUCCH-PC-AdjustmentStates, in which case UE assumes each block in the DCI format 2_2 is of 2 bits; 1 bit otherwise, in which case UE assumes each block in the DCI format 2_2 is of 3 bits;

– TPC command –2 bits

The number of information bits in format 2_2 shall be equal to or less than the payload size of format 1_0 monitored in common search space in the same serving cell. If the number of information bits in format 2_2 is less than the payload size of format 1_0 monitored in common search space in the same serving cell, zeros shall be appended to format 2_2 until the payload size equals that of format 1_0 monitored in common search space in the same serving cell.

7.3.1.3.4 Format 2_3

DCI format 2_3 is used for the transmission of a group of TPC commands for SRS transmissions by one or more UEs. Along with a TPC command, a SRS request may also be transmitted.

The following information is transmitted by means of the DCI format 2_3 with CRC scrambled by TPC-SRS-RNTI:

– block number 1, block number 2, …, block number

where the starting position of a block is determined by the parameter startingBitOfFormat2-3 or startingBitOfFormat2-3SUL-v1530 provided by higher layers for the UE configured with the block.

If the UE is configured with higher layer parameter srs-TPC-PDCCH-Group = typeA for an UL without PUCCH and PUSCH or an UL on which the SRS power control is not tied with PUSCH power control, one block is configured for the UE by higher layers, with the following fields defined for the block:

– SRS request – 0 or 2 bits. The presence of this field is according to the definition in Clause 11.4 of [5, TS38.213]. If present, this field is interpreted as defined by Table 7.3.1.1.2-24.

– TPC command number 1, TPC command number 2, …, TPC command number N, where each TPC command applies to a respective UL carrier provided by higher layer parameter cc-IndexInOneCC-Set

If the UE is configured with higher layer parameter srs-TPC-PDCCH-Group = typeB for an UL without PUCCH and PUSCH or an UL on which the SRS power control is not tied with PUSCH power control, one block or more blocks is configured for the UE by higher layers where each block applies to an UL carrier, with the following fields defined for each block:

– SRS request – 0 or 2 bits. The presence of this field is according to the definition in Clause 11.4 of [5, TS38.213]. If present, this field is interpreted as defined by Table 7.3.1.1.2-24.

– TPC command –2 bits

The number of information bits in format 2_3 shall be equal to or less than the payload size of format 1_0 monitored in common search space in the same serving cell. If the number of information bits in format 2_3 is less than the payload size of format 1_0 monitored in common search space in the same serving cell, zeros shall be appended to format 2_3 until the payload size equals that of format 1_0 monitored in common search space in the same serving cell.

7.3.1.3.5 Format 2_4

DCI format 2_4 is used for notifying the PRB(s) and OFDM symbol(s) where UE cancels the corresponding UL transmission from the UE according to Clause 11.2A of [5, TS 38.213].

The following information is transmitted by means of the DCI format 2_4 with CRC scrambled by CI-RNTI:

– Cancellation indication 1, Cancellation indication 2, …, Cancellation indication indication N.

The size of DCI format 2_4 is configurable by higher layers parameter dci-PayloadSizeForCI up to 126 bits, according to Clause 11.2A of [5, TS 38.213]. The number of bits for each cancellation indication is configurable by higher layer parameter ci-PayloadSize. For a UE, there is at most one cancellation indication for an UL carrier.

7.3.1.3.6 Format 2_5

DCI format 2_5 is used for notifying the availability of soft resources as defined in Clause 9.3.1 of [10, TS 38.473]

The following information is transmitted by means of the DCI format 2_5 with CRC scrambled by AI-RNTI:

– Availability indicator 1, Availability indicator 2, …, Availability indicator N.

The size of DCI format 2_5 is configurable by higher layers up to 128 bits, according to Clause 14 of [5, TS 38.213].

7.3.1.3.7 Format 2_6

DCI format 2_6 is used for notifying the power saving information outside DRX Active Time for one or more UEs.

The following information is transmitted by means of the DCI format 2_6 with CRC scrambled by PS-RNTI:

– block number 1, block number 2,…, block number N

where the starting position of a block is determined by the parameter ps-PositionDCI-2-6 provided by higher layers for the UE configured with the block.

If the UE is configured with higher layer parameter ps-RNTI and dci-Format2-6, one block is configured for the UE by higher layers, with the following fields defined for the block:

– Wake-up indication – 1 bit

– SCell dormancy indication – 0 bit if higher layer parameter dormancyGroupOutsideActiveTime is not configured; otherwise 1, 2, 3, 4 or 5 bits bitmap determined according to the number of different DormancyGroupID(s) provided by higher layer parameter dormancyGroupOutsideActiveTime, where each bit corresponds to one of the SCell group(s) configured by higher layers parameter dormancyGroupOutsideActiveTime, with MSB to LSB of the bitmap corresponding to the first to last configured SCell group in ascending order of DormancyGroupID.

The size of DCI format 2_6 is indicated by the higher layer parameter sizeDCI-2-6, according to Clause 10.3 of [5, TS 38.213].

7.3.1.3.8 Format 2_7

DCI format 2_7 is used for notifying the paging early indication and TRS availability indication for one or more UEs.

The following information is transmitted by means of the DCI format 2_7 with CRC scrambled by PEI-RNTI:

– Paging indication field – bit(s), where

– is the number of paging occasions configured by higher layer parameter po-NumPerPEI as defined in Clause 10.4A in [5, TS 38.213];

– is the number of sub-groups of a paging occasion configured by higher layer parameter subgroupsNumPerPO.

– Each bit in the field indicates one UE subgroup of a paging occasion.

– TRS availability indication – 1, 2, 3, 4, 5, or 6 bits, where the number of bits is equal to one plus the highest value of all the indBitID(s) provided by the trs-ResourceSetConfig if configured; 0 bits otherwise.

The size of DCI format 2_7 is indicated by the higher layer parameter payloadSizeDCI-2_7, according to Clause 10.4A of [5, TS 38.213]. The number of information bits in format 2_7 shall be equal to or less than the payload size of format 2_7. If the number of information bits in format 2_7 is less than the size of format 2_7, the remaining bits are reserved.

7.3.1.4 DCI formats for scheduling of sidelink

7.3.1.4.1 Format 3_0

DCI format 3_0 is used for scheduling of NR PSCCH and NR PSSCH in one cell.

The following information is transmitted by means of the DCI format 3_0 with CRC scrambled by SL-RNTI or SL-CS-RNTI:

– Resource pool index – bits, where I is the number of resource pools for transmission configured by the higher layer parameter sl-TxPoolScheduling.

– Time gap – 3 bits determined by higher layer parameter sl-DCI-ToSL-Trans, as defined in clause 8.1.2.1 of [6, TS 38.214]

– HARQ process number – 4 bits.

– New data indicator – 1 bit.

– Lowest index of the subchannel allocation to the initial transmission – bits as defined in clause 8.1.2.2 of [6, TS 38.214]

– SCI format 1-A fields according to clause 8.3.1.1:

– Frequency resource assignment.

– Time resource assignment.

– PSFCH-to-HARQ feedback timing indicator – bits, where is the number of entries in the higher layer parameter sl-PSFCH-ToPUCCH, as defined in clause 16.5 of [5, TS 38.213]

– PUCCH resource indicator – 3 bits as defined in clause 16.5 of [5, TS 38.213].

– Configuration index – 0 bit if the UE is not configured to monitor DCI format 3_0 with CRC scrambled by SL-CS-RNTI; otherwise 3 bits as defined in clause 8.1.2 of [6, TS 38.214]. If the UE is configured to monitor DCI format 3_0 with CRC scrambled by SL-CS-RNTI, this field is reserved for DCI format 3_0 with CRC scrambled by SL-RNTI.

– Counter sidelink assignment index – 2 bits

– 2 bits as defined in clause 16.5.2 of [5, TS 38.213] if the UE is configured with pdsch-HARQ-ACK-Codebook = dynamic

– 2 bits as defined in clause 16.5.1 of [5, TS 38.213] if the UE is configured with pdsch-HARQ-ACK-Codebook = semi-static

– Padding bits, if required

If multiple transmit resource pools are provided in sl-TxPoolScheduling, zeros shall be appended to the DCI format 3_0 until the payload size is equal to the size of a DCI format 3_0 given by a configuration of the transmit resource pool resulting in the largest number of information bits for DCI format 3_0.

If the UE is configured to monitor DCI format 3_1 and the number of information bits in DCI format 3_0 is less than the payload of DCI format 3_1, zeros shall be appended to DCI format 3_0 until the payload size equals that of DCI format 3_1.

7.3.1.4.2 Format 3_1

DCI format 3_1 is used for scheduling of LTE PSCCH and LTE PSSCH in one cell.

The following information is transmitted by means of the DCI format 3_1 with CRC scrambled by SL Semi-Persistent Scheduling V-RNTI:

– Timing offset – 3 bits determined by higher layer parameter sl-TimeOffsetEUTRA-List, as defined in clause 16.6 of [5, TS 38.213]

– Carrier indicator –3 bits as defined in 5.3.3.1.9A of [11, TS 36.212].

– Lowest index of the subchannel allocation to the initial transmission – bits as defined in 5.3.3.1.9A of [11, TS 36.212].

– Frequency resource location of initial transmission and retransmission, as defined in 5.3.3.1.9A of [11, TS 36.212]

– Time gap between initial transmission and retransmission, as defined in 5.3.3.1.9A of [11, TS 36.212]

– SL index – 2 bits as defined in 5.3.3.1.9A of [11, TS 36.212]

– SL SPS configuration index – 3 bits as defined in clause 5.3.3.1.9A of [11, TS 36.212].

– Activation/release indication – 1 bit as defined in clause 5.3.3.1.9A of [11, TS 36.212].

If the UE is configured to monitor DCI format 3_0 and the number of information bits in DCI format 3_1 is less than the payload of DCI format 3_0, zeros shall be appended to DCI format 3_1 until the payload size equals that of DCI format 3_0.

7.3.1.5 DCI formats for scheduling of MBS

7.3.1.5.1 Format 4_0

DCI format 4_0 is used for the scheduling of PDSCH for broadcast in DL cell.

The following information is transmitted by means of the DCI format 4_0 with CRC scrambled by MCCH-RNTI or G-RNTI for MTCH configured by MBS-SessionInfo:

– Frequency domain resource assignment – bits where equals to

– the size of CORESET 0 if CORESET 0 is configured for the cell; and

– the size of initial DL bandwidth part if CORESTE 0 is not configured for the cell.

– Time domain resource assignment – 4 bits as defined in Clause 5.1.2.1 of [6, TS38.214]

– VRB-to-PRB mapping – 1 bit according to Table 7.3.1.2.2-5

– Modulation and coding scheme – 5 bits as defined in Clause 5.1.3 of [6, TS38.214]

– Redundancy version – 2 bits as defined in Table 7.3.1.1.1-2

– MCCH change notification – 2 bits as defined in Clause x.x.x of [8, TS38.321] if the CRC of the DCI format 4_0 is scrambled by MCCH-RNTI. Otherwise, this bit field is reserved.

– Padding bits, if required

Zeros shall be appended to DCI format 4_0 until the payload size equals that of DCI format 1_0 monitored in common search space in the same serving cell.

7.3.1.5.2 Format 4_1

DCI format 4_1 is used for the scheduling of PDSCH for multicast in DL cell.

The following information is transmitted by means of the DCI format 4_1 with CRC scrambled by G-RNTI configured by G-RNTI-Config or G-CS-RNTI:

– Frequency domain resource assignment – bits where equals to

– the size of CORESET 0 if CORESET 0 is configured for the cell; and

– the size of initial DL bandwidth part if CORESET 0 is not configured for the cell.

– Time domain resource assignment – 4 bits as defined in Clause 5.1.2.1 of [6, TS38.214]

– VRB-to-PRB mapping – 1 bit according to Table 7.3.1.2.2-5

– Modulation and coding scheme – 5 bits as defined in Clause 5.1.3 of [6, TS38.214]

– New data indicator – 1 bit

– Redundancy version – 2 bits as defined in Table 7.3.1.1.1-2

– HARQ process number – 4 bits

– Downlink assignment index – 2 bits as defined in Clause 9.1.3 of [5, TS 38.213], as counter DAI

– PUCCH resource indicator – 3 bits as defined in Clause 9.2.3 of [5, TS38.213]

– PDSCH-to-HARQ_feedback timing indicator – 3 bits as defined in Clause 9.2.3 of [5, TS38.213]

– Reserved bits – 3 bits

7.3.1.5.3 Format 4_2

DCI format 4_2 is used for the scheduling of PDSCH in DL cell.

The following information is transmitted by means of the DCI format 4_2 with CRC scrambled by G-RNTI configured by G-RNTI-Config or G-CS-RNTI:

– Frequency domain resource assignment – number of bits determined by the following, where is the size of the common frequency resource as configured by higher layer parameter locationAndBandwidth-Multicast:

– bits if only resource allocation type 0 is configured, where is defined in Clause 5.1.2.2.1 of [6, TS38.214],

– bits if only resource allocation type 1 is configured, or

– bits if resourceAllocation in PDSCH-Config-Multicast is configured as ‘dynamicSwitch’.

– If resourceAllocation in PDSCH-Config-Multicast is configured as ‘dynamicSwitch’, the MSB bit is used to indicate resource allocation type 0 or resource allocation type 1, where the bit value of 0 indicates resource allocation type 0 and the bit value of 1 indicates resource allocation type 1.

– For resource allocation type 0, the LSBs provide the resource allocation as defined in Clause 5.1.2.2.1 of [6, TS 38.214].

– For resource allocation type 1, the LSBs provide the resource allocation as defined in Clause 5.1.2.2.2 of [6, TS 38.214]

– VRB-to-PRB mapping – 0 or 1 bit:

– 0 bit if only resource allocation type 0 is configured or if vrb-ToPRB-Interleaver in PDSCH-Config-Multicast is not configured;

– 1 bit according to Table 7.3.1.2.2-5 otherwise, only applicable to resource allocation type 1, as defined in Clause 7.3.1.6 of [4, TS 38.211].

– PRB bundling size indicator – 0 bit if the higher layer parameter prb-BundlingType is not configured in PDSCH-Config-Multicast or is set to ‘staticBundling’, or 1 bit if the higher layer parameter prb-BundlingType in PDSCH-Config-Multicast is set to ‘dynamicBundling’ according to Clause 5.1.2.3 of [6, TS 38.214].

– Rate matching indicator – 0, 1, or 2 bits according to higher layer parameters rateMatchPatternGroup1 and rateMatchPatternGroup2 in PDSCH-Config-Multicast, where the MSB is used to indicate rateMatchPatternGroup1 and the LSB is used to indicate rateMatchPatternGroup2 when there are two groups.

For transport block 1:

– Modulation and coding scheme – 5 bits as defined in Clause 5.1.3.1 of [6, TS 38.214]

– New data indicator – 1 bit

– Redundancy version – 2 bits as defined in Table 7.3.1.1.1-2

For transport block 2 (only present if maxNrofCodeWordsScheduledByDCI equals 2):

– Modulation and coding scheme – 5 bits as defined in Clause 5.1.3.1 of [6, TS 38.214]

– New data indicator – 1 bit

– Redundancy version – 2 bits as defined in Table 7.3.1.1.1-2

– HARQ process number – 4 bits

– Downlink assignment index – number of bits as defined in the following

– 2 bits if the higher layer parameter pdsch-HARQ-ACK-Codebook-Multicast=dynamic, where the 2 bits are the counter DAI;

– 0 bits otherwise.

If higher layer parameter priorityIndicatorDCI-4-2 is configured in PDSCH-Config-Multicast, if the bit width of the Downlink assignment index in DCI format 4_2 for one HARQ-ACK codebook is not equal to that of the Downlink assignment index in DCI format 4_2 for the other HARQ-ACK codebook, a number of most significant bits with value set to ‘0’ are inserted to smaller Downlink assignment index until the bit width of the Downlink assignment index in DCI format 4_2 for the two HARQ-ACK codebooks are the same.

– PUCCH resource indicator – 3 bits as defined in Clause 9.2.3 of [5, TS 38.213]

– PDSCH-to-HARQ_feedback timing indicator – 0, 1, 2, or 3 bits as defined in Clause 9.2.3 of [5, TS 38.213]. The bitwidth for this field is determined as bits, where I is the number of entries in the higher layer parameter dl-DataToUL-ACK in PUCCH-Config-Multicast1 if configured or PUCCH-Config-Multicast2 if configured; otherwise, I is the number of entries in the higher layer parameter dl-DataToUL-ACK in PUCCH-Config.

If higher layer parameter priorityIndicatorDCI-4-2 is configured in PDSCH-Config-Multicast, if the bit width of the PDSCH-to-HARQ_feedback timing indicator in DCI format 4_2 for one HARQ-ACK codebook is not equal to that of the PDSCH-to-HARQ_feedback timing indicator in DCI format 4_2 for the other HARQ-ACK codebook, a number of most significant bits with value set to ‘0’ are inserted to smaller PDSCH-to-HARQ_feedback timing indicator until the bit width of the PDSCH-to-HARQ_feedback timing indicator in DCI format 4_2 for the two HARQ-ACK codebooks are the same.

– Antenna port(s) – 4, 5, or 6 bits as defined by Tables 7.3.1.2.2-1/2/3/4, where the number of CDM groups without data of values 1, 2, and 3 refers to CDM groups {0}, {0,1}, and {0, 1,2} respectively. The antenna ports shall be determined according to the ordering of DMRS port(s) given by Tables 7.3.1.2.2-1/2/3/4.

– Transmission configuration indication – 0 bit if higher layer parameter tci-PresentInDCI in PDCCH-Config-Multicast is not enabled; otherwise 3 bits as defined in Clause 5.1.5 of [6, TS38.214].

– DMRS sequence initialization – 1 bit.

– Priority indicator – 0 bit if higher layer parameter priorityIndicatorDCI-4-2 is not configured in PDSCH-Config-Multicast; otherwise 1 bit as defined in Clause 9 in [5, TS 38.213].

– Enabling/disabling HARQ-ACK feedback indication –1 bit if higher layer parameter harq-FeedbackEnabler-Multicast indicates dci-enabler, where value 1 indicates enabling HARQ-ACK feedback and value 0 indicates disabling HARQ-ACK feedback; 0 bit, otherwise.

The size of DCI format 4_2 is configurable by higher layer parameter sizeDCI-4-2 from 20 bits and up to 140 bits.