dcj format 2_3 scrambled by different transmission power control sounding reference signal radio network temporary identifier

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) can receive a power control configuration for a plurality of component carriers. The power control configuration can indicate a first TPC-SRS-RNTI and a second TPC-SRS-RNTI. The plurality of component carriers can include a first component carrier and a second component carrier. The first component carrier can be configured with a first closed loop power control (CLPC) adjustment state and a second CLPC adjustment state, and the second component carrier can be configured with the first CLPC adjustment state. The UE can receive a downlink control information (DCI) indicating a TPC command for the second component carrier. The DCI can be scrambled by the first TPC-SRS-RNTI or the second TPC-SRS-RNTI. The UE can transmit an SRS based at least in part on applying the TPC command to the first closed loop power control adjustment state corresponding to the second component carrier. Numerous other aspects are described.

Description

Technical Field

[0001] All aspects of this disclosure relate to wireless communication in general, and specifically to techniques, apparatus, and methods for downlink control information format 2_3 scrambled by radio network temporary identifiers of different transmit power control detection reference signals. Background Technology

[0002] Wireless communication systems are widely deployed to provide a variety of services, including voice, text, messaging, video, data, and / or other services. Services may include unicast, multicast, and / or broadcast services, etc. Typical wireless communication systems employ multiple access radio access technologies (RATs) capable of supporting communication with multiple users by sharing available system resources (e.g., time-domain resources, frequency-domain resources, spatial-domain resources, and / or device transmit power, etc.). Examples of such multiple access RATs include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single-Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0003] The aforementioned Multiple Access RATs have been adopted in various telecommunications standards to provide a common protocol enabling different wireless communication devices to communicate at the city, national, regional, or global level. An example telecommunications standard is New Radio (NR). NR (also known as 5G) is part of the continuous evolution of mobile broadband announced by the 3rd Generation Partnership Project (3GPP). NR (and other mobile broadband evolutions beyond NR) can be designed to better support the Internet of Things (IoT) and reduced-capacity device deployments, industrial connectivity, millimeter-wave (mmWave) expansion, licensed and unlicensed spectrum access, non-terrestrial network (NTN) deployments, sidelinks and other device-to-device direct communication technologies (e.g., cellular vehicle-to-everything (CV2X) communications), massive MIMO, decomposed network architectures and network topology expansion, multi-subscriber implementations, high-precision positioning and / or radio frequency (RF) sensing, and more. As the demand for mobile broadband access continues to grow, further improvements to NR can be implemented, and other radio access technologies (such as 6G) can be introduced to further advance mobile broadband evolution. Summary of the Invention

[0004] Some aspects described herein relate to a method for wireless communication performed by a User Equipment (UE). The method may include receiving from a network node an uplink power control configuration for a plurality of uplink component carriers, wherein the uplink power control configuration indicates a first Transmit Power Control (TPC) Sounding Reference Signal (SRS) Radio Network Temporary Identifier (RNTI) and a second TPC-SRS-RNTI, wherein the plurality of uplink component carriers include a first component carrier and a second component carrier, wherein the first component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, and wherein the second component carrier is configured with a first SRS closed-loop power control adjustment state. The method may include receiving from the network node downlink control information (DCI) indicating a TPC command for the second component carrier, wherein the DCI is scrambled by either the first TPC-SRS-RNTI or the second TPC-SRS-RNTI. The method may include transmitting SRS to the network node at least in part based on applying a TPC command to the first SRS closed-loop power control adjustment state corresponding to the second component carrier.

[0005] Some aspects described herein relate to a method for wireless communication performed by a UE. The method may include receiving from a network node a configuration for an uplink component carrier, wherein the uplink component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, wherein the configuration indicates a first start position in DCI format 2_3 associated with the first closed-loop power control adjustment state and a second start position in DCI format 2_3 associated with the second closed-loop power control adjustment state, and wherein DCI format 2_3 associated with the first closed-loop power control adjustment state indicates a TPC command for the first SRS closed-loop power control adjustment state, and DCI format 2_3 associated with the second closed-loop power control adjustment state indicates a TPC command for the second SRS closed-loop power control adjustment state. The method may include receiving from the network node DCI format 2_3 having a cyclic redundancy check (CRC) scrambled by TPC-SRS-RNTI. The method may include sending SRS to network nodes based at least in part on the following: a TPC command in DCI format 2_3 based on a first starting position or a TPC command in DCI format 2_3 based on a second starting position corresponding to an uplink component carrier.

[0006] Some aspects described herein relate to a method for wireless communication performed by a network node. The method may include sending an uplink power control configuration to a UE for a plurality of uplink component carriers, wherein the uplink power control configuration indicates a first TPC-SRS-RNTI and a second TPC-SRS-RNTI, wherein the plurality of uplink component carriers include a first component carrier and a second component carrier, wherein the first component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, and wherein the second component carrier is configured with a first SRS closed-loop power control adjustment state. The method may include sending a DCI to the UE indicating a TPC command for the second component carrier, wherein the DCI is scrambled by either the first TPC-SRS-RNTI or the second TPC-SRS-RNTI. The method may include receiving SRS from the UE based at least in part on the TPC command being applied to the first SRS closed-loop power control adjustment state corresponding to the second component carrier.

[0007] Some aspects described herein relate to a method for wireless communication performed by a network node. The method may include sending a configuration to a UE for an uplink component carrier, wherein the uplink component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, wherein the configuration indicates a first start position in DCI format 2_3 associated with the first closed-loop power control adjustment state and a second start position in DCI format 2_3 associated with the second closed-loop power control adjustment state, and wherein DCI format 2_3 associated with the first closed-loop power control adjustment state indicates a TPC command for the first SRS closed-loop power control adjustment state, and DCI format 2_3 associated with the second closed-loop power control adjustment state indicates a TPC command for the second SRS closed-loop power control adjustment state. The method may include sending a DCI format 2_3 to the UE with a CRC scrambled by TPC-SRS-RNTI. The method may include receiving SRS from the UE based at least in part on either a TPC command in DCI format 2_3 based on a first starting position or a TPC command in DCI format 2_3 based on a second starting position corresponding to an uplink component carrier.

[0008] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. When executed by one or more processors of the UE, the set of instructions enables the UE to receive from a network node an uplink power control configuration for a plurality of uplink component carriers, wherein the uplink power control configuration indicates a first TPC-SRS-RNTI and a second TPC-SRS-RNTI, wherein the plurality of uplink component carriers include a first component carrier and a second component carrier, wherein the first component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, and wherein the second component carrier is configured with a first SRS closed-loop power control adjustment state. When executed by one or more processors of the UE, the set of instructions enables the UE to receive from the network node a DCI indicating a TPC command for the second component carrier, wherein the DCI is scrambled by either the first TPC-SRS-RNTI or the second TPC-SRS-RNTI. When executed by one or more processors of the UE, the set of instructions enables the UE to transmit SRS to the network node at least in part based on applying the TPC command to the first SRS closed-loop power control adjustment state corresponding to the second component carrier.

[0009] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication when executed by one or more processors of a UE. When executed by one or more processors of the UE, the set of instructions enables the UE to receive from a network node a configuration for an uplink component carrier, wherein the uplink component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state. The configuration indicates a first start position in DCI format 2_3 associated with the first closed-loop power control adjustment state and a second start position in DCI format 2_3 associated with the second closed-loop power control adjustment state. The DCI format 2_3 associated with the first closed-loop power control adjustment state indicates a TPC command for the first SRS closed-loop power control adjustment state, and the DCI format 2_3 associated with the second closed-loop power control adjustment state indicates a TPC command for the second SRS closed-loop power control adjustment state. When executed by one or more processors of the UE, the set of instructions enables the UE to receive from a network node DCI format 2_3 with a CRC scrambled by TPC-SRS-RNTI. When executed by one or more processors of the UE, this instruction set enables the UE to send SRS to the network node at least in part based on the following: a TPC command in DCI format 2_3 based on a first starting position or a TPC command in DCI format 2_3 based on a second starting position corresponding to an uplink component carrier.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. When executed by one or more processors of the network node, the set of instructions enables the network node to send an uplink power control configuration to a UE for a plurality of uplink component carriers, wherein the uplink power control configuration indicates a first TPC-SRS-RNTI and a second TPC-SRS-RNTI, wherein the plurality of uplink component carriers include a first component carrier and a second component carrier, wherein the first component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, and wherein the second component carrier is configured with a first SRS closed-loop power control adjustment state. When executed by one or more processors of the network node, the set of instructions enables the network node to send a DCI indicating a TPC command for the second component carrier to the UE, wherein the DCI is scrambled by either the first TPC-SRS-RNTI or the second TPC-SRS-RNTI. When executed by one or more processors of a network node, this instruction set enables the network node to receive SRS from the UE, at least in part, based on the TPC command being applied to the first SRS closed-loop power control adjustment state corresponding to the second component carrier.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. When executed by one or more processors of the network node, this set of instructions enables the network node to send a configuration to a UE for an uplink component carrier, wherein the uplink component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state. The configuration indicates a first start position in DCI format 2_3 associated with the first closed-loop power control adjustment state and a second start position in DCI format 2_3 associated with the second closed-loop power control adjustment state. The DCI format 2_3 associated with the first closed-loop power control adjustment state indicates a TPC command for the first SRS closed-loop power control adjustment state, and the DCI format 2_3 associated with the second closed-loop power control adjustment state indicates a TPC command for the second SRS closed-loop power control adjustment state. When executed by one or more processors of the network node, this set of instructions enables the network node to send a DCI format 2_3 to the UE with a CRC scrambled by TPC-SRS-RNTI. When executed by one or more processors of the network node, this instruction set enables the network node to receive SRS from the UE at least in part based on either a TPC command in DCI format 2_3 based on a first starting position or a TPC command in DCI format 2_3 based on a second starting position corresponding to an uplink component carrier.

[0012] Some aspects described herein relate to a UE for wireless communication. The UE may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to receive from a network node an uplink power control configuration for a plurality of uplink component carriers, wherein the uplink power control configuration indicates a first TPC-SRS-RNTI and a second TPC-SRS-RNTI, wherein the plurality of uplink component carriers include a first component carrier and a second component carrier, wherein the first component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, and wherein the second component carrier is configured with a first SRS closed-loop power control adjustment state. The one or more processors may be configured to receive from the network node a DCI indicating a TPC command for the second component carrier, wherein the DCI is scrambled by either the first TPC-SRS-RNTI or the second TPC-SRS-RNTI. The one or more processors may be configured to transmit SRS to the network node at least in part based on applying the TPC command to the first SRS closed-loop power control adjustment state corresponding to the second component carrier.

[0013] Some aspects described herein relate to a UE for wireless communication. The UE may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to receive configurations from a network node for an uplink component carrier, wherein the uplink component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, wherein the configuration indicates a first start position in DCI format 2_3 associated with the first closed-loop power control adjustment state and a second start position in DCI format 2_3 associated with the second closed-loop power control adjustment state, and wherein DCI format 2_3 associated with the first closed-loop power control adjustment state indicates a TPC command for the first SRS closed-loop power control adjustment state, and DCI format 2_3 associated with the second closed-loop power control adjustment state indicates a TPC command for the second SRS closed-loop power control adjustment state. The one or more processors may be configured to receive DCI format 2_3 with a CRC scrambled by TPC-SRS-RNTI from a network node. The one or more processors may be configured to send SRS to the network node based at least in part on the following: a TPC command in DCI format 2_3 based on a first starting position or a TPC command in DCI format 2_3 based on a second starting position corresponding to an uplink component carrier.

[0014] Some aspects described herein relate to a network node for wireless communication. The network node may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to send an uplink power control configuration to a UE for a plurality of uplink component carriers, wherein the uplink power control configuration indicates a first TPC-SRS-RNTI and a second TPC-SRS-RNTI, wherein the plurality of uplink component carriers include a first component carrier and a second component carrier, wherein the first component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, and wherein the second component carrier is configured with a first SRS closed-loop power control adjustment state. The one or more processors may be configured to send a DCI to the UE indicating a TPC command for the second component carrier, wherein the DCI is scrambled by either the first TPC-SRS-RNTI or the second TPC-SRS-RNTI. The one or more processors may be configured to receive SRS from the UE based at least in part on the TPC command being applied to the first SRS closed-loop power control adjustment state corresponding to the second component carrier.

[0015] Some aspects described herein relate to a network node for wireless communication. The network node may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to send a configuration to a UE for an uplink component carrier, wherein the uplink component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, wherein the configuration indicates a first start position in DCI format 2_3 associated with the first closed-loop power control adjustment state and a second start position in DCI format 2_3 associated with the second closed-loop power control adjustment state, and wherein DCI format 2_3 associated with the first closed-loop power control adjustment state indicates a TPC command for the first SRS closed-loop power control adjustment state, and DCI format 2_3 associated with the second closed-loop power control adjustment state indicates a TPC command for the second SRS closed-loop power control adjustment state. The one or more processors may be configured to send a DCI format 2_3 to the UE with a CRC scrambled by TPC-SRS-RNTI. The one or more processors may be configured to receive SRS from the UE based at least in part on either a TPC command in DCI format 2_3 based on a first starting position or a TPC command in DCI format 2_3 based on a second starting position corresponding to an uplink component carrier.

[0016] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving from a network node an uplink power control configuration for a plurality of uplink component carriers, wherein the uplink power control configuration indicates a first TPC-SRS-RNTI and a second TPC-SRS-RNTI, wherein the plurality of uplink component carriers include a first component carrier and a second component carrier, wherein the first component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, and wherein the second component carrier is configured with a first SRS closed-loop power control adjustment state. The apparatus may include components for receiving from the network node a DCI indicating a TPC command for the second component carrier, wherein the DCI is scrambled by either the first TPC-SRS-RNTI or the second TPC-SRS-RNTI. The apparatus may include components for transmitting an SRS to the network node at least in part based on applying a TPC command to the first SRS closed-loop power control adjustment state corresponding to the second component carrier.

[0017] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving from a network node a configuration for an uplink component carrier, wherein the uplink component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, wherein the configuration indicates a first start position in DCI format 2_3 associated with the first closed-loop power control adjustment state and a second start position in DCI format 2_3 associated with the second closed-loop power control adjustment state, and wherein DCI format 2_3 associated with the first closed-loop power control adjustment state indicates a TPC command for the first SRS closed-loop power control adjustment state, and DCI format 2_3 associated with the second closed-loop power control adjustment state indicates a TPC command for the second SRS closed-loop power control adjustment state. The apparatus may include components for receiving from a network node DCI format 2_3 having a CRC scrambled by TPC-SRS-RNTI. The apparatus may include components for transmitting SRS to network nodes based at least in part on either a TPC command in DCI format 2_3 based on a first starting position or a TPC command in DCI format 2_3 based on a second starting position corresponding to an uplink component carrier.

[0018] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for transmitting to a UE an uplink power control configuration for a plurality of uplink component carriers, wherein the uplink power control configuration indicates a first TPC-SRS-RNTI and a second TPC-SRS-RNTI, wherein the plurality of uplink component carriers include a first component carrier and a second component carrier, wherein the first component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, and wherein the second component carrier is configured with a first SRS closed-loop power control adjustment state. The apparatus may include components for transmitting to the UE a DCI indicating a TPC command for the second component carrier, wherein the DCI is scrambled by either the first TPC-SRS-RNTI or the second TPC-SRS-RNTI. The apparatus may include components for receiving SRS from the UE based at least in part on the TPC command being applied to the first SRS closed-loop power control adjustment state corresponding to the second component carrier.

[0019] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for transmitting to a UE a configuration for an uplink component carrier, wherein the uplink component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, wherein the configuration indicates a first start position in DCI format 2_3 associated with the first closed-loop power control adjustment state and a second start position in DCI format 2_3 associated with the second closed-loop power control adjustment state, and wherein DCI format 2_3 associated with the first closed-loop power control adjustment state indicates a TPC command for the first SRS closed-loop power control adjustment state, and DCI format 2_3 associated with the second closed-loop power control adjustment state indicates a TPC command for the second SRS closed-loop power control adjustment state. The one or more processors may be configured to transmit to the UE DCI format 2_3 having a CRC scrambled by TPC-SRS-RNTI. The apparatus may include components for receiving SRS from the UE based at least in part on either a TPC command in DCI format 2_3 based on a first starting position or a TPC command in DCI format 2_3 based on a second starting position corresponding to an uplink component carrier.

[0020] Various aspects of this disclosure may be implemented or be implemented as described in whole by or embodied in the methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network nodes, network entities, wireless communication devices and / or processing systems as fully described in the specification and drawings and illustrated in the specification and drawings.

[0021] The preceding paragraphs of this section have broadly summarized some aspects of this disclosure. These and additional aspects and their associated advantages will be described below. The disclosed aspects can serve as the basis for modifying or designing other aspects for performing the same or similar purposes of this disclosure. Such equivalent aspects do not depart from the scope of the appended claims. The characteristics of the aspects disclosed herein, their organization and operation, and their associated advantages will be better understood from the following description taken in conjunction with the accompanying drawings. Attached Figure Description

[0022] The accompanying drawings illustrate some aspects of this disclosure but do not limit its scope, as other aspects can be achieved by this description. Each drawing in the drawings is provided for illustrative and descriptive purposes and not as a definition of limitation of the claims. Identical or similar reference numerals in different drawings may identify identical or similar elements.

[0023] Figure 1 This is a diagram illustrating an example of a wireless communication network according to the present disclosure.

[0024] Figure 2 This is a diagram illustrating communication between an example network node and an example UE in a wireless network according to this disclosure.

[0025] Figure 3 This is a diagram illustrating an example decomposed base station architecture according to this disclosure.

[0026] Figure 4A and Figure 4B This is a diagram illustrating an example of carrier aggregation according to this disclosure.

[0027] Figure 5A and 5B This is a diagram illustrating an example of a DCI format 2_3 associated with a CRC scrambled by different TPC-SRS-RNTIs according to this disclosure.

[0028] Figure 6 This is a diagram illustrating an example of DCI format 2_3 associated with this disclosure, which indicates TPC commands associated with different SRS closed-loop power control adjustment states.

[0029] Figure 7 This is a diagram illustrating an example process performed, for example, at the UE or a device of the UE, according to this disclosure.

[0030] Figure 8 This is a diagram illustrating an example process performed, for example, at the UE or a device of the UE, according to this disclosure.

[0031] Figure 9 This is a diagram illustrating an example process performed, for example, at a network node or a device of a network node, according to the present disclosure.

[0032] Figure 10 This is a diagram illustrating an example process performed, for example, at a network node or a device of a network node, according to the present disclosure.

[0033] Figure 11 This is a diagram of an example device for wireless communication according to the present disclosure.

[0034] Figure 12 This is a diagram of an example device for wireless communication according to the present disclosure. Detailed Implementation

[0035] Various aspects of this disclosure are described below with reference to the accompanying drawings. However, aspects of this disclosure may be embodied in many different forms and should not be construed as limited to any specific aspect illustrated or described with reference to the drawings or otherwise presented in this disclosure. Rather, these aspects are provided so that this disclosure will be comprehensive and complete, and will fully convey the scope of this disclosure to those skilled in the art. Those skilled in the art will understand that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, various combinations or numbers of aspects set forth herein may be used to implement an apparatus or a method of practice. Furthermore, the scope of this disclosure is intended to cover apparatuses having structures and / or functionalities other than those available for practicing the various aspects of this disclosure set forth herein, or methods of practice using those other structures and / or functionalities. Any aspect of this disclosure disclosed herein may be embodied by one or more elements of the claims.

[0036] Various methods, operations, apparatuses, and techniques will now be presented with reference to them. These methods, operations, apparatuses, and techniques will be described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, “elements”). These elements may be implemented using hardware, software, or a combination of hardware and software. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0037] Downlink Control Information (DCI) format 2_3 is a group-shared DCI with Cyclic Redundancy Check (CRC) that utilizes Transmit Power Control (TPC) Sounding Reference Signal (SRS) Radio Network Temporary Identifier (RNTI) for scrambling. DCI format 2_3 can contain multiple blocks. The starting location of a block can be configured for each User Equipment (UE). The block's payload and / or fields may depend on whether an SRS Request field is included in the block and / or on the block type. The SRS Request field may include two bits, and whether it is included in the block can be configured by Radio Resource Control (RRC) parameters (e.g., fieldTypeFormat2_3).

[0038] The block type can be either a Type A block or a Type B block, and can be configured by RRC parameters (e.g., SRS-TPC-Physical Downlink Control Channel (PDCCH)-Group). A Type A block may include an SRS request field and a certain number of ( N The SRS request field can be one TPC command field. The SRS request field may include two bits. The UE does not expect the SRS request field to be absent for Type A blocks. N Each TPC command field can include 2* N Units. Each TPC command can be applied to the corresponding uplink component carrier provided by the RRC parameter (e.g., cc-IndexInOneCC-Set). The RRC parameter can correspond to the set of component carriers indicated by the SRS request field.

[0039] The Type B block may include an SRS request field and a TPC command field. When the SRS request field is not included in the Type B block, it may include zero bits; when it is included, it may include two bits. The TPC command field may include two bits and may be applicable to the corresponding uplink component carrier.

[0040] In some cases, the UE can be configured with two SRS closed-loop power control adjustment states (e.g., a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state). DCI format 2_3 may have a CRC scrambled with a first TPC-SRS-RNTI to indicate that a TPC command is used for the first SRS closed-loop power control adjustment state, and the CRC may be scrambled with a second TPC-SRS-RNTI to indicate that a TPC command is used for the second SRS closed-loop power control adjustment state.

[0041] However, for carrier aggregation with mixed component carrier modes (e.g., one or more component carriers are mode 1 component carriers configured with two separate SRS closed-loop power control adjustment states, and one or more component carriers are mode 2 component carriers configured with a single SRS closed-loop power control adjustment state), using DCI format 2_3 with a CRC scrambled by a first TPC-SRS-RNTI or a second TPC-SRS-RNTI to indicate that TPC commands are used for the first SRS closed-loop power control adjustment state or the second SRS closed-loop power control adjustment state respectively may result in signaling waste relative to the mode 2 component carrier.

[0042] Various aspects generally involve using DCI format 2_3 with a CRC scrambled by a first TPC-SRS-RNTI or a second TPC-SRS-RNTI to indicate the SRS closed-loop power control adjustment state for a mode 2 component carrier. Some aspects more specifically involve applying the TPC command in DCI format 2_3 to the component carrier when the component carrier is configured with a single SRS closed-loop power control adjustment state, regardless of whether the CRC is scrambled using the first TPC-SRS-RNTI or the second TPC-SRS-RNTI.

[0043] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, by applying the TPC command in DCI format 2_3 to the component carrier when the component carrier is configured with a single SRS closed-loop power control adjustment state, regardless of whether the CRC is scrambled using a first TPC-SRS-RNTI or a second TPC-SRS-RNTI, the described techniques can be used to improve the efficiency of the signaling required to indicate that a TPC command will be applied to a single SRS closed-loop power control adjustment state configured for the component carrier.

[0044] Multiple access radio access technology (RAT) has been adopted in various telecommunications standards to provide a common protocol that enables different wireless communication devices to communicate at the city, enterprise, national, regional, or global level. For example, 5G New Radio (NR) is part of the continuous mobile broadband evolution announced by the 3rd Generation Partnership Project (3GPP). 5G NR supports a variety of technologies and use cases, including enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine-type communication (mMTC), millimeter wave (mmWave) technology, beamforming, network slicing, edge computing, Internet of Things (IoT) connectivity and management, and network function virtualization (NFV).

[0045] With increasing demand for broadband access and the evolution of technologies supported by wireless communication networks, further technological improvements can be adopted or implemented in 5G NR or future RATs (such as 6G) to further advance the evolution of wireless communication for a variety of existing and new use cases and applications. Such technological improvements can be associated with new frequency band extensions, licensed and unlicensed spectrum access, overlapping spectrum use, small cell deployments, non-terrestrial network (NTN) deployments, decomposed network architectures and network topology extensions, device aggregation, advanced duplex communication, sidelinks and other device-to-device direct communication, IoT (including passive or ambient IoT) networks, reduced-capacity (RedCap) UE functionality, industrial connectivity, multi-subscriber implementations, high-precision positioning, radio frequency (RF) sensing and / or artificial intelligence or machine learning (AI / ML), and more. Such technological improvements can support use cases such as wireless backhaul, wireless data centers, extended reality (XR) and metaverse applications, meta-services for supporting vehicle connectivity, holographic and mixed reality communications, autonomous and collaborative robots, vehicle platooning and collaborative manipulation, sensor networks, posture monitoring, brain-computer interfaces, digital twin applications, asset management, and general coverage applications using off-ground and / or aerial platforms, etc. The methods, operations, apparatuses, and techniques described herein can implement one or more of the foregoing technologies and / or support one or more of the foregoing use cases.

[0046] Figure 1 This is a diagram illustrating an example of a wireless communication network 100 according to the present disclosure. The wireless communication network 100 may be a 5G (or NR) network or a 6G network, or may include elements of a 5G (or NR) network or a 6G network, etc. The wireless communication network 100 may include a plurality of network nodes 110, shown as network node (NN) 110a, network node 110b, network node 110c, and network node 110d. Network nodes 110 may support communication with a plurality of UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e).

[0047] Network nodes 110 and UEs 120 of wireless communication network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, frequency bands, carriers, and / or channels according to frequency or wavelength. For example, devices of wireless communication network 100 can communicate using one or more operating frequency bands. In some aspects, multiple wireless networks 100 can be deployed in a given geographical area. Each wireless communication network 100 can support a specific RAT (which may also be referred to as an air interface) and can operate on one or more carrier frequencies in one or more frequency ranges. Examples of RATs include 4G RATs, 5G / NRRATs, and / or 6G RATs, etc. In some examples, when multiple RATs are deployed in a given geographical area, each RAT in that geographical area can operate on a different frequency to avoid interference with each other.

[0048] Various operating frequency bands have been defined as frequency ranges designated FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Although a portion of FR1 is greater than 6 GHz, in some documents and articles, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band. Similarly, in some documents and articles, FR2 is often (interchangeably) referred to as the “millimeter wave” band, but this is different from the Very High Frequency (EHF) band (30 GHz to 300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU). The frequencies between FR1 and FR2 are often referred to as the mid-band frequencies, including FR3. Frequency bands falling within FR3 can inherit FR1 or FR2 characteristics, thereby effectively extending the characteristics of FR1 or FR2 into mid-band frequencies. Therefore, "below 6 GHz" (if used herein) can broadly refer to frequencies less than 6 GHz, within FR1, and / or included in mid-band frequencies. Similarly, the term "millimeter wave" (if used herein) can broadly refer to frequencies included in mid-band frequencies, within FR2, FR4, FR4-a, FR4-1, or FR5, and / or within the EHF band. Higher frequency bands can extend 5G NR operation, 6G operation, and / or other RATs above 52.6 GHz. For example, each of FR4a, FR4-1, FR4, and FR5 falls within the EHF band. In some examples, the wireless communication network 100 can implement dynamic spectrum sharing (DSS), where multiple RATs (e.g., 4G / LTE and 5G / NR) are implemented within a single frequency band using dynamic bandwidth allocation (e.g., based on user demand). It is conceivable that the frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1 and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0049] Network node 110 may include one or more devices, components, or systems that enable communication between UE 120 and one or more devices, components, or systems of wireless communication network 100. Network node 110 may be, may include, or may be referred to as: NR network node, 5G network node, 6G network node, node B, eNB, gNB, access point (AP), transmit / receive point (TRP), mobility element, core, network entity, network element, network equipment, and / or another type of device, component, or system included in the radio access network (RAN).

[0050] Network node 110 may be implemented as a single physical node (e.g., a single physical structure) or as two or more physical nodes (e.g., two or more different physical structures). For example, network node 110 may be a device or system implementing a portion of a radio protocol stack, a device or system implementing a complete protocol stack (such as a complete gNB protocol stack), or a collection of devices or systems collectively implementing a complete protocol stack. For example, and as shown, network node 110 may be an aggregated network node (with an aggregated architecture), meaning that network node 110 can implement a complete radio protocol stack physically and logically integrated within a single node (e.g., a single physical structure) in the wireless communication network 100. For example, aggregated network node 110 may consist of a single standalone base station or a single TRP that uses a complete radio protocol stack to implement or facilitate communication between UE 120 and the core network of wireless communication network 100.

[0051] Alternatively, and also as shown, network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 may use protocol stacks that are physically distributed and / or logically distributed across two or more nodes in the same or different geographic locations. For example, a decomposed network node may have a decomposed architecture. In some deployments, decomposed network node 110 may be used in integrated access and backhaul (IAB) networks, in open radio access networks (O-RAN) (such as network configurations compliant with the O-RAN Alliance), or in virtualized radio access networks (vRAN) (also referred to as cloud radio access networks (C-RAN)) to facilitate scaling by decomposing base station functionality into multiple individually deployable units.

[0052] Network nodes 110 of wireless communication network 100 may include one or more central units (CUs), one or more distributed units (DUs), and / or one or more radio units (RUs). CUs may host one or more higher-layer control functions, such as Radio Resource Control (RRC) functions, Packet Data Convergence Protocol (PDCP) functions, and / or Service Data Adaptation Protocol (SDAP) functions, etc. DUs may host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and / or one or more higher physical (PHY) layers, at least in part, according to functional splits (such as those defined by 3GPP). In some examples, DUs may also host one or more low-PHY layer functions, such as Fast Fourier Transform (FFT), Inverse FFT (iFFT), beamforming, Physical Random Access Channel (PRACH) extraction and filtering, and / or scheduling of resources for one or more UEs 120, etc. RUs may host RF processing functions or low-PHY layer functions, such as FFT, iFFT, beamforming, or PRACH extraction and filtering, etc., according to functional splits (such as lower-layer functional splits). In this type of architecture, each RU can be operated to handle over-the-air (OTA) communications with one or more UE 120s.

[0053] In some aspects, a single network node 110 may include a combination of one or more CUs, one or more DUs, and / or one or more RUs. Additionally or alternatively, network node 110 may include one or more near real-time (near RT) RAN Intelligent Controllers (RICs) and / or one or more non-real-time (non-RT) RICs. In some examples, CUs, DUs, and / or RUs may be implemented as virtual units, such as Virtual Central Units (VCUs), Virtual Distributed Units (VDUs), or Virtual Radio Units (VRUs), etc. Virtual units may be implemented as virtual network functions, such as those associated with cloud deployments.

[0054] Some network nodes 110 (e.g., base stations, RUs, or TRPs) can provide communication coverage for specific geographic areas. In 3GPP, the term "cell" can refer to the coverage area of ​​network node 110 or to network node 110 itself, depending on the context in which the term is used. Network node 110 can support one or more (e.g., three) cells. In some examples, network node 110 can provide communication coverage for macro cells, pico cells, femto cells, or another type of cell. A macro cell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UE 120 with a service subscription. A pico cell can cover a relatively small geographic area and can allow unrestricted access by UE 120 with a service subscription. A femto cell can cover a relatively small geographic area (e.g., a residential area) and can allow restricted access by UE 120 associated with that femto cell (e.g., UE 120 in a Closed Subscriber Group (CSG)). The network node 110 used for a macro cell may be referred to as a macro network node. Network node 110 used for a picocell may be referred to as a pico network node. Network node 110 used for a femtocell may be referred to as a femto network node or a home network node. In some examples, the cell may not necessarily be stationary. For example, the geographical area of ​​the cell may move depending on the location of the associated mobile network node 110 (e.g., a train, satellite base station, drone, or NTN network node).

[0055] The wireless communication network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, piconet nodes, femtonet nodes, relay network nodes, aggregation network nodes, and / or decomposition network nodes, etc. Figure 1 In the example shown, network node 110a can be a macro network node for macro cell 130a, network node 110b can be a pico network node for pico cell 130b, and network node 110c can be a femto network node for femto cell 130c. Compared to other types of network nodes 110, the various types of network nodes 110 typically transmit at different power levels, serve different coverage areas, and / or have different effects on interference in the wireless communication network 100. For example, macro network nodes may have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0056] In some examples, network node 110 may be, may include, or operate as a RU, TRP, or base station communicating with one or more UEs 120 via a radio access link (which may be referred to as a "Uu" link). The radio access link may include a downlink and an uplink. A "downlink" (or "DL") refers to the communication direction from network node 110 to UE 120, and an "uplink" (or "UL") refers to the communication direction from UE 120 to network node 110. Downlink channels may include one or more control channels and one or more data channels. Downlink control channels may be used to transmit DCI (e.g., scheduling information, reference signals, and / or configuration information) from network node 110 to UE 120. Downlink data channels may be used to transmit downlink data (e.g., user data associated with UE 120) from network node 110 to UE 120. Downlink control channels may include one or more physical downlink control channels (PDCCH), and downlink data channels may include one or more physical downlink shared channels (PDSCH). The uplink channel may similarly include one or more control channels and one or more data channels. The uplink control channel can be used to transmit uplink control information (UCI) from UE 120 to network node 110 (e.g., transmitting corresponding reference signals and / or feedback with one or more downlinks). The uplink data channel can be used to transmit uplink data (e.g., user data associated with UE 120) from UE 120 to network node 110. The uplink control channel may include one or more physical uplink control channels (PUCCH), and the uplink data channel may include one or more physical uplink shared channels (PUSCH). The downlink and uplink may each include a set of resources on which network node 110 and UE 120 can communicate.

[0057] Downlink and uplink resources may include time-domain resources (frames, subframes, time slots, and / or symbols), frequency-domain resources (bands, component carriers, subcarriers, resource blocks, and / or resource elements), and / or spatial-domain resources (specific transmission directions and / or beam parameters). Frequency-domain resources in some bands may be subdivided into bandwidth portions (BWPs). A BWP may be a contiguous block of frequency-domain resources allocated to one or more UEs 120 (e.g., a contiguous block of resource blocks). A UE 120 may be configured with both an uplink BWP and a downlink BWP (where the uplink BWP and downlink BWP may be the same BWP or different BWPs). BWPs may be dynamically configured and / or reconfigured (e.g., by sending DCI configuration to one or more UEs 120 via network node 110), meaning that BWPs may be adjusted in real-time (or near real-time) based on changing network conditions in the wireless communication network 100 and / or based on the specific requirements of one or more UEs 120. This allows for more efficient use of available frequency domain resources in the wireless communication network 100, as fewer frequency domain resources can be allocated to the BWP for UE 120 (which reduces the number of frequency domain resources that UE 120 needs to monitor), thus allowing more frequency domain resources to be distributed across multiple UE 120s. Therefore, the BWP can also assist in the implementation of such UE 120s by facilitating the configuration of smaller bandwidths for communications performed by lower-capacity UE 120s.

[0058] As described above, in some aspects, the wireless communication network 100 may be an IAB network, may include an IAB network, or may be included in an IAB network. In an IAB network, at least one network node 110 is an anchor network node communicating with a core network. The anchor network node 110 may also be referred to as an IAB donor (or "IAB donor"). The anchor network node 110 may be connected to the core network via a wired backhaul link. For example, the Ng interface of the anchor network node 110 may terminate at the core network. Additionally or alternatively, the anchor network node 110 may be connected to one or more devices in the core network that provide core access and mobility management functions (AMF). An IAB network typically also includes multiple non-anchor network nodes 110, which may also be referred to as relay network nodes or simply IAB nodes (or "IAB-nodes"). Each non-anchor network node 110 can directly communicate with the anchor network node 110 via a wireless backhaul link to access the core network, or can indirectly communicate with the anchor network node 110 via one or more other non-anchor network nodes 110 and an associated wireless backhaul link forming a backhaul path to the core network. Some anchor network nodes 110 or other non-anchor network nodes 110 can also directly communicate with one or more UEs 120 via a wireless access link carrying access services. For example, network resources used for wireless communication (such as time resources, frequency resources, and / or spatial resources) can be shared between the access link and the backhaul link.

[0059] In some examples, any network node 110 relaying communication may be referred to as a relay network node, a relay station, or simply a repeater. A repeater may receive communications from an upstream station (e.g., another network node 110 or UE 120) and transmit communications to a downstream station (e.g., UE 120 or another network node 110). In this case, the wireless communication network 100 may include or be referred to as a "multi-hop network." Figure 1 In the example shown, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. Additionally or alternatively, UE 120 can be a relay station capable of relaying transmissions to or from other UE 120s, or can operate as such a relay station. UE 120 relaying communication can be referred to as a UE repeater or relay UE, etc.

[0060] UE 120 may be physically distributed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile. UE 120 may be, may include, an access terminal, another terminal, a mobile station, or a subscriber unit, or may be included in an access terminal, another terminal, a mobile station, or a subscriber unit. UE 120 may be, or may include, a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband and / or smart jewelry (such as a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device and / or a satellite radio), an XR device, a vehicle component or sensor, a smart meter or sensor, industrial manufacturing equipment, a Global Navigation Satellite System (GNSS) device (such as a Global Positioning System device or another type of positioning device), a UE function of a network node, and / or any other suitable device or function that can communicate via a wireless medium, or may be coupled to them.

[0061] UE 120 and / or network node 110 may include one or more chips, system-on-a-chip (SoC), chipsets, packages, or devices that individually or collectively constitute or include a processing system. The processing system includes processor (or “processing”) circuitry in the form of one or more processors, microprocessors, processing units (such as central processing units (CPUs), graphics processing units (GPUs), neural processing units (NPUs), and / or digital signal processors (DSPs)), processing blocks, application-specific integrated circuits (ASICs), programmable logic devices (PLDs) (such as field-programmable gate arrays (FPGAs)), or other discrete gate or transistor logic components or circuits (all of which are generally referred to herein individually as “processors” or collectively as “processors” or “processor circuitry”). One or more of these processors may be individually or collectively configured to perform the various functions or operations described herein. A group of processors that can be configured or configured to perform a set of functions may include a first processor that can be configured or configured to perform a first function in the set, and a second processor that can be configured or configured to perform a second function in the set, or may include the entire group of processors that are configured or configured to perform the set of functions.

[0062] The processing system may also include memory circuitry in the form of one or more memory devices, memory blocks, memory elements, or other discrete gate or transistor logic components or circuits, each of which may include tangible storage media such as random access memory (RAM) or read-only memory (ROM) or combinations thereof (all of which are generally referred to herein individually as "memory" or collectively as "memory" or "memory circuitry"). One or more of these memories may be coupled to one or more processors in the processor (e.g., operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) and may store processor-executable code (such as software) individually or collectively, which, when executed by one or more processors in the processor, may configure one or more processors in the processor to perform the various functions or operations described herein. Additionally or alternatively, in some examples, one or more processors in the processor may be pre-configured to perform the various functions or operations described herein without being configured by software. The processing system may also include or be coupled to one or more modems (such as Wi-Fi (e.g., IEEE compliant) modems or cellular (e.g., 3GPP 4G LTE, 5G, or 6G compliant) modems). In some embodiments, one or more processors of the processing system include or implement one or more modems among the modems. The processing system may also include, or be coupled to, multiple radio components (collectively, “radio components”), multiple RF chains, or multiple transceivers, each of which may in turn be coupled to one or more antennas among multiple antennas. In some embodiments, one or more processors of the processing system include or implement one or more of the radio components, RF chains, or transceivers. UE 120 may be included or may be contained in a housing that houses components associated with UE 120, including the processing system.

[0063] Some UEs 120 may be considered Machine Type Communication (MTC) UEs, Evolved or Enhanced Machine Type Communication (eMTC) UEs, Further Enhanced eMTC (feMTC) UEs or Enhanced feMTC (efeMTC) UEs, or further evolutions thereof, all of which may be collectively referred to as "MTC UEs". MTC UEs may be, may include, or may be included in or coupled with the following: robots, unmanned aerial vehicles, remote devices, sensors, instruments, monitors, and / or location tags. Some UEs 120 may be considered IoT devices and / or may be implemented as NB-IoT (Narrowband IoT) devices. IoT UEs or NB-IoT devices may be, may include, or may be included in or coupled with the following: industrial machines, appliances, refrigerators, doorbell camera devices, home automation devices, and / or lighting fixtures, etc. Some UEs 120 may be considered customer premises equipment, which may include telecommunications equipment installed at a customer location (such as a home or office) to enable access to a service provider’s network (such as being included in or communicating with the wireless communication network 100).

[0064] Some UEs 120 can be categorized according to different categories associated with varying levels of complexity and / or capabilities. Category 1 UEs 120 facilitate large-scale IoT within the wireless communication network 100 and offer lower complexity and / or cost compared to Category 2 UEs 120. Category 2 UEs 120 may include mission-critical IoT devices capable of URLLC, enhanced mobile broadband (eMBB), and / or precise positioning within the wireless communication network 100, legacy UEs, baseline UEs, high-level UEs, advanced UEs, full-capability UEs, and / or premium UEs. Category 3 UEs 120 may possess intermediate-level complexity and / or capabilities (e.g., capabilities between Category 1 and Category 2 UEs 120). Category 3 UEs 120 may be referred to as reduced-capability UEs (“RedCap UEs”), intermediate-level UEs, NR lightweight UEs, and / or NR simplified UEs, etc. RedCap UEs bridge the gap in capabilities and complexity between NB-IoT devices and / or eMTC UEs and mission-critical IoT devices and / or premium UEs. RedCap UEs can include, for example, wearable devices, IoT devices, industrial sensors, and / or cameras associated with limited bandwidth, power capacity, and / or transmission range. RedCap UEs can support healthcare environments, building automation, power distribution, process automation, transportation and logistics, and / or smart city deployments, among others.

[0065] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly with each other using sidelink communication (e.g., without communicating through a network node 110 acting as an intermediary). As an example, UE 120a can send data, control information, or other signaling directly to UE 120e as sidelink communication. This contrasts with, for example, UE 120a first sending data to network node 110 in UL communication, and then that network node sending data to UE 120e in DL communication. In various examples, UE 120 can send and receive sidelink communication using peer-to-peer (P2P) communication protocols, device-to-device (D2D) communication protocols, vehicle-to-everything (V2X) communication protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, and / or vehicle-to-pedestrian (V2P) protocols), and / or mesh network communication protocols. In some deployments and configurations, network node 110 may schedule and / or allocate resources for sidelink communication between UEs 120 in the wireless communication network 100. In some other deployments and configurations, UE 120 (instead of network node 110) may perform or cooperate with or negotiate with one or more other UEs to perform scheduling operations, resource selection operations, and / or other operations for sidelink communication.

[0066] In various examples, in addition to half-duplex operation, some network nodes and UEs in the wireless communication network 100, including network node 110 and UE 120, can also be configured for full-duplex operation. Network node 110 or UE 120 operating in half-duplex mode can perform only one of transmission or reception during a specific time resource period (such as a specific time slot, symbol, or other time period). Half-duplex operation may involve time division duplex (TDD), where the DL transmission of network node 110 and the UL transmission of UE 120 do not occur in the same time resource (i.e., the transmissions do not overlap in time). In contrast, network node 110 or UE 120 operating in full-duplex mode can transmit and receive communications concurrently (e.g., within the same time resource). By operating in full-duplex mode, network node 110 and / or UE 120 can generally increase the capacity of the network and radio access links. In some examples, full-duplex operation may involve frequency division duplex (FDD), in which network node 110 performs DL transmission in a first frequency band or on a first component carrier, and UE 120 performs transmission in a second frequency band or on a second component carrier, the second frequency band or the second component carrier being different from the first frequency band or the first component carrier, respectively. In some examples, full-duplex operation may be enabled for UE 120 but not for network node 110. For example, UE 120 may simultaneously transmit UL to the first network node 110 and receive DL transmissions from the second network node 110 in the same time resources. In some other examples, full-duplex operation may be enabled for network node 110 but not for UE 120. For example, network node 110 may simultaneously transmit DL to the first UE 120 and receive UL transmissions from the second UE 120 in the same time resources. In some other examples, full-duplex operation may be enabled for both network node 110 and UE 120.

[0067] In some examples, UE 120 and network node 110 can perform MIMO communication. "MIMO" generally refers to the simultaneous transmission or reception of multiple signals (such as multiple layers or multiple data streams) using the same time and frequency resources. MIMO techniques typically utilize multipath propagation. MIMO can be implemented using various spatial processing or spatial multiplexing operations. In some examples, MIMO can support simultaneous transmission to multiple receivers, which is called multi-user MIMO (MU-MIMO). Some RATs can employ advanced MIMO techniques such as mTRP operations (including redundant transmission or reception on multiple TRPs), reciprocity in the time or frequency domain, single-frequency network (SFN) transmission, or noncoherent joint transmission (NC-JT).

[0068] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive from a network node an uplink power control configuration for a plurality of uplink component carriers, wherein the uplink power control configuration indicates a first TPC-SRS-RNTI and a second TPC-SRS-RNTI, wherein the plurality of uplink component carriers include a first component carrier and a second component carrier, wherein the first component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, and wherein the second component carrier is configured with a first SRS closed-loop power control adjustment state; receive from the network node downlink control information (DCI) indicating a TPC command for the second component carrier, wherein the DCI is scrambled by the first TPC-SRS-RNTI or the second TPC-SRS-RNTI; and transmit SRS to the network node at least in part based on applying the TPC command to the first SRS closed-loop power control adjustment state corresponding to the second component carrier. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0069] In some aspects, the communication manager 140 may receive configurations for uplink component carriers from a network node, wherein the uplink component carriers are configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, wherein the configuration indicates a first start position in DCI format 2_3 associated with the first closed-loop power control adjustment state and a second start position in DCI format 2_3 associated with the second closed-loop power control adjustment state, and wherein DCI format 2_3 associated with the first closed-loop power control adjustment state indicates a TPC command for the first SRS closed-loop power control adjustment state, and DCI format 2_3 associated with the second closed-loop power control adjustment state indicates a TPC command for the second SRS closed-loop power control adjustment state; receive DCI format 2_3 with a CRC scrambled by TPC-SRS-RNTI from the network node; and send SRS to the network node at least in part based on applying either a TPC command in DCI format 2_3 based on the first start position or a TPC command in DCI format 2_3 corresponding to the second start position of the uplink component carrier. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0070] In some aspects, network node 110 may include communication manager 150. As described in more detail elsewhere herein, communication manager 150 may send to the UE an uplink power control configuration for a plurality of uplink component carriers, wherein the uplink power control configuration indicates a first TPC-SRS-RNTI and a second TPC-SRS-RNTI, wherein the plurality of uplink component carriers include a first component carrier and a second component carrier, wherein the first component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, and wherein the second component carrier is configured with a first SRS closed-loop power control adjustment state; send to the UE a DCI indicating a TPC command for the second component carrier, wherein the DCI is scrambled by the first TPC-SRS-RNTI or the second TPC-SRS-RNTI; and receive SRS from the UE at least in part based on the TPC command being applied to the first SRS closed-loop power control adjustment state corresponding to the second component carrier. Additionally or alternatively, communication manager 150 may perform one or more other operations described herein.

[0071] In some aspects, the communication manager 150 may send to the UE a configuration for an uplink component carrier, wherein the uplink component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, wherein the configuration indicates a first start position in DCI format 2_3 associated with the first closed-loop power control adjustment state and a second start position in DCI format 2_3 associated with the second closed-loop power control adjustment state, and wherein DCI format 2_3 associated with the first closed-loop power control adjustment state indicates a TPC command for the first SRS closed-loop power control adjustment state, and DCI format 2_3 associated with the second closed-loop power control adjustment state indicates a TPC command for the second SRS closed-loop power control adjustment state; send to the UE a DCI format 2_3 having a CRC scrambled by TPC-SRS-RNTI; and receive SRS from the UE at least in part based on either a TPC command in DCI format 2_3 based on the first start position or a TPC command in DCI format 2_3 corresponding to the second start position of the uplink component carrier. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0072] As pointed out above, Figure 1 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 1 The examples described are different.

[0073] Figure 2 This is a diagram illustrating communication between an example network node 110 and an example UE 120 in a wireless network according to the present disclosure.

[0074] like Figure 2 As shown, network node 110 may include a data source 212, a transmit processor 214, a transmit (TX) MIMO processor 216, a set of modems 232 (shown as 232a to 232t, where t≥1), a set of antennas 234 (shown as 234a to 234v, where v≥1), a MIMO detector 236, a receive processor 238, a data sink 239, a controller / processor 240, a memory 242, a communication unit 244, a scheduler 246, and / or a communication manager 150, etc. In some configurations, one or a combination of antennas 234, modems 232, MIMO detectors 236, receive processors 238, transmit processors 214, and / or TX MIMO processors 216 may be included in the transceiver of network node 110. The transceiver may be under the control of and used by one or more processors (such as controller / processor 240), and in some respects, may perform aspects of the methods, procedures and / or operations described herein in conjunction with processor-readable code stored in memory 242. In some respects, network node 110 may include one or more interfaces, communication components and / or other components that facilitate communication with UE 120 or another network node.

[0075] The terms “processor,” “controller,” or “controller / processor” can refer to one or more controllers and / or one or more processors. For example, references to “a / the processor,” “a / the controller / processor,” etc. (in the singular) should be understood as referring to a combination of… Figure 2 The processor described refers to any one or more processors, such as a single processor or a combination of multiple different processors. The reference to "one or more processors" should be understood as referring to a combination of... Figure 2 Any one or more processors described herein. For example, one or more processors of network node 110 may include transmit processor 214, TX MIMO processor 216, MIMO detector 236, receive processor 238, and / or controller / processor 240. Similarly, one or more processors of UE 120 may include MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, and / or controller / processor 280.

[0076] In some aspects, a single processor can perform all operations described as being performed by one or more processors. In some aspects, a first set of one or more processors can perform a first operation described as being performed by that one or more processors, and a second set of one or more processors can perform a second operation described as being performed by that one or more processors. The first set of processors and the second set of processors can be the same set of processors or can be different sets of processors. The reference to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as combined... Figure 2 The memory described. For example, an operation described as being performed by one or more memories can be performed by the same subset of the one or more memories or by different subsets of the one or more memories.

[0077] For downlink communication from network node 110 to UE 120, transmitting processor 214 may receive data (“downlink data”) intended for use by UE 120 (or a set of UEs including UE 120) from data source 212 (such as a data pipeline or data queue). In some examples, transmitting processor 214 may select one or more MCSs for UE 120 based on one or more Channel Quality Indicators (CQIs) received from UE 120. Network node 110 may process the data (e.g., including encoding the data) according to the MCS selected for UE 120 for transmission to UE 120 on the downlink, thereby generating data symbols. Transmitting processor 214 may process system information (e.g., semi-static resource partitioning information (SRPI)) and / or control information (e.g., CQI requests, grants, and / or upper-layer signaling) and provide overhead symbols and / or control symbols. The transmitting processor 214 can generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS), demodulation reference signals (DMRS), or channel state information (CSI) reference signals (CSI-RS)) and / or synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)).

[0078] The TX MIMO processor 216 can perform space processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output a set of symbol streams (e.g., TA set of output symbol streams is provided to modem 232. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 232. Each modem 232 may use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for orthogonal frequency division multiplexing (OFDM)) to obtain an output sample stream. Each modem 232 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain a time-domain downlink signal. Modems 232a to 232t may transmit the set of downlink signals (e.g., via a set of corresponding antennas 234) together. T (One downlink signal).

[0079] Downlink signaling may include DCI communication, MAC control element (MAC-CE) communication, RRC communication, downlink reference signaling, or another type of downlink communication. Downlink signaling may be transmitted on the PDCCH, PDSCH, and / or another downlink channel. Downlink signaling may carry one or more transport blocks (TBs) of data. A TB may be a data unit transmitted via the air interface in the wireless communication network 100. A data stream (e.g., from data source 212) may be encoded into multiple TBs for transmission via the air interface. The number of TBs used to carry data associated with a particular data stream may be associated with a TB size shared by multiple TBs. The TB size may be based on the radio channel conditions of the air interface, the MCS used to encode the data, downlink resources allocated for transmitting data, and / or other parameters, or otherwise associated with them. Generally, a larger TB size allows for a larger amount of data to be transmitted in a single transmission, reducing signaling overhead. However, a larger TB size may be more prone to transmission and / or reception errors than a smaller TB size, but such errors can be mitigated by more robust error correction techniques.

[0080] For uplink communication from UE 120 to network node 110, the uplink signal from UE 120 may be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232, shown as DEMOD), detected where applicable by MIMO detector 236 (e.g., receive (Rx) MIMO processor), and / or further processed by receive processor 238 to obtain decoded data and / or control information. Receive processor 238 may provide the decoded data to data sink 239 (which may be a data pipeline, data queue, and / or another type of data sink) and provide the decoded control information to processors such as controller / processor 240.

[0081] Network node 110 may use scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some aspects, scheduler 246 may use DCI to dynamically schedule DL transmissions to and / or UL transmissions from UE 120. In some examples, scheduler 246 may allocate repetitive time-domain and / or frequency-domain resources that UE 120 may use to transmit and / or receive communication using RRC configuration (e.g., semi-static configuration), for example, to perform semi-persistent scheduling (SPS) or to configure configuration grant (CG) for UE 120.

[0082] One or more of the following may be included in the RF chain of network node 110: transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, and / or controller / processor 240. The RF chain may include filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs), and / or other devices for converting analog signals (such as those used for transmission or reception via an air interface) to digital signals (such as those used for processing by one or more processors of network node 110). In some aspects, the RF chain may be a transceiver of network node 110, or may be included in such a transceiver.

[0083] In some examples, network node 110 may use communication unit 244 to communicate with the core network and / or other network nodes. Communication unit 244 may support wired and / or wireless communication protocols and / or connections, such as Ethernet, fiber optic, Common Public Radio Interface (CPRI), and / or wired or wireless backhaul, etc. Network node 110 may use communication unit 244 to send and / or receive data associated with UE 120, or to execute network control signaling, etc. Communication unit 244 may include transceivers and / or interfaces, such as network interfaces.

[0084] UE 120 may include a collection of antennas 252 (shown as antennas 252a to 252r, where r ≥ 1), a collection of modems 254 (shown as modems 254a to 254u, where u ≥ 1), a MIMO detector 256, a receive processor 258, a data sink 260, a data source 262, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, a memory 282, and / or a communication manager 140, etc. One or more components of UE 120 may be included in housing 284. In some aspects, one or a combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, or TX MIMO processor 266 may be included in a transceiver included in UE 120. The transceiver may be under the control of and used by one or more processors (such as controller / processor 280), and in some respects, may perform aspects of the methods, procedures, or operations described herein in conjunction with processor-readable code stored in memory 282. In some respects, UE 120 may include another interface, another communication component, and / or another component that facilitates communication with network node 110 and / or another UE 120.

[0085] For downlink communication from network node 110 to UE 120, the set of antennas 252 can receive downlink communication or signals from network node 110, and can receive the set of downlink signals (e.g., R Each received signal is provided to a set of modems 254. For example, each received signal may be provided to a corresponding demodulator component (shown as DEMOD) of modem 254. Each modem 254 may use the corresponding demodulator component to condition (e.g., filter, amplify, down-convert, and / or digitize) the received signal to obtain an input sample. Each modem 254 may use the corresponding demodulator component to further demodulate or process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 may obtain the received symbols from the set of modems 254, may perform MIMO detection on the received symbols where applicable, and may provide the detected symbols. Receiver processor 258 may process (e.g., decode) the detected symbols, may provide the decoded data for UE 120 to data sink 260 (which may include data pipelines, data queues, and / or applications executed on UE 120), and may provide the decoded control information and system information to controller / processor 280.

[0086] For uplink communication from UE 120 to network node 110, the transmitting processor 264 may receive and process data (“uplink data”) from data source 262 (such as data pipelines, data queues, and / or applications running on UE 120) and control information from controller / processor 280. The control information may include one or more parameters, feedback, one or more signal measurements, and / or other types of control information. In some aspects, the receiving processor 258 and / or controller / processor 280 may determine one or more parameters related to the transmission of uplink communication for received signals (such as those received from network node 110 or another UE). One or more parameters may include a Reference Signal Received Power (RSRP) parameter, a Received Signal Strength Indicator (RSSI) parameter, a Reference Signal Received Quality (RSRQ) parameter, a CQI parameter, or a Transmit Power Control (TPC) parameter, etc. The control information may include indications of the RSRP parameter, RSSI parameter, RSRQ parameter, CQI parameter, TPC parameter, and / or another parameter. Control information can facilitate parameter selection and / or scheduling for UE 120 by network node 110.

[0087] Transmit processor 264 can generate reference symbols for one or more reference signals, such as uplink DMRS, uplink sounding reference signal (SRS), and / or another type of reference signal. Symbols from transmit processor 264 can be pre-decoded by TX MIMO processor 266 where applicable, and further processed by a set of modems 254 (e.g., for DFT-s-OFDM or CP-OFDM). TX MIMO processor 266 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output a set of symbol streams (e.g., ... U A set of output symbol streams is provided to modem 254. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 254. Each modem 254 may use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 254 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain an uplink signal.

[0088] Modems 254a to 254u can transmit uplink signal sets (e.g., via a set of corresponding antennas 252) R One uplink signal or UUplink signals may include UCI communication, MAC-CE communication, RRC communication, or another type of uplink communication. Uplink signals may be transmitted on PUSCH, PUCCH, and / or another type of uplink channel. Uplink signals may carry one or more TBs of data. Sidelink data and control transmission (i.e., transmission directly between two or more UEs 120) may typically use techniques similar to those described for uplink data and control transmission, and may use sidelink-specific channels such as the Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), and / or Physical Sidelink Feedback Channel (PSFCH).

[0089] One or more antennas in the set of antennas 252 or the set of antennas 234 may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc., or may be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, or with one or more transmitting or receiving components (such as...) Figure 2 An antenna module is a combination of one or more antenna elements coupled to one or more components. As used herein, "antenna" can mean one or more antennas, one or more antenna panels, one or more antenna groups, one or more collections of antenna elements, or one or more antenna arrays. "Antenna panel" can mean a group of antennas (such as antenna elements) arranged in an array or panel that can facilitate beamforming by manipulating the parameters of that group of antennas. "Antenna module" can mean a circuit that includes one or more antennas, and may also include one or more other components (such as filters, amplifiers, or processors) associated with integrating the antenna module into a wireless communication device.

[0090] In some examples, each antenna element of antenna 234 or antenna 252 may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element cross-polarized with a second sub-element, which can be used to independently transmit cross-polarized signals. Antenna elements may include patch antennas, dipole antennas, and / or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. The spacing between antenna elements can allow signals with a desired wavelength transmitted individually by the antenna elements to interact or interfere (e.g., to form a desired beam) in various directions. For example, given a desired wavelength or frequency range, the spacing may provide a quarter wavelength, half a wavelength, or another fraction of the wavelength between adjacent antenna elements to allow desired constructive and destructive interference modes of signals transmitted by individual antenna elements within that desired range.

[0091] The amplitude and / or phase of signals transmitted via antenna elements and / or sub-elements can be modulated and (e.g., by manipulating phase shifts, phase offsets, and / or amplitudes) shifted relative to each other to generate one or more beams; this is known as beamforming. The term "beam" can refer to the directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction. "Beam" can also generally refer to the direction associated with such directional signal transmission, the set of directional resources associated with the signal transmission (e.g., angle of arrival, horizontal direction, and / or vertical direction), and / or a set of parameters indicating one or more aspects of the directional signal, the direction associated with the signal, and / or the set of directional resources associated with the signal. In some implementations, antenna elements can be individually selected or deselected for the directional transmission of a signal (or multiple signals) by controlling the amplitude of one or more corresponding amplifiers and / or the phase of the signal to form one or more beams. The shape of the beam (such as amplitude, width, and / or the presence of sidelobes) and / or the direction of the beam (such as the angle of the beam relative to the surface of the antenna array) can be dynamically controlled by modifying the phase shifts, phase offsets, and / or amplitudes of multiple signals relative to each other.

[0092] Different UEs 120 or network nodes 110 may include different numbers of antenna elements. For example, UE 120 may include a single antenna element, two antenna elements, four antenna elements, eight antenna elements, or different numbers of antenna elements. As another example, network node 110 may include eight antenna elements, 24 antenna elements, 64 antenna elements, 128 antenna elements, or different numbers of antenna elements. Generally speaking, a larger number of antenna elements provides increased control over the parameters used for beamforming compared to a smaller number of antenna elements, while a smaller number of antenna elements may be less complex to implement and can use less power. Multiple antenna elements can support multi-layer transmission, in which the same time and frequency resources are used to utilize spatial multiplexing to transmit a first layer of communication (which may include a first data stream) and a second layer of communication (which may include a second data stream).

[0093] Although Figure 2 The boxes in the diagram are illustrated as different components, but the functions described above with respect to these boxes may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0094] Figure 3 This is an illustration of an example decomposed base station architecture 300 according to the present disclosure. One or more components of the example decomposed base station architecture 300 may be, may include, or may be included in one or more network nodes (such as one or more network nodes 110). The decomposed base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or may communicate indirectly with the core network 320 via one or more decomposed control units (such as non-RT RIC 350 and / or near-RT RIC 370 associated with a Service Management and Orchestration (SMO) framework 360) (e.g., via an E2 link). The CU 310 may communicate with one or more DU 330 via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RU 340 via a corresponding fronthaul link. Each RU 340 may communicate with one or more UE 120 via a corresponding RF access link. In some deployments, a UE 120 may be served simultaneously by multiple RU 340s.

[0095] Each component in the components of the decomposed base station architecture 300 (including CU 310, DU 330, RU 340, near-RT RIC 370, non-RT RIC 350, and SMO frame 360) may include one or more interfaces or may be coupled to one or more interfaces for receiving or transmitting signals, such as data or information, via wired or wireless transmission media.

[0096] In some respects, the CU 310 can be logically divided into one or more CU user plane (CU-UP) units and one or more CU control plane (CU-CP) units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be deployed to communicate with one or more DU 330s for network control and signaling, as needed. Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340s. For example, the DU 330 may host various layers, such as the RLC layer, MAC layer, or one or more PHY layers (such as one or more high PHY layers or one or more low PHY layers). Each layer (which may also be referred to as a module) can be implemented using an interface for signaling to other layers (and modules) hosted by the DU 330, or for signaling to control functions hosted by the CU 310. Each RU 340 may implement lower-layer functionality. In some respects, the real-time and non-real-time aspects of communication with the control plane and user plane of the RU 340 can be controlled by the corresponding DU 330.

[0097] The SMO framework 360 supports RAN deployment and provisioning for both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 360 supports the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 360 can interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 390 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 350, and / or near-RT RIC 370. In some aspects, the SMO framework 360 can communicate with hardware aspects of the 4G RAN, 5G NR RAN, and / or 6G RAN (such as the Open eNB (O-eNB) 380) via the O1 interface. Additionally or alternatively, the SMO framework 360 can communicate directly with each of one or more RUs 340 via the respective O1 interface. In some deployments, this configuration enables each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0098] The non-RT RIC 350 may include or implement logic functions that enable non-real-time control and optimization of RAN elements and resources, including AI / ML workflows for model training and updates, and / or policy-based guidance of applications and / or features in the near-RT RIC 370. The non-RT RIC 350 may be coupled to or communicate with the near-RT RIC 370, such as via an A1 interface. The near-RT RIC 370 may include or implement logic functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and actions, connecting one or more CU 310s, one or more DU 330s, and / or O-eNBs to the near-RT RIC 370.

[0099] In some aspects, to generate AI / ML models to be deployed in the near-RT RIC 370, the non-RT RIC 350 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 370 and can be received from non-network data sources or network functions at the SMO framework 360 or the non-RT RIC 350. In some examples, the non-RT RIC 350 or near-RT RIC 370 may modulate RAN behavior or performance. For example, the non-RT RIC 350 may monitor long-term trends and patterns in performance and may employ AI / ML models to perform corrective actions via the SMO framework 360 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0100] As pointed out above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0101] Figure 1 , Figure 2 or Figure 3 Network node 110, its controller / processor 240, UE 120, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technical solutions or perform one or more operations associated with DCI format 2_3 scrambled by different TPC-SRS-RNTIs (e.g., CRC scrambled by different TPC-SRS-RNTIs), as described in more detail elsewhere herein. For example, network node 110's controller / processor 240, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technical solutions or perform one or more operations associated with DCI format 2_3 scrambled by different TPC-SRS-RNTIs (e.g., CRC scrambled by different TPC-SRS-RNTIs), as described in more detail elsewhere herein. Figure 2 Any other component, CU 310, DU 330, or RU340 may (alone or in combination with one or more other processors) perform or direct, for example... Figure 7 The process 700 Figure 8 The process 800 Figure 9 The process 900 Figure 10The operation of process 1000 or other processes as described herein. Memory 242 may store data and program code for network node 110, CU 310, DU 330, or RU 340. Memory 282 may store data and program code for UE 120. In some examples, memory 242 or memory 282 may include a non-transitory computer-readable medium storing a set of instructions (e.g., code or program code) for wireless communication. Memory 242 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). Memory 282 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). For example, the set of instructions may be executed by one or more processors of network node 110, UE 120, CU 310, DU 330, or RU 340 (e.g., directly, or after compilation, transformation, or interpretation). Figure 7 Process 700 Figure 8 The process 800 Figure 9 The process 900 Figure 10 The process 1000 or other processes as described herein. In some examples, the execution instructions may include run instructions, transform instructions, compile instructions and / or interpret instructions, etc.

[0102] In some aspects, the UE (e.g., UE 120) includes components for receiving from a network node an uplink power control configuration for a plurality of uplink component carriers, wherein the uplink power control configuration indicates a first TPC-SRS-RNTI and a second TPC-SRS-RNTI, wherein the plurality of uplink component carriers include a first component carrier and a second component carrier, wherein the first component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, and wherein the second component carrier is configured with a first SRS closed-loop power control adjustment state; components for receiving from the network node downlink control information (DCI) indicating a TPC command for the second component carrier, wherein the DCI is scrambled by the first TPC-SRS-RNTI or the second TPC-SRS-RNTI; and / or components for transmitting SRS to the network node at least in part based on applying the TPC command to the first SRS closed-loop power control adjustment state corresponding to the second component carrier. Components that enable the UE to perform the operations described herein may include one or more of, for example, a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0103] In some aspects, the UE (e.g., UE 120) includes components for receiving configurations for an uplink component carrier from a network node, wherein the uplink component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, wherein the configuration indicates a first start position in DCI format 2_3 associated with the first closed-loop power control adjustment state and a second start position in DCI format 2_3 associated with the second closed-loop power control adjustment state, and wherein the DCI format 2_3 associated with the first closed-loop power control adjustment state indicates for the first SRS closed-loop power control adjustment. The TPC command for the second SRS closed-loop power control adjustment state, and the DCI format 2_3 associated with the second closed-loop power control adjustment state indicating the TPC command for the second SRS closed-loop power control adjustment state; components for receiving from the network node a DCI format 2_3 with a CRC scrambled by TPC-SRS-RNTI; and / or components for transmitting SRS to the network node based at least in part on applying the following: a TPC command in DCI format 2_3 based on a first starting position or a TPC command in DCI format 2_3 based on a second starting position corresponding to an uplink component carrier. Components for the UE to perform the operations described herein may include, for example, one or more of the following: communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0104] In some aspects, a network node (e.g., network node 110) includes: means for transmitting to a UE an uplink power control configuration for a plurality of uplink component carriers, wherein the uplink power control configuration indicates a first TPC-SRS-RNTI and a second TPC-SRS-RNTI, wherein the plurality of uplink component carriers include a first component carrier and a second component carrier, wherein the first component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, and wherein the second component carrier is configured with a first SRS closed-loop power control adjustment state; means for transmitting to the UE a DCI indicating a TPC command for the second component carrier, wherein the DCI is scrambled by the first TPC-SRS-RNTI or the second TPC-SRS-RNTI; and / or means for receiving SRS from the UE based at least in part on the TPC command being applied to the first SRS closed-loop power control adjustment state corresponding to the second component carrier. Components that enable network nodes to perform the operations described herein may include one or more of the following: a communication manager 150, a transmit processor 214, a TX MIMO processor 216, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0105] In some aspects, a network node (e.g., network node 110) includes components for transmitting configuration to the UE for an uplink component carrier, wherein the uplink component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, wherein the configuration indicates a first start position in DCI format 2_3 associated with the first closed-loop power control adjustment state and a second start position in DCI format 2_3 associated with the second closed-loop power control adjustment state, and wherein the DCI format 2_3 associated with the first closed-loop power control adjustment state indicates for the first SRS closed-loop power control adjustment state. The components include: a TPC command for a first SRS closed-loop power control adjustment state, and a DCI format 2_3 associated with a second closed-loop power control adjustment state indicating a TPC command for the second SRS closed-loop power control adjustment state; a component for sending a DCI format 2_3 with a CRC scrambled by TPC-SRS-RNTI to the UE; and / or a component for receiving SRS from the UE based at least in part on: a TPC command in DCI format 2_3 based on a first starting position or a TPC command in DCI format 2_3 based on a second starting position corresponding to an uplink component carrier. Components for network nodes to perform the operations described herein may include, for example, one or more of the following: a communication manager 150, a transmit processor 214, a TX MIMO processor 216, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0106] As pointed out above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0107] Figure 4A and Figure 4B This is a diagram illustrating example 400 of carrier aggregation according to this disclosure.

[0108] Carrier aggregation is a technique that enables two or more component carriers (CCs, sometimes referred to as carriers) to be combined (e.g., combined into a single channel) for a single UE 120 to enhance data capacity. As shown, carriers can be combined in the same or different frequency bands. Additionally or alternatively, contiguous or discontinuous carriers can be combined. Network node 110 can configure carrier aggregation for UE 120 (such as in Radio Resource Control (RRC) messages, Downlink Control Information (DCI) and / or other signaling messages).

[0109] like Figure 4AAs shown and as indicated by reference numeral 405, in some aspects, carrier aggregation can be configured in an intra-band continuous mode, wherein the aggregated carriers are continuous with each other and in the same frequency band. As indicated by reference numeral 410, in some aspects, carrier aggregation can be configured in an intra-band discontinuous mode, wherein the aggregated carriers are discontinuous with each other and in the same frequency band. As indicated by reference numeral 415, in some aspects, carrier aggregation can be configured in an inter-band discontinuous mode, wherein the aggregated carriers are discontinuous with each other and in different frequency bands.

[0110] In carrier aggregation, UE 120 can be configured using a primary carrier or primary cell (PCell) and one or more secondary carriers or secondary cells (SCells). In some aspects, the primary carrier may carry control information (e.g., downlink control information and / or scheduling information) for scheduling data communications on one or more secondary carriers; this may be referred to as cross-carrier scheduling. In some aspects, a carrier (e.g., a primary carrier or a secondary carrier) may carry control information for scheduling data communications on that carrier; this may be referred to as self-carrier scheduling or carrier self-scheduling.

[0111] In some cases, carrier aggregation can be configured, where the aggregated component carriers have a mixed component carrier mode. For example, such as... Figure 4B As shown and as indicated by reference numeral 420, the aggregated component carriers may include two mode 1 component carriers (e.g., CC0 and CC1, as shown in the figure). Figure 4B (as shown) and two mode 2 component carriers (e.g., CC2 and CC3, as shown) Figure 4B (As shown). In this case, using DCI format 2_3 with a CRC scrambled by the first TPC-SRS-RNTI or the second TPC-SRS-RNTI to indicate that the TPC command is used for the first SRS closed-loop power control adjustment state or the second SRS closed-loop power control adjustment state respectively may result in signaling waste relative to the mode 2 component carrier.

[0112] For example, the UE can be configured with four Type B blocks in DCI format 2_3. Each Type B block can correspond to one of the aggregated component carriers CC0-CC3. If DCI format 2_3 has a CRC scrambled by the first TPC-SRS-RNTI, then for the aggregated component carriers CC0-CC3, the TPC command in DCI format 2_3 is applied to the first SRS closed-loop power control adjustment state (e.g., =0). If DCI format 2_3 has a CRC scrambled by the second TPC-SRS-RNTI, then for the aggregated component carriers CC0-CC3, the TPC command in DCI format 2_3 is applied to the second SRS closed-loop power control adjustment state (e.g., =1). However, for component carriers CC2 and CC3, since only a single SRS closed-loop power control adjustment state is configured (e.g., When =0), the TPC commands corresponding to component carriers CC2 and CC3 in DCI format 2_3 with CRC scrambled by the second TPC-SRS-RNTI can be omitted.

[0113] As pointed out above, Figure 4A and Figure 4B This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 4A and Figure 4B The examples described are different.

[0114] Figure 5A and Figure 5B This is an illustration of example 500 associated with DCI format 2_3 having CRC scrambled by different TPC-SRS-RNTIs according to this disclosure. (See diagram below.) Figure 5A As shown, network node 110 and UE 120 can communicate with each other.

[0115] In some specific implementations, UE 120 may be configured with four uplink component carriers (e.g., component carriers CC0-CC3, as shown in Figure 5). As indicated by reference numeral 505, component carriers CC0 and CC1 may include mode 1 component carriers configured with two SRS closed-loop power control adjustment states, and component carriers CC2 and CC3 may include mode 2 component carriers configured with one SRS closed-loop power control adjustment state.

[0116] As shown by reference numeral 505 in the attached figure, network node 110 can send configuration information, and UE 120 can receive the configuration information. For example, network node 110 can send uplink power control configuration for multiple uplink component carriers, and UE 120 can receive the uplink power control configuration.

[0117] In some specific implementations, the configuration information can configure carrier aggregation with a set of component carriers, which has a mixed component carrier mode. For example, such as... Figure 5B As shown and as indicated by reference numeral 510 in the accompanying drawings, the component carrier set may include two SRS closed-loop power control adjustment states configured (e.g., =0 and =1, such as Figure 5B The two mode 1 component carriers (e.g., CC0 and CC1, as shown) Figure 5B (as shown) and configured with an SRS closed-loop power control adjustment state (e.g., =0, such as Figure 5B The two mode 2 component carriers (e.g., CC2 and CC3, as shown) Figure 5B (As shown).

[0118] In some specific implementations, the configuration information may indicate that the first TPC-SRS-RNTI is associated with a first SRS closed-loop power control adjustment state, and the second TPC-SRS-RNTI is associated with a second SRS closed-loop power control adjustment state. For example, the first SRS closed-loop power control adjustment state may be associated with a first closed-loop power control adjustment state index, and the second SRS closed-loop power control adjustment state may be associated with a second closed-loop power control adjustment state index. The configuration information may indicate that the first TPC-SRS-RNTI is associated with the first closed-loop power control adjustment state index, and that the second TPC-SRS-RNTI is associated with the second closed-loop power control adjustment state index.

[0119] In some specific implementations, UE 120 may determine (and / or configuration information may indicate) that a TPC command indicated in DCI format 2_3 with a CRC scrambled by a first TPC-SRS-RNTI will be applied to a first SRS closed-loop power control adjustment state, and determine that a TPC command indicated in DCI format 2_3 with a CRC scrambled by a second TPC-SRS-RNTI will be applied to a second SRS closed-loop power control adjustment state. For example, UE 120 may determine (and / or configuration information may indicate) that a TPC command indicated in DCI format 2_3, with a CRC scrambled by the first TPC-SRS-RNTI, will be applied to the first SRS closed-loop power control adjustment state, based at least in part on the association of the first TPC-SRS-RNTI with the first closed-loop power control adjustment state index and the association of the second TPC-SRS-RNTI with the second closed-loop power control adjustment state index, and determine that a TPC command indicated in DCI format 2_3, with a CRC scrambled by the second TPC-SRS-RNTI, will be applied to the second SRS closed-loop power control adjustment state.

[0120] like Figure 5A As shown and as indicated by reference numeral 515, network node 110 can transmit DCI format 2_3 with a CRC scrambled by a second TPC-SRS-RNTI, and UE 120 can receive DCI format 2_3. DCI format 2_3 may include one or more Type A blocks or one or more Type B blocks. The types of blocks included in DCI format 2_3 can be indicated in the configuration information.

[0121] like Figure 5BAs shown and as indicated by reference numeral 520, in some specific implementations, DCI format 2_3 may include multiple Type B blocks (e.g., block 1- N ,like Figure 5B (As shown). Each block may be associated with a corresponding component carrier and may indicate a TPC command for the corresponding component carrier. UE 120 may determine the location of a block having DCI format 2_3 based at least in part on the initial location. In some implementations, the initial location of a block may be indicated in configuration information. For example, the configuration information may indicate an initial location 525 corresponding to a block including a TPC command associated with component carrier CC0, an initial location 530 corresponding to a block including a TPC command associated with component carrier CC1, an initial location 535 corresponding to a block including a TPC command associated with component carrier CC2, and an initial location 540 corresponding to a block including a TPC command associated with component carrier CC3.

[0122] As indicated by reference numeral 545, in some embodiments, DCI format 2_3 may include a Type A block. In some embodiments, UE 120 may be associated with a specific block (e.g., block 1). For example, configuration information may indicate the same starting location for blocks associated with UE 120 for CC0 through CC3. UE 120 may identify blocks associated with UE 120 at least in part based on the starting location indicated in the configuration information.

[0123] As indicated by reference numeral 550, the block associated with UE 120 (e.g., block 1, such as...) Figure 5B (As shown) may include an SRS request field and multiple TPC command fields (e.g., TPC1-TPC4, such as...). Figure 5B (As shown). The SRS Request field can indicate the set of component carriers to which the TPC command indicated by multiple TPC command fields is applied (e.g., component carriers CC0-CC3). For example, UE120 can receive an RRC parameter indicating the index of a component carrier in the corresponding component carrier set (e.g., cc-IndexInOneCC-Set). The RRC parameter can indicate up to three component carrier sets, where one of these component carrier sets is triggered by the SRS Request field.

[0124] like Figure 5A As shown and as indicated by reference numeral 555, UE 120 may apply the TPC command indicated by DCI format 2_3 to the corresponding component carriers CC0-CC3. In some specific implementations, DCI format 2_3 may include multiple Type B blocks, and UE 120 may apply the TPC command indicated by the Type B block to the SRS closed-loop power control adjustment state of the corresponding component carrier associated with each Type B block.

[0125] In some specific implementations, UE 120 may apply the TPC command indicated by the first Type B block and the TPC command indicated by the second Type B block to the second SRS closed-loop power control adjustment state of component carrier CC0 and component carrier CC1, respectively, based at least in part on DCI format 2_3 with CRC scrambled by the second TPC-SRS-RNTI.

[0126] In some specific implementations, UE 120 may apply the TPC command indicated by the third Type B block and the TPC command indicated by the fourth Type B block to the first SRS closed-loop power control adjustment state of component carriers CC2 and CC3, respectively, based at least in part on the fact that component carriers CC2 and CC3 are configured with a single SRS closed-loop power control adjustment state. In other words, for a component carrier configured with a single SRS closed-loop power control adjustment state, UE 120 may apply the TPC command indicated in DCI format 2_3 to the single SRS closed-loop power control adjustment state configured for the component carrier, regardless of which TPC-SRS-RNTI is used to scramble the CRC (e.g., when DCI format 2_3 has a CRC scrambled by the first TPC-SRS-RNTI, or when DCI format 2_3 has a CRC scrambled by the second TPC-SRS-RNTI, the TPC command may be applied to the single SRS closed-loop power control adjustment state configured for the component carrier).

[0127] In some specific implementations, DCI format 2_3 may include a Type A block associated with UE 120, and UE 120 may apply TPC commands indicated by the TPC command field to the SRS closed-loop power control adjustment state of the corresponding component carrier associated with each TPC command field.

[0128] In some specific implementations, UE 120 may apply the TPC command indicated by the first TPC command field and the TPC command indicated by the second TPC command field to the second SRS closed-loop power control adjustment state of component carrier CC0 and component carrier CC1, respectively, based at least in part on DCI format 2_3 with CRC scrambled by the second TPC-SRS-RNTI.

[0129] In some specific implementations, UE 120 may apply TPC commands indicated by the third TPC command field and the fourth TPC command field, respectively, to the first SRS closed-loop power control adjustment states of component carriers CC2 and CC3, based at least in part on the fact that component carriers CC2 and CC3 are configured with a single SRS closed-loop power control adjustment state. In other words, for a component carrier configured with a single SRS closed-loop power control adjustment state, UE 120 may apply the TPC command indicated in DCI format 2_3 to the single SRS closed-loop power control adjustment state configured for the component carrier, regardless of which TPC-SRS-RNTI is used to scramble the CRC (e.g., when DCI format 2_3 has a CRC scrambled by the first TPC-SRS-RNTI, or when DCI format 2_3 has a CRC scrambled by the second TPC-SRS-RNTI, the TPC command may be applied to the single SRS closed-loop power control adjustment state configured for the component carrier).

[0130] As pointed out above, Figure 5A and Figure 5B This is provided as an example. Other examples are available relative to... Figure 5A and Figure 5B The examples described are different.

[0131] Figure 6 This is a diagram illustrating example 600 associated with DCI format 2_3 according to this disclosure, which indicates TPC commands associated with different SRS closed-loop power control adjustment states. For example... Figure 6 As shown, network node 110 and UE 120 can communicate with each other.

[0132] As shown by reference numeral 605, network node 110 can transmit a configuration for the uplink component carrier, and UE 120 can receive this configuration. In some implementations, the uplink component carrier can be configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state. This configuration can indicate a first start position in DCI format 2_3 associated with the first closed-loop power control adjustment state and a second start position in DCI format 2_3 associated with the second closed-loop power control adjustment state (e.g., the first SRS closed-loop power control adjustment state or the second SRS closed-loop power control adjustment state). For example, the first start position can indicate the position of the first bit of a block corresponding to a closed-loop power control adjustment state (e.g., the first SRS closed-loop power control adjustment state or the second SRS closed-loop power control adjustment state), and the second start position can indicate the position of the first bit of a block corresponding to another closed-loop power control adjustment state (e.g., the first SRS closed-loop power control adjustment state or the second SRS closed-loop power control adjustment state).

[0133] In some specific implementations, the configuration information may include a first field indicating a first starting position and a second field indicating a second starting position. For example, the configuration information may include SRS-TPC-CommandConfig, and the first field may include a first startingBitOfFormat2-3 field, and the second field may include a second startingBitOfFormat2-3 field.

[0134] In some specific implementations, the configuration information may include a first configuration and a second configuration. For example, network node 110 may send a first configuration for an uplink component carrier, and UE 120 may receive this first configuration. The first configuration may indicate a first starting position. For example, the first configuration may include a first SRS-TPC-CommandConfig, which includes a startingBitOfFormat2-3 field indicating the first position.

[0135] Network node 110 may transmit a second configuration for the uplink component carrier, and UE 120 may receive the second configuration. The second configuration may indicate a second starting position. For example, the second configuration may include a second SRS-TPC-CommandConfig, which includes a startingBitOfFormat2-3 field indicating the second position.

[0136] In some specific implementations, the configuration information can configure the UE 120 with different uplink component carrier sets for different SRS closed-loop power control adjustment states. For example, the configuration information can configure the first set of component carriers with a first SRS closed-loop power control adjustment state, and the second set of uplink component carriers with a second SRS closed-loop power control adjustment state.

[0137] In some specific implementations, the configuration information may include a first SRS-TPC-Physical Downlink Control Channel (PDCCH)-Config entry corresponding to the first SRS closed-loop power control adjustment state and a second SRS-TPC-PDCCH-Config entry corresponding to the second SRS closed-loop power control adjustment state.

[0138] In some specific implementations, the configuration information may include a list of component carrier set indices corresponding to multiple component carrier sets. The list of component carrier set indices can configure each component carrier set in the multiple component carrier sets with a first SRS closed-loop power control adjustment state or a second SRS closed-loop power control adjustment state.

[0139] In some specific implementations, the configuration information may indicate the first cc-SetIndex and the first cc-IndexInOneCC-Set corresponding to the first SRS closed-loop power control adjustment state, and the second cc-SetIndex and the second cc-IndexInOneCC-Set corresponding to the second SRS closed-loop power control adjustment state.

[0140] In some implementations, the configuration information may include fields indicating whether the SRS request field exists in both the DCI format 2_3 associated with the first closed-loop power control adjustment state and the DCI format 2_3 associated with the second closed-loop power control adjustment state. For example, the configuration information may include a field indicating whether the SRS request field exists (e.g., the fieldTypeFormat2_3 field), and this field may be applied to both the DCI format 2_3 associated with the first closed-loop power control adjustment state and the DCI format 2_3 associated with the second closed-loop power control adjustment state.

[0141] In some implementations, the configuration information may include a field indicating whether the SRS request field exists in the DCI format 2_3 associated with a fixed closed-loop power control adjustment state. For example, the configuration information may include a field indicating whether the SRS request field exists in the DCI format 2_3 associated with a first closed-loop power control adjustment state, and may not include a field indicating whether the SRS request field exists in the DCI format 2_3 associated with a second closed-loop power control adjustment state.

[0142] In some specific implementations, UE 120 may determine, at least in part, that the SRS request field is not present in DCI format 2_3 associated with the second closed-loop power control adjustment state, based on the presence of the SRS request field in DCI format 2_3 associated with the first closed-loop power control adjustment state. For example, when the SRS request field indicates that the SRS request field is present in DCI format 2_3 associated with the first closed-loop power control adjustment state, UE 120 may determine that the field is not present in DCI format 2_3 associated with the second closed-loop power control adjustment state.

[0143] As another example, UE 120 may determine that the SRS request field exists in DCI format 2_3 associated with the second closed-loop power control adjustment state. In this case, UE 120 may determine, at least in part, that the SRS request field does not exist in DCI format 2_3 associated with the first closed-loop power control adjustment state, based on the fact that the SRS request field exists in DCI format 2_3 associated with the second closed-loop power control adjustment state.

[0144] In some specific implementations, the configuration information may include a first field and a second field. The first field may indicate whether the SRS request field exists in the DCI format 2_3 associated with the first closed-loop power control adjustment state, and the second field may indicate whether the SRS request field exists in the DCI format 2_3 associated with the second closed-loop power control adjustment state.

[0145] In some specific implementations, the configuration information may include SRS-TPC-CommandConfig. SRS-TPC-CommandConfig may include a first fieldTypeFormat2-3 field indicating whether the SRS request field exists in DCI format 2_3 associated with the first closed-loop power control adjustment state and a second fieldTypeFormat2-3 field indicating whether the SRS request field exists in DCI format 2_3 associated with the second closed-loop power control adjustment state.

[0146] In some implementations, network node 110 may send a first configuration and a second configuration, and UE 120 may receive the first configuration and the second configuration. The first configuration may include an indication of whether an SRS request field exists in a field of DCI format 2_3 associated with a first closed-loop power control adjustment state. The second configuration may include an indication of whether an SRS request field exists in a field of DCI format 2_3 associated with a second closed-loop power control adjustment state.

[0147] As indicated by reference numeral 610, network node 110 may transmit DCI format 2_3, and UE 120 may receive DCI format 2_3. In some specific implementations, DCI format 2_3 may include CRC scrambled by TPC-SRS-RNTI.

[0148] As shown by reference numeral 615 in the attached figure, UE 120 can determine the starting position associated with the TPC command in DCI format 2_3 for the uplink component carrier.

[0149] For example, UE 120 may determine whether to use a first or second start position in DCI format 2_3 for the uplink component carrier, as described elsewhere in this document. UE 120 may determine the TPC command by at least partially determining the start position.

[0150] In some specific implementations, UE 120 may determine, at least in part, whether the uplink component carrier is associated with a first starting position or a second starting position based on the TPC-SRS-RNTI. For example, when DCI format 2_3 includes a CRC scrambled by the first TPC-SRS-RNTI, UE 120 may determine that the uplink component carrier is associated with the first starting position. When DCI format 2_3 includes a CRC scrambled by the second TPC-SRS-RNTI, UE 120 may determine that the uplink component carrier is associated with the second starting position.

[0151] In some specific implementations, UE 120 may determine whether the uplink component carrier is associated with a first starting position or a second starting position based at least in part on the cell associated with the received DCI format 2_3. For example, UE 120 may determine that the uplink component carrier is associated with the first starting position based at least in part on the detection of DCI format 2_3 in the first monitoring cell. UE 120 may determine that the uplink component carrier is associated with the second starting position based at least in part on the detection of DCI format 2_3 in the second monitoring cell.

[0152] As shown by reference numeral 620 in the accompanying drawing, UE 120 may apply TPC commands to uplink component carriers. In some implementations, UE 120 may apply TPC commands to a first SRS closed-loop power control adjustment state or a second SRS closed-loop power control adjustment state, at least in part, based on whether the TPC command is associated with a first start position or a second start position. For example, when the TPC command is associated with a first start position, UE 120 may apply the TPC command to the first closed-loop power control adjustment state. When the TPC command is associated with a second start position, UE 120 may apply the TPC command to the second closed-loop power control adjustment state.

[0153] As shown by reference numeral 625 in the accompanying figure, UE 120 may transmit SRS via uplink component carrier. UE 120 may transmit SRS via uplink component carrier at least in part based on applying a TPC command to a first SRS closed-loop power control adjustment state or a second SRS closed-loop power control adjustment state.

[0154] As pointed out above, Figure 6 This is provided as an example. Other examples are available relative to... Figure 6 The examples described are different.

[0155] Figure 7This is a diagram illustrating an example process 700 performed, for example, at a UE or a device of a UE, according to this disclosure. Example process 700 is an example in which a device or UE (e.g., UE 120) performs operations associated with DCI format 2_3 scrambled by different TPC-SRS-RNTI.

[0156] like Figure 7 As shown, in some aspects, process 700 may include receiving uplink power control configurations from a network node for a plurality of uplink component carriers, wherein the uplink power control configurations indicate a first TPC-SRS-RNTI and a second TPC-SRS-RNTI, wherein the plurality of uplink component carriers include a first component carrier and a second component carrier, wherein the first component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, and wherein the second component carrier is configured with a first SRS closed-loop power control adjustment state (block 710). For example, a UE (e.g., using...) Figure 11 The receiving component 1102 and / or communication manager 1106 depicted herein can receive uplink power control configurations for a plurality of uplink component carriers from a network node, wherein the uplink power control configurations indicate a first TPC-SRS-RNTI and a second TPC-SRS-RNTI, wherein the plurality of uplink component carriers include a first component carrier and a second component carrier, wherein the first component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, and wherein the second component carrier is configured with a first SRS closed-loop power control adjustment state, as described above.

[0157] like Figure 7 Further shown, in some aspects, process 700 may include receiving from a network node a DCI indicating a TPC command for a second component carrier, wherein the DCI is scrambled by a first TPC-SRS-RNTI or a second TPC-SRS-RNTI (box 720). For example, the UE (e.g., using...) Figure 11 The receiving component 1102 and / or communication manager 1106 depicted herein can receive from the network node a DCI indicating a TPC command for a second component carrier, wherein the DCI is scrambled by a first TPC-SRS-RNTI or a second TPC-SRS-RNTI, as described above.

[0158] like Figure 7 Further, as shown, in some aspects, process 700 may include sending an SRS (block 730) to the network node based at least in part on applying a TPC command to a first SRS closed-loop power control adjustment state corresponding to the second component carrier. For example, the UE (e.g., using...) Figure 11The transmitting component 1104 and / or the communication manager 1106 described above can transmit SRS to the network node at least in part based on applying TPC commands to the first SRS closed-loop power control adjustment state corresponding to the second component carrier, as described above.

[0159] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere in this document.

[0160] In the first aspect, DCI includes DCI format 2_3 messages.

[0161] In a second aspect, either alone or in combination with the first aspect, process 700 includes applying a TPC command to a first SRS closed-loop power control adjustment state corresponding to the second component carrier, based at least in part on the second component carrier being configured with a single SRS closed-loop power control adjustment state.

[0162] In a third aspect, either alone or in combination with one or more of the first and second aspects, the first SRS closed-loop power control adjustment state is associated with a first closed-loop power control adjustment state index, and the second SRS closed-loop power control adjustment state is associated with a second closed-loop power control adjustment state index.

[0163] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the DCI includes a plurality of blocks of the first type, and each of the plurality of blocks indicates a TPC command for a corresponding uplink component carrier among the plurality of uplink component carriers.

[0164] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the DCI includes a single block of the second type indicating multiple TPC commands for multiple component carriers, wherein each TPC command corresponds to a corresponding component carrier among the multiple component carriers.

[0165] although Figure 7 An example box of process 700 is shown, but in some respects, process 700 may include... Figure 7 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes, boxes, or boxes in a different manner. Alternatively, two or more boxes in the process 700 may be executed in parallel.

[0166] Figure 8This is a diagram illustrating an example process 800 performed, for example, at a UE or a device of a UE, according to this disclosure. Example process 800 is an example in which a device or UE (e.g., UE 120) performs an operation associated with DCI format 2_3, which indicates a TPC command associated with a different SRS closed-loop power control adjustment state.

[0167] like Figure 8 As shown, in some aspects, process 800 may include receiving configuration for an uplink component carrier from a network node, wherein the uplink component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, wherein the configuration indicates a first start position in DCI format 2_3 associated with the first closed-loop power control adjustment state and a second start position in DCI format 2_3 associated with the second closed-loop power control adjustment state, and wherein DCI format 2_3 associated with the first closed-loop power control adjustment state indicates a TPC command for the first SRS closed-loop power control adjustment state, and DCI format 2_3 associated with the second closed-loop power control adjustment state indicates a TPC command for the second SRS closed-loop power control adjustment state (block 810). For example, the UE (e.g., using...) Figure 11 The receiving component 1102 and / or communication manager 1106 depicted herein can receive configuration for an uplink component carrier from a network node, wherein the uplink component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, wherein the configuration indicates a first start position in DCI format 2_3 associated with the first closed-loop power control adjustment state and a second start position in DCI format 2_3 associated with the second closed-loop power control adjustment state, and wherein DCI format 2_3 associated with the first closed-loop power control adjustment state indicates a TPC command for the first SRS closed-loop power control adjustment state, and DCI format 2_3 associated with the second closed-loop power control adjustment state indicates a TPC command for the second SRS closed-loop power control adjustment state, as described above.

[0168] like Figure 8 Further, as shown, in some aspects, process 800 may include receiving DCI format 2_3 (box 820) from a network node with a CRC scrambled by TPC-SRS-RNTI. For example, the UE (e.g., using...) Figure 11 The receiving component 1102 and / or communication manager 1106 depicted herein can receive DCI format 2_3 with CRC scrambled by TPC-SRS-RNTI from the network node, as described above.

[0169] like Figure 8Further, in some aspects, process 800 may include sending SRS to the network node at least in part based on applying: a TPC command in DCI format 2_3 based on a first starting position or a TPC command in DCI format 2_3 based on a second starting position corresponding to an uplink component carrier (box 830). For example, the UE (e.g., using...) Figure 11 The transmitting component 1104 and / or communication manager 1106 described herein may transmit SRS to the network node at least in part based on the following: a TPC command in DCI format 2_3 based on a first starting position or a TPC command in DCI format 2_3 based on a second starting position corresponding to an uplink component carrier, as described above.

[0170] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere in this document.

[0171] In the first aspect, the TPC command in DCI format 2_3 is determined based on a first start position, which is at least partially based on TPC-SRS-RNTI including a first TPC-SRS-RNTI, and the TPC command in DCI format 2_3 is determined based on a second start position, which is at least partially based on TPC-SRS-RNTI corresponding to a second TPC-SRS-RNTI.

[0172] In a second aspect, either alone or in combination with the first aspect, the TPC command in DCI format 2_3 is based on a first starting position, which is at least partially based on the detection of DCI format 2_3 in a first monitoring cell, and wherein the TPC command in DCI format 2_3 is based on a second starting position, which is at least partially based on the detection of DCI format 2_3 in a second monitoring cell.

[0173] In a third aspect, the configuration includes a first field indicating a first starting position and a second field indicating a second starting position, either alone or in combination with one or more of the first and second aspects.

[0174] In the fourth aspect, the configuration includes SRS-TPC-CommandConfig, either alone or in combination with one or more of the first to third aspects, wherein the first field includes a first startingBitOfFormat2-3 field, and wherein the second field includes a second startingBitOfFormat2-3 field.

[0175] In the fifth aspect, receiving a configuration for an uplink component carrier, either alone or in combination with one or more of the first to fourth aspects, includes: receiving a first configuration for the uplink component carrier, wherein the first configuration indicates a first starting position; and receiving a second configuration for the uplink component carrier, wherein the second configuration indicates a second starting position.

[0176] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the first set of uplink component carriers is configured with a first SRS closed-loop power control adjustment state, and the second set of uplink component carriers is configured with a second SRS closed-loop power control adjustment state.

[0177] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the configuration for the uplink component carrier includes a first SRS-TPC-PDCCH-Config entry corresponding to a first SRS closed-loop power control adjustment state and a second SRS-TPC-PDCCH-Config entry corresponding to a second SRS closed-loop power control adjustment state.

[0178] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, a configuration is provided that includes a first set of component carrier set indices corresponding to a first SRS closed-loop power control adjustment state and a second set of component carrier set indices corresponding to a second SRS closed-loop power control adjustment state.

[0179] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, a list of component carrier set indices corresponding to multiple component carrier sets is configured, and the list of component carrier set indices configures each of the multiple component carrier sets with a first SRS closed-loop power control adjustment state or a second SRS closed-loop power control adjustment state.

[0180] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the configuration indicates the first cc-SetIndex and the first cc-IndexInOneCC-Set corresponding to the first SRS closed-loop power control adjustment state, and the second cc-SetIndex and the second cc-IndexInOneCC-Set corresponding to the second SRS closed-loop power control adjustment state.

[0181] In the eleventh aspect, the configuration includes, individually or in combination with one or more of the first to tenth aspects, a field indicating whether the SRS request field exists in the DCI format 2_3 associated with the first closed-loop power control adjustment state and the DCI format 2_3 associated with the second closed-loop power control adjustment state.

[0182] In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the fields include the fieldTypeFormat2-3 fields.

[0183] In the thirteenth aspect, the configuration includes, individually or in combination with one or more of the first to twelfth aspects, a field indicating whether the SRS request field exists in the DCI format 2_3 associated with the first closed-loop power control adjustment state or the DCI format 2_3 associated with the second closed-loop power control adjustment state.

[0184] In the fourteenth aspect, either alone or in combination with one or more of the first to thirteenth aspects, the configuration includes indicating whether the SRS request field exists in a field of DCI format 2_3 associated with the first closed-loop power control adjustment state, and at least in part based on the configuration including indicating whether the SRS request field exists in a field of DCI format 2_3 associated with the first closed-loop power control adjustment state, the SRS request field does not exist in DCI format 2_3 associated with the second closed-loop power control adjustment state.

[0185] In the fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, the configuration includes indicating whether the SRS request field exists in a field of DCI format 2_3 associated with the second closed-loop power control adjustment state, and at least in part based on the configuration including indicating whether the SRS request field exists in a field of DCI format 2_3 associated with the second closed-loop power control adjustment state, the SRS request field does not exist in DCI format 2_3 associated with the first closed-loop power control adjustment state.

[0186] In the sixteenth aspect, the configuration includes, individually or in combination with one or more of the first to fifteenth aspects, a first field in DCI format 2_3 that indicates whether the SRS request field exists in the first closed-loop power control adjustment state and a second field in DCI format 2_3 that indicates whether the SRS request field exists in the second closed-loop power control adjustment state.

[0187] In the seventeenth aspect, the configuration includes SRS-TPC-CommandConfig, either alone or in combination with one or more of the first to sixteenth aspects, wherein the first field includes a first fieldTypeFormat2-3 field, and wherein the second field includes a second fieldTypeFormat2-3 field.

[0188] In the eighteenth aspect, receiving configuration for an uplink component carrier, either alone or in combination with one or more of the first to seventeenth aspects, includes: receiving a first configuration, the first configuration including an indication of whether an SRS request field exists in a field of DCI format 2_3 associated with a first closed-loop power control adjustment state; and receiving a second configuration, the second configuration including an indication of whether an SRS request field exists in a field of DCI format 2_3 associated with a second closed-loop power control adjustment state.

[0189] although Figure 8 An example box of process 800 is shown, but in some respects, process 800 may include... Figure 8 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the process 800 may be executed in parallel.

[0190] Figure 9 This is a diagram illustrating an example process 900 performed, for example, at a network node or a device of a network node, according to the present disclosure. Example process 900 is an example in which a device or network node (e.g., network node 110) performs operations associated with DCI format 2_3 scrambled by different TPC-SRS-RNTI.

[0191] like Figure 9 As shown, in some aspects, process 900 may include sending an uplink power control configuration to the UE for a plurality of uplink component carriers, wherein the uplink power control configuration indicates a first TPC-SRS-RNTI and a second TPC-SRS-RNTI, wherein the plurality of uplink component carriers include a first component carrier and a second component carrier, wherein the first component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, and wherein the second component carrier is configured with a first SRS closed-loop power control adjustment state (block 910). For example, a network node (e.g., using...) Figure 12 The transmitting component 1204 and / or communication manager 1206 depicted herein may transmit to the UE an uplink power control configuration for a plurality of uplink component carriers, wherein the uplink power control configuration indicates a first TPC-SRS-RNTI and a second TPC-SRS-RNTI, wherein the plurality of uplink component carriers include a first component carrier and a second component carrier, wherein the first component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, and wherein the second component carrier is configured with a first SRS closed-loop power control adjustment state, as described above.

[0192] like Figure 9Further shown, in some aspects, process 900 may include sending a DCI to the UE indicating a TPC command for a second component carrier, wherein the DCI is scrambled by a first TPC-SRS-RNTI or a second TPC-SRS-RNTI (box 920). For example, a network node (e.g., using...) Figure 12 The transmitting component 1204 and / or the communication manager 1206 depicted herein may transmit to the UE a DCI indicating a TPC command for a second component carrier, wherein the DCI is scrambled by a first TPC-SRS-RNTI or a second TPC-SRS-RNTI, as described above.

[0193] like Figure 9 Further, as shown, in some aspects, process 900 may include receiving SRS from the UE based at least in part on a TPC command being applied to a first SRS closed-loop power control adjustment state corresponding to the second component carrier (block 930). For example, a network node (e.g., using...) Figure 12 The receiving component 1202 and / or communication manager 1206 described above can receive SRS from the UE at least in part based on a TPC command applied to a first SRS closed-loop power control adjustment state corresponding to the second component carrier, as described above.

[0194] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere in this document.

[0195] In the first aspect, DCI includes DCI format 2_3 messages.

[0196] In a second aspect, either alone or in combination with the first aspect, the first SRS closed-loop power control adjustment state is associated with a first closed-loop power control adjustment state index, and the second SRS closed-loop power control adjustment state is associated with a second closed-loop power control adjustment state index.

[0197] In a third aspect, either alone or in combination with one or more of the first and second aspects, the DCI comprises a plurality of blocks of the first type, and each of the plurality of blocks indicates a TPC command for a corresponding uplink component carrier among the plurality of uplink component carriers.

[0198] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the DCI includes a single block of the second type indicating multiple TPC commands for multiple component carriers, wherein each TPC command corresponds to a corresponding component carrier among the multiple component carriers.

[0199] although Figure 9An example box of process 900 is shown, but in some respects, process 900 may include... Figure 9 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the process 900 may be executed in parallel.

[0200] Figure 10 This is a diagram illustrating an example process 1000 performed, for example, at a network node or a device within a network node, according to the present disclosure. Example process 1000 is an example in which a device or network node (e.g., network node 110) performs an operation associated with dci format 2_3, which indicates a TPC command associated with a different SRS closed-loop power control adjustment state.

[0201] like Figure 10 As shown, in some aspects, process 1000 may include sending a configuration to the UE for an uplink component carrier, wherein the uplink component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, wherein the configuration indicates a first start position in DCI format 2_3 associated with the first closed-loop power control adjustment state and a second start position in DCI format 2_3 associated with the second closed-loop power control adjustment state, and wherein DCI format 2_3 associated with the first closed-loop power control adjustment state indicates a TPC command for the first SRS closed-loop power control adjustment state, and DCI format 2_3 associated with the second closed-loop power control adjustment state indicates a TPC command for the second SRS closed-loop power control adjustment state (block 1010). For example, a network node (e.g., using...) Figure 12 The transmitting component 1204 and / or communication manager 1206 depicted herein can transmit configuration to the UE for an uplink component carrier, wherein the uplink component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, wherein the configuration indicates a first start position in DCI format 2_3 associated with the first closed-loop power control adjustment state and a second start position in DCI format 2_3 associated with the second closed-loop power control adjustment state, and wherein DCI format 2_3 associated with the first closed-loop power control adjustment state indicates a TPC command for the first SRS closed-loop power control adjustment state, and DCI format 2_3 associated with the second closed-loop power control adjustment state indicates a TPC command for the second SRS closed-loop power control adjustment state, as described above.

[0202] like Figure 10Further shown, in some aspects, process 1000 may include sending the UE DCI format 2_3 (box 1020) with a CRC scrambled by TPC-SRS-RNTI. For example, a network node (e.g., using...) Figure 12 The transmitting component 1204 and / or the communication manager 1206 depicted herein can transmit to the UE a DCI format 2_3 with cyclic redundancy check (CRC) scrambled by TPC-SRS-RNTI, as described above.

[0203] like Figure 10 Further, in some aspects, process 1000 may include receiving SRS from the UE based at least in part on: a TPC command in DCI format 2_3 based on a first starting position or a TPC command in DCI format 2_3 based on a second starting position corresponding to an uplink component carrier (box 1030). For example, a network node (e.g., using...) Figure 12 The receiving component 1202 and / or communication manager 1206 described herein may receive SRS from the UE based at least in part on the following: a TPC command in DCI format 2_3 based on a first starting position or a TPC command in DCI format 2_3 based on a second starting position corresponding to an uplink component carrier, as described above.

[0204] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere in this document.

[0205] although Figure 10 An example box of process 1000 is shown, but in some aspects, process 1000 may include... Figure 10 The boxes depicted in the diagram are compared to additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in the process 1000 may be executed in parallel.

[0206] Figure 11 This is a diagram of an example device 1100 for wireless communication according to the present disclosure. Device 1100 may be a UE, or a UE may include device 1100. In some aspects, device 1100 includes a receiving component 1102, a transmitting component 1104, and / or a communication manager 1106 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, the communication manager 1106 is combined with... Figure 1 The described communication manager 140. As shown, device 1100 can communicate with another device 1108 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 1102 and transmitting component 1104.

[0207] In some respects, device 1100 can be configured to perform the functions described herein. Figure 4A , Figure 4B , Figure 5A , Figure 5B and Figure 6 The described one or more operations. Additionally or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as Figure 7 Process 700 Figure 8 The process 800 or a combination thereof. In some respects, Figure 11 The illustrated device 1100 and / or one or more components may include a combination Figure 2 One or more components of the described UE. Additionally or alternatively, Figure 11 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0208] Receiver 1102 may receive communications from device 1108, such as reference signals, control information, data communications, or combinations thereof. Receiver 1102 may provide the received communications to one or more other components of device 1100. In some aspects, receiver 1102 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications, and may provide the processed signals to the one or more other components of device 1100. In some aspects, receiver 1102 may include combinations of... Figure 2 The described UE includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof.

[0209] Transmitting component 1104 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1108. In some aspects, one or more other components of device 1100 may generate communications and provide the generated communications to transmitting component 1104 for transmission to device 1108. In some aspects, transmitting component 1104 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1108. In some aspects, transmitting component 1104 may include combinations of... Figure 2 The described UE may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 1104 may co-located with the receive component 1102 in one or more transceivers.

[0210] The communication manager 1106 may support the operation of the receiving component 1102 and / or the transmitting component 1104. For example, the communication manager 1106 may receive information associated with configuring the reception of communications by the receiving component 1102 and / or the transmission of communications by the transmitting component 1104. Additionally or alternatively, the communication manager 1106 may generate control information and / or provide control information to the receiving component 1102 and / or the transmitting component 1104 to control the reception and / or transmission of communications.

[0211] The receiving component 1102 can receive from a network node an uplink power control configuration for a plurality of uplink component carriers, wherein the uplink power control configuration indicates a first TPC-SRS-RNTI and a second TPC-SRS-RNTI, wherein the plurality of uplink component carriers includes a first component carrier and a second component carrier, wherein the first component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, and wherein the second component carrier is configured with a first SRS closed-loop power control adjustment state. The receiving component 1102 can receive from the network node a DCI indicating a TPC command for the second component carrier, wherein the DCI is scrambled by either the first TPC-SRS-RNTI or the second TPC-SRS-RNTI. The transmitting component 1104 can transmit SRS to the network node at least in part based on applying a TPC command to the first SRS closed-loop power control adjustment state corresponding to the second component carrier.

[0212] The communication manager 1106 can apply TPC commands to a first SRS closed-loop power control adjustment state corresponding to the second component carrier, at least in part, based on the second component carrier being configured with a single SRS closed-loop power control adjustment state.

[0213] The receiving component 1102 can receive from the network node a configuration for an uplink component carrier, wherein the uplink component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state. The configuration indicates a first start position in DCI format 2_3 associated with the first closed-loop power control adjustment state and a second start position in DCI format 2_3 associated with the second closed-loop power control adjustment state. The DCI format 2_3 associated with the first closed-loop power control adjustment state indicates a TPC command for the first SRS closed-loop power control adjustment state, and the DCI format 2_3 associated with the second closed-loop power control adjustment state indicates a TPC command for the second SRS closed-loop power control adjustment state. The receiving component 1102 can receive from the network node DCI format 2_3 with a CRC scrambled by TPC-SRS-RNTI. The transmitting component 1104 transmits SRS to the network node based at least in part on the following: a TPC command in DCI format 2_3 based on a first starting position or a TPC command in DCI format 2_3 based on a second starting position corresponding to an uplink component carrier.

[0214] Figure 11 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 11 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 11 The two or more components shown can be implemented within a single component, or Figure 11 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 11 The executable description of the collection of (one or more) components shown is composed of Figure 11 Another set of components shown performs one or more functions.

[0215] Figure 12 This is a diagram of an example device 1200 for wireless communication according to the present disclosure. Device 1200 may be a network node, or a network node may include device 1200. In some aspects, device 1200 includes a receiving component 1202, a transmitting component 1204, and / or a communication manager 1206 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1206 is combined with... Figure 1 The described communication manager 150. As shown, device 1200 can communicate with another device 1208 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 1202 and transmitting component 1204.

[0216] In some respects, device 1200 can be configured to perform the functions described herein. Figure 4A , Figure 4B , Figure 5A , Figure 5B and Figure 6 One or more operations described herein. Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as Figure 9 The process 900 Figure 10 The process 1000 or a combination thereof. In some respects, Figure 12 The illustrated device 1200 and / or one or more components may include a combination Figure 2 One or more components of the described network node. Additionally or alternatively, Figure 12 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0217] Receiver 1202 may receive communications from device 1208, such as reference signals, control information, data communications, or combinations thereof. Receiver 1202 may provide the received communications to one or more other components of device 1200. In some aspects, receiver 1202 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications, and may provide the processed signals to the one or more other components of device 1200. In some aspects, receiver 1202 may include combinations of... Figure 2 The described network node may include one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, receiver component 1202 and / or transmitter component 1204 may include or be included in a network interface. The network interface may be configured to acquire and / or output signals for device 1200 via one or more communication links, such as backhaul links, midhaul links, and / or fronthaul links.

[0218] Transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1208. In some aspects, one or more other components of device 1200 may generate communications and provide the generated communications to transmitting component 1204 for transmission to device 1208. In some aspects, transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1208. In some aspects, transmitting component 1204 may include combinations of... Figure 2 The described network node includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 1204 may co-located with the receive component 1202 in one or more transceivers.

[0219] The communication manager 1206 may support the operation of the receiving component 1202 and / or the transmitting component 1204. For example, the communication manager 1206 may receive information associated with configuring the reception of communications by the receiving component 1202 and / or the transmission of communications by the transmitting component 1204. Additionally or alternatively, the communication manager 1206 may generate control information and / or provide control information to the receiving component 1202 and / or the transmitting component 1204 to control the reception and / or transmission of communications.

[0220] Transmitting component 1204 can transmit to the UE an uplink power control configuration for a plurality of uplink component carriers, wherein the uplink power control configuration indicates a first TPC-SRS-RNTI and a second TPC-SRS-RNTI, wherein the plurality of uplink component carriers include a first component carrier and a second component carrier, wherein the first component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, and wherein the second component carrier is configured with a first SRS closed-loop power control adjustment state. Transmitting component 1204 can transmit to the UE a DCI indicating a TPC command for the second component carrier, wherein the DCI is scrambled by the first TPC-SRS-RNTI or the second TPC-SRS-RNTI. Receiving component 1202 can receive SRS from the UE at least in part based on the TPC command being applied to the first SRS closed-loop power control adjustment state corresponding to the second component carrier.

[0221] The transmitting component 1204 can transmit to the UE a configuration for an uplink component carrier, wherein the uplink component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state. The configuration indicates a first start position in DCI format 2_3 associated with the first closed-loop power control adjustment state and a second start position in DCI format 2_3 associated with the second closed-loop power control adjustment state. The DCI format 2_3 associated with the first closed-loop power control adjustment state indicates a TPC command for the first SRS closed-loop power control adjustment state, and the DCI format 2_3 associated with the second closed-loop power control adjustment state indicates a TPC command for the second SRS closed-loop power control adjustment state. The transmitting component 1204 can also transmit to the UE DCI format 2_3 with a CRC scrambled by TPC-SRS-RNTI. The receiving component 1202 may receive SRS from the UE based at least in part on either a TPC command in DCI format 2_3 based on a first starting position or a TPC command in DCI format 2_3 based on a second starting position corresponding to an uplink component carrier.

[0222] Figure 12 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 12 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 12 The two or more components shown can be implemented within a single component, or Figure 12 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 12 The executable description of the collection of (one or more) components shown is composed of Figure 12 Another set of components shown performs one or more functions.

[0223] The following provides an overview of some aspects of this disclosure.

[0224] Aspect 1: A method for wireless communication performed by a UE, the method comprising: receiving from a network node an uplink power control configuration for a plurality of uplink component carriers, wherein the uplink power control configuration indicates a first TPC-SRS-RNTI and a second TPC-SRS-RNTI, wherein the plurality of uplink component carriers includes a first component carrier and a second component carrier, wherein the first component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, and wherein the second component carrier is configured with the first SRS closed-loop power control adjustment state; receiving from the network node a DCI indicating a TPC command for the second component carrier, wherein the DCI is scrambled by the first TPC-SRS-RNTI or the second TPC-SRS-RNTI; and transmitting an SRS to the network node at least in part based on applying the TPC command to the first SRS closed-loop power control adjustment state corresponding to the second component carrier.

[0225] Aspect 2: According to the method of aspect 1, the DCI includes DCI format 2_3 messages.

[0226] Aspect 3: The method according to any one of Aspects 1 to 2, the method further comprising: applying the TPC command to the first SRS closed-loop power control adjustment state corresponding to the second component carrier, at least in part based on the fact that the second component carrier is configured with a single SRS closed-loop power control adjustment state.

[0227] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the first SRS closed-loop power control adjustment state is associated with a first closed-loop power control adjustment state index, and the second SRS closed-loop power control adjustment state is associated with a second closed-loop power control adjustment state index.

[0228] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the DCI comprises a plurality of blocks of a first type, and wherein each of the plurality of blocks indicates a TPC command for a corresponding uplink component carrier among the plurality of uplink component carriers.

[0229] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the DCI includes a single block of a second type, the single block of the second type indicating a plurality of TPC commands for the plurality of component carriers, wherein each TPC command corresponds to a corresponding component carrier among the plurality of component carriers.

[0230] Aspect 7: A method of wireless communication performed by a UE, the method comprising: receiving from a network node a configuration for an uplink component carrier, wherein the uplink component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, wherein the configuration indicates a first start position in a DCI format 2_3 associated with the first closed-loop power control adjustment state and a second start position in a DCI format 2_3 associated with the second closed-loop power control adjustment state, and wherein the DCI format 2_3 associated with the first closed-loop power control adjustment state indicates a configuration for the first SRS closed-loop power control adjustment state. The DCI format 2_3 associated with the second closed-loop power control adjustment state indicates the TPC command for the second SRS closed-loop power control adjustment state; receiving the DCI format 2_3 with a CRC scrambled by TPC-SRS-RNTI from the network node; and sending SRS to the network node at least in part based on applying the following: the TPC command in the DCI format 2_3 based on the first start position or the TPC command in the DCI format 2_3 based on the second start position corresponding to the uplink component carrier.

[0231] Aspect 8: According to the method of aspect 7, wherein the TPC command in the DCI format 2_3 is determined based on the first start position, the first start position being at least partially based on the TPC-SRS-RNTI including a first TPC-SRS-RNTI, and wherein the TPC command in the DCI format 2_3 is determined based on the second start position, the second start position being at least partially based on the TPC-SRS-RNTI corresponding to a second TPC-SRS-RNTI.

[0232] Aspect 9: The method according to any one of Aspects 7 to 8, wherein the TPC command in the DCI format 2_3 is based on the first starting position, the first starting position being at least partially based on the detection of the DCI format 2_3 in the first monitoring cell, and wherein the TPC command in the DCI format 2_3 is based on the second starting position, the second starting position being at least partially based on the detection of the DCI format 2_3 in the second monitoring cell.

[0233] Aspect 10: The method according to any one of Aspects 7 to 9, wherein the configuration includes a first field indicating the first starting position and a second field indicating the second starting position.

[0234] Aspect 11: According to the method of aspect 10, the configuration includes SRS-TPC-CommandConfig, wherein the first field includes a first startingBitOfFormat2-3 field, and wherein the second field includes a second startingBitOfFormat2-3 field.

[0235] Aspect 12: The method according to any one of Aspects 7 to 11, wherein receiving the configuration for the uplink component carrier comprises: receiving a first configuration for the uplink component carrier, wherein the first configuration indicates the first starting position; and receiving a second configuration for the uplink component carrier, wherein the second configuration indicates the second starting position.

[0236] Aspect 13: The method according to any one of Aspects 7 to 12, wherein a first set of uplink component carriers is configured with the first SRS closed-loop power control adjustment state, and a second set of uplink component carriers is configured with the second SRS closed-loop power control adjustment state.

[0237] Aspect 14: According to the method of aspect 13, the configuration for the uplink component carrier includes a first SRS-TPC-PDCCH-Config entry corresponding to the first SRS closed-loop power control adjustment state and a second SRS-TPC-PDCCH-Config entry corresponding to the second SRS closed-loop power control adjustment state.

[0238] Aspect 15: The method according to any one of Aspects 7 to 14, wherein the configuration includes a first set of component carrier set indices corresponding to the first SRS closed-loop power control adjustment state and a second set of component carrier set indices corresponding to the second SRS closed-loop power control adjustment state.

[0239] Aspect 16: The method according to any one of Aspects 7 to 15, wherein the configuration includes a list of component carrier set indices corresponding to a plurality of component carrier sets, and wherein the list of component carrier set indices configures each of the plurality of component carrier sets with either the first SRS closed-loop power control adjustment state or the second SRS closed-loop power control adjustment state.

[0240] Aspect 17: The method according to any one of Aspects 7 to 16, wherein the configuration indications correspond to the first cc-SetIndex and the first cc-IndexInOneCC-Set of the first SRS closed-loop power control adjustment state and the second cc-SetIndex and the second cc-IndexInOneCC-Set of the second SRS closed-loop power control adjustment state.

[0241] Aspect 18: The method according to any one of Aspects 7 to 17, wherein the configuration includes indicating whether an SRS request field exists in the DCI format 2_3 associated with the first closed-loop power control adjustment state and the DCI format 2_3 associated with the second closed-loop power control adjustment state.

[0242] Aspect 19: The method according to aspect 18, wherein the field includes the fieldTypeFormat2-3 field.

[0243] Aspect 20: The method according to any one of Aspects 7 to 19, wherein the configuration includes indicating whether an SRS request field exists in the DCI format 2_3 associated with the first closed-loop power control adjustment state or in the DCI format 2_3 associated with the second closed-loop power control adjustment state.

[0244] Aspect 21: The method according to aspect 20, wherein the configuration includes indicating whether the SRS request field exists in the field of the DCI format 2_3 associated with the first closed-loop power control adjustment state, and wherein at least in part based on the configuration, the configuration includes indicating whether the SRS request field exists in the field of the DCI format 2_3 associated with the first closed-loop power control adjustment state, wherein the SRS request field does not exist in the DCI format 2_3 associated with the second closed-loop power control adjustment state.

[0245] Aspect 22: The method according to aspect 20, wherein the configuration includes indicating whether the SRS request field exists in the field of the DCI format 2_3 associated with the second closed-loop power control adjustment state, and wherein at least in part based on the configuration, the configuration includes indicating whether the SRS request field exists in the field of the DCI format 2_3 associated with the second closed-loop power control adjustment state, wherein the SRS request field does not exist in the DCI format 2_3 associated with the first closed-loop power control adjustment state.

[0246] Aspect 23: The method according to any one of Aspects 7 to 22, wherein the configuration includes the first field indicating whether the SRS request field exists in a first field of the DCI format 2_3 associated with the first closed-loop power control adjustment state and the second field indicating whether the SRS request field exists in the DCI format 2_3 associated with the second closed-loop power control adjustment state.

[0247] Aspect 24: According to the method of aspect 23, the configuration includes SRS-TPC-CommandConfig, wherein the first field includes a first fieldTypeFormat2-3 field, and wherein the second field includes a second fieldTypeFormat2-3 field.

[0248] Aspect 25: The method according to any one of Aspects 7 to 24, wherein receiving the configuration for the uplink component carrier comprises: receiving a first configuration, the first configuration including an indication of whether an SRS request field exists in a field of the DCI format 2_3 associated with the first closed-loop power control adjustment state; and receiving a second configuration, the second configuration including an indication of whether an SRS request field exists in a field of the DCI format 2_3 associated with the second closed-loop power control adjustment state.

[0249] Aspect 26: A method for wireless communication performed by a network node, the method comprising: sending an uplink power control configuration to a UE for a plurality of uplink component carriers, wherein the uplink power control configuration indicates a first TPC-SRS-RNTI and a second TPC-SRS-RNTI, wherein the plurality of uplink component carriers includes a first component carrier and a second component carrier, wherein the first component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, and wherein the second component carrier is configured with the first SRS closed-loop power control adjustment state; sending a DCI to the UE indicating a TPC command for the second component carrier, wherein the DCI is scrambled by the first TPC-SRS-RNTI or the second TPC-SRS-RNTI; and receiving SRS from the UE at least in part based on the TPC command being applied to the first SRS closed-loop power control adjustment state corresponding to the second component carrier.

[0250] Aspect 27: The method according to aspect 26, wherein the DCI includes DCI format 2_3 messages.

[0251] Aspect 28: The method according to any one of Aspects 26 to 27, wherein the first SRS closed-loop power control adjustment state is associated with a first closed-loop power control adjustment state index, and the second SRS closed-loop power control adjustment state is associated with a second closed-loop power control adjustment state index.

[0252] Aspect 29: The method according to any one of Aspects 26 to 28, wherein the DCI comprises a plurality of blocks of a first type, and wherein each of the plurality of blocks indicates a TPC command for a corresponding uplink component carrier among the plurality of uplink component carriers.

[0253] Aspect 30: The method according to any one of Aspects 26 to 29, wherein the DCI includes a single block of a second type, the single block of the second type indicating a plurality of TPC commands for the plurality of component carriers, wherein each TPC command corresponds to a corresponding component carrier among the plurality of component carriers.

[0254] Aspect 31: A method of wireless communication performed by a network node, the method comprising: transmitting to a UE a configuration for an uplink component carrier, wherein the uplink component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, wherein the configuration indicates a first start position in a DCI format 2_3 associated with the first closed-loop power control adjustment state and a second start position in a DCI format 2_3 associated with the second closed-loop power control adjustment state, and wherein the DCI format 2_3 associated with the first closed-loop power control adjustment state indicates for the first SRS closed-loop power control adjustment state. The system sends a TPC command for the SRS closed-loop power control adjustment state and the DCI format 2_3 associated with the second closed-loop power control adjustment state indicates a TPC command for the second SRS closed-loop power control adjustment state; sends the DCI format 2_3 with a CRC scrambled by TPC-SRS-RNTI to the UE; and receives SRS from the UE based at least in part on the TPC command in the DCI format 2_3 based on the first start position or the TPC command in the DCI format 2_3 based on the second start position corresponding to the uplink component carrier.

[0255] Aspect 32: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method according to one or more aspects of aspects 1 to 31.

[0256] Aspect 33: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the device to perform the method according to one or more aspects 1 to 31.

[0257] Aspect 34: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 31.

[0258] Aspect 35: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the methods described in accordance with one or more aspects 1 to 31.

[0259] Aspect 36: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to one or more aspects 1 to 31.

[0260] Aspect 37: A device for wireless communication, the device including a processing system comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more aspects 1 to 31.

[0261] Aspect 38: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the device to perform the method according to one or more aspects of aspects 1 to 31.

[0262] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit aspects to the precise forms disclosed. Modifications and variations can be made based on the foregoing disclosure, or from various aspects of practice.

[0263] As used herein, the term "component" is intended to be broadly interpreted as hardware or a combination of hardware and at least one of software or firmware. "Software" should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable programs, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. As used herein, a "processor" is implemented in hardware or a combination of hardware and software. It will be apparent that the systems or methods described herein may be implemented in various forms of hardware or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems or methods is not limited in any way. Therefore, the operation and behavior of these systems or methods are described herein without reference to specific software code, as those skilled in the art will understand that the software and hardware can be designed to implement these systems or methods, at least in part, based on the description herein. Unless otherwise stated, a component configured to perform a function means that the component has the capability to perform that function, but it is not necessary for the component to actually perform that function.

[0264] As used in this article, depending on the context, "meeting the threshold" can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0265] As used in this article, the phrase “at least one of” in a list of items refers to any combination of these items, including a single member. As an example, “at least one of the following: a, b, or c” is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination with multiple of the same element (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c).

[0266] No element, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are interchangeable with “one or more.” Furthermore, as used herein, the article “the” is intended to include one or more items mentioned in connection with the article “the” and is interchangeable with “one or more.” Furthermore, as used herein, the terms “group” and “cluster” are intended to include one or more entries and are interchangeable with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Furthermore, as used herein, the terms “having” and similar terms are intended as open-ended terms that do not limit the elements they modify (e.g., “having” A may also have B). Furthermore, the phrase “based on” is intended to mean “based on or otherwise related to” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be inclusive when used consecutively and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “either of the two” or “only one of them”). It should be understood that “one or more” is equivalent to “at least one”.

[0267] Although specific combinations of features are set forth in the claims or disclosed in the description, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically stated in the claims or disclosed in the description. The disclosure of various aspects includes each dependent claim in combination with each other claim in the claim set.

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories, said one or more processors being configured to cause the UE to: Receive uplink power control configurations for multiple uplink component carriers from a network node, wherein the uplink power control configurations indicate a first transmit power control (TPC) sounding reference signal (SRS) radio network temporary identifier (RNTI) and a second TPC-SRS-RNTI, wherein the multiple uplink component carriers include a first component carrier and a second component carrier, wherein the first component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, and wherein the second component carrier is configured with the first SRS closed-loop power control adjustment state. Receive downlink control information (DCI) from the network node indicating a TPC command for the second component carrier, wherein the DCI is scrambled by the first TPC-SRS-RNTI or the second TPC-SRS-RNTI; as well as The SRS is sent to the network node at least in part based on applying the TPC command to the first SRS closed-loop power control adjustment state corresponding to the second component carrier.

2. The UE according to claim 1, wherein the DCI includes DCI format 2-3 messages.

3. The UE of claim 1, wherein the one or more processors are further configured to cause the UE to: The TPC command is applied to the first SRS closed-loop power control adjustment state corresponding to the second component carrier, at least in part, based on the fact that the second component carrier is configured with a single SRS closed-loop power control adjustment state.

4. The UE according to claim 1, wherein the first SRS closed-loop power control adjustment state is associated with a first closed-loop power control adjustment state index, and the second SRS closed-loop power control adjustment state is associated with a second closed-loop power control adjustment state index.

5. The UE of claim 1, wherein the DCI comprises a plurality of blocks of a first type, and wherein each of the plurality of blocks indicates a TPC command for a corresponding uplink component carrier among the plurality of uplink component carriers.

6. The UE of claim 1, wherein the DCI comprises a single block of a second type, the single block of the second type indicating a plurality of TPC commands for the plurality of uplink component carriers, wherein each TPC command corresponds to a corresponding component carrier among the plurality of uplink component carriers.

7. A UE for wireless communication, the UE comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories, said one or more processors being configured to cause the UE to: Receive configuration for an uplink component carrier from a network node, wherein the uplink component carrier is configured with a first sounding reference signal (SRS) closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, wherein the configuration indicates a first start position in a downlink control information (DCI) format 2_3 associated with the first closed-loop power control adjustment state and a second start position in a DCI format 2_3 associated with the second closed-loop power control adjustment state, and wherein the DCI format 2_3 associated with the first closed-loop power control adjustment state indicates a transmit power control (TPC) command for the first SRS closed-loop power control adjustment state, and the DCI format 2_3 associated with the second closed-loop power control adjustment state indicates a TPC command for the second SRS closed-loop power control adjustment state; Receive the DCI format 2_3 from the network node, which has a cyclic redundancy check (CRC) scrambled by the TPC-SRS-Radio Network Temporary Identifier (RNTI). as well as The SRS is sent to the network node based at least in part on either the TPC command in DCI format 2_3 based on the first starting position or the TPC command in DCI format 2_3 based on the second starting position corresponding to the uplink component carrier.

8. The UE of claim 7, wherein the TPC command in the DCI format 2_3 is determined based on the first start position, the first start position being at least partially based on the TPC-SRS-RNTI including a first TPC-SRS-RNTI, and wherein the TPC command in the DCI format 2_3 is determined based on the second start position, the second start position being at least partially based on the TPC-SRS-RNTI corresponding to a second TPC-SRS-RNTI.

9. The UE of claim 7, wherein the TPC command in the DCI format 2_3 is based on the first starting position, the first starting position being at least partially based on the detection of the DCI format 2_3 in the first monitoring cell, and wherein the TPC command in the DCI format 2_3 is based on the second starting position, the second starting position being at least partially based on the detection of the DCI format 2_3 in the second monitoring cell.

10. The UE of claim 7, wherein the configuration includes a first field indicating the first starting position and a second field indicating the second starting position.

11. The UE of claim 10, wherein the configuration includes SRS-TPC-CommandConfig, wherein the first field includes a first startingBitOfFormat2-3 field, and wherein the second field includes a second startingBitOfFormat2-3 field.

12. The UE of claim 7, wherein, in order for the UE to receive the configuration for the uplink component carrier, the one or more processors are configured to cause the UE to: Receive a first configuration for the uplink component carrier, wherein the first configuration indicates the first start position; and Receive a second configuration for the uplink component carrier, wherein the second configuration indicates the second starting position.

13. The UE according to claim 7, wherein the first set of uplink component carriers is configured with the first SRS closed-loop power control adjustment state, and the second set of uplink component carriers is configured with the second SRS closed-loop power control adjustment state.

14. The UE of claim 13, wherein the configuration for the uplink component carrier includes a first SRS-TPC-Physical Downlink Control Channel (PDCCH)-Config entry corresponding to the first SRS closed-loop power control adjustment state and a second SRS-TPC-PDCCH-Config entry corresponding to the second SRS closed-loop power control adjustment state.

15. The UE according to claim 7, wherein the configuration includes a first set of component carrier set indices corresponding to the first SRS closed-loop power control adjustment state and a second set of component carrier set indices corresponding to the second SRS closed-loop power control adjustment state.

16. The UE of claim 7, wherein the configuration includes a list of component carrier set indices corresponding to a plurality of component carrier sets, and wherein the list of component carrier set indices configures each of the plurality of component carrier sets with either the first SRS closed-loop power control adjustment state or the second SRS closed-loop power control adjustment state.

17. The UE of claim 7, wherein the configuration indications correspond to the first cc-SetIndex and the first cc-IndexInOneCC-Set of the first SRS closed-loop power control adjustment state and the second cc-SetIndex and the second cc-IndexInOneCC-Set of the second SRS closed-loop power control adjustment state.

18. The UE of claim 7, wherein the configuration includes an indication of whether an SRS request field exists in the DCI format 2_3 associated with the first closed-loop power control adjustment state and the DCI format 2_3 associated with the second closed-loop power control adjustment state.

19. The UE according to claim 18, wherein the field includes the fieldTypeFormat2-3 field.

20. The UE of claim 7, wherein the configuration includes an indication of whether an SRS request field exists in the DCI format 2_3 associated with the first closed-loop power control adjustment state or in the DCI format 2_3 associated with the second closed-loop power control adjustment state.

21. The UE of claim 20, wherein the configuration includes indicating whether the SRS request field exists in the field of the DCI format 2_3 associated with the first closed-loop power control adjustment state, and wherein the configuration includes at least in part indicating whether the SRS request field exists in the field of the DCI format 2_3 associated with the first closed-loop power control adjustment state, wherein the SRS request field does not exist in the DCI format 2_3 associated with the second closed-loop power control adjustment state.

22. The UE of claim 20, wherein the configuration includes indicating whether the SRS request field exists in the field of the DCI format 2_3 associated with the second closed-loop power control adjustment state, and wherein the configuration includes at least in part indicating whether the SRS request field exists in the field of the DCI format 2_3 associated with the second closed-loop power control adjustment state, wherein the SRS request field does not exist in the DCI format 2_3 associated with the first closed-loop power control adjustment state.

23. The UE of claim 7, wherein the configuration includes the first field indicating whether the SRS request field exists in a first field of the DCI format 2_3 associated with the first closed-loop power control adjustment state and the second field indicating whether the SRS request field exists in the DCI format 2_3 associated with the second closed-loop power control adjustment state.

24. The UE of claim 23, wherein the configuration includes SRS-TPC-CommandConfig, wherein the first field includes a first fieldTypeFormat2-3 field, and wherein the second field includes a second fieldTypeFormat2-3 field.

25. The UE of claim 7, wherein, in order for the UE to receive the configuration for the uplink component carrier, the one or more processors are configured to cause the UE to: Receive a first configuration, the first configuration including an indication of whether the SRS request field exists in the field of DCI format 2_3 associated with the first closed-loop power control adjustment state, and Receive a second configuration, the second configuration including an indication of whether the SRS request field exists in the field of the DCI format 2_3 associated with the second closed-loop power control adjustment state.

26. A network node for wireless communication, the network node comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories, said one or more processors being configured to cause the network node to: Sending uplink power control configurations for multiple uplink component carriers to User Equipment (UE), wherein the uplink power control configurations indicate a first Transmit Power Control (TPC) Sounding Reference Signal (SRS) Radio Network Temporary Identifier (RNTI) and a second TPC-SRS-RNTI, wherein the multiple uplink component carriers include a first component carrier and a second component carrier, wherein the first component carrier is configured with a first SRS closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, and wherein the second component carrier is configured with the second SRS closed-loop power control adjustment state. Send downlink control information (DCI) to the UE indicating a TPC command for the second component carrier, wherein the DCI is scrambled by the first TPC-SRS-RNTI or the second TPC-SRS-RNTI; as well as The SRS is received from the UE at least in part based on the TPC command being applied to the second SRS closed-loop power control adjustment state corresponding to the second component carrier.

27. The network node of claim 26, wherein the first SRS closed-loop power control adjustment state is associated with a first closed-loop power control adjustment state index, and the second SRS closed-loop power control adjustment state is associated with a second closed-loop power control adjustment state index.

28. The network node of claim 26, wherein the DCI comprises a plurality of blocks of a first type, and wherein each of the plurality of blocks indicates a TPC command for a corresponding uplink component carrier among the plurality of uplink component carriers.

29. The network node of claim 26, wherein the DCI comprises a single block of a second type, the single block of the second type indicating a plurality of TPC commands for the plurality of uplink component carriers, wherein each TPC command corresponds to a corresponding component carrier among the plurality of uplink component carriers.

30. A network node for wireless communication, the network node comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories, said one or more processors being configured to cause the network node to: A configuration for an uplink component carrier is sent to a User Equipment (UE), wherein the uplink component carrier is configured with a first Sounding Reference Signal (SRS) closed-loop power control adjustment state and a second SRS closed-loop power control adjustment state, wherein the configuration indicates a first start position in a downlink control information (DCI) format 2_3 associated with the first closed-loop power control adjustment state and a second start position in a DCI format 2_3 associated with the second closed-loop power control adjustment state, and wherein the DCI format 2_3 associated with the first closed-loop power control adjustment state indicates a transmit power control (TPC) command for the first SRS closed-loop power control adjustment state, and the DCI format 2_3 associated with the second closed-loop power control adjustment state indicates a TPC command for the second SRS closed-loop power control adjustment state; Send the DCI format 2_3 to the UE with cyclic redundancy check (CRC) scrambled by TPC-SRS-Radio Network Temporary Identifier (RNTI); as well as The SRS is received from the UE at least in part based on either the TPC command in the DCI format 2_3 based on the first starting position or the TPC command in the DCI format 2_3 based on the second starting position corresponding to the uplink component carrier.

Images