Ul power control for transport block transmission across multiple slot

Abstract

To provide a system and method for uplink power control for transport block over multiple slots (TBoMS).SOLUTION: 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 determined transmit power, thereby performing power control for TBoMS.SELECTED DRAWING: Figure 3

Description

Technical Field

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

[0002] This disclosure relates to uplink power control in a cellular communication system.

Background Art

[0003] Uplink Power Control As defined in the 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 38.213 v16.4.0, a PUSCH / PUCCH / SRS / PRACH transmission opportunity i is defined by a slot index in a frame with a system frame number SFN TIFF2025111483000002.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 was specified as shown in the following excerpt from Section 7.1 of 3GPP TS38.213 v16.4.0. **********Start of excerpt from 3GPP TS38.213 v16.3.0********** When a UE transmits a PUSCH on an active UL BWP b of a carrier f of a serving cell c using a parameter set configuration with index j and a PUSCH power control adjustment state with index l, the UE shall set the PUSCH transmission power P PUSCH,b,f,c (i, j, q d , l) as Determined as TIFF2025111483000003.tif19170, Here, - P CMAX,f,c (i) is the UE-configured maximum output power for carrier f of serving cell c in PUSCH transmission opportunity i, as defined in [8-1, TS38.101-1], [8-2, TS38.101-2] and [8-3, TS38.101-3]. - P O_PUSCH,b,f,c (j) is the component P O_NOMINALPUSCH,f,c (j) and component P O_UE_PUSCH,b,f,c (j) is a parameter assembled from the sum of (j) and component P(j), where j ∈ {0, 1,..., J-1}. - When the UE establishes a dedicated RRC connection using the type-1 random access procedure described in section 8 and P0-PUSCH-AlphaSet is not provided, or for PUSCH (re)transmission corresponding to the RAR UL grant described in section 8.3, j = 0, and P O_UE_PUSCH,b,f,c (0) = 0, and P O_NOMINAL_PUSCH,f,c (0) = P O_PRE + Δ PREAMBLE_Msg3 where, for carrier f of serving cell c, P is provided by preambleReceivedTargetPower [11, TS38.321], and Δ O_PRE is provided by msg3-DeltaPreamble, or when msg3-DeltaPreamble is not provided, Δ PREAMBLE_Msg3 = 0 dB PREAMBLE_Msg3 - When the UE establishes a dedicated RRC connection using the type-2 random access procedure described in section 8 and P0-PUSCH-AlphaSet is not provided, or for PUSCH transmission for the type-2 random access procedure described in section 8.1A, j = 0, and P O_UE_PUSCH,b,f,c (0) = 0, and P O_NOMINAL_PUSCH,f,c (0) = P O_PRE + Δ MsgA_PUSCH where, Here, for the carrier f of the 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 is in dB - For PUSCH (re)transmission 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) is provided by p0 obtained from p0 - PUSCH - Alpha in ConfiguredGrantConfig, which provides the index P0 - PUSCH - AlphaSetId to the set of P0 - PUSCH - AlphaSet for the active UL BWP b of the carrier f of the serving cell c - j ∈ {2,..., J - 1} = S J For all j ∈ S J The applicable P O_NOMINAL_PUSCH,f,c (j) values, for each carrier f of the serving cell c, are provided by p0 - NominalWithGrant, or, if p0 - NominalWithGrant is not provided, P O_NOMINAL_PUSCH,f,c (j) = P O_NOMINAL_PUSCH,f,c (0), and the set of P O_UE_PUSCH,b,f,c (j) values is provided by the set of p0 in the P0 - PUSCH - AlphaSet indicated by each set of p0 - PUSCH - AlphaSetId for the active UL BWP b of the carrier f of the serving cell c - If the UE is provided with two or more values of p0-PUSCH-AlphaSetId by SRI-PUSCH-PowerControl and the DCI format scheduling PUSCH transmission includes an SRI field, the UE shall obtain the mapping between the set of values for the SRI field in the DCI format [5, TS38.212] from sri-PUSCH-PowerControlId in SRI-PUSCH-PowerControl and the set of indices provided by the p0-PUSCH-AlphaSetId that maps to the set of P0-PUSCH-AlphaSet values, and determine P O_UE_PUSCH,b,f,c (j) from the first value in P0-PUSCH-Set with the p0-PUSCH-SetId value mapped to the SRI field value. 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 shall determine P O_UE_PUSCH,b,f,c (j) from the first value in P0-PUSCH-Set with the p0-PUSCH-SetId value mapped to the SRI field value. - If the PUSCH transmission, excluding PUSCH retransmission corresponding to the 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, - 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 determine P O_UE_PUSCH,b,f,c (j) as - when the value of the open-loop power control parameter set indication field is "0" or "00", 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", it is determined 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", it is determined from the second value in the P0-PUSCH-Set with the lowest p0-PUSCH-SetID value. - In other cases, the UE O_UE_PUSCH,b,f,c determines P (j) from the value of the first P0-PUSCH-AlphaSet in p0-AlphaSets. b,f,c - For α (j), - When j = 0, O_NOMINAL_PUSCH,f,c P O_PRE (0) = P MsgA_PUSCH + Δ b,f,c and when msgA-Alpha is provided, α (0) is the value of msgA-Alpha. O_NOMINAL_PUSCH,f,c - Otherwise, P O_PRE (0) = P PREAMBLE_Msg3 + Δ b,f,c or when msgA-Alpha is not provided and msg3-Alpha is provided, α (0) is the value of msg3-Alpha. b,f,c - In other cases, α (0) = 1. b,f,c - When j = 1, α (1) is provided by alpha obtained from p0-PUSCH-Alpha in ConfiguredGrantConfig, which provides the index P0-PUSCH-AlphaSetId to the set of P0-PUSCH-AlphaSets for the active UL BWP b of carrier f of serving cell c. j - When j ∈ S b,f,c the set of α (j) values is provided by the set of alphas in the P0-PUSCH-AlphaSets indicated by the respective sets of p0-PUSCH-AlphaSetId for the active UL BWP b of carrier f of serving cell c.- If the UE is provided with two or more values of SRI-PUSCH-PowerControl and p0-PUSCH-AlphaSetId, and the DCI format scheduling PUSCH transmission includes an SRI field, the UE shall obtain a mapping between the set of values for the SRI field in the DCI format [5, TS38.212] from sri-PUSCH-PowerControlId in SRI-PUSCH-PowerControl and the set of indices provided by p0-PUSCH-AlphaSetId that maps to the set of P0-PUSCH-AlphaSet values, and from the p0-PUSCH-AlphaSetId value mapped to the SRI field value, determine α b,f,c the value of (j) - If a PUSCH transmission excluding PUSCH retransmissions corresponding to RAR UL grants 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 shall determine α from the value of the first P0-PUSCH-AlphaSet in p0-AlphaSets b,f,c for (j) - TIFF2025111483000004.tif7170 is the bandwidth of the PUSCH resource allocation expressed in terms of the number of resource blocks for the PUSCH transmission opportunity i on the active UL BWP b of carrier f of serving cell c, and μ is the SCS setting defined in [4, TS38.211] - PL b,f,c (q d ) is the downlink path loss estimate in dB, calculated by the UE using the reference signal (RS) index q for the active DL BWP of carrier f of serving cell c as described in section 12 d ​- If the UE is not provided with PUSCH-PathlossReferenceRS and enableDefaultBeamPL-ForSRS, or before the UE provides the dedicated upper layer parameters, the UE uses the 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 obtain the MIB to calculate the PL b,f,c (q d ) to calculate - When the UE is configured with the number of RS resource indexes up to the value of maxNrofPUSCH-PathlossReferenceRSs and each set of RS configurations for the number of RS resource indexes by PUSCH-PathlossReferenceRS, the set of RS resource indexes can include either or both of a set of SS / PBCH block indexes provided by ssb-Index when the value of the corresponding pusch-PathlossReferenceRS-Id maps to the SS / PBCH block index and a set of CSI-RS resource indexes provided by csi-RS-Index when the value of the corresponding pusch-PathlossReferenceRS-Id maps to the CSI-RS resource index. The UE identifies the RS resource index q in the set of RS resource indexes corresponding to either the SS / PBCH block index or the CSI-RS resource index provided by pusch-PathlossReferenceRS-Id in PUSCH-PathlossReferenceRS d to identify - If the PUSCH transmission is scheduled by the RAR UL grant described in Section 8.3, or for the PUSCH transmission for the type-2 random access procedure described in Section 8.1A, the UE uses the same RS resource index q as in the case of the corresponding PRACH transmission d to use - If the UE is provided with two or more values of SRI-PUSCH-PowerControl and PUSCH-PathlossReferenceRS-Id, the UE shall obtain the mapping between the set of values for the SRI field in the DCI format scheduling the PUSCH transmission from the sri-PUSCH-PowerControlId in SRI-PUSCH-PowerControl and the set of PUSCH-PathlossReferenceRS-Id values, and from the value of PUSCH-PathlossReferenceRS-Id mapped to the SRI field value, the RS resource index q d is determined, where the RS resource is either on the serving cell c or, if provided, on the serving cell indicated by the value of pathlossReferenceLinking - If the PUSCH transmission is scheduled by DCI format 0_0 and the UE is provided with the spatial setting by PUCCH-SpatialRelationInfo for the PUCCH resource with the lowest index for each carrier f and the active UL BWP b of the serving cell c as described in Section 9.2.2, the UE shall use the same RS resource index q as in the case of PUCCH transmission in the PUCCH resource with the lowest index d for use - If the PUSCH transmission is not scheduled by DCI format 0_0 and the UE provides enableDefaultBeamPL-ForSRS and does not provide PUSCH-PathlossReferenceRS and PUSCH-PathlossReferenceRS-r16, the UE shall use the same RS resource index q as in the case of the SRS resource set having the SRS resource related to the PUSCH transmission d for use - In the following cases - The PUSCH transmission is scheduled by DCI format 0_0 and the UE does not provide the spatial setting for PUCCH transmission, or - The PUSCH transmission is scheduled by DCI format 0_1 or DCI format 0_2 that does not include the SRI field, or - SRI-PUSCH-PowerControl is not provided to the UE The UE determines the RS resource index q for which each PUSCH-PathlossReferenceRS-Id value is equal to 0 d where the RS resource is either on the serving cell c or, if provided, on the serving cell indicated by the value of pathlossReferenceLinking - In the following cases - The PUSCH transmission is scheduled by DCI format 0_0 on the serving cell c, - The UE is not provided with PUCCH resources for the active UL BWP of the serving cell c, and - The UE is provided with enableDefaultBeamPL-ForPUSCH0-0 The UE provides the RS resource index q with the 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 for the periodic RS resource d to be determined - In the following cases - The PUSCH transmission is scheduled by DCI format 0_0 on the serving cell c, - The UE is not provided with the spatial setting for the PUCCH resources on the active UL BWP of the primary cell [11, TS38.321], and - The UE is provided with enableDefaultBeamPL-ForPUSCH0-0 The UE provides a periodic RS resource with qcl-Type set to "typeD" in the TCI state or QCL assumption of the CORESET having the lowest index in the active DL BWP of serving cell c, where the RS resource index q d is determined - For PUSCH transmission configured by ConfiguredGrantConfig, if rrc-ConfiguredUplinkGrant is included in ConfiguredGrantConfig, the RS resource index q d is provided by the value of pathlossReferenceIndex included in rrc-ConfiguredUplinkGrant, where the RS resource is either on serving cell c or, if provided, on the serving cell indicated by the value of pathlossReferenceLinking - For PUSCH transmission configured by ConfiguredGrantConfig not including rrc-ConfiguredUplinkGrant, the UE determines the RS resource index q from the value of PUSCH-PathlossReferenceRS-Id 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 the SRI field, the UE determines the RS resource index q where each PUSCH-PathlossReferenceRS-Id value is equal to 0 d where the RS resource is either on serving cell c or, if provided, on the serving cell indicated by the value of pathlossReferenceLinking - When the UE is provided with enablePL-RS-UpdateForPUSCH-SRS, the mapping between the sri-PUSCH-PowerControlId value and the PUSCH-PathlossReferenceRS-Id value can be updated by the MAC CE as described in [11, TS38.321]. - For PUSCH transmissions scheduled by a DCI format that does not include an SRI field, or for PUSCH transmissions activated by a DCI format that does not include an SRI field and is configured by ConfiguredGrantConfig, as described in Section 10.2, the RS resource index q d q d is determined from the PUSCH-PathlossReferenceRS-Id mapped to sri-PUSCH-PowerControlId = 0. PL b,f,c (q d ) = referenceSignalPower - the RSRP processed by the upper layer filter, where referenceSignalPower is provided by the upper layer, RSRP is defined in [7, TS38.215] for the reference serving cell, and the upper layer filter settings provided by QuantityConfig are defined in [12, TS38.331] for the reference serving cell. If the UE does not have configured periodic CSI-RS reception, referenceSignalPower is provided by ss-PBCH-BlockPower. If the UE has configured periodic CSI-RS reception, referenceSignalPower is provided either by ss-PBCH-BlockPower or by powerControlOffsetSS which provides the offset of the CSI-RS transmission power with respect to the SS / PBCH block transmission power [6, TS38.214]. If powerControlOffsetSS is not provided to the UE, the UE assumes an offset of 0 dB. - Ks When = 1.25, it is TIFF2025111483000005.tif7170, and K s When = 0, Δ TF,b,f,c (i) = 0, where K s is provided by deltaMCS for each carrier f and each UL BWP b of serving cell c. When PUSCH transmission spans two or more layers [6, TS38.214], Δ TF,b,f,c (i) = 0. For each carrier f and each active UL BWP b of each serving cell c, BPRE and TIFF2025111483000006.tif6170 is calculated as follows - For PUSCH with UL - SCH data it is TIFF2025111483000007.tif9170, and for CSI transmission in PUSCH without UL - SCH data it is TIFF2025111483000008.tif7170, where - C is the number of code blocks to be transmitted, K r is the size for code block r, N RE is the number of resource elements determined as TIFF2025111483000009.tif12170, where TIFF2025111483000010.tif7170 is the number of symbols for PUSCH transmission opportunity i on carrier f of serving cell c's active UL BWP b, TIFF2025111483000011.tif7170 is the number of sub - carriers excluding DM - RS sub - carriers and phase - tracking RS samples [4, TS38.211] in PUSCH symbol j, and assuming no segmentation for nominal repetition when PUSCH transmission has repeating type B, it is TIFF2025111483000012.tif7170, C, K r is defined in [5, TS38.212] - When the PUSCH contains UL-SCH data, it is TIFF2025111483000013.tif6170, and when the PUSCH contains CSI and does not contain UL-SCH data, as described in Section 9.3, it is TIFF2025111483000014.tif6170 - As described 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 PUSCH transmissions that contain CSI and do not contain UL-SCH data - 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 for (i, l) - δ PUSCH,b,f,c (i, l) is included in the DCI format that schedules PUSCH transmission opportunity i on the 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 a CRC scrambled by TPC-PUSCH-RNTI, and is the TPC command value - When twoPUSCH-PC-AdjustmentStates is configured for the UE, l ∈ {0, 1}, and when twoPUSCH-PC-AdjustmentStates is not configured for the UE, or when the PUSCH transmission is scheduled by the RAR UL grant described in Section 8.3, l = 0 - For PUSCH (re)transmissions configured by ConfiguredGrantConfig, the value of l ∈ {0, 1} is provided to the UE by powerControlLoopToUse - When the UE is provided with SRI-PUSCH-PowerControl, the UE obtains the mapping between the set of values for the SRI field in the DCI format that schedules PUSCH transmissions and the (one or more) l values provided by sri-PUSCH-ClosedLoopIndex, and determines the l value mapped to the SRI field value. - When PUSCH transmissions are scheduled by a DCI format that does not include an SRI field, or when SRI-PUSCH-PowerControl is not provided to the UE, l = 0. - When the UE obtains one TPC command from DCI format 2_2 with a CRC scrambled by TPC-PUSCH-RNTI, the l value is provided by the closed-loop indicator field in DCI format 2_2. - TIFF2025111483000015.tif11170 is the PUSCH power control adjustment state l for the active UL BWP b of carrier f of serving cell c and PUSCH transmission opportunity i when the UE is not provided with tpc-Accumulation, where - δ PUSCH,b,f,c The value is given in Table 7.1.1-1. - TIFF2025111483000016.tif10170 is the sum of the TPC command values in the set D with cardinality C(D PUSCH (i - i0)-1 symbols before the PUSCH transmission opportunity i - i0 and K PUSCH (i) symbols before the PUSCH transmission opportunity i that the UE receives on the active UL BWP b of carrier f of serving cell c for the PUSCH power control adjustment state l, where i ) of the TPC command values, where i0 > 0 is the smallest integer such that the K i (i - i0) symbols before the PUSCH transmission opportunity i - i0 are earlier than the K PUSCH (i) symbols before the PUSCH transmission opportunity i. PUSCH (i) symbols before the PUSCH transmission opportunity i. - When PUSCH transmission is scheduled by a DCI format, K 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 PUSCH transmission - When PUSCH transmission is configured by a ConfiguredGrantConfig, K PUSCH (i) is the number of symbols per slot for the active UL BWP b of carrier f of serving cell c K is equal to the product of TIFF2025111483000017.tif7170 and the minimum value provided by k2 in PUSCH-ConfigCommon PUSCH,min The number of symbols - If the UE reaches the maximum power for the active UL BWP b of carrier f of serving cell c at PUSCH transmission opportunity i - i0, TIFF2025111483000018.tif10170, then f b,f,c (i, l) = f b,f,c (i - i0, l) - If the UE reaches the minimum power for the active UL BWP b of carrier f of serving cell c at PUSCH transmission opportunity i - i0, TIFF2025111483000019.tif11170, then f b,f,c (i, l) = f b,f,c (i - i0, l) - The UE resets the accumulation of the PUSCH power control adjustment state l for the active UL BWP b of carrier f of serving cell c to f b,f,c (k, l) = 0, k = 0, 1,..., i - For the corresponding P O_UE_PUSCH,b,f,c If the setting for the (j) value is provided by the upper layer, - For the corresponding α b,f,c If the setting for the (j) value is provided by the upper layer, Here, l is - If j > 1 and the UE is provided with higher layer SRI-PUSCH-PowerControl, l is the (one or more) sri-PUSCH-ClosedLoopIndex values configured in any SRI-PUSCH-PowerControl with the sri-P0-PUSCH-AlphaSetId value corresponding to j - If j > 1 and the UE is not provided with SRI-PUSCH-PowerControl or j = 0, l = 0 - If j = 1, l is provided by the value of powerControlLoopToUse as determined from the value of j - f b,f,c (i, l) = δ PUSCH,b,f,c (i, l) is the PUSCH power control adjustment state for the active UL BWP b of carrier f of serving cell c and PUSCH transmission opportunity i when the UE provides tpc-Accumulation, where - δ PUSCH,b,f,c The absolute value is given in Table 7.1.1-1 - If the UE receives a random access response message in response to a PRACH transmission or MsgA transmission on the active UL BWP b of carrier f of serving cell c as described in Section 8 - f b,f,c (0, l) = ΔP rampup,b,f,c + δ msg2,b,f,c where l = 0 - δ msg2,b,f,c is the TPC command value indicated in the random access response grant of the random access response message corresponding to a PRACH transmission following a type-1 random access procedure or the random access response grant of the random access response message corresponding to a MsgA transmission following a type-2 random access procedure with (one or more) RAR messages for fallbackRAR on the active UL BWP b of carrier f in serving cell c, - TIFF2025111483000020.tif is 18170, and ΔP rampuprequested,b,f,c is provided by the upper layer and corresponds to the total power ramp-up requested by the upper layer from the first random access preamble to the last random access preamble for carrier f in serving cell c, TIFF2025111483000021.tif 6170 is the bandwidth of the PUSCH resource allocation expressed in the number of resource blocks for the first PUSCH transmission on active UL BWP b of carrier f in serving cell c, and Δ TF,b,f,c (0) is the power adjustment of the first PUSCH transmission on active UL BWP b of carrier f in serving cell c. - If the UE transmits a PUSCH at PUSCH transmission opportunity i on active UL BWP b of carrier f in serving cell c as described in section 8.1A, f b,f,c (0,l)=Δ P_rampup,b,f,c where - l = 0, - TIFF2025111483000022.tif is 18170, and ΔP rampuprequested,b,f,c is provided by the upper layer and corresponds to the total power ramp-up requested by the upper layer, TIFF2025111483000023.tif 6170 is the bandwidth of the PUSCH resource allocation expressed in the number of resource blocks, and Δ TF,b,f,c (i) is the power adjustment of the PUSCH transmission at PUSCH transmission opportunity i. **********End of excerpt from 3GPP TS38.213 v16.3.0**********

[0005] Layer 3 filter processing The layer 3 filter processing is specified as shown in the following excerpt from 3GPP TS38.331 v16.3.1. **********Start of excerpt from 3GPP TS38.331 v16.3.1********** 5.5.3.2 Layer 3 Filtering The UE shall perform the following. 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 using for evaluation of reporting criteria or for measurement reporting, filter the measured results by the following formula. F n =(1 - a)*F n-1 +a*M n [2] Here M n is the latest received measurement result 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 result, where F0 is set to M1 when the first measurement result from the physical layer is received, and a = 1 / 2 for MeasObjectNR (ki / 4) and where k i is the filterCoefficient for the corresponding measurement quantity of the i-th QuantityConfigNR in the quantityConfigNR-List, i is indicated by the quantityConfigIndex in MeasObjectNR, and a = 1 / 2 for other measurements (k / 4) and where k is the filterCoefficient for the corresponding measurement quantity received by quantityConfig, and a = 1 / 2 for UTRA-FDD (k / 4) and where k is the filterCoefficient for the corresponding measurement quantity received by quantityConfigUTRA-FDD in QuantityConfig. [3] Note that assuming a sample rate equal to Xms for filterCoefficient k, the filter is adapted so that the filter's time characteristics are preserved at different input rates. The value of X is equivalent to the L1 measurement period within one frequency, as defined in TS38.133

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

[14] . See TS38.133

[14] for further details regarding physical layer measurements. Note 4: For CLI-RSSI measurements, whether the filter processing should be reset at BWP switching depends on the UE implementation. ... - FilterCoefficient IE FilterCoefficient specifies the measurement filter processing coefficient. The value fc0 corresponds to k = 0, fc1 corresponds to k = 1, and so on. FilterCoefficient information element TIFF2025111483000024.tif27170**********End of excerpt from 3GPP TS38.331 v16.3.1**********

[0006] Agreement on TBoMS in Rel-17 NR Coverage Expansion WI In the work item description (WID) for Rel-17 NR Coverage Expansion, it was agreed that single transport block (TB) transmission over multiple slots is specified as indicated by the following agreement. Agreement: Specify the (one or more) mechanisms for supporting TB processing over multi-slot PUSCH [RAN1] 〇 The TBS determined based on multiple slots and transmitted over multiple slots.

[0007] Some related agreements were made at the RAN1#104 meeting. Agreement: · Consider one or two of the following options as the starting point for designing the time domain resource determination of TBoMS 〇 TDRA (PUSCH repetition type A like TDRA) such as PUSCH repetition type A, that is, the number of allocated symbols is the same in each slot. 〇 TDRA (PUSCH repetition type B like TDRA) such as PUSCH repetition type B, that is, the number of allocated symbols in each slot can be different Agreement: · Consecutive physical slots for UL transmission can be used for TBoMS for unpaired spectrum. 〇 Resolve whether to support non-consecutive physical slots for UL transmission for TBoMS for unpaired spectrum in RAN1#104b~e · Consecutive physical slots for UL transmission can be used for TBoMS for paired spectrum and SUL band. 〇 Whether non-consecutive physical slots for UL transmission are also supported for paired spectrum and SUL band, FFS

Summary of the Invention

[0008] Systems and methods for uplink power control for transport blocks (TBs) (TBoMS) across multiple slots are disclosed herein. In one embodiment, a method implemented by a wireless communication device includes determining a transmission power for TBoMS uplink transmission for each TBoMS transmission opportunity and transmitting a TBoMS uplink transmission according to the transmission power. In this way, power control for TBoMS is provided.

[0009] In one embodiment, the transmission power is linear transmission 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 of the TBoMS uplink transmission is defined as part of the TBoMS uplink transmission within one slot, and the TBoMS transmission opportunity is defined by the slot index TIFF2025111483000025.tif7170 in a frame with a system frame number SFN, the first symbol S in the slot, and the number L of consecutive symbols of the TBoMS uplink transmission in the slot.

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

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

[0013] In one embodiment, all slots for the TBoMS uplink transmission are treated as a single TBoMS transmission opportunity.

[0014] In one embodiment, the set of all slots for the TBoMS uplink transmission is divided into two or more subsets, and each 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 regarding how the TBoMS transmission opportunity is defined, and one of the two or more options used by the wireless communication device when determining the transmission power for the TBoMS uplink transmission per TBoMS transmission opportunity is either set by the network node or determined in advance (e.g., predefined).

[0016] In one embodiment, one TBoMS transmission opportunity spans two or more slots, and determining the transmission power for TBoMS uplink transmission for each TBoMS transmission opportunity involves either determining the transmission power for the TBoMS transmission opportunity, where the transmission power is equivalent to the transmission power determined for the first slot of the TBoMS transmission opportunity and the same transmission power is maintained until the end of the TBoMS transmission opportunity, or determining the transmission power for the TBoMS transmission opportunity considering two or more slots of the TBoMS transmission opportunity as a whole. In one embodiment, certain parameters are different for at least two of the two or more slots of the TBoMS transmission opportunity, and determining the transmission power for the TBoMS transmission opportunity involves determining the transmission power for the TBoMS transmission opportunity based on specific parameters for one or more fixed ones of the two or more slots of the TBoMS transmission opportunity.

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

[0018] In one embodiment, the same transmission power is set or pre-determined across multiple slots of the TBoMS uplink transmission, and the wireless communication device determines the transmission power prior to transmission based on the transmission power in the first slot and maintains the same transmission power until the end of the TBoMS uplink transmission. In one embodiment, · The wireless communication device 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 receives a TPC command for the TBoMS uplink transmission during the TBoMS uplink transmission, ○ The wireless communication device discards the TPC command, or ○ The wireless communication device applies the TPC command in the next transmission after the TBoMS uplink transmission, and / or · The wireless communication device does not expect that each base station will change the reference signal and its transmission power that the wireless communication device uses to estimate the downlink path loss during the TBoMS uplink transmission, and / or · The wireless communication device does not perform downlink path loss measurements from the physical layer during the TBoMS uplink transmission, and / or · The wireless communication device does not expect that the PUSCH power control adjustment state l will be changed by RRC or DCI signaling during the TBoMS uplink transmission.

[0019] In one embodiment, determining the transmission 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 are (I) the MCS related parameter Δ TF,b,f,c (i), (II) BPRE, (III) the PUSCH power control adjustment state f for the active UL BWP b of carrier f of serving cell c in PUSCH transmission opportunity i b,f,cIt includes (i, l), or any two or more combinations of (I) to (III). In another embodiment, one or more TBoMS transmission opportunity related parameters include BPRE. In one embodiment, BPRE is BPRE for a multi-slot PUSCH with UL-SCH, calculated as TIFF2025111483000028.tif14170 across multiple slots of TBoMS, where N RE is the number of resource elements across multiple slots of TBoMS, determined as TIFF2025111483000029.tif12170, where N is the total number of transmission opportunities of TBoMS, TIFF2025111483000030.tif7170 is the number of symbols for PUSCH transmission opportunity i on active UL BWP b of carrier f of serving cell c, TIFF2025111483000031.tif7170 is the number of subcarriers excluding DM-RS subcarriers and phase tracking RS samples in PUSCH symbol j, TIFF2025111483000032.tif7170.

[0020] In one embodiment, BPRE is BPRE for a multi-slot PUSCH with UL-SCH, calculated as TIFF2025111483000033.tif14170 across multiple slots of TBoMS, where - N RE is the number of resource elements determined as TIFF2025111483000034.tif11170, where i = 0, TIFF2025111483000035.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, TIFF2025111483000036.tif6170 is the number of subcarriers excluding the DM-RS subcarriers and the phase-tracking RS samples [TS38.211] in PUSCH symbol j, and assuming no segmentation for nominal repetition when PUSCH transmission has repeating type B, is TIFF2025111483000037.tif7170, - N is the total number of transmission opportunities for TBoMS.

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

[0022] In one embodiment, multiple TBoMS transmission opportunities are used for power calculation for TBoMS uplink transmission. The absolute power adjustment for determining the transmission power in one TBoMS transmission opportunity is determined by the latest TPC command received before 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 the set of symbols / slots before the first slot of the TBoMS transmission opportunity.

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

[0024] In one embodiment, when TPC accumulation is enabled and the accumulated power offset value is used for power adjustment, determining the transmission power for TBoMS uplink transmission for each TBoMS transmission opportunity includes, on the active uplink bandwidth part b of carrier f of serving cell c for PUSCH power control adjustment state l, the K PUSCH (i - i0) - 1 symbols before the TBoMS transmission opportunity i - i0 and the K PUSCH (i) symbols before the TBoMS transmission opportunity i, determining the cumulative power adjustment at the TBoMS transmission opportunity of the TBoMS uplink transmission based on the set of TPC commands received between them, where i0 > 0 is the K PUSCH (i - i0) symbols that are the earliest and the smallest integer earlier than the K PUSCH (i) symbols before the PUSCH transmission opportunity i. In one embodiment, when PUSCH transmission is scheduled by a downlink control information (DCI) format, K PUSCH (i) is the number of symbols for the active uplink bandwidth part 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, when TPC accumulation is enabled and the accumulated power offset value is used for power adjustment, and multiple TBoMS transmission opportunities are used for power calculation for one TBoMS transmission, determining the transmission power for TBoMS uplink transmission for each TBoMS transmission opportunity (300) includes, on the active uplink bandwidth part b of carrier f of serving cell c for PUSCH power control adjustment state l, the K PUSCH (i - i0) - 1 symbols before the PUSCH transmission opportunity i - i0 and the K PUSCHDetermining cumulative power adjustment at a TBoMS transmission opportunity for TBoMS uplink transmission based on a set of TPC commands received between (i) symbols, where i0>0 is K before the PUSCH transmission opportunity i - i0 PUSCH (i - i0) symbols are the K PUSCH (i) symbols earlier, and is the smallest integer. In one embodiment, when PUSCH transmission is scheduled by a downlink control information (DCI) format, K PUSCH (i) is the number of symbols for the active uplink bandwidth part b of carrier f of serving cell c that are 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 the wireless communication device are also disclosed herein.

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

Brief Description of the Drawings

[0028]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Mode for Carrying Out the Invention

[0029] The embodiments described below represent information for enabling those skilled in the art to practice these embodiments and show the best mode of practicing these embodiments. 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 application examples of these concepts that are not specifically addressed herein. It should be understood that these concepts and application examples 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] Wireless Access Node: As used herein, a "wireless access node" or "wireless network node" or "wireless access network node" is any node in a radio access network (RAN) of a cellular communication network that is operative to transmit and / or receive signals wirelessly. Some examples of wireless access nodes include, but are not limited to, base stations (e.g., a new radio (NR) base station (gNB) in a 3rd Generation Partnership Project (3GPP) 5th Generation (5G) NR network, or an evolved or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), high power or macro base stations, low power base stations (e.g., micro base stations, pico base stations, home eNBs, etc.), relay nodes, network nodes implementing portions of base station functionality, or network nodes implementing a gNB distributed unit (gNB-DU), or network nodes implementing portions of the functionality of any other type of wireless 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 implementing core network functionality. Some examples of core network nodes include, for example, a mobility management entity (MME), a packet data network gateway (P-GW), a service capability exposure function (SCEF), a home subscriber server (HSS), etc. Some other examples of core network nodes include nodes implementing 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 exposure function (NEF), a network function (NF) repository function (NRF), a policy control function (PCF), an integrated data management (UDM), etc.

[0033] Communication device: As used herein, a "communication device" is any type of device having access to an access network. Some examples of communication devices include, but are not limited to, mobile phones, smartphones, sensor devices, meters, vehicles, household appliances, medical devices, media players, cameras, or any type of home electronics, such as, but not limited to, televisions, radios, lighting devices, tablet computers, laptop computers, or personal computers (PCs). A communication device can be a portable, handheld, computer-equipped, or in-vehicle mobile device enabled to communicate voice and / or data via a wireless or wired connection.

[0034] Wireless communication device: One type of communication device can be a wireless communication device, which can be any type of wireless device having access to a wireless network (e.g., a cellular network), i.e., served by a wireless network. Some examples of wireless communication devices include, but are not limited to, user equipment devices (UEs) in a 3GPP network, machine type communication (MTC) devices, and Internet of Things (IoT) devices. Such wireless communication devices can be, or can be integrated into, mobile phones, smartphones, sensor devices, meters, vehicles, household appliances, medical devices, media players, cameras, or any type of home electronics, such as, but not limited to, televisions, radios, lighting devices, tablet computers, laptop computers, or PCs. A wireless communication device can be a portable, handheld, computer-equipped, or in-vehicle mobile device enabled to communicate voice and / or data via 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 communication network / system.

[0036] Transmission / Reception Point (TRP): In some embodiments, the TRP can be any of a network node, a radio head, a spatial relationship, or a Transmission Configuration Indicator (TCI) state. The TRP can be represented by a spatial relationship or a TCI state in some embodiments. In some embodiments, the TRP may use multiple TCI states. In some embodiments, the 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 multi-TRP (multiple TRP) operation, the serving cell can schedule the UE from two TRPs to provide better Physical Downlink Shared Channel (PDSCH) coverage, reliability, and / or data rate. There are two different operating modes for multi-TRP, namely, single Downlink Control Information (DCI) and multi-DCI. For both modes, the control of uplink and downlink operations is performed by both the physical layer and the Medium Access Control (MAC). In the single DCI mode, the UE is scheduled by the same DCI for both TRPs, and in the multi-DCI mode, the UE is scheduled by independent DCIs from each TRP.

[0037] In some embodiments, a set of configured Transmission Points (TPs) is a set of geographically co-located transmission antennas (e.g., an antenna array (with one or more antenna elements)) for one cell, a part of one cell, or one Positioning Reference Signal (PRS) dedicated TP. The TP can include an evolved Node B (eNB) antenna, a Remote Radio Head (RRH), a remote antenna of a base station, an antenna of a PRS dedicated TP, etc. One cell can be formed by one or more TPs. In the case of a homogeneous arrangement, each TP can correspond to one cell.

[0038] In some embodiments, the set of TRPs is a set of geographically collocated antennas (e.g., an antenna array (with one or more antenna elements)) that support a TP and / or receive point (RP) function.

[0039] The description given herein focuses on 3GPP cellular communication systems, and thus it should be noted that 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, especially with respect to 5G NR concepts, beams may be used instead of cells, and thus it is important to note that the concepts described herein are equally applicable to both cells and beams.

[0041] Currently, there are several issues. 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 the scheduled uplink (UL) symbol in a slot. The transport block (TBoMS) of multiple slots in Release 17 has one transport block (TB) over multiple slots. One problem that needs to be solved is whether the transmission opportunity for TBoMS is the slot with the TB or multiple slots. This is implicitly related to the problem of whether the same transmit power can be used or different transmit powers can be used among 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 complex for a UE to calculate the number of information bits in a slot for a Type-B like TBoMS. Therefore, a calculation over multiple slots and how it is applied to the transmission opportunity of one slot is proposed.

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

[0044] Systems and methods are disclosed herein that provide solutions to the above or other problems. Embodiments of systems and methods related to providing a definition of a transmission opportunity for TBoMS PUSCH transmission are disclosed herein. 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 transmission are also disclosed herein.

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

[0046] Regarding this point, FIG. 1 shows an example of a cellular communication system 100 in which embodiments of the present disclosure can 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). However, the embodiments disclosed herein can 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, which in the 5GS include NR base stations (gNBs) and optionally Next Generation eNBs (ng-eNBs) (e.g., LTE RAN nodes connected to the 5GC), and these 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 station 102 and individually as base station 102. Similarly, the (macro) cells 104-1 and 104-2 are generally referred to herein collectively as (macro) cell 104 and individually as (macro) cell 104. The RAN may also include several low-power nodes 106-1 to 106-4 that control corresponding small cells 108-1 to 108-4. The low-power nodes 106-1 to 106-4 can be small base stations (such as pico base stations or femto base stations) or RRHs, etc. In particular, although not shown, one or more of the small cells 108-1 to 108-4 can be alternatively provided by the base station 102. The low-power nodes 106-1 to 106-4 are generally referred to herein collectively as low-power node 106 and individually as low-power node 106. Similarly, the small cells 108-1 to 108-4 are generally referred to herein collectively as small cell 108 and individually as small cell 108. The cellular communication system 100 also includes a core network 110, which is called 5GC in the 5GS. The base stations 102 (and optionally the low-power nodes 106) are connected to the core network 110.

[0047] Base station 102 and low-power node 106 provide services to wireless communication devices 112-1 to 112-5 in corresponding cells 104 and 108. The wireless communication devices 112-1 to 112-5 are generally collectively referred to as wireless communication device 112 in this specification and individually as wireless communication device 112. In the following description, the wireless communication device 112 is often a UE and may thus be referred to as UE112 in this specification, but the present disclosure is not limited thereto.

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

[0049] In the present disclosure, embodiments of systems and methods for providing a definition of a transmission opportunity for TBoMS are disclosed. Further, embodiments of systems and methods for maintaining the same power for cross-slot channel estimation that requires the same transmission power over multiple slots and for determining transmission opportunity-related power control parameters for TBoMS PUSCH transmission.

[0050] Definition of TBoMS PUSCH Transmission Opportunity for TBoMS PUSCH Power Calculation In NR Release 16, the PUSCH transmission power is determined for each PUSCH transmission opportunity. The PUSCH transmission opportunity i is defined by the slot index TIFF2025111483000038.tif7170 in a frame with system frame number SFN, the first symbol S in the slot, and the number L of consecutive symbols.

[0051] In the first embodiment, the UE 112 calculates the linear TBoMS PUSCH power for each TBoMS PUSCH transmission opportunity, and the TBoMS PUSCH transmission opportunity can 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 within one slot, and the TBoMS PUSCH transmission opportunity is the slot index within the frame with the system frame number SFN TIFF2025111483000039.tif7170, the first symbol S within the slot, and the number L of consecutive symbols of TBoMS within the slot. · Option 2: In this option, one TBoMS PUSCH transmission opportunity spans multiple consecutive slots of TBoMS. One transmission opportunity is the index of the first slot of the transmission opportunity with the system frame number SFN TIFF2025111483000040.tif7170, the first symbol S within the first slot of the transmission opportunity, 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 TBoMS. The transmission opportunity is the index of the first slot of the transmission opportunity with the system frame number SFN TIFF2025111483000041.tif7170, the first symbol S within the first slot, and the number L of symbols of TBoMS either in this slot or over multiple slots of TBoMS. · Option 4: In this option, all the slots for TBoMS transmission are treated as one TBoMS PUSCH transmission opportunity i. · Option 5: In this option, the entire set of slots for TBoMS transmission can be grouped into different subsets, and each subset of slots can be treated as one TBoMS PUSCH transmission opportunity.

[0052] In a sub - embodiment of the first embodiment, when a plurality of the options are supported, one of the options for determining the definition of PUSCH transmission opportunity i for power calculation can be set by a network node (e.g., base station 102) for the UE112 via, for example, downlink control information (DCI) and / or higher - layer signaling. Alternatively, one of the options to be used by the UE112 for determining the definition of PUSCH transmission opportunity i for power calculation can be predefined or otherwise pre - determined. · The above - mentioned options regarding the first embodiment, except Option 1, enable TBoMS transmission opportunities for multiple slots. The maximum number of slots enabled per TBoMS PUSCH opportunity can depend on whether non - consecutive slots are enabled in some time - division duplex (TDD) settings. · If non - consecutive slots are set for TBoMS, but only consecutive slots are enabled in a transmission opportunity as in the case of Option 2 above, multiple transmission opportunities for TBoMS may be required. However, enabling non - consecutive slots to be within one PUSCH opportunity allows for having only one TBoMS PUSCH opportunity when all slots are treated as one TBoMS PUSCH opportunity as described in Option 4. · Figure 2 shows an example where the TBoMS spans four uplink (UL) slots with a set of slots having a specific TDD configuration {DDSUUDDSUU} set. 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 the second embodiment, when one transmission opportunity of the TBoMS spans multiple slots, the UE112 can do the following. · Option 1: Determine the transmission power for the transmission opportunity to be equivalent to the transmission power determined in the first slot of the transmission opportunity and maintain it until the end of the transmission opportunity. · Option 2: Determine the transmission power for the multiple slots of the transmission opportunity as a whole.

[0054] Option 1 and Option 2 of the second embodiment can be equal when the power control relationship 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 sub - embodiment of the second embodiment, parameter X can be determined based on one or more of the following methods. · Option A: Parameter X in one or more fixed slots of the TBoMS PUSCH opportunity is used to determine the transmission power in the set of slots in this PUSCH opportunity. For example, "one or more fixed slots" can 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 can be set by the network

[0055] In one example, UE112 uses Option 1 of the second embodiment for all parameters except the BPRE 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 UL power control. When the transmission opportunity is within a slot, UE112 can quickly adapt to the power change factor in the next slot. On the other hand, when cross-slot channel estimation is considered, UE112 will better maintain the same transmission power over multiple slots and have a longer transmission opportunity. There are pros and cons to maintaining either the same or different transmission power over multiple slots of TBoMS.

[0057] The transmission opportunity of TBoMS can be pre-determined to reuse the transmission opportunity of a single-slot TB. In that case, UE112 can be configured / pre-determined whether different transmission powers are possible for the transmission of TBoMS. When TBoMS spans multiple slots, the base station 102 (e.g., gNB) can set the number of UE transmission power changes or when the power change can occur.

[0058] In the third embodiment, UE112 can be configured by the network (e.g., by base station 102), or it can be pre-determined whether a change in transmission power is possible during the transmission of TBoMS. When the repetition of TBoMS is configured for UE112, UE112 can be configured by the network, or it can be pre-determined whether a change in transmission power is possible between repetitions of TBoMS. In either of these two cases, if a change in transmission power is possible, UE112 can be configured with the number of in-transmission power changes or when the transmission power change can occur.

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

[0060] In the fourth embodiment, when the same transmission power is set / pre - determined over multiple slots of TBoMS, UE112 determines the transmission power before transmission based on the transmission power in the first slot and maintains the same transmission power until the end of the transmission.

[0061] In the fifth embodiment, when the same transmission power is set / pre - determined over multiple slots of TBoMS, one or more of the following methods may be used. · UE112 does not expect to receive a TPC command for the transmission of TBoMS during the transmission of TBoMS. · When UE112 receives a TPC command for the transmission of TBoMS during the transmission of TBoMS, ○ UE112 discards the TPC command, or ○ UE applies the TPC command in the next transmission after TBoMS. For example, a TPC cumulative command. · UE112 does not expect the base station 102 (e.g., gNB) to change the reference signal and its transmission power that UE112 uses to estimate the downlink (DL) path loss during the transmission of TBoMS. Otherwise, UE112 ignores the change. · UE112 does not perform DL path loss measurements from the physical layer during the transmission of TBoMS. · UE112 does not expect the PUSCH power control adjustment state l to be changed by RRC or DCI signaling during the transmission of TBoMS. Otherwise, UE112 ignores the change.

[0062] In a sub - embodiment of the fifth embodiment, if the same transmission power is set / pre - determined over the repetitions of TBoMS, the same method can be used over the repetitions.

[0063] Calculation of Transmission Opportunity - related Power Control Parameters for TBoMS In Release 16, one transmission opportunity i is within a slot and several parameters are determined per slot. If the definition of the transmission opportunity is to be reused for TBoMS, some parameters can 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, for the calculation of Δ TF,b,f,c (i), the bits per resource element (BPRE) is the number of bits transmitted by one resource element (RE) and is calculated per slot. Alternatively, if the existing definition of the transmission opportunity is reused for TBoMS, BPRE is calculated once over multiple transmission opportunities of TBoMS and can be applied to Δ TF,b,f,c (i) for all transmission opportunities. *****Start of excerpt***** It is TIFF2025111483000042.tif8170, - For PUSCH with UL - SCH data It is TIFF2025111483000043.tif8170, for CSI transmission in PUSCH without UL - SCH data TIFF2025111483000044.tif is 7170, where - C is the number of code blocks to be transmitted, K r is the size for code block r, N RE is TIFF2025111483000045.tif14170 is the number of resource elements determined as, where TIFF2025111483000046.tif7170 is the number of symbols for PUSCH transmission opportunity i on active UL BWP b of carrier f of serving cell c, TIFF2025111483000047.tif7170 is the number of subcarriers excluding the DM-RS subcarriers and phase-tracking RS samples [TS38.211] in PUSCH symbol j, and assuming no segmentation for nominal repetition when PUSCH transmission has repeating type B, TIFF2025111483000048.tif7170, C, K r is defined in [TS38.212] *****End of excerpt*****

[0065] In the sixth embodiment, the BPRE for multi-slot PUSCH with UL-SCH data can be calculated over multiple slots of the TB in one or more of the following ways, where the bold underlined text indicates the required changes 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 to be transmitted over multiple slots of the TBoMS. If there is no code block (CB) segmentation for the TBoMS, C = 1. - K r is the size for code block r over multiple slots of the TBoMS. TIFF2025111483000049.tif8170 is the TBS of the TBoMS. - Option 1, which is TIFF2025111483000050.tif8170, where ○ N RE is the number of resource elements over multiple slots of TBoMS, determined as TIFF2025111483000051.tif12170, where N is the total number of transmission opportunities of TBoMS, TIFF2025111483000052.tif7170 is the number of symbols for PUSCH transmission opportunity i on active UL bandwidth part (BWP) b of carrier f of serving cell c, TIFF2025111483000053.tif7170 is the number of subcarriers excluding the demodulation reference signal (DM-RS) subcarriers and phase-tracking RS samples [TS38.211] in PUSCH symbol j, which is TIFF2025111483000054.tif7170, - Option 2, which is TIFF2025111483000055.tif9170, where ○ N RE is the number of resource elements determined as TIFF2025111483000056.tif12170, where i = 0, TIFF2025111483000057.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, TIFF2025111483000058.tif6170 is the number of subcarriers excluding the DM-RS subcarriers and phase-tracking RS samples [TS38.211] in PUSCH symbol j and assuming no segmentation for nominal repetition when PUSCH transmission has repeating type B, which is TIFF2025111483000059.tif7170, ○ N is the total number of transmission opportunities of TBoMS

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

[0067] The BPRE calculation over multiple slots instead of one slot can save the effort of the UE that calculates the number of information bits in each slot. The transport block size (TBS) over all slots of TBoMS is much easier to obtain. In option 2 of the sixth embodiment, UE112 only calculates N RE at the first transmission opportunity. This can be used for a Type - A like TBoMS that has the same N RE at each transmission opportunity. Option 1 of the sixth embodiment can be considered for a TBoMS like Type - B.

[0068] Another parameter is the PUSCH power control adjustment state f b,f,c (i, l) for the active UL BWP b of carrier f of serving cell c at PUSCH transmission opportunity i, which is determined according to the following excerpt from 3GPP TS38.213 rev.16.4.0, section 7.1.1 in Rel - 16. *****Start of excerpt from 3GPP TS38.213***** The PUSCH power control adjustment state f b,f,c (i, l) for the active UL BWP b of carrier f of serving cell c at PUSCH transmission opportunity i - δ PUSCH,b,f,c(i, l) is included in the DCI format that schedules the PUSCH transmission opportunity i on the active UL BWP b of carrier f in serving cell c, or is jointly coded with other TPC commands in DCI format 2_2 with a CRC scrambled by TPC-PUSCH-RNTI as described in Section 11.3, and is the TPC command value - When twoPUSCH-PC-AdjustmentStates is configured for the UE, l ∈ {0, 1}; when twoPUSCH-PC-AdjustmentStates is not configured for the UE, or when PUSCH transmission is scheduled by the RAR UL grant described in Section 8.3, l = 0 - For PUSCH (re)transmission configured by ConfiguredGrantConfig, the value of l ∈ {0, 1} is provided to the UE by powerControlLoopToUse - When the UE is provided with SRI-PUSCH-PowerControl, the UE obtains the mapping between the set of values for the SRI field in the DCI format that schedules PUSCH transmission and the (one or more) l values provided by sri-PUSCH-ClosedLoopIndex, and determines the l value mapped to the SRI field value - When PUSCH transmission is scheduled by a DCI format that does not include an SRI field, or when SRI-PUSCH-PowerControl is not provided to the UE, l = 0 - When the UE obtains one TPC command from DCI format 2_2 with a CRC scrambled by TPC-PUSCH-RNTI, the l value is provided by the closed-loop indicator field in DCI format 2_2 - TIFF2025111483000061.tif11170 is the PUSCH power control adjustment state l for the 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 value is given in Table 7.1.1-1 - TIFF2025111483000062.tif10170 is the sum of the TPC command values of cardinality C(D PUSCH (i - i0)-1 symbols before the PUSCH transmission opportunity i - i0 and K PUSCH (i) symbols before the PUSCH transmission opportunity i that the UE receives on the active UL BWP b of carrier f of serving cell c for the PUSCH power control adjustment state l i ) in the set D of TPC command values, where i0 > 0 is the smallest integer such that the K i (i - i0) symbols before the PUSCH transmission opportunity i - i0 are earlier than the K PUSCH (i) symbols before the PUSCH transmission opportunity i PUSCH - When PUSCH transmission is scheduled by DCI format, K (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 PUSCH transmission PUSCH - When PUSCH transmission is configured by ConfiguredGrantConfig, K (i) is the number of symbols per slot for the active UL BWP b of carrier f of serving cell c PUSCH - Equal to the product of TIFF2025111483000063.tif7170 and the minimum value provided by k2 in PUSCH-ConfigCommon, K The number of symbols is PUSCH,min - - The UE reaches the maximum power for the active UL BWP b of carrier f of serving cell c at PUSCH transmission opportunity i - i0, if TIFF2025111483000064.tif10170, then f b,f,c (i, l) = f b,f,c (i - i0, l) - The UE reaches the minimum power for the active UL BWP b of carrier f of serving cell c at PUSCH transmission opportunity i - i0, if TIFF2025111483000065.tif11170, then f b,f,c (i, l) = f b,f,c (i - i0, l) - The UE resets the accumulation of the PUSCH power control adjustment state l for the active UL BWP b of carrier f of serving cell c to f b,f,c (k, l) = 0, k = 0, 1,..., i - For the corresponding P O_UE_PUSCH,b,f,c if the setting for the (j) value is provided by the upper layer, - For the corresponding α b,f,c if the setting for the (j) value is provided by the upper layer, where l is - j > 1 and the UE is provided with upper SRI - PUSCH - PowerControl, then l is the (one or more) sri - PUSCH - ClosedLoopIndex values set in any SRI - PUSCH - PowerControl with the sri - P0 - PUSCH - AlphaSetId value corresponding to j - j > 1 and the UE is not provided with SRI - PUSCH - PowerControl or j = 0, then l = 0 - j = 1, then l is provided by the value of powerControlLoopToUse 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 the 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 The absolute value is given in Table 7.1.1-1 Table 7.1.1-1: Absolute and cumulative δ of the TPC command field in the DCI format for scheduling PUSCH, 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 value TIFF2025111483000066.tif32170*****End of excerpt from 3GPP TS38.213*****

[0069] In the seventh embodiment, when the UE112 is provided with tpc-Accumulation, i.e., when TPC accumulation is disabled, the 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. · The absolute power offset is ○ The 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 the set of symbols / slots before the first slot for TBoMS transmission Determined by the latest TPC command received before · (When multiple TBoMS PUSCH opportunities are used for power calculation for one TBoMS transmission) The absolute power offset for power calculation for transmission in a TBoMS PUSCH opportunity is ○ The start of the first slot of the TBoMS PUSCH opportunity for TBoMS transmission ○ Start of the first symbol of the first slot of the TBoMS PUSCH opportunity for TBoMS or TBoMS transmission ○ Start of the set of symbols / slots before the first slot of the TBoMS PUSCH opportunity for TBoMS or TBoMS transmission Determined by the most recent TPC command received before

[0070] In the eighth embodiment, when the UE 112 is not provided with tpc-Accumulation, that is, when TPC accumulation is enabled, the accumulated power offset will be used for power adjustment, and one or more of the following rules can be applied to determine the power adjustment for TBoMS in each slot, where the bold underlined text indicates the Rel-16 K in Section 7.1.1 of 3GPP TS38.213 rev.16.4.0 PUSCH Indicates a change to the calculation. · The accumulated power offset is on the active UL BWP b of carrier f of serving cell c for PUSCH power control adjustment state l, before the PUSCH transmission opportunity i - i0, K PUSCH (i - i0) - 1 symbols, and before the PUSCH transmission opportunity i, K PUSCH (i) symbols, determined by the set of TPC commands received between them, where i0 > 0 is the smallest integer such that the K PUSCH (i - i0) symbols are earlier than the K PUSCH (i) symbols - When PUSCH transmission is scheduled by a DCI format, K 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 TBoMS transmission - When PUSCH transmission is configured by a ConfiguredGrantConfig, K PUSCH(i) is the number of symbols per slot for the active UL BWP b of carrier f in serving cell c K, which is equal to the product of TIFF2025111483000067.tif7170 and the minimum value provided by k2 in PUSCH-ConfigCommon PUSCH,min is the number of symbols · (when multiple TBoMS PUSCH opportunities are used for power calculation for one TBoMS transmission) The cumulative power offset is on the active UL BWP b of carrier f in serving cell c for PUSCH power control adjustment state l, and is K before the PUSCH transmission opportunity i - i0 PUSCH (i - i0) - 1 symbols, and K before the PUSCH transmission opportunity i PUSCH is determined by the set of TPC commands received between (i) symbols, where i0 > 0 and the K PUSCH (i - i0) symbols are the earliest and smallest integer before the K PUSCH (i) symbols - When PUSCH transmission is scheduled by a DCI format, K PUSCH (i) is the number of symbols for the active UL BWP b of carrier f in 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 - When PUSCH transmission is configured by ConfiguredGrantConfig, K PUSCH (i) is the number of symbols per slot for the active UL BWP b of carrier f in serving cell c K, which is equal to the product of TIFF2025111483000068.tif7170 and the minimum value provided by k2 in PUSCH-ConfigCommon PUSCH,min is the number of symbols

[0071] Additional explanation FIG. 3 is a flowchart showing the operation of a wireless communication device 112 (e.g., UE) according to at least some of the embodiments described above. As shown, the wireless communication device 112 determines the transmission power for TBoMS uplink transmission for each TBoMS transmission opportunity (step 300). The transmission 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 are not 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 transmission power for TBoMS uplink transmission for each TBoMS transmission opportunity (step 302).

[0072] Figure 4 is a schematic block diagram of a network node 400 according to some embodiments of the present disclosure. Optional features are represented by dashed boxes. The network node 400 can be, for example, a base station 102 or 106, or a network node implementing all or part of the functionality of the base station 102 or 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 circuitry. Further, 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 part of the functionality of the base station 102 or gNB), the network node 400 can 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 unit 410 can be referred to as, or be part of, a radio interface circuit. In some embodiments, the (one or more) radio units 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 (one or more) radio units 410 and potentially the (one or more) antennas 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 gNB described herein). In some embodiments, the (one or more) functions are implemented in software, for example, stored in the memory 406 and executed by the one or more processors 404.

[0073] FIG. 5 is a schematic block diagram showing a virtualized embodiment of network node 400 according to some embodiments of the present disclosure. Again, optional features are represented by the dashed boxes. As used herein, a "virtualized" network node is an implementation of network node 400 in which at least a portion of the functionality of network node 400 is implemented as one or more virtual components (e.g., via one or more virtual machines running on one or more physical processing nodes in one or more networks). As shown, in this example, if network node 400 is a radio access node, 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 one or more radio units 410 via, for example, an optical cable. Network node 400 includes one or more processing nodes 500 coupled to one or more networks 502 or included as part of one or more networks 502. If present, the control system 402 or the one or more radio units are connected to the one or more processing nodes 500 via network 502. Each processing node 500 includes one or more processors 504 (e.g., CPU, ASIC, FPGA, etc.), a memory 506, and a network interface 508.

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

[0075] In some embodiments, when executed by at least one processor, a computer program is provided that includes instructions for causing at least one processor to perform the functionality of a network node 400 or node (e.g., processing node 500) that implements one or more of the functionality 510 of network node 400 in a virtual environment, according to 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 memory, such as a non-transitory computer-readable medium).

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

[0077] FIG. 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, ASIC, 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 (one or more) transceivers 706 include a radio front-end circuit connected to the (one or more) antennas 712 and configured to condition signals communicated between the (one or more) antennas 712 and the (one or more) processors 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 functions of the wireless communication device 112 (or UE) described above may be implemented entirely or partially by software stored in the memory 704 and executed by the (one or more) processors 702. Note 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., an input / output interface including a display, buttons, a touch screen, a microphone, the (one or more) speakers, etc., and / or any other components that enable input of information to 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, when executed by at least one processor, a computer program is provided that includes instructions to cause the at least one processor to perform the functions of the wireless communication device 112 according to 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).

[0079] FIG. 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 (one or more) modules 800 provide the functions of the wireless communication device 112 (or UE) described herein.

[0080] Referring to FIG. 9, according to one embodiment, a communication network 900, such as a 3GPP type cellular network, includes an access network 902, such as a RAN, and a core network 904. The access network 902 includes a plurality of base stations 906A, 906B, 906C, such as Node B, eNB, gNB, or other types of wireless access points (APs), each defining a corresponding coverage area 908A, 908B, 908C. Each base station 906A, 906B, 906C is connectable 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 is wirelessly connectable to the corresponding base station 906A. Although a plurality of UEs 912, 914 are shown in this example, the disclosed embodiments are equally applicable to situations where only one UE is in the coverage area or only one UE is connected to the corresponding base station 906.

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

[0082] The communication system of FIG. 9 enables connectivity between the connected UEs 912, 914 and the host computer 916. The connectivity can be described as an over-the-top (OTT) connection 924. The host computer 916 and the 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 network 922, and possibly additional infrastructure (not shown) as a medium. The OTT connection 924 can 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 informed or need to be informed about the past routing of an incoming downlink communication with data originating from the host computer 916 that is 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 an outgoing uplink communication 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 one embodiment will be described with reference to FIG. 10. In communication system 1000, host computer 1002 comprises hardware 1004 including a communication interface 1006 configured to set up and maintain a wired or wireless connection with an interface of different communication devices of communication system 1000. Host computer 1002 further comprises a processing circuit 1008 that may have storage capabilities and / or processing capabilities. In particular, processing circuit 1008 may comprise one or more programmable processors, ASICs, FPGAs, or combinations thereof (not shown) adapted to execute instructions. Host computer 1002 further comprises software 1010 stored in or accessible by host computer 1002 and executable by processing circuit 1008. Software 1010 includes host application 1012. Host application 1012 may be operable to provide services to remote users such as UE 1014 that is connected via an OTT connection 1016 terminating at UE 1014 and host computer 1002. When providing services to a remote user, host application 1012 may provide user data transmitted using OTT connection 1016.

[0084] The communication system 1000 further includes a base station 1018 provided in the communication system, and the base station 1018 includes hardware 1020 that enables the base station 1018 to communicate with the host computer 1002 and the UE 1014. The hardware 1020 includes a communication interface 1022 for setting up and maintaining a wired or wireless connection with an interface of different communication devices in the communication system 1000, and a wireless interface 1024 for setting up and maintaining at least a wireless connection 1026 with the 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 a processing circuit 1030, and the processing circuit 1030 may include 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 radio interface 1036 configured to set up and maintain a radio connection 1026 with a base station serving the coverage area where 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 comprises 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 may be operable to provide services to human or non-human users via the UE 1014 with the support of the host computer 1002. In the host computer 1002, the running host application 1012 may communicate with the running client application 1042 via the OTT connection 1016 that terminates at the UE 1014 and the host computer 1002. When providing services to the 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 provided by the client application 1042.

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

[0087] In FIG. 10, the OTT connection 1016 is abstractly depicted to show communication between the host computer 1002 and the UE 1014 via the base station 1018 without an explicit mention of the mediation device and the exact routing of messages through these devices. The network infrastructure may determine the routing, which may be set 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 further make a determination to dynamically change the routing (e.g., based on network load distribution considerations or reconfiguration).

[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 services provided to the UE 1014 using the OTT connection 1016 that forms the last segment.

[0089] Measurement procedures can be provided for the purpose of monitoring data rate, latency, and other factors that one or more embodiments improve. There may further be optional network functions for reconfiguring the OTT connection 1016 between the host computer 1002 and the UE 1014 in response to variations in the measurement results. The measurement procedures and / or the network functions for reconfiguring the OTT connection 1016 can 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) can be deployed in or in relation to the communication device through which the OTT connection 1016 passes, and the sensors can participate in the measurement procedures by providing values of the monitored quantities exemplified above or by providing values of other physical quantities that the software 1010, 1040 can calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 1016 can include message format, retransmission settings, preferred routing, etc., and the reconfiguration need not affect the base station 1018 and can be unknown or imperceptible to the base station 1018. Such procedures and functions are known and practiced in the art. In some embodiments, the measurement can involve proprietary UE signaling that facilitates measurement of the host computer 1002, such as throughput, propagation time, latency, etc. The measurement can be implemented in that the software 1010 and 1040 cause the software 1010 and 1040 to transmit messages, particularly empty or "dummy" messages, using the OTT connection 1016 while monitoring propagation time, errors, etc.

[0090] FIG. 11 is a flowchart showing a method implemented in a communication system according to one embodiment. The communication system may include a host computer, a base station, and a UE as described with reference to FIGS. 9 and 10. For simplicity of the present disclosure, only the drawing reference to FIG. 11 is included in this section. At step 1100, the host computer provides user data. In an optional sub-step 1102 of step 1100, the host computer provides user data by executing a host application. At step 1104, the host computer initiates a transmission to carry the user data to the UE. At an optional step 1106, the base station transmits the user data carried in the transmission initiated by the host computer to the UE according to the teachings of the embodiments described throughout the present disclosure. At an optional step 1108, the UE executes a client application related to the host application executed by the host computer.

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

[0092] FIG. 13 is a flowchart showing a method implemented in a communication system according to an embodiment. The communication system may include a host computer, a base station, and a UE, as described with reference to FIGS. 9 and 10. For simplicity of the present disclosure, only the drawing reference to FIG. 13 is included in this section. In optional step 1300, the UE receives input data provided by the host computer. Additionally or alternatively, in step 1302, the UE provides user data. In optional sub-step 1304 of step 1300, the UE provides user data by executing a client application. In optional sub-step 1306 of step 1302, the UE executes a client application that provides user data in response to the received input data provided by the host computer. When providing user data, the executed client application may further consider user input received from the user. Regardless of the particular manner in which the user data is provided, the UE starts transmitting the user data to the host computer in optional sub-step 1308. In step 1310 of the method, the host computer receives the user data transmitted from the UE according to the teachings of the embodiments described throughout the present disclosure.

[0093] FIG. 14 is a flowchart showing a method implemented in a communication system according to an embodiment. The communication system may include a host computer, a base station, and a UE, as described with reference to FIGS. 9 and 10. For simplicity of the present disclosure, only the drawing reference to FIG. 14 is included in this section. In optional step 1400, according to the teachings of the embodiments described throughout the present disclosure, the base station receives user data from the UE. In optional step 1402, the base station starts transmitting the received user data to the host computer. In optional step 1404, 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 in this specification 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 a processing circuit, which may include one or more microprocessors or microcontrollers, and other digital hardware which may include a digital signal processor (DSP), application specific digital logic, etc. The processing circuit may be configured to execute program code stored in a 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, etc. The program code stored in the memory includes program instructions for executing one or more communication and / or data communication protocols, as well as instructions for performing one or more of the techniques described in this specification. In some implementations, the processing circuit may be used to cause each functional unit to perform corresponding functions according to one or more embodiments of the present disclosure.

[0095] Although the processes in the figures may show a particular order of operations implemented by some embodiments of the present disclosure, it should be understood that such order is 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. All such improvements and modifications are contemplated within the scope of the concepts disclosed herein.

Claims

1. A method performed by a wireless communication device (112), the method comprising: determining (300) a transmission power for Transport Block over Multiple Slots (TB oMS) uplink transmission for each TB oMS transmission opportunity over a plurality of slots; transmitting (302) the TB oMS uplink transmission according to the transmission power; and a method comprising.

2. The method according to claim 1, wherein the transmission power is a linear transmission power.

3. The method according to claim 1 or 2, wherein the TB oMS uplink transmission is a TB oMS Physical Uplink Shared Channel (PUSCH) transmission.

4. One TB oMS transmission opportunity of the TB oMS uplink transmission is defined as part of the TB oMS uplink transmission within one slot, and the TB oMS transmission opportunity is a slot index within a frame having a system frame number SFN and a first symbol S within the slot, and a number L of consecutive symbols of the TB oMS uplink transmission within the slot, according to any one of claims 1 to 3.

5. The method according to any one of claims 1 to 3, wherein one TB oMS transmission opportunity of the TB oMS uplink transmission extends over two or more consecutive slots of the TB oMS uplink transmission.

6. One TB oMS transmission opportunity of the TB oMS uplink transmission is an index of a first slot of the TB oMS transmission opportunity having a system frame number SFN and a first symbol S within the first slot of the TB oMS transmission opportunity, and a number L of consecutive symbols of the TB oMS uplink transmission within the first slot, or a total number L of symbols of the TB oMS uplink transmission in the transmission opportunity, according to claim 5.

7. The method according to any one of claims 1 to 3, wherein one TB oMS transmission opportunity of the TboMS uplink transmission extends over two or more consecutive or non-consecutive slots of the TboMS uplink transmission.

8. One TB oMS transmission opportunity of the TB oMS uplink transmission is an index of a first slot of the TB oMS transmission opportunity having a system frame number SFN and a method according to claim 7, defined by 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 over a plurality of slots of the TBoMS uplink transmission.

9. The method according to any one of claims 1 to 3, wherein all slots for the TBoMS uplink transmission are treated as a single TBoMS transmission opportunity.

10. The method according to any one of claims 1 to 3, wherein a set of all slots for the 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.

11. The wireless communication device (112) supports two or more options regarding 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 transmission power for the TboMS uplink transmission for each TboMS transmission opportunity is set by a network node or determined in advance. The method according to any one of claims 1 to 10.

12. One TBoMS transmission opportunity covers two or more slots, and determining (300) the transmission power for the TBoMS uplink transmission for each TBoMS transmission opportunity is determining the transmission power for the TBoMS transmission opportunity, where the transmission power is equivalent to the transmission power determined for the first slot of the TBoMS transmission opportunity and the same transmission power is maintained until the end of the TBoMS transmission opportunity, determining the transmission power for the TBoMS transmission opportunity, or determining the transmission power for the TBoMS transmission opportunity considering the two or more slots of the TBoMS transmission opportunity as a whole The method according to any one of claims 1 to 3 or 5 to 11, including any of the above.

13. Certain parameters are different for at least two of the two or more slots of the TB oMS transmission opportunity, and determining (300) the transmission power for the TB oMS transmission opportunity includes determining the transmission power for the TB oMS transmission opportunity based on the certain parameters for one or more fixed ones of the two or more slots of the TB oMS transmission opportunity. The method according to claim 12.

14. Whether a change in transmission power is allowed during the TB oMS uplink transmission is either set by a network node or determined in advance. The method according to any one of claims 1 to 13.

15. Whether a change in transmission power is allowed between repetitions of the TB oMS uplink transmission is either set by a network node or determined in advance. The method according to any one of claims 1 to 14.

16. The transmission power is interdependent with one or more other characteristics. The method according to claim 14 or 15.

17. The transmission power is interdependent with cross-slot channel estimation. The method according to claim 16.

18. The transmission power varies between TB oMS transmission opportunities for the TB oMS uplink transmission based on one or more parameters. The method according to any one of claims 14 to 17.

19. The one or more parameters include (a) the data-to-demodulation reference signal (DMRS) ratio in each slot, (b) the group common transmission power control (TPC) command, (c) the reference signal, (d) the path loss estimation, (e) the PUSCH power control adjustment state, or (f) any combination of two or more of (a) to (e). The method according to claim 18.

20. The same transmission power is set or determined in advance across the plurality of slots of the TB oMS uplink transmission, and the wireless communication device (112) determines the transmission power before transmission based on the transmission power in the first slot and keeps the transmission power the same until the end of the TB oMS uplink transmission. The method according to any one of claims 1 to 19.

21. - 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 the next transmission after the TBoMS uplink transmission, and / or - The wireless communication device (112) does not expect each base station (102) to change the reference signal and its transmission power that the wireless communication device (112) uses to estimate the downlink path loss during the TBoMS uplink transmission, and / or - The wireless communication device (112) does not perform downlink path loss measurement from the physical layer during the TBoMS uplink transmission, and / or - The wireless communication device (112) does not expect the PUSCH power control adjustment state l to be changed by RRC or DCI signaling during the TBoMS uplink transmission, The method according to claim 20.

22. Determining the transmission power for the TBoMS uplink transmission for each TBoMS transmission opportunity (300) includes calculating one or more TBoMS transmission opportunity related parameters, according to any one of claims 1 to 21. The method described.

23. The one or more TBoMS transmission opportunity related parameters are (I) MCS related parameter Δ ＴＦ，ｂ，ｆ，ｃ (i), (II) BPRE, (III) 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 ｂ，ｆ，ｃ The method according to claim 22, comprising (i, l), or (IV) any two or more combinations of (I) to (III).

24. The method according to claim 22, wherein the one or more TBoMS transmission opportunity related parameters include BPRE.

25. The BPRE is The BRE for the multi-slot PUSCH with UL-SCH, calculated over the plurality of slots of the TBoMS, Here, N ＲＥ is The number of resource elements over the plurality of slots of the TBoMS, determined as, where N is the total number of transmission opportunities of the TBoMS, Is the number of symbols for the PUSCH transmission opportunity i on the active UL BWP b of the carrier f of the serving cell c, Is the number of subcarriers excluding the DM-RS subcarriers and the phase tracking RS samples in the PUSCH symbol j, Is The method according to claim 24.

26. wherein the BPRE is a BRE for a multi-slot PUSCH with UL-SCH, calculated over the plurality of slots of the TBoMS as where -N ＲＥ is is the number of resource elements determined as, where i = 0, 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 the DM-RS subcarriers and the phase-tracking RS samples [TS38.211] in PUSCH symbol j, and assuming no segmentation for nominal repetition when the PUSCH transmission has repeating type B, is - N is the total number of the transmission opportunities of the TBoMS, The method according to claim 24.

27. Determining (300) the transmission power for the TBoMS uplink transmission for each transmission opportunity of the TBoMS, wherein TPC accumulation is disabled and an absolute power offset value is used for power adjustment, includes determining an absolute power adjustment in each slot of the TBoMS uplink transmission, according to any one of claims 1 to 26.

28. wherein the absolute power adjustment is · at the start of the first slot for the TBoMS uplink transmission, or · at the start of the first scheduled symbol of the first slot for the TBoMS uplink transmission, or · at the start of the symbol or set of symbols preceding the first slot for the TBoMS uplink transmission determined by the latest TPC command received before, according to the method of claim 27.

29. where a plurality of TBoMS transmission opportunities are used for power calculation for the TBoMS uplink transmission, and the absolute power adjustment for determining the transmission power in one TBoMS transmission opportunity is · at the start of the first slot of the TBoMS transmission opportunity, or · at the start of the first symbol of the first slot of the TBoMS transmission opportunity, or · at the start of the symbol or set of symbols preceding the first slot of the TBoMS transmission opportunity determined by the latest TPC command received before, according to the method of claim 27.

30. TPC accumulation is enabled, a cumulative power offset value is used for power adjustment, and determining (300) the transmission power for the TBoMS uplink transmission for each TBoMS transmission opportunity over a plurality of slots includes determining cumulative power adjustment in each slot of the TBoMS uplink transmission, the method according to any one of claims 1 to 26.

31. TPC accumulation is enabled, the accumulated power offset value is used for power adjustment, and determining (300) the transmission power for the TBoMS uplink transmission for each TBoMS transmission opportunity, on the active uplink bandwidth part b of carrier f of serving cell c for PUSCH power control adjustment state l, for TBoMS transmission opportunity i - i ０ before K ＰＵＳＣＨ of (i - i ０ ) - 1 symbols, and the K ＰＵＳＣＨ before TBoMS transmission opportunity i of (i) symbols, determining the cumulative power adjustment at the TBoMS transmission opportunity of the TBoMS uplink transmission, where i ０ > 0 is the smallest integer earlier than the K ０ before PUSCH transmission opportunity i - i ＰＵＳＣＨ of (i - i ０ ) symbols, which is earlier than the K ＰＵＳＣＨ before PUSCH transmission opportunity i of (i) symbols, the method according to any one of claims 1 to 26.

32. When PUSCH transmission is scheduled by a downlink control information (DCI) format, K ＰＵＳＣＨ The method according to claim 31, wherein (i) is the number of symbols for the active uplink bandwidth part 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.

33. TPC accumulation is enabled, the accumulated power offset value is used for power adjustment, a plurality of TBoMS transmission opportunities are used for power calculation for one TBoMS transmission, and determining (300) the transmission power for the TBoMS uplink transmission for each TBoMS transmission opportunity is performed on the active uplink bandwidth part b of carrier f of serving cell c for PUSCH power control adjustment state l, for PUSCH transmission opportunity i - i ０ the previous K ＰＵＳＣＨ of (i - i ０ ) - 1 symbols and the previous K ＰＵＳＣＨ of (i) symbols of PUSCH transmission opportunity i, and determining the cumulative power adjustment at the TBoMS transmission opportunity of the TBoMS uplink transmission based on a set of TPC commands received between them, where i ０ > 0 is the smallest integer earlier than the previous K ０ of (i - i ＰＵＳＣＨ ) symbols of PUSCH transmission opportunity i - i ０ than the previous K ＰＵＳＣＨ of (i) symbols of PUSCH transmission opportunity i, the method according to any one of claims 1 to 26.

34. When PUSCH transmission is scheduled by a downlink control information (DCI) format, K ＰＵＳＣＨ The method according to claim 33, wherein (i) is the number of symbols for the active uplink bandwidth part 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.

35. A wireless communication device (112), determining (300) the transmission power for the TBoMS uplink transmission for each TBoMS transmission opportunity over a plurality of slots; and transmitting (302) the TBoMS uplink transmission according to the transmission power A wireless communication device (112) adapted to perform.

36. The wireless communication device (112) according to claim 35, further adapted to implement the method according to any one of claims 2 to 34.

37. A wireless communication device (112), one or more transmitters (708); one or more receivers (710); a processing circuit (702) associated with the one or more transmitters (708) and the one or more receivers (710), wherein the processing circuit (702) causes the wireless communication device (112) to determine (300) the transmission power for the TBoMS uplink transmission for each TBoMS transmission opportunity over a plurality of slots; and transmit (302) the TBoMS uplink transmission according to the transmission power A wireless communication device (112) configured to perform.

38. The wireless communication device (112) according to claim 37, wherein the processing circuit (702) is further configured to cause the wireless communication device (112) to implement the method according to any one of claims 2 to 34.

Images