Physical Uplink Control Channel (PUCCH) Power Control for Multiple Transmission and Reception Points (TRPs)

Abstract

A method, system and apparatus for physical uplink control channel (PUCCH) power control for multiple transmission / reception points (TRPs) are disclosed. According to one aspect, the method in a network node includes configuring a wireless device (WD) with a list of at least two power control parameter sets for PUCCH power control applicable to at least one of at least one PUCCH resource and at least one PUCCH resource group. The method also includes transmitting a medium access control (MAC) control element (CE) to the WD to activate at least one power control parameter set from the list of power control parameter sets applicable to at least one of (1) the PUCCH resource, (2) each of the multiple PUCCH resources, and (3) the multiple PUCCH resource groups.

Description

Technical Field

[0001] The present disclosure relates to wireless communication, and in particular, to physical uplink control channel (PUCCH) power control for a plurality of transmit and receive points (TRPs).

Background Art

[0002] NR Frame Structure and Resource Grid The New Radio (NR, also called the 5th generation or 5G) of the 3rd Generation Partnership Project (3GPP) uses cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) for both downlink (DL) (i.e., from a network node (gNB) or base station to a wireless device (WD, also called a user equipment or UE)) and uplink (UL) (i.e., from WD to gNB). In the uplink, discrete Fourier transform (DFT) spread OFDM is also supported. In the time domain, the downlink and uplink of NR are each organized into subframes of equal size of 1 millisecond (ms). The subframe is further divided into a plurality of slots of the same length. The length of the slot depends on the subcarrier spacing. When the subcarrier spacing Δf = 15 kHz, there is only one slot per subframe, and each slot is composed of 14 OFDM symbols.

[0003] NR data scheduling is usually slot-based, and an example of a 14-symbol slot is shown in FIG. 1. The first two symbols contain the physical downlink control channel (PDCCH), and the rest contain either the physical shared data channel (PDSCH (physical downlink shared channel) or PUSCH (physical uplink shared channel)).

[0004] NR supports different subcarrier spacings. The supported subcarrier spacing values (also called different numerologies) are given by the following formula. Δf=(15×2 μ) kHz, where μ ∈ {0, 1, 2, 3, 4}. Δf = 15 kHz is the basic sub - carrier spacing. The slot duration for different sub - carrier spacings is 1 / 2 μ ms.

[0005] In the frequency domain, the system bandwidth is divided into resource blocks (RBs), each corresponding to 12 consecutive sub - carriers. RBs are numbered from 0 in order from one end of the system bandwidth. The basic NR physical time - frequency resource grid is shown in Figure 2, where only one resource block (RB) within 14 symbol slots is shown. One OFDM sub - carrier in one OFDM symbol interval forms one resource element (RE).

[0006] Downlink (DL) PDSCH transmission is either dynamically scheduled slot - by - slot or semi - permanently scheduled (SPS). Dynamic PDSCH scheduling is performed by transmitting downlink control information (DCI) on the PDCCH (Physical Downlink Control Channel). In NR, different DCI formats are defined for DL PDSCH scheduling, such as DCI format 1_0, DCI format 1_1, DCI format 1_2, etc. In the case of SPS, periodic PDSCH transmission is activated or deactivated by DCI.

[0007] Similarly, uplink (UL) PUSCH transmission may also be scheduled dynamically or semi - permanently with an uplink grant carried on the PDCCH. DCI formats for scheduling PUSCH include DCI format 0_0, DCI format 0_1, DCI format 0_2.

[0008] Physical Uplink Control Channel (PUCCH) In NR, PUCCH is used to transmit uplink control information (UCI) such as hybrid automatic repeat request acknowledgement (HARQ - ACK), channel state information (CSI), scheduling request (SR), etc.

[0009] In NR, five PUCCH formats, namely PUCCH formats 0 to 4, are defined, each having a different payload capacity and duration. In WD, multiple PUCCH resources are configured, each associated with a PUCCH format.

[0010] Spatial relationship is used in NR to refer to the spatial relationship between an UL channel or signal such as PUCCH, PUSCH, or sounding reference signal (SRS), and a DL reference signal (RS) such as CSI reference signal (CSI-RS), synchronization signal (SS), physical broadcast channel block (SSB), or UL sounding reference signal (SRS). When an UL channel is spatially related to a DL RS, the WD is expected to transmit the UL channel with the same antenna pattern or beam for receiving the DL RS. When an UL channel is spatially related to an UL SRS, the WD is expected to apply the same antenna pattern or beam to the UL channel and the SRS.

[0011] Up to 64 PUCCH spatial relationships are configured for the WD. For each PUCCH resource, one of the spatial relationships is activated or updated by a command transmitted in a media access control (MAC) control element (CE).

[0012] Note that PUCCH spatial relationships may not be configured in the frequency NR range 1 (FR1). In that case, a default relationship may be defined.

[0013] The PUCCH spatial relationship information element (IE) that can be configured for the WD for an NR UL bandwidth part (BWP) is provided below. This includes one of the SSB index, CSI-RS resource index, and SRS resource index, and several power control parameters such as the path loss reference RS index, P0-PUCCH index, and closed-loop index. PUCCH - Spatial Relationship Information Information Element --ASN1START --TAG-PUCCH-SPATIALRELATIONINFO-START PUCCH-SpatialRelationInf ::= SEQUENCE { pucch-SpatialRelationInfoId, servingCellId ServCellIndex OPTIONAL, --Need S referenceSignal CHOICE { ssb-Index SSB-Index, csi-RS-Index NZP-CSI-RS-ResourceId, srs PUCCH-SRS }, pucch-PathlossReferenceRS-Id, p0-PUCCH-Id, closedLoopIndex ENUMERATED { i0, i1} } PUCCH-SpatialRelationInfoExt-r16 ::= SEQUENCE { pucch-SpatialRelationInfoId-v1610 OPTIONAL, --Cond SetupOnly pucch-PathlossReferenceRS-Id-v1610 OPTIONAL, --Need R ... } PUCCH-SRS ::= SEQUENCE { resource SRS-ResourceId, uplinkBWP BWP-Id } --TAG-PUCCH-SPATIALRELATIONINFO-STOP --ASN1STOP

[0014] To speed up UL beam selection at frequency 2 (FR2), a unified Transmit Configuration Indicator (TCI) framework that replaces the spatial relationship in UL is currently under discussion in 3GPP's NR Release 17. The TCI state is used in NR to indicate the so-called Quasi-Co-Location (QCL) characteristics between the DL source RS and the DL target RS. If the WD knows that two signals are QCL with respect to a parameter (e.g., Doppler spread), the WD can estimate that parameter based on one signal and apply that estimated value to receive the other signal. Four types of QCL relationships are defined: - Type A: {Doppler shift, Doppler spread, average delay, delay spread}; - Type B: {Doppler shift, Doppler spread}; - Type C: {average delay, Doppler shift}; - Type D: {spatial Rx parameter}.

[0015] The TCI state can contain up to two types of QCL information. The IE of the TCI state is shown below. When two QCL types are shown, one of them is QCL of type D. TCI-State Information Element --ASN1START --TAG-TCI-STATE-START TCI-State ::= SEQUENCE { tci-StateId, qcl-Type1 QCL-Info, qcl-Type2 QCL-Inf · OPTIONAL, --Need R ... } QCL-Inf ·::= SEQUENCE { cell ServCellIndex OPTIONAL, --Need R bwp-Id BWP-Id OPTIONAL, --Cond CSI-RS-Indicated referenceSignal CHOICE { csi-rs NZP-CSI-RS-ResourceId, ssb SSB-Index }, qcl-Type ENUMERATED {typeA, typeB, typeC, typeD}, ... } --TAG-TCI-STATE-STOP --ASN1STOP

[0016] When a unified TCI framework is introduced, it is assumed that TCI states are used to indicate spatial relationships in UL. TCI states may be defined separately for UL and DL, or a common TCI state may be defined for both DL and UL.

[0017] PUCCH Power Control in NR PUCCH power control is used to determine an appropriate PUCCH transmission power level in WD. Generally, power control has two parts: open-loop power control and closed-loop power control. Open-loop power control is used to set the uplink transmission power based on the estimated downlink path loss (PL) between the gNB and WD, the target received power, the PUCCH format, the uplink control information (UCI) payload, etc.

[0018] Closed-loop power control is based on the transmission power control (TPC) command received from the gNB. The closed-loop adjustment at a given time is also called the power control adjustment state.

[0019] The downlink path loss is estimated based on the DL RS and is equal to the difference between the transmitted power and the received power measured at the DL RS in WD. The DL RS is called the DL path loss reference RS. The DL path loss reference RS is either CSI-RS or SSB.

[0020] When the WD uses the PUCCH power control adjustment state with index l (l = 0, 1) to transmit the PUCCH on the PUCCH resource of the active UL BWPb of carrier f in the primary cell c, the WD determines the PUCCH transmission power P PUCCH,b,f,c (i, q u , q d , l) of the PUCCH transmission opportunity i as follows: TIFF0007712386000001.tif13170 Here, P CMAX,f,c (i) is the maximum output power of the WD configured for carrier f of the primary cell c at the PUCCH transmission opportunity i, as defined in Section 8-1 of 3GPP TS38.101-1, Section 8-2 of 3GPP TS38.101-2, and Section 8-3 of 3GPP TS38.101-3. P open-loop,b,f,c (i, q u , q d ) is open-loop power adjustment and is given by the following formula: TIFF0007712386000002.tif24170 Here, ·P O_PUCCH,b,f,c (q u ) = P O_NOMINAL_PUCCH + P O_UE_PUCCH (q u ) is the nominal target received power in dBm. ·P O_NOMINAL_PUCCH is the cell-specific component, and P O_UE_PUCCH (q u ) is the WD-specific component. P O_NOMINAL_PUCCH is provided by the upper-layer parameter p0-nominal, or P O_NOMINAL_PUCCH = 0 if p0-nominal is not configured. P O_UE_PUCCH (q u ) is provided by the upper-layer parameter p0-PUCCH-Value of P0-PUCCH having index q u for the active UL BWPb of carrier f in the primary cell c, where 0 ≤ q u < Q u and Q uis the size of the set of P0-PUCCH provided by the upper layer parameter maxNrofPUCCH-P0-perSet. The set of P0-PUCCH is provided by the upper layer parameter p0-Set as shown in the following PUCCH power control information elements: · If p0-Set is not configured, P O_UE_PUCCH (q u ) = 0; · P RB (i) is the power adjustment related to the number of RBs occupied in transmission opportunity i; · PL b,f,c (q d ) is the path loss in dB estimated by WD using the PUCCH path loss reference RS with index q for the active DL BWPb of carrier f of primary cell c; d · Δ (F) is the power adjustment depending on the PUCCH format; F_PUCCH · Δ (i) is the power adjustment related to the PUCCH resource on the active UL BWPb of carrier f of primary cell c. TF,b,f,c

[0021] P closed-loop (i, l) is the closed-loop power adjustment and is given by the following formula: TIFF0007712386000003.tif9170 Here, · g b,f,c (i, l) is the PUCCH power control adjustment state with index l for the active UL BWPb of carrier f of primary cell c in PUCCH transmission opportunity i; · δ PUCCH,b,f,c(i, l) is the TPC command value included in the DCI format (i.e., DCI format 1_0, 1_1, or 1_2) that schedules PDSCH reception for the active UL BWP b of carrier f of primary cell c that WD detects for PUCCH transmission, or is coded jointly with other TPC commands in DCI format 2_2 scrambled by TPC-PUCCH-RNTI according to clause 11.3 of 3GPP TS36.212. ·Σ m=0 M δ PUCCH,b,f,c (i, m) is the sum of the TPC command values received by WD between the K (i - i0) - 1 symbols before the PUCCH transmission opportunity i - i0 and the K (i) symbols before the PUCCH transmission opportunity i on the active UL BWP b of carrier f of primary cell c for the PUCCH power control adjustment state having index l, where i0 > 0 is the smallest integer such that the K (i - i0) - 1 symbols before the PUCCH transmission opportunity i - i0 are earlier than the K (i) symbols before the PUCCH transmission opportunity i. If the PUCCH transmission is in response to the detection of a DCI format by WD, K (i) is the number of symbols after the last symbol of the corresponding PDCCH reception and before the first symbol of the PUCCH transmission. Otherwise, K (i) = k · N, where k is the minimum number of slots configured between the PDCCH and its scheduled PUSCH, and N is the number of symbols in a slot. PUCCH (i - i0) - 1 symbols before the PUCCH transmission opportunity i - i0 and the K PUCCH (i) symbols before the PUCCH transmission opportunity i, and here, i0 > 0 is the smallest integer such that the K PUCCH (i - i0) - 1 symbols before the PUCCH transmission opportunity i - i0 are earlier than the K PUCCH (i) symbols before the PUCCH transmission opportunity i. If the PUCCH transmission is in response to the detection of a DCI format by WD, K PUCCH (i) is the number of symbols after the last symbol of the corresponding PDCCH reception and before the first symbol of the PUCCH transmission. Otherwise, K PUCCH (i) = k 2,min ·N symb slot and here, k 2,min is the minimum number of slots configured between the PDCCH and its scheduled PUSCH, and N symb slot is the number of symbols in a slot.

[0022] Closed-loop index l, PUCCH path loss reference RS index q d and P0-PUCCH index q uIt is configured with the PUCCH spatial relation as shown in the above IE, which is activated for the PUCCH resource.

[0023] If the WD does not provide two PUCCH-PC-AdjustmentStates or PUCCH-SpatialRelationInfo, l = 0.

[0024] If the WD is not provided with PUCCH-SpatialRelationInfo, the WD obtains the p0-PUCCH-Value value from the P0-PUCCH whose p0-PUCCH-Id value is equal to the minimum p0-PUCCH-Id value of the p0-Set.

[0025] If the WD is not provided with PUCCH-SpatialRelationInfo but a set of PUCCH path loss RSs is configured, the PUCCH path loss reference RS of the first entry in the list (i.e., index = 0) may be used.

[0026] If neither the PUCCH path loss reference RS nor the PUCCH-SpatialRelationInfo is configured, but the WD is configured with enableDefaultBeamPlForPUCCH, the path loss reference RS is a periodic RS resource with "QCL-TypeD" of the TCI state of the control resource set (CORESET) with the smallest index in the active DL BWP of the primary cell.

[0027] If the WD does not provide the pathlossReferenceRS, the path loss reference RS may be an SS / PBCH block having the same SSB index as that used by the WD to obtain the master information block (MIB).

[0028] The PUCCH power control related parameters are notified to the WD by the PUCCH-PowerControl information element shown below. PUCCH - Power Control Information Element --ASN1START --TAG-PUCCH-POWERCONTROL-START PUCCH-PowerControl ::= SEQUENCE { deltaF-PUCCH-f0 INTEGER (-16..15) OPTIONAL, --Need R deltaF-PUCCH-f1 INTEGER (-16..15) OPTIONAL, --Need R deltaF-PUCCH-f2 INTEGER (-16..15) OPTIONAL, --Need R deltaF-PUCCH-f3 INTEGER (-16..15) OPTIONAL, --Need R deltaF-PUCCH-f4 INTEGER (-16..15) OPTIONAL, --Need R p0-Set SEQUENCE (SIZE (1..maxNrofPUCCH-P0-PerSet)) OF P0-PUCCH OPTIONAL, --Need M pathlossReferenceRSs SEQUENCE (SIZE (1..maxNrofPUCCH-PathlossReferenceRSs)) OF PUCCH-PathlossReferenceRS OPTIONAL, --Need M twoPUCCH-PC-AdjustmentStates ENUMERATED {twoStates} OPTIONAL, --Need S ..., pathlossReferenceRSs-v1610 SetupRelease { PathlossReferenceRSs-v1610} OPTIONAL --Need M } P0-PUCCH ::= SEQUENCE { p0-PUCCH-Id, ​​p0 - PUCCH - Value INTEGER (-16..15) } P0 - PUCCH - Id ::= INTEGER (1..8) PathlossReferenceRSs - v1610 ::= SEQUENCE (SIZE (1..maxNrofPUCCH - PathlossReferenceRSsDiff - r16)) OF PUCCH - PathlossReferenceRS - r16 PUCCH - PathlossReferenceRS ::= SEQUENCE { pucch - PathlossReferenceRS - Id, referenceSignal CHOICE { ssb - Index SSB - Index, csi - RS - Index NZP - CSI - RS - ResourceId } } PUCCH - PathlossReferenceRS - r16 ::= SEQUENCE { pucch - PathlossReferenceRS - Id - r16 PUCCH - PathlossReferenceRS - Id - v1610, referenceSignal - r16 CHOICE { ssb - Index - r16 SSB - Index, csi - RS - Index - r16 NZP - CSI - RS - ResourceId } } --TAG - PUCCH - POWERCONTROL - STOP --ASN1STOP

[0029] UL Transmission to Multiple Transmit Points (TRP) In 3GPP's NR Release 17, it is being considered to introduce UL enhancements with multiple TRPs by transmitting PUCCH towards different TRPs at different times or by repeatedly transmitting PUCCH to multiple TRPs. An example is shown in FIG. 3.

[0030] In 3GPP Release 17 of NR (3GPP Release 17), it is considered that two SRS resource sets, configured in a "codebook" or "non-codebook", are introduced for PUSCH repetition to two TRPs. Since the propagation channels to two TRPs can be quite different, in 3GPP's RAN1, for PUCCH repetition to multiple TRPs in FR1, two sets of power control parameters are used, and it is considered that each set has dedicated values for p0, path loss reference RS_ID, and closed-loop index. The related considerations are shown below: "To support per-TRP power control for the PUCCH scheme with multi-TRP in FR1: · Two sets of power control parameters are used, and each set is configured with dedicated values for p0, path loss RS_ID, and closed-loop index; · Future study item (FFS): Details of how to link PUCCH resources to one or both of the two power control parameters. · FFS: Whether PUCCH resource groups can be linked to power control parameter sets."

Summary of the Invention

[0031] Some embodiments advantageously provide a method, system, and apparatus for PUCCH power control towards multiple TRPs.

[0032] In one embodiment, the network node is configured to transmit a Media Access Control (MAC) Control Element (CE) to the WD, and the MAC_CE indicates an association between i) one of a Physical Uplink Control Channel (PUCCH) resource and a PUCCH resource group, and ii) at least one first PUCCH power control parameter set among a plurality of PUCCH power control parameter sets; Optionally, receive a PUCCH transmission from the WD on one of the PUCCH resource and the PUCCH resource group, and the PUCCH transmission includes a transmission power level based on at least one first PUCCH power control parameter set associated with one of the PUCCH resource and the PUCCH resource group.

[0033] In one embodiment, a Wireless Device (WD) is configured to receive a Media Access Control (MAC) Control Element CE, and the MAC_CE indicates an association between i) one of a Physical Uplink Control Channel (PUCCH) resource and a PUCCH resource group, and ii) at least one first PUCCH power control parameter set among a plurality of PUCCH power control parameter sets; Optionally, transmit a PUCCH transmission on one of the PUCCH resource and the PUCCH resource group, and the PUCCH transmission includes a transmission power level based on at least one first PUCCH power control parameter set associated with one of the PUCCH resource and the PUCCH resource group.

[0034] According to one aspect, a method in a network node comprises configuring, in a WD, a list of at least two power control parameter sets for physical uplink control channel (PUCCH) power control, applicable to at least one of at least one PUCCH resource and at least one PUCCH resource group. The process also comprises transmitting, to the WD, a media access control (MAC) control element (CE) to activate at least one power control parameter set from a list of power control parameter sets applicable to at least one of (1) one PUCCH resource, (2) each one of a plurality of PUCCH resources, and (3) a plurality of PUCCH resource groups.

[0035] According to this aspect, in some embodiments, each of the lists of at least two power control parameter sets includes a PUCCH path loss reference signal identifier (ID), a target received power (P0-PUCCH) ID, a closed-loop index, and a power control parameter set ID. In some embodiments, the method also includes constructing a WD having PUCCH repetitions to at least one transmission and reception point (TRP) associated with at least one of the at least two power control parameter sets. In some embodiments, the MAC_CE includes a PUCCH resource identifier that includes two bit fields, each bit field identifying a respective PUCCH power control parameter set from a list of at least two control parameter sets. In some embodiments, the MAC_CE includes a bit field indicating whether one of two PUCCH power control sets and a single PUCCH power control set is activated for at least one of (1) one PUCCH resource, (2) each one of a plurality of PUCCH resources, and (3) a plurality of PUCCH resource groups. In some embodiments, the MAC_CE includes: an octet spatial relationship information ID field that identifies a spatial relationship activated for one PUCCH resource of a plurality of PUCCH resources and one PUCCH resource of a plurality of PUCCH resource groups identified by the PUCCH resource index field of the previous octet.In some embodiments, the MAC_CE includes: a field E in the first octet indicating whether the PUCCH resource is updated by a spatial relationship or a power control set; a PUCCH resource index field in the second octet identifying one of the PUCCH resources from a plurality of PUCCH resources and the PUCCH resources from a plurality of PUCCH resource groups; a third octet following the second octet, the third octet including a spatial relationship information identifier (ID) field identifying a spatial relationship and an S field identifying a PUCCH power control parameter set; and based at least in part on the value configured in the E field, one of the spatial relationship and the S field is activated for one of the PUCCH resources and the PUCCH resource groups identified by the PUCCH resource index field in the second octet. In some embodiments, at least two PUCCH spatial relationships are configured for WD, and each PUCCH spatial relationship includes a PUCCH path loss reference identifier (ID), P0-PUCCH_ID, and a closed-loop index. In some embodiments, the MAC_CE includes a bandwidth part (BWP) field, a serving cell identifier (ID) field in the first octet, a field indicating whether one of a first set and a second set of PUCCH power control parameters is activated, a 7-bit PUCCH resource index field in the second octet, and a dedicated field for each of the second set of PUCCH power control parameters in the third octet. In some embodiments, each PUCCH power control parameter set includes power control parameters for calculating the PUCCH transmission power for WD towards the corresponding transmit-receive point (TRP) associated with the network node.

[0036] According to another aspect, a network node configured to communicate with a wireless device includes: a processing circuit configured to configure a list of at least two power control parameter sets for physical uplink control channel (PUCCH) power control applicable to at least one of at least one PUCCH resource and at least one PUCCH resource group for the WD; and a radio interface configured to communicate with the processing circuit and transmit a media access control (MAC) control element (CE) to the WD to activate at least one power control parameter set from a list of power control parameter sets applicable to at least one of (1) one PUCCH resource, (2) each one of a plurality of PUCCH resources, and (3) a plurality of PUCCH resource groups.

[0037] According to this aspect, in some embodiments, each of the lists of at least two power control parameter sets includes a PUCCH path loss reference signal identifier (ID), a target received power (P0-PUCCH) ID, a closed-loop index, and a power control parameter set ID. In some embodiments, the processing circuit is configured to configure a WD having PUCCH repetitions to at least one transmission and reception point (TRP) associated with at least one of the at least two power control parameter sets. In some embodiments, the MAC_CE includes a PUCCH resource identifier that includes two bit fields, each bit field identifying a respective PUCCH power control parameter set from a list of at least two control parameter sets. In some embodiments, the MAC_CE includes a bit field indicating whether one of two PUCCH power control sets and a single PUCCH power control set is activated for at least one of (1) one PUCCH resource, (2) each one of a plurality of PUCCH resources, and (3) a plurality of PUCCH resource groups. In some embodiments, the MAC_CE includes: an octet spatial relationship information ID field that identifies a spatial relationship activated for one PUCCH resource of a plurality of PUCCH resources and one PUCCH resource of a plurality of PUCCH resource groups identified by the PUCCH resource index field of the previous octet.In some embodiments, the MAC_CE includes: a field E in the first octet indicating whether the PUCCH resource is updated by a spatial relationship or a power control set; a PUCCH resource index field in the second octet identifying one of the PUCCH resources from a plurality of PUCCH resources and the PUCCH resources from a plurality of PUCCH resource groups; a third octet following the second octet, the third octet including a spatial relationship information identifier (ID) field identifying the spatial relationship and an S field identifying the PUCCH power control parameter set; and, based at least in part on the value configured in the E field, one of the spatial relationship and the S field is activated for one of the PUCCH resources and the PUCCH resource groups identified by the PUCCH resource index field in the second octet, the third octet. In some embodiments, at least two PUCCH spatial relationships are configured for WD, and each PUCCH spatial relationship includes a PUCCH path loss reference identifier (ID), P0-PUCCH_ID, and a closed-loop index. In some embodiments, the MAC_CE includes a bandwidth part (BWP) field, a serving cell identifier (ID) field in the first octet, a field indicating whether one of a set and a second set of PUCCH power control parameters is activated, a 7-bit PUCCH resource index field in the second octet, and a dedicated field for each of the two sets of PUCCH power control parameters in the third octet. In some embodiments, each PUCCH power control parameter set includes power control parameters for calculating the PUCCH transmission power for WD towards the corresponding transmit-receive point (TRP) associated with the network node.

[0038] According to yet another aspect, a method in a wireless device includes receiving a list of at least two power control parameter sets for physical uplink control channel (PUCCH) power control applicable to at least one of at least one PUCCH resource and at least one PUCCH resource group. The process also includes setting a transmission power level based at least in part on at least one of the at least two power control parameter sets in the list.

[0039] In some embodiments, each of the lists of at least two power control parameter sets includes a PUCCH path loss reference signal identifier (ID), a target received power (P0-PUCCH) ID, a closed loop index, and a power control parameter set ID. In some embodiments, the method also includes constructing a WD (22) with PUCCH repetitions to each TRP associated with at least one of the at least two power control parameter sets for at least one transmit receive point (TRP). In some embodiments, the MAC_CE includes a PUCCH resource identifier that includes two bit fields, each bit field identifying a respective PUCCH power control parameter set from a list of at least two control parameter sets. In some embodiments, the MAC_CE includes a bit field indicating whether one of two PUCCH power control sets and a single PUCCH power control set is activated for at least one of (1) one PUCCH resource, (2) each one of a plurality of PUCCH resources, and (3) a plurality of PUCCH resource groups. In some embodiments, the MAC_CE includes: an octet spatial relationship information ID field that identifies a spatial relationship activated for one PUCCH resource of a plurality of PUCCH resources and one PUCCH resource of a plurality of PUCCH resource groups identified by the PUCCH resource index field of the previous octet.In some embodiments, the MAC_CE includes: a field E in the first octet indicating whether the PUCCH resource is updated by a spatial relationship or a power control set; a PUCCH resource index field in the second octet identifying one of the PUCCH resources from a plurality of PUCCH resources and the PUCCH resources from a plurality of PUCCH resource groups; a third octet following the second octet, the third octet including a spatial relationship information identifier (ID) field identifying a spatial relationship and an S field identifying a PUCCH power control parameter set; and, based at least in part on the value configured in the E field, one of the spatial relationship and the S field is activated for one of the PUCCH resources and PUCCH resource groups identified by the PUCCH resource index field in the second octet, the third octet. In some embodiments, the MAC_CE is further configured to constitute at least two PUCCH spatial relationships, and each PUCCH spatial relationship includes a PUCCH path loss reference identifier (ID), P0-PUCCH_ID, and a closed-loop index. In some embodiments, the MAC_CE includes a bandwidth part (BWP) field, a serving cell identifier (ID) field in the first octet, a field indicating whether one of a set and a second set of PUCCH power control parameters is activated, a 7-bit PUCCH resource index field in the second octet, and dedicated fields for each of the two sets of PUCCH power control parameters in the third octet. In some embodiments, each PUCCH power control parameter set includes power control parameters for calculating the PUCCH transmission power for the WD towards the corresponding transmission and reception point (TRP) associated with the network node.

[0040] According to another aspect, a wireless device configured to communicate with a network node, comprising: a wireless interface configured to receive a list of at least two power control parameter sets for physical uplink control channel (PUCCH) power control, which is applied to at least one of at least one PUCCH resource and at least one PUCCH resource group; and a processing circuit configured to communicate with the wireless interface and set a transmission power level based at least in part on at least one of the at least two power control parameter sets in the list.

[0041] In some embodiments, each of the lists of at least two power control parameter sets comprises a PUCCH path loss reference signal identifier (ID), a target received power (P0-PUCCH) ID, a closed loop index, and a power control parameter set ID. In some embodiments, the processing circuitry is also configured to construct a WD having PUCCH repetitions to at least one TRP associated with at least one of the at least two power control parameter sets. In some embodiments, the MAC_CE includes a PUCCH resource identifier that includes two bit fields, each bit field identifying a respective PUCCH power control parameter set from a list of at least two control parameter sets. In some embodiments, the MAC_CE includes a bit field indicating whether one of two PUCCH power control sets and a single PUCCH power control set is activated for at least one of (1) one PUCCH resource, (2) each one of a plurality of PUCCH resources, and (3) a plurality of PUCCH resource groups. In some embodiments, the MAC_CE includes: an octet spatial relationship information ID field that identifies a spatial relationship activated for one PUCCH resource of a plurality of PUCCH resources and one PUCCH resource of a plurality of PUCCH resource groups identified by the PUCCH resource index field of the previous octet.In some embodiments, the MAC_CE includes: a field E in a first octet indicating whether a PUCCH resource is updated by a spatial relationship or a power control set; a PUCCH resource index field in a second octet identifying one of the PUCCH resources from a plurality of PUCCH resources and the PUCCH resources from a plurality of PUCCH resource groups; a third octet following the second octet, the third octet including a spatial relationship information identifier (ID) field identifying a spatial relationship and an S field identifying a PUCCH power control parameter set; and, based at least in part on a value configured in the E field, one of the spatial relationship and the S field is activated for one of the PUCCH resources and PUCCH resource groups identified by the PUCCH resource index field in the second octet, the third octet. In some embodiments, the MAC_CE is further configured to constitute at least two PUCCH spatial relationships, and each PUCCH spatial relationship includes a PUCCH path loss reference identifier (ID), P0-PUCCH_ID, and a closed-loop index. In some embodiments, the MAC_CE includes a bandwidth part (BWP) field, a serving cell identifier (ID) field in the first octet, a field indicating whether one of a set and a second set of PUCCH power control parameters is activated, a 7-bit PUCCH resource index field in the second octet, and dedicated fields for each of the two sets of PUCCH power control parameters in the third octet. In some embodiments, each PUCCH power control parameter set includes power control parameters for calculating PUCCH transmission power for a WD directed to a corresponding transmit-receive point (TRP) associated with a network node.

Brief Description of Drawings

[0042] A more complete understanding of the present embodiment, as well as the attendant advantages and features, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings:

[0043]

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

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

DETAILED DESCRIPTION OF THE INVENTION

[0044] In NR's 3GPP Release 15 / 16 (3GPP Release 15 / 16), the PUCCH spatial relationship may not be configured in FR1, and the WD can assume a P0-PUCCH with a closed-loop index of l = 0, a P0-PUCCH of a p0-Set with the minimum p0-PUCCH-Id value, and a PUCCH path loss reference RS with an index = 0. For PUCCH repetition for multiple TRPs and in the case of two sets of power control parameters configured in FR1, how to link the PUCCH resource to one of the two sets is an unsolved problem.

[0045] Some embodiments may include a configuration for linking and / or associating a PUCCH resource to one of two (or more) sets of PUCCH power control parameters, typically in FR1 when the PUCCH spatial relationship is not configured. In some embodiments, the two sets of PUCCH power control parameters may be explicitly configured such that each set is identified by a set index value. Each PUCCH resource may be activated / updated with MAC_CE using one or both of the sets of PUCCH power control parameters.

[0046] In some embodiments, for PUCCH repetition towards multiple TRPs where the PUCCH spatial relationship is not configured, two (or more) sets of PUCCH power control parameters are explicitly configured (e.g., in the PUCCH power control IE) by a set index or, more specifically, a set index value. In some embodiments, for each PUCCH resource (or PUCCH resource group), MAC_CE is used to link the PUCCH resource (or PUCCH resource group) to one or both of the two sets of PUCCH power control parameters.

[0047] In one embodiment, the MAC_CE consists of a 2-bit BWP field, a 5-bit serving cell identifier (ID) field, and a first reserved bit in the first octet, a 7-bit PUCCH resource index field, and a second reserved bit in the second octet, and one or more of 1-bit dedicated fields for each of two sets of PUCCH power control parameters in the third octet. A set is activated (or linked, or associated) with a PUCCH resource (or PUCCH resource group) if the corresponding field is set to 1, and deactivated (or unlinked, or dissociated) if the corresponding field is set to 0.

[0048] In another embodiment, the above applies only if the first reserved bit is set to 1. Otherwise, the fields for the two sets of power control parameters are ignored.

[0049] Alternatively, or additionally, the second reserved bit is used to indicate whether the third octet exists. If the third octet does not exist (e.g., if the second reserved bit is set to 0), both sets are activated (or deactivated) when the first reserved bit is set to 1 (or 0).

[0050] In yet another embodiment, the MAC_CE is composed of one or more of a 2-bit BWP field, a 5-bit serving cell ID field, a 1-bit first set indicator field in the first octet, a 7-bit PUCCH resource index field, and a 1-bit second set indicator field in the second octet. When the first set indicator field is set to 1, the PUCCH resource (or PUCCH resource group) is activated in both of the two sets, and the second bit field is ignored. When the first bit field is set to 0, the second bit field is used to activate one of the two sets of PUCCH resources (or PUCCH resource groups).

[0051] In some embodiments, when both of the two sets are activated for a PUCCH resource, the PUCCH transmission scheduled on the PUCCH resource is repeated towards two or more TRPs at different times. For example, the first set is applied to the PUCCH transmission opportunity to the first TRP, and the second set is applied to the PUCCH transmission opportunity to the second TRP.

[0052] Some embodiments can enable per-TRP PUCCH power control for different TRPs, especially when the PUCCH spatial relationship is not configured.

[0053] Before describing the exemplary embodiments in detail, it should be noted that the embodiments mainly exist in combinations of apparatus components and processing steps related to PUCCH power control for multiple TRPs. Therefore, the components are represented in the drawings as needed by conventional symbols that show only the specific details relevant to the understanding of the embodiments, so as not to obscure the disclosure by details that would be readily apparent to those skilled in the art having the advantages of the description herein. Like numbers refer to like elements throughout the specification.

[0054] As used herein, relational terms such as "first" and "second", "upper" and "lower" are used only to distinguish one entity or element from another entity or element, and do not necessarily require or imply a physical or logical relationship or order between such entities or elements. The terms used herein are for the purpose of describing particular embodiments only and are not intended to limit the concepts described herein. As used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. As used herein, the terms "comprises", "comprising", "includes", and / or "including" identify the presence of the described features, integers, steps, operations, elements, and / or components, but it will be further understood that they do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0055] In the embodiments described herein, conjunctive terms such as "in communication with" may be used to indicate electrical or data communication, which may be achieved, for example, by physical contact, induction, electromagnetic radiation, wireless signaling, infrared signaling, or optical signaling. Those skilled in the art will understand that modifications and variations are possible for multiple components to interact and achieve electrical and data communication.

[0056] In some embodiments described herein, terms such as "coupled", "connected" may be used herein to indicate a connection, although not necessarily a direct one, and may include a wired connection and / or a wireless connection.

[0057] As used herein, the term "network node" refers to a base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g-node B (gNB), evolved node B (eNB or eNodeB), node B, multi-standard radio (MSR) radio nodes such as BS of MSR, multi-cell / multicast coordination entity (MCE), integrated access / backhaul (IAB) node, relay node, donor node controlling the relay, wireless access point (AP), transmission point, transmission node, remote radio unit (RRU), remote radio head (RRH), core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, coordination node, positioning node, MDT node, etc.), external node (third-party node, node external to the current network, etc.), node of a distributed antenna system (DAS), spectrum access system (SAS) node, element management system (EMS), etc. Also, the network node may constitute a test apparatus. The term "wireless device" as used herein may also be used to denote a wireless device (WD) such as a wireless device (WD) or a user equipment (UE).

[0058] In some embodiments, the non-limiting terms wireless device (WD) or user equipment (UE) are used interchangeably. A WD herein can be any type of wireless device capable of communicating with a network node or another WD via wireless signals, such as a wireless device (WD). A WD can also be a wireless communication device, a target device, a device-to-device (D2D) WD, a machine type WD or a WD capable of machine-to-machine (M2M) communication, a low-cost and / or low-complexity WD, a sensor with a WD, a tablet, a mobile terminal, a smartphone, a laptop embedded equipment (LEE), a laptop-mounted equipment (LME), a USB dongle, a customer premise equipment (CPE), an Internet of Things (IoT) device, or a narrowband IoT (NB-IoT) device, etc.

[0059] Also, in some embodiments, the general term "radio network node" is used. This can be any kind of radio network node that can constitute a base station, a radio base station, a base transceiver station, a base station controller, a network controller, an RNC, an evolved Node B (eNB), a Node B, a gNB, a multi-cell / multicast coordination entity (MCE), an IAB node, a relay node, an access point, a wireless access point, a remote radio unit (RRU), or a remote radio head (RRH).

[0060] Although the description herein may be presented in the context of either downlink (DL) communication or uplink (UL) communication, it should be understood that the disclosed basic principles are also applicable to the other context of DL communication and UL communication. In some embodiments of the present disclosure, the principles are considered applicable to transmitters and receivers. In DL communication, the network node is the transmitter and the receiver is the WD. In the case of UL communication, the transmitter is the WD and the receiver is the network node.

[0061] Although this specification may describe things in the context of the PUCCH channel, it should be understood that the principles are also applicable to other channels such as, for example, the PUSCH.

[0062] The term "signaling" as used herein can include either upper layer signaling (e.g., via radio resource control (RRC), etc.), lower layer signaling (e.g., via a physical control channel or a broadcast channel), or a combination thereof. Signaling can be either implicit or explicit. Signaling can further be unicast, multicast, or broadcast. Also, signaling can be done directly to other nodes or via a third node.

[0063] Signaling generally consists of one or more symbols and / or signals and / or messages. A signal can consist of, or can be represented by, one or more bits. An indication represents signaling and / or can be implemented as a signal or as multiple signals. One or more signals may be included in, and / or represented by, a message. Signaling, particularly control signaling, may consist of multiple signals and / or messages, which may be transmitted on different carriers and / or may be associated with different signaling processes, for example, representing and / or relating to one or more such processes and / or corresponding information. An indication may consist of signaling and / or multiple signals and / or messages and / or be configured therein, which may be transmitted on different carriers and / or may be associated with different acknowledgment signaling processes, for example, representing one or more such processes and / or relating to such processes. Signaling related to a channel may be transmitted so as to represent signaling and / or information for that channel and / or so that the signaling is interpreted as belonging to that channel by a transmitter and / or receiver. Such signaling may generally conform to the transmission parameters and / or format of the channel.

[0064] An indication can generally indicate, explicitly and / or implicitly, the information it represents and / or indicates. An implicit indication can be based at least in part, for example, on the location and / or resources used for transmission. An explicit indication may be based at least in part, for example, on a parametrization having one or more parameters and / or one or more indexes or indices corresponding to a table and / or one or more bit patterns representing information.

[0065] Configuring a wireless node, particularly a terminal or a WD (e.g., a WD), may refer to the wireless node being adapted, or caused, or set, and / or instructed to operate according to the configuration. The configuration may be performed by another device, such as a network node (e.g., a network node) (e.g., a base station or a gNB) or a network, in which case it may consist of transmitting configuration data to the wireless node to be configured. Such configuration data may represent the configuration to be configured and / or may constitute one or more instructions related to the configuration for transmitting and / or receiving on the configured, e.g., allocated resources (particularly frequency resources). The wireless node may be able to configure itself, for example, based on the configuration data received from the network or a network node. The network node may utilize its circuitry / equipment for configuration and / or may be adapted to utilize it. The allocation information can be regarded as a form of configuration data. The configuration data may be composed of, and / or represented by, configuration information and / or one or more corresponding indications and / or messages.

[0066] Generally, configuring may include determining configuration data representing the configuration and providing it to one or more other nodes (in parallel and / or sequentially), for example transmitting it, and these nodes may further transmit it to a wireless node (or to another node, which may be repeated until reaching a wireless device). Alternatively or additionally, for example, configuring a wireless node by a network node or other device may include receiving configuration data and / or data related to the configuration data from another node, such as a network node which may be a higher-level node of the network, and / or transmitting the received configuration data to the wireless node. Thus, the determination of the configuration and the transmission of the configuration data to the wireless node may be performed by different network nodes or entities, and these nodes can communicate via an appropriate interface (for example, the X2 interface in the case of LTE or the corresponding interface for NR). Configuring a terminal (e.g., a WD) may include scheduling downlink and / or uplink transmissions for the terminal, for example, downlink data and / or downlink control signaling and / or DCI and / or uplink control or data or communication signaling, especially acknowledgment signaling, and / or configuring resources and / or resource pools. In particular, configuring a terminal (e.g., a WD) may include configuring the WD to perform specific measurements on a specific subframe or wireless resource and report such measurements, according to embodiments of the present disclosure.

[0067] Downlink transmission may relate to the transmission from a network or a network node to a terminal. The terminal may be regarded as a WD or a UE. Uplink transmission may relate to the transmission from a terminal to a network or a network node. Sidelink transmission may relate to the (direct) transmission from one terminal to another terminal. Uplink, downlink and sidelink (e.g., sidelink transmission and reception) may be regarded as communication directions. In some variants, uplink and downlink may also be used to describe wireless communication between network nodes, e.g., wireless backhaul and / or relay communication and / or (wireless) network communication, e.g., communication between base stations or similar network nodes, in particular, communication terminated by such communication. Backhaul and / or relay communication and / or network communication are considered to be implemented in the form of sidelink communication or a form similar thereto or an uplink communication.

[0068] As used herein, the term time or time resource may correspond to any type of physical resource or radio resource represented by a length of time. Examples of time resources are symbols, time slots, sub-slots, sub-frames, radio frames, TTIs, interleaving times, etc. As used herein, in some embodiments, the terms "sub-frame", "slot", "sub-slot", "sub-frame / slot", and "time resource" are used interchangeably and are intended to indicate a time resource and / or a time resource number.

[0069] A cell is generally a communication cell of a cellular communication network or a mobile communication network provided by a node. A serving cell is a cell in which a network node (a node providing the cell or a node related to the cell, such as a base station or a gNodeB) can send data (which may be data other than broadcast data) to a user equipment (in particular, control data and / or user data or payload data), and / or the user equipment can send data to the node. A serving cell may also be a cell in which the user equipment is configured, and / or synchronized, and / or an access procedure (for example, when the node and / or the user equipment and / or the network comply with the LTE or NR standard, the serving cell is a cell in which the user equipment is set, and / or synchronized, and / or an access procedure (such as a random access procedure) is executed, and / or the user equipment is in the RRC_connected or RRC_idle state. One or more carriers (for example, an uplink carrier and / or a downlink carrier / or both uplink and downlink carriers) may be associated with a cell.

[0070] In cellular communication, at least one uplink (UL) connection and / or channel and / or carrier and at least one downlink (DL) connection and / or channel and / or carrier are considered to be provided, for example, via and / or as defined by a cell, which may be provided by a network node, in particular a base station or a gNodeB. The uplink direction may refer to the data transfer direction from a terminal to a network node, such as a base station and / or a relay station. The downlink direction may refer to the data transfer direction from a network node, such as a base station and / or a relay node, to a terminal. The UL and DL may be associated with different frequency resources, such as carriers and / or spectral bands. A cell may consist of at least one uplink carrier and at least one downlink carrier, which may have different frequency bands. A network node, such as a base station or a gNodeB, may be adapted to provide and / or define and / or control one or more cells, such as PC cells and / or LA cells.

[0071] Defined in the context of the present disclosure means that the relevant information is defined, for example, in a standard, and / or is available without a specific configuration from a network or a network node, for example, stored in a memory regardless of being configured. Configured or configurable is considered to relate to the corresponding information being set / configured by, for example, a network or a network node.

[0072] In the present disclosure, terms from certain wireless systems, such as, for example, 3GPP's LTE and / or New Radio (NR), may be used, but it should be noted that this should not be regarded as limiting the scope of the present disclosure to only the aforementioned systems. Other wireless systems, including but not limited to Wideband Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB), and Global System for Mobile Communications (GSM), may also benefit from utilizing the ideas covered within the present disclosure.

[0073] Furthermore, it should be noted that the functions described herein as being performed by a wireless device or a network node may be distributed among a plurality of wireless devices and / or network nodes. In other words, the functions of the network nodes and wireless devices described herein are not limited to being performed by a single physical device, and in fact, it is contemplated that they may be distributed among multiple physical devices.

[0074] Unless otherwise defined, all terms (including technical and scientific terms) used herein shall have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. Furthermore, the terms used herein shall be interpreted as having a meaning that is consistent with the context of this specification and the related art, and it is understood that they shall not be interpreted in an idealized or overly formal sense unless explicitly defined as such herein.

[0075] Some embodiments provide an arrangement for PUCCH power control towards multiple TRPs. Referring again to the drawings in which like elements are referred to by like reference numerals, FIG. 4 shows a schematic diagram of a communication system 10 according to an embodiment, such as a 3GPP type cellular network that may support standards such as LTE and / or NR (5G), which is composed of an access network 12, such as a radio access network, and a core network 14. The access network 12 is composed of a plurality of network nodes 16a, 16b, 16c (collectively referred to as network nodes 16), such as NB, eNB, gNB, or other types of radio access points, each defining a corresponding coverage area 18a, 18b, 18c (collectively referred to as coverage area 18). Each network node 16a, 16b, 16c can be connected to the core network 14 via a wired or wireless connection 20. A first wireless device (WD) 22a located in the coverage area 18a is configured to wirelessly connect to the corresponding network node 16a or be paged by the corresponding network node 16a. A second WD 22b in the coverage area 18b can be wirelessly connected to the corresponding network node 16b. Although a plurality of WDs 22a, 22b (collectively referred to as wireless devices 22) are illustrated in this example, the disclosed embodiments are equally applicable to situations where only one WD is within the coverage area or where only one WD is connected to the corresponding network node 16. For convenience, only two WDs 22 and three network nodes 16 are shown, but it should be noted that the communication system may include more WDs 22 and network nodes 16. The network node 16 is also referred to herein as TRP 16.

[0076] Also, it is contemplated that WD22 can communicate simultaneously and / or can be configured to communicate separately with a plurality of network nodes 16 and a plurality of types of network nodes 16. For example, WD22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, WD22 can communicate with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0077] The communication system 10 may itself be connected to a host computer 24, which may be embodied in hardware and / or software as a stand-alone server, a cloud-implemented server, a distributed server, or a processing resource within a server farm. The host computer 24 may be under the ownership or management of a service provider and may be operated by or on behalf of the service provider. The connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30. The intermediate network 30 may be one of a public, private, or hosted network, or a combination of two or more thereof. The intermediate network 30 may be, if any, a backbone network or the Internet. In some embodiments, the intermediate network 30 may be composed of two or more sub-networks (not shown).

[0078] The communication system of FIG. 4 enables a connection between either of the connected WD22a, 22b and the host computer 24 as a whole. This connectivity can be expressed as an over-the-top (OTT) connection. The host computer 24 and the connected WD22a, 22b are configured to communicate data and / or signaling via the OTT connection using the access network 12, the core network 14, any intermediate network 30, and possible further infrastructure (not shown) as a mediation. The OTT connection can be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of the routing of the uplink communication and the downlink communication. For example, the network node 16 may not be informed of or need to know about the past routing of the incoming downlink communication having data transmitted from the host computer 24 and transferred (e.g., delivered) to the connected WD22a. Similarly, the network node 16 does not need to recognize the future routing of the outgoing uplink communication transmitted from the WD22a towards the host computer 24.

[0079] The network node 16 is configured to include a configuration unit 32 configured to configure the WD with a list of at least two power control parameter sets for physical uplink control channel (PUCCH) power control applicable to at least one of at least one PUCCH resource and at least one PUCCH resource group.

[0080] The wireless device 22 is configured to include a power control unit 34 configured to set a transmission power level based at least in part on at least one of at least two power control parameter sets in the list.

[0081] Next, an implementation example according to an embodiment of the WD22, the network node 16, and the host computer 24 described in the previous paragraph will be described with reference to FIG. 5. In the communication system 10, the host computer 24 includes hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with interfaces of different communication devices of the communication system 10. The host computer 24 further includes a processing circuit 42 that can have storage and / or processing capabilities. The processing circuit 42 may include a processor 44 and a memory 46. In particular, in addition to or instead of a processor such as a central processing unit and a memory, the processing circuit 42 may include an integrated circuit for processing and / or control, for example, one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application specific integrated circuit) adapted to execute instructions. The processor 44 may be configured to access (e.g., write to and / or read from) the memory 46, and this memory 46 may be composed of any type of volatile and / or non-volatile memory, for example, cache and / or buffer memory and / or RAM (random access memory) and / or ROM (read only memory) and / or optical memory and / or EPROM (erasable programmable read only memory).

[0082] The processing circuit 42 can control any of the methods and / or processes described herein and / or cause such methods and / or processes to be executed, for example, by the host computer 24. The processor 44 corresponds to one or more processors 44 for executing the functions of the host computer 24 described herein. The host computer 24 includes a memory 46 configured to store data, program software code, and / or other information described herein. In some embodiments, the software 48 and / or the host application 50, when executed by the processor 44 and / or the processing circuit 42, can include instructions that cause the processor 44 and / or the processing circuit 42 to perform the processes described herein with respect to the host computer 24. The instructions may be software related to the host computer 24.

[0083] Software 48 may be executable by processing circuit 42. The software 48 includes a host application 50. The host application 50 may be operable to provide services to remote users such as WD22 connected via an OTT connection 52 that terminates at WD22 and host computer 24. When providing services to remote users, the host application 50 can provide user data transmitted using the OTT connection 52. "User data" may be the data and information described herein as implementing the described functionality. In one embodiment, the host computer 24 may be configured to provide control and functionality to a service provider and may be operated by or on behalf of the service provider. The processing circuit 42 of the host computer 24 can enable the host computer 24 to observe, monitor, control, transmit, and / or receive from the network node 16 and / or the wireless device 22. The processing circuit 42 of the host computer 24 can include a monitoring unit 54 configured to enable a service provider to observe, monitor, control, transmit to, and / or receive from the network node 16 and / or the wireless device 22.

[0084] The communication system 10 further includes a network node 16 provided in the communication system 10 and including hardware 58 that enables communication with the host computer 24 and the WD 22. The hardware 58 can include a communication interface 60 for setting and maintaining a wired or wireless connection with interfaces of different communication devices of the communication system 10, and a wireless interface 62 for setting and maintaining at least a wireless connection 64 with the WD 22 located within the coverage area 18 provided by the network node 16. The wireless interface 62 may be formed as, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers, or may include these. The communication interface 60 may be configured to facilitate a connection 66 to the host computer 24. The connection 66 may be direct, may pass through the core network 14 of the communication system 10, or may pass through one or more intermediate networks 30 external to the communication system 10.

[0085] In the illustrated embodiment, the hardware 58 of the network node 16 further includes a processing circuit 68. The processing circuit 68 may include a processor 70 and a memory 72. In particular, in addition to or instead of a processor such as a central processing unit and a memory, the processing circuit 68 may include an integrated circuit for processing and / or control, for example, one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application specific integrated circuit) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to and / or read from) the memory 72, and this memory 72 may be composed of any type of volatile and / or non-volatile memory, such as cache and / or buffer memory and / or RAM (random access memory) and / or ROM (read only memory) and / or optical memory and / or EPROM (erasable programmable read only memory).

[0086] Accordingly, network node 16 further has software 74 stored internally, for example, in memory 72 or in an external memory (such as a database, a storage array, a network storage device, etc.) accessible by network node 16 via an external connection. The software 74 may be executable by processing circuitry 68. The processing circuitry 68 may be configured to control any of the methods and / or processes described herein and / or to cause such methods and / or processes to be executed, for example, by network node 16. The processor 70 corresponds to one or more processors 70 for performing the functions of network node 16 described herein. The memory 72 is configured to store data, program software code, and / or other information described herein. In some embodiments, when executed by the processor 70 and / or the processing circuitry 68, the software 74 can include instructions that cause the processor 70 and / or the processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, the processing circuitry 68 of network node 16 can include a configuration unit 32 configured to configure a list of at least two power control parameter sets for physical uplink control channel (PUCCH) power control applicable to at least one of at least one PUCCH resource and at least one group of PUCCH resources to WD. In some embodiments, the configuration unit 32 is configured to perform the network node methods discussed herein, such as the methods discussed with reference to FIG. 10 as in the other figures.

[0087] The communication system 10 further includes the already mentioned WD22. The WD22 can have hardware 80 including a wireless interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 that provides a coverage area 18 where the WD22 is currently located. The wireless interface 82 may be formed as, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers, or may include them.

[0088] The hardware 80 of the WD22 further includes a processing circuit 84. The processing circuit 84 may include a processor 86 and a memory 88. In particular, in addition to or instead of a processor such as a central processing unit and a memory, the processing circuit 84 may include integrated circuits for processing and / or control, for example, one or more processors and / or processor cores and / or an FPGA (Field Programmable Gate Array) and / or an ASIC (Application Specific Integrated Circuit) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and / or read from) the memory 88, and this memory 88 may be composed of any kind of volatile and / or non-volatile memory, for example, cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read Only Memory).

[0089] Accordingly, WD22 may further include software 90 that is stored, for example, in the memory 88 of WD22 or in an external memory (such as a database, a storage array, a network storage device, etc.) accessible by WD22. The software 90 may be executable by the processing circuit 84. The software 90 may include a client application 92. The client application 92 may be operable to provide services to a human or non-human user via WD22 with the support of the host computer 24. In the host computer 24, the running host application 50 can communicate with the running client application 92 via the OTT connection 52 that terminates at WD22 and the host computer 24. In providing services to the user, the client application 92 can receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transfer both the request data and the user data. The client application 92 can interact with the user to generate the user data to be provided.

[0090] The processing circuit 84 may be configured to control any of the methods and / or processes described herein and / or to cause such methods and / or processes to be executed, for example, by WD22. The processor 86 corresponds to one or more processors 86 for executing the functions of WD22 described herein. WD22 includes a memory 88 configured to store the data, program software code, and / or other information described herein. In some embodiments, software 90 and / or client application 92, when executed by processor 86 and / or processing circuit 84, may include instructions that cause processor 86 and / or processing circuit 84 to perform the processes described herein with respect to WD22. For example, the processing circuit 84 of the wireless device 22 may include a power control unit 34 configured to set a transmission power level based at least in part on at least one of at least two sets of power control parameters in a list. In some embodiments, the power control unit 34 is configured to perform a WD method discussed herein, such as the method discussed with reference to FIG. 11, similar to other figures.

[0091] In some embodiments, the internal structures of network node 16, WD22, and host computer 24 may be as shown in FIG. 5, and independently, the surrounding network topology may be that of FIG. 4.

[0092] In FIG. 5, the OTT connection 52 is abstractly depicted to illustrate the communication between the host computer 24 and the wireless device 22 via the network node 16, and does not explicitly refer to the intermediary devices and the exact routing of messages through these devices. The network infrastructure can determine a routing that is configured to hide from the WD22, or from the service provider operating the host computer 24, or from both. While the OTT connection 52 is active, the network infrastructure can further make a decision to dynamically change the routing (e.g., based on load balancing considerations or network reconfiguration).

[0093] The wireless connection 64 between the WD22 and the network node 16 complies with 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 WD22 using the OTT connection 52 where the wireless connection 64 can form the last segment. More precisely, some of the teachings of these embodiments improve the data rate, latency, and / or power consumption, thereby providing advantages such as reduced user latency, relaxed file size limitations, improved responsiveness, extended battery life, etc.

[0094] In some embodiments, measurement procedures may be provided for the purpose of monitoring data rate, latency, and other factors that are improved by one or more embodiments. In response to fluctuations in the measurement results, there may further be optional network functions for reconfiguring the OTT connection 52 between the host computer 24 and the WD 22. The measurement procedures and / or the network functions for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24, the software 90 of the WD 22, or both. In an embodiment, a sensor (not shown) may be deployed within or in relation to a communication device through which the OTT connection 52 passes, and the sensor may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or by supplying values of other physical quantities from which the software 48, 90 can calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 52 can include message format, retransmission settings, priority routing, and the like. The reconfiguration need not affect the network node 16 and may be unknown or imperceptible to the network node 16. Some of such procedures and functions are known in the art and may be implemented. In certain embodiments, the measurement can include unique WD signaling that facilitates measurement of the host computer 24 such as throughput, propagation time, latency, and the like. In some embodiments, the measurement may be performed such that the software 48, 90 causes messages, particularly empty messages or "dummy" messages, to be transmitted using the OTT connection 52 while monitoring propagation time, errors, and the like.

[0095] Accordingly, in some embodiments, host computer 24 includes a processing circuit 42 configured to provide user data, and a communication interface 40 configured to transfer the user data to a cellular network for transmission to WD22. In some embodiments, the cellular network also includes a network node 16 having a wireless interface 62. In some embodiments, network node 16 is configured to perform the functions and / or methods described herein to prepare / initiate / maintain / support / terminate a transmission to WD22 and / or to prepare / terminate / maintain / support / terminate upon receiving a transmission from WD22, and / or the processing circuit 68 of network node 16 is configured to perform the functions and / or methods described herein to prepare / initiate / maintain / support / terminate a transmission to WD22.

[0096] In some embodiments, host computer 24 includes a processing circuit 42 and a communication interface 40 configured to receive user data starting from a transmission from WD22 to network node 16. In some embodiments, WD22 is configured to perform the functions and / or methods described herein to prepare / initiate / maintain / support / terminate a transmission to network node 16 and / or to prepare / terminate / maintain / support / terminate upon receiving a transmission from network node 16, and / or includes a wireless interface 82 and / or a processing circuit 84.

[0097] FIGS. 4 and 5 show various “units” such as configuration unit 32, power control unit 34, etc. as being within respective processors, but it is contemplated that these units may be implemented such that a portion of the units are stored in corresponding memories within the processing circuit. In other words, the units may be implemented as hardware within the processing circuit, or as a combination of hardware and software.

[0098] FIG. 6 is a flowchart showing an exemplary method implemented in a communication system such as the communication systems of FIGS. 4 and 5 according to one embodiment. The communication system may include a host computer 24, a network node 16, and a WD 22, which may be as described with reference to FIG. 5. In a first step of the method, the host computer 24 provides user data (block S100). In an optional sub-step of the first step, the host computer 24 provides user data by executing a host application, such as host application 50 (block S102). In a second step, the host computer 24 initiates a transmission to send the user data to the WD 22 (block S104). In an optional third step, the network node 16 sends the user data transmitted in the transmission initiated by the host computer 24 to the WD 22 in accordance with the teachings of the embodiments described throughout this disclosure (block S106). In an optional fourth step, the WD 22 executes a client application, such as client application 92, associated with the host application 50 executed by the host computer 24 (block S108).

[0099] FIG. 7 is a flowchart showing an exemplary method implemented in a communication system, such as the communication system of FIG. 4, according to one embodiment. The communication system may include a host computer 24, a network node 16, and a WD 22, which may be as described with reference to FIGS. 4 and 5. In a first step of the method, the host computer 24 provides user data (block S110). In an optional sub-step (not shown), the host computer 24 provides user data by executing a host application, such as host application 50. In a second step, the host computer 24 initiates a transmission to send the user data to the WD 22 (block S112). This transmission may be via the network node 16 in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third step, the WD 22 receives the user data carried in the transmission (block S114).

[0100] FIG. 8 is a flowchart showing an exemplary method implemented in a communication system, such as the communication system of FIG. 4, according to one embodiment. The communication system may include a host computer 24, a network node 16, and a WD 22 which may be as described with reference to FIGS. 4 and 5. In a first optional step of the method, the WD 22 receives input data provided by the host computer 24 (block S116). In a sub-step of the first optional step, the WD 22 executes a client application 92 that provides user data in response to the received input data provided by the host computer 24 (block S118). Further, or alternatively, in a second optional step, the WD 22 provides user data (block S120). In a sub-step of the second optional step, the WD provides user data by executing a client application, such as client application 92 (block S122). When providing the user data, the executed client application 92 may further consider user input received from the user. Regardless of the particular way in which the user data is provided, the WD 22 may initiate transmission of the user data to the host computer 24 in a third optional sub-step (block S124). In a fourth step of the method, the host computer 24 receives the user data transmitted from the WD 22 in accordance with the teachings of the embodiments described throughout this disclosure (block S126).

[0101] FIG. 9 is a flowchart showing an exemplary method implemented in a communication system, such as the communication system of FIG. 4, according to one embodiment. The communication system may include a host computer 24, a network node 16, and a WD 22, which may be the ones described with reference to FIGS. 4 and 5. In a first optional step of the method, according to the teachings of the embodiments described throughout the present disclosure, the network node 16 receives user data from the WD 22 (block S128). In a second optional step, the network node 16 starts transmitting the received user data to the host computer 24 (block S130). In a third step, the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (block S132).

[0102] FIG. 10 is a flowchart of an exemplary process at network node 16 according to some embodiments of the present disclosure. One or more blocks and / or functions and / or methods executed by network node 16 may be executed by one or more elements of network node 16, such as configuration unit 32 in processing circuitry 68, processor 70, radio interface 62, etc., according to an exemplary method. Network node 16, such as via processing circuitry 68 and / or processor 70 and / or radio interface 62 and / or communication interface 60, is configured to perform at least one of the steps of blocks S134 and S136. The exemplary method includes transmitting a media access control (MAC) control element (CE) to the WD (block S134), such as via configuration unit 32, processing circuitry 68, processor 70, communication interface 60, and / or radio interface 62, where the MAC_CE indicates an association between i) one of a physical uplink control channel (PUCCH) resource and a PUCCH resource group, and ii) at least one first PUCCH power control parameter set of a plurality of PUCCH power control parameter sets. The method optionally includes receiving a PUCCH transmission from the WD on one of a PUCCH resource and a PUCCH resource group (block S136), such as via configuration unit 32, processing circuitry 68, processor 70, communication interface 60, and / or radio interface 62, where the PUCCH transmission includes a transmission power level based on at least one first PUCCH power control parameter set associated with one of a PUCCH resource and a PUCCH resource group.

[0103] In some embodiments, the method further comprises configuring the WD with at least two PUCCH power control parameter sets, such as via the configuration unit 32, the processing circuit 68, the processor 70, the communication interface 60, and / or the radio interface 62. In some embodiments, the MAC_CE includes an n-bit field "S", where each bit of the n-bit field "S" corresponds to a respective PUCCH power control parameter set, and each PUCCH power control parameter set is either activated or deactivated based on the value of the corresponding bit. In some embodiments, n is 2.

[0104] In some embodiments, the MAC_CE is composed of a 1-bit activation / deactivation field indicating that all of the plurality of PUCCH power control parameter sets configured for the WD are either activated or deactivated. In some embodiments, the MAC_CE is of variable size and includes a field indicating whether the octets constituting the n-bit field S are present within the MAC_CE. In some embodiments, the MAC_CE includes a field F indicating either i) whether all of the plurality of PUCCH power control parameter sets configured for the WD are activated or deactivated, and ii) whether only one of the sets is activated for all of the PUCCH resources indicated in the MAC_CE.

[0105] In some embodiments, the MAC_CE includes a field S, and the meaning of the first value configured in the field S is based on the second value configured in the field F. In some embodiments, when the second value configured in the field F is one of "1" and "0", the field S makes all of a plurality of PUCCH power control parameter sets active and inactive, and when the second value configured in the field F is the other one of "1" and "0", the field S makes only one PUCCH power control parameter set active and inactive. In some embodiments, when the second value configured in the field F is one of "1" and "0", the field S is ignored and all of a plurality of PUCCH power control parameter sets are activated; when the second value included in the field F is the other one of "1" and "0", only one PUCCH power control parameter set is activated / deactivated, and the field S indicates which of the plurality of PUCCH power control parameter sets is activated / deactivated.

[0106] In some embodiments, the MAC_CE comprises a spatial relationship information ID field within an octet, and the spatial relationship information ID field identifies a spatial relationship activated for one of the PUCCH resources and PUCCH resource groups identified in the PUCCH resource index field in the previous octet. In some embodiments, the MAC_CE comprises: a field E in a first octet indicating whether the PUCCH resource is updated by a spatial relationship or a power control set; a PUCCH resource index field in a second octet identifying one of the PUCCH resources and PUCCH resource groups associated with the MAC_CE; and a third octet following the second octet, the third octet including a spatial relationship information identifier (ID) field and a field S, the spatial relationship information ID identifying the spatial relationship, and the field S identifying a PUCCH power control parameter set. In some embodiments, based on a value configured in the field E, one of the spatial relationship and the field S is activated for one of the PUCCH resources and PUCCH resource groups identified by the PUCCH resource index field in the second octet.

[0107] In some embodiments, at least two PUCCH power control parameter sets are explicitly configured and / or each set includes a set index value that identifies the respective PUCCH power control parameter set. In some embodiments, at least two PUCCH power control parameter sets are implicitly configured and / or at least two PUCCH spatial relationships are configured for WD, each PUCCH spatial relationship including a closed-loop index corresponding to one of at least two sets of a PUCCH path loss reference identifier (ID), P0-PUCCH_ID, and PUCCH power control parameters. In some embodiments, at least two PUCCH power control parameter sets are configured for WD only if at least two sounding reference signal resource (SRS) sets have a parameter usage method set to "codebook" or "non-codebook" in the uplink (UL) bandwidth part (BWP) of the carrier frequency supported by the primary cell (Pcell).

[0108] In some embodiments, the MAC_CE is composed of at least one of a 2-bit bandwidth part (BWP) field, a 5-bit serving cell identifier (ID) field, and a first reserved bit in the first octet, a 7-bit PUCCH resource index field and a second reserved bit in the second octet, and a 1-bit field dedicated to each of two sets of PUCCH power control parameters in the third octet. In other embodiments, fields of different bit sizes are possible.

[0109] In some embodiments, each set is activated for one of the PUCCH resources and PUCCH resource groups when the corresponding dedicated 1-bit field is set to one of "1" and "0", and deactivated when the corresponding dedicated 1-bit field is set to the other of "1" and "0". In some embodiments, conditional on the value configured in the first or second reserved bit, the third octet and / or the dedicated 1-bit field is ignored / absent in the MAC_CE. In some embodiments, the MAC_CE includes at least one of a 2-bit bandwidth part (BWP) field, a 5-bit serving cell identifier (ID) field and a first set indicator in the first octet, and a 7-bit PUCCH resource index field and a second set indicator in the second octet. In other embodiments, fields of different bit sizes are possible.

[0110] In some embodiments, when the first set indicator is set to one of "1" and "0", all of the plurality of PUCCH power control parameter sets are activated, the second set indicator is ignored, and when the first set indicator is set to the other of "1" and "0", the second set indicator indicates the PUCCH power control parameter set that is activated among the plurality of PUCCH power control parameter sets. In some embodiments, when all of the plurality of PUCCH power control parameter sets configured in the WD are activated by the MAC_CE, the PUCCH transmissions from the WD are received at different times for each PUCCH power control parameter set.

[0111] In some embodiments, the method further comprises configuring WD22 as one of a PUCCH resource and a PUCCH resource group, such as via configuration unit 32, processing circuitry 68, processor 70, communication interface 60, and / or radio interface 62, wherein each PUCCH power control parameter set comprises power control parameters for signaling to be transmitted by the WD towards a corresponding transmission and reception point (TRP) associated with network node 16.

[0112] Figure 11 is a flowchart of an exemplary process in wireless device 22 according to some embodiments of the present disclosure. One or more blocks and / or functions and / or methods executed by WD22 may be executed by one or more elements of WD22, such as power control unit 34 in processing circuitry 84, processor 86, radio interface 82, etc. Wireless device 22, such as via processing circuitry 84 and / or processor 86 and / or radio interface 82, is configured to execute at least one of the steps of blocks S138 and S140. The exemplary method comprises receiving a medium access control (MAC) control element (CE) (block S138), such as via power control unit 34, processing circuitry 84, processor 86, and / or radio interface 82, wherein the MAC_CE indicates an association between i) one of a physical uplink control channel, a PUCCH resource, and a PUCCH resource group, and ii) at least one first PUCCH power control parameter set of a plurality of PUCCH power control parameter sets. The method optionally further comprises transmitting a PUCCH transmission (block S140) on one of a PUCCH resource and a PUCCH resource group, such as via power control unit 34, processing circuitry 84, processor 86, and / or radio interface 82, wherein the PUCCH transmission comprises a transmission power level based on at least one first PUCCH power control parameter set associated with one of a PUCCH resource and a PUCCH resource group.

[0113] In some embodiments, the method further includes receiving a configuration including at least two PUCCH power control parameter sets, such as via a power control unit 34, a processing circuit 84, a processor 86, and / or a radio interface 82. In some embodiments, the MAC_CE includes an n-bit field "S", each bit of the n-bit field "S" corresponding to a respective PUCCH power control parameter set, and each PUCCH power control parameter set is either activated or deactivated based on the value of the corresponding bit. In some embodiments, n is 2. In some embodiments, the MAC_CE includes a 1-bit activation / deactivation field indicating that all of the plurality of PUCCH power control parameter sets configured for WD are either activated or deactivated.

[0114] In some embodiments, the MAC_CE is of variable size and includes a field indicating whether the octets constituting the n-bit field S are present within the MAC_CE. In some embodiments, the MAC_CE includes a field F indicating either i) whether all of the plurality of PUCCH power control parameter sets configured for WD are activated or deactivated, and ii) whether only one of the sets is activated for all of the PUCCH resources indicated in the MAC_CE. In some embodiments, the MAC_CE includes the field S, and the meaning of a first value configured in the field S is based on a second value configured in the field F. In some embodiments, the field S activates and deactivates all of the plurality of PUCCH power control parameter sets when the second value configured in the field F is one of "1" and "0", and the field S activates and deactivates only one PUCCH power control parameter set when the second value configured in the field F is the other of "1" and "0".

[0115] In some embodiments, when the second value configured in field F is one of "1" and "0", field S is ignored and all of the plurality of PUCCH power control parameter sets are activated; when the second value included in field F is the other one of "1" and "0", only one PUCCH power control parameter set is activated / deactivated, and field S indicates which PUCCH power control parameter set among the plurality of PUCCH power control parameter sets is activated / deactivated.

[0116] In some embodiments, the MAC_CE comprises a spatial relationship information ID field within an octet, and the spatial relationship information ID field identifies the spatial relationship activated for one of the PUCCH resources and PUCCH resource groups identified in the PUCCH resource index field in the previous octet. In some embodiments, the MAC_CE comprises: a field E in a first octet indicating whether the PUCCH resource is updated by a spatial relationship or a power control set; a PUCCH resource index field in a second octet identifying one of the PUCCH resources and PUCCH resource groups associated with the MAC_CE; a third octet following the second octet, the third octet including a spatial relationship information identifier (ID) field and field S, the spatial relationship information ID identifying the spatial relationship and field S identifying the PUCCH power control parameter set; and, based on the value configured in field E, one of the spatial relationship and field S is activated for one of the PUCCH resources and PUCCH resource groups identified by the PUCCH resource index field in the second octet.

[0117] In some embodiments, at least two PUCCH power control parameter sets are explicitly configured and / or each set includes a set index value that identifies the respective PUCCH power control parameter set. In some embodiments, at least two PUCCH power control parameter sets are implicitly configured and / or at least two PUCCH spatial relationships are configured for WD, each PUCCH spatial relationship including a closed-loop index corresponding to one of at least two sets of PUCCH path loss reference identifiers (IDs), P0-PUCCH_ID, and PUCCH power control parameters.

[0118] In some embodiments, at least two PUCCH power control parameter sets are configured for WD22 only when at least two sounding reference signal resources (SRS) sets have a parameter usage method set to "codebook" or "non-codebook" in the uplink (UL) bandwidth part (BWP) of the carrier frequency supported by the primary cell (Pcell). In some embodiments, the MAC_CE is composed of a 2-bit bandwidth part (BWP) field, a 5-bit serving cell identifier (ID) field and a first reserved bit in the first octet, a 7-bit PUCCH resource index field and a second reserved bit in the second octet, and a 1-bit field dedicated to each of two sets of PUCCH power control parameters in the third octet.

[0119] In some embodiments, each set is activated for one of the PUCCH resources and PUCCH resource groups when the corresponding dedicated 1-bit field is set to one of "1" and "0", and deactivated when the corresponding dedicated 1-bit field is set to the other of "1" and "0". In some embodiments, conditional on the value configured in the first or second reserved bit, the third octet and / or the dedicated 1-bit field is ignored / absent in the MAC_CE. In some embodiments, the MAC_CE is composed of a 2-bit bandwidth part (BWP) field, a 5-bit serving cell identifier (ID) field, and a first set indicator in the first octet, and a 7-bit PUCCH resource index field and a second set indicator in the second octet.

[0120] In some embodiments, when the first set indicator is set to one of "1" and "0", all of the plurality of PUCCH power control parameter sets are activated, the second set indicator is ignored, and when the first set indicator is set to the other of "1" and "0", the second set indicator indicates the PUCCH power control parameter set to be activated among the plurality of PUCCH power control parameter sets. In some embodiments, when all of the plurality of PUCCH power control parameter sets configured for WD are activated by the MAC_CE, the method comprises transmitting each of the PUCCH transmissions corresponding to different times for each PUCCH power control parameter set, such as via the power control unit 34, the processing circuit 84, the processor 86, and / or the radio interface 82.

[0121] In some embodiments, the method further includes receiving a configuration including one of a PUCCH resource and a PUCCH resource group, such as via a power control unit 34, a processing circuit 84, a processor 86, and / or a radio interface 82, where each PUCCH power control parameter set includes power control parameters for the WD to transmit signaling towards a corresponding transmit-receive point (TRP) associated with the network node.

[0122] FIG. 12 is a flowchart of an exemplary process at a network node 16 according to some embodiments of the present disclosure. One or more blocks and / or functions and / or methods executed by the network node 16 can be executed by one or more elements of the network node 16, such as a configuration unit 32 in a processing circuit 68, a processor 70, a radio interface 62, etc., according to an exemplary method. The network node 16, such as via a processing circuit 68 and / or a processor 70 and / or a radio interface 62 and / or a communication interface 60, is configured to configure the WD using a list of at least two power control parameter sets for power control of a physical uplink control channel PUCCH applicable to at least one of (1) one PUCCH resource, (2) each one of a plurality of PUCCH resources, and (3) a plurality of PUCCH resource groups (block S142). The process also includes transmitting a media access control (MAC) control element (CE) to the WD (22) to activate at least one power control parameter set from a list of power control parameter sets applicable to at least one of (1) one PUCCH resource, (2) each one of a plurality of PUCCH resources, and (3) a plurality of PUCCH resource groups (block S144).

[0123] In some embodiments, each of the lists of at least two power control parameter sets includes a PUCCH path loss reference signal identifier (ID), a target received power (P0-PUCCH) ID, a closed-loop index, and a power control parameter set ID. In some embodiments, the method also includes constructing WD (22) with PUCCH repetitions to each TRP associated with at least one of the at least two power control parameter sets for at least one transmit-receive point (TRP). In some embodiments, the MAC_CE includes a PUCCH resource identifier that includes two bit fields, each bit field identifying a respective PUCCH power control parameter set from a list of at least two control parameter sets. In some embodiments, the MAC_CE includes a bit field indicating whether one of two PUCCH power control sets and a single PUCCH power control set is activated for (1) one PUCCH resource, (2) each one of a plurality of PUCCH resources, and (3) at least one of a plurality of PUCCH resource groups. In some embodiments, the MAC_CE includes: an octet spatial relationship information ID field, the spatial relationship information ID field identifying an activated spatial relationship for one PUCCH resource of a plurality of PUCCH resources and one PUCCH resource of a plurality of PUCCH resource groups identified by the PUCCH resource index field of the previous octet.In some embodiments, the MAC_CE includes: a field E in the first octet indicating whether the PUCCH resource is updated by a spatial relationship or a power control set; a PUCCH resource index field in the second octet identifying one of the PUCCH resources from a plurality of PUCCH resources and the PUCCH resources from a plurality of PUCCH resource groups; a third octet following the second octet, the third octet including a spatial relationship information identifier (ID) field identifying a spatial relationship and an S field identifying a PUCCH power control parameter set; and, based at least in part on the value configured in the E field, one of the spatial relationship and the S field is activated for one of the PUCCH resources and the PUCCH resource groups identified by the PUCCH resource index field in the second octet, the third octet. In some embodiments, at least two PUCCH spatial relationships are configured in WD(22), and each PUCCH spatial relationship includes a PUCCH path loss reference identifier (ID), P0-PUCCH_ID, and a closed loop index. In some embodiments, the MAC_CE includes a bandwidth part (BWP) field, a serving cell identifier (ID) field in the first octet, a field indicating whether one of a set and a second set of PUCCH power control parameters is activated, a 7-bit PUCCH resource index field in the second octet, and dedicated fields for each of the two sets of PUCCH power control parameters in the third octet. In some embodiments, each PUCCH power control parameter set constitutes power control parameters for calculating the PUCCH transmission power for WD(22) towards the corresponding transmit receive point (TRP) associated with the network node (16).

[0124] FIG. 13 is a flowchart of an exemplary process in wireless device 22 according to some embodiments of the present disclosure. One or more blocks and / or functions and / or methods executed by WD22 may be executed by one or more elements of WD22, such as power control unit 34 in processing circuit 84, processor 86, wireless interface 82, and the like. The wireless device 22, such as via the processing circuit 84 and / or the processor 86 and / or the wireless interface 82, is configured to receive a configuration of a list of at least two power control parameter sets for power control of a physical uplink control channel PUCCH applicable to at least one of at least one PUCCH resource and at least one PUCCH resource group (block S146). The process also includes setting a transmission power level based at least in part on at least one of the at least two power control parameter sets in the list (block S148).

[0125] In some embodiments, each of the lists of at least two power control parameter sets includes a PUCCH path loss reference signal identifier (ID), a target received power (P0-PUCCH) ID, a closed-loop index, and a power control parameter set ID. In some embodiments, the method also includes constructing a WD (22) with PUCCH repetitions to at least one transmission and reception point (TRP) associated with at least one of the at least two power control parameter sets. In some embodiments, the MAC_CE includes a PUCCH resource identifier that includes two bit fields, each bit field identifying a respective PUCCH power control parameter set from a list of at least two control parameter sets. In some embodiments, the MAC_CE includes a bit field indicating whether one of two PUCCH power control sets and a single PUCCH power control set is activated for at least one of (1) one PUCCH resource, (2) each one of a plurality of PUCCH resources, and (3) a plurality of PUCCH resource groups. In some embodiments, the MAC_CE includes: an octet spatial relationship information ID field that identifies a spatial relationship activated for one PUCCH resource of a plurality of PUCCH resources and one PUCCH resource of a plurality of PUCCH resource groups identified by a PUCCH resource index field of a previous octet.In some embodiments, the MAC_CE includes: a field E in a first octet indicating whether a PUCCH resource is updated by a spatial relationship or a power control set; a PUCCH resource index field in a second octet identifying one of the PUCCH resources from a plurality of PUCCH resources and the PUCCH resources from a plurality of PUCCH resource groups; a third octet following the second octet, the third octet including a spatial relationship information identifier (ID) field for identifying a spatial relationship and an S field for identifying a PUCCH power control parameter set; and, based at least in part on a value configured in the E field, one of the spatial relationship and the S field is activated for one of the PUCCH resources and the PUCCH resource groups identified by the PUCCH resource index field in the second octet, the third octet. In some embodiments, the MAC_CE is further configured to constitute at least two PUCCH spatial relationships, and each PUCCH spatial relationship includes a PUCCH path loss reference identifier (ID), P0-PUCCH_ID, and a closed-loop index. In some embodiments, the MAC_CE includes a bandwidth part (BWP) field, a serving cell identifier (ID) field in the first octet, a field indicating whether one of a set and a second set of PUCCH power control parameters is activated, a 7-bit PUCCH resource index field in the second octet, and dedicated fields for each of the two sets of PUCCH power control parameters in the third octet. In some embodiments, each PUCCH power control parameter set constitutes power control parameters for calculating PUCCH transmission power for WD(22) towards a corresponding transmission and reception point (TRP) associated with a network node(16).

[0126] The general process flow of the arrangements of the present disclosure has been described, and examples of hardware and software arrangements for implementing the processes and functions of the present disclosure have been provided. In the following sections, details and examples of arrangements for PUCCH power control for multiple TRPs that can be implemented by network node 16, wireless device 22, and / or host computer 24 are provided.

[0127] The following examples are described with respect to one or more TRPs that may be network node 16, but for ease of understanding, the term "TRP16" is used instead.

[0128] FIG. 14 shows an example of PUCCH repetitions for multiple TRP16s. For PUCCH repetitions intended for reception at two different TRP16s, PUCCH power control is performed individually for each intended receiving TRP16.

[0129] Two sets of PUCCH power control parameters, a first and a second set, can be configured for the WD22 intended for each TRP16 respectively. Each of the two sets of power control parameters consists of at least a PUCCH path loss reference signal index, a WD22-specific P0 value or P0-PUCCH index, and a closed-loop index. The WD22 may also be composed of one or more PUCCH resources.

[0130] Explicit Configuration of Two PUCCH Power Control Parameter Sets In one embodiment, the PUCCH spatial relationship may not be configured for the WD22. Two sets of PUCCH power control parameters are explicitly configured. An example is shown in FIG. 15, and each set is identified by a set index. The corresponding changes in the PUCCH-PowerControlIE are shown below: - The first set with set ID_1 · PUCCH path loss reference RS_ID_1 · P0-PUCCH_ID_1 · Closed-loop ID_1 - The second set with set ID_2 · PUCCH path loss reference RS_ID_2 · P0-PUCCH_ID_2 · Closed loop ID_2

[0131] Configuration example of two sets of power control parameters. PUCCH - Power control information element --ASN1START --TAG-PUCCH-POWERCONTROL-START PUCCH-PowerControl ::= SEQUENCE { deltaF-PUCCH-f0 INTEGER (-16..15) OPTIONAL, --Need R deltaF-PUCCH-f1 INTEGER (-16..15) OPTIONAL, --Need R deltaF-PUCCH-f2 INTEGER (-16..15) OPTIONAL, --Need R deltaF-PUCCH-f3 INTEGER (-16..15) OPTIONAL, --Need R deltaF-PUCCH-f4 INTEGER (-16..15) OPTIONAL, --Need R p0-Set SEQUENCE (SIZE (1..maxNrofPUCCH-P0-PerSet)) OF P0-PUCCH OPTIONAL, --Need M pathlossReferenceRSs SEQUENCE (SIZE (1..maxNrofPUCCH-PathlossReferenceRSs)) OF PUCCH-PathlossReferenceRS OPTIONAL, --Need M twoPUCCH-PC-AdjustmentStates ENUMERATED {twoStates} OPTIONAL, --Need S ..., ​pathlossReferenceRSs-v1610 SetupRelease { PathlossReferenceRSs-v1610} OPTIONAL --Need M , pucch-PowerControlSets-r17 SEQUENCE (SIZE (2)) OF Pucch-PowerControlParaSet-r17 } P0-PUCCH ::= SEQUENCE { p0-PUCCH-Id, p0-PUCCH-Value INTEGER (-16..15) } P0-PUCCH-Id ::= INTEGER (1..8) PathlossReferenceRSs-v1610 ::= SEQUENCE (SIZE (1..maxNrofPUCCH-PathlossReferenceRSsDiff-r16)) OF PUCCH-PathlossReferenceRS-r16 PUCCH-PathlossReferenceRS ::= SEQUENCE { pucch-PathlossReferenceRS-Id, referenceSignal CHOICE { ssb-Index SSB-Index, csi-RS-Index NZP-CSI-RS-ResourceId } } PUCCH-PathlossReferenceRS-r16 ::= SEQUENCE { pucch-PathlossReferenceRS-Id-r16 PUCCH-PathlossReferenceRS-Id-v1610, referenceSignal-r16 CHOICE { ssb-Index-r16 SSB-Index,​​ csi-RS-Index-r16 NZP-CSI-RS-ResourceId } } Pucch-PowerControlParaSet-r17 SEQUENCE{ pucch-PowerControlParaSet-Id PUCCH-PowerControlParaSet-Id pucch-PathlossReferenceRS-Id PUCCH-PathlossReferenceRS-Id p0-PUCCH-Id closedLoopIndex ENUMERATED {i0, i1} } PUCCH-PowerControlParaSet-Id ::= INTEGER (0,1) --TAG-PUCCH-POWERCONTROL-STOP --ASN1STOP

[0132] Each PUCCH resource (or PUCCH resource group) is activated / updated by a MAC_CE having one or both of the first and second sets of PUCCH power control parameters by referring to a set index (i.e., PUCCH-PowerControlParaSet-Id). An example of a MAC_CE for activating / updating one or both of the first and second sets of PUCCH power control parameters is shown in Fig. 15. This has a variable size including one or more of the following fields: - Serving cell ID: This field indicates the ID of the serving cell to which the MAC_CE is applied; - BWP_ID: This field indicates the UL BWP to which the MAC_CE is applied; - PUCCH Resource ID: This field contains an identifier of the PUCCH resource identified by the PUCCH-ResourceId as defined in 3GPP TS38.331. If the indicated PUCCH resource is configured as part of a PUCCH group as defined in 3GPP TS38.331, the other PUCCH resources within the same PUCCH group are not indicated by MAC_CE, and this MAC_CE applies to all PUCCH resources within the PUCCH group; - S i : S i indicates the activation state of the PUCCH power control parameter set i. S i The field is set to 1 to indicate that the PUCCH power control parameter set with a PUCCH-PowerControlParaSet-Id equal to i is activated. S i The field is set to 0 to indicate that the PUCCH power control parameter set with a PUCCH-PowerControlParaSet-Id equal to i is deactivated; - R: A reserved bit and is set to 0.

[0133] Figure 15 is a diagram showing an example of the MAC_CE for activating / updating the PUCCH power control parameter set.

[0134] Another example of the MAC_CE for activating / updating one or both of the first and second sets of PUCCH power control parameters is shown in Figure 14. The MAC_CE in Figure 16 has a variable size and includes one or more of the following fields: - Serving Cell ID: This field indicates the ID of the serving cell to which the MAC_CE applies; - BWP_ID: This field indicates the UL BWP to which the MAC_CE applies; - A / D: This field indicates whether both of the PUCCH-PowerControlParaSet-Ids are activated or deactivated if field C is set to 0; -PUCCH Resource ID: This field contains an identifier of the PUCCH resource ID identified by the PUCCH-ResourceId defined in 3GPP TS38.331. If the indicated PUCCH resource is configured as part of a PUCCH group defined in 3GPP TS38.331, other PUCCH resources within the same PUCCH group are not indicated by MAC_CE, and this MAC_CE applies to all PUCCH resources within the PUCCH group; -S i :S i indicates the activation state of the PUCCH power control parameter set i. S i The field is set to 1 to indicate that the PUCCH power control parameter set with a PUCCH-PowerControlParaSet-Id equal to i is activated. S i The field is set to 0 to indicate that the PUCCH power control parameter set with a PUCCH-PowerControlParaSet-Id equal to i is deactivated; -C: Indicates whether there is an octet containing the Si field. When C is set to 1, the octet containing the Si field exists, and when C is set to 0, the octet does not exist, and depending on how the A / D field is set, both PUCCH-PowerControlParaSet-Ids are activated or deactivated; -R: A reserved bit and is set to 0.

[0135] The advantage of this MAC_CE variant is that it can save the octets required for MAC_CE when both PUCCH-PowerControlParaSet-Ids become active or inactive. This MAC_CE can also be defined without the A / D field such that the C field with value 0 always activates both PUCCH-PowerControlParaSet-Ids.

[0136] Figure 17 shows yet another example of MAC_CE for activating / updating one or both of the first and second sets of PUCCH power control parameters. This has a variable size and includes one or more of the following fields: - Serving cell ID: This field indicates the ID of the serving cell to which the MAC_CE applies; - BWP_ID: This field indicates the UL BWP to which the MAC_CE applies; - F: This field indicates whether both PUCCH - PowerControlParaSet - Id are activated or deactivated, or whether only one of the PUCCH - PowerControlParaSet - Id is activated for all PUCCH resources indicated by this MAC_CE. When the value of the F field is "1", both PUCCH - PowerControlParaSet - Id are activated or deactivated depending on how the S field is set. When the F field is set to "0", one of the PUCCH - PowerControlParaSet - Id is activated and the other PUCCH - PowerControlParaSet - Id is deactivated as indicated by the S field. When the F field is set to "0", one of the PUCCH - PowerControlParaSet - Id is activated and the other PUCCH - PowerControlParaSet - Id is deactivated as indicated by the field S; - PUCCH resource ID: This field contains an identifier of the PUCCH resource ID identified by PUCCH - ResourceId as defined in 3GPP TS38.331. If the indicated PUCCH resource is configured as part of a PUCCH group as defined in 3GPP TS38.331, other PUCCH resources within the same PUCCH group are not indicated in the MAC_CE and this MAC_CE applies to all PUCCH resources within the PUCCH group; -S: When the F field is set to "1", the S field indicates the activation state of two PUCCH power control parameter sets. Setting the S field to 1 activates both PUCCH power control parameter sets. S i When the field is set to 0, both PUCCH power control parameter sets become inactive. Alternatively, when the F field has the value 1, both PUCCH-PowerControlParaSet-Ids become active and the S field is ignored. When the F field is set to "0", the S field indicates the activation state of PUCCH power control parameter set i. When the S field is set to "1", it indicates that the PUCCH power control parameter set with PUCCH-PowerControlParaSet-Id equal to 1 is activated and the PUCCH power control parameter set with PUCCH-PowerControlParaSet-Id equal to 0 is deactivated. When the S field is set to "0", it indicates that the PUCCH power control parameter with PUCCH-PowerControlParaSet-Id equal to 0 becomes active and the PUCCH power control parameter with PUCCH-PowerControlParaSet-Id equal to 1 becomes inactive.

[0137] The advantage of this MAC_CE is that it can save the octets required for the MAC_CE. The network transmits one MAC_CE for all PUCCH resources that activate / deactivate both PUCCH power control parameter sets, and another MAC_CE for all PUCCH resources that activate / deactivate one of the PUCCH power control parameter sets. Since the number of configured PUCCH resources per BWP per cell is 128, the overhead can be significantly reduced.

[0138] The MAC_CE of 3GPP's NR Release 16 in Figure 18 shows the MAC_CE for updating the PUCCH spatial relationship (quoted from Figure 6.1.3.25-1 of 3GPP TS38.321 V16.3.0).

[0139] In the existing MAC CE of FIG. 18, the spatial relationship of the PUCCH resource having the resource identifier "PUCCH resource ID" is updated / activated with the spatial relationship having the identifier "spatial relationship information ID" in the subsequent octet.

[0140] In another embodiment, the above MAC CE is modified as shown in FIG. 19. FIG. 19 shows an example of a modified MAC CE for activating / updating either a spatial relationship or a power control set. In this modified MAC CE, the "E" field in the first octet indicates whether the PUCCH resource is updated with a spatial relationship or a power control set(s). The fields "S1" and "S0" indicate whether the first power control set and / or the second power control set should be activated / updated for the PUCCH resource specified by the PUCCH resource ID in the previous octet, respectively. When both "S1" and "S0" are set to 1, both power control sets are activated for the PUCCH resource by the PUCCH resource ID in the previous octet, subject to the value of the "E" field. When "S1" is set to 0 and "S0" is set to 1, only the first power control set is activated for the PUCCH resource by the PUCCH resource ID in the previous octet, subject to the value of the "E" field. When "S1" is set to 0 and "S0" is set to 1, only the first power control set is activated for the PUCCH resource by the PUCCH resource ID in the previous octet, subject to the value of the "E" field. When "S1" is set to 1 and "S0" is set to 0, only the second power control set is activated for the PUCCH resource by the PUCCH resource ID in the previous octet, subject to the value of the "E" field.

[0141] When the "E" field is set to 0, the PUCCH resource having the resource ID "PUCCH resource ID" is activated with the spatial relationship having the identifier "spatial relationship information ID" in the next octet.

[0142] When the "E" field is set to 1, the PUCCH resource with the resource ID "PUCCH resource ID" is activated with the power control set specified by "S1" and "S0" in the next octet.

[0143] In another embodiment, a single MAC_CE different from the MAC_CE of FIG. 19 is used to update one or more PUCCH resources (s) in any of the following: · One or two power control sets, or · One or two spatial relationships (s).

[0144] The field of this single MAC_CE can indicate whether one or more PUCCH resources are updated with a power control set (s) or a spatial relationship (s).

[0145] When both sets are activated for a PUCCH resource, the PUCCH is repetitively transmitted to the first and second TRP16. The first set of power control parameters is applied to the PUCCH transmission opportunity to the first TRP16, and the second set of power control parameters is applied to the PUCCH transmission opportunity to the second TRP16. When the first (or second) set is activated for a PUCCH resource, the PUCCH will be transmitted to the TRP16 applying the power control parameters of the first (or second) set.

[0146] In another embodiment, the activation / update of the power control set for the PUCCH resource can be extended to the PUCCH resource group. In the following example, it is assumed that the PUCCH resource is configured as part of the PUCCH group defined in the 3GPP technical standard (TS) 38.331. Then, according to the proposed MAC_CE described above, when the power control set for this PUCCH resource is activated / updated, this activated / updated power control set is applied to all PUCCH resources within the PUCCH group. In this embodiment, the MAC_CE for updating the power control set may only permit a single PUCCH resource from the PUCCH group. The advantages of this embodiment include that there is no need to transmit multiple MAC_CEs to update the power control set of the PUCCH resources within the PUCCH resource group. Therefore, the overhead of control signaling is saved.

[0147] Note that the term TRP16 may not be used in the 3GPP specifications. Instead, TRP16 may be represented by the "power control parameter set" in the 3GPP specifications. For example, the first and second configured power control parameter sets can represent the first and second TRP16s, respectively.

[0148] Implicit Configuration of Two PUCCH Power Control Parameter Sets In one embodiment, it can be assumed that WD22 is configured in the PUCCH spatial relationship and two sets of power control parameters are implicitly configured. For example, the two sets of parameters are composed of two or more PUCCH path loss reference signals, two or more P0 values specific to WD22, and two closed loops, as shown in FIG. 18. This can be done using the existing PUCCH - power control IE. The following list shows examples of configuring two sets of power control parameters. · List of PUCCH path loss reference RS: · PUCCH path loss reference RS_ID_1; · PUCCH path loss reference RS_ID_2; ·List of P0-PUCCH: ·P0-PUCCH_ID_1; ·P0-PUCCH_ID_2; ·List of closed-loop indexes: ·Closed-loop ID_1; ·Closed-loop ID_2. The bold (Note: the end is ID_1) is the first set. The italic (Note: the end is ID_2) is the second set.

[0149] Each PUCCH spatial relationship includes a PUCCH path loss reference ID, a P0-PUCCH_ID, and one of two sets of closed-loop indexes of PUCCH power control parameters. When two PUCCH spatial relationships are activated for a PUCCH resource, the PUCCH is repeatedly transmitted to the first and second TRP16. The power control parameters shown in the first and second spatial relationships are applied to the PUCCH transmission opportunities to the first and second TRP16, respectively.

[0150] In one embodiment, the two sets of PUCCH power control parameters can be configured only when two SRS resource sets with the usage parameter set to "codebook" or "non-codebook" are configured for WD22 in the UL BWP of the carrier frequency of the primary cell.

[0151] Figure 20 is a call flow diagram showing an example of signaling between WD22 associated with TRP1 16a and TRP2 16b and network node 16. Although this embodiment is illustrated for two TRPs, it is also applicable to scenarios with two or more TRPs, in which case n sets are configured and n can be any number.

[0152] In step S1, WD22 reports support for PUCCH repetitions for a plurality of TRP16a, 16b. In step S2, one or more network nodes such as one or more of TRP16a, 16b can configure WD22 with one or more of the following: two SRS resource sets having uses set to "codebook" or "non-codebook", a plurality of PUCCH resources, and a set of two PUCCH power control parameters set one for each TRP. In step S3, the network node activates one or both sets of PUCCH power control parameters for each PUCCH resource, for example via TRP16a. In step S4, the network node such as via TRP16a schedules UCI on the PUCCH resources activated with two sets of power control parameters. In step S5, WD22 transmits UCI within the PUCCH resource towards TRP1 16a according to the first set of PUCCH power control parameters. In step S6, WD22 transmits the same UCI in the PUCCH resource (e.g., the same PUCCH resource used in step S5), but transmits according to the second set of PUCCH power control parameters towards TRP2 16b.

[0153] Some embodiments can include one or more of the following: Embodiment A1. A network node configured to communicate with a wireless device (WD), the network node transmits a media access control (MAC) control element (CE) to the WD, the MAC_CE indicating an association between i) one of a physical uplink control channel (PUCCH) resource and a PUCCH resource group, and ii) at least a first set of a plurality of PUCCH power control parameter sets, As an option, receive PUCCH transmissions from the WD on one of the PUCCH resources and PUCCH resource groups, where the PUCCH transmissions include a transmission power level based on at least one first PUCCH power control parameter set associated with one of the PUCCH resources and PUCCH resource groups. configured to perform one or more of , and / or comprising a radio interface, and / or comprising a processing circuit. Embodiment A2. The network node and / or radio interface and / or processing circuit is configured to configure the WD with at least two PUCCH power control parameter sets The network node according to Embodiment A1, configured as such. Embodiment A3. The MAC_CE comprises an n-bit field (S), each bit of the n-bit field (S) corresponding to a respective PUCCH power control parameter set, and each PUCCH power control parameter set being either activated or deactivated based on the value of the corresponding bit. The network node according to any one of Embodiments A1 and A2. Embodiment A4. The network node according to Embodiment A3, where n is 2. Embodiment A5. The MAC_CE comprises a 1-bit activation / deactivation field indicating that all of the plurality of PUCCH power control parameter sets configured for the WD are either activated or deactivated. The network node according to any one of Embodiments A3 and A4. Embodiment A6. The MAC_CE is of variable size and comprises a field indicating whether an octet constituting the n-bit field S is present in the MAC_CE. The network node according to any one of Embodiments A3 to A5. Embodiment A7. The MAC_CE includes a field F indicating either i) whether all of a plurality of PUCCH power control parameter sets configured for the WD are activated or deactivated, and ii) whether only one of the sets is activated for all PUCCH resources indicated in the MAC_CE, the network node according to Embodiment A1. Embodiment A8. The MAC_CE includes a field S, and the meaning of the first value configured in the field S is based on the second value configured in the field F, the network node according to Embodiment A7. Embodiment A9. The field (S) activates and deactivates all of the plurality of PUCCH power control parameter sets when the second value configured in the field (F) is one of "1" and "0"; Here, the field S activates and deactivates only one PUCCH power control parameter set when the second value configured in the field F is the other one of "1" and "0", the network node according to Embodiment A8. Embodiment A10. When the second value configured in the field (F) is one of "1" and "0", the field (S) is ignored and all of the plurality of PUCCH power control parameter sets are activated, Here, when the second value configured in the field F is the other one of "1" and "0", only one PUCCH power control parameter set is activated / deactivated, and the field S indicates which of the plurality of PUCCH power control parameter sets is activated / deactivated, the network node according to Embodiment A8. Embodiment A11. The MAC_CE is A network node according to Embodiment A1, comprising an octet's spatial relationship information ID field, the spatial relationship information ID field identifying a spatial relationship activated for one of a PUCCH resource and a PUCCH resource group identified by the PUCCH resource index field of the previous octet. Embodiment A12. The MAC CE A field E in the first octet indicating whether the PUCCH resource is updated by a spatial relationship or a power control set; A PUCCH resource index field in the second octet identifying one of a PUCCH resource and a PUCCH resource group associated with the MAC CE; A third octet following the second octet, comprising a spatial relationship information identifier (ID) field and a field S, the spatial relationship information ID identifying a spatial relationship and the field S identifying a PUCCH power control parameter set; and comprising wherein, based on the value configured in the field E, one of the spatial relationship and the field S is activated for one of a PUCCH resource and a PUCCH resource group identified by the PUCCH resource index field of the second octet, a network node according to Embodiment A1. Embodiment A13. A network node according to any one of Embodiments A1 - A12, wherein at least two PUCCH power control parameter sets are explicitly configured and / or each set includes a set index value identifying the respective PUCCH power control parameter set. Embodiment A14. A network node according to any one of Embodiments A1 - A13, wherein at least two PUCCH power control parameter sets are implicitly configured and / or at least two PUCCH spatial relationships are configured for WD, each PUCCH spatial relationship including a PUCCH path loss reference identifier (ID), P0 - PUCCH_ID, and a closed - loop index corresponding to each one of at least two PUCCH power control parameter sets. Embodiment A15. The at least two PUCCH power control parameter sets are configured for the WD only when at least two sounding reference signal resource (SRS) sets have parameter usage set to "codebook" or "non-codebook" for the uplink (UL) bandwidth part (BWP) of the carrier frequency supported by the primary cell (Pcell) with respect to the WD, the network node according to any of Embodiments A1 to A14. Embodiment A16. The MAC_CE A 2-bit bandwidth part (BWP) field, a 5-bit serving cell identifier (ID) field, and a first reserved bit in the first octet; and A 7-bit PUCCH resource index field and a second reserved bit in the second octet; and A 1-bit field dedicated to each of two sets of PUCCH power control parameters in the third octet The network node according to any of Embodiments A1, A2, A13 to A15, comprising Embodiment A17. Each set is activated for one of the PUCCH resources and PUCCH resource groups when the corresponding dedicated 1-bit field is set to one of "1" and "0", and deactivated when the corresponding dedicated 1-bit field is set to the other of "1" and "0", the network node according to Embodiment A16. Embodiment A18. Conditional on the value configured in the first or second reserved bit, the third octet and / or the dedicated 1-bit field is ignored / absent in the MAC_CE, the network node according to any of Embodiments A16 and A17. Embodiment A19. The MAC_CE A 2-bit bandwidth part (BWP) field, a 5-bit serving cell identifier (ID) field, and a first set indicator in the first octet; and 7-bit PUCCH resource index field and a second set indicator of the second octet A network node according to any of embodiments A1, A2, A13 - A15, comprising . Embodiment A20. When the first set indicator is set to one of "1" and "0", all of a plurality of PUCCH power control parameter sets are activated and the second set indicator is ignored, wherein when the first set indicator is set to the other one of "1" and "0", the second set indicator indicates an activated PUCCH power control parameter set among the plurality of PUCCH power control parameter sets, a network node according to embodiment A19. Embodiment A21. When all of a plurality of PUCCH power control parameter sets configured for WD are activated by MAC_CE, PUCCH transmissions from WD are received at different times for each PUCCH power control parameter set, a network node according to any of embodiments A1 - A20. Embodiment A22. The network node and / or the radio interface and / or the processing circuit configures WD with one of a PUCCH resource and a PUCCH resource group; wherein each PUCCH power control parameter set is configured to include power control parameters for WD to transmit signaling towards a corresponding transmission and reception point (TRP) associated with the network node, a network node according to any of embodiments A1 - A21.

[0154] Embodiment B1. A method implemented in a network node configured to communicate with a wireless device (WD), the method comprising Transmitting a Media Access Control (MAC) Control Element (CE) to a WD, where the MAC_CE indicates an association between i) one of a Physical Uplink Control Channel (PUCCH) resource and a PUCCH resource group, and ii) at least a first PUCCH power control parameter set of a plurality of PUCCH power control parameter sets. Optionally, receiving a PUCCH transmission from the WD on one of a PUCCH resource and a PUCCH resource group, where the PUCCH transmission includes a transmission power level based on at least a first PUCCH power control parameter set associated with one of the PUCCH resource and the PUCCH resource group. Including. Embodiment B2. The method according to Embodiment B1, further comprising configuring the WD with at least two PUCCH power control parameter sets. Embodiment B3. The MAC_CE comprises an n-bit field (S), each bit of the n-bit field (S) corresponding to a respective PUCCH power control parameter set, and each PUCCH power control parameter set is either activated or deactivated based on the value of the corresponding bit. The method according to any one of Embodiments B1 and B2. Embodiment B4. The method according to Embodiment B3, where n is 2. Embodiment B5. The MAC_CE includes a 1-bit activation / deactivation field indicating that all of the plurality of PUCCH power control parameter sets configured for the WD are either activated or deactivated. The method according to any one of Embodiments B3 and B4. Embodiment B6. The MAC_CE is of variable size, and the MAC_CE includes a field indicating whether an octet constituting the n-bit field S is present in the MAC_CE. The method according to any one of Embodiments B3 - B5. Embodiment B7. The method according to Embodiment B1, wherein the MAC_CE includes a field F indicating either i) whether all of a plurality of PUCCH power control parameter sets configured in the WD are activated or deactivated, and ii) whether only one of the sets is activated for all PUCCH resources indicated in the MAC_CE. Embodiment B8. The method according to Embodiment B7, wherein the MAC_CE includes a field S, and the meaning of a first value configured in the field S is based on a second value configured in the field F. Embodiment B9. The field (S) activates and deactivates all of a plurality of PUCCH power control parameter sets when the second value configured in the field (F) is one of "1" and "0"; Here, the field S activates and deactivates only one PUCCH power control parameter set when the second value configured in the field F is the other one of "1" and "0", according to the method described in Embodiment B8. Embodiment B10. When the second value configured in the field (F) is one of "1" and "0", the field (S) is ignored, and all of a plurality of PUCCH power control parameter sets are activated, Here, when the second value configured in the field F is the other one of "1" and "0", only one PUCCH power control parameter set is activated / deactivated, and the field S indicates which PUCCH power control parameter set among the plurality of PUCCH power control parameter sets is activated / deactivated, according to the method described in Embodiment B8. Embodiment B11. The MAC_CE is including an octet spatial relationship information ID field, and the spatial relationship information ID field identifies a spatial relationship activated for one of the PUCCH resources and PUCCH resource groups identified by the PUCCH resource index field of the previous octet, according to the method described in Embodiment B1. Embodiment B12. The MAC CE includes: a field E in the first octet indicating whether the PUCCH resource is updated by a spatial relationship or a power control set; a PUCCH resource index field in the second octet identifying one of the PUCCH resources and PUCCH resource groups associated with the MAC CE; a third octet following the second octet, including a spatial relationship information identifier (ID) field and a field S, where the spatial relationship information ID identifies a spatial relationship and the field S identifies a PUCCH power control parameter set; and includes wherein, based on the value configured in the field E, one of the spatial relationship and the field S is activated for one of the PUCCH resources and PUCCH resource groups identified by the PUCCH resource index field in the second octet, the method according to Embodiment B1. Embodiment B13. The method according to any one of Embodiments B1 to B12, wherein at least two PUCCH power control parameter sets are explicitly configured and / or each set includes a set index value identifying the respective PUCCH power control parameter set. Embodiment B14. The method according to any one of Embodiments B1 to B13, wherein at least two PUCCH power control parameter sets are implicitly configured and / or at least two PUCCH spatial relationships are configured in the WD, and each PUCCH spatial relationship includes a PUCCH path loss reference identifier (ID), P0-PUCCH_ID, and a closed-loop index corresponding to each one of at least two PUCCH power control parameter sets. Embodiment B15. The method according to any one of Embodiments B1 to B14, wherein at least two PUCCH power control parameter sets are configured for the WD only when at least two sounding reference signal resource (SRS) sets have parameter usage set to "codebook" or "non-codebook" for the WD in the uplink (UL) bandwidth part (BWP) of the carrier frequency supported by the primary cell (Pcell). Embodiment B16. The MAC CE comprises a 2-bit bandwidth part (BWP) field, a 5-bit serving cell identifier (ID) field, and a first reserved bit in the first octet; and a 7-bit PUCCH resource index field and a second reserved bit in the second octet; and a 1-bit field dedicated to each of two sets of PUCCH power control parameters in the third octet The method according to any one of Embodiments B1, B2, B13 to B15. Embodiment B17. Each set is activated for one of the PUCCH resources and PUCCH resource groups when the corresponding dedicated 1-bit field is set to one of "1" and "0", and deactivated when the corresponding dedicated 1-bit field is set to the other of "1" and "0". The method according to Embodiment B16. Embodiment B18. The method according to any one of Embodiments B16 and B17, wherein the third octet and / or the dedicated 1-bit field are ignored / absent in the MAC CE, conditional on the value configured in the first or second reserved bit. Embodiment B19. The MAC CE comprises a 2-bit bandwidth part (BWP) field, a 5-bit serving cell identifier (ID) field, and a first set indicator in the first octet; and a 7-bit PUCCH resource index field and a second set indicator in the second octet The method according to any one of embodiments B1, B2, B13 to B15, comprising Embodiment B20. When the first setting indicator is set to one of "1" and "0", all of a plurality of PUCCH power control parameter sets are activated and the second setting indicator is ignored. Here, when the first set indicator is set to the other one of "1" and "0", the second set indicator indicates the activated PUCCH power control parameter set among the plurality of PUCCH power control parameter sets, according to the method described in Embodiment B19. Embodiment B21. When all of a plurality of PUCCH power control parameter sets configured for a WD are activated by a MAC_CE, PUCCH transmissions from the WD are received at different times for each PUCCH power control parameter set, according to the method described in any one of Embodiments B1 to B20. Embodiment B22. Further comprising configuring the WD with one of a PUCCH resource and a PUCCH resource group; Here, each PUCCH power control parameter set includes power control parameters for the WD to transmit signaling towards a corresponding transmit receive point (TRP) associated with a network node, according to the method described in any one of Embodiments B1 to B21.

[0155] Embodiment C1. A wireless device (WD) configured to communicate with a network node, the WD receives a media access control (MAC) control element (CE), the MAC_CE indicating an association between i) one of a physical uplink control channel (PUCCH) resource and a PUCCH resource group and ii) at least a first PUCCH power control parameter set of a plurality of PUCCH power control parameter sets. Optionally, transmit PUCCH transmissions on one of the PUCCH resources and PUCCH resource groups, the PUCCH transmissions including a transmission power level based on at least one first PUCCH power control parameter set associated with one of the PUCCH resources and PUCCH resource groups. configured to perform and / or comprising a radio interface and / or a processing circuit. Embodiment C2. The WD and / or the radio interface and / or the processing circuit is configured to receive a configuration including at least two PUCCH power control parameter sets. The WD according to Embodiment C1, which is configured as such. Embodiment C3. The MAC_CE comprises an n-bit field (S), each bit of the n-bit field (S) corresponding to a respective PUCCH power control parameter set, and each PUCCH power control parameter set being either activated or deactivated based on the value of the corresponding bit. The WD according to any one of Embodiments C1 and C2. Embodiment C4. The WD according to Embodiment C3, wherein n is 2. Embodiment C5. The MAC_CE includes a 1-bit activation / deactivation field indicating that all of the plurality of PUCCH power control parameter sets configured for the WD are either activated or deactivated. The WD according to any one of Embodiments C3 and C4. Embodiment C6. The MAC_CE has a variable size and includes a field indicating whether the octets constituting the n-bit field S are present in the MAC_CE. The WD according to any one of Embodiments C3 to C5. Embodiment C7. The MAC_CE includes a field F indicating either i) whether all of the plurality of PUCCH power control parameter sets configured for the WD are activated or deactivated, and ii) whether only one of the sets is activated for all of the PUCCH resources indicated in the MAC_CE. The WD according to Embodiment C1. Embodiment C8. The MAC_CE includes a field S, and the meaning of the first value configured in the field S is based on the second value configured in the field F, the WD described in Embodiment C7. Embodiment C9. The field (S) activates and deactivates all of a plurality of PUCCH power control parameter sets when the second value configured in the field (F) is one of "1" and "0"; Here, the field S activates and deactivates only one PUCCH power control parameter set when the second value configured in the field F is the other one of "1" and "0", the WD described in Embodiment C8. Embodiment C10. When the second value configured in the field (F) is one of "1" and "0", the field (S) is ignored, and all of a plurality of PUCCH power control parameter sets are activated, Here, when the second value configured in the field F is the other one of "1" and "0", only one PUCCH power control parameter set is activated / deactivated, and the field S indicates which PUCCH power control parameter set among the plurality of PUCCH power control parameter sets is activated / deactivated, the WD described in Embodiment C8. Embodiment C11. The MAC_CE includes an octet spatial relationship information ID field, and the spatial relationship information ID field identifies the spatial relationship activated for one of the PUCCH resources and PUCCH resource groups identified by the PUCCH resource index field of the previous octet, the WD described in Embodiment C1. Embodiment C12. The MAC_CE a field E of the first octet indicating whether the PUCCH resource is updated by a spatial relationship or a power control set; a PUCCH resource index field of the second octet identifying one of the PUCCH resources and PUCCH resource groups associated with the MAC_CE; The third octet following the second octet, comprising a spatial relationship information identifier (ID) field and a field S, wherein the spatial relationship information ID identifies a spatial relationship and the field S identifies a PUCCH power control parameter set, and the third octet comprising wherein, based on the value configured in the field E, one of the spatial relationship and the field S is activated for one of the PUCCH resources and PUCCH resource groups identified by the PUCCH resource index field of the second octet, the WD according to Embodiment C1 Embodiment C13. The WD according to any one of Embodiments C1 to C12, wherein at least two PUCCH power control parameter sets are explicitly configured and / or each set includes a set index value identifying its respective PUCCH power control parameter set Embodiment C14. The WD according to any one of Embodiments C1 to C13, wherein at least two PUCCH power control parameter sets are implicitly configured and / or at least two PUCCH spatial relationships are configured in the WD, and each PUCCH spatial relationship includes a PUCCH path loss reference identifier (ID), P0-PUCCH_ID, and a closed-loop index corresponding to each one of at least two PUCCH power control parameter sets Embodiment C15. The WD according to any one of Embodiments C1 to C14, wherein at least two PUCCH power control parameter sets are configured for the WD only when at least two sounding reference signal resources (SRS) sets have parameter usage set to "codebook" or "non-codebook" for the WD in the uplink (UL) bandwidth part (BWP) of the carrier frequency supported by the primary cell (Pcell) Embodiment C16. The MAC_CE a 2-bit bandwidth part (BWP) field, a 5-bit serving cell identifier (ID) field, and a first reserved bit of the first octet; and The 7-bit PUCCH resource index field and the second reserved bit in the second octet; and A 1-bit field dedicated to each of two sets of PUCCH power control parameters in the third octet The WD according to any one of Embodiments C1, C2, C13 to C15, comprising Embodiment C17. Each set is activated for one of the PUCCH resources and PUCCH resource groups when the corresponding dedicated 1-bit field is set to one of "1" and "0", and deactivated when the corresponding dedicated 1-bit field is set to the other of "1" and "0", the WD according to Embodiment C16 Embodiment C18. Conditional on the value configured in the first or second reserved bit, the third octet and / or the dedicated 1-bit field is ignored / absent in the MAC_CE, the WD according to any one of Embodiments C16 and C17 Embodiment C19. The MAC_CE comprises A 2-bit bandwidth part (BWP) field, a 5-bit serving cell identifier (ID) field, and a first set indicator in the first octet; and A 7-bit PUCCH resource index field and a second set indicator in the second octet The WD according to any one of Embodiments C1, C2, C13 to C15, comprising Embodiment C20. When the first set indicator is set to one of "1" and "0", all of the plurality of PUCCH power control parameter sets are activated and the second set indicator is ignored, wherein when the first set indicator is set to the other of "1" and "0", the second set indicator indicates the PUCCH power control parameter set that is activated among the plurality of PUCCH power control parameter sets, the WD according to Embodiment C19 Embodiment C21. When all of a plurality of PUCCH power control parameter sets configured in a WD are activated by a MAC_CE, the WD and / or the radio interface and / or the processing circuit are configured to transmit each corresponding PUCCH transmission at different times for each PUCCH power control parameter set, the WD according to any of Embodiments C1 - C20. Embodiment C22. The WD and / or the radio interface and / or the processing circuit receives a configuration including one of a PUCCH resource and a PUCCH resource group; where each PUCCH power control parameter set is configured to include power control parameters for the WD to transmit signaling towards a corresponding transmission and reception point (TRP) associated with the network node, the WD according to any of Embodiments C1 - C21.

[0156] Embodiment D1. A method implemented in a wireless device (WD), the method comprising: receiving a media access control (MAC) control element (CE), the MAC_CE indicating an association between i) one of a physical uplink control channel (PUCCH) resource and a PUCCH resource group, and ii) at least a first PUCCH power control parameter set of a plurality of PUCCH power control parameter sets; optionally, transmitting a PUCCH transmission on one of a PUCCH resource and a PUCCH resource group, the PUCCH transmission including a transmission power level based on at least a first PUCCH power control parameter set associated with one of the PUCCH resource and the PUCCH resource group; including. Embodiment D2. The method according to Embodiment D1, further comprising receiving a configuration including at least two PUCCH power control parameter sets. Embodiment D3. The MAC_CE includes an n-bit field (S), and each bit of the n-bit field (S) corresponds to a respective PUCCH power control parameter set, and each PUCCH power control parameter set is either activated or deactivated based on the value of the corresponding bit, according to any one of Embodiments D1 and D2. Embodiment D4. The method according to Embodiment D3, where n is 2. Embodiment D5. The MAC_CE includes a 1-bit activation / deactivation field indicating that all of a plurality of PUCCH power control parameter sets configured in the WD are either activated or deactivated, according to any one of Embodiments D3 and C4. Embodiment D6. The MAC_CE has a variable size, and the MAC_CE includes a field indicating whether the octets constituting the n-bit field S are present in the MAC_CE, according to any one of Embodiments D3 to D5. Embodiment D7. The MAC_CE includes a field F indicating either i) whether all of a plurality of PUCCH power control parameter sets configured in the WD are activated or deactivated, and ii) whether only one of the sets is activated for all PUCCH resources indicated in the MAC_CE, according to Embodiment D1. Embodiment D8. The MAC_CE includes a field S, and the meaning of the first value configured in the field S is based on the second value configured in the field F, according to Embodiment D7. Embodiment D9. The field (S) activates and deactivates all of the plurality of PUCCH power control parameter sets when the second value configured in the field (F) is one of "1" and "0"; Here, the field S activates and deactivates only one PUCCH power control parameter set when the second value configured in the field F is the other one of "1" and "0", according to Embodiment D8. Embodiment D10. When the second value configured in the field (F) is one of "1" and "0", the field (S) is ignored and all of the plurality of PUCCH power control parameter sets are activated. Here, when the second value configured in the field F is the other one of "1" and "0", only one PUCCH power control parameter set is activated / deactivated, and the field S is the method described in Embodiment D8 that indicates which PUCCH power control parameter set among the plurality of PUCCH power control parameter sets is activated / deactivated. Embodiment D11. The MAC_CE includes an octet spatial relationship information ID field, and the spatial relationship information ID field identifies the spatial relationship activated for one of the PUCCH resource and PUCCH resource group identified by the PUCCH resource index field of the previous octet, according to the method described in Embodiment D1. Embodiment D12. The MAC_CE includes a field E in the first octet indicating whether the PUCCH resource is updated by a spatial relationship or a power control set; a PUCCH resource index field in the second octet identifying one of the PUCCH resources and PUCCH resource groups associated with the MAC_CE; a third octet following the second octet, including a spatial relationship information identifier (ID) field and a field S, where the spatial relationship information ID identifies the spatial relationship and the field S identifies the PUCCH power control parameter set; and here, based on the value configured in the field E, one of the spatial relationship and the field S is activated for one of the PUCCH resources and PUCCH resource groups identified by the PUCCH resource index field in the second octet, according to the method described in Embodiment D1. Embodiment D13. The method according to any one of Embodiments D1 to D12, wherein at least two PUCCH power control parameter sets are explicitly configured and / or each set includes a set index value for identifying each PUCCH power control parameter set. Embodiment D14. The method according to any one of Embodiments D1 to D13, wherein at least two PUCCH power control parameter sets are implicitly configured and / or at least two PUCCH spatial relationships are configured for WD, and each PUCCH spatial relationship includes a PUCCH path loss reference identifier (ID), P0-PUCCH_ID, and a closed-loop index corresponding to each one of at least two PUCCH power control parameter sets. Embodiment D15. The method according to any one of Embodiments D1 to D14, wherein at least two PUCCH power control parameter sets are configured for WD only when at least two sounding reference signal resource (SRS) sets have parameter usage set to "codebook" or "non-codebook" for WD in the uplink (UL) bandwidth part (BWP) of the carrier frequency supported by the primary cell (Pcell). Embodiment D16. The MAC_CE comprises a 2-bit bandwidth part (BWP) field, a 5-bit serving cell identifier (ID) field, and a first reserved bit in the first octet; and a 7-bit PUCCH resource index field and a second reserved bit in the second octet; and a 1-bit field dedicated to each of two sets of PUCCH power control parameters in the third octet The method according to any one of Embodiments D1, D2, D13 to D15. Embodiment D17. The method according to Embodiment D16, wherein each set is activated for one of the PUCCH resource and the PUCCH resource group when the corresponding dedicated 1-bit field is set to one of "1" and "0", and deactivated when the corresponding dedicated 1-bit field is set to the other of "1" and "0". Embodiment D18. The method according to any one of Embodiments D16 and D17, wherein the third octet and / or the dedicated 1-bit field is ignored / absent in the MAC_CE, conditional on the value configured in the first or second reserved bit. Embodiment D19. The MAC CE comprises a 2-bit bandwidth part (BWP) field, a 5-bit serving cell identifier (ID) field, and a first set indicator in the first octet; and a 7-bit PUCCH resource index field and a second set indicator in the second octet The method according to any one of Embodiments D1, D2, D13 to D15. Embodiment D20. When the first setting indicator is set to one of "1" and "0", all of the plurality of PUCCH power control parameter sets are activated, and the second setting indicator is ignored. Here, when the first set indicator is set to the other of "1" and "0", the second set indicator indicates the activated PUCCH power control parameter set among the plurality of PUCCH power control parameter sets. The method according to Embodiment D19. Embodiment D21. When all of the plurality of PUCCH power control parameter sets configured in the WD are activated by the MAC_CE, the method includes transmitting each corresponding PUCCH transmission at different times for each PUCCH power control parameter set. The method according to any one of Embodiments D1 to D20. Embodiment D22. Further comprising receiving a configuration including one of the PUCCH resource and the PUCCH resource group; Here, each PUCCH power control parameter set is configured to include power control parameters for the WD to transmit signaling towards the corresponding transmission and reception point (TRP) associated with the network node, according to any of the methods described in Embodiments D1 - D21.

[0157] As will be understood by those skilled in the art, the concepts described herein can be embodied as a method, a data processing system, a computer program product, and / or a computer storage medium storing an executable computer program. Accordingly, the concepts described herein can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects, all of which are generally referred to herein as a "circuit" or a "module". Any process, step, action, and / or function described herein can be performed by and / or associated with a corresponding module that can be implemented in software and / or firmware and / or hardware. Further, the present disclosure can take the form of a computer program product on a tangible computer-usable storage medium having computer program code embodied in a medium that can be executed by a computer. Any suitable tangible computer-readable medium can be utilized, including a hard disk, a CD-ROM, an electronic storage device, an optical storage device, or a magnetic storage device.

[0158] Some embodiments are described herein with reference to flowcharts and / or block diagrams of methods, systems, and computer program products. It will be understood that each block of the flowcharts and / or block diagrams, and combinations of blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the block or blocks of the flowchart and / or block diagram.

[0159] These computer program instructions can also be stored in a computer-readable memory or storage medium, and the instructions stored in the computer-readable memory can direct a computer or other programmable data processing apparatus to function in a particular manner to produce a manufactured article that includes instruction means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0160] Also, the computer program instructions can be loaded onto a computer or other programmable device to cause a series of operational steps to be performed on the computer or other programmable device to generate a computer-implemented process such that the instructions which execute on the computer or other programmable device provide steps for implementing the functions / acts specified in the flowchart and / or block diagram or block.

[0161] It should be understood that the functions / operations described in the blocks may occur in an order different from that shown in the operation explanatory diagram. For example, two blocks shown consecutively may actually be executed substantially simultaneously, or depending on the related functions / operations, the blocks may be executed in the reverse order. In some of the figures, arrows are drawn on the communication paths to indicate the main direction of communication, but it should be understood that communication may occur in the direction opposite to the drawn arrows.

[0162] The computer program code for performing the operations of the concepts described herein can be written in an object-oriented programming language such as Java (registered trademark) or C++. However, the computer program code for performing the operations of the present disclosure can also be written in a conventional procedural programming language such as the "C" programming language. The program code may be executed entirely on the user's computer, partially executed on the user's computer as a stand-alone software package, partially executed on the user's computer and partially executed on a remote computer, or entirely executed on a remote computer. In the latter scenario, the remote computer may be connected to the user's computer via a local area network (LAN) or a wide area network (WAN), or connected to an external computer (e.g., via the Internet using an Internet service provider).

[0163] In connection with the foregoing description and drawings, many different embodiments are disclosed herein. It will be understood that it would be unduly repetitious and cumbersome to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any manner and / or combination, and this specification, including the drawings, is to be construed as constituting a complete written description of all combinations and subcombinations of the embodiments described herein, as well as of the methods and processes of making and using them, and as supporting claims directed to such combinations or subcombinations.

[0164] Those skilled in the art will appreciate that the embodiments described herein are not limited to those particularly shown and described above. Additionally, note that all of the accompanying drawings are not to scale unless otherwise indicated above. Various modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.

Claims

1. A network node configured to communicate with a wireless device (WD) (22), the network node comprising: a processing circuit (68) configured to generate a list of at least two power control parameter sets for configuring the WD for physical uplink control channel (PUCCH) power control applicable to at least one of at least one PUCCH resource and at least one PUCCH resource group; a wireless interface (62) in communication with the processing circuit (68), the wireless interface (62) configured to transmit a media access control (MAC) control element (CE) to the WD to activate at least one power control parameter set from the list of power control parameter sets applicable to at least one of (1) one PUCCH resource, (2) each of a plurality of PUCCH resources, (3) a plurality of PUCCH resource groups; comprising: the MAC_CE comprising: a bandwidth part (BWP) field and a serving cell identifier (ID) field in a first octet; a field indicating which one of one set and two sets of PUCCH power control parameters is activated; a 7-bit PUCCH resource index field in a second octet; a dedicated field for each of the two sets of PUCCH power control parameters in a third octet; including: a network node.

2. Each of the list of at least two power control parameter sets includes a PUCCH path loss reference signal identifier (ID), a target received power (P0-PUCCH) ID, a closed loop index, and a power control parameter set ID. The network node according to claim 1.

3. The processing circuit (68) is further configured to configure the WD using PUCCH repetitions to at least one transmission and reception point (TRP), each TRP being associated with at least one of the at least two power control parameter sets. The network node according to claim 1.

4. The MAC_CE includes a PUCCH resource identifier including two bit fields, each bit field respectively identifying a PUCCH power control parameter set from the list of at least two power control parameter sets. The network node according to claim 1.

5. The MAC_CE includes a bit field indicating which of two PUCCH power control sets and one PUCCH power control set is activated for at least one of (1) one PUCCH resource, (2) each of a plurality of PUCCH resources, and (3) a plurality of PUCCH resource groups. The network node according to claim 1.

6. The MAC_CE includes an octet spatial relationship information ID field, and the spatial relationship information ID field identifies a spatial relationship activated for one of one PUCCH resource from the at least one PUCCH resource and one PUCCH resource group from the at least one PUCCH resource group, which is identified by a PUCCH resource index field of a preceding octet. The network node according to claim 1.

7. At least two PUCCH spatial relationships are configured in the WD, and each PUCCH spatial relationship includes a PUCCH path loss reference signal identifier (ID), P0-PUCCH_ID, and a closed-loop index. The network node according to claim 1.

8. Each PUCCH power control parameter set includes power control parameters for the WD to calculate PUCCH transmission power directed to a corresponding transceiver point (TRP) associated with the network node. The network node according to claim 1.

9. A method implemented in a network node configured to communicate with a wireless device (WD) (22), the method comprising: Configuring the WD (S142) using a list of at least two power control parameter sets for physical uplink control channel (PUCCH) power control applicable to at least one of at least one PUCCH resource and at least one PUCCH resource group. Transmitting a media access control (MAC) control element (CE) to the WD (S144) to activate at least one power control parameter set from the list of power control parameter sets applicable to at least one of (1) one PUCCH resource, (2) each of a plurality of PUCCH resources, and (3) a plurality of PUCCH resource groups. comprising the MAC_CE includes a bandwidth part (BWP) field and a serving cell identifier (ID) field in the first octet, a field indicating which one of one set and two sets of PUCCH power control parameters is activated, a 7-bit PUCCH resource index field in the second octet, a dedicated field for each of the two sets of PUCCH power control parameters in the third octet, including method. **Claim 10** Each of the lists of the at least two power control parameter sets includes a PUCCH path loss reference signal identifier (ID), a target received power (P0-PUCCH) ID, a closed-loop index, and a power control parameter set ID. The method according to claim 9. **Claim 11** Further comprising configuring the WD using PUCCH repetitions to at least one transmit-receive point (TRP), each TRP being associated with at least one of the at least two power control parameter sets The method according to claim 9. **Claim 12** The MAC_CE includes a PUCCH resource identifier including two bit fields, each bit field identifying a PUCCH power control parameter set from the list of the at least two power control parameter sets. The method according to claim 9. **Claim 13** The MAC_CE includes a bit field indicating which of two PUCCH power control sets and one PUCCH power control set is activated for at least one of (1) one PUCCH resource, (2) each of a plurality of PUCCH resources, and (3) a plurality of PUCCH resource groups. The method according to claim 9. **Claim 14** The MAC_CE includes an octet spatial relationship information ID field, and the spatial relationship information ID field identifies a spatial relationship that is activated for one of one PUCCH resource from the at least one PUCCH resource and one PUCCH resource group from the at least one PUCCH resource group, which is identified by the PUCCH resource index field of the preceding octet. The method according to claim 9.

15. At least two PUCCH spatial relationships are configured in the WD, and each PUCCH spatial relationship includes a PUCCH path loss reference signal identifier (ID), P0-PUCCH_ID, and a closed-loop index. The method according to claim 9.

16. Each PUCCH power control parameter set includes power control parameters for the WD to calculate the PUCCH transmission power directed to the corresponding transmission and reception point (TRP) associated with the network node. The method according to claim 9.

17. A wireless device (WD) (22) configured to communicate with a network node, the WD comprising: A radio interface (82) configured to receive a configuration of a list of at least two power control parameter sets for physical uplink control channel (PUCCH) power control, which is applicable to at least one of at least one PUCCH resource and at least one PUCCH resource group; A processing circuit (84) configured to communicate with the radio interface (82) and set a transmission power level based at least in part on at least one of the at least two power control parameter sets in the list; Comprising: The MAC_CE is: In the first octet, a bandwidth part (BWP) field and a serving cell identifier (ID) field; A field indicating which one of one set and two sets of PUCCH power control parameters is activated; In the second octet, a 7-bit PUCCH resource index field; In the third octet, dedicated fields for each of the two sets of PUCCH power control parameters; Including: WD.

18. Each of the lists of the at least two power control parameter sets includes a PUCCH path loss reference signal identifier (ID), a target received power (P0-PUCCH) ID, a closed loop index, and a power control parameter set ID. The WD according to claim 17.

19. The processing circuit (84) is further configured to configure the WD using PUCCH repetitions to at least one transmission and reception point (TRP), and each TRP is associated with at least one of the at least two power control parameter sets. The WD according to claim 17.

20. The MAC_CE includes a PUCCH resource identifier including two bit fields, and each bit field respectively identifies a PUCCH power control parameter set from the list of the at least two power control parameter sets. The WD according to claim 17.

21. The MAC_CE includes a bit field indicating which of two PUCCH power control sets and one PUCCH power control set is activated for at least one of (1) one PUCCH resource, (2) each of a plurality of PUCCH resources, and (3) a plurality of PUCCH resource groups. The WD according to claim 17.

22. The MAC_CE includes an octet spatial relationship information ID field, and the spatial relationship information ID field identifies a spatial relationship activated for one of one PUCCH resource from the at least one PUCCH resource and one PUCCH resource group from the at least one PUCCH resource group, which is identified by a PUCCH resource index field of a preceding octet. The WD according to claim 17.

23. The MAC_CE is configured to constitute at least two PUCCH spatial relationships, and each PUCCH spatial relationship includes a PUCCH path loss reference signal identifier (ID), a P0-PUCCH_ID, and a closed loop index. The WD according to claim 17.

24. Each PUCCH power control parameter set includes power control parameters for the WD to calculate the PUCCH transmission power directed to the corresponding transmission and reception point (TRP) associated with the network node. The WD according to claim 17.

25. A method implemented in a wireless device (WD) (22) configured to communicate with a network node, the method comprising: Receiving (S146) a list of at least two power control parameter sets for physical uplink control channel (PUCCH) power control, applicable to at least one of at least one PUCCH resource and at least one PUCCH resource group; Setting a transmission power level based at least in part on at least one of the at least two power control parameter sets in the list (S148); Including, The MAC_CE includes In the first octet, a bandwidth part (BWP) field and a serving cell identifier (ID) field; A field indicating which one of a set and a set of PUCCH power control parameters is activated; In the second octet, a 7-bit PUCCH resource index field; In the third octet, dedicated fields for each of the two sets of PUCCH power control parameters; Including Method.

26. Each of the lists of the at least two power control parameter sets includes a PUCCH path loss reference signal identifier (ID), a target received power (P0-PUCCH) ID, a closed loop index, and a power control parameter set ID. The method according to claim 25.

27. Further comprising configuring the WD using PUCCH repetition to at least one transmit receive point (TRP), each TRP being associated with at least one of the at least two power control parameter sets. The method according to claim 25.

28. The MAC_CE includes a PUCCH resource identifier including two bit fields, each bit field identifying a PUCCH power control parameter set from the list of at least two power control parameter sets. The method according to claim 25.

29. The MAC_CE includes a bit field indicating which of two PUCCH power control sets and one PUCCH power control set is activated for at least one of (1) one PUCCH resource, (2) each of a plurality of PUCCH resources, and (3) a plurality of PUCCH resource groups. The method according to claim 25.

30. The MAC_CE includes an octet spatial relationship information ID field, and the spatial relationship information ID field identifies a spatial relationship that is activated for one of one PUCCH resource from the at least one PUCCH resource and one PUCCH resource group from the at least one PUCCH resource group, which is identified by the PUCCH resource index field of a preceding octet. The method according to claim 25.

31. The MAC_CE is configured to constitute at least two PUCCH spatial relationships, and each PUCCH spatial relationship includes a PUCCH path loss reference signal identifier (ID), P0-PUCCH_ID, and a closed-loop index. The method according to claim 25.

32. Each PUCCH power control parameter set includes power control parameters for the WD to calculate the PUCCH transmission power directed to a corresponding transmit-receive point (TRP) associated with the network node. The method according to claim 25.

Images