Transmission of Power Control Commands

Abstract

Methods and apparatuses for the transmission of power control commands are disclosed. In one embodiment, a method at a UE includes receiving two or more TPC commands for PUCCH resources of the UE in a cell, each PUCCH resource being associated with a higher layer index value configured for a CORESET, determining, based on the higher layer index value, a TPC command for each PUCCH resource; and transmitting each PUCCH resource using a power according to the determined TPC command.

Description

Technical Field

[0001] The subject matter disclosed herein generally relates to wireless communication and, more particularly, to methods and apparatuses for the transmission of power control commands. Background Art

[0002] The following abbreviations are defined herein, some of which are mentioned in the following description: 3rd Generation Partnership Project (3GPP), Frequency Division Duplex (FDD), Long Term Evolution (LTE), New Radio (NR), Very Large Scale Integration (VLSI), Random Access Memory (RAM), Read Only Memory (ROM), Erasable Programmable Read Only Memory (EPROM or Flash Memory), Compact Disc Read Only Memory (CD-ROM), Local Area Network (LAN), Wide Area Network (WAN), User Equipment (UE), Uplink (UL), Evolved Node B (eNB), Next Generation Node B (gNB), Downlink (DL), Central Processing Unit (CPU), Graphics Processing Unit (GPU), Field Programmable Gate Array (FPGA), Dynamic RAM (DRAM), Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), Physical Downlink Control Channel (PDCCH), Sounding Reference Signal (SRS), SRS Resource Indicator (SRI), Downlink Control Information (DCI), Resource Block (RB), Time Division Duplex (TDD), Radio Resource Control (RRC), Medium Access Control (MAC), Transmission and Reception Point (TRP), Transmission Power Control (TPC), Multiple Input Multiple Output (MIMO), Control Resource Set (CORESET), Radio Network Temporary Identifier (RNTI), Primary Cell (PCell), Secondary Cell (SCell), Acknowledgment (ACK), Negative ACK (NACK).

[0003] In NR Release 15, transmissions from only a single TRP (Transmission and Reception Point) or panel are supported. DCI with format 2_2 scrambled by TPC-PUCCH-RNTI is used to transmit TPC commands for PUCCH for a group of UEs. Specifically, block number 1, block number 2, ……, block number N are included in DCI with format 2_2 for N UEs. Each block number can be used by an individual UE to determine its unique TPC command field. Each UE can determine the unique TPC command field based on the higher layer parameter tpc-IndexPCell or tpc-IndexPUCCH-SCell for a cell (PCell or SCell).

[0004] For each block, the following fields are defined:

[0005] Closed-loop indicator: For DCI format 2_2 scrambled with TPC-PUCCH-RNTI, if the UE is not configured with the higher layer parameter twoPUCCH-PC-AdjustmentStates, this field has 0 bits. Otherwise (i.e., the UE is configured with the higher layer parameter twoPUCCH-PC-AdjustmentStates), this field has 1 bit;

[0006] TPC command: 2 bits. This TPC command is only applied to the closed-loop indicated by the closed-loop indicator field.

[0007] In NR Release 16, multi-TRP / panel MIMO transmission is supported. In Release 16, at least for separate ACK / NACK feedback, multiple PUCCH resources transmitted to different TRPs within a slot are supported. As Figure 1 illustrated, PUCCH resource #0 and PUCCH resource #1 are transmitted within the same slot targeting TRP #0 and TRP #1 respectively. Independent power control including open-loop power control and closed-loop power control for different PUCCH resources targeting different TRPs is necessary to cope with different channel environments. Beam-specific open-loop power control for PUCCH is supported in Release 15 for FR2 and can be directly extended to the multi-TRP scenario. However, how to transmit the TPC (Transmission Power Control) commands for closed-loop power control for different PUCCH resources targeting different TRPs remains unknown. SUMMARY OF THE INVENTION

[0008] An object of the present application is to propose a method and apparatus for transmitting power control commands.

[0009] In one embodiment, a method at a UE includes receiving two or more TPC commands for PUCCH resources of a UE in a cell, each PUCCH resource being associated with a higher layer index value configured for a CORESET, determining a TPC command for each PUCCH resource according to the higher layer index value; and transmitting each PUCCH resource using a power according to the determined TPC command.

[0010] In some embodiments, each TPC command is carried in a DCI with format 2_2 scrambled by a TPC-PUCCH-RNTI. In some embodiments, the TPC command carried by the DCI transmitted from a CORESET is determined to be the TPC command for the PUCCH resource associated with the same higher layer index value configured for the CORESET. In some other embodiments, the TPC command associated with a closed-loop index is determined to be the TPC command for the PUCCH resource associated with the higher layer index value associated with the closed-loop index.

[0011] In another embodiment, all TPC commands are carried in a single DCI with format 2_2, where the same number of block number indexes as the number of different higher layer index values are configured for UEs in the cell. In some embodiments, each block with a block number index value contains one TPC command, and the one TPC command is determined to be the TPC command for the PUCCH resource associated with the higher layer index value associated with the block number index value.

[0012] In some embodiments, the method at the base station unit includes transmitting two or more TPC commands for the PUCCH resources of UEs in the cell, each PUCCH resource being associated with a higher layer index value configured for a CORESET; and receiving each PUCCH resource transmitted from the UE using the power according to the TPC command determined according to the higher layer index value.

[0013] In yet another embodiment, a UE includes a receiver configured to receive two or more TPC commands for the PUCCH resources of the UE in the cell, each PUCCH resource being associated with a higher layer index value configured for a CORESET; a processor configured to determine the TPC command for each PUCCH resource according to the higher layer index value; and a transmitter configured to transmit each PUCCH resource using the power according to the determined TPC command.

[0014] In a further embodiment, the base station unit includes a transmitter configured to transmit two or more TPC commands for the PUCCH resources of UEs in the cell, each PUCCH resource being associated with a higher layer index value configured for a CORESET; and a receiver configured to receive each PUCCH resource transmitted from the UE using the power according to the TPC command determined according to the higher layer index value.

[0015] Those skilled in the art will understand that the effects that the present disclosure can achieve are not limited to what has been specifically described above, and the above and other effects that the present disclosure can achieve will be more clearly understood from the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] A more specific description of the embodiments briefly described above will be rendered by reference to specific embodiments illustrated in the accompanying drawings. Understanding that these drawings depict only some embodiments and should not therefore be considered a limitation of scope, the embodiments will be described and illustrated with additional details and particulars by using the drawings, in which:

[0017] Figure 1 illustrates PUCCH resources targeted at multiple TRPs;

[0018] Figure 2 illustrates the transmission of TPC commands according to a first embodiment;

[0019] Figure 3 illustrates the transmission of TPC commands according to a third embodiment;

[0020] Figure 4 is a schematic flowchart illustrating an embodiment of a method for transmitting power control commands;

[0021] Figure 5 is a schematic flowchart illustrating another embodiment of a method for transmitting power control commands; and

[0022] Figure 6 is a schematic block diagram illustrating an apparatus according to an embodiment. Detailed Description

[0023] As will be understood by those skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and hardware aspects, which may generally be referred to herein as a "circuit", "module", or "system". Additionally, embodiments may take the form of a program product embodied in one or more computer-readable storage devices storing machine-readable code, computer-readable code, and / or program code referred to hereinafter as "code". The storage device may be tangible, non-transitory, and / or non-transmissive. The storage device may not embody a signal. In certain embodiments, the storage device merely employs a signal for accessing the code.

[0024] Certain functional units described in this specification may be marked as "modules" to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit including custom very large scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, etc.

[0025] The module can also be implemented in code and / or software for execution by various types of processors. The code identifying the module can, for example, include one or more physical or logical blocks of executable code, which can, for example, be organized as objects, procedures, or functions. However, the executable files identifying the module need not be physically located together, but can include different instructions stored in different locations, which, when logically joined together, include the module and implement the stated purpose of the module.

[0026] In fact, the module of code can contain a single instruction or many instructions and can even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, herein, the operational data can be identified and depicted within the module and can be embodied in any suitable form and organized within any suitable type of data structure. The operational data can be collected as a single data set or can be distributed over different locations, including on different computer-readable storage devices. In the case where the module or portions of the module are implemented in software, the software portions are stored on one or more computer-readable storage devices.

[0027] Any combination of one or more computer-readable media can be utilized. The computer-readable media can be a computer-readable storage medium. The computer-readable storage medium can be a storage device storing the code. The storage device can be, for example, but not necessarily, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micro-mechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0028] A non-exhaustive list of more specific examples of storage devices will include the following: an electrical connection with one or more wires, a portable computer floppy disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, the computer-readable storage medium can be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0029] The code for performing the operations of the embodiments can include any number of lines and can be written in any combination of one or more programming languages, including object-oriented programming languages such as Python, Ruby, Java, Smalltalk, C++, etc., and conventional procedural programming languages such as the "C" programming language, and / or machine languages such as assembly language. The code can be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the last scenario, the remote computer can be connected to the user's computer via any type of network including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0030] References to "one embodiment", "an embodiment", or similar language throughout the specification mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, unless otherwise explicitly stated, the appearances of the phrases "in one embodiment", "in an embodiment", and similar language throughout the specification may, but do not necessarily, all refer to the same embodiment, but rather mean "one or more but not all embodiments". Unless otherwise explicitly specified, the terms "comprises", "comprising", "has", and their variants mean "including but not limited to". Unless otherwise explicitly specified, an enumerated listing of items does not imply that any or all of the items are mutually exclusive. Unless otherwise explicitly specified, the terms "a", "an", and "the" also refer to "one or more".

[0031] In addition, the described features, structures, or characteristics of the various embodiments can be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of the embodiments. However, those skilled in the relevant art will recognize that the embodiments can be practiced without one or more of the specific details or with other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the embodiments.

[0032] Aspects of various embodiments will now be described with reference to the schematic flowcharts and / or schematic block diagrams of methods, apparatuses, systems, and program products according to the embodiments. It will be understood that each block of the schematic flowcharts and / or schematic block diagrams, and combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. This code can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions executed via the processor of the computer or other programmable data processing apparatus create a device for implementing the functions specified in the schematic flowchart and / or schematic block diagram.

[0033] The code can also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to operate in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions that implement the functions specified in the block or blocks of the schematic flowchart and / or schematic block diagram.

[0034] The code can also be loaded onto a computer, other programmable data processing apparatus, or other devices, so that a series of operational steps are performed on the computer, other programmable apparatus, or other devices to produce a computer-implemented process, such that the code executed on the computer or other programmable apparatus provides a process for implementing the functions specified in the block or blocks of the flowchart and / or block diagram.

[0035] The schematic flowcharts and / or schematic block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods, and program products according to various embodiments. In this regard, each block in the schematic flowcharts and / or schematic block diagrams may represent a module, segment, or portion of code that includes one or more executable instructions for implementing the specified logical function(s).

[0036] It should also be noted that in some alternative implementations, the functions noted in the blocks may not occur in the order indicated in the figures. For example, depending on the functions involved, two blocks shown in succession may be executed substantially simultaneously, or the blocks may sometimes be executed in the reverse order. Other steps and methods that are equivalent in function, logic, or effect to one or more blocks or portions of the figures shown are conceivable.

[0037] Although various arrow types and line types may be employed in flowcharts and / or block diagrams, they are understood not to limit the scope of the corresponding embodiments. In fact, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiments. For example, an arrow may indicate a waiting or monitoring period of unspecified duration between the enumerated steps of the depicted embodiments. It will also be noted that each block of the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, can be implemented by a system based on dedicated hardware that performs the specified function or action, or by a combination of dedicated hardware and code.

[0038] The description of elements in the various figures may refer to elements of the previous figure. Like reference numerals in all figures refer to the same elements, including alternative embodiments of the same element.

[0039] According to the first embodiment, different TPC commands are carried in DCIs with format 2_2 transmitted from different TRPs, where each TPC command is carried in a separate DCI. Specifically, the TPC command carried by a DCI with format 2_2 is applied only to the PUCCH resources associated with the same higher layer index (e.g., CORESETPoolIndex) value configured for the CORESET transmitting the DCI.

[0040] In particular, the PUCCH resources targeted at a specific TRP are each associated with a CORESETPoolIndex value. All CORESETs configured for a specific TRP are configured with the same CORESETPoolIndex value. Thus, the TPC command carried in a DCI with format 2_2 transmitted in a CORESET configured for a specific TRP (the CORESET is configured with a CORESETPoolIndex value) is applied only to the PUCCH resource group associated with the same CORESETPoolIndex value (each PUCCH resource in the PUCCH resource group targeted at a specific TRP is associated with the same CORESETPoolIndex value). Therefore, all PUCCH resources targeted at a specific TRP can be transmitted using power according to the TPC command carried in the DCI with format 2_2 transmitted in the CORESET configured for the specific TRP, because the CORESET transmitting the DCI is configured for the same CORESETPoolIndex value associated with the PUCCH resource group targeted at the specific TRP.

[0041] Figure 2The figure illustrates an example of the first embodiment. Two DCIs with format 2_2, each scrambled by a TPC-PUCCH-RNTI, are transmitted from CORESET#3 configured for TRP#1 and CORESET#0 configured for TRP#0 in time slots n and n+1, respectively. CORESET#0 is configured with the higher layer parameter CORESETPoolIndex = 0. CORESET#3 is configured with the higher layer parameter CORESETPoolIndex = 1. These two DCIs are received by the UE in time slots n and n+1, respectively.

[0042] Two PUCCH resources, namely, PUCCH resource #1 and PUCCH resource #2, are targeted at TRP#0 and TRP#1, respectively, i.e., they are required to be transmitted to TRP#0 and TRP#1 in time slot n+2, respectively. PUCCH resource #1 is associated with CORESETPoolIndex = 0. PUCCH resource #2 is associated with CORESETPoolIndex = 1.

[0043] According to the first embodiment, the TPC command carried in the DCI with format 2_2 transmitted in CORESET#0 is applied only to PUCCH resource #1 because CORESET#0 is configured with the higher layer parameter CORESETPoolIndex = 0 associated with PUCCH resource #1. Similarly, the TPC command carried in the DCI with format 2_2 transmitted in CORESET#3 is applied only to PUCCH resource #2 because CORESET#3 is configured with the higher layer parameter CORESETPoolIndex = 1 associated with PUCCH resource #2.

[0044] Therefore, PUCCH resource #1 is transmitted to TRP#0 using the power according to the TPC command included in the DCI transmitted in CORESET#0 configured for TRP#0. PUCCH resource #2 is transmitted to TRP#1 using the power according to the TPC command included in the DCI transmitted in CORESET#3 configured for TRP#1.

[0045] Figure 2 The figure illustrates an example in which a PUCCH resource is transmitted to two TRPs. Needless to say, under the condition that a PUCCH resource is transmitted to three or more TRPs, the TPC commands for the PUCCH resources targeted at each TRP can be carried in the same number (equal to the number of TRPs) of DCIs transmitted in the respective CORESETs configured for the TRPs.

[0046] It can be seen that, according to the first embodiment, the TPC command can be carried in the DCI with format 2_2 in the same manner as in Release 15. The PUCCH resource targeted at one TRP is transmitted using the power of the TPC command carried in the DCI with format 2_2 transmitted in the CORESET configured for the one TRP. That is, the PUCCH resource targeted at each TRP is transmitted using the power of the TPC command carried in the DCI with format 2_2 transmitted in the CORESET configured for the each TRP. In this way, the TPC commands for transmitting two or more TRPs are supported.

[0047] According to the first embodiment, each of the TRPs targeted by the PUCCH resource has to transmit the DCI with format 2_2 carrying the TPC command.

[0048] According to the second embodiment, the TRP can transmit the DCI with format 2_2 carrying the TPC command for the PUCCH targeted at another TRP.

[0049] In Release 15, up to two closed loops are supported for PUCCH power control. That is, a 1-bit closed-loop indicator field is included in each block contained in the DCI with format 2_2. The closed-loop indicator has two possible index values, for example, index = 0 and index = 1. Each closed-loop index value is associated with a CORESETPoolIndex value.

[0050] According to the second embodiment, each PUCCH resource group targeted at a TRP is associated with the same higher-layer index (e.g., CORESETPoolIndex) value, and each higher-layer index value is associated with a dedicated closed-loop index value. As a result, the PUCCH resource targeted at a TRP is associated with a dedicated closed-loop index value. The PUCCH resources associated with the same CORESETPoolIndex value only use the TPC command transmitted for the dedicated closed-loop index value. The PUCCH resources associated with the same CORESETPoolIndex value are also associated with a dedicated closed-loop index value. Since the closed-loop indicator has two possible index values, the second embodiment can support the transmission of the TPC commands for the PUCCH resources targeted at up to 2 TRPs.

[0051] For example, the TPC command for the first closed loop (i.e., closed loop index 0) carried in the DCI with format 2_2 is only applied to the PUCCH resources associated with the higher layer parameter CORESETPoolIndex having a lower value (e.g., CORESETPoolIndex = 0). That is, the lower CORESETPoolIndex value is associated with the TPC command for the first closed loop. The TPC command for the second closed loop (i.e., closed loop index 1) carried in the DCI with format 2_2 is only applied to the PUCCH resources associated with the higher layer parameter CORESETPoolIndex having a higher value (e.g., CORESETPoolIndex = 1). That is, the higher CORESETPoolIndex value is associated with the TPC command for the second closed loop.

[0052] It can be seen that according to the second embodiment, the TPC command can be carried in the DCI with format 2_2 in the same manner as in Release 15. The PUCCH resources targeted at one TRP are transmitted using the power according to the TPC command carried in the DCI with format 2_2 for the first closed loop. The PUCCH resources targeted at another TRP are transmitted using the power according to the TPC command carried in the DCI with format 2_2 for the second closed loop. In this way, the transmission of TPC commands for up to two TRPs is supported.

[0053] According to the first embodiment and the second embodiment, the TPC command can be carried in the DCI with format 2_2 in the same manner as in Release 15. On the other hand, each TPC command is carried in a separate DCI with format 2_2. That is, the same number of DCIs as the number of TRPs to be targeted (to which the PUCCH resources are transmitted) have to be transmitted to the UE.

[0054] According to the third embodiment, two or more block number indices can be configured for the UE in the DCI with format 2_2. In this way, two or more TPC commands can be carried in the DCI with format 2_2 for the UEs in the cell. This is particularly useful for some cases where the DCI with format 2_2 can only be transmitted from one TRP. For example, the common search space (CSS) can be configured only for one TRP and not for another TRP. Since the DCI with format 2_2 can only be transmitted from the TRP configured with CSS, it cannot be transmitted from the TRP not configured with CSS.

[0055] Each block contains a TPC command for a PUCCH resource targeted at a TRP. This can be achieved by configuring each block containing the TPC command with a block number index value associated with a specific higher layer index (e.g., CORESETPoolIndex) value associated with the PUCCH resource targeted at a TRP. Incidentally, the PUCCH resources associated with the same CORESETPoolIndex value are targeted at the same TRP.

[0056] For example, the UE can be configured with two block number indexes. Thus, two TPC command fields can be decoded by the UE for the cell from DCI with format 2_2. The first decoded TPC command (e.g., contained in the block with number index value = 0) is only applied to the PUCCH resources associated with the CORESETPoolIndex value = 0 (or the CORESETPoolIndex with a lower value). The second decoded TPC command (e.g., contained in the block with number index value = 1) is only applied to the PUCCH resources associated with the CORESETPoolIndex value = 1 (or the CORESETPoolIndex with a higher value). The higher layer index (e.g., CORESETPoolIndex) value can also be directly configured in the PUCCH-TPC-CommandConfig information element for each (TPC command) block number index, as in the following example:

[0057]

[0058] In the above example, each block number index (i.e., tpc-IndexPCell and tpc-IndexPCell-r16) has its associated CORESETPoolIndex value (i.e., associatedCORESETPoolIndex).

[0059] Figure 3The figure shows an example according to the third embodiment. For the M-TRP scenario based on M-DCI, two block number indexes are configured for the UE in the PCell, for example, tpc-IndexPCell and tpc-IndexPCell-r16. The TPC command included in the block with the block number index = tpc-IndexPCell associated with CORESETPoolIndex = 0 is used to determine the transmission power for the PUCCH resource associated with CORESETPoolIndex = 0, while the TPC command included in the block with the block number index = tpc-IndexPCell-r16 associated with CORESETPoolIndex = 1 is used to determine the transmission power for the PUCCH resource associated with CORESETPoolIndex = 1.

[0060] The UE receives DCI with format 2_2 transmitted from a CORESET (e.g., CORESET #0), which has two blocks, and each block contains a TPC command for the UE in time slot n. Two PUCCH resources need to be transmitted in time slot n+1, that is, PUCCH resource #1 associated with CORESETPoolIndex = 0 and PUCCH resource #2 associated with CORESETPoolIndex = 1. The TPC command included in the block with the block number index value = tpc-IndexPCell associated with CORESETPoolIndex = 0 is only applied to PUCCH resource #1. The TPC command included in the block with the block number index value = tpc-IndexPCell-r16 associated with CORESETPoolIndex = 1 is only applied to PUCCH resource #2.

[0061] In Figure 3 the example, in one DCI with format 2_2, two block number indexes are configured for the UE to support PUCCH resources targeted at two TRPs. Multiple (e.g., 3 or more) block number indexes each associated with a different block number index value can be configured in one DCI with format 2_2 to support PUCCH resources targeted at the same number (3 or more) of TRPs.

[0062] In addition, the UE may receive more than one DCI with format 2_2 each scrambled with TPC-PUCCH-RNTI in the same time slot. Under this condition, the UE may have an alternative option regarding which DCI is valid.

[0063] (1) The most recently received DCI is valid.

[0064] (2) The DCI transmitted from the CORESET configured with the lowest CORESETPoolIndex value is valid.

[0065] (3) The first received DCI is valid.

[0066] Figure 4 FIG. is a schematic flowchart illustrating an embodiment of a method 400 for the transmission of power control commands. In some embodiments, the method 400 is performed by a device such as a base station unit. In certain embodiments, the method 400 may be performed by a processor executing program code, e.g., a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0067] The method 400 may include 410 transmitting two or more TPC commands for PUCCH resources of UEs in a cell, each PUCCH resource being associated with a higher layer index value configured for a CORESET, and 420 receiving each PUCCH resource transmitted from a UE using the power according to the TPC command determined according to the higher layer index value.

[0068] Figure 5 FIG. is a schematic flowchart illustrating another embodiment of a method 500 for the transmission of power control commands. In some embodiments, the method 500 is performed by a device such as a remote unit or a UE. In certain embodiments, the method 500 may be performed by a processor executing program code, e.g., a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0069] The method 500 may include 510 receiving two or more TPC commands for PUCCH resources of UEs in a cell, each PUCCH resource being associated with a higher layer index value configured for a CORESET; 520 determining the TPC command for each PUCCH resource according to the higher layer index value, and 530 transmitting each PUCCH resource using the power according to the determined TPC command.

[0070] Figure 6 FIG. is a schematic block diagram illustrating a device according to an embodiment.

[0071] Referring to Figure 6 , the UE (i.e., the remote unit) includes a processor, a memory, and a transceiver. The processor implements the functions, procedures, and / or methods proposed in Figure 5 , and the gNB (i.e., the base station unit) includes a processor, a memory, and a transceiver. The processor implements Figure 4The functions, processes, and / or methods proposed in [reference]. Each layer of the radio interface protocol can be implemented by a processor. A memory is connected to the processor to store various pieces of information for driving the processor. A transceiver is connected to the processor to transmit and / or receive radio signals. Needless to say, the transceiver can be implemented as a transmitter for transmitting radio signals and a receiver for receiving radio signals.

[0072] The memory can be located inside or outside the processor and is connected to the processor by various well-known means.

[0073] In the above embodiments, the components and features of the embodiments are combined in a predetermined form. Unless otherwise explicitly stated, each component or function should be considered an option. Each component or feature can be implemented without being associated with other components or features. In addition, an embodiment can be configured by associating some components and / or features. The order of operations described in the embodiments can be changed. Some components or features of any embodiment can be included in another embodiment or replaced with components and features corresponding to another embodiment. Obviously, claims not explicitly recited in the claims are combined to form embodiments or included in new claims.

[0074] The embodiments can be implemented by hardware, firmware, software, or a combination thereof. In the case of implementation by hardware, according to the hardware implementation, the exemplary embodiments described herein can be implemented by using one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, etc.

[0075] The embodiments can be practiced in other specific forms. The described embodiments are to be considered in all respects only illustrative and not restrictive. The scope of the present invention is thus indicated by the appended claims rather than by the foregoing description. All changes falling within the equivalent meaning and scope of the claims should be covered within their scope.

Claims

1. A method at a UE, comprising: Receiving two or more TPC commands for PUCCH resources of the UE in a cell, each PUCCH resource being associated with a higher layer index value configured for a CORESET; Determining, according to the higher layer index value, a TPC command for each PUCCH resource; And Transmitting each PUCCH resource using a power according to the determined TPC command, Wherein each TPC command is carried in one DCI with format 2_2 scrambled by a TPC-PUCCH-RNTI.

2. The method according to claim 1, wherein A TPC command carried by a DCI transmitted from a CORESET is determined as a TPC command for a PUCCH resource associated with the same higher layer index value configured for the CORESET.

3. The method according to claim 1, wherein, A TPC command for a closed-loop index is determined as a TPC command for a PUCCH resource associated with a higher layer index value associated with the closed-loop index.

4. The method according to claim 1, wherein All the TPC commands are carried in a single DCI with format 2_2, wherein the same number of block number indexes as the number of different higher layer index values are configured for the UE in the cell.

5. The method according to claim 4, wherein, Each block with a block number index value contains one TPC command, and the one TPC command is determined as a TPC command for a PUCCH resource associated with a higher layer index value associated with the block number index value.

6. A method at a base station unit, comprising: Transmitting two or more TPC commands for PUCCH resources of a UE in a cell, each PUCCH resource being associated with a higher layer index value configured for a CORESET; Receiving each PUCCH resource transmitted from the UE using a power according to a TPC command determined according to the higher layer index value, Wherein each TPC command is carried in one DCI with format 2_2 scrambled by a TPC-PUCCH-RNTI.

7. The method according to claim 6, wherein, A TPC command carried by a DCI transmitted from a CORESET is determined as a TPC command for a PUCCH resource associated with the same higher layer index value configured for the CORESET.

8. The method according to claim 6, wherein, A TPC command for a closed-loop index is determined as a TPC command for a PUCCH resource associated with a higher layer index value associated with the closed-loop index.

9. The method according to claim 6, wherein All the TPC commands are carried in a single DCI with format 2_2, wherein the same number of block number indexes as the number of different higher layer index values are configured for the UE in the cell.

10. The method according to claim 9, wherein Each block with a block number index value contains one TPC command, and the one TPC command is determined as a TPC command for a PUCCH resource associated with a higher layer index value associated with the block number index value.

11. A UE, comprising: A receiver configured to receive two or more TPC commands for PUCCH resources of the UE in a cell, each PUCCH resource being associated with a higher layer index value configured for a CORESET; A processor configured to determine a TPC command for each PUCCH resource according to the higher layer index value; And A transmitter configured to transmit each PUCCH resource using a power according to the determined TPC command, wherein each TPC command is carried in one DCI with format 2_2 scrambled by TPC-PUCCH-RNTI.

12. The UE according to claim 11, wherein, The TPC command carried by the DCI transmitted from the CORESET is determined as the TPC command for the PUCCH resource associated with the same higher layer index value configured for the CORESET.

13. The UE according to claim 11, wherein, The TPC command for the closed-loop index is determined as the TPC command for the PUCCH resource associated with the higher layer index value associated with the closed-loop index.

14. The UE according to claim 11, wherein, All the TPC commands are carried in a single DCI with format 2_2, wherein the same number of block number indexes as the number of different higher layer index values are configured for the UE in the cell.

15. The UE according to claim 14, wherein, Each block with a block number index value contains a TPC command, and the one TPC command is determined as the TPC command for the PUCCH resource associated with the higher layer index value associated with the block number index value.

16. A base station unit, comprising: A transmitter configured to transmit two or more TPC commands for PUCCH resources of a UE in a cell, each PUCCH resource being associated with a higher layer index value configured for the CORESET; And A receiver configured to receive each PUCCH resource transmitted from the UE using a power according to the TPC command determined according to the higher layer index value, wherein each TPC command is carried in one DCI with format 2_2 scrambled by TPC-PUCCH-RNTI.

17. The base station unit according to claim 16, wherein, The TPC command carried by the DCI transmitted from the CORESET is determined as the TPC command for the PUCCH resource associated with the same higher layer index value configured for the CORESET.

18. The base station unit according to claim 16, wherein, The TPC command for the closed-loop index is determined as the TPC command for the PUCCH resource associated with the higher layer index value associated with the closed-loop index.

19. The base station unit according to claim 16, wherein, All the TPC commands are carried in a single DCI with format 2_2, wherein the same number of block number indexes as the number of different higher layer index values are configured for the UE in the cell.

20. The base station unit according to claim 19, wherein, Each block with a block number index value contains a TPC command, and the one TPC command is determined as the TPC command for the PUCCH resource associated with the higher layer index value associated with the block number index value.

Images