Power headroom reporting for simultaneous multi-panel transmission

Abstract

User equipment (UE) configured to identify conditions configured to trigger power headroom reports (PHRs) for a first and second panel of a UE configured for simultaneous multi-panel transmission (STxMP), and to configure transceiver circuits to transmit PHRs to the network using a physical uplink shared channel (PUSCH) with either the first or second panel of the UE when a transmission opportunity arises.

Description

Technical Field

[0001] The present disclosure generally relates to wireless communication, and more particularly to power headroom reporting for simultaneous multi-panel transmission.

Background Art

[0002] Multiple input multiple output (MIMO) operation may include simultaneous multi-panel transmission (STxMP) in a user equipment (UE). This feature can bring benefits to the UE such as higher uplink throughput and higher reliability. In STxMP operation, the panels can share the transmission power. The UE may report the power headroom to the network to indicate whether there is available transmission power at the UE. The network may consider the power headroom report when determining whether to allocate network resources to the UE. It has been confirmed that there is a need for a technique configured to support power headroom reporting for STxMP. [[ID=1 / 13]]

Summary of the Invention

[0003] Some exemplary embodiments relate to an apparatus of a user equipment (UE), the apparatus having a processing circuit, the processing circuit identifying conditions configured to trigger a power headroom report (PHR) for a first panel and a second panel of the UE configured for simultaneous multi-panel transmission (STxMP), and configuring a transceiver circuit to transmit the PHR to the network using a physical uplink shared channel (PUSCH) at a transmission opportunity using one of the first panel or the second panel of the UE.

[0004] Another exemplary embodiment relates to a processor, which is configured to identify conditions that trigger a power headroom report (PHR) for a first and second panel of a UE configured for simultaneous multi-panel transmission (STxMP), and to configure transceiver circuits to use either the first or second panel of the UE to transmit the PHR to the network using a physical uplink shared channel (PUSCH) when a transmission opportunity arises. [Brief explanation of the drawing]

[0005] [Figure 1] This figure shows exemplary network configurations according to various exemplary embodiments.

[0006] [Figure 2] This figure shows exemplary user equipment (UE) in various exemplary embodiments.

[0007] [Figure 3] This figure shows an exemplary base station in various exemplary embodiments.

[0008] [Figure 4] This is a signaling diagram for power headroom reporting for simultaneous multi-panel transmission (STxMP) in various exemplary embodiments.

[0009] [Figure 5] This document presents exemplary scenarios for power headroom reporting for STxMP through various exemplary embodiments.

[0010] [Figure 6] This illustrates an exemplary scenario in which multiple physical uplink sharing channels (PUSCHs) overlap temporally across multiple component carriers (CCs) and multiple panels after a Power Headroom Report (PHR) is triggered.

[0011] [Figure 7] This section presents exemplary scenarios using various exemplary embodiments.

[0012] [Figure 8] This section presents exemplary scenarios using various exemplary embodiments. [Modes for carrying out the invention]

[0013] Exemplary embodiments can be further understood by referring to the following description and the associated accompanying drawings, where similar elements are denoted by the same reference numerals. The exemplary embodiments relate to power headroom reporting for simultaneous multi-panel transmission (STxMP). However, references to the term "STxMP" are provided for illustrative purposes only. Various entities may refer to this type of multiple-input multiple-output (MIMO) extension by various names.

[0014] Exemplary embodiments are described with respect to user equipment (UE). The exemplary UEs described herein may comprise multiple panels, each having one or more antenna elements. However, references to UEs are provided for illustrative purposes only. Exemplary embodiments may be used with any electronic component, any electronic component capable of establishing network connectivity and comprising hardware, software, and / or firmware for supporting STxMP. Therefore, the UEs described herein can be used to represent any suitable type of electronic component.

[0015] The exemplary embodiments are also described in relation to a fifth-generation (5G) New Radio (NR) network supporting STxMP. However, references to 5G NR networks are provided for illustrative purposes only. The exemplary embodiments may be used in any suitable type of network supporting STxMP.

[0016] Exemplary embodiments are further described with respect to power headroom reporting. Power headroom may indicate whether the UE has available transmit power relative to its maximum transmit power. In some examples, the power headroom parameter may indicate how much more relative transmit power is available to the UE relative to its maximum transmit power capacity. A positive value parameter may indicate that the UE can transmit at higher power or higher throughput than it is currently using. The UE may calculate its power headroom and then send a Power Headroom Report (PHR) to the network (e.g., a base station). The network considers the PHR when deciding whether to allocate network resources to the UE.

[0017] MIMO operation may include STxMP in the UE. STxMP can bring benefits to the UE, such as higher uplink throughput and higher reliability. In STxMP operation, the UE's panels can share transmit power. To facilitate the implementation of STxMP, power headroom reporting should take concurrent multi-panel operation into consideration. Therefore, a technique configured to support power headroom reporting for STxMP is required.

[0018] The exemplary embodiments introduce techniques for various different aspects of power headroom reporting for STxMP. The exemplary techniques introduced herein may be used independently of each other, in conjunction with other currently implemented power headroom reporting mechanisms, in conjunction with future implementations of power headroom reporting mechanisms, or independently of other power headroom reporting mechanisms.

[0019] Figure 1 shows an exemplary network configuration 100 according to various exemplary embodiments. The exemplary network configuration 100 includes a UE 110. The UE 110 can be any type of electronic component configured to communicate over a network, such as, for example, a mobile phone, a tablet computer, a desktop computer, a smartphone, a phablet, an embedded device, a wearable, an Internet of Things (IoT) device, etc. It will be understood by those skilled in the art that the actual network configuration can include any number of UEs used by any number of users. Thus, the example of a single UE 110 is provided for illustrative purposes only.

[0020] The UE 110 can be configured to communicate with one or more networks. In an example of the network configuration 100, the network with which the UE 110 can communicate wirelessly is a 5G NR radio access network (RAN) 120. However, it should be understood that the UE 110 may communicate with other types of networks (such as, for example, a sixth generation (6G) RAN, a 5G cloud RAN, a next generation RAN (NG-RAN), a legacy cellular network, a wireless local area network (WLAN), etc.), and the UE 110 may also communicate with a network via a wired connection. Thus, the UE 110 may have a 5G NR chipset for communicating with the NR RAN 120 and, optionally, any other suitable type of chipset for communicating with other types of networks.

[0021] 5G NR RAN 120 may be part of a cellular network that can be deployed by a network carrier (e.g., Verizon, AT&T, Sprint, T-Mobile, etc.). 5G NR RAN 120 may include cells and base stations configured to transmit and receive traffic from UEs equipped with a suitable cellular chipset. In this example, 5G NR RAN 120 includes gNB 120A. However, the reference to gNB is provided for illustrative purposes only, and exemplary embodiments may be utilized with any suitable type of access node (e.g., Node B, eNode B, HeNB, eNB, gNB, g Node B, macrocell, microcell, small cell, femtocell, etc.).

[0022] Those skilled in the art will understand that any relevant association procedures may be performed for UE 110 to connect to 5G NR RAN 120. For example, as described above, 5G NR RAN 120 may be associated with a particular network carrier that has a contract and credential information (e.g., stored in a SIM card) for UE 110 and / or the user of UE 110. Upon detecting the presence of 5G NR RAN 120, UE 110 may transmit corresponding credential information to associate with 5G NR RAN 120. More specifically, UE 110 may be associated with a specific cell (e.g., gNB 120A).

[0023] The network configuration 100 also includes a cellular core network 130, the Internet 140, an IP Multimedia Subsystem (IMS) 150, and a network services backbone 160. The cellular core network 130 can be considered a set of interconnected components that manage the operation and traffic of the cellular network. The cellular core network 130 also manages the traffic flowing between the cellular network and the Internet 140. The IMS 150 can generally be described as an architecture for transmitting multimedia services to the UE 110 using the IP protocol. The IMS 150 can communicate with the cellular core network 130 and the Internet 140 in order to provide multimedia services to the UE 110. The network services backbone 160 communicates with the Internet 140 and the cellular core network 130 either directly or indirectly. The network services backbone 160 can generally be described as a set of components (e.g., servers, network storage arrangements, etc.) that implement a set of services that can be used to extend the UE 110's ability to communicate with various networks.

[0024] Figure 2 shows an exemplary UE110 in various exemplary embodiments. The UE110 is described with respect to the network configuration 100 of Figure 1. The UE110 may include a processor 205, a memory arrangement 210, a display device 215, an input / output (I / O) device 220, a transceiver 225, and other components 230. The other components 230 may be, for example, multiple panels, each of which includes one or more antenna elements, an audio input device, an audio output device, a power supply, a data acquisition device, ports for electrically connecting the UE110 to other electronic devices, and so on.

[0025] The processor 205 may be configured to run multiple engines for the UE110. For example, the engines may include power headroom reporting for the STxMP engine 235. Power headroom reporting for the STxMP engine 235 may perform various operations related to configuring and running power headroom reporting for STxMP operation.

[0026] The engine 235 described above, which is an application (e.g., a program) executed by processor 205, is provided for illustrative purposes only. The functions associated with engine 235 may also be represented as a separate, integrated component of UE 110, or as a modular component coupled to UE 110, such as an integrated circuit with or without firmware. For example, the integrated circuit may include an input circuit for receiving signals and a processing circuit for processing signals and other information. The engine may also be embodied as one application or a separate application. In addition, in some UEs, the functions described for processor 205 are divided among two or more processors, such as a baseband processor and an application processor. Exemplary embodiments may be implemented in any of these or other configurations of the UE.

[0027] The memory device 210 may be a hardware component configured to store data related to the operations performed by the UE 110. The display device 215 may be a hardware component configured to show data to the user, while the I / O device 220 may be a hardware component that allows the user to make inputs. The display device 215 and the I / O device 220 may be separate components or may be integrated together, such as in a touchscreen.

[0028] The transceiver 225 may be a hardware component configured to establish connections with a 5G NR-RAN 120, an LTE-RAN (not shown), a legacy RAN (not shown), a WLAN (not shown), etc. Therefore, the transceiver 225 may operate on various different frequencies or channels (e.g., a set of consecutive frequencies). The transceiver 225 includes circuitry configured to transmit and / or receive signals (e.g., control signals, data signals). Such signals may be encoded with information implementing one of the methods described herein. The processor 205 may be operably coupled to the transceiver 225 and configured to receive signals from and / or transmit signals to the transceiver 225. The processor 205 may be configured to encode and / or decode signals (e.g., signaling from a base station of the network) to implement one of the methods described herein.

[0029] Figure 3 shows exemplary base station 300 in various exemplary embodiments. Base station 300 may represent any other access node on which gNB120A or UE110 can establish a connection and manage network operations.

[0030] The base station 300 may include a processor 305, a memory device 310, an input / output (I / O) device 315, a transceiver 320, and other components 325. The other components 325 may include, for example, an audio input device, an audio output device, a battery, a data acquisition device, and ports for electrically connecting the base station 300 to other electronic devices and / or a power supply.

[0031] The processor 305 may be configured to run multiple engines for the base station 300. For example, the engines may include power headroom reporting for the STxMP engine 330. Power headroom reporting for the STxMP engine 330 may perform various operations related to the configuration and execution of power headroom reporting for STxMP by the UE 110.

[0032] The engine 330 described above, which is an application (e.g., a program) executed by the processor 305, is merely an example. The functions associated with the engine 330 may also be represented as a separate, integrated component of the base station 300, or as a modular component coupled to the base station 300, such as an integrated circuit with or without firmware. For example, the integrated circuit may include an input circuit for receiving signals and a processing circuit for processing signals and other information. In addition, in some base stations, the functions described for the processor 305 are divided among multiple processors (e.g., a baseband processor, an application processor, etc.). Exemplary embodiments may be implemented in any of these or other configurations of the base station.

[0033] The memory 310 may be a hardware component configured to store data relating to operations performed by the base station 300. The I / O device 315 may be a hardware component or port that allows a user to interact with the base station 300.

[0034] The transceiver 320 may be a hardware component configured to exchange data with the UE 110 and any other UEs in the network configuration 100. The transceiver 320 may operate on a variety of different frequencies or channels (e.g., a set of consecutive frequencies). The transceiver 320 includes circuitry configured to transmit and / or receive signals (e.g., control signals, data signals). Such signals may be encoded with information implementing one of the methods described herein. The processor 305 may be operably coupled to the transceiver 320 and configured to receive signals from and / or transmit signals to the transceiver 320. The processor 305 may be configured to encode and / or decode signals (e.g., signaling from the UE) to implement one of the methods described herein.

[0035] Figure 4 shows signaling diagram 400 for power headroom reporting for STxMP in various exemplary embodiments. Signaling diagram 400 is described with respect to UE110 and gNB120A in Figure 1. Signaling diagram 400 is intended to provide a general overview of power headroom reporting and to provide context for the exemplary techniques introduced herein. The exemplary embodiments are not limited to the power headroom reporting procedures described in signaling diagram 400 and may be used in any appropriate power headroom reporting procedure.

[0036] In 405, UE110 receives power headroom reporting configuration information. The configuration information may be provided using one or more radio resource control (RRC) messages or in any other suitable format.

[0037] At 410, a PHR for STxMP is triggered. The PHR may include power headroom values ​​for one or more panels of the UE. In some examples, there may be a PHR for each panel of the UE configured for STxMP. Thus, throughout this description, references to the term PHR may refer to a first PHR for a first panel of the UE and a second PHR for a second panel of the UE, where the first and second panels are configured to perform STxMP. In some embodiments, as will be described in more detail below, exemplary embodiments may introduce a condition that triggers the UE 110 to send a PHR for STxMP to the network.

[0038] In some embodiments, a prohibit timer (e.g., phr-ProhibitTimer) may be configured for each panel or shared by multiple panels. The configuration of one or more prohibit timers may be configured by the network via RRC, hard-encoded in the 3GPP specification, or provided to the UE110 in any other suitable format. Expiration of a prohibit timer may be a condition for triggering a PHR. In scenarios where prohibit timers are configured per panel, the expiration of one or both timers may be a trigger condition for power headroom reporting.

[0039] Another exemplary condition for triggering a PHR is a change in path loss exceeding a threshold for at least one activated serving cell in any panel used as a path loss reference since the last PHR transmission, when a medium access control (MAC) entity on the UE110 has uplink resources for a new transmission. The threshold may be set by the network via the RRC, hard-encoded in the 3GPP specification, or provided to the UE110 in any other suitable format. In some examples, at least a disable timer and a path loss condition may be used in combination as a trigger for a PHR. Using a disable timer and a path loss condition in combination to trigger a PHR may have the benefit of minimizing the signaling overhead associated with power headroom reporting for STxMP.

[0040] In other embodiments, a periodic timer (e.g., phr-PeriodicTimer) may be set for each panel or shared by multiple panels. Expiration of the periodic timer may be a condition for triggering the PHR. The settings of one or more periodic timers may be set by the network via RRC, hard-encoded in 3GPP specifications, or provided to the UE110 in any other suitable format.

[0041] In another example, a PHR report may be triggered when STxMP operation is enabled. UE110 may identify that STxMP operation is enabled based on one or more RRC messages received from the network, or in any other appropriate manner. Another exemplary condition for triggering a PHR report may be the activation or deactivation of a secondary cell (SCell) that supports STxMP. UE110 may identify the activation of an STxMP-supporting SCell based on one or more RRC messages received from the network, or in any other appropriate manner. The exemplary trigger conditions introduced herein may be used independently of each other, in conjunction with other currently implemented PHR trigger conditions, in conjunction with future implementations of PHR trigger conditions, or independently of other PHR trigger conditions.

[0042] In 415, UE110 receives one or more downlink control information (DCI) on one or more component carriers (CCs). Each DCI may schedule a subsequent PUSCH transmission. It should be understood that one or more DCIs may be received before and / or after the trigger conditions for the PHR occur. In some scenarios, the DCIs may overlap in time with the PHR trigger conditions. It should also be understood that DCIs are not mandatory, and exemplary embodiments may use one or more configured grant (CG) PUSCHs in place of, or in addition to, the PUSCHs scheduled by the DCIs.

[0043] In 420, UE110 transmits a PHR to gNB120A using PUSCH at the transmission opportunity. The PHR may be transmitted using a Media Access Control (MAC) control element (CE) or any other appropriate type of message as described above. The network may take the PHR into consideration when deciding whether and / or how to schedule uplink network resources for UE110.

[0044] At least two different types of power headroom, such as real power headroom and virtual power headroom, may be supported for STxMP operation. As will be described in more detail below, exemplary embodiments introduce a technique for the UE110 to determine whether to use real power headroom or virtual power headroom when calculating PHR for a particular panel.

[0045] Actual power headroom may be calculated by UE110 based on actual transmissions on the panel's component carriers (CCs), and virtual power headroom may be calculated by UE110 based on a reference PUSCH format set by the network via RRC or in another appropriate manner. Thus, throughout this description, the term power headroom may refer to virtual power headroom, actual power headroom, or any other appropriate type of power headroom. However, references to the terms “actual power headroom” and “virtual power headroom” are provided for illustrative purposes only. Various entities may refer to similar concepts by various names. Furthermore, the specific manner in which these types of power headroom values ​​are calculated is outside the scope of the exemplary embodiments.

[0046] In some embodiments, exemplary designs introduce rules that can be used by the UE110 to determine whether to use virtual power headroom or real power headroom for PHR. Some exemplary rules are described in relation to Scenario 500 in Figure 5.

[0047] Figure 5 shows an exemplary scenario 500 of power headroom reporting for STxMP in various exemplary embodiments. Scenario 500 includes a first panel (panel #0) and a second panel (panel #1) of UE110. In this example, each panel operates two CCs, for example, CC#0 and CC#1.

[0048] Scenario 500 shows a timeline in which a PHR is triggered at 505. For panel #0, DCI#1 is received on CC#0 and schedules PUSCH#1. In this example, there is no PUSCH on CC#1 for panel #0. For panel #1, DCI#2 schedules PUSCH#2 on CC#0, and DCI#3 schedules PUSCH#3 on CC#1. The scheduling DCI#2 for PUSCH#2 is received after scheduling DCI#1. The scheduling DCI#3 is received before scheduling DCI#1. In this example, it can be assumed that PUSCH#1 is used to provide a PHR.

[0049] In some embodiments, the following rules may be used by the UE110 to determine whether to use the actual power headroom or the virtual power headroom for a given panel. These rules may be predefined and hard-encoded in the 3GPP specification, or provided to the UE110 in any other suitable format.

[0050] The examples provided below assume that a PUSCH transmission opportunity i is used to transmit PHRs for multiple panels. In one example, UE110 may be configured to calculate virtual power headroom using the PUSCH reference format when UE110 does not transmit a PUSCH in transmission opportunity i for carrier f of panel k. Instead of, or in addition to, the above rules, UE110 may be configured to calculate virtual power headroom using the PUSCH reference format when the scheduling DCI for an actual PUSCH transmission on carrier f of panel k arrives after the first DCI scheduling a PUSCH transmission in PUSCH opportunity i. In other scenarios where a PUSCH is transmitted on carrier f of panel k in PUSCH opportunity i, the actual PHR is calculated based on the actual PUSCH transmission. The term PUSCH opportunity may refer to any transmission opportunity in which a PUSCH may be transmitted.

[0051] As an example within the context of Scenario 500, assume that PUSCH#1 is used to transmit PHRs for at least panels #0 and #1. Since UE110 does not transmit a PUSCH for CC#1 of panel #0, UE110 will calculate the virtual power headroom for this carrier using the rules described above. Since DCI#2 arrives after DCI#1, which schedules the actual PUSCH transmission and PUSCH#1 to be used for the PHR, UE110 can also calculate the virtual power headroom for CC#0 of panel #1.

[0052] Continuing the above example, the actual power headroom for CC#0 of panel #0 does not satisfy any of the exemplary virtual power headroom rules described above, so UE110 shall calculate this actual power headroom. For CC#1 of panel #1, DCI#3 is received before DCI#1, and therefore the actual power headroom for CC#1 of panel #1 does not satisfy any of the exemplary virtual power headroom rules described above, so UE110 shall calculate this actual power headroom.

[0053] The exemplary rules introduced herein may be used independently of each other, in conjunction with other currently implemented rules for power headroom reporting, in conjunction with future implementations of rules for power headroom reporting, or independently of other rules for power headroom reporting.

[0054] Alternatively, the network may use RRC signaling to indicate whether virtual or real power headroom should be reported. For example, when a PHR is transmitted at a PUSCH opportunity i on panel k, the network may use RRC to determine whether UE110 should report real or virtual power headroom for the CC on panel j, where j ≠ k. In this example, the RRC signaling is for the CC on the other panel, and conventional rules may be used to determine whether real or virtual power headroom should be transmitted for the other CC on panel k.

[0055] Virtual power headroom is reported when RRC signaling indicates that virtual power headroom should be reported for CC of panel j. For example, within the context of scenario 500, the network may indicate that one or both of CC#0 and CC#1 of panel #1 should report virtual PHR.

[0056] When the actual power headroom is set by RRC signaling, a virtual power headroom may still be reported in some scenarios. For example, a virtual power headroom may be reported when UE110 does not transmit a PUSCH during a transmit opportunity i for panel j's CC. In another example, when the actual power headroom is set by the network, a virtual power headroom may be reported when the scheduling DCI for the actual PUSCH transmit of panel j's CC arrives after the first DCI scheduling the PUSCH transmit during PUSCH opportunity i. Thus, there may be scenarios in which the CC of another panel reports a virtual PHR even though RRC signaling indicates that an actual PHR should be provided. An exemplary embodiment introduces a UE capability for STxMP operation to indicate whether UE110 supports setting virtual power headroom and / or actual power headroom via RRC signaling for the other panel (e.g., panel j).

[0057] In some embodiments, a scenario may arise in which there are temporally overlapping pushes across CC and panels after a PHR is triggered. An exemplary embodiment introduces a technique for selecting which pushes should be used for the PHR when this type of scenario occurs.

[0058] Figure 6 shows an exemplary scenario 600 in which multiple PUSCHs overlap temporally across CCs and panels after a PHR is triggered. Scenario 600 includes a first panel (Panel #0) and a second panel (Panel #1) of UE110. In this example, each panel operates two CCs, e.g., CC#0 and CC#1.

[0059] Scenario 600 shows a timeline in which a PHR is triggered at 605. For panel #0, DCI#1 is received on CC#0 and schedules PUSCH#1. For panel #0, there is no PUSCH on CC#1. For panel #1, DCI#2 is received on CC#1 and schedules PUSCH#2. For panel #1, there is no PUSCH on CC#0.

[0060] In some embodiments, the earliest PUSCH transmission across CC and panel may be selected to carry a triggered PHR. As an example within the context of exemplary scenario 600, PUSCH#2 may be selected for the PHR because it is scheduled to occur before PUSCH#1.

[0061] In other embodiments, a PUSCH transmission scheduled by the first DCI after the PHR trigger is selected to carry the triggered PHR. As an example within the context of the exemplary scenario 600, PUSCH#1 may be selected for the PHR because DCI#1 is received before DCI#2.

[0062] In some embodiments, exemplary embodiments introduce a technique for a scenario in which there are two or more pushes in a CC slot of panel k where the PHR is calculated, and that slot completely overlaps with a slot for an uplink transmit in the same or different CC of panel j (where j ≠ k) that carries the PHR. In this type of scenario, the earliest push may be reported in the same CC slot of panel k.

[0063] An example of this scenario is shown in Figure 7, where Scenario 700 includes panels #0 and #1 of UE110. Scenario 700 shows a timeline in which a PHR is triggered at 705. For panel #0, CC#0 includes DCI#1 which schedules PUSCH#1. For panel #1, CC#0 includes DCI#2 which schedules PUSCH#2 and DCI#3 which schedules PUSCH#3. Using the exemplary technique described above, PUSCH#2 on panel #1 may be selected for PHR calculation.

[0064] In another embodiment, an exemplary embodiment introduces a technique for a scenario in which the PHR is reported on the CC configured grant (CG) PUSCH of panel k. In this type of scenario, the PHR timing for UE110 to determine whether the PHR is real or virtual is offset (T) from the time of the first uplink symbol of the configured PUSCH transmission. offset This is the point at which DCI is subtracted from T offset If received internally, a virtual PHR may be reported for the corresponding CC. DCI is T offset If received outside, the actual PHR may be reported for the corresponding CC. offset The value may be predefined and hard-encoded according to the 3GPP specification, or it may depend on the subcarrier spacing (SCS) of CG PUSCH.

[0065] An example of this scenario is shown in Figure 8, where Scenario 800 includes panels #0 and #1 of UE110. Scenario 800 shows a timeline in which a PHR is triggered at 805. For panel #0, CC#0 includes CG-PUSCH#1, and there is no PUSCH on CC#1. For panel #1, CC#0 includes DCI#1 which schedules PUSCH#1, and CC#1 includes DCI#2 which schedules PUSCH#2. Using the exemplary technique described above, for CC#0, DCI#1 is T offsetSince it is located within the system, a virtual PHR may be reported, and for CC#1, DCI#2 is T offset Since it is received outside the area, the actual PHR may be reported. [Examples]

[0066] In the first embodiment, a method performed by a user device (UE) includes identifying conditions configured to trigger a power headroom report (PHR) for a first panel and a second panel of the UE configured for simultaneous multi-panel transmission (STxMP), and configuring a transceiver circuit to transmit the PHR to the network using a physical uplink shared channel (PUSCH) on a transmission opportunity, using either the first or second panel of the UE.

[0067] In a second embodiment, the method of the first embodiment further includes receiving a Radio Resource Control (RRC) message containing parameters for at least one prohibit timer, and the conditions configured to trigger a PHR are based on at least one prohibit timer and, since the transmission of a previous PHR, a change in path loss exceeds a threshold for at least one serving cell in any panel of the UE that is used as a path loss reference, when the Media Access Control (MAC) entity of the UE has an uplink resource for a new transmission.

[0068] In the third embodiment, a single disable timer is shared by the first panel and the second panel, in the method of the second embodiment.

[0069] In the fourth embodiment, in the method of the second embodiment, at least one prohibit timer includes a first prohibit timer corresponding to a first panel and a second prohibit timer corresponding to a second panel.

[0070] In a fifth embodiment, the method of the first embodiment further includes receiving a radio resource control (RRC) message containing parameters for at least one periodic timer, and the conditions configured to trigger the PHR are based on at least one periodic timer corresponding to a first panel and a second panel.

[0071] In the sixth embodiment, a single periodic timer is shared by the first panel and the second panel, in the method of the fifth embodiment.

[0072] In the seventh embodiment, in the method of the fifth embodiment, at least one periodic timer includes a first periodic timer corresponding to a first panel and a second periodic timer corresponding to a second panel.

[0073] In the eighth embodiment, the condition configured to trigger the PHR in the method of the first embodiment is when STxMP operation is enabled via Radio Resource Control (RRC).

[0074] In the ninth embodiment, the condition configured to trigger the PHR in the method of the first embodiment is the activation or deactivation of a secondary cell (SCell) configured with STxMP operation.

[0075] In the tenth embodiment, the method of the first embodiment further includes determining whether to use virtual power headroom reporting or real power headroom reporting for the first component carrier (CC) of the first panel.

[0076] In the eleventh embodiment, in the method of the tenth embodiment, the processing circuit decides to use a virtual power headroom report for the first CC of the first panel when the UE does not transmit a PUSCH at a PUSCH opportunity for the first CC of the first panel.

[0077] In the twelfth embodiment, in the method of the tenth embodiment, the processing circuit decides to use virtual power headroom reporting for the first CC of the first panel when the downlink control information (DCI) for an actual push transmission on the first CC of the first panel is received after the DCI used to schedule push opportunities used for PHR.

[0078] In the 13th embodiment, in the method of the 10th embodiment, the processing circuit decides to use actual power headroom reporting for the first CC of the first panel when PUSCH is transmitted on the first CC of the first panel during a PUSCH opportunity.

[0079] In the 14th embodiment, the method of the 10th embodiment further includes decoding a radio resource control (RRC) signaling configured to indicate whether the UE should use real power headroom reporting or virtual power headroom reporting for the first CC of the first panel, and the PHR is transmitted to the network using the second panel.

[0080] In the 15th embodiment, in the method of the 14th embodiment, if the RRC signaling indicates that an actual power headroom report should be reported for the first CC of the first panel, and the UE does not send a PUSCH at a PUSCH opportunity for the first CC of the first panel, a virtual power headroom report is reported for the first CC of the first panel.

[0081] In the sixteenth embodiment, in the method of the fourteenth embodiment, when RRC signaling indicates that an actual power headroom report should be reported for the first CC of the first panel, a virtual power headroom report is reported for the first CC of the first panel when the downlink control information (DCI) for an actual push transmission on the first CC of the first panel is received after the DCI used to schedule the push opportunities used for the PHR.

[0082] In the 17th embodiment, the method of the first embodiment further includes determining whether to use the first push of the first CC of the first panel or the second push of the second CC of the second panel to transport the PHR when the first push and the second push overlap in time.

[0083] In the 18th embodiment, in the method of the 17th embodiment, the processing circuit decides to use the earliest scheduled PUSCH among the first PUSCH and the second PUSCH to transport the PHR.

[0084] In the 19th embodiment, in the method of the 17th embodiment, downlink control information (DCI) for a first push is received after conditions configured to trigger a PHR, and before the DCI for a second push, and the processing circuit decides to use the first push to carry the PHR based on the fact that the DCI for the first push is received before the DCI for the second push.

[0085] In the 20th embodiment, the method of the first embodiment further includes selecting the earliest of the two or more PUSCHs for power headroom calculation for the PHR when the first PUSCH of the first component carrier (CC) of the first panel is used to transport the PHR, and two or more PUSCHs in a slot of the second CC of the second panel overlap in time with the first PUSCH.

[0086] In the 21st embodiment, the method of the first embodiment further includes determining whether to use virtual power headroom or real power headroom for at least one CC of the second panel, based on the time offset of the CG PUSCH relative to the first uplink symbol, when the PUSCH opportunity is a configured grant (CG) PUSCH on a first component carrier (CC) of the first panel.

[0087] In the 22nd embodiment, in the method of the 21st embodiment, the time offset value is at least partially based on the subcarrier spacing (SCS) of CG PUSCH.

[0088] In the 23rd embodiment, the processor is configured to perform any of the methods of the first to 22nd embodiments.

[0089] In the 24th embodiment, the user equipment (UE) comprises a transceiver configured to communicate with a network, and a processor communicatively coupled to the transceiver and configured to perform any of the methods of the first to 22nd embodiments.

[0090] Those familiar with the art will understand that the exemplary embodiments described above may be implemented in any preferred software configuration, hardware configuration, or combination thereof. Exemplary hardware platforms for implementing the exemplary embodiments may include, for example, Intel x86-based platforms, Windows OS, Mac platforms, and MAC OS with compatible operating systems, as well as mobile devices with operating systems such as iOS and Android. The exemplary embodiments described above may be embodied as a program containing lines of code stored in a non-temporary computer-readable storage medium, which, when compiled, can be executed on a processor or microprocessor.

[0091] While this application describes various embodiments, each having different characteristics in various combinations, it will be understood by those familiar with the art that any feature of one embodiment may be combined with features of other embodiments in such a way that no particular feature is specifically disallowed, or that it does not contradict the operation of the device of the disclosed embodiment or the described function in any way.

[0092] It is well understood that the use of personally identifiable information should be governed by privacy policies and practices that are generally recognized as meeting or exceeding industry or government requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and handled in a manner that minimizes the risk of unintended or unauthorized access or use, and the nature of authorized use should be clearly indicated to the user.

[0093] It will be apparent to those familiar with the art that various modifications may be made to this disclosure without departing from the spirit or scope of this disclosure. Accordingly, this disclosure is intended to cover all modifications and variations of this disclosure, insofar as they fall within the scope of the appended claims and equivalents thereof.

Claims

1. A user equipment (UE) device comprising a processing circuit, wherein the processing circuit is Identify the conditions configured to trigger a Power Headroom Report (PHR) for the first and second panels of the UE configured for simultaneous multi-panel transmission (STxMP), Using either the first or second panel of the UE, the transceiver circuit is configured to transmit the PHR to the network using a physical uplink shared channel (PUSCH) during a transmission opportunity. It is structured in such a way. Device.

2. The processing circuit described above The apparatus according to claim 1, further configured to receive a radio resource control (RRC) message including parameters for at least one dormant timer, wherein the conditions configured to trigger the PHR are based on the at least one dormant timer and, when the media access control (MAC) entity of the UE has uplink resources for a new transmission, a change in path loss exceeds a threshold for at least one serving cell in any panel of the UE that has been used as a path loss reference since the transmission of the previous PHR.

3. The apparatus according to claim 2, wherein a single disable timer is shared by the first panel and the second panel.

4. The apparatus according to claim 2, wherein the at least one prohibit timer includes a first prohibit timer corresponding to the first panel and a second prohibit timer corresponding to the second panel.

5. The processing circuit described above The apparatus according to claim 1, further configured to receive a radio resource control (RRC) message containing parameters for at least one periodic timer, wherein the condition configured to trigger the PHR is based on the at least one periodic timer corresponding to the first panel and the second panel.

6. The apparatus according to claim 5, wherein a single periodic timer is shared by the first panel and the second panel.

7. The apparatus according to claim 5, wherein the at least one periodic timer includes a first periodic timer corresponding to the first panel and a second periodic timer corresponding to the second panel.

8. The apparatus according to claim 1, wherein the condition configured to trigger the PHR is when STxMP operation is enabled via radio resource control (RRC).

9. The apparatus according to claim 1, wherein the condition configured to trigger the PHR is the activation or deactivation of a secondary cell (SCell) configured with STxMP operation.

10. The processing circuit described above The apparatus according to claim 1, further configured to determine whether to use virtual power headroom reporting or actual power headroom reporting for the first component carrier (CC) of the first panel.

11. The apparatus according to claim 10, wherein the processing circuit determines to use a virtual power headroom report for the first CC of the first panel when the UE does not transmit a PUSCH at the PUSCH opportunity for the first CC of the first panel.

12. The apparatus according to claim 10, wherein the processing circuit determines to use a virtual power headroom report for the first CC of the first panel when the downlink control information (DCI) for an actual push transmission on the first CC of the first panel is received after the DCI used to schedule the push opportunity used for the PHR.

13. The apparatus according to claim 10, wherein the processing circuit determines to use actual power headroom reporting for the first CC of the first panel when PUSCH is transmitted on the first CC of the first panel during the PUSCH opportunity.

14. The processing circuit described above The apparatus according to claim 10, further configured to decode radio resource control (RRC) signaling configured to indicate whether the UE should use actual power headroom reporting or virtual power headroom reporting for the first CC of the first panel, wherein the PHR is transmitted to the network using the second panel.

15. The apparatus according to claim 14, wherein when the RRC signaling indicates that an actual power headroom report should be reported for the first CC of the first panel, and the UE does not transmit a PUSCH on the PUSCH opportunity for the first CC of the first panel, a virtual power headroom report is reported for the first CC of the first panel.

16. The apparatus according to claim 14, where the RRC signaling indicates that an actual power headroom report should be reported for the first CC of the first panel, and a virtual power headroom report is reported for the first CC of the first panel when the downlink control information (DCI) for an actual push transmission on the first CC of the first panel is received after the DCI used to schedule the push opportunity used for the PHR.

17. The processing circuit described above The apparatus according to claim 1, further configured to determine whether to use the first push of the first CC of the first panel or the second push of the second CC of the second panel to transport the PHR when the first push and the second push overlap in time.

18. The apparatus according to claim 17, wherein the processing circuit determines to use the earliest scheduled PUSCH among the first PUSCH and the second PUSCH to transport the PHR.

19. The apparatus according to claim 17, wherein downlink control information (DCI) for the first push is received after the conditions configured to trigger the PHR, and before the DCI for the second push, and the processing circuit decides to use the first push to carry the PHR based on the fact that the DCI for the first push is received before the DCI for the second push.

20. The processing circuit described above The apparatus according to claim 1, wherein a first push of a first component carrier (CC) of the first panel is used to transport the PHR, and when two or more pushes in a slot of a second CC of the second panel overlap in time with the first push, the apparatus is further configured to select the earliest of the two or more pushes for power headroom calculation for the PHR.

Images