Power headroom reporting for serving cells

Abstract

Methods and apparatus for Power Headroom Report (PHR) for a serving cell, wherein an active BWP of the serving cell is a dormant BWP. The UE sends a PHR reporting the PH of the serving cell to at least one network node; the network node receives, from the UE, the PHR reporting the PH of the serving cell, and obtains a PH value from the PHR of the serving cell. Here, at least one of the following is reported for the serving cell: 1) Type 1PH; 2) type 3PH; 3) a specified field indicating whether the PH is type 1 or type 3; and 4) indicating whether the service cell is on the dormant BWP or on the non-dormant BWP.

Description

[0001] Description of Divisional Application

[0002] This application is a divisional application of the patent application with the application date of May 20, 2020, application number 202080102708.1, and invention title "Power Headroom Report of Serving Cell". Technical Field

[0003] The teachings of the example embodiments according to the present disclosure generally relate to wireless communication, and more specifically, to PHR of a serving cell. Background Art

[0004] This section is intended to provide background or context for the example embodiments of the present disclosure. The descriptions herein may include concepts that can be pursued, but are not necessarily concepts that have been previously envisioned or pursued. Therefore, unless otherwise indicated herein, the content described in this section is not prior art to the specification and claims of this application and will not be admitted as prior art by including it in this section.

[0005] Some abbreviations that can be found in the specification and / or drawings are defined as follows:[[]]

[0006] A-CSI Aperiodic CSI

[0007] BFD Beam Failure Detection

[0008] BFR Beam Failure Recovery

[0009] BWP Bandwidth Part

[0010] CSI Channel State Information

[0011] DL-SCH Downlink Shared Channel

[0012] gNB 5G Node B / Base Station

[0013] HARQ Hybrid Automatic Repeat Request

[0014] LS Liaison Statement

[0015] LTE Long Term Evolution

[0016] MAC CE Medium Access Control Control Element

[0017] NR New Radio (5G)

[0018] NW Network

[0019] PCell Primary Cell

[0020] PDCCH Physical Downlink Control Channel

[0021] PH Power Headroom

[0022] PHR Power Headroom Report

[0023] P-SRS Periodic SRS

[0024] PSCell Primary and Secondary Cell

[0025] PUCCH Physical Uplink Control Channel

[0026] RAN Radio Access Network

[0027] Rel Release

[0028] RRC Radio Resource Control

[0029] SCell Secondary Cell

[0030] SP / A-SRS Semi-Persistent / Aperiodic SRS

[0031] SpCell Special Cell (PCell / PSCell)

[0032] SRS Sounding Reference Signal

[0033] UE User Equipment

[0034] UL Uplink

[0035] UL-SCH Uplink Shared Channel

[0036] In LTE, the so-called "Dormant SCell State" was introduced in Rel-15 according to the following:

[0037] - No PDCCH monitoring;

[0038] - No UL transmission;

[0039] - Only periodic CSI reporting via the PCell is allowed.

[0040] The introduction of this state is to achieve power saving while also having a faster SCell activation than a deactivated SCell.

[0041] In NR, a similar concept is introduced via the "Dormant BWP" introduced in Rel-16 [TS 38.321 from e R2-2004183].

[0042] 1> If the BWP is active and it is a dormant BWP:

[0043] 2> If it is running, stop the bwp-InandorsedCRctivityTimer for this serving cell.

[0044] 2>Do not monitor PDCCH on the BWP;

[0045] 2>Do not monitor the PDCCH of the BWP;

[0046] 2>Do not receive DL-SCH on the BWP;

[0047] 2>If configured, perform CSI measurement on the BWP;

[0048] 2>Do not transmit SRS on the BWP;

[0049] 2>Do not transmit on the UL-SCH of the BWP;

[0050] 2>Do not transmit PUCCH on the BWP.

[0051] 2>Clear any configured downlink allocation and any configured uplink grant type 2 associated with the SCell, respectively;

[0052] 2>Suspend any configured uplink grant type 1 associated with the SCell;

[0053] 2>If configured, perform beam failure detection and if a beam failure is detected, perform beam failure recovery for the SCell. SUMMARY OF THE INVENTION

[0054] The scope sought to be protected by the various embodiments of the present disclosure is described by the independent claims. Embodiments and features (if any) described in this specification that do not fall within the scope of the independent claims will be construed as examples useful for understanding the various embodiments of the present disclosure.

[0055] According to a first aspect, various embodiments provide a method for a PHR of a serving cell, wherein the active BWP of the serving cell is a dormant BWP. The UE sends a PHR reporting the PH of the serving cell to a network node; wherein at least one of the following is reported for the serving cell:

[0056] - Type 1 PH;

[0057] - Type 3 PH;

[0058] - A specified field indicating whether the PH is Type 1 or Type 3;

[0059] - A specified field indicating whether the serving cell is on a dormant BWP or a non-dormant BWP.

[0060] According to a second aspect, various embodiments provide a method for a PHR of a serving cell, where the active BWP of the serving cell is a dormant BWP. The NW node receives from the UE a PHR reporting the PH of the serving cell and obtains the PH value of the serving cell from the PHR. Here, at least one of the following is reported for the serving cell:

[0061] - Type 1 PH;

[0062] - Type 3 PH;

[0063] - A designated field indicating whether the PH is Type 1 or Type 3;

[0064] - A designated field indicating whether the serving cell is on a dormant BWP or a non-dormant BWP.

[0065] According to a third aspect, various embodiments provide a method for a PHR of a serving cell. When the PHR is triggered at a handover event, the UE sends to a network node a PHR reporting the PH of the serving cell, where the handover event is that the active BWP on the serving cell switches from a dormant BWP to a non-dormant BWP or the active BWP on the serving cell switches from a non-dormant BWP to a dormant BWP.

[0066] According to a fourth aspect, various embodiments provide a method for a PHR of a serving cell, where the active BWP of the serving cell is a dormant BWP. The UE sends to at least one network node a PHR reporting the PH of the serving cell; the network node receives from the UE the PHR reporting the PH of the serving cell and obtains the PH value from the PHR of the serving cell. Here, at least one of the following is reported for the serving cell:

[0067] - Type 1 PH;

[0068] - Type 3 PH;

[0069] - A designated field indicating whether the PH is Type 1 or Type 3;

[0070] - A designated field indicating whether the serving cell is on a dormant BWP or a non-dormant BWP.

[0071] According to a fifth aspect, various embodiments provide a UE for a PHR of a serving cell, where the active BWP of the serving cell is a dormant BWP. The UE includes at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, together with the at least one processor, cause the UE to at least perform the following operations: send a PHR reporting the power headroom (PH) of the serving cell to a network node. Herein, report at least one of the following for the serving cell:

[0072] - Type 1 PH;

[0073] - Type 3 PH;

[0074] - a specified field indicating whether the PH is Type 1 or Type 3;

[0075] - a specified field indicating whether the serving cell is on a dormant BWP or a non-dormant BWP.

[0076] According to a sixth aspect, various embodiments provide a network node for a PHR of a serving cell, where the active BWP of the serving cell is a dormant BWP. The NW node includes at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, together with the at least one processor, cause the network node to at least perform the following operations: receive a PHR reporting the PH of the serving cell from a UE and obtain the PH value of the serving cell from the PHR. Herein, report at least one of the following for the serving cell:

[0077] - Type 1 PH;

[0078] - Type 3 PH;

[0079] - a specified field indicating whether the PH is Type 1 or Type 3;

[0080] - a specified field indicating whether the serving cell is on a dormant BWP or a non-dormant BWP.

[0081] According to a seventh aspect, various embodiments provide a UE for a PHR of a serving cell. The UE includes at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the UE to at least perform the following operations: when the PHR is triggered at a handover event, send a PHR reporting the PH of the serving cell, where the handover event is that the active BWP on the serving cell switches from a dormant BWP to a non-dormant BWP or the active BWP on the serving cell switches from a non-dormant BWP to a dormant BWP.

[0082] According to an eighth aspect, various embodiments provide a system for a PHR of a serving cell, where the active BWP of the serving cell is a dormant BWP. The system includes a UE and at least one network node. The UE includes at least one first processor and at least one first memory including first computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the UE to at least perform the following operations: send a PHR reporting the PH of the serving cell to the network node. The network node includes at least one second processor and at least one second memory including second computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the network node to at least perform the following operations: receive from the UE a PHR reporting the PH of the serving cell and obtain the PH value of the serving cell from the PHR. Here, at least one of the following is reported for the serving cell:

[0083] - type 1 PH;

[0084] - type 3 PH;

[0085] - a specified field indicating whether the PH is type 1 or type 3;

[0086] - a specified field indicating whether the serving cell is on a dormant BWP or a non-dormant BWP.

[0087] According to some embodiments, the reported PH is type 1 PH, where a virtual field indicates the use of a PUSCH reference format.

[0088] According to some embodiments, depending on whether there is an SRS transmission on the dormant BWP when reporting the PHR, the reported PH is type 3 PH.

[0089] According to some embodiments, the PHR is triggered upon a handover event, where the handover event is the active BWP on the serving cell switching from a dormant BWP to a non-dormant BWP or the active BWP on the serving cell switching from a non-dormant BWP to a dormant BWP.

[0090] According to some embodiments, if the PHR has not been reported for the serving cell when the active BWP is a dormant BWP, the PHR trigger occurs when the active BWP switches from a dormant BWP to a non-dormant BWP. Further, the UE continues downlink reference signal measurements for PH calculation without reporting to the network node until the PHR is triggered after the active BWP switches from a dormant BWP to a non-dormant BWP. Additionally, when the active BWP is a dormant BWP, the triggering of the PHR is per serving cell. The triggering of the PHR is configured by the network node.

[0091] According to some embodiments, when the first active BWP of the serving cell is not a dormant BWP, the PHR trigger occurs when the serving cell is activated. Additionally, when the active BWP is a dormant BWP, the triggering of the PHR is per serving cell. The triggering of the PHR is configured by the network node.

[0092] According to some embodiments, the UE is configured with dual connectivity to serving cells served by two network nodes, and the network node to which the UE sends the PHR is one of the two network nodes. BRIEF DESCRIPTION OF THE DRAWINGS

[0093] The above and other aspects, features, and benefits of various embodiments of the present disclosure will become more fully apparent from the following detailed description taken in conjunction with the reference drawings, in which like reference numerals are used to designate like or equivalent elements. The drawings are shown for the purpose of facilitating a better understanding of the embodiments of the present disclosure and the drawings are not necessarily drawn to scale. In the drawings:

[0094] Figure 1 A general block diagram showing various apparatuses for implementing some example embodiments of the present disclosure;

[0095] Figure 2a A method executable by a device according to some example embodiments of the present disclosure is shown; Figure 2b and Figure 2c Examples of methods executable by a UE and a network node according to some example embodiments of the present disclosure are shown, respectively.

[0096] Figure 3Shows an example of Table 6.1.3.9-1 according to some example embodiments of the present disclosure, the table showing multiple-entry PHR MAC CE where the highest ServCellIndex of the serving cell with a configured uplink is less than 8; and

[0097] Figure 4 Shows an example of Table 6.1.3.9-1 according to some example embodiments of the present disclosure, the table showing multiple-entry PHR MAC CE where the highest ServCellIndex of the serving cell with a configured uplink is equal to or higher than 8. Detailed Description

[0098] The principles of the present disclosure will now be described with reference to some example embodiments. It should be understood that the description of these example embodiments is for illustration purposes only and to assist those skilled in the art in understanding and implementing the present disclosure, without indicating any limitation on the scope of the present disclosure. The embodiments described herein can be implemented in various ways not limited to the ways described below.

[0099] In the following description and claims, unless otherwise defined, all technical terms used herein have the same meaning as commonly understood by those skilled in the art to which the present disclosure pertains.

[0100] As used herein, the term "terminal device" or "user equipment" (UE) refers to any terminal device capable of wireless communication with each other or with a base station. The communication may involve transmitting and / or receiving wireless signals using electromagnetic signals, radio waves, infrared signals, and / or other types of signals suitable for transmitting information in the air. In some example embodiments, the UE may be configured to transmit and / or receive information without direct human interaction. For example, when triggered by an internal or external event, or in response to a request from the network side, the UE may transmit information to a network node according to a predetermined schedule.

[0101] Examples of UEs include, but are not limited to, user equipment (UE) (such as a smart phone), a wireless-enabled tablet computer, a laptop embedded device (LEE), a laptop-mounted device (LME), a wireless client device (CPE), a sensor, a metering device, a personal wearable device (such as a watch, etc.), and / or a vehicle capable of communication. For the purpose of discussion, some example embodiments will be described with reference to a UE as an example of a terminal device, and the terms "terminal device" and "user equipment" (UE) may be used interchangeably in the context of the present disclosure.

[0102] As used herein, the term "network node" refers to a device through which services can be provided to a terminal device in a communication network. A network node can include an access network node and a core network node. An access network node can include any suitable device through which a terminal device or UE can access the communication network. Examples of access network nodes include relays, access points (APs), transmit points (TRPs), Node Bs (NodeB or NB), evolved Node Bs (eNodeB or eNB), New Radio (NR) Node Bs (gNB), remote radio modules (RRUs), radio heads (RHs), remote radio heads (RRHs), low-power nodes (such as pico nodes, femto nodes), and so on.

[0103] Communication systems and associated devices (e.g., UEs and network nodes) typically operate according to a given standard or specification that describes what the various entities associated with the system are permitted to do and how it should be implemented. Communication protocols and / or parameters applied to the connection are also typically defined. An example of a communication system is the Universal Mobile Telecommunications System (UMTS) radio access technology and the Long-Term Evolution (LTE) of the so-called 5G or New Radio (NR) network.

[0104] Before describing the exemplary embodiments of the present disclosure in detail, reference is made to Figure 1 for a simplified block diagram of various electronic devices suitable for practicing some exemplary embodiments of the present disclosure.

[0105] Figure 1 A block diagram of one possible and non-limiting exemplary system in which some exemplary embodiments of the present disclosure can be practiced is shown. In Figure 1 UE 10 communicates wirelessly with wireless network 1. The UE is a wireless device that can access the wireless network and is typically a mobile device. UE 10 can include, for example, one or more processors DP 10A, one or more memories MEM 10B, and one or more transceivers TRANS 10D interconnected by one or more buses. Each of the one or more transceivers TRANS 10D can include a receiver and a transmitter. The one or more buses can be an address bus, a data bus, or a control bus, and can include any interconnecting mechanism, such as a series of lines on a motherboard or integrated circuit, optical fibers, or other optical communication devices, and so on. The one or more transceivers TRANS 10D can be connected to one or more antennas for communications 21 and 22 with NN 12 and NN 13, respectively. The one or more memories MEM 10B include computer program code PROG 10C. UE 10 can communicate with NN 12 and / or NN 13 via a wireless link.

[0106] NN 12 (which can be an NR / 5G Node B, an evolved NB, or an LTE device) is associated with a device (such asFigure 1 a network node communicating with the NN 13 and / or the UE 10, such as a master or secondary node base station (e.g., for NR or LTE). The NN 12 may provide access to the wireless device, such as access of the UE 10 to the wireless network 1. The NN 12 may include, for example, one or more processors DP 12A, one or more memories MEM 12C, and one or more transceivers TRANS12D interconnected by one or more buses. According to some example embodiments, these TRANS12D may include X2 and / or Xn interfaces for performing some example embodiments of the present disclosure. Each of the one or more transceivers TRANS12D may include a receiver and a transmitter. The one or more transceivers TRANS12D may be connected to one or more antennas, for example, to communicate with the UE 10 via at least link 21. The one or more memories MEM 12B and the computer program code PROG 12C may be configured to, together with the one or more processors DP 12A, cause the NN 12 to perform one or more operations as described herein. The NN 12 may communicate with another network node (e.g., gNB or eNB) or a device such as the NN 13. Additionally, the link 21 and / or any other link may be wired or wireless or a combination of wired and wireless, and may implement, for example, an X2 or Xn interface. Additionally, the link 21 may pass through other network nodes, such as but not limited to NCE / MME / SGW devices, such as Figure 1 the NCE 14.

[0107] In some embodiments, NN 13 may include mobility function devices, such as an AMF or an SMF. In some embodiments, NN 13 may include an NR / 5G Node B (also referred to as a gNB) or possibly an evolved Node B (eNB), which may be a primary or secondary node base station (e.g., for NR or LTE) communicating with devices such as NN 12 and / or UE 10 and / or the wireless network 1. NN 13 may include, for example, one or more processors DP 13A, one or more memories MEM 13B, one or more network interfaces, and one or more transceivers TRANS12D interconnected by one or more buses. According to some example embodiments, these network interfaces of NN 13 may include X2 and / or Xn interfaces for performing some example embodiments of the present disclosure. Each of the one or more transceivers TRANS13D may include a receiver and a transmitter connected to one or more antennas. The one or more memories MEM 13B may include computer program code PROG 13C. For example, the one or more memories MEM 13B and the computer program code PROG 13C may be configured to, together with the one or more processors DP 13A, cause NN 13 to perform one or more operations as described herein. NN 13 may communicate with another mobility function device and / or a gNB (such as NN 12) using, for example, link 32, and may communicate with UE 10 or any other device using, for example, link 22 or another link. These links may be wired or wireless or a combination of wired and wireless, and may implement, for example, an X2 or Xn interface. Additionally, link 22 may pass through other network nodes, such as but not limited to an NCE / MME / SGW device, such as Figure 1 the NCE 14.

[0108] Figure 1 The one or more buses of the devices may be an address bus, a data bus, or a control bus, and may include any interconnect mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optic or other optical communication devices, wireless channels, etc. For example, one or more of the transceivers TRANS12D, TRANS13D, and / or TRANS10D may be implemented as a remote radio head (RRH), where other elements of NN 12 are physically located at a different location from the RRH, and the one or more buses may be partially implemented as an optical cable for connecting the other elements of NN 12 to the RRH.

[0109] It should be noted that although Figure 1 network nodes such as NN 12 and NN 13 are shown, any of these nodes may be incorporated into or incorporated into an eNB or gNB and may still be configured to perform the example embodiments of the present disclosure.

[0110] It should also be noted that the descriptions herein indicate that a "cell" performs some functions, but it should be clear that the network node providing the cell (e.g., eNB or gNB) performs the functions, and in some cases, the user equipment and / or the mobility management function entity are used to facilitate. Additionally, a cell forms part of a gNB, and there can be multiple cells per gNB.

[0111] The wireless network 1 may include a network control element (NCE) 14, which may include MME (Mobility Management Entity) / SGW (Serving Gateway) functionality, and the network control element provides connectivity to another network (such as a telephone network and / or a data communication network (e.g., the Internet)). NN 12 and NN 13 may be coupled to the NCE 14 via link 31 and / or link 32. Additionally, it should be noted that the operations performed by NN 13 according to some example embodiments may also be performed at the NCE 14.

[0112] The NCE 14 may include, for example, one or more processors DP 14A, one or more memories MEM 14B, and one or more network interfaces (N / W I / F) interconnected by one or more buses, and the one or more buses are coupled to link 13 and / or 14. According to some example embodiments, these network interfaces may include X2 and / or Xn interfaces for performing some example embodiments of the present disclosure. One or more memories MEM 14B may include computer program code PROG 14C. One or more memories MEM 14B and computer program code PROG 14C may be configured to, together with one or more processors DP 14A, cause the NCE 14 to perform one or more operations that may be required to support the operations according to some example embodiments of the present disclosure.

[0113] The wireless network 1 may implement network virtualization, which is the process of combining hardware and software network resources and network functionality into a single software-based management entity (i.e., a virtual network). Network virtualization involves platform virtualization, usually combined with resource virtualization. Network virtualization is classified as external, i.e., combining many networks or parts of networks into virtual units, or internal, i.e., providing network-like functionality to software containers on a single system. It should be noted that hardware (such as processors DP10, DP12A, DP13A, and / or DP14A and memories MEM 10B, MEM 12B, MEM 13B, and / or MEM 14B) may still be used to some extent to implement the virtualized entities resulting from network virtualization, and likewise, such virtualized entities produce technical effects.

[0114] The computer-readable memories MEM 12B, MEM 13B, and MEM 14B can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The computer-readable memories MEM 12B, MEM 13B, and MEM 14B can be devices for performing storage functions. The processors DP10, DP12A, DP13A, and DP14A can be of any type suitable for the local technical environment and can include, by way of non-limiting example, one or more of the following: general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), and processors based on multi-core processor architectures. The processors DP10, DP12A, DP13A, and DP14A can be devices for performing functions such as controlling UE10, NN 12, NN 13, and other functions as described herein.

[0115] LS is sent from RAN2 to RAN1 to ask if it has found any issues with aperiodic CSI reports that do not support a dormant BWP and SRS transmissions on a dormant BWP. The following is the response from RAN1 (R1-2003075): RAN1 could not reach a consensus on whether to support A-CSI measurements in a dormant BWP (where the report is triggered by another cell such as the PCell) or SP / A-SRS transmissions in a dormant BWP. RAN1 did not find any issues in at least supporting long periodic P-SRS (e.g., >100 ms).

[0116] RAN1 replied to LS in R1-2003075 to resume the previous RAN2 assumption of aperiodic SRS transmissions when the UE is on a dormant DL BWP (possibly also with A-CSI, but this is not yet clear). This issue needs to be resolved in RAN2.

[0117] Assuming no UL transmission when the DL is on a dormant BWP, the following consensus has been reached in RAN2.

[0118] - The UL dormant BWP is not defined, and the UL behavior when the DL BWP switches to a dormant BWP is detailed in TS38.321.

[0119] - RAN2 confirms that the UE does not switch the UL BWP (for FDD) due to a transition from dormant to non-dormant or from non-dormant to dormant (as far as BWP switching is concerned, this has not changed so far).

[0120] - Activated SCell with an active BWP being a dormant BWP should not be included in the PHR report. For further study, whether PHR triggering factors need to be added / modified.

[0121] Currently, PHR triggering factors are defined in TS 38.321, and the specification has not yet reflected the following consensus: for a dormant BWP, PHR is not reported.

[0122] How PHR works is not discussed. Since the UE starts to perform SRS transmission, whether PHR is needed also needs to be discussed. The NW node needs to know the PH value of the serving cell.

[0123] In addition, in the case of dual connectivity, there may be problems if the PHR content depends on whether the UE is in a dormant BWP or a non-dormant BWP because

[0124] - Another NW node does not know on which BWP the UE is for a cell from another node, and

[0125] - The bitmap in the PHR only indicates whether the PH of the cell (the cell is activated or not) is reported, and

[0126] - The virtual bit only indicates whether the PH is real or virtual.

[0127] Another NW node cannot determine whether the PH is for Type 1 of PUSCH in the non-dormant case or for Type 3 of SRS transmission in the dormant case.

[0128] Now refer to Figures 2a to 2c , which shows an example of a method for PHR of a serving cell according to some example embodiments of the present disclosure. Figure 2a Shows the interaction between the UE and the NW node, while Figure 2b and Figure 2c respectively show the operations performed at the UE and the NW node.

[0129] In step 201, the UE sends a PHR reporting the PH of the serving cell to the NW node.

[0130] Here, the reported PH is indicated by one of the following:

[0131] 1) Type 1 PH;

[0132] 2) Type 3 PH;

[0133] 3) A specified field indicating whether the PH is Type 1 or Type 3;

[0134] 4) A specified field indicating whether the serving cell is on a dormant bandwidth part (BWP) or a non-dormant BWP.

[0135] In some embodiments, the reported PH of the serving cell may be a type 1 PH. When the active BWP of the serving cell is a dormant BWP, the UE may always report a type 1 PH for the cell. In the PHR, a virtual field (V field) is used to indicate whether the PH value is based on real transmission or the reference format. For a type 1 PH, setting the V field to 0 indicates real transmission on the PUSCH, and setting the V field to 1 indicates the use of the PUSCH reference format. In some embodiments, since there is no PUSCH transmission when the DL active BWP is a dormant BWP, only a virtual type 1 PH is reported for the serving cell. In other words, whenever the V bit indicates a virtual PHR, the NW knows that it is of type 1 without ambiguity.

[0136] In the absence of a defined dormant UL BWP, a type 1 virtual PH of the serving cell is reported based on the reference PUSCH of the dormant UL BWP or the active UL BWP.

[0137] In some embodiments, the reported PH of the serving cell may be a type 3 PH. When the SRS is configured to be transmitted in a dormant state, the UE may always report a type 3 for a dormant SCell or a serving cell having an active DL BWP on a dormant BWP. Depending on whether there is an SRS transmission on the dormant BWP when reporting the PHR, a real / virtual type 3 PH is used for reporting. When reporting the PHR, when an SRS transmission occurs on the dormant BWP, the real type 3 PH is included in the PHR. When reporting the PHR and there is no SRS transmission on the dormant BWP, the virtual type 3 PH is included in the PHR.

[0138] In some embodiments, a designated field in the PHR may be used to indicate whether the PH is type 1 or type 3. In an example embodiment of the present disclosure, in the case of a real SRS transmission when reporting the PHR, a type 3 real PH is reported, while in the case where no transmission occurs in the dormant BWP, a virtual type 1 PH may be reported.

[0139] Reference Figure 3 , the figure shows an example of a multi-entry PHR MAC CE, where the highest ServCellIndex of the serving cell with a configured uplink is less than 8. The previously reserved field is denoted as the "D" field to indicate whether the PH is type 1 or type 3. If a type 1 PH is reported, the V field is always set to 1 when the active BWP of this serving cell is a dormant BWP.

[0140] In some embodiments, a designated field in the PHR may be used to indicate whether the serving cell is on a dormant BWP or a non-dormant BWP. In an example embodiment of the present disclosure, the reserved bits in the PHR may be redefined for such indication, and subsequently the NW node will know whether the UE is on a dormant BWP and whether it is reporting a type 1 or type 3 PH.

[0141] Referring again to Figure 3 , the previously reserved field is denoted as the "D" field to indicate whether the PH value is transmitted based on a dormant BWP or a non-dormant BWP. If reporting a type 1 PH, the V field is always set to 1 when the active BWP of this serving cell is a dormant BWP.

[0142] In some embodiments, the PHR may be triggered on an event defined in TS 38.321. In other embodiments, a new triggering event for triggering the PHR is introduced. In an example embodiment of the present disclosure, the new triggering event may be a handover event of the active BWP on the serving cell, which triggers the PHR of the serving cell when the active BWP is switched from a dormant BWP to a non-dormant BWP or when the active BWP is switched from a non-dormant BWP to a dormant BWP.

[0143] In addition, in some embodiments, if the PHR is not reported for a serving cell when the active BWP is a dormant BWP, the trigger occurs when the active BWP is switched from a dormant BWP to a non-dormant BWP. In an example embodiment of the present disclosure, when the dormant BWP is the previously activated BWP, the UE triggers the PHR when activating the non-dormant BWP. In addition, such a trigger may be further subject to whether the PH of the dormant SCell is reported, for example, due to SRS transmission. For example, if the PHR is not reported for an SCell in a dormant state, the PHR is triggered when the non-dormant BWP is activated after the dormant BWP is the previously activated BWP.

[0144] In some embodiments, triggering the PHR when activating a serving cell may be limited to the case where the first active BWP of the serving cell is not a dormant BWP. In other words, for example, in the case where the first active BWP of the serving cell to be activated is a dormant BWP, the UE may not trigger the PHR. For example, in the case where the first active BWP of the serving cell to be activated is not a dormant BWP, the UE may trigger the PHR. In some examples, the serving cell may be activated by the NW node by means of a MAC CE (e.g., SCell activation / deactivation MAC CE) or by means of RRC signaling.

[0145] In some embodiments, before step 201, the UE continues downlink reference signal measurements for PH calculation without reporting to the NW node until a PHR is triggered after the active BWP switches from a dormant BWP to a non-dormant BWP. In an example embodiment of the present disclosure, when in the dormant BWP, the UE continues DL RS measurements for power headroom (PH) calculation but does not report a given SCell. If a PHR is triggered during the active period of the dormant BWP, the UE will send a report to the NW after moving to the non-dormant BWP.

[0146] In some embodiments, PHR is further prohibited within a predefined time. In an example embodiment of the present disclosure, the PHR reporting as in the above embodiments may also be restricted by the phr-ProhibitTimer. If an SCell is placed in the dormant BWP only for a short time, this will allow the NW to limit overly frequent PHR reports.

[0147] In some embodiments, the triggering of the PHR is configured by the NW node. In an example embodiment of the present disclosure, the NW node may configure whether the UE should trigger a PHR when moving from a dormant BWP to a non-dormant BWP. Additionally, such configuration can be done per SCell configured with a dormant BWP.

[0148] In some embodiments, the UE is configured with dual connectivity to serving cells served by two NW nodes. To avoid type 1 / type 3 PHR reporting ambiguity for the other node (MN or SN respectively) due to the other node not knowing which BWP (dormant or non-dormant BWP) the UE is using, a PHR procedure according to an embodiment of the present disclosure for reporting the PH of a serving cell whose active BWP thereon is a dormant BWP.

[0149] Return reference Figures 2b to 2c , at step 202, the NW node receives a PHR reporting the PH of the serving cell; subsequently at step 203, the NW node obtains the reported PH of the serving cell from the PHR.

[0150] In some embodiments, when the PH is always type 1 PH or type 3 PH, the NW node can decode the reported PH. In other embodiments, the NW node can decode the reported PH according to an indication in a specified field that indicates whether the reported PH is type 1 or type 3 or whether the serving cell is on a dormant BWP or a non-dormant BWP.

[0151] In the following text, an example of the specification changes based on TS 38.321 required for the new PHR trigger option in the case of moving from a dormant BWP to a non-dormant BWP is described in detail. Specification changes are made in the following three sections: namely, Power Headroom Report (Section 5.4.6), Bandwidth Part (BWP) operation (Section 5.15), and Multiple Entry PHR MAC CE (Section 6.1.3.9).

[0152] Power Headroom Report (Section 5.4.6)

[0153] The power headroom reporting procedure is used to provide the serving gNB with the following information:

[0154] - Type 1 power headroom: The difference between the nominal UE maximum transmit power for UL-SCH transmission on the active serving cell and the estimated power;

[0155] - Type 2 power headroom: The difference between the nominal UE maximum transmit power for UL-SCH and PUCCH transmission on the SpCell of other MAC entities (i.e., E-UTRA MAC entities in the EN-DC, NE-DC, and NGEN-DC cases) and the estimated power;

[0156] - Type 3 power headroom: The difference between the nominal UE maximum transmit power for SRS transmission on the active serving cell and the estimated power.

[0157] RRC controls the power headroom reporting by configuring the following parameters:

[0158] - phr-PeriodicTimer;

[0159] - phr-ProhibitTimer;

[0160] - phr-Tx-PowerFactorChange;

[0161] - phr-Type2OtherCell;

[0162] - phr-ModeOtherCG;

[0163] - multiplePHR.

[0164] If any of the following events occurs, a Power Headroom Report (PHR) will be triggered:

[0165] - The -phr-ProhibitTimer has expired or has elapsed, and when any MAC entity used as a path loss reference has UL resources for a new transmission, the change in path loss since the last PHR transmission in this MAC entity has exceeded the phr-Tx-PowerFactorChange dB of at least one active serving cell of this MAC entity;

[0166] Note 1: The change in path loss of a cell evaluated above is between the path loss measured currently on the current path loss reference and the path loss measured on the path loss reference used at the transmission time of the last PHR transmission, regardless of whether the path loss reference has changed in between.

[0167] - The -phr-PeriodicTimer has expired;

[0168] - When the power headroom reporting functionality is configured or reconfigured by the upper layer, the configuration or reconfiguration is not used to deactivate the function;

[0169] - In case the first BWP is not a dormant BWP, activate the SCell of any MAC entity with a configured uplink ;

[0170] (Added according to an implementation introduced in this disclosure.)

[0171] - Addition of a PSCell (i.e., a new PSCell is added or changed);

[0172] - When switching the active BWP from a dormant BWP to a non-dormant BWP (as detailed in Article 5.15);

[0173] (This is a triggering event, a new event introduced in this disclosure for triggering the PHR of a serving cell.)

[0174] - The -phr-ProhibitTimer has expired or has elapsed, when the MAC entity has UL resources for a new transmission and the following is true for any active serving cell of any MAC entity with a configured uplink:

[0175] - There are UL resources allocated for transmission or there is a PUCCH transmission on this cell, and when the MAC entity has UL resources allocated for transmission or a PUCCH transmission on this cell, the change in the power back-off required for this cell due to power management (as allowed by P-MPR c as detailed in TS 38.101-1

[14] , TS 38.101-2

[15] and TS 38.101-3

[16] ) since the last PHR transmission has exceeded the phr-x-PowerFactorChange dB.

[0176] Note 2: When the power back-off required due to power management is only temporary (e.g., lasting for a few tens of milliseconds), the MAC entity shall avoid triggering a PHR, and when the PHR is triggered by other triggering conditions, the MAC entity shall avoid reflecting such a temporary decrease in the P CMAX,f,c / PH value.

[0177] Note 3: If a HARQ process is configured with a cg-RetransmissionTimer and if a PHR has been included in the MAC PDU for transmission via this HARQ process but has not yet been transmitted by the lower layer, it depends on how the UE implementation processes the PHR content.

[0178] If the MAC entity has UL resources allocated for a new transmission, the MAC entity shall:

[0179] 1> If the resource is the first UL resource allocated for a new transmission since the last MAC reset:

[0180] 2> Start the phr-PeriodicTimer;

[0181] 1> If the power headroom reporting procedure determines that at least one PHR has been triggered and will not be cancelled; and

[0182] 1> If, due to the LCP defined in Subclause 5.4.3.1, the allocated UL resources can accommodate the MAC CE and its sub-header of the PHR that the MAC entity is configured to transmit:

[0183] 2> If multiplePHR is configured with a value of true:

[0184] 3> For each active serving cell that has a configured uplink associated with any MAC entity and whose active BWP is not a dormant BWP:

[0185] 4> Obtain the value of the type 1 or type 3 power headroom of the corresponding uplink carrier, as detailed in Clause 7.7 of TS 38.213 [6];

[0186] 4> If this MAC entity has UL resources allocated for transmission on this serving cell; or

[0187] 4> If another MAC entity (if configured) has UL resources allocated for transmission on this serving cell and phr-ModeOtherCG is set to true by the upper layer:

[0188] 5> Obtain the value of the corresponding PCMAX,f,c field from the physical layer.

[0189] 3>For each activated serving cell that has a configured uplink associated with any MAC entity and whose active BWP is the dormant BWP for which the configured SRS is targeted:

[0190] Service cell:

[0191] 4>Obtain the value of the virtual type 1 power headroom of the corresponding uplink carrier, as detailed in clause 7.7 of TS 38.213 [6];

[0192] (The NW node obtains the value of the virtual type 1 PH of the active BWP that is the dormant BWP with the configured SRS. Added according to an embodiment introduced in this disclosure.)

[0193] 4>If, when reporting the PHR, this MAC entity has SRS resources allocated for transmission on this serving cell:

[0194] 5>Obtain the value of the actual type 3 power headroom of the corresponding uplink carrier, as detailed in clause 7.7 of TS 38.213 [6];

[0195] 4>Otherwise:

[0196] 5>Obtain the value of the virtual type 1 power headroom of the corresponding uplink carrier, as detailed in clause 7.7 of TS 38.213 [6];

[0197] (The NW node obtains the actual type 3 value for the active BWP that has SRS transmission when reporting the PHR, or the virtual type 1 PH value for the active BWP that is the dormant BWP with the configured SRS. Added according to an embodiment introduced in this disclosure.)

[0198] 3>If phr-Type2OtherCell with the value true is configured:

[0199] 4>If another MAC entity is an E-UTRA MAC entity:

[0200] 5>Obtain the value of the type 2 power headroom of the SpCell of the other MAC entity (i.e., the E-UTRA MAC entity);

[0201] 5>If phr-ModeOtherCG is set to true by the upper layer:

[0202] 6>Obtain the value of the corresponding P CMAX,f,c field of the SpCell of the other MAC entity (i.e., the E-UTRA MAC entity) from the physical layer.

[0203] 3> Indicate that the multiplexing and assembly procedure generates and transmits a multi-entry PHR MAC CE based on the values reported by the physical layer, as defined in clause 6.1.3.9.

[0204] 2> Otherwise (i.e., using the single-entry PHR format):

[0205] 3> Obtain the value of the type 1 power headroom of the corresponding uplink carrier of the PCell from the physical layer;

[0206] of the power headroom;

[0207] 3> Obtain the value of the corresponding P CMAX,f,c field from the physical layer;

[0208] 3> Indicate that the multiplexing and assembly procedure generates and transmits a single-entry PHR MAC CE based on the values reported by the physical layer, as defined in clause 6.1.3.8.

[0209] 2> Start or restart the phr-PeriodicTimer;

[0210] 2> Start or restart the phr-ProhibitTimer;

[0211] 2> Cancel all triggered PHRs.

[0212] Bandwidth Part (BWP) operation (Section 5.15)

[0213] Downlink and uplink (Section 5.15.1)

[0214] Except for clause 12 of TS 38.213 [6], which details the requirements for BWP operation.

[0215] A serving cell may be configured with one or more BWPs, and the maximum number of BWPs per serving cell is detailed in TS38.213 [6].

[0216] BWP switching in the serving cell is sometimes used to activate an inactive BWP and deactivate an active BWP. BWP switching is controlled by a PDCCH indicating a downlink assignment or an uplink grant, by bwp-InactivityTimer, by RRC signaling, or by the MAC entity itself when starting a random access procedure or detecting a consistent LBT failure on the SpCell. When the RRC (re)configuration of the firstActiveDownlinkBWP-Id and / or firstActiveUplinkBWP-Id of the SpCell or the activation of an SCell occurs, the DL BWP and / or UL BWP indicated by the firstActiveDownlinkBWP-Id and / or firstActiveUplinkBWP-Id respectively (as detailed in TS 38.331 [5]) become active without receiving a PDCCH indicating a downlink assignment or an uplink grant. The active BWP of the serving cell is indicated by RRC or PDCCH (as detailed in TS 38.213 [6]). For unpaired spectrum, the DL BWP is paired with the UL BWP, and BWP switching is common for both UL and DL.

[0217] For each SCell, a dormant BWP can be configured by RRC signaling with the dormantDownlinkBWP-Id as described in TS38.331 [5]. Entering or leaving the dormant BWP of an SCell is done by BWP switching using the PDCCH on a per SCell or per group of dormant SCells basis (as detailed in TS 38.213 [6]). The configuration of the group of dormant SCells indicated by dormancySCellGroups is configured by RRC signaling as described in TS 38.331 [5]. When receiving a PDCCH indicating leaving the dormant BWP, the DL BWP indicated by the firstOutside ActiveTimeBWP-Id or by the firstWithinActiveTimeBWP-Id (as detailed in TS 38.331 [5] and TS 38.213 [6]) is activated. The configuration of the dormant BWP for the SpCell or PUCCH SCell is not supported.

[0218] For each active serving cell configured with a BWP, the MAC entity shall:

[0219] 1> If the BWP is active and it is not a dormant BWP:

[0220] 2> Transmit on the UL-SCH on the BWP;

[0221] 2> If a PRACH occasion is configured, transmit on the RACH on the BWP;

[0222] 2>Monitor PDCCH on the BWP;

[0223] 2>Transmit PUCCH on the BWP if configured;

[0224] 2>Report CSI of the BWP;

[0225] 2>Transmit SRS on the BWP if configured;

[0226] 2>Receive DL-SCH on the BWP;

[0227] 2>If the previous active BWP is a dormant BWP:

[0228] 3> Trigger a PHR according to Article 5.4.6.

[0229] (The UE triggers a PHR when the active BWP switches from a dormant BWP to a non-dormant BWP. Added according to an embodiment introduced in the present disclosure.)

[0230] 2>(Re)initialize any suspended configured uplink grants of configured grant type 1 on the active BWP according to the stored configuration (if any) and start with a symbol according to the rules in Section 5.8.2.

[0231] 2>If consistent LBT failure recovery is configured:

[0232] 3>If it is running, stop the lbt-FailureDetectionTimer,

[0233] 3>Set LBT_COUNTER to 0;

[0234] 3>Monitor the LBT failure indication from the lower layer as detailed in Section 5.21.2.

[0235] 1>If the BWP is activated and it is a dormant BWP:

[0236] 2>If it is running, stop the bwp-InactivityTimer of this serving cell.

[0237] 2>Do not monitor PDCCH on the BWP;

[0238] 2>Do not monitor the PDCCH of the BWP;

[0239] 2>Do not receive DL-SCH on the BWP;

[0240] 2>If configured, perform CSI measurement on the BWP;

[0241] 2> Do not transmit SRS on the BWP;

[0242] 2> Do not transmit on the UL-SCH on the BWP;

[0243] 2> Do not transmit PUCCH on the BWP.

[0244] 2> Remove any configured downlink allocation and any configured type 2 uplink grant associated with the SCell, respectively;

[0245] 2> Suspend any configured type 1 uplink grant associated with the SCell;

[0246] 2> If configured, perform beam failure detection and if a beam failure is detected, perform beam failure recovery for the SCell.

[0247] 1> If the BWP is deactivated:

[0248] 2> Do not transmit on the UL-SCH on the BWP;

[0249] 2> Do not transmit on the RACH on the BWP;

[0250] 2> Do not monitor PDCCH on the BWP;

[0251] 2> Do not transmit PUCCH on the BWP;

[0252] 2> Do not report CSI of the BWP;

[0253] 2> Do not transmit SRS on the BWP;

[0254] 2> Do not receive DL-SCH on the BWP;

[0255] 2> Remove any configured downlink allocation and configured type 2 uplink grant of the configured uplink grant on the BWP;

[0256] 2> Suspend any configured type 1 uplink grant of the configured uplink grant on the inactive BWP.

[0257] When starting a random access procedure on the serving cell, after selecting the carrier for performing the random access procedure as detailed in Section 5.1.1, the MAC entity shall, for the selected carrier of this serving cell:

[0258] 1> If no PRACH opportunity is configured for the active UL BWP:

[0259] 2> Switch the active UL BWP to the BWP indicated by initialUplinkBWP;

[0260] 2> If the serving cell is a SpCell:

[0261] 3>Switch the active DL BWP to the BWP indicated by initialDownlinkBWP.

[0262] 1>Otherwise:

[0263] 2>If the serving cell is a SpCell:

[0264] 3>If the active DL BWP does not have the same bwp-Id as the active UL BWP:

[0265] 4>Switch the active DL BWP to the DL BWP that has the same bwp-Id as the active UL BWP.

[0266] 1>If running, stop the bwp-InactivityTimer associated with the active DL BWP of this serving cell.

[0267] 1>If the serving cell is an SCell:

[0268] 2>If running, stop the bwp-InactivityTimer associated with the active DL BWP of the SpCell.

[0269] 1>Perform a random access procedure for the active DL BWP of the SpCell and the active UL BWP of this serving cell.

[0270] If the MAC entity receives a PDCCH for BWP switching of the serving cell, the MAC entity shall:

[0271] 1>If there is no ongoing random access procedure associated with this serving cell; or

[0272] 1>If, after receiving this PDCCH addressed to the C-RNTI, the ongoing random access procedure associated with this serving cell has been successfully completed (as detailed in Articles 5.1.4, 5.1.4a, and 5.1.5):

[0273] 2>Cancel (if any) the triggered consistent LBT failure for this serving cell;

[0274] 2>Perform the BWP switch to the BWP indicated by the PDCCH.

[0275] If, while a random access procedure associated with the serving cell is in progress in the MAC entity, the MAC entity receives a PDCCH for BWP switching for the serving cell or a dormant SCell group, depending on the UE implementation, the UE shall either switch the BWP or ignore the PDCCH for BWP switching, except when receiving a PDCCH for BWP switching addressed to the C-RNTI for successfully completing the random access procedure (as detailed in Sections 5.1.4, 5.1.4a, and 5.1.5). In such a case, the UE shall perform a BWP switch to the BWP indicated by the PDCCH. When receiving a PDCCH for BWP switching instead of successful contention resolution, if the MAC entity decides to perform a BWP switch, the MAC entity shall stop the ongoing random access procedure and initiate a random access procedure after performing the BWP switch; if the MAC decides to ignore the PDCCH for BWP switching, the MAC entity shall continue the ongoing random access procedure on the serving cell.

[0276] When receiving an RRC (re)configuration for BWP switching for the serving cell while a random access procedure associated with the serving cell is in progress in the MAC entity, the MAC entity shall stop the ongoing random access procedure and initiate a random access procedure after performing the BWP switch.

[0277] After receiving an RRC (re)configuration for BWP switching for the serving cell, cancel any triggered LBT failures in this serving cell.

[0278] For each active serving cell configured with bwp-InactivityTimer, the MAC entity shall:

[0279] 1> If defaultDownlinkBWP-Id is configured, and the active DL BWP is not the BWP indicated by defaultDownlinkBWP-Id, and the active DL BWP is not the BWP indicated by dormantDownlinkBWP-Id (if configured); or

[0280] 1> If defaultDownlinkBWP-Id is not configured, and the active DL BWP is not initialDownlinkBWP, and the active DL BWP is not the BWP indicated by dormantDownlink BWP-Id (if configured):

[0281] 2> If a PDCCH addressed to the C-RNTI or CS-RNTI indicating a downlink allocation or an uplink grant is received on the active BWP; or

[0282] 2> If a PDCCH addressed to a C-RNTI or CS-RNTI indicating a downlink allocation or an uplink grant is received for the active BWP; or

[0283] 2> If a MAC PDU is transmitted in a configured uplink grant or a MAC PDU is received in a configured downlink allocation:

[0284] 3> If there is no ongoing random access procedure associated with this serving cell; or

[0285] 3> If an ongoing random access procedure associated with this serving cell is successfully completed after receiving this PDCCH addressed to a C-RNTI (as detailed in Articles 5.1.4, 5.1.4a, and 5.1.5):

[0286] 5.1.4, 5.1.4a, and 5.1.5):

[0287] 4> Start or restart the bwp-InactivityTimer associated with the active DL BWP.

[0288] 2> If the bwp-InactivityTimer associated with the active DL BWP expires:

[0289] 3> If defaultDownlinkBWP-Id is configured:

[0290] 4> Perform a BWP switch to the BWP indicated by defaultDownlinkBWP-Id.

[0291] 3> Otherwise:

[0292] 4> Perform a BWP switch to the initialDownlinkBWP.

[0293] Note: If a random access procedure is initiated on an SCell, both this SCell and the SpCell are associated with this random access procedure.

[0294] 1> If a PDCCH for BWP switch is received and the MAC entity switches the active DL BWP:

[0295] 2> If defaultDownlinkBWP-Id is configured and the MAC entity switches to a DL BWP that is not indicated by defaultDownlinkBWP-Id and is not indicated by dormantDownlinkBWP-Id (if configured); or

[0296] 2> If defaultDownlinkBWP-Id is not configured and the MAC entity switches to a DL BWP that is not the initialDownlinkBWP and is not indicated by dormantDownlinkBWP-Id (if configured):

[0297] 3> Start or restart the bwp-InactivityTimer associated with the active DL BWP.

[0298] Multi-Entry PHR MAC CE (Section 6.1.3.9)

[0299] The multi-entry PHR MAC CE is identified by a MAC sub-header with an LCID, as detailed in Table 6.2.1-2.

[0300] It has a variable size and includes a bitmap, a type 2 PH field for the SpCell of another MAC entity, and an eight-octet containing the associated P CMAX,f,c field (if reported), a type 1 PH field for the PCell, and an eight-octet containing the associated P CMAX,f,c field (if reported). It also includes, in ascending order based on ServCellIndex, one or more of a type X PH field for service cells other than the PCell indicated in the bitmap and an eight-octet containing the associated P CMAX,f,c field (if reported). According to TS 38.213 [6] and TS 36.213

[17] , X is 1 or 3.

[0301] The presence of the type 2 PH field for the SpCell of another MAC entity is configured by phr-Type2OtherCell with a value of true.

[0302] When the highest ServCellIndex of the serving cell with a configured uplink is less than 8, a single eight-octet bitmap is used to indicate the presence of the PH per serving cell, otherwise four eight-octets are used.

[0303] The MAC entity determines whether the PH value of the active serving cell is based on actual transmission or reference format by considering the configured grant and downlink control information. If a PHR MAC CE is reported on the uplink grant received on the PDCCH, the configured grant and downlink control information are received before (and including) the PDCCH occasion in which the first UL grant for a new transmission has been received since the PHR was triggered, and the new transmission may be applicable to the MAC CE for PHR due to the LCP defined in Clause 5.4.3.1; or if a PHR MAC CE is reported on the configured grant, the configured grant and downlink control information are received before the first uplink symbol of the PUSCH transmission minus the PUSCH preparation time (as defined in Clause 7.7 of TS 38.213 [6]).

[0304] For a band combination where the UE does not support dynamic power sharing, the UE may omit the eight - byte containing the power headroom field and the PCMAX,f,c field for serving cells in another MAC entity other than the PCell in another MAC entity, and the reported values of the power headroom of the PCell and P CMAX,f,c depend on the UE implementation.

[0305] The PHR MAC CE is defined as follows:

[0306] - The Ci field: This field indicates the presence of the PH field of the serving cell with ServCellIndex i, as detailed in TS 38.331 [5]. The Ci field is set to 1 to indicate reporting of the PH field of the serving cell with ServCellIndex i. The Ci field is set to 0 to indicate non - reporting of the PH field of the serving cell with ServCellIndex i.

[0307] - The R bit: Reserved bit, set to 0;

[0308] - The V field: This field indicates whether the PH value is based on actual transmission or reference format. For type 1 PH, the V field is set to 0 to indicate actual transmission on the PUSCH, and the V field is set to 1 to indicate use of the PUSCH reference format. For type 2 PH, the V field is set to 0 to indicate actual transmission on the PUCCH, and the V field is set to 1 to indicate use of the PUCCH reference format. For type 3 PH, the V field is set to 0 to indicate actual transmission on the SRS, and the V field is set to 1 to indicate use of the SRS reference format. Additionally, for type 1, type 2, and type 3 PH, the V field is set to 0 to indicate the presence of the eight - byte containing the associated P CMAX,f,c field, and the V field is set to 1 to indicate omission of the eight - byte containing the associated P CMAX,f,c field;

[0309] - Power Headroom (PH): This field indicates the power headroom level. The field length is 6 bits. The reported PH and the corresponding power headroom levels are shown in Table 6.1.3.9-1 of Figure 3 (the corresponding measured values in dB for NR serving cells are detailed in TS 38.133

[11] , while the corresponding measured values in dB for E-UTRA serving cells are detailed in TS 36.133

[12] );

[0310] - P: This field indicates whether the MAC entity applies power back-off due to power management (as allowed by P-MPRc, detailed in TS 38.101-1

[14] , TS 38.101-2

[15] , and TS 38.101-3

[16] ). If power back-off due to power management is not applied, the corresponding P CMAX,f,c field has a different value, and thus the MAC entity shall set the P field to 1.

[0311] - P CMAX,f,c : If present, this field indicates the P of the NR serving cell used to calculate the previous PH field CMAX,f,c (detailed in TS 38.213 [6]) and the P of the E-UTRA serving cell CMAX,c or (detailed in TS 36.213

[17] ). The reported P CMAX,f,c and the corresponding nominal UE transmit power levels are shown in Figure 4 Table 6.1.3.9-2 of (the corresponding measured values in dBm for NR serving cells are detailed in TS 38.133

[11] , while the corresponding measured values in dBm for E-UTRA serving cells are detailed in TS 36.133

[12] ).

[0312] - D: If present, this field indicates whether the PH value is transmitted based on a dormant BWP or a non-dormant BWP.

[0313] (The D field is a designated field used to indicate whether the serving cell is on a dormant BWP or a non-dormant BWP. Added according to an implementation introduced in this disclosure.)

[0314] In general, the various embodiments can be implemented using hardware or dedicated circuits, software, logic, or any combination thereof. For example, some aspects can be implemented using hardware, while other aspects can be implemented using firmware or software that can be executed by a controller, microprocessor, or other computing device, but the present disclosure is not limited thereto. Although the various aspects of the present disclosure may be illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it will be understood that the blocks, devices, systems, techniques, or methods described herein can be implemented (by way of non-limiting example) using hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0315] For example, the embodiments of the present disclosure can be practiced in various components such as integrated circuit modules. The design of integrated circuits is generally a highly automated process. Sophisticated and powerful software tools can be used to convert a logic-level design into a semiconductor circuit design that is easy to etch and form on a semiconductor substrate.

[0316] As used in the present disclosure, the term "circuit" can refer to one or more or all of the following:

[0317] (a) Only hardware circuit implementations (such as implementations in only analog and / or digital circuits), and

[0318] (b) Combinations of hardware circuits and software, such as (when applicable):

[0319] (i) Combinations of analog and / or digital hardware circuits and software / firmware, and

[0320] (ii) Any portion of a hardware processor (including a digital signal processor), software, and memory that work together to cause a device (such as a mobile phone or a server) to perform various functions, and

[0321] (c) Hardware circuits and / or processors that require software (e.g., firmware) to operate, such as a microprocessor or a portion of a microprocessor, but may not require software when it can operate without it.

[0322] This circuit definition applies to all uses of this term in the present disclosure, including in any claims. As another example, as used in the present disclosure, the term "circuit" also encompasses implementations of only hardware circuits or processors (or multiple processors) or a portion of a hardware circuit or processor and its accompanying software and / or firmware. The term "circuit" also encompasses, for example and when applicable to a particular claim element, a baseband integrated circuit or a processor integrated circuit for a mobile device or a similar integrated circuit in a server, a cellular network device, or other computing or network device.

[0323] The term "example" is used herein to mean "serving as an example, instance, or illustration". Any embodiment described herein as an "example" should not necessarily be construed as more preferred or advantageous than other embodiments. All embodiments described in the detailed description are example embodiments provided to enable those skilled in the art to make or use the present disclosure and do not limit the scope of the present disclosure as defined by the claims.

[0324] The foregoing description has provided a complete and informative description of the best mode and apparatus contemplated by the inventors for practicing the present disclosure by way of examples and non-limiting examples. However, various modifications and changes will likely become apparent to those skilled in the art in view of the foregoing description when read in conjunction with the accompanying drawings and appended claims. However, all such and similar modifications of the teachings of the present disclosure will still fall within the scope of the present disclosure.

[0325] It should be noted that the terms "connected", "coupled", or any variant thereof denote any connection or coupling (direct or indirect) between two or more elements and may encompass the presence of one or more intermediate elements between the two elements "connected" or "coupled" together. The coupling or connection between elements can be physical, logical, or a combination thereof. As used herein, by way of several non-limiting and non-exhaustive examples, two elements can be considered to be "connected" or "coupled" together by using one or more wires, cables, and / or printed electrical connections and by using electromagnetic energy (such as electromagnetic energy having wavelengths in the radio frequency region, microwave region, and optical (visible and invisible) regions).

[0326] In addition, it may be advantageous to use some features of some example embodiments of the present disclosure without using other features correspondingly. Thus, the foregoing description should be regarded as illustrative only of the principles of the present disclosure and not as limiting thereof.

Claims

1. A method for power headroom report (PHR) of a serving cell, wherein the active bandwidth part (BWP) of the serving cell is a dormant BWP; The method comprises: sending, by a user equipment (UE), a PHR reporting the power headroom (PH) of the serving cell to a network node; wherein at least one of the following is reported for the serving cell: - Type 1 PH; - Type 3 PH; - a designated field indicating whether the PH is Type 1 or Type 3; - a designated field indicating whether the serving cell is on a dormant BWP or a non-dormant BWP.

2. The method according to claim 1, wherein the reported PH is Type 1 PH, and a virtual field indicates the use of a PUSCH reference format.

3. The method according to claim 1, wherein depending on whether there is an SRS transmission on the dormant BWP when reporting the PHR, the reported PH is Type 3 PH.

4. The method according to claim 1, wherein the PHR is triggered at a handover event, the handover event being that the active BWP on the serving cell switches from a dormant BWP to a non-dormant BWP or the active BWP on the serving cell switches from a non-dormant BWP to a dormant BWP.

5. The method according to claim 4, wherein if no PHR is reported for the serving cell when the active BWP is a dormant BWP, the PHR trigger occurs when the active BWP switches from a dormant BWP to a non-dormant BWP.

6. The method according to claim 4, wherein the method further comprises: continuing downlink reference signal measurement for PH calculation without reporting to the network node until the PHR is triggered after the active BWP switches from a dormant BWP to a non-dormant BWP.

7. The method according to claim 1, wherein when the first active BWP of the serving cell is not a dormant BWP, the PHR trigger occurs when activating the serving cell.

8. The method according to claim 1, wherein the UE is configured with dual connectivity with a serving cell served by two network nodes, and the network node to which the UE sends the PHR is one of the two network nodes.

9. The method according to claim 4 or 7, wherein the trigger of the PHR is configured by the network node.

10. The method according to claim 9, wherein when the active BWP is a dormant BWP, the trigger of the PHR is per serving cell.

11. A method for power headroom report (PHR) of a serving cell, wherein the active bandwidth part (BWP) of the serving cell is a dormant BWP; The method comprises: receiving, by a network node, from a user equipment (UE), a PHR reporting the power headroom (PH) of the serving cell; wherein at least one of the following is reported for the serving cell: - Type 1 PH; - Type 3 PH; - a designated field indicating whether the PH is Type 1 or Type 3; - a designated field indicating whether the serving cell is on a dormant BWP or a non-dormant BWP; and Obtain the PH value of the serving cell from the PHR.

12. The method according to claim 11, wherein the reported PH is a type 1 PH, and the virtual field indicates the use of the PUSCH reference format.

13. The method according to claim 11, wherein depending on whether there is an SRS transmission on the dormant BWP when reporting the PHR, the reported PH is a type 3 PH.

14. The method according to claim 11, wherein the method further comprises: Configure the trigger of the PHR on the UE.

15. The method according to claim 14, wherein the trigger of the PHR is configured at a handover event, and the handover event is that the active BWP on the serving cell switches from the dormant BWP to the non-dormant BWP or the active BWP on the serving cell switches from the non-dormant BWP to the dormant BWP.

16. The method according to claim 14, wherein when the active BWP is the dormant BWP, the trigger of the PHR is per serving cell.

17. The method according to claim 11, wherein the UE is configured with dual connectivity for a serving cell served by two network nodes, and the network node receiving the PHR is one of the two network nodes.

18. A method for power headroom reporting (PHR) for a serving cell, the method comprises: When the PHR is triggered at a handover event, send, by a user equipment (UE), a PHR reporting the power headroom (PH) of the serving cell to a network node, where the handover event is that the active bandwidth part (BWP) on the serving cell switches from the dormant BWP to the non-dormant BWP or the active BWP on the serving cell switches from the non-dormant BWP to the dormant BWP.

19. The method according to claim 18, wherein the reported PH is indicated by one of the following: - Type 1 PH; - Type 3 PH; - A designated field indicating whether the PH is type 1 or type 3; - A designated field indicating whether the serving cell is on the dormant BWP or the non-dormant BWP.

20. A user equipment (UE) for power headroom reporting (PHR) for a serving cell, wherein the active bandwidth part (BWP) of the serving cell is the dormant BWP; The user equipment comprises: At least one processor; and At least one memory, the at least one memory including computer program code; The at least one memory and the computer program code are configured to, together with the at least one processor, cause the UE to at least perform the following operations: Send a PHR reporting the power headroom (PH) of the serving cell to a network node; wherein at least one of the following is reported for the serving cell: - Type 1 PH; - Type 3 PH; - A designated field indicating whether the PH is type 1 or type 3; - A designated field indicating whether the serving cell is on the dormant BWP or the non-dormant BWP.

21. The UE according to claim 20, wherein the reported PH is a type 1 PH, and a virtual field indicates the use of a PUSCH reference format.

22. The UE according to claim 20, wherein depending on whether there is an SRS transmission on the dormant BWP when reporting the PHR, the reported PH is a type 3 PH.

23. The UE according to claim 20, wherein the PHR is triggered at a handover event, the handover event being that the active BWP on the serving cell switches from a dormant BWP to a non-dormant BWP or the active BWP on the serving cell switches from a non-dormant BWP to a dormant BWP.

24. The UE according to claim 23, wherein if the PHR is not reported for the serving cell when the active BWP is a dormant BWP, the PHR trigger occurs when the active BWP switches from a dormant BWP to a non-dormant BWP.

25. The UE according to claim 23, wherein the UE further performs the following operations: Continue downlink reference signal measurement for PH calculation without reporting to the network node until the PHR is triggered after the active BWP switches from a dormant BWP to a non-dormant BWP.

26. The UE according to claim 20, wherein when the first active BWP of the serving cell is not a dormant BWP, the PHR trigger occurs when activating the serving cell.

27. The UE according to claim 20, wherein the UE is configured with dual connectivity to a serving cell served by two network nodes, and the network node to which the UE sends the PHR is one of the two network nodes.

28. The UE according to claim 23 or 26, wherein the trigger of the PHR is configured by the network node.

29. The UE according to claim 28, wherein when the active BWP is a dormant BWP, the trigger of the PHR is performed per serving cell.

30. A network node for power headroom reporting (PHR) of a serving cell, wherein the active bandwidth part (BWP) of the serving cell is a dormant BWP; The network node comprises: at least one processor; and at least one memory, the at least one memory including computer program code; The at least one memory and the computer program code are configured to, together with the at least one processor, cause the network node to at least perform the following operations: Receive a PHR reporting the power headroom (PH) of the serving cell from a user equipment (UE); wherein at least one of the following is reported for the serving cell: - type 1 PH; - type 3 PH; - a designated field indicating whether the PH is type 1 or type 3; - a designated field indicating whether the serving cell is on a dormant BWP or a non-dormant BWP; and Obtain the PH value of the serving cell from the PHR.

31. The network node according to claim 30, wherein the reported PH is a type 1 PH, and a virtual field indicates the use of a PUSCH reference format.

32. The network node according to claim 30, wherein the reported PH is a type 3 PH depending on whether there is an SRS transmission on the dormant BWP when reporting the PHR.

33. The network node according to claim 30, wherein the network node further performs the following steps: Configure the triggering of the PHR on the UE.

34. The network node according to claim 33, wherein the triggering of the PHR is configured at a handover event, the handover event being that the active BWP on the serving cell switches from a dormant BWP to a non-dormant BWP or the active BWP on the serving cell switches from a non-dormant BWP to a dormant BWP.

35. The network node according to claim 33, wherein when the active BWP is a dormant BWP, the triggering of the PHR is per serving cell.

36. The network node according to claim 30, wherein the UE is configured with dual connectivity to a serving cell served by two network nodes, and the network node receiving the PHR is one of the two network nodes.

37. A user equipment (UE) for power headroom report (PHR) of a serving cell, the user equipment comprising: at least one processor; and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to cause the UE to at least perform the following operations together with the at least one processor: When the PHR is triggered at a handover event, send a PHR reporting the power headroom (PH) of the serving cell to a network node, the handover event being that the active bandwidth part (BWP) on the serving cell switches from a dormant BWP to a non-dormant BWP or the active BWP on the serving cell switches from a non-dormant BWP to a dormant BWP.

38. The UE according to claim 37, wherein the reported PH is indicated by one of the following: - Type 1 PH; - Type 3 PH; - A designated field indicating whether the PH is type 1 or type 3; - A designated field indicating whether the serving cell is on a dormant BWP or a non-dormant BWP.

39. A method for power headroom report (PHR) of a serving cell, wherein the active bandwidth part (BWP) of the serving cell is a dormant BWP; the method comprises: Send, by a user equipment (UE), a PHR reporting the power headroom (PH) of the serving cell to at least one network node; wherein at least one of the following is reported for the serving cell: - Type 1 PH; - Type 3 PH; - A designated field indicating whether the PH is type 1 or type 3; - A designated field indicating whether the serving cell is on a dormant BWP or a non-dormant BWP; Receive, by the network node, the PHR reporting the PH of the serving cell from the UE; and Obtain a PH value from the PHR of the serving cell by the network node.

40. A system for power headroom report (PHR) of a serving cell, the system comprising a user equipment (UE) and at least one network node, wherein an active bandwidth part (BWP) of the serving cell is a dormant BWP; wherein the UE comprises: at least one first processor; and at least one first memory, the at least one first memory including first computer program code; the at least one memory and the computer program code are configured to, together with the at least one processor, cause the UE to at least perform the following operations: send a PHR reporting a power headroom (PH) of the serving cell to the network node; wherein at least one of the following is reported for the serving cell: - type 1 PH; - type 3 PH; - a designated field indicating whether the PH is type 1 or type 3; - a designated field indicating whether the serving cell is on a dormant BWP or a non-dormant BWP; wherein the network node comprises: at least one second processor; and at least one second memory, the at least one second memory including second computer program code; the at least one memory and the computer program code are configured to, together with the at least one processor, cause the network node to at least perform the following operations: receive the PHR reporting the PH of the serving cell from the UE; and obtain a PH value of the serving cell from the PHR.

Images