Power headroom reporting for multi-beam uplink transmissions

Abstract

This application relates to devices and components including apparatuses, systems, and methods for providing a power headroom report with respect to repetition of uplink data transmissions with different beams in a wireless communication system.

Description

Background Technology

[0001] The 3rd Generation Partnership Project (3GPP) 5G New Radio (NR) network enables uplink data transmission with repeatability, which supports lower latency and / or higher reliability. Attached Figure Description

[0002] Figure 1 A network environment according to some implementation schemes is shown.

[0003] Figure 2A The expression for Power Headroom Report (PHR) based on actual physical uplink scheduling channel (PUSCH) transmission is shown.

[0004] Figure 2B An expression for PHR based on reference PUSCH transmission is shown.

[0005] Figure 3 An example of uplink transmission is shown to support the description of various implementation schemes.

[0006] Figure 4 An example of uplink transmission for which the PHR can be calculated based on a first option is shown according to some implementation schemes.

[0007] Figure 5 An example of uplink transmission for which the PHR can be calculated based on the second and third options is shown, according to some implementation schemes.

[0008] Figure 6 An example of uplink transmission for which the PHR can be calculated based on a fourth option is shown according to some implementation schemes.

[0009] Figure 7 An example of uplink transmission for which the PHR can be calculated based on the fifth option is shown according to some implementation schemes.

[0010] Figure 8 The operational flow / algorithm structure according to some implementation schemes is shown.

[0011] Figure 9 The operational flow / algorithm structure according to some implementation schemes is shown.

[0012] Figure 10 The operational flow / algorithm structure according to some implementation schemes is shown.

[0013] Figure 11 User equipment according to some implementation schemes is shown.

[0014] Figure 12 A base station according to some implementation schemes is shown. Detailed Implementation

[0015] 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" means (A), (B), or (A and B). For the purposes of this document, the phrase "A based on B" means "A is at least based on B".

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

[0017] 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-a-chip (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.

[0018] 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).

[0019] 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.

[0020] As used herein, the term "user equipment" or "UE" refers to a device 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 device or any computing device that includes a wireless communication interface.

[0021] 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.

[0022] 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.

[0023] 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.

[0024] 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.

[0025] 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.

[0026] 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 devices, network nodes, virtualized network functions, etc.

[0027] 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 a data element that contains content. An information element may include one or more additional information elements. The term "get" is used to indicate any of its general meanings, such as calculation, derivation, receiving (e.g., from another element or device), and / or retrieval (e.g., from an array of storage elements).

[0028] A technique is described for repeatedly providing power margin reports relative to uplink data transmission with different beams. Figure 1 A network environment 100 according to some embodiments is illustrated. Network environment 100 may include a UE 104 and an access node (or “base station”) 108. Access node 108 may provide one or more radio serving cells 112 and 114, such as 3GPP New Radio (NR) cells, through which UE 104 may communicate with access node 108 (e.g., via an NR-Uu interface). In some aspects, access node 108 is a next-generation node B (gNB) providing one or more 3GPP NR cells.

[0029] Access node (or “base station”) 108 (which may be a gNB) can transmit information (e.g., data and control signaling) in the downlink direction by mapping logical channels onto transport channels and transport channels onto physical channels. Logical channels can transmit data between the Radio Link Control (RLC) layer and the Media Access Control (MAC) layer; transport channels can transmit data between the MAC and PHY layers; and physical channels can transmit information across the air interface. Physical channels may include the Physical Broadcast Channel (PBCH); the Physical Downlink Shared Channel (PDSCH); and the Physical Downlink Control Channel (PDCCH).

[0030] The PBCH can be used to broadcast system information that UE 104 can use for initial access to the serving cell. The PBCH can be transmitted together with the Physical Synchronization Signal (PSS) and the Secondary Synchronization Signal (SSS) in the Synchronization Signal (SS) / PBCH block. The SS / PBCH block (SSB) can be used by UE 104 during the cell search process and for beam selection.

[0031] PDSCH can be used to transmit end-user application data, signaling radio bearer (SRB) messages, system information messages (except for, for example, master information block (MIB)), and paging messages.

[0032] Access node 108 (e.g., a base station or gNB) can use PDCCH to transmit downlink control information (DCI) to UE 104. DCI can provide uplink resource allocation on the Physical Uplink Shared Channel (PUSCH), downlink resource allocation on the PDSCH, and various other control information. DCI can also be used to provide uplink power control commands, configure time slot formats, or indicate that preemption has occurred.

[0033] Access node (e.g., base station or gNB) 108 can also transmit various reference signals to UE 104. Reference signals (RS) are special signals that exist only at the PHY layer and are not used to deliver any specific information (e.g., data), but their purpose is to provide a reference point for transmit power. Reference signals may include demodulation reference signals (DMRS) for PBCH, PDCCH, and PDSCH. UE 104 can compare the received version of the DMRS with a known sequence of transmitted DMRS to estimate the impact of the propagation channel. UE 104 can then apply the inversion of the propagation channel during the demodulation process corresponding to the physical channel transmission.

[0034] The reference signal may also include a Channel State Information Reference Signal (CSI-RS). The CSI-RS can be a multi-purpose downlink transmission that can be used for CSI reporting, beam management, connection mode mobility, radio link failure detection, beam failure detection and recovery, and fine-tuning of time and frequency synchronization. For example, UE 104 can measure the SSB and CSI-RS to determine the desired downlink beam pairs for transmit / receive PDCCH and PDSCH transmissions. UE 104 can use the Physical Uplink Control Channel (PUCCH) to transmit uplink control information (UCI) to access node 108, including, for example, Hybrid Automatic Repeat Request (HARQ) acknowledgments, scheduling requests, and periodic and semi-persistent Channel State Information (CSI) reports.

[0035] UE 104 may include enhanced multiple-input multiple-output (eMIMO) capability that supports simultaneous communication from several (or even many) different serving cells via beams. Figure 1 An example of carrier aggregation (CA) is shown, in which UE 104 communicates information with access node 108 via serving cell 112 on component carrier (CC) 122 and via serving cell 114 on component carrier (CC) 124.

[0036] CC 122 may be in a frequency band within frequency range 1 (FR1) or frequency range 2 (FR2). Similarly, CC 124 may be in a frequency band within FR1 or FR2. CC 112 and 124 may be in the same frequency band (intra-band, continuous or discontinuous) or in different frequency bands (inter-band) and within potentially different frequency ranges. For FR1 (e.g., below 7.225 GHz), the transmit antenna of UE 104 is typically implemented as an omnidirectional antenna. For FR2 (e.g., 24.250 GHz and above, also known as mmWave), the transmit antenna of UE 104 may be implemented as a panel with multiple antenna elements. For example, the multiple antenna elements of the panel may be driven as a phased array (e.g., to guide the beam in a desired direction).

[0037] The 5G network can implement PUSCH repetition type A, which supports the repetition of PUSCH transmissions in consecutive time slots. Additionally or alternatively, the 5G network can implement PUSCH repetition type B, which supports multiple repetitions of PUSCH transmissions within a single time slot and / or repetition of the same PUSCH transmission across multiple time slots. For example, PUSCH repetition type B can be used to achieve a desired level of low latency and / or high reliability. UE 104 can transmit repetitions of PUSCH transmissions within the same time slot and / or on the same CC as other uplink transmission instances. For example, UE 104 can transmit repetitions within the same time slot and / or on the same CC as one or more regular PUSCH transmissions. Additionally or alternatively, UE 104 can transmit repetitions of PUSCH transmissions within the same time slot and / or on the same CC as a repetition of another PUSCH transmission. The UE can transmit uplink transmission instances on the same uplink beam or on different uplink beams. For example, the UE may transmit duplicate PUSCH transmissions on the same uplink beam or on different uplink beams. UE 104 may also transmit duplicate PUSCH transmissions on a CC that is different from other uplink transmission instances (e.g., one or more regular PUSCH transmissions, duplicates of another PUSCH transmission), which may occur within the same time slot.

[0038] Both Dynamic Grant (DG) and Configuration Grant (CG) can support PUSCH repetition type B. In the case of CG, PUSCH repetition type B can be supported for type 1 and / or type 2. Base station 108 can communicate PUSCH repetition configuration to UE 104 by providing slot configuration and scheduling information. Slot configuration indicates the symbols available for uplink transmission within a certain time period, and base station 108 can provide slot configuration, for example, in RRC signaling messages or DCI messages. Scheduling information may include time domain resource allocation (e.g., Time Domain Resource Allocation (TDRA) field), modulation and coding scheme (MCS), and / or frequency resource allocation (which may indicate, for example, the number of physical resource blocks (PRBs)) in DCI messages or type 1 CG configuration messages, and can be provided, for example, in one or more RRC messages and / or one or more DCI messages. PUSCH repetition type B can be scheduled by DCI format 0_1 ​​or DCI format 0_2, but is generally not scheduled by DCI format 0_0.

[0039] A Power Headroom Report (PHR) can be used to report uplink transmission power status to reflect the uplink link budget. The PHR is calculated in response to the detection of a PHR trigger condition (e.g., as indicated in Clause 5.4.6 of 3GPP Technical Specification (TS) 38.321 (5G; NR; Media Access Control (MAC) Protocol Specification Version 16.4.0 (2021-04)), such as a periodic timer expiring or a path loss change exceeding a threshold. The UE transmits the PHR within the Media Access Control (MAC) Control Element (CE) during PUSCH transmissions. A PHR may not be scheduled; conversely, it may be transmitted when the UE has already been allocated resources on the PUSCH for another reason (e.g., for uplink data transmission).

[0040] As described in Clause 7.7.1 of 3GPP TS 38.213 (5G; NR; Physical Layer Control Procedures, Version 16.5.0 (2021-04)), the UE uses a parameter set configuration with index j and a PUSCH power control adjustment state with index l to calculate the effective PHR for PUSCH transmission timing i on the active UL BWP b of carrier f of serving cell c. Clause 7.7.1 of 3GPP TS 38.213 provides two different types of PHR. The first type of PHR is the actual PHR, where the PHR is based on... Figure 2A The expression shown is calculated based on actual PUSCH transmissions and includes the maximum output power P configured for the UE. CMAX,f,c (i) and scheduling bandwidth (For example, as described in Clause 7.1.1 of 3GPP TS 38.213). The second type of PHR is a virtual PHR, where the PHR is based on, for example... Figure 2B The expression shown is calculated based on a reference PUSCH transmission, and includes a reference maximum output power value. (For example, as described in Clause 7.7.1 of 3GPP TS 38.213).

[0041] If the timing of a PUSCH transmission carrying a PHR occurs too early after the PHR triggering condition, the UE may not have enough time to calculate the actual PHR. A threshold can be applied to accommodate the PUSCH transmission preparation delay. For example, a threshold can be applied such that if the time offset between the PHR triggering condition and the PUSCH transmission with the PHR exceeds the threshold, the UE reports the actual PHR; otherwise, the UE reports a virtual PHR. For dynamically authorized PUSCHs, the threshold could be a time slot with a PDCCH that uses the PHR to schedule the PUSCH transmission. For configuration-authorized PUSCHs, the threshold could be based on the minimum scheduling delay.

[0042] In version 17 of the 5G specification, it may be expected to support PUSCH repetition with multi-beam operation, allowing repetitions with different beams to be received by one or more transmit-receive points (TRPs). PUSCH repetition with multi-beam operation is also referred to herein as "multi-beam PUSCH". In multi-beam PUSCH, PUSCH repetitions can be multiplexed in a time-division multiplexing (TDM) manner based on the following types: 1) Repetition type A (e.g., each repetition occupies one time slot); 2) Repetition type B (e.g., repetitions are multiplexed in consecutive time slots, and more than one repetition can be transmitted in one time slot).

[0043] For multi-beam PUSCH, the PHR of different beams can vary significantly, making it unclear how to calculate the PHR. One possible approach is to report N PHRs for N TRPs (e.g., N=2) based on the multi-beam PUSCH.

[0044] PHR calculation may depend on the configuration and transmission state in the corresponding transmission timing. For the case of one or more repetitions of a PUSCH transmission to be sent, PHR calculation can be based on the configuration and transmission state in the first transmission timing (e.g., the initial repetition of the PUSCH transmission). However, if the initial repetition will be sent on the first beam and a later repetition of the PUSCH transmission will be sent on the second beam, the transmission state of the first repetition of the PUSCH transmission on the second beam may be unknown when preparing the transport block for the PUSCH transmission. Consequently, the UE may not be able to predict what the transmission state of the second beam will be during the corresponding transmission timing on the second beam. For such reasons, how to report multiple PHRs via multi-beam PUSCH can be a problem.

[0045] Figure 3 An example of a potential problem is shown. As shown in this example, when preparation for a PUSCH transmission begins on CC2, the UE does not yet have information about whether a PUSCH transmission will occur on CC1 during the same time slot as PUSCH repetition #3, and the reported PHR may vary depending on whether a PUSCH transmission will occur on CC1 during that time slot.

[0046] This paper describes PHR calculation techniques when a multi-beam PUSCH reports more than one PHR, and demonstrates how these techniques can be implemented to address the aforementioned issues. As described herein, PHR calculation techniques when a multi-beam PUSCH reports more than one PHR may include using any of several different options for power headroom (PH) calculation.

[0047] When the PHR report of the first beam meets the conditions for reporting an actual PHR, the first PHR can be calculated as the actual PHR based on the configuration information (e.g., scheduling bandwidth) of the first PUSCH transmission timing. For the second PHR, a first option is to calculate the second PHR as a virtual PHR (e.g., based on a reference PUSCH transmission). Power control parameters for virtual PHR calculation can be configured for each TRP via higher-layer signaling (e.g., RRC signaling or MAC CE). Alternatively, the power control parameters for virtual PHR calculation can be based on the default power control parameters for each TRP (based on the default association between a configured set of power control parameters and the corresponding beam).

[0048] In one example of this first option, the default power control parameters may be as follows: a first set of values ​​{the first value in P0-AlphaSet; the path loss reference signal (PL-RS) corresponding to PUSCHPathlossReferenceRS-Id = 0, and the closed-loop index I = 0} may be used for TRP1, and a second set of values ​​{the second value in P0-AlphaSet; the PL-RS corresponding to PUSCHPathlossReferenceRS-Id = 1; and the closed-loop index I = 1 if twoPUSCH-PC-AdjustmentStates are configured, otherwise I = 0} may be used for TRP2. In this case, TRP1 corresponds to the beam indicated by the probe reference signal (SRS) resource indicator (SRI) from the first SRS resource set, and TRP2 corresponds to the beam indicated by the SRI from the second SRS resource set. Although some embodiments describe PUSCH transmissions on two beams being received by the respective TRPs, PUSCH transmissions on more than one beam (e.g., these two beams) may be received by the same TRP. Figure 4 An example of uplink transmissions for which PHR can be calculated based on a first option is shown, wherein repetitions #1 and #2 of PUSCH transmissions are performed on the first beam / precoder X and repetitions #3 and #4 of PUSCH transmissions are performed on the second beam / precoder Y.

[0049] As described above, when the PHR report of the first beam meets the conditions for reporting an actual PHR, the first PHR can be calculated as the actual PHR based on the configuration information (e.g., scheduling bandwidth) of the first PUSCH transmission timing. For the second PHR, a second option is to calculate the second PHR as the actual PHR based on the configuration information (e.g., scheduling bandwidth) of the first PUSCH transmission timing with the second beam. In this case, when calculating the second PHR, the UE can assume that it will not transmit additional signals in another CC during the first PUSCH transmission timing with the second beam. Alternatively, the UE can calculate the second PHR based on the assumption that the signal transmission state in other CCs during the time slot including the first PUSCH transmission timing with the second beam will be the same as during the time slot including the first PUSCH transmission timing with the first beam.

[0050] For reference Figure 5 Let's understand an example of uplink transmissions where the PHR can be calculated based on the second option. In this example, it is assumed that the UE does not perform a PUSCH transmission on CC1 during the time slot including repetition #3, PHR1 is calculated based on the configuration information of repetition #1, and PHR2 is calculated based on the configuration information of repetition #3.

[0051] As described above, when the PHR report of the first beam meets the conditions for reporting an actual PHR, the first PHR can be calculated as the actual PHR based on the configuration information (e.g., scheduling bandwidth) of the first PUSCH transmission timing. For the second PHR, a third option is to calculate the second PHR as the actual PHR based on the configuration information (e.g., scheduling bandwidth) of the first PUSCH transmission timing with the first beam. However, to calculate this second PHR, the UE can use power control parameters (e.g., P0, α, PL-RS, and / or closed-loop power control parameters) based on the indication for the second beam. Additionally or alternatively, if beam-level maximum power reduction (MPR) is enabled, the UE can calculate the second PHR based on the corresponding MPR of the second beam.

[0052] Can be referenced again Figure 5 Let's understand an example of uplink transmission where the PHR can be calculated based on the third option. In this example, PHR1 is calculated based on the configuration information of repeating #1 and using the power control parameters of beam / precoder X, and PHR2 is calculated based on the configuration information of repeating #1 but using the power control parameters of beam / precoder Y.

[0053] As described above, when the PHR report of the first beam meets the conditions for reporting an actual PHR, the first PHR can be calculated as an actual PHR based on the configuration information of the first PUSCH transmission timing (e.g., scheduling bandwidth). For the second PHR, the fourth option is to calculate the second PHR based on the length of the gap between the first repetition on the first beam and the first repetition on the second beam, and / or based on the length of the gap between the time of the PHR triggering condition and the first repetition on the second beam. According to this option, if the gap between the first repetition on the first beam and the first repetition on the second beam is within a threshold, and / or if the gap between the time of the PHR triggering condition and the first repetition on the second beam is within a threshold, the UE can calculate the second PHR as an actual PHR based on the configuration information of the first PUSCH transmission timing with the second beam (e.g., scheduling bandwidth). If the gap is higher than the corresponding threshold, the UE can calculate the second PHR according to the first option, the second option, or the third option as described above, or the UE can calculate both the first PHR and the second PHR as virtual PHRs. A predefined threshold, or one that can be reported by the UE as a UE capability (e.g., via capability signaling), can be configured to ensure that no other signals are scheduled after the time for preparing a transport block for PUSCH transport has begun.

[0054] Figure 6 An example of uplink transmission for which the PHR can be calculated based on the fourth option is shown, where PHR1 is calculated based on the configuration information of repetition #1 (e.g., scheduling bandwidth) and PHR3 is calculated based on the configuration information of repetition #3 (e.g., scheduling bandwidth). It may be desirable for the UE to use the fourth option (e.g., multiple repetitions in one slot) for repetition type B, and to use the first, second, or third option (e.g., one repetition per slot) for repetition type A as described above.

[0055] The above describes several options for calculating the power hazard ratio (PH) when the PHR report for the first beam meets the conditions for reporting the actual PHR. In the fifth option, the UE calculates both the first and second PHRs as virtual PHRs. In this case, the UE can calculate each virtual PHR based on default power control parameters or based on power control parameters configured for the corresponding TRP. Figure 6 An example of uplink transmission for which PHR can be calculated based on the fifth option is shown.

[0056] The above describes several options for reporting PHR in a multi-beam PUSCH. In another approach, the UE does not report PHR in a multi-beam PUSCH. For example, this approach could include reporting PHR only in a PUSCH with single-beam operation. Alternatively, whether or not to report PHR via a multi-beam PUSCH can be indicated as a UE capability, which the UE can communicate to the gNB using capability signaling.

[0057] Several different options for reporting the first PHR and the second PHR, which have been calculated by the UE as described above, are now described. In the first reporting option, the UE reports only one PHR in the multi-beam PUSCH. In this case, the UE may report the minimum of the two PHRs, the maximum of the two PHRs, the average of the two PHRs (e.g., mean), or the first PHR (e.g., the PHR corresponding to the initial repetition of the PUSCH transmission).

[0058] In the second reporting option, the UE reports only two PHRs in the multi-beam PUSCH. In the third reporting option, whether the UE uses the first reporting option (e.g., reporting only one PHR) or the second reporting option (e.g., reporting two PHRs) can be configured by the gNB (e.g., via RRC signaling) or reported as a UE capability.

[0059] In the fourth reporting option, the gNB can configure separate triggering conditions for the first and second PHRs (e.g., via RRC signaling, MAC CE, and / or DCI), and whether the UE reports one or two PHRs can be determined by which PHR triggering conditions occurred. If the triggering conditions for the first and second PHRs occur simultaneously, the UE can use any of the first, second, or third reporting options as described above. In one example, the PHR triggering condition is that the path loss change of the TRP exceeds a threshold, which can be configured individually for each TRP. In another example, if the UE detects a maximum power transmit (MPE) event of the beam (e.g., the MPE change of the beam exceeds a threshold) when beam-level MPE is enabled, a beam PHR can be triggered.

[0060] If a common trigger condition is configured, a PHR report can be triggered when the path loss or MPE of two or one of the TRPs changes. In this case, the PHR can be reported using any of the first, second, or third reporting options as described above.

[0061] Figure 8 An operational flow / algorithm structure 800 according to some implementation schemes is shown. The operational flow / algorithm structure 800 may be executed or implemented by a UE such as, for example, UE 104 or UE 1100 or its components such as baseband processor 1104A.

[0062] The operation flow / algorithm structure 800 may include, at block 804, receiving scheduling information to schedule multiple repetitions of uplink data transmission on the first CC. This scheduling information may indicate that these repetitions will be PUSCH repetition type B. The scheduling information may also indicate that one of the multiple repetitions will be transmitted on the first beam, while another of the multiple repetitions will be transmitted on the second beam.

[0063] The operation flow / algorithm structure 800 may include, at block 808, detecting the power headroom report (PHR) trigger condition. For example, this condition may be a timer expiring, or exceeding a threshold (e.g., a path loss threshold, an MPE threshold).

[0064] The operation flow / algorithm structure 800 may be included in block 812, which, based on the detection, calculates the first PHR of the first beam on the first CC according to the configuration information of the first repetition among the plurality of repetitions. The first PHR may be an actual PHR or a virtual PHR. The first PHR may be based on actual PUSCH transmission or reference PUSCH transmission.

[0065] The operation flow / algorithm structure 800 may include, at block 816, calculating the second PHR of the second beam on the first CC. The second PHR may be an actual PHR or a virtual PHR. The second PHR may be based on actual PUSCH transmission or reference PUSCH transmission. The second PHR may be based on power control parameters (PCP) determined for the beam. Determining the PCP may include: receiving the PCP in RRC or MAC CE signaling; or determining the PCP based on a default association between a configured set of PCPs and the second beam.

[0066] Figure 9 An operational flow / algorithm structure 900 according to some implementation schemes is shown. The operational flow / algorithm structure 900 may be executed or implemented by a UE such as, for example, UE 104 or UE 1100 or its components such as baseband processor 1104A.

[0067] The operation flow / algorithm structure 900 may include, at block 904, receiving scheduling information to schedule multiple repetitions of uplink data transmission on the first CC. This scheduling information may indicate that these repetitions will be PUSCH repetition type B. The scheduling information may also indicate that one of the multiple repetitions will be transmitted on the first beam, while another of the multiple repetitions will be transmitted on the second beam.

[0068] The operation flow / algorithm structure 900 may include, at block 912, calculating the first PHR of the first beam on the first CC based on the configuration information of the first repetition among the plurality of repetitions. The first PHR may be an actual PHR or a virtual PHR. The first PHR may be based on actual PUSCH transmission or reference PUSCH transmission.

[0069] The operation flow / algorithm structure 900 may include, at block 916, calculating the second PHR of the second beam on the first CC. The second PHR may be an actual PHR or a virtual PHR. The second PHR may be based on actual PUSCH transmission or reference PUSCH transmission. The second PHR may be based on power control parameters (PCP) determined for the TRP. Determining the PCP may include: receiving the PCP in RRC or MAC CE signaling; or determining the PCP based on a default association between a configured set of PCPs and the second beam.

[0070] Operational flow / algorithm structure 900 may include, at block 920, sending a report based on a first PHR or a second PHR. This report may include either the first PHR or the second PHR. The report may include neither the first nor the second PHR. The report may include the minimum of the first and second PHRs, the maximum of the first and second PHRs, or the average of the first and second PHRs (e.g., an average value). The report may be based on the first PHR, and block 920 may also include sending a second report based on the second PHR. The number of reports may be based on the UE's capabilities or may be configured via RRC or MAC CE signaling. Structure 900 may also include first configuration information for receiving a first beam's PHR trigger condition and / or second configuration information for receiving a second beam's PHR trigger condition.

[0071] Figure 10 An operational flow / algorithm structure 1000 according to some implementation schemes is shown. The operational flow / algorithm structure 1000 may be executed or implemented by a base station such as, for example, base station 108 or 1200 or its components such as baseband processor 1204A.

[0072] The operation flow / algorithm structure 1000 may include, at block 1004, sending scheduling information to the UE to schedule multiple repetitions of uplink data transmission on at least two beams of a first carrier. The scheduling information may indicate that these repetitions will be PUSCH repetition type B. The scheduling information may also indicate that one of the multiple repetitions will be transmitted on the first beam of the at least two beams, while another of the multiple repetitions will be transmitted on the second beam of the at least two beams.

[0073] The operation flow / algorithm structure 1000 may include, at block 1008, sending to the UE a first set of power control parameters for the first beam and a second set of power control parameters for the second beam. This transmission can be performed using, for example, RRC or MAC CE signaling.

[0074] Operational flow / algorithm structure 1000 may include, at block 1012, receiving a Power Headroom Report (PHR) from the UE in at least one of a plurality of repetitions. The report may include one PHR, or a first PHR and a second PHR. Structure 900 may also include sending configuration information to the UE via RRC or MAC CE signaling indicating the number of PHRs to be included in the report. Structure 900 may include receiving the number of PHRs to be included in the report from the UE via capability signaling. Structure 900 may also include sending first configuration information (e.g., path loss threshold and / or MPE threshold) for PHR triggering conditions of a first beam and / or second configuration information (e.g., path loss threshold and / or MPE threshold) for PHR triggering conditions of a second beam to the UE.

[0075] Figure 11 A UE 1100 according to some implementation schemes is shown. UE 1100 may be similar to Figure 1 UE 104, and is basically compatible with Figure 1 UE 104 interchange.

[0076] UE 1100 can be any mobile or non-mobile computing device, such as, for example, mobile phones, computers, tablets, 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.

[0077] 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. 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 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.

[0078] 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.

[0079] 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.

[0080] 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 the following operations: 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 operations may additionally / optionally be performed by components of the RF interface circuit 1108.

[0081] 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 may 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.

[0082] The memory / storage device 1112 may include one or more non-transitory computer-readable media, including instructions (e.g., a 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. The memory / storage device 1112 includes any type of volatile or non-volatile memory that can be distributed throughout UE 1100. In some embodiments, some of the memory / storage devices 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. The 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.

[0083] 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 transmit or receive path. These components may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, control circuitry, etc.

[0084] In the receiving path, the RFEM can receive the radiated 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.

[0085] 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 amplifies the RF signal using a power amplifier before it is radiated across the air interface via antenna 1126.

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

[0087] 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.

[0088] 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.), wherein the output of characters, graphics, multimedia objects, etc., is generated or produced by the operation of UE 1100.

[0089] 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 triaxial accelerometers, triaxial 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 radiation detectors, etc.); depth sensors; ambient light sensors; ultrasonic transceivers; microphones or other similar audio capture devices; etc.

[0090] 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.

[0091] 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.

[0092] In some implementations, the PMIC 1124 may control or otherwise become part of various power-saving mechanisms of the UE 1100, including DRX, as discussed herein.

[0093] 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.

[0094] Figure 12 An access node 1200 (e.g., a base station or gNB) according to some embodiments is shown. Access node 1200 may be similar to access node 108 and is substantially interchangeable with it.

[0095] Access node 1200 may include processor 1204, RF interface circuit 1208, core network (CN) interface circuit 1212, memory / storage device circuit 1216 and antenna structure 1226.

[0096] The components of access node 1200 can be coupled to various other components via one or more interconnectors 1228.

[0097] 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.

[0098] The CN interface circuit 1212 can provide connectivity to a core network (e.g., a 5GC using a 5G core network (5GC) compatible network interface protocol (such as Carrier Ethernet) or some other suitable protocol). Network connectivity can be provided to / from access node 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.

[0099] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0100] 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.

[0101] Example

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

[0103] Example 1 includes a method for operating a UE, the method comprising: receiving scheduling information to schedule multiple repetitions of uplink data transmission on a first (CC); detecting a PHR triggering condition; based on the detection, calculating a first PHR of a first beam on the first CC according to configuration information of a first repetition among the multiple repetitions; and calculating a second PHR of a second beam on the first CC.

[0104] Example 2 includes the method according to Example 1 or some other embodiment herein, wherein the second PHR is a virtual PHR.

[0105] Example 3 includes the method according to Example 2 or some other embodiment herein, wherein the first PHR is based on actual physical uplink shared channel (PUSCH) transmission or reference PUSCH transmission.

[0106] Example 4 includes the method according to Example 2 or some other embodiment herein, the method further comprising determining power control parameters of the beam, wherein the calculation of the second PHR is based on the power control parameters.

[0107] Example 5 includes the method according to Example 4 or some other embodiment herein, wherein determining the power control parameter includes: receiving the power control parameter in Radio Resource Control (RRC) or Medium Access Control (MAC) control element (CE) signaling; or determining the power control parameter based on a default association between a configured set of power control parameters and the second beam.

[0108] Example 6 includes the method according to Example 1 or some other embodiment herein, wherein the calculation of the second PHR is based on configuration information of a second repetition among the plurality of repetitions, wherein the second repetition will occur on the second beam.

[0109] Example 7 includes the method according to Example 6 or some other embodiment herein, wherein the calculation of the second PHR is based on the assumption that the UE does not perform uplink data transmission on the second CC during the second repetition period.

[0110] Example 8 includes the method according to Example 6 or some other embodiment herein, wherein the calculation of the second PHR is based on the assumption that the uplink data transmission state of the UE on the second CC during the second repetition is equivalent to the uplink data transmission state of the UE on the second CC during the first repetition.

[0111] Example 9 includes the method according to Example 6 or some other embodiment herein, wherein the second PHR is calculated based on the length of the gap between the first repeat and the second repeat.

[0112] Example 10 includes the method according to Example 6 or some other embodiment herein, wherein the second PHR is calculated based on the length of the gap between the time of detecting the PHR trigger condition and the second repetition.

[0113] Example 11 includes the method according to Example 10 or some other embodiment herein, wherein the calculation of the second PHR is based on the relationship between a threshold and the length of the gap, and wherein the method further includes an indication of the UE's ability to transmit, wherein the ability includes the threshold.

[0114] Example 12 includes the method according to Example 1 or some other embodiment herein, wherein the calculation of the second PHR is based on the first repeated configuration information.

[0115] Example 13 includes one or more computer-readable media having instructions that, when executed by one or more processors, cause the UE to perform the following operations: receive scheduling information to schedule multiple repetitions of uplink data transmission on a first CC; calculate a first PHR of a first beam on the first CC based on configuration information of a first repetition of the multiple repetitions; calculate a second PHR of a second beam on the first CC; and send a report based on the first PHR or the second PHR.

[0116] Example 14 includes one or more computer-readable media according to Example 13 or some other embodiment herein, wherein the report is based on the first PHR, and the instruction, when executed by the one or more processors, also causes the UE to send a second report based on the second PHR.

[0117] Example 15 includes one or more computer-readable media according to Example 14 or some other embodiment herein, wherein the instructions, when executed by the one or more processors, also cause the UE to send a message instructing the UE to send the second report.

[0118] Example 16 includes one or more computer-readable media according to Example 13 or some other embodiment herein, wherein the report does not include the first PHR or the second PHR.

[0119] Example 17 includes one or more computer-readable media according to Example 13 or some other embodiment herein, wherein the report includes the minimum of the first PHR and the second PHR, the maximum of the first PHR and the second PHR, or the average of the first PHR and the second PHR.

[0120] Example 18 includes one or more computer-readable media according to Example 13 or some other embodiment herein, wherein the instructions, when executed by one or more processors, also cause the user equipment to perform the following operations: receive first configuration information of the PHR triggering condition of the first beam; and second configuration information of the PHR triggering condition of the second beam.

[0121] Example 19 includes a base station comprising a processing circuit for: sending scheduling information to a UE to schedule multiple repetitions of uplink data transmission on at least two beams of a CC; sending to the UE a first set of power control parameters for a first beam of the at least two beams and a second set of power control parameters for a second beam of the at least two beams; and receiving a Power Response Parameter (PHR) from the UE in at least one of the multiple repetitions, a memory coupled to the processing circuit for storing the PHR.

[0122] Example 20 includes a base station according to Example 19 or some other embodiment herein, wherein the processing circuit is configured to send to the UE first configuration information of the PHR triggering condition of the first beam and second configuration information of the PHR triggering condition of the second beam.

[0123] Example 21 includes a base station according to Example 20 or some other embodiment herein, wherein the first configuration information is used to indicate a first path loss threshold, and the second configuration information is used to indicate a second path loss threshold different from the first path loss threshold.

[0124] Example 22 includes a base station according to Example 20 or some other embodiment herein, wherein the first configuration information is used to indicate a first maximum power transmit (MPE) threshold, and the second configuration information is used to indicate a second MPE threshold different from the first MPE threshold.

[0125] Example 23 includes a base station according to Example 19 or some other embodiment herein, wherein the processing circuitry is configured to send configuration information to the UE to indicate the number of PHRs to be transmitted.

[0126] Example 24 may include an apparatus comprising means for performing one or more elements of the method described or associated with any of Examples 1 to 23 or any other method or process described herein.

[0127] Example 25 may include one or more non-transitory computer-readable media, the one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of the method or any other method or process described herein according to any one of Examples 1 to 23 or related thereto.

[0128] Example 26 may include an apparatus comprising one or more elements of a logic component, module, or circuit for performing a method or process described or associated with any of Examples 1 to 23 or any other method or process described herein.

[0129] Example 27 may include a method, technique, or process, or a part or component thereof, as described or associated with any of Examples 1 to 23.

[0130] Implementation scheme 28 may include an apparatus comprising: one or more processors and one or more computer-readable media, the instructions of which, when executed by the one or more processors, cause the one or more processors to perform the methods, techniques or processes or portions thereof described or associated with any of embodiments 1 to 23.

[0131] Example 29 may include a signal, or a portion thereof, as described or associated with any of Examples 1 to 23.

[0132] Example 30 may include a datagram, information element, packet, frame, segment, PDU or message, or a portion or component thereof, as described or otherwise in this disclosure, according to any of Examples 1 to 23.

[0133] Example 31 may include a signal encoded with data, or a portion or component thereof, as described or otherwise in accordance with any of Examples 1 to 23, or otherwise described in this disclosure.

[0134] Example 32 may include a signal, or a portion or component thereof, encoded as a datagram, IE, packet, frame, segment, PDU, or message, as described or associated with any of Examples 1 to 23, or otherwise described in this disclosure.

[0135] Example 33 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process, or a portion thereof, as described or associated with any of Examples 1 to 23.

[0136] Example 34 may include a computer program comprising instructions, wherein execution of the program by a processing element will cause the processing element to perform, or in part with, the methods, techniques or processes described or associated with any of Examples 1 to 23.

[0137] Example 35 may include signals in a wireless network as shown and described herein.

[0138] Example 36 may include methods for communicating in a wireless network as shown and described herein.

[0139] Example 37 may include a system for providing wireless communication as shown and described herein.

[0140] Example 38 may include a device for providing wireless communication as shown and described herein.

[0141] 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 view of the teachings above, modifications and variations are possible, or modifications and variations may be derived from practice of various embodiments.

[0142] 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. A method for operating a user equipment (UE), the method comprising: Receive scheduling information to schedule multiple repetitions of uplink data transmission on the first component carrier CC; Power headroom detection report (PHR) trigger conditions; Based on the detection, the first PHR of the first beam on the first CC is calculated based on the configuration information of the first repetition among the plurality of repetitions; Calculate the second PHR of the second beam on the first CC, wherein the calculation of the second PHR is based on: The assumption that the UE did not perform uplink data transmission on the second CC during the second repetition of the plurality of repetitions, or The assumption that the uplink data transmission state of the UE on the second CC during the second repetition is equivalent to the uplink data transmission state of the UE on the second CC during the first repetition; as well as Send a report based on the first PHR or the second PHR.

2. The method according to claim 1, wherein the second PHR is a virtual PHR.

3. The method according to claim 2, wherein the first PHR is transmitted based on the actual physical uplink shared channel PUSCH or reference PUSCH.

4. The method according to claim 2, further comprising: Determine the power control parameters for the second beam. The calculation of the second PHR is based on the power control parameters.

5. The method of claim 4, wherein determining the power control parameters comprises: The power control parameters are received in the Radio Resource Control (RRC) or Media Access Control (MAC) control element (CE) signaling. or The power control parameters are determined based on the default association between a configured set of power control parameters and the second beam.

6. The method of claim 1, wherein the calculation of the second PHR is based on the length of the gap between the first repetition and the second repetition.

7. The method of claim 1, wherein the calculation of the second PHR is based on the length of the gap between the time when the PHR trigger condition is detected and the second repetition.

8. The method of claim 7, wherein the calculation of the second PHR is based on the relationship between the threshold and the length of the gap, and The method further includes: Indication of the UE's capabilities, wherein the capabilities include the threshold.

9. The method according to any one of claims 1 to 8, wherein detecting the PHR triggering condition comprises: If the path loss change on the first beam exceeds a first threshold, or The path loss change on the second beam was detected to exceed the second threshold.

10. The method according to any one of claims 1 to 5, wherein the first PHR is transmitted based on the actual physical uplink shared channel (PUSCH) and the second PHR is transmitted based on the reference PUSCH.

11. One or more computer-readable media having instructions that, when executed by one or more processors, cause a user-equipped UE to perform the following operations: Obtain scheduling information to schedule multiple repetitions of uplink data transmission on the first component carrier CC; Based on the configuration information of the first repetition among the plurality of repetitions, calculate the first power margin report (PHR) of the first beam on the first CC; Calculate the second PHR of the second beam on the first CC, wherein the calculation of the second PHR is based on: The assumption that the UE did not perform uplink data transmission on the second CC during the second repetition of the plurality of repetitions, or The assumption that the uplink data transmission state of the UE on the second CC during the second repetition is equivalent to the uplink data transmission state of the UE on the second CC during the first repetition; and Generate a report based on the first PHR or the second PHR.

12. One or more computer-readable media according to claim 11, wherein: The report is based on the first PHR, and When the instruction is executed by the one or more processors, it also causes the UE to generate a second report based on the second PHR.

13. The one or more computer-readable media of claim 12, wherein the instructions, when executed by the one or more processors, further cause the UE to generate a message instructing the UE to send the second report.

14. One or more computer-readable media according to any one of claims 11 to 13, wherein the report does not include the first PHR or the second PHR.

15. One or more computer-readable media according to any one of claims 11 to 13, wherein the report includes the minimum of the first PHR and the second PHR, the maximum of the first PHR and the second PHR, or the average of the first PHR and the second PHR.

16. One or more computer-readable media according to any one of claims 11 to 13, wherein the instructions, when executed by one or more processors, further cause the user equipment to acquire: First configuration information of the PHR triggering condition of the first beam; and The second configuration information for the PHR triggering condition of the second beam.

17. One or more computer-readable media according to any one of claims 11 to 13, wherein the first PHR is transmitted based on the actual physical uplink shared channel (PUSCH) and the second PHR is transmitted based on the reference PUSCH.

18. A base station, the base station comprising: Processing circuit, the processing circuit being used for: Send scheduling information to the user equipment (UE) to schedule multiple repetitions of uplink data transmission on at least two beams of the component carrier; Send to the UE a first set of power control parameters for the first beam of the at least two beams and a second set of power control parameters for the second beam of the at least two beams; as well as In at least one of the plurality of repetitions, a first power headroom report (PHR) or a second PHR is received from the UE, wherein the second PHR is calculated based on: The assumption that the UE did not perform uplink data transmission on the second CC during the second repetition of the plurality of repetitions, or The assumption that the uplink data transmission state of the UE on the second CC during the second repetition is equivalent to the uplink data transmission state of the UE on the second CC during the first repetition; as well as A memory coupled to the processing circuitry, the memory being used to store the PHR.

19. The base station of claim 18, wherein the processing circuit is configured to send to the UE: First configuration information of the PHR triggering condition of the first beam; and The second configuration information for the PHR triggering condition of the second beam.

20. The base station according to claim 19, wherein: The first configuration information is used to indicate a first path loss threshold, and The second configuration information is used to indicate a second path loss threshold that is different from the first path loss threshold.

21. The base station according to claim 19, wherein: The first configuration information is used to indicate a first maximum power transmit MPE threshold, and The second configuration information is used to indicate a second MPE threshold that is different from the first MPE threshold.

22. The base station according to any one of claims 18 to 21, wherein the processing circuitry is configured to send configuration information to the UE to indicate the number of PHRs to be transmitted.

23. The base station according to any one of claims 18 to 21, wherein the processing circuitry is configured to receive from the UE an indication of the ability to report more than one PHR during uplink data transmission.

Images