Closed loop power control for sounding reference signals

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive a configuration for closed loop power control. The UE may transmit a sounding reference signal (SRS) using a value of a physical uplink shared channel power control adjustment state that is the same as or different from a value of a physical uplink shared channel power control adjustment state based at least in part on the configuration comprising a closed loop indication or the configuration being a radio resource control configuration. Numerous other aspects are described.

Description

Technical Field

[0001] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for closed-loop power control of sounding reference signals. Background Art

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies 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, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0003] A wireless network may include one or more network nodes that support communications for wireless communication devices, such as user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network node to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communications, such as via a local link (e.g., a side link (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, etc.).

[0004] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by: improving spectrum efficiency; reducing costs; improving services; utilizing new spectrum; and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards; and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0005] Some aspects described herein relate to a method of performing wireless communications by a user equipment (UE). The method may include receiving a configuration for closed-loop power control. The method may include transmitting a sounding reference signal (SRS) power control adjustment state using a value that is the same as or different from a value of a physical uplink shared channel (PUSCH) power control adjustment state based at least in part on the configuration including a closed-loop indication or the configuration being a radio resource control (RRC) configuration.

[0006] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include sending a configuration for closed-loop power control. The method may include receiving an SRS using a value of an SRS power control adjustment state that is the same as or different from a value of a PUSCH power control adjustment state based at least in part on the configuration including a closed-loop indication or the configuration being an RRC configuration.

[0007] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a configuration for closed-loop power control. The one or more processors may be configured to send an SRS using a value of an SRS power control adjustment state that is the same as or different from a value of a PUSCH power control adjustment state based at least in part on the configuration including a closed-loop indication or the configuration being an RRC configuration.

[0008] Some aspects described herein relate to a network entity for wireless communication. The network entity may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send a configuration for closed-loop power control. The one or more processors may be configured to receive an SRS using a value of an SRS power control adjustment state that is the same as or different from a value of a PUSCH power control adjustment state based at least in part on the configuration including a closed-loop indication or the configuration being an RRC configuration.

[0009] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive a configuration for closed-loop power control. The instruction set, when executed by one or more processors of the UE, may cause the UE to send an SRS using a value of an SRS power control adjustment state that is the same as or different from a value of a PUSCH power control adjustment state, based at least in part on the configuration including a closed-loop indication or the configuration being an RRC configuration.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network entity. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to send a configuration for closed-loop power control. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to receive an SRS using a value of an SRS power control adjustment state that is the same as or different from a value of a PUSCH power control adjustment state based at least in part on the configuration including a closed-loop indication or the configuration being an RRC configuration.

[0011] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a configuration for closed-loop power control. The apparatus may include means for transmitting an SRS using a value of an SRS power control adjustment state that is the same as or different from a value of a PUSCH power control adjustment state based at least in part on the configuration including a closed-loop indication or the configuration being an RRC configuration.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending a configuration for closed-loop power control. The apparatus may include means for receiving an SRS using a value of an SRS power control adjustment state that is the same as or different from a value of a PUSCH power control adjustment state based at least in part on the configuration including a closed-loop indication or the configuration being an RRC configuration.

[0013] Aspects collectively include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the drawings and description and as illustrated in the drawings and description.

[0014] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.

[0015] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to be able to understand the above-mentioned features of the present disclosure in detail, a more specific description briefly summarized above may be obtained by reference to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings illustrate only certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

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

[0018] Figure 2 is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0019] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0020] Figure 4 is a diagram illustrating an example of a sounding reference signal (SRS) resource set according to the present disclosure.

[0021] Figure 5 is a diagram illustrating an example associated with closed-loop power control for SRS according to the present disclosure.

[0022] Figure 6 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0023] Figure 7 is a diagram illustrating an example process performed, for example, by a network entity according to the present disclosure.

[0024] Figure 8 is a diagram of an example apparatus for wireless communications according to the present disclosure.

[0025] Fig. 9 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0026] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method that is practiced using other structures, functionality, or structure and functionality other than the various aspects of the disclosure set forth herein or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present claim.

[0027] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0028] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT and / or RATs beyond 5G (e.g., 6G).

[0029] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, as well as other examples. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), which means that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0030] In some examples, the network node 110 is or includes a network node that communicates with the UE 120 via a radio access link, such as an RU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or communicates with the core network via a backhaul link, such as a CU. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. The network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul, midhaul, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks) using any suitable transport network.

[0031] In some examples, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​the network node 110 and / or the network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1 In the example shown in , network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

[0032] In some aspects, the term "base station", "network entity" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station", "network entity" or "network node" may refer to a CU, a DU, a RU, a near real-time (near RT) RAN intelligent controller (RIC) or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station", "network entity" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with the network node 110). In some aspects, the term "base station", "network entity" or "network node" may refer to a plurality of devices configured to perform one or more functions. For example, in some distributed systems, each of a number of different devices (which may be located in the same geographical location or in different geographical locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station", "network entity" or "network node" may refer to any one or more of these different devices. In some aspects, the terms "base station," "network entity," or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the terms "base station," "network entity," or "network node" may refer to one of the base station functions but not another base station function. In this way, a single device may include more than one base station.

[0033] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown in , a network node 110d (e.g., a relay network node) may communicate with a network node 110a (e.g., a macro network node) and a UE 120d to facilitate communication between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, etc.

[0034] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0035] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless or wired backhaul communication link. In some aspects, the network controller 130 may be, or may include, a CU or a core network device.

[0036] UE 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smart phone), 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 smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and / or any other suitable device configured to communicate via a wireless or wired medium.

[0037] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0038] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0039] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary to communicate with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0040] The devices of the wireless network 100 may communicate using an electromagnetic spectrum that may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that, although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0041] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125 GHz–24.25 GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and thus the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz-71 GHz), FR4 (52.6 GHz-114.25 GHz), and FR5 (114.25 GHz-300 GHz). Each of these higher frequency bands falls within the EHF band.

[0042] Considering the above examples, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0043] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, communication manager 140 may receive a configuration for closed-loop power control. Communication manager 140 may transmit an SRS using a value of a sounding reference signal (SRS) power control adjustment state that is the same as or different from a value of a physical uplink shared channel (PUSCH) power control adjustment state based at least in part on the configuration including a closed-loop indication or the configuration being a radio resource control (RRC) configuration. Additionally or alternatively, communication manager 140 may perform one or more other operations described herein.

[0044] In some aspects, a network entity (e.g., network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may send a configuration for closed-loop power control. The communication manager 150 may receive the SRS using a value of an SRS power control adjustment state that is the same as or different from a value of a PUSCH power control adjustment state based at least in part on the configuration including a closed-loop indication or the configuration being an RRC configuration. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0045] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0046] Figure 2 2 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 254. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0047] At the network node 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQI) received from the UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0048] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0049] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0050] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0051] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to Figures 4 to 9 ) any aspects of any of the methods described herein.

[0052] At the network node 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component (shown as DEMOD) of the modem 232), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink communication and / or uplink communication. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., with reference to Figures 4 to 9 ) any aspects of any of the methods described herein.

[0053] As described in more detail elsewhere herein, a controller / processor of a network entity (e.g., controller / processor 240 of network node 110), controller / processor 280 of UE 120, and / or Figure 2 Any other component of the UE 120 may perform one or more techniques associated with closed-loop power control for SRS. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Figure 6 The process of 600 Figure 7 10 and / or operations of process 700 and / or other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly executed, or executed after compilation, conversion and / or interpretation), may cause one or more processors, UE 120 and / or network node 110 to perform or direct, for example, Figure 6 The process of 600 Figure 7 The process 700 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0054] In some aspects, a UE (e.g., UE 120) includes means for receiving a configuration for closed loop power control; and / or means for transmitting SRS using a value of an SRS power control adjustment state that is the same as or different from a value of a PUSCH power control adjustment state based at least in part on the configuration including a closed loop indication or the configuration being an RRC configuration. The means for the UE to perform operations described herein may include, for example, one or more of the following: a communications 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.

[0055] In some aspects, the network entity (e.g., network node 110) includes means for transmitting a configuration for closed loop power control; and / or means for receiving SRS using a value of an SRS power control adjustment state that is the same or different from a value of a PUSCH power control adjustment state based at least in part on the configuration including a closed loop indication or the configuration being an RRC configuration. In some aspects, means for the network entity to perform operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0056] Although Figure 2 The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0057] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0058] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) that perform base station functionality can be implemented as an aggregated base station (also referred to as an independent base station or a monolithic base station) or a decomposed base station. "Network entity" or "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0059] An aggregated base station (e.g., an aggregated network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), and the like.

[0060] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Individual units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0061] Figure 3 3 is a diagram illustrating an example disaggregated base station architecture 300 according to the present disclosure. The disaggregated base station architecture 300 may include a CU 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units, such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via an F1 interface. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0062] Each of the units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO framework 305 may include or be coupled to one or more interfaces, the one or more interfaces being configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of the units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, the wireless interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, or both.

[0063] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include RRC functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some specific implementations, the CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, the CU 310 may be implemented to communicate with the DU330 for network control and signaling.

[0064] 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 RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers, at least in part, according to a functional split (such as a functional split defined by 3GPP). In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may further host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0065] Each RU 340 may implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions based on functional split (e.g., functional split defined by 3GPP) (such as lower layer functional split), such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc. In this architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of control and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0066] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RTRIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0067] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or communicate with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0068] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0069] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0070] Figure 4 is a diagram illustrating an example 400 of an SRS resource set according to the present disclosure.

[0071] The UE 120 may be configured with one or more SRS resource sets to allocate resources for SRS transmission by the UE 120. For example, the configuration for the SRS resource set may be indicated in an RRC message (e.g., an RRC configuration message or an RRC reconfiguration message). As shown by reference numeral 405, the SRS resource set may include one or more resources (e.g., shown as SRS resources), which may include time resources and / or frequency resources (e.g., time slots, symbols, resource blocks, and / or periodicity of time resources).

[0072] As shown by reference numeral 410, the SRS resources may include one or more antenna ports on which the SRS is to be sent (e.g., in time-frequency resources). Thus, the configuration for an SRS resource set may indicate one or more time-frequency resources on which the SRS is to be sent, and may indicate antenna ports on which the SRS is to be sent in these time-frequency resources. In some aspects, the configuration for the SRS resource set may indicate a use case for the SRS resource set (e.g., in an SRS-SetUse information element). For example, the SRS resource set may have use cases for antenna switching, codebook, non-codebook, or beam management.

[0073] The antenna switching SRS resource set may be used to indicate downlink channel state information (CSI) with reciprocity between the uplink channel and the downlink channel. For example, when there is reciprocity between the uplink channel and the downlink channel, a network entity (e.g., network node 110) may use an antenna switching SRS (e.g., an SRS sent using resources in an antenna switching SRS resource set) to obtain downlink CSI (e.g., to determine a downlink precoder to be used for communication with UE 120).

[0074] The codebook SRS resource set may be used to indicate uplink CSI when the network node 110 indicates an uplink precoder to the UE 120. For example, when the network node 110 is configured to indicate an uplink precoder to the UE 120 (e.g., using a precoder codebook), the network node 110 may use the codebook SRS (e.g., an SRS sent using resources in the codebook SRS resource set) to obtain uplink CSI (e.g., to determine an uplink precoder to be indicated to the UE 120 and to be used by the UE 120 to communicate with the network node 110). In some aspects, at least for the codebook SRS, a virtual port (e.g., a combination of two or more antenna ports) with a maximum transmit power may be supported.

[0075] When UE 120 selects an uplink precoder to be used by UE 120 (e.g., instead of the uplink precoder indicated by network node 110), the non-codebook SRS resource set may be used to indicate uplink CSI. For example, when UE 120 is configured to select an uplink precoder, network node 110 may use a non-codebook SRS (e.g., an SRS sent using resources in a non-codebook SRS resource set) to obtain uplink CSI. In this case, the non-codebook SRS may be precoded using a precoder selected by UE 120 (e.g., the precoder may be indicated to network node 110).

[0076] The beam-managed SRS resource set may be used to indicate CSI for millimeter wave communications.

[0077] SRS resources may be configured as periodic, semi-persistent (sometimes referred to as semi-persistent scheduling (SPS), or aperiodic. Periodic SRS resources may be configured via a configuration message indicating the periodicity of the SRS resources (e.g., slot-level periodicity, where the SRS resources occur every Y slots) and the slot offset. In some cases, periodic SRS resources may always be activated and may not be dynamically activated or deactivated. Semi-persistent SRS resources may also be configured via a configuration message indicating the periodicity and slot offset for the semi-persistent SRS resources, and may be dynamically activated and deactivated (e.g., using downlink control information (DCI) or MAC control element (CE) (MAC-CE)). Aperiodic SRS resources may be dynamically triggered, such as via DCI (e.g., UE-specific DCI or group-common DCI) or MAC CE.

[0078] In some aspects, the UE 120 may be configured with a mapping between an SRS port (e.g., an antenna port) and a corresponding SRS resource. The UE 120 may use the SRS port indicated in the configuration to send an SRS on a specific SRS resource. In some aspects, the SRS resource may span N adjacent symbols within a time slot (e.g., where N is equal to 1, 2, or 4). The UE 120 may be configured with X SRS ports (e.g., where X≤4). In some aspects, each of the X SRS ports may be mapped to a corresponding symbol of the SRS resource and used to send the SRS in the symbol.

[0079] like Figure 4 As shown, in some aspects, different SRS resource sets (e.g., having different use cases) indicated to UE 120 may overlap (e.g., in time and / or frequency, such as in the same time slot). For example, as shown by reference numeral 415, a first SRS resource set (e.g., shown as SRS resource set 1) is shown as having an antenna switching use case. As shown, the example antenna switching SRS resource set includes a first SRS resource (shown as SRS resource A) and a second SRS resource (shown as SRS resource B). Therefore, antenna port 0 and antenna port 1 may be used to send antenna switching SRS in SRS resource A (e.g., a first time-frequency resource), and antenna port 2 and antenna port 3 may be used to send antenna switching SRS in SRS resource B (e.g., a second time-frequency resource).

[0080] As shown by reference numeral 420, a second SRS resource set (e.g., shown as SRS resource set 2) may be a codebook use case. As shown, the example codebook SRS resource set includes only the first SRS resource (shown as SRS resource A). Therefore, antenna port 0 and antenna port 1 may be used to send codebook SRS in SRS resource A (e.g., the first time-frequency resource). In this case, UE 120 may not use antenna port 2 and antenna port 3 to send codebook SRS in SRS resource B (e.g., the second time-frequency resource).

[0081] A closed-loop power control system may be used to control the transmit power of the SRS. In a closed-loop power control system, a transmit power control (TPC) command received via a MAC CE or DCI is used to dynamically control the UE power. The TPC may include a closed-loop index value for a power setting algorithm at the UE 120. In some examples, the UE 120 may support an SRS closed-loop power control value that is the same (shared) or different (separated) from the closed-loop power control value for PUSCH communication. That is, there may be one closed-loop index value (e.g., i0 or i1) for both the SRS and PUSCH, or there may be separate closed-loop index values ​​(e.g., i0 and i1) for the SRS and PUSCH.

[0082] If UE 120 transmits PUSCH communications on active uplink bandwidth part (BWP) b of carrier f of serving cell c using parameter set configuration indexed j and PUSCH power control adjustment state indexed l, UE 120 may set the PUSCH transmit power P in PUSCH transmission opportunity i to PUSCH,b,f,c (i,j,q d ,l) is determined as

[0083]

[0084] Where P CMAX,f,c (i) is the maximum output power configured by the UE for carrier f of serving cell c in PUSCH transmission opportunity i, P O_PUSCH,b,f,c (j) is composed of the component P O_NOMINAL,PUSCH,f,c (j) and the component P O_UE_PUSCH,b,f,C (j), where j∈{0,1,…,J-1}. PL may be the bandwidth of the PUSCH resource assignment expressed in number of resource blocks for PUSCH transmission opportunity i on active uplink BWPb of carrier f serving cell c, and μ may be the subcarrier spacing (SCS). b,f,c (q d ) may be the reference signal (RS) index q of the active downlink BWP used by the UE on carrier f of serving cell c. dThe calculated downlink path loss estimate in decibels (dB). s =1.25, And for K s =0,Δ TF,b,f,c (i) = 0, where K s It can be provided by deltaMCS for each uplink BWPb of each carrier f and serving cell c.

[0085] If UE 120 transmits SRS based on the configuration of the SRS-ResourceSet on the active uplink BWPb of carrier f of serving cell c using the SRS power control adjustment state indexed as l, UE 120 may set the SRS transmission power P in SRS transmission opportunity i to SRS,b,f,C (i,q s ,l) is determined as

[0086]

[0087] Where P CMAX,f,c (i) is the maximum output power configured by the UE for carrier f of serving cell c in SRS transmission opportunity i. O_SRS,b,f,c (q s ) can be represented by p0 as the active UL BWPb of carrier f of serving cell c and the SRS resource set q provided by SRS-ResourceSet and SRS-ResourceSetId s Provide. SRS,b,f,c (i) may be the SRS bandwidth expressed in terms of the number of resource blocks for SRS transmission opportunity i on the active uplink BWPb of carrier f serving cell c, and α SRS,b,f,c (q s ) can be represented by alpha as the active uplink BWPb and SRS resource set q of carrier f serving cell c s Provided. PL b,f,c (q d ) may be the RS resource index q of the active downlink BWP used by the UE in serving cell c d and SRS resource set q s The calculated downlink path loss estimate in dB.

[0088] For the active uplink BWPb of carrier f of serving cell c and the SRS power control adjustment state of SRS transmission opportunity i, the SRS power control adjustment state l can be h b,f,C (i,l)=f b,f,c(i, l), where if srs-PowerControlAdjustmentStates indicates the same power control adjustment state for SRS transmission and PUSCH transmission, then f b,f,c (i,l) is the current PUSCH power control adjustment state. If the UE is not configured for PUSCH transmission on the active uplink BWPb of carrier f serving cell c, or if srs-PowerControlAdjustmentStates indicates separate power control adjustment states between SRS transmission and PUSCH transmission, and if tpc-Accumulation is not provided, then the SRS power control adjustment state l can be where δ SRS,b,f,c The values ​​are given in the table, δ SRS,b,f,c (m) jointly decoded with other TPC commands in a physical downlink control channel (PDCCH) with DCI format 2_3, and The cardinality is C(S i )’s TPC command value set S i The sum of the TPC command values ​​in the UE's active UL BWPf of the carrier of the serving cell c in the SRS power control adjustment state before the SRS transmission opportunity i-i0 SRS (i-i0)-1 symbol and K before SRS transmission timing i SRS (i) symbols, where i0>0 is the K before the SRS transmission opportunity i-i0 SRS (i) symbols earlier than K before SRS transmission opportunity i SRS The smallest integer of (i-i0) symbols.

[0089] The closed loop index may be RRC configured for SRS in a unified transmission configuration indicator (TCI) state frame, where the TCI state may apply to multiple beams. The closed loop index may be received with the p0 and α parameters in, for example, P0AlphaSet-r17. In a unified TCI state frame involving PUSCH, the UE 120 may use a closed loop index with a value of i0 or i1. However, a UE configured to use a unified TCI state currently does not support a closed loop index for SRS having a value separate from the PUSCH closed loop index.

[0090] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 The examples described are different.

[0091] Figure 5 is a diagram illustrating an example 500 associated with closed-loop power control for SRS according to the present disclosure. Figure 5As shown, a network entity 510 (e.g., network node 110) and a UE 520 (e.g., UE 120) may communicate with each other via a wireless network (e.g., wireless network 100). UE 520 may be configured with an SRS power control adjustment state 532 for SRS transmission and a PUSCH power control adjustment state 534 for PUSCH transmission. The power control adjustment state may include a closed loop index value.

[0092] According to various aspects described herein, UE 520 may support SRS with the same or separate power control adjustment states as PUSCH in a unified TCI framework. For example, SRS power control adjustment state 532 may include a closed-loop index value that is the same as the closed-loop index value of PUSCH power control adjustment state 534. Example 500 shows that the shared value may be a closed-loop index value of l=0. In another example, SRS power control adjustment state 532 may include a closed-loop index value that is separate (different) from the closed-loop index value of PUSCH power control adjustment state 534. Example 500 shows a closed-loop index value l=0 for SRS power control adjustment state and a closed-loop index value l=1 for PUSCH.

[0093] As indicated by reference numeral 525, the network entity 510 may send a configuration for closed-loop power control. The configuration may include a closed-loop indication (e.g., a closed-loop index value). Alternatively, the configuration may be an RRC configuration with an explicit indication of using the same or separate power control adjustment states for SRS and PUSCH.

[0094] In some aspects, the UE 520 may reinterpret the closed loop indication (e.g., closedLoopIndex-r17) to indicate whether the SRS power control adjustment state 532 is the same as or different from the PUSCH power control adjustment state 534. In some aspects, if a closed loop indication is provided, the SRS power control adjustment state 532 may be the same as the PUSCH power control adjustment state 534. For example, if the closed loop indication is i0, the SRS power control adjustment state 532 may be a first index value (e.g., l=0) and the PUSCH power control adjustment state 534 may be a first index value (e.g., l=0). If the closed loop indication is i1, the SRS power control adjustment state 532 may be a second index value (e.g., l=1) and the PUSCH power control adjustment state 534 may be a second index value (e.g., l=1). If the power control adjustment state is not RRC configured for SRS (e.g., srs-PowerControlAdjustmentStates) or specified in the RRC configuration, the UE 520 may determine to use these values.

[0095] Otherwise, if no closed loop indication is provided, the SRS power control adjustment state 532 may be separate from the PUSCH power control adjustment state 534. For example, in the absence of a closed loop indication, the SRS power control adjustment state 532 may be a first index value (e.g., l=0) and the PUSCH power control adjustment state 534 may be a second index value (e.g., l=1), or the SRS power control adjustment state 532 may be a second index value (e.g., l=1) and the PUSCH power control adjustment state 534 may be a first index value (e.g., l=0). If the power control adjustment state is not RRC configured for SRS or specified in the RRC configuration, the UE 520 may determine to use these values.

[0096] For example, if the UE 520 is provided with TCIState in dl-OrJoint-TCIStateList or UL-TCIstate, and for the indicated TCIState or UL-TCIstate, if p0AlphaSetforSRS is provided, and if followUnifiedTCIstateSRS is provided for the SRS resource set, then P O_SRS,b,f,c (q s ), α SRS,b,f,c (q s ) and the value of the SRS power control adjustment state 1 may be provided by the p0AlphaSetforSRS associated with the indicated TCIState or UL-TCIState. If the parameter closedLoopIndex-r17 is provided, the SRS power control adjustment state 1 may be the PUSCH power control adjustment state 1; otherwise, if the parameter closedLoopIndex-r17 is not provided, the SRS power control adjustment state 1 may be a separate SRS power control adjustment state. Otherwise, if the UE 520 is provided with a TCIState in dl-OrJoint-TCIStateList or UL-TCIstate, and for the indicated TCIState or UL-TCIstate, if p0AlphaSetforSRS is provided, and if followUnifiedTCIstateSRS is not provided for the SRS resource set and for the SRS resources from the SRS resource set, P O_SRS,b,f,c (q s ), α SRS,b,f,c (q s) and the value of the SRS power control adjustment state l can be provided by the p0AlphaSetforSRS associated with the TCIState or UL-TCIState of the SRS resource with the lowest SRS-ResourceId in the SRS resource set, and is used to obtain the RS index q of the path loss estimate for SRS transmission d It may be provided by pathlossReferenceRS-Id-r17 in the TCIState or UL-TCIState of the SRS resource with the lowest SRS-ResourceId in the SRS resource set. If the parameter closedLoopIndex-r17 is provided, the SRS power control adjustment state l may be the PUSCH power control adjustment state l; otherwise, if the parameter closedLoopIndex-r17 is not provided, the SRS power control adjustment state l may be a separate SRS power control adjustment state.

[0097] In some aspects, the RRC configuration closedLoopIndex-r17 in P0AlphaSet-r17 of SRS may include one of three candidate values ​​(e.g., "i0", "i1", and "separate closed-loop"). When an explicit indication "separate-close-loop" is received in the closed-loop index indication, the UE 520 may determine to use a separate closed-loop index for SRS.

[0098] In some aspects, if the closed loop indication is provided by p0AlphaSetforSRS in the TCI state for SRS, the SRS power control adjustment state 532 can be the same as the PUSCH power control adjustment state 534. For example, if the closed loop indication is i0, the SRS power control adjustment state 532 can be a first index value (e.g., l=0) and the PUSCH power control adjustment state 534 can be a first index value (e.g., l=0). If the closed loop indication is i1, the SRS power control adjustment state 532 can be a second index value (e.g., l=1) and the PUSCH power control adjustment state 534 can be a second index value (e.g., l=1). In some other aspects, the TPC indication can be dedicated to SRS. For example, at least when the serving cell of the SRS is not configured with any PUCCH transmission and PUSCH transmission or the SRS resource set is configured for beam management purposes, a group common DCI such as in DCI format 2-3 can be used to indicate a transmit power command for an SRS without a separate closed loop index.

[0099] In some aspects, a parameter for a unified TCI state for SRS may be provided (e.g., followUnifiedTCIstateSRS). If so, if the parameter closedLoopIndex-r17 is provided in p0AlphaSetforSRS, the SRS power control adjustment state 532 may be the PUSCH power control adjustment state 534. Otherwise, if the parameter closedLoopIndex-r17 is not provided, the SRS power control adjustment state 532 may be the individual SRS power control adjustment state in p0AlphaSetforSRS.

[0100] Alternatively, in some aspects, the configuration may be an RRC configuration that explicitly configures the SRS power control adjustment state 532 and the PUSCH power control adjustment state 534 to the same or different values. For example, the UE 520 may support configuring the power control adjustment state in an SRS set (e.g., srs-PowerControlAdjustmentStates) or a power control parameter set (e.g., P0AlphaSet-r17) for a unified TCI framework (e.g., configured to use uplink TCI states for multiple beams, downlink TCI states for multiple beams, or joint TCI states for beams). If the RRC configuration indicates the use of the same value (e.g., the RRC parameter is configured as "sameAs-Fci1" to have the same closed-loop index value as the first closed-loop index value for PUSCH, or the RRC parameter does not exist or is released), the SRS power control adjustment state 532 may be the first index value (e.g., l=0) and the same as the PUSCH power control adjustment state 534 of the first index value (e.g., l=0). If the RRC configuration indicates to use the same value (e.g., the RRC parameter is configured as "sameAs-Fci2" to have the same closed loop index value as the second closed loop index value used for PUSCH "sameAs-Fci2"), the SRS power control adjustment state 532 can be the second index value (e.g., l=1) and the same as the PUSCH power control adjustment state 534 having the second index value (e.g., l=1). In some aspects, the RRC configuration can indicate a separate power control adjustment state (e.g., separateClosedLoop). The SRS power control adjustment state 532 can be separate from the PUSCH power control adjustment state 534.

[0101] In some aspects, if the SRS power control adjustment state is configured (e.g., in P0AlphaSet-r17), the configuration can be an RRC configuration. Otherwise, if the SRS power control adjustment state is not configured, the UE 520 can re-interpret the closed-loop indication instead of using the explicit indication in the RRC configuration.

[0102] As shown by reference numeral 530, UE 520 may transmit SRS based at least in part on SRS power control adjustment state 532. By supporting a power control adjustment state for SRS separate from a power control adjustment state for PUSCH, UE 520 may have better power control for SRS, and the power used for SRS may help with channel estimation based on SRS and may help reduce interference caused by SRS. Improved channel estimation and reduced interference save power, processing resources, and signaling resources.

[0103] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 The examples described are different.

[0104] Figure 6 6 is a diagram illustrating an example process 600 performed, for example, by a UE according to the present disclosure. Example process 600 is an example in which a UE (eg, UE 120, UE 520) performs operations associated with closed-loop power control for SRS.

[0105] like Figure 6 As shown, in some aspects, process 600 may include receiving a configuration for closed loop power control (block 610). For example, a UE (e.g., using Figure 8 The communication manager 808 and / or receiving component 802 depicted in FIG. 8 may receive a configuration for closed-loop power control, as described above.

[0106] like Figure 6 As further shown, in some aspects, process 600 may include transmitting the SRS using a value of an SRS power control adjustment state that is the same as or different from a value of a PUSCH power control adjustment state based at least in part on the configuration including a closed loop indication or the configuration being an RRC configuration (block 620). Figure 8 The communication manager 808 and / or the sending component 804 depicted in the figure may send the SRS using a value of an SRS power control adjustment state that is the same as or different from a value of a PUSCH power control adjustment state based at least in part on the configuration including a closed loop indication or the configuration being an RRC configuration, as described above.

[0107] Process 600 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 herein.

[0108] In a first aspect, based at least in part on the configuration comprising a closed loop indication, a value of an SRS power control adjustment state and a value of a PUSCH power control adjustment state are the same value.

[0109] In a second aspect, either alone or in combination with the first aspect, a value of the SRS power control adjustment state and a value of the PUSCH power control adjustment state both correspond to a first index value of the closed loop indication or to a second index value of the closed loop indication.

[0110] In a second aspect, alone or in combination with the first aspect, further at least in part based on the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state not being specified by the configuration, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are the same value.

[0111] In a third aspect, alone or in combination with one or more of the first and second aspects, based at least in part on the configuration not including a closed loop indication, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are different values.

[0112] In a fourth aspect, alone or in combination with one or more of the first to third aspects, further at least in part based on the fact that the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are not specified by the configuration, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are different values.

[0113] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the configuration is an RRC configuration indicating that a value of an SRS power control adjustment state and a value of a PUSCH power control adjustment state are the same value.

[0114] In the sixth aspect, alone or in combination with one or more of the first to fifth aspects, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state both correspond to the first index value of the closed-loop indication or to the second index value of the closed-loop indication.

[0115] In the seventh aspect, alone or in combination with one or more of the first to sixth aspects, further at least in part based on the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state being specified by the configuration, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state being the same value.

[0116] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the configuration is an RRC configuration indicating that a value of an SRS power control adjustment state and a value of a PUSCH power control adjustment state are different values.

[0117] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, further at least in part based on the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state being specified by the configuration, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state being different values.

[0118] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the closed loop indication is a closed loop index value.

[0119] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the SRS power control adjustment state is configured for use in a unified TCI framework.

[0120] although Figure 6 An example block diagram of process 600 is shown, but in some aspects, process 600 may include Figure 6 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 600 may be performed in parallel.

[0121] Figure 7 is a diagram illustrating an example process 700, performed, for example, by a network entity, according to the present disclosure. The example process 700 is an example in which a network entity (eg, network node 110, network entity 510) performs operations associated with closed-loop power control for SRS.

[0122] like Figure 7 As shown, in some aspects, process 700 may include sending a configuration for closed loop power control (block 710). For example, a network entity (e.g., using Fig. 9 The communication manager 908 and / or the transmitting component 904 depicted in FIG. 9 may transmit a configuration for closed-loop power control, as described above.

[0123] like Figure 7 As further shown, in some aspects, process 700 may include receiving the SRS using a value of an SRS power control adjustment state that is the same as or different from a value of a PUSCH power control adjustment state based at least in part on the configuration including a closed loop indication or the configuration being an RRC configuration (block 720). Fig. 9 The communication manager 908 and / or receiving component 902 depicted in the figure may receive the SRS using a value of an SRS power control adjustment state that is the same as or different from a value of a PUSCH power control adjustment state based at least in part on the configuration including a closed loop indication or the configuration being an RRC configuration, as described above.

[0124] 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 herein.

[0125] In a first aspect, based at least in part on the configuration comprising a closed loop indication, a value of an SRS power control adjustment state and a value of a PUSCH power control adjustment state are the same value.

[0126] In a second aspect, either alone or in combination with the first aspect, a value of the SRS power control adjustment state and a value of the PUSCH power control adjustment state both correspond to a first index value of the closed loop indication or to a second index value of the closed loop indication.

[0127] In the third aspect, alone or in combination with one or more of the first and second aspects, alone or in combination with the first aspect, further at least in part based on the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state being specified by the configuration, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state being the same value.

[0128] In a fourth aspect, alone or in combination with one or more of the first to third aspects, based at least in part on the configuration not including a closed loop indication, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are different values.

[0129] In the fifth aspect, alone or in combination with one or more of the first to fourth aspects, further at least in part based on the fact that the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are not specified by the configuration, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are different values.

[0130] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the configuration is an RRC configuration indicating that a value of an SRS power control adjustment state and a value of a PUSCH power control adjustment state are the same value.

[0131] In the seventh aspect, alone or in combination with one or more of the first to sixth aspects, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state both correspond to the first index value of the closed-loop indication or to the second index value of the closed-loop indication.

[0132] In the eighth aspect, alone or in combination with one or more of the first to seventh aspects, further at least in part based on the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state being specified by the configuration, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state being the same value.

[0133] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the configuration is an RRC configuration indicating that a value of an SRS power control adjustment state and a value of a PUSCH power control adjustment state are different values.

[0134] In the tenth aspect, alone or in combination with one or more of the first to eighth aspects, further at least in part based on the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state being specified by the configuration, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state being different values.

[0135] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the closed loop indication is a closed loop index value.

[0136] although Figure 7 An example block diagram of process 700 is shown, but in some aspects, process 700 may include Figure 7 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 700 may be performed in parallel.

[0137] Figure 8 is a diagram of an example apparatus 800 for wireless communication according to the present disclosure. Apparatus 800 may be a UE (e.g., UE 120, UE 520), or a UE may include apparatus 800. In some aspects, apparatus 800 includes a receiving component 802 and a transmitting component 804, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 800 may communicate with another apparatus 806 (such as a UE, a base station, or another wireless communication device) using receiving component 802 and transmitting component 804. As further shown, apparatus 800 may include a communication manager 808. Communication manager 808 may control and / or otherwise manage one or more operations of receiving component 802 and / or transmitting component 804. In some aspects, communication manager 808 may include a communication manager 808 in conjunction with Figure 2 One or more antennas, modems, controllers / processors, memories, or combinations thereof of the UE. The communication manager 808 may be or be similar to Figure 1 and Figure 2For example, in some aspects, the communication manager 808 can be configured to perform one or more of the functions described as being performed by the communication manager 140. In some aspects, the communication manager 808 can include a receiving component 802 and / or a sending component 804. The communication manager 140 can include a power control component 810, among other things.

[0138] In some aspects, the apparatus 800 may be configured to perform Figures 1 to 5 Additionally or alternatively, the apparatus 800 may be configured to perform one or more processes described herein, such as Figure 6 The process 600. In some aspects, Figure 8 The device 800 and / or one or more components shown may include a combination of Figure 2 One or more components of the UE. Additionally or alternatively, Figure 8 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0139] The receiving component 802 may receive communications from the device 806, such as reference signals, control information, data communications, or combinations thereof. The receiving component 802 may provide the received communications to one or more other components of the device 800. In some aspects, the receiving component 802 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 one or more other components of the device 800. In some aspects, the receiving component 802 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories or combinations thereof of the UE.

[0140] The transmitting component 804 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 806. In some aspects, one or more other components of the device 800 may generate communications and may provide the generated communications to the transmitting component 804 for transmission to the device 806. In some aspects, the transmitting component 804 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 the device 806. In some aspects, the transmitting component 804 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the UE. In some aspects, the transmit component 804 can be co-located with the receive component 802 in a transceiver.

[0141] Receiving component 802 can receive a configuration for closed-loop power control. Power control component 810 can select a transmit power based at least in part on the configuration. Transmitting component 804 can transmit the SRS using a value of an SRS power control adjustment state that is the same as or different from a value of a PUSCH power control adjustment state based at least in part on the configuration comprising a closed-loop indication or the configuration being an RRC configuration.

[0142] Figure 8 The number and arrangement of components shown are provided as examples. In practice, there may be Figure 8 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Figure 8 Two or more components shown may be implemented in a single component, or Figure 8 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 8 The illustrated set of component(s) may be described as being executable by Figure 8 Another collection of components shown performs one or more functions.

[0143] Fig. 9 is a diagram of an example apparatus 900 for wireless communication according to the present disclosure. Apparatus 900 may be a network entity (e.g., network node 110, network entity 510), or a network entity may include apparatus 900. In some aspects, apparatus 900 includes a receiving component 902 and a sending component 904, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 900 may communicate with another apparatus 906 (such as a UE, a base station, or another wireless communication device) using receiving component 902 and sending component 904. As further shown, apparatus 900 may include a communication manager 908. The communication manager 908 may control and / or otherwise manage one or more operations of receiving component 902 and / or sending component 904. In some aspects, the communication manager 908 may include a communication manager 908 in conjunction with Figure 2 One or more antennas, modems, controllers / processors, memories, or combinations thereof of the network entities. The communication manager 908 may be or be similar to Figure 1 and Figure 2For example, in some aspects, the communication manager 908 can be configured to perform one or more of the functions described as being performed by the communication manager 150. In some aspects, the communication manager 908 can include a receiving component 902 and / or a transmitting component 904. The communication manager 908 can include a power control component 910, among other things.

[0144] In some aspects, the apparatus 900 may be configured to perform Figures 1 to 5 Additionally or alternatively, the apparatus 900 may be configured to perform one or more processes described herein, such as Figure 7 The process 700. In some aspects, Fig. 9 The device 900 and / or one or more components shown may include a combination of Figure 2 One or more components of the network entity. Additionally or alternatively, Fig. 9 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0145] The receiving component 902 may receive communications from the device 906, such as reference signals, control information, data communications, or combinations thereof. The receiving component 902 may provide the received communications to one or more other components of the device 900. In some aspects, the receiving component 902 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 one or more other components of the device 900. In some aspects, the receiving component 902 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories or combinations thereof of the network entity.

[0146] Transmit component 904 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 906. In some aspects, one or more other components of device 900 may generate communications and may provide the generated communications to transmit component 904 for transmission to device 906. In some aspects, transmit component 904 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 906. In some aspects, transmit component 904 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the network entity. In some aspects, the transmit component 904 can be co-located with the receive component 902 in a transceiver.

[0147] The transmitting component 904 can transmit a configuration for closed-loop power control. The power control component 910 can generate the configuration based at least in part on UE capabilities, traffic conditions, and / or channel conditions. The receiving component 902 can receive the SRS using a value of an SRS power control adjustment state that is the same as or different from a value of a PUSCH power control adjustment state based at least in part on the configuration including a closed-loop indication or the configuration being an RRC configuration.

[0148] Fig. 9 The number and arrangement of components shown are provided as examples. In practice, there may be Fig. 9 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig. 9 Two or more components shown may be implemented in a single component, or Fig. 9 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig. 9 The illustrated set of component(s) may be described as being executable by Fig. 9 Another collection of components shown performs one or more functions.

[0149] The following provides an overview of some aspects of the disclosure:

[0150] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a configuration for closed-loop power control; and sending an SRS using a sounding reference signal (SRS) power control adjustment state value that is the same as or different from a value of a physical uplink shared channel (PUSCH) power control adjustment state based at least in part on the configuration including a closed-loop indication or the configuration being a radio resource control (RRC) configuration.

[0151] Aspect 2: The method according to aspect 1, wherein, based at least in part on the configuration including the closed-loop indication, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are the same value.

[0152] Aspect 3: The method according to Aspect 2, wherein the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state both correspond to the first index value of the closed-loop indication or to the second index value of the closed-loop indication.

[0153] Aspect 4: A method according to Aspect 2, wherein further at least in part based on the fact that the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are not specified by the configuration, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are the same value.

[0154] Aspect 5: The method according to aspect 1, wherein the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are different values, at least in part based on the configuration not including the closed loop indication.

[0155] Aspect 6: A method according to Aspect 5, wherein further at least in part based on the fact that the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are not specified by the configuration, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are different values.

[0156] Aspect 7: The method according to aspect 1, wherein the configuration is an RRC configuration indicating that the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are the same value.

[0157] Aspect 8: The method according to Aspect 7, wherein the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state both correspond to the first index value of the closed-loop indication or to the second index value of the closed-loop indication.

[0158] Aspect 9: A method according to Aspect 7, wherein further at least in part based on the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state being specified by the configuration, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state being the same value.

[0159] Aspect 10: The method according to aspect 1, wherein the configuration is an RRC configuration indicating that the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are different values.

[0160] Aspect 11: A method according to Aspect 10, wherein further at least in part based on the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state being specified by the configuration, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state being different values.

[0161] Aspect 12: The method according to any one of Aspects 1 to 11, wherein the closed loop indication is a closed loop index value.

[0162] Aspect 13: The method according to any one of aspects 1 to 12, wherein the SRS power control adjustment state is configured for use in a unified transmission configuration indicator framework.

[0163] Aspect 14: A method of wireless communication performed by a network entity, the method comprising: sending a configuration for closed-loop power control; and receiving an SRS using a sounding reference signal (SRS) power control adjustment state value that is the same as or different from a value of a physical uplink shared channel (PUSCH) power control adjustment state based at least in part on the configuration including a closed-loop indication or the configuration being a radio resource control (RRC) configuration.

[0164] Aspect 15: The method according to aspect 14, wherein, based at least in part on the configuration including the closed loop indication, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are the same value.

[0165] Aspect 16: The method according to Aspect 15, wherein the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state both correspond to the first index value of the closed-loop indication or to the second index value of the closed-loop indication.

[0166] Aspect 17: A method according to Aspect 16, wherein further at least in part based on the fact that the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are not specified by the configuration, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are the same value.

[0167] Aspect 18: The method according to aspect 14, wherein the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are different values ​​based at least in part on the configuration not including the closed loop indication.

[0168] Aspect 19: A method according to Aspect 18, wherein further at least in part based on the fact that the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are not specified by the configuration, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are different values.

[0169] Aspect 20: The method according to aspect 14, wherein the configuration is an RRC configuration indicating that the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are the same value.

[0170] Aspect 21: The method according to Aspect 20, wherein the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state both correspond to the first index value of the closed-loop indication or to the second index value of the closed-loop indication.

[0171] Aspect 22: A method according to Aspect 20, wherein further at least in part based on the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state being specified by the configuration, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state being the same value.

[0172] Aspect 23: The method according to aspect 14, wherein the configuration is an RRC configuration indicating that the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are different values.

[0173] Aspect 24: A method according to Aspect 23, wherein further at least in part based on the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state being specified by the configuration, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state being different values.

[0174] Aspect 25: The method according to any one of aspects 14 to 24, wherein the closed loop indication is a closed loop index value.

[0175] Aspect 26: An apparatus for wireless communication at a device, the apparatus comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 25.

[0176] Aspect 27: A device for wireless communication, the device comprising a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 25.

[0177] Aspect 28: 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 25.

[0178] Aspect 29: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 25.

[0179] Aspect 30: 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 one or more of the methods described in aspects 1 to 25.

[0180] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the various aspects.

[0181] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to a specific software code herein to describe the operation and behavior of the system and / or method, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0182] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0183] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (it includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (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).

[0184] Any element, action or instruction used herein should not be interpreted as key or necessary unless explicitly described as such. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items mentioned in conjunction with the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only one item is intended to be referred to, the phrase "only one" or similar terms will be used. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "an element with" A may also have B). In addition, the phrase "based on" is intended to represent "based at least in part on", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (e.g., if used in conjunction with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and one or more processors coupled to the memory and configured to: receiving a configuration for closed-loop power control; as well as Based at least in part on the configuration comprising a closed loop indication or the configuration being a radio resource control (RRC) configuration, a sounding reference signal (SRS) power control adjustment state value is sent using the same or different value as a physical uplink shared channel (PUSCH) power control adjustment state.

2. The UE of claim 1, wherein based at least in part on the configuration including the closed loop indication, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are the same value.

3. The UE according to claim 2, wherein the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state both correspond to the first index value of the closed loop indication or to the second index value of the closed loop indication.

4. The UE of claim 2, wherein further based at least in part on the fact that the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are not specified by the configuration, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are the same value.

5. The UE of claim 1, wherein based at least in part on the configuration not including the closed loop indication, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are different values.

6. The UE of claim 5, wherein the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are different values, further based at least in part on the fact that the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are not specified by the configuration. 7 . The UE according to claim 1 , wherein the configuration is an RRC configuration indicating that the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are the same value.

8. The UE according to claim 7, wherein the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state both correspond to the first index value of the closed loop indication or to the second index value of the closed loop indication.

9. The UE of claim 7, wherein further based at least in part on the fact that the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are specified by the configuration, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are the same value. 10 . The UE according to claim 1 , wherein the configuration is an RRC configuration indicating that the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are different values.

11. The UE of claim 10, wherein further based at least in part on the fact that the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are specified by the configuration, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are different values.

12. The UE according to claim 1, wherein the closed loop indication is a closed loop index value.

13. A network entity for wireless communication, the network entity comprising: Memory; and one or more processors coupled to the memory and configured to: sending a configuration for closed loop power control; as well as Based at least in part on the configuration comprising a closed loop indication or the configuration being a radio resource control (RRC) configuration, a sounding reference signal (SRS) power control adjustment state value that is the same as or different from a physical uplink shared channel (PUSCH) power control adjustment state is used to receive the SRS.

14. The network entity of claim 13, wherein based at least in part on the configuration including the closed loop indication, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are the same value. 15 . The network entity according to claim 14 , wherein the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state both correspond to a first index value of the closed loop indication or to a second index value of the closed loop indication.

16. The network entity of claim 15, wherein further based at least in part on the fact that the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are not specified by the configuration, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are the same value.

17. The network entity of claim 13, wherein based at least in part on the configuration not including the closed loop indication, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are different values.

18. The network entity of claim 17, wherein the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are different values, further based at least in part on the fact that the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are not specified by the configuration.

19. The network entity of claim 13, wherein the configuration is an RRC configuration indicating that the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are the same value.

20. The network entity according to claim 19, wherein the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state both correspond to a first index value of the closed loop indication or to a second index value of the closed loop indication.

21. The network entity of claim 19, wherein further based at least in part on the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state being specified by the configuration, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are the same value.

22. The network entity of claim 13, wherein the configuration is an RRC configuration indicating that the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are different values.

23. The network entity of claim 22, wherein further based at least in part on the fact that the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are specified by the configuration, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are different values.

24. The network entity of claim 13, wherein the loop closure indication is a loop closure index value.

25. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a configuration for closed-loop power control; as well as Based at least in part on the configuration comprising a closed loop indication or the configuration being a radio resource control (RRC) configuration, a sounding reference signal (SRS) power control adjustment state value is sent using the same or different value as a physical uplink shared channel (PUSCH) power control adjustment state.

26. The method of claim 25, wherein based at least in part on the configuration including the closed loop indication, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are the same value.

27. The method of claim 25, wherein based at least in part on the configuration not including the closed loop indication, the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are different values.

28. The method of claim 25, wherein the configuration is an RRC configuration indicating that the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are the same value.

29. The method of claim 25, wherein the configuration is an RRC configuration indicating that the value of the SRS power control adjustment state and the value of the PUSCH power control adjustment state are different values.

30. A method of wireless communication performed by a network entity, the method comprising: sending a configuration for closed loop power control; as well as Based at least in part on the configuration comprising a closed loop indication or the configuration being a radio resource control (RRC) configuration, a sounding reference signal (SRS) power control adjustment state value that is the same as or different from a physical uplink shared channel (PUSCH) power control adjustment state is used to receive the SRS.

Images