6.3.2 Uplink control information on PUSCH

38.2123GPPMultiplexing and channel codingNRRelease 17TS

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

The following clauses 6.3.2.2, 6.3.2.3, and 6.3.2.5 apply regardless of whether the higher layer parameter uci-MuxWithDiffPrio is configured or not. The following clauses 6.3.2.1, 6.3.2.4, and 6.3.2.6 apply by assuming uci-MuxWithDiffPrio is not configured, or uci-MuxWithDiffPrio is configured and the UCIs for transmission on a PUSCH are of the same priority index, unless stated otherwise.

If the UE is configured with a PUCCH-SCell, uci-MuxWithDiffPrio is replaced by uci-MuxWithDiffPrioSecondaryPUCCHgroup for the secondary PUCCH group in this clause.

6.3.2.1 UCI bit sequence generation

6.3.2.1.1 HARQ-ACK

If HARQ-ACK bits are transmitted on a PUSCH, the UCI bit sequence is determined as follows:

– If UCI is transmitted on PUSCH without UL-SCH and the UCI includes CSI part 1 without CSI part 2,

– if there is no HARQ-ACK bit given by Clause 9.1 of [5, TS 38.213], set , , and ;

– if there is only one HARQ-ACK bit given by Clause 9.1 of [5, TS 38.213], set , , and ;

– otherwise, set for and , where the HARQ-ACK bit sequence is given by Clause 9.1 of [5, TS 38.213].

6.3.2.1.2 CSI

If cqi-BitsPerSubband is configured, this Clause 6.3.2.1.2 applies by taking Subband CQI as Subband differential CQI and replacing the corresponding number of bits 2 by 4.

The bitwidth for PMI of codebookType=typeI-SinglePanel and codebookType=typeI-MultiPanel is specified in Clause 6.3.1.1.2.

The bitwidth for RI/LI/CQI/CRI of codebookType=typeI-SinglePanel and codebookType=typeI-MultiPanel is specified in Clause 6.3.1.1.2.

The bitwidth for PMI of codebookType=typeII is provided in Tables 6.3.2.1.2-1, where the values of , , , , , , and are given by Clause 5.2.2.2.3 in [6, TS 38.214].

Table 6.3.2.1.2-1: PMI of codebookType= typeII

	Information fields for wideband PMI			Information fields for wideband PMI or per subband PMI

Rank=1 SBAmp off		N/A	N/A		N/A	N/A	N/A
Rank=2 SBAmp off						N/A	N/A
Rank=1 SBAmp on		N/A	N/A		N/A		N/A
Rank=2 SBAmp on

The bitwidth for PMI of codebookType=typeII-r16 is provided in Tables 6.3.2.1.2-1A, where the values of , , , , , and are given by Clause 5.2.2.2.5 in [6, TS 38.214].

Table 6.3.2.1.2-1A: PMI of codebookType= typeII-r16

Information fields

Rank=1

N/A

Rank=2

N/A

Rank=3

N/A

Rank=4

Rank=1

N/A

Rank=2

N/A

Rank=3

N/A

Rank=4

Information fields

Rank=1

N/A

Rank=2

N/A

Rank=3

N/A

Rank=4

N/A

Rank=1

N/A

Rank=2

N/A

Rank=3

N/A

Rank=4

Note: the bitwidth for , and shown in Table 6.3.2.1.2-1A is the total bitwidth of , and up to Rank = , respectively, and the corresponding per layer bitwidths are , , and 4, (i.e., 1, 3, and 4 bits for each respective indicator elements , , and , respectively), where as defined in Clause 5.2.2.2.5 in [6, TS 38.214] is the number of nonzero coefficients for layer such that .

The bitwidth for PMI of codebookType= typeII-PortSelection is provided in Tables 6.3.2.1.2-2, where the values of , , , , , , and are given by Clause 5.2.2.2.4 in [6, TS 38.214].

Table 6.3.2.1.2-2: PMI of codebookType= typeII-PortSelection

	Information fields for wideband PMI			Information fields for wideband PMI or per subband PMI

Rank=1 SBAmp off		N/A	N/A		N/A	N/A	N/A
Rank=2 SBAmp off						N/A	N/A
Rank=1 SBAmp on		N/A	N/A		N/A		N/A
Rank=2 SBAmp on

The bitwidth for PMI of codebookType=typeII-PortSelection-r16 is provided in Tables 6.3.2.1.2-2A, where the values of ,, , , , and are given by Clause 5.2.2.2.6 in [6, TS 38.214].

Table 6.3.2.1.2-2A: PMI of codebookType= typeII-PortSelection-r16

Information fields

Rank=1

N/A

Rank=2

N/A

Rank=3

N/A

Rank=4

Rank=1

N/A

Rank=2

N/A

Rank=3

N/A

Rank=4

Information fields

Rank=1

N/A

Rank=2

N/A

Rank=3

N/A

Rank=4

N/A

Rank=1

N/A

Rank=2

N/A

Rank=3

N/A

Rank=4

Note: the bitwidth for , and shown in Table 6.3.2.1.2-2A is the total bitwidth of , and up to Rank = , respectively, and the corresponding per layer bitwidths are , , and 4, (i.e., 1, 3, and 4 bits for each respective indicator elements , , and , respectively), where as defined in Clause 5.2.2.2.5 in [6, TS 38.214] is the number of nonzero coefficients for layer such that .

The bitwidth for PMI of codebookType=typeII-PortSelection-r17 is provided in Tables 6.3.2.1.2-2B, where the values of ,, , , and are given by Clause 5.2.2.2.7 in [6, TS 38.214].

Table 6.3.2.1.2-2B: PMI of codebookType= typeII-PortSelection-r17

Information fields

Rank=1

if N > M=2, N/A otherwise

N/A

Rank=2

if N > M=2, N/A otherwise

N/A

Rank=3

if N > M=2, N/A otherwise

N/A

Rank=4

if N > M=2, N/A otherwise

Information fields

Rank=1

N/A

N/A if ;

otherwise

Rank=2

N/A

N/A if ;

otherwise

Rank=3

N/A

Rank=4

Note: the bitwidth for , and shown in Table 6.3.2.1.2-2B is the total bitwidth of , and up to Rank = , respectively, and the corresponding per layer bitwidths are , , and 4, (i.e., 1, 3, and 4 bits for each respective indicator elements , , and , respectively), where as defined in Clause 5.2.2.2.7 in [6, TS 38.214] is the number of nonzero coefficients for layer such that .

For CSI on PUSCH, two UCI bit sequences are generated, and . The CSI fields of all CSI reports, in the order from upper part to lower part in Table 6.3.2.1.2-6, are mapped to the UCI bit sequence starting with . The CSI fields of all CSI reports, in the order from upper part to lower part in Table 6.3.2.1.2-7, are mapped to the UCI bit sequence starting with .

The mapping order of CSI fields of one report for CRI/RSRP or SSBRI/RSRP or CRI/RSRP/CapabilityIndex or SSBRI/RSRP/CapabilityIndex reporting is provided in Table 6.3.1.1.2-8. The mapping order of CSI fields of one report for inter-cell SSBRI/RSRP reporting is provided in Table 6.3.1.1.2-8. The mapping order of CSI fields of one report for CRI/SINR or SSBRI/SINR or CRI/SINR/CapabilityIndex or SSBRI/SINR/CapabilityIndex reporting is provided in Table 6.3.1.1.2-8A. The mapping order of CSI fields of one report for group-based CRI/RSRP or SSBRI/RSRP reporting is provided in Table 6.3.1.1.2-8B. The procedure in clause 6.3.2 described for CSI part 1 is also applicable for one report for CRI/RSRP, SSBRI/RSRP, CRI/SINR, or SSBRI/SINR reporting.

Table 6.3.2.1.2-3: Mapping order of CSI fields of one CSI report, CSI part 1

CSI report number	CSI fields
CSI report #n CSI part 1	CRI as in Tables 6.3.1.1.2-3/4/6, if reported
	Rank Indicator as in Tables 6.3.1.1.2-3/4/5 or 6.3.2.1.2-8/9, if reported
	Wideband CQI for the first TB as in Tables 6.3.1.1.2-3/4/5 or 6.3.2.1.2-8/9, if reported
	Subband differential CQI for the first TB with increasing order of subband number as in Tables 6.3.1.1.2-3/4/5 or 6.3.2.1.2-8/9, if reported
	Indicator of the number of non-zero wideband amplitude coefficients for layer 0 as in Table 6.3.1.1.2-5, if reported
	Indicator of the number of non-zero wideband amplitude coefficients for layer 1 as in Table 6.3.1.1.2-5 (if the rank according to the reported RI is equal to one, this field is set to all zeros), if 2-layer PMI reporting is allowed according to the rank restriction in Clauses 5.2.2.2.3 and 5.2.2.2.4 [6, TS 38.214] and if reported
	Indicator of the total number of non-zero coefficients summed across all layers as in Table 6.3.2.1.2-8/9, if reported
Note: Subbands for given CSI report n indicated by the higher layer parameter csi-ReportingBand are numbered continuously in the increasing order with the lowest subband of csi-ReportingBand as subband 0.

Table 6.3.2.1.2-3A: Mapping order of CSI fields of one CSI report, CSI part 1, csi-ReportMode= Mode 1

CSI report number	CSI fields
CSI report #n CSI part 1	CRI as in Tables 6.3.1.1.2-3A, if associated with one CSI-RS resource pair and if reported
	Rank Combination Indicator as in Tables 6.3.1.1.2-3A, if reported
	Wideband CQI for the first TB as in Tables 6.3.1.1.2-3A, if reported
	Subband differential CQI for the first TB with increasing order of subband number as in Tables 6.3.1.1.2-3A, if reported
	CRI as in Tables 6.3.1.1.2-3B, if associated with one CSI-RS resource, numberOfSingleTRP-CSI-Mode1 = 1 and if reported; First CRI as in Tables 6.3.1.1.2-3B, if associated with one CSI-RS resource, numberOfSingleTRP-CSI-Mode1 = 2 and if reported
	Rank Indicator associated with CRI as in Tables 6.3.1.1.2-3B, if numberOfSingleTRP-CSI-Mode1 = 1 and if reported; Rank Indicator associated with the first CRI as in Tables 6.3.1.1.2-3B, if numberOfSingleTRP-CSI-Mode1 = 2 and if reported
	Wideband CQI associated with CRI for the first TB as in Tables 6.3.1.1.2-3B, if numberOfSingleTRP-CSI-Mode1 = 1 and if reported; Wideband CQI associated with the first CRI for the first TB as in Tables 6.3.1.1.2-3B, if numberOfSingleTRP-CSI-Mode1 = 2 and if reported
	Subband differential CQI associated with CRI for the first TB with increasing order of subband number as in Tables 6.3.1.1.2-3B, if numberOfSingleTRP-CSI-Mode1 = 1 if reported; Subband differential CQI associated with the first CRI for the first TB with increasing order of subband number as in Tables 6.3.1.1.2-3B, if numberOfSingleTRP-CSI-Mode1 = 2 and if reported
	Second CRI as in Tables 6.3.1.1.2-3B, if associated with one CSI-RS resource, numberOfSingleTRP-CSI-Mode1 = 2 and if reported
	Rank Indicator associated with the second CRI as in Tables 6.3.1.1.2-3B, if numberOfSingleTRP-CSI-Mode1 = 2 and if reported
	Wideband CQI associated with the second CRI for the first TB as in Tables 6.3.1.1.2-3B, if numberOfSingleTRP-CSI-Mode1 = 2 and if reported
	Subband differential CQI associated with the second CRI for the first TB with increasing order of subband number as in Tables 6.3.1.1.2-3B, if numberOfSingleTRP-CSI-Mode1 = 2 and if reported
Note: Subbands for given CSI report n indicated by the higher layer parameter csi-ReportingBand are numbered continuously in the increasing order with the lowest subband of csi-ReportingBand as subband 0.

Table 6.3.2.1.2-3B: Mapping order of CSI fields of one CSI report, CSI part 1, csi-ReportMode= Mode 2

CSI report number

CSI fields

CSI report #n

CSI part 1

CRI as in Tables 6.3.1.1.2-3A, if associated with one CSI-RS resource pair and if reported;

CRI as in Tables 6.3.1.1.2-3B, if associated with one CSI-RS resource and if reported

Rank Combination Indicator as in Tables 6.3.1.1.2-3A, if associated with one CSI-RS resource pair and if reported;

Rank Indicator as in Tables 6.3.1.1.2-3B, if associated with one CSI-RS resource and if reported;

Zero padding bits , if needed

Wideband CQI for the first TB as in Tables 6.3.1.1.2-3A, if associated with one CSI-RS resource pair and if reported;

Wideband CQI for the first TB as in Tables 6.3.1.1.2-3B, if associated with one CSI-RS resource and if reported

Subband differential CQI for the first TB with increasing order of subband number as in Tables 6.3.1.1.2-3A, if associated with one CSI-RS resource pair and if reported;

Subband differential CQI for the first TB with increasing order of subband number as in Tables 6.3.1.1.2-3B, if associated with one CSI-RS resource and if reported

Note: Subbands for given CSI report n indicated by the higher layer parameter csi-ReportingBand are numbered continuously in the increasing order with the lowest subband of csi-ReportingBand as subband 0.

The number of zero padding bits in Table 6.3.1.1.2-9B is 0 for 1 CSI-RS port and for more than 1 CSI-RS port, where

– . is the set of rank and rank combination values r that are allowed to be reported. is obtained according to Tables 6.3.1.1.2-3A/3B for rank combination indicator and rank indicator respectively.

– is obtained according to Tables 6.3.1.1.2-3A for rank combination indicator and R is the reported rank combination

– is obtained according to Tables 6.3.1.1.2-3B for rank indicator and R is the reported rank

Table 6.3.2.1.2-4: Mapping order of CSI fields of one CSI report, CSI part 2 wideband

CSI report number	CSI fields
CSI report #n CSI part 2 wideband	Wideband CQI for the second TB as in Tables 6.3.1.1.2-3/4/5, if present and reported
	Layer Indicator as in Tables 6.3.1.1.2-3/4/5, if reported
	PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1/2 or 6.3.2.1.2-1/2, if reported
	PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1/2 or 6.3.2.1.2-1/2, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214], if pmi-FormatIndicator= widebandPMI and if reported

Table 6.3.2.1.2-4A: Mapping order of CSI fields of one CSI report, CSI part 2 wideband, csi-ReportMode= Mode 1

CSI report number	CSI fields
CSI report #n CSI part 2 wideband	Two Layer Indicators as in Table 6.3.1.1.2-3A, where the first Layer Indicator and the second Layer Indicator are associated with the first resource and the second resource within the resource pair respectively and if reported;
	PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1 associated with the first resource within the CSI-RS resource pair, if reported
	PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214] associated with the first CSI-RS resource within the CSI-RS resource pair, if pmi-FormatIndicator= widebandPMI and if reported
	PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1 associated with the second resource within the CSI-RS resource pair, if reported
	PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214] associated with the second CSI-RS resource within the CSI-RS resource pair, if pmi-FormatIndicator= widebandPMI and if reported
	Wideband CQI for the second TB as in Tables 6.3.1.1.2-3B, if associated with CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 1 and if reported; Wideband CQI for the second TB as in Tables 6.3.1.1.2-3B, if associated with the first CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 2 and if reported
	Layer Indicator as in Table 6.3.1.1.2-3B, if associated with CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 1 and if reported; Layer Indicator as in Table 6.3.1.1.2-3B, if associated with the first CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 2 and if reported
	PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, if associated with CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 1 and if reported; PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, if associated with the first CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 2 and if reported
	PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214], if associated with CRI in CSI part 1, pmi-FormatIndicator= widebandPMI, numberOfSingleTRP-CSI-Mode1 = 1 and if reported; PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214], if associated with the first CRI in CSI part 1, pmi-FormatIndicator= widebandPMI, numberOfSingleTRP-CSI-Mode1 = 2 and if reported
	Wideband CQI for the second TB as in Tables 6.3.1.1.2-3B, if associated with the second CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 2 and if reported
	Layer Indicator as in Table 6.3.1.1.2-3B, if associated with the second CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 2 and if reported
	PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, if associated with the second CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 2 and if reported
	PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214], if associated with the second CRI in CSI part 1, pmi-FormatIndicator= widebandPMI, numberOfSingleTRP-CSI-Mode1 = 2 and if reported

Table 6.3.2.1.2-4B: Mapping order of CSI fields of one CSI report, CSI part 2 wideband, csi-ReportMode= Mode 2

CSI report number	CSI fields
CSI report #n CSI part 2 wideband	Wideband CQI for the second TB as in Tables 6.3.1.1.2-3B, if reported part 1 is associated with one CSI-RS resource and if reported
	Two Layer Indicators as in Table 6.3.1.1.2-3A, if reported part 1 is associated with one CSI-RS resource pair, where the first Layer Indicator and the second Layer Indicator are associated with the first resource and the second resource within the resource pair respectively and if reported; Layer Indicator as in Table 6.3.1.1.2-3B, if reported part 1 is associated with one CSI-RS resource and if reported
	PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1 associated with the first resource within the CSI-RS resource pair, if reported part 1 is associated with one CSI-RS resource pair and if reported
	PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214] associated with the first CSI-RS resource within the CSI-RS resource pair, if pmi-FormatIndicator= widebandPMI and reported part 1 is associated with one CSI-RS resource pair and if reported
	PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1 associated with the second CSI-RS resource within the CSI-RS resource pair, if reported part 1 is associated with one CSI-RS resource pair and if reported
	PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214] associated with the second CSI-RS resource within the CSI-RS resource pair, if pmi-FormatIndicator= widebandPMI and reported part 1 is associated with one CSI-RS resource pair and if reported
	PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, if reported part 1 is associated with one CSI-RS resource and if reported
	PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214], if pmi-FormatIndicator= widebandPMI and reported part 1 is associated with one CSI-RS resource and if reported

Table 6.3.2.1.2-5: Mapping order of CSI fields of one CSI report, CSI part 2 subband

CSI report #n Part 2 subband	Subband differential CQI for the second TB of all even subbands with increasing order of subband number, as in Tables 6.3.1.1.2-3/4/5, if cqi-FormatIndicator=subbandCQI and if reported
	PMI subband information fields of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1/2 or 6.3.2.1.2-1/2, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and if reported
	Subband differential CQI for the second TB of all odd subbands with increasing order of subband number, as in Tables 6.3.1.1.2-3/4/5, if cqi-FormatIndicator=subbandCQI and if reported
	PMI subband information fields of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1/2 or 6.3.2.1.2-1/2, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and if reported

Table 6.3.2.1.2-5A: Mapping order of CSI fields of one CSI report, CSI part 2 of codebookType=typeII-r16 or typeII-PortSelection-r16

CSI report number	CSI fields
CSI report #n CSI part 2, group 0	PMI fields , from left to right as in Tables 6.3.2.1.2-1A/2A, if reported
CSI report #n CSI part 2, group 1	The following PMI fields , from left to right, as in Tables 6.3.2.1.2-1A/2A:, , and highest priority bits of highest priority bits of and highest priority bits of, in decreasing order of priority based on the corresponding function defined in clause 5.2.3 of TS38.214, if reported
CSI report #n CSI part 2, group 2	The following PMI fields , from left to right, as in Tables 6.3.2.1.2-1A/2A lowest priority bits of lowest priority bits of and lowest priority bits of , in decreasing order of priority based on the corresponding function defined in clause 5.2.3 of TS38.214, if reported

Table 6.3.2.1.2-5B: Mapping order of CSI fields of one CSI report, CSI part 2 of codebookType=typeII-PortSelection-r17

CSI report number	CSI fields
CSI report #n CSI part 2, group 0	PMI fields , from left to right as in Tables 6.3.2.1.2-2B, if reported
CSI report #n CSI part 2, group 1	The following PMI fields , from left to right, as in Tables 6.3.2.1.2-2B: highest priority bits of highest priority bits of and highest priority bits of, in decreasing order of priority based on the corresponding function defined in clause 5.2.3 of TS38.214, if reported
CSI report #n CSI part 2, group 2	The following PMI fields , from left to right, as in Tables 6.3.2.1.2-2B lowest priority bits of lowest priority bits of and lowest priority bits of , in decreasing order of priority based on the corresponding function defined in clause 5.2.3 of TS38.214, if reported

Table 6.3.2.1.2-5C: Mapping order of CSI fields of one CSI report, CSI part 2 subband, ReportMode= Mode 1

CSI report #n Part 2 subband	PMI subband information fields of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the first resource within the CSI-RS resource pair, according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and if reported
	PMI subband information fields of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the second resource within the CSI-RS resource pair, according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and if reported
	Subband differential CQI for the second TB of all even subbands with increasing order of subband number associated with CRI in CSI part 1, as in Tables 6.3.1.1.2-3B, if cqi-FormatIndicator=subbandCQI, numberOfSingleTRP-CSI-Mode1 = 1 and if reported; Subband differential CQI for the second TB of all even subbands with increasing order of subband number associated with the first CRI in CSI part 1, as in Tables 6.3.1.1.2-3B, if cqi-FormatIndicator=subbandCQI, numberOfSingleTRP-CSI-Mode1 = 2 and if reported
	PMI subband information fields of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with CRI in CSI part 1 according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI, numberOfSingleTRP-CSI-Mode1 = 1 and if reported; PMI subband information fields of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the first CRI in CSI part 1 according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI, numberOfSingleTRP-CSI-Mode1 = 2 and if reported
	Subband differential CQI for the second TB of all even subbands with increasing order of subband number associated with the second CRI in CSI part 1, as in Tables 6.3.1.1.2-3B, if cqi-FormatIndicator=subbandCQI, numberOfSingleTRP-CSI-Mode1 = 2 and if reported
	PMI subband information fields of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the second CRI in CSI part 1 according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI, numberOfSingleTRP-CSI-Mode1 = 2 and if reported
	PMI subband information fields of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the first resource within the CSI-RS resource pair, according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and if reported
	PMI subband information fields of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the second resource within the CSI-RS resource pair, according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and if reported
	Subband differential CQI for the second TB of all odd subbands with increasing order of subband number associated with CRI in CSI part 1, as in Tables 6.3.1.1.2-3B, if cqi-FormatIndicator=subbandCQI, numberOfSingleTRP-CSI-Mode1 = 1 and if reported; Subband differential CQI for the second TB of all odd subbands with increasing order of subband number associated with the first CRI in CSI part 1, as in Tables 6.3.1.1.2-3B, if cqi-FormatIndicator=subbandCQI, numberOfSingleTRP-CSI-Mode1 = 2 and if reported
	PMI subband information fields of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with CRI in CSI part 1 according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI, numberOfSingleTRP-CSI-Mode1 = 1 and if reported; PMI subband information fields of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the first CRI in CSI part 1 according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI, numberOfSingleTRP-CSI-Mode1 = 2 and if reported
	Subband differential CQI for the second TB of all odd subbands with increasing order of subband number associated with the second CRI in CSI part 1, as in Tables 6.3.1.1.2-3B, if cqi-FormatIndicator=subbandCQI, numberOfSingleTRP-CSI-Mode1 = 2 and if reported
	PMI subband information fields of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the second CRI in CSI part 1 according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI, numberOfSingleTRP-CSI-Mode1 = 2 and if reported

Table 6.3.2.1.2-5D: Mapping order of CSI fields of one CSI report, CSI part 2 subband, ReportMode= Mode 2

CSI report #n Part 2 subband	PMI subband information fields of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the first resource within the CSI-RS resource pair, according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and reported part 1 is associated with one CSI-RS resource pair and if reported
	PMI subband information fields of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the second resource within the CSI-RS resource pair, according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and reported part 1 is associated with one CSI-RS resource pair and if reported
	PMI subband information fields of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the first resource within the CSI-RS resource pair, according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and reported part 1 is associated with one CSI-RS resource pair and if reported
	PMI subband information fields of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the second resource within the CSI-RS resource pair, according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and reported part 1 is associated with one CSI-RS resource pair and if reported
	Subband differential CQI for the second TB of all even subbands with increasing order of subband number associated with one CSI-RS resource, as in Tables 6.3.1.1.2-3B, if cqi-FormatIndicator=subbandCQI and reported part 1 is associated with one CSI-RS resource and if reported
	PMI subband information fields of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with one CSI-RS resource according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and reported part 1 is associated with one CSI-RS resource and if reported
	Subband differential CQI for the second TB of all odd subbands with increasing order of subband number associated with one CSI-RS resource, as in Tables 6.3.1.1.2-3B, if cqi-FormatIndicator=subbandCQI and reported part 1 is associated with one CSI-RS resource and if reported
	PMI subband information fields of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1/2, or codebook index for 2 antenna ports associated with one CSI-RS resource according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and reported part 1 is associated with one CSI-RS resource and if reported

Table 6.3.2.1.2-6: Mapping order of CSI reports to UCI bit sequence ,
with two-part CSI report(s)

UCI bit sequence	CSI report number
	CSI part 1 of CSI report #1 as in Table 6.3.2.1.2-3/3A/3B or Table 6.3.1.1.2-8/8A/8B
	CSI part 1 of CSI report #2 as in Table 6.3.2.1.2-3/3A/3B or Table 6.3.1.1.2-8/8A/8B
	…
	CSI part 1 of CSI report #n as in Table 6.3.2.1.2-3/3A/3B or Table 6.3.1.1.2-8/8A/8B

where CSI report #1, CSI report #2, …, CSI report #n in Table 6.3.2.1.2-6 correspond to the CSI reports in increasing order of CSI report priority values according to Clause 5.2.5 of [6, TS38.214].

Table 6.3.2.1.2-7: Mapping order of CSI reports to UCI bit sequence ,
with two-part CSI report(s)

UCI bit sequence

CSI report number

CSI report #1, CSI part 2 wideband, as in Table 6.3.2.1.2-4/4A/4B,

or CSI part 2 with group 0, as in Table 6.3.2.1.2-5A/5B,
if CSI part 2 exists for CSI report #1

CSI report #2, CSI part 2 wideband, as in Table 6.3.2.1.2-4/4A/4B,

or CSI part 2 with group 0, as in Table 6.3.2.1.2-5A/5B,
if CSI part 2 exists for CSI report #2

…

CSI report #n, CSI part 2 wideband, as in Table 6.3.2.1.2-4/4A/4B,

or CSI part 2 with group 0, as in Table 6.3.2.1.2-5A/5B,
if CSI part 2 exists for CSI report #n

CSI report #1, CSI part 2 subband, as in Table 6.3.2.1.2-5/5C/5D,

or CSI part 2 with group 1 and 2, as in Table 6.3.2.1.2-5A/5B,
if CSI part 2 exists for CSI report #1

CSI report #2, CSI part 2 subband, as in Table 6.3.2.1.2-5/5C/5D,

or CSI part 2 with group 1 and 2, as in Table 6.3.2.1.2-5A/5B,

if CSI part 2 exists for CSI report #2

…

CSI report #n, CSI part 2 subband, as in Table 6.3.2.1.2-5/5C/5D,

or CSI part 2 with group 1 and 2, as in Table 6.3.2.1.2-5A/5B,

if CSI part 2 exists for CSI report #n

where CSI report #1, CSI report #2, …, CSI report #n in Table 6.3.2.1.2-7 correspond to the CSI reports in increasing order of CSI report priority values according to Clause 5.2.5 of [6, TS38.214].

The bitwidth for RI/CQI of codebookType= typeII-r16 or codebookType=typeII-PortSelection-r16 is provided in Table 6.3.2.1.2-8.

Table 6.3.2.1.2-8: RI and CQI of codebookType=typeII-r16 or typeII-PortSelection-r16

Field	Bitwidth
Rank Indicator
Wide-band CQI	4
Subband differential CQI	2
Indicator of the total number of non-zero coefficients summed across all layers	if max allowed rank is 1; otherwise

where is the number of allowed rank indicator values according to Clauses 5.2.2.2.5 and 5.2.2.2.6 [6, TS 38.214],, where , , , and are given by Clause 5.2.2.2.5 and 5.2.2.2.6 in [6, TS 38.214]. The values of the rank indicator field are mapped to allowed rank indicator values with increasing order, where ‘0’ is mapped to the smallest allowed rank indicator value. The values of the indicator field are mapped to the allowed values of , according to Clauses 5.2.2.2.5 and 5.2.2.2.6 [6, TS 38.214], with increasing order, where ‘0’ is mapped to .

The bitwidth for RI/CQI of codebookType=typeII-PortSelection-r17 is provided in Table 6.3.2.1.2-9.

Table 6.3.2.1.2-9: RI and CQI of codebookType=typeII-PortSelection-r17

Field	Bitwidth
Rank Indicator
Wide-band CQI	4
Subband differential CQI	2
Indicator of the total number of non-zero coefficients summed across all layers	if max allowed rank is 1; otherwise

where is the number of allowed rank indicator values according to Clauses 5.2.2.2.7 [6, TS 38.214],, where , , and are given by Clause 5.2.2.2.7 in [6, TS 38.214]. The values of the rank indicator field are mapped to allowed rank indicator values with increasing order, where ‘0’ is mapped to the smallest allowed rank indicator value. The values of the indicator field are mapped to the allowed values of , according to Clauses 5.2.2.2.7 [6, TS 38.214], with increasing order, where ‘0’ is mapped to .

6.3.2.1.3 CG-UCI

For CG-UCI bits transmitted on a CG PUSCH when the higher layer parameter cg-RetransmissionTimer is configured, the CG-UCI bit sequence is determined as follows:

– set for and , where the CG-UCI bit sequence is given by Table 6.3.2.1.3-1, mapped in the order from upper part to lower part.

Table 6.3.2.1.3-1: Mapping order of CG-UCI fields

Field	Bitwidth
HARQ process number	4
Redundancy version	2
New data indicator	1
Channel Occupancy Time (COT) sharing information	if both higher layer parameter ul-toDL-COT-SharingED-Threshold and higher layer parameter cg-COT-SharingList are configured, or if both higher layer parameter ue-SemiStaticChannelAccessConfig and higher layer parameter cg-COT-SharingList are configured, or if higher layer parameter cg-COT-SharingList is configured in frequency range 2-2, where C is the number of combinations configured in cg-COT-SharingList; 1 if higher layer parameter ul-toDL-COT-SharingED-Threshold is not configured, and if higher layer parameter ue-SemiStaticChannelAccessConfig is not configured, and if higher layer parameter cg-COT-SharingOffset is configured; 0 otherwise; If a UE indicates COT sharing other than "no sharing" in a CG PUSCH within the UE’s initiated COT, the UE should provide consistent COT sharing information in all the subsequent CG PUSCHs, if any, occurring within the same UE’s initiated COT such that the same DL starting point and duration are maintained.

6.3.2.1.4 HARQ-ACK and CG-UCI

When higher layer parameter cg-UCI-Multiplexing is configured, the UCI bit sequence is determined as follows, where .

– The CG-UCI bits are mapped to the UCI bit sequence, where for . The CG-UCI bit sequence is given by Table 6.3.2.1.3-1 mapped in the order from upper part to lower part, and is number of CG-UCI bits;

– The HARQ-ACK bits are mapped to the UCI bit sequence , where for . The HARQ-ACK bit sequence is given by Clause 9.1 of [5, TS38.213], and is number of HARQ-ACK bits.

6.3.2.1.5 UCI with different priority indexes

If uci-MuxWithDiffPrio is configured, and HARQ-ACK bits associated with priority index 0, and CSI part 1 if any are transmitted on a PUSCH associated with priority index 1, the following UCI bit sequences are generated, , and if any, according to the following:

– If CSI part 1 is also transmitted on the PUSCH,

– Set for as the bit sequence of CSI part 1, where the CSI fields of all CSI reports, in the order from upper part to lower part in Table 6.3.2.1.2-6, are mapped to the UCI bit sequence starting with .

– Set for and , where the HARQ-ACK bit sequence associated with priority index 0 is given by Clause 9.1 of [5, TS 38.213].

– Otherwise, set for and , where the HARQ-ACK bit sequence associated with priority index 0 is given by Clause 9.1 of [5, TS 38.213].

If uci-MuxWithDiffPrio is configured, and HARQ-ACK bits associated with priority index 1, and CSI if any are transmitted on a PUSCH associated with priority index 0, the following UCI bit sequences are generated,, if any, and if any, according to the following:

– If HARQ-ACK bits associated with priority index 1 and CSI are transmitted on the PUSCH without UL-SCH and the CSI includes CSI part 1 without CSI part 2, and there is only one HARQ-ACK bit associated with priority index 1 given by Clause 9.1 of [5, TS 38.213], set , , and ; otherwise, set for and , where the HARQ-ACK bit sequence associated with priority index 1 is given by Clause 9.1 of [5, TS 38.213];

– Set for as the bit sequence of CSI part 1, if CSI part 1 is also transmitted on the PUSCH, where the CSI fields of all CSI reports, in the order from upper part to lower part in Table 6.3.2.1.2-6, are mapped to the UCI bit sequence starting with ;

– Set for as the bit sequence of CSI part 2, if CSI part 2 is also transmitted on the PUSCH, where the CSI fields of all CSI reports, in the order from upper part to lower part in Table 6.3.2.1.2-7, are mapped to the UCI bit sequence starting with .

If uci-MuxWithDiffPrio is configured, and HARQ-ACK bits associated with priority index 0, HARQ-ACK bits associated with priority index 1 and/or CG-UCI associated with priority index 1, and CSI part 1 if any are transmitted on a PUSCH, the following UCI bit sequences are generated,, , and if any, according to the following:

– Set for and if HARQ-ACK bits associated with priority index 1 are transmitted without CG-UCI associated with priority index 1, where the HARQ-ACK bit sequence associated with priority index 1 is given by Clause 9.1 of [5, TS 38.213];

– Set for and if CG-UCI associated with priority index 1 is transmitted without HARQ-ACK bits associated with priority index 1, where the CG-UCI bit sequence associated with priority index 1 is given by Table 6.3.2.1.3-1, mapped in the order from upper part to lower part;

– Set as follows, if both CG-UCI associated with priority index 1 and HARQ-ACK bits associated with priority index 1 are transmitted, where

– The CG-UCI bits are mapped to the UCI bit sequence , where for . The CG-UCI bit sequence is given by Table 6.3.2.1.3-1 mapped in the order from upper part to lower part, and is number of CG-UCI bits

– The HARQ-ACK bits are mapped to the UCI bit sequence , where for . The HARQ-ACK bit sequence associated with priority index 1 is given by Clause 9.1 of [5, TS 38.213].

– If CSI part 1 is also transmitted on the PUSCH and the PUSCH is associated with priority index 1,

– Set for and , where the HARQ-ACK bit sequence associated with priority index 0 is given by Clause 9.1 of [5, TS 38.213].

– Otherwise,

– Set for and , where the HARQ-ACK bit sequence associated with priority index 0 is given by Clause 9.1 of [5, TS 38.213].

– Set for and , if CSI part 1 is also transmitted on the PUSCH and the PUSCH is associated with priority index 0, where the CSI part 1 sequence is given by Table 6.3.2.1.2-6 by replacing , and the CSI fields of all CSI reports, in the order from upper part to lower part in Table 6.3.2.1.2-6, are mapped to the CSI part 1 sequence starting with .

– Set for and , where the HARQ-ACK bit sequence associated with priority index 1 is given by Clause 9.1 of [5, TS 38.213];

– Set for and if CG-UCI associated with priority index 0 is transmitted without HARQ-ACK bits associated with priority index 0, where the CG-UCI bit sequence associated with priority index 0 is given by Table 6.3.2.1.3-1, mapped in the order from upper part to lower part;

– Set as follows if both CG-UCI associated with priority index 0 and HARQ-ACK bits associated with priority index 0 are transmitted, where

– The CG-UCI bits are mapped to the UCI bit sequence , where for . The CG-UCI bit sequence is given by Table 6.3.2.1.3-1 mapped in the order from upper part to lower part, and is number of CG-UCI bits

– The HARQ-ACK bits are mapped to the UCI bit sequence , where for . The HARQ-ACK bit sequence associated with priority index 0 is given by Clause 9.1 of [5, TS 38.213].

6.3.2.2 Code block segmentation and CRC attachment

Denote the bits of the payload by , where is the payload size. The procedure in 6.3.2.2.1 applies for and the procedure in Clause 6.3.2.2.2 applies for .

6.3.2.2.1 UCI encoded by Polar code

Code block segmentation and CRC attachment is performed according to Clause 6.3.1.2.1.

6.3.2.2.2 UCI encoded by channel coding of small block lengths

The procedure in Clause 6.3.1.2.2 applies.

6.3.2.3 Channel coding of UCI

6.3.2.3.1 UCI encoded by Polar code

Channel coding is performed according to Clause 6.3.1.3.1, except that the rate matching output sequence length is given in Clause 6.3.2.4.1.

6.3.2.3.2 UCI encoded by channel coding of small block lengths

Information bits are delivered to the channel coding block. They are denoted by , where is the number of bits.

The information bits are encoded according to Clause 5.3.3.

After encoding the bits are denoted by , where is the number of coded bits.

6.3.2.4 Rate matching

6.3.2.4.1 UCI encoded by Polar code

6.3.2.4.1.1 HARQ-ACK

For HARQ-ACK transmission on PUSCH not using repetition type B with UL-SCH and if numberOfSlotsTBoMS is not present in the resource allocation table, or if numberOfSlotsTBoMS is present in the resource allocation table and the value of numberOfSlotsTBoMS in the row indicated by the Time domain resource assignment field in DCI is equal to 1, the number of coded modulation symbols per layer for HARQ-ACK transmission, denoted as , is determined as follows:

where

– is the number of HARQ-ACK bits;

– if , ; otherwise is the number of CRC bits for HARQ-ACK determined according to Clause 6.3.1.2.1;

– ;

– is the number of code blocks for UL-SCH of the PUSCH transmission;

– if the DCI format scheduling the PUSCH transmission includes a CBGTI field indicating that the UE shall not transmit the -th code block, =0; otherwise, is the -th code block size for UL-SCH of the PUSCH transmission;

– is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers;

– is the number of subcarriers in OFDM symbol that carries PTRS, in the PUSCH transmission;

– is the number of resource elements that can be used for transmission of UCI in OFDM symbol , for , in the PUSCH transmission and is the total number of OFDM symbols of the PUSCH, including all OFDM symbols used for DMRS;

– for any OFDM symbol that carries DMRS of the PUSCH, ;

– for any OFDM symbol that does not carry DMRS of the PUSCH, ;

– is configured by higher layer parameter scaling;

– is the symbol index of the first OFDM symbol that does not carry DMRS of the PUSCH, after the first DMRS symbol(s), in the PUSCH transmission.

For HARQ-ACK transmission on PUSCH not using repetition type B with UL-SCH, and if numberOfSlotsTBoMS is present in the resource allocation table and the value of numberOfSlotsTBoMS in the row indicated by the Time domain resource assignment field in DCI is larger than 1, the number of coded modulation symbols per layer for HARQ-ACK transmission, denoted as , is determined as follows:

where

– is the value of numberOfSlotsTBoMS in the row indicated by the Time domain resource assignment field in DCI;

– is the number of subcarriers in OFDM symbol that carries PTRS, in the PUSCH transmission of TB processing over multiple slots in the slot with the HARQ-ACK transmission;

– is the number of resource elements that can be used for transmission of UCI in OFDM symbol , for , in the PUSCH transmission of TB processing over multiple slots in the slot with the HARQ-ACK transmission and is the total number of OFDM symbols of the PUSCH in the slot, including all OFDM symbols used for DMRS;

– is the symbol index of the first OFDM symbol that does not carry DMRS of the PUSCH, after the first DMRS symbol(s), in the PUSCH transmission of TB processing over multiple slots in the slot with the HARQ-ACK transmission;

– and all the other notations in the formula are defined the same as for PUSCH not using repetition type B and if numberOfSlotsTBoMS is not present in the resource allocation table.

For HARQ-ACK transmission on an actual repetition of a PUSCH with repetition Type B with UL-SCH, the number of coded modulation symbols per layer for HARQ-ACK transmission, denoted as , is determined as follows:

where

– is the number of resource elements that can be used for transmission of UCI in OFDM symbol , for , in the PUSCH transmission assuming a nominal repetition without segmentation, and is the total number of OFDM symbols in a nominal repetition of the PUSCH, including all OFDM symbols used for DMRS;

– for any OFDM symbol that carries DMRS of the PUSCH assuming a nominal repetition without segmentation, ;

– for any OFDM symbol that does not carry DMRS of the PUSCH assuming a nominal repetition without segmentation, where is the number of subcarriers in OFDM symbol that carries PTRS, in the PUSCH transmission assuming a nominal repetition without segmentation;

– is the number of resource elements that can be used for transmission of UCI in OFDM symbol , for , in the actual repetition of the PUSCH transmission, and is the total number of OFDM symbols in the actual repetition of the PUSCH transmission, including all OFDM symbols used for DMRS;

– for any OFDM symbol that carries DMRS of the actual repetition of the PUSCH transmission, ;

– for any OFDM symbol that does not carry DMRS of the actual repetition of the PUSCH transmission, where is the number of subcarriers in OFDM symbol that carries PTRS, in the actual repetition of the PUSCH transmission;

– and all the other notations in the formula are defined the same as for PUSCH not using repetition type B and if numberOfSlotsTBoMS is not present in the resource allocation table.

For HARQ-ACK transmission on PUSCH without UL-SCH, the number of coded modulation symbols per layer for HARQ-ACK transmission, denoted as , is determined as follows:

where

– is the number of HARQ-ACK bits;

– if , ; otherwise is the number of CRC bits for HARQ-ACK defined according to Clause 6.3.1.2.1;;

– ;

– is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers;

– is the number of subcarriers in OFDM symbol that carries PTRS, in the PUSCH transmission;

– for any OFDM symbol that carries DMRS of the PUSCH, ;

– for any OFDM symbol that does not carry DMRS of the PUSCH, ;

– is the symbol index of the first OFDM symbol that does not carry DMRS of the PUSCH, after the first DMRS symbol(s), in the PUSCH transmission;

– is the code rate of the PUSCH, determined according to Clause 6.1.4.1 of [6, TS38.214];

– is the modulation order of the PUSCH;

– is configured by higher layer parameter scaling.

The input bit sequence to rate matching is where is the code block number, and is the number of coded bits in code block number .

Rate matching is performed according to Clause 5.4.1 by setting and the rate matching output sequence length to , where

– is the number of code blocks for UCI determined according to Clause 5.2.1;

– is the number of transmission layers of the PUSCH;

– is the modulation order of the PUSCH;

– .

The output bit sequence after rate matching is denoted as where is the length of rate matching output sequence in code block number .

6.3.2.4.1.2 CSI part 1

For CSI part 1 transmission on PUSCH not using repetition type B with UL-SCH and if numberOfSlotsTBoMS is not present in the resource allocation table, or if numberOfSlotsTBoMS is present in the resource allocation table and the value of numberOfSlotsTBoMS in the row indicated by the Time domain resource assignment field in DCI is equal to 1, the number of coded modulation symbols per layer for CSI part 1 transmission, denoted as , is determined as follows:

where

– is the number of bits for CSI part 1;

– if , ; otherwise is the number of CRC bits for CSI part 1 determined according to Clause 6.3.1.2.1;

– ;

– is the number of code blocks for UL-SCH of the PUSCH transmission;

– is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers;

– is the number of subcarriers in OFDM symbol that carries PTRS, in the PUSCH transmission;

– if HARQ-ACK is present for transmission on the same PUSCH with UL-SCH and without CG-UCI, where is the number of coded modulation symbols per layer for HARQ-ACK transmitted on the PUSCH as defined in clause 6.3.2.4.1.1 if number of HARQ-ACK information bits is more than 2, and if the number of HARQ-ACK information bits is no more than 2 bits, where is the number of reserved resource elements for potential HARQ-ACK transmission in OFDM symbol , for , in the PUSCH transmission, defined in Clause 6.2.7; or

– if both HARQ-ACK and CG-UCI are present on the same PUSCH with UL-SCH, where is the number of coded modulation symbols per layer for HARQ-ACK and CG-UCI transmitted on the PUSCH as defined in clause 6.3.2.4.1.5; or

– if CG-UCI is present on the same PUSCH with UL-SCH and without HARQ-ACK, where is the number of coded modulation symbols per layer for CG-UCI transmitted on the PUSCH as defined in clause 6.3.2.4.1.4;

– for any OFDM symbol that carries DMRS of the PUSCH, ;

– for any OFDM symbol that does not carry DMRS of the PUSCH, ;

– is configured by higher layer parameter scaling.

For CSI part 1 transmission on PUSCH not using repetition type B with UL-SCH, and if numberOfSlotsTBoMS is present in the resource allocation table and the value of numberOfSlotsTBoMS in the row indicated by the Time domain resource assignment field in DCI is larger than 1, the number of coded modulation symbols per layer for CSI part 1 transmission, denoted as , is determined as follows:

where

– is the value of numberOfSlotsTBoMS in the row indicated by the Time domain resource assignment field in DCI;

– is the number of subcarriers in OFDM symbol that carries PTRS, in the PUSCH transmission of TB processing over multiple slots in the slot with the CSI part 1 transmission;

– is the number of resource elements that can be used for transmission of UCI in OFDM symbol , for , in the PUSCH transmission of TB processing over multiple slots in the slot with the CSI part 1 transmission and is the total number of OFDM symbols of the PUSCH in the slot, including all OFDM symbols used for DMRS;

– and all the other notations in the formula are defined the same as for PUSCH not using repetition type B and if numberOfSlotsTBoMS is not present in the resource allocation table.

For CSI part 1 transmission on an actual repetition of a PUSCH with repetition Type B with UL-SCH, the number of coded modulation symbols per layer for CSI part 1 transmission, denoted as , is determined as follows:

where

– for any OFDM symbol that carries DMRS of the PUSCH assuming a nominal repetition without segmentation, ;

– for any OFDM symbol that carries DMRS of the actual repetition of the PUSCH transmission, ;

– and all the other notations in the formula are defined the same as for PUSCH not using repetition type B and if numberOfSlotsTBoMS is not present in the resource allocation table.

For CSI part 1 transmission on PUSCH without UL-SCH, the number of coded modulation symbols per layer for CSI part 1 transmission, denoted as , is determined as follows:

if there is CSI part 2 to be transmitted on the PUSCH,

else

end if

where

– is the number of bits for CSI part 1;

– if , ; otherwise is the number of CRC bits for CSI part 1 determined according to Clause 6.3.1.2.1;

– ;

– is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers;

– is the number of subcarriers in OFDM symbol that carries PTRS, in the PUSCH transmission;

– is the number of coded modulation symbols per layer for HARQ-ACK transmitted on the PUSCH if number of HARQ-ACK information bits is more than 2, and if the number of HARQ-ACK information bits is no more than 2 bits, where is the number of reserved resource elements for potential HARQ-ACK transmission in OFDM symbol , for , in the PUSCH transmission, defined in Clause 6.2.7;

– for any OFDM symbol that carries DMRS of the PUSCH, ;

– for any OFDM symbol that does not carry DMRS of the PUSCH, ;

– is the code rate of the PUSCH, determined according to Clause 6.1.4.1 of [6, TS38.214];

– is the modulation order of the PUSCH.

The input bit sequence to rate matching is where is the code block number, and is the number of coded bits in code block number .

Rate matching is performed according to Clause 5.4.1 by setting and the rate matching output sequence length to , where

– is the number of code blocks for UCI determined according to Clause 5.2.1;

– is the number of transmission layers of the PUSCH;

– is the modulation order of the PUSCH;

– .

The output bit sequence after rate matching is denoted as where is the length of rate matching output sequence in code block number .

6.3.2.4.1.3 CSI part 2

For CSI part 2 transmission on PUSCH not using repetition type B with UL-SCH and if numberOfSlotsTBoMS is not present in the resource allocation table, or if numberOfSlotsTBoMS is present in the resource allocation table and the value of numberOfSlotsTBoMS in the row indicated by the Time domain resource assignment field in DCI is equal to 1, the number of coded modulation symbols per layer for CSI part 2 transmission, denoted as , is determined as follows:

where

– is the number of bits for CSI part 2;

– if , ; otherwise is the number of CRC bits for CSI part 2 determined according to Clause 6.3.1.2.1;

– ;

– is the number of code blocks for UL-SCH of the PUSCH transmission;

– is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers;

– is the number of subcarriers in OFDM symbol that carries PTRS, in the PUSCH transmission;

– is the number of coded modulation symbols per layer for CSI part 1 transmitted on the PUSCH;

– for any OFDM symbol that carries DMRS of the PUSCH, ;

– for any OFDM symbol that does not carry DMRS of the PUSCH, .

– is configured by higher layer parameter scaling.

For CSI part 2 transmission on PUSCH not using repetition type B with UL-SCH, and if numberOfSlotsTBoMS is present in the resource allocation table and the value of numberOfSlotsTBoMS in the row indicated by the Time domain resource assignment field in DCI is larger than 1, the number of coded modulation symbols per layer for CSI part 2 transmission, denoted as , is determined as follows:

where

– is the value of numberOfSlotsTBoMS in the row indicated by the Time domain resource assignment field in DCI;

– is the number of subcarriers in OFDM symbol that carries PTRS, in the PUSCH transmission of TB processing over multiple slots in the slot with the CSI part 2 transmission;

– is the number of resource elements that can be used for transmission of UCI in OFDM symbol , for , in the PUSCH transmission of TB processing over multiple slots in the slot with the CSI part 2 transmission and is the total number of OFDM symbols of the PUSCH in the slot, including all OFDM symbols used for DMRS;

– and all the other notations in the formula are defined the same as for PUSCH not using repetition type B and if numberOfSlotsTBoMS is not present in the resource allocation table.

For CSI part 2 transmission on an actual repetition of a PUSCH with repetition Type B with UL-SCH, the number of coded modulation symbols per layer for CSI part 2 transmission, denoted as , is determined as follows:

where

– for any OFDM symbol that carries DMRS of the PUSCH assuming a nominal repetition without segmentation, ;

– for any OFDM symbol that carries DMRS of the actual repetition of the PUSCH transmission, ;

– and all the other notations in the formula are defined the same as for PUSCH not using repetition type B and if numberOfSlotsTBoMS is not present in the resource allocation table.

For CSI part 2 transmission on PUSCH without UL-SCH, the number of coded modulation symbols per layer for CSI part 2 transmission, denoted as , is determined as follows:

where

– is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers;

– is the number of subcarriers in OFDM symbol that carries PTRS, in the PUSCH transmission;

– is the number of coded modulation symbols per layer for CSI part 1 transmitted on the PUSCH;

– for any OFDM symbol that carries DMRS of the PUSCH, ;

– for any OFDM symbol that does not carry DMRS of the PUSCH, .

The input bit sequence to rate matching is where is the code block number, and is the number of coded bits in code block number .

Rate matching is performed according to Clause 5.4.1 by setting and the rate matching output sequence length to , where

– is the number of code blocks for UCI determined according to Clause 5.2.1;

– is the number of transmission layers of the PUSCH;

– is the modulation order of the PUSCH;

– .

The output bit sequence after rate matching is denoted as where is the length of rate matching output sequence in code block number .

6.3.2.4.1.4 CG-UCI

For CG-UCI transmission on PUSCH with UL-SCH and if numberOfSlotsTBoMS is not present in the resource allocation table, or if numberOfSlotsTBoMS is present in the resource allocation table and the value of numberOfSlotsTBoMS in the row indicated by the Time domain resource assignment field in DCI is equal to 1, the number of coded modulation symbols per layer for CG-UCI transmission, denoted as , is determined as follows:

where

– is the number of CG-UCI bits;

– is the number of CRC bits for CG-UCI determined according to Clause 6.3.1.2.1;

– ;

– is the number of code blocks for UL-SCH of the PUSCH transmission;

– is the r-th code block size for UL-SCH of the PUSCH transmission;

– is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers;

– is the number of subcarriers in OFDM symbol l that carries PTRS, in the PUSCH transmission;

– is the number of resource elements that can be used for transmission of UCI in OFDM symbol l, for =0,1,2,…, , in the PUSCH transmission and is the total number of OFDM symbols of the PUSCH, including all OFDM symbols used for DMRS;

– for any OFDM symbol that carries DMRS of the PUSCH, ;

– for any OFDM symbol that does not carry DMRS of the PUSCH, ;

– is configured by higher layer parameter scaling;

– is the symbol index of the first OFDM symbol that does not carry DMRS of the PUSCH, after the first DMRS symbol(s), in the PUSCH transmission.

For CG-UCI transmission on PUSCH with UL-SCH, and if numberOfSlotsTBoMS is present in the resource allocation table and the value of numberOfSlotsTBoMS in the row indicated by the Time domain resource assignment field in DCI is larger than 1, the number of coded modulation symbols per layer for CG-UCI transmission, denoted as , is determined as follows:

where

– is the value of numberOfSlotsTBoMS in the row indicated by the Time domain resource assignment field in DCI;

– is the number of subcarriers in OFDM symbol that carries PTRS, in the PUSCH transmission of TB processing over multiple slots in the slot with the CG-UCI transmission;

– is the number of resource elements that can be used for transmission of UCI in OFDM symbol , for , in the PUSCH transmission of TB processing over multiple slots in the slot with the CG-UCI transmission and is the total number of OFDM symbols of the PUSCH in the slot, including all OFDM symbols used for DMRS;

– and all the other notations in the formula are defined the same as for PUSCH with UL-SCH and if numberOfSlotsTBoMS is not present in the resource allocation table.

The input bit sequence to rate matching is where r is the code block number, and is the number of coded bits in code block number r.

Rate matching is performed according to Clause 5.4.1 by setting and the rate matching output sequence length to , where

– is the number of code blocks for UCI determined according to Clause 5.2.1;

– is the number of transmission layers of the PUSCH;

– is the modulation order of the PUSCH;

– .

The output bit sequence after rate matching is denoted as where is the length of rate matching output sequence in code block number r.

6.3.2.4.1.5 HARQ-ACK and CG-UCI

For HARQ-ACK and CG-UCI transmission on PUSCH with UL-SCH and if numberOfSlotsTBoMS is not present in the resource allocation table, or if numberOfSlotsTBoMS is present in the resource allocation table and the value of numberOfSlotsTBoMS in the row indicated by the Time domain resource assignment field in DCI is equal to 1, the number of coded modulation symbols per layer for HARQ-ACK and CG-UCI transmission, denoted as , is determined as follows:

where

– is the number of HARQ-ACK bits;

– is the number of CG-UCI bits;

– if , ; otherwise is the number of CRC bits for HARQ-ACK and CG-UCI determined according to Clause 6.3.1.2.1;

– ;

– is the number of code blocks for UL-SCH of the PUSCH transmission;

– is the r-th code block size for UL-SCH of the PUSCH transmission;

– is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers;

– is the number of subcarriers in OFDM symbol l that carries PTRS, in the PUSCH transmission;

– for any OFDM symbol that carries DMRS of the PUSCH, ;

– for any OFDM symbol that does not carry DMRS of the PUSCH, ;

– is configured by higher layer parameter scaling;

– is the symbol index of the first OFDM symbol that does not carry DMRS of the PUSCH, after the first DMRS symbol(s), in the PUSCH transmission.

For HARQ-ACK and CG-UCI transmission on PUSCH with UL-SCH, and if numberOfSlotsTBoMS is present in the resource allocation table and the value of numberOfSlotsTBoMS in the row indicated by the Time domain resource assignment field in DCI is larger than 1, the number of coded modulation symbols per layer for HARQ-ACK and CG-UCI transmission, denoted as , is determined as follows:

where

– is the value of numberOfSlotsTBoMS in the row indicated by the Time domain resource assignment field in DCI;

– is the number of subcarriers in OFDM symbol that carries PTRS, in the PUSCH transmission of TB processing over multiple slots in the slot with the HARQ-ACK and CG-UCI transmission;

– is the number of resource elements that can be used for transmission of UCI in OFDM symbol , for , in the PUSCH transmission of TB processing over multiple slots in the slot with the HARQ-ACK and CG-UCI transmission and is the total number of OFDM symbols of the PUSCH in the slot, including all OFDM symbols used for DMRS;

– and all the other notations in the formula are defined the same as for PUSCH with UL-SCH and if numberOfSlotsTBoMS is not present in the resource allocation table.

The input bit sequence to rate matching is where r is the code block number, and is the number of coded bits in code block number r.

Rate matching is performed according to Clause 5.4.1 by setting and the rate matching output sequence length to , where

– is the number of code blocks for UCI determined according to Clause 5.2.1;

– is the number of transmission layers of the PUSCH;

– is the modulation order of the PUSCH;

– .

The output bit sequence after rate matching is denoted as where is the length of rate matching output sequence in code block number r.

6.3.2.4.1.6 UCI with different priority indexes

In this clause, is equal to defined in [5, TS38.213] in case of PUSCH associated with priority index 1, and equal to defined in [5, TS38.213] in case of PUSCH associated with priority index 0. is equal to defined in [5, TS38.213] in case of PUSCH associated with priority index 0, and equal to defined in [5, TS38.213] in case of PUSCH associated with priority index 1.

If uci-MuxWithDiffPrio is configured, and HARQ-ACK bits associated with priority index 0, and CSI part 1 if any are transmitted on a PUSCH associated with priority index 1:

– If CSI part 1 is also transmitted on the PUSCH,

– Perform rate matching for CSI part 1 according to clause 6.3.2.4.1.2, by assuming the number of HARQ-ACK information bits to be transmitted on PUSCH in clause 6.3.2.4.1.2 is 0 bit.

– Perform rate matching for HARQ-ACK with priority index 0 according to clause 6.3.2.4.1.3, by taking HARQ-ACK with priority index 0 as CSI part 2 and replacing by , and assuming the number of HARQ-ACK information bits to be transmitted on PUSCH in clause 6.3.2.4.1.3 is 0 bit.

– Otherwise, perform rate matching for HARQ-ACK with priority index 0 according to clause 6.3.2.4.1.2, by taking HARQ-ACK with priority index 0 as CSI-part 1 and replacing by , and assuming the number of HARQ-ACK information bits to be transmitted on PUSCH in clause 6.3.2.4.1.2 is 0 bit.

If uci-MuxWithDiffPrio is configured, and HARQ-ACK bits associated with priority index 1, and CSI if any are transmitted on a PUSCH associated with priority index 0:

– Perform rate matching for HARQ-ACK with priority index 1 according to clause 6.3.2.4.1.1, by taking HARQ-ACK with priority index 1 as HARQ-ACK and replacing by .

– Perform rate matching for CSI part 1 according to clause 6.3.2.4.1.2, by taking HARQ-ACK with priority index 1 as HARQ-ACK, if CSI part 1 is also transmitted on the PUSCH.

– Perform rate matching for CSI part 2 according to clause 6.3.2.4.1.3, by taking HARQ-ACK with priority index 1 as HARQ-ACK, if CSI part 2 is also transmitted on the PUSCH.

– Perform rate matching for HARQ-ACK with priority index 1 according to clause 6.3.2.4.1.1, by taking HARQ-ACK with priority index 1 as HARQ-ACK and replacing by , if HARQ-ACK bits associated with priority index 1 are transmitted without CG-UCI associated with priority index 1.

– Perform rate matching for CG-UCI with priority index 1 according to clause 6.3.2.4.1.4, if CG-UCI associated with priority index 1 is transmitted without HARQ-ACK bits associated with priority index 1.

– Perform rate matching for CG-UCI with priority index 1 and HARQ-ACK with priority index 1 according to clause 6.3.2.4.1.5, if both CG-UCI associated with priority index 1 and HARQ-ACK bits associated with priority index 1 are transmitted, by taking HARQ-ACK with priority index 1 as HARQ-ACK and replacing by .

– If CSI part 1 is also transmitted on the PUSCH and the PUSCH is associated with priority index 1,

– Perform rate matching for CSI part 1 according to clause 6.3.2.4.1.2, by taking HARQ-ACK with priority index 1 as HARQ-ACK.

– Perform rate matching for HARQ-ACK with priority index 0 according to clause 6.3.2.4.1.3, by taking HARQ-ACK with priority index 0 as CSI part 2 and replacing by , and taking HARQ-ACK with priority index 1 as HARQ-ACK.

– Otherwise,

– Perform rate matching for HARQ-ACK with priority index 0 according to clause 6.3.2.4.1.2, by taking HARQ-ACK with priority index 0 as CSI-part 1 and replacing by and taking HARQ-ACK with priority index 1 if any as HARQ-ACK, and taking CG-UCI associated with priority index 1 if any as CG-UCI.

– Perform rate matching for CSI part 1 according to clause 6.3.2.4.1.3, by taking CSI part 1 as CSI part 2 and replacing by , taking HARQ-ACK with priority index 0 as CSI-part 1, taking CG-UCI associated with priority index 1 if any as CG-UCI and taking HARQ-ACK with priority index 1 if any as HARQ-ACK, if CSI part 1 is also transmitted on the PUSCH and the PUSCH is associated with priority index 0.

– Perform rate matching for HARQ-ACK with priority index 1 according to clause 6.3.2.4.1.1, by taking HARQ-ACK with priority index 1 as HARQ-ACK and replacing by .

– Perform rate matching for CG-UCI associated with priority index 0 according to clause 6.3.2.4.1.2, if CG-UCI associated with priority index 0 is transmitted without HARQ-ACK bits associated with priority index 0, by taking CG-UCI associated with priority index 0 as CSI-part 1 and replacing by and taking HARQ-ACK with priority index 1 as HARQ-ACK.

– Perform rate matching for CG-UCI associated with priority index 0 and HARQ-ACK bits associated with priority index 0 according to clause 6.3.2.4.1.2, if both CG-UCI associated with priority index 0 and HARQ-ACK bits associated with priority index 0 are transmitted, by taking CG-UCI associated with priority index 0 and HARQ-ACK bits associated with priority index 0 as CSI-part 1 and replacing by and taking HARQ-ACK with priority index 1 as HARQ-ACK.

– Perform rate matching for CSI part 1 according to clause 6.3.2.4.1.3, by taking CSI part 1 as CSI part 2 and replacing by , taking CG-UCI associated with priority index 0 and HARQ-ACK bits associated with priority index 0 if any as CSI-part 1 and taking HARQ-ACK with priority index 1 as HARQ-ACK, if CSI part 1 is also transmitted on the PUSCH and the PUSCH is associated with priority index 0.

6.3.2.4.2 UCI encoded by channel coding of small block lengths

6.3.2.4.2.1 HARQ-ACK

For HARQ-ACK transmission on PUSCH, the number of coded modulation symbols per layer for HARQ-ACK transmission, denoted as , is determined according to Clause 6.3.2.4.1.1, by setting the number of CRC bits .

The input bit sequence to rate matching is .

Rate matching is performed according to Clause 5.4.3, by setting the rate matching output sequence length , where

– is the number of transmission layers of the PUSCH;

– is the modulation order of the PUSCH.

The output bit sequence after rate matching is denoted as .

6.3.2.4.2.2 CSI part 1

For CSI part 1 transmission on PUSCH, the number of coded modulation symbols per layer for CSI part 1 transmission, denoted as , is determined according to Clause 6.3.2.4.1.2, by setting the number of CRC bits .

Rate matching is performed according to Clause 5.4.3, by setting the rate matching output sequence length , where

– is the number of transmission layers of the PUSCH;

– is the modulation order of the PUSCH.

The output bit sequence after rate matching is denoted as .

6.3.2.4.2.3 CSI part 2

For CSI part 2 transmission on PUSCH, the number of coded modulation symbols per layer for CSI part 2 transmission, denoted as , is determined according to Clause 6.3.2.4.1.3, by setting the number of CRC bits .

Rate matching is performed according to Clause 5.4.3, by setting the rate matching output sequence length , where

– is the number of transmission layers of the PUSCH;

– is the modulation order of the PUSCH.

The output bit sequence after rate matching is denoted as .

6.3.2.4.2.4 CG-UCI

For CG-UCI transmission on PUSCH, the number of coded modulation symbols per layer for CG-UCI transmission, denoted as , is determined according to Clause 6.3.2.4.1.4, by setting the number of CRC bits .

The input bit sequence to rate matching is .

Rate matching is performed according to Clause 5.4.3, by setting the rate matching output sequence length

, where

– is the number of transmission layers of the PUSCH;

– is the modulation order of the PUSCH.

The output bit sequence after rate matching is denoted as .

6.3.2.4.2.5 HARQ-ACK and CG-UCI

For HARQ-ACK and CG-UCI transmission on PUSCH, the number of coded modulation symbols per layer for HARQ-ACK and CG-UCI transmission, denoted as , is determined according to Clause 6.3.2.4.1.5, by setting the number of CRC bits .

The input bit sequence to rate matching is .

Rate matching is performed according to Clause 5.4.3, by setting the rate matching output sequence length , where

– is the number of transmission layers of the PUSCH;

– is the modulation order of the PUSCH.

The output bit sequence after rate matching is denoted as .

6.3.2.4.2.6 UCI with different priority indexes

If uci-MuxWithDiffPrio is configured, and HARQ-ACK bits associated with priority index 0, and CSI part 1 if any are transmitted on a PUSCH associated with priority index 1:

– If CSI part 1 is also transmitted on the PUSCH,

– Perform rate matching for CSI part 1 according to clause 6.3.2.4.2.2, by assuming the number of HARQ-ACK information bits to be transmitted on PUSCH in clause 6.3.2.4.2.2 is 0 bit.

– Perform rate matching for HARQ-ACK with priority index 0 according to clause 6.3.2.4.2.3, by taking HARQ-ACK with priority index 0 as CSI part 2 and replacing by , and assuming the number of HARQ-ACK information bits to be transmitted on PUSCH in clause 6.3.2.4.2.3 is 0 bit.

– Otherwise, perform rate matching for HARQ-ACK with priority index 0 according to clause 6.3.2.4.2.2, by taking HARQ-ACK with priority index 0 as CSI-part 1 and replacing by , and assuming the number of HARQ-ACK information bits to be transmitted on PUSCH in clause 6.3.2.4.2.2 is 0 bit.

If uci-MuxWithDiffPrio is configured, and HARQ-ACK bits associated with priority index 1, and CSI if any are transmitted on a PUSCH associated with priority index 0:

– Perform rate matching for HARQ-ACK with priority index 1 according to clause 6.3.2.4.2.1, by taking HARQ-ACK with priority index 1 as HARQ-ACK and replacing by .

– Perform rate matching for CSI part 1 according to clause 6.3.2.4.2.2, by taking HARQ-ACK with priority index 1 as HARQ-ACK, if CSI part 1 is also transmitted on the PUSCH.

– Perform rate matching for CSI part 2 according to clause 6.3.2.4.2.3, by taking HARQ-ACK with priority index 1 as HARQ-ACK, if CSI part 2 is also transmitted on the PUSCH.

– Perform rate matching for HARQ-ACK with priority index 1 according to clause 6.3.2.4.2.1, by taking HARQ-ACK with priority index 1 as HARQ-ACK and replacing by , if HARQ-ACK bits associated with priority index 1 are transmitted without CG-UCI associated with priority index 1.

– Perform rate matching for CG-UCI with priority index 1 according to clause 6.3.2.4.2.4, if CG-UCI associated with priority index 1 is transmitted without HARQ-ACK bits associated with priority index 1.

– Perform rate matching for CG-UCI with priority index 1 and HARQ-ACK with priority index 1 according to clause 6.3.2.4.2.5, if both CG-UCI associated with priority index 1 and HARQ-ACK bits associated with priority index 1 are transmitted, by taking HARQ-ACK with priority index 1 as HARQ-ACK and replacing by .

– If CSI part 1 is also transmitted on the PUSCH and the PUSCH is associated with priority index 1,

– Perform rate matching for CSI part 1 according to clause 6.3.2.4.2.2, by taking HARQ-ACK with priority index 1 as HARQ-ACK.

– Perform rate matching for HARQ-ACK with priority index 0 according to clause 6.3.2.4.2.3, by taking HARQ-ACK with priority index 0 as CSI part 2 and replacing by , and taking HARQ-ACK with priority index 1 as HARQ-ACK.

– Otherwise,

– Perform rate matching for HARQ-ACK with priority index 0 according to clause 6.3.2.4.2.2, by taking HARQ-ACK with priority index 0 as CSI-part 1 and replacing by and taking HARQ-ACK with priority index 1 if any as HARQ-ACK, and taking CG-UCI associated with priority index 1 if any as CG-UCI.

– Perform rate matching for CSI part 1 according to clause 6.3.2.4.2.3, by taking CSI part 1 as CSI part 2 and replacing by , taking HARQ-ACK with priority index 0 as CSI-part 1, taking CG-UCI associated with priority index 1 if any as CG-UCI and taking HARQ-ACK with priority index 1 if any as HARQ-ACK, if CSI part 1 is also transmitted on the PUSCH and the PUSCH is associated with priority index 0.

– Perform rate matching for HARQ-ACK with priority index 1 according to clause 6.3.2.4.1.1, by taking HARQ-ACK with priority index 1 as HARQ-ACK and replacing by .

– Perform rate matching for CG-UCI associated with priority index 0 according to clause 6.3.2.4.2.2, if CG-UCI associated with priority index 0 is transmitted without HARQ-ACK bits associated with priority index 0, by taking CG-UCI associated with priority index 0 as CSI-part 1 and replacing by and taking HARQ-ACK with priority index 1 as HARQ-ACK.

– Perform rate matching for CG-UCI associated with priority index 0 and HARQ-ACK bits associated with priority index 0 according to clause 6.3.2.4.2.2, if both CG-UCI associated with priority index 0 and HARQ-ACK bits associated with priority index 0 are transmitted, by taking CG-UCI associated with priority index 0 and HARQ-ACK bits associated with priority index 0 as CSI-part 1 and replacing by and taking HARQ-ACK with priority index 1 as HARQ-ACK.

– Perform rate matching for CSI part 1 according to clause 6.3.2.4.2.3, by taking CSI part 1 as CSI part 2 and replacing by , taking CG-UCI associated with priority index 0 and HARQ-ACK bits associated with priority index 0 if any as CSI-part 1 and taking HARQ-ACK with priority index 1 as HARQ-ACK, if CSI part 1 is also transmitted on the PUSCH and the PUSCH is associated with priority index 0.

6.3.2.5 Code block concatenation

Code block concatenation is performed according to Clause 6.3.1.5, except that the values of and given in Clause 6.3.2.4.1.

6.3.2.6 Multiplexing of coded UCI bits to PUSCH

The coded UCI bits are multiplexed onto PUSCH according to the procedures in Clause 6.2.7.

6.3.2.7 Multiplexing of coded UCI bits with different priority indexes to PUSCH

If uci-MuxWithDiffPrio is configured, and HARQ-ACK bits associated with priority index 0, and CSI part 1 if any are transmitted on a PUSCH associated with priority index 1,

– If CSI part 1 is also transmitted on the PUSCH, the coded UCI bits are multiplexed onto PUSCH according to the procedures in Clause 6.2.7 by taking HARQ-ACK with priority index 0 as CSI part 2, and assuming the number of HARQ-ACK information in Clause 6.2.7 is 0 bit;

– Otherwise, the coded UCI bits are multiplexed onto PUSCH according to the procedures in Clause 6.2.7 by taking HARQ-ACK with priority index 0 as CSI-part 1, and assuming the number of HARQ-ACK information in Clause 6.2.7 is 0 bit.

If uci-MuxWithDiffPrio is configured, and HARQ-ACK bits associated with priority index 1, and CSI if any are transmitted on a PUSCH associated with priority index 0, the coded UCI bits are multiplexed onto PUSCH according to the procedures in Clause 6.2.7 by taking HARQ-ACK with priority index 1 as HARQ-ACK.

– if CSI part 1 is also transmitted on the PUSCH and the PUSCH is associated with priority index 1, the coded UCI bits are multiplexed onto PUSCH according to the procedures in Clause 6.2.7 by taking HARQ-ACK with priority index 1 as HARQ-ACK, and taking HARQ-ACK with priority index 0 as CSI part 2;

– otherwise, the coded UCI bits are multiplexed onto PUSCH according to the procedures in Clause 6.2.7 by taking HARQ-ACK with priority index 1 if any as HARQ-ACK, taking CG-UCI associated with priority index 1 if any as CG-UCI, taking HARQ-ACK with priority index 0 as CSI part 1, and taking CSI part 1 as CSI part 2 if CSI part 1 is also transmitted on the PUSCH and the PUSCH is associated with priority index 0.

If uci-MuxWithDiffPrio is configured, and CG-UCI associated with priority index 0 and HARQ-ACK bits associated with priority index 0 if any, HARQ-ACK bits associated with priority index 1, and CSI part 1 if any are transmitted on a PUSCH associated with priority index 0, the coded UCI bits are multiplexed onto PUSCH according to the procedures in Clause 6.2.7 by taking HARQ-ACK with priority index 1 as HARQ-ACK, taking CG-UCI associated with priority index 0 and HARQ-ACK bits associated with priority index 0 if any as CSI part 1, and taking CSI part 1 as CSI part 2 if CSI part 1 is also transmitted on the PUSCH and the PUSCH is associated with priority index 0.