Power headroom reporting for unconfigured carriers with unconfigured uplink

Abstract

Aspects related to power headroom reporting for carriers that are not configured for uplink communications are described. In some aspects, a user equipment (UE) can transmit a power headroom report (PHR) to a network entity, the power headroom report (PHR) including first power headroom information for a configured carrier configured for uplink communication and second power headroom information for at least one unconfigured carrier not configured for uplink communication. The UE can also receive a message indicating a selected carrier from the network entity in response to the PHR, the selected carrier comprising one of the configured carrier and the at least one unconfigured carrier, and can transmit an uplink transmission to the network entity via the selected carrier. Other aspects, embodiments, and features are also claimed and described.

Description

[0001] Priority declaration

[0002] This patent application claims priority to pending non-provisional application serial number 18 / 474,966 filed in the United States Patent and Trademark Office on September 26, 2023, and provisional application serial number 63 / 412,272 filed in the United States Patent and Trademark Office on September 30, 2022, both of which are assigned to the assignee of this application and are hereby expressly incorporated herein by reference in their entirety as if fully set forth below and for all applicable purposes. Technical Field

[0003] The techniques discussed below relate generally to wireless communication systems, and more particularly to power headroom reporting. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, and the like. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (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 techniques 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 communication system may include one or more base stations, each of which supports wireless communications for communication devices, which may be referred to as user equipment (UE).

[0005] In some systems, the UE may be configured to report power headroom information. The UE may send one or more power headroom reports to a network entity. These power headroom reports may indicate the amount of power available for uplink transmission by the UE via the corresponding component carrier. Summary of the invention

[0006] An overview of one or more aspects of the present disclosure is presented below to provide a basic understanding of these aspects. This overview is not an extensive review of all expected features of the present disclosure, and is neither intended to identify key or important elements of all aspects of the present disclosure, nor is it intended to describe the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in a form as a preface to a more detailed description presented later.

[0007] In one example, a method for wireless communication by a user equipment (UE) is disclosed. The method includes sending a power headroom report (PHR) to a network entity, the power headroom report (PHR) including first power headroom information for a configured carrier configured for uplink communication and second power headroom information for at least one unconfigured carrier that is not configured for uplink communication. The method also includes: receiving a message indicating a selected carrier from the network entity in response to the PHR, the selected carrier including one of the configured carrier and the at least one unconfigured carrier; and sending an uplink transmission to the network entity via the selected carrier.

[0008] In another example, a UE for wireless communication is disclosed. The UE includes: at least one processor; a transceiver, the transceiver being communicatively coupled to the at least one processor; and a memory, the memory being communicatively coupled to the at least one processor. The at least one processor may be configured to: send a PHR to a network entity, the PHR including first power headroom information for a configured carrier configured for uplink communication and second power headroom information for at least one unconfigured carrier that is not configured for uplink communication; receive a message indicating a selected carrier from the network entity in response to the PHR, the selected carrier including one of the configured carrier and the at least one unconfigured carrier; and send an uplink transmission to the network entity via the selected carrier.

[0009] In another example, a non-transitory computer-readable storage medium having instructions for a UE thereon may be disclosed. The instructions, when executed by a processing circuit, cause the processing circuit to: send a PHR to a network entity, the PHR including first power headroom information for a configured carrier configured for uplink communication and second power headroom information for at least one unconfigured carrier not configured for uplink communication; receive a message indicating a selected carrier from the network entity in response to the PHR, the selected carrier including one of the configured carrier and the at least one unconfigured carrier; and send an uplink transmission to the network entity via the selected carrier.

[0010] In a further example, a UE for wireless communication may be disclosed. The UE includes: means for sending a PHR to a network entity, the PHR including first power headroom information for a configured carrier configured for uplink communication and second power headroom information for at least one unconfigured carrier not configured for uplink communication; means for receiving a message indicating a selected carrier from the network entity in response to the PHR, the selected carrier including one of the configured carrier and the at least one unconfigured carrier; and means for sending an uplink transmission to the network entity via the selected carrier.

[0011] In one example, a method for wireless communication by a network entity is disclosed. The method includes receiving a PHR from a UE, the PHR including first power headroom information for a configured carrier configured for uplink communication and second power headroom information for at least one unconfigured carrier that is not configured for uplink communication. The method includes: selecting a carrier including one of the configured carrier and the at least one unconfigured carrier based on the PHR; and sending a message indicating the selected carrier to the UE. The method also includes receiving an uplink transmission from the UE via the selected carrier.

[0012] In another example, a network entity for wireless communication is disclosed. The network entity includes: at least one processor; a transceiver, the transceiver is communicatively coupled to the at least one processor; and a memory, the memory is communicatively coupled to the at least one processor. The at least one processor can be configured to: receive a PHR from a UE, the PHR including first power headroom information for a configured carrier configured for uplink communication and second power headroom information for at least one unconfigured carrier that is not configured for uplink communication; select a carrier including one of the configured carrier and the at least one unconfigured carrier based on the PHR; send a message indicating the selected carrier to the UE; and receive an uplink transmission from the UE via the selected carrier.

[0013] In another example, a non-transitory computer-readable storage medium having instructions for a network entity station thereon may be disclosed. The instructions, when executed by a processing circuit, cause the processing circuit to: receive a PHR from a UE, the PHR including first power headroom information for a configured carrier configured for uplink communication and second power headroom information for at least one unconfigured carrier not configured for uplink communication; select a carrier including one of the configured carrier and the at least one unconfigured carrier based on the PHR; send a message indicating the selected carrier to the UE; and receive an uplink transmission from the UE via the selected carrier.

[0014] In a further example, a network entity for wireless communication may be disclosed. The network entity includes: a component for receiving a PHR from a UE, the PHR including first power headroom information for a configured carrier configured for uplink communication and second power headroom information for at least one unconfigured carrier that is not configured for uplink communication; a component for selecting a carrier including one of the configured carrier and the at least one unconfigured carrier based on the PHR; a component for sending a message indicating the selected carrier to the UE; and a component for receiving an uplink transmission from the UE via the selected carrier.

[0015] After studying the specific embodiments below, these and other aspects of the present disclosure will become more fully understood. After studying the description of the following specific, exemplary embodiments in conjunction with the accompanying drawings, other aspects, features and embodiments will become apparent to those of ordinary skill in the art. Although features may be discussed with respect to certain embodiments and figures below, all embodiments may include one or more of the advantageous features discussed herein. In other words, although one or more embodiments may be discussed as having certain advantageous features, one or more of such features may also be used according to the various embodiments discussed herein. In a similar manner, although the exemplary embodiments may be discussed below as device, system or method embodiments, it should be understood that these exemplary embodiments may be implemented in various devices, systems and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 is a schematic illustration of a wireless communication system according to some aspects.

[0017] Figure 2 is a conceptual illustration of an example radio access network in accordance with some aspects.

[0018] Figure 3 is a block diagram illustrating a wireless communication system supporting multiple-input multiple-output (MIMO) communications in accordance with some aspects.

[0019] Figure 4 is a schematic illustration of organization of radio resources in an air interface utilizing orthogonal frequency division multiplexing (OFDM) in accordance with some aspects.

[0020] Figure 5 is an example diagram illustrating communications between a user equipment (UE) and a network entity using various carriers in accordance with some aspects.

[0021] Figure 6 is an example flow diagram illustrating features performed by a UE and a network entity in accordance with some aspects.

[0022] Figure 7 is a block diagram conceptually illustrating an example of a hardware implementation for a UE in accordance with some aspects.

[0023] Figure 8 is a flow chart illustrating an example process for wireless communications by a UE in accordance with some aspects.

[0024] Fig. 9 is a block diagram conceptually illustrating an example of a hardware implementation for a network entity in accordance with some aspects.

[0025] Fig.10is a flow chart illustrating an example process for wireless communications by a network entity in accordance with some aspects. DETAILED DESCRIPTION

[0026] The specific embodiments described below in conjunction with the accompanying drawings are intended as descriptions of various configurations and are not intended to represent the only configurations with which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, it is apparent to those skilled in the art that these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid blurring such concepts.

[0027] Although various aspects and embodiments are described in this application by illustrating some examples, it will be understood by those skilled in the art that additional specific implementations and use cases can be generated in many different arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, embodiments and / or uses can be generated via integrated chip embodiments and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, AI-enabled devices, etc.). Although some examples may or may not specifically point to use cases or applications, the applicability of a wide range of described innovations may occur. Specific implementations can range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed, or original equipment manufacturer (OEM) devices or systems in conjunction with one or more aspects of the described innovations. In some actual settings, the device in conjunction with the aspects and features must also include additional components and features for specific implementations and practices of the embodiments protected and described by the claims. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.) It is expected that the innovations described herein can be practiced in a variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc., having different sizes, shapes, and configurations.

[0028] The various concepts presented throughout this disclosure may be implemented across a wide variety of telecommunication systems, network architectures, and communication standards. Figure 1, various aspects of the present disclosure are illustrated with reference to a wireless communication system 100 as an illustrative example and not as a limitation. The wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. By means of the wireless communication system 100, the UE 106 may be enabled to perform data communications with an external data network 110, such as (but not limited to) the Internet.

[0029] The RAN 104 may implement any suitable one or more wireless communication technologies to provide radio access to the UE 106. As an example, the RAN 104 may operate according to the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification, commonly referred to as 5G. As another example, the RAN 104 may operate according to a hybrid of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, commonly referred to as Long Term Evolution (LTE). 3GPP refers to such a hybrid RAN as the Next Generation RAN or NG-RAN. Of course, many other examples may be utilized within the scope of the present disclosure.

[0030] As shown, RAN 104 includes multiple network entities 108, which may be base stations. In a broad sense, a base station is a network element in a radio access network that is responsible for radio transmission and reception to or from a UE in one or more cells. In different technologies, standards or contexts, a base station may be referred to as a base transceiver station (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), a Node B (NB), an eNode B (eNB), a gNode B (gNB), a transmission and reception point (TRP) or some other suitable terminology by those skilled in the art. In some examples, a base station may include two or more TRPs that may be co-located or non-co-located. Each TRP may communicate on the same or different carrier frequencies in the same or different frequency bands. In an example where RAN 104 operates according to both the LTE standard and the 5GNR standard, one of the base stations may be an LTE base station, and the other may be a 5GNR base station.

[0031] RAN 104 is also illustrated as supporting wireless communications for multiple mobile devices. In the 3GPP standards, a mobile device may be referred to as a user equipment (UE), but those skilled in the art may also refer to it as a mobile station (MS), a user station, a mobile unit, a user unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile user station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology. A UE may be a device (e.g., a mobile device) that provides access to network services to a user.

[0032] Within the present disclosure, a "mobile" device does not necessarily need to have the ability to move, but may be stationary. The term mobile device or mobile equipment refers broadly to a wide variety of devices and technologies. A UE may include a number of hardware structural components whose size, shape, and arrangement facilitate communication; such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile stations, cellular (cell) phones, smart phones, Session Initiation Protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smartbooks, tablet devices, personal digital assistants (PDAs), and a wide range of embedded systems, for example, corresponding to the "Internet of Things" (IoT).

[0033] The mobile device may also be a car or other transportation vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-rotor aircraft, a quadcopter, a remote control device, a consumer and / or wearable device (such as glasses, a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., an MP3 player), a camera, a game console, etc. The mobile device may also be a digital home or smart home device (such as home audio, video and / or multimedia equipment), an appliance, a vending machine, a smart lighting device, a home security system, a smart meter Etc. The mobile device may also be a smart energy device, a security device, a solar panel or solar array, a municipal infrastructure device that controls power (e.g., smart grid), lighting, water supply, etc., an industrial automation and enterprise device, a logistics controller, and / or agricultural equipment, etc. In addition, the mobile device may provide connected medical or telemedicine support, such as health care at a distance. Telemedicine devices may include telemedicine monitoring devices and telemedicine management devices, whose communications may be given priority or access priority over other types of information, for example, in terms of priority access for the transmission of critical service data and / or associated QoS for the transmission of critical service data.

[0034] Wireless communication between RAN 104 and UE 106 may be described as utilizing an air interface. Transmissions from a base station (e.g., network entity 108) to one or more UEs (e.g., similar to UE 106) over an air interface may be referred to as downlink (DL) transmissions. According to certain aspects of the present disclosure, the term "downlink" may refer to point-to-multipoint transmissions originating at a base station (e.g., network entity 108). Another way to describe this scheme may be to use the term "broadcast channel multiplexing". Transmissions from a UE (e.g., UE 106) to a base station (e.g., network entity 108) may be referred to as uplink (UL) transmissions. According to further aspects of the present disclosure, the term "uplink" may refer to point-to-point transmissions originating at a UE (e.g., UE 106).

[0035] In some examples, access to the air interface may be scheduled, wherein a scheduling entity (e.g., a network entity 108) allocates resources for communication among some or all devices and equipment within its service area or cell. Within the present disclosure, as discussed further below, a scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities (e.g., UEs 106). That is, for scheduled communications, multiple UEs 106 (which may be scheduled entities) may utilize resources allocated by the scheduling entity 108.

[0036] The network entity 108 is not the only entity that can act as a scheduling entity. That is, in some examples, a UE can act as a scheduling entity, scheduling resources for one or more scheduled entities (e.g., one or more other UEs). For example, a UE can communicate directly with other UEs in a peer-to-peer or device-to-device manner and / or in a relay configuration.

[0037] like Figure 1 , the scheduling entity 108 may broadcast downlink traffic 112 to one or more scheduled entities (e.g., one or more UEs 106). Broadly speaking, the scheduling entity 108 is a node or device responsible for scheduling traffic in the wireless communication network, including downlink traffic 112, and in some examples, uplink traffic 116 from one or more scheduled entities (e.g., one or more UEs 106) to the scheduling entity 108. On the other hand, the scheduled entity (e.g., UE 106) is a node or device that receives downlink control information 114 (including but not limited to scheduling information (e.g., grants), synchronization or timing information, or other control information) from another entity in the wireless communication network (such as the scheduling entity 108). The scheduled entity 106 may also send uplink control information 118 (including but not limited to scheduling requests or feedback information or other control information) to the scheduling entity 108.

[0038] In addition, uplink and / or downlink control information 114 and / or 118 and / or business 112 and / or 116 information may be sent on a waveform that may be divided into frames, subframes, time slots and / or symbols by time. As used herein, a symbol may refer to a time unit that carries one resource element (RE) per subcarrier in an orthogonal frequency division multiplexing (OFDM) waveform. A time slot may carry 7 or 14 OFDM symbols. A subframe may refer to a duration of 1 ms. Multiple subframes or time slots may be grouped together to form a single frame or radio frame. In the present disclosure, a frame may refer to a predetermined duration (e.g., 10 ms) for wireless transmission, wherein each frame is composed of, for example, 10 subframes of 1 ms each. Of course, these definitions are not required, and any suitable scheme for organizing waveforms may be utilized, and the various time divisions of waveforms may have any suitable duration.

[0039] In general, the network entities 108 may include a backhaul interface for communicating with a backhaul portion 120 of the wireless communication system 100. The backhaul portion 120 may provide a link between the network entities 108 and the core network 102. Furthermore, in some examples, a backhaul network may provide interconnections between the respective network entities 108. Various types of backhaul interfaces may be employed, such as a direct physical connection using any suitable transport network, a virtual network, or the like.

[0040] The core network 102 may be part of the wireless communication system 100 and may be independent of the radio access technology used in the RAN 104. In some examples, the core network 102 may be configured according to 5G standards (e.g., 5GC). In other examples, the core network 102 may be configured according to 4G Evolved Packet Core (EPC) or any other appropriate standard or configuration.

[0041] See now Figure 2 , by way of illustrative example and not limitation, a schematic diagram of a radio access network (RAN) 200 according to some aspects of the present disclosure is provided. In some examples, the RAN 200 may be similar to the RAN described above and in Figure 1 is the same as the RAN 104 illustrated in .

[0042] The geographic area covered by the RAN 200 may be divided into multiple cellular regions (cells) that may be uniquely identified by a user equipment (UE) based on an identity broadcast from an access point or base station over the geographic area. Figure 2Cells 202, 204, 206, and 208 are illustrated, each of which may include one or more sectors (not shown). A sector is a sub-area of ​​a cell. All sectors within a cell are served by the same base station. A radio link within a sector may be identified by a single logical identifier belonging to the sector. In a cell divided into sectors, multiple sectors within a cell may be formed by multiple groups of antennas, each of which is responsible for communicating with a UE in a portion of the cell.

[0043] Various base station arrangements can be used. Figure 2 , two base stations (base station 210 and base station 212) are shown in cells 202 and 204. A third base station (base station 214) is shown as controlling a remote radio head (RRH) 216 in cell 206. That is, the base station may have an integrated antenna, or may be connected to an antenna or RRH 216 by a feeder cable. In the illustrated example, cells 202, 204, and 206 may be referred to as macro cells because base stations 210, 212, and 214 support cells with large sizes. In addition, base station 218 is shown in cell 208, which may overlap with one or more macro cells. In this example, cell 208 may be referred to as a small cell (e.g., a micro cell, a pico cell, a femto cell, a home base station, a home Node B, a home eNode B, etc.) because base station 218 supports a cell with a relatively small size. The cell size setting may be performed according to the system design and component constraints.

[0044] It should be appreciated that the RAN 200 may include any number of wireless base stations and cells. In addition, relay nodes may be deployed to extend the size or coverage area of ​​a given cell. Base stations 210, 212, 214, 218 provide wireless access points to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, and / or 218 may be similar to those described above and in Figure 1 The scheduling entity 108 illustrated in FIG. 1 is the same as or similar to that in FIG.

[0045] Figure 2 Also included is an unmanned aerial vehicle (UAV) 220, which may be a drone or a quadcopter. UAV 220 may be configured to act as a base station, or more specifically, a mobile base station. That is, in some examples, the cell may not necessarily be stationary, and the geographic area of ​​the cell may move according to the location of a mobile base station (such as UAV 220).

[0046] Within the RAN 200, cells may include UEs that may communicate with one or more sectors of each cell. In addition, each base station 210, 212, 214, 218, and 220 may be configured to provide access to the core network 102 (see FIG. 1 ) for all UEs in the corresponding cell. Figure 1 ) access point. For example, UEs 222 and 224 may communicate with base station 210; UEs 226 and 228 may communicate with base station 212; UEs 230 and 232 may communicate with base station 214 via RRH 216; UE 234 may communicate with base station 218; and UE 236 may communicate with mobile base station 220. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 may communicate with the base stations described above and Figure 1 200. In some examples, UAV 220 (e.g., a quadcopter) may be a mobile network node and may be configured to act as a UE. For example, UAV 220 may operate within cell 202 by communicating with base station 210.

[0047] In other aspects of RAN 200, sidelink signals can be used between UEs without relying on scheduling or control information from a base station. Sidelink communications can be used in device-to-device (D2D) networks, peer-to-peer (P2P) networks, vehicle-to-vehicle (V2V) networks, vehicle-to-everything (V2X) networks, and / or other suitable sidelink networks. For example, two or more UEs (e.g., UE 238, 240, and 242) can communicate with each other using sidelink signals 237 without relaying the communication through a base station. In some examples, UE 238, 240, and 242 can each act as a scheduling entity or a transmitting sidelink device and / or a scheduled entity or a receiving sidelink device to schedule resources and communicate sidelink signals 237 between them without relying on scheduling or control information from a base station. In other examples, two or more UEs (e.g., UE 226 and 228) within the coverage area of ​​a base station (e.g., base station 212) can also communicate sidelink signals 227 via a direct link (sidelink) without transmitting the communication through base station 212. In this example, base station 212 may allocate resources to UEs 226 and 228 for sidelink communications.

[0048] In order to obtain a low block error rate (BLER) for transmissions over the air interface while still achieving very high data rates, channel coding may be used. That is, wireless communications may typically utilize a suitable error-correcting block code. In a typical block code, an information message or sequence is split into code blocks (CBs), and an encoder (e.g., a codec) at the transmitting device then mathematically adds redundancy to the information message. Utilizing this redundancy in the encoded information message improves the reliability of the message, enabling correction of any bit errors that may occur due to noise.

[0049] Data decoding can be implemented in a variety of ways. In early 5G NR specifications, user data is decoded using quasi-cyclic low-density parity check (LDPC) with two different basemaps: one basemap is used for large code blocks and / or high code rates, and the other basemap is used for other cases. Control information and the physical broadcast channel (PBCH) are decoded using polar decoding based on nested sequences. For these channels, rate matching is performed using puncturing, shortening, and repetition.

[0050] Aspects of the present disclosure may be implemented using any suitable channel code. Various implementations of base stations and UEs may include appropriate hardware and capabilities (eg, encoders, decoders, and / or codecs) to utilize one or more of these channel codes for wireless communications.

[0051] In the RAN 200, the ability of a UE to communicate while moving (independent of its location) is called mobility. The various physical channels between the UE and the RAN 200 are generally established, maintained, and released under the control of an access and mobility management function (AMF). In some scenarios, the AMF may include: a security context management function (SCMF) and a security anchor function (SEAF) that performs authentication. The SCMF may manage security contexts for both control plane functionality and user plane functionality in whole or in part.

[0052] In various aspects of the present disclosure, the RAN 200 may utilize DL-based mobility or UL-based mobility to implement mobility and handover (i.e., the transfer of a UE's connection from one radio channel to another). In a network configured for DL-based mobility, during a call with a scheduling entity or at any other time, the UE may monitor various parameters of the signal from its serving cell and various parameters of neighboring cells. Based on the quality of these parameters, the UE may maintain communication with one or more neighboring cells. During this time, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell for a given amount of time, the UE may perform a handover or handover from the serving cell to a neighboring (target) cell. For example, a UE 224 may move from a geographic area corresponding to its serving cell 202 to a geographic area corresponding to a neighboring cell 206. When the signal strength or quality from a neighboring cell 206 exceeds the signal strength or quality of its serving cell 202 for a given amount of time, the UE 224 may send a report message indicating this condition to its serving base station 210. In response, UE 224 may receive the handover command, and the UE may proceed with the handover to cell 206 .

[0053] In a network configured for UL-based mobility, the network can select a serving cell for each UE using a UL reference signal from each UE. In some examples, base stations 210, 212, and 214 / 216 may broadcast unified synchronization signals (e.g., a unified primary synchronization signal (PSS), a unified secondary synchronization signal (SSS), and a unified physical broadcast channel (PBCH)). UEs 222, 224, 226, 228, 230, and 232 may receive the unified synchronization signals, derive carrier frequency and slot timing from these synchronization signals, and send an uplink pilot or reference signal in response to the derived timing. The uplink pilot signal sent by a UE (e.g., UE 224) may be received concurrently by two or more cells (e.g., base stations 210 and 214 / 216) within RAN 200. Each of the cells may measure the strength of the pilot signal, and the radio access network (e.g., one or more of the base stations 210 and 214 / 216 and / or a central node within the core network) may determine a serving cell for the UE 224. As the UE 224 moves through the RAN 200, the RAN 200 may continue to monitor the uplink pilot signals sent by the UE 224. When the signal strength or quality of the pilot signal measured by the neighboring cell exceeds the signal strength or quality measured by the serving cell, the RAN 200 may hand over the UE 224 from the serving cell to the neighboring cell with or without notifying the UE 224.

[0054] Although the synchronization signals transmitted by base stations 210, 212 and 214 / 216 may be uniform, the synchronization signal may not identify a specific cell, but may identify a zone of multiple cells operating on the same frequency and / or using the same timing. Using zones in a 5G network or other next generation communication network implements an uplink-based mobility framework and improves the efficiency of both the UE and the network, since the number of mobility messages that need to be exchanged between the UE and the network can be reduced.

[0055] In various specific implementations, the air interface in the radio access network 200 may utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum typically provides exclusive use of a portion of the spectrum with the help of a mobile network operator purchasing a license from a government regulator. Unlicensed spectrum provides shared use of a portion of the spectrum without the need for a government-granted license. Although it is still generally necessary to comply with some technical rules to access the unlicensed spectrum, access is generally available to any operator or device. Shared spectrum can fall between licensed spectrum and unlicensed spectrum, where some technical rules or restrictions may be required to access the spectrum, but the spectrum can still be shared by multiple operators and / or multiple RATs. For example, a license holder of a portion of a licensed spectrum may provide licensed shared access (LSA) to share the spectrum with other parties (e.g., with appropriate licensee-determined conditions to obtain access).

[0056] Devices communicating in the radio access network 200 may utilize one or more multiplexing techniques and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification utilizes orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) to provide multiple access for UL transmissions from UEs 222 and 224 to the base station 210, and multiplexing for DL ​​transmissions from the base station 210 to one or more UEs 222 and 224. In addition, for UL transmissions, the 5G NR specification provides support for discrete Fourier transform spread OFDM (DFT-s-OFDM) with CP (also known as single carrier FDMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes, and may be provided using time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource extension multiple access (RSMA), or other suitable multiple access schemes. In addition, multiplexing of DL transmissions from base station 210 to UEs 222 and 224 may be provided using time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes.

[0057] The equipment in the radio access network 200 may also utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link in which two endpoints can communicate with each other in two directions. Full-duplex means that two endpoints can communicate with each other at the same time. Half-duplex means that only one endpoint can transmit information to the other endpoint at a time. Half-duplex simulation is often implemented for wireless links using time division duplex (TDD). In TDD, transmissions in different directions on a given channel are separated from each other using time division multiplexing. That is, in some scenarios, a channel is dedicated to transmission in one direction, while at other times, the channel is dedicated to transmission in another direction, where the direction can change very quickly, for example, several times per time slot. In wireless links, full-duplex channels generally rely on physical isolation of transmitters and receivers and suitable interference cancellation techniques. Full-duplex simulation is often implemented for wireless links by utilizing frequency division duplex (FDD) or space division duplex (SDD). In FDD, transmissions in different directions can operate at different carrier frequencies (e.g., within a paired spectrum). In SDD, transmissions in different directions on a given channel are separated from each other using spatial division multiplexing (SDM). In other examples, full-duplex communication may be implemented within an unpaired spectrum (e.g., within a single carrier bandwidth), where transmissions in different directions occur within different sub-bands of the carrier bandwidth. This type of full-duplex communication may be referred to herein as sub-band full-duplex (SBFD), also known as flexible duplex.

[0058] In some aspects of the present disclosure, the scheduling entity and / or the scheduled entity may be configured for beamforming and / or multiple-input multiple-output (MIMO) techniques. Figure 3 An example of a wireless communication system 300 supporting MIMO is illustrated. In a MIMO system, a transmitter 302 includes multiple transmit antennas 304 (e.g., N transmit antennas), and a receiver 306 includes multiple receive antennas 308 (e.g., M receive antennas). Therefore, there are N×M signal paths 310 from the transmit antennas 304 to the receive antennas 308. Each of the transmitter 302 and the receiver 306 may be implemented, for example, within the scheduling entity 108, the scheduled entity 106, or any other suitable wireless communication device.

[0059] The use of such multi-antenna technology enables wireless communication systems to exploit the spatial domain to support spatial multiplexing, beamforming, and transmit diversity. Spatial multiplexing can be used to simultaneously send different data streams (also referred to as layers) on the same time-frequency resource. These data streams can be sent to a single UE to increase the data rate or to multiple UEs to increase the total system capacity, the latter of which is called multi-user MIMO (MU-MIMO). This is achieved by spatially precoding each data stream (i.e., multiplying the data stream by different weights and phase shifts) and then sending each spatially precoded stream through multiple transmit antennas on the downlink. The spatially precoded data streams arrive at UEs with different spatial characteristics, and the different spatial characteristics enable each UE in the UE to recover one or more data streams destined for the UE. On the uplink, each UE sends a spatially precoded data stream, which enables the base station to identify the source of each spatially precoded data stream.

[0060] The number of data streams or layers corresponds to the rank of transmission. In general, the rank of the MIMO system 300 is limited to the lower of the number of transmit antennas 304 or receive antennas 308. In addition, the channel conditions at the UE and other considerations (such as the available resources at the base station) can also affect the transmission rank. For example, the rank assigned to a specific UE on the downlink (and therefore the number of data streams) can be determined based on a rank indicator (RI) sent from the UE to the base station. The RI can be determined based on the antenna configuration (e.g., the number of transmit antennas and receive antennas) on each receive antenna in the receive antenna and the measured signal to interference and noise ratio (SINR). For example, the RI can indicate the number of layers that can be supported under the current channel conditions. The base station can use the RI and resource information (e.g., the available resources and amount of data to be scheduled for the UE) to assign the rank of transmission to the UE.

[0061] In a time division duplex (TDD) system, UL and DL are reciprocal because they each use different time slots of the same frequency bandwidth. Therefore, in a TDD system, the base station can assign a rank for DL ​​MIMO transmission based on UL SINR measurements (e.g., based on a sounding reference signal (SRS) or other pilot signal sent from the UE). Based on the assigned rank, the base station can then send a CSI-RS with a separate C-RS sequence for each layer to provide multi-layer channel estimation. Based on the CSI-RS, the UE can measure the channel quality across layers and resource blocks and feed back a channel quality indicator (CQI) and RI value to the base station for use in updating the rank and assigning REs for future downlink transmissions.

[0062] In the simplest case, Figure 3As shown, a rank 2 spatial multiplexing transmission on a 2×2 MIMO antenna configuration will transmit one data stream from each transmit antenna 304. Each data stream follows a different signal path 310 to each receive antenna 308. The receiver 306 can then use the received signal from each receive antenna 308 to reconstruct the data stream.

[0063] Will refer to Figure 4 Various aspects of the present disclosure are described with reference to OFDM waveforms schematically illustrated in . It should be understood by those skilled in the art that various aspects of the present disclosure can be applied to DFT-s-OFDMA waveforms in substantially the same manner as described below herein. That is, although some examples of the present disclosure may focus on OFDM links for clarity, it should be appreciated that the same principles can also be applied to DFT-s-OFDMA waveforms.

[0064] In this disclosure, a frame refers to a duration of 10 ms used for wireless transmission, where each frame consists of 10 subframes, each subframe is 1 ms. On a given carrier, there may be one set of frames in the UL and another set of frames in the DL. Now refer to Figure 4 , illustrates an expanded view of an exemplary DL subframe 402 showing an OFDM resource grid 404. However, as will be readily appreciated by those skilled in the art, the physical (PHY) layer transmission structure for any particular application may differ from the examples described herein, depending on any number of factors. Here, time is in units of OFDM symbols in the horizontal direction; and frequency is in units of subcarriers or tones in the vertical direction.

[0065] Resource grid 404 can be used to schematically represent the time-frequency resources for a given antenna port. That is, in a MIMO implementation with multiple available antenna ports, a corresponding number of resource grids 404 can be available for communication. Resource grid 404 is divided into multiple resource elements (REs) 406. RE (which is 1 subcarrier × 1 symbol) is the smallest discrete part of the time-frequency grid and contains a single complex value representing data from a physical channel or signal. Depending on the modulation utilized in a specific implementation, each RE can represent one or more information bits. In some examples, a block of REs can be referred to as a physical resource block (PRB), or more simply a resource block (RB) 408, which contains any suitable number of consecutive subcarriers in the frequency domain. In one example, an RB can include 12 subcarriers (a number independent of the parameter set used). In some examples, depending on the parameter set, an RB can include any suitable number of consecutive OFDM symbols in the time domain. In the present disclosure, it is assumed that a single RB (such as RB 408) corresponds entirely to communication in a single direction (transmission or reception for a given device).

[0066] A UE typically utilizes only a subset of the resource grid 404. An RB may be the smallest unit of resources that may be allocated to a UE. Thus, the more RBs scheduled for a UE, and the higher the modulation scheme selected for the air interface, the higher the data rate for the UE.

[0067] In this illustration, RB 408 is shown as occupying less than the entire bandwidth of subframe 402, with some subcarriers illustrated above and below RB 408. In a given implementation, subframe 402 may have a bandwidth corresponding to any number of one or more RBs 408. Furthermore, in this illustration, RB 408 is shown as occupying less than the entire duration of subframe 402, although this is only one possible example.

[0068] Each subframe 402 (eg, a 1 ms subframe) may be composed of one or more adjacent time slots. Figure 4 In the example shown, as an illustrative example, one subframe 402 includes four time slots 410. In some examples, a time slot may be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot may include 7 or 14 OFDM symbols with a nominal CP. Additional examples may include mini-time slots with shorter durations (e.g., 1, 2, 4, or 7 OFDM symbols). In some cases, these mini-time slots may be transmitted occupying resources scheduled for ongoing time slot transmissions for the same UE or for different UEs.

[0069] The expanded view of one of the time slots 410 illustrates that the time slot 410 includes a control region 412 and a data region 414. In general, the control region 412 may carry a control channel (e.g., PDCCH), and the data region 414 may carry a data channel (e.g., PDSCH or PUSCH). Of course, a time slot may contain all DL, all UL, or at least one DL portion and at least one UL portion. Figure 4 The simple structure illustrated in is merely exemplary in nature, and different slot structures may be utilized and may include one or more regions in each of the control region and the data region.

[0070] Although in Figure 4 408, but each RE 406 within the RB 408 may be scheduled to carry one or more physical channels, including a control channel, a shared channel, a data channel, etc. Other REs 406 within the RB 408 may also carry pilot signals or reference signals. These pilot signals or reference signals may be provided to a receiving device to perform channel estimation of the corresponding channel, which may enable coherent demodulation / detection of the control channel and / or data channel within the RB 408.

[0071] In some examples, time slot 410 may be used for broadcast or unicast communication. For example, broadcast, multicast, or groupcast communication may refer to point-to-multipoint transmission from one device (e.g., a base station, UE, or other similar device) to other devices. Here, broadcast communication is delivered to all devices, while multicast communication is delivered to multiple intended recipient devices. Unicast communication may refer to point-to-point transmission from one device to a single other device.

[0072] In an example of cellular communication on a cellular carrier via a Uu interface, for DL ​​transmission, a scheduling entity (e.g., a base station) may allocate one or more REs 406 (e.g., within a control region 412) to one or more scheduled entities (e.g., UEs) to carry DL control information including one or more DL control channels (such as a physical downlink control channel (PDCCH)). The PDCCH carries downlink control information (DCI), including but not limited to power control commands (e.g., one or more open-loop power control parameters and / or one or more closed-loop power control parameters), scheduling information, grants, and / or assignments of REs for DL ​​transmission and UL transmission. The PDCCH may further carry hybrid automatic repeat request (HARQ) feedback transmissions, such as acknowledgements (ACKs) or negative acknowledgements (NACKs). HARQ is a technique well known to those of ordinary skill in the art, wherein the integrity of packet transmissions may be checked for accuracy at the receiving side, for example, using any appropriate integrity check mechanism, such as a check or cyclic redundancy check (CRC). If the integrity of the transmission is confirmed, an ACK may be sent, and if the integrity of the transmission is not confirmed, a NACK may be sent. In response to the NACK, the sending device may transmit a HARQ retransmission, which may implement trace combining, incremental redundancy, and the like.

[0073] The base station may also allocate one or more REs 406 (e.g., in the control region 412 or the data region 414) to carry other DL signals, such as a demodulation reference signal (DMRS); a phase tracking reference signal (PT-RS); a channel state information (CSI) reference signal (CSI-RS); and a synchronization signal block (SSB). The SSB may be broadcast at regular intervals based on a periodicity (e.g., 5ms, 10ms, 20ms, 40ms, 80ms, or 140ms). The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast control channel (PBCH). The UE may utilize the PSS and SSS to achieve radio frame, subframe, time slot, and symbol synchronization in the time domain, to identify the center of the channel (system) bandwidth in the frequency domain, and to identify the physical cell identity (PCI) of the cell.

[0074] The PBCH in the SSB may also include a master information block (MIB) containing various system information and parameters for decoding a system information block (SIB). The SIB may be, for example, SystemInformationType 1 (SIB1), which may include various additional system information. Examples of system information sent in the MIB may include, but are not limited to, subcarrier spacing, system frame number, configuration of a PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0), and a search space for SIB1. Examples of additional system information sent in SIB1 may include, but are not limited to, random access search space, downlink configuration information, and uplink configuration information. The MIB and SIB1 together provide minimum system information (SI) for initial access.

[0075] In an UL transmission, a scheduled entity (e.g., a UE) may utilize one or more REs 406 to a scheduling entity to carry UL control information (UCI) including one or more UL control channels, such as a physical uplink control channel (PUCCH). The UCI may include various packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions. In some examples, the UCI may include a scheduling request (SR), i.e., a request to the scheduling entity to schedule uplink transmissions. In this document, in response to the SR sent on the UCI, the scheduling entity may send downlink control information (DCI), which may schedule resources for uplink packet transmissions. The UCI may also include HARQ feedback, channel state feedback (CSF) (such as a CSI report), or any other appropriate UCI.

[0076] In addition to control information, one or more REs 406 (e.g., within the data region 414) may also be allocated for data traffic. Such data traffic may be carried on one or more traffic channels, such as for DL ​​transmissions, on a physical downlink shared channel (PDSCH); or for UL transmissions, on a physical uplink shared channel (PUSCH). In some examples, one or more REs 406 within the data region 414 may be configured to carry other signals, such as one or more SIBs and DMRS.

[0077] In an example of sidelink communication over a sidelink carrier via a PC5 interface, a control region 412 of a time slot 410 may include a physical sidelink control channel (PSCCH) including sidelink control information (SCI) sent by an initiating (transmitting) sidelink device (e.g., a Tx V2X device or other Tx UE) to a set of one or more other receiving sidelink devices (e.g., an Rx V2X device or other Rx UE). A data region 414 of the time slot 410 may include a physical sidelink shared channel (PSSCH) including sidelink data traffic sent by an initiating (transmitting) sidelink device in resources reserved by the transmitting sidelink device on the sidelink carrier via the SCI. Other information may also be sent via various REs 406 within the time slot 410. For example, HARQ feedback information may be sent from a receiving sidelink device to a transmitting sidelink device in a physical sidelink feedback channel (PSFCH) within the time slot 410.

[0078] Described above and Figure 1 and Figure 4 The channels or carriers illustrated in the figure are not necessarily all channels or carriers that can be utilized between the scheduling entity 108 and the scheduled entity 106, and a person skilled in the art will recognize that other channels or carriers may be utilized in addition to the channels or carriers illustrated, such as other business, control and feedback channels.

[0079] These physical channels described above are typically multiplexed and mapped to transport channels for processing at the medium access control (MAC) layer. The transport channels carry blocks of information called transport blocks (TBs). Based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission, the transport block size (TBS), which may correspond to the number of information bits, may be a controlled parameter.

[0080] In some aspects, the UE 106 may be configured to report power headroom. The power headroom may indicate the amount of remaining transmit power available to the UE 106 in addition to the transmit power used by the current transmission. For example, the network entity 108 may send RRC signaling or some other type of control signaling that indicates a set of parameters for power headroom reporting. In some aspects, the power headroom reporting configuration may be indicated via an IE in the control signaling and configured across a set of one or more cells (e.g., indicated via a MAC-CellGroupConfig IE or some other IE). The parameters for power headroom reporting indicated via the power headroom reporting configuration (e.g., phr-Config) may include one or more timers for power headroom reporting, a threshold change in a power factor of a parameter for triggering PHR report transmission (e.g., phr-Tx-PowerFactorChange), an indication of the format or number of fields in the power headroom report (e.g., multiplePHR), a type of power headroom report (e.g., phr-Type2OtherCell), a mode of power headroom reporting (e.g., phr-ModeOtherCG), a configuration for maximum permissible exposure (MPE) reporting (e.g., mpe-Reporting-FR2-r16), one or more other parameters, or any combination thereof. The timers for power headroom reporting may include a periodic timer (e.g., phr-PeriodicTimer) indicating a periodicity at which the UE 106 may transmit a power headroom report, a prohibit timer (e.g., phr-ProhibitTimer) indicating a duration after which the UE 106 may refrain from transmitting a power headroom report, or both. The configuration for MPE reporting may indicate a timer (eg, mpe-ProhibitTimer-r16), a threshold for MPE reporting, or both.

[0081] The UE 106 receiving the power headroom report configuration may send one or more power headroom reports to the network entity 108 according to the parameters indicated via the power headroom report configuration. Each power headroom report may be sent via a medium access control (MAC) control element (CE) (or MAC-CE) or some other uplink message. In some cases, the power headroom MAC-CE may include multiple fields for indicating power headroom parameters. The headroom field in the power headroom MAC-CE may include a first number of bits (e.g., six bits or some other number of bits) for indicating the power headroom of a given component carrier. In some aspects, Table 1 includes example values ​​of power headroom levels that may be indicated via the headroom field (e.g., a range of 64 power headroom levels), and Table 2 includes an example mapping between values ​​reported via the power headroom MAC-CE and a measurement of power headroom in decibels (dB).

[0082] Power Headroom Power headroom level 0 POWER_HEADROOM_0 1 POWER_HEADROOM_1 2 POWER_HEADROOM_2 3 POWER_HEADROOM_3 … … 60 POWER_HEADROOM_60 61 POWER_HEADROOM_61 62 POWER_HEADROOM_62 63 POWER_HEADROOM_63

[0083] Table 1: Power headroom levels for power headroom reporting

[0084] Reported Value Measured value (dB) POWER_HEADROOM_0 PH<-32 POWER_HEADROOM_1 -32≤PH<-31 POWER_HEADROOM_2 -31≤PH<-30 POWER_HEADROOM_3 -30≤PH<-29 … … POWER_HEADROOM_53 20≤PH<21 POWER_HEADROOM_54 21≤PH<22 POWER_HEADROOM_55 22≤PH<24 POWER_HEADROOM_56 24≤PH<26 POWER_HEADROOM_57 26≤PH<28 POWER_HEADROOM_58 28≤PH<30 POWER_HEADROOM_59 30≤PH<32 POWER_HEADROOM_60 32≤PH<34 POWER_HEADROOM_61 34≤PH<36 POWER_HEADROOM_62 36≤PH<38 POWER_HEADROOM_63 PH≥38

[0085] Table 2: Power Headroom Report Mapping

[0086] A second field in the Power Headroom MAC-CE may include a number of bits (e.g., six bits or some other number of bits) configured to indicate the amount of power available for transmission by UE 106 on a given component carrier and a given serving cell, which may be determined by a parameter P CMAX,f,c , where f may correspond to (eg, point to) a carrier and c may correspond to (eg, point to) a serving cell. CMAX,f,c It can be relatively fine-grained information. For example, in some cases, P CMAX,f,c The most granular information (e.g., 1 dB resolution) related to the amount of available transmit power at the UE 106 that the UE 106 can provide to the network entity 108. In some aspects, Table 3 includes the P in the second field that can be included in the power headroom MAC-CE. CMAX,f,c , and Table 4 includes example values ​​of P in the power headroom MAC-CE CMAX,f,c The value reported in the field is the same as the P value in decibels per milliwatt (dBm). CMAX,f,c Example mapping between measurements of .

[0087]

[0088]

[0089] Table 3: Nominal UE transmit power levels for power headroom reporting

[0090] Reported Value Measured value unit PCMAX_C_00 <![CDATA[P CMAX,f,c <-29]]> dBm PCMAX_C_01 <![CDATA[-29≤P CMAX,f,c <-28]]> dBm PCMAX_C_02 <![CDATA[-28≤P CMAX,f,c <-27]]> dBm … … … PCMAX_C_61 <![CDATA[-31≤P CMAX,f,c <-32]]> dBm PCMAX_C_62 <![CDATA[-32≤P CMAX,f,c <-33]]> dBm PCMAX_C_63 <![CDATA[-33≤P CMAX,f,c ]]> dBm

[0091] Table 4: P CMAX,f,c Mapping

[0092] UE 106 may set P within the following limits: CMAX,f,c The value of (e.g., the maximum output power configured for a given carrier f and serving cell c): P CMAXL,f,c ≤P CMAX.f,c ≤P CMAXH,f,c , where P CMAX L,f,c and P CMAX H,f,c The UE 106 may determine the maximum transmit power (e.g., P) configured by the network entity 108 for the UE 106 based on one or more defined parameters. EMAX), the maximum transmit power configured by the network entity 108 for the UE 106 in a given serving cell c (e.g., P EMAX,c ), a maximum power determined based on the power class of UE 106 (e.g., P PowerClass ), a change or increment in maximum power associated with the power class of UE 106 (eg, ΔP PowerClass ), a maximum power reduction (MPR) parameter, one or more other parameters configured for UE 106, or any combination thereof.

[0093] UE 106 can be based on P CMAX,f,c The value of and determines the transmit power to be used for transmitting uplink transmissions (e.g., physical uplink shared channel (PUSCH) transmissions) in the active uplink bandwidth part (BWP) b in component carrier f and serving cell c according to Formula 1 below.

[0094]

[0095] In the example of Formula 1, j may correspond to a parameter set index, l may correspond to a PUSCH power control adjustment state index, and i may correspond to a transmission opportunity index. CMAX,f,c The maximum power level that UE 106 can use to send uplink transmissions in a given transmission opportunity is determined by the value of

[0096] The power headroom field in the power headroom report sent by the UE 106 may indicate the maximum power per carrier, P CMAX,f,c and the transmit power P used by UE 106 on a given carrier PUSCH,b,f,c (i,j,q d ,l). For example, for each component carrier, the power headroom field may be based on Formula 2.

[0097] PH(i,j,q d ,l)=P CMAXf,c -P PUSCH,b,f,c (i,j,q d ,l) Formula (2)

[0098] The P field in the MAC-CE may indicate whether MPE information is being reported by the UE 106. If the P field is set to 1 and MPE reporting is configured via a power headroom reporting configuration for the UE 106, the UE 106 may indicate the applied power backoff (e.g., power management MPR (P-MPR) level) via the MPE field in the power headroom report to meet one or more MPE requirements for the UE 106. If the P field is not set to 1, if MPE reporting is not configured in the power headroom reporting configuration, if the UE 106 operates in a frequency band that does not support MPE reporting (e.g., frequency range 1 (FR1)), or any combination thereof, the MPE field may be a reserved field, which may be empty or a null value (e.g., R bits may be present). Table 5 includes example values ​​for the MPE field in the power headroom MAC-CE.

[0099] MPE Nominal UE transmit power level 0 P-MPR_00 1 P-MPR_01 2 P-MPR_02 3 P-MPR_03

[0100] Table 5: Effective power reduction of MPE P-MPR

[0101] The MAC entity at the UE 106 may set the P field based on the P-MPR level applied to meet the MPE requirement. For example, if the applied P-MPR value is less than a threshold value (e.g., P-MPR_00), the UE 106 may set the P field to 0. If the applied P-MPR value is greater than or the same as the threshold value, the UE 106 may set the P field to 1 and report the P-MPR value via the MPE field. If MPE reporting is not configured in the power headroom reporting configuration, or if the UE 106 operates in a frequency band that does not support MPE reporting (e.g., FR1), the P field may indicate whether power backoff is applied for power management. If the power backoff applied for power management affects P CMAX,f,c field, the P field may be set to 1. The P field may otherwise be set to 0.

[0102] The UE 106 may thus receive a power headroom reporting configuration including one or more parameters for a power headroom report, and the UE 106 may send one or more power headroom reports, each of which includes one or more bit fields to convey a power headroom measurement or parameter, such as the examples illustrated in Tables 1 to 5. Each power headroom report may indicate a headroom parameter for a corresponding component carrier. For example, P, power headroom, MPE, and P CMAX,f,c The bit value in each of the fields may be associated with communication on a single component carrier. In such a case, the UE 106 may send a power headroom report via each component carrier configured for communication at the UE 106.

[0103] Additionally or alternatively, the UE 106 may generate and send a power headroom report that reports the power headrooms of more than two component carriers. For example, a combined power headroom report may include separate fields for reporting per-carrier power headroom information. An example combined power headroom report is shown in Table 6, which includes a bitmap to indicate which component carrier power headroom is being reported (using C1 to C7); an indication of whether power backoff is being applied (using the P field); an indication of whether the corresponding power headroom report is real or virtual (using the V field); a reserved field represented by the R field; and a power headroom report.

[0104]

[0105] Table 6: Multi-entry Power Headroom MAC-CE

[0106] In some systems, the UE 106 may report a power headroom on a per-carrier basis, as described with reference to Tables 1-5 and Equation 2, and the UE 106 may not report a maximum output power across multiple component carriers. In such cases, the network entity 108 communicating with the UE 106 may not be aware of the transmit power constraints at the UE 106. For example, the UE 106 may report a headroom for a maximum output power per carrier (e.g., the amount of remaining power available for communication), but may not report a headroom for a total maximum output power across multiple carriers.

[0107] For DL ​​communications, the UE may be configured with DL carrier aggregation (CA) across multiple carriers in different frequency bands. On the other hand, for UL communications, the UE is typically configured with a single carrier. For DL ​​communications using DL CA, the UE monitors and takes measurements across different carriers to ensure that DL reception remains robust. However, these measurements are not used for UL communications in at least some of these carriers because the UE is typically not configured to use carrier aggregation across these carriers for UL communications.

[0108] The UE may sometimes determine that scheduling UL transmissions in a carrier different from the configured carrier that is configured for UL may be better for the network than using the configured carrier for UL transmissions. The UE's knowledge of regulatory constraints on RF exposure may play a role in determining the amount of power that the UE is able to deliver on a particular carrier. The amount of power that the UE is able to deliver on a particular carrier may vary over time and across different carriers, for example, based on how much RF exposure has occurred. Rather than having a network entity select a carrier for the UL based solely on path loss information, it may be beneficial to have the UE also report the amount of power available in each carrier so that the network entity can consider both the path loss information and the amount of power available in each carrier to determine which carrier is best for the UL. Therefore, it may be advantageous to provide additional signaling that allows the network entity to be aware of the power available for the UL in unconfigured carriers through power headroom reporting and / or through energy headroom reporting.

[0109] According to some aspects of the present disclosure, a UE (e.g., UE 106) may send a power headroom report (PHR) including first power headroom information about a configured carrier configured for UL and second power headroom information about at least one unconfigured carrier not configured for UL, so that a network entity (e.g., network entity 108) may receive the PHR and select one of the configured carrier and the at least one unconfigured carrier based on the PHR. For example, the network entity may select a carrier whose power headroom information indicates the most UE transmit power available for UL from the configured carrier and the at least one unconfigured carrier. In one aspect, the unconfigured carrier may be a carrier that does not have an active uplink BWP or is not provided with an uplink configuration or a PUSCH configuration. After selecting a carrier based on the PHR, the network entity may send a message indicating the selected carrier to the UE. In one aspect, the message indicating the selected carrier may be sent via an RRC configuration message. When the UE receives the message indicating the selected carrier, the UE may use the selected carrier to send UL communications. In one aspect, the selected carrier may be a configured carrier or an unconfigured carrier in the at least one unconfigured carrier.

[0110] In one aspect, the first power headroom information about the configured carrier may be based on an actual PUSCH transmission that occurred on the configured carrier. In another aspect, the second power headroom information about the at least one unconfigured carrier may be based on a reference PUSCH transmission on each of the at least one unconfigured carrier. Because no actual UL or PUSCH transmission occurs on the unconfigured carrier, a reference (or virtual) PUSCH transmission may be assumed for the at least one unconfigured carrier to determine the second power headroom information for the at least one unconfigured carrier for the PHR. For example, the use of the reference PUSCH transmission may involve estimating how power could be used if the actual PUSCH transmission had occurred on the unconfigured carrier.

[0111] Figure 5 is an example diagram illustrating communications between a user equipment (UE) and a network entity using various carriers according to some aspects. Figure 5 As shown, UE 502 and network entity 504 may communicate with each other using one or more of carriers including first carrier 522, second carrier 524, third carrier 526, and fourth carrier 528. In some aspects, UE 502 may be Figure 1 UE 106, and the network entity 504 may be Figure 1 network entity 108.

[0112] For DL ​​communications, DL carrier aggregation across the first carrier 522, the second carrier 524, the third carrier 526, and the fourth carrier 528 may be configured. On the other hand, for UL communications, only a single carrier, such as the first carrier 522, may be configured. For the first carrier 522 configured for UL, the UE 502 transmits a PUSCH on the first carrier 522 at a specific power level, and thus may determine first power headroom information for the PHR to indicate how much additional power is available at the UE. However, because no actual UL transmission occurs on the second carrier 524, the third carrier 526, and the fourth carrier 528 that are not configured for UL, no PUSCH is transmitted on these three unconfigured carriers. Therefore, a reference (or virtual) PUSCH transmission may be assumed for the second carrier 524, the third carrier 526, and the fourth carrier 528 to determine second power headroom information for these three unconfigured carriers for the PHR.

[0113] When the network entity 504 receives the PHR from the UE 502, the network entity may select a carrier including one of the first carrier 522, the second carrier 524, the third carrier 526, and the fourth carrier 528 based on the PHR, and transmit a message indicating the selected carrier. When the UE 502 receives the message indicating the selected carrier, the UE 502 may use the selected carrier for UL transmission. For example, if the network entity 504 selects the second carrier 524 after considering the power headroom information for the four carriers based on the PHR, the network entity 504 may transmit a message indicating the second carrier 524 to the UE 502, and the UE 502 will use the second carrier 524 for UL transmission based on the message.

[0114] In one aspect, the UE may periodically send the PHR based on a specific periodicity. In this aspect, the periodicity may be based on the periodicity of a carrier different from the configured carrier. For example, the periodicity may match the periodicity of a carrier different from the configured carrier. For example, referring to Figure 5, the periodicity for sending the PHR may match the periodicity of one of the second carrier 524, the third carrier 526, and the fourth carrier 528 that is different from the first carrier 522 configured for UL. In an aspect, the network entity may send a PHR configuration (e.g., phr-Config) indicating the periodicity to the UE, where the PHR configuration may be provided via an RRC message.

[0115] In one aspect, the UE may send the PHR after receiving the PHR request from the network entity. In an example, the network entity may send the PHR request to the UE via MAC-CE or DCI. In this aspect, the network entity may send the PHR request in response to the signal strength at the network entity being lower than a network entity signal strength threshold and / or in response to a load parameter on a configured carrier exceeding a carrier load threshold. In some examples, if the radio condition of the configured carrier supporting the UL deteriorates (e.g., the signal strength at the network entity drops below the network entity signal strength threshold), the network may attempt to find a better carrier supporting the UL communication by sending a PHR request to the UE. In some examples, if the network entity determines that the configured carrier is overloaded (e.g., the load parameter on the configured carrier exceeds the carrier load threshold), the network may attempt to find another carrier that can better support the UL communication by sending a PHR request to the UE.

[0116] In an aspect, the UE may send a PHR in response to a triggering event. Examples of triggering events are described below.

[0117] In one aspect, the triggering event may be that the path loss of the configured carrier exceeds a path loss threshold. In the example where the path loss threshold is 100 dB, the path loss of the configured carrier exceeding 100 dB may indicate that the network entity is too stressed to perform UL.

[0118] In one aspect, the triggering event may be that the signal strength of the configured carrier drops below a UE signal strength threshold. In an example, the signal strength may be represented by a reference signal received power (RSRP). Thus, if the configured carrier becomes weak or undesirable, the UE may let the network entity know of the condition by sending a PHR.

[0119] On the one hand, the trigger event may be that the available power (or energy) in one of the at least one unconfigured carriers exceeds the available power threshold. In the example, the available power threshold may be an absolute threshold or a relative threshold relative to the available power in the configured carrier. In the example using the absolute threshold, if the available power in the unconfigured carrier exceeds the available power threshold, the trigger event occurs. In the example using the relative threshold, if the available power in the unconfigured carrier is greater than the available power in the configured carrier by at least the relative threshold, the trigger event occurs. For example, assuming the relative threshold is 3dBm, if the available power that the UE can deliver on the configured carrier is 18dBm and the available power on the unconfigured carrier is 23dBm, the trigger event occurs because the available power in the unconfigured carrier is greater than the available power in the configured carrier by at least the relative threshold of 3dBm. On the other hand, in this example, if the available power that the UE can deliver on the configured carrier is 18dBm and the available power on the unconfigured carrier is 19dBm, the trigger event does not occur because the available power in the unconfigured carrier is not greater than the available power in the configured carrier by at least the relative threshold of 3dBm.

[0120] In one aspect, the triggering event may be that the P-MPR backoff for one of the at least one unconfigured carriers is below a backoff threshold. In the example where the backoff threshold is 3 dB, if the UE is capable of transmitting at 20 dB on the unconfigured carrier but is set to transmit at 18 dB, the P-MPR backoff is 2 DB, which is below the backoff threshold, and thus the triggering event occurs.

[0121] In one aspect, the first power headroom information may include one or more of a first maximum UE output power for a configured carrier, a first power management maximum power reduction value (or a first P-MPR), and a first power headroom value. In one aspect, the second power headroom information may include one or more of a second maximum UE output power for each of at least one unconfigured carrier, a second power management maximum power reduction value (or a second P-MPR), and a second power headroom value, respectively. The maximum UE output power may be referred to as P CMAX .

[0122] In one aspect, the second power headroom value may be based on the second maximum UE output power, the second power management maximum power reduction value, the open-loop transmit power based on the open-loop power control, and the path loss. In this aspect, the open-loop transmit power is based on an open-loop nominal power parameter set to a predefined default value and an open-loop UE power parameter set to 0 for at least one unconfigured carrier. The open-loop transmit power for PUSCH transmission may be referred to as P O_PUSCH .

[0123] In some aspects, for PUSCH transmission opportunity i, with active UL BWPb for carrier f of serving cell c, the power headroom (PH) value of the unconfigured carrier may be calculated according to the following formula 3. As discussed above, the PH value of the unconfigured carrier may be determined based on a reference PUSCH transmission.

[0124]

[0125] On the one hand, P CMAX,b,f,c P may represent the maximum configured power determined by the UE after taking into account P-MPR backoff and other backoffs. P may be calculated assuming that MPR is 0 dB, A-MPR is 0 dB, and P-MPR is allowed to be non-zero. CMAX,b,f,c If the P-MPR is non-zero, the UE reports the P-MPR to the network entity. In some aspects, ΔT c Can be set to 0dB.

[0126] On the one hand, Or the open-loop transmit power for PUSCH transmission may indicate the transmit power for PUSCH transmission calculated by the open-loop power control. Can include P O_NOMINAL_PUSCH and P O_UE_PUSCH .P O_NOMINAL_PUSCH +P O_UE_PUSCH The PUSCHPowerContro may be determined based on one or more parameters including preambleReceivedTargetPower, msg3-DeltaPreamble, ConfiguredGrantConfig, p0-NominalWithoutGrant, p0-PUSCH-Alpha, p0-PUSCH-AlphaSet, SRI-PUSCHPowerContro, and SRS Resource Indicator (SRI) fields in DCI format 0_0 / 0_1. O_NOIINAL_PUSCH It may depend on other configuration parameters that are unlikely to be used for unconfigured carriers, but these configuration parameters are usually available for configured carriers. Therefore, in the case where these configuration parameters are not available to the UE, P O_NOMINAL_PUSCH can be set to a default value. In one aspect, P O_UE_PUSCH It can be managed by p0-PUSCH-Alpha and associated parameters. In this regard, for unconfigured carriers, P O_UE_PUSCH Can be set to 0.

[0127] On the one hand, α b,f,c It can represent the parameter governing the fractional path loss compensation. b,f,c The amount of path loss to be compensated can be controlled. For a configured carrier, α b,f,cCan be set to 0. For example, α b,f,c can be set to p0-PUSCH-AlphaSetId, which is 0 for configured carriers. On the other hand, for unconfigured carriers, α b,f,c Can be set to 1.

[0128] On the one hand, PL b,f,c PL may represent the path loss, which may be determined by the UE via downlink measurements. b,f,c It can be calculated using pusch-PathlossReferenceRS-Id, which is 0 for configured carriers. For unconfigured carriers, SSB (default SSB) can be used to calculate PL b,f,c .

[0129] On the one hand, f b,f,c It can represent the accumulated transmit power control (TPC) command. For unconfigured carriers, f b,f,c Can be set to 0.

[0130] In some aspects, the UE may use a multi-entry PHR MAC-CE to send a PHR. For example, the multi-entry PHR MAC-CE may be used to report both first power headroom information for a configured carrier and second power headroom information for at least one unconfigured carrier. An example of a multi-entry PHR MAC-CE is shown in Table 6 below.

[0131] When no PUSCH path loss reference is given, the UE may utilize the SSB from which the MIB is obtained as a reference. In some aspects, when a field for PUCCH power control (e.g., PUCCH-powerControl information element) is not configured, the UE may utilize the SSB as a reference signal for reporting PHR for unconfigured carriers.

[0132] Figure 6 is an example flow diagram illustrating features performed by a UE and a network entity according to some aspects. Figure 6 As shown, UE 602 and network entity 604 can communicate with each other to perform features of various aspects. In some aspects, UE 602 can be Figure 1 UE 106, and the network entity 604 may be Figure 1 In some aspects, the UE 602 may be a network entity 108. Figure 5 UE 502, and the network entity 604 may be Figure 5 network entity 504.

[0133] At 614, the UE 602 may send a PHR, and the network entity 604 may receive the PHR, the PHR including first power headroom information for configured carriers configured for uplink communication and second power headroom information for at least one unconfigured carrier that is not configured for uplink communication. In some aspects, the UE 602 may send the PHR at 614 when the UE 602 determines at 612 that a triggering event for the PHR has occurred or receives a PHR request from the network entity 604. In some aspects, the UE 602 may periodically send the PHR at 614 based on a periodicity.

[0134] At 616, the network entity 604 may select a carrier including one of a configured carrier and at least one unconfigured carrier based on the PHR.

[0135] At 618, the network entity 604 may send a message indicating the selected carrier, and the UE 602 may receive the message.

[0136] At 620, UE 602 may send an uplink transmission, such as a PUSCH transmission, to network entity 604 via the selected carrier.

[0137] Figure 7 7 is a block diagram illustrating an example of a hardware implementation for a scheduled entity 700 employing a processing system 714. For example, the scheduled entity 700 may be Figure 1 , Figure 2 , Figure 3 , Figure 5 and / or Figure 6 In another example, the scheduled entity 700 may be a UE as illustrated in any one or more of Figure 1 , Figure 2 and / or Figure 3 A base station as illustrated in any one or more of .

[0138] The scheduled entity 700 may be implemented using a processing system 714 including one or more processors 704. Examples of processor 704 include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic components, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout this disclosure. In various examples, the scheduled entity 700 may be configured to perform any one or more of the functions described herein. That is, the processor 704 as utilized in the scheduled entity 700 may be used to implement the functions described below and in Figure 8 Any one or more of the processes and procedures illustrated in .

[0139] In this example, the processing system 714 can be implemented using a bus architecture, which is generally represented by bus 702. Bus 702 may include any number of interconnecting buses and bridges, depending on the specific application of the processing system 714 and the overall design constraints. Bus 702 communicatively couples various circuits including one or more processors (generally represented by processor 704), memory 705, and computer-readable media (generally represented by computer-readable storage media 706). Bus 702 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be further described. Bus interface 708 provides an interface between bus 702 and transceiver 710. Transceiver 710 provides a communication interface or component for communicating with various other devices through a transmission medium. Depending on the nature of the device, a user interface 712 (e.g., a keypad, display, speaker, microphone, joystick) may also be provided. Of course, such a user interface 712 is optional and may be omitted in some examples (such as a base station).

[0140] In some aspects of the present disclosure, the processor 704 may include a PHR management circuit 740 configured for various functions, including, for example, sending a PHR to a network entity, the PHR including first power headroom information for a configured carrier configured for uplink communication and second power headroom information for at least one unconfigured carrier not configured for uplink communication. For example, the PHR management circuit 740 may be configured to implement the following regarding Figure 8 (including, for example, block 802) one or more of the functions described.

[0141] In some aspects of the present disclosure, the processor 704 may include a communication management circuit 742 configured for various functions, including, for example, receiving a message indicating a selected carrier from a network entity in response to a PHR, the selected carrier including one of a configured carrier and at least one unconfigured carrier. For example, the communication management circuit 742 may be configured to implement the following description of Figure 8 (including, for example, block 804) one or more of the functions described.

[0142] In some aspects of the present disclosure, the processor 704 may include a carrier management circuit 744 configured with a communication management circuit 742 for various functions, including, for example, sending an uplink transmission to a network entity via a selected carrier. For example, the carrier management circuit 744 with the communication management circuit 742 may be configured to implement the following description of Figure 8 (including, for example, block 806) one or more of the functions described.

[0143] The processor 704 is responsible for managing the bus 702 and general processing, including executing software stored on the computer-readable storage medium 706. The software, when executed by the processor 704, causes the processing system 714 to perform the various functions described below for any particular device. The computer-readable storage medium 706 and the memory 705 may also be used to store data that is manipulated by the processor 704 when executing the software.

[0144] One or more processors 704 in the processing system may execute software. Software should be construed broadly to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. The software may reside on a computer-readable storage medium 706. The computer-readable storage medium 706 may be a non-transitory computer-readable storage medium. By way of example, non-transitory computer-readable storage media include magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips), optical disks (e.g., compact disks (CDs) or digital versatile disks (DVDs)), smart cards, flash memory devices (e.g., card, stick, or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. The computer-readable storage medium 706 may reside in the processing system 714, external to the processing system 714, or distributed across multiple entities including the processing system 714. The computer-readable storage medium 706 may be embodied in a computer program product. By way of example, a computer program product may include a computer-readable storage medium in packaging materials. Those skilled in the art will recognize how to best implement the described functionality presented throughout this disclosure, depending on the specific application and the overall design constraints imposed on the overall system.

[0145] In some aspects of the present disclosure, the computer-readable storage medium 706 may include PHR management software / instructions 760 configured for various functions, including, for example, sending a PHR to a network entity, the PHR including first power headroom information for a configured carrier configured for uplink communication and second power headroom information for at least one unconfigured carrier not configured for uplink communication. For example, the PHR management software / instructions 760 may be configured to implement the following description of Figure 8 (including, for example, block 802) one or more of the functions described.

[0146] In some aspects of the present disclosure, the computer-readable storage medium 706 may include communication management software / instructions 762 configured for various functions, including, for example, receiving a message indicating a selected carrier from a network entity in response to a PHR, the selected carrier including one of a configured carrier and at least one unconfigured carrier. For example, the communication management software / instructions 762 may be configured to implement the following description of Figure 8 (including, for example, block 804) one or more of the functions described.

[0147] In some aspects of the present disclosure, the computer-readable storage medium 706 may include carrier management software / instructions 764 configured with communication management software / instructions 762 for various functions, including, for example, sending uplink transmissions to a network entity via a selected carrier. For example, the carrier management software / instructions 764 with communication management software / instructions 762 may be configured to implement the following description of Figure 8 (including, for example, block 806) one or more of the functions described.

[0148] Figure 8 800 for wireless communication by a UE according to some aspects. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required for implementations of all embodiments. In some examples, process 800 may be performed by Figure 7 In some examples, process 800 may be performed by any suitable device or component for performing the functions or algorithms described below.

[0149] At block 802, the UE may send a PHR to a network entity, the PHR including first power headroom information for a configured carrier configured for uplink communication and second power headroom information for at least one unconfigured carrier not configured for uplink communication. Figure 7 The illustrated and described PHR management circuitry 740 may provide means for sending a PHR.In an aspect, the PHR may be sent via a multi-entry PHR MAC-CE.

[0150] In an aspect, the PHR may be sent periodically based on a periodicity, after receiving a PHR request from a network entity, or in response to a triggering event.

[0151] In an aspect, the periodicity may be based on a periodicity of a carrier different from the configured carrier. In an aspect, the PHR request may be received in response to at least one of the following: a signal strength at the network entity is less than a network entity signal strength threshold, or a load parameter on the configured carrier exceeds a carrier load threshold. In an aspect, the triggering event may include at least one of the following: a path loss of the configured carrier exceeds a path loss threshold, a signal strength of the configured carrier drops below a UE signal strength threshold, an available power in one of the at least one unconfigured carrier exceeds an available power threshold, an available power in one of the at least one unconfigured carrier exceeds an available power in the configured carrier by at least relative to an available power threshold, or a P-MPR backoff for one of the at least one unconfigured carrier is less than a backoff threshold.

[0152] In an aspect, the first power headroom information is sent based on a PUSCH on a configured carrier, and the second power headroom information is sent based on a reference PUSCH on each of the at least one unconfigured carrier.

[0153] In one aspect, the first power headroom information includes one or more of a first maximum UE output power, a first power management maximum power reduction value, and a first power headroom value for a configured carrier, and the second power headroom information includes one or more of a second maximum UE output power, a second power management maximum power reduction value, and a second power headroom value for each of at least one unconfigured carrier, respectively. In one aspect, the second power headroom value is based on the second maximum UE output power, the second power management maximum power reduction value, an open-loop transmit power based on open-loop power control, and a path loss. In one aspect, the open-loop transmit power is based on an open-loop nominal power parameter set to a predefined default value and an open-loop UE power parameter set to 0 for at least one unconfigured carrier.

[0154] At block 804, the UE may receive a message from a network entity in response to the PHR indicating a selected carrier, the selected carrier including one of a configured carrier and at least one unconfigured carrier. Figure 7 The illustrated and described communications management circuitry 742 may provide means for receiving the message. In an aspect, the UE receiving the message at block 804 may include receiving an RRC configuration message indicating the selected carrier.

[0155] At block 806, the UE may send an uplink transmission to the network entity via the selected carrier. Figure 7 The carrier management circuitry 744 shown and described with the communication management circuitry 742 may provide means for transmitting uplink transmissions.

[0156] In one configuration, a UE / scheduled entity 700 for wireless communication includes: means for sending a PHR to a network entity, the PHR including first power headroom information for a configured carrier configured for uplink communication and second power headroom information for at least one unconfigured carrier not configured for uplink communication; means for receiving a message indicating a selected carrier from the network entity in response to the PHR, the selected carrier including one of the configured carrier and the at least one unconfigured carrier; and means for sending an uplink transmission to the network entity via the selected carrier. In one aspect, the aforementioned means may be in Figure 7 The processor 704 shown in FIG. 7 is configured to perform the functions described by the aforementioned components. On the other hand, the aforementioned components may be a circuit or any device configured to perform the functions described by the aforementioned components.

[0157] Of course, in the above examples, the circuits included in the processor 704 are provided only as examples, and other components for performing the described functions may be included in various aspects of the present disclosure, including but not limited to instructions stored in the computer-readable storage medium 706 or in Figure 1 , Figure 2 , Figure 3 , Figure 5 and / or Figure 6 Any of the descriptions and use of the foregoing Figure 8 Any other suitable means or components of the described processes and / or algorithms.

[0158] Fig. 9 904. Figure 1 , Figure 2 , Figure 3 , Figure 5 and / or Figure 6 A network entity or base station as illustrated in any one or more of .

[0159] The processing system 914 can be used with Figure 7 The processing system 714 illustrated in FIG. 1 is substantially the same as the processing system 714 illustrated in FIG. 1 , which includes a bus interface 908, a bus 902, a memory 905, a processor 904, and a computer-readable storage medium 906. Depending on the nature of the device, a user interface 912 (e.g., a keypad, a display, a speaker, a microphone, a joystick) may also be provided. In addition, the network entity may include the same as described above in Figure 7That is, the processor 904 as utilized in the network entity may be used to implement the following description and in Fig.10 Any one or more of the processes illustrated in .

[0160] In some aspects of the present disclosure, the processor 904 may include a PHR processing circuit 940 configured for various functions, including, for example, receiving a PHR from a UE, the PHR including first power headroom information for a configured carrier configured for uplink communication and second power headroom information for at least one unconfigured carrier not configured for uplink communication. For example, the PHR processing circuit 940 may be configured to implement the following description of Fig.10 (including, for example, block 1002) one or more of the functions described.

[0161] In some aspects of the present disclosure, the processor 904 may include a carrier management circuit 942 configured for various functions, including, for example, selecting a carrier including one of a configured carrier and at least one unconfigured carrier based on the PHR. For example, the carrier management circuit 942 may be configured to implement the following Fig.10 (including, for example, block 1004) one or more of the functions described.

[0162] In some aspects of the present disclosure, the processor 904 may include a communication management circuit 944 configured for various functions, including, for example, sending a message indicating the selected carrier to the UE. For example, the communication management circuit 944 may be configured to implement the following Fig.10 (including, for example, block 1006) one or more of the functions described.

[0163] In some aspects of the present disclosure, the communication management circuit 944 may be configured for various functions, including, for example, receiving uplink transmissions from a UE via a selected carrier. For example, the communication management circuit 944 may be configured to implement the following description of Fig.10 (including, for example, block 1008) One or more of the functions described.

[0164] In some aspects of the present disclosure, the computer-readable storage medium 906 may include PHR processing software / instructions 960 configured for various functions, including, for example, receiving a PHR from a UE, the PHR including first power headroom information for a configured carrier configured for uplink communication and second power headroom information for at least one unconfigured carrier not configured for uplink communication. For example, the PHR processing software / instructions 960 may be configured to implement the following description of Fig.10 (including, for example, block 1002) one or more of the functions described.

[0165] In some aspects of the present disclosure, the computer-readable storage medium 906 may include carrier management software / instructions 962 configured for various functions, including, for example, selecting a carrier including one of a configured carrier and at least one unconfigured carrier based on a PHR. For example, the carrier management software / instructions 962 may be configured to implement the following description of Fig.10 (including, for example, block 1004) one or more of the functions described.

[0166] In some aspects of the present disclosure, the computer-readable storage medium 906 may include communication management software / instructions 964 configured for various functions, including, for example, sending a message to the UE indicating the selected carrier. For example, the communication management software / instructions 964 may be configured to implement the following description of Fig.10 (including, for example, block 1006) one or more of the functions described.

[0167] In some aspects of the present disclosure, the communication management software / instructions 964 may be configured for various functions, including, for example, receiving uplink transmissions from a UE via a selected carrier. For example, the communication management software / instructions 964 may be configured to implement the following description of Fig.10 (including, for example, block 1008) One or more of the functions described.

[0168] Fig.10 is a flow chart illustrating an exemplary process 1000 for wireless communication by a network entity according to some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required for implementations of all embodiments. In some examples, process 1000 may be performed by Fig. 9 In some examples, process 1000 may be performed by any suitable device or component for performing the functions or algorithms described below.

[0169] At block 1002, a network entity may receive a PHR from a UE, the PHR including first power headroom information for a configured carrier configured for uplink communication and second power headroom information for at least one unconfigured carrier not configured for uplink communication. Fig. 9 The illustrated and described PHR processing circuitry 940 may provide means for receiving a PHR.In an aspect, the PHR may be received via a multi-entry PHR MAC-CE.

[0170] In an aspect, the PHR may be received periodically based on a periodicity, received in response to a PHR request being sent to the UE, or received in response to a triggering event.

[0171] In an aspect, the periodicity may be based on a periodicity of a carrier different from the configured carrier. In an aspect, the triggering event may include at least one of the following: a path loss of the configured carrier exceeds a path loss threshold, a signal strength of the configured carrier drops below a signal strength threshold, an available power in one of the at least one unconfigured carriers exceeds an absolute available power threshold, an available power in one of the at least one unconfigured carriers exceeds an available power in the configured carrier by at least a relative available power threshold, or a P-MPR backoff for one of the at least one unconfigured carriers is below a backoff threshold.

[0172] In an aspect, the PHR request may be sent in response to at least one of: a signal strength at the network entity being below a network entity signal strength threshold, or a load parameter on a configured carrier exceeding a carrier load threshold.

[0173] In one aspect, the first power headroom information includes one or more of a first maximum UE output power, a first power management maximum power reduction value, and a first power headroom value for a configured carrier, and the second power headroom information includes one or more of a second maximum UE output power, a second power management maximum power reduction value, and a second power headroom value for each of at least one unconfigured carrier, respectively. In one aspect, the second power headroom value is based on the second maximum UE output power, the second power management maximum power reduction value, an open-loop transmit power based on open-loop power control, and a path loss. In one aspect, the open-loop transmit power is based on an open-loop nominal power parameter set to a predefined default value and an open-loop UE power parameter set to 0 for at least one unconfigured carrier.

[0174] At block 1004, the network entity may select a carrier including one of a configured carrier and at least one unconfigured carrier based on the PHR. Fig. 9 The carrier management circuit 942 shown and described may provide means for selecting a carrier.

[0175] At block 1006, the network entity may send a message to the UE indicating the selected carrier. Fig. 9 The illustrated and described communications management circuitry 944 may provide means for sending the message.In an aspect, the network entity sending the message at block 1006 may include sending an RRC configuration message indicating the selected carrier.

[0176] At block 1008, the network entity may receive an uplink transmission from the UE via the selected carrier. Fig. 9 The communications management circuitry 944 shown and described may provide means for receiving uplink transmissions.

[0177] In one configuration, a network entity 900 for wireless communication includes: a component for receiving a PHR from a UE, the PHR including first power headroom information for a configured carrier configured for uplink communication and second power headroom information for at least one unconfigured carrier that is not configured for uplink communication; a component for selecting a carrier including one of the configured carrier and the at least one unconfigured carrier based on the PHR; a component for sending a message indicating the selected carrier to the UE; and a component for receiving an uplink transmission from the UE via the selected carrier. In one aspect, the aforementioned components may be in Fig. 9 The processor 904 shown in the figure is configured to perform the functions described by the aforementioned components. On the other hand, the aforementioned components can be a circuit or any device configured to perform the functions described by the aforementioned components.

[0178] Of course, in the above examples, the circuits included in the processor 904 are provided only as examples, and other components for performing the described functions may be included in various aspects of the present disclosure, including but not limited to instructions stored in the computer-readable storage medium 906 or in Figure 1 , Figure 2 , Figure 3 , Figure 5 and / or Figure 6 Any of the descriptions and use of the foregoing Fig.10 Any other suitable means or components of the described processes and / or algorithms.

[0179] A summary of several aspects of the disclosure is provided below.

[0180] Aspect 1: A method for wireless communication by a user equipment (UE), the method comprising: sending a power headroom report (PHR) to a network entity, the power headroom report (PHR) comprising first power headroom information for a configured carrier configured for uplink communication and second power headroom information for at least one unconfigured carrier not configured for uplink communication; receiving a message indicating a selected carrier from the network entity in response to the PHR, the selected carrier comprising one of the configured carrier and the at least one unconfigured carrier; and sending an uplink transmission to the network entity via the selected carrier.

[0181] Aspect 2: The method of claim 1, wherein receiving the message comprises receiving a radio resource control (RRC) configuration message indicating the selected carrier.

[0182] Aspect 3: The method according to claim 1, wherein the PHR is sent periodically based on a periodicity, the PHR is sent after receiving a PHR request from the network entity, or the PHR is sent in response to a trigger event.

[0183] Aspect 4: The method of claim 3, wherein the triggering event comprises at least one of the following: a path loss of the configured carrier exceeds a path loss threshold, a signal strength of the configured carrier drops below a UE signal strength threshold, an available power in one of the at least one unconfigured carriers exceeds an available power threshold, an available power in one of the at least one unconfigured carriers exceeds the available power in the configured carrier by at least relative to an available power threshold, or a power management maximum power reduction (P-MPR) backoff for one of the at least one unconfigured carriers is below a backoff threshold.

[0184] Aspect 5: The method of claim 3, wherein the periodicity is based on a periodicity of a carrier different from the configured carrier.

[0185] Aspect 6: The method of claim 3, wherein the PHR request is received in response to at least one of the following: a signal strength at the network entity is lower than a network entity signal strength threshold, or a load parameter on the configured carrier exceeds a carrier load threshold.

[0186] Aspect 7: The method of claim 1, wherein the first power headroom information is sent based on a physical uplink shared channel (PUSCH) on the configured carrier, and wherein the second power headroom information is sent based on a reference PUSCH on each of the at least one unconfigured carrier.

[0187] Aspect 8: The method of claim 1, wherein the first power headroom information comprises one or more of a first maximum UE output power, a first power management maximum power reduction value, and a first power headroom value for the configured carrier, and wherein the second power headroom information comprises one or more of a second maximum UE output power, a second power management maximum power reduction value, and a second power headroom value for each of the at least one unconfigured carrier, respectively.

[0188] Aspect 9: The method of claim 8, wherein the second power headroom value is based on the second maximum UE output power, the second power management maximum power reduction value, an open-loop transmit power based on open-loop power control, and a path loss.

[0189] Aspect 10: The method of claim 9, wherein the open-loop transmit power is based on an open-loop nominal power parameter set to a predefined default value and an open-loop UE power parameter set to zero for the at least one unconfigured carrier.

[0190] Aspect 11: The method of claim 1, wherein the PHR is sent via a multi-entry PHR medium access control (MAC) control element (CE).

[0191] Aspect 12: A user equipment (UE), comprising: a transceiver configured to communicate with a radio access network; a memory; and a processor communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to perform any one of Aspects 1 to 11.

[0192] Aspect 13: A UE configured for wireless communication, the UE comprising at least one component for performing any one of aspects 1 to 11.

[0193] Aspect 14: A non-transitory computer-readable storage medium having instructions thereon for a UE, wherein the instructions, when executed by a processing circuit, cause the processing circuit to perform any one of aspects 1 to 11.

[0194] Aspect 15: A method for wireless communication by a network entity, the method comprising: receiving a power headroom report (PHR) from a user equipment (UE), the power headroom report (PHR) comprising first power headroom information for a configured carrier configured for uplink communication and second power headroom information for at least one unconfigured carrier that is not configured for uplink communication; selecting a carrier including one of the configured carrier and the at least one unconfigured carrier based on the PHR; sending a message indicating the selected carrier to the UE; and receiving an uplink transmission from the UE via the selected carrier.

[0195] Aspect 16: The method of claim 15, wherein sending the message comprises sending a radio resource control (RRC) configuration message indicating the selected carrier.

[0196] Aspect 17: The method of claim 15, wherein the PHR is received periodically based on a periodicity, is received in response to sending a PHR request to the UE, or is received in response to a triggering event.

[0197] Aspect 18: The method of claim 17, wherein the triggering event comprises at least one of the following: a path loss of the configured carrier exceeds a path loss threshold, a signal strength of the configured carrier drops below a signal strength threshold, an available power in one of the at least one unconfigured carriers exceeds an absolute available power threshold, an available power in one of the at least one unconfigured carriers exceeds the available power in the configured carrier by at least a relative available power threshold, or a power management maximum power reduction (P-MPR) backoff for one of the at least one unconfigured carriers is below a backoff threshold.

[0198] Aspect 19: The method of claim 17, wherein the periodicity is based on a periodicity of a carrier different from the configured carrier.

[0199] Aspect 20: The method of claim 17, wherein the PHR request is sent in response to at least one of the following: a signal strength at the network entity is lower than a network entity signal strength threshold, or a load parameter on the configured carrier exceeds a carrier load threshold.

[0200] Aspect 21: The method of claim 15, wherein the first power headroom information is sent based on a physical uplink shared channel (PUSCH) on the configured carrier, and wherein the second power headroom information is sent based on a reference PUSCH on each of the at least one unconfigured carrier.

[0201] Aspect 22: A method according to claim 15, wherein the first power headroom information includes one or more of a first maximum UE output power, a first power management maximum power reduction value, and a first power headroom value for the configured carrier, and wherein the second power headroom information respectively includes one or more of a second maximum UE output power, a second power management maximum power reduction value, and a second power headroom value for each of the at least one unconfigured carrier.

[0202] Aspect 23: The method of claim 22, wherein the second power headroom value is based on the second maximum UE output power, the second power management maximum power reduction value, an open-loop transmit power based on open-loop power control, and a path loss.

[0203] Aspect 24: The method of claim 23, wherein the open-loop transmit power is based on an open-loop nominal power parameter set to a predefined default value and an open-loop UE power parameter set to zero for the at least one unconfigured carrier.

[0204] Aspect 25: The method of claim 15, wherein the PHR is received via a multi-entry PHR medium access control (MAC) control element (CE).

[0205] Aspect 26: A network entity, comprising: a transceiver configured to communicate with a radio access network; a memory; and a processor communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to perform any one of aspects 15 to 25.

[0206] Aspect 27: A network entity configured for wireless communication, the network entity comprising at least one component for performing any one of aspects 15 to 25.

[0207] Aspect 28: A non-transitory computer-readable storage medium entity having thereon instructions for a network, wherein the instructions, when executed by a processing circuit, cause the processing circuit to perform any of aspects 15 to 25.

[0208] Several aspects of wireless communication networks have been presented with reference to exemplary implementations. As those skilled in the art will readily appreciate, various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures and communication standards.

[0209] By way of example, various aspects may be implemented within other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile (GSM). Various aspects may also be extended to systems defined by the Third Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolution-Data Optimized (EV-DO). Other examples may be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunication standard, network architecture, and / or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.

[0210] Within the present disclosure, the word "exemplary" is used to mean "serving as an example, instance, or illustration". Any specific implementation or aspect described herein as "exemplary" is not necessarily to be construed as superior or superior to other aspects of the present disclosure. Likewise, the term "aspect" does not require that all aspects of the present disclosure include the discussed features, advantages, or modes of operation. The term "coupled" is used herein to refer to a direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, objects A and C may still be considered to be coupled to each other, even if they are not in direct physical contact with each other. For example, a first object may be coupled to a second object, even if the first object has never been in direct physical contact with the second object. The terms "circuit" are used broadly, and they are intended to include both hardware implementations of electronic devices and conductors (where these electronic devices and conductors, when connected and configured, implement the execution of the functions described in the present disclosure, without limitation on the type of electronic circuits) and software implementations of information and instructions (where these information and instructions, when executed by a processor, implement the execution of the functions described in the present disclosure).

[0211] Figures 1 to 10 One or more of the components, steps, features, and / or functions illustrated in the present invention may be rearranged and / or combined into a single component, step, feature, or function or may be embodied in several components, steps, or functions. Additional elements, components, steps, and / or functions may also be added without departing from the novel features disclosed herein. Figures 1 to 10 The apparatus, device and / or components illustrated in the examples may be configured to perform one or more of the methods, features or steps described herein. The novel algorithms described herein may also be effectively implemented in software and / or embedded in hardware.

[0212] It should be understood that the specific order or hierarchy of steps in the disclosed methods is an illustration of an exemplary process. It should be understood that the specific order or hierarchy of steps in these methods can be rearranged based on design preferences. The attached method claims provide elements of various steps in an exemplary order, but are not intended to be limited to the specific order or hierarchy provided unless explicitly stated herein.

[0213] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the various aspects shown herein, but to conform to the full scope consistent with the text of the claims, wherein unless explicitly stated otherwise, reference to an element in the singular form is not intended to mean "one and only one", but "one or more". Unless otherwise specified, the term "some" refers to one or more. The phrase "at least one" of a list of items refers to any combination of those items, including a single member. As an example, "at least one of a, b, or c" is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are known or will be known later to a person of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. No claim element is to be construed under 35 USC §112(f) unless the element is expressly recited using the phrase “means for” or, in the case of a method claim, the phrase “step for.”

Claims

1. A method for wireless communication by a user equipment (UE), the method comprising: sending a power headroom report (PHR) to a network entity, the power headroom report (PHR) comprising first power headroom information for configured carriers configured for uplink communication and second power headroom information for at least one unconfigured carrier not configured for uplink communication; receiving, in response to the PHR, from the network entity a message indicating a selected carrier, the selected carrier comprising one of the configured carrier and the at least one unconfigured carrier; as well as An uplink transmission is sent to the network entity via the selected carrier.

2. The method of claim 1, wherein receiving the message comprises receiving a radio resource control (RRC) configuration message indicating the selected carrier.

3. The method according to claim 1, wherein periodically sending the PHR based on a periodicity, The PHR is sent after receiving a PHR request from the network entity or in response to a triggering event.

4. The method according to claim 3, wherein the triggering event comprises at least one of the following: The path loss of the configured carrier exceeds a path loss threshold, The signal strength of the configured carrier drops below the UE signal strength threshold, The available power in one of the at least one unconfigured carriers exceeds an available power threshold, The available power in one of the at least one unconfigured carrier exceeds the available power in the configured carrier by at least a relative available power threshold, or A power management maximum power reduction (P-MPR) backoff for one of the at least one unconfigured carrier is below a backoff threshold. The method of claim 3 , wherein the periodicity is based on a periodicity of a carrier different from the configured carrier.

6. The method of claim 3, wherein the PHR request is received in response to at least one of: The signal strength at the network entity is lower than a network entity signal strength threshold, or the load parameter on the configured carrier exceeds a carrier load threshold.

7. The method of claim 1, wherein the first power headroom information is sent based on a physical uplink shared channel (PUSCH) on the configured carrier, and The second power headroom information is sent based on a reference PUSCH on each of the at least one unconfigured carrier.

8. The method of claim 1, wherein the first power headroom information comprises one or more of a first maximum UE output power for the configured carrier, a first power management maximum power reduction value, and a first power headroom value, and The second power headroom information comprises one or more of a second maximum UE output power, a second power management maximum power reduction value, and a second power headroom value for each of the at least one unconfigured carrier.

9. The method of claim 8, wherein the second power headroom value is based on the second maximum UE output power, the second power management maximum power reduction value, an open-loop transmit power based on open-loop power control, and a path loss.

10. The method of claim 9, wherein the open loop transmit power is based on an open loop nominal power parameter set to a predefined default value and an open loop UE power parameter set to zero for the at least one unconfigured carrier.

11. The method of claim 1, wherein the PHR is sent via a multi-entry PHR medium access control (MAC) control element (CE).

12. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: at least one processor; a transceiver communicatively coupled to the at least one processor; and a memory communicatively coupled to the at least one processor, wherein the at least one processor is configured to: sending a power headroom report (PHR) to a network entity, the power headroom report (PHR) comprising first power headroom information for configured carriers configured for uplink communication and second power headroom information for at least one unconfigured carrier not configured for uplink communication; receiving, in response to the PHR, from the network entity a message indicating a selected carrier, the selected carrier comprising one of the configured carrier and the at least one unconfigured carrier; as well as An uplink transmission is sent to the network entity via the selected carrier.

13. The UE of claim 12, wherein the at least one processor configured to receive the message is configured to receive a radio resource control (RRC) configuration message indicating the selected carrier.

14. The UE according to claim 12, wherein periodically sending the PHR based on a periodicity, The PHR is sent after receiving a PHR request from the network entity or in response to a triggering event.

15. The UE according to claim 14, wherein the triggering event comprises at least one of the following: The path loss of the configured carrier exceeds a path loss threshold, The signal strength of the configured carrier drops below the UE signal strength threshold, The available power in one of the at least one unconfigured carriers exceeds an available power threshold, The available power in one of the at least one unconfigured carrier exceeds the available power in the configured carrier by at least a relative available power threshold, or A power management maximum power reduction (P-MPR) backoff for one of the at least one unconfigured carrier is below a backoff threshold.

16. A method for wireless communication by a network entity, the method comprising: receiving a power headroom report (PHR) from a user equipment (UE), the power headroom report (PHR) comprising first power headroom information for a configured carrier configured for uplink communication and second power headroom information for at least one unconfigured carrier not configured for uplink communication; selecting a carrier comprising one of the configured carrier and the at least one unconfigured carrier based on the PHR; sending a message indicating the selected carrier to the UE; and An uplink transmission is received from the UE via the selected carrier.

17. The method of claim 16, wherein sending the message comprises sending a radio resource control (RRC) configuration message indicating the selected carrier.

18. The method according to claim 16, wherein periodically receiving the PHR based on a periodicity, receiving the PHR in response to sending a PHR request to the UE, or The PHR is received in response to a triggering event.

19. The method of claim 18, wherein the triggering event comprises at least one of the following: The path loss of the configured carrier exceeds a path loss threshold, The signal strength of the configured carrier drops below a signal strength threshold, The available power in one of the at least one unconfigured carriers exceeds an absolute available power threshold, The available power in one of the at least one unconfigured carrier exceeds the available power in the configured carrier by at least a relative available power threshold, or A power management maximum power reduction (P-MPR) backoff for one of the at least one unconfigured carrier is below a backoff threshold.

20. The method of claim 18, wherein the periodicity is based on a periodicity of a carrier different than the configured carrier.

21. The method of claim 18, wherein the PHR request is sent in response to at least one of: The signal strength at the network entity is lower than a network entity signal strength threshold, or the load parameter on the configured carrier exceeds a carrier load threshold.

22. The method of claim 16, wherein the first power headroom information is transmitted based on a physical uplink shared channel (PUSCH) on the configured carrier, and The second power headroom information is sent based on a reference PUSCH on each of the at least one unconfigured carrier.

23. The method of claim 16, wherein the first power headroom information comprises one or more of a first maximum UE output power for the configured carrier, a first power management maximum power reduction value, and a first power headroom value, and The second power headroom information comprises one or more of a second maximum UE output power, a second power management maximum power reduction value, and a second power headroom value for each of the at least one unconfigured carrier.

24. The method of claim 23, wherein the second power headroom value is based on the second maximum UE output power, the second power management maximum power reduction value, an open loop transmit power based on open loop power control, and a path loss.

25. The method of claim 24, wherein the open loop transmit power is based on an open loop nominal power parameter set to a predefined default value and an open loop UE power parameter set to zero for the at least one unconfigured carrier.

26. The method of claim 16, wherein the PHR is received via a multi-entry PHR medium access control (MAC) control element (CE).

27. A network entity for wireless communication, the network entity comprising: at least one processor; a transceiver communicatively coupled to the at least one processor; and a memory communicatively coupled to the at least one processor, wherein the at least one processor is configured to: receiving a power headroom report (PHR) from a user equipment (UE), the power headroom report (PHR) comprising first power headroom information for a configured carrier configured for uplink communication and second power headroom information for at least one unconfigured carrier not configured for uplink communication; selecting a carrier comprising one of the configured carrier and the at least one unconfigured carrier based on the PHR; sending a message indicating the selected carrier to the UE; and An uplink transmission is received from the UE via the selected carrier.

28. The network entity of claim 27, wherein the at least one processor configured to send the message is configured to send a radio resource control (RRC) configuration message indicating the selected carrier.

29. The network entity according to claim 27, wherein periodically receiving the PHR based on a periodicity, receiving the PHR in response to sending a PHR request to the UE, or The PHR is received in response to a triggering event.

30. The network entity according to claim 29, wherein the triggering event comprises at least one of the following: The path loss of the configured carrier exceeds a path loss threshold, The signal strength of the configured carrier drops below a signal strength threshold, The available power in one of the at least one unconfigured carriers exceeds an absolute available power threshold, The available power in one of the at least one unconfigured carrier exceeds the available power in the configured carrier by at least a relative available power threshold, or A power management maximum power reduction (P-MPR) backoff for one of the at least one unconfigured carrier is below a backoff threshold.

Images