Beam management for transmit power

By reporting virtual PHR and P-MPR to the base station through user equipment, and combining L1-RSRP, beam selection and power backoff are optimized, solving the problem of beam exceeding MPE and improving spectrum efficiency and communication performance.

CN121865394APending Publication Date: 2026-04-14APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2021-09-15
Publication Date
2026-04-14

AI Technical Summary

Technical Problem

In the beam management of user equipment, existing technologies cannot effectively prevent the beam transmitted to the target from exceeding the maximum permissible exposure (MPE), which leads to a decrease in communication performance or waste of resources, and the base station cannot accurately select an alternative beam.

Method used

By reporting virtual power headroom (PHR) and maximum power reduction (P-MPR) to the base station through user equipment, combined with closed-loop power control factor and reference signal received power (L1-RSRP), beam optimization and power back-off are achieved to ensure that the MPE is not exceeded while maintaining communication efficiency.

Benefits of technology

It improves spectrum efficiency, avoids communication performance degradation caused by power backoff, and ensures the accuracy of base station beam selection and effective utilization of resources.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN121865394A_ABST
    Figure CN121865394A_ABST
Patent Text Reader

Abstract

The invention relates to beam management for transmit power. The application relates to devices and components, including apparatuses, systems, and methods for providing beam management for beams with reduced maximum transmission power.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of the invention patent application with application number 202180071058.3, application date September 15, 2021, entitled "Beam Management for Transmit Power". Cross-reference to related applications

[0002] This application claims the benefit and priority of PCT International Application No. PCT / CN2020 / 121733, filed on October 18, 2020, the entire contents of which are incorporated herein by reference for all purposes. Background Technology

[0003] The use of user equipment has become a common phenomenon in the lives of many individuals. User equipment can transmit signals from itself using beams pointed in different directions, a portion of which can be emitted toward objects and / or organisms near the user equipment. The emission amount of the beam emitted toward the object and / or organism can be defined. Attached Figure Description

[0004] Figure 1 An example network environment based on some implementation schemes is shown.

[0005] Figure 2 Example beamforming diagrams according to some implementation schemes are shown.

[0006] Figure 3 Another example beamforming diagram according to some implementation schemes is shown.

[0007] Figure 4 An example beam feature reporting process according to some implementation schemes is shown.

[0008] Figure 5 An example receive power determination process according to some implementation schemes is shown.

[0009] Figure 6 Example channel state information configuration report information elements are shown according to some implementation schemes.

[0010] Figure 7 Another example of a channel state information configuration report information element is shown according to some implementation schemes.

[0011] Figure 8 Another example of a channel state information configuration report information element is shown according to some implementation schemes.

[0012] Figure 9 Another example of a channel state information configuration report information element is shown according to some implementation schemes.

[0013] Figure 10An example beamforming circuit according to some implementation schemes is shown.

[0014] Figure 11 Example user equipment according to some implementation schemes is shown.

[0015] Figure 12 An example of a next-generation Node B is shown according to some implementation schemes. Detailed Implementation

[0016] The following detailed description relates to the accompanying drawings. The same reference numerals may be used in different drawings to identify the same or similar elements. In the following description, specific details, such as particular structures, architectures, interfaces, technologies, etc., are set forth for illustrative and non-limiting purposes to provide a thorough understanding of various aspects of the various embodiments. However, it will be apparent to those skilled in the art that various aspects of the various embodiments may be practiced in other examples departing from these specific details. In some cases, descriptions of well-known devices, circuits, and methods have been omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of this document, the phrase "A or B" refers to (A), (B), or (A and B).

[0017] The following is a glossary of terms that may be used in this disclosure.

[0018] As used herein, the term "circuit" refers to, is part of, or includes the following: hardware components such as electronic circuits, logic circuits, processors (shared, dedicated, or grouped) or memories (shared, dedicated, or grouped), application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable system-on-chips (SoCs)), digital signal processors (DSPs), etc. In some embodiments, a circuit may execute one or more software or firmware programs to provide at least some of the said functions. The term "circuit" may also refer to a combination of one or more hardware elements and program code for performing the functions (or a combination of circuits used in an electrical or electronic system). In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit.

[0019] As used herein, the term "processor circuit" means, is part of, or includes the following: a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transmitting digital data. The term "processor circuit" may also refer to an application processor, baseband processor, central processing unit (CPU), graphics processing unit, single-core processor, dual-core processor, triple-core processor, quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions (such as program code, software modules, and / or functional procedures).

[0020] As used herein, the term "interface circuit" refers to, is part of, or includes a circuit that enables the exchange of information between two or more components or devices. The term "interface circuit" can refer to one or more hardware interfaces, such as buses, I / O interfaces, peripheral component interfaces, network interface cards, etc.

[0021] As used herein, the term "user equipment" or "UE" refers to equipment of a remote user that has radio communication capabilities and can describe network resources in a communication network. Furthermore, the term "user equipment" or "UE" can be considered synonymous and can be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Additionally, the term "user equipment" or "UE" can include any type of wireless / wired equipment or any computing device that includes a wireless communication interface.

[0022] As used herein, the term "computer system" means any type of interconnected electronic device, computer device, or component thereof. Additionally, the term "computer system" or "system" may refer to the various components of a computer that are communicatively coupled to each other. Furthermore, the term "computer system" or "system" may refer to multiple computer devices or multiple computing systems that are communicatively coupled to each other and configured to share computing resources or network resources.

[0023] As used herein, the term "resource" refers to physical or virtual devices, physical or virtual components within a computing environment, or physical or virtual components within a specific device, such as computer equipment, mechanical equipment, memory space, processor / CPU time, processor / CPU utilization, processor and accelerator load, hardware time or utilization, power supply, input / output operations, port or network sockets, channel / link allocation, throughput, memory utilization, storage, network, databases and applications, units of workload, etc. "Hardware resource" can refer to computing, storage, or networking resources provided by physical hardware components. "Virtualized resource" can refer to computing, storage, or networking resources provided by virtualization infrastructure to applications, devices, systems, etc. The terms "network resource" or "communication resource" can refer to resources that computer equipment / systems can access via a communication network. The term "system resource" can refer to any kind of shared entity providing services and can include computing or network resources. System resources can be considered as a coherent set of functions, network data objects, or services accessible through a server, wherein such system resources reside on a single host or multiple hosts and are clearly identifiable.

[0024] As used herein, the term "channel" refers to any tangible or intangible transmission medium used for transmitting data or data streams. The term "channel" may be synonymous or equivalent with "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," or any other similar term indicating a path or medium through which data is transmitted. Additionally, as used herein, the term "link" refers to a connection between two devices used for transmitting and receiving information.

[0025] As used in this article, the terms "instantiate" and "instantiate" refer to the creation of an instance. "Instance" also refers to the concrete occurrence of an object, which may occur, for example, during the execution of program code.

[0026] The term "connection" can mean that two or more elements at a common communication protocol layer have an established signaling relationship with each other through a communication channel, link, interface, or reference point.

[0027] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as networked computers, network hardware, network equipment, network nodes, virtualized network functions, etc.

[0028] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual content of an information element, or the data element that contains that content. An information element may include one or more additional information elements.

[0029] As used herein, the term "object" refers to one or more objects. Such an object can be a human being. In some implementations, the term "object" can refer to a human being, another organism, or some other object to which a maximum permissible exposure level (MPE) can be assigned.

[0030] Figure 1 An example network environment 100 according to some implementation schemes is shown. Specifically, network environment 100 shows the possible locations of user equipment (UE) 102 and object 104 according to some instances.

[0031] Network environment 100 includes UE 102, such as UE 1100 ( Figure 11 UE 102 may be part of a radio access network (RAN) and may utilize the RAN to communicate with one or more other devices. Multi-panel operation may be applied to the UE, where different directional panels may be oriented in different directions. For example, UE 102 may include one or more panels 106 with antennas that can be used to communicate with the RAN. Panel 106 may transmit one or more beams 108 from UE 102 for communication with the RAN. Beams 108 may be transmitted from UE 102 in multiple different directions. In some embodiments, panel 106 may be directional panels, where each of these directional panels may transmit beams in different directions. For example, one of panels 106 may transmit a beam in a first direction, while another of panels 106 may transmit a beam in a second direction. In other embodiments, a portion of the antenna within the panel may transmit a beam in the first direction, and another portion of the antenna within the panel may transmit a beam in the second direction. In the illustrated implementation, for clarity, a limited number of panels 106 and a limited number of beams are shown; however, it should be understood that in other implementations, there may be more or fewer panels 106 and / or beams 108, and beams 108 may be transmitted from the UE 102 in more, fewer, or different directions than illustrated.

[0032] Network environment 100 includes object 104. Object 104 may be located near UE 102. For example, object 104 may be located within a specific distance of UE 102, wherein this distance may be less than a threshold distance for the standard transmit power of beam 108. Some UE beams in one or more panels may be directed toward the object. For example, the main lobe or side lobe of the beam may be directed toward the object. Furthermore, one or more beams 108 of UE 102 may be transmitted toward object 104. Specifically, the main lobe or side lobe of the beam may be transmitted toward object 104. In the illustrated embodiment, a first beam 108a may be transmitted toward object 104, such that the main lobe 108a of the first beam is transmitted toward object 104. Other beams, such as a second beam 108b and a third beam 108c, may have side lobes of the beams transmitted toward object 104. Regarding transmit exposure, the UE may back off the maximum transmit power or avoid using beams that exceed the maximum permissible exposure (MPE) toward the object. Figure 2 and Figure 3 The exposure caused by the beam will be described further.

[0033] Object 104 may have an assigned MPE from beam 108. Specifically, the MPE may define the amount of exposure that object 104 will experience from beam 108. The amount of exposure caused by the beam on object 104 may depend on the direction of the beam relative to object 104, the distance of object 104 from UE 102, the transmission power of the beam, or some combination thereof. If the exposure of the beam exceeds the MPE, the operation of the beam may be modified. Modification of beam operation may include backing up the maximum transmission power of the beam. For example, the first beam 108a may exceed the MPE of object 104 during normal operation in the illustrated embodiment. Therefore, the maximum transmission power of the first beam 108a may be backed up to meet the MPE for object 104.

[0034] Network environment 100 includes base station 110 (such as gNB 1200 ( Figure 12 Base station 110 may be part of a radio access network (RAN) (such as a 3GPP RAN). In implementations, the RAN may include one or more base stations having characteristics of base station 110 or similar characteristics. Base station 110 may exchange transports with UE 102, where the transports facilitate the operation of UE 102. For example, the RAN may be responsible for defining the functionality, requirements, and / or interfaces of UE 102. The RAN may be based on new broadband, multi-mode, flexible radio access. Base station 110 may be configured for use by UE 102 within the RAN.

[0035] Several methods have been applied to address situations where the beam exceeds the target's MPE during normal operation. One method introduces a duty cycle during which no uplink signal is transmitted. Significant uplink performance improvements can be observed with this method. Another method involves the UE reporting Power Management Maximum Power Reduction (P-MPR) to the next-generation Node B (gNB) so that the gNB is aware of power backoff. However, the gNB has no way of knowing about the power backoff of candidate beams, preventing it from comparing the performance of the current beam with another beam candidate or other beam candidates. Yet another method involves the UE performing uplink / downlink beam reporting separately. In this method, switching to a new beam results in performance degradation, and some beams in the target beam still function well with some backoff. Another method involves the UE reporting Power Headroom (PHR) per beam. In this method, PHR is calculated based on the higher-layer filtered reference signal received power (RSRP), which requires significant measurement delay, and PHR does not reflect beam quality with respect to different P-MPRs used for different beams.

[0036] Several different methods were evaluated to determine which approach provides optimal spectral efficiency for addressing beam transmission to the target. The baseline approach includes beam selection without panel switching, where the UE continues to utilize the beam transmitted to the target with a 10 dB power backoff. A second approach includes beam / panel selection utilizing UE-specific P-MPR. A third approach includes beam / panel selection utilizing panel-specific P-MPR. A fourth approach includes beam / panel selection based on uplink received power. The fourth approach provides optimal spectral efficiency. Therefore, the methods described throughout this disclosure can be based on this fourth approach.

[0037] While the MPE for object 104 can be satisfied by backing up the maximum transmit power of the beam, the reduction in maximum transmit power may cause communication problems with other devices within the RAN. For example, base stations (such as gNB 1200) Figure 12 Transmissions on a beam may be misunderstood and / or failed to be identified due to a reduction in maximum transmission power. Furthermore, a base station may schedule transmissions on a beam when the beam is insufficient for transmission and / or when a better beam option for transmission exists. The methods described throughout this disclosure help notify the base station of the backoff of the maximum transmission power of a beam to avoid failure to identify and / or schedule transmissions on the beam when a better beam option for transmission exists. Some embodiments describe beam selection based on UL-Rx power. Aspects of these embodiments include descriptions of beam reporting, beam report content, and control signaling for different preferred (e.g., optimal) beams for different bandwidths.

[0038] Figure 2 An example beamforming diagram 200 according to some embodiments is shown. Specifically, Figure 200 shows an example amount of beamforming gain produced by a beam emitted from a UE such as UE 102. Furthermore, Figure 200 shows the direction of the UE from an object. Specifically, in Figure 200, the object is shown at an angle of 0 degrees.

[0039] The beamforming gain has a peak 202 with a main lobe at the 0-degree angle in Figure 200. Therefore, in the illustrated embodiment, the beam generating the beamforming gain can be directly transmitted to the object. Assuming the object is in the 0-degree direction, it can be determined that the exposure exceeds the MPE. The beamforming gain can be compared to a threshold to determine whether the beam transmission to the object exceeds the MPE for the object. In the illustrated embodiment, peak 202 may exceed the threshold, and the beam transmission may exceed the MPE for the object. Therefore, in this case, it can be determined that the maximum transmission power should be backed up.

[0040] In Rel-15 (a 3GPP organization partner). 3 Partner Program; Technical Specification Group for Radio Access Networks. (Version 15) / Rel-16 (3GPP Organization Partner). 3 In the Partner Program; Technical Specification Group for Radio Access Networks (Version 16), two options are defined to address this issue. Option 1: Introduces a duty cycle during which no uplink signal is transmitted. A potential drawback of Option 1 is that a significant UL performance degradation can be observed. Option 2: The UE reports P-MPR (Maximum Power Reduction) to the gNB so that the gNB is aware of the power backoff. A potential drawback of Option 2 is that the gNB has no way of knowing about the power backoff of the candidate beam, making it impossible for the gNB to compare the performance of the current beam with other candidate beams.

[0041] In addition, several other options for addressing this issue have been discussed. Option 3: The UE can perform UL / DL beam reporting independently. A potential drawback of Option 3 is that some beams for a given target may still function well with some power back-off, and constantly switching to a new beam can lead to performance degradation. Option 4: The UE can report the power headroom (PHR) for each beam. A potential drawback of Option 4 is that PHR calculation is based on the RSRP of higher-layer filtering, which requires greater measurement delay, and PHR does not reflect the beam quality with respect to different P-MPRs for different beams.

[0042] These four schemes have been studied through system-level evaluation. Scheme 1 (baseline): Beam selection without panel switching. The UE continues to use the target beam with an MPE exceeding 10 dB power backoff. Scheme 2: Beam / panel selection utilizing UE-specific P-MPR. Scheme 3: Beam / panel selection utilizing panel-specific P-MPR. Scheme 4: Beam / panel selection based on UL Rx power. Scheme 4 was observed to provide the best spectral efficiency (SE).

[0043] Figure 3 Another example beamforming diagram 300 according to some embodiments is shown. Specifically, Figure 300 shows an example amount of beamforming gain produced by a beam emitted from a UE such as UE 102. Furthermore, Figure 300 shows the direction of the UE from an object. Specifically, in Figure 300, the object is shown at an angle of 0 degrees.

[0044] The beamforming gain has a peak 302 with sidelobes at the 0-degree angle in Figure 300. Therefore, in the illustrated embodiment, the beam generating the beamforming gain can be emitted toward the object at a certain angle, but sidelobes may be emitted at the object. The beamforming gain can be compared to a threshold to determine whether the beam emission toward the object exceeds the MPE for that object. Assuming the object is at the 0-degree direction, it can be determined that the exposure exceeds the MPE. In the illustrated embodiment, peak 302 may exceed the threshold, and the beam emission may exceed the MPE for that object. Therefore, in this case, it can be determined that the maximum transmission power should be backed up.

[0045] Figure 4 An example beam feature reporting process 400 according to some implementations is shown. Specifically, process 400 may include determining beam-related features and reporting these features to another device in the RAN. Process 400 may be performed by a UE (such as UE1100). Figure 11 )) can be executed and can be sent to base stations (such as gNB 1200 ( Figure 12 Report these characteristics.

[0046] Process 400 may include identifying, in 402, a beam to which process 400 is to be performed. The identified beam may be a beam whose maximum transmission power can be backed up. For example, process 400 may include identifying an object (such as object 104) near the UE and identifying a beam that exceeds the MPE for that object based on the beam transmitted for that object. Process 400 may repeat for the beam that exceeds the MPE for the object.

[0047] Process 400 may include determining, in 404, characteristics related to the beam identified in 402. In a first option, these characteristics may include the beam's virtual PHR, the beam's maximum power transmission (P_cmax), the beam's maximum power reduction (P_MPR), and / or the Layer 1 Reference Signal Received Power (L1-RSRP). The virtual PHR may be calculated from P_cmax - P_MPR - (P0 + α*pathloss + f). If multiple closed-loop indices are configured, the closed-loop indices used to calculate f can be predefined or configured via higher-layer signaling. The path loss for calculating the virtual PHR may be determined by the L1-RSRP or the RSRP of higher-layer filtering. In some embodiments of the first option implementation, P_cmax and P_MPR may be included as a single value equal to the maximum transmitted power P_cmax – P_MPR.

[0048] In the second option, these features may include P_cmax, P_MPR, L1-RSRP, closed-loop power control factor f, and beam index, i.e., SSB resource index (SSBRI) or CSI-RS resource index (CRI). If multiple closed-loop indices are configured, the closed-loop index used to calculate f can be predefined or configured via higher-layer signaling. In some embodiments of the second option, these features may not include f. Furthermore, in some embodiments of the second option, P_cmax and P_MPR may be included as a single value equal to the maximum transmitted power P_cmax – P_MPR.

[0049] The virtual PHR can be determined based on P_cmax, P_MPR, target received power (P0), path loss, a path loss compensation factor (α), and / or a closed-loop power control factor (f). P0 and α can be provided by higher layers. f can be maintained by the UE based on a Transmission Power Control (TPC) command indicated by the gNB prior to reporting for use in the closed-loop power control procedure. The closed-loop power control procedure index used to determine f can be predefined or configured via higher-layer signaling. For example, the closed-loop power control procedure index used to determine f can be predefined as a first closed-loop procedure index, or configured by higher-layer signaling if multiple closed-loop indices are configured. In some implementations, TPC can be indicated by downlink control information (DCI). In some implementations, path loss can be determined by L1-RSRP. In other implementations, path loss can be determined by RSRP filtered by higher layers. The virtual PHR can be performed by calculating P_cmax - P_MPR - (P0 + α*pathloss + f).

[0050] Process 400 may include reporting features to the base station in 406. Specifically, the UE may be configured to report features to the base station, such as via Radio Resource Control (RRC) signaling. In a first option, when configured, the UE may report a virtual PHR, P_cmax, P_MPR, L1-RSRP, and beam index, i.e., SSB Resource Index (SSBRI) or CSI-RS Resource Index (CRI). For example, in some embodiments, process 400 may include reporting the virtual PHR, P_cmax, P_MPR, and / or L1-RSRP and beam index (e.g., SSBRI or CRI) to the base station. These features may be reported by the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH). In some embodiments of the first option, P_cmax and P_MPR may be reported as a single value equal to the modified maximum transmission power of P_cmax - P_MPR. For example, the modified maximum transmission power may also be determined by P_cmax - P_MPR, and the modified maximum transmission power may be notified to the base station.

[0051] In the second option, when configured, the UE may report P_cmax, P_MPR, L1-RSRP, closed-loop power control factor f, and beam index, i.e., SSBRI or CRI. For example, in some implementations, process 400 may include reporting P_cmax, P_MPR, L1-RSRP and / or closed-loop power control factor f, as well as the beam index and beam index (e.g., SSBRI or CRI), to the base station. These features may be reported via PUCCH or PUSCH. In some implementations of the second option, f may not be reported. In some implementations of the first option, P_cmax and P_MPR may be reported as a single value equal to the modified maximum transmission power of P_cmax - P_MPR. For example, the modified maximum transmission power may also be determined via P_cmax - P_MPR, and the modified maximum transmission power may be notified to the base station.

[0052] In the first option, PHR-related parameters, including PHR, P_cmax, and P_MPR, can be reported together with L1-RSRP for beamforming purposes or reported separately. For example, in some embodiments of the first option, these characteristics can be reported as candidate values ​​separate from L1-RSRP in the information elements. Figure 6An example Channel State Information Configuration Report (CSI-ReportConfig) information element 600 according to some implementation schemes is shown. In some implementation schemes of the first option, new candidate values, such as “cri-Phr” and “ssb-Index Phr” in the reporting quantity, may be added. For example, these features and beam indices may be reported as candidate values ​​separate from L1-RSRP in CSI-ReportConfig information element 600. Virtual PHR, P_cmax, and P_MPR may be reported as the first candidate value (cri-Phr) within CSI-ReportConfig information element 600, and the beam index may be reported as the second candidate value (ssb-Index-Phr) within CSI-ReportConfig information element 600.

[0053] In other implementations of the first option, these features may be reported together with L1-RSRP as candidate values ​​in the information elements. Figure 7 Another example CSI-ReportConfig information element 700 according to some implementations is shown. Specifically, L1-RSRP can be used as a candidate value in CSI-ReportConfig information element 700 to report these characteristics, and beam index can be used as another candidate value in CSI-ReportConfig information element 700. New candidate values ​​can be added, such as “cri-Phy-RSRP” and “ssb-Index-Phy-RSRP” in the reporting quantity. Virtual PHR, P_cmax, P_MPR, and L1-RSRP can be reported as a first candidate value (cri-Phr-RSRP) in CSI-ReportConfig information element 700, and beam index can be reported as a second candidate value (ssb-Index-Phr-RSRP).

[0054] The priority of this new CSI report type can be calculated using the following equation with the assumptions that k=-1, k=0, or k=2. For example, the priority of CSI-ReportConfig information element 600 and CSI-ReportConfig information element 700 can be calculated using... When CSI-ReportConfig information element 600 or 700 is an aperiodic Channel State Information (CSI) report carried on the PUSCH, y can be equal to 0; when CSI-ReportConfig information element 600 or 700 is a semi-persistent CSI report carried on the PUSCH, y can be equal to 1; when CSI-ReportConfig information element 600 or 700 is a semi-persistent CSI report carried on the PUCCH, y can be equal to 2; and when CSI-ReportConfig information element 600 or 700 is a periodic CSI report carried on the PUCCH, y can be equal to 3. The value of k in CSI-ReportConfig information elements 600 and 700 can be equal to -1, 0, or 2. c can be the value of the serving cell index. N cell This can be the maximum number of serving cells, which can be the value of the higher-level parameter `maxNrofServingCells`. `s` can be the report configuration identifier (`reportConfigID`). M s This can be the maximum number of report configurations, which can be the value of the higher-level parameter maxNrofCSI-ReportConfigurations.

[0055] In other embodiments, process 400 may include reporting P_cmax, P_MPR, L1-RSRP, and / or f to the base station in 406. In some embodiments, these characteristics may be reported by PUCCH or PUSCH. In some embodiments, P_cmax and P_MPR may be reported as a single value. For example, the modified maximum transmission power may also be determined by P_cmax - P_MPR, and the modified maximum transmission power may be notified to the base station.

[0056] In the second option, power control-related factors, including P_cmax, P_MPR, and the closed-loop power control factor f, can be reported together with the L1-RSRP for beamforming purposes or reported separately. For example, in some embodiments of the second option, these features can be reported as candidate values ​​separate from the L1-RSRP in the information elements. Figure 8An example CSI-ReportConfig information element 800 according to some implementations is shown. Specifically, these features and beam indices can be reported as candidate values ​​separate from L1-RSRP in CSI-ReportConfig information element 800. New candidate values ​​can be added, such as “cri-Pcmax” and “ssb-Index-Pcmax” in the reporting quantity. For example, P_cmax, P_MPR, and f can be reported as the first candidate value (cri-Pcmax) within CSI-ReportConfig information element 800, and the beam index can be reported as the second candidate value (ssb-Index-Pcmax) within CSI-ReportConfig information element 800.

[0057] In other implementations of the second option, these features may be reported together with L1-RSRP as candidate values ​​in the information elements. Figure 9 Another example CSI-ReportConfig information element 900 according to some implementations is shown. Specifically, L1-RSRP can be used as a candidate value in CSI-ReportConfig information element 900 to report these characteristics, and beam index can be used as another candidate value in CSI-ReportConfig information element 900. New candidate values ​​can be added, such as “cri-Pcmax-RSRP” and “ssb-Index-Pcmax-RSRP” in the reporting quantity. For example, P_cmax, P_MPR, L1-RSRP, and f can be reported as the first candidate value (cri-Pcmax-RSRP) in CSI-ReportConfig information element 900, and beam index can be reported as the second candidate value (ssb-Index-Pcmax-RSRP).

[0058] The priority of this new CSI report type can be calculated using the following equation with the assumptions that k=-1, k=0, or k=2. For example, the priority of CSI-ReportConfig information element 800 and CSI-ReportConfig information element 900 can be calculated using... When CSI-ReportConfig element 800 or 900 is a non-periodic CSI report carried on the PUSCH, y can be equal to 0; when CSI-ReportConfig element 800 or 900 is a semi-persistent CSI report carried on the PUSCH, y can be equal to 1; when CSI-ReportConfig element 800 or 900 is a semi-persistent CSI report carried on the PUCCH, y can be equal to 2; and when CSI-ReportConfig element 800 or 900 is a periodic CSI report carried on the PUCCH, y can be equal to 3. The value of k for CSI-ReportConfig elements 800 and 900 can be equal to -1, 0, or 2. c can be the value of the serving cell index. N cell This can be the maximum number of serving cells, which can be the value of the higher-level parameter `maxNrofServingCells`. `s` can be `reportConfigID`. M s This can be the maximum number of report configurations, which can be the value of the higher-level parameter maxNrofCSI-ReportConfigurations.

[0059] Figure 5 An example received power determination process 500 according to some implementation schemes is shown. Process 500 can be performed by a base station (such as gNB 1200). Figure 12 )) Execution. Specifically, the base station can utilize process 400 ( Figure 4 ) of 406 ( Figure 4 The features reported in the report are used to perform process 500 to determine the received power of the beam associated with these features.

[0060] The received (Rx) power of a resource element can be calculated as P_rx = P_tx – 10log10(M_SC) – pathloss, where M_SC indicates the total number of scheduled subcarriers. Furthermore, the transmitted power (P_tx) can be calculated as P_tx = min{P0 + 10*log10(N_RB*u) + α*pathloss + f + Δ, P_cmax – P_MPR}, where N_RB indicates the number of scheduled resource blocks, u indicates the subcarrier spacing (SCS) scaler, with 15 kHz as the baseline (e.g., for a 120 kHz SCS, u equals 8), P0 and α are provided by higher-layer parameters, f represents the closed-loop power control factor, Δ is a factor determined by the modulation and coding scheme (MCS), and P_cmax represents the maximum transmitted power. All parameters are defined in the bandwidth portion (BWP).

[0061] Therefore, the Rx power can be calculated as follows. If P0 + 10*log10(N_RB*u) + α*pathloss + f + Δ > P_cmax – P_MPR, then P_rx = P_cmax – P_MPR – 10log10(M_SC) –pathloss. Otherwise, P_rx = P0 + 10*log10(u / N_SC_RB) + (α-1)*pathloss + f + Δ, where N_SC_RB represents the number of subcarriers per resource block. However, the above received power calculation does not consider the effect of backoff. This paper discloses several methods to support beam selection based on ULRx power, including: control signaling for beam reporting; beam reporting content; and beam indication of different optimal beams for different bandwidths.

[0062] Process 500 may include determining the transmission power for uplink transmission in 502. Specifically, the base station may utilize features or portions thereof reported in 406 to determine the transmission power for uplink transmission of the beams associated with those features. In some implementations, the base station may utilize P_cmax, P_MPR, and / or virtual_PHR reported in 406 to determine the transmission power for uplink transmission. The base station may further utilize the number of scheduling resource blocks (N_RB) of the beam, the subcarrier spacing (SCS) scaler (u) of the beam, and / or a factor (Δ) determined by the modulation and coding scheme (MCS) of the UE to determine the transmission power for uplink transmission. u may be u with 15 kHz as the baseline. For example, for a 120 kHz SCS, u may be equal to 8. In the gNB context, beam selection may be performed on a phase-based basis. In the first phase, with the first option having virtual PHR, P_MPR, and P_cmax, the gNB can calculate the tx power used for uplink transmission as P_tx = P_cmax - P_MPR - virtual_PHR + 10*log10(N_RB*u) + Δ. For example, the base station can determine the transmission power (P_tx) using the equation P_tx = P_cmax – P_MPR – virtual_PHR +10*log10(N_RB*u) + Δ.

[0063] In other implementations, the base station may use L1-RSRP, f, P_cmax, and / or P_MPR reported in 406 to determine the transmission power for uplink transmission. The base station may further use N_RB, u, Δ, P0, α, and / or the energy per resource element (EPRE) for the synchronization block / channel state information reference signal (SSB / CSI-RS) to determine the transmission power for uplink transmission. In the first phase of the second option, the gNB may calculate the tx power for uplink transmission as P_tx = min{P0 + 10*log10(N_RB*u) + α*(L1-RSRP - P_tx_0) + f + Δ, P_cmax - P_MPR}. For example, the transmission power (P_tx) can be determined by the equation P_tx = min{P0 + 10*log10(N_RB*u) + α (L1-RSRP – P_tx_0) +f + Δ, P_cmax - P_MPR}, where P_tx_0 indicates the EPRE for SSB / CSI-RS.

[0064] Process 500 may further include determining the received power for uplink transmission in 504. Specifically, the base station may use the features or a portion thereof reported in 406 to determine the received power for uplink transmission. For example, the base station may use the L1-RSRP reported in 406 to determine the received power for uplink transmission. The base station may further use P_tx determined in 502 and / or EPRE for SSB / CSI-RS to determine the received power for uplink transmission. In the second phase of the first and second options, the Rx power can be calculated by P_rx = P_tx + L1-RSRP - P_tx_0, where P_tx_0 indicates the energy per resource element (EPRE) for SSB / CSI-RS.

[0065] Process 500 may further include determining a preferred beam for uplink transmission in 506. For example, the base station may compare the received power determined for one or more beams for the UE to determine that the beam with the optimal received power is the preferred beam for uplink transmission. The optimal received power may be the beam with the highest received power that satisfies transmission characteristics such as transmission frequency, resources to be used for transmission, whether the received power meets a threshold power for transmission, and / or other transmission characteristics. In some instances, the base station may perform 502 and 504 on one or more beams for the UE to determine the received power of the beam. The base station may then compare the received power determined in 504 with / or the received power of other beams for the UE to determine the preferred beam. When the Rx power of two beams is the same, the gNB may select the beam with the minimum Tx power with respect to power savings. For example, when two or more beams are determined to have the same received power and are bundled to satisfy the highest received power for transmission characteristics, the base station may determine the preferred beam as the beam with the lowest transmission power among the two or more beams (such as the transmission power determined in 502). Selecting the beam with the lowest transmission power among the two or more beams can provide power savings for communication with the UE. Furthermore, in some instances, the beam that the base station compares or determines as the preferred beam among the two or more beams may be a beam that can be used for that transmission (such as a beam that is not currently scheduled for another transmission or cannot be used for a particular transmission).

[0066] In some implementations, the Transmission Configuration Indicator (TCI) of the Unified Beam Indication Framework can be used to apply a preferred beam to one or more uplink channels. Based on the Unified Beam Indication Framework, one beam indication signaling, such as the Transmission Configuration Indicator (TCI), can be applied to multiple uplink channels, such as PUSCH, PUCCH, and SRS. For example, the TCI can indicate that a preferred beam can be applied to multiple uplink channels, such as PUSCH, PUCCH, and / or Sound Reference Signal (SRS). However, the optimal beam can be different for different bandwidth allocations.

[0067] In some implementations, different channels may have different preferred beams. For example, a channel with a first bandwidth allocation may be determined to have a first preferred beam, and a channel with a second bandwidth allocation may be determined to have a second preferred beam, which is different from the first preferred beam. In these implementations, different TCI states with different preferred beams may be provided for different uplink channels.

[0068] In a first option of these implementations, uplink channels can be grouped based on allocated bandwidth, and a unified beam indication framework can provide two TCI states. For example, different TCI states of the unified beam indication framework can be provided for different uplink channel groups, where channels can be grouped based on allocated bandwidth. Uplink channels can be grouped into a first group of uplink signals with bandwidth greater than a threshold and a second group of uplink signals with bandwidth less than or equal to the threshold. A first TCI state can be applied to uplink channels with bandwidth greater than the threshold. A second TCI state can be applied to uplink channels with bandwidth less than or equal to the threshold. For example, a first TCI state can be applied to the first group of uplink channels with bandwidth greater than the threshold, and a second TCI state can be applied to the second group of uplink channels with bandwidth less than or equal to the threshold. This threshold can be configured via higher-layer signaling, such as RRC or MAC CE. For example, the TCI state can be provided by MAC CE or DCI. This threshold can be assigned via higher-layer signaling such as Radio Resource Control (RRC) or Medium Access Control (MAC) control elements (CE).

[0069] In the second option of these implementations, the unified beam indication framework can provide N TCI states for multiple bandwidth portions (BWPs). For example, the unified beam indication framework can provide multiple TCI states for multiple bandwidth portions (BWPs). Each TCI state can be applied to a BWP with respect to different bandwidths of different BWPs. For both the first and second options, the TCI states can be provided by MAC CE or DCI. In some implementations, 506 can be omitted.

[0070] Determining the received power of one or more beams helps the RAN correctly identify and / or interpret transmissions from the UE. For example, the base station can identify transmissions from the UE in the vicinity of the determined received power and / or interpret transmissions based on the determined received power. Furthermore, determining the preferred beams ensures that the UE's transmissions have appropriate quality for correct identification and / or interpretation.

[0071] Process 500 may further include indicating a preferred beam for uplink transmission to the UE in 508. In a third stage of both the first and second options, the gNB may indicate a beam for uplink transmission with optimal Rx power. For example, the preferred beam determined in 506 may be indicated to the UE for uplink transmission. The UE can then use the preferred beam for uplink transmission. In some embodiments, 508 may be omitted.

[0072] Figure 10 An example beamforming circuit 1000 according to some embodiments is shown. The beamforming circuit 1000 may include a first antenna panel (i.e., panel 1 1004) and a second antenna panel (i.e., panel 2 1008). Each antenna panel may include multiple antenna elements. Other embodiments may include other numbers of antenna panels.

[0073] The digital beamforming (BF) component 1028 can be derived from, for example, a baseband processor (such as, for example...) Figure 11 The baseband processor 1104A receives the input baseband (BB) signal. The digital BF component 1028 can rely on complex weights to precode the BB signal and provide beamformed BB signals to the parallel radio frequency (RF) chains 1020 / 1024.

[0074] Each RF chain 1020 / 1024 may include a digital-to-analog converter that converts the BB signal into the analog domain; a mixer that mixes the baseband signal into an RF signal; and a power amplifier that amplifies the RF signal for transmission.

[0075] RF signals can be provided to analog beamforming components 1012 / 1016, which can further apply beamforming by providing a phase shift in the analog domain. The RF signals can then be provided to antenna panels 1004 / 1008 for transmission.

[0076] In some implementations, beamforming may be performed only in the digital domain or only in the analog domain, instead of the hybrid beamforming shown herein.

[0077] In various implementations, control circuitry residing in the baseband processor can provide BF weights to the analog / digital BF components to provide a transmission beam at the corresponding antenna panel. These BF weights can be determined by the control circuitry to provide directional assignment of the serving cell as described herein. In some implementations, the BF components and antenna panels can operate together to provide a dynamic phased array capable of guiding the beam in the desired direction.

[0078] Figure 11 Example UE 1100 according to some implementations is shown. UE 1100 can be any mobile or non-mobile computing device, such as, for example, a mobile phone, computer, tablet, industrial wireless sensors (e.g., microphones, carbon dioxide sensors, pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, laser scanners, fluid level sensors, stock sensors, voltmeters / ammeters, actuators, etc.), video surveillance / monitoring devices (e.g., cameras, camcorders, etc.), wearable devices (e.g., smartwatches), and loosely coupled IoT devices. In some implementations, UE 1100 can be a RedCap UE or an NR-Light UE.

[0079] UE 1100 may include a processor 1104, RF interface circuitry 1108, memory / storage device 1112, user interface 1116, sensor 1120, drive circuitry 1122, power management integrated circuit (PMIC) 1124, antenna structure 1126, and battery 1128. The components of UE 1100 may be implemented as integrated circuits (ICs), portions of integrated circuits, discrete electronic devices or other modules, logic components, hardware, software, firmware, or combinations thereof. Figure 11 The block diagram is intended to show a high-level view of some of the components of the UE 1100. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other specific implementations.

[0080] The components of UE 1100 can be coupled to various other components via one or more interconnects 1132, which can represent any type of interface, input / output, bus (local, system, or extension), transmission line, trace, optical connector, etc., allowing various circuit components (on common or different chips or chipsets) to interact with each other.

[0081] Processor 1104 may include processor circuitry, such as, for example, baseband processor circuitry (BB) 1104A, central processing unit circuitry (CPU) 1104B, and graphics processing unit circuitry (GPU) 1104C. Processor 1104 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions, such as program code, software modules, or functional processes from memory / storage device 1112, to cause UE 1100 to perform the operations described herein.

[0082] In some implementations, the baseband processor circuit 1104A can access the communication protocol stack 1136 in the memory / storage device 1112 to communicate over a 3GPP-compliant network. Generally, the baseband processor circuit 1104A can access the communication protocol stack to perform user plane functions at the PHY, MAC, RLC, PDCP, SDAP, and PDU layers; and control plane functions at the PHY, MAC, RLC, PDCP, RRC, and non-access layers. In some implementations, PHY layer operation may additionally / optionally be performed by components of the RF interface circuit 1108.

[0083] The baseband processor circuit 1104A can generate or process baseband signals or waveforms carrying information in a 3GPP-compliant network. In some implementations, the waveforms used for NR can be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and Discrete Fourier Transform Extended OFDM (DFT-S-OFDM) in the uplink.

[0084] Memory / storage device 1112 may include one or more non-transitory computer-readable media, including instructions (e.g., communication protocol stack 1136) that can be executed by one or more processors in processor 1104 to cause UE 1100 to perform the various operations described herein. Memory / storage device 1112 includes any type of volatile or non-volatile memory that can be distributed throughout UE 1100. In some embodiments, some memory / storage devices in memory / storage device 1112 may be located on processor 1104 itself (e.g., L1 cache and L2 cache), while other memory / storage devices 1112 may be located external to processor 1104 but accessible via a memory interface. Memory / storage device 1112 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0085] RF interface circuitry 1108 may include transceiver circuitry and a radio frequency front-end module (RFEM), which allows UE 1100 to communicate with other devices via a radio access network. RF interface circuitry 1108 may include various components arranged in the transmission or reception path. These components may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, control circuitry, etc.

[0086] In the receiving path, the RFEM can receive the transmitted signal from the air interface via antenna structure 1126 and continue to filter and amplify the signal (using a low-noise amplifier). This signal can be provided to the receiver of the transceiver, which downconverts the RF signal into a baseband signal that is provided to the baseband processor of processor 1104.

[0087] In the transmission path, the transceiver's transmitter upconverts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM can amplify the RF signal using a power amplifier before it is transmitted across the air interface via antenna 1126.

[0088] In various implementations, the RF interface circuit 1108 can be configured to transmit / receive signals in a manner compatible with NR access technology.

[0089] Antenna 1126 may include antenna elements to convert electrical signals into radio waves for propagation through the air and to convert received radio waves back into electrical signals. These antenna elements may be arranged in one or more antenna panels. Antenna 1126 may have omnidirectional, directional, or combinations thereof antenna panels to enable beamforming and multiple-input multiple-output (MIMO) communication. Antenna 1126 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, phased array antennas, etc. Antenna 1126 may have one or more panels designed for a specific frequency band included in FR1 or FR2.

[0090] In some implementations, UE 1100 may include beamforming circuitry 1000. Figure 11 The beamforming circuit 1000 can be used to communicate with the UE 1100. In some embodiments, components of the UE 1100 and the beamforming circuit can be shared. For example, the antenna 1126 of the UE may include panel 1 1004 and panel 2 1008 of the beamforming circuit 1000.

[0091] User interface circuitry 1116 includes various input / output (I / O) devices designed to enable users to interact with UE 1100. User interface circuitry 1116 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting input, particularly including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, a headset, etc. Output device circuitry includes any physical or virtual means for displaying information or otherwise conveying information, such as sensor readings, actuator positions, or other similar information. Output device circuitry may include any number or combination of audio or visual displays, particularly including one or more simple visual outputs / indicators (e.g., binary status indicators, such as light-emitting diodes "LEDs") and multi-character visual outputs, or more complex outputs, such as display devices or touchscreens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.), where the output of characters, graphics, multimedia objects, etc., is generated or produced by the operation of UE 1100.

[0092] Sensor 1120 may include a device, module, or subsystem designed to detect events or changes in its environment and transmit information about the detected events (sensor data) to another device, module, subsystem, etc. Examples of such sensors include, in particular: inertial measurement units including accelerometers, gyroscopes, or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) including 3-axis accelerometers, 3-axis gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless aperture sensors); light detection and ranging sensors; proximity sensors (e.g., infrared emission detectors, etc.); depth sensors; ambient light sensors; ultrasonic transceivers; microphones or other similar audio capture devices; etc.

[0093] The driving circuit 1122 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the UE 1100. The driving circuit 1122 may include various drivers that allow other components to interact with or control various input / output (I / O) devices that may exist within or be connected to the UE 1100. For example, the driving circuit 1122 may include: a display driver for controlling and allowing access to a display device; a touchscreen driver for controlling and allowing access to a touchscreen interface; a sensor driver for acquiring sensor readings of the sensor circuit 1120 and controlling and allowing access to the sensor circuit 1120; a driver for acquiring actuator positions of electromechanical components or controlling and allowing access to electromechanical components; a camera driver for controlling and allowing access to an embedded image capture device; and an audio driver for controlling and allowing access to one or more audio devices.

[0094] The PMIC 1124 manages the power supplied to various components of the UE 1100. Specifically, relative to the processor 1104, the PMIC 1124 controls power selection, voltage scaling, battery charging, or DC-DC conversion.

[0095] In some implementations, the PMIC 1124 can control or otherwise become part of various power-saving mechanisms of the UE 1100. For example, if the platform UE is in the RRC_Connected state, where it remains connected to the RAN node as it anticipates receiving traffic soon, it can enter a state known as Discontinuous Receive Mode (DRX) after a period of inactivity. During this state, the UE 1100 can power down for short intervals to conserve power. If there is no data traffic activity for an extended period, the UE 1100 can transition to the RRC_Idle state, where the device is disconnected from the network and does not perform operations such as channel quality feedback, handover, etc. The UE 1100 enters a very low-power state and performs paging, where the device periodically wakes up again to listen to the network and then power down again. The UE 1100 may not receive data in this state; to receive data, the platform must transition back to the RRC_Connected state. Additional power-saving modes can allow the device to be unable to use the network for longer than the paging interval (ranging from a few seconds to several hours). During this period, the device is completely unable to connect to the network and can be completely powered off. Any data sent during this time will result in significant latency, which is assumed to be acceptable.

[0096] Battery 1128 can power UE 1100, but in some examples, UE 1100 may be mounted in a fixed location and may have a power source coupled to the mains. Battery 1128 may be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in vehicle-based applications, battery 1128 may be a typical lead-acid automotive battery.

[0097] Figure 12 An exemplary gNB 1200 according to some embodiments is shown. The gNB 1200 may include a processor 1204, an RF interface circuit 1208, a core network (CN) interface circuit 1212, a memory / storage device circuit 1216, and an antenna structure 1226.

[0098] The components of gNB 1200 can be coupled to various other components via one or more interconnects 1228.

[0099] The processor 1204, RF interface circuit 1208, memory / storage device circuit 1216 (including communication protocol stack 1210), antenna structure 1226, and interconnect 1228 are similar to those in the reference. Figure 11 Similar named elements are shown and described.

[0100] The CN interface circuit 1212 may provide connectivity to the core network, for example, using a 5th generation core network (5GC) compatible network interface protocol (such as Carrier Ethernet protocol) or some other suitable 5GC protocol. Network connectivity may be provided to / from the gNB 1200 via fiber optic or wireless backhaul. The CN interface circuit 1212 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 1212 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0101] As described above, one aspect of this technology is the collection and use of data available from specific and legitimate sources to determine the UE's transmit power and / or receive power. This disclosure envisions that, in some instances, the collected data may include personal information data that uniquely identifies or can be used to identify a specific person. Such personal information data may include demographic data, location-based data, online identifiers, telephone numbers, email addresses, home addresses, data or records related to a user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other personal information.

[0102] This disclosure recognizes that the use of such personal information data in the techniques of this invention can be beneficial to a user. For example, personal information data can be used to determine the location of an object, wherein the determined location can be used to determine the UE's transmit power and / or receive power.

[0103] This disclosure assumes that entities responsible for collecting, analyzing, disclosing, transmitting, storing, or otherwise using such personal information data will comply with established privacy policies and / or privacy practices. Specifically, it is expected that such entities will implement and consistently apply privacy practices generally recognized as meeting or exceeding industry or governmental requirements for protecting user privacy. Such information regarding the use of personal data should be highlighted and easily accessible to users, and should be updated as data collection and / or use changes. Users' personal information should be collected only for lawful use. Furthermore, such collection / sharing should only occur after receiving user consent or other lawful grounds provided for in applicable law. In addition, such entities should consider taking any necessary steps to protect and safeguard access to such personal information data and ensure that others with access to personal information data comply with their privacy policies and processes. Additionally, such entities may be subject to third-party evaluations to demonstrate their compliance with widely accepted privacy policies and practices. Furthermore, policies and practices should be tailored to the specific types of personal information data collected and / or accessed, and made applicable to applicable laws and standards, including jurisdiction-specific considerations that may be used to impose higher standards. For example, in the United States, the collection or access to certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); while health data in other countries may be subject to other regulations and policies and should be handled accordingly.

[0104] Regardless of the foregoing, this disclosure also anticipates implementation schemes for users to selectively block the use or access to personal information data. That is, this disclosure anticipates providing hardware and / or software components to prevent or block access to such personal information data. For example, such as in relation to determining the location of an object, the technology can be configured to allow users to opt-in or opt-out at any time during or after registration for the service to participate in the collection of personal information data. In addition to providing opt-in and opt-out options, this disclosure also envisions providing notifications related to access to or use of personal information. For example, the user may be notified before determining the location of an object, and then reminded again just before the location of the object is to be determined.

[0105] Furthermore, the purpose of this disclosure is to manage and process personal information data to minimize the risk of unintentional or unauthorized access or use. Once data is no longer needed, this risk can be minimized by limiting data collection and deleting data. Additionally, and where applicable, including in certain health-related applications, data deidentification can be used to protect user privacy. Deidentification can be facilitated, where appropriate, by removing identifiers, controlling the amount or specificity of stored data (e.g., collecting location data at the city level rather than the address level), controlling how data is stored (e.g., aggregating data among users), and / or other methods such as differentiated privacy.

[0106] Therefore, while this disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, it is also contemplated that various embodiments can be implemented without access to such personal information data. That is, various embodiments of the present invention will not be rendered inoperable due to the absence of all or part of such personal information data. For example, content can be selected and delivered to the user based on aggregated non-personal information data or an absolute minimum amount of personal information, such as content processed only on the user's device or other non-personal information that can be used for content delivery services.

[0107] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods as described in the Examples section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples below. Similarly, circuitry associated with the UE, base station, network element, etc., described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the Examples section below.

[0108] Example Further exemplary implementations are provided in the following sections.

[0109] Example 1 may include one or more computer-readable media having instructions, when executed by one or more processors, to cause a user equipment (UE) to perform the following operations: identify a beam of the UE transmitted toward a target for radio access network (RAN) communication, determine the maximum power reduction (P_MPR) and layer 1 reference signal received power (L1-RSRP) of the beam, and report to a base station a value based on the P_MPR, the index of the beam, and the L1-RSRP for determining the received (Rx) power associated with the beam.

[0110] Example 2 may include one or more computer-readable media according to Example 1, wherein the instructions, when executed by the one or more processors, further cause the UE to determine the virtual power margin (PHR) of the beam based on the P_MPR, and report the virtual PHR to the base station for the purpose of determining the Rx power.

[0111] Example 3 may include one or more computer-readable media according to Example 2, wherein the virtual PHR will be further determined based on the maximum power transmission (P_cmax) of the beam, and wherein the instructions, when executed by the one or more processors, further cause the UE to report the P_cmax to the base station.

[0112] Example 4 may include one or more computer-readable media according to Example 1, wherein the indication of P_MPR is reported as a modified maximum transmission power equal to the maximum power transmission (P_cmax) minus the P_MPR.

[0113] Example 5 may include one or more computer-readable media according to Example 2, wherein the virtual PHR will be further determined based on the target received power (P0), the path loss compensation factor (α), the path loss, and the closed-loop power control factor (f) of the beam.

[0114] Example 6 may include one or more computer-readable media according to Example 5, wherein the path loss is determined based on the L1-RSRP.

[0115] Example 7 may include one or more computer-readable media according to Example 5, wherein f will be predefined or configured by higher-level signaling.

[0116] Example 8 may include one or more computer-readable media according to Example 2, wherein the instructions, when executed by the one or more processors, further cause the UE to report the maximum power transmission (P_cmax) of the beam along with the P_MPR and the PHR as a first candidate value (cri-Phr) within a Channel State Information (CSI) Report Configuration (CSI-ReportConfig) information element, and to report the beam index of the beam as a second candidate value (ssb-Index-Phr) within the CSI-ReportConfig information element.

[0117] Example 9 may include one or more computer-readable media according to Example 2, wherein the instructions, when executed by the one or more processors, further cause the UE to report the maximum power transmission (P_cmax) of the beam along with the P_MPR, the PHR, and the L1-RSRP as a first candidate value (cri-Phy-RSRP) within a Channel State Information (CSI) Report Configuration (CSI-ReportConfig) information element, and to report the beam index of the beam as a second candidate value (ssb-Index-Phy-RSRP) within the CSI-ReportConfig information element.

[0118] Example 10 may include one or more computer-readable media according to Example 1, wherein the instructions, when executed by the one or more processors, further cause the UE to report the maximum power transmission (P_cmax) of the beam to the base station for the purpose of determining the Rx power associated with the beam.

[0119] Example 11 may include one or more computer-readable media according to Example 10, wherein the instructions, when executed by the one or more processors, further cause the UE to report the closed-loop power control factor (f) of the beam to the base station for the purpose of determining the RX power associated with the beam.

[0120] Example 12 may include one or more computer-readable media according to Example 11, wherein f will be predefined or configured by higher-level signaling.

[0121] Example 13 may include one or more computer-readable media according to Example 10, wherein P_MPR and P_cmax are reported as a modified maximum transmission power equal to P_cmax minus P_MPR.

[0122] Example 14 may include one or more computer-readable media according to Example 10, wherein the instructions, when executed by the one or more processors, further cause the UE to report the closed-loop power control factor (f) with P_cmax and P_MPR in a first candidate (cri-Pcmax) within a Channel State Information (CSI) Report Configuration (CSI-ReportConfig) information element, and to report the beam index of the beam as a second candidate value (ssb-Index-Pcmax) within the CSI-ReportConfig information element.

[0123] Example 15 may include one or more computer-readable media according to Example 10, wherein the instructions, when executed by the one or more processors, further cause the UE to report the closed-loop power control factor (f) along with the P_cmax, P_MPR and the L1-RSRP as a first candidate (cri-Pcmax-RSRP) within a Channel State Information (CSI) Report Configuration (CSI-ReportConfig) information element, and to report the beam index of the beam as a second candidate value (ssb-Index-Pcmax-RSRP) within the CSI-ReportConfig information element.

[0124] Example 16 may include one or more computer-readable media according to Example 1, wherein the P_MPR and the L1-RSRP are reported via the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH).

[0125] Example 17 may include one or more computer-readable media according to Example 1, wherein reporting the value includes reporting the value in a Channel State Information (CSI) report, and wherein the processing circuitry is further configured to determine that the priority for the CSI report will be equal to Where k equals -1, 0, or 2, y equals 0 when the CSI report will be aperiodic and carried on the Physical Uplink Shared Channel (PUSCH), y equals 1 when the CSI report will be semi-persistent and carried on the PUSCH, y equals 2 when the CSI report will be semi-persistent and carried on the Physical Uplink Control Channel (PUCCH), and y equals 3 when the CSI report will be periodic and carried on the PUCCH, c is the serving cell index, and N... cell This represents the maximum number of serving cells, s is the report configuration identifier, and M... s This is the maximum number of report configurations.

[0126] Example 18 may include a user equipment (UE) comprising: a plurality of panels that transmit multiple beams for radio access network (RAN) communication from the UE in multiple directions; and processing circuitry coupled to the plurality of panels, the processing circuitry being configured to identify a beam among the plurality of beams transmitted toward an object, determine a maximum power reduction (P_MPR) for the beam based on the position of the object relative to the beam, determine a Layer 1 reference signal received power (L1-RSRP), and report to a base station a value based on the P_MPR, the index of the beam, and the L1-RSRP for determining the received (Rx) power associated with the beam.

[0127] Example 19 may include the UE according to Example 18, wherein the processing circuitry is further configured to determine the maximum power transmission (P_cmax) of the beam, and wherein the value is the P_MPR or a modified maximum transmission power, the modified maximum transmission power being equal to the P_cmax minus the P_MPR.

[0128] Example 20 may include the UE according to Example 18, wherein the processing circuitry is further configured to determine the virtual power margin (PHR) of the beam based on P_MPR and P_cmax, and to report the virtual PHR to the base station for the determination of the Rx power.

[0129] Example 21 may include the UE according to Example 20, wherein the virtual PHR will be further determined based on the target received power (P0), the path loss compensation factor (α), the path loss, and the closed-loop power control factor (f) of the beam.

[0130] Example 22 may include the UE according to Example 21, wherein the path loss is determined based on the L1-RSRP.

[0131] Example 23 may include the UE according to Example 21, wherein f will be predefined or configured by higher-layer signaling.

[0132] Example 24 may include the UE according to Example 18, wherein the processing circuitry is further configured to report the closed-loop power control factor (f) of the beam to the base station for determining the Rx power associated with the beam.

[0133] Example 25 may include the UE according to Example 24, wherein f will be predefined or configured by higher-layer signaling.

[0134] Example 26 may include the UE according to Example 18, wherein the P_MPR, the P_cmax and the L1-RSRP are reported via the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH).

[0135] Example 27 may include the UE according to Example 18, wherein reporting the value includes reporting the value in a Channel State Information (CSI) report, and wherein the processing circuitry is further configured to determine that the priority for the CSI report will be equal to Where k equals -1, 0, or 2, y equals 0 when the CSI report will be aperiodic and carried on the Physical Uplink Shared Channel (PUSCH), y equals 1 when the CSI report will be semi-persistent and carried on the PUSCH, y equals 2 when the CSI report will be semi-persistent and carried on the Physical Uplink Control Channel (PUCCH), and y equals 3 when the CSI report will be periodic and carried on the PUCCH, c is the serving cell index, and N... cell This represents the maximum number of serving cells, s is the report configuration identifier, and M... s This is the maximum number of report configurations.

[0136] Example 28 may include a method of operating a user equipment (UE), the method comprising: identifying an object within a specific proximity of the UE; identifying a beam of the UE for radio access network (RAN) communication emitted toward the object; determining a maximum power reduction (P_MPR) for the beam based on the position of the object relative to the direction of the beam and the distance from the UE; and reporting to a base station a value based on the P_MPR and a Layer 1 Reference Signal Received Power (L1-RSRP) for determining the received (Rx) power associated with the beam.

[0137] Example 29 may include the method according to Example 28, the method further comprising determining the virtual power margin (PHR) of the beam based on the P_MPR, and reporting the virtual PHR to the base station for use in determining the Rx power.

[0138] Example 30 may include the method according to Example 29, wherein the virtual PHR is further determined based on the maximum power transmission (P_cmax) of the beam, and wherein the method further includes reporting the P_cmax to the base station.

[0139] Example 31 may include the method according to Example 28, wherein the method further includes determining the maximum power transmission (P_cmax) of the beam, wherein the value is the P_MPR or a modified maximum transmission power, and wherein the modified maximum transmission power is equal to the P_cmax minus the P_MPR.

[0140] Example 32 may include the method according to Example 29, wherein the virtual PHR is further determined based on the target received power (P0), the path loss compensation factor (α), the path loss, and the closed-loop power control factor (f) of the beam.

[0141] Example 33 may include the method according to Example 32, the method further including determining the path loss based on the L1-RSRP.

[0142] Example 34 may include the method according to Example 32, the method further including determining f based on a predefined value or higher-layer signaling.

[0143] Example 35 may include the method according to Example 29, the method further comprising reporting the maximum power transmission (P_cmax) of the beam together with the P_MPR and the PHR as a first candidate value (cri-Phr) in a Channel State Information (CSI) Report Configuration (CSI-ReportConfig) information element, and reporting the beam index of the beam as a second candidate value (ssb-Index-Phr) in the CSI-ReportConfig information element.

[0144] Example 36 may include the method according to Example 29, the method further comprising reporting the maximum power transmission (P_cmax) of the beam together with the P_MPR, the PHR and the L1-RSRP as a first candidate value (cri-Phy-RSRP) within a Channel State Information (CSI) Report Configuration (CSI-ReportConfig) information element, and reporting the beam index of the beam as a second candidate value (ssb-Index-Phy-RSRP) within the CSI-ReportConfig information element.

[0145] Example 37 may include the method according to Example 28, the method further including reporting the maximum power transmission (P_cmax) of the beam to the base station for determining the Rx power associated with the beam.

[0146] Example 38 may include the method according to Example 37, the method further including reporting the closed-loop power control factor (f) of the beam to the base station for determining the Rx power associated with the beam.

[0147] Example 39 may include the method according to Example 38, wherein f will be predefined or configured by higher-layer signaling.

[0148] Example 40 may include the method according to Example 37, the method further comprising subtracting P_MPR from P_cmax to produce a modified maximum transmission power, wherein P_MPR and P_cmax are reported as the modified maximum transmission power.

[0149] Example 41 may include the method according to Example 37, the method further including reporting the closed-loop power control factor (f) with P_cmax and P_MPR in a first candidate (cri-Pcmax) within a channel state information (CSI) report configuration (CSI-ReportConfig) information element, and reporting the beam index of the beam as a second candidate value (ssb-Index-Pcmax) within the CSI-ReportConfig information element.

[0150] Example 42 may include the method according to Example 37, the method further comprising reporting the closed-loop power control factor (f) along with the P_cmax, P_MPR and the L1-RSRP as a first candidate (cri-Pcmax-RSRP) within a Channel State Information (CSI) Report Configuration (CSI-ReportConfig) information element, and reporting the beam index of the beam as a second candidate value (ssb-Index-Pcmax-RSRP) within the CSI-ReportConfig information element.

[0151] Example 43 may include the method according to Example 28, wherein the P_MPR and the L1-RSRP are reported via the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH).

[0152] Example 44 may include the method according to Example 28, wherein reporting the value includes reporting the value in a Channel State Information (CSI) report, and wherein the method further includes determining that the priority for the CSI report will be equal to Where k equals -1, 0, or 2; y equals 0 when the CSI report will be aperiodic and carried on the Physical Uplink Shared Channel (PUSCH); y equals 1 when the CSI report will be semi-persistent and carried on the PUSCH; y equals 2 when the CSI report will be semi-persistent and carried on the Physical Uplink Control Channel (PUCCH); and y equals 3 when the CSI report will be periodic and carried on the PUCCH. c is the serving cell index N. cell This represents the maximum number of serving cells, s is the report configuration identifier, and M... s This is the maximum number of report configurations.

[0153] Example 45 may include one or more computer-readable media having instructions, when executed by one or more processors, to cause a base station to perform the following operations: process a report from a user equipment (UE) to determine an index corresponding to a beam, a value based on a maximum power reduction (P_MPR) and a layer 1 reference signal received power (L1-RSRP), determine a transmit (Tx) power for uplink (UL) transmission of the beam for the user equipment (UE) based on the value, and determine a receive (Rx) power for the beam based on the transmit power and the L1-RSRP.

[0154] Example 46 may include one or more computer-readable media according to Example 45, wherein the Tx power will be further determined based on the virtual power headroom (PHR) of the beam indicated by the UE.

[0155] Example 47 may include one or more computer-readable media according to Example 46, wherein the Tx power will be further determined based on the maximum power transmission (P_cmax) of the beam indicated by the UE.

[0156] Example 48 may include one or more computer-readable media according to Example 45, wherein the Tx power will be further determined based on the number of scheduling resource blocks (RBs) of the beam, the subcarrier spacing scaler of the beam, and a factor (Δ) determined by the modulation and coding scheme (MCS) of the UE.

[0157] Example 49 may include one or more computer-readable media according to Example 45, wherein the Rx power will be further determined based on the per-resource element energy (EPRE) of the UE's synchronization signal / physical broadcast channel block (SSB) / channel state information reference signal (CSI-RS).

[0158] Example 50 may include one or more computer-readable media according to Example 45, wherein the Tx power will be further determined based on the L1-RSRP, the closed-loop power control factor (f) indicated by the UE, and the maximum power transmission (P_cmax) of the beam indicated by the UE.

[0159] Example 51 may include one or more computer-readable media according to Example 45, wherein the Tx power will be further determined based on the target received power (P0) of the UE, the number of scheduling resource blocks (RBs) of the beam, the factor (α) for compensating path loss of the beam, and the factor (Δ) determined by the modulation and coding scheme (MCS) of the UE.

[0160] Example 52 may include one or more computer-readable media according to Example 45, wherein the instructions, when executed by the one or more processors, further cause the gNB to compare the Rx power with the Rx power associated with other beams of the UE, and indicate to the UE a preferred beam for UL transmission based on the comparison.

[0161] Example 53 may include a next-generation Node B (gNB) including a memory for storing data provided to the gNB by a user equipment (UE), and processing circuitry coupled to the memory. The processing circuitry identifies values ​​based on a maximum power reduction (P_MPR) of a beam indicated by the UE and a Layer 1 reference signal received power (L1-RSRP) indicated by the UE, determines a transmit (Tx) power for uplink (UL) transmission of the beam for the UE based on the values, and determines a receive (Rx) power of the beam based on the Tx power and the L1-RSRP.

[0162] Example 54 may include the gNB according to Example 53, wherein the processing circuitry further identifies the virtual power headroom (PHR) of the beam indicated by the UE, and wherein the Tx power is further determined based on the virtual PHR.

[0163] Example 55 may include the gNB according to Example 54, wherein the processing circuitry further identifies the maximum power transmission (P_cmax) of the beam indicated by the UE, and wherein the TX power is further determined based on the P_cmax.

[0164] Example 56 may include the gNB according to Example 53, wherein the Tx power is further determined based on the number of scheduling resource blocks (RBs) of the beam, the subcarrier spacing scaler of the beam, and a factor (Δ) determined by the modulation and coding scheme (MCS) of the UE.

[0165] Example 57 may include the gNB according to Example 53, wherein the Rx power will be further determined based on the per resource element energy (EPRE) of the UE's synchronization signal / physical broadcast channel block (SSB) / channel state information reference signal (CSI-RS).

[0166] Example 58 may include the gNB according to Example 53, wherein the processing circuitry further identifies a closed-loop power control factor (f) indicated by the UE and a maximum power transmission (P_cmax) of the beam indicated by the UE, and wherein the Tx power is further determined based on the L1-RSRP, the f, and the P_cmax.

[0167] Example 59 may include the gNB according to Example 53, wherein the Tx power is further determined based on the target received power (P0) of the UE, the number of scheduling resource blocks (RBs) of the beam, the factor (α) for compensating path loss of the beam, and the factor (Δ) determined by the modulation and coding scheme (MCS) of the UE.

[0168] Example 60 may include the gNB according to Example 53, wherein the processing circuitry further compares the Rx power with the Rx power associated with other beams of the UE, and indicates to the UE a preferred beam for UL transmission based on the comparison.

[0169] Example 61 may include a method of operating a next-generation Node B (gNB) comprising: determining a transmit (Tx) power for uplink (UL) transmission of the beam for the UE based on a value relating to a maximum power reduction (P_MPR) of the beam indicated by a user equipment (UE); determining a receive (Rx) power of the beam based on the transmit power indicated by the UE and a Layer 1 reference signal received power (L1-RSRP); and determining a preferred beam for UL transmission of the UE based on the Rx power.

[0170] Example 62 may include the method according to Example 61, wherein the Tx power is further determined based on the virtual power headroom (PHR) of the beam indicated by the UE.

[0171] Example 63 may include the method according to Example 62, wherein the Tx power is further determined based on the maximum power transmission (P_cmax) of the beam indicated by the UE.

[0172] Example 64 may include the method according to Example 61, wherein the Tx power is further determined based on the number of scheduling resource blocks (RBs) of the beam, the subcarrier spacing scaler of the beam, and a factor (Δ) determined by the modulation and coding scheme (MCS) of the UE.

[0173] Example 65 may include the method according to Example 61, wherein the Rx power is further determined based on the per resource element energy (EPRE) of the UE's synchronization signal / physical broadcast channel block (SSB) / channel state information reference signal (CSI-RS).

[0174] Example 66 may include the method according to Example 61, wherein the Tx power is further determined based on the L1-RSRP, the closed-loop power control factor (f) indicated by the UE, and the maximum power transmission (P_cmax) of the beam indicated by the UE.

[0175] Example 67 may include the method according to Example 61, wherein the Tx power is further determined based on the target received power (P0) of the UE, the number of scheduling resource blocks (RBs) of the beam, the factor (α) for compensating path loss of the beam, and the factor (Δ) determined by the modulation and coding scheme (MCS) of the UE.

[0176] Example 68 may include a method of operating a base station, the method comprising processing a report from a user equipment (UE), determining a beam to be utilized by the UE based on information from the report, and transmitting an indication of the beam to the UE to indicate that the beam is to be applied to a plurality of uplink channels of the UE.

[0177] Example 69 may include the method according to Example 68, wherein the beam is a first beam, wherein the plurality of uplink channels are uplink channels having bandwidth greater than a threshold, and wherein the method further includes: determining a second beam to be used for an uplink channel having bandwidth less than the threshold, and transmitting an indication of the second beam to the UE to indicate that the second beam is to be applied to the uplink channel having bandwidth less than the threshold.

[0178] Example 70 may include the method according to Example 68, wherein the beam is a first beam, wherein the plurality of uplink channels are uplink channels corresponding to a first bandwidth portion, and wherein the method further includes determining a second beam to be used for an uplink channel corresponding to a second bandwidth portion, and transmitting an indication of the second beam to the UE to indicate that the second beam is to be applied to the uplink channel corresponding to the second bandwidth portion.

[0179] Unless otherwise expressly stated, any of the examples above may be combined with any other example (or combination of examples). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. In light of the teachings above, modifications and variations are possible, or modifications and variations may be derived from practice of various embodiments.

[0180] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the disclosure is fully understood. This disclosure is intended to render the following claims as encompassing all such variations and modifications.

Claims

1. One or more computer-readable media having instructions that, when executed, cause processing circuitry to: Determine the characteristics of the power headroom (PHR) element; and Generate the PHR element for transmission, the PHR element including the beam and an indication of the characteristics.

2. The one or more computer-readable media according to claim 1, wherein, The indication of the beam includes the beam index of the beam.

3. The one or more computer-readable media according to claim 2, wherein, The beam index includes the Synchronization Block Resource Index (SSBRI) or the Channel State Information Reference Resource Index (CRI).

4. The one or more computer-readable media according to claim 1, wherein, The feature mentioned includes maximum power transfer (P_cmax).

5. The one or more computer-readable media according to claim 1, wherein, The PHR element also includes an indication of the PHR.

6. The one or more computer-readable media according to claim 5, wherein, The indications of the PHR include indications of the virtual PHR.

7. The one or more computer-readable media according to claim 6, wherein, The virtual PHR is determined at least in part based on maximum power transfer (P_cmax) and maximum power reduction (P_MPR).

8. The one or more computer-readable media according to claim 1, wherein, The characteristic includes Layer 1 Reference Signal Received Power (L1-RSRP).

9. The one or more computer-readable media according to claim 8, wherein, The PHR elements also include maximum power transfer (P_cmax), maximum power reduction (P_MPR), and closed-loop power control factor.

10. One or more computer-readable media according to claim 1, wherein, The PHR element includes the PHR Media Access Control (MAC) control element.

11. A method for wireless communication, the method comprising: Determine whether to generate a beam power headroom (PHR) report; as well as A PHR report for transmission is generated, the PHR report including an indication of the beam.

12. The method according to claim 11, wherein, The indication of the beam includes a beam index.

13. The method according to claim 12, wherein, The beam index includes the Synchronization Block Resource Index (SSBRI) or the Channel State Information Reference Resource Index (CRI).

14. The method according to claim 11, wherein, The PHR report also includes a maximum power delivery (P_cmax) indication.

15. The method according to claim 11, wherein, The PHR report also includes instructions for a virtual PHR.

16. The method according to claim 11, wherein, The PHR report also includes a Layer 1 Reference Signal Received Power (L1-RSRP) indication.

17. An apparatus for: The power headroom (PHR) element to be generated is determined at least in part based on the beam; and Generate the PHR element for transmission, the PHR element including the beam index of the beam.

18. The apparatus according to claim 17, wherein, The beam index includes the Synchronization Block Resource Index (SSBRI) or the Channel State Information Reference Resource Index (CRI).

19. The apparatus according to claim 17, wherein, The PHR element includes the maximum power transfer (P_cmax).

20. The apparatus according to claim 17, wherein, The PHR element includes an indication of a virtual PHR determined at least in part based on maximum power transfer (P_cmax) and maximum power reduction (P_MPR).