Power control for uplink control signaling

By setting independent power control states for each PUCCH format or format group and combining open-loop and closed-loop power control, the transmission power is dynamically adjusted, which solves the problem of insufficient flexibility of the power control framework in 5G NR systems, improves the reliability and efficiency of uplink control signaling, and optimizes UE power consumption and interference management.

CN123124072APending Publication Date: 2026-11-17NOKIA TECHNOLOGIES OY
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202610659520.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2025-05-16
Filing Date
2026-05-13
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

The existing power control framework lacks flexibility in 5G NR systems and is difficult to adapt to changing transmission characteristics, reliability requirements and interference conditions, resulting in limited reliability and efficiency of uplink control signaling.

Method used

It provides a flexible power control adjustment scheme, allowing independent setting of power control status for each PUCCH format or format group. Combining open-loop and closed-loop power control, it dynamically adjusts transmission power through DCI/PDCCH signaling, supports dedicated and public TPC commands, and reduces frequent RRC reconfiguration.

Benefits of technology

It enables precise power adjustment for different PUCCH formats, improves the reliability and efficiency of uplink control signaling, reduces signaling overhead, and optimizes UE power consumption and interference management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123124072A_ABST
    Figure CN123124072A_ABST
Patent Text Reader

Abstract

Embodiments of this disclosure relate to power control for uplink control signaling. The method (200) disclosed herein includes receiving a power control adjustment configuration specific to a Physical Uplink Control Channel (PUCCH) format from a second device (120), and receiving a power control command associated with the PUCCH format from the second device (120). The method (200) further includes determining a power adjustment value based on the received power control command and the corresponding power control adjustment configuration.
Need to check novelty before this filing date? Find Prior Art

Description

Technical fields: The exemplary embodiments of this disclosure relate to the field of wireless communication, and more specifically to apparatus, user equipment (UE), network nodes, and methods for providing power control for uplink control signaling. Background technology: Some abbreviations that can be found in the instruction manual and / or accompanying drawings are defined here as follows.

[0001]

[0002] In modern wireless communication systems such as 5G New Radio (NR), User Equipment (UE) can use the Physical Uplink Control Channel (PUCCH) to transmit uplink control information (UCI), including Hybrid Automatic Repeat Request (HARQ) acknowledgments, scheduling requests, and Channel State Information (CSI). Reliable transmission of this control information helps ensure proper scheduling, link adaptation, and feedback mechanisms within the network. To maintain the integrity and efficiency of uplink control signaling, both open-loop and closed-loop transmission power control is employed to dynamically adapt the UE's transmission power based on radio conditions, path loss, and interference levels.

[0003] However, existing power control frameworks apply transmission power control in a very general way, without sufficient flexibility to adapt to changing transmission characteristics, reliability requirements, or interference conditions. Summary of the Invention: The following describes aspects relating to the exemplary embodiments disclosed herein. It should be understood that these aspects are not intended to limit the scope of this disclosure. In fact, this disclosure may cover aspects that may not be set forth below.

[0004] The independent claims provide the subject matter for several aspects. Additional aspects are defined in the dependent claims.

[0005] Details of exemplary embodiments are set forth in the accompanying drawings and the following description. Other features, objects, and advantages of this disclosure will be apparent from the specification, drawings, and claims. Attached image description: Specific embodiments are described with reference to the accompanying drawings. The same reference numerals are used throughout the drawings to refer to the same features and components.

[0006] Figure 1 A wireless communication system in which example embodiments of the present disclosure may be implemented is shown; Figure 2 A method performed by a first device according to an example embodiment of the present disclosure is shown; Figure 3 A method performed by a first device according to an example embodiment of the present disclosure is shown; Figure 4 A method performed by a first device according to an example embodiment of the present disclosure is shown; Figure 5 A method performed by a second apparatus according to an example embodiment of the present disclosure is shown; Figure 6 A method performed by a second apparatus according to an example embodiment of the present disclosure is shown; Figure 7 A method performed by a second apparatus according to an example embodiment of the present disclosure is shown; Figure 8 Signaling diagrams of a first apparatus and a second apparatus according to exemplary embodiments of the present disclosure are shown; Figure 9 A block diagram of a first apparatus according to an exemplary embodiment of the present disclosure is shown; and Figure 10 A block diagram of a second apparatus according to an exemplary embodiment of the present disclosure is shown. Detailed Implementation

[0007] Example embodiments will now be described with reference to the accompanying drawings. The terminology used in this disclosure of the example embodiments shown in the drawings is not intended to be limiting. In the drawings, the same reference numerals denote the same elements.

[0008] It should be understood that although the terms "first," "second," etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element.

[0009] This specification may refer to "a," "an," or "some" embodiments in several places. This does not necessarily mean that every such reference is for the same embodiment, or that the feature applies only to a single embodiment. Individual features of different embodiments may also be combined to provide other embodiments.

[0010] As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless otherwise expressly stated. It will also be understood that, when used in this specification, the terms “comprising” and / or “including” specify the presence of the stated feature, integer, step, operation, element, and / or component, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or combinations thereof.

[0011] As used herein, whenever the phrase “at least one” or “one or more” precedes a list of elements, where the elements are connected by “and” or “or”, it means that at least any one of the elements, or at least some of the elements, or all of the elements are present. As used herein, whenever the phrase “one of” precedes a list of elements, where the elements are connected by “and” or “or”, it means that only one of the elements is present at a given moment, unless the context permits the inclusion of more than one element. Unless the relevant context otherwise indicates, the use of the term “or” should be understood as “inclusive or” rather than “exclusive or”. Unless otherwise specifically stated, or otherwise understood in the context in which it is used, conditional language, such as “may” or “can”, is generally intended to convey that certain embodiments may include certain features, elements, and / or steps, while other embodiments may exclude certain features, elements, and / or steps. Therefore, such conditional language is generally not intended to imply that one or more embodiments require features, elements, and / or steps in any way. It should be understood that when an element is referred to as “connected” or “coupled” to another element, it may be directly connected or coupled to the other element, or there may be intermediate elements. Furthermore, as used herein, “connected” or “coupled” can include wireless connections or couplings. As used herein, the term “and / or” includes any and all combinations and arrangements of one or more of the associated listed items. As used herein, the terms “at least one” and “one or more” mean “any one of at least one” and “any one of one or more”, respectively.

[0012] Unless otherwise defined, all terms used herein (including technical and scientific terms) shall have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. It will also be understood that terms such as those defined in common dictionaries shall be interpreted as having a meaning consistent with their meaning in the context of the relevant field, and shall not be interpreted in an idealized or overly formal sense unless expressly defined herein.

[0013] The accompanying drawings depict a simplified structure showing only some elements and functional entities, all of which are logical units whose implementation may differ from that shown. The connections shown are logical connections; actual physical connections may differ. Furthermore, all logical units described and depicted in the drawings include the software and / or hardware components required for the unit's operation. Additionally, each unit itself may implicitly include one or more components. These components may be operatively coupled to each other and configured to communicate with each other to perform the unit's functions.

[0014] As used herein, the term "circuit" may refer to at least one of the following: a) Implemented only in hardware circuitry (such as in analog, digital, and / or quantum circuitry); b) A combination of hardware circuitry and software, such as (if applicable): (i) a combination of (multiple) analog, digital, and / or quantum hardware circuitry with software / firmware, and (ii) any or all portions of (multiple) hardware processors (including (multiple) digital and / or quantum processors), software, and (multiple) memories, which work together to enable a device (such as a mobile device, computing device, or server) to perform various functions; or c) Any or all parts of (multiple) hardware circuits, such as (multiple) microprocessors, (multiple) processors and / or (multiple) quantum processors, which require software (e.g., firmware) to operate, but may not exist when the software is not required to operate.

[0015] This definition of "circuit" applies to all uses of the term in this application (including in any claim). As another example, as used herein, the term "circuit" also covers implementations of hardware circuitry or processors (or processors in general) or a portion thereof and their accompanying software and / or firmware. For instance, where applicable to a particular claim element, the term "circuit" also covers baseband integrated circuits or processor integrated circuits for mobile devices or similar integrated circuits in servers, cellular network devices, or other computing or networking devices.

[0016] In the following text, different example embodiments will be described using communication network architectures (such as 5G NR or 6G (sixth generation)) based on 3GPP (3rd Generation Partnership Project) standards for communication networks as examples of communication networks to which example embodiments can be applied, without limiting the example embodiments to such architectures.

[0017] The 5G NR Physical Uplink Control Channel (PUCCH) supports multiple PUCCH formats, referred to as PUCCH formats 0 to 4.

[0018] Uplink transmission power control (TPC) can be used to determine the transmission power of the physical layer (PHY-layer) uplink channel. Optimal TPC algorithms and parameterization strategies for uplink control channels can be provided: - Meet link quality objectives, such as detection probability. - Limit interference to other PUCCH transmissions to and from the same cell or (multiple) adjacent cells.

[0019] - Save energy (i.e., reduce battery consumption) In cellular communication systems, the transmission power of user equipment (UE) (also known as mobile station (MS), mobile terminal (MT), or terminal user station (ES)) is managed by a standard-specified formula that takes into account the target cell bandwidth received power specified by the base station, path loss estimation, transmission bandwidth, maximum output power, and static and dynamic power offsets.

[0020] For the 5G NR Physical Uplink Control Channel (PUCCH), the transmission power formula is explained here: As follows, the UE adjusts the state using PUCCH power control with index l for the k-th indicated TCI-State or TCI-UL-State (k=0 if not indicated) to enable the active uplink bandwidth portion (UL BWP) b of carrier f in primary cell c. ("PUCCH" ,b,f,c,k) (i,q_u,q_d,l) Use the given transmission power to send the PUCCH:

[0021] in, - During PUCCH transmission China targets service communities carrier The maximum output power of the UE configuration for the kth indicated TCI-State or TCI-UL-State.

[0022] - It is for the main community carrier The component provided by p0-nominal (Or if p0-nominal is not provided, then) dBm) and main cell carrier UL BWP activities The component provided by the p0-PUCCH value in P0-PUCCH The parameters are composed of the sum (if provided).

[0023] - It is the main community carrier UL BWP activities PUCCH transmission timing The bandwidth allocated to PUCCH resources, expressed in terms of the number of resource blocks, and It's an SCS configuration.

[0024] - The UE uses the RS resource index Calculated downlink path loss estimate in dB.

[0025] - It is the value of deltaF-PUCCH-f0 for PUCCH format 0, deltaF-PUCCH-f1 for PUCCH format 1, deltaF-PUCCH-f2 for PUCCH format 2, deltaF-PUCCH-f3 for PUCCH format 3, and deltaF-PUCCH-f4 for PUCCH format 4 (if provided); otherwise .

[0026] - It is the main community carrier UL BWP activities PUCCH transmission power adjustment component It is the main community carrier UL BWP activities PUCCH transmission timing Current PUCCH power control adjustment status ,in By mapping the TPC command field in the DCI format to predefined values, it is given value.

[0027] In the latest 3GPP specification, the PUCCH power control adjustment status index This depends on the spatial relationship information for signaling notification, or the applicable uplink / joint TCI status, or the PUCCH group for signaling notification during PUCCH cell handover. If used for the primary cell... carrier UL BWP activities Corresponding PUCCH power control adjustment status of The configuration of the value is provided by a higher layer. -

[0028] -[Spatial Relation Information] If the UE is provided with PUCCH-SpatialRelationInfo, then the UE is based on the spatial relationship information corresponding to... The p0-PUCCH-Id value and the corresponding The pucch-SpatialRelationInfoId value associated with the closedLoopIndex value is from The value is determined The value; -[PUCCH Cell Handover] Otherwise, if the UE is provided with more than one set of power control parameters for operation in FR1, and if the UE receives an activation command for PUCCH resources indicating one or both of the more than one set of power control parameters, the UE determines the appropriate power control parameter based on the closedLoopIndex value in one or both sets of power control parameters. The value; -[Default] Otherwise,

[0029] Power control adjustments specific to each PUCCH format or PUCCH format group are not supported.

[0030] PUCCH DTX is detected by the base station as no valid PUCCH transmission detected, which typically occurs during a momentary low PUCCH SINR. The No-Transmission (DTX) rate (DTXr) is the ratio of the count of PUCCH instances that are DTXed to the total count of PUCCH transmissions expected to be received from the UE.

[0031] However, even after OLPC+CLPC optimization, it is difficult to achieve acceptable DTXr simultaneously for all PUCCH formats used in a cell using the conventional TPC framework. Optimization is desired to improve PUCCH DTXr performance.

[0032] The proposed embodiments provide solutions for power control adjustment. The proposed embodiments provide multiple apparatuses and methods for power control adjustment in wireless communication networks.

[0033] Figure 1 An example of a wireless communication network 100 in which exemplary embodiments of the present disclosure may be implemented is shown. The network 100 may include at least a first device 110 and a second device 120 (the first device 110 is also referred to as a terminal device, and the second device 120 is also referred to as a network device).

[0034] In some example embodiments, the first device 110 may include a user equipment (UE) and may be any wireless communication device capable of transmitting and receiving radio signals. The first device 110 may be used to communicate with a radio access network (RAN) via an uplink channel. Non-limiting examples of the first device 110 include smartphones, tablets, laptops, etc. The first device 110 may include and / or be referred to as a "terminal device," "user equipment," "wireless transceiver unit," or another name.

[0035] In some example embodiments, the second device 120 may include a network node in a communication network (e.g., network 100) through which the first device 110 can access the network and receive services. The second device 120 may include and / or be referred to as a “base station,” “radio access network node,” “radio unit,” or another name. The second device 120 may operate according to one of several radio access technologies (RATs) in communication with the first device 110 and may be part of the RAN. The second device 120 may communicate with the first device 110 via a downlink channel.

[0036] In the wireless communication network 100, there may be radio coverage areas (referred to as "cells"). Cell 130 may be supported by the second device 120.

[0037] In the example, the proposed disclosure provides a TPC framework for the first device 110 and the second device 120, which supports and implements power control adjustments specific to each PUCCH format or specific to a set of PUCCH formats. In the proposed disclosure, for PUCCH power control adjustments... ,state The PUCCH format may vary depending on the application.

[0038] In the example, for the PUCCH format Power adjustment status This means that there is a separate CLPC state for each PUCCH format. In another example, the state... Covers a set of PUCCH formats, namely

[0039] In this proposed disclosure, all PUCCH formats share the same OLPC parameters (except for the deltaF and deltaTF parameters specific to the semi-static PUCCH format), while having separate CLPC adjustments.

[0040] In at least some cases, each DCI / PDCCH requires a single TPC command field, wherein the first device 110 can use the TPC command indicated via the DCI / PDCCH to determine the TPC accumulation, and thus determine the Tx power of the PUCCH format corresponding to the triggered / scheduled PUCCH transmission or the DCI / PDCCH.

[0041] In at least some cases, both dedicated TPCs and common TPCs for each adjustment state are supported. The application of TPC commands is flexible, whether for the power adjustment state of each PUCCH format or for a separate state for a group of PUCCH formats (one state per PUCCH format group). For example, NW can send: Option 1: TPC specifically applied to a PUCCH format. Option 2: TPC specifically applied to multiple PUCCH formats. Option 3: Common TPC applied to all PUCCH formats. The range or list of TPC commands can differ between adjustment states associated with a PUCCH format or a group of PUCCH formats.

[0042] The first device 110 can report information about the ability to support TPC adjustments specific to each PUCCH format or format group.

[0043] Figure 2 A flowchart of method 200 performed by first device 110 is shown. In step 202, method 200 provides receiving a power control adjustment configuration specific to the Physical Uplink Control Channel (PUCCH) format from second device 120. In step 204, method 200 provides receiving a power control command associated with the PUCCH format from second device 120. In step 206, method 200 provides determining a power adjustment value based on the received power control command and the corresponding power control adjustment configuration.

[0044] In the example, the power control commands include the Transmit Power Control (TPC) command.

[0045] In the example, the first device 110 is also configured to receive open-loop power control (OLPC) configuration from the second device to determine the base transmission power based on path loss estimation and one or more configuration parameters. The first device 110 is also configured to receive closed-loop power control (CLPC) configuration from the second device 120 to maintain a separate adjustment state for the PUCCH format.

[0046] In the example, the first device 110 is also configured to maintain a separate power control adjustment state for the PUCCH format, update the maintained power control adjustment state by accumulating the received power control commands corresponding to the PUCCH format, and calculate a power adjustment value based on the updated power control adjustment state.

[0047] In the example, the first device 110 is also configured to send PUCCH transmissions to the second device 120 using a PUCCH format with a transmission power obtained from at least one of the following: a corresponding power adjustment value of the PUCCH format; an OLPC power value; and a maximum transmission power limit.

[0048] In the example, power control adjustment configuration is received via Radio Resource Control (RRC) signaling messages or Media Access Control (MAC) control elements. Power control commands are received in Downlink Control Information (DCI) messages.

[0049] In the example, the range of power control commands differs for different PUCCH formats.

[0050] In the example, the first device is also configured to send information to the second device indicating the capability of the first device 110 to support PUCCH format-specific power adjustments.

[0051] Figure 3 A flowchart of method 300 performed by first device 110 is shown. In step 302, method 300 provides receiving a power control adjustment configuration for a set of Physical Uplink Control Channel (PUCCH) formats from second device 120, and in step 304, method 300 provides receiving a power control command associated with the PUCCH format set from second device 120. In step 306, method 300 provides determining a power adjustment value based on the received power control command and power control adjustment configuration.

[0052] In the example, the PUCCH format set includes one or more PUCCH formats.

[0053] In the example, the PUCCH format set is grouped based on at least one of similar duration or payload characteristics.

[0054] In the example, the power control commands include the transmit power control (TPC) commands applied to the PUCCH format set.

[0055] In the example, the first device 110 is also configured to receive a reset instruction from the second device 120, and upon receiving the reset instruction, reset the power control adjustment state of at least one PUCCH format in the PUCCH format set to: zero or a predefined value.

[0056] In the example, power control adjustment configuration is received via Radio Resource Control (RRC) signaling messages or Media Access Control (MAC) control elements, and power control commands are received in downlink control information (DCI) messages.

[0057] In the example, the range of power control commands differs for different sets of PUCCH formats.

[0058] In the example, the first device 110 is also configured to receive an open-loop power control (OLPC) configuration from the second device 120 to determine the base transmission power based on path loss estimation and one or more configuration parameters, or to receive a closed-loop power control (CLPC) configuration from the second device 120 to maintain a separate adjustment state for the PUCCH format set.

[0059] In the example, the first device 110 is also configured to maintain a separate power control adjustment state for the PUCCH format set, update the maintained power control adjustment state by accumulating the received power control commands corresponding to the PUCCH format set, and calculate a power adjustment value based on the accumulation and the updated power control adjustment state.

[0060] In the example, the first device 110 is also configured to use at least one PUCCH format from the PUCCH format set to send PUCCH transmissions to the second device 120 with transmission power obtained from at least one of the following: a corresponding power adjustment value for the corresponding PUCCH format; an OLPC power value; and a maximum transmission power limit.

[0061] In the example, the first device 110 is also configured to send information to the second device 120 instructing the first device 110 to support group-based power control adjustments.

[0062] Figure 4 A flowchart of method 400 performed by first device 110 is shown. In step 402, method 400 provides an indication of the applicability of a power control command received from second device 120, and in step 404, method 400 provides a method for determining a power adjustment value based on the indication of the applicability of the received power control command by selectively applying or ignoring the power control command.

[0063] In the example, the indication of applicability of power control commands includes at least one of the following: an activation indication for enabling power control commands, a deactivation indication for disabling power control commands, an activation indication for enabling power control command accumulation, or a deactivation indication for disabling power control command accumulation.

[0064] In the example, the indication of the applicability of the power control command includes applicability information for the Physical Uplink Control Channel (PUCCH) format or the set of PUCCH formats.

[0065] In the example, the indication of the applicability of the power control command is received via one of the following: Radio Resource Control (RRC) signaling messages, Media Access Control (MAC) control elements, or Downlink Control Information (DCI) messages.

[0066] In the example, the first device 110 is configured to receive an indication of power adjustment parameters for one or more PUCCH formats or for a set of PUCCH formats.

[0067] In the example, the indication of the power adjustment parameters is received via either a Radio Resource Control (RRC) signaling message or a Media Access Control (MAC) control element.

[0068] In the example, the first device 110 is also configured to: maintain a separate power control adjustment state for the PUCCH format; update the maintained power control adjustment state by accumulating or ignoring one or more power control commands corresponding to the PUCCH format received, based on an indication of the applicability of the power control commands; and calculate a power adjustment value based on the updated power control adjustment state.

[0069] Figure 5 A flowchart of method 500 performed by second device 120 is shown. In step 502, method 500 provides sending a power control adjustment configuration specific to the Physical Uplink Control Channel (PUCCH) format to at least one first device 110. In step 504, method 500 provides sending a power control command associated with the PUCCH format to at least one first device 110.

[0070] In the example, the second device 120 is also configured to receive capability information from at least one first device 110 indicating that at least one first device 110 supports PUCCH format-specific power adjustment.

[0071] Figure 6 A flowchart of method 600 performed by second device 120 is shown. In step 602, method 600 provides sending a power control adjustment configuration for a set of Physical Uplink Control Channel (PUCCH) formats to at least one first device 110. In step 604, method 600 further provides sending a power control command associated with the set of PUCCH formats to at least one first device 110.

[0072] In the example, the second device 120 is also configured to receive information from at least one first device 110 indicating the capability of the first device to support group-based power control adjustments.

[0073] Figure 7 A flowchart of method 700 performed by second device 120 is shown. In step 702, method 700 provides an indication of determining the applicability of a power control command for at least one first device 110, and in step 704, method 700 provides an indication of transmitting the applicability of the power control command to at least one first device 110.

[0074] In the example, the indication of power control command applicability includes at least one of the following: an activation indication for enabling power control commands for a PUCCH format, a deactivation indication for disabling power control commands for a PUCCH format, an activation indication for enabling power control command accumulation for a PUCCH format, a deactivation indication for disabling power control command accumulation for a PUCCH format, an activation indication for enabling power control commands for a set of PUCCH formats, a deactivation indication for disabling power control commands for a set of PUCCH formats, an activation indication for enabling power control command accumulation for a set of PUCCH formats, or a deactivation indication for disabling power control command accumulation for a set of PUCCH formats.

[0075] In the example, the second device 120 is also configured to send an indication to at least one first device 110 for power adjustment parameters for one or more PUCCH formats or for a set of PUCCH formats.

[0076] In some embodiments, the first device 110 may be designated or configured to receive an indication of activation or deactivation of the applicability of TPC commands or TPC accumulation for / per PUCCH format or group of PUCCH formats. This indication may be shared via at least one of RRC, MAC CE, and / or DCI.

[0077] If the first device 110 is instructed to deactivate the applicability of TPC commands or TPC accumulation for a PUCCH format or a group of PUCCH formats, the first device 110 may determine the Tx power for a PUCCH format or a PUCCH format in a group of PUCCH formats without using the indicated TPC commands.

[0078] In another example, the first device 110 may be specified or configured to receive a dedicated or shared MAC CE to enable dynamic indication or updates of power adjustment parameters (i.e., Delta_F) for one or more PUCCH formats or groups of PUCCH formats at a time.

[0079] The first device 110 may receive an indication of which one or more PUCCH formats or PUCCH format groups the MAC CE may include corresponding power adjustment parameter indications for. Alternatively, the first device 110 may receive an indication of the number of PUCCH formats or PUCCH format groups for which the MAC CE includes corresponding power adjustment parameter indications. As described above, this indication may be carried by the MAC CE (e.g., using a bitmap or using at least one bit / field) or the MAC CE subheader or by another MAC CE or by an RRC.

[0080] On the other hand, the first device 110 includes components for causing the first device 110 to perform the methods 200, 300 and 400 discussed above.

[0081] On the other hand, the second device 120 includes components for causing the second device 120 to perform the methods 500, 600 and 700 discussed above.

[0082] Components for the first device 110 and the second device 120 can be implemented in hardware and / or software (to be discussed later). Figure 9 and Figure 10 (Discussed herein). These include, for example, at least one processor 1104 / 1204 for executing computer program code / instructions to cause a corresponding device (e.g., a UE or a network node) to perform a corresponding method 200, 300, 400 / 500, 600, 700, and at least one memory 1102 / 1202 for storing the computer program code / instructions. The component may also include circuitry (as defined herein) for causing a corresponding first device 110 / second device 120 to perform a corresponding method 200, 300, 400, or method 500, 600, 700.

[0083] According to another aspect, a computer-readable medium (e.g., a non-transitory computer-readable medium) is provided. The computer-readable medium includes instructions that, when executed by the first device 110 / second device 120, cause the first device 110 / second device 120 to perform methods 200, 300, 400 or 500, 600, 700, respectively.

[0084] Figure 8 A first signaling diagram 800 is shown for the first device 110 and the second device 120. Signaling diagram 800 depicts the PUCCH power control signaling discussed below: In step 802, the second device 120 sends an RRC message to the first device 110, the RRC message including at least one of the following: one or more power control parameters (e.g., path loss compensation factor), power control adjustment configuration (e.g., mapping of TPC commands for adjusting power values), and an indication of CLPC applicability for each PUCCH format or format group.

[0085] In step 804, the first device 110 may receive a TPC command from the second device 120 via DCI or MAC CE.

[0086] In steps 806 and 808, the first device 110 is configured to check the applicability indication received in step 802 to check whether CLPC is activated for the relevant format or group, and then the first device 110 may apply CLPC; or if CLPC is deactivated, the first device 110 may ignore the CLPC command. The first device 110 is configured to apply a first CLPC power adjustment value to the first PUCCH format indicated by the TPC command and TPC configuration.

[0087] The first device 110 is configured to apply a second CLPC power adjustment value to a second PUCCH format indicated by a TPC command and a TPC configuration.

[0088] In step 810, the first device 110 performs transmission of the first PUCCH format with a transmission power based on the first CLPC power adjustment value, the OLPC power value, and the maximum transmission power limit.

[0089] In step 812, the first device 110 performs transmission of the second PUCCH format with a transmission power based on the second CLPC power adjustment value, the OLPC power value, and the maximum transmission power limit.

[0090] In step 814, the second device 120 is configured to calculate suitable or required future one or more TPC commands for the first and second PUCCH formats based on measurements and reports specific to each PUCCH format.

[0091] In the example, the PUCCH TPC command is signaled. The DCI (e.g., via 5G NR DCI format 2-2) can indicate that the PUCCH TPC command will be specifically applied to the 5G NR DCI format 2-2. A state can be applied to a specific set of states or to all states.

[0092] In order to determine the next PUCCH TPC command for a PUCCH format, the second device 120 may keep track of the accumulated TPC commands for each PUCCH format, the UE-specific PUCCH SINR and RSSI levels, the cell-specific interference and noise levels, the UE-specific Pcmax and power margin, and the UE-specific or cell-specific DTXr.

[0093] In the example, a signal can be sent to notify a PC adjustment status specific to one or more PUCCH formats if one or any combination of the following conditions are met. The transmission power increase command (e.g., ): -Condition 1: The estimated transmission power required by (multiple) associated PUCCH formats does not reach above Pcmax.

[0094] -Condition 2: The measured or predicted SINR or received power is lower than the target. -Condition 3: The DTXr of (multiple) associated PUCCH format measurements is higher than the target. - Condition 4: (Multiple) associated measured or predicted RSSI in PUCCH format is below the limit - Condition 5: The measured or predicted PUCCH interference to other UEs in the same cell or UEs in other cells is below the limit, or both.

[0095] In examples similar to those discussed above, a signal can be sent to indicate a PC adjustment status specific to one or more PUCCH formats if one or a combination of the following conditions may occur. Transmission power reduction command (e.g., ).

[0096] - Condition 6: The estimated transmission power required by (multiple) associated PUCCH formats does not reach below Pcmin.

[0097] - Condition 7: The measured or predicted SINR or received power of the state is higher than the target. - Condition 8: (Multiple) associated PUCCH format measurements of DTXr are below the target. - Condition 9: (Multiple) associated measured or predicted RSSI in PUCCH format exceeds the limit. - Condition 10: The measured or predicted PUCCH interference to other UEs in the same cell or UEs in other cells is higher than the limit, or both.

[0098] In the example, the accumulation of each PC adjustment state mapped to one or more PUCCH formats can be individually reset to zero or reset to the currently indicated TPC command. In another example, the accumulation of all states is simultaneously reset to zero or reset to the currently indicated TPC command.

[0099] In one or more implementations, this disclosure provides at least one of the following exemplary advantages: - The proposed disclosure enables closed-loop power control (CLPC) to be applied by PUCCH format or by format group, thereby allowing for more accurate and performance-optimized power adjustment that reflects the reliability and interference characteristics of different uplink control signaling formats.

[0100] - By allowing group-based adjustment of state and centralized CLPC applicability control, the proposed disclosure minimizes the need for frequent RRC reconfiguration for various formats, thereby reducing signaling overhead and improving control efficiency.

[0101] - The proposed disclosure supports dynamic activation or deactivation of CLPC applicability for specific PUCCH formats or format groups via signaling via Radio Resource Control (RRC), Media Access Control (MAC CE) elements, or Downlink Control Information (DCI). This provides the network with fine-grained control over which formats should use TPC accumulation, thereby helping to avoid unnecessary adjustments in low-impact scenarios.

[0102] - In the proposed disclosure, the target signal-to-interference-plus-noise ratio (SINR) range and transmit-free rate (DTXr) for each PUCCH format can be achieved simultaneously using only CLPC adjustment, thereby eliminating the need for additional open-loop power control (OLPC) parameters for each utilized PUCCH format to achieve the target.

[0103] - In the proposed disclosure, non-optimal PUCCH format-specific OLPC parameters can be overcome by PUCCH format-specific CLPC, and UE power saving and interference reduction can be achieved through PUCCH format-specific CLPC optimization.

[0104] - The proposed disclosure provides frequent RRC reconfiguration to adjust the PUCCH format, thereby avoiding the requirement for specific OLPC parameters.

[0105] - In the proposed disclosure, the PUCCH PC adjustment state framework for multiple spatial relationship information and PUCCH cell handover (or Transmitter Receiver Point (TRP) handover) can be extended to support states mapped to (multiple) PUCCH formats.

[0106] Figure 9 and Figure 10 Block diagrams are shown of a first device 110 and a second device 120 for implementing one or more exemplary embodiments of the present disclosure. The first device 110 may be or include a terminal device, etc. The second device 120 may be or include a base station, a next-generation B-node (gNB), etc.

[0107] The first device 110 and the second device 120 may each include processors 1104 and 1204 for controlling the corresponding operations of the first device 110 and the second device 120. Processors 1104 / 1204 may also be referred to as a central processing unit (CPU). Processors 1104 / 1204 may be implemented in various ways, including circuitry, at least one processing core, one or more coprocessors, one or more multi-core processors, one or more controllers, processing circuitry, other processing elements including integrated circuits (e.g., application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), etc.), or some combination thereof.

[0108] The first device 110 and the second device 120 may each include a memory 1102 and a memory 1202, respectively. The memory 1102 / 1202 may include both read-only memory (ROM) and random access memory (RAM), and may provide instructions and data to the processor 1104 / 1204, respectively. The memory 1102 and the processor 1104 of the first device 110 may be operatively coupled. Similarly, the memory 1202 and the processor 1204 of the second device 120 may be operatively coupled.

[0109] Memory 1102 / 1202 may store instructions, such as computer-readable instructions / computer program code. The computer-readable instructions / computer program code may be pre-stored in memory 1102 / 1202, or alternatively or additionally, they may be received by the first device 110 and the second device 120 via electromagnetic carrier signals and / or copied from a physical entity such as a computer program product. Execution of the computer-readable instructions by processor 1104 / 1204 may cause the first device 110 or the second device 120 to perform the example embodiments described herein, such as... Figures 2 to 8 The steps outlined in the document.

[0110] The first device 110 and the second device 120 may each include transmitter / receiver (TX / RX) circuits 1106 / 1206, and may further include transmitters 1108 / 1208 and receivers 1110 / 1210. The TX / RX circuits 1106 of the first device 110 and 1206 of the second device 120 may enable them to transmit or receive data, respectively. The first device 110 and the second device 120 may include (not shown) multiple antennas, transmitters, and receivers.

[0111] In some example embodiments, the first device 110 and the second device 120 may each include components that enable them to perform... Figures 2 to 8The component of the steps / operations (if applicable). This component can be implemented in any suitable form. For example, the component can be implemented at least in a circuit, a combination of memory 1102 / 1202, processor 1104 / 1204, TX / RX circuit 1106 / 1206, or software module.

[0112] Example embodiments of the present disclosure have been disclosed in the accompanying drawings and description. Although specific terminology has been used, it is used in a general and descriptive sense only and not for limiting purposes. It will be apparent to those skilled in the art that various modifications and variations can be made to the embodiments disclosed herein that are consistent with the present disclosure without departing from the spirit and scope of the present disclosure. Other embodiments consistent with the present disclosure will become apparent upon consideration of the description in the specification and the present disclosure.

[0113] Furthermore, the various implementations of this disclosure can be described with reference to the following terms, and their features can be combined in any reasonable manner.

[0114] Clause 1. A first apparatus (110) comprising: at least one processor (1104); and at least one memory (1102) storing instructions, said instructions, when executed by said at least one processor (1104), causing the first apparatus (110) to at least: receive a power control adjustment configuration specific to a Physical Uplink Control Channel (PUCCH) format from a second apparatus (120); receive a power control command associated with said PUCCH format from the second apparatus (120); and determine a power adjustment value based on the received power control command and the corresponding power control adjustment configuration.

[0115] Clause 2. The first device (110) according to Clause 1, wherein the power control command includes a Transmit Power Control (TPC) command.

[0116] Clause 3. The first device (110) according to any one of the preceding clauses, wherein the first device (110) is further configured to: receive an open-loop power control (OLPC) configuration from the second device (120) to determine a base transmission power based on path loss estimation and one or more configuration parameters; or receive a closed-loop power control (CLPC) configuration from the second device (120) to maintain a separate adjustment state for the PUCCH format.

[0117] Clause 4. The first device (110) according to any one of the preceding clauses, wherein the first device (110) is further configured to: maintain a separate power control adjustment state for the PUCCH format; update the maintained power control adjustment state by accumulating the received power control commands corresponding to the PUCCH format; and calculate the power adjustment value based on the updated power control adjustment state.

[0118] Clause 5. The first device (110) according to any one of the preceding clauses, wherein the first device (110) is further configured to: use the PUCCH format to send PUCCH transmissions to the second device (120) with a transmission power obtained from at least one of the following: a corresponding power adjustment value of the PUCCH format; an OLPC power value; and a maximum transmission power limit.

[0119] Clause 6. The first apparatus (110) according to any one of the preceding clauses, wherein the power control adjustment configuration is received via a Radio Resource Control (RRC) signaling message or a Media Access Control (MAC) control element, and wherein the power control command is received in a Downlink Control Information (DCI) message.

[0120] Clause 7. The first device (110) according to any one of the preceding clauses, wherein the range of the power control commands is different for different PUCCH formats.

[0121] Clause 8. The first device (110) according to any one of the preceding clauses, wherein the first device (110) is further configured to: send to the second device (120) information indicating that the first device (110) supports PUCCH format-specific power adjustment capability.

[0122] Clause 9. A second apparatus (120) comprising: at least one processor (1204); and at least one memory (1202) storing instructions, which, when executed by the at least one processor (1204), cause the second apparatus (120) to at least: send a power control adjustment configuration specific to a Physical Uplink Control Channel (PUCCH) format to at least one first apparatus (110); and send a power control command associated with the PUCCH format to the at least one first apparatus (110).

[0123] Clause 10. The second device (120) according to Clause 9, wherein the second device (120) is further configured to: receive from the at least one first device (110) capability information indicating that the at least one first device (110) supports PUCCH format-specific power adjustment.

[0124] Clause 11. A method (200) for a first device (110) comprising: receiving a power control adjustment configuration specific to a Physical Uplink Control Channel (PUCCH) format from a second device (120); receiving a power control command associated with the PUCCH format from the second device (120); and determining (206) a power adjustment value based on the received power control command and the corresponding power control adjustment configuration.

[0125] Clause 12. A method (500) for a second device (120) comprising: sending (502) a power control adjustment configuration specific to a Physical Uplink Control Channel (PUCCH) format to at least one first device (110); and sending (504) a power control command associated with the PUCCH format to the at least one first device (110).

[0126] Clause 13. A terminal device (110) comprising: a component for performing the method (200) according to Clause 11.

[0127] Clause 14. A network device (120) comprising: a component for performing the method (500) according to Clause 12.

Claims

1. A first device for communication, comprising: At least one processor; as well as At least one memory storing instructions, which, when executed by the at least one processor, cause the first device to at least: Receive power control adjustment configurations in the format specific to the Physical Uplink Control Channel (PUCCH) from the second device; Receive power control commands associated with the PUCCH format from the second device; as well as The power adjustment value is determined based on the received power control command and the corresponding power control adjustment configuration.

2. The first apparatus according to claim 1, wherein the power control command includes a Transmit Power Control (TPC) command.

3. The first device according to claim 1 or 2, wherein the first device is further configured to: Receive open-loop power control (OLPC) configuration from the second device to determine the base transmission power based on path loss estimation and one or more configuration parameters; or Receive closed-loop power control (CLPC) configuration from the second device to maintain a separate adjustment state for the PUCCH format.

4. The first device according to claim 1 or 2, wherein the first device is further configured to: Maintain a separate power control adjustment state for the aforementioned PUCCH format; The maintained power control adjustment state is updated by accumulating the received power control commands corresponding to the PUCCH format; and The power adjustment value is calculated based on the updated power control adjustment state.

5. The first device according to claim 1 or 2, wherein the first device is further configured to: Using the PUCCH format, PUCCH transmissions are sent to the second device with transmission power obtained from at least one of the following: The corresponding power adjustment value in the PUCCH format; OLPC power values; and Maximum transmission power limit.

6. The first apparatus according to claim 1 or 2, wherein the power control adjustment configuration is received via a Radio Resource Control (RRC) signaling message or a Media Access Control (MAC) control element, and The power control command is received in the downlink control information (DCI) message.

7. The first apparatus according to claim 1 or 2, wherein the range of the power control commands is different for different PUCCH formats.

8. The first device according to claim 1 or 2, wherein the first device is further configured to: Send information to the second device indicating the first device's ability to support PUCCH format-specific power adjustment.

9. A second means for communication, comprising: At least one processor; as well as At least one memory storing instructions, which, when executed by the at least one processor, cause the second means to at least: Send a power control adjustment configuration specific to the Physical Uplink Control Channel (PUCCH) format to at least one first device; as well as Send a power control command associated with the PUCCH format to the at least one first device.

10. The second device according to claim 9, wherein the second device is further configured to: Receive from the at least one first device information indicating that the at least one first device supports power adjustment specific to the PUCCH format.