Power headroom report for serving cell

Abstract

A method and apparatus for PHR of a serving cell, wherein the active BWP of the serving cell is a dormant BWP. A UE sends a PHR reporting the PH of the serving cell to at least one network node; the network node receives the PHR reporting the PH of the serving cell from the UE, and obtains a PH value from the PHR of the serving cell. Here, at least one of the following items is reported for the serving cell: 1) Type 1 PH; 2) Type 3 PH; 3) a designated field indicating whether the PH is Type 1 or Type 3; 4) a designated field indicating whether the serving cell is on a dormant BWP or a non-dormant BWP.

Description

Technical Field

[0001] Teachings of example embodiments according to the present disclosure relate generally to wireless communications, and more particularly, to PHR of a serving cell. Background Art

[0002] This section is intended to provide background or context for the example embodiments of the present disclosure. The descriptions herein may include concepts that may be pursued, but not necessarily concepts that were previously conceived or pursued. Therefore, unless otherwise indicated herein, the content described in this section is not prior art to the specification and claims in this application and will not be admitted to be prior art by inclusion in this section.

[0003] Some abbreviations that may be found in the specification and / or drawings are defined herewith as follows:

[0004] A-CSI Aperiodic CSI

[0005] BFD Beam Fault Detection

[0006] BFR Beam Failure Recovery

[0007] BWP Bandwidth Part

[0008] CSI Channel State Information

[0009] DL-SCH Downlink Shared Channel

[0010] gNB 5G Node B / Base Station

[0011] HARQ Hybrid Automatic Repeat Request

[0012] LS Contact Statement

[0013] LTE Long Term Evolution

[0014] MAC CE Media Access Control Element

[0015] NR New Radio (5G)

[0016] NW Network

[0017] PCell Primary Cell

[0018] PDCCH Physical Downlink Control Channel

[0019] PH Power Headroom

[0020] PHR Power Headroom Report

[0021] P-SRS Periodic SRS

[0022] PSCell primary and secondary cells

[0023] PUCCH Physical Uplink Control Channel

[0024] RAN Radio Access Network

[0025] Rel version

[0026] RRC Radio Resource Control

[0027] SCell Secondary Cell

[0028] SP / A-SRS Semi-permanent / Aperiodic SRS

[0029] SpCell Special Cell (PCell / PSCell)

[0030] SRS Sounding Reference Signal

[0031] UE User Equipment

[0032] UL Uplink

[0033] UL-SCH Uplink Shared Channel

[0034] In LTE, the so-called "dormant SCell state" was introduced in Rel-15 according to the following:

[0035] - No PDCCH monitoring;

[0036] - No UL transmission;

[0037] - Periodic CSI reporting is only allowed via PCell.

[0038] This state was introduced to achieve power savings while also having faster SCell activation than deactivated SCells.

[0039] In NR, a similar concept is introduced via "dormant BWP" introduced in Rel-16 [TS 38.321 from Rel-2004183].

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

[0041] 2> If it is running, stop the bwp-Inandorsed CRctivityTimer of this serving cell.

[0042] 2>Do not monitor PDCCH on BWP;

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

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

[0045] 2> If configured, perform CSI measurements on BWP;

[0046] 2> Do not transmit SRS on BWP;

[0047] 2> Not transmitting on UL-SCH on BWP;

[0048] 2> PUCCH is not transmitted on BWP.

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

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

[0051] 2> If configured, perform beam failure detection and perform beam failure recovery on the SCell if beam failure is detected. Summary of the invention

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

[0053] According to the first aspect, various embodiments provide a method for 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 items is reported for the serving cell:

[0054] - Type 1PH;

[0055] - Type 3PH;

[0056] - a designated field indicating whether the PH is type 1 or type 3;

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

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

[0059] - Type 1PH;

[0060] - Type 3PH;

[0061] - a designated field indicating whether the PH is type 1 or type 3;

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

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

[0064] According to a fourth aspect, various embodiments provide a method for 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 at least one network node; the network node receives the PHR reporting the PH of the serving cell from the UE and obtains a PH value from the PHR of the serving cell. Here, at least one of the following items is reported for the serving cell:

[0065] - Type 1PH;

[0066] - Type 3PH;

[0067] - a designated field indicating whether the PH is type 1 or type 3;

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

[0069] According to a fifth aspect, various embodiments provide a UE for PHR of a serving cell, wherein 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 cause the UE to perform at least the following operations together with the at least one processor: send a PHR reporting the power headroom (PH) of the serving cell to a network node. Here, at least one of the following items is reported for the serving cell:

[0070] - Type 1PH;

[0071] - Type 3PH;

[0072] - a designated field indicating whether the PH is type 1 or type 3;

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

[0074] According to a sixth aspect, various embodiments provide a network node for PHR of a serving cell, wherein 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 cause the network node to perform at least the following operations together with the at least one processor: 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. Here, at least one of the following items is reported for the serving cell:

[0075] - Type 1PH;

[0076] - Type 3PH;

[0077] - a designated field indicating whether the PH is type 1 or type 3;

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

[0079] According to a seventh aspect, various embodiments provide a UE for 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, together with the at least one processor, cause the UE to at least perform the following operations: when the PHR is triggered at a switching event, send a PHR reporting the PH of the serving cell to a network node, the switching event being that an active BWP on the serving cell switches from a dormant BWP to a non-dormant BWP or that the active BWP on the serving cell switches from a non-dormant BWP to a dormant BWP.

[0080] According to an eighth aspect, various embodiments provide a system for a PHR of a serving cell, wherein the active BWP of the serving cell is a dormant BWP. The system comprises a UE and at least one network node. The UE comprises at least one first processor and at least one first memory comprising a first computer program code. At least one memory and the computer program code are configured to, together with 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 comprises at least one second processor and at least one second memory comprising a second computer program code. At least one memory and the computer program code are configured to, together with 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 the UE and obtain the PH value of the serving cell from the PHR. Here, at least one of the following items is reported for the serving cell:

[0081] - Type 1PH;

[0082] - Type 3PH;

[0083] - a designated field indicating whether the PH is type 1 or type 3;

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

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

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

[0087] According to some embodiments, the PHR is triggered at a switching event, wherein the switching 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.

[0088] According to some embodiments, if no PHR is reported for the serving cell when the active BWP is a dormant BWP, the PHR triggering occurs when the active BWP switches from a dormant BWP to a non-dormant BWP. In addition, 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. In addition, when the active BWP is a dormant BWP, the triggering of the PHR is performed on each serving cell. The triggering of the PHR is configured by the network node.

[0089] According to some embodiments, when the first active BWP of the serving cell is not a dormant BWP, the PHR triggering occurs when the serving cell is activated. In addition, when the active BWP is a dormant BWP, the PHR triggering is performed on each serving cell. The triggering of the PHR is configured by the network node.

[0090] According to some embodiments, the UE is configured with dual connectivity with 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

[0091] 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 made with reference to the accompanying drawings, in which like reference numerals are used to designate similar or equivalent elements. The drawings are shown to facilitate a better understanding of the embodiments of the present disclosure and are not necessarily drawn to scale, in which:

[0092] Figure 1 A generalized block diagram showing various apparatus for implementing some example embodiments of the present disclosure;

[0093] Figure 2a Methods that may be performed by a device according to some example embodiments of the present disclosure are shown; Figure 2b and Figure 2c Examples of methods that may be performed by a UE and a network node according to some example embodiments of the present disclosure are shown respectively;

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

[0095] Figure 4 An example of Table 6.1.3.9-1 is shown, which shows a multi-entry PHR MAC CE where the highest ServCellIndex of the serving cell with configured uplink is equal to or higher than 8, according to some example embodiments of the present disclosure. DETAILED DESCRIPTION

[0096] The principles of the present disclosure will now be described with reference to some example embodiments. It should be understood that these example embodiments are described only for illustration and to help those skilled in the art understand and implement the present disclosure, without indicating any limitation on the scope of the present disclosure. The embodiments described herein may be implemented in various ways not limited to the ways described below.

[0097] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0098] 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. Communication may involve the transmission and / or reception of wireless signals using electromagnetic signals, radio waves, infrared signals, and / or other types of signals suitable for transmitting information over 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 on a predetermined schedule.

[0099] Examples of UE include, but are not limited to, user equipment (UE) (such as a smart phone), a wireless-enabled tablet, a laptop embedded device (LEE), a laptop mounted device (LME), a wireless client equipment (CPE), a sensor, a metering device, a personal wearable device (such as a watch, etc.), and / or a vehicle capable of communicating. For discussion, some example embodiments will be described with reference to 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.

[0100] As used herein, the term "network node" refers to a device via which services can be provided to terminal devices in a communication network. Network nodes may include access network nodes and core network nodes. Access network nodes may include any suitable device via which a terminal device or UE can access a communication network. Examples of access network nodes include relays, access points (APs), transmission points (TRPs), node Bs (NodeBs or NBs), evolved NodeBs (eNodeBs or eNBs), new radio (NR) NodeBs (gNBs), remote radio modules (RRUs), radio heads (RHs), remote radio heads (RRHs), low power nodes (such as pico nodes, micro nodes), and the like.

[0101] A communication system 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 achieved. Communication protocols and / or parameters applied to the connection are also typically defined. An example of a communication system Long Term Evolution (LTE) is the Universal Mobile Telecommunications System (UMTS) radio access technology and the so-called 5G or New Radio (NR) network.

[0102] Before describing in detail the exemplary embodiments of the present disclosure, Figure 1 , to illustrate a simplified block diagram of various electronic devices that are suitable for use in practicing some example embodiments of the present disclosure.

[0103] Figure 1 A block diagram of one possible and non-limiting example system in which some example embodiments of the present disclosure may be practiced is shown. Figure 1 In the embodiment, UE 10 performs wireless communication with a wireless network 1. UE is a wireless device that can access a wireless network, typically a mobile device. UE 10 may 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 may include a receiver and a transmitter. The one or more buses may be an address bus, a data bus, or a control bus, and may include any interconnection mechanism, such as a series of wires on a motherboard or an integrated circuit, an optical fiber or other optical communication device, and the like. The one or more transceivers TRANS 10D may be connected to one or more antennas for communication 21 and 22 with NN 12 and NN 13, respectively. The one or more memories MEM 10B include a computer program code PROG 10C. UE 10 may communicate with NN 12 and / or NN 13 via a wireless link.

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

[0105] In some embodiments, NN 13 may include a mobility function device, such as an AMF or SMF. In some embodiments, NN 13 may include an NR / 5G Node B (also referred to as a gNB) or may be an evolved NB (eNB), which may be a primary or secondary node base station (e.g., for NR or LTE) that communicates with a device (e.g., NN 12 and / or UE 10 and / or wireless network 1). NN13 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 TRANS 12D interconnected by one or more buses. According to some example embodiments, these network interfaces of NN13 may include X2 and / or Xn interfaces for executing some example embodiments of the present disclosure. Each of the one or more transceivers TRANS 13D may include a receiver and a transmitter connected to one or more antennas. One or more memories MEM 13B may include a computer program code PROG 13C. For example, one or more memories MEM 13B and computer program code PROG 13C may be configured to, together with 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 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 both, and may implement, for example, an X2 or Xn interface. In addition, link 22 may pass through other network nodes, such as, but not limited to, NCE / MME / SGW devices, such as Figure 1 NCE 14.

[0106] Figure 1 The one or more buses of the device may be an address bus, a data bus, or a control bus, and may include any interconnection mechanism, such as a series of wires on a motherboard or integrated circuit, optical fiber or other optical communication equipment, a wireless channel, etc. For example, one or more transceivers TRANS 12D, TRANS 13D and / or TRANS 10D may be implemented as a remote radio head (RRH), where other elements of the NN 12 are physically located in a different location from the RRH, and one or more buses may be implemented in part as optical cables for connecting the other elements of the NN 12 to the RRH.

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

[0108] It should also be noted that the description herein indicates that a "cell" performs some functions, but it should be clear that the network node (e.g., eNB or gNB) providing the cell performs the functions, facilitated in some cases by user equipment and / or mobility management functional devices. In addition, a cell forms part of a gNB, and there may be multiple cells per gNB.

[0109] The wireless network 1 may include a network control element (NCE) 14, which may include MME (mobility management entity) / SGW (serving gateway) functionality and which provides connectivity with 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 NCE 14 via link 31 and / or link 32. In addition, it should be noted that the operations performed by NN 13 according to some example embodiments may also be performed at NCE 14.

[0110] 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 / WI / F) interconnected by one or more buses, the one or more buses being coupled to links 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 cause NCE 14 to perform one or more operations together with one or more processors DP 14A, which may be required to support operations according to some example embodiments of the present disclosure.

[0111] 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 a virtual unit, or as internal, i.e., providing class network functionality to software containers on a single system. It should be noted that the virtualized entities produced by network virtualization can still be implemented to some extent using hardware (such as processors DP10, DP12A, DP13A and / or DP14A and memories MEM 10B, MEM 12B, MEM 13B and / or MEM 14B), and likewise, such virtualized entities produce technical effects.

[0112] The computer-readable memories MEM 12B, MEM 13B, and MEM 14B may be of any type suitable for the local technical environment and may 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 may be devices for performing storage functions. The processors DP10, DP12A, DP13A, and DP14A may be of any type suitable for the local technical environment and may include, as non-limiting examples, one or more of the following: a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. The processors DP10, DP12A, DP13A, and DP14A may be devices for performing functions such as controlling UE 10, NN 12, NN 13, and other functions as described herein.

[0113] LS is sent from RAN2 to RAN1 to ask if it finds any issues with not supporting aperiodic CSI reporting of dormant BWP and not supporting SRS transmission on dormant BWP. Here is the reply from RAN1 (R1-2003075): RAN1 could not reach a consensus on whether to support A-CSI measurements in dormant BWP (where the reporting is triggered by another cell such as PCell) or SP / A-SRS transmission in dormant BWP. RAN1 does not find any issues with supporting at least long periodicity P-SRS (e.g. >100ms).

[0114] RAN1 replied to LS in R1-2003075, resuming the previous RAN2 assumption of aperiodic SRS transmission when the UE is on a dormant DL BWP (possibly also with A-CSI, but this is not yet clear). The problem needs to be solved in RAN2.

[0115] Assuming that no UL transmission is performed when DL is on dormant BWP, the following agreement has been reached in RAN2.

[0116] - UL dormant BWP is not defined, and the UL behavior when the DL BWP is switched to dormant BWP is detailed in TS38.321.

[0117] - RAN2 confirms that the UE will not switch UL BWP (for FDD) due to transitioning from dormant to non-dormant or vice versa (unchanged so far as BWP switching is concerned).

[0118] - The activated SCell whose active BWP is a dormant BWP shall not be included in the PHR report. For further study, whether the PHR triggering factors need to be added / modified.

[0119] PHR triggers are currently defined in TS 38.321 and the specification does not yet reflect the consensus that for dormant BWPs, PHR is not reported.

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

[0121] Furthermore, in case of dual connectivity, if the PHR content depends on whether the UE is a dormant BWP or a non-dormant BWP, this may be problematic because

[0122] - the other NW node does not know which BWP the UE is on for cells from other nodes, and

[0123] - the bitmap in the PHR only indicates whether the PH of a cell is reported (whether the cell is activated or inactive), and

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

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

[0126] Reference now Figure 2a to Figure 2c , the figure 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 UE and NW nodes, and Figure 2b and Figure 2c The operations performed at the UE and NW nodes are shown respectively.

[0127] In step 201, the UE sends a PHR reporting the PH of the serving cell to the NW node. Here, the reported PH is indicated by one of the following:

[0128] 1) Type 1 PH;

[0129] 2) Type 3PH;

[0130] 3) A designated field indicating whether the PH is type 1 or type 3;

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

[0132] 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 a real transmission or a reference format. For Type 1 PH, the V field is set to 0 to indicate a real transmission on the PUSCH, and the V field is set to 1 to indicate 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 Type 1 without ambiguity.

[0133] In case there is no definition of dormant UL BWP, the type 1 virtual PH of the serving cell is reported based on the reference PUSCH of the dormant UL BWP or active UL BWP.

[0134] In some embodiments, the reported PH of the serving cell may be a Type 3 PH. When SRS is configured to be transmitted in dormancy, the UE may always report Type 3 for a dormant SCell or a serving cell with 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 an SRS transmission occurs on the dormant BWP when reporting the PHR, a real Type 3 PH is included in the PHR. When a PHR is reported and there is no SRS transmission on the dormant BWP, a virtual Type 3 PH is included in the PHR.

[0135] 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, a type 3 real PH is reported if a real SRS transmission occurs when the PHR is reported, and a virtual type 1 PH may be reported if no transmission occurs in a dormant BWP.

[0136] refer to Figure 3 , which shows an example of a multi-entry PHR MAC CE where the highest ServCellIndex of the serving cell with 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.

[0137] 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, a reserved bit in the PHR may be redefined for such an indication, and then the NW node will know whether the UE is on a dormant BWP and whether to report type 1 or type 3 PH.

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

[0139] In some embodiments, PHR may be triggered on events defined in TS 38.321. In other embodiments, new triggering events for triggering PHR are introduced. In an example embodiment of the present disclosure, the new triggering event may be a switching event of an active BWP on a serving cell, and when the active BWP switches from a dormant BWP to a non-dormant BWP or the active BWP switches from a non-dormant BWP to a dormant BWP, the PHR of the serving cell is triggered.

[0140] In addition, in some embodiments, if PHR is not reported for the serving cell when the active BWP is a dormant BWP, the triggering 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 a previously activated BWP, the UE triggers PHR when activating the non-dormant BWP. In addition, such triggering may be further subject to whether the PH of the dormant SCell is reported, for example, due to SRS transmission. For example, if PHR is not reported for a dormant SCell, PHR is triggered when the non-dormant BWP is activated after the dormant BWP is a previously activated BWP.

[0141] In some embodiments, triggering a PHR when activating a serving cell may be limited to the case when 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 a 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 a PHR. In some examples, the serving cell may be activated by a NW node by means of a MAC CE (e.g., SCell activation / deactivation MAC CE) or by means of RRC signaling.

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

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

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

[0145] In some embodiments, the UE is configured to have dual connectivity with a serving cell served by two NW nodes. In order to avoid type 1 / type 3 PHR reporting ambiguity for another node (MN or SN) due to the fact that the other node (SN or MN, respectively) does not know which BWP (dormant or non-dormant BWP) the UE is using, a PHR procedure for reporting the PH of a serving cell on which the active BWP is a dormant BWP according to an embodiment of the present disclosure.

[0146] Return to reference Figure 2b to Figure 2c , in step 202, the NW node receives a PHR reporting a PH of a serving cell; then in step 203, the NW node obtains the reported PH of the serving cell from the PHR.

[0147] In some embodiments, the NW node may decode the reported PH when the PH is always type 1 PH or type 3 PH. In other embodiments, the NW node may decode the reported PH according to an indication in a designated field indicating 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.

[0148] In the following, an example of the specification changes based on TS 38.321 required for the new triggering option of PHR 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 reporting (Section 5.4.6), bandwidth part (BWP) operation (Section 5.15), and multi-entry PHR MAC CE (Section 6.1.3.9).

[0149] Power Headroom Report (Section 5.4.6)

[0150] The Power Headroom Reporting procedure is used to provide the following information to the serving gNB:

[0151] - Type 1 power headroom: the difference between the nominal UE maximum transmit power and the estimated power for UL-SCH transmissions for each activated serving cell;

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

[0153] - Type 3 power headroom: The difference between the nominal UE maximum transmit power and the estimated power for SRS transmission of each activated serving cell.

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

[0155] -phr-PeriodicTimer;

[0156] -phr-ProhibitTimer;

[0157] -phr-Tx-PowerFactorChange;

[0158] -phr-Type2OtherCell;

[0159] -phr-ModeOtherCG;

[0160] -multiplePHR.

[0161] A Power Headroom Report (PHR) is triggered if any of the following events occurs:

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

[0163] NOTE 1: The path loss change for a cell assessed above is the path loss currently measured on the current path loss reference and the path loss measured on the path loss reference in use at the time of the last PHR transmission, regardless of whether the path loss reference has changed in the meantime.

[0164] -phr-PeriodicTimer expires;

[0165] - when configuration or reconfiguration of the power headroom reporting functionality is performed by upper layers, the configuration or reconfiguration does not serve to deactivate the functionality;

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

[0167] (Added according to a certain embodiment introduced in this disclosure.)

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

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

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

[0171] -phr-ProhibitTimer expires or has expired when the MAC entity has UL resources for new transmissions and the following is true for any activated serving cell of any MAC entity with configured uplink:

[0172] - 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 power backoff required for this cell due to power management (such as P-MPR) since the last PHR transmission c The change allowed by TS 38.101-1

[14] , TS 38.101-2

[15] and TS 38.101-3

[16] ) exceeds phr-x-PowerFactorChange dB.

[0173] NOTE 2: The MAC entity should avoid triggering PHR when the power backoff required due to power management is only temporarily (e.g., lasting at most tens of milliseconds), and should avoid reflecting PHR when PHR is triggered by other triggering conditions. CMAX,f,c / Such temporary decrease in pH value.

[0174] NOTE 3: If the HARQ process is configured with cg-RetransmissionTimer and if the PHR has been included in the MAC PDU for transmission by this HARQ process but has not yet been transmitted by lower layers, it is up to the UE implementation how to handle the PHR content.

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

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

[0177] 2>Start phr-PeriodicTimer;

[0178] 1> If the Power Headroom Reporting procedure determines that at least one PHR has been triggered and will not be cancelled; and

[0179] 1> If, due to the LCP defined in clause 5.4.3.1, the allocated UL resources can accommodate the MAC CE and its subheaders of the PHR that the MAC entity is configured to transmit:

[0180] 2> If multiplePHR with value true is configured:

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

[0182] 4> obtain the value of the Type 1 or Type 3 power headroom for the corresponding uplink carrier as detailed in Section 7.7 of TS 38.213 [6];

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

[0184] 4> If other MAC entities (if configured) have UL resources allocated for transmission on this serving cell and phr-ModeOtherCG is set to true by upper layers:

[0185] 5> Obtain the corresponding PCMAX, f, c field values ​​from the physical layer.

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

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

[0188] (The NW node obtains the value of the virtual type 1PH where the active BWP is a dormant BWP with a configured SRS. Added according to a certain embodiment introduced in the present disclosure.)

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

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

[0191] 4> Otherwise:

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

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

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

[0195] 4> If the other MAC entity is an E-UTRA MAC entity:

[0196] 5> obtain the value of the type 2 power headroom of the SpCell of another MAC entity (ie, the E-UTRA MAC entity);

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

[0198] 6> Obtain the corresponding P of the SpCell of another MAC entity (ie, E-UTRA MAC entity) from the physical layer CMAX,f,c The value of the field.

[0199] 3> Instructs the multiplexing and assembly procedures to generate and transmit a multi-entry PHR MAC CE based on the values ​​reported by the physical layer, as defined in clause 6.1.3.9.

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

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

[0202] 3> Get the corresponding P from the physical layer CMAX,f,c The value of the field;

[0203] 3> Instructs the multiplexing and assembly procedures to generate and transmit a single-entry PHR MAC CE based on the value reported by the physical layer, as defined in clause 6.1.3.8.

[0204] 2>Start or restart phr-PeriodicTimer;

[0205] 2> Start or restart phr-ProhibitTimer;

[0206] 2>Cancel all triggered PHRs.

[0207] Bandwidth Part (BWP) Operation (Section 5.15)

[0208] Downlink and uplink (Section 5.15.1)

[0209] In addition to clause 12 of TS 38.213[6], this clause also details the requirements for BWP operations.

[0210] A serving cell may be configured with one or more BWPs, and the maximum number of BWPs per serving cell is specified in TS 38.213 [6].

[0211] BWP switching of the serving cell is sometimes used to activate the inactive BWP and deactivate the active BWP. BWP switching is controlled by a PDCCH indicating a downlink allocation or uplink grant, by a bwp-InactivityTimer, by RRC signaling or by the MAC entity itself when starting the random access procedure or detecting a consistent LBT failure on the SpCell. Upon RRC (re)configuration of the firstActiveDownlinkBWP-Id and / or firstActiveUplinkBWP-Id of the SpCell or activation of the SCell, the DLBWP and / or UL BWP indicated by firstActiveDownlinkBWP-Id and / or firstActiveUplinkBWP-Id, respectively (as detailed in TS 38.331 [5]) are active without receiving a PDCCH indicating a downlink allocation or 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.

[0212] For each SCell, a dormant BWP may be configured via RRC signaling with dormantDownlinkBWP-Id, as described in TS 38.331 [5]. SCell entry or exit from a dormant BWP is accomplished by switching BWP per SCell or per dormant SCell group using PDCCH (as described in detail in TS 38.213 [6]). As described in TS 38.331 [5], the dormant SCell group configuration indicated by dormancySCellGroups is configured via RRC signaling. Upon receipt of a PDCCH indicating exit from a dormant BWP, the DL BWP indicated by firstOutsideActiveTimeBWP-Id or by firstWithinActiveTimeBWP-Id (as described in detail in TS 38.331 [5] and TS 38.213 [6]) is activated. Configuration of dormant BWP for SpCell or PUC CH SCell is not supported.

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

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

[0215] 2> Transmit on UL-SCH on BWP;

[0216] 2> If PRACH timing is configured, it is transmitted on RACH on BWP;

[0217] 2>Monitor PDCCH on BWP;

[0218] 2> If configured, PUCCH is transmitted on BWP;

[0219] 2> Report the CSI of BWP;

[0220] 2> Transmit SRS on BWP if configured;

[0221] 2> Receive DL-SCH on BWP;

[0222] 2> If the previously active BWP is a dormant BWP:

[0223] 3> Trigger PHR according to Section 5.4.6.

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

[0225] 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 starting with symbol according to the rules in clause 5.8.2.

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

[0227] 3>Stop lbt-FailureDetectionTimer if it is running,

[0228] 3> Set LBT_COUNTER to 0;

[0229] 3> Monitor LBT fault indications from lower layers as detailed in Section 5.21.2.

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

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

[0232] 2>Do not monitor PDCCH on BWP;

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

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

[0235] 2> If configured, perform CSI measurements on BWP;

[0236] 2> Do not transmit SRS on BWP;

[0237] 2> Not transmitting on UL-SCH on BWP;

[0238] 2> PUCCH is not transmitted on BWP.

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

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

[0241] 2> If configured, perform beam failure detection and perform beam failure recovery on the SCell if beam failure is detected.

[0242] 1> If BWP is disabled:

[0243] 2> Not transmitting on UL-SCH on BWP;

[0244] 2> Not transmitting on RACH on BWP;

[0245] 2>Do not monitor PDCCH on BWP;

[0246] 2> PUCCH is not transmitted on BWP;

[0247] 2> Do not report CSI of BWP;

[0248] 2> Do not transmit SRS on BWP;

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

[0250] 2> Clear any configured downlink allocations and configured uplink grants of configured grant type 2 on the BWP;

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

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

[0253] 1> If PRACH opportunity is not configured for active UL BWP:

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

[0255] 2> If the serving cell is SpCell:

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

[0257] 1> Otherwise:

[0258] 2> If the serving cell is SpCell:

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

[0260] 4> Switch the active DL BWP to a DL BWP with the same bwp-Id as the active UL BWP.

[0261] 1> Stop the bwp-InactivityTimer associated with the active DL BWP of this serving cell if it is running.

[0262] 1> If the serving cell is SCell:

[0263] 2> Stop the bwp-InactivityTimer associated with the active DL BWP of the SpCell if it is running.

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

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

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

[0267] 1> If, upon receipt of this PDCCH addressed to the C-RNTI, an ongoing random access procedure associated with this serving cell (as detailed in clauses 5.1.4, 5.1.4a and 5.1.5) is successfully completed:

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

[0269] 2> Switch the BWP to the BWP indicated by the PDCCH.

[0270] If a random access procedure associated with a serving cell is being performed in the MAC entity, and the MAC entity receives a PDCCH for BWP switching of the serving cell or dormant SCell group, depending on whether the UE implementation switches the BWP or ignores the PDCCH for BWP switching, except for receiving a PDCCH for BWP switching addressed to the C-RNTI in order to successfully complete the random access procedure (as detailed in Articles 5.1.4, 5.1.4a and 5.1.5), in which case the UE shall perform a BWP switch to the BWP indicated by the PDCCH. Upon receiving a PDCCH for BWP switching instead of a 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.

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

[0272] After receiving the RRC (re)configuration for BWP handover of a serving cell, any triggered LBT failure in this serving cell is cancelled.

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

[0274] 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

[0275] 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):

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

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

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

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

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

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

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

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

[0284] 4> Execute switching of BWP to the BWP indicated by defaultDownlinkBWP-Id.

[0285] 3> Otherwise:

[0286] 4>Execute and switch BWP to initialDownlinkBWP.

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

[0288] 1> If PDCCH for BWP switching is received and the MAC entity switches the active DL BWP:

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

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

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

[0292] Multi-entry PHRMACCE (Section 6.1.3.9)

[0293] A multi-entry PHR MAC CE is identified by a MAC subheader with an LCID as detailed in Table 6.2.1-2.

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

[17] , X is 1 or 3.

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

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

[0297] The MAC entity determines whether the PH value of the activated serving cell is based on a real transmission or a reference format by taking into account the configured grant and downlink control information. If the PHR MAC CE is reported on an uplink grant received on the PDCCH, the configured grant and downlink control information are received before (and including) the PDCCH opportunity in which the first UL grant for a new transmission is received since the PHR was triggered, and the new transmission can be adapted to the MAC CE for the PHR due to the LCP defined in clause 5.4.3.1; or if the PHR MAC CE is reported on a 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]).

[0298] For a frequency band combination for which the UE does not support dynamic power sharing, the UE may omit the eight bytes containing the power headroom field and the PCMAX,f,c field for a serving cell in another MAC entity other than the PCell in another MAC entity, and the power headroom and PCMAX,f,c fields of the PCell may be omitted. CMAX,f,c The reported value of depends on the UE implementation.

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

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

[0301] -R: reserved bit, set to 0;

[0302] -V: This field indicates whether the PH value is based on a real transmission or a reference format. For Type 1 PH, the V field is set to 0 to indicate a real transmission on PUSCH, and the V field is set to 1 to indicate the use of the PUSCH reference format. For Type 2 PH, the V field is set to 0 to indicate a real transmission on PUCCH, and the V field is set to 1 to indicate the use of the PUCCH reference format. For Type 3 PH, the V field is set to 0 to indicate a real transmission on SRS, and the V field is set to 1 to indicate the use of the SRS reference format. In addition, for Type 1, Type 2, and Type 3 PH, the V field is set to 0 to indicate the presence of a reference format with an associated PUSCH. CMAX,f,c The V field is set to 1 to indicate that the associated P CMAX,f,c The eight bytes of the field;

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

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

[12] );

[0304] -P: This field indicates whether the MAC entity applies power backoff caused by power management (as allowed by P-MPRc, as detailed in TS 38.101-1

[14] , TS 38.101-2

[15] and TS 38.101-3

[16] ). If power backoff caused by power management is not applied, the corresponding P CMAX,f,c The fields have different values, so the MAC entity should set the P field to 1.

[0305] -P CMAX,f,c PH: If present, this field indicates the PH of the NR serving cell used to calculate the preceding PH field. CMAX,f,c (as detailed in TS 38.213 [6]) and the P of the E-UTRA serving cell CMAX,c or (As 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 (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] ).

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

[0307] (The D field is a designated field for indicating whether the serving cell is on a dormant BWP or a non-dormant BWP. It is added according to a certain embodiment introduced in the present disclosure.)

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

[0309] For example, embodiments of the present disclosure may be practiced in various components such as integrated circuit modules. The design of integrated circuits is generally a highly automated process. Complex and powerful software tools are available to convert logic-level designs into semiconductor circuit designs that are easily etched and formed on semiconductor substrates.

[0310] As used in this disclosure, the term "circuitry" may refer to one, more, or all of the following:

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

[0312] (b) a combination of hardware circuitry and software such as (where applicable):

[0313] (i) a combination of analog and / or digital hardware circuits and software / firmware, and

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

[0315] (c) A hardware circuit and / or processor that requires software (e.g., firmware) to operate, such as a microprocessor or a portion of a microprocessor, but may not require software when the circuit can operate without the software.

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

[0317] The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any implementation described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other implementations. All implementations described in the detailed description are example implementations provided to enable persons skilled in the art to make or use the present disclosure and do not limit the scope of the present disclosure, which is defined by the claims.

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

[0319] It should be noted that the terms "connected," "coupled," or any variations thereof, refer to any connection or coupling (direct or indirect) between two or more elements, and may encompass the presence of one or more intermediate elements between two elements that are "connected" or "coupled" together. The coupling or connection between elements may be physical, logical, or a combination thereof. As used herein, two elements may 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 with wavelengths in the radio frequency region, microwave region, and optical (visible and invisible) region, as several non-limiting and non-exhaustive examples.

[0320] Furthermore, some features of some exemplary embodiments of the disclosure may be used to advantage without the corresponding use of other features.Thus, the foregoing description should be regarded as merely illustrative of the principles of the disclosure, and not in limitation thereof.

Claims

1. A method for reporting power headroom to a network node, the network node being associated with a plurality of serving cells, the method comprising: A power headroom report PHR is triggered by a user equipment UE to report a power headroom PH of a serving cell to a network node, wherein the PHR is triggered upon the following events: if a first BWP of the serving cell is a non-dormant BWP and if the serving cell is an SCell of a MAC entity, activating the serving cell, wherein the MAC entity has a configured uplink; and Downlink reference signal measurements for PH calculation are continued without reporting to the network node until the PHR is triggered after the active BWP is switched from a dormant BWP to a non-dormant BWP.

2. The method of claim 1 , wherein the reported PH for the serving cell is indicated by one of: - Type 1PH; - Type 3PH; - 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.

3. The method of claim 1 or 2, wherein the reported PH for the serving cell is a Type 1 PH with a dummy field indicating that a PUSCH reference format is used, or Wherein, depending on whether there is SRS transmission on the dormant BWP when the PHR is reported, the reported PH for the serving cell is a Type 3 PH. 4 . The method of claim 1 , wherein if no PHR is reported for the serving cell when the active BWP is a dormant BWP, a PHR trigger occurs when the active BWP switches from a dormant BWP to a non-dormant BWP.

5. A user equipment UE configured to report power headroom to a network node, the network node being associated with a plurality of serving cells, the user equipment comprising: at least one processor; and at least one memory, the at least one memory comprising 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: triggering a power headroom report PHR to report a power headroom PH of a serving cell to a network node, wherein the PHR is triggered upon the following event: activating the serving cell if a first BWP of the serving cell is a non-dormant BWP and if the serving cell is an SCell of a MAC entity, wherein the MAC entity has a configured uplink; and Downlink reference signal measurements for PH calculation are continued without reporting to the network node until the PHR is triggered after the active BWP is switched from a dormant BWP to a non-dormant BWP.

6. The UE of claim 5, wherein the reported PH for the serving cell is indicated by one of: - Type 1PH; - Type 3PH; - 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.

7. The UE of claim 5 or 6, wherein the reported PH for the serving cell is a type 1 PH with a dummy field indicating that a PUSCH reference format is used, or Wherein, depending on whether there is SRS transmission on the dormant BWP when the PHR is reported, the reported PH for the serving cell is a Type 3 PH.

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

9. The UE of claim 5, wherein the triggering of the PHR is configured by the network node.

10. The UE of claim 9, wherein when the active BWP is a dormant BWP, the triggering of the PHR is performed on each serving cell.

11. A system for reporting power headroom to a network node, the network node being associated with a plurality of serving cells, the system comprising a user equipment UE and at least one network node, The active bandwidth part BWP of the serving cell is a dormant BWP; The UE comprises: at least one first processor; and at least one first memory, the at least one first memory comprising a 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: triggering a power headroom report PHR to report a power headroom PH of a serving cell to the network node, wherein the PHR is triggered upon the following event: activating the serving cell if the first BWP of the serving cell is a dormant BWP and if the serving cell is an SCell of a MAC entity, wherein the MAC entity has a configured uplink; and continuing downlink reference signal measurements for PH calculation without reporting to the network node until the PHR is triggered after the active BWP is switched from a dormant BWP to a non-dormant BWP, The network nodes include: at least one second processor; and at least one second memory, the at least one second memory comprising a 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: receiving, from the UE, the PHR reporting the PH of the serving cell; and The PH value of the serving cell is obtained from the PHR.

Images