Device and method for generating power headroom report

By aggregating serving cells in the wireless communication network and generating success rate margin reports, the problems of low resource allocation efficiency and complex power control in multi-service cell scenarios are solved, and more efficient resource management and flexible power control are achieved.

CN117377050BActive Publication Date: 2024-11-29LENOVO (SINGAPORE) PTE LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202311286447.5
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2018-09-14
Publication Date
2024-11-29
Estimated Expiration
2038-09-14

AI Technical Summary

Technical Problem

In wireless communication networks, it is difficult for the prior art to effectively generate and process power headroom reports, especially in the aggregation scenario of multi-service cells, resulting in low resource allocation efficiency and complex calculation of power control parameters.

Method used

By aggregating multiple serving cells, it is determined that the power headroom report is triggered and the uplink permission is received at the first time, and the power headroom value of each serving cell is calculated based on the received information, so as to generate success rate headroom report media access control Control element, containing real or virtual power headroom values.

Benefits of technology

It improves the efficiency and accuracy of resource allocation, simplifies the calculation of power control parameters, reduces signaling overhead, and enhances the flexibility and adaptability of the system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117377050B_ABST
    Figure CN117377050B_ABST
Patent Text Reader

Abstract

The present invention relates to power headroom report generation. An apparatus, method and system for power headroom report generation are disclosed. A method includes aggregating multiple service cells. The method includes determining that a power headroom report is triggered. The method includes receiving a first uplink grant at a first time after triggering the power headroom report, the first uplink grant allocating resources for a new transmission on a service cell in multiple service cells. The method includes determining a power headroom value for each of the multiple service cells that are activated based on information received before and including the first time. The method includes generating a power headroom report media access control control element, the power headroom report media access control control element including at least a power headroom value for each of the multiple service cells that are activated.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of an application which entered the Chinese national phase on February 19, 2020, with PCT application number PCT / IB2018 / 001180, international application date September 14, 2018, Chinese application number 201880053802.5, and invention name “Power Headroom Report Generation”.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims priority to U.S. patent application serial number 62 / 558,433 filed on September 14, 2017 by Joachim Loehr, entitled “POWER HEADROOMELEMENT FORMATTIN,” the entire contents of which are incorporated herein by reference. Technical Field

[0004] The subject matter disclosed herein relates generally to wireless communications and, more particularly, to power headroom report generation. Background Art

[0005] The following abbreviations are defined herein, at least some of which are referenced in the following description: 3rd Generation Partnership Project (“3GPP”), acknowledgement (“ACK”), access point (“AP”), binary phase shift keying (“BPSK”), buffer status report (“BSR”), clear channel assessment (“CCA”), code division multiple access (“CDMA”), control element (“CE”), cyclic prefix (“CP”), cyclic redundancy check (“CRC”), channel state information (“CSI”), common search space (“CSS”), control resource set (“CORESET”), discrete Fourier transform spreading (“DFTS”), downlink control information (“DCI”), downlink (“DL”) , Downlink Pilot Time Slot (“DwPTS”), Enhanced Clear Channel Assessment (“eCCA”), Enhanced Mobile Broadband (“eMBB”), Evolved Node B (“eNB”), European Telecommunications Standards Institute (“ETSI”), Frame-based Equipment (“FBE”), Frequency Division Duplex (“FDD”), Frequency Division Multiple Access (“FDMA”), Frequency Division Orthogonal Cover Codes (“FD-OCC”), General Packet Radio Service (“GPRS”), Guard Period (“GP”), Global System for Mobile Communications (“GSM”), Hybrid Automatic Repeat Request (“HARQ”), International Mobile Telecommunications (“IMT”), Internet of Things (“IoT”), Layer 2 (“L2”), License Assisted Access (“LAA”) ), Load-based Equipment (“LBE”), Listen Before Talk (“LBT”), Logical Channel (“LCH”), Logical Channel Prioritization (“LCP”), Long Term Evolution (“LTE”), Multiple Access (“MA”), Medium Access Control (“MAC”), Multimedia Broadcast Multicast Service (“MBMS”), Modulation and Coding Scheme (“MCS”), Machine Type Communication (“MTC”), Massive MTC (“mMTC”), Multiple Input Multiple Output (“MIMO”), Multi-User Shared Access (“MUSA”), Narrowband (“NB”), Negative Acknowledgement (“NACK”) or (“NAK”), Next Generation Node B (“gNB”), Non-Orthogonal Multiple Access (“NOMA”), New Radio (“ NR”), Orthogonal Frequency Division Multiplexing (“OFDM”), Primary Cell (“PCell”), Physical Broadcast Channel (“PBCH”), Physical Downlink Control Channel (“PDCCH”), Packet Data Convergence Protocol (“PDCP”), Physical Downlink Shared Channel (“PDSCH”), Pattern Division Multiple Access (“PDMA”), Physical Hybrid ARQ Indicator Channel (“PHICH”), Power Headroom (“PH”), Power Headroom Report (“PHR”), Physical Layer (“PHY”), Physical Random Access Channel (“PRACH”), Physical Resource Block (“PRB”), Physical Uplink Control Channel (“PUCCH”), Physical Uplink Shared Channel (“PUSCH”),Quality of Service (“QoS”), Quadrature Phase Shift Keying (“QPSK”), Radio Access Network (“RAN”), Radio Resource Control (“RRC”), Random Access Procedure (“RACH”), Random Access Response (“RAR”), Radio Link Control (“RLC”), Radio Network Temporary Identifier (“RNTI”), Reference Signal (“RS”), Remaining Minimum System Information (“RMSI”), Resource Extended Multiple Access (“RSMA”), Reference Signal Received Power (“RSRP”), Round Trip Time (“RTT”), Reception (“RX”), Sparse Code Multiple Access (“SCMA”), Scheduling Request (“SR”), Sounding Reference Signal (“SRS”), Single Carrier Frequency Division Multiple Access (“SC-FDMA”), Secondary Cell (“SCell”), Shared Channel (“SCH ”), subcarrier spacing (“SCS”), service data unit (“SDU”), signal to interference plus noise ratio (“SINR”), system information block (“SIB”), synchronization signal (“SS”), transport block (“TB”), transport block size (“TBS”), time division duplex (“TDD”), time division multiplexing (“TDM”), time division orthogonal cover code (“TD-OCC”), transmission time interval (“TTI”), transmission (“TX”), uplink control information (“UCI”), user entity / equipment (mobile terminal) (“UE”), uplink (“UL”), universal mobile telecommunications system (“UMTS”), uplink pilot time slot (“UpPTS”), ultra-reliable and low latency communications (“URLLC”), and world-wide interoperability for microwave access (“WiMAX”).

[0006] In some wireless communication networks, power headroom reports may be used. In such networks, the power headroom reports may include various information. Summary of the invention

[0007] A method for power headroom report generation is disclosed. The device and system also perform the functions of the device. One embodiment of the method includes aggregating multiple service cells. In some embodiments, the method includes determining that a power headroom report is triggered. In certain embodiments, the method includes receiving a first uplink grant at a first time after triggering the power headroom report, the first uplink grant allocating resources for a new transmission on a service cell in the multiple service cells. In various embodiments, the method includes determining a power headroom value for each of the multiple service cells that are activated based on information received before and including the first time. In one embodiment, the method includes generating a power headroom report media access control control element, the power headroom report media access control control element including at least a power headroom value for each of the multiple service cells that are activated.

[0008] An apparatus for power headroom report generation includes a processor that: aggregates multiple service cells; and determines that a power headroom report is triggered. In some embodiments, the apparatus includes a receiver that receives a first uplink grant at a first time after the power headroom report is triggered, the first uplink grant allocating resources for a new transmission on a service cell in the multiple service cells. In various embodiments, the processor: determines a power headroom value for each of the multiple service cells that are activated based on information received before and including the first time; and generates a power headroom report media access control control element, the power headroom report media access control control element including at least a power headroom value for each of the multiple service cells that are activated.

[0009] A method for power headroom report generation includes receiving a power headroom report medium access control control element, the power headroom report medium access control control element including a power headroom for each of a plurality of activated serving cells. In such an embodiment, the power headroom for the respective serving cells is real or virtual.

[0010] An apparatus for power headroom report generation includes a receiver that receives a power headroom report medium access control control element, the power headroom report medium access control control element including a power headroom for each of a plurality of activated serving cells. In such an embodiment, the power headroom for the respective serving cells is real or virtual. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] A more particular description of the embodiments briefly described above will be presented by reference to specific embodiments illustrated in the accompanying drawings. Understanding that these drawings depict only some embodiments and are therefore not to be considered limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:

[0012] Figure 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for power headroom report generation and / or reception;

[0013] Figure 2 is a schematic block diagram illustrating one embodiment of an apparatus that may be used for power headroom report generation;

[0014] Figure 3 is a schematic block diagram illustrating one embodiment of an apparatus that may be used for power headroom report reception;

[0015] Figure 4 is a schematic block diagram illustrating one embodiment of timing of multiple serving cells for power headroom report generation;

[0016] Figure 5 is a schematic block diagram illustrating one embodiment of a power headroom report;

[0017] Figure 6 is a schematic block diagram illustrating another embodiment of a power headroom report;

[0018] Figure 7 is a flow chart illustrating one embodiment of a method for power headroom report generation; and

[0019] Figure 8 is a flow chart illustrating one embodiment of a method for power headroom report reception. DETAILED DESCRIPTION

[0020] As will be appreciated by those skilled in the art, aspects of the embodiments may be embodied as systems, devices, methods or program products. Therefore, the embodiments may take the form of a complete hardware embodiment, a complete software embodiment (including firmware, resident software, microcode, etc.) or a combination of software and hardware aspects, which may generally be referred to herein as "circuit", "module" or "system". In addition, the embodiments may take the form of a program product embodied in one or more computer-readable storage devices stored in machine-readable code, computer-readable code and / or program code, hereinafter referred to as code. The storage device may be tangible, non-temporary and / or non-transmitting. The storage device may not embody a signal. In a certain embodiment, the storage device only employs a signal for accessing the code.

[0021] Certain functional units described in this specification may be labeled as modules in order to more specifically emphasize their implementation independence. For example, a module may be implemented as a hardware circuit including a custom very large scale integration ("VLSI") circuit or gate array, an off-the-shelf semiconductor such as a logic chip, a transistor, or other discrete components. A module may also be implemented in a programmable hardware device such as a field programmable gate array, a programmable array logic, a programmable logic device, or the like.

[0022] Modules can also be implemented in code and / or software to be executed by various types of processors. The identified code modules can, for example, include one or more physical or logical blocks of executable code, which can, for example, be organized as objects, processes, or functions. However, the executable files of the identified modules do not need to be physically located together, but can include irrelevant instructions stored in different locations, which, when logically connected together, include the module and achieve the described purpose of the module.

[0023] In fact, a code module can be a single instruction or many instructions, and can even be distributed on several different code segments, among different programs, and across several memory devices. Similarly, in this article, operating data can be identified and shown in a module, and can be embodied in any suitable form and organized in a data structure of any suitable type. Operating data can be collected as a single data set, or can be distributed in different locations, including on different computer-readable storage devices. When a module or part of a module is implemented in software, the software portion is stored on one or more computer-readable storage devices.

[0024] Any combination of one or more computer readable media may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical or semiconductor system, apparatus or device, or any suitable combination of the foregoing.

[0025] More specific examples of storage devices (a non-exhaustive list) would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory ("RAM"), a read-only memory ("ROM"), an erasable programmable read-only memory ("EPROM" or flash memory), a portable compact disc read-only memory ("CD-ROM"), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0026] The code for performing the operations of the embodiments may be any number of lines and may be written in any combination of one or more programming languages ​​including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, C++, and the like, and traditional procedural programming languages ​​such as the "C" programming language, and / or machine languages ​​such as assembly languages. The code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer, partially on a remote computer, or entirely on a remote computer or server. In the latter case, the remote computer may be connected to the user's computer via any type of network, including a local area network ("LAN") or a wide area network ("WAN"), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0027] References to "one embodiment", "embodiment" or similar language in this specification are intended to mean that a particular feature, structure or characteristic described in conjunction with the embodiment is included in at least one embodiment. Therefore, unless otherwise expressly stated, the phrases "in one embodiment", "in an embodiment" and similar language appearing throughout the specification may, but not necessarily all refer to the same embodiment, but rather mean "one or more but not all embodiments". Unless otherwise expressly stated, the terms "include", "comprising", "having" and their variations mean "including but not limited to". Unless otherwise expressly stated, the list of items listed does not imply that any or all items are mutually exclusive. Unless otherwise expressly stated, the terms "a", "an" and "the" also refer to "one or more".

[0028] In addition, the features, structures or characteristics of the described embodiments may be combined in any suitable manner. In the following description, many specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of the embodiments. However, those skilled in the relevant art will recognize that the embodiments may be practiced without one or more of the specific details, or using other methods, components, materials, etc. In other cases, well-known structures, materials or operations are not shown or described in detail to avoid obscuring some aspects of the embodiments.

[0029] Various aspects of the embodiments are described below with reference to schematic flow charts and / or schematic block diagrams of the methods, devices, systems, and program products according to the embodiments. It will be understood that each block of the schematic flow charts and / or schematic block diagrams and the combination of blocks in the schematic flow charts and / or schematic block diagrams can be implemented by code. The code can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, so that instructions executed by the processor of the computer or other programmable data processing device create a device for implementing the functions / operations specified in the schematic flow charts and / or schematic block diagram blocks.

[0030] The code may also be stored in a storage device that is capable of instructing a computer, other programmable data processing apparatus, or other device to operate in a specific manner so that the instructions stored in the storage device produce an article of manufacture including instructions that implement the functions / operations specified in the blocks of the schematic flowchart and / or schematic block diagram.

[0031] The code may also be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operational steps are performed on the computer, other programmable apparatus, or other device to produce a computer-implemented process, so that the code executed on the computer or other programmable apparatus provides a process for implementing the functions / operations specified in the blocks of the flowchart and / or block diagram.

[0032] The schematic flow charts and / or schematic block diagrams in the accompanying drawings illustrate possible implementations of the apparatus, system, method, and program product according to various embodiments, architecture, functions, and operations. In this regard, each block in the schematic flow charts and / or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing a specified logical function.

[0033] It should also be noted that in some alternative implementations, the functions annotated in the blocks may not occur in the order annotated in the drawings. For example, two blocks shown in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order, depending on the functions involved. Other steps and methods are contemplated that are equivalent in function, logic, or effect to one or more blocks or portions thereof of the illustrated drawings.

[0034] Although various arrow types and line types can be adopted in flow charts and / or block diagrams, it should be understood that they do not limit the scope of the corresponding embodiments. In fact, some arrows or other connectors can only be used to indicate the logical flow of the depicted embodiment. For example, an arrow can indicate the waiting or monitoring period of the unspecified duration between the enumeration steps of the depicted embodiment. It will also be noted that each block of the block diagram and / or flow chart and the combination of the blocks in the block diagram and / or flow chart can be realized by a system based on dedicated hardware that performs a specific function or operation, or a combination of dedicated hardware and code.

[0035] The description of an element in each figure may refer to the elements of the previous figure. In all figures, the same numerals refer to the same elements, including alternative embodiments of the same elements.

[0036] Figure 1 An embodiment of a wireless communication system 100 for power headroom report generation and / or reception is depicted. In one embodiment, the wireless communication system 100 includes a remote unit 102 and a network unit 104. Even if Figure 1 Although a particular number of remote units 102 and network units 104 are depicted in FIG. 1 , those skilled in the art will recognize that any number of remote units 102 and network units 104 may be included in the wireless communication system 100 .

[0037] In one embodiment, the remote unit 102 may include a computing device such as a desktop computer, a laptop computer, a personal digital assistant ("PDA"), a tablet computer, a smart phone, a smart TV (e.g., a TV connected to the Internet), a set-top box, a game console, a security system (including a security camera), a vehicle computer, a network device (e.g., a router, a switch, a modem), an aircraft, a drone, etc. In some embodiments, the remote unit 102 includes a wearable device such as a smart watch, a fitness band, an optical head-mounted display, etc. In addition, the remote unit 102 may be referred to as a user unit, a mobile device, a mobile station, a user, a terminal, a mobile terminal, a fixed terminal, a user station, a UE, a user terminal, a device, or other terms used in the art. The remote unit 102 may communicate directly with one or more network units 104 via UL communication signals.

[0038] The network elements 104 may be distributed over a geographic area. In some embodiments, the network elements 104 may also be referred to as access points, access terminals, base stations, base stations, node-Bs, eNBs, gNBs, home node-Bs, relay nodes, devices, core networks, air servers, radio access nodes, APs, NRs, or any other terminology used in the art. The network elements 104 are typically part of a radio access network that includes one or more controllers that are communicatively coupled to one or more corresponding network elements 104. The radio access network is typically communicatively coupled to one or more core networks, which may be coupled to other networks, such as the Internet and public switched telephone networks, among others. These and other elements of the radio access and core networks are not illustrated, but are generally well known to those of ordinary skill in the art.

[0039] In one embodiment, the wireless communication system 100 complies with the NR protocol standardized in 3GPP, wherein the network unit 104 transmits on the DL using an OFDM modulation scheme, and the remote unit 102 transmits on the UL using an SC-FDMA scheme or an OFDM scheme. However, more generally, the wireless communication system 100 may implement some other open or proprietary communication protocol, such as WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA2000, ZigBee, Sigfoxx, and other protocols. The present disclosure is not intended to be limited to any particular wireless communication system architecture or protocol implementation.

[0040] The network unit 104 can serve multiple remote units 102 within a service area (eg, a cell or cell sector) via wireless communication links. The network unit 104 sends DL communication signals to serve the remote units 102 in the time, frequency, and / or spatial domains.

[0041] In one embodiment, the remote unit 102 may be used for power headroom report generation. The remote unit 102 may aggregate multiple serving cells. In some embodiments, the remote unit 102 may determine that the power headroom report is triggered. In some embodiments, the remote unit 102 may receive a first uplink grant at a first time after triggering the power headroom report, and the first uplink grant allocates resources for transmission (e.g., new transmission) on a serving cell in the multiple serving cells. In various embodiments, the remote unit 102 may determine a power headroom value for each serving cell in the activated multiple serving cells based on information received before and including the first time. In one embodiment, the remote unit 102 may generate a power headroom report media access control control element, which includes at least a power headroom value for each serving cell in the activated multiple serving cells. In some embodiments, the remote unit 102 may send a power headroom report media access control control element on resources allocated by the first uplink grant. Therefore, the remote unit 102 may be used for power headroom report generation.

[0042] In some embodiments, the network unit 104 may be configured to receive a power headroom report. In some embodiments, the network unit 104 may receive a power headroom report media access control control element, the power headroom report media access control control element including a power headroom for each of the activated plurality of serving cells. In such an embodiment, the power headroom of the corresponding serving cell is real or virtual. Therefore, the network unit 104 may be configured to receive a power headroom report.

[0043] Figure 2 An embodiment of an apparatus 200 that may be used for power headroom report generation is depicted. Apparatus 200 includes an embodiment of a remote unit 102. In addition, remote unit 102 may include a processor 202, a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212. In some embodiments, input device 206 and display 208 are combined into a single device, such as a touch screen. In some embodiments, remote unit 102 may not include any input device 206 and / or display 208. In various embodiments, remote unit 102 may include one or more of processor 202, memory 204, transmitter 210, and receiver 212, and may not include input device 206 and / or display 208.

[0044] In one embodiment, the processor 202 may include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, the processor 202 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or a similar programmable controller. In some embodiments, the processor 202 executes instructions stored in the memory 204 to perform the methods and routines described herein. In various embodiments, the processor 202 may: aggregate multiple serving cells; and determine that a power headroom report is triggered. In some embodiments, the processor 202 may: determine a power headroom value for each of the multiple serving cells that are activated based on information received before and including the first time; and generate a power headroom report media access control control element, which includes at least a power headroom value for each of the multiple serving cells that are activated. The processor 202 is communicatively coupled to the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212.

[0045] In one embodiment, memory 204 is a computer-readable storage medium. In some embodiments, memory 204 includes volatile computer storage media. For example, memory 204 may include RAM, including dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and / or static RAM ("SRAM"). In some embodiments, memory 204 includes non-volatile computer storage media. For example, memory 204 may include a hard drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 204 includes both volatile and non-volatile computer storage media. In some embodiments, memory 204 also stores program code and related data, such as an operating system or other controller algorithm running on remote unit 102.

[0046] In one embodiment, input device 206 may include any known computer input device, including a touchpad, buttons, keyboard, stylus, microphone, etc. In some embodiments, input device 206 may be integrated with display 208, for example, as a touch screen or similar touch-sensitive display. In some embodiments, input device 206 includes a touch screen so that text can be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. In some embodiments, input device 206 includes two or more different devices such as a keyboard and a touchpad.

[0047] In one embodiment, display 208 may include any known electronically controllable display or display device. Display 208 may be designed to output visual, auditory and / or tactile signals. In some embodiments, display 208 includes an electronic display capable of outputting visual data to a user. For example, display 208 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or a similar display device capable of outputting images, text, etc. to a user. As another non-limiting example, display 208 may include a wearable display such as a smart watch, smart glasses, a head-up display, etc. In addition, display 208 may be a component of a smart phone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

[0048] In some embodiments, the display 208 includes one or more speakers for generating sounds. For example, the display 208 can generate an audible alarm or notification (e.g., a beep or chime). In some embodiments, the display 208 includes one or more tactile devices for generating vibration, motion, or other tactile feedback. In some embodiments, all or part of the display 208 can be integrated with the input device 206. For example, the input device 206 and the display 208 can form a touch screen or similar touch-sensitive display. In other embodiments, the display 208 can be located near the input device 206.

[0049] As described herein, the transmitter 210 is used to provide UL communication signals to the network unit 104, and the receiver 212 is used to receive DL communication signals from the network unit 104. In some embodiments, the receiver 212 receives a first uplink grant at a first time after triggering a power headroom report, and the first uplink grant allocates resources for a transmission (e.g., a new transmission) on one of the multiple serving cells. In some embodiments, the transmitter 210 sends a power headroom report media access control control element on the resources allocated by the first uplink grant. Although only one transmitter 210 and one receiver 212 are shown, the remote unit 102 can have any suitable number of transmitters 210 and receivers 212. The transmitter 210 and the receiver 212 can be any suitable type of transmitter and receiver. In one embodiment, the transmitter 210 and the receiver 212 can be part of a transceiver.

[0050] Figure 3One embodiment of an apparatus 300 that may be used for power headroom report reception is depicted. The apparatus 300 includes one embodiment of the network unit 104. In addition, the network unit 104 may include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. It is understood that the processor 302, the memory 304, the input device 306, the display 308, the transmitter 310, and the receiver 312 may be substantially similar to the processor 202, the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212 of the remote unit 102, respectively.

[0051] In some embodiments, the receiver 312 may receive a power headroom report media access control control element that includes a power headroom for each of the plurality of activated serving cells. In such an embodiment, the power headroom for the corresponding serving cell is real or virtual. Although only one transmitter 310 and one receiver 312 are shown, the network unit 104 may have any suitable number of transmitters 310 and receivers 312. The transmitter 310 and the receiver 312 may be any suitable type of transmitter and receiver. In one embodiment, the transmitter 310 and the receiver 312 may be part of a transceiver.

[0052] To support various services (e.g., eMBB, URLLC, mMTC), 5G / NR may support different OFDM parameter sets (e.g., SCS, CP length) in a single framework. As can be appreciated, various configurations of NR may have different requirements in terms of data rate, latency, and / or coverage. For example, eMBB may support certain data rates (e.g., 20 Gbps for downlink and 10 Gbps for uplink), as well as a data rate that is more than three times the user experience provided by IMT-Advanced systems. On the other hand, for URLLC, ultra-low latency (e.g., 0.5 ms each for UL and DL for user plane latency) and high reliability (e.g., 1-10 within 1 ms) are required. -5) puts forward more stringent requirements. In addition, mMTC may use high connection density, wide coverage in harsh environments, and ultra-long life batteries for low-cost devices. Therefore, an OFDM parameter set (e.g., SCS, OFDM symbol duration, CP duration, number of symbols per scheduling interval) suitable for one configuration may not be suitable for another configuration. For example, compared with mMTC services, low-delay services may use shorter symbol durations (and therefore larger SCSs) and / or fewer symbols in each scheduling interval (e.g., TTI). In addition, configurations with larger channel delay spreads may use longer CP durations compared to scenarios with smaller delay spreads. In some configurations, the SCS can be optimized to facilitate specific CP overhead. In various embodiments, in order to support the application of different parameter sets on different carriers for a given remote unit 102 and the use of different parameter sets within the same carrier for a given remote unit 102, different OFDM parameter sets can be multiplexed in the frequency domain and / or time domain within the same carrier and / or on different carriers. This multiplexing can facilitate simultaneous support of services with vastly different requirements, such as ultra-low latency communications (short symbols and therefore wide subcarrier spacing) and MBMS services (long symbols to enable long cyclic prefixes and therefore narrow subcarrier spacing).

[0053] In LTE, both TTI and subframe can correspond to the same duration of 1ms. In addition, both can refer to a 1ms period associated with different physical channels, including the shortest possible interval between two PDCCH opportunities, the duration of the transmission of a transport block on PDSCH or PUSCH, or the time domain scheduling granularity. However, for NR, the PDSCH or PUSCH duration for the transmission of a transport block can vary between microslots, time slots, or multiple time slots. In addition, in some embodiments, the remote unit 102 can be configured to monitor the DL control channel in terms of time slots or OFDM symbols relative to the parameter set of the DL control channel. Therefore, the remote unit 102 can be configured to monitor the PDCCH once every multiple time slots at the PDCCH monitoring opportunity (e.g., on a subset of PDCCH monitoring candidates).

[0054] As used herein, TTI may refer to a time period (e.g., one or more OFDM symbols or time slots) during which the remote unit 102 is configured to monitor a downlink control channel, a time period during which the remote unit 102 is configured to monitor the PDCCH (on a particular CORESET), and / or the duration of data transmission on the PDSCH and / or PUSCH.

[0055] In various embodiments, in order to aggregate multiple serving cells and / or component carriers with different parameter sets in NR, PHR may be used. In some embodiments, PHR may be reported only for activated serving cells with configured uplink.

[0056] In LTE, the remote unit 102 may report an extended PHR for configurations that include carrier aggregation (e.g., PH information for each activated serving cell with configured uplink may be included in the PH MAC CE). It will be appreciated that because the TTI length in LTE may be the same for all carriers, the PHR subframes (e.g., the TTI to which the PH information refers) may be aligned across all component carriers and / or serving cells.

[0057] In NR, due to its support for different parameter sets, the TTI of one component carrier and / or serving cell may overlap with multiple TTIs of another carrier (e.g., the TTI of eMBB on one carrier may overlap with the TTI of URLLC on another carrier). In some embodiments, the network unit 104 receiving the extended PHR may not know which TTI the reported PH information refers to. For example, in a configuration where an extended PHR report is triggered and then sent in a TTI that overlaps with multiple TTIs on different carriers, the network unit 104 may not know which overlapping TTI is the reference for PH calculation. Therefore, the network unit 104 may make its future scheduling decisions based on incorrect assumptions (e.g., how close the remote unit 102 is running to the power limit), which may lead to power scaling issues and / or underutilization of resources.

[0058] In various embodiments, the PHR in NR may have issues with the size of the (extended) PHR MAC CE, i.e., the PHR MAC CE containing power headroom information for multiple activated serving cells with configured uplink. In particular, because NR may be used for very high data rates and low latency, the processing time available for both the transmitter and the receiver (e.g., for generating and / or decoding TBs) may be limited. Therefore, the L2 protocol functions for NR may be designed in a processing power-friendly manner. One such example may be not supporting concatenation of data segments in the RLC layer. Not supporting concatenation of data segments in the RLC layer may enable pre-processing of the RLC layer and the MAC layer (e.g., PDCP SDUs may be pre-built to a MAC SDU with its own MAC subheader) before receiving an UL grant. With regard to the placement of the MAC CE, in various embodiments, the UL MAC CE may be placed at the end of the TB before any potential padding. This may be so that once an UL grant is received, the transmitter may immediately start feeding a portion of the TB to the PHY. In a configuration where the MAC CE is placed at the beginning of a TB, the transmitter may need to wait until the MAC CE content is generated before starting channel coding. In some embodiments, the calculation of the BSR and PHR MAC CE may be performed at a later point in time, since both reflect the latest state before transmission (e.g., the BSR may only be calculated after the LCP has completed).

[0059] Because the size of the extended PHR MAC CE may not be fixed, but depends on the number of activated serving cells (with configured uplink) and also on whether a virtual PH or a real PH is reported for the serving cell (for a virtual PHR, no P is reported). cmax,c), from a processing timing perspective, the generation of TBs may be challenging for NR for configurations that multiplex the extended PHR MAC CE in the TB. In some embodiments, to generate the TB (e.g., during LCP), because MAC CEs are generally prioritized on data channels, the remote unit 102 may first reserve sufficient space for the MAC CE within the TB before allocating data to a logical channel (e.g., a data radio bearer). In various embodiments, in response to the size of the MAC CE being known only at a later point in time, the LCP process may be delayed. In some embodiments, to determine the size of the extended PHR MAC CE for NR (e.g., when the remote unit 102 is aggregating multiple serving cells with different parameter sets and / or TTI lengths), the remote unit 102 may determine whether a virtual uplink transmission or an actual uplink transmission occurs on the serving cell in the TTI in which the PH is reported. However, in some embodiments, for NRs that use different parameter sets with different TTI lengths and / or timing relationships on the serving cell, the remote unit 102 may not immediately (e.g., after receiving the UL grant) know whether to calculate the PH information for the serving cell based on an actual uplink transmission or a virtual uplink transmission. In addition, in some embodiments, the size of the PHR MAC CE may not be immediately known, which may also mean that the LCP may not start immediately after receiving the UL grant.

[0060] In some embodiments, for configurations in which the remote unit 102 aggregates multiple NR component carriers and / or serving cells so as to be able to start the LCP process immediately after receiving a UL grant, the remote unit 102 may determine the size of the extended PHR MAC CE immediately after receiving the UL grant.

[0061] In one embodiment, the remote unit 102 may determine the size of the extended PHR MAC CE based on the UL resource allocations, e.g., UL grants, received up to the point in time when the remote unit 102 performs the LCP. More specifically, at the time when the remote unit 102 receives the UL grant in TTI N and has triggered at least one PHR, the remote unit 102 may consider all UL grants received for other activated serving cells (respectively UL component carriers) up to and including TTI N for determining the size of the extended PHR MAC CE (e.g., for determining whether to determine the PH value for the serving cell based on actual uplink transmission or virtual uplink transmission).

[0062] In various embodiments, for the determination of PH information, the remote unit 102 may ignore any uplink grant received later than TTI N for scheduling uplink transmissions on another activated serving cell in the TTI in which the PHR MAC CE is sent. Thus, in some embodiments, the remote unit 102 may determine at TTI N (after receiving a UL grant in TTI N that schedules an initial PUSCH transmission in TTI N+x, including an (extended) PHR MAC CE) that a virtual PH is to be calculated for a serving cell (e.g., no uplink transmission occurred on the serving cell in the PHR reference subframe). In such an embodiment, the remote unit 102 may report a virtual PHR for the serving cell even if an uplink transmission is to be scheduled at a later point in time in the PHR reference subframe of the serving cell. As used herein, a PHR reference subframe (respectively, a PHR reference TTI) may refer to a specific subframe / TTI used as a reference point for the PHR. In other words, the information in the PHR may be relative to a specific subframe / TTI (i.e., the PHR reference subframe). For example, in Figure 4 In the example, subframes I and S are PHR reference subframes.

[0063] It will be appreciated that considering only the UL grants received for the active serving cell up to and including the TTI in which a UL grant scheduling uplink resources for transmission of the extended PHR MAC CE has been received enables the remote unit 102 to immediately determine the size of the extended PHR MAC CE (e.g., as in LTE), which in turn enables the remote unit 102 to immediately initiate the TB generation process (e.g., by performing an LCP process).

[0064] Figure 4 is a schematic block diagram illustrating one embodiment of timing 400 of multiple serving cells for power headroom report generation. A first serving cell 402 (or carrier), a second serving cell 404 (or carrier), and a third serving cell 406 (or carrier) are illustrated.

[0065] In some embodiments, the remote unit 102 is configured with 3 component carriers and / or serving cells (with all 3 activated), each of which has a different set of parameters and / or TTI / time slot length. Figure 4 In the illustrated embodiment, the remote unit 102 is configured with a first serving cell 402, a second serving cell 404, and a third serving cell 406. In some embodiments, the PHR may be determined based on predetermined criteria prior to a first time 408 ("t0") (e.g., within a TTI of the first serving cell 402). N-3 During TTI N-2, the UL grant received at t0 is triggered on the first serving cell 402 during TTI NThe extended PHR MAC CE is sent in.

[0066] Once the UL grant for the PHR reporting subframe N is received at t0 (TTI N-2 on the first serving cell 402), the remote unit 102 may start the LCP process to facilitate the generation of the TB. It can be appreciated that in order to determine the MAC SDU size of the LCH, the remote unit 102 may need to know the size of the PHR MAC CE (or extended PHR ("ePHR") MAC CE). However, because potential UL grants for the PHR reference subframes on the second serving cell 404 and the third serving cell 406 are received at a later point in time (e.g., at the second time 410 "t1" and the third time 412 "t2", respectively), the remote unit 102 may not be able to determine at t0 (e.g., TTIN-2) whether uplink transmissions occur on the second serving cell 404 and the third serving cell 406 in the PHR reference subframes (e.g., subframe I and subframe S, respectively). Therefore, the remote unit 102 may need to delay the LCP process, which may make it difficult to ultimately generate the TB (e.g., physical channel coding).

[0067] Figure 5 is a schematic block diagram illustrating one embodiment of a power headroom report 500. In one embodiment, the power headroom report 500 may include a first PH value, a second PH value, and a third PH value. One or more PH values ​​may be real (e.g., actual) PH values ​​and / or one or more PH values ​​may be virtual (e.g., calculated, estimated, etc.).

[0068] Figure 6 is a schematic block diagram illustrating another embodiment of a power headroom report 600. In one embodiment, the power headroom report 600 may include a first PH value, a first v field, a second PH value, a second v field, a third PH value, and a third v field. One or more PH values ​​may be real (e.g., actual) PH values ​​and / or one or more PH values ​​may be virtual (e.g., calculated, estimated, etc.). The first v field may correspond to the first PH value, the second v field may correspond to the second PH value, and the third v field may correspond to the third PH value. The v field may indicate whether its corresponding PH value is real or virtual. For example, in one embodiment, the v field may be a bit, where a logical "0" indicates that the corresponding PH value is real, and a logical "1" indicates that the corresponding PH value is virtual. In another embodiment, the v field may be a bit, where a logical "1" indicates that the corresponding PH value is real, and a logical "0" indicates that the corresponding PH value is virtual.

[0069] Back to Figure 4In some embodiments, the remote unit 102 may only consider the UL grants received up to and including t0 for the activated component carriers and / or serving cells (e.g., the UL grants received up to and including TTI N-2) to help determine the size of the extended PHR MAC CE. Therefore, even if the actual uplink transmission will occur in the PH reference subframe (e.g., TTI i is the PHR reference subframe of the second serving cell scheduled in TTI i-2 on the second serving cell 404, and TTI s is the PHR reference subframe of the third serving cell scheduled in TTI s-2 on the third serving cell 406), the remote unit 102 may determine at t0 that a virtual PH value is to be calculated and reported for the second serving cell 404 and the third serving cell 406. In some embodiments, the remote unit 102 may set the field value of the extended PHR MAC CE based on the reception status at t0 (e.g., the remote unit 102 sets the V field of the second serving cell 404 and the third serving cell 406 to 1, which indicates that the PH value is based on the reference format (virtual PH)). In an embodiment where the V field indicates a virtual PH, the PH of the second serving cell 404 and the third serving cell 406 may not be reported. CMAX,c Additionally, in such an embodiment, the MAC may indicate to the PHY that a virtual PH value should be calculated for the second serving cell 404 and the third serving cell 406 .

[0070] In various embodiments, the remote unit 102 may determine the size of the triggered (e.g., extended) PHRMAC CE by considering only UL grants on the activated serving cell and transmissions on the PUCCH and unlicensed uplink transmissions before a predetermined time (e.g., receipt of an UL grant that in turn triggers the LCP process). Figure 4 , the remote unit 102 may consider all UL grants received up to t0 on the activated serving cell / carrier, as well as the remote unit 102's knowledge and / or state of unlicensed uplink transmissions and PUCCH transmissions occurring in the PHR reference subframe at t0, for determining the size of the PHR MAC CE.

[0071] In some embodiments, in embodiments where the PH value is based on a reference format (eg, a virtual PH), the extended PHR MAC CE for the serving cell and / or component carrier may not include the PH value. CMAX,c This may be because the virtual PH's P CMAX,cThe value is known to the network unit 104 and does not need to be reported, thereby reducing signaling overhead. In some embodiments, even for embodiments in which the PH value of the serving cell is based on a reference format (e.g., a virtual PH), the remote unit 102 may always include the PH value for the activated serving cell in the extended PHR MAC CE. CMAX,c field. Such an embodiment may enable the remote unit 102 to immediately know the size of the extended PHR MAC CE upon receiving the UL grant, thereby enabling the remote unit 102 to immediately start the TB generation process (e.g., by performing LCP). In some embodiments, the remote unit 102 may be enabled to report the PH value according to the uplink transmission status in the PHR reference subframe, and the V-flag may be set according to the transmitted PH information (e.g., virtual or real). In some embodiments, the remote unit 102 may include the P values ​​for the first serving cell 402, the second serving cell 404, and the third serving cell 406 in the extended PHR MAC CE. CMAX,c field. In some embodiments, processing power capabilities may enable remote unit 102 to consider the UL grant received at t1 for second serving cell 404 for generating a TB scheduled at t0. In such embodiments, remote unit 102 may report a real PH (e.g., with a V-flag set to 0) for second serving cell 404 in the extended PHR MAC CE. In such embodiments, remote unit 102 may report a virtual PHR (e.g., with a V-flag set to 1) for third serving cell 406.

[0072] In various embodiments, the remote unit 102 may determine the size of the triggered (e.g., extended) PHR MAC CE by considering UL grants on the activated serving cell and transmissions on the PUCCH and unlicensed uplink transmissions prior to a defined time instance (e.g., received UL grants, which in turn triggered the LCP process). In some embodiments, the remote unit 102 may consider all UL grants received until t0, as well as the remote unit 102's knowledge and / or state of unlicensed uplink transmissions and PUCCH transmissions in the PHR reference subframe at t0, for determining the size of the PHR MAC CE.

[0073] In various embodiments, the remote unit 102 may decide at t0 (e.g., upon receiving an UL grant on the first serving cell 402) to report virtual PHR values ​​for the second serving cell 404 and the third serving cell 406 (e.g., because no uplink transmission occurred in the reference PHR subframe on the second serving cell 404 and the third serving cell 406 according to the grant reception state at t0). In some embodiments, in addition to the extended PHR MAC sent on the first serving cell 402, the remote unit 102 sends a PHR MAC CE for the second serving cell 404 in the next uplink transmission occurring on the second serving cell 404 (e.g., in the PHR reference subframe) and sends a PHR MAC CE for the third serving cell 406 in the next uplink transmission on the third serving cell 406. This may be because only a virtual PHR is reported for the second serving cell 404 and the third serving cell 406 in the extended PHR MAC CE sent on the first serving cell 402. In such an embodiment, the additional PHR MAC CE may provide the network element 104 with detailed information regarding the power condition of the remote unit 102 serving the cell, rather than the information conveyed by the virtual PHR.

[0074] In various embodiments, to support multiple open-loop power control parameters, the network unit 104 may configure multiple P0 and / or α values ​​(e.g., for a specific combination of one or more beams, UL waveforms, and / or service types). In certain embodiments, the network unit 104 may configure different power control parameters for URLLC and eMBB because the two services have different QoS requirements. In some embodiments, for a PHR calculated based on a reference transmission and / or format (e.g., a virtual PH), the network unit 104 may know which uplink power control parameters the remote unit 102 used for the virtual PHR calculation to facilitate the correct interpretation of the received PH information. Thus, the power control parameters (e.g., P0, P1, P2, P3, P4, P5, P6, P7, P8, P9, P10, P11, P12, P13, P14, P15, P16, P17, P18, P19, P20, P21, P22, P23, P24, P25, P26, P27, P28, P29, P30, P31, P32, P33, P34, P35, P36, P48, P49, P40, P41, P42, P43, P44, P45, P46, P47, P48, P49, P40, P41, P4 O_PUSCH,c A predefined set of α and / or α values) is used for the calculation of the virtual PH.

[0075] In some embodiments where the network unit 104 configures a plurality of power control parameters (e.g., a plurality of pairs of P0 and α), the remote unit 102 may use a first number of power control parameters in the set of configured power control parameters for calculation of the virtual PH value. In some embodiments, a predefined TX beam or combination of beams and / or a predefined set of parameters may be used to calculate the virtual PH value (e.g., the PH value may be based on a reference format).

[0076] In one embodiment, the network unit 104 may configure multiple (e.g., open-loop) power control parameters (e.g., P0 and α values) for different service types. In such an embodiment, during the time when the remote unit 102 performs logical channel multiplexing (e.g., data of multiple LCHs are multiplexed in one TB), the remote unit 102 MAC may indicate to the PHY layer contained in the TB the service with the highest logical channel priority (e.g., according to the LCP procedure). In some embodiments, the PHY selects the open-loop power control parameters based on the indicated service from the MAC.

[0077] In some embodiments, the remote unit 102 power level for centimeter wave ("CMW") and millimeter wave ("MMW") (e.g., above 24 GHz) can be considered to be the effective isotropic radiated power ("EIRP"). In some embodiments, for antenna radiation pattern measurements, if a single EIRP value is given, this can be the maximum value of the EIRP at all measurement angles. In some embodiments, the EIRP can be calculated by the following formula: EIRP = P t –L+G vs. the power sent from the radio / PA (“P t ”), cable losses (e.g., which may include antenna mismatch) “L” and antenna gain (“G”).

[0078] In various embodiments, the cable loss L can be neglected because it is typically only a small fraction of a dB. In some embodiments, P can be defined for the range above 24 GHz in terms of EIRP including antenna beamforming gain. cmax . In certain RAN simulation assumptions, the RX beamforming gain of the remote unit 102 may be included in the RSRP measurement and therefore in the path loss calculation. In certain embodiments, it is contemplated that the power control equation for NR may be similar to the power control equation for LTE. For example, for PUSCH, the UL output power in dBm may be: P PUSCH =min{P cmax,c ,(P 0,PUSCH +αPL)+10log(M PUSCH )+Δ other +f c (i)}.

[0079] In some embodiments, because the path loss value PL may take into account the RX beamforming and / or antenna gain of the remote unit 102, there may be an additional factor representing the TX antenna gain in the formula for UL output power (e.g., for PUSCH, PUCCH, and / or SRS). In one particular embodiment, the difference between the RX and TX antenna gains may be used in the power control formula. For embodiments where the RX and TX antenna gains are the same, the factor representing the TX antenna gain may be zero.

[0080] In some embodiments, when calculating the virtual PHR (e.g., based on some reference format and / or transmitted PH value), the remote unit 102 may assume that the TX antenna gain and the RX antenna gain are the same (e.g., without considering the correction factor). In another embodiment, a predefined TX antenna gain may be used for the calculation of the virtual PHR (e.g., the TX antenna gain and / or the beamforming gain may be set to zero to determine the PHR). cmax value and the corresponding pH value).

[0081] Various embodiments of the extended PHR MAC CE and corresponding field descriptions are described below.

[0082] C i : This field may indicate the presence of a PH field for an SCell with SCellIndex i. In some embodiments, a C i The PH field may indicate that the PH field for the SCell with SCellIndex i is reported. In such an embodiment, the C i The field may indicate that the PH field for the SCell with SCellIndex i is not reported.

[0083] R: This field may be used for a reserved bit and, in some embodiments, may be set to "0".

[0084] V: This field can indicate whether the PH value is based on a real transmission or a reference format (e.g., virtual). For type 1 PH, V=0 can indicate an actual transmission on PUSCH, while V=1 can indicate the use of a PUSCH reference format. For type 2 PH, V=0 can indicate an actual transmission on PUCCH, while V=1 can indicate the use of a PUCCH reference format. For type 3 PH, V=0 can indicate an actual transmission on SRS, while V=1 can indicate the use of an SRS reference format. In addition, for type 1, type 2, and type 3 PH, V=0 can indicate the presence of a PUSCH reference format containing an associated CMAX,c octet of the field, and V = 1 may indicate that the associated P CMAX,c The octet of the field.

[0085] PH: This field may indicate the power headroom level. The length of the field may be 6 bits.

[0086] P: This field may indicate whether the MAC entity is due to power management (e.g., P-MPR c If power backoff due to power management is not applied, if the corresponding P CMAX,c The field may have different values, then the MAC entity may set P=1.

[0087] P CMAX,c PH: If present, this field may indicate the P used to calculate the previous PH field. CMAX,c or P~ CMAX,c .

[0088] Figure 7 is a flow chart illustrating one embodiment of a method 700 for power headroom report generation. In some embodiments, the method 700 is performed by a device such as the remote unit 102. In certain embodiments, the method 700 may be performed by a processor executing program code, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0089] The method 700 may include aggregating 702 a plurality of serving cells. In some embodiments, the method 700 includes determining 704 that a power headroom report is triggered. In certain embodiments, the method 700 includes receiving 706 a first uplink grant at a first time after the power headroom report is triggered, the first uplink grant allocating resources for an uplink transmission (e.g., a new transmission) on a serving cell in the plurality of serving cells. In various embodiments, the method 700 includes determining 708 a power headroom value for each of the plurality of serving cells that are activated based on information received before and including the first time. In one embodiment, the method 700 includes generating 710 a power headroom report media access control control element, the power headroom report media access control control element including at least a power headroom value for each of the plurality of serving cells that are activated. In some embodiments, the method 700 includes sending 712 a power headroom report media access control control element on resources allocated by the first uplink grant.

[0090] In some embodiments, the information includes uplink-related downlink control information. In some embodiments, the information includes uplink resource allocations for configured grants. In various embodiments, the first time corresponds to a physical downlink control channel opportunity. In one embodiment, determining a power headroom value for each of the plurality of activated serving cells includes ignoring information received at a second time that is later than the first time.

[0091] In some embodiments, determining a power headroom value for each of the plurality of activated serving cells includes determining whether the power headroom value for each of the plurality of activated serving cells is based on a real uplink transmission or a virtual uplink transmission. In some embodiments, the real uplink transmission includes a transmission based on a received uplink grant. In various embodiments, the virtual uplink transmission includes a virtual transmission based on a reference format.

[0092] In one embodiment, the power headroom report medium access control control element includes an indicator corresponding to each of the plurality of activated serving cells, and the indicator indicates whether the power headroom value for the corresponding serving cell is real or virtual. In certain embodiments, the power headroom report includes a power headroom corresponding to each of the plurality of activated serving cells, and the power headroom for the corresponding serving cell is real or virtual. In some embodiments, the power headroom report is triggered in response to expiration of a timer.

[0093] Figure 8 is a flow chart illustrating one embodiment of a method 800 for power headroom report reception. In some embodiments, the method 800 is performed by an apparatus such as the network unit 104. In certain embodiments, the method 800 may be performed by a processor executing program code, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0094] The method 800 may include receiving 802 a power headroom report medium access control control element including a power headroom for each serving cell of a plurality of activated serving cells. In such an embodiment, the power headroom of the corresponding serving cell is real or virtual.

[0095] In some embodiments, the power headroom report media access control control element includes an indicator corresponding to each of the plurality of serving cells that are activated, and the indicator indicates whether a power headroom value for the corresponding serving cell is real or virtual. In some embodiments, the power headroom for the corresponding serving cell is real in response to the remote unit 102 performing an uplink transmission in accordance with an uplink grant on the corresponding serving cell. In various embodiments, the power headroom for the corresponding serving cell is virtual in response to the remote unit not performing an uplink transmission on the serving cell in accordance with the uplink grant.

[0096] In one embodiment, a method includes: aggregating multiple service cells; determining that a power headroom report is triggered; at a first time after the power headroom report is triggered, receiving a first uplink grant, the first uplink grant allocating resources for transmission (e.g., new transmission) on a service cell among the multiple service cells; determining a power headroom value for each of the multiple service cells that are activated based on information received before and including the first time; generating a power headroom report media access control control element, the power headroom report media access control control element at least including the power headroom value for each of the multiple service cells that are activated; and / or sending a power headroom report media access control control element on the resources allocated by the first uplink grant.

[0097] In some embodiments, the information includes uplink-related downlink control information.

[0098] In some embodiments, the information includes uplink resource allocations for configured grants.

[0099] In various embodiments, the first time corresponds to a Physical Downlink Control Channel opportunity.

[0100] In one embodiment, determining the power headroom value for each of the activated plurality of serving cells includes ignoring information received at a second time later than the first time.

[0101] In certain embodiments, determining the power headroom value for each of the plurality of activated serving cells includes determining whether the power headroom value for each of the plurality of activated serving cells is based on real uplink transmission or virtual uplink transmission.

[0102] In some embodiments, the actual uplink transmission comprises a transmission based on a received uplink grant.

[0103] In various embodiments, the dummy uplink transmission comprises a dummy transmission based on a reference format.

[0104] In one embodiment, the power headroom report medium access control control element includes an indicator corresponding to each serving cell of the plurality of serving cells being activated, and the indicator indicates whether the power headroom value for the corresponding serving cell is real or virtual.

[0105] In certain embodiments, the power headroom report includes a power headroom corresponding to each of the plurality of serving cells that are activated, and the power headroom for the corresponding serving cell is real or virtual.

[0106] In some embodiments, the power headroom report is triggered in response to expiration of a timer.

[0107] In one embodiment, a device includes: a processor that aggregates multiple service cells; and determines that a power headroom report is triggered; a receiver that receives a first uplink grant at a first time after the power headroom report is triggered, the first uplink grant allocating resources for transmission (e.g., new transmission) on a service cell among the multiple service cells; and / or a transmitter, wherein: the processor: determines a power headroom value for each of the multiple service cells that are activated based on information received before and including the first time; and generates a power headroom report media access control control element, the power headroom report media access control control element at least including the power headroom value for each of the multiple service cells that are activated; and / or the transmitter sends a power headroom report media access control control element on the resources allocated by the first uplink grant.

[0108] In some embodiments, the information includes uplink-related downlink control information.

[0109] In some embodiments, the information includes uplink resource allocations for configured grants.

[0110] In various embodiments, the first time corresponds to a Physical Downlink Control Channel opportunity.

[0111] In one embodiment, for calculating the power headroom report, the processor ignores downlink control information allocating uplink resources received at a second time later than the first time.

[0112] In certain embodiments, the processor determines whether the power headroom value for each of the activated plurality of serving cells is based on a real uplink transmission or a virtual uplink transmission.

[0113] In some embodiments, the actual uplink transmission comprises a transmission based on a received uplink grant.

[0114] In various embodiments, the dummy uplink transmission comprises a dummy transmission based on a reference format.

[0115] In one embodiment, the power headroom report medium access control control element includes an indicator corresponding to each serving cell of the plurality of serving cells being activated, and the indicator indicates whether the power headroom value for the corresponding serving cell is real or virtual.

[0116] In certain embodiments, the power headroom report includes a power headroom corresponding to each of the plurality of serving cells that are activated, and the power headroom for the corresponding serving cell is real or virtual.

[0117] In some embodiments, the power headroom report is triggered in response to expiration of a timer.

[0118] In one embodiment, a method includes receiving a power headroom report medium access control control element, the power headroom report medium access control control element including a power headroom for each serving cell of a plurality of activated serving cells, wherein the power headroom for the respective serving cell is real or virtual.

[0119] In certain embodiments, the power headroom report medium access control control element includes an indicator corresponding to each serving cell of the plurality of serving cells that are activated, and the indicator indicates whether the power headroom value for the corresponding serving cell is real or virtual.

[0120] In some embodiments, the power headroom for the corresponding serving cell is real in response to the remote unit performing an uplink transmission in accordance with an uplink grant on the corresponding serving cell.

[0121] In various embodiments, in response to the remote unit not performing an uplink transmission on the serving cell in accordance with the uplink grant, the power headroom for the corresponding serving cell is virtual.

[0122] In one embodiment, an apparatus includes: a receiver that receives a power headroom report media access control control element, the power headroom report media access control control element including a power headroom for each of a plurality of activated service cells, wherein the power headroom for the corresponding service cell is real or virtual.

[0123] In certain embodiments, the power headroom report medium access control control element includes an indicator corresponding to each serving cell of the plurality of serving cells that are activated, and the indicator indicates whether the power headroom value for the corresponding serving cell is real or virtual.

[0124] In some embodiments, the power headroom for the corresponding serving cell is real in response to the remote unit performing an uplink transmission in accordance with an uplink grant on the corresponding serving cell.

[0125] In various embodiments, in response to the remote unit not performing an uplink transmission on the serving cell in accordance with the uplink grant, the power headroom for the corresponding serving cell is virtual.

[0126] In one embodiment, a method includes: generating a power headroom report media access control control element, which includes at least a power headroom value for each of a plurality of activated service cells; and sending the power headroom report media access control control element on resources allocated by a first uplink grant, wherein the power headroom value for at least one service cell is a virtual power headroom value, and the virtual power headroom value is based on a reference transmission format.

[0127] In some embodiments, a method for calculating a virtual power headroom report includes using predefined power control parameters from a set of configured power control parameters. In such embodiments, the predefined power control parameters may include P0, P O_PUSCH,c , α, or some combination thereof. In certain embodiments, a method for calculating a virtual power headroom report includes using a first configured power control parameter from each predefined power control parameter in a set of configured power control parameters. In various embodiments, a method for calculating a virtual power headroom report includes calculating a virtual power headroom report using predefined beam information.

[0128] Embodiments may be practiced in other specific forms. The described embodiments should be considered in all respects as merely illustrative and not restrictive. Therefore, the scope of the present invention is indicated by the appended claims rather than the preceding description. All changes within the meaning and equivalent range of the claims are included within their scope.

Claims

1. A method for generating a power headroom report, comprising: Aggregate multiple service cells; Determining that a power headroom report is triggered; receiving an uplink grant at a time after triggering the power headroom report, the uplink grant allocating uplink resources for an initial transmission; determining whether a power headroom report for an activated serving cell is based on a real or reference physical channel uplink shared channel transmission; responsive to determining that the power headroom report for the activated serving cell is based on the reference physical uplink shared channel transmission, calculating a power headroom value for the activated serving cell of the plurality of serving cells based on the reference physical uplink shared channel transmission, wherein the power headroom value is calculated using a predetermined set of power control parameters; generating a power headroom report medium access control control element including the power headroom value for the activated serving cell; as well as The power headroom report medium access control control element is sent on uplink resources allocated by the uplink grant.

2. The method according to claim 1, wherein: The time corresponds to a Physical Downlink Control Channel opportunity.

3. The method according to claim 1, wherein: The power headroom report is a type 1 power headroom report.

4. The method according to claim 1, wherein: The power headroom report medium access control control element includes an indicator indicating that the power headroom value is transmitted based on the reference physical uplink shared channel.

5. The method according to claim 1, wherein: In response to expiration of the timer, the power headroom report is triggered.

6. The method according to claim 1, wherein: The predetermined power control parameter set includes open-loop power control parameters.

7. The method according to claim 1, wherein: The predetermined power control parameter set includes an α value.

8. The method according to claim 1, wherein: The predetermined power control parameter set includes a power level.

9. A user equipment (UE) for power headroom report generation, the UE comprising: A processor, the processor: Aggregate multiple service cells; as well as Determining that a power headroom report is triggered; A receiver, the receiver receiving an uplink grant at a time after triggering the power headroom report, the uplink grant allocating uplink resources for an initial transmission, wherein: The processor further: determining whether a power headroom report for an activated serving cell is based on a real or reference physical channel uplink shared channel transmission; In response to determining that the power headroom report for the activated serving cell is based on the reference physical uplink shared channel transmission, calculating a power headroom value for the activated serving cell among the plurality of serving cells based on the reference physical uplink shared channel transmission, wherein the power headroom value is calculated using a predetermined set of power control parameters; generating a power headroom report medium access control control element including the power headroom value for the activated serving cell; and A transmitter transmits the power headroom report medium access control element on uplink resources allocated by the uplink grant.

10. The UE according to claim 9, wherein: The time corresponds to a Physical Downlink Control Channel opportunity.

11. The UE according to claim 9, wherein: The power headroom report is a type 1 power headroom report.

12. The UE according to claim 9, wherein: The power headroom report medium access control control element includes an indicator indicating that the power headroom value is transmitted based on the reference physical uplink shared channel.

13. The UE according to claim 9, wherein: In response to expiration of the timer, the power headroom report is triggered.

14. The UE according to claim 9, wherein: The predetermined power control parameter set includes open-loop power control parameters.

15. The UE according to claim 9, wherein: The predetermined power control parameter set includes an α value.

16. The UE according to claim 9, wherein: The predetermined power control parameter set includes a power level.

17. The UE according to claim 9, wherein: The predetermined power control parameter set includes P0.

18. The UE according to claim 9, wherein: The predetermined power control parameter set is a power control parameter set in a plurality of configured power control parameter sets, and each power control parameter set in the plurality of configured power control parameter sets includes a power level and an α value.

19. The UE according to claim 18, wherein: The power headroom value is calculated using a power level and an alpha value of a power control parameter set that is a first listed power control parameter set of the plurality of configured power control parameter sets.

Citation Information

Patent Citations

  • Apparatus and method for transmitting a power headroom report in a wireless communication system supporting multi-carriers

    CN103069870A

  • Method and apparatus for reporting maximum transmission power in wireless communication

    CN105491654A