[go: up one dir, main page]

WO2025175553A1 - Power control information for multiple transmission configuration indication states - Google Patents

Power control information for multiple transmission configuration indication states

Info

Publication number
WO2025175553A1
WO2025175553A1 PCT/CN2024/078289 CN2024078289W WO2025175553A1 WO 2025175553 A1 WO2025175553 A1 WO 2025175553A1 CN 2024078289 W CN2024078289 W CN 2024078289W WO 2025175553 A1 WO2025175553 A1 WO 2025175553A1
Authority
WO
WIPO (PCT)
Prior art keywords
power control
uplink
transmission configuration
configuration indication
control parameter
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/078289
Other languages
French (fr)
Inventor
Shaozhen GUO
Mostafa KHOSHNEVISAN
Yan Zhou
Jing Sun
Xiaoxia Zhang
Peter Gaal
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Priority to PCT/CN2024/078289 priority Critical patent/WO2025175553A1/en
Publication of WO2025175553A1 publication Critical patent/WO2025175553A1/en
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B17/00—Monitoring; Testing
    • H04B17/30—Monitoring; Testing of propagation channels
    • H04B17/309—Measuring or estimating channel quality parameters
    • H04B17/347—Path loss
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/04—Transmission power control [TPC]
    • H04W52/18—TPC being performed according to specific parameters
    • H04W52/24—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters
    • H04W52/242—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters taking into account path loss

Definitions

  • the following relates to wireless communication, including power control information for multiple transmission configuration indication (TCI) states.
  • TCI transmission configuration indication
  • the described techniques relate to improved methods, systems, devices, and apparatuses that support power control information for multiple transmission configuration indication (TCI) states.
  • TCI transmission configuration indication
  • the described techniques enable a network entity to indicate uplink power control information to a user equipment (UE) , where the uplink power control information is indicated via a single message and is associated with multiple TCI states.
  • the network entity may transmit a control message that indicates multiple TCI states for uplink communications by the UE via one or more component carriers (CCs) .
  • the control message may be, for example, a radio resource control (RRC) configuration, or some other type of message.
  • RRC radio resource control
  • the network entity may transmit, to the UE, another message that includes uplink power control information for the UE.
  • receiving the message may include operations, features, means, or instructions for receiving a medium access control-control element (MAC-CE) indicates the power control parameter corresponding to the at least two TCI states.
  • MAC-CE medium access control-control element
  • Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving the power control parameter via a set of one or more reserved bits within the MAC-CE, an uplink power control field within the MAC-CE, or both.
  • a quantity of the set of multiple uplink power control fields may be based on a quantity of TCI states from among the set of multiple TCI states that may be activated for the uplink communications by the UE and the quantity of the set of multiple uplink power control fields may be based on the quantity of TCI states from among the set of multiple TCI states that may be activated for the uplink communications by the UE and that may be associated with an uplink power control configuration.
  • Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, via the MAC-CE, one or more fields that indicate one or more TCI states from among the set of multiple TCI states that may be activated for the uplink communications by the UE, where each field of the one or more fields indicates a respective TCI state and indicates whether the set of multiple uplink power control fields includes a respective power uplink control field that corresponds to the respective TCI state.
  • Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, via each uplink power control field of the set of multiple uplink power control fields, a respective identifier associated with a respective TCI state to which the power control parameter included in the uplink power control field applies.
  • Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining the one or more transmit powers for the at least two TCI states using the power control parameter based on the at least two TCI states being activated for the uplink communications by the UE, determining the one or more transmit powers for the at least two TCI states using the power control parameter based on the at least two TCI states being activated for the uplink communications by the UE and further based on the at least two TCI states being associated with an uplink power control configuration, and determining the one or more transmit powers for the at least two TCI states using the power control parameter based on at least two bits in the MAC-CE that indicate the power control parameter applies to the at least two TCI states.
  • Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving a unified TCI state activation MAC-CE, where the unified TCI state activation MAC-CE indicates one or more TCI states from among the set of multiple TCI states that may be activated for the uplink communications by the UE.
  • the power control parameter includes a pathloss offset and the MAC-CE includes at least one field that indicates whether the pathloss offset may be with respect to a nominal pathloss or a measured pathloss.
  • Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving a first indication of a first set of CCs for TCI state activation, receiving a second indication of a second set of CCs associated with uplink power control, where the power control parameter corresponds to the one or more CCs that may be the same as the second set of CCs for uplink power control, and applying the power control parameter to the at least two TCI states across the second set of CCs.
  • a method for wireless communication by a network entity may include outputting a control message that indicates a set of multiple TCI states for uplink communications by a UE via one or more CCs, outputting a message including uplink power control information that indicates a power control parameter associated with uplink pathloss, the power control parameter corresponding to at least two TCI states from among the set of multiple TCI states, and obtaining, via the one or more CCs in accordance with the at least two TCI states, the uplink communications using one or more transmit powers based on the power control parameter.
  • the network entity may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories.
  • the one or more processors may individually or collectively be operable to execute the code to cause the network entity to output a control message that indicates a set of multiple TCI states for uplink communications by a UE via one or more CCs, output a message including uplink power control information that indicates a power control parameter associated with uplink pathloss, the power control parameter corresponding to at least two TCI states from among the set of multiple TCI states, and obtain, via the one or more CCs in accordance with the at least two TCI states, the uplink communications using one or more transmit powers based on the power control parameter.
  • the network entity may include means for outputting a control message that indicates a set of multiple TCI states for uplink communications by a UE via one or more CCs, means for outputting a message including uplink power control information that indicates a power control parameter associated with uplink pathloss, the power control parameter corresponding to at least two TCI states from among the set of multiple TCI states, and means for obtaining, via the one or more CCs in accordance with the at least two TCI states, the uplink communications using one or more transmit powers based on the power control parameter.
  • a non-transitory computer-readable medium storing code for wireless communication is described.
  • the code may include instructions executable by one or more processors to output a control message that indicates a set of multiple TCI states for uplink communications by a UE via one or more CCs, output a message including uplink power control information that indicates a power control parameter associated with uplink pathloss, the power control parameter corresponding to at least two TCI states from among the set of multiple TCI states, and obtain, via the one or more CCs in accordance with the at least two TCI states, the uplink communications using one or more transmit powers based on the power control parameter.
  • outputting the message may include operations, features, means, or instructions for outputting a MAC-CE that indicates the power control parameter corresponding to the at least two TCI states.
  • Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting the power control parameter via a set of one or more reserved bits within the MAC-CE, an uplink power control field within the MAC-CE, or both.
  • Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting, via a set of multiple uplink power control fields within the MAC-CE, the power control parameter.
  • a quantity of the set of multiple uplink power control fields may be based on a quantity of TCI states from among the set of multiple TCI states that may be activated for the uplink communications by the UE and the quantity of the set of multiple uplink power control fields may be based on the quantity of TCI states from among the set of multiple TCI states that may be activated for the uplink communications by the UE and that may be associated with an uplink power control configuration.
  • Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting, via the MAC-CE, one or more fields that indicate one or more TCI states from among the set of multiple TCI states that may be activated for the uplink communications by the UE, where each field of the one or more fields indicates a respective TCI state and indicates whether the set of multiple uplink power control fields includes a respective power uplink control field that corresponds to the respective TCI state.
  • outputting the MAC-CE may include operations, features, means, or instructions for outputting a unified TCI state activation MAC-CE that indicates one or more TCI states from among the set of multiple TCI states that may be activated for the uplink communications by the UE.
  • the power control parameter includes a pathloss offset and the MAC-CE includes at least one field that indicates whether the pathloss offset may be with respect to a nominal pathloss or a measured pathloss.
  • Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting, after receiving the uplink communications using the one or more transmit powers, a second message including second uplink power control information, where the message includes a unified TCI state activation MAC-CE that indicates one or more TCI states from among the set of multiple TCI states that may be activated for the uplink communications by the UE, and where the second message includes a MAC-CE different than the unified TCI state activation MAC-CE.
  • FIG. 1 shows an example of a wireless communications system that supports power control information for multiple transmission configuration indication (TCI) states in accordance with one or more aspects of the present disclosure.
  • TCI transmission configuration indication
  • FIG. 2 shows an example of a network architecture that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure.
  • FIG. 10 shows a block diagram of a communications manager that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure.
  • FIG. 11 shows a diagram of a system including a device that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure.
  • FIGs. 12 and 13 show block diagrams of devices that support power control information for multiple TCI states in accordance with one or more aspects of the present disclosure.
  • a user equipment may receive a downlink reference signal from a network entity for determining (e.g., calculating, obtaining) a pathloss associated with a channel between the UE and the network entity. The UE may use the pathloss to determine an uplink transmit power for uplink messages to the network entity.
  • Some wireless communications system may be associated with an uplink dense deployment in which a central network entity is configured for transmitting downlink signaling to the UE and multiple network entities (e.g., uplink-dedicated network entities) are configured for receiving uplink signaling from the UE. In such systems, the uplink-dedicated network entities may not transmit the downlink reference signals and the UE may instead transmit uplink reference signals to an uplink-dedicated network entity.
  • the uplink-dedicated network entity may indicate channel information (e.g., pathloss) based on the uplink reference signal to the central network entity, and the central network entity may transmit a message to the UE indicating pathloss information or other power control information, such as a pathloss offset or scaling factor, based on the channel information, where the pathloss offset or scaling factor is applied with respect to a reference pathloss.
  • the reference pathloss may be a measured downlink pathloss based on a pathloss reference signal, a nominal pathloss or any combination thereof.
  • the nominal pathloss may be one of an initial measured downlink pathloss associated with the same transmission configuration indication (TCI) state as the pathloss offset, an initial uplink pathloss associated with the same TCI state as the pathloss offset, a previous or latest uplink pathloss associated with the same TCI state as the pathloss offset, or a previous or latest downlink pathloss associated with the same TCI state as the pathloss offset.
  • TCI transmission configuration indication
  • the power control information may be indicated on a per TCI state basis. As such, if a UE supports multiple TCI states, the signaling to indicate the power control information may increase, which may increase complexity and overhead.
  • the network entity may transmit control signaling, such as a radio resource control (RRC) message, to a UE to configure multiple TCI states for the UE across multiple component carriers (CCs) .
  • RRC radio resource control
  • the network entity may subsequently activate a set of one or more of the TCI states for uplink transmissions by the UE.
  • the network entity may transmit a single message that indicates a power control parameter applicable to one or more TCI states across one or more CCs.
  • the message may be a medium access control-control element (MAC-CE) , such as a TCI state activation MAC-CE or a separate MAC-CE.
  • MAC-CE medium access control-control element
  • the power control parameter may be indicated via one or more reserved bits or fields in the MAC-CE. Various techniques for indicating which TCI states are associated with the indicated power control parameter are described.
  • the power control parameter may be applied to a set of CCs that is the same as the CCs associated with the activated TCI states or with a different set of CCs, and the UE may utilize the power control parameter for transmission across the set of CCs.
  • the UE may use the power control parameter to determine (e.g., calculate) a transmit power for transmissions using each TCI state or CC.
  • the power control parameter may be a pathloss offset or a pathloss scaling factor, and the UE may calculate uplink pathloss using the parameter. The uplink pathloss may then be used to calculate the transmit power for a given TCI state.
  • the described indication of power control information for multiple TCI states may thereby reduce overhead and latency while maintaining reliable wireless communications.
  • FIG. 1 shows an example of a wireless communications system 100 that supports power control information for multiple transmission configuration indication states in accordance with one or more aspects of the present disclosure.
  • the wireless communications system 100 may include one or more devices, such as one or more network devices (e.g., network entities 105) , one or more UEs 115, and a core network 130.
  • the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-A Pro LTE-A Pro
  • NR New Radio
  • the network entities 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may include devices in different forms or having different capabilities.
  • a network entity 105 may be referred to as a network element, a mobility element, a radio access network (RAN) node, or network equipment, among other nomenclature.
  • network entities 105 and UEs 115 may wirelessly communicate via communication link (s) 125 (e.g., a radio frequency (RF) access link) .
  • a network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UEs 115 and the network entity 105 may establish the communication link (s) 125.
  • the coverage area 110 may be an example of a geographic area over which a network entity 105 and a UE 115 may support the communication of signals according to one or more radio access technologies (RATs) .
  • RATs radio access technologies
  • a node of the wireless communications system 100 which may be referred to as a network node, or a wireless node, may be a network entity 105 (e.g., any network entity described herein) , a UE 115 (e.g., any UE described herein) , a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein.
  • a node may be a UE 115.
  • a node may be a network entity 105.
  • a first node may be configured to communicate with a second node or a third node.
  • the first node may be a UE 115
  • the second node may be a network entity 105
  • the third node may be a UE 115.
  • the first node may be a UE 115
  • the second node may be a network entity 105
  • the third node may be a network entity 105.
  • the first, second, and third nodes may be different relative to these examples.
  • reference to a UE 115, network entity 105, apparatus, device, computing system, or the like may include disclosure of the UE 115, network entity 105, apparatus, device, computing system, or the like being a node.
  • disclosure that a UE 115 is configured to receive information from a network entity 105 also discloses that a first node is configured to receive information from a second node.
  • network entities 105 may communicate with a core network 130, or with one another, or both.
  • network entities 105 may communicate with the core network 130 via backhaul communication link (s) 120 (e.g., in accordance with an S1, N2, N3, or other interface protocol) .
  • network entities 105 may communicate with one another via backhaul communication link (s) 120 (e.g., in accordance with an X2, Xn, or other interface protocol) either directly (e.g., directly between network entities 105) or indirectly (e.g., via the core network 130) .
  • network entities 105 may communicate with one another via a midhaul communication link 162 (e.g., in accordance with a midhaul interface protocol) or a fronthaul communication link 168 (e.g., in accordance with a fronthaul interface protocol) , or any combination thereof.
  • the backhaul communication link (s) 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., an electrical link, an optical fiber link) or one or more wireless links (e.g., a radio link, a wireless optical link) , among other examples or various combinations thereof.
  • a UE 115 may communicate with the core network 130 via a communication link 155.
  • One or more of the network entities 105 or network equipment described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or giga-NodeB (either of which may be referred to as a gNB) , a 5G NB, a next-generation eNB (ng-eNB) , a Home NodeB, a Home eNodeB, or other suitable terminology) .
  • a base station 140 e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or giga-NodeB (either of which may be referred
  • a network entity 105 may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within one network entity (e.g., a network entity 105 or a single RAN node, such as a base station 140) .
  • a network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) , which may be configured to utilize a protocol stack that is physically or logically distributed among multiple network entities (e.g., network entities 105) , such as an integrated access and 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) ) .
  • a disaggregated architecture e.g., a disaggregated base station architecture, a disaggregated RAN architecture
  • a protocol stack that is physically or logically distributed among multiple network entities (e.g., network entities 105) , such as an integrated access and backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by
  • An RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) .
  • One or more components of the network entities 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 105 may be located in distributed locations (e.g., separate physical locations) .
  • one or more of the network entities 105 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU) ) .
  • VCU virtual CU
  • VDU virtual DU
  • VRU virtual RU
  • the split of functionality between a CU 160, a DU 165, and an RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combinations thereof) are performed at a CU 160, a DU 165, or an RU 170.
  • functions e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combinations thereof
  • a functional split of a protocol stack may be employed between a CU 160 and a DU 165 such that the CU 160 may support one or more layers of the protocol stack and the DU 165 may support one or more different layers of the protocol stack.
  • a functional split of the protocol stack may be employed between a DU 165 and an RU 170 such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack.
  • the DU 165 may support one or multiple different cells (e.g., via one or multiple different RUs, such as an RU 170) .
  • a CU 160 may be connected to a DU 165 via a midhaul communication link 162 (e.g., F1, F1-c, F1-u) , and a DU 165 may be connected to an RU 170 via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface) .
  • a midhaul communication link 162 or a fronthaul communication link 168 may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities (e.g., one or more of the network entities 105) that are in communication via such communication links.
  • infrastructure and spectral resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, providing an IAB network architecture (e.g., to a core network 130) .
  • IAB network architecture e.g., to a core network 130
  • one or more of the network entities 105 may be partially controlled by each other.
  • the IAB node (s) 104 may be referred to as a donor entity or an IAB donor.
  • a DU 165 or an RU 170 may be partially controlled by a CU 160 associated with a network entity 105 or base station 140 (such as a donor network entity or a donor base station) .
  • An IAB-MT may be equipped with an independent set of antennas for relay of communications with UEs 115 or may share the same antennas (e.g., of an RU 170) of IAB node (s) 104 used for access via the DU 165 of the IAB node (s) 104 (e.g., referred to as virtual IAB-MT (vIAB-MT) ) .
  • the IAB node (s) 104 may include one or more DUs (e.g., DUs 165) that support communication links with additional entities (e.g., IAB node (s) 104, UEs 115) within the relay chain or configuration of the access network (e.g., downstream) .
  • one or more components of the disaggregated RAN architecture e.g., the IAB node (s) 104 or components of the IAB node (s) 104) may be configured to operate according to the techniques described herein.
  • IAB node (s) 104 may refer to RAN nodes that provide IAB functionality (e.g., access for UEs 115, wireless self-backhauling capabilities) .
  • a DU 165 may act as a distributed scheduling node towards child nodes associated with the IAB node (s) 104, and the IAB-MT may act as a scheduled node towards parent nodes associated with IAB node (s) 104. That is, an IAB donor may be referred to as a parent node in communication with one or more child nodes (e.g., an IAB donor may relay transmissions for UEs through other IAB node (s) 104) .
  • IAB node (s) 104 may be referred to as parent nodes that support communications for child IAB nodes, or may be referred to as child IAB nodes associated with IAB donors, or both.
  • An IAB donor may include a CU 160 with a wired or wireless connection (e.g., backhaul communication link (s) 120) to the core network 130 and may act as a parent node to IAB node (s) 104.
  • the DU 165 of an IAB donor may relay transmissions to UEs 115 through IAB node (s) 104, or may directly signal transmissions to a UE 115, or both.
  • one or more components of the disaggregated RAN architecture may be configured to support test as described herein.
  • some operations described as being performed by a UE 115 or a network entity 105 may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., components such as an IAB node, a DU 165, a CU 160, an RU 170, an RIC 175, an SMO system 180) .
  • a UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples.
  • a UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA) , a tablet computer, a laptop computer, or a personal computer.
  • PDA personal digital assistant
  • a UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, vehicles, or meters, among other examples.
  • WLL wireless local loop
  • IoT Internet of Things
  • IoE Internet of Everything
  • MTC machine type communications
  • the UEs 115 described herein may be able to communicate with various types of devices, such as UEs 115 that may sometimes operate as relays, as well as the network entities 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.
  • devices such as UEs 115 that may sometimes operate as relays, as well as the network entities 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.
  • the UEs 115 and the network entities 105 may wirelessly communicate with one another via the communication link (s) 125 (e.g., one or more access links) using resources associated with one or more carriers.
  • the term “carrier” may refer to a set of RF spectrum resources having a defined PHY layer structure for supporting the communication link (s) 125.
  • a carrier used for the communication link (s) 125 may include a portion of an RF spectrum band (e.g., a bandwidth part (BWP) ) that is operated according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR) .
  • a given RAT e.g., LTE, LTE-A, LTE-A Pro, NR
  • the terms “transmitting, ” “receiving, ” or “communicating, ” when referring to a network entity 105 may refer to any portion of a network entity 105 (e.g., a base station 140, a CU 160, a DU 165, a RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities, such as one or more of the network entities 105) .
  • a network entity 105 e.g., a base station 140, a CU 160, a DU 165, a RU 170
  • another device e.g., directly or via one or more other network entities, such as one or more of the network entities 105
  • a carrier may have acquisition signaling or control signaling that coordinates operations for other carriers.
  • a carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute RF channel number (EARFCN) ) and may be identified according to a channel raster for discovery by the UEs 115.
  • E-UTRA evolved universal mobile telecommunication system terrestrial radio access
  • a carrier may be operated in a standalone mode, in which case initial acquisition and connection may be conducted by the UEs 115 via the carrier, or the carrier may be operated in a non-standalone mode, in which case a connection is anchored using a different carrier (e.g., of the same or a different RAT) .
  • the communication link (s) 125 of the wireless communications system 100 may include downlink transmissions (e.g., forward link transmissions) from a network entity 105 to a UE 115, uplink transmissions (e.g., return link transmissions) from a UE 115 to a network entity 105, or both, among other configurations of transmissions.
  • Carriers may carry downlink or uplink communications (e.g., in an FDD mode) or may be configured to carry downlink and uplink communications (e.g., in a TDD mode) .
  • a carrier may be associated with a particular bandwidth of the RF spectrum and, in some examples, the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system 100.
  • the carrier bandwidth may be one of a set of bandwidths for carriers of a particular RAT (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz) ) .
  • Devices of the wireless communications system 100 e.g., the network entities 105, the UEs 115, or both
  • the wireless communications system 100 may include network entities 105 or UEs 115 that support concurrent communications using carriers associated with multiple carrier bandwidths.
  • each served UE 115 may be configured for operating using portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth.
  • Signal waveforms transmitted via a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM) ) .
  • MCM multi-carrier modulation
  • OFDM orthogonal frequency division multiplexing
  • DFT-S-OFDM discrete Fourier transform spread OFDM
  • a resource element may refer to resources of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related.
  • the quantity of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both) , such that a relatively higher quantity of resource elements (e.g., in a transmission duration) and a relatively higher order of a modulation scheme may correspond to a relatively higher rate of communication.
  • a wireless communications resource may refer to a combination of an RF spectrum resource, a time resource, and a spatial resource (e.g., a spatial layer, a beam) , and the use of multiple spatial resources may increase the data rate or data integrity for communications with a UE 115.
  • One or more numerologies for a carrier may be supported, and a numerology may include a subcarrier spacing ( ⁇ f) and a cyclic prefix.
  • a carrier may be divided into one or more BWPs having the same or different numerologies.
  • a UE 115 may be configured with multiple BWPs.
  • a single BWP for a carrier may be active at a given time and communications for the UE 115 may be restricted to one or more active BWPs.
  • Each frame may include multiple consecutively-numbered subframes or slots, and each subframe or slot may have the same duration.
  • a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a quantity of slots.
  • each frame may include a variable quantity of slots, and the quantity of slots may depend on subcarrier spacing.
  • Each slot may include a quantity of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period) .
  • a slot may further be divided into multiple mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f ) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.
  • a subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and may be referred to as a transmission time interval (TTI) .
  • TTI duration e.g., a quantity of symbol periods in a TTI
  • the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs) ) .
  • Physical channels may be multiplexed for communication using a carrier according to various techniques.
  • a physical control channel and a physical data channel may be multiplexed for signaling via a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques.
  • a control region e.g., a control resource set (CORESET)
  • CORESET control resource set
  • One or more control regions may be configured for a set of the UEs 115.
  • one or more of the UEs 115 may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner.
  • An aggregation level for a control channel candidate may refer to an amount of control channel resources (e.g., control channel elements (CCEs) ) associated with encoded information for a control information format having a given payload size.
  • Search space sets may include common search space sets configured for sending control information to UEs 115 (e.g., one or more UEs) or may include UE-specific search space sets for sending control information to a UE 115 (e.g., a specific UE) .
  • Such cells may range from smaller areas (e.g., a structure, a subset of structure) to larger areas depending on various factors such as the capabilities of the network entity 105.
  • a cell may be or include a building, a subset of a building, or exterior spaces between or overlapping with coverage areas 110, among other examples.
  • a macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by the UEs 115 with service subscriptions with the network provider supporting the macro cell.
  • a small cell may be associated with a network entity 105 operating with lower power (e.g., a base station 140 operating with lower power) relative to a macro cell, and a small cell may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells.
  • Small cells may provide unrestricted access to the UEs 115 with service subscriptions with the network provider or may provide restricted access to the UEs 115 having an association with the small cell (e.g., the UEs 115 in a closed subscriber group (CSG) , the UEs 115 associated with users in a home or office) .
  • a network entity 105 may support one or more cells and may also support communications via the one or more cells using one or multiple CCs.
  • a network entity 105 may be movable and therefore provide communication coverage for a moving coverage area, such as the coverage area 110.
  • coverage areas 110 e.g., different coverage areas
  • coverage areas 110 may overlap, but the coverage areas 110 (e.g., different coverage areas) may be supported by the same network entity (e.g., a network entity 105) .
  • overlapping coverage areas, such as a coverage area 110, associated with different technologies may be supported by different network entities (e.g., the network entities 105) .
  • the wireless communications system 100 may include, for example, a heterogeneous network in which different types of the network entities 105 support communications for coverage areas 110 (e.g., different coverage areas) using the same or different RATs.
  • the wireless communications system 100 may support synchronous or asynchronous operation.
  • network entities 105 e.g., base stations 140
  • network entities 105 may have different frame timings, and transmissions from different network entities (e.g., different ones of network entities 105) may, in some examples, not be aligned in time.
  • the techniques described herein may be used for either synchronous or asynchronous operations.
  • Some UEs 115 may be relatively low cost or low complexity devices and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication) .
  • M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a network entity 105 (e.g., a base station 140) without human intervention.
  • M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application program that uses the information or presents the information to humans interacting with the application program.
  • Some UEs 115 may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.
  • Some UEs 115 may be configured to employ operating modes that reduce power consumption, such as half-duplex communications (e.g., a mode that supports one-way communication via transmission or reception, but not transmission and reception concurrently) .
  • half-duplex communications may be performed at a reduced peak rate.
  • Other power conservation techniques for the UEs 115 may include entering a power saving deep sleep mode when not engaging in active communications, operating using a limited bandwidth (e.g., according to narrowband communications) , or a combination of these techniques.
  • some UEs 115 may be configured for operation using a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs) ) within a carrier, within a guard-band of a carrier, or outside of a carrier.
  • a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs) ) within a carrier, within a guard-band of a carrier, or outside of a carrier.
  • a UE 115 may be configured to support communicating directly with other UEs (e.g., one or more of the UEs 115) via a device-to-device (D2D) communication link, such as a D2D communication link 135 (e.g., in accordance with a peer-to-peer (P2P) , D2D, or sidelink protocol) .
  • D2D device-to-device
  • P2P peer-to-peer
  • one or more UEs 115 of a group that are performing D2D communications may be within the coverage area 110 of a network entity 105 (e.g., a base station 140, an RU 170) , which may support aspects of such D2D communications being configured by (e.g., scheduled by) the network entity 105.
  • one or more UEs 115 of such a group may be outside the coverage area 110 of a network entity 105 or may be otherwise unable to or not configured to receive transmissions from a network entity 105.
  • groups of the UEs 115 communicating via D2D communications may support a one-to-many (1: M) system in which each UE 115 transmits to one or more of the UEs 115 in the group.
  • a network entity 105 may facilitate the scheduling of resources for D2D communications.
  • D2D communications may be carried out between the UEs 115 without an involvement of a network entity 105.
  • the core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions.
  • the core network 130 may be an evolved packet core (EPC) or 5G core (5GC) , which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management function (AMF) ) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) .
  • EPC evolved packet core
  • 5GC 5G core
  • MME mobility management entity
  • AMF access and mobility management function
  • S-GW serving gateway
  • PDN Packet Data Network gateway
  • UPF user plane function
  • the control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the network entities 105 (e.g., base stations 140) associated with the core network 130.
  • NAS non-access stratum
  • User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions.
  • the user plane entity may be connected to IP services 150 for one or more network operators.
  • the IP services 150 may include access to the Internet, Intranet (s) , an IP Multimedia Subsystem (IMS) , or a Packet-Switched Streaming Service.
  • IMS IP Multimedia Subsystem
  • the wireless communications system 100 may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz) .
  • the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from 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 the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers) compared to communications using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.
  • HF high frequency
  • VHF very high frequency
  • the wireless communications system 100 may utilize both licensed and unlicensed RF spectrum bands.
  • the wireless communications system 100 may employ License Assisted Access (LAA) , LTE-Unlicensed (LTE-U) RAT, or NR technology using an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band.
  • LAA License Assisted Access
  • LTE-U LTE-Unlicensed
  • NR NR technology
  • an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band.
  • devices such as the network entities 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance.
  • operations using unlicensed bands may be based on a carrier aggregation configuration in conjunction with CCs operating using a licensed band (e.g., LAA) .
  • Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.
  • a network entity 105 e.g., a base station 140, an RU 170
  • a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming.
  • the antennas of a network entity 105 or a UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming.
  • one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower.
  • antennas or antenna arrays associated with a network entity 105 may be located at diverse geographic locations.
  • a network entity 105 may include an antenna array with a set of rows and columns of antenna ports that the network entity 105 may use to support beamforming of communications with a UE 115.
  • a UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations.
  • an antenna panel may support RF beamforming for a signal transmitted via an antenna port.
  • the network entities 105 or the UEs 115 may use MIMO communications to exploit multipath signal propagation and increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers.
  • Such techniques may be referred to as spatial multiplexing.
  • the multiple signals may, for example, be transmitted by the transmitting device via different antennas or different combinations of antennas. Likewise, the multiple signals may be received by the receiving device via different antennas or different combinations of antennas.
  • Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords) .
  • Different spatial layers may be associated with different antenna ports used for channel measurement and reporting.
  • MIMO techniques include single-user MIMO (SU-MIMO) , for which multiple spatial layers are transmitted to the same receiving device, and multiple-user MIMO (MU-MIMO) , for which multiple spatial layers are transmitted to multiple devices.
  • SU-MIMO single-user MIMO
  • Beamforming which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device.
  • Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating along particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference.
  • the adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device.
  • the adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation) .
  • a network entity 105 or a UE 115 may use beam sweeping techniques as part of beamforming operations.
  • a network entity 105 e.g., a base station 140, an RU 170
  • Some signals e.g., synchronization signals, reference signals, beam selection signals, or other control signals
  • the network entity 105 may transmit a signal according to different beamforming weight sets associated with different directions of transmission.
  • Transmissions along different beam directions may be used to identify (e.g., by a transmitting device, such as a network entity 105, or by a receiving device, such as a UE 115) a beam direction for later transmission or reception by the network entity 105.
  • a transmitting device such as a network entity 105
  • a receiving device such as a UE 115
  • Some signals may be transmitted by a transmitting device (e.g., a network entity 105 or a UE 115) along a single beam direction (e.g., a direction associated with the receiving device, such as another network entity 105 or UE 115) .
  • a transmitting device e.g., a network entity 105 or a UE 115
  • a single beam direction e.g., a direction associated with the receiving device, such as another network entity 105 or UE 115
  • the beam direction associated with transmissions along a single beam direction may be determined based on a signal that was transmitted along one or more beam directions.
  • a UE 115 may receive one or more of the signals transmitted by the network entity 105 along different directions and may report to the network entity 105 an indication of the signal that the UE 115 received with a highest signal quality or an otherwise acceptable signal quality.
  • transmissions by a device may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from a network entity 105 to a UE 115) .
  • the UE 115 may report feedback that indicates precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more sub-bands.
  • the network entity 105 may transmit a reference signal (e.g., a cell-specific reference signal (CRS) , a channel state information reference signal (CSI-RS) ) , which may be precoded or unprecoded.
  • a reference signal e.g., a cell-specific reference signal (CRS) , a channel state information reference signal (CSI-RS)
  • the UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook) .
  • PMI precoding matrix indicator
  • codebook-based feedback e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook
  • these techniques are described with reference to signals transmitted along one or more directions by a network entity 105 (e.g., a base station 140, an RU 170)
  • a UE 115 may employ similar techniques for transmitting signals multiple times along different directions (e.g., for identifying a beam direction for subsequent transmission or reception by the UE 115) or for transmitting a signal along a single direction (e.g., for transmitting data to a receiving device) .
  • a receiving device may perform reception operations in accordance with multiple receive configurations (e.g., directional listening) when receiving various signals from a transmitting device (e.g., a network entity 105) , such as synchronization signals, reference signals, beam selection signals, or other control signals.
  • a transmitting device e.g., a network entity 105
  • a receiving device may perform reception in accordance with multiple receive directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as “listening” according to different receive configurations or receive directions.
  • a receiving device may use a single receive configuration to receive along a single beam direction (e.g., when receiving a data signal) .
  • the single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio (SNR) , or otherwise acceptable signal quality based on listening according to multiple beam directions) .
  • receive configuration directions e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio (SNR) , or otherwise acceptable signal quality based on listening according to multiple beam directions
  • the UEs 115 and the network entities 105 may support retransmissions of data to increase the likelihood that data is received successfully.
  • Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly via a communication link (e.g., the communication link (s) 125, a D2D communication link 135) .
  • HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC) ) , forward error correction (FEC) , and retransmission (e.g., automatic repeat request (ARQ) ) .
  • FEC forward error correction
  • ARQ automatic repeat request
  • HARQ may improve throughput at the MAC layer in relatively poor radio conditions (e.g., low signal-to-noise conditions) .
  • a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific slot for data received via a previous symbol in the slot. In some other examples, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.
  • a UE 115 may be configured with a unified TCI state type per CC.
  • the unified TCI may indicate a TCI state (e.g., a TCI mode) , which may include one or more communication parameters (e.g., a channel) for communicating with one or more network entities 105.
  • the unified TCI may indicate a joint TCI state, where the UE 115 may communicate with the network entity 105 via at least one downlink channel and at least one uplink channel using the common beam.
  • the unified TCI may indicate a separate downlink TCI state, where the UE 115 may communicate with the network entity 105 via multiple downlink channels, reference signals, or both, using the common beam.
  • the unified TCI state may indicate a separate uplink TCI state, where the UE 115 may communicate with the network entity 105 via multiple uplink channels, reference signals, or both, using the common beam.
  • the UE 115 may be configured with a set of TCI states. For example, the UE 115 may receive control signaling (e.g., an RRC configuration) that indicates a list of TCI states (e.g., up to 128 TCI states) via a parameter (e.g., dl-OrJointTCI-StateList) for downlink and uplink operation.
  • control signaling e.g., an RRC configuration
  • a parameter e.g., dl-OrJointTCI-StateList
  • the TCI state may be used to provide a reference signal for a quasi co-location (QCL) for a demodulation reference signal (DMRS) of a physical downlink shared channel (PDSCH) , a DMRS of a physical downlink control channel (PDCCH) , and a channel state information (CSI) reference signal (CSI-RS) and to determine an uplink transmit spatial filter for dynamic physical uplink shared channel (PUSCH) , configured grant, physical uplink control channel (PUCCH) , and sounding reference signal (SRS) transmissions.
  • QCL quasi co-location
  • DMRS demodulation reference signal
  • PDSCH physical downlink shared channel
  • PDCCH physical downlink control channel
  • CSI-RS channel state information reference signal
  • the UE 115 may be configured with a set of TCI states (e.g., up to 128 TCI states) via a parameter (e.g., dl-OrJointTCI-StateList) for downlink and a second set (e.g., up to 64 TCI states) via a second parameter (e.g., ul-TCI-ToAddModList) for uplink.
  • the downlink TCI state may be used to provide a reference signal for a QCL for a DMRS of a PDSCH, for a DMRS of a PDCCH, and a CSI-RS.
  • the uplink TCI state may be used to determine an uplink transmit spatial filter for dynamic PUSCH, configured grant, PUCCH, and SRS transmissions.
  • up to eight TCI states or pairs of TCI states including one TCI state for uplink and one TCI state for downlink may be activated by a TCI activation MAC-CE. That is, the network entity 105 may transmit a TCI state activation MAC-CE to the UE 115 to indicate some quantity of one or more TCI states that are activated for uplink or downlink communications by the UE 115.
  • a common TCI state identifier update and activation may be supported to provide QCL information, common uplink transmit spatial filters, or both across a set of configured CCs.
  • a set of RRC configured TCI state pools may be configured for each bandwidth part or CC. Additionally, or alternatively, a set of RRC configured TCI state pools for each bandwidth or CC may be absent, and may be replaced with a reference to RRC configured TCI state pools in a reference bandwidth part or CC.
  • a network entity 105 may transmit uplink power control information to a UE 115 for multiple TCI states supported by the UE 115.
  • the network entity 105 may transmit, to the UE 115, a single message that is associated with multiple TCI states.
  • the message may be a TCI state activation MAC-CE or another type of MAC-CE, in some examples.
  • the message may be transmitted after the UE 115 is configured with one or more TCI states across one or more CCs.
  • the uplink power control information may indicate a power control parameter for uplink pathloss calculation for the one or more CCs.
  • the power control parameter may be, for example, an uplink pathloss offset, an uplink pathloss scaling factor, or some other parameter that may be used in a calculation of uplink transmit power.
  • the power control parameter may correspond to one or more TCI states from the multiple TCI states configured for the UE 115.
  • the UE 115 may transmit uplink communications via one or more CCs according to the one or more TCI states.
  • the uplink communications may be transmitted according to one or more transmit powers that are based on the power control parameter.
  • FIG. 2 shows an example of a network architecture 200 (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that supports power control information for multiple transmission configuration indication states in accordance with one or more aspects of the present disclosure.
  • the network architecture 200 may illustrate an example for implementing one or more aspects of the wireless communications system 100.
  • the network architecture 200 may include one or more CUs 160-a that may communicate directly with a core network 130-a via a backhaul communication link 120-a, or indirectly with the core network 130-a through one or more disaggregated network entities 105 (e.g., a Near-RT RIC 175-b via an E2 link, or a Non-RT RIC 175-a associated with an SMO 180-a (e.g., an SMO Framework) , or both) .
  • a CU 160-a may communicate with one or more DUs 165-a via respective midhaul communication links 162-a (e.g., an F1 interface) .
  • the DUs 165-a may communicate with one or more RUs 170-a via respective fronthaul communication links 168-a.
  • the RUs 170-a may be associated with respective coverage areas 110-a and may communicate with UEs 115-a via one or more communication links 125-a.
  • a UE 115-a may be simultaneously served by multiple RUs 170-a.
  • Each of the network entities 105 of the network architecture 200 may include one or more interfaces or may be coupled with one or more interfaces configured to receive or transmit signals (e.g., data, information) via a wired or wireless transmission medium.
  • Each network entity 105, or an associated processor (e.g., controller) providing instructions to an interface of the network entity 105 may be configured to communicate with one or more of the other network entities 105 via the transmission medium.
  • a CU 160-a may host one or more higher layer control functions. Such control functions may include RRC, PDCP, SDAP, or the like. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by the CU 160-a.
  • a CU 160-a may be configured to handle user plane functionality (e.g., CU-UP) , control plane functionality (e.g., CU-CP) , or a combination thereof.
  • a CU 160-a may be logically split into one or more CU-UP units and one or more CU-CP units.
  • a CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface, such as an E1 interface when implemented in an O-RAN configuration.
  • a CU 160-a may be implemented to communicate with a DU 165-a, as necessary, for network control and signaling.
  • a DU 165-a may correspond to a logical unit that includes one or more functions (e.g., base station functions, RAN functions) to control the operation of one or more RUs 170-a.
  • a DU 165-a may host, at least partially, one or more of an RLC layer, a MAC layer, and one or more aspects of a PHY layer (e.g., a high PHY layer, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, or the like) depending, at least in part, on a functional split, such as those defined by the 3rd Generation Partnership Project (3GPP) .
  • a DU 165-a may further host one or more low PHY layers. Each layer may be implemented with an interface configured to communicate signals with other layers hosted by the DU 165-a, or with control functions hosted by a CU 160-a.
  • lower-layer functionality may be implemented by one or more RUs 170-a.
  • an RU 170-a controlled by a DU 165-a, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (e.g., performing fast Fourier transform (FFT) , inverse FFT (iFFT) , digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like) , or both, based at least in part on the functional split, such as a lower-layer functional split.
  • FFT fast Fourier transform
  • iFFT inverse FFT
  • PRACH physical random access channel extraction and filtering, or the like
  • an RU 170-a may be implemented to handle over the air (OTA) communication with one or more UEs 115-a.
  • OTA over the air
  • real-time and non-real-time aspects of control and user plane communication with the RU (s) 170-a may be controlled by the corresponding DU 165-a.
  • a configuration may enable a DU 165-a and a CU 160-a to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.
  • the SMO 180-a may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network entities 105.
  • the SMO 180-a may be configured to support the deployment of dedicated physical resources for RAN coverage requirements which may be managed via an operations and maintenance interface (e.g., an O1 interface) .
  • the SMO 180-a may be configured to interact with a cloud computing platform (e.g., an O-Cloud 205) to perform network entity life cycle management (e.g., to instantiate virtualized network entities 105) via a cloud computing platform interface (e.g., an O2 interface) .
  • a cloud computing platform e.g., an O-Cloud 205
  • network entity life cycle management e.g., to instantiate virtualized network entities 105
  • a cloud computing platform interface e.g., an O2 interface
  • the Non-RT RIC 175-a may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence (AI) or Machine Learning (ML) workflows including model training and updates, or policy-based guidance of applications/features in the Near-RT RIC 175-b.
  • the Non-RT RIC 175-a may be coupled to or communicate with (e.g., via an A1 interface) the Near-RT RIC 175-b.
  • the Non-RT RIC 175-a may monitor long-term trends and patterns for performance and employ AI or ML models to perform corrective actions through the SMO 180-a (e.g., reconfiguration via O1) or via generation of RAN management policies (e.g., A1 policies) .
  • AI or ML models to perform corrective actions through the SMO 180-a (e.g., reconfiguration via O1) or via generation of RAN management policies (e.g., A1 policies) .
  • a network entity 105 may communicate with a UE 115-a via an uplink dense deployment, in which the network entity 105 may transmit downlink communications to the UE 115-a and may receive uplink communications from the UE 115-a via another node, such as an RU 170-a.
  • the network entity 105 may transmit downlink communications to the UE 115-a and may receive uplink communications from the UE 115-a via another node, such as an RU 170-a.
  • techniques for the UE 115-a to calculate an uplink transmit power may be ambiguous.
  • the network entity 105 may transmit, to the UE 115-a, a single message that is associated with multiple TCI states.
  • the message may be a TCI state activation MAC-CE or another type of MAC-CE, in some examples.
  • the message may be transmitted after the UE 115-a is configured with one or more TCI states across one or more CCs.
  • the uplink power control information may indicate a power control parameter for uplink pathloss calculation for the one or more CCs.
  • the power control parameter may be, for example, an uplink pathloss offset, an uplink pathloss scaling factor, or some other parameter that may be used in a calculation of uplink transmit power.
  • the power control parameter may correspond to one or more TCI states from the multiple TCI states configured for the UE 115-a.
  • the UE 115-a may transmit uplink communications via one or more CCs according to the one or more TCI states.
  • the uplink communications may be transmitted according to one or more transmit powers that are based on the power control parameter.
  • the uplink dense deployment 300 may be understood as or associated with an asymmetric downlink single transmission and reception point (sTRP) /uplink multi-transmission and reception point (mTRP) deployment scenarios, in intra-band intra-cell non-collocated mTRP scenarios, and with a unified TCI framework for mTRP (using, such as communicating via, FR1 or FR2) .
  • the uplink dense deployment 300 may support two closed-loop power control adjustment states for SRS, both separate from PUSCH, and pathloss offset configurations for pathloss calculation to uplink TRP (s) , when the pathloss reference signal is from a downlink sTRP (e.g., the downlink transmission point 305) .
  • the uplink dense deployment 300 may further support multi-downlink control information (DCI) -based two transmitter address toward uplink TRP (s) and downlink sTRP without using CoresetPoolIndex, while assuming backwards compatible PRACH resources.
  • DCI multi-downlink control
  • the network entity 105 may refer to a base station, a gNB, or another entity or node that controls or is otherwise associated with (such as connected with via a backhaul link) one or more uplink reception points 310.
  • the network entity 105 may be understood as including one or more uplink reception points 310 or as being communicatively coupled with the one or more uplink reception points 310 (via, for example, one or more backhaul links 315, which may be wired or wireless) .
  • the network entity 105 may receive or otherwise obtain uplink signaling from one or more UEs 115 via one or more uplink reception points 310.
  • the UE 115 and the network entity 105 may support one or more signaling designs according to which the network entity 105 may indicate a transmit power adjustment due to uplink pathloss change.
  • the network entity 105 may include a transmit power control (TPC) command in a MAC-CE to indicate (an update to) a pathloss offset, with the pathloss offset being relative to a measured downlink pathloss.
  • the TPC command may indicate an absolute pathloss offset or a relative offset with respect to a previous pathloss offset.
  • a pathloss offset may be sufficient to reconcile the difference between the downlink pathloss and the uplink pathloss.
  • a pathloss offset or a relative pathloss offset change may become larger.
  • the pathloss offset to reconcile the difference between downlink pathloss and uplink pathloss may exceed a range of the MAC-CE and the MAC-CE may be unable to update the pathloss offset to a suitable value (with such a suitable value being, for example, a value that reconciles the difference) .
  • the network entity 105 may transmit multiple MAC-CEs to reconcile the difference, which may lead to inaccurate uplink power control or higher signaling overhead.
  • the UE 115 may apply the pathloss offset to a reference pathloss where the reference pathloss may be one of a measured downlink pathloss or a nominal pathloss. Whether the measured downlink pathloss or the nominal pathloss is used as the reference pathloss may be determined based on one or more rules (e.g., predefined or configured rules) or based on an indication from the network.
  • rules e.g., predefined or configured rules
  • the nominal pathloss may be one of an initial measured downlink pathloss associated with the same TCI state as the pathloss offset, an initial uplink pathloss associated with the same TCI state as the pathloss offset, a previous or latest uplink pathloss associated with the same TCI state as the pathloss offset or a previous or latest downlink pathloss associated with the same TCI state as the pathloss offset.
  • the UE 115 may apply a pathloss scaling factor (e.g., a scaling factor for uplink pathloss) to the nominal pathloss or the measured downlink pathloss for uplink power control.
  • Such a pathloss scaling factor may be a ratio of an uplink pathloss to a reference pathloss, where the reference pathloss may be the nominal pathloss or the measured downlink pathloss.
  • the pathloss scaling factor may be applied separately from a pathloss compensation coefficient ⁇ .
  • the pathloss scaling factor may be an additional ⁇ parameter such that PL b, f, c (q d ) is replaced by ⁇ *PL b, f, c (q d ) and such that ⁇ *PL b, f, c (q d ) is replaced by ⁇ * ⁇ *PL b, f, c (q d ) .
  • the pathloss scaling factor may be combined with the pathloss compensation coefficient ⁇ .
  • the network entity 105 may configure a set of ⁇ values and each of the ⁇ values may correspond to a combined scaling factor of a pathloss compensation coefficient and a pathloss scaling factor.
  • a pathloss offset or a scaling factor that is indicated to the UE 115 is per TCI state. That is, a MAC-CE or other control message may update a TPC command for a given uplink TCI state.
  • one or more TCI states may be activated for uplink communications by the UE 115 via a given CC or across multiple CCs.
  • the network entity 105 may configure multiple TCI states for the UE 115, or the network entity 105 may transmit an activation MAC-CE that activates one or more TCI states for the UE 115, or both, as described with reference to FIG. 1. In such cases, using separate MAC-CEs to update the pathloss offset or scaling factor for different uplink TCI states may increase overhead.
  • the network entity 105 may transmit a single control message, such as the single MAC-CE 330, that indicates uplink power control adjustment information for multiple TCI states.
  • the single control message may include a single uplink power control parameter that may be applied to multiple TCI states for communications via a single CC or multiple CCs.
  • the single control message may further indicate which TCI states the power control parameter may be applied to.
  • the UE 115 may thereby receive the power control parameter, determine which TCI states the power control parameter applies to, and calculate one or more uplink transmit power (s) for the TCI states based on the power control parameter.
  • the power control parameter may be used for uplink pathloss calculation, in some examples.
  • the power control parameter may be a pathloss offset, a pathloss scaling factor, or both.
  • the UE 115 may utilize the pathloss offset or scaling factor in a calculation of transmit power for a given TCI state.
  • the network entity 105 may transmit the power control parameter to update a transmit power at the UE 115.
  • the uplink pathloss and scaling factor may be applied relative to a previous or latest measured downlink pathloss or a nominal pathloss.
  • the control message described herein may include one or more fields to indicate whether to apply the parameter to the measured or nominal pathloss.
  • the single control message that conveys the power control parameter may be, for example, a unified TCI state activation MAC-CE 330, a separate MAC-CE 330, or may be indicated via a combination of both.
  • the network entity 105 may indicate, via control signaling that configures a set of TCI states for the UE 115 (e.g., RRC configuration) , whether pathloss offset indication is enabled or disabled for each TCI state.
  • FIG. 4 shows an example of an uplink power control message 400 that supports power control information for multiple transmission configuration indication states in accordance with one or more aspects of the present disclosure.
  • the uplink power control message 400 may implement or be implemented by aspects of the wireless communications system 100, the network architecture 200, and the uplink dense deployment 300, as described with reference to FIGs. 1–3.
  • the uplink power control message 400 represents an example format or configuration of a single control message that is operable to convey uplink power control information for multiple TCI states over one or more CCs.
  • the uplink power control message 400 illustrated in FIG. 4 may be a MAC-CE in this example. Although described with reference to a MAC-CE, it is to be understood that any other type of message may be used in a similar manner to indicate uplink power control information for multiple TCI states. In this example, one or more reserved bits 405 in the message are used to convey the uplink power control information. Thus, any quantity of one or more bits that are not being used in the MAC-CE for indicating other information may be repurposed for indicating uplink power control information as described herein.
  • the uplink power control message 400 may also be operable to convey TCI state activation information.
  • the uplink power control message 400 may include one or more TCI state activation fields 410 (e.g., TCI state activation fields 410-a, 410-b, through 410-n) that may include one or more bits to indicate an ID of a corresponding TCI state to be activated for the UE.
  • the uplink power control message 400 may thereby represent an example of a TCI state activation MAC-CE, in some examples. As described with reference to FIG.
  • the TCI state activation MAC-CE may be operable to active up to a threshold quantity of TCI states (e.g., eight, or some other quantity) from among a set of multiple TCI states indicated via a previous RRC configuration for the UE.
  • the TCI states may be uplink TCI states, downlink TCI states, or both.
  • the uplink power control message 400 may include one or more P fields 415 that indicate whether each TCI state activation field 410 (e.g., TCI codepoint) indicates multiple TCI states or a single TCI state. For example, if a given P field 415, such as an i-th field Pi, is set to a first value (e.g., ‘1’ ) , the field may indicate that the corresponding i-th TCI state activation field 410 includes both a downlink TCI state and an uplink TCI state.
  • a given P field 415 such as an i-th field Pi
  • a first value e.g., ‘1’
  • the field may indicate that the corresponding i-th TCI state activation field 410 includes only a downlink or joint TCI state or only an uplink TCI state.
  • the uplink power control message 400 may include one or more downlink/uplink fields 420 that indicate whether each TCI state activation field 410 is for an uplink TCI state or a downlink or joint TCI state.
  • the uplink power control message 400 may include multiple sets of information (e.g., octets, or sets of eight bits) . Each row illustrated in FIG. 4 may represent a set.
  • the downlink/uplink field 420 in a given set may indicate whether the TCI state ID that is in the same set is for an uplink TCI state or for a downlink or joint TCI state.
  • the field may indicate that the TCI state ID is used for downlink.
  • the downlink TCI state ID may be indicated via some quantity of bits, such as seven bits, in some examples.
  • the downlink/uplink field 420 is set to a second value (e.g., ‘0’ ) , the field may indicate that the TCI state ID is used for uplink.
  • the uplink TCI state ID may be indicated via some quantity of bits, such as six bits, in some examples, such that one or more remaining or extra bits may be unused or repurposed. For example, the one or more remaining bits may be used as an extra reserved bit 405-c to indicate power control information, as described herein.
  • the network may convey uplink power control information for multiple TCI states via a separate MAC-CE or other type of message, in some examples.
  • a separate MAC-CE different than the unified TCI state activation MAC-CE may be used to update power control information (e.g., pathloss offset, scaling factor, or the like) for multiple TCI states.
  • the uplink power control message 400 is a separate MAC-CE, the uplink power control message 400 may not include the TCI state activation fields 410, among other types of fields.
  • the network may indicate the power control parameter and other uplink power control information via one or more bits or other fields in the separate MAC-CE.
  • One or more other bits or fields in the uplink power control message 400 may not be used to convey information, in some examples. Such bits may be referred to as reserved bits 405 herein.
  • the uplink power control message 400 may include a reserved bit 405-a, a set of reserved bits 405-b, and at least one reserved bit 405-c in at least one of the TCI state activation fields 410.
  • Techniques described herein provide for a network entity to repurpose the one or more reserved bits 405 to indicate uplink power control information.
  • the quantity of reserved bits to be reused may be up to seven plus M bits, where M may represent a quantity of activated uplink TCI states.
  • a set of reserved bits 405-b may be used to convey a value of a power control parameter for multiple TCI states.
  • the power control parameter may be, for example, an uplink pathloss offset, an uplink pathloss scaling factor, or some other type of parameter for uplink power control.
  • another one of the reserved bits 405, such as the reserved bit 405-a in the uplink power control message 400 may be used to indicate whether the remaining reserved bits are used to indicate the pathloss offset (e.g., as a TPC command) or not.
  • the power control parameter indicated via the set of reserved bits 405-b may be applied to each of the activated uplink TCI states. That is, a receiving UE may apply the power control parameter to each uplink TCI state ID that is included in the uplink power control message 400 when the UE calculates uplink transmit power (s) for the uplink TCI states.
  • the activated uplink TCI states may be indicated via the TCI state activation fields 410 in the uplink power control message 400 or in TCI state activation fields in a separate message (e.g., an uplink TCI state activation message) , if the uplink power control message 400 is separate from a TCI state activation message.
  • the power control parameter indicated via the set of reserved bits 405-b may be applied to each of the activated uplink TCI states that are also associated with an uplink power control parameter configuration (e.g., enabled with pathloss offset by RRC) .
  • the UE may receive control signaling that configures multiple potential TCI states for the UE and indicates whether each TCI state is configured with an uplink power control parameter configuration or not (e.g., whether each TCI state supports uplink pathloss offset indication or whether the pathloss offset is enabled for each TCI state) .
  • the UE may apply the power control parameter to the TCI states that are indicated in the uplink power control message 400 and that are configured for uplink power control via the previous control message when the UE calculates uplink transmit power (s) for the uplink TCI states.
  • whether the power control parameter indicated via the set of reserved bits 405-b is to be applied to a given activated TCI state may be indicated by a respective reserved bit 405-c in the corresponding uplink TCI state activation field 410.
  • a TCI state activation field 410 such as the TCI state activation field 410-b
  • the ID of the uplink TCI state may not occupy all of the bits in the TCI state activation field 410-b, and there may be one or more reserved bits 405-c.
  • the reserved bits 405-c in each TCI state activation field 410 that activates an uplink TCI state may thereby be used to indicate whether the power control parameter indicated via the set of reserved bits 405-b is applied to the corresponding TCI state. Additionally, or alternatively, the reserved bit (s) 405-c in the TCI state activation fields 410 may be reused to indicate a portion of the uplink power control parameter if, for example, the set of reserved bits 405-b is not large enough.
  • the power control parameter may be, for example, an uplink pathloss offset, an uplink pathloss scaling factor, or some other type of parameter for uplink power control.
  • a quantity of bits used to indicate a pathloss offset may be greater than a quantity of bits to indicate a pathloss scaling factor.
  • all or a portion of the reserved bits 405-b may be used to convey the value of the uplink power control parameter, depending on a value and type of the power control parameter.
  • the uplink power control message 400 may thereby be utilized to indicate a power control parameter for multiple TCI states across multiple CCs.
  • a set of CCs to which the power control parameter applies may be configured via a CC list.
  • a set of CCs may be configured for TCI state activation.
  • a TCI state activation MAC-CE may indicate TCI states that are activated across the set of CCs.
  • the set of CCs for TCI state activation may be used for power control parameter indications.
  • the uplink power control message 400 indicates, via the reserved bits 405-b, a single power control parameter applicable to multiple TCI state IDs in a CC (e.g., power control parameter is indicated for one CC in a set of CCs)
  • the power control parameter may be applied to the same set of TCI state IDs across all CCs of the set of CCs.
  • the uplink power control message 400 indicates, via the reserved bits 405-b, multiple power control parameters for a set of TCI state IDs in a single CC, with each power control parameter corresponding to a single uplink TCI state ID, the power control parameters may be applied to the same TCI state IDs on all CCs across the set of CCs.
  • the power control parameter-to-TCI state ID mapping indicated via the uplink power control message 400 may be for a single CC, and may be applied across all CCs in the set of CCs configured for both TCI state activation and uplink power control parameter indication.
  • a separate set of CCs for power control parameter indication may be supported and may be different than the set of CCs for TCI state activation.
  • the uplink power control message 400 indicates, via the reserved bits 405-b, a single power control parameter applicable to multiple TCI state IDs in a CC (e.g., power control parameter is indicated for one CC in a set of CCs)
  • the power control parameter may be applied to the same set of TCI state IDs across all CCs of the set of CCs.
  • the power control parameters may be applied to the same TCI state IDs on all CCs across the set of CCs when the same TCI state ID for the one or more CCs are activated with corresponding power control updates enabled. That is, the power control parameter-to-TCI state ID mapping indicated via the uplink power control message 400 may be for a single CC, and may be applied across all CCs in the set of CCs configured for both TCI state activation and uplink power control parameter indication.
  • FIG. 5 shows an example of an uplink power control message 500 that supports power control information for multiple transmission configuration indication states in accordance with one or more aspects of the present disclosure.
  • the uplink power control message 500 may implement or be implemented by aspects of the wireless communications system 100, the network architecture 200, and the uplink dense deployment 300, as described with reference to FIGs. 1–3.
  • the uplink power control message 500 represents an example format or configuration of a single control message that is operable to convey uplink power control information for multiple TCI states over one or more CCs.
  • the uplink power control message 500 illustrated in FIG. 5 may be a MAC-CE in this example. Although described with reference to a MAC-CE, it is to be understood that any other type of message may be used in a similar manner to indicate uplink power control information for multiple TCI states.
  • the uplink power control message 500 may also be operable to convey TCI state activation information.
  • the uplink power control message 500 may include one or more TCI state activation fields 510 (e.g., TCI state activation fields 510-a, 510-b, through 510-n) that may include one or more bits to indicate an ID of a corresponding TCI state to be activated for the UE.
  • the uplink power control message 500 may thereby represent an example of a TCI state activation MAC-CE, in some examples.
  • the TCI state activation MAC-CE may be operable to active up to a threshold quantity of TCI states (e.g., eight, or some other quantity) from among a set of multiple TCI states indicated via a previous RRC configuration for the UE.
  • the TCI states may be uplink TCI states, downlink TCI states, or both.
  • the uplink power control message 500 may include a serving cell ID field, which may indicate a serving cell ID for which the uplink power control message 500 applies. If the indicated serving cell is configured as part of a simultaneous TCI update list (e.g., simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3 or simultaneousU-TCI-UpdateList4) , the uplink power control message 500 may apply to all serving cells that are included in the set of CCs in the simultaneous TCI update list.
  • the uplink power control message 500 may include an uplink BWP ID field and a downlink BWP ID field, which may indicate a BWP that the message applies for a downlink or uplink TCI state, respectively.
  • the uplink power control message 500 may include one or more P fields 515 that indicate whether each TCI state activation field 510 (e.g., TCI codepoint) indicates multiple TCI states or a single TCI state.
  • the uplink power control message 500 may include one or more downlink/uplink fields 520 that indicate whether each TCI state activation field 510 is for an uplink TCI state or a downlink or joint TCI state.
  • the uplink power control message 500 may include multiple sets of information (e.g., octets, or sets of eight bits) . Each row illustrated in FIG. 4 may represent a set.
  • the downlink/uplink field 520 in a given set may indicate whether the TCI state ID that is in the same set is for an uplink TCI state or for a downlink or joint TCI state.
  • the field may indicate that the TCI state ID is used for downlink.
  • the downlink TCI state ID may be indicated via some quantity of bits, such as seven bits, in some examples.
  • the downlink/uplink field 520 is set to a second value (e.g., ‘0’ ) , the field may indicate that the TCI state ID is used for uplink.
  • the uplink TCI state ID may be indicated via some quantity of bits, such as six bits, in some examples, such that one or more remaining or extra bits may be unused or repurposed. For example, the one or more remaining bits may be used as an extra reserved bit 505-b to indicate power control information, as described herein.
  • the network may convey uplink power control information for multiple TCI states via a separate MAC-CE or other type of message, in some examples.
  • a separate MAC-CE different than the unified TCI state activation MAC-CE may be used to update power control information (e.g., pathloss offset, scaling factor, or the like) for multiple TCI states.
  • the uplink power control message 500 is a separate MAC-CE, the uplink power control message 500 may not include the TCI state activation fields 510, among other types of fields.
  • the network may indicate the power control parameter and other uplink power control information via one or more of the power control parameter fields 525 in a separate MAC-CE.
  • the uplink power control message 500 may include one or more power control parameter fields 525 (e.g., power control parameter fields 525-a through 525-m) .
  • the power control parameter fields 525 may represent additional fields (e.g., bits) appended to or otherwise included in the uplink power control message 500 and configured to convey information indicative of one or more power control parameters for multiple TCI states.
  • the uplink power control message 500 may include a single power control parameter field 525-a. That is, although the power control parameter fields 525-b through 525-m are illustrated in FIG. 5, in some examples, the uplink power control message 500 may not include these fields.
  • the single power control parameter field 525-a in the uplink power control message 500 may include one or more bits configured to convey a value of a power control parameter for multiple TCI states (e.g., power control parameter 1) .
  • a reserved bit 505-a in the uplink power control message 500 may be used to indicate whether the power control parameter field 525-a is present or not.
  • the power control parameter indicated via the power control parameter field 525-a may be applied to each of the activated uplink TCI states. That is, a receiving UE may apply the power control parameter to each uplink TCI state ID that is included in the uplink power control message 500 when the UE calculates uplink transmit power (s) for the uplink TCI states.
  • the activated uplink TCI states may be indicated via the TCI state activation fields 510 in the uplink power control message 500 or in TCI state activation fields in a separate message (e.g., an uplink TCI state activation message) , if the uplink power control message 500 is separate from a TCI state activation message.
  • the power control parameter indicated via the power control parameter field 525-a may be applied to each of the activated uplink TCI states that are also associated with an uplink power control parameter configuration (e.g., enabled with pathloss offset by RRC) .
  • the UE may receive control signaling that configures multiple potential TCI states for the UE and indicates whether each TCI state is configured with an uplink power control parameter configuration or not (e.g., whether each TCI state supports uplink pathloss offset indication or whether the pathloss offset is enabled for each TCI state) .
  • the UE may apply the power control parameter to the TCI states that are indicated in the uplink power control message 500 and that are configured for uplink power control via the previous control message when the UE calculates uplink transmit power (s) for the uplink TCI states.
  • whether the power control parameter indicated via the power control parameter field 525-a is to be applied to a given activated TCI state may be indicated by a respective reserved bit 505-b in the corresponding uplink TCI state activation field 510.
  • a TCI state activation field 510 such as the TCI state activation field 510-b
  • the ID of the uplink TCI state may not occupy all of the bits in the TCI state activation field 510-b, and there may be one or more reserved bits 505-b.
  • the reserved bits 505-b in each TCI state activation field 510 that activates an uplink TCI state may thereby be used to indicate whether the power control parameter indicated via the power control parameter field 525-a is present for the corresponding TCI state. Additionally, or alternatively, the reserved bit (s) 505-b in the TCI state activation fields 510 may be reused to indicate a portion of the uplink power control parameter if, for example, the power control parameter field 525-a is not large enough.
  • the uplink power control message 500 may include multiple power control parameter fields 525, such as power control parameter fields 525-a, 525-b, through 525-m.
  • a quantity of power control parameter fields 525, M may be the same as a quantity of activated uplink TCI states in the uplink power control message 500, in some examples.
  • the quantity of TCI state activation fields 510 in the uplink power control message 500 may be equal to N and may include uplink TCI states, downlink TCI states, or any combination thereof.
  • the quantity of uplink TCI states in the uplink power control message 500 may be equal to M, which may also correspond to a quantity of power control parameter fields 525 that are appended to or otherwise included in the uplink power control message 500.
  • the uplink power control message 500 includes the same quantity of power control parameter fields 525 as uplink TCI states, at least one reserved bit 505-a in the uplink power control message 500 may be used to indicate whether the multiple power control parameter fields 525 are present or not.
  • Each power control parameter field 525 may indicate a respective power control parameter, which may be the same parameter or one or more different parameters.
  • a receiving UE may apply the power control parameter indicated via each power control parameter field 525 to a respective TCI state from among the multiple uplink TCI states in the uplink power control message 500.
  • a quantity of power control parameter fields 525 that are included in the uplink power control message 500 may be the same as a quantity of activated uplink TCI states in the uplink power control message 500 that are also associated with (e.g., configured for) an uplink power control parameter configuration via a previous control message (e.g., an RRC message) . If the uplink power control message 500 includes the same quantity of power control parameter fields 525 as uplink TCI states that are activated and configured for uplink power control, at least one reserved bit 505-a in the uplink power control message 500 may be used to indicate whether the multiple power control parameter fields 525 are present or not. Each power control parameter field 525 may indicate a respective power control parameter, which may be the same parameter or one or more different parameters. A receiving UE may apply the power control parameter indicated via each power control parameter field 525 to a respective TCI state from among the multiple uplink TCI states in the uplink power control message 500 that are also configured for uplink power control.
  • a quantity of power control parameter fields 525 included in the uplink power control message 500 may be indicated.
  • a reserved bit 505-b e.g., a most significant bit
  • the reserved bit 505-b may indicate whether the uplink power control message 500 includes a power control parameter field 525 for the TCI state indicated via the TCI state activation field 510-b.
  • the reserved bit 505-b is set to a first value, there may not be a corresponding power control parameter field 525. If the reserved bit 505-b is set to a second value, the bit may indicate that the power control parameter field 525-a, for example, is associated with (e.g., indicates power control information for) the TCI state indicated via the TCI state activation field 510-b. In this case, the network may refrain from indicating whether power control update is enabled or not per TCI state, in some examples.
  • the uplink power control message 500 may include a power control parameter field 525 for a given activated uplink TCI state indicated via the uplink power control message 500 if the corresponding TCI state is enabled for power control updates via a previous control message (e.g., an RRC message) .
  • a previous control message e.g., an RRC message
  • the uplink power control message 500 may not include the TCI state activation fields 510.
  • the uplink power control message 500 may include multiple power control parameter fields 525 and an uplink TCI state ID may be associated with or included in each of the multiple power control parameter fields.
  • the uplink TCI state ID may indicate that the power control parameter indicated in the power control parameter field 525 is to applied to the corresponding uplink TCI state.
  • the MAC-CE may include multiple TCI state fields each corresponding to a respective power control parameter field 525 to indicate the TCI state ID associated with each power control parameter field 525.
  • Such power control parameter fields 525 including TCI state IDs may be included in the uplink power control message 500 regardless of whether power control is enabled by an RRC configuration. Additionally, or alternatively, the power control parameter fields 525 including TCI state IDs may be included in the uplink power control message 500 if power control is enabled by RRC for a given uplink TCI state.
  • the power control parameter (s) indicated via the power control parameter fields 525 in the uplink power control message 500 may be, for example, an uplink pathloss offset, an uplink pathloss scaling factor, or some other type of parameter for uplink power control.
  • an uplink pathloss offset may be indicated via a greater quantity of bits than an uplink pathloss scaling factor.
  • the power control parameter fields 525 may be smaller in size for uplink pathloss scaling factor indications, or one or more bits in the power control parameter fields 525 used to indicate a scaling factor may be repurposed, or both.
  • the uplink power control message 500 may thereby be utilized to indicate a power control parameter for multiple TCI states across multiple CCs.
  • a set of CCs to which the power control parameter applies may be configured via a CC list.
  • a set of CCs may be configured for TCI state activation.
  • a TCI state activation MAC-CE may indicate TCI states that are activated across the set of CCs.
  • the set of CCs for TCI state activation may be used for power control parameter indications.
  • the uplink power control message 500 indicates, via one or more power control parameter fields 525, a single power control parameter applicable to multiple TCI state IDs in a CC (e.g., power control parameter is indicated for one CC in a set of CCs)
  • the power control parameter may be applied to the same set of TCI state IDs across all CCs of the set of CCs.
  • the uplink power control message 500 indicates, via one or more power control parameter fields 525, multiple power control parameters for a set of TCI state IDs in a single CC, with each power control parameter corresponding to a single uplink TCI state ID, the power control parameters may be applied to the same TCI state IDs on all CCs across the set of CCs.
  • the power control parameter-to-TCI state ID mapping indicated via the uplink power control message 500 may be for a single CC, and may be applied across all CCs in the set of CCs configured for both TCI state activation and uplink power control parameter indication.
  • a separate set of CCs for power control parameter indication may be supported and may be different than the set of CCs for TCI state activation.
  • the uplink power control message 500 indicates, via one or more power control parameter fields 525, a single power control parameter applicable to multiple TCI state IDs in a CC (e.g., power control parameter is indicated for one CC in a set of CCs)
  • the power control parameter may be applied to the same set of TCI state IDs across all CCs of the set of CCs.
  • the uplink power control message 500 indicates, via one or more power control parameter fields 525, multiple power control parameters for a set of TCI state IDs in a single CC, with each power control parameter corresponding to a single uplink TCI state ID, the power control parameters may be applied to the same TCI state IDs on all CCs across the set of CCs when the same TCI state ID for the one or more CCs are activated with corresponding power control updates enabled. That is, the power control parameter-to-TCI state ID mapping indicated via the uplink power control message 500 may be for a single CC, and may be applied across all CCs in the set of CCs configured for both TCI state activation and uplink power control parameter indication.
  • FIG. 6 shows an example of a signaling sequence 600 that supports power control information for multiple transmission configuration indication states in accordance with one or more aspects of the present disclosure.
  • the signaling sequence 600 may implement or be implemented by aspects of the wireless communications system 100, the network architecture 200, the uplink dense deployment 300, or the uplink power control messages 400 and 500.
  • the signaling sequence 600 illustrates communication between a UE 115 and a network entity 105 (via a downlink transmission point 305 and an uplink reception point 310) , which may be examples of corresponding devices as described herein.
  • the signaling sequence 600 illustrates an example of uplink power control in accordance with signaling from the network entity 105 that indicates a power control parameter for multiple TCI states across one or more CCs.
  • the network entity 105 may use both a unified TCI state activation MAC-CE 625 and a separate MAC-CE 630 to indicate or update a power control parameter for multiple TCI states.
  • the unified TCI state activation MAC-CE 625 may indicate an initial power control parameter for one or more TCI states.
  • the UE 115 may calculate an initial power value based on the initial power control parameter with reference to a measured downlink power control parameter (e.g., a measured downlink pathloss) .
  • the UE 115 may subsequently receive a separate MAC-CE 630 that indicates an update or change in the power control parameter.
  • the unified TCI state activation MAC-CE 625 may be received before the separate MAC-CE 630.
  • the power control parameter may be described with reference to a pathloss offset in the example of FIG. 6. However, it is to be understood that the power control parameter may additionally, or alternatively, include a pathloss scaling factor, or some other parameter or value associated with uplink power control.
  • the UE 115 and the network entity 105 may exchange downlink communications, which may be associated with a measured downlink pathloss (denoted as PL_d in the example of FIG. 6) of 100 dB and a first uplink pathloss (denoted as PL_u in the example of FIG. 6) of 40 dB.
  • an initially indicated pathloss offset 645 (PL Offset 0) may be set to 60 dB to indicate an offset from the measured downlink pathloss to the target uplink pathloss.
  • the network entity 105 may transmit a unified TCI state activation MAC-CE 625 to the UE 115 to indicate the initially indicated pathloss offset 645.
  • the pathloss offset 645 may be associated with a first TCI state.
  • the pathloss offset 645 may reconcile a difference between the measured downlink pathloss of 100 dB and the uplink pathloss of 40 dB.
  • the unified TCI state activation MAC-CE 625 may be applied.
  • the UE 115 may transmit an uplink signal 635 using a first TCI state and a first transmit power.
  • the UE 115 may calculate the first transmit power for the first TCI state based on the uplink pathloss and one or more other parameters.
  • the unified TCI state activation MAC-CE 625 may indicate the pathloss offset 645 for the first TCI state and one or more other TCI states.
  • the unified TCI state activation MAC-CE 625 may include one or more reserved bits or power control parameter fields configured to indicate the pathloss offset 645.
  • the UE 115 may determine that the pathloss offset 645 is to be applied to the first TCI state based on whether the first TCI state is activated, is configured for uplink power control, based on one or more bits or fields in the unified TCI state activation MAC-CE 625, or any combination thereof, as described in further detail elsewhere herein, including with reference to FIGs. 4 and 5.
  • the network entity 105 may transmit a separate MAC-CE 630 including power control information that indicates a second pathloss offset 650 (e.g., a power control parameter) .
  • the second pathloss offset 650 may be a pathloss offset referenced with respect to a nominal pathloss.
  • the nominal pathloss may be one of an initial uplink pathloss, a previous uplink pathloss (e.g., PL U , PL UL1 ) , a previous downlink pathloss, an initial downlink pathloss (e.g., PL D , PL DL1 ) , or any combination thereof.
  • the second pathloss offset 650 indicated via the MAC-CE 630 may be a pathloss offset with respect to a measured downlink pathloss or a nominal pathloss. Whether the second pathloss offset 650 is with respect to the nominal pathloss or the measured downlink pathloss may be indicated via one or more fields in the MAC-CE 630.
  • multiple pathloss offsets may be indicated via the MAC-CE 630.
  • a single field in the MAC-CE 630 may be used to indicate whether all of the pathloss offsets are with respect to the corresponding measured downlink pathloss or the nominal pathloss.
  • multiple fields may be included in the MAC-CE 630 and may each correspond to a respective pathloss offset update field. These fields may be used to indicate whether the respective pathloss offset update field is with respect to the measured downlink pathloss or nominal pathloss.
  • Each pathloss offset may be associated with a respective TCI state and the reference parameter for each pathloss offset may also be associated with the same respective TCI state, in some examples.
  • the MAC-CE 630 may indicate the second pathloss offset 650 for the first TCI state relative to a nominal pathloss, which may be the previous uplink pathloss (e.g., PL UL1 ) .
  • the MAC-CE 630 may include a field that indicates the second pathloss offset 650 is relative to the nominal pathloss.
  • the MAC-CE 630 may be applied.
  • the UE 115 may transmit a second uplink signal 640 using the first TCI state and a second transmit power.
  • the UE 115 may calculate the second transmit power for the first TCI state based on the uplink pathloss PL UL2 and one or more other parameters.
  • the transmit power used by the UE 115 to transmit the second uplink signal 640 may be different than the transmit power used by the UE 115 to transmit the uplink signal 635 based on the differing uplink pathloss values.
  • the network entity 105 may thereby transmit a single message that indicates power control information for multiple TCI states.
  • the single message e.g., the MAC-CE 630
  • the uplink power control information may be a pathloss offset, a pathloss scaling factor, or some other power control parameter that can be used by the UE 115 to calculate a transmit power.
  • FIG. 7 shows an example of a process flow 700 that supports power control information for multiple transmission configuration indication states in accordance with one or more aspects of the present disclosure.
  • the process flow 700 may implement or be implemented by aspects of the wireless communications system 100, the network architecture 200, the uplink dense deployment 300, the uplink power control messages 400 and 500, or the signaling sequence 600.
  • the process flow 700 illustrates communications between a network entity 105 and a UE 115, which may represent aspects of corresponding devices as described with reference to FIGs. 1–6.
  • the network entity 105 may transmit, via a single message, uplink power control information for multiple TCI states supported by the UE 115.
  • the operations between the network entity 105 and the UE 115 may be performed in different orders or at different times. Some operations may also be left out of the process flow 700, or other operations may be added. Although the network entity 105 and the UE 115 are shown performing the operations of the process flow 700, some aspects of some operations may also be performed by one or more other wireless devices.
  • the network entity 105 may transmit, to the UE 115, a control message that indicates multiple TCI states for uplink communications by the UE 115 via one or more CCs.
  • the control message may be an RRC message, in some examples.
  • the network entity may transmit an RRC configuration that indicates the multiple potential TCI states supported by the UE 115.
  • the control message may indicate whether an uplink power control parameter configuration is enabled or disabled for the multiple TCI states.
  • the control message may indicate, for each TCI state, whether the TCI state supports power control updates (e.g., whether pathloss offset is enabled) .
  • the network entity 105 may transmit, to the UE 115, a message including uplink power control information for multiple TCI states supported by the UE 115 (e.g., at least two TCI states) .
  • the uplink power control information may indicate a power control parameter for uplink pathloss calculation for the one or more CCs.
  • the power control parameter may correspond to one or more TCI states from among the multiple TCI states indicated via the control message.
  • the message may be a MAC-CE or some other type of message.
  • the message may represent an example of the uplink power control messages 400 and 500, or the MAC-CE 630 as described with reference to FIGs. 4–6.
  • the message may include one or more bits or fields that convey the power control parameter and information that indicates which TCI states the parameter applies to, a reference parameter, or any combination thereof.
  • the UE 115 may determine (e.g., calculate) one or more transmit powers for the one or more TCI states based on the power control parameter. For example, the UE 115 may input the power control parameter into an equation or algorithm for calculating uplink transmit power for a given TCI state, along with one or more other parameters for uplink transmit power calculation.
  • each TCI state may be associated with a respective equation or set of parameters. As such, the transmit power for each TCI state may be the same or different.
  • the UE 115 may transmit, to the network entity 105 via one or more CCs, the uplink communications using the one or more transmit powers calculated at 715.
  • the UE 115 may transmit the uplink communications according to the one or more TCI states and the one or more transmit powers that are based on the power control parameter indicated at 710.
  • the network entity 105 may thereby transmit, via a single message, uplink power control information applicable to multiple TCI states of the UE 115.
  • the UE 115 may utilize the information to calculate uplink transmit power (s) for uplink communications, which may improve throughput and reliability of the wireless communications while reducing overhead as compared with systems in which the uplink power control information may be indicated per TCI state.
  • FIG. 8 shows a block diagram 800 of a device 805 that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure.
  • the device 805 may be an example of aspects of a UE 115 as described herein.
  • the device 805 may include a receiver 810, a transmitter 815, and a communications manager 820.
  • the device 805, or one or more components of the device 805 may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 810 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to power control information for multiple TCI states) . Information may be passed on to other components of the device 805.
  • the receiver 810 may utilize a single antenna or a set of multiple antennas.
  • the transmitter 815 may provide a means for transmitting signals generated by other components of the device 805.
  • the transmitter 815 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to power control information for multiple TCI states) .
  • the transmitter 815 may be co-located with a receiver 810 in a transceiver module.
  • the transmitter 815 may utilize a single antenna or a set of multiple antennas.
  • the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be examples of means for performing various aspects of power control information for multiple TCI states as described herein.
  • the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be capable of performing one or more of the functions described herein.
  • At least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory) .
  • the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code) . If implemented in code executed by at least one processor, the functions of the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure) .
  • the communications manager 820 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 810, the transmitter 815, or both.
  • the communications manager 820 may receive information from the receiver 810, send information to the transmitter 815, or be integrated in combination with the receiver 810, the transmitter 815, or both to obtain information, output information, or perform various other operations as described herein.
  • the communications manager 820 may support wireless communication in accordance with examples as disclosed herein.
  • the communications manager 820 is capable of, configured to, or operable to support a means for receiving a control message that indicates a set of multiple TCI states for uplink communications by the UE via one or more CCs.
  • the communications manager 820 is capable of, configured to, or operable to support a means for receiving a message including uplink power control information that indicates a power control parameter for uplink pathloss calculation for the one or more CCs, the power control parameter corresponding to one or more TCI states from among the set of multiple TCI states.
  • the communications manager 820 is capable of, configured to, or operable to support a means for transmitting, via the one or more CCs in accordance with the one or more TCI states, the uplink communications using one or more transmit powers that are based on the power control parameter.
  • the device 805 e.g., at least one processor controlling or otherwise coupled with the receiver 810, the transmitter 815, the communications manager 820, or a combination thereof
  • the device 805 may support techniques for reduced processing, reduced power consumption, and more efficient utilization of communication resources, among other examples.
  • FIG. 9 shows a block diagram 900 of a device 905 that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure.
  • the device 905 may be an example of aspects of a device 805 or a UE 115 as described herein.
  • the device 905 may include a receiver 910, a transmitter 915, and a communications manager 920.
  • the device 905, or one or more components of the device 905 may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 910 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to power control information for multiple TCI states) . Information may be passed on to other components of the device 905.
  • the receiver 910 may utilize a single antenna or a set of multiple antennas.
  • the transmitter 915 may provide a means for transmitting signals generated by other components of the device 905.
  • the transmitter 915 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to power control information for multiple TCI states) .
  • the transmitter 915 may be co-located with a receiver 910 in a transceiver module.
  • the transmitter 915 may utilize a single antenna or a set of multiple antennas.
  • the device 905, or various components thereof may be an example of means for performing various aspects of power control information for multiple TCI states as described herein.
  • the communications manager 920 may include a TCI state component 925, an uplink power control component 930, a transmit power component 935, or any combination thereof.
  • the communications manager 920 may be an example of aspects of a communications manager 820 as described herein.
  • the communications manager 920, or various components thereof may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 910, the transmitter 915, or both.
  • the communications manager 920 may receive information from the receiver 910, send information to the transmitter 915, or be integrated in combination with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.
  • the communications manager 920 may support wireless communication in accordance with examples as disclosed herein.
  • the TCI state component 925 is capable of, configured to, or operable to support a means for receiving a control message that indicates a set of multiple TCI states for uplink communications by the UE via one or more CCs.
  • the uplink power control component 930 is capable of, configured to, or operable to support a means for receiving a message including uplink power control information that indicates a power control parameter for uplink pathloss calculation for the one or more CCs, the power control parameter corresponding to one or more TCI states from among the set of multiple TCI states.
  • the transmit power component 935 is capable of, configured to, or operable to support a means for transmitting, via the one or more CCs in accordance with the one or more TCI states, the uplink communications using one or more transmit powers that are based on the power control parameter.
  • FIG. 10 shows a block diagram 1000 of a communications manager 1020 that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure.
  • the communications manager 1020 may be an example of aspects of a communications manager 820, a communications manager 920, or both, as described herein.
  • the communications manager 1020, or various components thereof may be an example of means for performing various aspects of power control information for multiple TCI states as described herein.
  • the communications manager 1020 may include a TCI state component 1025, an uplink power control component 1030, a transmit power component 1035, a MAC-CE component 1040, a frequency configuration component 1045, a pathloss component 1050, a power control parameter component 1055, or any combination thereof.
  • Each of these components, or components or subcomponents thereof e.g., one or more processors, one or more memories
  • the communications manager 1020 may support wireless communication in accordance with examples as disclosed herein.
  • the TCI state component 1025 is capable of, configured to, or operable to support a means for receiving a control message that indicates a set of multiple TCI states for uplink communications by the UE via one or more CCs.
  • the uplink power control component 1030 is capable of, configured to, or operable to support a means for receiving a message including uplink power control information that indicates a power control parameter for uplink pathloss calculation for the one or more CCs, the power control parameter corresponding to one or more TCI states from among the set of multiple TCI states.
  • the transmit power component 1035 is capable of, configured to, or operable to support a means for transmitting, via the one or more CCs in accordance with the one or more TCI states, the uplink communications using one or more transmit powers that are based on the power control parameter.
  • the power control parameter component 1055 is capable of, configured to, or operable to support a means for receiving the power control parameter via a set of one or more reserved bits within the MAC-CE, an uplink power control field within the MAC-CE, or both.
  • the power control parameter component 1055 is capable of, configured to, or operable to support a means for receiving, via a set of multiple uplink power control fields within the MAC-CE, the power control parameter.
  • a quantity of the set of multiple uplink power control fields is based on a quantity of TCI states from among the set of multiple TCI states that are activated for the uplink communications by the UE. In some examples, the quantity of the set of multiple uplink power control fields is based on the quantity of TCI states from among the set of multiple TCI states that are activated for the uplink communications by the UE and that are associated with an uplink power control parameter configuration.
  • the TCI state component 1025 is capable of, configured to, or operable to support a means for receiving, via the MAC-CE, one or more fields that indicate one or more TCI states from among the set of multiple TCI states that are activated for the uplink communications by the UE, where each field of the one or more fields indicates a respective TCI state and indicates whether the set of multiple uplink power control fields includes a respective power uplink control field that corresponds to the respective TCI state.
  • the TCI state component 1025 is capable of, configured to, or operable to support a means for receiving, via a set of multiple TCI state fields within the MAC-CE, a respective ID associated with a respective TCI state to which the power control parameter included in the uplink power control field applies.
  • the transmit power component 1035 is capable of, configured to, or operable to support a means for determining the one or more transmit powers for the one or more TCI states using the power control parameter based on the one or more TCI states being activated for the uplink communications by the UE. In some examples, the transmit power component 1035 is capable of, configured to, or operable to support a means for determining the one or more transmit powers for the one or more TCI states using the power control parameter based on the one or more TCI states being activated for the uplink communications by the UE and further based on the one or more TCI states being associated with an uplink power control parameter configuration.
  • the transmit power component 1035 is capable of, configured to, or operable to support a means for determining the one or more transmit powers for the one or more TCI states using the power control parameter based on at least two bits in the MAC-CE that indicate the power control parameter applies to the one or more TCI states.
  • the MAC-CE component 1040 is capable of, configured to, or operable to support a means for receiving a unified TCI state activation MAC-CE that indicates one or more TCI states from among the set of multiple TCI states that are activated for the uplink communications by the UE.
  • the MAC-CE component 1040 is capable of, configured to, or operable to support a means for receiving a unified TCI state activation MAC-CE, where the unified TCI state activation MAC-CE indicates one or more TCI states from among the set of multiple TCI states that are activated for the uplink communications by the UE.
  • the power control parameter includes a pathloss offset.
  • the MAC-CE includes at least one field that indicates whether the pathloss offset is with respect to a nominal pathloss or a measured pathloss.
  • the uplink power control component 1030 is capable of, configured to, or operable to support a means for receiving, after transmitting the uplink communications using the one or more transmit powers, a second message including second uplink power control information, where the message includes a unified TCI state activation MAC-CE that indicates one or more TCI states from among the set of multiple TCI states that are activated for the uplink communications by the UE, and where the second message includes a MAC-CE different than the unified TCI state activation MAC-CE.
  • the power control parameter indicated via the message includes a reference to a measured parameter.
  • a second power control parameter indicated via the second message includes a second reference to a nominal parameter, a measured parameter, or any combination thereof, where the nominal parameter includes one of an initial parameter, a previous parameter, a previous measured parameter or an initial measured parameter.
  • the second message includes one or more fields that indicate whether the second power control parameter indicated via the second message references the nominal parameter or the measured parameter.
  • the frequency configuration component 1045 is capable of, configured to, or operable to support a means for receiving an indication of a set of CCs for TCI state activation, where the power control parameter corresponds to the one or more CCs that are the same as the set of CCs for TCI state activation.
  • the transmit power component 1035 is capable of, configured to, or operable to support a means for applying the power control parameter to the one or more TCI states across the set of CCs.
  • the frequency configuration component 1045 is capable of, configured to, or operable to support a means for receiving a first indication of a first set of CCs for TCI state activation. In some examples, the frequency configuration component 1045 is capable of, configured to, or operable to support a means for receiving a second indication of a second set of CCs associated with uplink power control, where the power control parameter corresponds to the one or more CCs that are the same as the second set of CCs for uplink power control. In some examples, the transmit power component 1035 is capable of, configured to, or operable to support a means for applying the power control parameter to the one or more TCI states across the second set of CCs.
  • the pathloss component 1050 is capable of, configured to, or operable to support a means for determining an uplink pathloss associated with the one or more TCI states based on the power control parameter and a reference pathloss value, where the power control parameter includes a pathloss offset value.
  • the transmit power component 1035 is capable of, configured to, or operable to support a means for determining the one or more transmit powers for the uplink communications according to the one or more TCI states based on the calculated uplink pathloss.
  • the pathloss component 1050 is capable of, configured to, or operable to support a means for determining an uplink pathloss associated with the one or more TCI states based on the power control parameter and a reference pathloss value, where the power control parameter includes a pathloss scaling factor.
  • the transmit power component 1035 is capable of, configured to, or operable to support a means for determining the one or more transmit powers for the uplink communications according to the one or more TCI states based on the calculated uplink pathloss.
  • FIG. 11 shows a diagram of a system 1100 including a device 1105 that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure.
  • the device 1105 may be an example of or include components of a device 805, a device 905, or a UE 115 as described herein.
  • the device 1105 may communicate (e.g., wirelessly) with one or more other devices (e.g., network entities 105, UEs 115, or a combination thereof) .
  • the device 1105 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 1120, an input/output (I/O) controller, such as an I/O controller 1110, a transceiver 1115, one or more antennas 1125, at least one memory 1130, code 1135, and at least one processor 1140. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1145) .
  • a bus 1145 e.g., a bus 1145
  • the I/O controller 1110 may manage input and output signals for the device 1105.
  • the I/O controller 1110 may also manage peripherals not integrated into the device 1105.
  • the I/O controller 1110 may represent a physical connection or port to an external peripheral.
  • the I/O controller 1110 may utilize an operating system such as or another known operating system.
  • the I/O controller 1110 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device.
  • the I/O controller 1110 may be implemented as part of one or more processors, such as the at least one processor 1140.
  • 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.
  • the device 1105 may include a single antenna. However, in some other cases, the device 1105 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the transceiver 1115 may communicate bi-directionally via the one or more antennas 1125 using wired or wireless links as described herein.
  • the transceiver 1115 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 1115 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 1125 for transmission, and to demodulate packets received from the one or more antennas 1125.
  • the transceiver 1115 may be an example of a transmitter 815, a transmitter 915, a receiver 810, a receiver 910, or any combination thereof or component thereof, as described herein.
  • the at least one memory 1130 may include random access memory (RAM) and read-only memory (ROM) .
  • the at least one memory 1130 may store computer-readable, computer-executable, or processor-executable code, such as the code 1135.
  • the code 1135 may include instructions that, when executed by the at least one processor 1140, cause the device 1105 to perform various functions described herein.
  • the code 1135 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory.
  • the code 1135 may not be directly executable by the at least one processor 1140 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the at least one memory 1130 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • BIOS basic I/O system
  • the at least one processor 1140 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more central processing units (CPUs) , one or more graphics processing units (GPUs) , one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs) ) , one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof) .
  • the at least one processor 1140 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the at least one processor 1140.
  • the at least one processor 1140 may be configured to execute computer-readable instructions stored in a memory (e.g., the at least one memory 1130) to cause the device 1105 to perform various functions (e.g., functions or tasks supporting power control information for multiple TCI states) .
  • the device 1105 or a component of the device 1105 may include at least one processor 1140 and at least one memory 1130 coupled with or to the at least one processor 1140, the at least one processor 1140 and the at least one memory 1130 configured to perform various functions described herein.
  • the at least one processor 1140 may include multiple processors and the at least one memory 1130 may include multiple memories.
  • the at least one processor 1140 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 1140) and memory circuitry (which may include the at least one memory 1130) ) , or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs.
  • the processing system may be configured to perform one or more of the functions described herein.
  • the at least one processor 1140 or a processing system including the at least one processor 1140 may be configured to, configurable to, or operable to cause the device 1105 to perform one or more of the functions described herein.
  • being “configured to, ” being “configurable to, ” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code 1135 (e.g., processor-executable code) stored in the at least one memory 1130 or otherwise, to perform one or more of the functions described herein.
  • code 1135 e.g., processor-executable code
  • the communications manager 1120 may support wireless communication in accordance with examples as disclosed herein.
  • the communications manager 1120 is capable of, configured to, or operable to support a means for receiving a control message that indicates a set of multiple TCI states for uplink communications by the UE via one or more CCs.
  • the communications manager 1120 is capable of, configured to, or operable to support a means for receiving a message including uplink power control information that indicates a power control parameter for uplink pathloss calculation for the one or more CCs, the power control parameter corresponding to one or more TCI states from among the set of multiple TCI states.
  • the communications manager 1120 is capable of, configured to, or operable to support a means for transmitting, via the one or more CCs in accordance with the one or more TCI states, the uplink communications using one or more transmit powers that are based on the power control parameter.
  • the device 1105 may support techniques for improved communication reliability, reduced latency, reduced power consumption, more efficient utilization of communication resources, and improved coordination between devices, among other examples.
  • the communications manager 1120 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 1115, the one or more antennas 1125, or any combination thereof.
  • the communications manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1120 may be supported by or performed by the at least one processor 1140, the at least one memory 1130, the code 1135, or any combination thereof.
  • the code 1135 may include instructions executable by the at least one processor 1140 to cause the device 1105 to perform various aspects of power control information for multiple TCI states as described herein, or the at least one processor 1140 and the at least one memory 1130 may be otherwise configured to, individually or collectively, perform or support such operations.
  • FIG. 12 shows a block diagram 1200 of a device 1205 that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure.
  • the device 1205 may be an example of aspects of a network entity 105 as described herein.
  • the device 1205 may include a receiver 1210, a transmitter 1215, and a communications manager 1220.
  • the device 1205, or one or more components of the device 1205 may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the transmitter 1215 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1205.
  • the transmitter 1215 may output information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) .
  • the transmitter 1215 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 1215 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
  • the transmitter 1215 and the receiver 1210 may be co-located in a transceiver, which may include or be coupled with a modem.
  • the communications manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) .
  • the hardware may include at least one of a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure.
  • at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory) .
  • the communications manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code) . If implemented in code executed by at least one processor, the functions of the communications manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure) .
  • a general-purpose processor e.g., a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions
  • the communications manager 1220 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1210, the transmitter 1215, or both.
  • the communications manager 1220 may receive information from the receiver 1210, send information to the transmitter 1215, or be integrated in combination with the receiver 1210, the transmitter 1215, or both to obtain information, output information, or perform various other operations as described herein.
  • the communications manager 1220 may support wireless communication in accordance with examples as disclosed herein.
  • the communications manager 1220 is capable of, configured to, or operable to support a means for outputting a control message that indicates a set of multiple TCI states for uplink communications by a UE via one or more CCs.
  • the communications manager 1220 is capable of, configured to, or operable to support a means for outputting a message including uplink power control information that indicates a power control parameter for uplink pathloss calculation for the one or more CCs, the power control parameter corresponding to one or more TCI states from among the set of multiple TCI states.
  • the communications manager 1220 is capable of, configured to, or operable to support a means for obtaining, via the one or more CCs in accordance with the one or more TCI states, the uplink communications using one or more transmit powers based on the power control parameter.
  • the device 1205 e.g., at least one processor controlling or otherwise coupled with the receiver 1210, the transmitter 1215, the communications manager 1220, or a combination thereof
  • the device 1205 may support techniques for reduced processing, reduced power consumption, and more efficient utilization of communication resources, among other examples.
  • FIG. 13 shows a block diagram 1300 of a device 1305 that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure.
  • the device 1305 may be an example of aspects of a device 1205 or a network entity 105 as described herein.
  • the device 1305 may include a receiver 1310, a transmitter 1315, and a communications manager 1320.
  • the device 1305, or one or more components of the device 1305 may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 1310 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) .
  • Information may be passed on to other components of the device 1305.
  • the receiver 1310 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 1310 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
  • the transmitter 1315 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1305.
  • the transmitter 1315 may output information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) .
  • the transmitter 1315 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 1315 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
  • the transmitter 1315 and the receiver 1310 may be co-located in a transceiver, which may include or be coupled with a modem.
  • the device 1305, or various components thereof may be an example of means for performing various aspects of power control information for multiple TCI states as described herein.
  • the communications manager 1320 may include a TCI state component 1325, an uplink power control component 1330, a power control parameter component 1335, or any combination thereof.
  • the communications manager 1320 may be an example of aspects of a communications manager 1220 as described herein.
  • the communications manager 1320, or various components thereof may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1310, the transmitter 1315, or both.
  • the communications manager 1320 may receive information from the receiver 1310, send information to the transmitter 1315, or be integrated in combination with the receiver 1310, the transmitter 1315, or both to obtain information, output information, or perform various other operations as described herein.
  • the communications manager 1320 may support wireless communication in accordance with examples as disclosed herein.
  • the TCI state component 1325 is capable of, configured to, or operable to support a means for outputting a control message that indicates a set of multiple TCI states for uplink communications by a UE via one or more CCs.
  • the uplink power control component 1330 is capable of, configured to, or operable to support a means for outputting a message including uplink power control information that indicates a power control parameter for uplink pathloss calculation for the one or more CCs, the power control parameter corresponding to one or more TCI states from among the set of multiple TCI states.
  • the power control parameter component 1335 is capable of, configured to, or operable to support a means for obtaining, via the one or more CCs in accordance with the one or more TCI states, the uplink communications using one or more transmit powers based on the power control parameter.
  • FIG. 14 shows a block diagram 1400 of a communications manager 1420 that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure.
  • the communications manager 1420 may be an example of aspects of a communications manager 1220, a communications manager 1320, or both, as described herein.
  • the communications manager 1420, or various components thereof, may be an example of means for performing various aspects of power control information for multiple TCI states as described herein.
  • the communications manager 1420 may include a TCI state component 1425, an uplink power control component 1430, a power control parameter component 1435, a MAC-CE component 1440, a frequency configuration component 1445, or any combination thereof.
  • Each of these components, or components or subcomponents thereof may communicate, directly or indirectly, with one another (e.g., via one or more buses) .
  • the communications may include communications within a protocol layer of a protocol stack, communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105) , or any combination thereof.
  • the communications manager 1420 may support wireless communication in accordance with examples as disclosed herein.
  • the TCI state component 1425 is capable of, configured to, or operable to support a means for outputting a control message that indicates a set of multiple TCI states for uplink communications by a UE via one or more CCs.
  • the uplink power control component 1430 is capable of, configured to, or operable to support a means for outputting a message including uplink power control information that indicates a power control parameter for uplink pathloss calculation for the one or more CCs, the power control parameter corresponding to one or more TCI states from among the set of multiple TCI states.
  • the power control parameter component 1435 is capable of, configured to, or operable to support a means for obtaining, via the one or more CCs in accordance with the one or more TCI states, the uplink communications using one or more transmit powers based on the power control parameter.
  • the MAC-CE component 1440 is capable of, configured to, or operable to support a means for outputting a MAC-CE that indicates the power control parameter corresponding to the one or more TCI states.
  • the power control parameter component 1435 is capable of, configured to, or operable to support a means for outputting the power control parameter via a set of one or more reserved bits within the MAC-CE, an uplink power control field within the MAC-CE, or both.
  • the power control parameter component 1435 is capable of, configured to, or operable to support a means for outputting, via a set of multiple uplink power control fields within the MAC-CE, the power control parameter.
  • a quantity of the set of multiple uplink power control fields is based on a quantity of TCI states from among the set of multiple TCI states that are activated for the uplink communications by the UE. In some examples, the quantity of the set of multiple uplink power control fields is based on the quantity of TCI states from among the set of multiple TCI states that are activated for the uplink communications by the UE and that are associated with an uplink power control parameter configuration.
  • the TCI state component 1425 is capable of, configured to, or operable to support a means for outputting, via the MAC-CE, one or more fields that indicate one or more TCI states from among the set of multiple TCI states that are activated for the uplink communications by the UE, where each field of the one or more fields indicates a respective TCI state and indicates whether the set of multiple uplink power control fields includes a respective power uplink control field that corresponds to the respective TCI state.
  • the TCI state component 1425 is capable of, configured to, or operable to support a means for outputting, via a set of multiple TCI state fields in the MAC-CE, a respective ID associated with a respective TCI state to which the power control parameter included in the uplink power control field applies.
  • the MAC-CE component 1440 is capable of, configured to, or operable to support a means for outputting a unified TCI state activation MAC-CE that indicates one or more TCI states from among the set of multiple TCI states that are activated for the uplink communications by the UE.
  • the MAC-CE component 1440 is capable of, configured to, or operable to support a means for outputting a unified TCI state activation MAC- CE, where the unified TCI state activation MAC-CE indicates one or more TCI states from among the set of multiple TCI states that are activated for the uplink communications by the UE.
  • the uplink power control component 1430 is capable of, configured to, or operable to support a means for outputting, after receiving the uplink communications using the one or more transmit powers, a second message including second uplink power control information, where the message includes a unified TCI state activation MAC-CE that indicates one or more TCI states from among the set of multiple TCI states that are activated for the uplink communications by the UE, and where the second message includes a MAC-CE different than the unified TCI state activation MAC-CE.
  • the power control parameter indicated via the message includes a reference to a measured parameter.
  • a second power control parameter indicated via the second message includes a second reference to a nominal parameter, a measured parameter, or any combination thereof, where the nominal parameter includes one of an initial parameter, a previous parameter, a previous measured parameter or an initial measured parameter.
  • the second message includes one or more fields that indicate whether the second power control parameter indicated via the second message references the nominal parameter or the measured parameter.
  • the frequency configuration component 1445 is capable of, configured to, or operable to support a means for outputting an indication of a set of CCs for TCI state activation, where the power control parameter corresponds to the one or more CCs that are the same as the set of CCs for TCI state activation, and where the power control parameter is applied to the one or more TCI states across the set of CCs.
  • the frequency configuration component 1445 is capable of, configured to, or operable to support a means for outputting a first indication of a first set of CCs for TCI state activation. In some examples, the frequency configuration component 1445 is capable of, configured to, or operable to support a means for outputting a second indication of a second set of CCs associated with uplink power control, where the power control parameter corresponds to the one or more CCs that are the same as the second set of CCs for uplink power control, and where the power control parameter is applied to the one or more TCI states across the second set of CCs.
  • FIG. 15 shows a diagram of a system 1500 including a device 1505 that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure.
  • the device 1505 may be an example of or include components of a device 1205, a device 1305, or a network entity 105 as described herein.
  • the device 1505 may communicate with other network devices or network equipment such as one or more of the network entities 105, UEs 115, or any combination thereof.
  • the communications may include communications over one or more wired interfaces, over one or more wireless interfaces, or any combination thereof.
  • the device 1505 may include components that support outputting and obtaining communications, such as a communications manager 1520, a transceiver 1510, one or more antennas 1515, at least one memory 1525, code 1530, and at least one processor 1535. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1540) .
  • a communications manager 1520 e.g., operatively, communicatively, functionally, electronically, electrically
  • buses e.g., a bus 1540
  • the transceiver 1510 may also include a modem to modulate signals, to provide the modulated signals for transmission (e.g., by one or more antennas 1515, by a wired transmitter) , to receive modulated signals (e.g., from one or more antennas 1515, from a wired receiver) , and to demodulate signals.
  • the transceiver 1510 may include one or more interfaces, such as one or more interfaces coupled with the one or more antennas 1515 that are configured to support various receiving or obtaining operations, or one or more interfaces coupled with the one or more antennas 1515 that are configured to support various transmitting or outputting operations, or a combination thereof.
  • the transceiver 1510 may include or be configured for coupling with one or more processors or one or more memory components that are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other outputting, or any combination thereof.
  • the transceiver 1510, or the transceiver 1510 and the one or more antennas 1515, or the transceiver 1510 and the one or more antennas 1515 and one or more processors or one or more memory components may be included in a chip or chip assembly that is installed in the device 1505.
  • the transceiver 1510 may be operable to support communications via one or more communications links (e.g., communication link (s) 125, backhaul communication link (s) 120, a midhaul communication link 162, a fronthaul communication link 168) .
  • communications links e.g., communication link (s) 125, backhaul communication link (s) 120, a midhaul communication link 162, a fronthaul communication link 168) .
  • the at least one memory 1525 may include RAM, ROM, or any combination thereof.
  • the at least one memory 1525 may store computer-readable, computer-executable, or processor-executable code, such as the code 1530.
  • the code 1530 may include instructions that, when executed by one or more of the at least one processor 1535, cause the device 1505 to perform various functions described herein.
  • the code 1530 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1530 may not be directly executable by a processor of the at least one processor 1535 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the at least one memory 1525 may include, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • the at least one processor 1535 may include multiple processors and the at least one memory 1525 may include multiple memories.
  • One or more of the multiple processors may be coupled with one or more of the multiple memories which may, individually or collectively, be configured to perform various functions herein (for example, as part of a processing system) .
  • the at least one processor 1535 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more central processing units (CPUs) , one or more graphics processing units (GPUs) , one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs) ) , one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof) .
  • the at least one processor 1535 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into one or more of the at least one processor 1535.
  • the at least one processor 1535 may be configured to execute computer-readable instructions stored in a memory (e.g., one or more of the at least one memory 1525) to cause the device 1505 to perform various functions (e.g., functions or tasks supporting power control information for multiple TCI states) .
  • the device 1505 or a component of the device 1505 may include at least one processor 1535 and at least one memory 1525 coupled with one or more of the at least one processor 1535, the at least one processor 1535 and the at least one memory 1525 configured to perform various functions described herein.
  • the at least one processor 1535 may be an example of a cloud-computing platform (e.g., one or more physical nodes and supporting software such as operating systems, virtual machines, or container instances) that may host the functions (e.g., by executing code 1530) to perform the functions of the device 1505.
  • the at least one processor 1535 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1505 (such as within one or more of the at least one memory 1525) .
  • the at least one processor 1535 may include multiple processors and the at least one memory 1525 may include multiple memories.
  • the at least one processor 1535 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 1535) and memory circuitry (which may include the at least one memory 1525) ) , or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs.
  • the processing system may be configured to perform one or more of the functions described herein.
  • the at least one processor 1535 or a processing system including the at least one processor 1535 may be configured to, configurable to, or operable to cause the device 1505 to perform one or more of the functions described herein.
  • being “configured to, ” being “configurable to, ” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code stored in the at least one memory 1525 or otherwise, to perform one or more of the functions described herein.
  • a bus 1540 may support communications of (e.g., within) a protocol layer of a protocol stack. In some examples, a bus 1540 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack) , which may include communications performed within a component of the device 1505, or between different components of the device 1505 that may be co-located or located in different locations (e.g., where the device 1505 may refer to a system in which one or more of the communications manager 1520, the transceiver 1510, the at least one memory 1525, the code 1530, and the at least one processor 1535 may be located in one of the different components or divided between different components) .
  • a logical channel of a protocol stack e.g., between protocol layers of a protocol stack
  • the device 1505 may refer to a system in which one or more of the communications manager 1520, the transceiver 1510, the at least one memory 1525, the code 1530, and the at least one
  • the communications manager 1520 may manage aspects of communications with a core network 130 (e.g., via one or more wired or wireless backhaul links) .
  • the communications manager 1520 may manage the transfer of data communications for client devices, such as one or more UEs 115.
  • the communications manager 1520 may manage communications with one or more other network devices, and may include a controller or scheduler for controlling communications with UEs 115 (e.g., in cooperation with the one or more other network devices) .
  • the communications manager 1520 may support an X2 interface within an LTE/LTE-A wireless communications network technology to provide communication between network entities 105.
  • the device 1505 may support techniques for improved communication reliability, reduced latency, reduced power consumption, more efficient utilization of communication resources, and improved coordination between devices, among other examples.
  • the communications manager 1520 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver 1510, the one or more antennas 1515 (e.g., where applicable) , or any combination thereof.
  • the code 1530 may include instructions executable by one or more of the at least one processor 1535 to cause the device 1505 to perform various aspects of power control information for multiple TCI states as described herein, or the at least one processor 1535 and the at least one memory 1525 may be otherwise configured to, individually or collectively, perform or support such operations.
  • FIG. 16 shows a flowchart illustrating a method 1600 that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure.
  • the operations of the method 1600 may be implemented by a UE or its components as described herein.
  • the operations of the method 1600 may be performed by a UE 115 as described with reference to FIGs. 1 through 11.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving a control message that indicates a set of multiple TCI states for uplink communications by the UE via one or more CCs.
  • the operations of 1605 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed by a TCI state component 1025 as described with reference to FIG. 10.
  • the method may include receiving a message including uplink power control information that indicates a power control parameter for uplink pathloss calculation for the one or more CCs, the power control parameter corresponding to one or more TCI states from among the set of multiple TCI states.
  • the operations of 1610 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed by an uplink power control component 1030 as described with reference to FIG. 10.
  • the method may include transmitting, via the one or more CCs in accordance with the one or more TCI states, the uplink communications using one or more transmit powers that are based on the power control parameter.
  • the operations of 1615 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed by a transmit power component 1035 as described with reference to FIG. 10.
  • FIG. 17 shows a flowchart illustrating a method 1700 that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure.
  • the operations of the method 1700 may be implemented by a UE or its components as described herein.
  • the operations of the method 1700 may be performed by a UE 115 as described with reference to FIGs. 1 through 11.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving a control message that indicates a set of multiple TCI states for uplink communications by the UE via one or more CCs.
  • the operations of 1705 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed by a TCI state component 1025 as described with reference to FIG. 10.
  • the method may include receiving a message including uplink power control information that indicates a power control parameter for uplink pathloss calculation for the one or more CCs, the power control parameter corresponding to one or more TCI states from among the set of multiple TCI states.
  • the operations of 1710 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed by an uplink power control component 1030 as described with reference to FIG. 10.
  • the method may include transmitting, via the one or more CCs in accordance with the one or more TCI states, the uplink communications using one or more transmit powers that are based on the power control parameter.
  • the operations of 1715 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed by a transmit power component 1035 as described with reference to FIG. 10.
  • the method may include receiving, after transmitting the uplink communications using the one or more transmit powers, a second message including second uplink power control information, where the message includes a unified TCI state activation MAC-CE that indicates one or more TCI states from among the set of multiple TCI states that are activated for the uplink communications by the UE, and where the second message includes a MAC-CE different than the unified TCI state activation MAC-CE.
  • the operations of 1720 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1720 may be performed by an uplink power control component 1030 as described with reference to FIG. 10.
  • FIG. 18 shows a flowchart illustrating a method 1800 that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure.
  • the operations of the method 1800 may be implemented by a UE or its components as described herein.
  • the operations of the method 1800 may be performed by a UE 115 as described with reference to FIGs. 1 through 11.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving a control message that indicates a set of multiple TCI states for uplink communications by the UE via one or more CCs.
  • the operations of 1805 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed by a TCI state component 1025 as described with reference to FIG. 10.
  • the method may include receiving a message including uplink power control information that indicates a power control parameter for uplink pathloss calculation for the one or more CCs, the power control parameter corresponding to one or more TCI states from among the set of multiple TCI states.
  • the operations of 1810 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed by an uplink power control component 1030 as described with reference to FIG. 10.
  • the method may include determining an uplink pathloss associated with the one or more TCI states based on the power control parameter and a reference pathloss value, where the power control parameter includes a pathloss offset value.
  • the operations of 1815 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed by a pathloss component 1050 as described with reference to FIG. 10.
  • the method may include determining one or more transmit powers for the uplink communications according to the one or more TCI states based on the calculated uplink pathloss.
  • the operations of 1820 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1820 may be performed by a transmit power component 1035 as described with reference to FIG. 10.
  • the method may include transmitting, via the one or more CCs in accordance with the one or more TCI states, the uplink communications using the one or more transmit powers that are based on the power control parameter.
  • the operations of 1825 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1825 may be performed by a transmit power component 1035 as described with reference to FIG. 10.
  • FIG. 19 shows a flowchart illustrating a method 1900 that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure.
  • the operations of the method 1900 may be implemented by a UE or a network entity or its components as described herein.
  • the operations of the method 1900 may be performed by a UE 115 as described with reference to FIGs. 1 through 11 or a network entity as described with reference to FIGs. 1 through 7 and 12 through 15.
  • a UE or a network entity may execute a set of instructions to control the functional elements of the UE or the network entity to perform the described functions.
  • the UE or the network entity may perform aspects of the described functions using special-purpose hardware.
  • the method may include outputting a control message that indicates a set of multiple TCI states for uplink communications by a UE via one or more CCs.
  • the operations of 1905 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1905 may be performed by a TCI state component 1025 or a TCI state component 1425 as described with reference to FIGs. 10 and 14.
  • the method may include outputting a message including uplink power control information that indicates a power control parameter for uplink pathloss calculation for the one or more CCs, the power control parameter corresponding to one or more TCI states from among the set of multiple TCI states.
  • the operations of 1910 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1910 may be performed by an uplink power control component 1030 or an uplink power control component 1430 as described with reference to FIGs. 10 and 14.
  • the method may include outputting a control message that indicates a set of multiple TCI states for uplink communications by a UE via one or more CCs.
  • the operations of 2015 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2015 may be performed by a TCI state component 1025 or a TCI state component 1425 as described with reference to FIGs. 10 and 14.
  • the method may include outputting a message including uplink power control information that indicates a power control parameter for uplink pathloss calculation for the one or more CCs, the power control parameter corresponding to one or more TCI states from among the set of multiple TCI states, where the power control parameter corresponds to the one or more CCs that are the same as the second set of CCs for uplink power control, and where the power control parameter is applied to the one or more TCI states across the second set of CCs.
  • the operations of 2020 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2020 may be performed by an uplink power control component 1030 or an uplink power control component 1430 as described with reference to FIGs. 10 and 14.
  • Aspect 4 The method of aspect 2, further comprising: receiving, via a plurality of uplink power control fields within the MAC-CE, the power control parameter.
  • Aspect 5 The method of aspect 4, wherein a quantity of the plurality of uplink power control fields is based at least in part on a quantity of TCI states from among the plurality of TCI states that are activated for the uplink communications by the UE; or the quantity of the plurality of uplink power control fields is based at least in part on the quantity of TCI states from among the plurality of TCI states that are activated for the uplink communications by the UE and that are associated with an uplink power control configuration.
  • Aspect 6 The method of aspect 4, further comprising: receiving, via the MAC-CE, one or more fields that indicate one or more TCI states from among the plurality of TCI states that are activated for the uplink communications by the UE, wherein each field of the one or more fields indicates a respective TCI state and indicates whether the plurality of uplink power control fields comprises a respective power uplink control field that corresponds to the respective TCI state.
  • Aspect 7 The method of aspect 4, further comprising: receiving, via each uplink power control field of the plurality of uplink power control fields, a respective identifier associated with a respective TCI state to which the power control parameter included in the uplink power control field applies.
  • Aspect 8 The method of any of aspects 2 through 7, further comprising: determining the one or more transmit powers for the at least two TCI states using the power control parameter based at least in part on the at least two TCI states being activated for the uplink communications by the UE; or determining the one or more transmit powers for the at least two TCI states using the power control parameter based at least in part on the at least two TCI states being activated for the uplink communications by the UE and further based at least in part on the at least two TCI states being associated with an uplink power control configuration; or determining the one or more transmit powers for the at least two TCI states using the power control parameter based at least in part on at least two bits in the MAC-CE that indicate the power control parameter applies to the at least two TCI states.
  • Aspect 10 The method of any of aspects 2 through 8, further comprising: receiving a unified TCI state activation MAC-CE, wherein the unified TCI state activation MAC-CE indicates one or more TCI states from among the plurality of TCI states that are activated for the uplink communications by the UE.
  • Aspect 11 The method of any of aspects 2 through 10, wherein the power control parameter comprises a pathloss offset; and the MAC-CE comprises at least one field that indicates whether the pathloss offset is with respect to a nominal pathloss or a measured pathloss.
  • Aspect 13 The method of aspect 12, wherein the power control parameter indicated via the message comprises a reference to a measured parameter; a second power control parameter indicated via the second message comprises a second reference to a nominal parameter, a previous parameter, an initial parameter, a measured parameter, or any combination thereof; and the second message comprises one or more fields that indicate whether the second power control parameter indicated via the second message references the nominal parameter, the previous parameter, the initial parameter, the measured parameter, or any combination thereof.
  • Aspect 14 The method of any of aspects 1 through 13, further comprising: receiving an indication of a set of CCs for TCI state activation, wherein the power control parameter corresponds to the one or more CCs that are the same as the set of CCs for TCI state activation; and applying the power control parameter to the at least two TCI states across the set of CCs.
  • Aspect 15 The method of any of aspects 1 through 13, further comprising: receiving a first indication of a first set of CCs for TCI state activation; receiving a second indication of a second set of CCs associated with uplink power control, wherein the power control parameter corresponds to the one or more CCs that are the same as the second set of CCs for uplink power control; and applying the power control parameter to the at least two TCI states across the second set of CCs.
  • Aspect 16 The method of any of aspects 1 through 15, further comprising: determining an uplink pathloss associated with the at least two TCI states based at least in part on the power control parameter and a reference pathloss value, wherein the power control parameter comprises a pathloss offset value; and determining the one or more transmit powers for the uplink communications according to the at least two TCI states based at least in part on the calculated uplink pathloss.
  • Aspect 17 The method of any of aspects 1 through 15, further comprising: determining an uplink pathloss associated with the at least two TCI states based at least in part on the power control parameter and a reference pathloss value, wherein the power control parameter comprises a pathloss scaling factor; and determining the one or more transmit powers for the uplink communications according to the at least two TCI states based at least in part on the calculated uplink pathloss.
  • a method for wireless communication at a network entity comprising: outputting a control message that indicates a plurality of TCI states for uplink communications by a UE via one or more CCs; outputting a message comprising uplink power control information that indicates a power control parameter associated with uplink pathloss, the power control parameter corresponding to at least two TCI states from among the plurality of TCI states; and obtaining, via the one or more CCs in accordance with the at least two TCI states, the uplink communications using one or more transmit powers based at least in part on the power control parameter.
  • Aspect 19 The method of aspect 18, wherein outputting the message comprises: outputting a MAC-CE that indicates the power control parameter corresponding to the at least two TCI states.
  • Aspect 20 The method of aspect 19, further comprising: outputting the power control parameter via a set of one or more reserved bits within the MAC-CE, an uplink power control field within the MAC-CE, or both.
  • Aspect 21 The method of aspect 19, further comprising: outputting, via a plurality of uplink power control fields within the MAC-CE, the power control parameter.
  • Aspect 22 The method of aspect 21, wherein a quantity of the plurality of uplink power control fields is based at least in part on a quantity of TCI states from among the plurality of TCI states that are activated for the uplink communications by the UE; or the quantity of the plurality of uplink power control fields is based at least in part on the quantity of TCI states from among the plurality of TCI states that are activated for the uplink communications by the UE and that are associated with an uplink power control configuration.
  • Aspect 23 The method of aspect 21, further comprising: outputting, via the MAC-CE, one or more fields that indicate one or more TCI states from among the plurality of TCI states that are activated for the uplink communications by the UE, wherein each field of the one or more fields indicates a respective TCI state and indicates whether the plurality of uplink power control fields comprises a respective power uplink control field that corresponds to the respective TCI state.
  • Aspect 24 The method of aspect 21, further comprising: outputting, via each uplink power control field of the plurality of uplink power control fields, a respective identifier associated with a respective TCI state to which the power control parameter included in the uplink power control field applies.
  • Aspect 25 The method of any of aspects 19 through 24, wherein outputting the MAC-CE comprises: outputting a unified TCI state activation MAC-CE that indicates one or more TCI states from among the plurality of TCI states that are activated for the uplink communications by the UE.
  • Aspect 27 The method of any of aspects 19 through 26, wherein the power control parameter comprises a pathloss offset; and the MAC-CE comprises at least one field that indicates whether the pathloss offset is with respect to a nominal pathloss or a measured pathloss.
  • Aspect 28 The method of any of aspects 18 through 27, further comprising: outputting, after receiving the uplink communications using the one or more transmit powers, a second message comprising second uplink power control information, wherein the message comprises a unified TCI state activation MAC-CE that indicates one or more TCI states from among the plurality of TCI states that are activated for the uplink communications by the UE, and wherein the second message comprises a MAC-CE different than the unified TCI state activation MAC-CE.
  • Aspect 30 The method of any of aspects 18 through 29, further comprising: outputting an indication of a set of CCs for TCI state activation, wherein the power control parameter corresponds to the one or more CCs that are the same as the set of CCs for TCI state activation, and wherein the power control parameter is applied to the at least two TCI states across the set of CCs.
  • Aspect 31 The method of any of aspects 18 through 29, further comprising: outputting a first indication of a first set of CCs for TCI state activation; and outputting a second indication of a second set of CCs associated with uplink power control, wherein the power control parameter corresponds to the one or more CCs that are the same as the second set of CCs for uplink power control, and wherein the power control parameter is applied to the at least two TCI states across the second set of CCs.
  • a UE for wireless communication comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to perform a method of any of aspects 1 through 17.
  • a UE for wireless communication comprising at least one means for performing a method of any of aspects 1 through 17.
  • Aspect 34 A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to perform a method of any of aspects 1 through 17.
  • a network entity for wireless communication comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to perform a method of any of aspects 18 through 31.
  • a network entity for wireless communication comprising at least one means for performing a method of any of aspects 18 through 31.
  • Aspect 37 A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to perform a method of any of aspects 18 through 31.
  • LTE, LTE-A, LTE-A Pro, or NR may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks.
  • the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB) , Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.
  • UMB Ultra Mobile Broadband
  • IEEE Institute of Electrical and Electronics Engineers
  • Wi-Fi Institute of Electrical and Electronics Engineers
  • WiMAX IEEE 802.16
  • IEEE 802.20 Flash-OFDM
  • a general-purpose processor may be a microprocessor but, in the alternative, the 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 in conjunction with a DSP core, or any other such configuration) . Any functions or operations described herein as being capable of being performed by a processor may be performed by multiple processors that, individually or collectively, are capable of performing the described functions or operations.
  • the functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as or transmitted using one or more instructions or code of a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
  • Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
  • a non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.
  • non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor.
  • any connection is properly termed a computer-readable medium.
  • the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) , or wireless technologies such as infrared, radio, and microwave
  • the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium.
  • Disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD) , floppy disk, and Blu-ray disc. Disks may reproduce data magnetically, and discs may reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media. Any functions or operations described herein as being capable of being performed by a memory may be performed by multiple memories that, individually or collectively, are capable of performing the described functions or operations.
  • the article “a” before a noun is open-ended and understood to refer to “at least one” of those nouns or “one or more” of those nouns.
  • the terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable.
  • a claim recites “a component” that performs one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components.
  • the term “acomponent” having characteristics or performing functions may refer to “at least one of one or more components” having a particular characteristic or performing a particular function.
  • a component introduced with the article “a” using the terms “the” or “said” may refer to any or all of the one or more components.
  • a component introduced with the article “a” may be understood to mean “one or more components, ” and referring to “the component” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components.
  • subsequent reference to a component introduced as “one or more components” using the terms “the” or “said” may refer to any or all of the one or more components.
  • referring to “the one or more components” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components. ”
  • determining encompasses a variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database, or another data structure) , ascertaining, and the like. Also, “determining” can include receiving (e.g., receiving information) , accessing (e.g., accessing data stored in memory) , and the like. Also, “determining” can include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • Electromagnetism (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Methods, systems, and devices for wireless communications are described. In some wireless communications systems, a network entity may transmit, to a user equipment (UE), a control message that indicates multiple transmission configuration indication (TCI) states for uplink communications by the UE via one or more component carriers. The network entity may transmit a message including uplink power control information that indicates a power control parameter associated with uplink pathloss. The power control parameter may correspond to one or more TCI states from the multiple TCI states. The UE may transmit uplink communications via one or more component carriers according to the one or more TCI states. The uplink communications may be transmitted according to one or more transmit powers that are based on the power control parameter.

Description

POWER CONTROL INFORMATION FOR MULTIPLE TRANSMISSION CONFIGURATION INDICATION STATES
FIELD OF TECHNOLOGY
The following relates to wireless communication, including power control information for multiple transmission configuration indication (TCI) states.
BACKGROUND
Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the 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-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 spread orthogonal frequency division multiplexing (DFT-S-OFDM) . A wireless multiple-access communications system may include one or more base stations, each supporting wireless communication for communication devices, which may be known as user equipment (UE) .
SUMMARY
The described techniques relate to improved methods, systems, devices, and apparatuses that support power control information for multiple transmission configuration indication (TCI) states. For example, the described techniques enable a network entity to indicate uplink power control information to a user equipment (UE) , where the uplink power control information is indicated via a single message and is associated with multiple TCI states. The network entity may transmit a control message that indicates multiple TCI states for uplink communications by the UE via one or more component carriers (CCs) . The control message may be, for example, a radio resource control (RRC) configuration, or some other type of message. The network entity may  transmit, to the UE, another message that includes uplink power control information for the UE. The uplink power control information may indicate a power control parameter for uplink pathloss calculation associated with the one or more CCs. The power control parameter may correspond to one or more TCI states from the multiple TCI states configured for the UE. The UE may transmit uplink communications via one or more CCs according to the one or more TCI states. The uplink communications may be transmitted according to one or more transmit powers that are based at least in part on the power control parameter. The power control parameter may be, for example, an uplink pathloss offset, an uplink pathloss scaling factor, or some other power control parameter that may be used in the determination (e.g., calculation) of uplink transmission power.
A method for wireless communication by a UE is described. The method may include receiving a control message that indicates a set of multiple TCI states for uplink communications by the UE via one or more CCs, receiving a message including uplink power control information that indicates a power control parameter associated with uplink pathloss, the power control parameter corresponding to at least two TCI states from among the set of multiple TCI states, and transmitting, via the one or more CCs in accordance with the at least two TCI states, the uplink communications using one or more transmit powers that are based on the power control parameter.
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 with the one or more memories. The one or more processors may individually or collectively be operable to execute the code to cause the UE to receive a control message that indicates a set of multiple TCI states for uplink communications by the UE via one or more CCs, receive a message including uplink power control information that indicates a power control parameter associated with uplink pathloss, the power control parameter corresponding to at least two TCI states from among the set of multiple TCI states, and transmit, via the one or more CCs in accordance with the at least two TCI states, the uplink communications using one or more transmit powers that are based on the power control parameter.
Another UE for wireless communication is described. The UE may include means for receiving a control message that indicates a set of multiple TCI states for  uplink communications by the UE via one or more CCs, means for receiving a message including uplink power control information that indicates a power control parameter associated with uplink pathloss, the power control parameter corresponding to at least two TCI states from among the set of multiple TCI states, and means for transmitting, via the one or more CCs in accordance with the at least two TCI states, the uplink communications using one or more transmit powers that are based on the power control parameter.
A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to receive a control message that indicates a set of multiple TCI states for uplink communications by the UE via one or more CCs, receive a message including uplink power control information that indicates a power control parameter associated with uplink pathloss, the power control parameter corresponding to at least two TCI states from among the set of multiple TCI states, and transmit, via the one or more CCs in accordance with the at least two TCI states, the uplink communications using one or more transmit powers that are based on the power control parameter.
In some examples of the method, UEs, and non-transitory computer-readable medium described herein, receiving the message may include operations, features, means, or instructions for receiving a medium access control-control element (MAC-CE) indicates the power control parameter corresponding to the at least two TCI states.
Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving the power control parameter via a set of one or more reserved bits within the MAC-CE, an uplink power control field within the MAC-CE, or both.
Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, via a set of multiple uplink power control fields within the MAC-CE, the power control parameter.
In some examples of the method, UEs, and non-transitory computer-readable medium described herein, a quantity of the set of multiple uplink power control fields may be based on a quantity of TCI states from among the set of multiple TCI states that  may be activated for the uplink communications by the UE and the quantity of the set of multiple uplink power control fields may be based on the quantity of TCI states from among the set of multiple TCI states that may be activated for the uplink communications by the UE and that may be associated with an uplink power control configuration.
Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, via the MAC-CE, one or more fields that indicate one or more TCI states from among the set of multiple TCI states that may be activated for the uplink communications by the UE, where each field of the one or more fields indicates a respective TCI state and indicates whether the set of multiple uplink power control fields includes a respective power uplink control field that corresponds to the respective TCI state.
Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, via each uplink power control field of the set of multiple uplink power control fields, a respective identifier associated with a respective TCI state to which the power control parameter included in the uplink power control field applies.
Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining the one or more transmit powers for the at least two TCI states using the power control parameter based on the at least two TCI states being activated for the uplink communications by the UE, determining the one or more transmit powers for the at least two TCI states using the power control parameter based on the at least two TCI states being activated for the uplink communications by the UE and further based on the at least two TCI states being associated with an uplink power control configuration, and determining the one or more transmit powers for the at least two TCI states using the power control parameter based on at least two bits in the MAC-CE that indicate the power control parameter applies to the at least two TCI states.
In some examples of the method, UEs, and non-transitory computer-readable medium described herein, receiving the MAC-CE may include operations, features,  means, or instructions for receiving a unified TCI state activation MAC-CE that indicates one or more TCI states from among the set of multiple TCI states that may be activated for the uplink communications by the UE.
Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving a unified TCI state activation MAC-CE, where the unified TCI state activation MAC-CE indicates one or more TCI states from among the set of multiple TCI states that may be activated for the uplink communications by the UE.
In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the power control parameter includes a pathloss offset and the MAC-CE includes at least one field that indicates whether the pathloss offset may be with respect to a nominal pathloss or a measured pathloss.
Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, after transmitting the uplink communications using the one or more transmit powers, a second message including second uplink power control information, where the message includes a unified TCI state activation MAC-CE that indicates one or more TCI states from among the set of multiple TCI states that may be activated for the uplink communications by the UE, and where the second message includes a MAC-CE different than the unified TCI state activation MAC-CE.
In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the power control parameter indicated via the message includes a reference to a measured parameter, a second power control parameter indicated via the second message includes a second reference to a nominal parameter, a previous parameter, an initial parameter, a measured parameter, or any combination thereof, and the second message includes one or more fields that indicate whether the second power control parameter indicated via the second message references the nominal parameter, the previous parameter, the initial parameter, the measured parameter, or any combination thereof.
Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or  instructions for receiving an indication of a set of CCs for TCI state activation, where the power control parameter corresponds to the one or more CCs that may be the same as the set of CCs for TCI state activation and applying the power control parameter to the at least two TCI states across the set of CCs.
Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving a first indication of a first set of CCs for TCI state activation, receiving a second indication of a second set of CCs associated with uplink power control, where the power control parameter corresponds to the one or more CCs that may be the same as the second set of CCs for uplink power control, and applying the power control parameter to the at least two TCI states across the second set of CCs.
Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining an uplink pathloss associated with the at least two TCI states based on the power control parameter and a reference pathloss value, where the power control parameter includes a pathloss offset value and determining the one or more transmit powers for the uplink communications according to the at least two TCI states based on the calculated uplink pathloss.
Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining an uplink pathloss associated with the at least two TCI states based on the power control parameter and a reference pathloss value, where the power control parameter includes a pathloss scaling factor and determining the one or more transmit powers for the uplink communications according to the at least two TCI states based on the calculated uplink pathloss.
A method for wireless communication by a network entity is described. The method may include outputting a control message that indicates a set of multiple TCI states for uplink communications by a UE via one or more CCs, outputting a message including uplink power control information that indicates a power control parameter associated with uplink pathloss, the power control parameter corresponding to at least two TCI states from among the set of multiple TCI states, and obtaining, via the one or  more CCs in accordance with the at least two TCI states, the uplink communications using one or more transmit powers based on the power control parameter.
A network entity for wireless communication is described. The network entity may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively be operable to execute the code to cause the network entity to output a control message that indicates a set of multiple TCI states for uplink communications by a UE via one or more CCs, output a message including uplink power control information that indicates a power control parameter associated with uplink pathloss, the power control parameter corresponding to at least two TCI states from among the set of multiple TCI states, and obtain, via the one or more CCs in accordance with the at least two TCI states, the uplink communications using one or more transmit powers based on the power control parameter.
Another network entity for wireless communication is described. The network entity may include means for outputting a control message that indicates a set of multiple TCI states for uplink communications by a UE via one or more CCs, means for outputting a message including uplink power control information that indicates a power control parameter associated with uplink pathloss, the power control parameter corresponding to at least two TCI states from among the set of multiple TCI states, and means for obtaining, via the one or more CCs in accordance with the at least two TCI states, the uplink communications using one or more transmit powers based on the power control parameter.
A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to output a control message that indicates a set of multiple TCI states for uplink communications by a UE via one or more CCs, output a message including uplink power control information that indicates a power control parameter associated with uplink pathloss, the power control parameter corresponding to at least two TCI states from among the set of multiple TCI states, and obtain, via the one or more CCs in accordance with the at least two TCI states, the uplink communications using one or more transmit powers based on the power control parameter.
In some examples of the method, network entities, and non-transitory computer-readable medium described herein, outputting the message may include operations, features, means, or instructions for outputting a MAC-CE that indicates the power control parameter corresponding to the at least two TCI states.
Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting the power control parameter via a set of one or more reserved bits within the MAC-CE, an uplink power control field within the MAC-CE, or both.
Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting, via a set of multiple uplink power control fields within the MAC-CE, the power control parameter.
In some examples of the method, network entities, and non-transitory computer-readable medium described herein, a quantity of the set of multiple uplink power control fields may be based on a quantity of TCI states from among the set of multiple TCI states that may be activated for the uplink communications by the UE and the quantity of the set of multiple uplink power control fields may be based on the quantity of TCI states from among the set of multiple TCI states that may be activated for the uplink communications by the UE and that may be associated with an uplink power control configuration.
Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting, via the MAC-CE, one or more fields that indicate one or more TCI states from among the set of multiple TCI states that may be activated for the uplink communications by the UE, where each field of the one or more fields indicates a respective TCI state and indicates whether the set of multiple uplink power control fields includes a respective power uplink control field that corresponds to the respective TCI state.
Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features,  means, or instructions for outputting, via each uplink power control field of the set of multiple uplink power control fields, a respective identifier associated with a respective TCI state to which the power control parameter included in the uplink power control field applies.
In some examples of the method, network entities, and non-transitory computer-readable medium described herein, outputting the MAC-CE may include operations, features, means, or instructions for outputting a unified TCI state activation MAC-CE that indicates one or more TCI states from among the set of multiple TCI states that may be activated for the uplink communications by the UE.
Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting a unified TCI state activation MAC-CE, where the unified TCI state activation MAC-CE indicates one or more TCI states from among the set of multiple TCI states that may be activated for the uplink communications by the UE.
In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the power control parameter includes a pathloss offset and the MAC-CE includes at least one field that indicates whether the pathloss offset may be with respect to a nominal pathloss or a measured pathloss.
Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting, after receiving the uplink communications using the one or more transmit powers, a second message including second uplink power control information, where the message includes a unified TCI state activation MAC-CE that indicates one or more TCI states from among the set of multiple TCI states that may be activated for the uplink communications by the UE, and where the second message includes a MAC-CE different than the unified TCI state activation MAC-CE.
In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the power control parameter indicated via the message includes a reference to a measured parameter, a second power control parameter indicated via the second message includes a second reference to a nominal  parameter, a previous parameter, an initial parameter, a measured parameter, or any combination thereof, and the second message includes one or more fields that indicate whether the second power control parameter indicated via the second message references the nominal parameter, the previous parameter, the initial parameter, the measured parameter, or any combination thereof.
Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting an indication of a set of CCs for TCI state activation, where the power control parameter corresponds to the one or more CCs that may be the same as the set of CCs for TCI state activation, and where the power control parameter may be applied to the at least two TCI states across the set of CCs.
Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting a first indication of a first set of CCs for TCI state activation and outputting a second indication of a second set of CCs associated with uplink power control, where the power control parameter corresponds to the one or more CCs that may be the same as the second set of CCs for uplink power control, and where the power control parameter may be applied to the at least two TCI states across the second set of CCs.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 shows an example of a wireless communications system that supports power control information for multiple transmission configuration indication (TCI) states in accordance with one or more aspects of the present disclosure.
FIG. 2 shows an example of a network architecture that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure.
FIG. 3 shows an example of an uplink dense deployment that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure.
FIG. 4 shows an example of an uplink power control message that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure.
FIG. 5 shows an example of an uplink power control message that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure.
FIG. 6 shows an example of a signaling sequence that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure.
FIG. 7 shows an example of a process flow that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure.
FIGs. 8 and 9 show block diagrams of devices that support power control information for multiple TCI states in accordance with one or more aspects of the present disclosure.
FIG. 10 shows a block diagram of a communications manager that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure.
FIG. 11 shows a diagram of a system including a device that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure.
FIGs. 12 and 13 show block diagrams of devices that support power control information for multiple TCI states in accordance with one or more aspects of the present disclosure.
FIG. 14 shows a block diagram of a communications manager that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure.
FIG. 15 shows a diagram of a system including a device that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure.
FIGs. 16 through 20 show flowcharts illustrating methods that support power control information for multiple TCI states in accordance with one or more aspects of the present disclosure.
DETAILED DESCRIPTION
In some wireless communications systems, a user equipment (UE) may receive a downlink reference signal from a network entity for determining (e.g., calculating, obtaining) a pathloss associated with a channel between the UE and the network entity. The UE may use the pathloss to determine an uplink transmit power for uplink messages to the network entity. Some wireless communications system may be associated with an uplink dense deployment in which a central network entity is configured for transmitting downlink signaling to the UE and multiple network entities (e.g., uplink-dedicated network entities) are configured for receiving uplink signaling from the UE. In such systems, the uplink-dedicated network entities may not transmit the downlink reference signals and the UE may instead transmit uplink reference signals to an uplink-dedicated network entity.
The uplink-dedicated network entity may indicate channel information (e.g., pathloss) based on the uplink reference signal to the central network entity, and the central network entity may transmit a message to the UE indicating pathloss information or other power control information, such as a pathloss offset or scaling factor, based on the channel information, where the pathloss offset or scaling factor is applied with respect to a reference pathloss. The reference pathloss may be a measured downlink pathloss based on a pathloss reference signal, a nominal pathloss or any combination thereof. The nominal pathloss may be one of an initial measured downlink pathloss associated with the same transmission configuration indication (TCI) state as the pathloss offset, an initial uplink pathloss associated with the same TCI state as the pathloss offset, a previous or latest uplink pathloss associated with the same TCI state as the pathloss offset, or a previous or latest downlink pathloss associated with the same TCI state as the pathloss offset. However, in some systems, the power control  information may be indicated on a per TCI state basis. As such, if a UE supports multiple TCI states, the signaling to indicate the power control information may increase, which may increase complexity and overhead.
Techniques, systems, and devices described herein enable a network entity to indicate power control information for multiple TCI states via a single message. The network entity may transmit control signaling, such as a radio resource control (RRC) message, to a UE to configure multiple TCI states for the UE across multiple component carriers (CCs) . The network entity may subsequently activate a set of one or more of the TCI states for uplink transmissions by the UE. As described herein, the network entity may transmit a single message that indicates a power control parameter applicable to one or more TCI states across one or more CCs. The message may be a medium access control-control element (MAC-CE) , such as a TCI state activation MAC-CE or a separate MAC-CE. The power control parameter may be indicated via one or more reserved bits or fields in the MAC-CE. Various techniques for indicating which TCI states are associated with the indicated power control parameter are described. The power control parameter may be applied to a set of CCs that is the same as the CCs associated with the activated TCI states or with a different set of CCs, and the UE may utilize the power control parameter for transmission across the set of CCs.
The UE may use the power control parameter to determine (e.g., calculate) a transmit power for transmissions using each TCI state or CC. In some examples, the power control parameter may be a pathloss offset or a pathloss scaling factor, and the UE may calculate uplink pathloss using the parameter. The uplink pathloss may then be used to calculate the transmit power for a given TCI state. The described indication of power control information for multiple TCI states may thereby reduce overhead and latency while maintaining reliable wireless communications.
Aspects of the disclosure are initially described in the context of wireless communications systems. Additional aspects are described with reference to an uplink dense deployment, uplink power control messages, a signaling sequence, and a process flow. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to power control information for multiple transmission configuration indication states.
FIG. 1 shows an example of a wireless communications system 100 that supports power control information for multiple transmission configuration indication states in accordance with one or more aspects of the present disclosure. The wireless communications system 100 may include one or more devices, such as one or more network devices (e.g., network entities 105) , one or more UEs 115, and a core network 130. In some examples, the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.
The network entities 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may include devices in different forms or having different capabilities. In various examples, a network entity 105 may be referred to as a network element, a mobility element, a radio access network (RAN) node, or network equipment, among other nomenclature. In some examples, network entities 105 and UEs 115 may wirelessly communicate via communication link (s) 125 (e.g., a radio frequency (RF) access link) . For example, a network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UEs 115 and the network entity 105 may establish the communication link (s) 125. The coverage area 110 may be an example of a geographic area over which a network entity 105 and a UE 115 may support the communication of signals according to one or more radio access technologies (RATs) .
The UEs 115 may be dispersed throughout a coverage area 110 of the wireless communications system 100, and each UE 115 may be stationary, or mobile, or both at different times. The UEs 115 may be devices in different forms or having different capabilities. Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communications with various types of devices in the wireless communications system 100 (e.g., other wireless communication devices, including UEs 115 or network entities 105) , as shown in FIG. 1.
As described herein, a node of the wireless communications system 100, which may be referred to as a network node, or a wireless node, may be a network entity 105 (e.g., any network entity described herein) , a UE 115 (e.g., any UE described  herein) , a network controller, an apparatus, a device, a 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 a UE 115. As another example, a node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first, second, and third nodes may be different relative to these examples. Similarly, reference to a UE 115, network entity 105, apparatus, device, computing system, or the like may include disclosure of the UE 115, network entity 105, apparatus, device, computing system, or the like being a node. For example, disclosure that a UE 115 is configured to receive information from a network entity 105 also discloses that a first node is configured to receive information from a second node.
In some examples, network entities 105 may communicate with a core network 130, or with one another, or both. For example, network entities 105 may communicate with the core network 130 via backhaul communication link (s) 120 (e.g., in accordance with an S1, N2, N3, or other interface protocol) . In some examples, network entities 105 may communicate with one another via backhaul communication link (s) 120 (e.g., in accordance with an X2, Xn, or other interface protocol) either directly (e.g., directly between network entities 105) or indirectly (e.g., via the core network 130) . In some examples, network entities 105 may communicate with one another via a midhaul communication link 162 (e.g., in accordance with a midhaul interface protocol) or a fronthaul communication link 168 (e.g., in accordance with a fronthaul interface protocol) , or any combination thereof. The backhaul communication link (s) 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., an electrical link, an optical fiber link) or one or more wireless links (e.g., a radio link, a wireless optical link) , among other examples or various combinations thereof. A UE 115 may communicate with the core network 130 via a communication link 155.
One or more of the network entities 105 or network equipment described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or giga-NodeB (either of which may be referred to as a gNB) , a 5G NB, a next-generation eNB (ng-eNB) , a Home NodeB, a Home eNodeB, or other suitable terminology) . In some examples, a network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within one network entity (e.g., a network entity 105 or a single RAN node, such as a base station 140) .
In some examples, a network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) , which may be configured to utilize a protocol stack that is physically or logically distributed among multiple network entities (e.g., network entities 105) , such as an integrated access and 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, a network entity 105 may include one or more of a central unit (CU) , such as a CU 160, a distributed unit (DU) , such as a DU 165, a radio unit (RU) , such as an RU 170, a RAN Intelligent Controller (RIC) , such as an RIC 175 (e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC) ) , a Service Management and Orchestration (SMO) system, such as an SMO system 180, or any combination thereof. An RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) . One or more components of the network entities 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 105 may be located in distributed locations (e.g., separate physical locations) . In some examples, one or more of the network entities 105 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU) ) .
The split of functionality between a CU 160, a DU 165, and an RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or  any combinations thereof) are performed at a CU 160, a DU 165, or an RU 170. For example, a functional split of a protocol stack may be employed between a CU 160 and a DU 165 such that the CU 160 may support one or more layers of the protocol stack and the DU 165 may support one or more different layers of the protocol stack. In some examples, the CU 160 may host upper protocol layer (e.g., layer 3 (L3) , layer 2 (L2) ) functionality and signaling (e.g., Radio Resource Control (RRC) , service data adaption protocol (SDAP) , Packet Data Convergence Protocol (PDCP) ) . The CU 160 (e.g., one or more CUs) may be connected to a DU 165 (e.g., one or more DUs) or an RU 170 (e.g., one or more RUs) , or some combination thereof, and the DUs 165, RUs 170, or both may 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 may each be at least partially controlled by the CU 160. Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU 165 and an RU 170 such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or multiple different cells (e.g., via one or multiple different RUs, such as an RU 170) . In some cases, a functional split between a CU 160 and a DU 165 or between a DU 165 and an RU 170 may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU 160, a DU 165, or an RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170) . A CU 160 may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU 160 may be connected to a DU 165 via a midhaul communication link 162 (e.g., F1, F1-c, F1-u) , and a DU 165 may be connected to an RU 170 via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface) . In some examples, a midhaul communication link 162 or a fronthaul communication link 168 may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities (e.g., one or more of the network entities 105) that are in communication via such communication links.
In some wireless communications systems (e.g., the wireless communications system 100) , infrastructure and spectral resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections,  providing an IAB network architecture (e.g., to a core network 130) . In some cases, in an IAB network, one or more of the network entities 105 (e.g., network entities 105 or IAB node (s) 104) may be partially controlled by each other. The IAB node (s) 104 may be referred to as a donor entity or an IAB donor. A DU 165 or an RU 170 may be partially controlled by a CU 160 associated with a network entity 105 or base station 140 (such as a donor network entity or a donor base station) . The one or more donor entities (e.g., IAB donors) may be in communication with one or more additional devices (e.g., IAB node (s) 104) via supported access and backhaul links (e.g., backhaul communication link (s) 120) . IAB node (s) 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by one or more DUs (e.g., DUs 165) of a coupled IAB donor. An IAB-MT may be equipped with an independent set of antennas for relay of communications with UEs 115 or may share the same antennas (e.g., of an RU 170) of IAB node (s) 104 used for access via the DU 165 of the IAB node (s) 104 (e.g., referred to as virtual IAB-MT (vIAB-MT) ) . In some examples, the IAB node (s) 104 may include one or more DUs (e.g., DUs 165) that support communication links with additional entities (e.g., IAB node (s) 104, UEs 115) within the relay chain or configuration of the access network (e.g., downstream) . In such cases, one or more components of the disaggregated RAN architecture (e.g., the IAB node (s) 104 or components of the IAB node (s) 104) may be configured to operate according to the techniques described herein.
For instance, an access network (AN) or RAN may include communications between access nodes (e.g., an IAB donor) , IAB node (s) 104, and one or more UEs 115. The IAB donor may facilitate connection between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130) . That is, an IAB donor may refer to a RAN node with a wired or wireless connection to the core network 130. The IAB donor may include one or more of a CU 160, a DU 165, and an RU 170, in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link) . The IAB donor and IAB node (s) 104 may communicate via an F1 interface according to a protocol that defines signaling messages (e.g., an F1 AP protocol) . Additionally, or alternatively, the CU 160 may communicate with the core network 130 via an interface, which may be an example of a portion of a backhaul link, and may communicate with other CUs (e.g., including a CU 160 associated with an  alternative IAB donor) via an Xn-C interface, which may be an example of another portion of a backhaul link.
IAB node (s) 104 may refer to RAN nodes that provide IAB functionality (e.g., access for UEs 115, wireless self-backhauling capabilities) . A DU 165 may act as a distributed scheduling node towards child nodes associated with the IAB node (s) 104, and the IAB-MT may act as a scheduled node towards parent nodes associated with IAB node (s) 104. That is, an IAB donor may be referred to as a parent node in communication with one or more child nodes (e.g., an IAB donor may relay transmissions for UEs through other IAB node (s) 104) . Additionally, or alternatively, IAB node (s) 104 may also be referred to as parent nodes or child nodes to other IAB node (s) 104, depending on the relay chain or configuration of the AN. The IAB-MT entity of IAB node (s) 104 may provide a Uu interface for a child IAB node (e.g., the IAB node (s) 104) to receive signaling from a parent IAB node (e.g., the IAB node (s) 104) , and a DU interface (e.g., a DU 165) may provide a Uu interface for a parent IAB node to signal to a child IAB node or UE 115.
For example, IAB node (s) 104 may be referred to as parent nodes that support communications for child IAB nodes, or may be referred to as child IAB nodes associated with IAB donors, or both. An IAB donor may include a CU 160 with a wired or wireless connection (e.g., backhaul communication link (s) 120) to the core network 130 and may act as a parent node to IAB node (s) 104. For example, the DU 165 of an IAB donor may relay transmissions to UEs 115 through IAB node (s) 104, or may directly signal transmissions to a UE 115, or both. The CU 160 of the IAB donor may signal communication link establishment via an F1 interface to IAB node (s) 104, and the IAB node (s) 104 may schedule transmissions (e.g., transmissions to the UEs 115 relayed from the IAB donor) through one or more DUs (e.g., DUs 165) . That is, data may be relayed to and from IAB node (s) 104 via signaling via an NR Uu interface to MT of IAB node (s) 104 (e.g., other IAB node (s) ) . Communications with IAB node (s) 104 may be scheduled by a DU 165 of the IAB donor or of IAB node (s) 104.
In the case of the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support test as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a  base station 140) may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., components such as an IAB node, a DU 165, a CU 160, an RU 170, an RIC 175, an SMO system 180) .
A UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples. A UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA) , a tablet computer, a laptop computer, or a personal computer. In some examples, a UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, vehicles, or meters, among other examples.
The UEs 115 described herein may be able to communicate with various types of devices, such as UEs 115 that may sometimes operate as relays, as well as the network entities 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.
The UEs 115 and the network entities 105 may wirelessly communicate with one another via the communication link (s) 125 (e.g., one or more access links) using resources associated with one or more carriers. The term “carrier” may refer to a set of RF spectrum resources having a defined PHY layer structure for supporting the communication link (s) 125. For example, a carrier used for the communication link (s) 125 may include a portion of an RF spectrum band (e.g., a bandwidth part (BWP) ) that is operated according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR) . Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information) , control signaling that coordinates operation for the carrier, user data, or other signaling. The wireless communications system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation. A UE 115 may be configured with multiple downlink CCs and one or more uplink CCs according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time  division duplexing (TDD) CCs. Communication between a network entity 105 and other devices may refer to communication between the devices and any portion (e.g., entity, sub-entity) of a network entity 105. For example, the terms “transmitting, ” “receiving, ” or “communicating, ” when referring to a network entity 105, may refer to any portion of a network entity 105 (e.g., a base station 140, a CU 160, a DU 165, a RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities, such as one or more of the network entities 105) .
In some examples, such as in a carrier aggregation configuration, a carrier may have acquisition signaling or control signaling that coordinates operations for other carriers. A carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute RF channel number (EARFCN) ) and may be identified according to a channel raster for discovery by the UEs 115. A carrier may be operated in a standalone mode, in which case initial acquisition and connection may be conducted by the UEs 115 via the carrier, or the carrier may be operated in a non-standalone mode, in which case a connection is anchored using a different carrier (e.g., of the same or a different RAT) .
The communication link (s) 125 of the wireless communications system 100 may include downlink transmissions (e.g., forward link transmissions) from a network entity 105 to a UE 115, uplink transmissions (e.g., return link transmissions) from a UE 115 to a network entity 105, or both, among other configurations of transmissions. Carriers may carry downlink or uplink communications (e.g., in an FDD mode) or may be configured to carry downlink and uplink communications (e.g., in a TDD mode) .
A carrier may be associated with a particular bandwidth of the RF spectrum and, in some examples, the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system 100. For example, the carrier bandwidth may be one of a set of bandwidths for carriers of a particular RAT (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz) ) . Devices of the wireless communications system 100 (e.g., the network entities 105, the UEs 115, or both) may have hardware configurations that support communications using a particular carrier bandwidth or may be configurable to support communications using one of a set of carrier bandwidths. In some examples, the wireless communications system 100 may include network entities 105 or UEs 115 that support concurrent communications using  carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured for operating using portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth.
Signal waveforms transmitted via a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM) ) . In a system employing MCM techniques, a resource element may refer to resources of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The quantity of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both) , such that a relatively higher quantity of resource elements (e.g., in a transmission duration) and a relatively higher order of a modulation scheme may correspond to a relatively higher rate of communication. A wireless communications resource may refer to a combination of an RF spectrum resource, a time resource, and a spatial resource (e.g., a spatial layer, a beam) , and the use of multiple spatial resources may increase the data rate or data integrity for communications with a UE 115.
One or more numerologies for a carrier may be supported, and a numerology may include a subcarrier spacing (Δf) and a cyclic prefix. A carrier may be divided into one or more BWPs having the same or different numerologies. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time and communications for the UE 115 may be restricted to one or more active BWPs.
The time intervals for the network entities 105 or the UEs 115 may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of Ts=1/(Δfmax·Nf) seconds, for which Δfmax may represent a supported subcarrier spacing, and Nf may represent a supported discrete Fourier transform (DFT) size. Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms) ) . Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023) .
Each frame may include multiple consecutively-numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a quantity of slots. Alternatively, each frame may include a variable quantity of slots, and the quantity of slots may depend on subcarrier spacing. Each slot may include a quantity of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period) . In some wireless communications systems, such as the wireless communications system 100, a slot may further be divided into multiple mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., Nf) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.
A subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and may be referred to as a transmission time interval (TTI) . In some examples, the TTI duration (e.g., a quantity of symbol periods in a TTI) may be variable. Additionally, or alternatively, the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs) ) .
Physical channels may be multiplexed for communication using a carrier according to various techniques. A physical control channel and a physical data channel may be multiplexed for signaling via a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET) ) for a physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) may be configured for a set of the UEs 115. For example, one or more of the UEs 115 may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate may refer to an amount of control channel resources (e.g., control channel elements (CCEs) ) associated with encoded  information for a control information format having a given payload size. Search space sets may include common search space sets configured for sending control information to UEs 115 (e.g., one or more UEs) or may include UE-specific search space sets for sending control information to a UE 115 (e.g., a specific UE) .
A network entity 105 may provide communication coverage via one or more cells, for example a macro cell, a small cell, a hot spot, or other types of cells, or any combination thereof. The term “cell” may refer to a logical communication entity used for communication with a network entity 105 (e.g., using a carrier) and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID) , a virtual cell identifier (VCID) ) . In some examples, a cell also may refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) over which the logical communication entity operates. Such cells may range from smaller areas (e.g., a structure, a subset of structure) to larger areas depending on various factors such as the capabilities of the network entity 105. For example, a cell may be or include a building, a subset of a building, or exterior spaces between or overlapping with coverage areas 110, among other examples.
A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by the UEs 115 with service subscriptions with the network provider supporting the macro cell. A small cell may be associated with a network entity 105 operating with lower power (e.g., a base station 140 operating with lower power) relative to a macro cell, and a small cell may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to the UEs 115 with service subscriptions with the network provider or may provide restricted access to the UEs 115 having an association with the small cell (e.g., the UEs 115 in a closed subscriber group (CSG) , the UEs 115 associated with users in a home or office) . A network entity 105 may support one or more cells and may also support communications via the one or more cells using one or multiple CCs.
In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT) , enhanced mobile broadband (eMBB) ) that may provide access for different types of devices.
In some examples, a network entity 105 (e.g., a base station 140, an RU 170) may be movable and therefore provide communication coverage for a moving coverage area, such as the coverage area 110. In some examples, coverage areas 110 (e.g., different coverage areas) associated with different technologies may overlap, but the coverage areas 110 (e.g., different coverage areas) may be supported by the same network entity (e.g., a network entity 105) . In some other examples, overlapping coverage areas, such as a coverage area 110, associated with different technologies may be supported by different network entities (e.g., the network entities 105) . The wireless communications system 100 may include, for example, a heterogeneous network in which different types of the network entities 105 support communications for coverage areas 110 (e.g., different coverage areas) using the same or different RATs.
The wireless communications system 100 may support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base stations 140) may have similar frame timings, and transmissions from different network entities (e.g., different ones of the network entities 105) may be approximately aligned in time. For asynchronous operation, network entities 105 may have different frame timings, and transmissions from different network entities (e.g., different ones of network entities 105) may, in some examples, not be aligned in time. The techniques described herein may be used for either synchronous or asynchronous operations.
Some UEs 115, such as MTC or IoT devices, may be relatively low cost or low complexity devices and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication) . M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a network entity 105 (e.g., a base station 140) without human intervention. In some examples, M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application program that uses the information or presents the information to humans interacting with the application program. Some UEs 115 may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and  geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.
Some UEs 115 may be configured to employ operating modes that reduce power consumption, such as half-duplex communications (e.g., a mode that supports one-way communication via transmission or reception, but not transmission and reception concurrently) . In some examples, half-duplex communications may be performed at a reduced peak rate. Other power conservation techniques for the UEs 115 may include entering a power saving deep sleep mode when not engaging in active communications, operating using a limited bandwidth (e.g., according to narrowband communications) , or a combination of these techniques. For example, some UEs 115 may be configured for operation using a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs) ) within a carrier, within a guard-band of a carrier, or outside of a carrier.
The wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communications system 100 may be configured to support ultra-reliable low-latency communications (URLLC) . The UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communications may include private communication 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 commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.
In some examples, a UE 115 may be configured to support communicating directly with other UEs (e.g., one or more of the UEs 115) via a device-to-device (D2D) communication link, such as a D2D communication link 135 (e.g., in accordance with a peer-to-peer (P2P) , D2D, or sidelink protocol) . In some examples, one or more UEs 115 of a group that are performing D2D communications may be within the coverage area 110 of a network entity 105 (e.g., a base station 140, an RU 170) , which may support aspects of such D2D communications being configured by (e.g., scheduled by) the network entity 105. In some examples, one or more UEs 115 of such a group may be  outside the coverage area 110 of a network entity 105 or may be otherwise unable to or not configured to receive transmissions from a network entity 105. In some examples, groups of the UEs 115 communicating via D2D communications may support a one-to-many (1: M) system in which each UE 115 transmits to one or more of the UEs 115 in the group. In some examples, a network entity 105 may facilitate the scheduling of resources for D2D communications. In some other examples, D2D communications may be carried out between the UEs 115 without an involvement of a network entity 105.
The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or 5G core (5GC) , which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management function (AMF) ) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) . The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to IP services 150 for one or more network operators. The IP services 150 may include access to the Internet, Intranet (s) , an IP Multimedia Subsystem (IMS) , or a Packet-Switched Streaming Service.
The wireless communications system 100 may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz) . Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from 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 the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. Communications using UHF waves may be  associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers) compared to communications using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.
The wireless communications system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communications system 100 may employ License Assisted Access (LAA) , LTE-Unlicensed (LTE-U) RAT, or NR technology using an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. While operating using unlicensed RF spectrum bands, devices such as the network entities 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance. In some examples, operations using unlicensed bands may be based on a carrier aggregation configuration in conjunction with CCs operating using a licensed band (e.g., LAA) . Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.
A network entity 105 (e.g., a base station 140, an RU 170) or a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a network entity 105 or a UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations 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, antennas or antenna arrays associated with a network entity 105 may be located at diverse geographic locations. A network entity 105 may include an antenna array with a set of rows and columns of antenna ports that the network entity 105 may use to support beamforming of communications with a UE 115. Likewise, a UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally, or alternatively, an antenna panel may support RF beamforming for a signal transmitted via an antenna port.
The network entities 105 or the UEs 115 may use MIMO communications to exploit multipath signal propagation and increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such techniques may be referred  to as spatial multiplexing. The multiple signals may, for example, be transmitted by the transmitting device via different antennas or different combinations of antennas. Likewise, the multiple signals may be received by the receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords) . Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO) , for which multiple spatial layers are transmitted to the same receiving device, and multiple-user MIMO (MU-MIMO) , for which multiple spatial layers are transmitted to multiple devices.
Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating along particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation) .
A network entity 105 or a UE 115 may use beam sweeping techniques as part of beamforming operations. For example, a network entity 105 (e.g., a base station 140, an RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to conduct beamforming operations for directional communications with a UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted by a network entity 105 multiple times along  different directions. For example, the network entity 105 may transmit a signal according to different beamforming weight sets associated with different directions of transmission. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device, such as a network entity 105, or by a receiving device, such as a UE 115) a beam direction for later transmission or reception by the network entity 105.
Some signals, such as data signals associated with a particular receiving device, may be transmitted by a transmitting device (e.g., a network entity 105 or a UE 115) along a single beam direction (e.g., a direction associated with the receiving device, such as another network entity 105 or UE 115) . In some examples, the beam direction associated with transmissions along a single beam direction may be determined based on a signal that was transmitted along one or more beam directions. For example, a UE 115 may receive one or more of the signals transmitted by the network entity 105 along different directions and may report to the network entity 105 an indication of the signal that the UE 115 received with a highest signal quality or an otherwise acceptable signal quality.
In some examples, transmissions by a device (e.g., by a network entity 105 or a UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from a network entity 105 to a UE 115) . The UE 115 may report feedback that indicates precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more sub-bands. The network entity 105 may transmit a reference signal (e.g., a cell-specific reference signal (CRS) , a channel state information reference signal (CSI-RS) ) , which may be precoded or unprecoded. The UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook) . Although these techniques are described with reference to signals transmitted along one or more directions by a network entity 105 (e.g., a base station 140, an RU 170) , a UE 115 may employ similar techniques for transmitting signals multiple times along different directions (e.g., for identifying a beam direction  for subsequent transmission or reception by the UE 115) or for transmitting a signal along a single direction (e.g., for transmitting data to a receiving device) .
A receiving device (e.g., a UE 115) may perform reception operations in accordance with multiple receive configurations (e.g., directional listening) when receiving various signals from a transmitting device (e.g., a network entity 105) , such as synchronization signals, reference signals, beam selection signals, or other control signals. For example, a receiving device may perform reception in accordance with multiple receive directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as “listening” according to different receive configurations or receive directions. In some examples, a receiving device may use a single receive configuration to receive along a single beam direction (e.g., when receiving a data signal) . The single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio (SNR) , or otherwise acceptable signal quality based on listening according to multiple beam directions) .
The UEs 115 and the network entities 105 may support retransmissions of data to increase the likelihood that data is received successfully. Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly via a communication link (e.g., the communication link (s) 125, a D2D communication link 135) . HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC) ) , forward error correction (FEC) , and retransmission (e.g., automatic repeat request (ARQ) ) . HARQ may improve throughput at the MAC layer in relatively poor radio conditions (e.g., low signal-to-noise conditions) . In some examples, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific slot for data received  via a previous symbol in the slot. In some other examples, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.
In some examples, a UE 115 may be configured with a unified TCI state type per CC. The unified TCI may indicate a TCI state (e.g., a TCI mode) , which may include one or more communication parameters (e.g., a channel) for communicating with one or more network entities 105. For example, the unified TCI may indicate a joint TCI state, where the UE 115 may communicate with the network entity 105 via at least one downlink channel and at least one uplink channel using the common beam. In some other examples, the unified TCI may indicate a separate downlink TCI state, where the UE 115 may communicate with the network entity 105 via multiple downlink channels, reference signals, or both, using the common beam. In yet some other examples, the unified TCI state may indicate a separate uplink TCI state, where the UE 115 may communicate with the network entity 105 via multiple uplink channels, reference signals, or both, using the common beam.
If a joint unified TCI state is configured, the UE 115 may be configured with a set of TCI states. For example, the UE 115 may receive control signaling (e.g., an RRC configuration) that indicates a list of TCI states (e.g., up to 128 TCI states) via a parameter (e.g., dl-OrJointTCI-StateList) for downlink and uplink operation. In this case, the TCI state may be used to provide a reference signal for a quasi co-location (QCL) for a demodulation reference signal (DMRS) of a physical downlink shared channel (PDSCH) , a DMRS of a physical downlink control channel (PDCCH) , and a channel state information (CSI) reference signal (CSI-RS) and to determine an uplink transmit spatial filter for dynamic physical uplink shared channel (PUSCH) , configured grant, physical uplink control channel (PUCCH) , and sounding reference signal (SRS) transmissions.
If a separate TCI state is configured, the UE 115 may be configured with a set of TCI states (e.g., up to 128 TCI states) via a parameter (e.g., dl-OrJointTCI-StateList) for downlink and a second set (e.g., up to 64 TCI states) via a second parameter (e.g., ul-TCI-ToAddModList) for uplink. In this case, the downlink TCI state may be used to provide a reference signal for a QCL for a DMRS of a PDSCH, for a DMRS of a PDCCH, and a CSI-RS. The uplink TCI state may be used to determine an  uplink transmit spatial filter for dynamic PUSCH, configured grant, PUCCH, and SRS transmissions.
In some examples, up to eight TCI states or pairs of TCI states including one TCI state for uplink and one TCI state for downlink may be activated by a TCI activation MAC-CE. That is, the network entity 105 may transmit a TCI state activation MAC-CE to the UE 115 to indicate some quantity of one or more TCI states that are activated for uplink or downlink communications by the UE 115. In some examples, a common TCI state identifier update and activation may be supported to provide QCL information, common uplink transmit spatial filters, or both across a set of configured CCs. For example, a set of RRC configured TCI state pools may be configured for each bandwidth part or CC. Additionally, or alternatively, a set of RRC configured TCI state pools for each bandwidth or CC may be absent, and may be replaced with a reference to RRC configured TCI state pools in a reference bandwidth part or CC.
In some examples described herein, a network entity 105 may transmit uplink power control information to a UE 115 for multiple TCI states supported by the UE 115. For example, the network entity 105 may transmit, to the UE 115, a single message that is associated with multiple TCI states. The message may be a TCI state activation MAC-CE or another type of MAC-CE, in some examples. The message may be transmitted after the UE 115 is configured with one or more TCI states across one or more CCs. The uplink power control information may indicate a power control parameter for uplink pathloss calculation for the one or more CCs. The power control parameter may be, for example, an uplink pathloss offset, an uplink pathloss scaling factor, or some other parameter that may be used in a calculation of uplink transmit power. The power control parameter may correspond to one or more TCI states from the multiple TCI states configured for the UE 115. The UE 115 may transmit uplink communications via one or more CCs according to the one or more TCI states. The uplink communications may be transmitted according to one or more transmit powers that are based on the power control parameter.
FIG. 2 shows an example of a network architecture 200 (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that supports power control information for multiple transmission configuration indication states in accordance with one or more aspects of the present disclosure. The network architecture  200 may illustrate an example for implementing one or more aspects of the wireless communications system 100. The network architecture 200 may include one or more CUs 160-a that may communicate directly with a core network 130-a via a backhaul communication link 120-a, or indirectly with the core network 130-a through one or more disaggregated network entities 105 (e.g., a Near-RT RIC 175-b via an E2 link, or a Non-RT RIC 175-a associated with an SMO 180-a (e.g., an SMO Framework) , or both) . A CU 160-a may communicate with one or more DUs 165-a via respective midhaul communication links 162-a (e.g., an F1 interface) . The DUs 165-a may communicate with one or more RUs 170-a via respective fronthaul communication links 168-a. The RUs 170-a may be associated with respective coverage areas 110-a and may communicate with UEs 115-a via one or more communication links 125-a. In some implementations, a UE 115-a may be simultaneously served by multiple RUs 170-a.
Each of the network entities 105 of the network architecture 200 (e.g., CUs 160-a, DUs 165-a, RUs 170-a, Non-RT RICs 175-a, Near-RT RICs 175-b, SMOs 180-a, Open Clouds (O-Clouds) 205, Open eNBs (O-eNBs) 210) may include one or more interfaces or may be coupled with one or more interfaces configured to receive or transmit signals (e.g., data, information) via a wired or wireless transmission medium. Each network entity 105, or an associated processor (e.g., controller) providing instructions to an interface of the network entity 105, may be configured to communicate with one or more of the other network entities 105 via the transmission medium. For example, the network entities 105 may include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other network entities 105. Additionally, or alternatively, the network entities 105 may include a wireless interface, which may include a receiver, a transmitter, or transceiver (e.g., an RF transceiver) configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other network entities 105.
In some examples, a CU 160-a may host one or more higher layer control functions. Such control functions may include RRC, PDCP, SDAP, or the like. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by the CU 160-a. A CU 160-a may be configured to handle user plane functionality (e.g., CU-UP) , control plane functionality  (e.g., CU-CP) , or a combination thereof. In some examples, a CU 160-a may be logically split into one or more CU-UP units and one or more CU-CP units. A CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface, such as an E1 interface when implemented in an O-RAN configuration. A CU 160-a may be implemented to communicate with a DU 165-a, as necessary, for network control and signaling.
A DU 165-a may correspond to a logical unit that includes one or more functions (e.g., base station functions, RAN functions) to control the operation of one or more RUs 170-a. In some examples, a DU 165-a may host, at least partially, one or more of an RLC layer, a MAC layer, and one or more aspects of a PHY layer (e.g., a high PHY layer, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, or the like) depending, at least in part, on a functional split, such as those defined by the 3rd Generation Partnership Project (3GPP) . In some examples, a DU 165-a may further host one or more low PHY layers. Each layer may be implemented with an interface configured to communicate signals with other layers hosted by the DU 165-a, or with control functions hosted by a CU 160-a.
In some examples, lower-layer functionality may be implemented by one or more RUs 170-a. For example, an RU 170-a, controlled by a DU 165-a, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (e.g., performing fast Fourier transform (FFT) , inverse FFT (iFFT) , digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like) , or both, based at least in part on the functional split, such as a lower-layer functional split. In such an architecture, an RU 170-a may be implemented to handle over the air (OTA) communication with one or more UEs 115-a. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU (s) 170-amay be controlled by the corresponding DU 165-a. In some examples, such a configuration may enable a DU 165-a and a CU 160-a to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.
The SMO 180-a may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a may be configured to support the deployment of dedicated physical resources for RAN coverage requirements which may be managed  via an operations and maintenance interface (e.g., an O1 interface) . For virtualized network entities 105, the SMO 180-a may be configured to interact with a cloud computing platform (e.g., an O-Cloud 205) to perform network entity life cycle management (e.g., to instantiate virtualized network entities 105) via a cloud computing platform interface (e.g., an O2 interface) . Such virtualized network entities 105 can include, but are not limited to, CUs 160-a, DUs 165-a, RUs 170-a, and Near-RT RICs 175-b. In some implementations, the SMO 180-a may communicate with components configured in accordance with a 4G RAN (e.g., via an O1 interface) . Additionally, or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RUs 170-a via an O1 interface. The SMO 180-a also may include a Non-RT RIC 175-a configured to support functionality of the SMO 180-a.
The Non-RT RIC 175-a may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence (AI) or Machine Learning (ML) workflows including model training and updates, or policy-based guidance of applications/features in the Near-RT RIC 175-b. The Non-RT RIC 175-a may be coupled to or communicate with (e.g., via an A1 interface) the Near-RT RIC 175-b. The Near-RT RIC 175-b may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (e.g., via an E2 interface) connecting one or more CUs 160-a, one or more DUs 165-a, or both, as well as an O-eNB 210, with the Near-RT RIC 175-b.
In some examples, to generate AI/ML models to be deployed in the Near-RT RIC 175-b, the Non-RT RIC 175-a may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 175-b and may be received at the SMO 180-a or the Non-RT RIC 175-a from non-network data sources or from network functions. In some examples, the Non-RT RIC 175-a or the Near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 175-a may monitor long-term trends and patterns for performance and employ AI or ML models to perform corrective actions through the SMO 180-a (e.g., reconfiguration via O1) or via generation of RAN management policies (e.g., A1 policies) .
In some examples described herein, a network entity 105 may communicate with a UE 115-a via an uplink dense deployment, in which the network entity 105 may transmit downlink communications to the UE 115-a and may receive uplink communications from the UE 115-a via another node, such as an RU 170-a. In such examples, techniques for the UE 115-a to calculate an uplink transmit power may be ambiguous.
Techniques described herein provide for the network entity 105 to transmit a single message that indicates uplink power control information for multiple TCI states supported by the UE 115-a. For example, the network entity 105 may transmit, to the UE 115-a, a single message that is associated with multiple TCI states. The message may be a TCI state activation MAC-CE or another type of MAC-CE, in some examples. The message may be transmitted after the UE 115-a is configured with one or more TCI states across one or more CCs. The uplink power control information may indicate a power control parameter for uplink pathloss calculation for the one or more CCs. The power control parameter may be, for example, an uplink pathloss offset, an uplink pathloss scaling factor, or some other parameter that may be used in a calculation of uplink transmit power. The power control parameter may correspond to one or more TCI states from the multiple TCI states configured for the UE 115-a. The UE 115-a may transmit uplink communications via one or more CCs according to the one or more TCI states. The uplink communications may be transmitted according to one or more transmit powers that are based on the power control parameter.
FIG. 3 shows an example of an uplink dense deployment 300 that supports power control information for multiple transmission configuration indication states in accordance with one or more aspects of the present disclosure. The uplink dense deployment 300 may implement or be implemented by aspects of the wireless communications system 100 or the network architecture 200. For example, the uplink dense deployment 300 illustrates a system including a downlink transmission point 305 and uplink reception points 310 connected with the downlink transmission point 305 via backhaul links 315. In some implementations, the downlink transmission point 305 and the uplink reception points 310 may be associated with a network entity 105, such as a network entity 105 as illustrated by or described with reference to FIGs. 1 and 2. Further, although illustrated as including multiple uplink reception points 310, the  uplink dense deployment 300 may include any quantity of one or more uplink reception points 310 or any quantity of downlink transmission points 305.
The uplink dense deployment 300 may be understood as or associated with an asymmetric downlink single transmission and reception point (sTRP) /uplink multi-transmission and reception point (mTRP) deployment scenarios, in intra-band intra-cell non-collocated mTRP scenarios, and with a unified TCI framework for mTRP (using, such as communicating via, FR1 or FR2) . In some aspects, the uplink dense deployment 300 may support two closed-loop power control adjustment states for SRS, both separate from PUSCH, and pathloss offset configurations for pathloss calculation to uplink TRP (s) , when the pathloss reference signal is from a downlink sTRP (e.g., the downlink transmission point 305) . The uplink dense deployment 300 may further support multi-downlink control information (DCI) -based two transmitter address toward uplink TRP (s) and downlink sTRP without using CoresetPoolIndex, while assuming backwards compatible PRACH resources.
The network entity 105 may refer to a base station, a gNB, or another entity or node that controls or is otherwise associated with (such as connected with via a backhaul link) one or more uplink reception points 310. Thus, the network entity 105 may be understood as including one or more uplink reception points 310 or as being communicatively coupled with the one or more uplink reception points 310 (via, for example, one or more backhaul links 315, which may be wired or wireless) . Accordingly, the network entity 105 may receive or otherwise obtain uplink signaling from one or more UEs 115 via one or more uplink reception points 310.
The network entity 105 may also include or otherwise control the downlink transmission point 305 via which the network entity 105 transmits downlink signals or channels. Such a downlink transmission point 305 may be associated with (e.g., may be) a macro node associated with the network entity 105, a central node associated with the network entity 105, a serving cell associated with the network entity 105, or a serving base station associated with the network entity 105. The network entity 105 may support both uplink and downlink communication via its collocated (or approximately collocated) antenna panels and may use the one or more uplink reception points 310 to supplement the uplink coverage or capacity provided by the network entity 105. For example, the network entity 105 may be collocated with the downlink transmission  point 305, may additionally include uplink reception capabilities via one or more antenna panels, and may control or otherwise be associated with the (non-collocated) uplink reception points 310 to supplement uplink coverage and capacity. Uplink signals and channels transmitted by the UE 115 may be received by the uplink reception point (s) 310 and forwarded to the network entity 105.
In other words, the uplink dense deployment 300 may be configured or allocated to improve coverage or capacity of uplink communication and may be associated with an asymmetric downlink/uplink densification. By providing and using the uplink reception points 310, the network entity 105 may reduce uplink pathloss, which may be helpful in scenarios in which uplink coverage is a bottleneck for uplink communication, and in terms of deployment cost or complexity because the uplink reception points 310 may not transmit any downlink signaling. Instead, an uplink reception point 310 may receive an uplink signal or channel and send (e.g., forward, relay, or transmit) the signal or channel (or information parsed or decoded from the signal or channel) to the network entity 105 (e.g., the macro node) . An uplink reception point 310 may send the signal or channel (or information parsed or decoded therefrom) to the network entity 105 with complete or partial processing or without any processing.
In some systems, a UE 115 and a network entity 105 may support an uplink power control operation that relies on a measured downlink pathloss at the UE 115. For example, to control uplink power, the network entity 105 may transmit information indicative of a pathloss reference signal to the UE 115 and the UE 115 may measure a downlink pathloss in accordance with receiving the pathloss reference signal from the network entity 105. The UE 115 may use the measured downlink pathloss to calculate an uplink power, which, in some systems, the UE 115 may expect to be similar to (e.g., a proxy for) an uplink pathloss from the UE 115 to the network entity 105. Uplink power control operations that rely on a measured downlink pathloss at the UE 115 may utilize various different power control formulator or equations for uplink power control, such as depending on a type of transmission by the UE 115.
In scenarios in which a downlink transmission point 305 via which the network entity 105 transmits the pathloss reference signal is non-collocated with an uplink reception point 310 to which the UE 115 transmits uplink signaling, however, the measured downlink pathloss between the UE 115 and the downlink transmission point  305 may deviate substantially from an uplink pathloss between the UE 115 and the uplink reception point 310. In other words, a pathloss associated with a downlink 320 may differ substantially from a pathloss associated with an uplink 325. Such a substantial difference may be understood as a difference that is potentially unable to be reconciled via a pathloss offset (e.g., via a single pathloss offset) , for example, when a relative offset is indicated. That is, in the uplink dense deployment 300 (e.g., uplink-only mode) , there may not be a downlink pathloss reference signal from the uplink reception point 310 to the UE 115. As such, the downlink pathloss reference signal may be received from the downlink transmission point 305 and may not be applicable to the uplink 325.
In some examples, the UE 115 and the network entity 105 may support one or more signaling designs according to which the network entity 105 may indicate a transmit power adjustment due to uplink pathloss change. For example, the network entity 105 may include a transmit power control (TPC) command in a MAC-CE to indicate (an update to) a pathloss offset, with the pathloss offset being relative to a measured downlink pathloss. The TPC command may indicate an absolute pathloss offset or a relative offset with respect to a previous pathloss offset. In such examples, the UE 115 may determine (e.g., calculate, select, estimate, or identify) an uplink pathloss based on a measured downlink pathloss and the pathloss offset, such as by PLu= PLd-pathloss offset. In scenarios in which a downlink pathloss change and an uplink pathloss change are in a same direction (e.g., both increasing or both decreasing) , such a pathloss offset may be sufficient to reconcile the difference between the downlink pathloss and the uplink pathloss. In scenarios in which the downlink pathloss and the uplink pathloss change in opposite directions, however, a pathloss offset or a relative pathloss offset change may become larger. In such scenarios, the pathloss offset to reconcile the difference between downlink pathloss and uplink pathloss may exceed a range of the MAC-CE and the MAC-CE may be unable to update the pathloss offset to a suitable value (with such a suitable value being, for example, a value that reconciles the difference) . Thus, the network entity 105 may transmit multiple MAC-CEs to reconcile the difference, which may lead to inaccurate uplink power control or higher signaling overhead.
In some examples, the UE 115 may apply the pathloss offset to a reference pathloss where the reference pathloss may be one of a measured downlink pathloss or a nominal pathloss. Whether the measured downlink pathloss or the nominal pathloss is used as the reference pathloss may be determined based on one or more rules (e.g., predefined or configured rules) or based on an indication from the network. In some examples, the nominal pathloss may be one of an initial measured downlink pathloss associated with the same TCI state as the pathloss offset, an initial uplink pathloss associated with the same TCI state as the pathloss offset, a previous or latest uplink pathloss associated with the same TCI state as the pathloss offset or a previous or latest downlink pathloss associated with the same TCI state as the pathloss offset. In some other examples, the UE 115 may apply a pathloss scaling factor (e.g., a scaling factor for uplink pathloss) to the nominal pathloss or the measured downlink pathloss for uplink power control. Such a pathloss scaling factor may be a ratio of an uplink pathloss to a reference pathloss, where the reference pathloss may be the nominal pathloss or the measured downlink pathloss. In some implementations, the pathloss scaling factor may be applied separately from a pathloss compensation coefficient α. For example, the pathloss scaling factor may be an additional β parameter such that PLb, f, c (qd) is replaced by β*PLb, f, c (qd) and such that α*PLb, f, c (qd) is replaced by α*`*PLb, f, c (qd) . In some other implementations, the pathloss scaling factor may be combined with the pathloss compensation coefficient α. For example, the network entity 105 may configure a set of α values and each of the α values may correspond to a combined scaling factor of a pathloss compensation coefficient and a pathloss scaling factor. In some aspects, such a combined scaling factor may be denoted as α′=α*β.
In some systems, a pathloss offset or a scaling factor that is indicated to the UE 115 is per TCI state. That is, a MAC-CE or other control message may update a TPC command for a given uplink TCI state. However, one or more TCI states may be activated for uplink communications by the UE 115 via a given CC or across multiple CCs. For example, the network entity 105 may configure multiple TCI states for the UE 115, or the network entity 105 may transmit an activation MAC-CE that activates one or more TCI states for the UE 115, or both, as described with reference to FIG. 1. In such cases, using separate MAC-CEs to update the pathloss offset or scaling factor for different uplink TCI states may increase overhead.
Techniques described herein provide for the network entity 105 to transmit a single control message, such as the single MAC-CE 330, that indicates uplink power control adjustment information for multiple TCI states. The single control message may include a single uplink power control parameter that may be applied to multiple TCI states for communications via a single CC or multiple CCs. The single control message may further indicate which TCI states the power control parameter may be applied to. The UE 115 may thereby receive the power control parameter, determine which TCI states the power control parameter applies to, and calculate one or more uplink transmit power (s) for the TCI states based on the power control parameter.
The power control parameter may be used for uplink pathloss calculation, in some examples. For example, the power control parameter may be a pathloss offset, a pathloss scaling factor, or both. The UE 115 may utilize the pathloss offset or scaling factor in a calculation of transmit power for a given TCI state. As such, the network entity 105 may transmit the power control parameter to update a transmit power at the UE 115. In some examples, the uplink pathloss and scaling factor may be applied relative to a previous or latest measured downlink pathloss or a nominal pathloss. Alternatively, or additionally, the control message described herein may include one or more fields to indicate whether to apply the parameter to the measured or nominal pathloss.
The single control message that conveys the power control parameter may be, for example, a unified TCI state activation MAC-CE 330, a separate MAC-CE 330, or may be indicated via a combination of both. In some examples, the network entity 105 may indicate, via control signaling that configures a set of TCI states for the UE 115 (e.g., RRC configuration) , whether pathloss offset indication is enabled or disabled for each TCI state.
Example signaling formats for conveying uplink power control information for multiple TCI states via a single MAC-CE are described in further detail elsewhere herein, including with reference to FIGs. 4–6.
FIG. 4 shows an example of an uplink power control message 400 that supports power control information for multiple transmission configuration indication states in accordance with one or more aspects of the present disclosure. The uplink  power control message 400 may implement or be implemented by aspects of the wireless communications system 100, the network architecture 200, and the uplink dense deployment 300, as described with reference to FIGs. 1–3. For example, the uplink power control message 400 represents an example format or configuration of a single control message that is operable to convey uplink power control information for multiple TCI states over one or more CCs.
The uplink power control message 400 illustrated in FIG. 4 may be a MAC-CE in this example. Although described with reference to a MAC-CE, it is to be understood that any other type of message may be used in a similar manner to indicate uplink power control information for multiple TCI states. In this example, one or more reserved bits 405 in the message are used to convey the uplink power control information. Thus, any quantity of one or more bits that are not being used in the MAC-CE for indicating other information may be repurposed for indicating uplink power control information as described herein.
In the example illustrated in FIG. 4, the uplink power control message 400 may also be operable to convey TCI state activation information. For example, the uplink power control message 400 may include one or more TCI state activation fields 410 (e.g., TCI state activation fields 410-a, 410-b, through 410-n) that may include one or more bits to indicate an ID of a corresponding TCI state to be activated for the UE. The uplink power control message 400 may thereby represent an example of a TCI state activation MAC-CE, in some examples. As described with reference to FIG. 1, the TCI state activation MAC-CE may be operable to active up to a threshold quantity of TCI states (e.g., eight, or some other quantity) from among a set of multiple TCI states indicated via a previous RRC configuration for the UE. The TCI states may be uplink TCI states, downlink TCI states, or both.
The uplink power control message 400 may include a serving cell ID field, which may indicate a serving cell ID for which the uplink power control message 400 applies. If the indicated serving cell is configured as part of a simultaneous TCI update list (e.g., simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3 or simultaneousU-TCI-UpdateList4) , the uplink power control message 400 may apply to all serving cells that are included in the set of CCs in the simultaneous TCI update list. The uplink power control message 400 may include an  uplink BWP ID field and a downlink BWP ID field, which may indicate a BWP that the message applies for a downlink or uplink TCI state, respectively.
The uplink power control message 400 may include one or more P fields 415 that indicate whether each TCI state activation field 410 (e.g., TCI codepoint) indicates multiple TCI states or a single TCI state. For example, if a given P field 415, such as an i-th field Pi, is set to a first value (e.g., ‘1’ ) , the field may indicate that the corresponding i-th TCI state activation field 410 includes both a downlink TCI state and an uplink TCI state. If the i-th field Pi is set to a second value (e.g., ‘0’ ) , the field may indicate that the corresponding i-th TCI state activation field 410 includes only a downlink or joint TCI state or only an uplink TCI state.
The uplink power control message 400 may include one or more downlink/uplink fields 420 that indicate whether each TCI state activation field 410 is for an uplink TCI state or a downlink or joint TCI state. In some examples, the uplink power control message 400 may include multiple sets of information (e.g., octets, or sets of eight bits) . Each row illustrated in FIG. 4 may represent a set. In such cases, the downlink/uplink field 420 in a given set may indicate whether the TCI state ID that is in the same set is for an uplink TCI state or for a downlink or joint TCI state. If the downlink/uplink field 420 is set to a first value (e.g., ‘1’ ) , the field may indicate that the TCI state ID is used for downlink. The downlink TCI state ID may be indicated via some quantity of bits, such as seven bits, in some examples. If the downlink/uplink field 420 is set to a second value (e.g., ‘0’ ) , the field may indicate that the TCI state ID is used for uplink. The uplink TCI state ID may be indicated via some quantity of bits, such as six bits, in some examples, such that one or more remaining or extra bits may be unused or repurposed. For example, the one or more remaining bits may be used as an extra reserved bit 405-c to indicate power control information, as described herein.
Although an uplink TCI state activation MAC-CE is illustrated in FIG. 4, it is to be understood that the network may convey uplink power control information for multiple TCI states via a separate MAC-CE or other type of message, in some examples. For example, a separate MAC-CE different than the unified TCI state activation MAC-CE may be used to update power control information (e.g., pathloss offset, scaling factor, or the like) for multiple TCI states. In such cases, if the uplink power control message 400 is a separate MAC-CE, the uplink power control message  400 may not include the TCI state activation fields 410, among other types of fields. In such cases, the network may indicate the power control parameter and other uplink power control information via one or more bits or other fields in the separate MAC-CE.
One or more other bits or fields in the uplink power control message 400 may not be used to convey information, in some examples. Such bits may be referred to as reserved bits 405 herein. For example, the uplink power control message 400 may include a reserved bit 405-a, a set of reserved bits 405-b, and at least one reserved bit 405-c in at least one of the TCI state activation fields 410. Techniques described herein provide for a network entity to repurpose the one or more reserved bits 405 to indicate uplink power control information. In some examples, the quantity of reserved bits to be reused may be up to seven plus M bits, where M may represent a quantity of activated uplink TCI states.
As described herein, a set of reserved bits 405-b may be used to convey a value of a power control parameter for multiple TCI states. The power control parameter may be, for example, an uplink pathloss offset, an uplink pathloss scaling factor, or some other type of parameter for uplink power control. In some examples, another one of the reserved bits 405, such as the reserved bit 405-a in the uplink power control message 400 may be used to indicate whether the remaining reserved bits are used to indicate the pathloss offset (e.g., as a TPC command) or not.
In some examples, the power control parameter indicated via the set of reserved bits 405-b may be applied to each of the activated uplink TCI states. That is, a receiving UE may apply the power control parameter to each uplink TCI state ID that is included in the uplink power control message 400 when the UE calculates uplink transmit power (s) for the uplink TCI states. The activated uplink TCI states may be indicated via the TCI state activation fields 410 in the uplink power control message 400 or in TCI state activation fields in a separate message (e.g., an uplink TCI state activation message) , if the uplink power control message 400 is separate from a TCI state activation message. Additionally, or alternatively, the power control parameter indicated via the set of reserved bits 405-b may be applied to each of the activated uplink TCI states that are also associated with an uplink power control parameter configuration (e.g., enabled with pathloss offset by RRC) . For example, the UE may receive control signaling that configures multiple potential TCI states for the UE and  indicates whether each TCI state is configured with an uplink power control parameter configuration or not (e.g., whether each TCI state supports uplink pathloss offset indication or whether the pathloss offset is enabled for each TCI state) . In such cases, the UE may apply the power control parameter to the TCI states that are indicated in the uplink power control message 400 and that are configured for uplink power control via the previous control message when the UE calculates uplink transmit power (s) for the uplink TCI states.
Additionally, or alternatively, in some examples, whether the power control parameter indicated via the set of reserved bits 405-b is to be applied to a given activated TCI state may be indicated by a respective reserved bit 405-c in the corresponding uplink TCI state activation field 410. For example, if an uplink TCI state is indicated via a TCI state activation field 410, such as the TCI state activation field 410-b, the ID of the uplink TCI state may not occupy all of the bits in the TCI state activation field 410-b, and there may be one or more reserved bits 405-c. The reserved bits 405-c in each TCI state activation field 410 that activates an uplink TCI state may thereby be used to indicate whether the power control parameter indicated via the set of reserved bits 405-b is applied to the corresponding TCI state. Additionally, or alternatively, the reserved bit (s) 405-c in the TCI state activation fields 410 may be reused to indicate a portion of the uplink power control parameter if, for example, the set of reserved bits 405-b is not large enough.
The power control parameter may be, for example, an uplink pathloss offset, an uplink pathloss scaling factor, or some other type of parameter for uplink power control. In some examples, a quantity of bits used to indicate a pathloss offset may be greater than a quantity of bits to indicate a pathloss scaling factor. As such, all or a portion of the reserved bits 405-b may be used to convey the value of the uplink power control parameter, depending on a value and type of the power control parameter.
The uplink power control message 400 may thereby be utilized to indicate a power control parameter for multiple TCI states across multiple CCs. A set of CCs to which the power control parameter applies may be configured via a CC list. In some examples, a set of CCs may be configured for TCI state activation. For example, a TCI state activation MAC-CE may indicate TCI states that are activated across the set of CCs. The set of CCs for TCI state activation may be used for power control parameter  indications. In this example, if the uplink power control message 400 indicates, via the reserved bits 405-b, a single power control parameter applicable to multiple TCI state IDs in a CC (e.g., power control parameter is indicated for one CC in a set of CCs) , the power control parameter may be applied to the same set of TCI state IDs across all CCs of the set of CCs. If the uplink power control message 400 indicates, via the reserved bits 405-b, multiple power control parameters for a set of TCI state IDs in a single CC, with each power control parameter corresponding to a single uplink TCI state ID, the power control parameters may be applied to the same TCI state IDs on all CCs across the set of CCs. That is, the power control parameter-to-TCI state ID mapping indicated via the uplink power control message 400 may be for a single CC, and may be applied across all CCs in the set of CCs configured for both TCI state activation and uplink power control parameter indication.
Additionally, or alternatively, a separate set of CCs for power control parameter indication may be supported and may be different than the set of CCs for TCI state activation. In this example, if the uplink power control message 400 indicates, via the reserved bits 405-b, a single power control parameter applicable to multiple TCI state IDs in a CC (e.g., power control parameter is indicated for one CC in a set of CCs) , the power control parameter may be applied to the same set of TCI state IDs across all CCs of the set of CCs. If the uplink power control message 400 indicates, via the reserved bits 405-b, multiple power control parameters for a set of TCI state IDs in a single CC, with each power control parameter corresponding to a single uplink TCI state ID, the power control parameters may be applied to the same TCI state IDs on all CCs across the set of CCs when the same TCI state ID for the one or more CCs are activated with corresponding power control updates enabled. That is, the power control parameter-to-TCI state ID mapping indicated via the uplink power control message 400 may be for a single CC, and may be applied across all CCs in the set of CCs configured for both TCI state activation and uplink power control parameter indication.
FIG. 5 shows an example of an uplink power control message 500 that supports power control information for multiple transmission configuration indication states in accordance with one or more aspects of the present disclosure. The uplink power control message 500 may implement or be implemented by aspects of the wireless communications system 100, the network architecture 200, and the uplink  dense deployment 300, as described with reference to FIGs. 1–3. For example, the uplink power control message 500 represents an example format or configuration of a single control message that is operable to convey uplink power control information for multiple TCI states over one or more CCs.
The uplink power control message 500 illustrated in FIG. 5 may be a MAC-CE in this example. Although described with reference to a MAC-CE, it is to be understood that any other type of message may be used in a similar manner to indicate uplink power control information for multiple TCI states. In the example illustrated in FIG. 5, the uplink power control message 500 may also be operable to convey TCI state activation information. For example, the uplink power control message 500 may include one or more TCI state activation fields 510 (e.g., TCI state activation fields 510-a, 510-b, through 510-n) that may include one or more bits to indicate an ID of a corresponding TCI state to be activated for the UE. The uplink power control message 500 may thereby represent an example of a TCI state activation MAC-CE, in some examples. As described with reference to FIG. 1, the TCI state activation MAC-CE may be operable to active up to a threshold quantity of TCI states (e.g., eight, or some other quantity) from among a set of multiple TCI states indicated via a previous RRC configuration for the UE. The TCI states may be uplink TCI states, downlink TCI states, or both.
The uplink power control message 500 may include a serving cell ID field, which may indicate a serving cell ID for which the uplink power control message 500 applies. If the indicated serving cell is configured as part of a simultaneous TCI update list (e.g., simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3 or simultaneousU-TCI-UpdateList4) , the uplink power control message 500 may apply to all serving cells that are included in the set of CCs in the simultaneous TCI update list. The uplink power control message 500 may include an uplink BWP ID field and a downlink BWP ID field, which may indicate a BWP that the message applies for a downlink or uplink TCI state, respectively. The uplink power control message 500 may include one or more P fields 515 that indicate whether each TCI state activation field 510 (e.g., TCI codepoint) indicates multiple TCI states or a single TCI state.
The uplink power control message 500 may include one or more downlink/uplink fields 520 that indicate whether each TCI state activation field 510 is for an uplink TCI state or a downlink or joint TCI state. In some examples, the uplink power control message 500 may include multiple sets of information (e.g., octets, or sets of eight bits) . Each row illustrated in FIG. 4 may represent a set. In such cases, the downlink/uplink field 520 in a given set may indicate whether the TCI state ID that is in the same set is for an uplink TCI state or for a downlink or joint TCI state. If the downlink/uplink field 520 is set to a first value (e.g., ‘1’ ) , the field may indicate that the TCI state ID is used for downlink. The downlink TCI state ID may be indicated via some quantity of bits, such as seven bits, in some examples. If the downlink/uplink field 520 is set to a second value (e.g., ‘0’ ) , the field may indicate that the TCI state ID is used for uplink. The uplink TCI state ID may be indicated via some quantity of bits, such as six bits, in some examples, such that one or more remaining or extra bits may be unused or repurposed. For example, the one or more remaining bits may be used as an extra reserved bit 505-b to indicate power control information, as described herein.
Although an uplink TCI state activation MAC-CE is illustrated in FIG. 5, it is to be understood that the network may convey uplink power control information for multiple TCI states via a separate MAC-CE or other type of message, in some examples. For example, a separate MAC-CE different than the unified TCI state activation MAC-CE may be used to update power control information (e.g., pathloss offset, scaling factor, or the like) for multiple TCI states. In such cases, if the uplink power control message 500 is a separate MAC-CE, the uplink power control message 500 may not include the TCI state activation fields 510, among other types of fields. In such cases, the network may indicate the power control parameter and other uplink power control information via one or more of the power control parameter fields 525 in a separate MAC-CE.
Techniques described herein provide for a network entity to convey, via one or more power control parameter fields 525 in the uplink power control message 500, information that indicates one or more power control parameters for the multiple TCI states. For example, the uplink power control message 500 may include one or more power control parameter fields 525 (e.g., power control parameter fields 525-a through 525-m) . The power control parameter fields 525 may represent additional fields (e.g.,  bits) appended to or otherwise included in the uplink power control message 500 and configured to convey information indicative of one or more power control parameters for multiple TCI states.
In some examples described herein, the uplink power control message 500 may include a single power control parameter field 525-a. That is, although the power control parameter fields 525-b through 525-m are illustrated in FIG. 5, in some examples, the uplink power control message 500 may not include these fields. The single power control parameter field 525-a in the uplink power control message 500 may include one or more bits configured to convey a value of a power control parameter for multiple TCI states (e.g., power control parameter 1) . In some examples, a reserved bit 505-a in the uplink power control message 500 may be used to indicate whether the power control parameter field 525-a is present or not.
If the power control parameter field 525-a is included, the power control parameter indicated via the power control parameter field 525-a may be applied to each of the activated uplink TCI states. That is, a receiving UE may apply the power control parameter to each uplink TCI state ID that is included in the uplink power control message 500 when the UE calculates uplink transmit power (s) for the uplink TCI states. The activated uplink TCI states may be indicated via the TCI state activation fields 510 in the uplink power control message 500 or in TCI state activation fields in a separate message (e.g., an uplink TCI state activation message) , if the uplink power control message 500 is separate from a TCI state activation message. Additionally, or alternatively, the power control parameter indicated via the power control parameter field 525-a may be applied to each of the activated uplink TCI states that are also associated with an uplink power control parameter configuration (e.g., enabled with pathloss offset by RRC) . For example, the UE may receive control signaling that configures multiple potential TCI states for the UE and indicates whether each TCI state is configured with an uplink power control parameter configuration or not (e.g., whether each TCI state supports uplink pathloss offset indication or whether the pathloss offset is enabled for each TCI state) . In such cases, the UE may apply the power control parameter to the TCI states that are indicated in the uplink power control message 500 and that are configured for uplink power control via the previous control message when the UE calculates uplink transmit power (s) for the uplink TCI states.
Additionally, or alternatively, in some examples, whether the power control parameter indicated via the power control parameter field 525-a is to be applied to a given activated TCI state may be indicated by a respective reserved bit 505-b in the corresponding uplink TCI state activation field 510. For example, if an uplink TCI state is indicated via a TCI state activation field 510, such as the TCI state activation field 510-b, the ID of the uplink TCI state may not occupy all of the bits in the TCI state activation field 510-b, and there may be one or more reserved bits 505-b. The reserved bits 505-b in each TCI state activation field 510 that activates an uplink TCI state may thereby be used to indicate whether the power control parameter indicated via the power control parameter field 525-a is present for the corresponding TCI state. Additionally, or alternatively, the reserved bit (s) 505-b in the TCI state activation fields 510 may be reused to indicate a portion of the uplink power control parameter if, for example, the power control parameter field 525-a is not large enough.
In some examples, the uplink power control message 500 may include multiple power control parameter fields 525, such as power control parameter fields 525-a, 525-b, through 525-m. A quantity of power control parameter fields 525, M, may be the same as a quantity of activated uplink TCI states in the uplink power control message 500, in some examples. For example, the quantity of TCI state activation fields 510 in the uplink power control message 500 may be equal to N and may include uplink TCI states, downlink TCI states, or any combination thereof. In this example, the quantity of uplink TCI states in the uplink power control message 500 may be equal to M, which may also correspond to a quantity of power control parameter fields 525 that are appended to or otherwise included in the uplink power control message 500. If the uplink power control message 500 includes the same quantity of power control parameter fields 525 as uplink TCI states, at least one reserved bit 505-a in the uplink power control message 500 may be used to indicate whether the multiple power control parameter fields 525 are present or not. Each power control parameter field 525 may indicate a respective power control parameter, which may be the same parameter or one or more different parameters. A receiving UE may apply the power control parameter indicated via each power control parameter field 525 to a respective TCI state from among the multiple uplink TCI states in the uplink power control message 500.
In some other examples, a quantity of power control parameter fields 525 that are included in the uplink power control message 500 may be the same as a quantity of activated uplink TCI states in the uplink power control message 500 that are also associated with (e.g., configured for) an uplink power control parameter configuration via a previous control message (e.g., an RRC message) . If the uplink power control message 500 includes the same quantity of power control parameter fields 525 as uplink TCI states that are activated and configured for uplink power control, at least one reserved bit 505-a in the uplink power control message 500 may be used to indicate whether the multiple power control parameter fields 525 are present or not. Each power control parameter field 525 may indicate a respective power control parameter, which may be the same parameter or one or more different parameters. A receiving UE may apply the power control parameter indicated via each power control parameter field 525 to a respective TCI state from among the multiple uplink TCI states in the uplink power control message 500 that are also configured for uplink power control.
In some other examples, a quantity of power control parameter fields 525 included in the uplink power control message 500 may be indicated. For example, for each activated uplink TCI state in the uplink power control message 500, a reserved bit 505-b (e.g., a most significant bit) in the corresponding uplink TCI state activation field 510 may be used to indicate whether the uplink power control message 500 includes a power control parameter field 525 for that uplink TCI state or not. For example, the reserved bit 505-b may indicate whether the uplink power control message 500 includes a power control parameter field 525 for the TCI state indicated via the TCI state activation field 510-b. If the reserved bit 505-b is set to a first value, there may not be a corresponding power control parameter field 525. If the reserved bit 505-b is set to a second value, the bit may indicate that the power control parameter field 525-a, for example, is associated with (e.g., indicates power control information for) the TCI state indicated via the TCI state activation field 510-b. In this case, the network may refrain from indicating whether power control update is enabled or not per TCI state, in some examples.
Additionally, or alternatively, the uplink power control message 500 may include a power control parameter field 525 for a given activated uplink TCI state indicated via the uplink power control message 500 if the corresponding TCI state is  enabled for power control updates via a previous control message (e.g., an RRC message) .
In some examples, if the uplink power control message 500 is a MAC-CE that is separate than a TCI state activation MAC-CE, the uplink power control message 500 may not include the TCI state activation fields 510. In such cases, the uplink power control message 500 may include multiple power control parameter fields 525 and an uplink TCI state ID may be associated with or included in each of the multiple power control parameter fields. The uplink TCI state ID may indicate that the power control parameter indicated in the power control parameter field 525 is to applied to the corresponding uplink TCI state. Additionally, or alternatively, the MAC-CE may include multiple TCI state fields each corresponding to a respective power control parameter field 525 to indicate the TCI state ID associated with each power control parameter field 525. Such power control parameter fields 525 including TCI state IDs may be included in the uplink power control message 500 regardless of whether power control is enabled by an RRC configuration. Additionally, or alternatively, the power control parameter fields 525 including TCI state IDs may be included in the uplink power control message 500 if power control is enabled by RRC for a given uplink TCI state.
The power control parameter (s) indicated via the power control parameter fields 525 in the uplink power control message 500 may be, for example, an uplink pathloss offset, an uplink pathloss scaling factor, or some other type of parameter for uplink power control. In some examples, an uplink pathloss offset may be indicated via a greater quantity of bits than an uplink pathloss scaling factor. As such, the power control parameter fields 525 may be smaller in size for uplink pathloss scaling factor indications, or one or more bits in the power control parameter fields 525 used to indicate a scaling factor may be repurposed, or both.
In some examples, the uplink power control message 500 may indicate a reference parameter. For example, the one or more power control parameters indicated via the uplink power control message 500 may include an offset or a scaling factor relative to some reference value. The reference value may be a downlink pathloss value (e.g., a previously used/measured value) or a nominal value (e.g., a nominal pathloss) . The uplink power control message 500 may indicate whether each of the power control  parameter fields 525 indicates a power control parameter with respect to a measured downlink value or a nominal value in the same message. In some examples, the indication may be included in each power control parameter field 525. Additionally, or alternatively, a common field or multiple separate fields may be included in the uplink power control message 500 to indicate which reference parameter to use for the multiple power control parameters.
The uplink power control message 500 may thereby be utilized to indicate a power control parameter for multiple TCI states across multiple CCs. A set of CCs to which the power control parameter applies may be configured via a CC list. In some examples, a set of CCs may be configured for TCI state activation. For example, a TCI state activation MAC-CE may indicate TCI states that are activated across the set of CCs. The set of CCs for TCI state activation may be used for power control parameter indications. In this example, if the uplink power control message 500 indicates, via one or more power control parameter fields 525, a single power control parameter applicable to multiple TCI state IDs in a CC (e.g., power control parameter is indicated for one CC in a set of CCs) , the power control parameter may be applied to the same set of TCI state IDs across all CCs of the set of CCs. If the uplink power control message 500 indicates, via one or more power control parameter fields 525, multiple power control parameters for a set of TCI state IDs in a single CC, with each power control parameter corresponding to a single uplink TCI state ID, the power control parameters may be applied to the same TCI state IDs on all CCs across the set of CCs. That is, the power control parameter-to-TCI state ID mapping indicated via the uplink power control message 500 may be for a single CC, and may be applied across all CCs in the set of CCs configured for both TCI state activation and uplink power control parameter indication.
Additionally, or alternatively, a separate set of CCs for power control parameter indication may be supported and may be different than the set of CCs for TCI state activation. In this example, if the uplink power control message 500 indicates, via one or more power control parameter fields 525, a single power control parameter applicable to multiple TCI state IDs in a CC (e.g., power control parameter is indicated for one CC in a set of CCs) , the power control parameter may be applied to the same set of TCI state IDs across all CCs of the set of CCs. If the uplink power control message  500 indicates, via one or more power control parameter fields 525, multiple power control parameters for a set of TCI state IDs in a single CC, with each power control parameter corresponding to a single uplink TCI state ID, the power control parameters may be applied to the same TCI state IDs on all CCs across the set of CCs when the same TCI state ID for the one or more CCs are activated with corresponding power control updates enabled. That is, the power control parameter-to-TCI state ID mapping indicated via the uplink power control message 500 may be for a single CC, and may be applied across all CCs in the set of CCs configured for both TCI state activation and uplink power control parameter indication.
FIG. 6 shows an example of a signaling sequence 600 that supports power control information for multiple transmission configuration indication states in accordance with one or more aspects of the present disclosure. The signaling sequence 600 may implement or be implemented by aspects of the wireless communications system 100, the network architecture 200, the uplink dense deployment 300, or the uplink power control messages 400 and 500. For example, the signaling sequence 600 illustrates communication between a UE 115 and a network entity 105 (via a downlink transmission point 305 and an uplink reception point 310) , which may be examples of corresponding devices as described herein. The signaling sequence 600 illustrates an example of uplink power control in accordance with signaling from the network entity 105 that indicates a power control parameter for multiple TCI states across one or more CCs.
In this example, the network entity 105 may use both a unified TCI state activation MAC-CE 625 and a separate MAC-CE 630 to indicate or update a power control parameter for multiple TCI states. For example, the unified TCI state activation MAC-CE 625 may indicate an initial power control parameter for one or more TCI states. The UE 115 may calculate an initial power value based on the initial power control parameter with reference to a measured downlink power control parameter (e.g., a measured downlink pathloss) . The UE 115 may subsequently receive a separate MAC-CE 630 that indicates an update or change in the power control parameter. In some examples, the unified TCI state activation MAC-CE 625 may be received before the separate MAC-CE 630.
The power control parameter may be described with reference to a pathloss offset in the example of FIG. 6. However, it is to be understood that the power control parameter may additionally, or alternatively, include a pathloss scaling factor, or some other parameter or value associated with uplink power control.
At 605, the UE 115 and the network entity 105 may exchange downlink communications, which may be associated with a measured downlink pathloss (denoted as PL_d in the example of FIG. 6) of 100 dB and a first uplink pathloss (denoted as PL_u in the example of FIG. 6) of 40 dB. In such examples, an initially indicated pathloss offset 645 (PL Offset 0) may be set to 60 dB to indicate an offset from the measured downlink pathloss to the target uplink pathloss. The network entity 105 may transmit a unified TCI state activation MAC-CE 625 to the UE 115 to indicate the initially indicated pathloss offset 645. The pathloss offset 645 may be associated with a first TCI state. The pathloss offset 645 may reconcile a difference between the measured downlink pathloss of 100 dB and the uplink pathloss of 40 dB.
At 610, the unified TCI state activation MAC-CE 625 may be applied. In accordance with the initially indicated pathloss offset 645 (e.g., PLO0) , the UE 115 may calculate (e.g., obtain) an uplink pathloss associated with the first TCI state as PLu, 1=PLd, 1-PLO0=40 dB. By calculating the uplink pathloss PLu, 1, the UE 115 may transmit an uplink signal 635 using a first TCI state and a first transmit power. For example, the UE 115 may calculate the first transmit power for the first TCI state based on the uplink pathloss and one or more other parameters.
As described herein, the unified TCI state activation MAC-CE 625 may indicate the pathloss offset 645 for the first TCI state and one or more other TCI states. For example, the unified TCI state activation MAC-CE 625 may include one or more reserved bits or power control parameter fields configured to indicate the pathloss offset 645. The UE 115 may determine that the pathloss offset 645 is to be applied to the first TCI state based on whether the first TCI state is activated, is configured for uplink power control, based on one or more bits or fields in the unified TCI state activation MAC-CE 625, or any combination thereof, as described in further detail elsewhere herein, including with reference to FIGs. 4 and 5.
At 615, there may be a pathloss change (e.g., in accordance with movement by the UE 115 or other network or environmental conditions changing) according to which the uplink pathloss may change to 50 dB. In accordance with such a change in uplink pathloss, the network entity 105 may transmit a separate MAC-CE 630 including power control information that indicates a second pathloss offset 650 (e.g., a power control parameter) . In some examples, the second pathloss offset 650 may be a pathloss offset referenced with respect to a nominal pathloss. The nominal pathloss may be one of an initial uplink pathloss, a previous uplink pathloss (e.g., PLU, PLUL1) , a previous downlink pathloss, an initial downlink pathloss (e.g., PLD, PLDL1) , or any combination thereof. In some other examples, the second pathloss offset 650 indicated via the MAC-CE 630 may be a pathloss offset with respect to a measured downlink pathloss or a nominal pathloss. Whether the second pathloss offset 650 is with respect to the nominal pathloss or the measured downlink pathloss may be indicated via one or more fields in the MAC-CE 630.
In some examples, multiple pathloss offsets, including the second pathloss offset 650, may be indicated via the MAC-CE 630. In such cases, a single field in the MAC-CE 630 may be used to indicate whether all of the pathloss offsets are with respect to the corresponding measured downlink pathloss or the nominal pathloss. Additionally, or alternatively, multiple fields may be included in the MAC-CE 630 and may each correspond to a respective pathloss offset update field. These fields may be used to indicate whether the respective pathloss offset update field is with respect to the measured downlink pathloss or nominal pathloss. Each pathloss offset may be associated with a respective TCI state and the reference parameter for each pathloss offset may also be associated with the same respective TCI state, in some examples.
In the example illustrated in FIG. 6, the MAC-CE 630 may indicate the second pathloss offset 650 for the first TCI state relative to a nominal pathloss, which may be the previous uplink pathloss (e.g., PLUL1) . In some examples, the MAC-CE 630 may include a field that indicates the second pathloss offset 650 is relative to the nominal pathloss.
At 620, the MAC-CE 630 may be applied. The UE 115 may calculate a second pathloss based on the second pathloss offset 650 indicated via the MAC-CE 630  and the nominal pathloss offset (e.g., PLOUL1) , the UE 115 may calculate (e.g., obtain) an uplink pathloss as PLUL2=PLUL1+PLO1=50 dB. By calculating the uplink pathloss PLUL2, the UE 115 may transmit a second uplink signal 640 using the first TCI state and a second transmit power. For example, the UE 115 may calculate the second transmit power for the first TCI state based on the uplink pathloss PLUL2 and one or more other parameters. The transmit power used by the UE 115 to transmit the second uplink signal 640 may be different than the transmit power used by the UE 115 to transmit the uplink signal 635 based on the differing uplink pathloss values.
The network entity 105 may thereby transmit a single message that indicates power control information for multiple TCI states. In this example, the single message (e.g., the MAC-CE 630) may indicate the power control information relative to previous information indicated via a previous message (e.g., the unified TCI state activation MAC-CE 625) . The uplink power control information may be a pathloss offset, a pathloss scaling factor, or some other power control parameter that can be used by the UE 115 to calculate a transmit power.
FIG. 7 shows an example of a process flow 700 that supports power control information for multiple transmission configuration indication states in accordance with one or more aspects of the present disclosure. The process flow 700 may implement or be implemented by aspects of the wireless communications system 100, the network architecture 200, the uplink dense deployment 300, the uplink power control messages 400 and 500, or the signaling sequence 600. For example, the process flow 700 illustrates communications between a network entity 105 and a UE 115, which may represent aspects of corresponding devices as described with reference to FIGs. 1–6. In some aspects, the network entity 105 may transmit, via a single message, uplink power control information for multiple TCI states supported by the UE 115.
In the following description of the process flow 700, the operations between the network entity 105 and the UE 115 may be performed in different orders or at different times. Some operations may also be left out of the process flow 700, or other operations may be added. Although the network entity 105 and the UE 115 are shown performing the operations of the process flow 700, some aspects of some operations may also be performed by one or more other wireless devices.
At 705, the network entity 105 may transmit, to the UE 115, a control message that indicates multiple TCI states for uplink communications by the UE 115 via one or more CCs. The control message may be an RRC message, in some examples. For example, the network entity may transmit an RRC configuration that indicates the multiple potential TCI states supported by the UE 115. In some examples, the control message may indicate whether an uplink power control parameter configuration is enabled or disabled for the multiple TCI states. For example, the control message may indicate, for each TCI state, whether the TCI state supports power control updates (e.g., whether pathloss offset is enabled) .
At 710, the network entity 105 may transmit, to the UE 115, a message including uplink power control information for multiple TCI states supported by the UE 115 (e.g., at least two TCI states) . The uplink power control information may indicate a power control parameter for uplink pathloss calculation for the one or more CCs. The power control parameter may correspond to one or more TCI states from among the multiple TCI states indicated via the control message. The message may be a MAC-CE or some other type of message. In some examples, the message may represent an example of the uplink power control messages 400 and 500, or the MAC-CE 630 as described with reference to FIGs. 4–6. In some examples, the message may include one or more bits or fields that convey the power control parameter and information that indicates which TCI states the parameter applies to, a reference parameter, or any combination thereof.
At 715, in some examples, the UE 115 may determine (e.g., calculate) one or more transmit powers for the one or more TCI states based on the power control parameter. For example, the UE 115 may input the power control parameter into an equation or algorithm for calculating uplink transmit power for a given TCI state, along with one or more other parameters for uplink transmit power calculation. In some examples, each TCI state may be associated with a respective equation or set of parameters. As such, the transmit power for each TCI state may be the same or different.
At 720, the UE 115 may transmit, to the network entity 105 via one or more CCs, the uplink communications using the one or more transmit powers calculated at 715. The UE 115 may transmit the uplink communications according to the one or more  TCI states and the one or more transmit powers that are based on the power control parameter indicated at 710.
The network entity 105 may thereby transmit, via a single message, uplink power control information applicable to multiple TCI states of the UE 115. The UE 115 may utilize the information to calculate uplink transmit power (s) for uplink communications, which may improve throughput and reliability of the wireless communications while reducing overhead as compared with systems in which the uplink power control information may be indicated per TCI state.
FIG. 8 shows a block diagram 800 of a device 805 that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure. The device 805 may be an example of aspects of a UE 115 as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communications manager 820. The device 805, or one or more components of the device 805 (e.g., the receiver 810, the transmitter 815, the communications manager 820) , may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .
The receiver 810 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to power control information for multiple TCI states) . Information may be passed on to other components of the device 805. The receiver 810 may utilize a single antenna or a set of multiple antennas.
The transmitter 815 may provide a means for transmitting signals generated by other components of the device 805. For example, the transmitter 815 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to power control information for multiple TCI states) . In some examples, the transmitter 815 may be co-located with a receiver 810 in a  transceiver module. The transmitter 815 may utilize a single antenna or a set of multiple antennas.
The communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be examples of means for performing various aspects of power control information for multiple TCI states as described herein. For example, the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be capable of performing one or more of the functions described herein.
In some examples, the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) . The hardware may include at least one of a processor, a digital signal processor (DSP) , a central processing unit (CPU) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory) .
Additionally, or alternatively, the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code) . If implemented in code executed by at least one processor, the functions of the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure) .
In some examples, the communications manager 820 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 810, the transmitter 815, or both. For example, the communications manager 820 may receive information from the receiver 810, send information to the transmitter 815, or be integrated in combination with the receiver 810, the transmitter 815, or both to obtain information, output information, or perform various other operations as described herein.
Additionally, or alternatively, the communications manager 820 may support wireless communication in accordance with examples as disclosed herein. For example, the communications manager 820 is capable of, configured to, or operable to support a means for receiving a control message that indicates a set of multiple TCI states for uplink communications by the UE via one or more CCs. The communications manager 820 is capable of, configured to, or operable to support a means for receiving a message including uplink power control information that indicates a power control parameter for uplink pathloss calculation for the one or more CCs, the power control parameter corresponding to one or more TCI states from among the set of multiple TCI states. The communications manager 820 is capable of, configured to, or operable to support a means for transmitting, via the one or more CCs in accordance with the one or more TCI states, the uplink communications using one or more transmit powers that are based on the power control parameter.
By including or configuring the communications manager 820 in accordance with examples as described herein, the device 805 (e.g., at least one processor controlling or otherwise coupled with the receiver 810, the transmitter 815, the communications manager 820, or a combination thereof) may support techniques for reduced processing, reduced power consumption, and more efficient utilization of communication resources, among other examples.
FIG. 9 shows a block diagram 900 of a device 905 that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure. The device 905 may be an example of aspects of a device 805 or a UE 115 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communications manager 920. The device 905, or one or more components of the device 905 (e.g., the receiver 910, the transmitter 915, the communications  manager 920) , may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .
The receiver 910 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to power control information for multiple TCI states) . Information may be passed on to other components of the device 905. The receiver 910 may utilize a single antenna or a set of multiple antennas.
The transmitter 915 may provide a means for transmitting signals generated by other components of the device 905. For example, the transmitter 915 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to power control information for multiple TCI states) . In some examples, the transmitter 915 may be co-located with a receiver 910 in a transceiver module. The transmitter 915 may utilize a single antenna or a set of multiple antennas.
The device 905, or various components thereof, may be an example of means for performing various aspects of power control information for multiple TCI states as described herein. For example, the communications manager 920 may include a TCI state component 925, an uplink power control component 930, a transmit power component 935, or any combination thereof. The communications manager 920 may be an example of aspects of a communications manager 820 as described herein. In some examples, the communications manager 920, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 910, the transmitter 915, or both. For example, the communications manager 920 may receive information from the receiver 910, send information to the transmitter 915, or be integrated in combination with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.
The communications manager 920 may support wireless communication in accordance with examples as disclosed herein. The TCI state component 925 is capable of, configured to, or operable to support a means for receiving a control message that indicates a set of multiple TCI states for uplink communications by the UE via one or more CCs. The uplink power control component 930 is capable of, configured to, or operable to support a means for receiving a message including uplink power control information that indicates a power control parameter for uplink pathloss calculation for the one or more CCs, the power control parameter corresponding to one or more TCI states from among the set of multiple TCI states. The transmit power component 935 is capable of, configured to, or operable to support a means for transmitting, via the one or more CCs in accordance with the one or more TCI states, the uplink communications using one or more transmit powers that are based on the power control parameter.
FIG. 10 shows a block diagram 1000 of a communications manager 1020 that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure. The communications manager 1020 may be an example of aspects of a communications manager 820, a communications manager 920, or both, as described herein. The communications manager 1020, or various components thereof, may be an example of means for performing various aspects of power control information for multiple TCI states as described herein. For example, the communications manager 1020 may include a TCI state component 1025, an uplink power control component 1030, a transmit power component 1035, a MAC-CE component 1040, a frequency configuration component 1045, a pathloss component 1050, a power control parameter component 1055, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories) , may communicate, directly or indirectly, with one another (e.g., via one or more buses) .
Additionally, or alternatively, the communications manager 1020 may support wireless communication in accordance with examples as disclosed herein. The TCI state component 1025 is capable of, configured to, or operable to support a means for receiving a control message that indicates a set of multiple TCI states for uplink communications by the UE via one or more CCs. The uplink power control component 1030 is capable of, configured to, or operable to support a means for receiving a  message including uplink power control information that indicates a power control parameter for uplink pathloss calculation for the one or more CCs, the power control parameter corresponding to one or more TCI states from among the set of multiple TCI states. The transmit power component 1035 is capable of, configured to, or operable to support a means for transmitting, via the one or more CCs in accordance with the one or more TCI states, the uplink communications using one or more transmit powers that are based on the power control parameter.
In some examples, to support receiving the message, the MAC-CE component 1040 is capable of, configured to, or operable to support a means for receiving a MAC-CE that indicates the power control parameter corresponding to the one or more TCI states.
In some examples, the power control parameter component 1055 is capable of, configured to, or operable to support a means for receiving the power control parameter via a set of one or more reserved bits within the MAC-CE, an uplink power control field within the MAC-CE, or both.
In some examples, the power control parameter component 1055 is capable of, configured to, or operable to support a means for receiving, via a set of multiple uplink power control fields within the MAC-CE, the power control parameter.
In some examples, a quantity of the set of multiple uplink power control fields is based on a quantity of TCI states from among the set of multiple TCI states that are activated for the uplink communications by the UE. In some examples, the quantity of the set of multiple uplink power control fields is based on the quantity of TCI states from among the set of multiple TCI states that are activated for the uplink communications by the UE and that are associated with an uplink power control parameter configuration.
In some examples, the TCI state component 1025 is capable of, configured to, or operable to support a means for receiving, via the MAC-CE, one or more fields that indicate one or more TCI states from among the set of multiple TCI states that are activated for the uplink communications by the UE, where each field of the one or more fields indicates a respective TCI state and indicates whether the set of multiple uplink  power control fields includes a respective power uplink control field that corresponds to the respective TCI state.
In some examples, the TCI state component 1025 is capable of, configured to, or operable to support a means for receiving, via a set of multiple TCI state fields within the MAC-CE, a respective ID associated with a respective TCI state to which the power control parameter included in the uplink power control field applies.
In some examples, the transmit power component 1035 is capable of, configured to, or operable to support a means for determining the one or more transmit powers for the one or more TCI states using the power control parameter based on the one or more TCI states being activated for the uplink communications by the UE. In some examples, the transmit power component 1035 is capable of, configured to, or operable to support a means for determining the one or more transmit powers for the one or more TCI states using the power control parameter based on the one or more TCI states being activated for the uplink communications by the UE and further based on the one or more TCI states being associated with an uplink power control parameter configuration. In some examples, the transmit power component 1035 is capable of, configured to, or operable to support a means for determining the one or more transmit powers for the one or more TCI states using the power control parameter based on at least two bits in the MAC-CE that indicate the power control parameter applies to the one or more TCI states.
In some examples, to support receiving the MAC-CE, the MAC-CE component 1040 is capable of, configured to, or operable to support a means for receiving a unified TCI state activation MAC-CE that indicates one or more TCI states from among the set of multiple TCI states that are activated for the uplink communications by the UE.
In some examples, the MAC-CE component 1040 is capable of, configured to, or operable to support a means for receiving a unified TCI state activation MAC-CE, where the unified TCI state activation MAC-CE indicates one or more TCI states from among the set of multiple TCI states that are activated for the uplink communications by the UE.
In some examples, the power control parameter includes a pathloss offset. In some examples, the MAC-CE includes at least one field that indicates whether the pathloss offset is with respect to a nominal pathloss or a measured pathloss.
In some examples, the uplink power control component 1030 is capable of, configured to, or operable to support a means for receiving, after transmitting the uplink communications using the one or more transmit powers, a second message including second uplink power control information, where the message includes a unified TCI state activation MAC-CE that indicates one or more TCI states from among the set of multiple TCI states that are activated for the uplink communications by the UE, and where the second message includes a MAC-CE different than the unified TCI state activation MAC-CE.
In some examples, the power control parameter indicated via the message includes a reference to a measured parameter. In some examples, a second power control parameter indicated via the second message includes a second reference to a nominal parameter, a measured parameter, or any combination thereof, where the nominal parameter includes one of an initial parameter, a previous parameter, a previous measured parameter or an initial measured parameter. In some examples, the second message includes one or more fields that indicate whether the second power control parameter indicated via the second message references the nominal parameter or the measured parameter.
In some examples, the frequency configuration component 1045 is capable of, configured to, or operable to support a means for receiving an indication of a set of CCs for TCI state activation, where the power control parameter corresponds to the one or more CCs that are the same as the set of CCs for TCI state activation. In some examples, the transmit power component 1035 is capable of, configured to, or operable to support a means for applying the power control parameter to the one or more TCI states across the set of CCs.
In some examples, the frequency configuration component 1045 is capable of, configured to, or operable to support a means for receiving a first indication of a first set of CCs for TCI state activation. In some examples, the frequency configuration component 1045 is capable of, configured to, or operable to support a means for  receiving a second indication of a second set of CCs associated with uplink power control, where the power control parameter corresponds to the one or more CCs that are the same as the second set of CCs for uplink power control. In some examples, the transmit power component 1035 is capable of, configured to, or operable to support a means for applying the power control parameter to the one or more TCI states across the second set of CCs.
In some examples, the pathloss component 1050 is capable of, configured to, or operable to support a means for determining an uplink pathloss associated with the one or more TCI states based on the power control parameter and a reference pathloss value, where the power control parameter includes a pathloss offset value. In some examples, the transmit power component 1035 is capable of, configured to, or operable to support a means for determining the one or more transmit powers for the uplink communications according to the one or more TCI states based on the calculated uplink pathloss.
In some examples, the pathloss component 1050 is capable of, configured to, or operable to support a means for determining an uplink pathloss associated with the one or more TCI states based on the power control parameter and a reference pathloss value, where the power control parameter includes a pathloss scaling factor. In some examples, the transmit power component 1035 is capable of, configured to, or operable to support a means for determining the one or more transmit powers for the uplink communications according to the one or more TCI states based on the calculated uplink pathloss.
FIG. 11 shows a diagram of a system 1100 including a device 1105 that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure. The device 1105 may be an example of or include components of a device 805, a device 905, or a UE 115 as described herein. The device 1105 may communicate (e.g., wirelessly) with one or more other devices (e.g., network entities 105, UEs 115, or a combination thereof) . The device 1105 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 1120, an input/output (I/O) controller, such as an I/O controller 1110, a transceiver 1115, one or more antennas 1125, at least one memory 1130, code 1135, and at least one processor  1140. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1145) .
The I/O controller 1110 may manage input and output signals for the device 1105. The I/O controller 1110 may also manage peripherals not integrated into the device 1105. In some cases, the I/O controller 1110 may represent a physical connection or port to an external peripheral. In some cases, the I/O controller 1110 may utilize an operating system such as or another known operating system. Additionally, or alternatively, the I/O controller 1110 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I/O controller 1110 may be implemented as part of one or more processors, such as the 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.
In some cases, the device 1105 may include a single antenna. However, in some other cases, the device 1105 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1115 may communicate bi-directionally via the one or more antennas 1125 using wired or wireless links as described herein. For example, the transceiver 1115 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 1115 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 1125 for transmission, and to demodulate packets received from the one or more antennas 1125. The transceiver 1115, or the transceiver 1115 and one or more antennas 1125, may be an example of a transmitter 815, a transmitter 915, a receiver 810, a receiver 910, or any combination thereof or component thereof, as described herein.
The at least one memory 1130 may include random access memory (RAM) and read-only memory (ROM) . The at least one memory 1130 may store computer-readable, computer-executable, or processor-executable code, such as the code 1135. The code 1135 may include instructions that, when executed by the at least one processor 1140, cause the device 1105 to perform various functions described herein. The code 1135 may be stored in a non-transitory computer-readable medium such as  system memory or another type of memory. In some cases, the code 1135 may not be directly executable by the at least one processor 1140 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 1130 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
The at least one processor 1140 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more central processing units (CPUs) , one or more graphics processing units (GPUs) , one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs) ) , one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof) . In some cases, the at least one processor 1140 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the at least one processor 1140. The at least one processor 1140 may be configured to execute computer-readable instructions stored in a memory (e.g., the at least one memory 1130) to cause the device 1105 to perform various functions (e.g., functions or tasks supporting power control information for multiple TCI states) . For example, the device 1105 or a component of the device 1105 may include at least one processor 1140 and at least one memory 1130 coupled with or to the at least one processor 1140, the at least one processor 1140 and the at least one memory 1130 configured to perform various functions described herein. In some examples, the at least one processor 1140 may include multiple processors and the at least one memory 1130 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions described herein. In some examples, the at least one processor 1140 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 1140) and memory circuitry (which may include the at least one memory 1130) ) , or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set  of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 1140 or a processing system including the at least one processor 1140 may be configured to, configurable to, or operable to cause the device 1105 to perform one or more of the functions described herein. Further, as described herein, being “configured to, ” being “configurable to, ” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code 1135 (e.g., processor-executable code) stored in the at least one memory 1130 or otherwise, to perform one or more of the functions described herein.
Additionally, or alternatively, the communications manager 1120 may support wireless communication in accordance with examples as disclosed herein. For example, the communications manager 1120 is capable of, configured to, or operable to support a means for receiving a control message that indicates a set of multiple TCI states for uplink communications by the UE via one or more CCs. The communications manager 1120 is capable of, configured to, or operable to support a means for receiving a message including uplink power control information that indicates a power control parameter for uplink pathloss calculation for the one or more CCs, the power control parameter corresponding to one or more TCI states from among the set of multiple TCI states. The communications manager 1120 is capable of, configured to, or operable to support a means for transmitting, via the one or more CCs in accordance with the one or more TCI states, the uplink communications using one or more transmit powers that are based on the power control parameter.
By including or configuring the communications manager 1120 in accordance with examples as described herein, the device 1105 may support techniques for improved communication reliability, reduced latency, reduced power consumption, more efficient utilization of communication resources, and improved coordination between devices, among other examples.
In some examples, the communications manager 1120 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 1115, the one or more antennas 1125, or any combination thereof. Although the communications manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference  to the communications manager 1120 may be supported by or performed by the at least one processor 1140, the at least one memory 1130, the code 1135, or any combination thereof. For example, the code 1135 may include instructions executable by the at least one processor 1140 to cause the device 1105 to perform various aspects of power control information for multiple TCI states as described herein, or the at least one processor 1140 and the at least one memory 1130 may be otherwise configured to, individually or collectively, perform or support such operations.
FIG. 12 shows a block diagram 1200 of a device 1205 that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure. The device 1205 may be an example of aspects of a network entity 105 as described herein. The device 1205 may include a receiver 1210, a transmitter 1215, and a communications manager 1220. The device 1205, or one or more components of the device 1205 (e.g., the receiver 1210, the transmitter 1215, the communications manager 1220) , may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .
The receiver 1210 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) . Information may be passed on to other components of the device 1205. In some examples, the receiver 1210 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 1210 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
The transmitter 1215 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1205. For example, the transmitter 1215 may output information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g.,  control channels, data channels, information channels, channels associated with a protocol stack) . In some examples, the transmitter 1215 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 1215 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1215 and the receiver 1210 may be co-located in a transceiver, which may include or be coupled with a modem.
The communications manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may be examples of means for performing various aspects of power control information for multiple TCI states as described herein. For example, the communications manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may be capable of performing one or more of the functions described herein.
In some examples, the communications manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) . The hardware may include at least one of a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory) .
Additionally, or alternatively, the communications manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code) . If implemented in code executed by at least one processor, the functions of the communications manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may be performed by a general-purpose processor,  a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure) .
In some examples, the communications manager 1220 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1210, the transmitter 1215, or both. For example, the communications manager 1220 may receive information from the receiver 1210, send information to the transmitter 1215, or be integrated in combination with the receiver 1210, the transmitter 1215, or both to obtain information, output information, or perform various other operations as described herein.
Additionally, or alternatively, the communications manager 1220 may support wireless communication in accordance with examples as disclosed herein. For example, the communications manager 1220 is capable of, configured to, or operable to support a means for outputting a control message that indicates a set of multiple TCI states for uplink communications by a UE via one or more CCs. The communications manager 1220 is capable of, configured to, or operable to support a means for outputting a message including uplink power control information that indicates a power control parameter for uplink pathloss calculation for the one or more CCs, the power control parameter corresponding to one or more TCI states from among the set of multiple TCI states. The communications manager 1220 is capable of, configured to, or operable to support a means for obtaining, via the one or more CCs in accordance with the one or more TCI states, the uplink communications using one or more transmit powers based on the power control parameter.
By including or configuring the communications manager 1220 in accordance with examples as described herein, the device 1205 (e.g., at least one processor controlling or otherwise coupled with the receiver 1210, the transmitter 1215, the communications manager 1220, or a combination thereof) may support techniques for reduced processing, reduced power consumption, and more efficient utilization of communication resources, among other examples.
FIG. 13 shows a block diagram 1300 of a device 1305 that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure. The device 1305 may be an example of aspects of a device 1205 or a network entity 105 as described herein. The device 1305 may include a receiver 1310, a transmitter 1315, and a communications manager 1320. The device 1305, or one or more components of the device 1305 (e.g., the receiver 1310, the transmitter 1315, the communications manager 1320) , may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .
The receiver 1310 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) . Information may be passed on to other components of the device 1305. In some examples, the receiver 1310 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 1310 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
The transmitter 1315 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1305. For example, the transmitter 1315 may output information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) . In some examples, the transmitter 1315 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 1315 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1315 and the receiver 1310 may be co-located in a transceiver, which may include or be coupled with a modem.
The device 1305, or various components thereof, may be an example of means for performing various aspects of power control information for multiple TCI states as described herein. For example, the communications manager 1320 may include a TCI state component 1325, an uplink power control component 1330, a power control parameter component 1335, or any combination thereof. The communications manager 1320 may be an example of aspects of a communications manager 1220 as described herein. In some examples, the communications manager 1320, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1310, the transmitter 1315, or both. For example, the communications manager 1320 may receive information from the receiver 1310, send information to the transmitter 1315, or be integrated in combination with the receiver 1310, the transmitter 1315, or both to obtain information, output information, or perform various other operations as described herein.
The communications manager 1320 may support wireless communication in accordance with examples as disclosed herein. The TCI state component 1325 is capable of, configured to, or operable to support a means for outputting a control message that indicates a set of multiple TCI states for uplink communications by a UE via one or more CCs. The uplink power control component 1330 is capable of, configured to, or operable to support a means for outputting a message including uplink power control information that indicates a power control parameter for uplink pathloss calculation for the one or more CCs, the power control parameter corresponding to one or more TCI states from among the set of multiple TCI states. The power control parameter component 1335 is capable of, configured to, or operable to support a means for obtaining, via the one or more CCs in accordance with the one or more TCI states, the uplink communications using one or more transmit powers based on the power control parameter.
FIG. 14 shows a block diagram 1400 of a communications manager 1420 that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure. The communications manager 1420 may be an example of aspects of a communications manager 1220, a communications manager 1320, or both, as described herein. The communications manager 1420, or various  components thereof, may be an example of means for performing various aspects of power control information for multiple TCI states as described herein. For example, the communications manager 1420 may include a TCI state component 1425, an uplink power control component 1430, a power control parameter component 1435, a MAC-CE component 1440, a frequency configuration component 1445, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories) , may communicate, directly or indirectly, with one another (e.g., via one or more buses) . The communications may include communications within a protocol layer of a protocol stack, communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105) , or any combination thereof.
Additionally, or alternatively, the communications manager 1420 may support wireless communication in accordance with examples as disclosed herein. The TCI state component 1425 is capable of, configured to, or operable to support a means for outputting a control message that indicates a set of multiple TCI states for uplink communications by a UE via one or more CCs. The uplink power control component 1430 is capable of, configured to, or operable to support a means for outputting a message including uplink power control information that indicates a power control parameter for uplink pathloss calculation for the one or more CCs, the power control parameter corresponding to one or more TCI states from among the set of multiple TCI states. The power control parameter component 1435 is capable of, configured to, or operable to support a means for obtaining, via the one or more CCs in accordance with the one or more TCI states, the uplink communications using one or more transmit powers based on the power control parameter.
In some examples, to support outputting the message, the MAC-CE component 1440 is capable of, configured to, or operable to support a means for outputting a MAC-CE that indicates the power control parameter corresponding to the one or more TCI states.
In some examples, the power control parameter component 1435 is capable of, configured to, or operable to support a means for outputting the power control  parameter via a set of one or more reserved bits within the MAC-CE, an uplink power control field within the MAC-CE, or both.
In some examples, the power control parameter component 1435 is capable of, configured to, or operable to support a means for outputting, via a set of multiple uplink power control fields within the MAC-CE, the power control parameter.
In some examples, a quantity of the set of multiple uplink power control fields is based on a quantity of TCI states from among the set of multiple TCI states that are activated for the uplink communications by the UE. In some examples, the quantity of the set of multiple uplink power control fields is based on the quantity of TCI states from among the set of multiple TCI states that are activated for the uplink communications by the UE and that are associated with an uplink power control parameter configuration.
In some examples, the TCI state component 1425 is capable of, configured to, or operable to support a means for outputting, via the MAC-CE, one or more fields that indicate one or more TCI states from among the set of multiple TCI states that are activated for the uplink communications by the UE, where each field of the one or more fields indicates a respective TCI state and indicates whether the set of multiple uplink power control fields includes a respective power uplink control field that corresponds to the respective TCI state.
In some examples, the TCI state component 1425 is capable of, configured to, or operable to support a means for outputting, via a set of multiple TCI state fields in the MAC-CE, a respective ID associated with a respective TCI state to which the power control parameter included in the uplink power control field applies.
In some examples, to support outputting the MAC-CE, the MAC-CE component 1440 is capable of, configured to, or operable to support a means for outputting a unified TCI state activation MAC-CE that indicates one or more TCI states from among the set of multiple TCI states that are activated for the uplink communications by the UE.
In some examples, the MAC-CE component 1440 is capable of, configured to, or operable to support a means for outputting a unified TCI state activation MAC- CE, where the unified TCI state activation MAC-CE indicates one or more TCI states from among the set of multiple TCI states that are activated for the uplink communications by the UE.
In some examples, the power control parameter includes a pathloss offset. In some examples, the MAC-CE includes at least one field that indicates whether the pathloss offset is with respect to a nominal pathloss or a measured pathloss.
In some examples, the uplink power control component 1430 is capable of, configured to, or operable to support a means for outputting, after receiving the uplink communications using the one or more transmit powers, a second message including second uplink power control information, where the message includes a unified TCI state activation MAC-CE that indicates one or more TCI states from among the set of multiple TCI states that are activated for the uplink communications by the UE, and where the second message includes a MAC-CE different than the unified TCI state activation MAC-CE.
In some examples, the power control parameter indicated via the message includes a reference to a measured parameter. In some examples, a second power control parameter indicated via the second message includes a second reference to a nominal parameter, a measured parameter, or any combination thereof, where the nominal parameter includes one of an initial parameter, a previous parameter, a previous measured parameter or an initial measured parameter. In some examples, the second message includes one or more fields that indicate whether the second power control parameter indicated via the second message references the nominal parameter or the measured parameter.
In some examples, the frequency configuration component 1445 is capable of, configured to, or operable to support a means for outputting an indication of a set of CCs for TCI state activation, where the power control parameter corresponds to the one or more CCs that are the same as the set of CCs for TCI state activation, and where the power control parameter is applied to the one or more TCI states across the set of CCs.
In some examples, the frequency configuration component 1445 is capable of, configured to, or operable to support a means for outputting a first indication of a first set of CCs for TCI state activation. In some examples, the frequency configuration  component 1445 is capable of, configured to, or operable to support a means for outputting a second indication of a second set of CCs associated with uplink power control, where the power control parameter corresponds to the one or more CCs that are the same as the second set of CCs for uplink power control, and where the power control parameter is applied to the one or more TCI states across the second set of CCs.
FIG. 15 shows a diagram of a system 1500 including a device 1505 that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure. The device 1505 may be an example of or include components of a device 1205, a device 1305, or a network entity 105 as described herein. The device 1505 may communicate with other network devices or network equipment such as one or more of the network entities 105, UEs 115, or any combination thereof. The communications may include communications over one or more wired interfaces, over one or more wireless interfaces, or any combination thereof. The device 1505 may include components that support outputting and obtaining communications, such as a communications manager 1520, a transceiver 1510, one or more antennas 1515, at least one memory 1525, code 1530, and at least one processor 1535. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1540) .
The transceiver 1510 may support bi-directional communications via wired links, wireless links, or both as described herein. In some examples, the transceiver 1510 may include a wired transceiver and may communicate bi-directionally with another wired transceiver. Additionally, or alternatively, in some examples, the transceiver 1510 may include a wireless transceiver and may communicate bi-directionally with another wireless transceiver. In some examples, the device 1505 may include one or more antennas 1515, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently) . The transceiver 1510 may also include a modem to modulate signals, to provide the modulated signals for transmission (e.g., by one or more antennas 1515, by a wired transmitter) , to receive modulated signals (e.g., from one or more antennas 1515, from a wired receiver) , and to demodulate signals. In some implementations, the transceiver 1510 may include one or more interfaces, such as one or more interfaces coupled with the one or more antennas 1515 that are configured  to support various receiving or obtaining operations, or one or more interfaces coupled with the one or more antennas 1515 that are configured to support various transmitting or outputting operations, or a combination thereof. In some implementations, the transceiver 1510 may include or be configured for coupling with one or more processors or one or more memory components that are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other outputting, or any combination thereof. In some implementations, the transceiver 1510, or the transceiver 1510 and the one or more antennas 1515, or the transceiver 1510 and the one or more antennas 1515 and one or more processors or one or more memory components (e.g., the at least one processor 1535, the at least one memory 1525, or both) , may be included in a chip or chip assembly that is installed in the device 1505. In some examples, the transceiver 1510 may be operable to support communications via one or more communications links (e.g., communication link (s) 125, backhaul communication link (s) 120, a midhaul communication link 162, a fronthaul communication link 168) .
The at least one memory 1525 may include RAM, ROM, or any combination thereof. The at least one memory 1525 may store computer-readable, computer-executable, or processor-executable code, such as the code 1530. The code 1530 may include instructions that, when executed by one or more of the at least one processor 1535, cause the device 1505 to perform various functions described herein. The code 1530 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1530 may not be directly executable by a processor of the at least one processor 1535 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 1525 may include, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices. In some examples, the at least one processor 1535 may include multiple processors and the at least one memory 1525 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories which may, individually or collectively, be configured to perform various functions herein (for example, as part of a processing system) .
The at least one processor 1535 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more central processing units (CPUs) , one or more graphics processing units (GPUs) , one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs) ) , one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof) . In some cases, the at least one processor 1535 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into one or more of the at least one processor 1535. The at least one processor 1535 may be configured to execute computer-readable instructions stored in a memory (e.g., one or more of the at least one memory 1525) to cause the device 1505 to perform various functions (e.g., functions or tasks supporting power control information for multiple TCI states) . For example, the device 1505 or a component of the device 1505 may include at least one processor 1535 and at least one memory 1525 coupled with one or more of the at least one processor 1535, the at least one processor 1535 and the at least one memory 1525 configured to perform various functions described herein. The at least one processor 1535 may be an example of a cloud-computing platform (e.g., one or more physical nodes and supporting software such as operating systems, virtual machines, or container instances) that may host the functions (e.g., by executing code 1530) to perform the functions of the device 1505. The at least one processor 1535 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1505 (such as within one or more of the at least one memory 1525) . In some examples, the at least one processor 1535 may include multiple processors and the at least one memory 1525 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein. In some examples, the at least one processor 1535 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 1535) and memory circuitry (which may include the at least one memory 1525) ) , or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing  system may be configured to perform one or more of the functions described herein. For example, the at least one processor 1535 or a processing system including the at least one processor 1535 may be configured to, configurable to, or operable to cause the device 1505 to perform one or more of the functions described herein. Further, as described herein, being “configured to, ” being “configurable to, ” and being “operable to”may be used interchangeably and may be associated with a capability, when executing code stored in the at least one memory 1525 or otherwise, to perform one or more of the functions described herein.
In some examples, a bus 1540 may support communications of (e.g., within) a protocol layer of a protocol stack. In some examples, a bus 1540 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack) , which may include communications performed within a component of the device 1505, or between different components of the device 1505 that may be co-located or located in different locations (e.g., where the device 1505 may refer to a system in which one or more of the communications manager 1520, the transceiver 1510, the at least one memory 1525, the code 1530, and the at least one processor 1535 may be located in one of the different components or divided between different components) .
In some examples, the communications manager 1520 may manage aspects of communications with a core network 130 (e.g., via one or more wired or wireless backhaul links) . For example, the communications manager 1520 may manage the transfer of data communications for client devices, such as one or more UEs 115. In some examples, the communications manager 1520 may manage communications with one or more other network devices, and may include a controller or scheduler for controlling communications with UEs 115 (e.g., in cooperation with the one or more other network devices) . In some examples, the communications manager 1520 may support an X2 interface within an LTE/LTE-A wireless communications network technology to provide communication between network entities 105.
Additionally, or alternatively, the communications manager 1520 may support wireless communication in accordance with examples as disclosed herein. For example, the communications manager 1520 is capable of, configured to, or operable to support a means for outputting a control message that indicates a set of multiple TCI  states for uplink communications by a UE via one or more CCs. The communications manager 1520 is capable of, configured to, or operable to support a means for outputting a message including uplink power control information that indicates a power control parameter for uplink pathloss calculation for the one or more CCs, the power control parameter corresponding to one or more TCI states from among the set of multiple TCI states. The communications manager 1520 is capable of, configured to, or operable to support a means for obtaining, via the one or more CCs in accordance with the one or more TCI states, the uplink communications using one or more transmit powers based on the power control parameter.
By including or configuring the communications manager 1520 in accordance with examples as described herein, the device 1505 may support techniques for improved communication reliability, reduced latency, reduced power consumption, more efficient utilization of communication resources, and improved coordination between devices, among other examples.
In some examples, the communications manager 1520 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver 1510, the one or more antennas 1515 (e.g., where applicable) , or any combination thereof. Although the communications manager 1520 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1520 may be supported by or performed by the transceiver 1510, one or more of the at least one processor 1535, one or more of the at least one memory 1525, the code 1530, or any combination thereof (for example, by a processing system including at least a portion of the at least one processor 1535, the at least one memory 1525, the code 1530, or any combination thereof) . For example, the code 1530 may include instructions executable by one or more of the at least one processor 1535 to cause the device 1505 to perform various aspects of power control information for multiple TCI states as described herein, or the at least one processor 1535 and the at least one memory 1525 may be otherwise configured to, individually or collectively, perform or support such operations.
FIG. 16 shows a flowchart illustrating a method 1600 that supports power control information for multiple TCI states in accordance with one or more aspects of  the present disclosure. The operations of the method 1600 may be implemented by a UE or its components as described herein. For example, the operations of the method 1600 may be performed by a UE 115 as described with reference to FIGs. 1 through 11. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
At 1605, the method may include receiving a control message that indicates a set of multiple TCI states for uplink communications by the UE via one or more CCs. The operations of 1605 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed by a TCI state component 1025 as described with reference to FIG. 10.
At 1610, the method may include receiving a message including uplink power control information that indicates a power control parameter for uplink pathloss calculation for the one or more CCs, the power control parameter corresponding to one or more TCI states from among the set of multiple TCI states. The operations of 1610 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed by an uplink power control component 1030 as described with reference to FIG. 10.
At 1615, the method may include transmitting, via the one or more CCs in accordance with the one or more TCI states, the uplink communications using one or more transmit powers that are based on the power control parameter. The operations of 1615 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed by a transmit power component 1035 as described with reference to FIG. 10.
FIG. 17 shows a flowchart illustrating a method 1700 that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure. The operations of the method 1700 may be implemented by a UE or its components as described herein. For example, the operations of the method 1700 may be performed by a UE 115 as described with reference to FIGs. 1 through 11. In some examples, a UE may execute a set of instructions to control the functional  elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
At 1705, the method may include receiving a control message that indicates a set of multiple TCI states for uplink communications by the UE via one or more CCs. The operations of 1705 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed by a TCI state component 1025 as described with reference to FIG. 10.
At 1710, the method may include receiving a message including uplink power control information that indicates a power control parameter for uplink pathloss calculation for the one or more CCs, the power control parameter corresponding to one or more TCI states from among the set of multiple TCI states. The operations of 1710 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed by an uplink power control component 1030 as described with reference to FIG. 10.
At 1715, the method may include transmitting, via the one or more CCs in accordance with the one or more TCI states, the uplink communications using one or more transmit powers that are based on the power control parameter. The operations of 1715 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed by a transmit power component 1035 as described with reference to FIG. 10.
At 1720, the method may include receiving, after transmitting the uplink communications using the one or more transmit powers, a second message including second uplink power control information, where the message includes a unified TCI state activation MAC-CE that indicates one or more TCI states from among the set of multiple TCI states that are activated for the uplink communications by the UE, and where the second message includes a MAC-CE different than the unified TCI state activation MAC-CE. The operations of 1720 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1720 may be performed by an uplink power control component 1030 as described with reference to FIG. 10.
FIG. 18 shows a flowchart illustrating a method 1800 that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure. The operations of the method 1800 may be implemented by a UE or its components as described herein. For example, the operations of the method 1800 may be performed by a UE 115 as described with reference to FIGs. 1 through 11. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
At 1805, the method may include receiving a control message that indicates a set of multiple TCI states for uplink communications by the UE via one or more CCs. The operations of 1805 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed by a TCI state component 1025 as described with reference to FIG. 10.
At 1810, the method may include receiving a message including uplink power control information that indicates a power control parameter for uplink pathloss calculation for the one or more CCs, the power control parameter corresponding to one or more TCI states from among the set of multiple TCI states. The operations of 1810 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed by an uplink power control component 1030 as described with reference to FIG. 10.
At 1815, the method may include determining an uplink pathloss associated with the one or more TCI states based on the power control parameter and a reference pathloss value, where the power control parameter includes a pathloss offset value. The operations of 1815 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed by a pathloss component 1050 as described with reference to FIG. 10.
At 1820, the method may include determining one or more transmit powers for the uplink communications according to the one or more TCI states based on the calculated uplink pathloss. The operations of 1820 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1820  may be performed by a transmit power component 1035 as described with reference to FIG. 10.
At 1825, the method may include transmitting, via the one or more CCs in accordance with the one or more TCI states, the uplink communications using the one or more transmit powers that are based on the power control parameter. The operations of 1825 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1825 may be performed by a transmit power component 1035 as described with reference to FIG. 10.
FIG. 19 shows a flowchart illustrating a method 1900 that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure. The operations of the method 1900 may be implemented by a UE or a network entity or its components as described herein. For example, the operations of the method 1900 may be performed by a UE 115 as described with reference to FIGs. 1 through 11 or a network entity as described with reference to FIGs. 1 through 7 and 12 through 15. In some examples, a UE or a network entity may execute a set of instructions to control the functional elements of the UE or the network entity to perform the described functions. Additionally, or alternatively, the UE or the network entity may perform aspects of the described functions using special-purpose hardware.
At 1905, the method may include outputting a control message that indicates a set of multiple TCI states for uplink communications by a UE via one or more CCs. The operations of 1905 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1905 may be performed by a TCI state component 1025 or a TCI state component 1425 as described with reference to FIGs. 10 and 14.
At 1910, the method may include outputting a message including uplink power control information that indicates a power control parameter for uplink pathloss calculation for the one or more CCs, the power control parameter corresponding to one or more TCI states from among the set of multiple TCI states. The operations of 1910 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1910 may be performed by an uplink power control  component 1030 or an uplink power control component 1430 as described with reference to FIGs. 10 and 14.
At 1915, the method may include obtaining, via the one or more CCs in accordance with the one or more TCI states, the uplink communications using one or more transmit powers based on the power control parameter. The operations of 1915 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1915 may be performed by a power control parameter component 1055 or a power control parameter component 1435 as described with reference to FIGs. 10 and 14.
FIG. 20 shows a flowchart illustrating a method 2000 that supports power control information for multiple TCI states in accordance with one or more aspects of the present disclosure. The operations of the method 2000 may be implemented by a UE or a network entity or its components as described herein. For example, the operations of the method 2000 may be performed by a UE 115 as described with reference to FIGs. 1 through 11 or a network entity as described with reference to FIGs. 1 through 7 and 12 through 15. In some examples, a UE or a network entity may execute a set of instructions to control the functional elements of the UE or the network entity to perform the described functions. Additionally, or alternatively, the UE or the network entity may perform aspects of the described functions using special-purpose hardware.
At 2005, the method may include outputting a first indication of a first set of CCs for TCI state activation. The operations of 2005 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2005 may be performed by a frequency configuration component 1045 or a frequency configuration component 1445 as described with reference to FIGs. 10 and 14.
At 2010, the method may include outputting a second indication of a second set of CCs associated with uplink power control. The operations of 2010 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2010 may be performed by a frequency configuration component 1045 or a frequency configuration component 1445 as described with reference to FIGs. 10 and 14.
At 2015, the method may include outputting a control message that indicates a set of multiple TCI states for uplink communications by a UE via one or more CCs. The operations of 2015 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2015 may be performed by a TCI state component 1025 or a TCI state component 1425 as described with reference to FIGs. 10 and 14.
At 2020, the method may include outputting a message including uplink power control information that indicates a power control parameter for uplink pathloss calculation for the one or more CCs, the power control parameter corresponding to one or more TCI states from among the set of multiple TCI states, where the power control parameter corresponds to the one or more CCs that are the same as the second set of CCs for uplink power control, and where the power control parameter is applied to the one or more TCI states across the second set of CCs. The operations of 2020 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2020 may be performed by an uplink power control component 1030 or an uplink power control component 1430 as described with reference to FIGs. 10 and 14.
At 2025, the method may include obtaining, via the one or more CCs in accordance with the one or more TCI states, the uplink communications using one or more transmit powers based on the power control parameter. The operations of 2025 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2025 may be performed by a power control parameter component 1055 or a power control parameter component 1435 as described with reference to FIGs. 10 and 14.
The following provides an overview of aspects of the present disclosure:
Aspect 1: A method for wireless communication at a UE, comprising: receiving a control message that indicates a plurality of TCI states for uplink communications by the UE via one or more CCs; receiving a message comprising uplink power control information that indicates a power control parameter associated with uplink pathloss, the power control parameter corresponding to at least two TCI states from among the plurality of TCI states; and transmitting, via the one or more CCs  in accordance with the at least two TCI states, the uplink communications using one or more transmit powers that are based at least in part on the power control parameter.
Aspect 2: The method of aspect 1, wherein receiving the message comprises: receiving a MAC-CE that indicates the power control parameter corresponding to the at least two TCI states.
Aspect 3: The method of aspect 2, further comprising: receiving the power control parameter via a set of one or more reserved bits within the MAC-CE, an uplink power control field within the MAC-CE, or both.
Aspect 4: The method of aspect 2, further comprising: receiving, via a plurality of uplink power control fields within the MAC-CE, the power control parameter.
Aspect 5: The method of aspect 4, wherein a quantity of the plurality of uplink power control fields is based at least in part on a quantity of TCI states from among the plurality of TCI states that are activated for the uplink communications by the UE; or the quantity of the plurality of uplink power control fields is based at least in part on the quantity of TCI states from among the plurality of TCI states that are activated for the uplink communications by the UE and that are associated with an uplink power control configuration.
Aspect 6: The method of aspect 4, further comprising: receiving, via the MAC-CE, one or more fields that indicate one or more TCI states from among the plurality of TCI states that are activated for the uplink communications by the UE, wherein each field of the one or more fields indicates a respective TCI state and indicates whether the plurality of uplink power control fields comprises a respective power uplink control field that corresponds to the respective TCI state.
Aspect 7: The method of aspect 4, further comprising: receiving, via each uplink power control field of the plurality of uplink power control fields, a respective identifier associated with a respective TCI state to which the power control parameter included in the uplink power control field applies.
Aspect 8: The method of any of aspects 2 through 7, further comprising: determining the one or more transmit powers for the at least two TCI states using the  power control parameter based at least in part on the at least two TCI states being activated for the uplink communications by the UE; or determining the one or more transmit powers for the at least two TCI states using the power control parameter based at least in part on the at least two TCI states being activated for the uplink communications by the UE and further based at least in part on the at least two TCI states being associated with an uplink power control configuration; or determining the one or more transmit powers for the at least two TCI states using the power control parameter based at least in part on at least two bits in the MAC-CE that indicate the power control parameter applies to the at least two TCI states.
Aspect 9: The method of any of aspects 2 through 8, wherein receiving the MAC-CE comprises: receiving a unified TCI state activation MAC-CE that indicates one or more TCI states from among the plurality of TCI states that are activated for the uplink communications by the UE.
Aspect 10: The method of any of aspects 2 through 8, further comprising: receiving a unified TCI state activation MAC-CE, wherein the unified TCI state activation MAC-CE indicates one or more TCI states from among the plurality of TCI states that are activated for the uplink communications by the UE.
Aspect 11: The method of any of aspects 2 through 10, wherein the power control parameter comprises a pathloss offset; and the MAC-CE comprises at least one field that indicates whether the pathloss offset is with respect to a nominal pathloss or a measured pathloss.
Aspect 12: The method of any of aspects 1 through 11, further comprising: receiving, after transmitting the uplink communications using the one or more transmit powers, a second message comprising second uplink power control information, wherein the message comprises a unified TCI state activation MAC-CE that indicates one or more TCI states from among the plurality of TCI states that are activated for the uplink communications by the UE, and wherein the second message comprises a MAC-CE different than the unified TCI state activation MAC-CE.
Aspect 13: The method of aspect 12, wherein the power control parameter indicated via the message comprises a reference to a measured parameter; a second power control parameter indicated via the second message comprises a second reference  to a nominal parameter, a previous parameter, an initial parameter, a measured parameter, or any combination thereof; and the second message comprises one or more fields that indicate whether the second power control parameter indicated via the second message references the nominal parameter, the previous parameter, the initial parameter, the measured parameter, or any combination thereof.
Aspect 14: The method of any of aspects 1 through 13, further comprising: receiving an indication of a set of CCs for TCI state activation, wherein the power control parameter corresponds to the one or more CCs that are the same as the set of CCs for TCI state activation; and applying the power control parameter to the at least two TCI states across the set of CCs.
Aspect 15: The method of any of aspects 1 through 13, further comprising: receiving a first indication of a first set of CCs for TCI state activation; receiving a second indication of a second set of CCs associated with uplink power control, wherein the power control parameter corresponds to the one or more CCs that are the same as the second set of CCs for uplink power control; and applying the power control parameter to the at least two TCI states across the second set of CCs.
Aspect 16: The method of any of aspects 1 through 15, further comprising: determining an uplink pathloss associated with the at least two TCI states based at least in part on the power control parameter and a reference pathloss value, wherein the power control parameter comprises a pathloss offset value; and determining the one or more transmit powers for the uplink communications according to the at least two TCI states based at least in part on the calculated uplink pathloss.
Aspect 17: The method of any of aspects 1 through 15, further comprising: determining an uplink pathloss associated with the at least two TCI states based at least in part on the power control parameter and a reference pathloss value, wherein the power control parameter comprises a pathloss scaling factor; and determining the one or more transmit powers for the uplink communications according to the at least two TCI states based at least in part on the calculated uplink pathloss.
Aspect 18: A method for wireless communication at a network entity, comprising: outputting a control message that indicates a plurality of TCI states for uplink communications by a UE via one or more CCs; outputting a message comprising  uplink power control information that indicates a power control parameter associated with uplink pathloss, the power control parameter corresponding to at least two TCI states from among the plurality of TCI states; and obtaining, via the one or more CCs in accordance with the at least two TCI states, the uplink communications using one or more transmit powers based at least in part on the power control parameter.
Aspect 19: The method of aspect 18, wherein outputting the message comprises: outputting a MAC-CE that indicates the power control parameter corresponding to the at least two TCI states.
Aspect 20: The method of aspect 19, further comprising: outputting the power control parameter via a set of one or more reserved bits within the MAC-CE, an uplink power control field within the MAC-CE, or both.
Aspect 21: The method of aspect 19, further comprising: outputting, via a plurality of uplink power control fields within the MAC-CE, the power control parameter.
Aspect 22: The method of aspect 21, wherein a quantity of the plurality of uplink power control fields is based at least in part on a quantity of TCI states from among the plurality of TCI states that are activated for the uplink communications by the UE; or the quantity of the plurality of uplink power control fields is based at least in part on the quantity of TCI states from among the plurality of TCI states that are activated for the uplink communications by the UE and that are associated with an uplink power control configuration.
Aspect 23: The method of aspect 21, further comprising: outputting, via the MAC-CE, one or more fields that indicate one or more TCI states from among the plurality of TCI states that are activated for the uplink communications by the UE, wherein each field of the one or more fields indicates a respective TCI state and indicates whether the plurality of uplink power control fields comprises a respective power uplink control field that corresponds to the respective TCI state.
Aspect 24: The method of aspect 21, further comprising: outputting, via each uplink power control field of the plurality of uplink power control fields, a respective  identifier associated with a respective TCI state to which the power control parameter included in the uplink power control field applies.
Aspect 25: The method of any of aspects 19 through 24, wherein outputting the MAC-CE comprises: outputting a unified TCI state activation MAC-CE that indicates one or more TCI states from among the plurality of TCI states that are activated for the uplink communications by the UE.
Aspect 26: The method of any of aspects 19 through 24, further comprising: outputting a unified TCI state activation MAC-CE, wherein the unified TCI state activation MAC-CE indicates one or more TCI states from among the plurality of TCI states that are activated for the uplink communications by the UE.
Aspect 27: The method of any of aspects 19 through 26, wherein the power control parameter comprises a pathloss offset; and the MAC-CE comprises at least one field that indicates whether the pathloss offset is with respect to a nominal pathloss or a measured pathloss.
Aspect 28: The method of any of aspects 18 through 27, further comprising: outputting, after receiving the uplink communications using the one or more transmit powers, a second message comprising second uplink power control information, wherein the message comprises a unified TCI state activation MAC-CE that indicates one or more TCI states from among the plurality of TCI states that are activated for the uplink communications by the UE, and wherein the second message comprises a MAC-CE different than the unified TCI state activation MAC-CE.
Aspect 29: The method of aspect 28, wherein the power control parameter indicated via the message comprises a reference to a measured parameter; a second power control parameter indicated via the second message comprises a second reference to a nominal parameter, a previous parameter, an initial parameter, a measured parameter, or any combination thereof; and the second message comprises one or more fields that indicate whether the second power control parameter indicated via the second message references the nominal parameter, the previous parameter, the initial parameter, the measured parameter, or any combination thereof.
Aspect 30: The method of any of aspects 18 through 29, further comprising: outputting an indication of a set of CCs for TCI state activation, wherein the power control parameter corresponds to the one or more CCs that are the same as the set of CCs for TCI state activation, and wherein the power control parameter is applied to the at least two TCI states across the set of CCs.
Aspect 31: The method of any of aspects 18 through 29, further comprising: outputting a first indication of a first set of CCs for TCI state activation; and outputting a second indication of a second set of CCs associated with uplink power control, wherein the power control parameter corresponds to the one or more CCs that are the same as the second set of CCs for uplink power control, and wherein the power control parameter is applied to the at least two TCI states across the second set of CCs.
Aspect 32: A UE for wireless communication, comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to perform a method of any of aspects 1 through 17.
Aspect 33: A UE for wireless communication, comprising at least one means for performing a method of any of aspects 1 through 17.
Aspect 34: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to perform a method of any of aspects 1 through 17.
Aspect 35: A network entity for wireless communication, comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to perform a method of any of aspects 18 through 31.
Aspect 36: A network entity for wireless communication, comprising at least one means for performing a method of any of aspects 18 through 31.
Aspect 37: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to perform a method of any of aspects 18 through 31.
It should be noted that the methods described herein describe possible implementations. The operations and the steps may be rearranged or otherwise modified and other implementations are possible. Further, aspects from two or more of the methods may be combined.
Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB) , Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.
Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed using a general-purpose processor, a DSP, an ASIC, a CPU, a graphics processing unit (GPU) , a neural processing unit (NPU) , an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor but, in the alternative, the 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 in conjunction with a DSP core, or any other such configuration) . Any functions or operations described herein as being capable of being performed by a processor may be performed by multiple processors that, individually or collectively, are capable of performing the described functions or operations.
The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as or transmitted using one or more instructions or code of a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another. A non-transitory storage medium may be any available medium that may be accessed 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, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) , or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD) , floppy disk, and Blu-ray disc. Disks may reproduce data magnetically, and discs may reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media. Any functions or operations described herein as being capable of being  performed by a memory may be performed by multiple memories that, individually or collectively, are capable of performing the described functions or operations.
As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of” ) indicates an inclusive list such that, for example, a list of at least one of 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) . Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. ”
As used herein, including in the claims, the article “a” before a noun is open-ended and understood to refer to “at least one” of those nouns or “one or more” of those nouns. Thus, the terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable. For example, if a claim recites “a component” that performs 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 “acomponent” having characteristics or performing functions may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent reference to a component introduced with the article “a” using the terms “the” or “said” may refer to any or all of the one or more components. For example, a component introduced with the article “a” may be understood to mean “one or more components, ” and referring to “the component” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components. ” Similarly, subsequent reference to a component introduced as “one or more components” using the terms “the” or “said” may refer to any or all of the one or more components. For example, referring to “the one or more components” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components. ”
The term “determine” or “determining” encompasses a variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database, or another data  structure) , ascertaining, and the like. Also, “determining” can include receiving (e.g., receiving information) , accessing (e.g., accessing data stored in memory) , and the like. Also, “determining” can include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.
In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label or other subsequent reference label.
The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration” and not “preferred” or “advantageous over other examples. ” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some figures, known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.
The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims (30)

  1. A user equipment (UE) , comprising:
    one or more memories storing processor-executable code; and
    one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to:
    receive a control message that indicates a plurality of transmission configuration indication states for uplink communications by the UE via one or more component carriers;
    receive a message comprising uplink power control information that indicates a power control parameter for uplink pathloss calculation for the one or more component carriers, the power control parameter corresponding to one or more transmission configuration indication states from among the plurality of transmission configuration indication states; and
    transmit, via the one or more component carriers in accordance with the one or more transmission configuration indication states, the uplink communications using one or more transmit powers that are based at least in part on the power control parameter.
  2. The UE of claim 1, wherein, to receive the message, the one or more processors are individually or collectively operable to execute the code to cause the UE to:
    receive a medium access control-control element that indicates the power control parameter corresponding to the one or more transmission configuration indication states.
  3. The UE of claim 2, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:
    receive the power control parameter via a set of one or more reserved bits within the medium access control-control element, an uplink power control field within the medium access control-control element, or both.
  4. The UE of claim 2, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:
    receive, via a plurality of uplink power control fields within the medium access control-control element, the power control parameter.
  5. The UE of claim 4, wherein:
    a quantity of the plurality of uplink power control fields is based at least in part on a quantity of transmission configuration indication states from among the plurality of transmission configuration indication states that are activated for the uplink communications by the UE; or
    the quantity of the plurality of uplink power control fields is based at least in part on the quantity of transmission configuration indication states from among the plurality of transmission configuration indication states that are activated for the uplink communications by the UE and that are associated with an uplink power control parameter configuration.
  6. The UE of claim 4, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:
    receive, via the medium access control-control element, one or more fields that indicate one or more transmission configuration indication states from among the plurality of transmission configuration indication states that are activated for the uplink communications by the UE, wherein each field of the one or more fields indicates a respective transmission configuration indication state and indicates whether the plurality of uplink power control fields comprises a respective power uplink control field that corresponds to the respective transmission configuration indication state.
  7. The UE of claim 4, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:
    receive, via a plurality of transmission configuration indication state fields within the medium access control-control element, a respective identifier associated with a respective transmission configuration indication state to which the power control parameter included in the uplink power control field applies.
  8. The UE of claim 2, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:
    determine the one or more transmit powers for the one or more transmission configuration indication states using the power control parameter based at least in part on the one or more transmission configuration indication states being activated for the uplink communications by the UE; or
    determine the one or more transmit powers for the one or more transmission configuration indication states using the power control parameter based at least in part on the one or more transmission configuration indication states being activated for the uplink communications by the UE and further based at least in part on the one or more transmission configuration indication states being associated with an uplink power control parameter configuration; or
    determine the one or more transmit powers for the one or more transmission configuration indication states using the power control parameter based at least in part on at least two bits in the medium access control-control element that indicate the power control parameter applies to the one or more transmission configuration indication states.
  9. The UE of claim 2, wherein, to receive the medium access control-control element, the one or more processors are individually or collectively operable to execute the code to cause the UE to:
    receive a unified transmission configuration indication state activation medium access control-control element that indicates one or more transmission configuration indication states from among the plurality of transmission configuration indication states that are activated for the uplink communications by the UE.
  10. The UE of claim 2, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:
    receive a unified transmission configuration indication state activation medium access control-control element, wherein the unified transmission configuration indication state activation medium access control-control element indicates one or more transmission configuration indication states from among the plurality of transmission configuration indication states that are activated for the uplink communications by the UE.
  11. The UE of claim 2, wherein:
    the power control parameter comprises a pathloss offset; and
    the medium access control-control element comprises at least one field that indicates whether the pathloss offset is with respect to a nominal pathloss or a measured pathloss.
  12. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:
    receive, after transmitting the uplink communications using the one or more transmit powers, a second message comprising second uplink power control information, wherein the message comprises a unified transmission configuration indication state activation medium access control-control element that indicates one or more transmission configuration indication states from among the plurality of transmission configuration indication states that are activated for the uplink communications by the UE, and wherein the second message comprises a medium access control-control element different than the unified transmission configuration indication state activation medium access control-control element.
  13. The UE of claim 12, wherein:
    the power control parameter indicated via the message is referenced to a measured parameter;
    a second power control parameter indicated via the second message is referenced to a nominal parameter, a measured parameter, or any combination thereof, wherein the nominal parameter comprises one of an initial parameter, a previous parameter, a previous measured parameter or an initial measured parameter; and
    the second message comprises one or more fields that indicate whether the second power control parameter indicated via the second message is referenced to the nominal parameter or the measured parameter.
  14. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:
    receive an indication of a set of component carriers for transmission configuration indication state activation, wherein the power control parameter corresponds to the one or more component carriers that are the same as the set of component carriers for transmission configuration indication state activation; and
    apply the power control parameter to the one or more transmission configuration indication states across the set of component carriers.
  15. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:
    receive a first indication of a first set of component carriers for transmission configuration indication state activation;
    receive a second indication of a second set of component carriers associated with uplink power control, wherein the power control parameter corresponds to the one or more component carriers that are the same as the second set of component carriers for uplink power control; and
    apply the power control parameter to the one or more transmission configuration indication states across the second set of component carriers.
  16. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:
    determine an uplink pathloss associated with the one or more transmission configuration indication states based at least in part on the power control parameter and a reference pathloss value, wherein the power control parameter comprises a pathloss offset value; and
    determine the one or more transmit powers for the uplink communications according to the one or more transmission configuration indication states based at least in part on the calculated uplink pathloss.
  17. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:
    determine an uplink pathloss associated with the one or more transmission configuration indication states based at least in part on the power control parameter and a reference pathloss value, wherein the power control parameter comprises a pathloss scaling factor; and
    determine the one or more transmit powers for the uplink communications according to the one or more transmission configuration indication states based at least in part on the calculated uplink pathloss.
  18. A network entity, comprising:
    one or more memories storing processor-executable code; and
    one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to:
    output a control message that indicates a plurality of transmission configuration indication states for uplink communications by a user equipment (UE) via one or more component carriers;
    output a message comprising uplink power control information that indicates a power control parameter for uplink pathloss calculation for the one or more component carriers, the power control parameter corresponding to one or more transmission configuration indication states from among the plurality of transmission configuration indication states; and
    obtain, via the one or more component carriers in accordance with the one or more transmission configuration indication states, the uplink communications using one or more transmit powers based at least in part on the power control parameter.
  19. The network entity of claim 18, wherein, to output the message, the one or more processors are individually or collectively operable to execute the code to cause the network entity to:
    output a medium access control-control element that indicates the power control parameter corresponding to the one or more transmission configuration indication states.
  20. The network entity of claim 19, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to:
    output the power control parameter via a set of one or more reserved bits within the medium access control-control element, an uplink power control field within the medium access control-control element, or both.
  21. The network entity of claim 19, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to:
    output, via a plurality of uplink power control fields within the medium access control-control element, the power control parameter.
  22. The network entity of claim 21, wherein:
    a quantity of the plurality of uplink power control fields is based at least in part on a quantity of transmission configuration indication states from among the plurality of transmission configuration indication states that are activated for the uplink communications by the UE; or
    the quantity of the plurality of uplink power control fields is based at least in part on the quantity of transmission configuration indication states from among the plurality of transmission configuration indication states that are activated for the uplink communications by the UE and that are associated with an uplink power control parameter configuration.
  23. The network entity of claim 21, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to:
    output, via the medium access control-control element, one or more fields that indicate one or more transmission configuration indication states from among the plurality of transmission configuration indication states that are activated for the uplink communications by the UE, wherein each field of the one or more fields indicates a respective transmission configuration indication state and indicates whether the plurality of uplink power control fields comprises a respective power uplink control field that corresponds to the respective transmission configuration indication state.
  24. The network entity of claim 19, wherein, to output the medium access control-control element, the one or more processors are individually or collectively operable to execute the code to cause the network entity to:
    output a unified transmission configuration indication state activation medium access control-control element that indicates one or more transmission configuration indication states from among the plurality of transmission configuration indication states that are activated for the uplink communications by the UE.
  25. The network entity of claim 19, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to:
    output a unified transmission configuration indication state activation medium access control-control element, wherein the unified transmission configuration indication state activation medium access control-control element indicates one or more transmission configuration indication states from among the plurality of transmission configuration indication states that are activated for the uplink communications by the UE.
  26. The network entity of claim 18, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to:
    output, after receiving the uplink communications using the one or more transmit powers, a second message comprising second uplink power control information, wherein the message comprises a unified transmission configuration indication state activation medium access control-control element that indicates one or more transmission configuration indication states from among the plurality of transmission configuration indication states that are activated for the uplink communications by the UE, and wherein the second message comprises a medium access control-control element different than the unified transmission configuration indication state activation medium access control-control element.
  27. A method for wireless communication at a user equipment (UE) , comprising:
    receiving a control message that indicates a plurality of transmission configuration indication states for uplink communications by the UE via one or more component carriers;
    receiving a message comprising uplink power control information that indicates a power control parameter for uplink pathloss calculation for the one or more component carriers, the power control parameter corresponding to one or more transmission configuration indication states from among the plurality of transmission configuration indication states; and
    transmitting, via the one or more component carriers in accordance with the one or more transmission configuration indication states, the uplink communications using one or more transmit powers that are based at least in part on the power control parameter.
  28. The method of claim 27, wherein receiving the message comprises:
    receiving a medium access control-control element that indicates the power control parameter corresponding to the one or more transmission configuration indication states.
  29. A method for wireless communication at a network entity, comprising:
    outputting a control message that indicates a plurality of transmission configuration indication states for uplink communications by a user equipment (UE) via one or more component carriers;
    outputting a message comprising uplink power control information that indicates a power control parameter for uplink pathloss calculation for the one or more component carriers, the power control parameter corresponding to one or more transmission configuration indication states from among the plurality of transmission configuration indication states; and
    obtaining, via the one or more component carriers in accordance with the one or more transmission configuration indication states, the uplink communications using one or more transmit powers based at least in part on the power control parameter.
  30. The method of claim 29, wherein outputting the message comprises:
    outputting a medium access control-control element that indicates the power control parameter corresponding to the one or more transmission configuration indication states.
PCT/CN2024/078289 2024-02-23 2024-02-23 Power control information for multiple transmission configuration indication states Pending WO2025175553A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/078289 WO2025175553A1 (en) 2024-02-23 2024-02-23 Power control information for multiple transmission configuration indication states

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/078289 WO2025175553A1 (en) 2024-02-23 2024-02-23 Power control information for multiple transmission configuration indication states

Publications (1)

Publication Number Publication Date
WO2025175553A1 true WO2025175553A1 (en) 2025-08-28

Family

ID=96846241

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/078289 Pending WO2025175553A1 (en) 2024-02-23 2024-02-23 Power control information for multiple transmission configuration indication states

Country Status (1)

Country Link
WO (1) WO2025175553A1 (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114245979A (en) * 2019-08-23 2022-03-25 高通股份有限公司 Uplink power control through MAC-CE messaging
US20220330167A1 (en) * 2020-01-22 2022-10-13 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method for power control parameter determination, terminal, and network device
US20230284149A1 (en) * 2020-08-06 2023-09-07 Lenovo (Beijing) Limited Configuring uplink transmission configuration indication power control parameters
CN116939794A (en) * 2018-02-16 2023-10-24 联想（新加坡）私人有限公司 Method and apparatus with power control for unlicensed uplink transmission
US20230397193A1 (en) * 2020-09-29 2023-12-07 Lenovo (Beijing) Limited Joint tci states for dl and ul beam indication

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116939794A (en) * 2018-02-16 2023-10-24 联想（新加坡）私人有限公司 Method and apparatus with power control for unlicensed uplink transmission
CN114245979A (en) * 2019-08-23 2022-03-25 高通股份有限公司 Uplink power control through MAC-CE messaging
US20220330167A1 (en) * 2020-01-22 2022-10-13 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method for power control parameter determination, terminal, and network device
US20230284149A1 (en) * 2020-08-06 2023-09-07 Lenovo (Beijing) Limited Configuring uplink transmission configuration indication power control parameters
US20230397193A1 (en) * 2020-09-29 2023-12-07 Lenovo (Beijing) Limited Joint tci states for dl and ul beam indication

Similar Documents

Publication Publication Date Title
WO2022067635A1 (en) Default pathloss reference signals for multi-panel uplink transmissions
WO2023220950A1 (en) Per transmission and reception point power control for uplink single frequency network operation
EP4578229A1 (en) Power headroom reporting for uplink carrier aggregation communications
WO2024000221A1 (en) Transmission configuration indicator state selection for reference signals in multi transmission and reception point operation
WO2023173358A1 (en) Managing power imbalances and power controls for antennas
US12464388B2 (en) Beam failure detection reference signal set update
WO2023220914A1 (en) Transmission configuration indication-specific virtual power headroom reporting
US20240049242A1 (en) Cross-transmission and reception point (trp) indication of a transmission configuration indication state
WO2025175553A1 (en) Power control information for multiple transmission configuration indication states
WO2024007093A1 (en) Per-transmission and reception point (trp) power control parameters
WO2025209014A1 (en) Physical downlink control channel (pdcch) -ordered physical random access channel (prach) for an uplink-only transmission and reception point (trp)
WO2025179416A1 (en) Separate power control adjustment state configurations for sounding reference signals
WO2025209013A1 (en) Transmission configuration indication (tci) state activation for pathloss offset indication
WO2025097418A1 (en) Closed loop power control for multiple transmission-reception point communications
WO2024020820A1 (en) Timing advance offset configuration for inter-cell multiple downlink control information multiple transmission and reception point operation
WO2025156132A1 (en) Techniques for uplink power control selection
US12323972B2 (en) Frequency resource selection for multiple channels
WO2023206578A1 (en) Managing selection of transmission reception points
WO2024031517A1 (en) Unified transmission configuration indication determination for single frequency network
WO2025208403A1 (en) Mapping of reference signals to transmission configuration indicators for beam management and reporting
WO2025208566A1 (en) Pathloss adjustment indication for sounding reference signal transmissions
WO2025054937A1 (en) Layer one measurement based on demodulation reference signal
US20250227489A1 (en) Aggregation factor adaptation for directional communication
US20250096960A1 (en) Antenna recycling for carrier aggregation
WO2024026617A1 (en) Default power parameters per transmission and reception point

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24925304

Country of ref document: EP

Kind code of ref document: A1