Uplink power control for uplink dense deployment scenarios

Abstract

Methods, systems, and devices are described for wireless communication. The described techniques can enable a user equipment (UE) to determine a transmit power for an uplink message in an uplink dense deployment. For example, the UE can receive a medium access control-control element (MAC-CE) message that indicates transmit power control (TPC) information for one or more uplink messages to an uplink dedicated network entity. For example, the MAC-CE message can indicate a closed loop power control parameter, a path loss offset, or an open loop power control parameter. Additionally or alternatively, the UE can receive a downlink control information (DCI) message that indicates a path loss offset change or a relative open loop power control parameter change. Additionally or alternatively, the UE can receive an indication of a reference signal received power (RSRP) associated with an uplink reference signal and can calculate a path loss of an uplink channel based on the RSRP.

Description

Technical Field

[0001] The following text relates to wireless communication, including uplink power control for scenarios with dense uplink deployments. Background Technology

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication of communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0003] The described technology relates to improved methods, systems, devices, and apparatuses for uplink power control in uplink-intensive deployment scenarios. For example, the described technology enables a user equipment (UE) to determine the transmission power of uplink messages in uplink-intensive deployment scenarios. For example, the UE may receive a Media Access Control-Control Element (MAC-CE) message indicating transmission power control (TPC) information for one or more uplink messages destined for an uplink dedicated network entity. For example, the MAC-CE message may indicate closed-loop power control parameters, path loss offsets relative to path losses associated with one or more downlink reference signals, or open-loop power control parameters. Additionally or alternatively, the UE may receive downlink control information (DCI) messages indicating changes in path loss offsets relative to an initial path loss offset value or open-loop power control parameters. Additionally or alternatively, the UE may receive an indication of a Reference Signal Received Power (RSRP) associated with an uplink reference signal and may calculate the path loss of the uplink channel (e.g., and correspondingly, the transmission power) based on the RSRP.

[0004] A method for wireless communication by a UE is described. The method may include: receiving a MAC-CE message including TPC information for one or more uplink messages; and transmitting one or more uplink messages based on the TPC information.

[0005] A UE for wireless communication is described. The UE may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute code to enable the UE to: receive a MAC-CE message including TPC information for one or more uplink messages; and transmit one or more uplink messages based on the TPC information.

[0006] Another UE for wireless communication is described. This UE may include: components for receiving a MAC-CE message including TPC information for one or more uplink messages; and components for transmitting one or more uplink messages based on the TPC information.

[0007] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to: receive a MAC-CE message including TPC information for one or more uplink messages; and transmit one or more uplink messages based on the TPC information.

[0008] In some examples of the methods described herein, the UE, and non-transitory computer-readable media, TPC information includes updates to closed-loop power control parameters.

[0009] In some examples of the methods described herein, UEs, and non-transitory computer-readable media, the TPC information also includes a closed-loop index associated with the TPC information.

[0010] In the methods described herein, in some examples of UEs and nontransitory computer-readable media, TPC information includes updates to path loss offset parameters, and the path loss offset parameters may be offset from the path loss associated with the downlink reference signal.

[0011] The methods described herein, some examples of UEs and non-transitory computer-readable media may also include operations, features, components or instructions for receiving configuration or indication of a downlink reference signal associated with a path loss offset parameter.

[0012] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the downlink reference signal may be a downlink path loss reference signal in a set of downlink path loss reference signals, and the downlink reference signal may be associated with: the lowest path loss reference signal ID in the set of downlink path loss reference signals, the highest path loss reference signal ID in the set of downlink path loss reference signals, the lowest path loss value in the set of downlink path loss reference signals, the highest path loss value in the set of downlink path loss reference signals, the downlink path loss reference signal associated with the lowest TCI state in the set of active transmission configuration indicator (TCI) states associated with the set of downlink path loss reference signals, or the downlink path loss reference signal associated with the highest TCI state in the set of active TCI states associated with the set of downlink path loss reference signals.

[0013] In the methods described herein, in some examples of UEs and non-transitory computer-readable media, TPC information includes updates to open-loop power control parameters.

[0014] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, TPC information may be shared by a set of multiple uplink channels or uplink signals, or may be specific to a single uplink channel or uplink signal.

[0015] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, TPC information includes indications of absolute TPC parameter values ​​or indications of offsets from previous TPC parameter values.

[0016] The methods described herein, examples of UEs, and nontransitory computer-readable media may also include operations, features, components, or instructions for receiving radio resource control (RRC) messages that indicate TPC information, including indications of absolute TPC parameter values ​​or indications of offsets from previous TPC parameter values.

[0017] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, TPC information may be associated with an ID, and previous TPC parameter values ​​may be either initial TPC parameter values ​​associated with an ID or the last received TPC parameter values ​​associated with an ID.

[0018] The methods described herein, some examples of UEs and non-transitory computer-readable media may also include operations, features, components or instructions for receiving control messages indicating initial TPC parameter values.

[0019] In the methods described herein, and in some examples of UEs and nontransitory computer-readable media, MAC-CE messages indicate the ID of the TCI state associated with TPC information, the path loss reference signal, the open-loop power control parameter set, the BWP, the serving cell, the sounding reference signal (SRS) resource set, the physical uplink control channel (PUCCH) resource, or some combination thereof.

[0020] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for receiving an RRC message indicating whether the UE will receive one or more DCI messages including additional TPC information.

[0021] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for receiving one or more DCI messages including additional TPC information, wherein sending one or more uplink messages includes sending one or more uplink messages based on the additional TPC information.

[0022] In some examples of the methods described herein, UEs, and nontransitory computer-readable media, one or more uplink messages include one or more PUCCH messages, one or more Physical Uplink Shared Channel (PUSCH) messages, one or more SRSs, or some combination thereof.

[0023] A method for wireless communication by a UE is described. The method may include: receiving a DCI message indicating TPC parameters for one or more uplink messages, wherein the TPC parameters include either an update to open-loop power control parameters relative to previous open-loop power control parameters or an update to path loss offset parameters, wherein the path loss offset parameters are an offset from path loss associated with a downlink reference signal; and transmitting one or more uplink messages based on the TPC parameters.

[0024] A UE for wireless communication is described. The UE may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute code that causes the UE to: receive a DCI message indicating TPC parameters for one or more uplink messages, wherein the TPC parameters include one of an update to open-loop power control parameters relative to previous open-loop power control parameters or an update to path loss offset parameters, wherein the path loss offset parameters are an offset from the path loss associated with a downlink reference signal; and transmit one or more uplink messages based on the TPC parameters.

[0025] Another UE for wireless communication is described. The UE may include: means for receiving a DCI message indicating TPC parameters for one or more uplink messages, wherein the TPC parameters include either an update to open-loop power control parameters relative to previous open-loop power control parameters or an update to path loss offset parameters, wherein the path loss offset parameters are an offset from path loss associated with a downlink reference signal; and means for transmitting one or more uplink messages based on the TPC parameters.

[0026] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to: receive a DCI message indicating TPC parameters for one or more uplink messages, wherein the TPC parameters include either an update to open-loop power control parameters relative to previous open-loop power control parameters or an update to path loss offset parameters, wherein the path loss offset parameters are an offset from the path loss associated with a downlink reference signal; and transmit one or more uplink messages based on the TPC parameters.

[0027] The methods described herein, some examples of UEs and non-transitory computer-readable media may also include operations, features, components or instructions for receiving configuration or indication of downlink reference signals.

[0028] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the downlink reference signal may be a downlink path loss reference signal in a set of downlink path loss reference signals, and the downlink reference signal may be associated with: the lowest path loss reference signal ID in the set of downlink path loss reference signals, the highest path loss reference signal ID in the set of downlink path loss reference signals, the lowest path loss value in the set of downlink path loss reference signals, the highest path loss value in the set of downlink path loss reference signals, the downlink path loss reference signal associated with the lowest TCI state in the set of active TCI states associated with the set of downlink path loss reference signals, or the downlink path loss reference signal associated with the highest TCI state in the set of active TCI states associated with the set of downlink path loss reference signals.

[0029] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, updating the path loss offset parameter includes an indication of an absolute path loss offset value or an indication of an offset from a previous path loss offset value.

[0030] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for receiving an RRC message indicating an offset, including an indication of an absolute path loss offset value or an offset relative to a previous path loss offset value.

[0031] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, updates to open-loop power control parameters may be associated with an ID, and previous open-loop power control parameters may include initial open-loop power control parameters associated with an ID or the last received open-loop power control parameters associated with an ID.

[0032] In the methods described herein, and in some examples of UEs and nontransitory computer-readable media, DCI messages indicate the ID of the TCI state associated with TPC parameters, the path loss reference signal, the open-loop power control parameter set, the BWP, the serving cell, the SRS resource set, the PUCCH resource, or some combination thereof.

[0033] The methods described herein, UEs, and some examples of non-transitory computer-readable media may also include operations, features, components, or instructions for receiving an RRC message indicating whether the UE will receive one or more additional DCI messages including additional TPC information.

[0034] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for receiving one or more additional DCI messages that include additional TPC information, wherein sending one or more uplink messages includes sending one or more uplink messages based on the additional TPC information.

[0035] In some examples of the methods described herein, UEs, and non-transitory computer-readable media, DCI messages can be scheduled DCIs or group public DCIs.

[0036] In some examples of the methods described herein, UEs, and nontransitory computer-readable media, one or more uplink messages include one or more PUCCH messages, one or more PUSCH messages, one or more SRSs, or some combination thereof.

[0037] A method for wireless communication by a UE is described. The method may include: transmitting an uplink reference signal; receiving an indication of an RSRP associated with the uplink reference signal; and transmitting one or more uplink messages, wherein the transmit power associated with the one or more uplink messages is based on the RSRP.

[0038] A UE for wireless communication is described. The UE may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute code to cause the UE to: transmit an uplink reference signal; receive an indication of an RSRP associated with the uplink reference signal; and transmit one or more uplink messages, wherein the transmit power associated with the one or more uplink messages is based on the RSRP.

[0039] Another UE for wireless communication is described. The UE may include: components for transmitting an uplink reference signal; components for receiving an indication of the RSRP associated with the uplink reference signal; and components for transmitting one or more uplink messages, wherein the transmit power associated with the one or more uplink messages is based on the RSRP.

[0040] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to: transmit an uplink reference signal; receive an indication of an RSRP associated with the uplink reference signal; and transmit one or more uplink messages, wherein the transmit power associated with the one or more uplink messages is based on the RSRP.

[0041] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for calculating uplink path loss associated with an uplink reference signal based on RSRP, wherein transmit power may be based on uplink path loss.

[0042] In some examples of the methods described herein, UEs, and nontransitory computer-readable media, one or more uplink messages include one or more PUCCH messages, one or more PUSCH messages, one or more SRSs, or some combination thereof.

[0043] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for receiving an indication of an uplink reference signal that may be associated with one or more PUCCH messages, one or more PUSCH messages, one or more SRSs, or some combination thereof.

[0044] The methods described herein, some examples of UEs and non-transitory computer-readable media may also include operations, features, components or instructions for receiving control messages indicating uplink reference signals from a set of uplink reference signals.

[0045] In some examples of the methods described herein, UEs, and non-transitory computer-readable media, indications of RSRP may be received via MAC-CE messages or via DCI messages.

[0046] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for sending one or more initial uplink messages based on a default path loss value prior to receiving an instruction to RSRP.

[0047] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for determining a default path loss value based on the path loss associated with a downlink reference signal.

[0048] In the methods described herein, and in some examples of UEs and nontransitory computer-readable media, the default path loss value can be zero.

[0049] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for receiving a control message indicating a corresponding default path loss value associated with each uplink reference signal in a set of uplink reference signals, the set of uplink reference signals including the uplink reference signal, wherein the default path loss value may be a corresponding default path loss value associated with the uplink reference signal. Attached Figure Description

[0050] Figure 1 An example of a wireless communication system supporting uplink power control for uplink-intensive deployment scenarios, according to one or more aspects of this disclosure, is shown.

[0051] Figure 2 An example of a wireless communication system supporting uplink power control for uplink-intensive deployment scenarios, according to one or more aspects of this disclosure, is shown.

[0052] Figure 3 An example of a slot diagram supporting uplink power control for uplink-intensive deployment scenarios, according to one or more aspects of this disclosure, is shown.

[0053] Figure 4 An example of a slot diagram supporting uplink power control for uplink-intensive deployment scenarios, according to one or more aspects of this disclosure, is shown.

[0054] Figure 5 An example of a process flow supporting uplink power control for uplink-intensive deployment scenarios, according to one or more aspects of this disclosure, is shown.

[0055] Figure 6 An example of a process flow supporting uplink power control for uplink-intensive deployment scenarios, according to one or more aspects of this disclosure, is shown.

[0056] Figure 7 An example of a process flow supporting uplink power control for uplink-intensive deployment scenarios, according to one or more aspects of this disclosure, is shown.

[0057] Figure 8 and Figure 9 A block diagram of an apparatus for uplink power control in uplink-intensive deployment scenarios, according to one or more aspects of this disclosure, is shown.

[0058] Figure 10 A block diagram of a communication manager supporting uplink power control for uplink-intensive deployment scenarios, according to one or more aspects of this disclosure, is shown.

[0059] Figure 11 A diagram of a system including devices supporting uplink power control for uplink-intensive deployment scenarios is shown, according to one or more aspects of this disclosure.

[0060] Figures 12 to 17 A flowchart illustrating a method for uplink power control for uplink-intensive deployment scenarios, according to one or more aspects of this disclosure, is shown. Detailed Implementation

[0061] In some wireless communication systems, a user equipment (UE) may receive a downlink reference signal from a network entity to calculate the path loss associated with the channel between the UE and the network entity. In some examples, the UE may use the path loss to determine the uplink transmit power for one or more uplink messages (e.g., Physical Uplink Shared Channel (PUSCH) messages, Physical Uplink Control Channel (PUCCH) messages, or Sounding Reference Signals (SRS)) used to reach the network entity. However, in some cases, the wireless communication system may have an uplink-dense deployment comprising a central network entity for transmitting downlink signaling to the UE and multiple network entities dedicated to receiving uplink signaling from the UE (e.g., and not transmitting downlink signaling). In such cases, the dedicated uplink network entities may not transmit the downlink reference signal.

[0062] Therefore, the UE can conversely transmit one or more uplink reference signals to the uplink dedicated network entity via the uplink channel. The uplink dedicated network entity can indicate channel information (e.g., path loss, Reference Signal Received Power (RSRP)) based on the uplink reference signals destined for the central network entity, and the central network entity can configure path loss information or other transmit power control (TPC) information for the UE based on the channel information. However, such techniques may involve larger TPC messages than some other power control techniques, and therefore the TPC field in the downlink control information (DCI) used for other power control techniques may be too small to adequately indicate the TPC. Additionally, in some examples, the UE may miss one or more DCI messages, which could lead to transmit power misalignment between the uplink dedicated network entity and the UE.

[0063] The techniques described herein allow a UE to determine the transmission power of uplink messages in a dense uplink deployment. For example, the UE may receive a Media Access Control-Control Element (MAC-CE) indicating TPC information for one or more uplink messages destined for an uplink dedicated network entity. The MAC-CE may indicate closed-loop power control parameters, path loss offsets (e.g., path loss relative to one or more downlink reference signals), or open-loop power control parameters. Additionally or alternatively, the UE may receive a DCI message indicating a change in path loss offset or a change relative to open-loop power control parameters (e.g., relative to an initial path loss offset value or open-loop power control parameter). Additionally or alternatively, the UE may receive an indication of the RSRP associated with the uplink reference signal and may calculate the path loss of the uplink channel (e.g., and correspondingly, the transmission power) based on the RSRP.

[0064] The aspects of this disclosure are first described in the context of a wireless communication system. The aspects of this disclosure are further illustrated and described with reference to time slot diagrams and process flowcharts. The aspects of this disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts related to uplink power control for uplink dense deployment scenarios.

[0065] Figure 1An example of a wireless communication system 100 supporting uplink power control for uplink-intensive deployment scenarios, according to one or more aspects of this disclosure, is shown. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0066] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0067] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are illustrated herein. The UE 115 described herein can be able to support various types of devices (such as, e.g., ...). Figure 1 It communicates with other UEs (115 or network entity 105) as shown.

[0068] As described herein, nodes of the wireless communication system 100 (which may be referred to as network nodes or wireless nodes) may be network entity 105 (e.g., any network entity described herein), UE 115 (e.g., any UE described herein), network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. Alternatively, a node may be network entity 105. Furthermore, a first node may be configured to communicate with a second or third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0069] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.

[0070] One or more network entities in network entity 105 described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, node B, evolved node B (eNodeB, eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home evolved node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0071] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across two or more network entities 105, such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) 160, a Distributed Unit (DU) 165, a Radio Unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a near-real-time RIC, a non-real-time RIC), a Service Management and Orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0072] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and each can be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via such communication links.

[0073] In a wireless communication system (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0074] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support uplink power control for uplink-intensive deployment scenarios as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0075] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or some other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0076] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes act as relays, network entities 105, and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0077] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 can be configured using multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0078] In some examples, such as in carrier aggregation configurations, a carrier may also have acquisition signaling or control signaling to coordinate the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel grating used for discovery by UE 115. A carrier may operate in standalone mode, in which case initial acquisition and connection can be performed by UE 115 via that carrier, or the carrier may operate in non-standalone mode, in which case different carriers (e.g., the same or different radio access technologies) are used to anchor the connection.

[0079] The communication link 125 shown in the wireless communication system 100 may include downlink transmission (e.g., forward link transmission) from network entity 105 to UE 115, uplink transmission (e.g., return link transmission) from UE 115 to network entity 105, or both, as well as other transmission configurations. A carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0080] A carrier may be associated with a specific bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one bandwidth in a set of bandwidths for a particular radio access technology (e.g., 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., network entity 105, UE 115, or both) may have hardware configurations that support communication using a specific carrier bandwidth, or may be configured to support communication using one of the carrier bandwidths in a set of carrier bandwidths. In some examples, the wireless communication system 100 may include network entity 105 or UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., subband, BWP) or all of the carrier bandwidth.

[0081] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0082] It can support one or more sets of parameters for a carrier, and the set of parameters may include subcarrier spacing ( (and cyclic prefix). A carrier can be divided into one or more BWPs with the same or different sets of parameters. In some examples, multiple BWPs can be used to configure UE 115. In some examples, a single BWP of a carrier can be active at a given time, and communication for UE 115 can be constrained to one or more active BWPs.

[0083] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, in response This can represent the supported subcarrier spacing, and The supported Discrete Fourier Transform (DFT) size can be represented. Time intervals for communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0084] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may also be divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0085] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0086] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

[0087] Network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used (e.g., using a carrier) to communicate with network entity 105 and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID), or other identifier). In some examples, a cell may also refer to a coverage area 110 or a portion of coverage area 110 (e.g., a sector) in which a logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the range of such cells may be from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be a building, a subset of buildings, or external space between or overlapping coverage areas 110, or may include buildings, subsets of buildings, or external space between or overlapping coverage areas.

[0088] Macro cells typically cover a relatively large geographical area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. In contrast, small cells may be associated with a lower-power network entity 105 (e.g., a lower-power base station 140) and may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UE 115 that has a service subscription with a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a closed subscriber group (CSG), or UE 115 associated with a user in a home or office). Network entity 105 may support one or more cells and may also use one or more component carriers to support communication via one or more cells.

[0089] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0090] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

[0091] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0092] In some examples, UE 115 may be configured to support direct communication with other UE 115s via device-to-device (D2D) communication link 135 (e.g., according to peer-to-peer (P2P), D2D, or sidelink protocols). In some examples, one or more UE 115s performing D2D communication in a group may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UE 115s in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, the group of UE 115s communicating via D2D communication may support a one-to-many (1:M) system in which each UE 115 transmits to each of the other UE 115s in the group. In some examples, network entity 105 may facilitate the scheduling of resources used for D2D communication. In other examples, D2D communication may be performed between UEs 115 without involving network entity 105.

[0093] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), access and mobility management function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be delivered through the user plane entity, which provides IP address allocation and other functions. The user plane entity may connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0094] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0095] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may employ licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology using unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands may be based on carrier aggregation configurations combined with component carriers operating with licensed frequency bands (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0096] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0097] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device by the transmitting or receiving device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0098] Network entity 105 or UE 115 may use beam scanning technology as part of beamforming operations. For example, network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by network entity 105 in different directions. For example, network entity 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. Beam directions may be identified (e.g., by a transmitting device (such as network entity 105) or by a receiving device (such as UE 115)) by transmission along different beam directions for later transmission or reception by network entity 105.

[0099] Some signals (such as data signals associated with a specific receiving device) may be transmitted by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., the direction associated with a receiving device (such as receiving network entity 105 or receiving UE 115). In some examples, the beam direction associated with transmission along a single beam direction may be determined based on the signals transmitted along one or more beam directions. For example, UE 115 may receive one or more signals transmitted by network entity 105 in different directions and may report to network entity 105 an indication of signals received by UE 115 with the highest signal quality or other acceptable signal quality.

[0100] In some examples, transmissions performed by a device (e.g., network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital pre-decoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating pre-decoding weights for one or more beam directions, and this feedback may correspond to a beam set configured across the system bandwidth or one or more subbands. Network entity 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)) that may or may not be pre-decoded. UE 115 may provide feedback for beam selection, which may be a pre-decoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel codebook, linear combination codebook, port selection codebook). Although these techniques are described with reference to signals transmitted by network entity 105 (e.g., base station 140, RU 170) along one or more directions, UE 115 may use similar techniques to transmit signals multiple times along different directions (e.g., to identify the beam direction used by UE 115 for subsequent transmission or reception), or to transmit signals along a single direction (e.g., to transmit data to a receiving device).

[0101] A receiving device (e.g., UE 115) may perform reception operations according to multiple reception configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a transmitting device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple reception directions by: receiving via different antenna subarrays; processing the received signal according to different antenna subarrays; receiving according to different sets of reception beamforming weights (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of the antenna array; or processing the received signal according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array. Any of these operations may be referred to as “listening” according to different reception configurations or reception directions. In some examples, the receiving device may use a single reception configuration to receive along a single beam direction (e.g., when a data signal is received). A single receiver configuration can be aligned along a beam direction determined based on listening according to different receiver configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0102] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer performs packet segmentation and reassembly for transmission via logical channels. The MAC layer performs priority processing and multiplexing of logical channels to transport channels. The MAC layer can also implement error detection, error correction, or both to support retransmission and improve link efficiency. In the control plane, the RRC layer can provide the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 supporting user plane data radio bearers. The PHY layer maps transport channels to physical channels.

[0103] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to a different time interval.

[0104] In some cases, UE 115 can operate using a Unified Transmit Configuration Indicator (TCI) state. That is, UE 115 can receive an indication of a TCI state for use by UE 115 in uplink beamforming. A unified TCI state can be applied to more than one type of signal. For example, UE 115 can use a unified TCI state for uplink data messages (such as PUSCH signaling), for PUCCH signaling, and for SRS. UE 115 can use unified or combined TCI states in one or more frequency ranges (FRs) (e.g., FR1 or FR2). In some examples, UE 115 can use a different TCI state for each of PUSCH, PUCCH, and SRS.

[0105] In some examples of the wireless communication system 100, the UE 115 can operate in an uplink-dense deployment scenario. That is, the UE 115 can send uplink signaling to one or more uplink-dedicated network entities 105 (e.g., uplink receiving points). The uplink-dedicated network entity 105 can receive uplink signaling or channels from the UE 115 and may not send downlink signaling or channels to the UE 115. The UE 115 can communicate uplink and downlink signaling or channels with a central network entity 105 (e.g., macro node, central node, serving cell, serving base station). The central network entity 105 can communicate with the uplink-dedicated network entity 105 via one or more backhaul channels. This asymmetric uplink and downlink density can improve the coverage and capacity of uplink signaling from the UE 115. For example, when insufficient uplink coverage causes path loss (e.g., bottlenecks), uplink-dense deployment can reduce path loss associated with uplink signaling. In addition, dense uplink deployment can reduce the deployment costs and complexity associated with the dedicated uplink network entity 105, because the dedicated uplink network entity 105 can receive uplink signaling and forward it to the central network entity 105 (e.g., process it or not) and may not send downlink signaling.

[0106] In some uplink-intensive deployment scenarios, UE 115 can perform power control operations by transmitting one or more uplink reference signals via the uplink channel for uplink signaling to uplink dedicated network entity 105. Uplink dedicated network entity 105 can indicate channel information (e.g., path loss) based on the uplink reference signals to central network entity 105, and central network entity 105 can configure path loss information or other TPC information for UE 115 based on the channel information. However, such techniques may involve larger TPC messages than power control techniques based on downlink reference signals, and therefore the TPC field in the DCI used for such power control techniques may be too small to adequately indicate the TPC. Additionally, in some examples, UE 115 may miss one or more DCI messages, which could lead to a misalignment of transmit power between uplink dedicated network entity 105 and UE 115.

[0107] Therefore, the techniques described herein allow UE 115 to determine the transmission power of uplink messages in a dense uplink deployment. For example, UE 115 may receive a MAC-CE indicating TPC information for one or more uplink messages destined for uplink dedicated network entity 105. The MAC-CE may indicate closed-loop power control parameters, path loss offset (e.g., relative to path loss associated with one or more downlink reference signals), or open-loop power control parameters. Additionally or alternatively, UE 115 may receive a DCI message indicating a change in path loss offset or a change relative to open-loop power control parameters (e.g., relative to an initial path loss offset value or open-loop power control parameter). Additionally or alternatively, UE 115 may receive an indication of RSRP associated with an uplink reference signal and may calculate the path loss of the uplink channel (e.g., and correspondingly, the transmission power) based on the RSRP.

[0108] Figure 2 An example of a wireless communication system 200 supporting uplink power control for uplink-intensive deployment scenarios, according to one or more aspects of this disclosure, is shown. The wireless communication system 200 may implement, or be implemented by, aspects of the wireless communication system 100. For example, the wireless communication system 200 may include a UE 115 (e.g., UE 115-a) and network entities 105 (e.g., central network entity 105-a, uplink dedicated network entity 105-b, and uplink dedicated network entity 105-c), which may be as described in reference... Figure 1 Examples of the corresponding devices described.

[0109] In some examples of the wireless communication system 200, UE 115-a can perform uplink power control to determine the transmission power of one or more uplink messages 225. P (e.g., in decibels (dB)). For example, UE 115-a may receive one or more downlink reference signals 215-a from network entity 105-a (e.g., central network entity 105-a) via downlink channel 205, and may determine the path loss associated with downlink channel 205 based on downlink reference signals 215-a. UE 115-a may use Formula 1, Formula 2, or Formula 3 (e.g., for PUSCH transmission, PUCCH transmission, or SRS transmission, respectively) to determine the transmit power. P .

[0110]

[0111] Refer to formulas 1, 2, and 3. i It can be defined as a sending timing index. j It can be an index of the power control parameter set configuration (e.g., (and the set of α). It can be an index of the downlink reference signal 215 from the path loss reference signal 215 set. l This could be a power control adjustment state (e.g., closed-loop index). μ It can be the subcarrier spacing associated with the channel between UE 115-a and network entity 105-a, and b It can be a carrier wave. f Service or main community c The BWP (e.g., the BWP, carrier, and serving cell used by UE 115-a to communicate with network entity 105-a). If UE 115-a uses a unified or combined TCI state for PUSCH, PUCCH, and SRS, then UE 115-a can receive a set of power control parameters associated with the unified or combined uplink TCI state. j (For example, The power control parameter set may be additionally or alternatively associated with uplink channel 210-a or downlink reference signal 215 (e.g., it may be channel- or signal-dependent). UE 115-a may obtain information elements from network entity 105-a (e.g., ...). Uplink-powerControlId-r17 , ul-powercontrolId-r17 The system receives instructions on the set of power control parameters.

[0112] It can be used by UE 115-a via uplink channel 210-a (e.g., on carrier). f Service Community c The maximum transmission power of the uplink message 225-a sent to network entity 105-a. , and It can represent open-loop power control parameters These parameters are derived from the components. and components The sum is derived from the weight. and components The sum (for example, where) express A value from a set of values, and a value derived from an SRS resource set. . , and The bandwidth of PUSCH resource assignment, PUCCH resource assignment and SRS resource assignment can be expressed as (e.g., in the number of resource blocks (RB)). It can be a parameter related to the spectral efficiency of the serving cell, and This can be a parameter related to the PUCCH format of the PUCCH resource.

[0113] It can have a downlink reference signal index The path loss estimate (e.g., in dB) of the downlink reference signal 215. and This could be a path loss compensation factor. Therefore, UE 115-a can determine the uplink transmit power based on the measured downlink reference signal 215-a. For example, for PUSCH and PUCCH transmissions, UE 115-a can receive configurations for one or more path loss reference signals 215 (e.g., parameters via Radio Resource Control (RRC) messages). PUSCH-PathlossReferenceRS or parameter PUCCH- PathlossReferenceRS ), and may additionally or alternatively receive indications of path loss reference signals 215 from one or more path loss reference signals 215 (e.g., via MAC-CE or SRS resource indicator in uplink grant). For path loss reference signals 215 used for SRS power control, UE 115-a may receive path loss reference signals 215 configured for each SRS resource set (e.g., parameters). pathlossReferenceRS The UE 115-a can receive RRC messages indicating the path loss reference signal 215 for each SRS resource set, and can apply the path loss reference signal 215 to all SRS resources in the resource set. The UE 115-a can also receive MAC-CE messages indicating updates to the configured path loss reference signal 215 for each SRS resource set. If the UE 115-a uses a combined or unified TCI state for PUSCH, PUCCH, and SRS, the path loss reference signal 215 can be associated with the combined or unified TCI state (e.g., via...). TCI Parameters in the status information element PUSCH-PathlossReferenceRS-Id-17 ,parameter PUCCH- PathlossReferenceRS or parameter pathlossReferenceRS-Id-17 ).

[0114] UE 115-a can use open-loop power control and closed-loop power control to determine the transmit power. For example, UE 115-a can receive a set of open-loop power control parameters (e.g., ...). The UE 115-a is configured to calculate the first part (e.g., the open-loop power control part) of the power control formulas in Formulas 1, 2, and 3, using a set of indications for the downlink reference signal 215-a. The UE 115-a may also receive closed-loop power adjustments indicating the second part (e.g., the closed-loop power control part) of the power control formulas. or TPC commands (e.g., in UE-specific or group public (GC) DCI).

[0115] In some examples of the wireless communication system 200, UE 115-a may use a dense uplink deployment with an asymmetric downlink single transmit / receive point (sTRP) and multiple uplink TRPs (mTRPs), where the multiple uplink TRPs are in-band, in-cell, non-co-located TRPs (e.g., no new uplink-only cells are defined for the uplink mTRPs). That is, UE 115-a may send uplink signaling to one or more uplink dedicated network entities 105 (e.g., uplink dedicated network entities 105-b and 105-c). Uplink dedicated network entities 105-b and 105-c may receive uplink signaling or channels from UE 115-a and may not send downlink signaling or channels to UE 115-a. UE 115-a may communicate uplink and downlink signaling or channels with the central network entity 105-a. Central network entity 105 can communicate with uplink dedicated network entity 105-b and uplink dedicated network entity 105-c via one or more backhaul channels.

[0116] Because uplink dedicated network entities 105-b and 105-c may not send downlink signaling to UE 115-a, UE 115-a may not receive downlink reference signals from them. Accordingly, UE 115-a may not use downlink reference signal 215 to determine path loss and thus the uplink transmission power for uplink signaling (e.g., PUSCH, PUCCH, and SRS) to uplink dedicated network entities 105-b and 105-c.

[0117] Therefore, UE 115-a can transmit uplink reference signals 215-b and 215-c to uplink dedicated network entities 105-b and 105-c, respectively, via uplink channel 210-b and uplink channel 210-c. Uplink dedicated network entities 105-b and 105-c can indicate to the central network entity 105-a the channel conditions (e.g., RSRP, path loss) associated with reference signals 215-b and 215-c, respectively. The central network entity 105-a can accordingly estimate the uplink path loss based on the indicated channel conditions associated with reference signals 215-b and 215-c.

[0118] Central network entity 105-a may indicate path loss or path loss offset configuration to UE 115-a (e.g., in the TPC field of DCI). The indicated path loss may include the path loss associated with uplink reference signal 215-b and uplink reference signal 215-c. The path loss offset configuration may include the offset between the path loss associated with downlink reference signal 215-a and the path loss associated with uplink reference signal 215-b and uplink reference signal 215-c. Therefore, UE 115-a may determine the transmission power (e.g., via uplink channel 210-b and uplink channel 210-c) for one or more uplink messages 225-b and one or more uplink messages 225-c to uplink dedicated network entity 105-b and uplink dedicated network entity 105-c, respectively.

[0119] However, the TPC command in the DCI can indicate small changes to the closed-loop power control parameters, and therefore may not indicate large values ​​(e.g., due to changes in path loss or interference) associated with updating the path loss or path loss offset of uplink reference signals 215-b and 215-c. That is, for non-uplink-dense deployments, UE 115-a can adjust the open-loop transmit power based on the measured path loss associated with the downlink reference signal, and the TPC command can indicate a relatively small range of values ​​to adjust the closed-loop power control parameters. Therefore, such DCI-based TPC commands can include a relatively small number of bits (e.g., two bits) for updating the closed-loop path loss control parameters, while the path loss or path loss offset of uplink reference signals 215-b and 215-c can use a relatively large number of bits (e.g., more than two bits).

[0120] Therefore, in some aspects, UE 115-a may receive additional messages (e.g., MAC-CE messages) indicating transmit power information 220. For example, UE 115-a may receive messages indicating closed-loop power control parameters (e.g., ... or The UE 115-a may also receive an updated MAC-CE message indicating an update to the path loss offset value (e.g., an offset relative to the path loss associated with the downlink reference signal 215-a). Additionally or alternatively, the UE 115-a may also receive an updated MAC-CE message indicating an update to the open-loop power control parameters (e.g., ...). Updated MAC-CE messages. (See related technical references.) Figure 3 To describe in further detail.

[0121] In some respects, UE 115-a may receive a DCI indicating transmit power information 220. For example, the DCI may indicate a path loss offset value (e.g., an offset relative to the path loss associated with downlink reference signal 215-a). Additionally or alternatively, the DCI may indicate the open-loop power control parameters (e.g., This refers to the updating of the initial values ​​of the open-loop power control parameters. (See related technical references.) Figure 4 To describe in further detail.

[0122] In some examples, UE 115-a may miss DCI messages (e.g., due to DCI missed detection). Accordingly, UE 115-a may not receive TPC commands from central network entity 105-a, which could lead to a misalignment of transmit power among UE 115-a, uplink dedicated network entity 105-b, and uplink dedicated network entity 105-c. Therefore, uplink dedicated network entities 105-b and 105-c may incorrectly estimate the path loss associated with uplink reference signals 215-b and 215-c, potentially resulting in inaccurate transmit power calculations.

[0123] Accordingly, UE 115-a may receive an indication of an index associated with the uplink reference signal 215 (e.g., not the downlink reference signal 215-a via downlink channel 205) to be used as the uplink path loss reference signal 215 for measuring path loss. UE 115-a may further receive an indication of the RSRP (e.g., Layer 1 (L1) RSRP) associated with the uplink path loss reference signal 215 via transmit power information 220. For example, central network entity 105-a may indicate the L1 RSRP to UE 115-a, and UE 115-a may calculate the higher-layer filtered RSRP based on the indicated L1 RSRP. UE 115-a may calculate the path loss associated with the uplink path loss reference signal 215 as the transmit power associated with the uplink path loss reference signal 215 minus the higher-layer filtered RSRP. Because UE 115-a knows the transmit power associated with the path loss reference signal 215, UE 115-a can determine the accurate path loss without transmit power misalignment.

[0124] In such examples, UE 115-a may receive transmit power information 220 via MAC-CE or DCI. For example, UE 115-a may receive a MAC-CE or DCI message indicating the L1 RSRP and an identifier (ID) associated with the corresponding uplink path loss reference signal 215. UE 115-a may apply the transmit power calculated using L1 RSRP for X time slots after receiving the MAC-CE or DCI. In some examples, the corresponding uplink path loss reference signal 215 may be an uplink reference signal transmitted in Y time slots before receiving the MAC-CE or DCI.

[0125] In some examples, UE 115-a may use a default path loss value to determine the transmission power for uplink message 225 before receiving a DCI or MAC-CE indicating RSRP. For example, UE 115-a may determine the default path loss based on one or more downlink reference signals 215. Additionally or alternatively, UE 115-a may receive an indication of the default path loss (e.g., in an RRC, MAC-CE, or DCI message). Additionally or alternatively, UE 115-a may assume a default path loss (e.g., path loss is 0).

[0126] In some examples, UE 115-a may use the same uplink path loss reference signal 215 to determine the transmit power of PUSCH, PUCCH, and SRS. In some examples, UE 115-a may use a different uplink path loss reference signal 215 for each of PUSCH, PUCCH, and SRS. In some examples, UE 115-a may receive indications of multiple uplink path loss reference signals 215 (e.g., via RRC), and may receive indications of a selected uplink path loss reference signal 215 among the multiple uplink path loss reference signals 215 (e.g., via MAC-CE or DCI).

[0127] Figure 3 An example of a time slot diagram 300 supporting uplink power control for uplink-intensive deployment scenarios, according to one or more aspects of this disclosure, is shown. The time slot diagram 300 may implement, or be implemented by, aspects of wireless communication system 100 or wireless communication system 200. For example, the time slot diagram 300 may be implemented by UE 115 and one or more network entities 105 (which may be as described in reference...) Figure 1 (Example of the corresponding device described) implementation.

[0128] In some examples, to determine the uplink transmit power for uplink message 320 destined for uplink dedicated network entity 105, UE 115 may receive one or more MAC-CE messages 315 indicating transmit power information. That is, central network entity 105 may receive indications of channel information (e.g., RSRP, path loss) associated with the uplink reference signal from UE 115 to uplink dedicated network entity 105. Central network entity 105 may indicate one or more TPC parameters in one or more MAC-CE messages 315 for UE 115 to use for one or more uplink messages destined for uplink dedicated network entity 105 (e.g., PUSCH, PUCCH, SRS). One or more TPC parameters may include, for example, closed-loop power control parameters (e.g., ...). or ), open-loop power control parameters (e.g., ) or path loss offset (e.g., path loss relative to the downlink reference signal).

[0129] A TPC command may be associated with multiple uplink channels or signals, or may depend on an uplink channel or uplink signal (e.g., the same or different TPC commands for PDCCH, PUSCH, and SRS messages). In some examples, a TPC command may be absolute or cumulative. For example, a TPC command may indicate the absolute value of an associated TPC parameter or an offset from a previous value of the TPC parameter. UE 115 may receive an indication of whether a TPC command is cumulative (e.g., whether cumulativeness is enabled). In some examples, a TPC command may apply a number of X time slots after sending an acknowledgment message (e.g., HARQ-ACK) for MAC-CE 315.

[0130] In some examples, UE 115 may receive DCI 310 (e.g., scheduling DCI, UE-specific DCI, GC DCI) indicating TPC commands (e.g., closed-loop power control parameters). In some examples, UE 115 may not receive DCI 310 indicating TPC commands. In some examples, UE 115 may receive control messages (e.g., RRC messages) indicating whether UE 115 will receive DCI 310 indicating TPC commands (e.g., indicating whether DCI-based TPC is enabled). DCI 310 may indicate the closed-loop index to which the TPC commands in DCI 310 can be applied.

[0131] In some examples, MAC-CE message 315 can indicate closed-loop control parameters. This is especially relevant if multiple power control adjustment states or closed-loop indices are configured for PUSCH, PUCCH, and / or SRS at UE 115-a. lThen, MAC-CE message 315 can further indicate the closed-loop index to which the closed-loop control parameters can be applied. As an illustrative example, if cumulative and DCI-based TPC is enabled, UE 115 can receive a first DCI 310-a associated with closed-loop index 0 via time slot 305-a (e.g., scheduling an uplink message 320-a, such as PUSCH, PUCCH, or SRS, associated with closed-loop index 0 in time slot 305-c). The first DCI 310-a can indicate a closed-loop power control parameter of -2. UE 115 can receive MAC-CE 315-a associated with closed-loop index 0 in time slot 305-a. MAC-CE 315-a can indicate an update of +8 to the closed-loop power control parameters (e.g., to be applied after X time slots, for example, starting at time slot 305-e). In time slot 305-c, UE 115 can use a closed-loop power control parameter of -2 (e.g., the closed-loop power control parameter indicated in the first DCI 310-a, since MAC-CE 315-a may not be applied before time slot 305-e) to send uplink message 320-a.

[0132] In time slot 305-d, UE 115 may receive a second DCI 310-a associated with closed-loop index 0 (e.g., scheduling a second uplink message 320-a associated with closed-loop index 0 in time slot 305-f). The second DCI 310-a may indicate a closed-loop power control parameter change of +2. In time slot 305-f, UE 115 may transmit the second uplink message 320-a using a closed-loop power control parameter of -2+8+2=8 (e.g., the accumulation of the closed-loop power control parameters indicated by DCI 310-a and MAC-CE 315-a).

[0133] In time slot 305-b, UE 115 may receive a first DCI 310-b associated with closed-loop index 1 (e.g., scheduling a first uplink message 320-b associated with closed-loop index 1 in time slot 305-d). The first DCI 310-b may indicate a closed-loop power control parameter of -4. Therefore, in time slot 305-d, UE 115 may use a closed-loop power control parameter of -4 to send the first uplink message 320-b. In time slot 305-e, UE 115 may receive a MAC-CE message 315-b associated with closed-loop index 1, which indicates a closed-loop parameter change of -6 (e.g., starting at time slot 305-h).

[0134] In time slot 305-f, UE 115 may receive a second DCI 310-b associated with closed-loop index 1 (e.g., scheduling a second uplink message 320-b associated with closed-loop index 1 in time slot 305-g). The second DCI 310-b may indicate a closed-loop power control parameter of -2. In time slot 305-g, UE 115 may use a closed-loop power control parameter of -4-2=-6 (e.g., an accumulation of the closed-loop power control parameter indicated in DCI 310-b, since MAC-CE 315-b may not be applied before time slot 305-h) to send the second uplink message 320-b.

[0135] In time slot 305-g, UE 115 may also receive a third DCI 310-b (e.g., a third uplink message 320-b scheduled in time slot 305-h associated with closed-loop index 1). The third DCI 310-b may indicate a closed-loop power control parameter change of +2. In time slot 305-h, UE 115 may use a closed-loop power control parameter of -4-6-2+2=-10 (e.g., the accumulation of the closed-loop power control parameters indicated by DCI 310-b and MAC-CE 315-b) to send the third uplink message 320-b.

[0136] Referring to the closed-loop power control parameters in the illustrative examples above, if accumulation is disabled, each MAC-CE315 and DCI 310 can indicate an absolute closed-loop power control parameter value instead of a change in the closed-loop power control parameter. For example, UE115 can use a closed-loop power control parameter of -2 indicated by the second DCI 310-b instead of the accumulation of the closed-loop power control parameter indicated by DCI 310-b to send the second uplink message 320-b.

[0137] Referring to the closed-loop power control parameters in the illustrative examples above, if DCI-based TPC is disabled, UE 115 can use a TPC command indicated via MAC-CE 315 (e.g., instead of a TPC command indicated via DCI 310). For example, UE 115 can use a closed-loop power control parameter of 0 (e.g., the default closed-loop power control parameter) to send the first uplink message 320-a because UE 115 may not have received a TPC command yet. UE 115 can use a closed-loop power control parameter of +8 indicated by MAC-CE 315-a (e.g., instead of the accumulation of closed-loop power control parameters indicated by DCI 310-a and MAC-CE 315-a) to send the second uplink message 320-a.

[0138] In some examples, the TPC command in MAC-CE 315 can indicate a path loss offset or an update to the path loss offset (e.g., associated with an ID or information element). The path loss offset can be, for example, an offset of the path loss associated with a downlink reference signal in a set of path loss reference signals. In some examples, the TPC command in MAC-CE can indicate open-loop power control parameters. Or to Updates to values ​​(e.g., those associated with IDs or information elements). Path loss offset or It can be associated with the following: TCI state ID (e.g., for the uplink unified TCI framework); path loss reference signal ID (e.g., for a unified TCI state of...). pathlossReferenceRS-Id-r17 Or for non-unified TCI frameworks pusch-PathlossReferenceRS-Id , pucch-PathlossReferenceRS-Id or SRS- PathlossReferenceRS-Id ); Open-loop power control parameter set (e.g., for a unified TCI framework) ul- powercontrolId-r17 Or for non-unified TCI frameworks p0-PUSCH-AlphaSetId , p0-PUCCH-Id or srs- ResourceSetId ); or a resource set (e.g., an SRS resource set or a PUCCH resource set). Additionally or alternatively, path loss offset or It can be associated with the serving cell ID or BWP ID to which the UE 115 applies the path loss offset update. The UE 115 can receive the associated ID via MAC-CE 315.

[0139] UE 115 can apply the path loss offset value or within X time slots after sending an acknowledgment message (e.g., HARQ-ACK) for MAC-CE 315. As described in the example of closed-loop power control parameters above. When the TPC command indicates the path loss offset value or At this time, DCI-based TPC commands can be enabled or disabled, as described in the closed-loop power control parameter example above.

[0140] In such examples, the path loss offset indicated by the TPC or This can be absolute or relative (e.g., as described above in the reference to closed-loop power control parameters). In some examples, UE 115 may receive an indication of the path loss offset indicated via TPC or This is an absolute or relative configuration message (e.g., via RRC). In some examples, if the path loss offset or It is relative, path loss offset or The path loss offset relative to the last received value associated with the ID or Value, or offset relative to the initial path loss associated with the ID or Value. In some examples, UE115 may receive an indication of path loss offset or Is it relative to the initial or default path loss offset or The value is still the path loss offset of the last received value or Configuration messages for values ​​(e.g., via RRC).

[0141] For example, UE 115 can receive parameters indicating the initial path loss offset value. PL-OFFSET-Value UE 115 can receive parameters in the following information elements. PL-OFFSET-Value :exist TCI-State In information elements (e.g., for a unified TCI state framework, if path loss offset is associated with uplink or joint TCI state); in PL-ReferenceRS In information elements (e.g., if the path loss offset is associated with the path loss reference signal); or associated with the open-loop power control parameter set or SRS resource set (e.g., for a unified TCI state framework in ul-powercontrolId-r17 In information elements, or for non-uniform TCI state frameworks p0-PUSCH-AlphaSetId , p0-PUCCH-Id or srs- ResourceSetId (In information elements).

[0142] In some examples, if the TPC command indicates a path loss offset relative to the path loss of the downlink reference signal, the UE 115 may receive an indication of the associated downlink reference signal via MAC-CE 315. In some examples, the UE 115 may be configured using one or more predefined rules for determining the associated downlink reference signal. For example, the associated downlink reference signal may be a path loss reference signal with the lowest or highest path loss reference signal ID, a path loss reference signal with the lowest or highest path loss value, or a path loss reference signal with the lowest or highest TCI state in a set of downlink reference signals (e.g., a set of active TCI states). In some examples, the UE 115 may monitor indications of the associated downlink reference signal (e.g., in MAC-CE 315), and if the UE 115 does not detect an indication of the associated downlink reference signal, it may determine the associated downlink reference signal based on predefined rules.

[0143] Figure 4An example of a time slot diagram 400 supporting uplink power control for uplink-intensive deployment scenarios, according to one or more aspects of this disclosure, is shown. Time slot diagram 400 may implement aspects of wireless communication system 100, wireless communication system 200, or time slot diagram 300, or may be implemented by these aspects. For example, time slot diagram 400 may be implemented by UE 115 and one or more network entities 105 (which may be as described in reference...) Figure 1 (Example of the corresponding device described) implementation.

[0144] In some examples, to determine the uplink transmit power for uplink message 415 to uplink dedicated network entity 105, UE 115 may receive one or more DCI messages 410 (e.g., scheduling DCI, UE-specific DCI, GC DCI) indicating transmit power information. That is, central network entity 105 may receive indications of channel information (e.g., RSRP, path loss) associated with the uplink reference signal from UE 115 to uplink dedicated network entity 105. Central network entity 105 may indicate one or more TPC parameters (e.g., associated with ID or information elements) in one or more DCI messages 410 for UE 115 to use in one or more uplink messages to uplink dedicated network entity 105 (e.g., PUSCH, PUCCH, SRS). One or more TPC parameters may include, for example, open-loop power control parameters (e.g., ...). Updates to the path loss offset (e.g., the path loss relative to the downlink reference signal).

[0145] For path loss offset or The update can be associated with the following: TCI state ID (e.g., for the uplink unified TCI framework); path loss reference signal ID (e.g., for a unified TCI state of...). pathlossReferenceRS-Id- r17 Or for non-unified TCI frameworks pusch-PathlossReferenceRS-Id , pucch- PathlossReferenceRS-Id or SRS-PathlossReferenceRS-Id ); Open-loop power control parameter set (e.g., for a unified TCI framework) ul-powercontrolId-r17 Or for non-unified TCI frameworks p0-PUSCH- AlphaSetId , p0-PUCCH-Id or srs-ResourceSetId ); or a resource set (e.g., an SRS resource set or a PUCCH resource set). UE 115 may receive the associated ID via GC DCI 410. In some examples, GC DCI 410 may additionally or alternatively be specific to component carriers (CCs). In such examples, UE 115 may receive an indication of the location of each CC.

[0146] right The update of the path loss offset can, for example, be relative to the initial or last received data. Or path loss offset. For example, path loss offset or The update can be relative to the last received path loss offset associated with the ID or Value, or offset relative to the initial path loss associated with the ID or Value. In some examples, UE 115 may receive an indication of path loss offset or Is it relative to the initial or default path loss offset or The value is still the path loss offset of the last received value or The configuration message for the value (e.g., via RRC). In some examples, the update of the path loss offset can be absolute.

[0147] In some examples, if the TPC command indicates a path loss offset relative to the path loss of the downlink reference signal, UE 115 may receive an indication of the associated downlink reference signal via DCI 410. In some examples, UE 115 may be configured using one or more predefined rules for determining the associated downlink reference signal. For example, the associated downlink reference signal may be a path loss reference signal with the lowest or highest path loss reference signal ID, a path loss reference signal with the lowest or highest path loss value, or a path loss reference signal with the lowest or highest TCI state in a set of downlink path loss reference signals (e.g., in a set of active TCI states). In some examples, UE 115 may monitor indications of the associated downlink reference signal (e.g., in DCI 410), and if UE 115 does not detect an indication of the associated downlink reference signal, it may determine the associated downlink reference signal based on predefined rules.

[0148] In some examples, additional DCI-based TPC commands can be enabled or disabled. For example, UE 115 may or may not receive one or more additional TPC commands (e.g., instructions for updating closed-loop power control parameters) via DCI 410. In some examples, UE 115 may receive control messages (e.g., via RRC) indicating whether UE 115 will receive additional TPC commands.

[0149] As an illustrative example, in time slot 405-a, UE 115 may receive the first DCI 410 of the first uplink message 415 (e.g., PUCCH, PUSCH, or SRS) in scheduling time slot 405-b. The first DCI 410 may indicate the ID and path loss offset or Or the initial (e.g., default) path loss offset associated with the ID or Value update. In time slot 405-b, UE 115 can utilize the path loss offset indicated in the first DCI 410 or Use a determined transmit power to send uplink message 415.

[0150] In time slot 405-c, UE 115 may receive a second DCI 410 that schedules a second uplink message 415 in time slot 405-d. The second DCI 410 may indicate a new path loss offset or Or the path loss offset associated with the ID or Value updates. For example, the second DCI 410 could indicate an offset relative to the initial (e.g., default) path loss or The value is either the path loss offset relative to the last received value associated with the ID or Values ​​(e.g., path loss offset received via the first DCI 410) Path loss offset (value) or Value update. In slot 405-d, UE 115 may update the value at least in part based on the path loss offset indicated via the second DCI 410 or The value is used to send the second uplink message 415.

[0151] Figure 5 An example of a process flow 500 supporting uplink power control for uplink-intensive deployment scenarios, according to one or more aspects of this disclosure, is shown. Process flow 500 may implement, or be implemented by, aspects of wireless communication system 100, wireless communication system 200, time slot diagram 300, or time slot diagram 400. For example, process flow 500 may include UE 115 (e.g., UE 115-b) and one or more network entities 105 (e.g., uplink dedicated network entity 105-d, central network entity 105-e), which may be as described in reference... Figure 1 Examples of the corresponding devices described.

[0152] In the following description of process flow 500, operations between UE115-b, network entity 105-d, and network entity 105-e may be transmitted in a different order than the example order shown. Some operations may also be omitted from process flow 500, and other operations may be added to process flow 500. Furthermore, although some operations or signaling are shown to occur at different times for discussion purposes, these operations may actually occur simultaneously.

[0153] In some examples, at 505, UE 115-b may receive a set of downlink path loss reference signals from central network entity 105-e. In some examples, UE 115-b may determine the path loss associated with each downlink path loss reference signal in the set of downlink path loss reference signals. For example, UE 115-b may measure the RSRP associated with each downlink path loss reference signal in the set of downlink path loss reference signals.

[0154] At 510, UE 115-b may transmit one or more uplink reference signals to uplink dedicated network entity 105-d. Uplink dedicated network entity 105-d may determine the path loss associated with each uplink reference signal in the set of uplink reference signals. For example, uplink dedicated network entity 105-d may measure the RSRP associated with each uplink reference signal in the set of uplink reference signals.

[0155] In some examples, at 515, the uplink dedicated network entity 105-d may send an indication to the central network entity 105-e of channel information associated with the uplink reference signal set. For example, the uplink dedicated network entity 105-d may indicate the RSRP or path loss associated with the uplink reference signal set.

[0156] In some examples, at 520, the central network entity 105-e may indicate to the UE 115-b control information associated with determining the transmission power for one or more uplink messages to the dedicated uplink network entity 105-d. In some examples, the control information may include configuration or indication of downlink path loss reference signals from a set of downlink path loss reference signals. In some examples, the control information may indicate whether the TPC information is absolute or relative (e.g., relative to one or more last received or initial TPC information messages). In some examples, the control information may indicate an initial or default TPC value. In some examples, the control information may indicate whether the UE will receive one or more DCI messages that include additional TPC information. The control information may be in MAC-CE, RRC, or DCI messages.

[0157] In some examples, at 525, UE 115-b may receive DCI messages from central network entity 105-e. DCI messages may be, for example, scheduling DCI or GC DCI. DCI messages may indicate TPC commands for one or more uplink messages. In some examples, DCI messages may not indicate TPC commands (e.g., based on control information).

[0158] At 530, UE 115-b may receive a MAC-CE message from central network entity 105-e including TPC information for one or more uplink messages. The TPC information may include one or more of the following: updates to closed-loop power control parameters (e.g., and a closed-loop index associated with the TPC), updates to open-loop power control parameters, or updates to path loss offset parameters, wherein the path loss offset parameter is an offset from the path loss associated with a downlink reference signal. In some examples, the downlink reference signal may be a downlink reference signal indicated via control information. In some examples, the downlink reference signal may be a downlink reference signal from the set of downlink reference signals associated with the highest or lowest path loss reference signal ID, or the highest or lowest path loss, and the highest or lowest TCI state from the set of active TCI states.

[0159] In some examples, the MAC-CE message may indicate an ID associated with TPC information. This ID may be one or more of the following: an ID used for TCI status, an uplink or downlink path loss reference signal, an open-loop power control parameter set, a BWP, a serving cell, an SRS resource set, or a PUCCH resource set.

[0160] In some examples, TPC information may be specific to an uplink channel or signal, or it may be shared across multiple uplink channels or signals. In some examples, TPC information may be absolute TPC information, or it may be an update (e.g., an offset) to the last received or initial TPC information associated with the ID (e.g., based on control information). For example, TPC information may be an offset relative to TPC information included in the DCI, or an offset relative to an initial or default TPC value.

[0161] At 535, UE 115-b may transmit one or more uplink messages to uplink dedicated network entity 105-d. UE 115-b may transmit one or more uplink messages using transmit power determined based on TPC information in MAC-CE messages (e.g., and DCI messages). The one or more uplink messages may include one or more of PUSCH, PUCCH, or SRS.

[0162] Figure 6An example of a process flow 600 supporting uplink power control for uplink-intensive deployment scenarios, according to one or more aspects of this disclosure, is shown. Process flow 600 may implement, or be implemented by, aspects of wireless communication system 100, wireless communication system 200, time slot diagram 300, time slot diagram 400, or process flow 500. For example, process flow 600 may include UE 115 (e.g., UE 115-c) and one or more network entities 105 (e.g., uplink dedicated network entity 105-f, central network entity 105-g), which may be as described in reference... Figure 1 Examples of the corresponding devices described.

[0163] In the following description of process flow 600, operations between network entity 105-f, network entity 105-g, and UE 115-c may be sent in a different order than the example order shown. Some operations may also be omitted from process flow 600, and other operations may be added to process flow 600. Furthermore, although some operations or signaling are shown to occur at different times for discussion purposes, these operations may actually occur simultaneously.

[0164] In some examples, at 605, UE 115-c may receive a set of downlink path loss reference signals from central network entity 105-g. In some examples, UE 115-c may determine the path loss associated with each downlink path loss reference signal in the set of downlink path loss reference signals. For example, UE 115-c may measure the RSRP associated with each downlink path loss reference signal in the set of downlink path loss reference signals.

[0165] At 610, UE 115-c may send one or more uplink path loss reference signals to uplink dedicated network entity 105-f. Uplink dedicated network entity 105-f may determine the path loss associated with each uplink path loss reference signal in the set of uplink path loss reference signals. For example, uplink dedicated network entity 105-f may measure the RSRP associated with each uplink path loss reference signal in the set of uplink path loss reference signals.

[0166] In some examples, at 615, the uplink dedicated network entity 105-f may send an indication to the central network entity 105-g of channel information associated with the uplink path loss reference signal set. For example, the uplink dedicated network entity 105-f may indicate the RSRP or path loss associated with the uplink path loss reference signal set.

[0167] In some examples, at 620, the central network entity 105-g may indicate to the UE 115-c control information associated with determining the transmission power for one or more uplink messages to the uplink dedicated network entity 105-f. In some examples, the control information may include configuration or indication of downlink path loss reference signals from a set of downlink path loss reference signals. In some examples, the control information may indicate whether the TPC information is absolute or relative (e.g., relative to one or more last received or initial TPC information messages). In some examples, the control information may indicate initial or default TPC parameter values. In some examples, the control information may indicate whether the UE will receive one or more additional DCI messages that include additional TPC information. The control information may be in MAC-CE, RRC, or DCI messages.

[0168] At 625, UE 115-c can receive DCI messages from central network entity 105-g. DCI messages can be, for example, scheduled DCI, UE-specific DCI, or GC DCI. DCI messages can indicate TPC commands for one or more uplink messages. For example, a DCI message can indicate an update to the open-loop power control parameters relative to previous open-loop power control parameters, or an update to the path loss offset parameters from the path loss offset associated with a downlink reference signal. In some examples, the downlink reference signal can be a downlink reference signal associated with the highest or lowest path loss reference signal ID in the set of downlink reference signals, or the highest or lowest path loss, and the highest or lowest TCI state in the set of active TCI states.

[0169] In some examples, the DCI message may indicate an ID associated with the TPC information. This ID may be one or more of the following: an ID used for TCI status, an uplink or downlink path loss reference signal, an open-loop power control parameter set, a BWP, a serving cell, an SRS resource set, or a PUCCH resource set. In some examples, the TPC information may be specific to an uplink channel or signal, or shared across multiple uplink channels or signals. In some examples, the TPC information may be absolute TPC information, or it may be an update (e.g., an offset) to the last received or initial TPC information associated with the ID (e.g., based on control information).

[0170] In some examples, at 630, UE 115-c may receive an additional DCI message from central network entity 105-g. The additional DCI message may be, for example, a scheduling DCI or a GC DCI. The additional DCI message may indicate an additional TPC command for one or more uplink messages. In some examples, the DCI message may not indicate an additional TPC command (e.g., based on control information).

[0171] At 635, UE 115-c may transmit one or more uplink messages to uplink dedicated network entity 105-f. UE 115-c may transmit one or more uplink messages using transmit power determined based on TPC information in DCI messages (e.g., and supplementary DCI messages). The one or more uplink messages may include one or more of PUSCH, PUCCH, or SRS.

[0172] Figure 7 An example of a process flow 700 supporting uplink power control for uplink-intensive deployment scenarios according to one or more aspects of this disclosure is shown. Process flow 700 may implement, or be implemented by, aspects of wireless communication system 100, wireless communication system 200, time slot diagram 300, time slot diagram 400, process flow 500, or process flow 600. For example, process flow 700 may include UE 115 (e.g., UE 115-d) and one or more network entities 105 (e.g., uplink dedicated network entity 105-h, central network entity 105-i), which may be as referenced... Figure 1 Examples of the corresponding devices described.

[0173] In the following description of process flow 700, operations between network entity 105-h, network entity 105-i, and UE 115-d may be sent in a different order than the example order shown. Some operations may also be omitted from process flow 700, and other operations may be added to process flow 700. Furthermore, although some operations or signaling are shown to occur at different times for discussion purposes, these operations may actually occur simultaneously.

[0174] In some examples, at 705, UE 115-d may receive a set of downlink path loss reference signals from central network entity 105-i. In some examples, UE 115-d may determine the path loss associated with each downlink path loss reference signal in the set of downlink path loss reference signals. For example, UE 115-d may measure the RSRP associated with each downlink path loss reference signal in the set of downlink path loss reference signals.

[0175] At 710, UE 115-d may send one or more uplink path loss reference signals to uplink dedicated network entity 105-h. Uplink dedicated network entity 105-h may determine the path loss associated with each uplink path loss reference signal in the set of uplink path loss reference signals. For example, uplink dedicated network entity 105-h may measure the RSRP associated with each uplink path loss reference signal in the set of uplink path loss reference signals.

[0176] In some examples, at 715, the uplink dedicated network entity 105-h may send an indication to the central network entity 105-i of channel information associated with the uplink path loss reference signal set. For example, the uplink dedicated network entity 105-h may indicate the RSRP associated with the uplink path loss reference signal set.

[0177] In some examples, at 720, the central network entity 105-i may indicate to the UE 115-d control information associated with determining the transmission power for one or more uplink messages to the uplink dedicated network entity 105-h. In some examples, the control information may include configuration or indication of downlink path loss reference signals from a set of downlink path loss reference signals. In some examples, the control information may include configuration or indication of uplink path loss reference signals from a set of uplink path loss reference signals. In some examples, the control information may indicate a default path loss value for the UE 115-d to use for one or more uplink messages. In some examples, the control information may indicate that the uplink path loss reference signals are associated with one or more PUCCH messages, one or more PUSCH messages, or one or more SRSs.

[0178] In some examples, at 725, UE 115-d can use a default path loss value to send one or more uplink messages to calculate the transmission power of those one or more uplink messages. The default path loss value can be the path loss associated with an indicated downlink reference signal, a default path loss value indicated via control information, or a default value of 0.

[0179] At 730, UE 115-d can receive an indication of the RSRP associated with the indicated uplink path loss reference signal from the central network entity 105-e. UE 115-d can calculate the uplink path loss associated with the uplink path loss reference signal based on the indicated RSRP. UE 115-d can receive the RSRP via DCI, MAC-CE, or RRC messages.

[0180] At 735, UE 115-d may transmit one or more uplink messages to uplink dedicated network entity 105-h. UE 115-d may transmit one or more uplink messages using transmit power determined based on the calculated uplink path loss. The one or more uplink messages may include one or more of PUSCH, PUCCH, or SRS messages (e.g., as indicated in the control information).

[0181] Figure 8 A block diagram 800 of a device 805 supporting uplink power control for uplink-intensive deployment scenarios according to one or more aspects of this disclosure is shown. Device 805 may be an example of various aspects of a UE 115 as described herein. Device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. Device 805, or one or more components of device 805 (e.g., receiver 810, transmitter 815, and communication manager 820), may include at least one processor that can be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0182] Receiver 810 may provide components for receiving information (such as packets, user data, control information, or combinations thereof) associated with various information channels (e.g., control channels, data channels, information channels related to uplink power control for uplink-intensive deployment scenarios). The information may be passed to other components of device 805. Receiver 810 may utilize a single antenna or a collection of antennas.

[0183] Transmitter 815 may provide components for transmitting signals generated by other components of device 805. For example, transmitter 815 may transmit information associated with various information channels, such as control channels, data channels, and information channels related to uplink power control for uplink-intensive deployment scenarios, including packets, user data, control information, or any combination thereof. In some examples, transmitter 815 may be co-located with receiver 810 in a transceiver module. Transmitter 815 may utilize a single antenna or a collection of multiple antennas.

[0184] The communication manager 820, receiver 810, transmitter 815, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of uplink power control for uplink-intensive deployment scenarios as described herein. For example, the communication manager 820, receiver 810, transmitter 815, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0185] In some examples, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0186] Additionally or alternatively, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).

[0187] In some examples, the communication manager 820 may be configured to use a receiver 810, a transmitter 815, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 820 may receive information from the receiver 810, transmit information to the transmitter 815, or be integrated with the receiver 810, the transmitter 815, or both to acquire information, output information, or perform various other operations as described herein.

[0188] The communication manager 820 may support wireless communication according to examples disclosed herein. For example, the communication manager 820 may be capable of, configured to, or operable to support components for receiving MAC-CE messages that include TPC information for one or more uplink messages. The communication manager 820 may be capable of, configured to, or operable to support components for transmitting one or more uplink messages based on TPC information.

[0189] Additionally or alternatively, the communication manager 820 may support wireless communication according to examples disclosed herein. For example, the communication manager 820 may be capable of, configured to, or operable to support components for receiving DCI messages indicating TPC parameters for one or more uplink messages, wherein the TPC parameters include either an update to open-loop power control parameters relative to previous open-loop power control parameters or an update to path loss offset parameters, wherein the path loss offset parameters are offsets from path loss associated with a downlink reference signal. The communication manager 820 may be capable of, configured to, or operable to support components for transmitting one or more uplink messages based on the TPC parameters.

[0190] Additionally or alternatively, the communication manager 820 may support wireless communication according to examples disclosed herein. For example, the communication manager 820 may be capable of, configured to, or operable to support components for transmitting an uplink reference signal. The communication manager 820 may be capable of, configured to, or operable to support components for receiving an indication of the reference signal received power associated with the uplink reference signal. The communication manager 820 may be capable of, configured to, or operable to support components for transmitting one or more uplink messages, wherein the transmission power associated with one or more uplink messages is based on the reference signal received power.

[0191] By including or configuring a communication manager 820 according to an example as described herein, device 805 (e.g., controlling receiver 810, transmitter 815, communication manager 820 or a combination thereof, or at least one processor otherwise coupled to them) can support techniques for determining transmit power for dense uplink deployments, which can result in reduced power consumption and improved communication reliability.

[0192] Figure 9 A block diagram 900 of a device 905 supporting uplink power control for uplink-intensive deployment scenarios according to one or more aspects of this disclosure is shown. Device 905 may be an example of aspects of device 805 or UE 115 as described herein. Device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Device 905, or one or more components of device 905 (e.g., receiver 910, transmitter 915, and communication manager 920), may include at least one processor coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0193] Receiver 910 may provide components for receiving information (such as packets, user data, control information, or combinations thereof) associated with various information channels (e.g., control channels, data channels, information channels related to uplink power control for uplink-intensive deployment scenarios). The information may be passed to other components of device 905. Receiver 910 may utilize a single antenna or a collection of antennas.

[0194] Transmitter 915 may provide components for transmitting signals generated by other components of device 905. For example, transmitter 915 may transmit information associated with various information channels, such as control channels, data channels, and information channels related to uplink power control for uplink-intensive deployment scenarios, including packets, user data, control information, or any combination thereof. In some examples, transmitter 915 may be co-located with receiver 910 in a transceiver module. Transmitter 915 may utilize a single antenna or a collection of multiple antennas.

[0195] Device 905 or its various components may be examples of parts used to perform various aspects of uplink power control for uplink-intensive deployment scenarios as described herein. For example, communication manager 920 may include TPC manager 925, uplink message manager 930, uplink reference signal manager 935, RSRP manager 940, or any combination thereof. Communication manager 920 may be examples of aspects of communication manager 820 as described herein. In some examples, communication manager 920 or its various components may be configured to use receiver 910, transmitter 915, or both, or otherwise cooperate with them to perform various operations (e.g., receive, acquire, monitor, output, transmit). For example, communication manager 920 may receive information from receiver 910, transmit information to transmitter 915, or be integrated in combination with receiver 910, transmitter 915, or both to acquire information, output information, or perform various other operations as described herein.

[0196] The communication manager 920 can support wireless communication according to the examples disclosed herein. The TPC processor 925 is capable of, configured to, or operable to support components for receiving MAC-CE messages that include TPC information for one or more uplink messages. The uplink message manager 930 is capable of, configured to, or operable to support components for transmitting one or more uplink messages based on TPC information.

[0197] Additionally or alternatively, the communication manager 920 may support wireless communication according to examples disclosed herein. The TPC manager 925 is capable of, configured to, or operable to support components for receiving DCI messages indicating TPC parameters for one or more uplink messages, wherein the TPC parameters include either an update to open-loop power control parameters relative to previous open-loop power control parameters or an update to path loss offset parameters, wherein the path loss offset parameters are offsets from the path loss associated with a downlink reference signal. The uplink message manager 930 is capable of, configured to, or operable to support components for transmitting one or more uplink messages based on TPC parameters.

[0198] Additionally or alternatively, the communication manager 920 may support wireless communication according to examples disclosed herein. The uplink reference signal manager 935 is capable of, configured to, or operable to support components for transmitting uplink reference signals. The RSRP manager 940 is capable of, configured to, or operable to support components for receiving an indication of the reference signal received power associated with the uplink reference signal. The uplink message manager 930 is capable of, configured to, or operable to support components for transmitting one or more uplink messages, wherein the transmission power associated with one or more uplink messages is based on the reference signal received power.

[0199] Figure 10 A block diagram 1000 is shown of a communication manager 1020 supporting uplink power control for uplink-intensive deployment scenarios according to one or more aspects of this disclosure. The communication manager 1020 may be an example of a communication manager 820, a communication manager 920, or aspects thereof as described herein. The communication manager 1020 or its various components may be examples of parts for performing various aspects of uplink power control for uplink-intensive deployment scenarios as described herein. For example, the communication manager 1020 may include a TPC manager 1025, an uplink message manager 1030, an uplink reference signal manager 1035, an RSRP manager 1040, a DCI-based TPC manager 1045, a path loss offset manager 1050, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0200] The communication manager 1020 can support wireless communication according to the examples disclosed herein. The TPC manager 1025 is capable of, configured to, or operable to support components for receiving MAC-CE messages that include TPC information for one or more uplink messages. The uplink message manager 1030 is capable of, configured to, or operable to support components for sending one or more uplink messages based on TPC information.

[0201] In some examples, TPC information includes updates to the closed-loop power control parameters.

[0202] In some examples, the TPC information also includes a closed-loop index associated with the TPC information.

[0203] In some examples, the TPC information includes updates to the path loss offset parameter. In some examples, the path loss offset parameter is an offset from the path loss associated with the downlink reference signal.

[0204] In some examples, the path loss offset manager 1050 is capable of, configured to, or able to operate to support components for receiving configurations or indications of downlink reference signals associated with path loss offset parameters.

[0205] In some examples, the downlink reference signal is a downlink path loss reference signal within a set of downlink path loss reference signals. In some examples, the downlink reference signal is associated with: the lowest path loss reference signal identifier in the set of downlink path loss reference signals, the highest path loss reference signal identifier in the set of downlink path loss reference signals, the lowest path loss value in the set of downlink path loss reference signals, the highest path loss value in the set of downlink path loss reference signals, the downlink path loss reference signal associated with the lowest TCI state in the set of active TCI states associated with the set of downlink path loss reference signals, or the downlink path loss reference signal associated with the highest TCI state in the set of active TCI states associated with the set of downlink path loss reference signals.

[0206] In some examples, TPC information includes updates to the open-loop power control parameters.

[0207] In some examples, TPC information is shared by a set of multiple uplink channels or uplink signals, or is specific to a single uplink channel or uplink signal.

[0208] In some examples, TPC information includes an indication of the absolute TPC parameter value or an indication of the offset from the previous TPC parameter value.

[0209] In some examples, the TPC manager 1025 is capable of, configured to, or operable to support components for receiving RRC messages that indicate TPC information, including either an indication of an absolute TPC parameter value or an indication of an offset from a previous TPC parameter value.

[0210] In some examples, TPC information is associated with an identifier. In some examples, the previous TPC parameter value is either the initial TPC parameter value associated with the identifier or the last received TPC parameter value associated with the identifier.

[0211] In some examples, the TPC manager 1025 is capable of, configured to, or able to operate to support components for receiving control messages indicating initial TPC parameter values.

[0212] In some examples, the MAC-CE message indicates the identifier of the TCI state associated with the TPC information, the path loss reference signal, the open-loop power control parameter set, the bandwidth portion, the serving cell, the sounding reference signal resource set, the physical uplink control channel resource, or some combination thereof.

[0213] In some examples, the DCI-based TPC manager 1045 is capable of, configured to, or able to operate to support components for receiving RRC messages that indicate whether the UE will receive one or more DCI messages including additional TPC information.

[0214] In some examples, the DCI-based TPC manager 1045 is capable of, configured to, or operable to support components for receiving one or more DCI messages including additional TPC information, wherein sending one or more uplink messages includes sending one or more uplink messages based on the additional TPC information. In some examples, the uplink message manager 1030 is capable of, configured to, or operable to support components for sending one or more uplink messages based on additional TPC information.

[0215] In some examples, one or more uplink messages include one or more physical uplink control channel messages, one or more physical uplink shared channel messages, one or more probe reference signals, or some combination thereof.

[0216] Additionally or alternatively, the communication manager 1020 may support wireless communication according to examples disclosed herein. In some examples, the TPC manager 1025 is capable of, configured to, or operable to support components for receiving DCI messages indicating TPC parameters for one or more uplink messages, wherein the TPC parameters include either an update to open-loop power control parameters relative to previous open-loop power control parameters or an update to path loss offset parameters, wherein the path loss offset parameters are offsets from the path loss associated with a downlink reference signal. In some examples, the uplink message manager 1030 is capable of, configured to, or operable to support components for transmitting one or more uplink messages based on TPC parameters.

[0217] In some examples, the path loss offset manager 1050 is capable of, configured to, or able to operate to support components for receiving configurations or indications of downlink reference signals.

[0218] In some examples, the downlink reference signal is a downlink path loss reference signal within a set of downlink path loss reference signals. In some examples, the downlink reference signal is associated with: the lowest path loss reference signal identifier in the set of downlink path loss reference signals, the highest path loss reference signal identifier in the set of downlink path loss reference signals, the lowest path loss value in the set of downlink path loss reference signals, the highest path loss value in the set of downlink path loss reference signals, the downlink path loss reference signal associated with the lowest TCI state in the set of active TCI states associated with the set of downlink path loss reference signals, or the downlink path loss reference signal associated with the highest TCI state in the set of active TCI states associated with the set of downlink path loss reference signals.

[0219] In some examples, updating the path loss offset parameter includes an indication of the absolute path loss offset value or an indication of the offset from the previous path loss offset value.

[0220] In some examples, the path loss offset manager 1050 is capable of, configured to, or able to operate to support components for receiving RRC messages that indicate the offset, including an indication of an absolute path loss offset value or an indication of an offset relative to a previous path loss offset value.

[0221] In some examples, updates to the open-loop power control parameters are associated with an identifier. In some examples, previous open-loop power control parameters include either the initial open-loop power control parameters associated with the identifier or the last received open-loop power control parameters associated with the identifier.

[0222] In some examples, the DCI message indicates the identifier of the TCI state associated with the TPC parameters, the path loss reference signal, the open-loop power control parameter set, the bandwidth portion, the serving cell, the sounding reference signal resource set, the physical uplink control channel resource, or some combination thereof.

[0223] In some examples, the DCI-based TPC manager 1045 is capable of, configured to, or able to operate to support components for receiving RRC messages that indicate whether the UE will receive one or more additional DCI messages including additional TPC information.

[0224] In some examples, the DCI-based TPC manager 1045 is capable of, configured to, or operable to support components for receiving one or more additional DCI messages including additional TPC information, wherein sending one or more uplink messages includes sending one or more uplink messages based on the additional TPC information. In some examples, the DCI-based TPC manager 1045 is capable of, configured to, or operable to support components for sending one or more uplink messages based on additional TPC information.

[0225] In some examples, DCI messages are scheduled DCI or group public DCI.

[0226] In some examples, one or more uplink messages include one or more physical uplink control channel messages, one or more physical uplink shared channel messages, one or more probe reference signals, or some combination thereof.

[0227] Additionally or alternatively, the communication manager 1020 may support wireless communication according to examples disclosed herein. The uplink reference signal manager 1035 is capable of, configured to, or operable to support components for transmitting uplink reference signals. The RSRP manager 1040 is capable of, configured to, or operable to support components for receiving an indication of the reference signal received power associated with the uplink reference signal. In some examples, the uplink message manager 1030 is capable of, configured to, or operable to support components for transmitting one or more uplink messages, wherein the transmission power associated with one or more uplink messages is based on the reference signal received power.

[0228] In some examples, the RSRP manager 1040 is capable of, configured to, or able to operate to support components for calculating uplink path loss associated with an uplink reference signal based on the reference signal received power, wherein the transmit power is based on the uplink path loss.

[0229] In some examples, one or more uplink messages include one or more physical uplink control channel messages, one or more physical uplink shared channel messages, one or more probe reference signals, or some combination thereof.

[0230] In some examples, the uplink reference signal manager 1035 is capable of, configured to, or operable to support components for receiving indications about the association of uplink reference signals with one or more physical uplink control channel messages, one or more physical uplink shared channel messages, one or more probe reference signals, or some combination thereof.

[0231] In some examples, the uplink reference signal receiver 1035 is capable of, configured to, or operable to support components for receiving control messages indicating the uplink reference signal in the set of uplink reference signals.

[0232] In some examples, the indication of the received power of the reference signal is received via a MAC-CE message or via a DCI message.

[0233] In some examples, the uplink message manager 1030 is capable of, configured to, or able to operate to support components for sending one or more initial uplink messages based on a default path loss value before receiving an indication of the power received for a reference signal.

[0234] In some examples, the path loss offset manager 1050 is capable of, can be configured to, or can operate to support components for determining default path loss values ​​based on path loss associated with a downlink reference signal.

[0235] In some examples, the default path loss value is zero.

[0236] In some examples, the path loss offset manager 1050 is capable of, configured to, or operable to support components for receiving control messages indicating a corresponding default path loss value associated with each uplink reference signal in a set of uplink reference signals, the set of uplink reference signals including the uplink reference signal, wherein the default path loss value is a corresponding default path loss value associated with the uplink reference signal.

[0237] Figure 11A diagram of a system 1100 including device 1105 supporting uplink power control for uplink-intensive deployment scenarios, according to one or more aspects of this disclosure, is shown. Device 1105 may be an example of device 805, device 905, or UE 115 as described herein, or may include components thereof. Device 1105 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 1105 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1120, an input / output (I / O) controller 1110, a transceiver 1115, an antenna 1125, at least one memory 1130, code 1135, and at least one processor 1140. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1145).

[0238] I / O controller 1110 manages the input and output signals of device 1105. I / O controller 1110 can also manage peripheral devices not integrated into device 1105. In some cases, I / O controller 1110 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1110 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Or another known operating system. Additionally or alternatively, the I / O controller 1110 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 1110 may be implemented as part of one or more processors, such as at least one processor 1140. In some cases, a user may interact with the device 1105 via the I / O controller 1110 or via hardware components controlled by the I / O controller 1110.

[0239] In some cases, device 1105 may include a single antenna 1125. However, in other cases, device 1105 may have more than one antenna 1125, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1115 may communicate bidirectionally via one or more antennas 1125 as described herein, a wired or wireless link. For example, transceiver 1115 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1115 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1125 for transmission; and demodulating packets received from one or more antennas 1125. Transceiver 1115, or transceiver 1115 and one or more antennas 1125, may be an example of transmitter 815, transmitter 915, receiver 810, receiver 910, or any combination thereof or components thereof as described herein.

[0240] At least one memory 1130 may include random access memory (RAM) and read-only memory (ROM). At least one memory 1130 may store computer-readable, computer-executable code 1135, including instructions that, when executed by at least one processor 1140, cause device 1105 to perform the various functions described herein. Code 1135 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1135 may not be directly executable by at least one processor 1140, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, among other things, at least one memory 1130 may also include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0241] At least one processor 1140 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 1140 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into at least one processor 1140. At least one processor 1140 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 1130) to cause device 1105 to perform various functions (e.g., functions or tasks supporting uplink power control for uplink-intensive deployment scenarios). For example, device 1105 or components of device 1105 may include at least one processor 1140 and at least one memory 1130 coupled to or coupled to at least one processor 1140, wherein at least one processor 1140 and at least one memory 1130 are configured to perform the various functions described herein. In some examples, at least one processor 1140 may include multiple processors, and at least one memory 1130 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1140 may be a component of a processing system, which may refer to a system of machines, circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1140) and memory circuitry (which may include at least one memory 1130)) or components that receive or obtain input and process such input to produce, generate, or obtain output. The processing system may be configured to perform one or more of the functions described herein. Thus, at least one processor 1140 or a processing system including at least one processor 1140 may be configured, configured to, or operable to cause device 1105 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “configurable to,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1130 or otherwise.

[0242] The communication manager 1120 may support wireless communication according to examples disclosed herein. For example, the communication manager 1120 may be capable of, configured to, or operable to support components for receiving MAC-CE messages that include TPC information for one or more uplink messages. The communication manager 1120 may be capable of, configured to, or operable to support components for transmitting one or more uplink messages based on TPC information.

[0243] Additionally or alternatively, the communication manager 1120 may support wireless communication according to examples disclosed herein. For example, the communication manager 1120 may be capable of, configured to, or operated to support components for receiving DCI messages indicating TPC parameters for one or more uplink messages, wherein the TPC parameters include either an update to open-loop power control parameters relative to previous open-loop power control parameters or an update to path loss offset parameters, wherein the path loss offset parameters are offsets from path loss associated with a downlink reference signal. The communication manager 1120 may be capable of, configured to, or operated to support components for transmitting one or more uplink messages based on the TPC parameters.

[0244] Additionally or alternatively, the communication manager 1120 may support wireless communication according to examples disclosed herein. For example, the communication manager 1120 may be, configured to, or operated to support components for transmitting an uplink reference signal. The communication manager 1120 may be, configured to, or operated to support components for receiving an indication of the reference signal received power associated with the uplink reference signal. The communication manager 1120 may be, configured to, or operated to support components for transmitting one or more uplink messages, wherein the transmission power associated with one or more uplink messages is based on the reference signal received power.

[0245] By including or configuring a communication manager 1120 according to an example as described herein, device 1105 can support techniques for determining transmit power for dense uplink deployments, which may result in improved communication reliability, reduced power consumption, and improved coordination between devices.

[0246] In some examples, the communication manager 1120 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using transceiver 1115, one or more antennas 1125, or any combination thereof, or otherwise cooperating with them. Although the communication manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 may be supported or executed by at least one processor 1140, at least one memory 1130, code 1135, or any combination thereof. For example, code 1135 may include instructions that can be executed by at least one processor 1140 to cause device 1105 to perform various aspects of uplink power control for uplink-intensive deployment scenarios as described herein, or at least one processor 1140 and at least one memory 1130 may be otherwise configured to perform or support such operations individually or jointly.

[0247] Figure 12 A flowchart illustrating a method 1200 for uplink power control in a dense uplink deployment scenario, according to various aspects of this disclosure, is shown. Operation of method 1200 can be implemented by a UE or its components as described herein. For example, operation of method 1200 can be achieved by, as referenced... Figures 1 to 11 The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0248] At 1205, the method may include receiving a MAC-CE message that includes TPC information for one or more uplink messages. The operation of 1205 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1205 may be provided by reference to [reference needed]. Figure 10 The TPC Manager 1025 described is executed.

[0249] At 1210, the method may include sending one or more uplink messages based on TPC information. The operation of 1210 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1210 may be provided by reference to [reference needed]. Figure 10 The described uplink message manager 1030 is executed.

[0250] Figure 13 A flowchart illustrating a method 1300 for uplink power control in a dense uplink deployment scenario, according to various aspects of this disclosure, is shown. Operation of method 1300 can be implemented by a UE or its components as described herein. For example, operation of method 1300 can be achieved by, as referenced... Figures 1 to 11The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0251] At 1305, the method may include receiving a MAC-CE message that includes TPC information for one or more uplink messages. The operation of 1305 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1305 may be provided by reference to [reference needed]. Figure 10 The TPC Manager 1025 described is executed.

[0252] At 1310, the method may include receiving an RRC message indicating whether the UE will receive one or more DCI messages including additional TPC information. Operation of 1310 may be performed according to the examples disclosed herein. In some examples, aspects of operation of 1310 may be provided by reference to [reference needed]. Figure 10 The DCI-based TPC Manager 1045 is described in the description.

[0253] At 1315, the method may include sending one or more uplink messages based on TPC information. The operation of 1315 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1315 may be provided by reference to [reference needed]. Figure 10 The described uplink message manager 1030 is executed.

[0254] Figure 14 A flowchart illustrating a method 1400 for uplink power control in a dense uplink deployment scenario, according to various aspects of this disclosure, is shown. Operation of method 1400 can be implemented by a UE or its components as described herein. For example, operation of method 1400 can be achieved by, as referenced... Figures 1 to 11 The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0255] At 1405, the method may include receiving a DCI message indicating TPC parameters for one or more uplink messages, wherein the TPC parameters include either an update to the open-loop power control parameters relative to previous open-loop power control parameters or an update to path loss offset parameters, wherein the path loss offset parameters are offsets from path loss associated with a downlink reference signal. The operation of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1405 may be provided by reference to... Figure 10 The TPC Manager 1025 described is executed.

[0256] At 1410, the method may include sending one or more uplink messages based on TPC parameters. The operation of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1410 may be provided by reference to [reference needed]. Figure 10 The described uplink message manager 1030 is executed.

[0257] Figure 15 A flowchart illustrating a method 1500 for uplink power control in a dense uplink deployment scenario, according to various aspects of this disclosure, is shown. Operation of method 1500 can be implemented by a UE or its components as described herein. For example, operation of method 1500 can be achieved by, as referenced... Figures 1 to 11 The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0258] At 1505, the method may include receiving a DCI message indicating TPC parameters for one or more uplink messages, wherein the TPC parameters include either an update to the open-loop power control parameters relative to previous open-loop power control parameters or an update to path loss offset parameters, wherein the path loss offset parameters are offsets from the path loss associated with a downlink reference signal. The operation of 1505 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1505 may be provided by reference to... Figure 10 The TPC Manager 1025 described is executed.

[0259] At 1510, the method may include sending one or more uplink messages based on TPC parameters. The operation of 1510 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1510 may be provided by reference to [reference needed]. Figure 10 The described uplink message manager 1030 is executed.

[0260] At 1515, the method may include receiving configuration or indication of a downlink reference signal. The operation of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1515 may be determined by reference to... Figure 10 The described path loss offset manager 1050 is executed.

[0261] Figure 16 A flowchart illustrating a method 1600 for uplink power control in a dense uplink deployment scenario, according to various aspects of this disclosure, is shown. Operation of method 1600 can be implemented by a UE or its components as described herein. For example, operation of method 1600 can be achieved by, as referenced... Figures 1 to 11The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0262] At 1605, the method may include sending an uplink reference signal. The operation of 1605 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1605 may be determined by reference to... Figure 10 The described uplink reference signal manager 1035 is executed.

[0263] At 1610, the method may include receiving an indication of a reference signal received power associated with an uplink reference signal. Operation of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1610 may be determined by reference to... Figure 10 The RSRP manager 1040 described is executed.

[0264] At 1615, the method may include transmitting one or more uplink messages, wherein the transmit power associated with the one or more uplink messages is based on the reference signal receive power. The operation of 1615 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1615 may be determined by reference to... Figure 10 The described uplink message manager 1030 is executed.

[0265] Figure 17 A flowchart illustrating a method 1700 for uplink power control in a dense uplink deployment scenario, according to various aspects of this disclosure, is shown. Operation of method 1700 can be implemented by a UE or its components as described herein. For example, operation of method 1700 can be achieved by, as referenced... Figures 1 to 11 The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0266] At 1705, the method may include sending an uplink reference signal. The operation of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1705 may be determined by reference to... Figure 10 The described uplink reference signal manager 1035 is executed.

[0267] At 1710, the method may include receiving an indication of the reference signal received power associated with the uplink reference signal. Operation of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1710 may be determined by reference to... Figure 10The RSRP manager 1040 described is executed.

[0268] At 1715, the method may include transmitting one or more uplink messages, wherein the transmit power associated with the one or more uplink messages is based on the reference signal receive power. The operation of 1715 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1715 may be determined by reference to... Figure 10 The described uplink message manager 1030 is executed.

[0269] At 1720, the method may include calculating the uplink path loss associated with the uplink reference signal based on the received power of the reference signal, wherein the transmitted power is based on the uplink path loss. The operation of 1720 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1720 may be determined by, as in the reference… Figure 10 The RSRP manager 1040 described is executed.

[0270] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for wireless communication by a UE, the method comprising: receiving a MAC-CE message including TPC information for one or more uplink messages; and transmitting the one or more uplink messages at least in part based on the TPC information.

[0271] Aspect 2: According to the method of aspect 1, the TPC information includes updates to the closed-loop power control parameters.

[0272] Aspect 3: According to the method of aspect 2, the TPC information further includes a closed-loop index associated with the TPC information.

[0273] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the TPC information includes an update of the path loss offset parameter, and wherein the path loss offset parameter is an offset from the path loss associated with the downlink reference signal.

[0274] Aspect 5: According to the method of aspect 4, the method further includes: receiving configuration or indication of the downlink reference signal associated with the path loss offset parameter.

[0275] Aspect 6: The method according to any one of Aspects 4 to 5, wherein the downlink reference signal is a downlink path loss reference signal in a set of downlink path loss reference signals, and the downlink reference signal is associated with: the lowest path loss reference signal ID of the set of downlink path loss reference signals, the highest path loss reference signal ID of the set of downlink path loss reference signals, the lowest path loss value of the set of downlink path loss reference signals, the highest path loss value of the set of downlink path loss reference signals, a downlink path loss reference signal associated with the lowest TCI state in the set of active TCI states associated with the set of downlink path loss reference signals, or a downlink path loss reference signal associated with the highest TCI state in the set of active TCI states associated with the set of downlink path loss reference signals.

[0276] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the TPC information includes updates to the open-loop power control parameters.

[0277] Aspect 8: The method according to any one of Aspects 1 to 7, wherein the TPC information is shared by multiple uplink channels or uplink signals, or is specific to one uplink channel or uplink signal.

[0278] Aspect 9: The method according to any one of Aspects 1 to 8, wherein the TPC information includes an indication of an absolute TPC parameter value or an indication of an offset from a previous TPC parameter value.

[0279] Aspect 10: The method according to aspect 9, the method further comprising: receiving an RRC message indicating whether the TPC information includes an indication of the absolute TPC parameter value or an indication of the offset from the previous TPC parameter value.

[0280] Aspect 11: The method according to any one of Aspects 9 to 10, wherein the TPC information is associated with an ID, and the previous TPC parameter value is an initial TPC parameter value associated with the ID or a last received TPC parameter value associated with the ID.

[0281] Aspect 12: According to the method of aspect 11, the method further includes: receiving a control message indicating the initial TPC parameter value.

[0282] Aspect 13: The method according to any one of Aspects 1 to 12, wherein the MAC-CE message indicates the ID of the TCI state associated with the TPC information, the path loss reference signal, the open-loop power control parameter set, the BWP, the serving cell, the SRS resource set, the PUCCH resource, or some combination thereof.

[0283] Aspect 14: The method according to any one of Aspects 1 to 13, the method further comprising: receiving an RRC message indicating whether the UE will receive one or more DCI messages including additional TPC information.

[0284] Aspect 15: The method according to any one of Aspects 1 to 14, the method further comprising: receiving one or more DCI messages including additional TPC information, wherein sending the one or more uplink messages comprises: sending the one or more uplink messages at least in part based on the additional TPC information.

[0285] Aspect 16: The method according to any one of Aspects 1 to 15, wherein the one or more uplink messages include one or more PUCCH messages, one or more PUSCH messages, one or more SRS messages, or some combination thereof.

[0286] Aspect 17: A method for wireless communication by a UE, the method comprising: receiving a DCI message indicating TPC parameters for one or more uplink messages, wherein the TPC parameters include one of an update to open-loop power control parameters relative to previous open-loop power control parameters or an update to path loss offset parameters, wherein the path loss offset parameters are an offset from path loss associated with a downlink reference signal; and transmitting the one or more uplink messages at least in part based on the TPC parameters.

[0287] Aspect 18: The method according to aspect 17 further includes: receiving configuration or indication of the downlink reference signal.

[0288] Aspect 19: The method according to any one of Aspects 17 to 18, wherein the downlink reference signal is a downlink path loss reference signal in a set of downlink path loss reference signals, and the downlink reference signal is associated with: the lowest path loss reference signal ID of the set of downlink path loss reference signals, the highest path loss reference signal ID of the set of downlink path loss reference signals, the lowest path loss value of the set of downlink path loss reference signals, the highest path loss value of the set of downlink path loss reference signals, a downlink path loss reference signal associated with the lowest TCI state in the set of active TCI states associated with the set of downlink path loss reference signals, or a downlink path loss reference signal associated with the highest TCI state in the set of active TCI states associated with the set of downlink path loss reference signals.

[0289] Aspect 20: The method according to any one of Aspects 17 to 19, wherein the update of the path loss offset parameter includes an indication of an absolute path loss offset value or an indication of an offset from a previous path loss offset value.

[0290] Aspect 21: The method according to aspect 20, the method further comprising: receiving an RRC message indicating whether the offset includes the indication of the absolute path loss offset value or the indication of the offset relative to the previous path loss offset value.

[0291] Aspect 22: The method according to any one of Aspects 17 to 21, wherein the update of the open-loop power control parameters is associated with an ID, and the previous open-loop power control parameters include an initial open-loop power control parameter associated with the ID or a last received open-loop power control parameter associated with the ID.

[0292] Aspect 23: The method according to any one of Aspects 17 to 22, wherein the DCI message indicates the ID of the TCI state associated with the TPC parameters, a path loss reference signal, an open-loop power control parameter set, a BWP, a serving cell, an SRS resource set, a PUCCH resource, or some combination thereof.

[0293] Aspect 24: The method according to any one of Aspects 17 to 23, the method further comprising: receiving an RRC message indicating whether the UE will receive one or more additional DCI messages including additional TPC information.

[0294] Aspect 25: The method according to any one of Aspects 17 to 24, the method further comprising: receiving one or more additional DCI messages including additional TPC information, wherein sending the one or more uplink messages comprises: sending the one or more uplink messages at least in part based on the additional TPC information.

[0295] Aspect 26: The method according to any one of Aspects 17 to 25, wherein the DCI message is a scheduling DCI or GCDCI.

[0296] Aspect 27: The method according to any one of Aspects 17 to 26, wherein the one or more uplink messages include one or more PUCCH messages, one or more PUSCH messages, one or more SRS messages, or some combination thereof.

[0297] Aspect 28: A method for wireless communication by a UE, the method comprising: transmitting an uplink reference signal; receiving an indication of an RSRP associated with the uplink reference signal; and transmitting one or more uplink messages, wherein a transmission power associated with the one or more uplink messages is at least partially based on the RSRP.

[0298] Aspect 29: The method according to aspect 28, the method further comprising: calculating an uplink path loss associated with the uplink reference signal based at least in part on the RSRP, wherein the transmit power is based at least in part on the uplink path loss.

[0299] Aspect 30: The method according to any one of Aspects 28 to 29, wherein the one or more uplink messages include one or more PUCCH messages, one or more PUSCH messages, one or more SRS messages, or some combination thereof.

[0300] Aspect 31: The method according to any one of Aspects 28 to 30, the method further comprising: receiving an indication that the uplink reference signal is associated with one or more PUCCH messages, one or more PUSCH messages, one or more SRS messages, or some combination thereof.

[0301] Aspect 32: The method according to aspect 31, the method further comprising: receiving a control message indicating the uplink reference signals from the set of uplink reference signals.

[0302] Aspect 33: The method according to any one of aspects 28 to 32, wherein the indication of the RSRP is received via a MAC-CE message or via a DCI message.

[0303] Aspect 34: The method according to any one of Aspects 28 to 33, the method further comprising: sending one or more initial uplink messages at least in part based on a default path loss value before receiving the indication to the RSRP.

[0304] Aspect 35: The method according to aspect 34 further includes: determining the default path loss value based at least in part on the path loss associated with the downlink reference signal.

[0305] Aspect 36: The method according to any one of Aspects 34 to 35, wherein the default path loss value is zero.

[0306] Aspect 37: The method according to any one of Aspects 34 to 36, the method further comprising: receiving a control message indicating a corresponding default path loss value associated with each uplink reference signal in a set of uplink reference signals, the set of uplink reference signals including the uplink reference signals, wherein the default path loss value is the corresponding default path loss value associated with the uplink reference signal.

[0307] Aspect 38: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the UE to perform a method according to any one of aspects 1 to 16.

[0308] Aspect 39: A UE for wireless communication, the UE comprising at least one component for performing the method according to any one of aspects 1 to 16.

[0309] Aspect 40: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform the method according to any one of aspects 1 to 16.

[0310] Aspect 41: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the UE to perform a method according to any one of aspects 17 to 27.

[0311] Aspect 42: A UE for wireless communication, the UE comprising at least one component for performing a method according to any one of aspects 17 to 27.

[0312] Aspect 43: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform a method according to any one of aspects 17 to 27.

[0313] Aspect 44: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the UE to perform a method according to any one of aspects 28 to 37.

[0314] Aspect 45: A UE for wireless communication, the UE including at least one component for performing the method according to any one of aspects 28 to 37.

[0315] Aspect 46: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform a method according to any one of aspects 28 to 37.

[0316] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0317] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0318] The information and signals described herein can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0319] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described functions or operations individually or jointly.

[0320] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including various portions distributed such that the functions are implemented in different physical locations.

[0321] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0322] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0323] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "one or more components" in subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0324] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, obtaining, selecting, choosing, building, and other similar actions.

[0325] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second reference numeral to differentiate them. If only the first reference numeral is used in the description, the description can be applied to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0326] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all implementable or within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," and not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0327] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE: Receive a media access control-control element message that includes transmit power control information for one or more uplink messages; and The one or more uplink messages are transmitted based at least in part on the transmit power control information.

2. The UE according to claim 1, wherein the transmit power control information includes updates to closed-loop power control parameters.

3. The UE according to claim 2, wherein the transmit power control information further includes a closed-loop index associated with the transmit power control information.

4. The UE of claim 1, wherein the transmit power control information includes an update of a path loss offset parameter, and wherein the path loss offset parameter is an offset from the path loss associated with a downlink reference signal.

5. The UE of claim 4, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Receive configuration or indication of the downlink reference signal associated with the path loss offset parameter.

6. The UE of claim 4, wherein the downlink reference signal is a downlink path loss reference signal in a set of downlink path loss reference signals, and wherein the downlink reference signal is associated with: the lowest path loss reference signal identifier of the downlink path loss reference signal set, the highest path loss reference signal identifier of the downlink path loss reference signal set, the lowest path loss value of the downlink path loss reference signal set, the highest path loss value of the downlink path loss reference signal set, a downlink path loss reference signal associated with the lowest transmission configuration indicator state in the set of active transmission configuration indicator states associated with the downlink path loss reference signal set, or a downlink path loss reference signal associated with the highest transmission configuration indicator state in the set of active transmission configuration indicator states associated with the downlink path loss reference signal set.

7. The UE according to claim 1, wherein the transmit power control information includes an update of the open-loop power control parameters.

8. The UE according to claim 1, wherein the transmit power control information is shared by multiple uplink channels or uplink signals, or is specific to one uplink channel or uplink signal.

9. The UE of claim 1, wherein the transmit power control information includes an indication of an absolute transmit power control parameter value or an indication of an offset from a previous transmit power control parameter value.

10. The UE of claim 9, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: A radio resource control message is received indicating whether the transmit power control information includes an indication of the absolute transmit power control parameter value or an indication of the offset from the previous transmit power control parameter value.

11. The UE of claim 9, wherein the transmit power control information is associated with an identifier, and wherein the previous transmit power control parameter value is an initial transmit power control parameter value associated with the identifier or a last received transmit power control parameter value associated with the identifier.

12. The UE of claim 11, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Receive a control message indicating the initial transmit power control parameter value.

13. The UE of claim 1, wherein the medium access control-control element message indicates an identifier of the transmit configuration indicator state associated with the transmit power control information, a path loss reference signal, an open-loop power control parameter set, a bandwidth portion, a serving cell, a probe reference signal resource set, a physical uplink control channel resource, or some combination thereof.

14. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: The UE receives a radio resource control message indicating whether it will receive one or more downlink control information messages, including additional transmit power control information.

15. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Receive one or more downlink control information messages including additional transmit power control information, wherein, in order to transmit the one or more uplink messages, the one or more processors are also capable of operating individually or jointly to: The one or more uplink messages are transmitted based at least in part on the additional transmit power control information.

16. The UE of claim 1, wherein the one or more uplink messages include one or more physical uplink control channel messages, one or more physical uplink shared channel messages, one or more probe reference signals, or some combination thereof.

17. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE: Receive a downlink control information message indicating transmit power control parameters for one or more uplink messages, wherein the transmit power control parameters include: Update the open-loop power control parameters relative to the previous open-loop power control parameters; or Update the path loss offset parameter, wherein the path loss offset parameter is an offset from the path loss associated with the downlink reference signal; and The one or more uplink messages are transmitted based at least in part on the transmit power control parameters.

18. The UE of claim 17, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Receive configuration or indication of the downlink reference signal.

19. The UE according to claim 17, wherein: The downlink reference signal is a downlink path loss reference signal from the set of downlink path loss reference signals, and The downlink reference signal is associated with the following: the lowest path loss reference signal identifier of the downlink path loss reference signal set, the highest path loss reference signal identifier of the downlink path loss reference signal set, the lowest path loss value of the downlink path loss reference signal set, the highest path loss value of the downlink path loss reference signal set, the downlink path loss reference signal associated with the lowest transmission configuration indicator state in the active transmission configuration indicator state set associated with the downlink path loss reference signal set, or the downlink path loss reference signal associated with the highest transmission configuration indicator state in the active transmission configuration indicator state set associated with the downlink path loss reference signal set.

20. The UE of claim 17, wherein the update of the path loss offset parameter includes an indication of an absolute path loss offset value or an indication of an offset from a previous path loss offset value.

21. The UE of claim 20, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Receive a radio resource control message indicating whether the offset includes the indication of the absolute path loss offset value or the indication of the offset relative to the previous path loss offset value.

22. The UE of claim 17, wherein the update of the open-loop power control parameter is associated with an identifier, and wherein the previous open-loop power control parameter includes an initial open-loop power control parameter associated with the identifier or a last received open-loop power control parameter associated with the identifier.

23. The UE of claim 17, wherein the downlink control information message indicates an identifier of the transmit configuration indicator state associated with the transmit power control parameters, a path loss reference signal, an open-loop power control parameter set, a bandwidth portion, a serving cell, a probe reference signal resource set, a physical uplink control channel resource, or some combination thereof.

24. The UE of claim 17, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: The UE receives a radio resource control message indicating whether it will receive one or more additional downlink control information messages, including additional transmit power control information.

25. The UE of claim 17, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Receive one or more additional downlink control information messages including additional transmit power control information, wherein transmitting the one or more uplink messages includes: The one or more uplink messages are transmitted based at least in part on the additional transmit power control information.

26. The UE according to claim 17, wherein the downlink control information message is scheduling downlink control information or group common downlink control information.

27. The UE of claim 17, wherein the one or more uplink messages include one or more physical uplink control channel messages, one or more physical uplink shared channel messages, one or more probe reference signals, or some combination thereof.

28. A method for wireless communication by a user equipment (UE), the method comprising: Receive a media access control-control element message that includes transmit power control information for one or more uplink messages; as well as The one or more uplink messages are transmitted based at least in part on the transmit power control information.

29. The method of claim 28, wherein the transmit power control information includes updating the closed-loop power control parameters.

30. A method for wireless communication by a user equipment (UE), the method comprising: Receive a downlink control information message indicating transmit power control parameters for one or more uplink messages, wherein the transmit power control parameters include: Update the open-loop power control parameters relative to the previous open-loop power control parameters; or Update the path loss offset parameter, wherein the path loss offset parameter is an offset from the path loss associated with the downlink reference signal; and The one or more uplink messages are transmitted based at least in part on the transmit power control parameters.

Images