UL power control for transport block transmissions spanning multiple slots

Abstract

A system and method for uplink power control for a transport block (TB) (TBoMS) spanning multiple slots is disclosed herein. In one embodiment, a method implemented by a wireless communication device includes determining a transmit power for a TBoMS uplink transmission for each TBoMS transmission opportunity and transmitting the TBoMS uplink transmission. In this manner, power control for the TBoMS is provided.

Description

[Technical field]

[0001] Related Applications This application claims the benefit of Provisional Patent Application No. PCT / CN2021 / 085475, filed April 3, 2021, and Provisional Patent Application No. PCT / CN2021 / 085712, filed April 6, 2021, the disclosures of which are incorporated herein by reference in their entireties.

[0002] The present disclosure relates to uplink power control in cellular communication systems. [Background technology]

[0003] Uplink Power Control As defined in the 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 38.213 v16.4.0, The slot index within a frame with system frame number SFN for which the PUSCH / PUCCH / SRS / PRACH transmission opportunity i is TIFF0007662820000001.tif7170, the first symbol S in the slot, and the number L of consecutive symbols.

[0004] Physical Uplink Shared Channel (PUSCH) power control in New Radio (NR) Release 16 is specified as shown in the following excerpt from section 7.1 of 3GPP TS38.213 v16.4.0: **********Start excerpt from 3GPP TS38.213 v16.3.0********** If the UE transmits a PUSCH on an active UL BWP b of carrier f of serving cell c using a parameter set configuration with index j and a PUSCH power control adjustment state with index l, the UE shall determine the PUSCH transmit power P PUSCH,b,f,c (i,j,q d ,l) Determined as TIFF0007662820000002.tif19170, Where: - P CMAX,f,c (i) is the UE configured maximum output power, as specified in [8-1, TS38.101-1], [8-2, TS38.101-2] and [8-3, TS38.101-3], for carrier f of serving cell c during PUSCH transmission opportunity i. - P O_PUSCH,b,f,c (j) is component P O_NOMINALPUSCH,f,c (j) and component P O_UE_PUSCH,b,f,c (j), where j∈{0,1,...,J-1}. - if the UE establishes a dedicated RRC connection using the Type-1 random access procedure as described in clause 8 and is not provided with a P0-PUSCH-AlphaSet or for a PUSCH (re)transmission corresponding to a RAR UL grant as described in clause 8.3, j=0, P O_UE_PUSCH,b,f,c (0)=0, and P O_NOMINAL_PUSCH,f,c (0)=P O_PRE +Δ PREAMBLE_Msg3 and Here, for carrier f of serving cell c, P O_PRE is provided by preambleReceivedTargetPower [11, TS38.321], and Δ PREAMBLE_Msg3 is provided by msg3-DeltaPreamble, or, if msg3-DeltaPreamble is not provided, Δ PREAMBLE_Msg3 = 0 dB - if the UE establishes a dedicated RRC connection using the Type-2 random access procedure described in clause 8 and is not provided with a P0-PUSCH-AlphaSet or for PUSCH transmission for the Type-2 random access procedure described in clause 8.1A, j=0, P O_UE_PUSCH,b,f,c (0)=0, and P O_NOMINAL_PUSCH,f,c (0)=P O_PRE +Δ MsgA_PUSCH and Here, for carrier f of serving cell c, P O_PRE is provided by msgA-preambleReceivedTargetPower, or, if msgA-preambleReceivedTargetPower is not provided, by preambleReceivedTargetPower, and Δ MsgA_PUSCH is provided by msgA-DeltaPreamble, or, if msgA-DeltaPreamble is not provided, Δ MsgA_PUSCH = Δ PREAMBLE_Msg3 dB For PUSCH (re)transmissions configured by ConfiguredGrantConfig, j=1 and P O_NOMINAL_PUSCH,f,c (1) is provided by p0-NominalWithoutGrant, or if p0-NominalWithoutGrant is not provided, P O_NOMINAL_PUSCH,f,c (1)=P O_NOMINAL_PUSCH,f,c (0) and P O_UE_PUSCH,b,f,c (1) provides an index P0-PUSCH-AlphaSetId to the set of P0-PUSCH-AlphaSets for active UL BWP b of carrier f of serving cell c, obtained from p0-PUSCH-Alpha in ConfiguredGrantConfig, provided by p0 - j∈{2,...,J-1}=S J For all j∈S J About applicable P O_NOMINAL_PUSCH,f,c (j) Value is provided by p0-NominalWithGrant for each carrier f of serving cell c, or P O_NOMINAL_PUSCH,f,c (j)=P O_NOMINAL_PUSCH,f,c (0) and P O_UE_PUSCH,b,f,c (j) The set of values ​​is provided by the set of p0 in P0-PUSCH-AlphaSet indicated by the respective set of p0-PUSCH-AlphaSetId for the active UL BWP b of carrier f of serving cell c. - if the UE is provided with more than one value of p0-PUSCH-AlphaSetId by SRI-PUSCH-PowerControl and if the DCI format for scheduling PUSCH transmission includes an SRI field, the UE shall obtain from sri-PUSCH-PowerControlId in SRI-PUSCH-PowerControl a mapping between a set of values ​​for the SRI field in the DCI format [5, TS38.212] and a set of indices provided by p0-PUSCH-AlphaSetId that map to a set of P0-PUSCH-AlphaSet values, and shall select from the p0-PUSCH-AlphaSetId values ​​that are mapped to the SRI field values ​​a P0-PUSCH-AlphaSetId. O_UE_PUSCH,b,f,c If the DCI format also includes an open-loop power control parameter set indication field, and the value of the open-loop power control parameter set indication field is “1”, the UE determines the value of P0-PUSCH-SetId from the first value in P0-PUSCH-Set having a p0-PUSCH-SetId value that is mapped to the SRI field value. O_UE_PUSCH,b,f,c Determine the value of (j). - j=2 if a PUSCH transmission, excluding a PUSCH retransmission corresponding to a RAR UL grant, is scheduled by a DCI format that does not include an SRI field or if SRI-PUSCH-PowerControl is not provided to the UE; - If P0-PUSCH-Set is provided to the UE and the DCI format includes an open loop power control parameter set indication field, the UE shall O_UE_PUSCH,b,f,c The value of (j) is - if the value of the open loop power control parameter set indication field is '0' or '00', determine from the first P0-PUSCH-AlphaSet in p0-AlphaSets; - if the value of the open loop power control parameter set indication field is '1' or '01', then determine from the first value in the P0-PUSCH-Set with the lowest p0-PUSCH-SetID value; - if the value of the open loop power control parameter set indication field is '10', then determine from the second value in the P0-PUSCH-Set with the lowest p0-PUSCH-SetID value; - otherwise, the UE O_UE_PUSCH,b,f,c (j) is determined from the value of the first P0-PUSCH-AlphaSet in p0-AlphaSets. - α b,f,c Regarding (j), - If j=0, - P O_NOMINAL_PUSCH,f,c (0)=P O_PRE +Δ MsgA_PUSCH and if msgA-Alpha is provided, α b,f,c (0) is the value of msgA-Alpha - No, P O_NOMINAL_PUSCH,f,c (0)=P O_PRE +Δ PREAMBLE_Msg3 or if msgA-Alpha is not provided and msg3-Alpha is provided, α b,f,c (0) is the value of msg3-Alpha - otherwise, α b,f,c (0)=1 - For j=1, α b,f,c (1) is provided by alpha, obtained from p0-PUSCH-Alpha in ConfiguredGrantConfig, which provides an index P0-PUSCH-AlphaSetId to the set of P0-PUSCH-AlphaSet for active UL BWP b of carrier f of serving cell c. - j ∈ S j In the case of α b,f,c (j) The set of values ​​is provided by the set of alpha in P0-PUSCH-AlphaSet indicated by the respective set of p0-PUSCH-AlphaSetId for the active UL BWP b of carrier f of serving cell c. - if the UE is provided with SRI-PUSCH-PowerControl and two or more values ​​of p0-PUSCH-AlphaSetId, and if the DCI format for scheduling PUSCH transmission includes an SRI field, the UE shall obtain from sri-PUSCH-PowerControlId in SRI-PUSCH-PowerControl a mapping between a set of values ​​for the SRI field in the DCI format [5, TS38.212] and a set of indices provided by p0-PUSCH-AlphaSetId that map to a set of P0-PUSCH-AlphaSet values, and from the p0-PUSCH-AlphaSetId values ​​that map to the SRI field values, determine α b,f,c Determine the value of (j) - if a PUSCH transmission, excluding a PUSCH retransmission corresponding to an RAR UL grant, is scheduled by a DCI format that does not include an SRI field or if SRI-PUSCH-PowerControl is not provided to the UE, j=2, and the UE selects α from the value of the first P0-PUSCH-AlphaSet in p0-AlphaSets. b,f,c (j) Determine - TIFF0007662820000003.tif7170 is the bandwidth of the PUSCH resource allocation expressed in number of resource blocks for a PUSCH transmission opportunity i on active UL BWP b of carrier f of serving cell c, and μ is the SCS setting specified in [4, TS38.211]. - PL b,f,c (q d ) is the reference signal (RS) index q for the active DL BWP of carrier f of serving cell c as described in clause 12. d is the downlink path loss estimate in dB, calculated by the UE using - If the UE is not provided with PUSCH-PathlossReferenceRS and enableDefaultBeamPL-ForSRS, or before the UE is provided with dedicated higher layer parameters, the UE shall use RS resources from the SS / PBCH block with the same SS / PBCH block index as the SS / PBCH block index used by the UE to acquire the MIB. b,f,c (q d ) - if the UE is configured with a number of RS resource indexes up to the value of maxNrofPUSCH-PathlossReferenceRSs and a respective set of RS configurations for the number of RS resource indexes by PUSCH-PathlossReferenceRS, the set of RS resource indexes may include one or both of a set of SS / PBCH block indexes, each provided by ssb-Index when the corresponding value of pusch-PathlossReferenceRS-Id maps to an SS / PBCH block index, and a set of CSI-RS resource indexes, each provided by csi-RS-Index when the corresponding value of pusch-PathlossReferenceRS-Id maps to a CSI-RS resource index. The UE may select an RS resource index q in the set of RS resource indexes to correspond to either an SS / PBCH block index or a CSI-RS resource index, each provided by pusch-PathlossReferenceRS-Id in PUSCH-PathlossReferenceRS. d Identify - if the PUSCH transmission is scheduled by a RAR UL grant as described in subclause 8.3 or for a PUSCH transmission for a Type-2 random access procedure as described in subclause 8.1A, the UE shall select the same RS resource index q as for the corresponding PRACH transmission. d Use - if the UE is provided with SRI-PUSCH-PowerControl and two or more values ​​of PUSCH-PathlossReferenceRS-Id, the UE shall obtain from sri-PUSCH-PowerControlId in SRI-PUSCH-PowerControl a mapping between a set of values ​​for the SRI field in the DCI format for scheduling PUSCH transmission and a set of PUSCH-PathlossReferenceRS-Id values, and from the values ​​of PUSCH-PathlossReferenceRS-Id that are mapped to the SRI field values, d where the RS resource is either on serving cell c or, if provided, on a serving cell indicated by the value of pathlossReferenceLinking. - if a PUSCH transmission is scheduled according to DCI format 0_0 and if the UE is provided with spatial settings by PUCCH-SpatialRelationInfo for the PUCCH resource with the lowest index for each carrier f and active UL BWP b of serving cell c as described in clause 9.2.2, the UE shall select the same RS resource index q as for the PUCCH transmission on the PUCCH resource with the lowest index. d Use - if the PUSCH transmission is not scheduled by DCI format 0_0, and if the UE is provided with enableDefaultBeamPL-ForSRS and is not provided with PUSCH-PathlossReferenceRS and PUSCH-PathlossReferenceRS-r16, the UE shall select the same RS resource index q as in the SRS resource set with the SRS resource associated with the PUSCH transmission. d Use - In the following cases: - PUSCH transmission is scheduled by DCI format 0_0 and the UE is not provided with a spatial setting for PUCCH transmission, or - the PUSCH transmission is scheduled by DCI format 0_1 ​​or DCI format 0_2, which does not include an SRI field, or - SRI-PUSCH-PowerControl is not provided to the UE The UE shall send the RS resource index q d where the RS resource is either on serving cell c or, if provided, on a serving cell indicated by the value of pathlossReferenceLinking. - In the following cases: - PUSCH transmission is scheduled by DCI format 0_0 on serving cell c; - the UE is not provided with PUCCH resources for an active UL BWP of the serving cell c, and - The UE is provisioned with enableDefaultBeamPL-ForPUSCH0-0 The UE provides periodic RS resources with qcl-Type set to “typeD” in the TCI state or QCL assumption of the CORESET with the lowest index in the active DL BWP of the serving cell c with RS resource index q d Determine - In the following cases: - PUSCH transmission is scheduled by DCI format 0_0 on serving cell c; - the UE is not provided with a spatial setting for PUCCH resources on the active UL BWP of the primary cell [11, TS 38.321], and - The UE is provisioned with enableDefaultBeamPL-ForPUSCH0-0 The UE provides periodic RS resources with qcl-Type set to “typeD” in the TCI state or QCL assumption of the CORESET with the lowest index in the active DL BWP of the serving cell c with RS resource index q d Determine For a PUSCH transmission configured by ConfiguredGrantConfig, if rrc-ConfiguredUplinkGrant is included in ConfiguredGrantConfig, then RS resource index q d is provided by the value of pathlossReferenceIndex included in the rrc-ConfiguredUplinkGrant, where the RS resources are either on serving cell c or, if provided, on the serving cell indicated by the value of pathlossReferenceLinking. For a PUSCH transmission configured by ConfiguredGrantConfig that does not include rrc-ConfiguredUplinkGrant, the UE determines the RS resource index q from the value of PUSCH-PathlossReferenceRS-Id that is mapped to the SRI field value in the DCI format that activates the PUSCH transmission. d If the DCI format that activates the PUSCH transmission does not include an SRI field, the UE shall determine the RS resource indexes q d where the RS resource is either on serving cell c or, if provided, on a serving cell indicated by the value of pathlossReferenceLinking. - if the UE is provided with enablePL-RS-UpdateForPUSCH-SRS, the mapping between sri-PUSCH-PowerControlId values ​​and PUSCH-PathlossReferenceRS-Id values ​​may be updated by the MAC CE as described in [11, TS38.321] - for a PUSCH transmission scheduled by a DCI format that does not include an SRI field or activated as described in clause 10.2 by a DCI format that does not include an SRI field configured by ConfiguredGrantConfig, RS resource index q d q d is determined from the PUSCH-PathlossReferenceRS-Id that is mapped to sri-PUSCH-PowerControlId=0 PL b,f,c (q d ) = referenceSignalPower - upper layer filtered RSRP, where referenceSignalPower is provided by the upper layers, RSRP is specified in [7, TS38.215] for the reference serving cell, and the upper layer filter configuration provided by QuantityConfig is specified in [12, TS38.331] for the reference serving cell. If the UE is not configured for periodic CSI-RS reception, then referenceSignalPower is provided by ss-PBCH-BlockPower. If the UE is configured for periodic CSI-RS reception, then referenceSignalPower is either provided by ss-PBCH-BlockPower or by powerControlOffsetSS, which provides the offset of the CSI-RS transmit power relative to the SS / PBCH block transmit power [6, TS38.214]. If powerControlOffsetSS is not provided to the UE, then the UE shall assume an offset of 0 dB. -Ks If = 1.25, TIFF0007662820000004.tif7170, K s If = 0, Δ TF,b,f,c (i)=0, where K s is given by deltaMCS for each UL BWP b of each carrier f and serving cell c. If the PUSCH transmission spans more than one layer [6, TS38.214], Δ TF,b,f,c (i)=0. The BPRE and the BPRE for the active UL BWP b of each carrier f and each serving cell c are TIFF0007662820000005.tif6170 is calculated as follows - For PUSCH with UL-SCH data TIFF0007662820000006.tif9170, and CSI transmission on PUSCH without UL-SCH data TIFF0007662820000007.tif7170, where: - C is the number of code blocks to be transmitted, and K r is the size of the code block r, and N RE teeth, The number of resource elements determined as TIFF0007662820000008.tif12170, where: TIFF0007662820000009.tif7170 is the number of symbols for PUSCH transmission opportunity i on active UL BWP b of carrier f of serving cell c, TIFF0007662820000010.tif7170 is the number of subcarriers in PUSCH symbol j, excluding DM-RS subcarriers and phase tracking RS samples [4, TS38.211], and assuming no segmentation for nominal repetition when the PUSCH transmission has repetition type B, TIFF0007662820000011.tif7170, C, K r is specified in [5, TS38.212] - when the PUSCH contains UL-SCH data, TIFF0007662820000012.tif6170, and the PUSCH contains CSI and no UL-SCH data, as described in clause 9.3: TIFF0007662820000013.tif6170 - As explained in [6, TS38.214], Q m is the modulation order, R is the target code rate, and is provided by the DCI format that schedules the PUSCH transmission containing CSI and no UL-SCH data. - PUSCH power control adjustment state f for active UL BWP b of carrier f of serving cell c at PUSCH transmission opportunity i b,f,c Regarding (i,l) - δ PUSCH,b,f,c (i,l) is the TPC command value that is included in the DCI format to schedule PUSCH transmission opportunity i on active UL BWP b of carrier f of serving cell c, or is jointly coded with other TPC commands in DCI format 2_2 with CRC scrambled by the TPC-PUSCH-RNTI, as described in clause 11.3. l ∈ {0,1} if twoPUSCH-PC-AdjustmentStates is configured in the UE, and l = 0 if twoPUSCH-PC-AdjustmentStates is not configured in the UE or if PUSCH transmission is scheduled by a RAR UL grant as described in clause 8.3. For PUSCH (re)transmissions configured by ConfiguredGrantConfig, the value of l ∈ {0,1} is provided to the UE by powerControlLoopToUse If the UE is provided with SRI-PUSCH-PowerControl, the UE obtains a mapping between a set of values ​​for the SRI field in the DCI format for scheduling PUSCH transmissions and the l value(s) provided by sri-PUSCH-ClosedLoopIndex and determines the l value to be mapped to the SRI field value. - l=0 if the PUSCH transmission is scheduled by a DCI format that does not contain an SRI field or if SRI-PUSCH-PowerControl is not provided to the UE. - if the UE obtains one TPC command from DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI, the l value is provided by the closed-loop indicator field in DCI format 2_2; - TIFF0007662820000014.tif11170 is the PUSCH power control adjustment state l for active UL BWP b and PUSCH transmission opportunity i of carrier f of serving cell c when the UE is not provided with tpc-Accumulation, where: - δ PUSCH,b,f,c The values ​​are given in Table 7.1.1-1 - TIFF0007662820000015.tif10170 represents the PUSCH transmission opportunity ii on the active UL BWP b of carrier f of serving cell c for PUSCH power control adjustment state l. 0 K before PUSCH (ii 0 )-1 symbols before PUSCH transmission opportunity i PUSCH (i) symbols received by the UE between i ) a set of TPC command values ​​D i where i 0 >0 is PUSCH transmission opportunity ii 0 K before PUSCH (ii 0) symbols before PUSCH transmission opportunity i PUSCH (i) is the smallest integer that is faster than symbols - K if PUSCH transmission is scheduled by the DCI format PUSCH (i) is the number of symbols for an active UL BWP b of carrier f of serving cell c after the last symbol of the corresponding PDCCH reception and before the first symbol of the PUSCH transmission - K if PUSCH transmission is configured by ConfiguredGrantConfig PUSCH (i) is the number of symbols per slot for the active UL BWP b of carrier f of serving cell c K, which is equal to the product of TIFF0007662820000016.tif7170 and the minimum of the value provided by k2 in PUSCH-ConfigCommon PUSCH,min is the number of symbols - UE receives PUSCH transmission opportunity ii 0 the maximum power for the active UL BWP b of carrier f of serving cell c is reached at If TIFF0007662820000017.tif10170, then b,f,c (i,l)=f b,f,c (ii 0 ,l) - UE receives PUSCH transmission opportunity ii 0 a minimum power is reached for the active UL BWP b of carrier f of serving cell c at If TIFF0007662820000018.tif11170, then b,f,c (i,l)=f b,f,c (ii 0 ,l) The UE calculates an accumulation of PUSCH power control adjustment states l for an active UL BWP b of a carrier f of a serving cell c as f b,f,c Reset (k,l)=0, k=0,1,...,i - Corresponding P O_UE_PUSCH,b,f,c(j) if configuration for the value is provided by a higher layer, - the corresponding alpha b,f,c (j) if configuration for the value is provided by a higher layer, Here, l is - if j>1 and the UE is provided with an upper SRI-PUSCH-PowerControl, l is the sri-PUSCH-ClosedLoopIndex value(s) configured in any SRI-PUSCH-PowerControl with sri-P0-PUSCH-AlphaSetId value corresponding to j - l=0 if j>1 and the UE is not provided with SRI-PUSCH-PowerControl or j=0. - if j=1, l is given by the value of powerControlLoopToUse is determined from the value of j as -f b,f,c (i,l)=δ PUSCH,b,f,c (i,l) is the PUSCH power control adjustment state for active UL BWP b of carrier f of serving cell c and PUSCH transmission opportunity i when the UE is provided with tpc-Accumulation, where: - δ PUSCH,b,f,c Absolute values ​​are given in Table 7.1.1-1 - if the UE receives a random access response message in response to a PRACH or MsgA transmission on an active UL BWP b of carrier f of a serving cell c as described in clause 8; -f b,f,c (0,l)=ΔP rampup,b,f,c +δ msg2,b,f,c where l=0, - δ msg2,b,f,cis the TPC command value indicated in the random access response grant of a random access response message corresponding to a PRACH transmission according to a Type-1 random access procedure or to a MsgA transmission according to a Type-2 random access procedure with RAR message(s) for fallbackRAR on an active UL BWP b of carrier f in a serving cell c, - TIFF0007662820000019.tif18170, and ΔP rampuprequested,b,f,c is provided by higher layers and corresponds to the total power ramp-up requested by higher layers from the first random access preamble to the last random access preamble for carrier f in serving cell c; TIFF0007662820000020.tif6170 is the bandwidth of the PUSCH resource allocation expressed in number of resource blocks for the first PUSCH transmission on the active UL BWP b of carrier f of serving cell c, and Δ TF,b,f,c (0) is the power adjustment for the first PUSCH transmission on active UL BWP b of carrier f of serving cell c. - if the UE transmits a PUSCH at a PUSCH transmission opportunity i on an active UL BWP b of carrier f of serving cell c as described in clause 8.1A, b,f,c (0,l)=Δ P_rampup,b,f,c where: - l=0, - TIFF0007662820000021.tif18170, and ΔP rampuprequested,b,f,c corresponds to the total power ramp-up provided by and requested by the higher layers, TIFF0007662820000022.tif6170 is the bandwidth of the PUSCH resource allocation expressed in number of resource blocks, and Δ TF,b,f,c(i) is the power adjustment for the PUSCH transmission at PUSCH transmit opportunity i. **********END EXCERPT FROM 3GPP TS38.213 v16.3.0**********

[0005] Layer 3 Filtering Layer 3 filtering is specified as shown in the following excerpt from 3GPP TS38.331 v16.3.1: **********Start excerpt from 3GPP TS38.331 v16.3.1********** 5.5.3.2 Layer 3 Filtering The UE shall: 1> for each cell measurement quantity, each beam measurement quantity, each sidelink measurement quantity required in subclause 5.8.10 and for each CLI measurement quantity for which the UE performs measurements according to 5.5.3.1, [1] 2> Before being used for evaluation of reporting criteria or for measurement reporting, the measured results are filtered by the following formula: F n =(1-a)*F n-1 +a*M n [2] Where: M n is the most recent received measurement from the physical layer. F n is the updated filtered measurement result used for evaluation of reporting criteria or for measurement reporting. F n-1 is the old filtered measurement, where F 0 When the first measurement result from the physical layer is received, M 1 For MeasObjectNR, a=1 / 2 (ki / 4) where k iis the filterCoefficient for the corresponding measurement quantity of the i-th QuantityConfigNR in the quantityConfigNR-List, where i is indicated by the quantityConfigIndex in MeasObjectNR, and for other measurements, a=1 / 2 (k / 4) where k is the filterCoefficient for the corresponding measurement received by quantityConfig, and a=1 / 2 for UTRA-FDD. (k / 4) where k is the filterCoefficient for the corresponding measurement quantity received by UTRA-FDD in QuantityConfig. [3] 2> filterCoefficient k adapts the filter such that its time characteristics are preserved at different input rates, assuming a sample rate equal to Xms. The value of X is equivalent to one intra-frequency L1 measurement period as specified in TS38.133

[14] , assuming non-DRX operation, and depends on the frequency range. NOTE 1: If k is set to 0, then layer 3 filtering is not applicable. NOTE 2: Filtering is performed in the same domain as that used for evaluation of the reporting criteria or for measurement reporting, i.e. logarithmic filtering for logarithmic measurements. NOTE 3: The filter input rate is implementation dependent in order to meet the performance requirements set in TS 38.133

[14] . For further details regarding physical layer measurements, please refer to TS 38.133

[14] . NOTE 4: In case of CLI-RSSI measurements, it is up to the UE implementation whether the filtering should be reset when switching BWP. ... - FilterCoefficient IE FilterCoefficient specifies the measurement filtering coefficient, where the value fc0 corresponds to k=0, fc1 corresponds to k=1, and so on. FilterCoefficient Information Element TIFF0007662820000023.tif27170**********END EXCERPT FROM 3GPP TS38.331 v16.3.1**********

[0006] Agreement on TBoMS in Rel-17 NR Coverage Extension WI In the Work Item Description (WID) for Release 17 NR Coverage Extension, it was agreed that a single Transport Block (TB) transmission across multiple slots is specified as indicated in the following agreement: agreement: Specify the mechanism(s) to support TB processing over multi-slot PUSCH [RAN1] o A TBS that is determined based on multiple slots and transmitted across multiple slots.

[0007] Several relevant agreements were reached at the RAN1#104 meeting. agreement: Consider one or two of the following options as a starting point for designing the time domain resource decision for TBoMS: o PUSCH repetition type A like TDRA, i.e. the number of allocated symbols is the same in each slot. PUSCH repetition type B like TDRA, i.e. the number of allocated symbols in each slot can vary agreement: Consecutive physical slots for UL transmission can be used for TBoMS for unpaired spectrum In RAN1#104b-e, to resolve whether to support non-contiguous physical slots for UL transmission for TBoMS for unpaired spectrum Consecutive physical slots for UL transmission can be used for TBoMS for paired spectrum and SUL bands o Whether non-contiguous physical slots for UL transmission are also supported for paired spectrum and SUL bands, FFS Summary of the Invention

[0008] A system and method for uplink power control for a transport block (TB) (TBoMS) spanning multiple slots is disclosed herein. In one embodiment, a method implemented by a wireless communication device includes determining a transmit power for a TBoMS uplink transmission for each TBoMS transmission opportunity and transmitting the TBoMS uplink transmission according to the transmit power. In this manner, power control for the TBoMS is provided.

[0009] In one embodiment, the transmit power is a linear transmit power.In one embodiment, the TBoMS uplink transmission is a TBoMS Physical Uplink Shared Channel (PUSCH) transmission.

[0010] In one embodiment, one TBoMS transmission opportunity is defined as the portion of the TBoMS uplink transmission in one slot, and the TBoMS transmission opportunity is defined as a slot index in a frame having a system frame number SFN. TIFF0007662820000024.tif7170, the first symbol S in the slot, and the number L of consecutive symbols of TBoMS uplink transmission in the slot.

[0011] In one embodiment, one TBoMS transmission opportunity for a TBoMS uplink transmission spans two or more consecutive slots of a TBoMS uplink transmission. In one embodiment, one TBoMS transmission opportunity for a TBoMS uplink transmission is represented by the index of the first slot of the TBoMS transmission opportunity with the system frame number SFN. TIFF0007662820000025.tif7170, the first symbol S in the first slot of the TBoMS transmission opportunity, and the number L of consecutive symbols of TBoMS uplink transmission in the first slot, or the total number L of symbols of TBoMS uplink transmission in the transmission opportunity.

[0012] In one embodiment, one TBoMS transmission opportunity for a TBoMS uplink transmission spans two or more consecutive or non-consecutive slots of a TBoMS uplink transmission. In one embodiment, one TBoMS transmission opportunity for a TBoMS uplink transmission is represented by the index of the first slot of the TBoMS transmission opportunity with the system frame number SFN. TIFF0007662820000026.tif7170, a first symbol S in the first slot, and a number L of symbols of the TBoMS uplink transmission either in the first slot or across multiple slots of the TBoMS uplink transmission.

[0013] In one embodiment, every slot for TBoMS uplink transmission is treated as a single TBoMS transmission opportunity.

[0014] In one embodiment, the set of all slots for TBoMS uplink transmission is divided into two or more subsets, and each subset of the two or more subsets is treated as one TBoMS transmission opportunity.

[0015] In one embodiment, the wireless communication device supports two or more options for how TBoMS transmission opportunities are defined, and one of the two or more options used by the wireless communication device when determining the transmit power for a TBoMS uplink transmission for each TBoMS transmission opportunity is either configured or predetermined (e.g., predefined) by the network node.

[0016] In one embodiment, one TBoMS transmission opportunity spans two or more slots, and determining a transmit power for a TBoMS uplink transmission for each TBoMS transmission opportunity includes either determining a transmit power for the TBoMS transmission opportunity, where the transmit power is equivalent to the transmit power determined for a first slot of the TBoMS transmission opportunity, and where the same transmit power is kept until an end of the TBoMS transmission opportunity, or determining a transmit power for the TBoMS transmission opportunity taking into account the two or more slots of the TBoMS transmission opportunity as a whole. In one embodiment, the specific parameter is different for at least two of the two or more slots of the TBoMS transmission opportunity, and determining the transmit power for the TBoMS transmission opportunity includes determining a transmit power for the TBoMS transmission opportunity based on the specific parameter for a fixed one or more of the two or more slots of the TBoMS transmission opportunity.

[0017] In one embodiment, whether or not a change in transmit power is allowed during a TBoMS uplink transmission is either configured or predetermined by a network node. In one embodiment, whether or not a change in transmit power is allowed between repetitions of a TBoMS uplink transmission is either configured or predetermined by a network node. In one embodiment, the transmit power is interdependent on one or more other features (e.g., cross-slot channel estimation). In one embodiment, the transmit power varies between TBoMS transmission opportunities for a TBoMS uplink transmission based on one or more parameters. In one embodiment, the one or more parameters include (a) a data-to-DMRS ratio in each slot, (b) a group-common TPC command, (c) a reference signal, (d) a path loss estimation, a PUSCH power control adjustment state, or (e) any combination of two or more of (a)-(d).

[0018] In one embodiment, the same transmit power is set or predetermined across multiple slots of a TBoMS uplink transmission, and the wireless communication device determines the transmit power prior to the transmission based on the transmit power in the first slot, and keeps the transmit power the same until the end of the TBoMS uplink transmission. the wireless communication device does not expect to receive a TPC command for a TBoMS uplink transmission during the TBoMS uplink transmission, and / or If the wireless communication device receives a TPC command for a TBoMS uplink transmission during a TBoMS uplink transmission, The wireless communication device discards the TPC command, or o the wireless communication device applies the TPC commands in the next transmission after the TBoMS uplink transmission, and / or the wireless communication device does not expect that the respective base station will modify the reference signal and its transmit power that the wireless communication device uses to estimate downlink path loss during TBoMS uplink transmissions; and / or The wireless communication device does not perform downlink path loss measurements from the physical layer during TBoMS uplink transmissions, and / or · The wireless communication device does not expect the PUSCH power control adjustment state to be changed by RRC or DCI signaling during a TBoMS uplink transmission.

[0019] In one embodiment, determining the transmit power for the TBoMS uplink transmission for each TBoMS transmission opportunity includes calculating one or more TBoMS transmission opportunity related parameters. In one embodiment, the one or more TBoMS transmission opportunity related parameters include (I) an MCS-related parameter Δ TF,b,f,c (i), (II) BPRE, (III) PUSCH power control adjustment state f for active UL BWP b of carrier f of serving cell c in PUSCH transmission opportunity i. b,f,c(i, l), or (IV) any combination of two or more of (I)-(III). In another embodiment, the one or more TBoMS transmission opportunity related parameters include a BPRE. In one embodiment, the BPRE is BPRE for multi-slot PUSCH with UL-SCH, calculated over multiple slots of TBoMS as TIFF0007662820000027.tif14170; Here, N RE teeth, TIFF0007662820000028.tif12170, where N is the total number of transmission opportunities for TBoMS; TIFF0007662820000029.tif7170 is the number of symbols for PUSCH transmission opportunity i on active UL BWP b of carrier f of serving cell c, TIFF0007662820000030.tif7170 is the number of subcarriers excluding DM-RS subcarriers and phase tracking RS samples in PUSCH symbol j, The file is TIFF0007662820000031.tif7170.

[0020] In one embodiment, the BPRE is BPRE for multi-slot PUSCH with UL-SCH, calculated over multiple slots of TBoMS as TIFF0007662820000032.tif14170; Where: - N RE teeth, The number of resource elements determined as TIFF0007662820000033.tif11170, where i=0, TIFF0007662820000034.tif7170 is the number of symbols for the first transmission opportunity for TBoMS on active UL BWP b of carrier f of serving cell c, TIFF0007662820000035.tif6170 is the number of subcarriers in PUSCH symbol j, excluding DM-RS subcarriers and phase tracking RS samples [TS38.211], and assuming no segmentation for nominal repetition when the PUSCH transmission has repetition type B; TIFF0007662820000036.tif7170, - N is the total number of transmission opportunities for TBoMS.

[0021] In one embodiment, TPC accumulation is disabled and an absolute power offset value is used for power adjustment, and determining a transmit power for a TBoMS uplink transmission per TBoMS transmission opportunity includes determining an absolute power adjustment in each slot of the TBoMS uplink transmission. In one embodiment, the absolute power adjustment is determined by a most recent TPC command received before a start of a first slot for a TBoMS uplink transmission, or a start of a first scheduled symbol of a first slot for a TBoMS uplink transmission, or a start of a set of symbols / slots prior to a first slot for a TBoMS uplink transmission.

[0022] In one embodiment, multiple TBoMS transmit opportunities are used for power calculation for TBoMS uplink transmission, and the absolute power adjustment for determining the transmit power in one TBoMS transmit opportunity is determined by the most recent TPC command received before the start of the first slot of the TBoMS transmit opportunity, or the start of the first symbol of the first slot of the TBoMS transmit opportunity, or the start of the set of symbols / slots prior to the first slot of the TBoMS transmit opportunity.

[0023] In one embodiment, TPC accumulation is enabled, the accumulated power offset value is used for power adjustment, and determining the transmit power for the TBoMS uplink transmission per TBoMS transmission opportunity includes determining an accumulated power adjustment in each slot of the TBoMS uplink transmission.

[0024] In one embodiment, TPC accumulation is enabled, and the accumulated power offset value is used for power adjustment, and determining a transmit power for a TBoMS uplink transmission per TBoMS transmission opportunity includes determining a transmit power for a TBoMS uplink transmission per TBoMS transmission opportunity on an active uplink bandwidth portion b of carrier f of serving cell c for a PUSCH power control adjustment state l for TBoMS transmission opportunity ii. 0 K before PUSCH (ii 0 )-1 symbol and K PUSCH (i) determining a cumulative power adjustment in a TBoMS transmit opportunity for a TBoMS uplink transmission based on a set of TPC commands received between symbols i 0 >0 is PUSCH transmission opportunity ii 0 K before PUSCH (ii 0 ) symbols before PUSCH transmission opportunity i PUSCH (i) symbols earlier. In one embodiment, when PUSCH transmission is scheduled by a downlink control information (DCI) format, PUSCH (i) is the number of symbols for the active uplink bandwidth portion b of carrier f of serving cell c after the last symbol of the corresponding physical downlink control channel (PDCCH) reception and before the first symbol of the first slot of the current PUSCH opportunity i of the TBoMS transmission.

[0025] In one embodiment, TPC accumulation is enabled, an accumulated power offset value is used for power adjustment, and multiple TBoMS transmission opportunities are used for power calculation for one TBoMS transmission, and determining 300 a transmit power for a TBoMS uplink transmission for each TBoMS transmission opportunity includes determining a transmit power for PUSCH transmission opportunity ii on an active uplink bandwidth portion b of carrier f of serving cell c for a PUSCH power control adjustment state l. 0 K before PUSCH (ii 0 )-1 symbols before PUSCH transmission opportunity i PUSCH(i) determining a cumulative power adjustment in a TBoMS transmit opportunity for a TBoMS uplink transmission based on a set of TPC commands received between symbols i 0 >0 is PUSCH transmission opportunity ii 0 K before PUSCH (ii 0 ) symbols before PUSCH transmission opportunity i PUSCH (i) symbols earlier. In one embodiment, when PUSCH transmission is scheduled by a downlink control information (DCI) format, PUSCH (i) is the number of symbols for the active uplink bandwidth portion b of carrier f of serving cell c after the last symbol of the corresponding physical downlink control channel (PDCCH) reception and before the first symbol of the first slot of the current PUSCH opportunity i of the TBoMS transmission.

[0026] Corresponding embodiments of wireless communication devices are also disclosed herein.

[0027] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate several aspects of the present disclosure and, together with the description, serve to explain the principles of the disclosure. [Brief description of the drawings]

[0028] [Figure 1] FIG. 1 illustrates an example of a cellular communication system in which embodiments of the present disclosure may be implemented. [Diagram 2] FIG. 13 illustrates an example of TBoMS transmission opportunities for an example where TBoMS spans four uplink (UL) slots with a set of slots configured with a specific TDD setting {DDSUUDDSUU}. [Diagram 3] 4 is a flowchart illustrating the operation of a wireless communication device (e.g., a user equipment device (UE)) in accordance with an embodiment of the present disclosure. [Figure 4] FIG. 2 is a schematic block diagram of a network node according to some embodiments of the present disclosure. [Diagram 5] FIG. 2 is a schematic block diagram of a network node according to some embodiments of the present disclosure. [Figure 6] FIG. 2 is a schematic block diagram of a network node according to some embodiments of the present disclosure. [Figure 7] 1 is a schematic block diagram of a wireless communication device (e.g., a UE) in accordance with some embodiments of the present disclosure. [Figure 8] 1 is a schematic block diagram of a wireless communication device (e.g., a UE) in accordance with some embodiments of the present disclosure. [Figure 9] FIG. 1 illustrates a communication network connected to a host computer through an intermediate network in accordance with some embodiments of the present disclosure. [Figure 10] FIG. 2 is a generalized block diagram of a host computer communicating with a UE via a base station over a partial wireless connection in accordance with some embodiments of the present disclosure. [Figure 11] 1 is a flowchart illustrating a method implemented in a communication system according to an embodiment of the present disclosure. [Figure 12] 1 is a flowchart illustrating a method implemented in a communication system according to an embodiment of the present disclosure. [Figure 13] 1 is a flowchart illustrating a method implemented in a communication system according to an embodiment of the present disclosure. [Figure 14] 1 is a flowchart illustrating a method implemented in a communication system according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0029] The embodiments described below represent information to enable those skilled in the art to practice the embodiments and illustrate the best modes of practicing the embodiments. Upon reading the following description in light of the accompanying drawings, those skilled in the art will understand the concepts of the present disclosure and recognize applications of these concepts not specifically addressed herein. It is to be understood that these concepts and applications fall within the scope of the present disclosure.

[0030] Wireless Node: As used herein, a "wireless node" is either a wireless access node or a wireless communication device.

[0031] Radio Access Node: As used herein, a "radio access node" or "radio network node" or "radio access network node" is any node in a radio access network (RAN) of a cellular communications network that operates to transmit and / or receive signals wirelessly. Some examples of radio access nodes include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a 3rd Generation Partnership Project (3GPP) fifth generation (5G) NR network, or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), a high power or macro base station, a low power base station (e.g., a micro base station, a pico base station, a home eNB, etc.), a relay node, a network node implementing part of the functionality of a base station, or a network node implementing a gNB distributed unit (gNB-DU), or a network node implementing part of the functionality of some other type of radio access node.

[0032] Core Network Node: As used herein, a "core network node" is any type of node in a core network or any node that implements a core network function. Some examples of core network nodes include, for example, a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Publication Function (SCEF), a Home Subscriber Server (HSS), etc. Some other examples of core network nodes include nodes that implement an Access and Mobility Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF), a Network Publication Function (NEF), a Network Function (NF) Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), etc.

[0033] Communication Device: As used herein, a "communication device" is any type of device that has access to an access network. Some examples of communication devices include, but are not limited to, a mobile phone, a smartphone, a sensor device, a meter, a vehicle, a household appliance, a medical appliance, a media player, a camera, or any type of consumer electronic device, such as, but not limited to, a television, a radio, a lighting device, a tablet computer, a laptop computer, or a personal computer (PC). A communication device may be a portable, handheld, computer-equipped, or vehicle-mounted mobile device enabled to communicate voice and / or data over a wireless or wired connection.

[0034] Wireless Communication Device: One type of communication device is a wireless communication device, which may be any type of wireless device having access to (i.e., served by) a wireless network (e.g., a cellular network). Some examples of wireless communication devices include, but are not limited to, user equipment devices (UE) in 3GPP networks, machine-type communication (MTC) devices, and Internet of Things (IoT) devices. Such wireless communication devices may be or may be integrated into mobile phones, smartphones, sensor devices, meters, vehicles, household appliances, medical appliances, media players, cameras, or any type of consumer electronics, such as, but not limited to, televisions, radios, lighting devices, tablet computers, laptop computers, or PCs. Wireless communication devices may be portable, handheld, computer-equipped, or vehicle-mounted mobile devices enabled to communicate voice and / or data over a wireless connection.

[0035] Network Node: As used herein, a "network node" is any node that is part of either the RAN or the core network of a cellular communications network / system.

[0036] Transmitting / Receiving Point (TRP): In some embodiments, a TRP can be either a network node, a radio head, a spatial relationship, or a transmission configuration indicator (TCI) state. A TRP can be represented by a spatial relationship or a TCI state in some embodiments. In some embodiments, a TRP may be using multiple TCI states. In some embodiments, a TRP can be part of a gNB that transmits and receives radio signals to / from a UE according to physical layer properties and parameters specific to that element. In some embodiments, in multiple TRP (multi-TRP) operation, a serving cell can schedule a UE from two TRPs to provide better physical downlink shared channel (PDSCH) coverage, reliability, and / or data rates. There are two different operating modes for multi-TRP: single downlink control information (DCI) and multi-DCI. For both modes, control of uplink and downlink operations is done by both the physical layer and the medium access control (MAC). In single DCI mode, the UE is scheduled by the same DCI for both TRPs, and in multi-DCI mode, the UE is scheduled by independent DCI from each TRP.

[0037] In some embodiments, a set of transmission points (TPs) is a set of geographically co-located transmit antennas (e.g., antenna arrays (with one or more antenna elements)) for one cell, part of one cell, or one Positioning Reference Signal (PRS) dedicated TP. The TPs can include base station (eNB) antennas, remote radio heads (RRHs), remote antennas of base stations, antennas of PRS dedicated TPs, etc. One cell can be formed by one or more TPs. In case of homogeneous deployment, each TP can correspond to one cell.

[0038] In some embodiments, a set of TRPs is a set of geographically collocated antennas (e.g., antenna arrays (having one or more antenna elements)) that support TP and / or receiving point (RP) functionality.

[0039] It should be noted that the description provided herein focuses on 3GPP cellular communication systems, and therefore 3GPP terminology or terminology similar to 3GPP terminology is often used, however, the concepts disclosed herein are not limited to 3GPP systems.

[0040] It should be noted that in the description herein, reference may be made to the term "cell." However, it is important to note that, particularly with respect to 5G NR concepts, a beam may be used in place of a cell, and thus the concepts described herein are equally applicable to both cells and beams.

[0041] Currently, several challenges exist. In NR Release 15 and Release 16, the UE determines the physical uplink shared channel (PUSCH) transmit power for each transmission opportunity, which refers to a scheduled uplink (UL) symbol in a slot. A Transport Block of Multiple Slots (TBoMS) in Release 17 has one Transport Block (TBoMS) that spans multiple slots. One issue that needs to be resolved is whether the transmission opportunity for TBoMS is a slot with a TB or multiple slots. This is implicitly related to the question of whether the same or different transmit powers can be used between the multiple slots of TBoMS.

[0042] For example, the per-slot calculation of some power control parameters, such as Bits Per Resource Element (BPRE), is complex for TBoMS. It is complicated for a UE to calculate the number of information bits in a slot for Type-B like TBoMS. Therefore, a calculation across multiple slots and how it applies to the transmission opportunities of one slot is proposed.

[0043] Furthermore, transmit power control (TPC) command determination for TPC accumulation needs to be specially considered, especially when multiple opportunities are configured for a single TBoMS transmission.

[0044] Systems and methods that provide solutions to the above-mentioned or other problems are disclosed herein. Disclosed herein are embodiments of systems and methods related to providing definition of transmission opportunities for TBoMS PUSCH transmissions. Disclosed herein are also embodiments of systems and methods for maintaining the same power for cross-slot channel estimation and determining transmission opportunity related power control parameters for TBoMS PUSCH transmissions.

[0045] Although not limited to or by a particular advantage, embodiments of the present disclosure may provide possible definition of transmission opportunities for uplink power control for transmission of TBoMS and provide solution(s) for how power control related parameters should be applied in each slot of TBoMS.

[0046] In this regard, FIG. 1 illustrates an example of a cellular communication system 100 in which embodiments of the present disclosure may be implemented. In the embodiments described herein, the cellular communication system 100 is a 5G system (5GS) including a Next Generation RAN (NG-RAN) and a 5G Core (5GC), although the embodiments disclosed herein may be used in any type of wireless or cellular communication system that utilizes TBoMS. In this example, the RAN includes base stations 102-1 and 102-2, including NR base stations (gNBs) in 5GS and optionally Next Generation eNBs (ng-eNBs) (e.g., LTE RAN nodes connected to 5GC), which control corresponding (macro) cells 104-1 and 104-2. The base stations 102-1 and 102-2 are generally referred to herein collectively as base stations 102 and individually as base stations 102. Similarly, the (macro) cells 104-1 and 104-2 are generally referred to herein collectively as (macro) cells 104 and individually as (macro) cells 104. The RAN may also include several low power nodes 106-1-106-4 that control corresponding small cells 108-1-108-4. The low power nodes 106-1-106-4 may be small base stations (such as pico or femto base stations) or RRHs, etc. Although not specifically shown, one or more of the small cells 108-1-108-4 may alternatively be provided by the base station 102. The low power nodes 106-1-106-4 are generally referred to herein collectively as low power nodes 106 and individually as low power nodes 106. Similarly, the small cells 108-1-108-4 are generally referred to herein collectively as small cells 108 and individually as small cells 108. The cellular communication system 100 also includes a core network 110, referred to in 5GS as 5GC. The base stations 102 (and optionally the low power nodes 106 ) are connected to a core network 110 .

[0047] The base station 102 and low power node 106 serve wireless communication devices 112-1 through 112-5 in corresponding cells 104 and 108. The wireless communication devices 112-1 through 112-5 are generally referred to herein collectively as wireless communication devices 112 and individually as wireless communication devices 112. In the following description, the wireless communication devices 112 are often UEs and thus may be referred to herein as UEs 112, although the disclosure is not limited thereto.

[0048] As explained in the Background section above, in NR Release 15 / 16, one TB is in a slot, but NR Release 17 will support TB across multiple slots (TBoMS, or multi-slot TB). In 3GPP, two types of TBoMS are considered: TBoMS with time domain resource allocation (TDRA) in each slot as type A, and TBoMS with TDRA in each slot as type B.

[0049] In the present disclosure, embodiments of systems and methods are disclosed that relate to providing definition of transmission opportunities for TBoMS, as well as maintaining the same power for cross-slot channel estimation requiring the same transmit power across multiple slots, and determining transmission opportunity related power control parameters for TBoMS PUSCH transmissions.

[0050] TBoMS PUSCH transmission opportunity provision for TBoMS PUSCH power calculation In NR Release 16, the PUSCH transmit power is determined for each PUSCH transmission opportunity. The PUSCH transmission opportunity i is the slot index within a frame with system frame number SFN. TIFF0007662820000037.tif7170, the first symbol S in the slot, and the number L of consecutive symbols.

[0051] In a first embodiment, the UE 112 calculates a linear TBoMS PUSCH power for each TBoMS PUSCH transmission opportunity, which may be determined based on one or more of the following options: Option 1: In this option, one TBoMS PUSCH transmission opportunity is defined as part of the TBoMS transmission in one slot, and the TBoMS PUSCH transmission opportunity is defined as the slot index within a frame with the system frame number SFN. TIFF0007662820000038.tif7170, the first symbol S in the slot, and the number L of consecutive symbols of TBoMS in the slot. Option 2: In this option, one TBoMS PUSCH transmission opportunity spans multiple consecutive slots of the TBoMS. One transmission opportunity is the index of the first slot of the transmission opportunity with the system frame number SFN. TIFF0007662820000039.tif7170, the first symbol S in the first slot of the transmission opportunity, and the number L of consecutive symbols of TBoMS in this slot, or the total number L of symbols of TBoMS in the transmission opportunity. Option 3: In this option, one PUSCH transmission opportunity spans multiple consecutive or non-consecutive slots of the TBoMS. The transmission opportunity is expressed as the index of the first slot of the transmission opportunity with the system frame number SFN. TIFF0007662820000040.tif7170, the first symbol S in the first slot, and the number L of symbols of the TBoMS either in this slot or across multiple slots of the TBoMS. · Option 4: In this option, every slot for TBoMS transmission is treated as one TBoMS PUSCH transmission opportunity i. · Option 5: In this option, the entire set of slots for TBoMS transmission may be grouped into different subsets, and each subset of slots may be treated as one TBoMS PUSCH transmission opportunity.

[0052] In a sub-embodiment of the first embodiment, when more than one of the options is supported, the UE 112 may be configured with one of the options for determining the provision of the PUSCH transmission opportunity i for the power calculation by a network node (e.g., the base station 102), e.g., via downlink control information (DCI) and / or higher layer signaling. Alternatively, one of the options to be used by the UE 112 for determining the provision of the PUSCH transmission opportunity i for the power calculation may be pre-defined or otherwise predetermined. The above options for the first embodiment allow for multiple slot TBoMS transmission opportunities, except for option 1. The maximum number of slots allowed per TBoMS PUSCH opportunity may depend on whether non-contiguous slots are allowed in some Time Division Duplex (TDD) configurations. If non-contiguous slots are configured for TBoMS, but only consecutive slots are allowed in a transmission opportunity as in Option 2 above, multiple transmission opportunities for TBoMS may be needed. However, allowing non-contiguous slots in one PUSCH opportunity makes it possible to have only one TBoMS PUSCH opportunity when every slot is treated as one TBoMS PUSCH opportunity as described in Option 4. · Figure 2 shows an example where TBoMS spans over four uplink (UL) slots with a set of slots configured with a specific TDD configuration {DDSUUDDSUU}. In this case, if only consecutive slots are allowed for each PUSCH opportunity, each TBoMS PUSCH opportunity {PO1 or PO2} can have up to two slots as shown in Figure 2(a). However, if non-consecutive uplink slots are also allowed for one PUSCH opportunity, one TBoMS PUSCH opportunity PO1 can have up to four slots as shown in Figure 2(b).

[0053] In a second embodiment, if one transmission opportunity for TBoMS spans multiple slots, the UE 112 may: Option 1: Determine a transmit power for the transmit opportunity that is equal to the transmit power determined in the first slot of the transmit opportunity and maintain it until the end of the transmit opportunity; Option 2: Determine the transmit power for multiple slots of transmit opportunity as a whole.

[0054] Option 1 and option 2 of the second embodiment may be equivalent when the power control related parameters in each slot of the set of slots for this TBoMS transmission opportunity are the same. However, when at least one of the parameters (e.g., parameter X) is different for each slot, in one subembodiment of the second embodiment, parameter X may be determined based on one or more of the following methods: Option A: The parameter X in one or more fixed slots of a TBoMS PUSCH opportunity is used to determine the transmit power in a set of slots in this PUSCH opportunity, e.g. the “one or more fixed slots” could be the first one or more slots or the last one or more slots of this TBoMS PUSCH opportunity. Option B: X or the corresponding slot may be configured by the network

[0055] An example is that the UE 112 uses option 1 of the second embodiment for all parameters except the BPRE, which is determined over multiple slots of the TB.

[0056] TBoMS PUSCH Power Control for Cross-Slot Channel Estimation The transmission opportunity is the time domain granularity of the UL power control. If the transmission opportunity is within a slot, the UE 112 can quickly adapt to the power change factor in the next slot. On the other hand, if cross-slot channel estimation is taken into account, the UE 112 will better keep the same transmission power in multiple slots and have a longer transmission opportunity. There are pros and cons to keeping either the same transmission power or different transmission powers across multiple slots of TBoMS.

[0057] The transmission opportunities for TBoMS can be predetermined to reuse the transmission opportunities for single slots TB. In that case, the UE 112 can be configured / predetermined whether different transmit powers are allowed for the transmission of TBoMS. If the TBoMS spans many slots, the base station 102 (e.g., gNB) can configure the number of UE transmit power changes or when the power changes can occur.

[0058] In a third embodiment, the UE 112 may be configured by the network (e.g., by the base station 102) or may be predetermined whether transmit power changes are allowed during a TBoMS transmission. If the UE 112 is configured with TBoMS repetitions, the UE 112 may be configured by the network or may be predetermined whether transmit power changes are allowed between TBoMS repetitions. In either of these two cases, if transmit power changes are allowed, the UE 112 may be configured with the number of power changes during a transmission or when transmit power changes may occur.

[0059] In a sub-embodiment of the third embodiment, the same or different transmit power during the transmission of TBoMS may be interdependent on other features, such as, for example, cross-slot channel estimation. For example, if cross-slot channel estimation is configured for the UE 112, the UE 112 keeps the same transmit power over slots for one or more repeated transmissions of TBoMS for joint channel estimation. If the transmission opportunity is shorter than the transmission duration of TBoMS, the UE 112 determines the UL transmit power multiple times for the transmission of TBoMS. Possible factors that may change the UL transmit power during multiple slots of TB include different data-to-DMRS resource ratios in each slot, group common TPC commands, reference signals, path loss estimation, PUSCH power control adjustment state.

[0060] In a fourth embodiment, when the same transmission power is set / predetermined across multiple slots of TBoMS, the UE 112 determines the transmission power prior to transmission based on the transmission power in the first slot and keeps the same transmission power until the end of the transmission.

[0061] In the fifth embodiment, if the same transmission power is set / predetermined across multiple slots of TBoMS, one or more of the following methods may be used. · The UE 112 does not expect to receive TPC commands for TBoMS transmission during the transmission of TBoMS. If the UE 112 receives a TPC command for TBoMS transmission while transmitting TBoMS, The UE 112 discards the TPC command, or o The UE applies the TPC command in the next transmission after TBoMS, e.g. a TPC accumulation command. The UE 112 does not expect the base station 102 (e.g., gNB) to modify the reference signal and its transmit power that the UE 112 uses to estimate the downlink (DL) path loss during TBoMS transmission. Otherwise, the UE 112 ignores the modification. · The UE 112 does not perform DL path loss measurements from the physical layer during TBoMS transmission. The UE 112 does not expect the PUSCH power control adjustment state to be changed by RRC or DCI signaling during a TBoMS transmission. Otherwise, the UE 112 ignores the change.

[0062] In a sub-embodiment of the fifth embodiment, if the same transmission power is set / predetermined across TBoMS repetitions, the same method may be used across the repetitions.

[0063] Calculation of Transmission Opportunity Related Power Control Parameters for TBoMS In Release 16, one transmission opportunity i is in a slot and some parameters are determined for each slot. If the definition of the transmission opportunity is to be reused for TBoMS, some parameters may be determined over multiple slots.

[0064] One parameter related to the transmission opportunity is the modulation and coding scheme (MCS) related parameter Δ TF,b,f,c (i). In Release 16, as captured in the following excerpt, Δ TF,b,f,c For the calculation of (i), bits per resource element (BPRE) is the number of bits transmitted by one resource element (RE) and is calculated per slot. In an alternative method, the existing definition of transmission opportunities is reused for TBoMS, but BPRE is calculated once over the transmission opportunities of TBoMS, and Δ TF,b,f,c This may be applicable to (i). *****BEGIN EXCERPT***** TIFF0007662820000041.tif8170, - For PUSCH with UL-SCH data TIFF0007662820000042.tif8170, and CSI transmission on PUSCH without UL-SCH data TIFF0007662820000043.tif7170, where: - C is the number of code blocks to be transmitted, and K r is the size of the code block r, and N RE teeth, The number of resource elements determined as TIFF0007662820000044.tif14170, where: TIFF0007662820000045.tif7170 is the number of symbols for PUSCH transmission opportunity i on active UL BWP b of carrier f of serving cell c, TIFF0007662820000046.tif7170 is the number of subcarriers in PUSCH symbol j, excluding DM-RS subcarriers and phase tracking RS samples [TS38.211], and assuming no segmentation for nominal repetition when the PUSCH transmission has repetition type B; TIFF0007662820000047.tif7170, C, K r is specified in [TS38.212] *****END EXCERPT*****

[0065] In a sixth embodiment, the BPRE for a multi-slot PUSCH with UL-SCH data may be calculated over multiple slots of a TB in one or more of the following ways, where the bold underlined text indicates the required modifications to the Rel-16 BPRE calculation in 3GPP TS38.213 rev.16.4.0 section 7.1.1: - C is the number of code blocks transmitted across multiple slots of TBoMS. If there is no code block (CB) segmentation for TBoMS, then C=1. -K r is the size for code block r across multiple slots of TBoMS. TIFF0007662820000048.tif8170 is the TBS of TBoMS. - Option 1, TIFF0007662820000049.tif8170, where: ○ N RE teeth, TIFF0007662820000050.tif12170, where N is the total number of transmission opportunities for TBoMS; TIFF0007662820000051.tif7170 is the number of symbols for PUSCH transmission opportunity i on active UL bandwidth portion (BWP) b of carrier f of serving cell c, TIFF0007662820000052.tif7170 is the number of subcarriers in PUSCH symbol j excluding the demodulation reference signal (DM-RS) subcarriers and phase tracking RS samples [TS38.211], TIFF0007662820000053.tif7170, - Option 2, TIFF0007662820000054.tif9170, where: ○ N RE teeth, The number of resource elements determined as TIFF0007662820000055.tif12170, where i=0, TIFF0007662820000056.tif7170 is the number of symbols for the first transmission opportunity of TBoMS on active UL BWP b of carrier f of serving cell c, TIFF0007662820000057.tif6170 is the number of subcarriers in PUSCH symbol j, excluding DM-RS subcarriers and phase tracking RS samples [TS38.211], and assuming no segmentation for nominal repetition when the PUSCH transmission has repetition type B; TIFF0007662820000058.tif7170, ○ N is the total number of TBoMS transmission opportunities

[0066] In a sub-embodiment of the sixth embodiment, TIFF0007662820000059.tif8170. Δ TF,b,f,c is the same for all transmission opportunities of the TBoMS.

[0067] BPRE calculation over multiple slots instead of one slot can save the UE effort of calculating the number of information bits in each slot. The transport block size (TBS) over all slots of the TBoMS is much easier to obtain. In option 2 of the sixth embodiment, the UE 112 calculates N RE This is done by simply calculating the same N RE Option 1 of the sixth embodiment may be considered for Type-B like TBoMS.

[0068] Another parameter is the PUSCH power control adjustment state f for the active UL BWP b of carrier f of serving cell c at PUSCH transmission opportunity i. b,f,c (i,l), which is determined in Rel-16 according to the following excerpt from 3GPP TS38.213 rev.16.4.0 section 7.1.1: *****Start excerpt from 3GPP TS38.213***** PUSCH power control adjustment state f for active UL BWP b of carrier f of serving cell c at PUSCH transmission opportunity i b,f,c Regarding (i,l) - δ PUSCH,b,f,c(i,l) is the TPC command value that is included in the DCI format to schedule PUSCH transmission opportunity i on active UL BWP b of carrier f of serving cell c, or is jointly coded with other TPC commands in DCI format 2_2 with CRC scrambled by the TPC-PUSCH-RNTI, as described in clause 11.3. l ∈ {0,1} if twoPUSCH-PC-AdjustmentStates is configured in the UE, and l = 0 if twoPUSCH-PC-AdjustmentStates is not configured in the UE or if PUSCH transmission is scheduled by a RAR UL grant as described in clause 8.3. For PUSCH (re)transmissions configured by ConfiguredGrantConfig, the value of l ∈ {0,1} is provided to the UE by powerControlLoopToUse If the UE is provided with SRI-PUSCH-PowerControl, the UE obtains a mapping between a set of values ​​for the SRI field in the DCI format for scheduling PUSCH transmissions and the l value(s) provided by sri-PUSCH-ClosedLoopIndex and determines the l value to be mapped to the SRI field value. - l=0 if the PUSCH transmission is scheduled by a DCI format that does not contain an SRI field or if SRI-PUSCH-PowerControl is not provided to the UE. - if the UE obtains one TPC command from DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI, the l value is provided by the closed-loop indicator field in DCI format 2_2; - TIFF0007662820000060.tif11170 is the PUSCH power control adjustment state l for active UL BWP b and PUSCH transmission opportunity i of carrier f of serving cell c when the UE is not provided with tpc-Accumulation, where: - δ PUSCH,b,f,c The values ​​are given in Table 7.1.1-1 - TIFF0007662820000061.tif10170 represents the PUSCH transmission opportunity ii on the active UL BWP b of carrier f of serving cell c for PUSCH power control adjustment state l. 0 K before PUSCH (ii 0 )-1 symbols before PUSCH transmission opportunity i PUSCH (i) symbols received by the UE between i ) a set of TPC command values ​​D i where i 0 >0 is PUSCH transmission opportunity ii 0 K before PUSCH (ii 0 ) symbols before PUSCH transmission opportunity i PUSCH (i) is the smallest integer that is faster than symbols - K if PUSCH transmission is scheduled by the DCI format PUSCH (i) is the number of symbols for an active UL BWP b of carrier f of serving cell c after the last symbol of the corresponding PDCCH reception and before the first symbol of the PUSCH transmission - K if PUSCH transmission is configured by ConfiguredGrantConfig PUSCH (i) is the number of symbols per slot for the active UL BWP b of carrier f of serving cell c K, which is equal to the product of TIFF0007662820000062.tif7170 and the minimum of the value provided by k2 in PUSCH-ConfigCommon PUSCH,minis the number of symbols - UE receives PUSCH transmission opportunity ii 0 the maximum power for the active UL BWP b of carrier f of serving cell c is reached at If TIFF0007662820000063.tif10170, then b,f,c (i,l)=f b,f,c (ii 0 ,l) - UE receives PUSCH transmission opportunity ii 0 a minimum power is reached for the active UL BWP b of carrier f of serving cell c at If TIFF0007662820000064.tif11170, then b,f,c (i,l)=f b,f,c (ii 0 ,l) The UE calculates an accumulation of PUSCH power control adjustment states l for an active UL BWP b of a carrier f of a serving cell c as f b,f,c Reset (k,l)=0, k=0,1,...,i - Corresponding P O_UE_PUSCH,b,f,c (j) if configuration for the value is provided by a higher layer, - the corresponding alpha b,f,c (j) if configuration for the value is provided by a higher layer, Here, l is - if j>1 and the UE is provided with an upper SRI-PUSCH-PowerControl, l is the sri-PUSCH-ClosedLoopIndex value(s) configured in any SRI-PUSCH-PowerControl with sri-P0-PUSCH-AlphaSetId value corresponding to j - l=0 if j>1 and the UE is not provided with SRI-PUSCH-PowerControl or j=0. - if j=1, l is given by the value of powerControlLoopToUse is determined from the value of j as -f b,f,c(i,l)=δ PUSCH,b,f,c (i,l) is the PUSCH power control adjustment state for active UL BWP b of carrier f of serving cell c and PUSCH transmission opportunity i when the UE is provided with tpc-Accumulation, where: - δ PUSCH,b,f,c Absolute values ​​are given in Table 7.1.1-1 Table 7.1.1-1: Absolute and cumulative δ of the TPC command field in DCI formats scheduling PUSCH transmissions or in DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI or in DCI format 2_3 PUSCH,b,f,c value or δ SRS,b,f,c Mapping to Values TIFF0007662820000065.tif32170*****END EXCERPT FROM 3GPP TS38.213*****

[0069] In a seventh embodiment, when UE 112 is provided with tpc-Accumulation, i.e., when TPC accumulation is disabled, an absolute power offset value will be used for power adjustment, and one or more of the following rules may be applied to determine the power adjustment for TBoMS in each slot. Absolute power offset is ○ Start of the first slot for TBoMS transmission ○ Or the start of the first scheduled symbol of the first slot for TBoMS transmission ○ Or the start of a set of symbols / slots before the first slot for TBoMS transmission Determined by the most recent TPC command received before The absolute power offset for the power calculation for a transmission in a TBoMS PUSCH opportunity (when multiple TBoMS PUSCH opportunities are used for the power calculation for one TBoMS transmission) is ○ Start of the first slot of a TBoMS PUSCH opportunity for TBoMS transmission ○ Or the start of the first symbol of the first slot of a TBoMS PUSCH opportunity for TBoMS transmission ○ Or the start of the set of symbols / slots before the first slot of a TBoMS PUSCH opportunity for TBoMS transmission Determined by the most recent TPC command received before

[0070] In an eighth embodiment, when the UE 112 is not provided with tpc-Accumulation, i.e., when TPC accumulation is enabled, the accumulated power offset will be used for power adjustment, and one or more of the following rules may be applied to determine the power adjustment for TBoMS in each slot, where the bold underlined text refers to the Rel-16 K in 3GPP TS38.213 rev.16.4.0 section 7.1.1: PUSCH Indicate changes to a calculation. The accumulated power offset is calculated for PUSCH transmission opportunities ii on the active UL BWP b of carrier f of serving cell c for PUSCH power control adjustment state l. 0 K before PUSCH (ii 0 )-1 symbols before PUSCH transmission opportunity i PUSCH (i) is determined by a set of TPC commands received between symbols i 0 >0 is PUSCH transmission opportunity ii 0 K before PUSCH (ii 0 ) symbols before PUSCH transmission opportunity i PUSCH (i) is the smallest integer that is faster than symbols - K if PUSCH transmission is scheduled by the DCI format PUSCH (i) is the number of symbols for an active UL BWP b of carrier f of serving cell c after the last symbol of the corresponding PDCCH reception and before the first symbol of the first slot of the TBoMS transmission - K if PUSCH transmission is configured by ConfiguredGrantConfig PUSCH (i) is the number of symbols per slot for the active UL BWP b of carrier f of serving cell c K, which is equal to the product of TIFF0007662820000066.tif7170 and the minimum of the value provided by k2 in PUSCH-ConfigCommon PUSCH,min is the number of symbols The accumulated power offset (when multiple TBoMS PUSCH opportunities are used for power calculation for one TBoMS transmission) is calculated for PUSCH transmission opportunity ii on the active UL BWP b of carrier f of serving cell c for PUSCH power control adjustment state l. 0 K before PUSCH (ii 0 )-1 symbols before PUSCH transmission opportunity i PUSCH (i) is determined by a set of TPC commands received between symbols i 0 >0 is PUSCH transmission opportunity ii 0 K before PUSCH (ii 0 ) symbols before PUSCH transmission opportunity i PUSCH (i) is the smallest integer that is faster than symbols - K if PUSCH transmission is scheduled by the DCI format PUSCH (i) is the number of symbols for the active UL BWP b of carrier f of serving cell c after the last symbol of the corresponding PDCCH reception and before the first symbol of the first slot of the current PUSCH opportunity i of the TBoMS transmission - K if PUSCH transmission is configured by ConfiguredGrantConfig PUSCH (i) is the number of symbols per slot for the active UL BWP b of carrier f of serving cell c K, which is equal to the product of TIFF0007662820000067.tif7170 and the minimum of the value provided by k2 in PUSCH-ConfigCommon PUSCH,min is the number of symbols

[0071] Additional explanation 3 is a flow chart illustrating the operation of a wireless communication device 112 (e.g., a UE) according to at least some of the embodiments described above. As shown, the wireless communication device 112 determines a transmit power for a TBoMS uplink transmission for each TBoMS transmission opportunity (step 300). The transmit power may be determined using any of the first, second, third, fourth, fifth, sixth, seventh, and / or eighth embodiments and / or any of their sub-embodiments. Details of these embodiments and their sub-embodiments have been described above and therefore will not be repeated here. However, it should be understood that all of the details provided above are equally applicable here to step 300. The wireless communication device 112 then transmits a TBoMS uplink transmission according to the determined transmit power for a TBoMS uplink transmission for each TBoMS transmission opportunity (step 302).

[0072] 4 is a schematic block diagram of a network node 400 according to some embodiments of the disclosure. Optional features are represented by dotted boxes. The network node 400 may be, for example, a base station 102 or 106, or a network node implementing all or a portion of the functionality of a base station 102 or a gNB described herein. As shown, the network node 400 includes a control system 402 including one or more processors 404 (e.g., a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), etc.), a memory 406, and a network interface 408. The one or more processors 404 are also referred to herein as processing circuits. Additionally, if the network node 400 is a radio access node (e.g., a base station 102, a gNB, or a network node implementing at least a portion of the functionality of a base station 102 or a gNB), the network node 400 may include one or more radio units 410, each including one or more transmitters 412 and one or more receivers 414 coupled to one or more antennas 416. The radio units 410 may be referred to as or part of a radio interface circuit. In some embodiments, the radio unit(s) 410 are external to the control system 402 and are connected to the control system 402, for example, via a wired connection (e.g., an optical cable). However, in some other embodiments, the radio unit(s) 410 and potentially the antenna(s) 416 are integrated with the control system 402. The one or more processors 404 operate to provide one or more functions of the network node 400 described herein (e.g., one or more functions of the base station 102 or a gNB described herein). In some embodiments, the function(s) are implemented in software, for example, stored in memory 406 and executed by one or more processors 404.

[0073] FIG. 5 is a schematic block diagram illustrating a virtualized embodiment of a network node 400 according to some embodiments of the disclosure. Again, optional features are represented by dashed boxes. As used herein, a "virtualized" network node is an implementation of a network node 400 in which at least a portion of the functionality of the network node 400 is implemented as virtual component(s) (e.g., via virtual machine(s) executing on physical processing node(s) in the network(s)). As shown, in this example, if the network node 400 is a radio access node, the network node 400 may include a control system 402 and / or one or more radio units 410, as described above. The control system 402 may be connected to the radio unit(s) 410, e.g., via an optical cable or the like. The network node 400 includes one or more processing nodes 500 coupled to or included as part of the network(s) 502. If present, the control system 402 or wireless unit(s) is connected to processing node(s) 500 via a network 502. Each processing node 500 includes one or more processors 504 (e.g., CPU, ASIC, FPGA, etc.), memory 506, and a network interface 508.

[0074] In this example, the functions 510 of the network node 400 described herein (e.g., one or more functions of a base station 102 or gNB described herein) are implemented in one or more processing nodes 500 or distributed in any desired manner across one or more processing nodes 500 and the control system 402 and / or radio unit(s) 410. In some particular embodiments, some or all of the functions 510 of the network node 400 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s) 500. As will be appreciated by those skilled in the art, additional signaling or communication between the processing node(s) 500 and the control system 402 is used to perform at least some of the desired functions 510. Notably, in some embodiments, the control system 402 may not be included, in which case the radio unit(s) 410 communicate directly with the processing node(s) 500 via an appropriate network interface(s).

[0075] In some embodiments, a computer program is provided that includes instructions that, when executed by at least one processor, cause the at least one processor to perform functions of the network node 400 or a node (e.g., processing node 500) implementing one or more of the functions 510 of the network node 400 in a virtual environment in accordance with any of the embodiments described herein. In some embodiments, a carrier is provided that comprises the computer program product described above. The carrier is one of an electronic signal, an optical signal, a wireless signal, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium such as a memory).

[0076] 6 is a schematic block diagram of a network node 400 in accordance with some other embodiments of the disclosure. The network node 400 includes one or more modules 600, each of which is implemented in software. The module(s) 600 provide the functionality of the network node 400 described herein. This description is equally applicable to the processing node 500 of FIG. 5, where the module 600 may be implemented in one of the processing nodes 500 or distributed across multiple processing nodes 500 and / or distributed across the processing node(s) 500 and the control system 402.

[0077] 7 is a schematic block diagram of a wireless communication device 112 (e.g., a UE) according to some embodiments of the present disclosure. As shown, the wireless communication device 112 includes one or more processors 702 (e.g., a CPU, an ASIC, an FPGA, etc.), a memory 704, and one or more transceivers 706, each including one or more transmitters 708 and one or more receivers 710 coupled to one or more antennas 712. The transceiver(s) 706 includes a radio front-end circuit connected to the antenna(s) 712 configured to condition signals communicated between the antenna(s) 712 and the processor(s) 702, as will be appreciated by those skilled in the art. The processor 702 is also referred to herein as a processing circuit. The transceiver 706 is also referred to herein as a radio circuit. In some embodiments, the functionality of the wireless communication device 112 (or UE) described above may be fully or partially implemented in software, for example, stored in the memory 704 and executed by the processor(s) 702. It should be noted that the wireless communication device 112 may include additional components not shown in FIG. 7 , such as, for example, one or more user interface components (e.g., input / output interfaces including a display, buttons, a touch screen, a microphone, speaker(s), etc., and / or any other components for enabling input of information into and / or output of information from the wireless communication device 112), a power supply (e.g., a battery and associated power circuitry), etc.

[0078] In some embodiments, a computer program is provided that includes instructions that, when executed by at least one processor, cause the at least one processor to perform the functions of the wireless communication device 112 in accordance with any of the embodiments described herein. In some embodiments, a carrier is provided that comprises the computer program product described above. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium such as a memory).

[0079] 8 is a schematic block diagram of a wireless communication device 112 according to some other embodiments of the present disclosure. The wireless communication device 112 includes one or more modules 800, each of which is implemented in software. The module(s) 800 provide the functionality of the wireless communication device 112 (or UE) described herein.

[0080] Referring to FIG. 9, according to one embodiment, a communication system includes a communication network 900, such as a 3GPP type cellular network, comprising an access network 902, such as a RAN, and a core network 904. The access network 902 comprises a number of base stations 906A, 906B, 906C, such as Node Bs, eNBs, gNBs, or other types of wireless access points (APs), each defining a corresponding coverage area 908A, 908B, 908C. Each base station 906A, 906B, 906C can be connected to the core network 904 via a wired or wireless connection 910. A first UE 912 located in the coverage area 908C is configured to wirelessly connect to or be paged by the corresponding base station 906C. A second UE 914 in the coverage area 908A can be wirelessly connected to the corresponding base station 906A. Although multiple UEs 912, 914 are shown in this example, the disclosed embodiments are equally applicable to situations where only one UE is in a coverage area or where only one UE is connected to a corresponding base station 906.

[0081] The communication network 900 is itself connected to a host computer 916, which may be embodied in hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer 916 may be owned or under the control of a service provider, or may be operated by or on behalf of the service provider. Connections 918 and 920 between the communication network 900 and the host computer 916 may extend directly from the core network 904 to the host computer 916 or may proceed through an optional intermediate network 922. The intermediate network 922 may be one of a public network, a private network, or a hosted network, or a combination of two or more of them, and the intermediate network 922 may be a backbone network or the Internet, if any, and in particular the intermediate network 922 may comprise two or more sub-networks (not shown).

[0082] The communication system of FIG. 9 as a whole enables connectivity between connected UEs 912, 914 and a host computer 916. The connectivity may be described as an over-the-top (OTT) connection 924. The host computer 916 and connected UEs 912, 914 are configured to communicate data and / or signaling via the OTT connection 924 using the access network 902, the core network 904, any intermediate networks 922, and possible further infrastructure (not shown) as intermediaries. The OTT connection 924 may be transparent in the sense that the participating communication devices through which the OTT connection 924 passes are unaware of the routing of the uplink and downlink communications. For example, the base station 906 may not be or need not be informed of the past routing of incoming downlink communications involving data originating from the host computer 916 to be forwarded (e.g., handed over) to the connected UE 912. Similarly, the base station 906 does not need to be aware of the future routing of outgoing uplink communications originating from the UE 912 and destined for the host computer 916 .

[0083] Next, an exemplary implementation of the UE, base station, and host computer described in the previous paragraph according to an embodiment will be described with reference to FIG. 10. In the communication system 1000, the host computer 1002 comprises hardware 1004 including a communication interface 1006 configured to set up and maintain wired or wireless connections with interfaces of different communication devices of the communication system 1000. The host computer 1002 further comprises a processing circuit 1008, which may have storage and / or processing capabilities. In particular, the processing circuit 1008 may comprise one or more programmable processors, ASICs, FPGAs, or combinations thereof (not shown) adapted to execute instructions. The host computer 1002 further comprises software 1010, which is stored in or accessible by the host computer 1002 and executable by the processing circuit 1008. The software 1010 includes a host application 1012. The host application 1012 may be operable to provide services to a remote user, such as the UE 1014 connecting via an OTT connection 1016 that terminates at the UE 1014 and the host computer 1002. In providing services to the remote user, the host application 1012 may provide user data that is transmitted using the OTT connection 1016.

[0084] The communication system 1000 further includes a base station 1018 provided in the communication system, the base station 1018 comprising hardware 1020 enabling the base station 1018 to communicate with the host computer 1002 and the UE 1014. The hardware 1020 may include a communication interface 1022 for setting up and maintaining wired or wireless connections with interfaces of different communication devices of the communication system 1000, as well as a wireless interface 1024 for setting up and maintaining at least a wireless connection 1026 with a UE 1014 located in a coverage area (not shown in FIG. 10) served by the base station 1018. The communication interface 1022 may be configured to facilitate a connection 1028 to the host computer 1002. The connection 1028 may be direct, or the connection 1028 may pass through a core network (not shown in FIG. 10) of the communication system and / or one or more intermediate networks outside the communication system. In the illustrated embodiment, the hardware 1020 of the base station 1018 further includes processing circuitry 1030, which may comprise one or more programmable processors, ASICs, FPGAs, or combinations thereof (not shown) adapted to execute instructions. The base station 1018 further has software 1032 stored internally or accessible via an external connection.

[0085] The communication system 1000 further includes the UE 1014 already mentioned. The hardware 1034 of the UE 1014 may include a wireless interface 1036 configured to set up and maintain a wireless connection 1026 with a base station serving a coverage area in which the UE 1014 is currently located. The hardware 1034 of the UE 1014 further includes a processing circuit 1038, which may comprise one or more programmable processors, ASICs, FPGAs, or combinations thereof (not shown) adapted to execute instructions. The UE 1014 further includes software 1040 stored in or accessible by the UE 1014 and executable by the processing circuit 1038. The software 1040 includes a client application 1042. The client application 1042, with the support of the host computer 1002, may be operable to provide services to a human or non-human user via the UE 1014. At the host computer 1002, a running host application 1012 may communicate with a running client application 1042 via an OTT connection 1016 that terminates at the UE 1014 and the host computer 1002. In providing services to a user, the client application 1042 may receive request data from the host application 1012 and provide user data in response to the request data. The OTT connection 1016 may transfer both the request data and the user data. The client application 1042 may interact with the user to generate the user data that the client application 1042 provides.

[0086] It should be noted that the host computer 1002, base station 1018, and UE 1014 shown in Figure 10 may be similar or equivalent to the host computer 916, one of the base stations 906A, 906B, 906C, and one of the UEs 912, 914, respectively, of Figure 9. That is, the inner workings of these entities may be as shown in Figure 10, and separately, the surrounding network topology may be that of Figure 9.

[0087] 10, the OTT connection 1016 is depicted abstractly to show communication between the host computer 1002 and the UE 1014 via the base station 1018, without explicit reference to intermediary devices and the exact routing of messages through these devices. The network infrastructure may determine the routing, which may be configured to be hidden from the UE 1014 or from the service provider operating the host computer 1002, or both. While the OTT connection 1016 is active, the network infrastructure may also make decisions to dynamically change the routing (e.g., based on load balancing considerations or reconfiguration of the network).

[0088] The wireless connection 1026 between the UE 1014 and the base station 1018 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT service provided to the UE 1014 using the OTT connection 1016 of which the wireless connection 1026 forms the final segment.

[0089] Measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors that one or more embodiments improve upon. There may further be an optional network function for reconfiguring the OTT connection 1016 between the host computer 1002 and the UE 1014 in response to fluctuations in the measurement results. The measurement procedures and / or the network function for reconfiguring the OTT connection 1016 may be implemented in the software 1010 and hardware 1004 of the host computer 1002 or in the software 1040 and hardware 1034 of the UE 1014, or both. In some embodiments, sensors (not shown) may be deployed in or in association with the communication devices through which the OTT connection 1016 passes, and the sensors may participate in the measurement procedures by providing values ​​of the monitored quantities exemplified above, or other physical quantities from which the software 1010, 1040 may calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 1016 may include message formats, retransmission settings, preferred routing, etc., and the reconfiguration need not affect the base station 1018, and the reconfiguration may be unknown or imperceptible to the base station 1018. Such procedures and functions may be known and practiced in the art. In some embodiments, the measurements may involve proprietary UE signaling that facilitates the host computer 1002 measurements of throughput, propagation time, latency, etc. The measurements may be implemented in that the software 1010 and 1040 cause the software 1010 and 1040 to send messages, particularly empty or "dummy" messages, using the OTT connection 1016 while the software 1010 and 1040 monitors propagation times, errors, etc.

[0090] FIG. 11 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 9 and FIG. 10. For simplicity of the disclosure, only drawing references to FIG. 11 are included in this section. In step 1100, the host computer provides user data. In sub-step 1102 (which may be optional) of step 1100, the host computer provides the user data by executing a host application. In step 1104, the host computer initiates a transmission carrying the user data to the UE. In step 1106 (which may be optional), the base station transmits the user data carried in the host computer initiated transmission to the UE, according to the teachings of the embodiments described throughout this disclosure. In step 1108 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0091] FIG. 12 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 9 and FIG. 10. For simplicity of the disclosure, only drawing references to FIG. 12 are included in this section. In step 1200 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In step 1202, the host computer initiates a transmission carrying the user data to the UE. The transmission may proceed via the base station according to the teachings of the embodiments described throughout this disclosure. In step 1204 (which may be optional), the UE receives the user data carried in the transmission.

[0092] FIG. 13 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 9 and FIG. 10. For simplicity of the disclosure, only drawing references to FIG. 13 are included in this section. In step 1300 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1302, the UE provides user data. In sub-step 1304 (which may be optional) of step 1300, the UE provides the user data by executing a client application. In sub-step 1306 (which may be optional) of step 1302, the UE executes a client application that provides the user data in response to the received input data provided by the host computer. In providing the user data, the executed client application may further take into account user input received from the user. Regardless of the particular manner in which the user data is provided, the UE initiates transmission of the user data to the host computer in sub-step 1308 (which may be optional). In method step 1310, the host computer receives user data transmitted from the UE according to the teachings of the embodiments described throughout this disclosure.

[0093] FIG. 14 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 9 and FIG. 10. For simplicity of the disclosure, only drawing references to FIG. 14 are included in this section. In step 1400 (which may be optional), the base station receives user data from the UE, according to the teachings of the embodiments described throughout this disclosure. In step 1402 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 1404 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0094] Any suitable steps, methods, features, functions, or benefits disclosed herein may be implemented through one or more functional units or modules of one or more virtual devices. Each virtual device may comprise several of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), dedicated digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, and the like. The program code stored in memory includes program instructions for implementing one or more communication and / or data communication protocols, as well as instructions for performing one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause each functional unit to perform a corresponding function according to one or more embodiments of the present disclosure.

[0095] Although the processes in the figures may indicate a particular order of operations performed by some embodiments of the present disclosure, it should be understood that such orders are exemplary (e.g., alternative embodiments may perform operations in a different order, combine some operations, overlap some operations, etc.).

[0096] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure, and all such improvements and modifications are considered within the scope of the concepts disclosed herein.

Claims

1. A method implemented by a wireless communication device (112), the method comprising: determining (300) a transmit power for a transport block (TBoMS) uplink transmission per TBoMS transmission opportunity across a number of slots; Transmitting the TBoMS uplink transmission according to the transmit power (302); Including, the transmission power is a linear transmission power, A TBoMS transmission opportunity of the TBoMS uplink transmission is defined as a portion of the TBoMS uplink transmission in one slot, the TBoMS transmission opportunity being defined as a slot index within a frame having a system frame number SFN. a first symbol S in the slot, and a number L of consecutive symbols of the TBoMS uplink transmission in the slot; determining (300) the transmit power for the TBoMS uplink transmission for each TBoMS transmission opportunity includes calculating one or more TBoMS transmission opportunity related parameters; the one or more TBoMS transmission opportunity related parameters include a BPRE; The BPRE is a BRE for a multi-slot PUSCH with UL-SCH, calculated over the multiple slots of the TBoMS as Where: - N RE is where i=0 and is the number of symbols for the first transmission opportunity of the TBoMS on the active UL BWP b of carrier f of serving cell c, is the number of subcarriers, excluding DM-RS subcarriers and phase tracking RS samples [TS38.211] in PUSCH symbol j, and assuming no segmentation for nominal repetition when the PUSCH transmission has repetition type B; and K r is the size for code block r across the slots of the TBoMS; C is the number of code blocks transmitted across the slots of the TBoMS; is the bandwidth of the resource allocation expressed as the number of resource blocks for a PUSCH transmission opportunity i on the active UL BWP b of carrier f of serving cell c; is the total number of transmission opportunities for the TBoMS.

2. 2. The method of claim 1, wherein the TBoMS uplink transmission is a TBoMS Physical Uplink Shared Channel (PUSCH) transmission.

3. 2. The method of claim 1, wherein the wireless communication device (112) supports two or more options for how a TBoMS transmission opportunity is defined, and one of the two or more options used by the wireless communication device (112) when determining (300) the transmit power for the TBoMS uplink transmission for each TBoMS transmission opportunity is either configured or predetermined by a network node.

4. 2. The method of claim 1, wherein whether or not a change in transmission power is allowed during the TBoMS uplink transmission is either configured or predetermined by a network node.

5. 2. The method of claim 1, wherein whether or not a change in transmission power is allowed between repetitions of the TBoMS uplink transmission is either configured or predetermined by a network node.

6. The method of claim 4 , wherein the transmit power is interdependent on one or more other characteristics.

7. The method of claim 6 , wherein the transmit power is interdependent on a cross-slot channel estimate.

8. The method of claim 4 , wherein the transmit power is varied between TBoMS transmission opportunities for the TBoMS uplink transmission based on one or more parameters.

9. 9. The method of claim 8, wherein the one or more parameters include: (a) a data to demodulation reference signal (DMRS) ratio in each slot; (b) a group-common transmit power control (TPC) command; (c) a reference signal; (d) a path loss estimate; (e) a PUSCH power control adjustment state; or (f) any combination of two or more of (a)-(e).

10. 2. The method of claim 1, wherein the same transmit power is set or predetermined across the multiple slots of the TBoMS uplink transmission, and the wireless communication device (112) determines the transmit power prior to transmission based on a transmit power in a first slot and keeps the transmit power the same until the end of the TBoMS uplink transmission.

11. the wireless communication device (112) does not expect to receive a TPC command for the TBoMS uplink transmission during the TBoMS uplink transmission; and / or if the wireless communication device (112) receives a TPC command for the TBoMS uplink transmission during the TBoMS uplink transmission; the wireless communication device (112) discards the TPC command, or the wireless communication device (112) applies the TPC command in a next transmission after the TBoMS uplink transmission; and / or the wireless communication device (112) does not expect that the respective base station (102) will modify the reference signal and its transmit power that the wireless communication device (112) uses to estimate downlink path loss during the TBoMS uplink transmission; and / or the wireless communication device (112) does not perform downlink path loss measurements from a physical layer during the TBoMS uplink transmission; and / or the wireless communication device (112) does not expect the PUSCH power control adjustment state / to be changed by RRC or DCI signaling during the TBoMS uplink transmission; The method of claim 10.

12. The one or more TBoMS transmission opportunity related parameters are: (I) an MCS related parameter Δ ＴＦ，ｂ，ｆ，ｃ (i), (II) PUSCH power control adjustment state f for active UL BWP b of carrier f of serving cell c at PUSCH transmission opportunity i ｂ，ｆ，ｃ The method of claim 1 further comprising (i, l), or (III) a combination of (I)-(II).

13. 2. The method of claim 1, wherein TPC accumulation is disabled and an absolute power offset value is used for power adjustments, and determining (300) the transmit power for the TBoMS uplink transmission per TBoMS transmit opportunity includes determining an absolute power adjustment in each slot of the TBoMS uplink transmission.

14. The absolute power adjustment comprises: the start of the first slot for said TBoMS uplink transmission, or the start of a first scheduled symbol of the first slot for the TBoMS uplink transmission; or the start of a set of symbols or slots before the first slot for the TBoMS uplink transmission 14. The method of claim 13, wherein the TPC command is determined by the most recent TPC command received before .

15. A plurality of TBoMS transmission opportunities are used for power calculations for the TBoMS uplink transmissions, and the absolute power adjustment for determining the transmit power in one TBoMS transmission opportunity comprises: the start of the first slot of the TBoMS transmission opportunity; or the start of the first symbol of the first slot of the TBoMS transmission opportunity; or the start of a set of symbols or slots prior to the first slot of the TBoMS transmission opportunity 14. The method of claim 13, wherein the TPC command is determined by the most recent TPC command received before .

16. determining (300) the transmit power for the TBoMS uplink transmission for each TBoMS transmission opportunity, with TPC accumulation enabled and an accumulated power offset value being used for power adjustment; 2. The method of claim 1, comprising determining a cumulative power adjustment in each slot of the TBoMS uplink transmission.

17. The method further comprises: determining 300 the transmit power for the TBoMS uplink transmission per TBoMS transmission opportunity, with TPC accumulation enabled and an accumulated power offset value being used for power adjustment, for TBoMS transmission opportunities i-i on an active uplink bandwidth portion b of carrier f of serving cell c for PUSCH power control adjustment state l; ０ K before ＰＵＳＣＨ (i-i ０ ) −1 symbol and K ＰＵＳＣＨ (i) symbols, and determining a cumulative power adjustment in a TBoMS transmit opportunity for the TBoMS uplink transmission based on a set of TPC commands received between the i ０ >0 is PUSCH transmission opportunity i-i ０ K before ＰＵＳＣＨ (i-i ０ ) symbols before PUSCH transmission opportunity i ＰＵＳＣＨ 2. The method of claim 1, wherein the first bit is the smallest integer number that is earlier than (i) symbols.

18. When PUSCH transmission is scheduled by a downlink control information (DCI) format, K ＰＵＳＣＨ 18. The method of claim 17, wherein (i) is the number of symbols for the active uplink bandwidth portion b of carrier f of serving cell c after the last symbol of a corresponding physical downlink control channel (PDCCH) reception and before the first symbol of the first slot of a current PUSCH opportunity i of a TBoMS transmission.

19. The power control adjustment state l is a state where a TBoMS transmission opportunity is determined based on an active uplink bandwidth portion b of a carrier f of a serving cell c for a PUSCH transmission opportunity i-i, where TPC accumulation is enabled, an accumulated power offset value is used for power adjustment, and multiple TBoMS transmission opportunities are used for power calculation for one TBoMS transmission, and the transmit power for the TBoMS uplink transmission for each TBoMS transmission opportunity is determined based on an active uplink bandwidth portion b of a carrier f of a serving cell c for a PUSCH power control adjustment state l. ０ K before ＰＵＳＣＨ (i-i ０ ) −1 symbol and K ＰＵＳＣＨ (i) symbols, and determining a cumulative power adjustment in a TBoMS transmit opportunity for the TBoMS uplink transmission based on a set of TPC commands received between the i ０ >0 is PUSCH transmission opportunity i-i ０ K before ＰＵＳＣＨ (i-i ０ ) symbols before PUSCH transmission opportunity i ＰＵＳＣＨ 2. The method of claim 1, wherein the first bit is the smallest integer number that is earlier than (i) symbols.

20. When PUSCH transmission is scheduled by a downlink control information (DCI) format, K ＰＵＳＣＨ 20. The method of claim 19, wherein (i) is the number of symbols for the active uplink bandwidth portion b of carrier f of serving cell c after the last symbol of a corresponding physical downlink control channel (PDCCH) reception and before the first symbol of the first slot of a current PUSCH opportunity i of a TBoMS transmission.

21. A wireless communication device (112), determining (300) a transmit power for a transport block (TBoMS) uplink transmission per TBoMS transmission opportunity across a number of slots; Transmitting the TBoMS uplink transmission according to the transmit power (302); It is adapted to the transmission power is a linear transmission power, A TBoMS transmission opportunity of the TBoMS uplink transmission is defined as a portion of the TBoMS uplink transmission in one slot, the TBoMS transmission opportunity being defined as a slot index within a frame having a system frame number SFN. a first symbol S in the slot, and a number L of consecutive symbols of the TBoMS uplink transmission in the slot; determining (300) the transmit power for the TBoMS uplink transmission for each TBoMS transmission opportunity includes calculating one or more TBoMS transmission opportunity related parameters; the one or more TBoMS transmission opportunity related parameters include a BPRE; The BPRE is a BRE for a multi-slot PUSCH with UL-SCH, calculated over the multiple slots of the TBoMS as Where: - N RE is where i=0 and is the number of symbols for the first transmission opportunity of the TBoMS on the active UL BWP b of carrier f of serving cell c, is the number of subcarriers, excluding DM-RS subcarriers and phase tracking RS samples [TS38.211] in PUSCH symbol j, and assuming no segmentation for nominal repetition when the PUSCH transmission has repetition type B; and K r is the size for code block r across the slots of the TBoMS; C is the number of code blocks transmitted across the slots of the TBoMS; is the bandwidth of the resource allocation expressed as the number of resource blocks for a PUSCH transmission opportunity i on the active UL BWP b of carrier f of serving cell c; A wireless communication device (112), wherein N is a total number of transmission opportunities for said TBoMS.

22. A wireless communication device (112) according to claim 21, further adapted to perform the method according to any one of claims 2 to 20.

23. A wireless communication device (112), One or more transmitters (708); One or more receivers (710); a processing circuit (702) associated with said one or more transmitters (708) and said one or more receivers (710); and wherein the processing circuit (702) is configured to: determining (300) a transmit power for a transport block (TBoMS) uplink transmission per TBoMS transmission opportunity across a number of slots; Transmitting the TBoMS uplink transmission according to the transmit power (302); is set to the transmission power is a linear transmission power, A TBoMS transmission opportunity of the TBoMS uplink transmission is defined as a portion of the TBoMS uplink transmission in one slot, the TBoMS transmission opportunity being defined as a slot index within a frame having a system frame number SFN. a first symbol S in the slot, and a number L of consecutive symbols of the TBoMS uplink transmission in the slot; determining (300) the transmit power for the TBoMS uplink transmission for each TBoMS transmission opportunity includes calculating one or more TBoMS transmission opportunity related parameters; the one or more TBoMS transmission opportunity related parameters include a BPRE; The BPRE is a BRE for a multi-slot PUSCH with UL-SCH, calculated over the multiple slots of the TBoMS as Where: - N RE is where i=0 and is the number of symbols for the first transmission opportunity of the TBoMS on the active UL BWP b of carrier f of serving cell c, is the number of subcarriers, excluding DM-RS subcarriers and phase tracking RS samples [TS38.211] in PUSCH symbol j, and assuming no segmentation for nominal repetition when the PUSCH transmission has repetition type B; and K r is the size for code block r across the slots of the TBoMS; C is the number of code blocks transmitted across the slots of the TBoMS; is the bandwidth of the resource allocation expressed as the number of resource blocks for a PUSCH transmission opportunity i on the active UL BWP b of carrier f of serving cell c; - N is the total number of transmission opportunities for said TBoMS.

24. 24. The wireless communication device (112) of claim 23, wherein the processing circuit (702) is further configured to cause the wireless communication device (112) to perform a method according to any one of claims 2 to 20.

Images