CN113016216A - Reporting power headroom - Google Patents

Abstract

Apparatus, methods, and systems for reporting power headroom are disclosed. An apparatus 400 includes a processor 405 that identifies 605 a transmission opportunity for an AUL transmission on an unlicensed serving cell and generates 610 a PHR MAC CE. The apparatus 400 includes a transceiver 425 to transmit 615 a PHR MAC CE to a RAN node in a mobile communication network using AUL transmission, wherein transmitting the PHR MAC CE includes: timing information corresponding to the PHR is indicated.

Description

Reporting power headroom

Technical Field

The subject matter disclosed herein relates generally to wireless communications, and more specifically to reporting power headroom.

Background

The following abbreviations are herewith defined, at least some of which are referred to in the following description. Third generation partnership project ("3 GPP"), fifth generation core network ("5 CG"), fifth generation system ("5 GS"), authentication, authorization, and accounting ("AAA"), access and mobility management function ("AMF"), access restricted local operator service ("ARLOS"), positive acknowledgement ("ACK"), application programming interface ("API"), authentication center ("AuC"), access stratum ("AS"), autonomous uplink ("AUL"), AUL downlink feedback information ("AUL-DFI"), base station ("BS"), binary phase shift keying ("BPSK"), bandwidth part ("BWP"), clear channel assessment ("CCA"), control element ("CE"), cyclic prefix ("CP"), cyclic redundancy check ("CRC"), channel state information ("CSI"), common search space ("CSS"), "BPSK", and the like, Connected mode ("CM", which is NAS state in 5 GS), core network ("CN"), control plane ("CP"), data radio bearer ("DRB"), discrete Fourier transform extension ("DFTS"), Downlink control information ("DCI"), Downlink ("DL"), Downlink Pilot time Slot ("DwPTS"), Dual connectivity ("DC"), Dual registration mode ("DR mode"), enhanced clear channel assessment ("eCCA"), enhanced licensed assisted Access ("eLAA"), enhanced Mobile broadband ("eMBB"), evolved node B ("eNB"), evolved packet core ("EPC")), evolved packet System ("EPS"), mobility management ("EMM", which is NAS state in EPS), evolved UMTS terrestrial radio Access ("E-UTRA"), evolved UMTS terrestrial radio Access network ("E-UTRAN"), (E-UTRAN), European telecommunications standards institute ("ETSI"), frame-based devices ("FBE"), frequency division duplex ("FDD"), frequency division multiple access ("FDMA"), frequency division orthogonal cover code ("FD-OCC"), general packet radio service ("GPRS"), general public service identifier ("GPSI"), guard period ("GP"), global system for mobile communications ("GSM"), globally unique temporary UE identifier ("GUTI"), hybrid automatic repeat request ("HARQ"), home subscriber server ("HSS"), home public land mobile network ("HPLMN"), information element ("IE"), internet of things ("IoT"), international mobile subscriber identity ("IMSI"), licensed assisted access ("LAA"), load-based devices ("LBE"), listen-before-talk ("LBT"), long term evolution ("LTE"), multiple access ("MA"),(s), Mobility management ("MM"), mobility management entity ("MME"), modulation coding scheme ("MCS"), machine type communication ("MTC"), multiple-input multiple-output ("MIMO"), mobile station international subscriber directory number ("MSISDN"), multiple user shared access ("MUSA"), narrowband ("NB"), negative acknowledgement ("NACK") or ("NAK"), new generation (5G) node B ("gNB"), new generation radio access network ("NG-RAN", RAN for 5GS networks), new radio ("NR", 5G radio access technology; also known as "5G NR"), non-access stratum ("NAS"), network exposure function ("NEF"), non-orthogonal multiple access ("NOMA"), network slice selection assistance information ("NSSAI"), operation and maintenance system ("OAM"), orthogonal frequency division multiplexing ("OFDM"), (m-m), and (m-m) for example, Packet data units ("PDUs," used in conjunction with a "PDU session"), packet switched ("PS," e.g., packet switched domain or packet switched service), primary cell ("PCell"), physical broadcast channel ("PBCH"), physical downlink control channel ("PDCCH"), physical downlink shared channel ("PDSCH"), code division multiple access ("PDMA"), physical hybrid ARQ indicator channel ("PHICH"), physical random access channel ("PRACH"), physical resource block ("PRB"), physical uplink control channel ("PUCCH"), physical uplink shared channel ("PUSCH"), public land mobile network ("PLMN"), quality of service ("QoS"), quadrature phase shift keying ("QPSK"), radio access network ("RAN"), radio access technology ("RAT"), radio resource control ("RRC"), and, Random access channel ("RACH"), random access response ("RAR"), radio network temporary identifier ("RNTI"), reference signal ("RS"), registration area ("RA", similar to tracking area lists used in LTE/EPC), registration management ("RM", referring to NAS layer procedures and states), remaining minimum system information ("RMSI"), resource extended multiple access ("RSMA"), round trip time ("RTT"), receive ("RX"), radio link control ("RLC"), sparse code multiple access ("SCMA"), scheduling request ("SR"), single carrier frequency division multiple access ("SC-FDMA"), secondary cell ("SCell"), shared channel ("SCH"), session management ("SM" "), session management function (" SMF "), service provider (" SP "), signal-to-interference-plus-noise ratio (" SINR ")," LTE ", and the like, Single network slice selection assistance information ("S-NSSAI"), single registration mode ("SR mode"), sounding reference signal ("SRs"), system information block ("SIB"), synchronization signal ("SS"), supplemental uplink ("SUL"), subscriber identity module ("SIM"), tracking area ("TA"), 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"), unified access control ("UAC"), unified data management ("UDM"), user data repository ("UDR"), uplink control information ("UCI"), user entity/device (mobile terminal) ("UE"), UE configuration update ("UCU"), "UE" is, and, UE routing policies ("URSP"), uplink ("UL"), user plane ("UP"), universal mobile telecommunications system ("UMTS"), UMTS subscriber identity module ("USIM"), UMTS terrestrial radio access ("UTRA"), UMTS terrestrial radio access network ("UTRAN"), uplink pilot time slot ("UpPTS"), ultra-reliable and low-delay communications ("URLLC"), visited public land mobile network ("VPLMN"), and worldwide interoperability for microwave access ("WiMAX"). As used herein, "HARQ-ACK" may collectively refer to positive acknowledgement ("ACK") and negative acknowledgement ("NACK"). ACK means that the TB was received correctly, and NACK (or NAK) means that the TB was received in error.

For LTE eLAA, Autonomous Uplink (AUL) transmission may be enabled through a combination of an enabling message and RRC signaling conveyed by DCI in a physical control channel. The RRC configuration includes subframes in which the UE is allowed to autonomously transmit, and a legal HARQ process ID. The enabling message includes a Resource Block Allocation (RBA) and MCS from which the UE can determine the transport block size for any AUL transmission.

When using Autonomous Uplink (AUL) for unlicensed access in NR (NR-U), due to potential LBT failures, the gNB may not be able to determine when to initially generate UL transmissions/TBs even if subsequent transmissions (retransmissions) of the same HARQ process are correctly decoded by the gNB. This uncertainty may have some negative impact on the PHR transmission, among other things, because the PHR content at the time of transmission may not truly reflect the state at the time it was generated.

Disclosure of Invention

A process for reporting power headroom is disclosed. The apparatus and system also perform the functions of the method. The method may also be embodied in one or more computer program products comprising a computer-readable storage medium storing executable code that, when executed by a processor, performs the steps of the method.

A method of a UE for reporting power headroom comprising: a transmission opportunity for an AUL transmission on an unlicensed serving cell is identified. The method comprises the following steps: generating a power headroom report ("PHR") medium access control ("MAC") control element ("CE"), and transmitting the PHR MAC CE to a RAN node in the mobile communication network using AUL transmission, wherein the transmitting PHR MAC CE includes timing information corresponding to a PHR.

Another method of a UE for reporting power headroom includes: a first transmission opportunity of AUL transmission on an unlicensed serving cell is identified and a PHR MAC CE is generated that includes power headroom information for each enabled serving cell configured with an uplink, wherein the power headroom information for the enabled serving cell is calculated for a predetermined PHR type in response to the serving cell being configured with two UL carriers. The method includes transmitting the PHR MAC CE to a RAN node in the mobile communication network in an AUL transmission.

Yet another method of a UE for reporting power headroom includes: a first transmission opportunity on a configured uplink grant resource is identified. The method comprises the following steps: generating a PHR MAC CE including power headroom information of each enabled serving cell, and transmitting the PHR MAC CE to a RAN node in a mobile communication network. Here, the power headroom information is calculated for a predetermined PHR type in response to the serving cell being configured with two UL carriers.

Drawings

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

fig. 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for reporting power headroom;

fig. 2 is a diagram illustrating one embodiment of uplink control information for autonomous uplink transmission;

fig. 3 is a diagram illustrating one embodiment of a MAC control element for power headroom reporting;

fig. 4 is a schematic block diagram illustrating one embodiment of a user equipment device that may be used to report power headroom;

fig. 5 is a schematic block diagram illustrating one embodiment of a base station apparatus that may be used to report power headroom;

FIG. 6 is a block diagram illustrating one embodiment of a method for reporting power headroom;

fig. 7 is a block diagram illustrating another embodiment of a method for reporting power headroom; and

fig. 8 is a block diagram illustrating yet another embodiment of a method for reporting power headroom.

Detailed Description

As will be appreciated by one skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects.

For example, the disclosed embodiments may be implemented as hardware circuits comprising custom very large scale integration ("VLSI") circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. The disclosed embodiments may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like. As another example, the disclosed embodiments may include one or more physical or logical blocks of executable code, which may be organized as an object, procedure, or function, for example.

Furthermore, embodiments may take the form of a program product embodied in one or more computer-readable storage devices that store machine-readable code, computer-readable code, and/or program code (hereinafter code). The storage device may be tangible, non-transitory, and/or non-transmitting. The storage device may not embody the signal. In a certain embodiment, the storage device only employs signals for the access codes.

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 the code. A 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.

More specific examples (a non-exhaustive list) of the storage device may 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.

The code for carrying out operations of embodiments may be in any number of lines and may be written in any combination of one or more programming languages, including an object oriented programming language such as Python, Ruby, Java, Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language and/or machine languages, such as assembly language. The code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network ("LAN") or a wide area network ("WAN"), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

Reference throughout this specification to "one embodiment," "an embodiment," or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases "in one embodiment," "in an embodiment," and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean "one or more but not all embodiments" unless expressly specified otherwise. The terms "comprising," "including," "having," and variations thereof mean "including, but not limited to," unless expressly specified otherwise. The enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms "a", "an" and "the" also mean "one or more", unless expressly specified otherwise.

As used herein, a list having a conjunction of "and/or" includes any single item in the list or combination of items in the list. For example, the list of A, B and/or C includes a combination of only a, only B, only C, A and B, B and C, a and C, or A, B and C. As used herein, a list using one or more of the terms "includes any single item in the list or combination of items in the list. For example, one or more of A, B and C includes A only, B only, a combination of C, A and B only, B and C only, A and C only, or A, B and C only. As used herein, a list using one of the terms "includes one and only one of any single item in the list. For example, "one of A, B and C" includes a alone, B alone, or C alone, and excludes a combination of A, B and C. As used herein, "a member selected from the group consisting of A, B and C" includes one and only one of A, B or C, and excludes a combination of A, B and C. As used herein, "a member selected from the group consisting of A, B and C, and combinations thereof" includes a alone, B alone, C, A and B alone, B and C alone, a and C alone, or A, B and C alone.

Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous 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 embodiments. One skilled in the relevant art will recognize, however, that an embodiment may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the embodiments.

Various aspects of the embodiments are described below with reference to schematic flow charts and/or schematic block diagrams of methods, apparatus, systems, and program products according to the embodiments. It is to be understood that each block of the schematic flow chart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flow chart diagrams and/or schematic block diagrams, can be implemented by code. The code may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code which executes on the computer or other programmable apparatus provides processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and/or block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods and program products according to various embodiments. In this regard, each block in the flowchart and/or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s).

It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated figure.

Although various arrow types and line types may be employed in the flow chart diagrams and/or block diagram block or blocks, they are understood not to limit the scope of the corresponding embodiment. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and code.

The description of the elements in each figure may refer to elements of previous figures. Like numbers refer to like elements throughout, including alternative embodiments of the same elements.

[ summary of the invention ]

In general, this disclosure describes systems, methods, and apparatuses for reporting power headroom. In certain wireless communication networks, such as LTE eLAA, autonomous uplink ("AUL") transmission is enabled through a combination of an enabling message and RRC signaling conveyed by DCI in a physical control channel. The RRC configuration includes subframes in which the UE is allowed to autonomously transmit and a legal HARQ process ID. The enabling message includes a resource block allocation ("RBA") and a modulation and coding scheme ("MCS") from which the UE can determine a transport block size for any AUL transmission.

Data belonging to transport blocks that are not correctly received by the eNB may be autonomously retransmitted. To this end, the UE monitors the AUL downlink feedback information (e.g., "AUL-DFI") transmitted by the eNB. The AUL-DFI includes HARQ-ACK information of the AUL-enabled HARQ process ID. In case the UE detects a NACK message, it may attempt autonomous access to a channel for retransmitting the same transport block in a corresponding HARQ process. As a safety guarantee against errors, the AUL transmission includes at least a new data indicator ("NDI") and a HARQ process ID accompanying the PUSCH. In various embodiments, the AUL transmission includes uplink control information, an AUL-UCI including a HARQ process ID and an NDI.

The eNB may also transmit an uplink grant through DCI that allocates uplink resources using the indicated HARQ process for retransmission of the same transport block. The eNB may also transmit the uplink grant through DCI that allocates uplink resources for transmission of a new transport block using the indicated HARQ process. In other words, even though the HARQ process ID may be legitimate for AUL transmission, the eNB still has access to the process at any time through a scheduling grant (e.g., in DCI). In general, if the UE detects a grant for UL transmission for a subframe legitimate to the AUL (according to RRC configuration), the UE will follow the received grant and will not perform the AUL transmission in that subframe.

When using an AUL for unlicensed access in NR (an AUL called NR-U), due to potential listen before talk ("LBT") failures, the gNB may not be able to determine when to initially generate UL transmissions/TBs even if subsequent transmissions (retransmissions) of the same HARQ process are correctly decoded by the gNB. This uncertainty may have some negative impact on the transmission of the PHR, among other things, because the PHR content at the time of transmission may not accurately reflect the state at the time it was generated. This may affect UL scheduling and link adaptation.

A more serious problem is that for the SUL case, e.g. the UE is configured with two UL carriers for the serving cell, the gNB needs to know when to generate a PHR in order to know what type of PHR is reported in the PHR MAC, e.g. type 1PHR or type 3 PHR. Currently, depending on whether the UE determines the PHs of the two carriers to be real or virtual, the UE needs to report whether it is type 1PH or type 3 PH.

If the UE is configured with two UL carriers for the serving cell, and if the UE reports the UE capability "simultaneousTxSUL-nosul" for the serving cell, and if the UE determines that the type 1 power headroom report of the serving cell is based on the reference PUSCH transmission and the type 3 power headroom report of the serving cell is based on the reference SRS transmission, the UE provides a type 1 PHR.

If the UE is configured with two UL carriers for the serving cell, and if the UE reports the UE capability "simultaneousTxSUL-nosul" for the serving cell, and if the UE determines that the power headroom of only one of the two UL carriers of the serving cell is based on the actual transmission, the UE provides a type 1PHR when the actual transmission is a PUSCH transmission, or a type 3PHR when the actual transmission is an SRS transmission.

In order to know whether the PHR value reported at the gbb side is a type 1PHR or a type 3PHR, the gbb needs to know which grants are considered by the PH determination. Therefore, the gNB basically needs to know when to generate a PHR in order to know whether a PHR MAC CE contains a PHR type 1 report or a PHR type 3 report. It should be noted that the PHR MAC CE format (multi-entry PHR MAC CE) does not explicitly indicate the PHR type according to TS 38.321 v15.3.0.

The present disclosure includes embodiments that provide a solution for reporting power headroom. In a first solution, the UE signals timing information to a RAN node, such as a gNB, eNB, etc., indicating whether the respective uplink transmission represents a first transmission attempt or a second or later transmission attempt. In a second solution, the UE updates the contents of the MAC CE contained in the TB for each transmission attempt. In a third solution, the UE always reports a predefined PHR type, e.g. type 1PHR, when transmitting the PHR MAC CE on the unlicensed cell. In a fourth solution, a field in the PHR MAC CE indicates the type of PH value reported. In a fifth solution, the UE prioritizes PHR MAC CE transmission on the licensed cell over PHR MAC CE transmission on the unlicensed cell. In a sixth solution, the UE reports a virtual PHR of a predefined PHR type, e.g. PHR type 1, for a serving cell configured with two UL carriers.

[ FIG. 1]

Fig. 1 depicts an embodiment of a wireless communication system 100 for accessing denied network resources in accordance with various embodiments of the present disclosure. In one embodiment, wireless communication system 100 includes remote unit 105, base unit 110, and communication link 115. Although a particular number of remote units 105, base station units 110, and communication links 115 are depicted in fig. 1, those skilled in the art will appreciate that any number of remote units 105, base station units 110, and communication links 115 may be included in wireless communication system 100.

In one embodiment, the wireless communication system 100 conforms to the NR system specified in the 3GPP specification and/or the LTE system specified in the 3 GPP. More generally, however, the wireless communication system 100 may implement some other open or proprietary communication networks, such as WiMAX and others. The present disclosure is not intended to be limited to implementation of any particular wireless communication system architecture or protocol.

In one embodiment, remote unit 105 may include a computing device such as a desktop computer, laptop computer, personal digital assistant ("PDA"), tablet computer, smart phone, smart television (e.g., television connected to the internet), smart appliance (e.g., appliance connected to the internet), set-top box, gaming console, security system (including security camera), on-board computer, networking device (e.g., router, switch, modem), and so forth. In some embodiments, remote unit 105 includes a wearable device, such as a smart watch, a fitness band, an optical head-mounted display, and so forth. Moreover, remote unit 105 may be referred to as a subscriber unit, mobile device, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, UE, user terminal, device, or by other terms used in the art. Remote units 105 may communicate directly with one or more base units 110 via uplink ("UL") and downlink ("DL") communication signals. Further, UL and DL communication signals may be carried on communication link 115.

In some embodiments, the remote unit 105 may decide to establish a data connection (e.g., a PDU session) with an application service area ("AS") 151 in the data network 150 via the mobile core network 130. Here, the data path of the PDU session may be established on one of a plurality of network slices supported by the mobile core network 130. The particular network slice used by the PDU session may be determined by the S-NSSAI attribute of the PDU session. Here, the remote unit 105 may be provided with network slice selection policy ("NSSP") rules that the remote unit 105 uses to determine how to route the requested PDU session.

Base units 110 may be distributed over a geographic area. In some embodiments, base station unit 110 may also be referred to as a RAN node, access terminal, base station, nodeb, eNB, gNB, home nodeb, relay node, home base station, access point, device, or by any other terminology used in the art. Base unit 110 is typically part of an access network 120, such as a radio access network ("RAN"), which access network 120 may include one or more controllers communicatively coupled to one or more respective base units 110. These and other elements of access network 120 are not shown, but are generally well known to those of ordinary skill in the art. The base station unit 110 is connected to a mobile core network 130 via an access network 120. The access network 120 and the mobile core network 130 may be collectively referred to herein as a "mobile network" or a "mobile communication network".

Base unit 110 may serve several remote units 105 within a serving area (e.g., a cell or cell sector) via a wireless network link. Base unit 110 may communicate directly with one or more remote units via communication signals. In general, base unit 110 transmits downlink ("DL") communication signals in the time, frequency, and/or spatial domains to serve remote unit 105. Further, DL communication signals may be carried on the communication link 115. The communication link 115 may be any suitable carrier in the licensed or unlicensed radio spectrum. Communication links 115 facilitate communication between one or more remote units 105 and/or one or more base units 110.

In one embodiment, the mobile core network 130 is a 5G core ("5 GC"), which may be coupled to several networks 150, such as the internet, private data networks, and other data networks. In some embodiments, the remote unit 105 communicates with an application server ("AS") 151 (external to the mobile core network 130) via a network connection with the mobile core network 130. Each mobile core network 130 belongs to a single public land mobile network ("PLMN"). The present disclosure is not intended to be limited to implementation of any particular wireless communication system architecture or protocol. For example, other embodiments of mobile core network 130 include an enhanced packet core ("EPC") or a multi-service core, as described by the broadband forum ("BBF").

The mobile core network 130 includes several network functions ("NFs"). As shown, the mobile core network 130 includes at least one user plane function ("UPF") 131. The mobile core network 130 also includes a number of control plane functions including, but not limited to, an access and mobility management function ("AMF") 133, a session management function ("SMF") 135, a network exposure function ("NEF") 137, a policy control function ("PCF") 138, a unified data management and unified data repository function ("UDM/UDR") 139 that serve the access network 120. The control plane network functions provide services such as UE registration, UE connection management, UE mobility management, session management, etc. Instead, the UPF provides data transmission services to the remote unit 105. In some embodiments, the mobile core network 130 may also include an authentication server function ("AUSF"), a network repository function ("NRF") (used by various NFs to discover and communicate with each other through application programming interfaces ("APIs")) or other NFs defined for 5 GCs.

NEF 137 supports exposure of capabilities and events, secure provision of information from external applications to the 3GPP network, translation of internal/external information. UDM/UDR 139 includes unified data management ("UDM") and its internal component user data repository ("UDR"). The UDR maintains subscription data including policy data. In particular, the policy data stored by the UDM/UDR 139 includes NSSPs.

Although a particular number and type of network functions are depicted in fig. 1, those skilled in the art will appreciate that any number and type of network functions may be included in mobile core network 130. Furthermore, where the mobile core network 130 is an EPC, the depicted network functions may be replaced with appropriate EPC entities such as MME, SGW, HSS, etc. In some embodiments, mobile core network 130 may include an authentication, authorization, and accounting ("AAA") server.

In various embodiments, mobile core network 130 supports different types of mobile data connections and different types of network slices, where each mobile data connection utilizes a particular network slice. Here, "network slice" refers to a portion of the mobile core network 130 that is optimized for a certain traffic type or communication service. In some embodiments, various network slices may include separate instances of network functions, such as SMF 135 and UPF 131. In some embodiments, different network slices may share some common network functions, such as the AMF 133. For ease of illustration, different network slices are not shown in fig. 1, but are assumed to be supported.

A network slice is a logical network within the mobile core network 130. In certain embodiments, a network slice is a partition of resources and/or services of mobile core network 130. Different network slices may be used to meet different service requirements (e.g., delay, reliability, and capacity). Examples of different types of network slices include enhanced mobile broadband ("eMBB"), large machine type communication ("mtc"), and ultra-reliable and low latency communication ("URLLC"). Mobile core network 130 may include multiple network slice instances of the same network slice type. Different network slice instances of the same type may be distinguished by a slice "tenant" (also referred to as a "slice discriminator") associated with the instance.

Due to LBT failure, base unit 110 may not know when the UE generates TBs transmitted on the configured grant resources and therefore when to calculate the PHR. This timing uncertainty basically causes two problems. The first problem is that the base station unit 110 does not know for which UL resource allocation (e.g. the PRBs allocated in the time slot for which the PHR is calculated) the PH is calculated/reported, and therefore some erroneous conclusions may be made for future scheduling. Second, base station unit 110 may not know the reported PHR type-for the case of a serving cell configured with two UL carriers-and thus may misinterpret the reported PH value, which may in turn lead to future scheduling decisions that negatively impact performance.

To address the above-described problems of PHR reporting of AUL transmissions 125, remote unit 105 may perform one or more of the following: conveying timing information as part of the AUL-UCI, updating the PH value of the second/subsequent transmission attempt, reporting all the time using a predefined PHR type when PHR MAC CE is transmitted on AUL PUSCH, and/or applying policy rules for PHR types.

According to a first solution, the remote unit 105 signals timing information related to calculating power headroom information to the base station unit 110(RAN node, such as a gNB, eNB, etc.) indicating whether the corresponding uplink transmission corresponds to (1) a first transmission attempt or (2) a second or later transmission attempt. Because the remote unit 105 must first go through a CCA (clear channel assessment) procedure before it can transmit on the unlicensed spectrum, for example, the remote unit 105 may not be able to transmit the generated TB immediately on the first transmission occasion/attempt, but only at a later point in time when LBT (listen before talk) succeeds, since the CCA procedure is unsuccessful for the first transmission attempt.

The timing information may be used by the base station unit 110(RAN node) for future scheduling/link adaptation. In particular, when the PHR MAC CE is received, it is important that the base unit 110 know when to calculate the PHR information in the remote unit 105 in order to correctly interpret the reported PH value.

According to an embodiment of the first solution, the timing information may be signaled by a 1-bit field/flag. For example, when set to '1', the flag indicates that an uplink transmission occurred at the first transmission opportunity/attempt, e.g., CCA success. Similarly, a flag set to '0' indicates that the uplink transmission is completed at the second or later transmission attempt, e.g., the generated TB cannot be transmitted immediately due to the CCA being unsuccessful. In other embodiments, the flag value may be switched such that a value of '0' indicates a first transmission attempt and a value of '1' indicates a second or later transmission attempt.

According to another embodiment of the first solution, the timing information may indicate an offset (e.g., number of frames, slots, subframes, or symbols) of the first transmission attempt using a plurality of bits. In case the CCA is successful for the first transmission attempt, e.g. the generated TB is transmitted immediately at the corresponding next available PUSCH occasion, the timing information will indicate a "zero" slot/symbol offset. Accordingly, when the transmission of the TB occurs 5 slots after the first transmission attempt, e.g., before LBT failure, the timing information will indicate an offset of 5 slots. Alternatively, the timing information may indicate the number of transmission attempts and the number of LBT failures until the CCA is successful, respectively, using a plurality of bits, for example.

According to certain embodiments of the first solution, the timing information is transmitted as part of Uplink Control Information (UCI) which is transmitted independently of PUSCH transmissions (transport blocks). The UCI conveying timing information is encoded separately from the PUSCH data. Thus, the base unit 110 receiver will decode UCI and PUSCH separately. In one implementation of the first embodiment, the timing information is carried within the AUL-UCI.

[ FIG. 2]

Fig. 2 depicts one embodiment of an AUL-UCI 200 in accordance with an embodiment of the present disclosure. The AUL-UCI 200 contains a number of fields including an AUL-RNTI 205, a number of HARQ processes 210, a redundancy version ("RV") 215, a new data indicator ("NDI") 220, a PUSCH start symbol 225, a PUSCH end symbol 230, a channel occupancy time ("COT") share indication 235. Importantly, the AUL-UCI 200 includes a 'PH timing information' field 240 that indicates timing related to calculating power headroom information. As shown, the PH timing information 240 may be represented by three bits in the AUL-UCI. In one embodiment, the PH timing information 240 indicates the number of transmission attempts. In another embodiment, the PH timing information 240 indicates an offset for the first transmission attempt. The information carried in this field is used in the scheduler/gNB for future scheduling/link adaptation. It basically provides the base station unit 110 with information when the TB is generated.

According to a second solution, the remote unit 105 updates the contents of the MAC CE contained in the TB for each transmission attempt. For example, in the event that a generated TB cannot be transmitted at a transmission (PUSCH) opportunity due to LBT failure, remote unit 105 will update the contents of the MAC CE carried within the TB for the next transmission attempt. In other words, the MEC CE in the TB always indicates the latest value.

In particular, for a PHR MAC CE contained in a TB, the remote unit 105 may update the reported PH value for each transmission attempt so that when the PHR MAC CE is received, the base station unit 110 knows when to calculate the reported PH value, e.g., the base station unit 110 knows which control information (such as uplink grants and configuration grants) to consider when calculating the reported PHR. The second solution also ensures that the base station unit 110 knows what type of PHR is reported within the PHR MAC CR, e.g. for a cell configured with two UL carriers (SUL and NUL), type 1PHR or type 3 PHR.

In addition to PHR MAC CEs, it may also be beneficial for the scheduler to update the BAR MAC CE indicating the buffer status of the remote unit 105 for each transmission attempt. According to one implementation of the second embodiment, only the reported values within the MAC CE, e.g. PHR MAC CE, are updated for each transmission attempt, but the PDU format of the MAC CE is not changed. This ensures that the remote unit 105 does not need to run the Logical Channel Prioritization (LCP) procedure again.

According to a third solution, the remote unit 105 always reports a predefined PHR type, e.g., type 1PHR, for a serving cell configured with two (uplink) carriers (e.g., SUL and NUL) and/or for transmitting PHR MAC CEs on an unlicensed serving cell. As described above, the remote unit 105 reports type 1PHR reports or type 3PHR reports for the serving cell configured with two carriers depending on whether actual PUSCH or SRS transmission occurs on the carrier in the reporting slot, according to the UE behavior currently defined in the standard. Thus, the base unit 110 needs to know when the remote unit 105 determines the PHR type of the serving cell in order to know what information is included in the PHR MAC CE, e.g., PHR type 1 or PHR type 3.

According to various embodiments of the third solution, new/special rules for PHR value determination (PHR type 1 and PHR type 3) may be used in case of PHR MAC CE transmission on an unlicensed cell, compared to case of PHR MEC CE transmission on a licensed cell. This new rule ensures that the gNB always knows what PHR type, e.g. type 1PHR or type 3PHR, is signaled in the PHR MAC CE.

According to one embodiment of the third solution, for a serving cell configured with two carriers (e.g., SUL and NUL) and transmitting PHR MAC CE on the AUL PUSCH, the remote unit 105 always reports using a predefined PHR type (e.g., type 1 PHR). Legacy UE reporting behavior relative to PHR reporting is applied for scheduled PUSCH transmissions on unlicensed cells.

One implementation of the third solution can be described using the following rules: if the UE (remote unit 105) is configured with two UL carriers for the serving cell, and if the UE reports UE capability simultaneousTxSUL-nosul for the serving cell, and if the PHR is transmitted on the AUL-PUSCH, the UE (remote unit 105) provides a type 1PHR for the serving cell.

According to a fourth solution, a field in the PHR MAC CE indicates the type of PH value reported, e.g. PHR type 1 or PHR type 3. According to one embodiment of the fourth solution, P is signaled for the serving cell_cmaxIs used to indicate the PHR type. In one embodiment, when one of the reserved fields 'R' is set to '1', it may indicate that the PH value is a type 1PH value. Accordingly, when set to '0', the corresponding reported PH is a type 3 PH. In another embodiment, two 'R' fields may be used to indicate the PHR type (e.g., to distinguish up to four different PHR types).

[ FIG. 3]

Fig. 3 depicts one embodiment of a MAC PDU format 300 for a PHR MAC CE, according to an embodiment of the present invention. The MAC PDU format 300 may be used to implement the fourth solution described herein. It should be noted that the options shown should only be understood as examples of embodiments. As shown, the exemplary MAC PDU format for PHR MAC CE contains a new field denoted as 'T' indicating the PHR type. Including P_cmaxIs reused as a new 'T' field as one (or two) 'R' fields in the octet(s) of (a).

According to a fifth solution, the remote unit 105 prioritizes PHR MAC CE transmission on the licensed cell over PHR MAC CE transmission on the unlicensed cell. Here, for the case where there is PUSCH resource available for initial transmission on both the licensed and unlicensed cells, remote unit 105 transmits the PHR MAC CE on the PUSCH resource of the licensed cell, e.g., before triggering the PHR. According to one embodiment of the fifth solution, in the event that the remote unit 105 is configured with at least one licensed cell and at least one unlicensed cell, the remote unit 105 always transmits PHR MAC CEs on the licensed cell, e.g., transmission of PHR MAC CEs on the unlicensed cell is not allowed. According to another embodiment of the fifth solution, the remote unit 105 does not transmit the PHR MAC CE on the AUL-PUSCH. Here, the remote unit 105 does not multiplex the PHR MAC CE in the transport block when performing the LCP procedure for AUL transmission.

According to a sixth solution, a remote unit 105 (e.g., UE) configured with carrier aggregation reports a virtual PHR of a predefined PHR type (e.g., PHR type 1) for a serving cell configured with two UL carriers. Further, remote unit 105 reports virtual PHR for other enabled serving cells (with configured uplink) for either 1) the case of transmitting PHR MAC CE on a configuration grant, e.g., the PHSCH resource allocated by the configuration grant, or 2) the case of transmitting PHR MAC CE on a configuration grant PUSCH resource and the MAC entity configured with lch-basedprioritification. According to this embodiment of the sixth solution, the remote unit 105 reports the virtual PHR for all enabled serving cells (with configured uplink), i.e. reports a virtual PHR of a predefined PHR type (e.g. PHR type 1) for a serving cell configured with two UL carriers.

According to an alternative embodiment of the sixth solution, the remote unit 105 reports the actual PHR for the serving cell on which the PHR MAC CE is transmitted and reports the virtual PHR for the other enabled serving cells (with configured uplink). Furthermore, if the serving cell is configured with two UL carriers, the remote unit 105 reports a virtual PHR of a predefined PHR type for the case where the PHR MAC CE is transmitted on a configuration grant on an unlicensed cell or the case where the PHR MAC CE is transmitted on a configuration grant PUSCH resource and the MAC entity is configured with lch-basedpropriority.

Reporting a predefined/fixed PHR type for a serving cell configured with two UL carriers solves the problem of base station unit 110 (e.g., the gNB) not knowing the reported PHR type. Reporting the virtual PHR solves the problem that base station unit 110 (e.g., the gNB) does not know which UL resource allocations to calculate the PH for. It should be noted that the same problem may also occur for the case where configuration grant PUSCH transmissions are preempted or de-prioritized due to overlapping PUSCH resources required for some higher priority UL transmissions. For example, the configuration grant may be preempted by a later received dynamic UL grant that schedules overlapping PUSCH resources. Thus, according to a sixth solution, for the case where the MAC entity is configured with lch-basedproprioritization, a remote unit 105 configured with carrier aggregation reports a virtual PHR of a predefined PHR type (e.g., PHR type 1) for a serving cell configured with two UL carriers and reports the virtual PHR for other enabled serving cells (with configured uplink). The condition "lch-basedPrioritization" refers to a situation where the network (e.g., base unit 110) configures remote unit 105 to allow (low) priority UL transmissions to be de-prioritized/preempted by some (later) high priority UL grants/transmissions, a new feature of industrial IOT WI. It is assumed that each UE is configured with a prioritization mechanism feature for backward compatibility and separate from UEs that do not support this feature. The terminology may be changed later in further discussion in 3 GPP.

According to another embodiment, a remote unit 105 that is not configured with carrier aggregation reports a virtual PHR for the serving cell for the case where the PHR MAC CE is transmitted on a configuration grant, e.g., the PHSCH resource allocated by the configuration grant, and the serving cell is an unlicensed cell, and the case where the PHR MAC CE is transmitted on a configuration grant PUSCH resource and the MAC entity is configured with lch-basedproprioritization. According to one embodiment of this embodiment, the UE reports P within a single entry PHR MAC CE even when a virtual PHR is reported_CMAX,f,cThe value is obtained.

[ FIG. 4-UE APPARATUS 400]

Fig. 4 depicts a user equipment device 400 that may be used for PHR reporting in accordance with an embodiment of the present disclosure. In various embodiments, the user equipment device 400 is used to implement one or more of the above solutions. The user equipment device 400 may be one embodiment of the remote unit 105 described above. Further, the user equipment device 400 may include a processor 405, a memory 410, an input device 415, an output device 420, and a transceiver 425. In some embodiments, the input device 415 and the output device 420 are combined into a single device, such as a touch screen. In some embodiments, the user equipment device 400 may not include any input devices 415 and/or output devices 420. In various embodiments, the user equipment device 400 may include one or more of the following: processor 405, memory 410, and transceiver 425, and may not include input device 415 and/or output device 420.

In one embodiment, the processor 405 may include any known controller capable of executing computer readable instructions and/or capable of performing logical operations. For example, the processor 405 may be a microcontroller, microprocessor, central processing unit ("CPU"), graphics processing unit ("GPU"), auxiliary processing unit, field programmable gate array ("FPGA"), or similar programmable controller. In some embodiments, the processor 405 executes instructions stored in the memory 410 to perform the methods and routines described herein. The processor 405 is communicatively coupled to a memory 410, an input device 415, an output device 420, and a receiver 425.

In various embodiments, the processor 405 identifies a transmission opportunity for an AUL transmission on an unlicensed serving cell and generates a PHR MAC CE. The receiver 425 then transmits the PHR MAC CE to the RAN node in the mobile communication network using AUL transmission. Here, transmitting the PHR MAC CE includes: timing information corresponding to the PHR is indicated. In some embodiments, the timing information provides the RAN node with information about the first transmission attempt of the PHR MAC CE. In some embodiments, the timing information includes a 1-bit flag, wherein a first value of the 1-bit flag indicates that the PHR MAC CE transmission corresponds to a first transmission attempt and a second value of the 1-bit flag indicates that the PHR MAC CE transmission corresponds to a subsequent transmission attempt.

In some embodiments, the timing information includes an indication of a timing offset between the PHR MAC CE transmission and the first transmission attempt. In one embodiment, the timing offset indicates the number of time slots that have elapsed since the first transmission attempt. In another embodiment, the timing offset indicates the number of symbols that have passed since the first transmission attempt. In some embodiments, the timing information includes an indication of a number of transmission attempts prior to the PHR transmission. In some embodiments, the timing information is transmitted as part of the uplink control information and is encoded separately from the PHR.

In various embodiments, the processor 405 identifies a transmission opportunity for an AUL transmission on an unlicensed serving cell. The processor 405 generates a PHR MAC CE including power headroom information for each enabled serving cell configured with an uplink. Here, the power headroom information of the enabled serving cell is calculated for a predetermined PHR type in response to a serving cell configured with two UL carriers. The transceiver 425 then transmits the PHR MAC CE to the RAN node in the mobile communication network in an AUL transmission. In some embodiments, the processor 405 prioritizes transmission of the PHR MAC CE on the licensed cell over transmission of the PHR on the unlicensed serving cell.

In various embodiments, the processor 405 identifies a first transmission opportunity on the configured uplink grant resource. The processor 405 generates a PHR MAC CE including power headroom information for each enabled serving cell. Here, the power headroom information is calculated for a predetermined PHR type in response to the serving cell being configured with two UL carriers. The transceiver 425 then transmits the PHR MAC CE in the configuration authorization transmission to the RAN node in the mobile communication network.

In some embodiments, generating the PHR MAC CE comprises: reporting the virtual power headroom of each enabled serving cell in response to transmitting the PHR MAC CE on the configured uplink grant and further in response to the MAC entity of the user equipment device 400 being configured to lower prioritized uplink transmissions while supporting higher priority uplink transmissions. In these embodiments, preparing the PHR MAC CE includes: the virtual PHR is reported for a predefined PHR type in response to a serving cell configured with two UL carriers.

In some embodiments, the user equipment device 400 is configured for carrier aggregation using a plurality of enabled serving cells, wherein preparing the PHR MAC CE comprises: the actual PHR is reported for the serving cell on which the PHR MAC CE is to be transmitted, and the virtual PHR is reported for one or more other enabled serving cells.

In one embodiment, memory 410 is a computer-readable storage medium. In some embodiments, memory 410 includes volatile computer storage media. For example, the memory 410 may include RAM, including dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and/or static RAM ("SRAM"). In some embodiments, memory 410 includes non-volatile computer storage media. For example, memory 410 may include a hard drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 410 includes volatile and nonvolatile computer storage media.

In some embodiments, memory 410 stores data related to power headroom reports. For example, the memory 410 may store PH values, AUL data, AUL configuration information, timing offsets, and the like. In certain embodiments, memory 410 also stores program code and related data, such as an operating system or other controller algorithms operating on remote unit 102.

In one embodiment, input device 415 may comprise any known computer input device, including a touch panel, buttons, a keyboard, a stylus, a microphone, and the like. In some embodiments, the input device 415 may be integrated with the output device 420, for example, as a touch screen or similar touch sensitive display. In some embodiments, the input device 415 includes a touch screen, such that text may be entered using a virtual keyboard displayed on the touch screen and/or by handwriting on the touch screen. In some embodiments, input device 415 includes two or more different devices, such as a keyboard and a touch panel.

In one embodiment, output device 420 is designed to output visual, audible, and/or tactile signals. In some embodiments, output device 420 comprises an electronically controllable display or display device capable of outputting visual data to a user. For example, output device 420 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or similar display device capable of outputting images, text, and the like to a user. As another non-limiting example, the output device 420 may include a wearable display, such as a smart watch, smart glasses, heads-up display, or the like, separate from the user equipment apparatus 400 but communicatively coupled to the user equipment apparatus 400. Further, output device 420 may be a component of a smart phone, personal digital assistant, television, desktop computer, notebook (laptop) computer, personal computer, vehicle dashboard, or the like.

In some embodiments, the output device 420 includes one or more speakers for producing sound. For example, the output device 420 may generate an audible alarm or notification (e.g., a beep or alert tone). In some embodiments, output device 420 includes one or more haptic devices for generating vibrations, motions, or other haptic feedback. In some embodiments, all or part of the output device 420 may be integrated with the input device 415. For example, the input device 415 and the output device 420 may form a touch screen or similar touch sensitive display. In other embodiments, the output device 420 may be located near the input device 415.

As described above, the transceiver 425 communicates with one or more network functions of the mobile communication network via one or more access networks. The transceiver 425 operates under the control of the processor 405 to transmit and also receive messages, data, and other signals. For example, the processor 405 may selectively enable the transceiver 415 (or a portion thereof) at particular times in order to send and receive messages.

The transceiver 425 may include one or more transmitters 430 and one or more receivers 435. Although only one transmitter 430 and one receiver 435 are shown, the user equipment device 400 may have any suitable number of transmitters 430 and receivers 435. Further, the transmitter 430 and the receiver 435 may be any suitable type of transmitter and receiver. Further, the transceiver 425 may support at least one network interface 440. Here, the at least one network interface 440 facilitates communication with a RAN node (such as an eNB or a gNB), for example, using a "Uu" interface. Further, the at least one network interface 440 may include an interface for communicating with one or more network functions (such as UPF, AMF, and/or SMF) in the mobile core network.

In one embodiment, the transceiver 425 includes a first transmitter/receiver pair for communicating with a mobile communications network over a licensed radio spectrum and a second transmitter/receiver pair for communicating with the mobile communications network over an unlicensed radio spectrum. In some embodiments, a first transmitter/receiver pair for communicating with a mobile communications network over a licensed radio spectrum and a second transmitter/receiver pair for communicating with a mobile communications network over an unlicensed radio spectrum may be combined into a single transceiver unit, e.g., a single chip that performs the functions for the licensed and unlicensed radio spectra. In some embodiments, the first transmitter/receiver pair and the second transmitter/receiver pair may share one or more hardware components. For example, certain of the transceiver 425, the transmitter 430, and the receiver 435 may be implemented as physically separate components that access shared hardware resources and/or software resources, such as, for example, the network interface 440.

In various embodiments, the one or more transmitters 430 and/or the one or more receivers 435 may be implemented and/or integrated into a single hardware component, such as a multi-transceiver chip, a system-on-a-chip, an application specific integrated circuit ("ASIC"), or other type of hardware component. In some embodiments, one or more transmitters 430 and/or one or more receivers 435 may be implemented and/or integrated into a multi-chip module. In some embodiments, other components such as the network interface 440 or other hardware components/circuits may be integrated into a single chip with any number of transmitters 430 and/or receivers 435. In this embodiment, the transmitter 430 and receiver may be logically configured as a transceiver 425 using one or more common control signals or as a modular transmitter 430 and receiver 435 implemented in the same hardware chip or multi-chip module.

[ FIG. 5-gNB receiving PHR ]

Fig. 5 depicts a base station apparatus 500 that may be used to report power headroom in accordance with an embodiment of the present disclosure. Base station apparatus 500 may be an embodiment of remote unit 105 or UE described above. Further, the base station apparatus 500 may include a processor 505, a memory 510, an input device 515, an output device 520, and a transceiver 525. In some embodiments, the input device 515 and the output device 520 are combined into a single device, such as a touch screen. In some embodiments, base station apparatus 500 may not include any input device 515 and/or output device 520. In various embodiments, base station apparatus 500 may include one or more of the following: processor 505, memory 510, and transceiver 525, and may not include input device 515 and/or output device 520.

In one embodiment, the processor 505 may comprise any known controller capable of executing computer readable instructions and/or capable of performing logical operations. For example, the processor 505 may be a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, or similar programmable controller. In some embodiments, the processor 505 executes instructions stored in the memory 510 to perform the methods and routines described herein. The processor 505 is communicatively coupled to a memory 510, an input device 515, an output device 520, and a receiver 525.

In various embodiments, base station apparatus 500 receives (e.g., via transceiver 525) a PHR from a served UE. Further, base station apparatus 500 may receive timing information regarding PHR described herein. Using the timing information, the processor 505 interprets the reported power headroom values.

In various embodiments, processor 505 identifies a number of uplink carriers for a serving cell of the UE. The processor 505 may interpret the reported power headroom value using the configuration of the uplink carrier, e.g., inferring a PHR type (e.g., type 1 or type 3) from the uplink carrier configuration and/or inferring an actual PHR or a virtual PHR from the uplink carrier configuration.

In one embodiment, memory 510 is a computer-readable storage medium. In some embodiments, memory 510 includes volatile computer storage media. For example, memory 510 may include RAM, including dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and/or static RAM ("SRAM"). In some embodiments, memory 510 includes non-volatile computer storage media. For example, memory 510 may include a hard drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 510 includes volatile and nonvolatile computer storage media.

In some embodiments, memory 510 stores data related to reporting power headroom. For example, the memory 510 may store PH timing information, UL carrier configuration, PHR value, and the like. In certain embodiments, memory 510 also stores program code and related data, such as an operating system or other controller algorithms operating on remote unit 102.

In one embodiment, input device 515 may include any known computer input device, including a touch panel, buttons, a keyboard, a stylus, a microphone, and the like. In some embodiments, input device 515 may be integrated with output device 520, e.g., as a touch screen or similar touch-sensitive display. In some embodiments, input device 515 includes a touch screen, such that text may be entered using a virtual keyboard displayed on the touch screen and/or by handwriting on the touch screen. In some embodiments, input device 515 includes two or more different devices, such as a keyboard and a touch panel.

In one embodiment, output device 520 is designed to output visual, audible, and/or tactile signals. In some embodiments, output device 520 comprises an electronically controllable display or display device capable of outputting visual data to a user. For example, output device 520 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or similar display device capable of outputting images, text, and the like to a user. As another non-limiting example, output device 520 may include a wearable display, such as a smart watch, smart glasses, heads-up display, or the like, separate from, but communicatively coupled to, base station apparatus 500. Further, output device 520 may be a component of a smart phone, personal digital assistant, television, desktop computer, notebook (laptop) computer, personal computer, vehicle dashboard, or the like.

In certain embodiments, output device 520 includes one or more speakers for producing sound. For example, the output device 520 may generate an audible alarm or notification (e.g., a beep or alert tone). In some embodiments, output device 520 includes one or more haptic devices for generating vibrations, motions, or other haptic feedback. In some embodiments, all or part of output device 520 may be integrated with input device 515. For example, input device 515 and output device 520 may form a touch screen or similar touch sensitive display. In other embodiments, the output device 520 may be located near the input device 515.

The transceiver 525 includes at least one transmitter 530 and at least one receiver 535. One or more transmitters 530 may be used to communicate with the UEs described herein. Likewise, one or more receivers 535 may be used to communicate with other network functions in the PLMN described herein. Although only one transmitter 530 and one receiver 535 are shown, the base station apparatus 500 may have any suitable number of transmitters 530 and receivers 535. Further, the transmitter 525 and receiver 530 may be any suitable type of transmitter and receiver.

[ AUL UE method 600]

Fig. 6 depicts one embodiment of a method 600 for reporting power headroom in accordance with an embodiment of the present disclosure. In various embodiments, the method 600 is performed by the remote unit 105 and/or the user equipment device 400 described above. In some embodiments, method 600 is performed by a processor, such as a microcontroller, microprocessor, Central Processing Unit (CPU), Graphics Processing Unit (GPU), auxiliary processing unit, FPGA, or the like.

The method 600 begins and a transmission opportunity for an AUL transmission on an unlicensed serving cell is identified 605. The method 600 includes generating 610 a PHR MAC CE. The method 600 includes transmitting 615 the PHR MAC CE to a RAN node in the mobile communication network using AUL transmission. Here, transmitting the PHR MAC CE includes: timing information corresponding to the PHR is indicated. The method 600 ends.

[ AUL + CA UE METHOD 700]

Fig. 7 depicts one embodiment of a method 700 for reporting power headroom in accordance with an embodiment of the present disclosure. In various embodiments, the method 700 is performed by a UE, such as the remote unit 105 and/or the user equipment device 400 described above. In some embodiments, method 700 is performed by a processor, such as a microcontroller, microprocessor, Central Processing Unit (CPU), Graphics Processing Unit (GPU), auxiliary processing unit, FPGA, or the like.

The method 700 begins and a first transmission opportunity for AUL transmission on an unlicensed serving cell is identified 705. The method 700 includes generating 710 a PHR MAC CE including power headroom information for each enabled serving cell configured with an uplink. Here, the power headroom information of the enabled serving cell is calculated for a predetermined PHR type in response to the serving cell being configured with two UL carriers. The method 700 includes transmitting 715 the PHR MAC CE to a RAN node in the mobile communication network in an AUL transmission. The method 700 ends.

[ CA UE method 800]

Fig. 8 depicts one embodiment of a method 800 for reporting power headroom in accordance with an embodiment of the present disclosure. In various embodiments, the method 800 is performed by a UE, such as the remote unit 105 and/or the user equipment device 400 described above. In some embodiments, method 800 is performed by a processor, such as a microcontroller, microprocessor, Central Processing Unit (CPU), Graphics Processing Unit (GPU), auxiliary processing unit, FPGA, or the like.

The method 800 begins and a first transmission opportunity on a configured uplink grant resource is identified 805. The method 800 includes generating 810 a PHR MAC CE including power headroom information for each enabled serving cell.

The method 800 includes transmitting 815 the PHR MAC CE to a RAN node in the mobile communication network. Here, the power headroom information is calculated for a predetermined PHR type in response to the configuration of two UL carrier serving cells. The method 800 ends.

[ claims to be made ]

[ AUL UE DEVICE ]

A first apparatus for reporting power headroom according to an embodiment of the present disclosure is disclosed herein. The first apparatus may be implemented by a UE, such as remote unit 105 and/or user equipment apparatus 400. The first apparatus includes a processor that identifies a transmission opportunity for an AUL transmission on an unlicensed serving cell and generates a PHR MAC CE. The first apparatus includes a transceiver to transmit a PHA MAC CE to a RAN node in a mobile communication network using AUL transmission, wherein transmitting the PHR MAC CE includes indicating timing information corresponding to a PHR.

In some embodiments, the timing information provides the RAN node with information about the first transmission attempt of the PHR MAC CE. In some embodiments, the timing information includes a 1-bit flag, wherein a first value of the 1-bit flag indicates that the PHR MAC CE transmission corresponds to a first transmission attempt and a second value of the 1-bit flag indicates that the PHR MAC CE transmission corresponds to a subsequent transmission attempt.

In some embodiments, the timing information includes an indication of a timing offset between the PHR MAC CE transmission and the first transmission attempt. In one embodiment, the timing offset indicates the number of time slots that have elapsed since the first transmission attempt. In another embodiment, the timing offset indicates the number of symbols that have passed since the first transmission attempt.

In some embodiments, the timing information includes an indication of a number of transmission attempts prior to the PHR transmission. In some embodiments, the timing information is transmitted as part of the uplink control information and is encoded separately from the PHR.

[ AUL UE method ]

A first method for reporting power headroom according to an embodiment of the present disclosure is disclosed herein. The first method may be performed by a UE, such as remote unit 105 and/or user equipment device 400. The first method includes identifying a transmission opportunity for an AUL transmission on an unlicensed serving cell. The first method includes generating a PHR MAC CE, and transmitting the PHR MAC CE to a RAN node in a mobile communication network using AUL transmission, wherein transmitting the PHR MAC CE includes indicating timing information corresponding to a PHR.

In some embodiments of the first method, the timing information provides the RAN node with information about a first transmission attempt of the PHR MAC CE. In some embodiments of the first method, the timing information comprises a 1-bit flag, wherein a first value of the 1-bit flag indicates that the PHR MAC CE transmission corresponds to a first transmission attempt and a second value of the 1-bit flag indicates that the PHR MAC CE transmission corresponds to a subsequent transmission attempt.

In some embodiments of the first method, the timing information comprises an indication of a timing offset between the PHR MAC CE transmission and the first transmission attempt. In one embodiment, the timing offset indicates the number of time slots that have elapsed since the first transmission attempt. In another embodiment, the timing offset indicates the number of symbols that have passed since the first transmission attempt.

In some embodiments of the first method, the timing information comprises an indication of a number of transmission attempts prior to the PHR transmission. In some embodiments of the first method, the timing information is transmitted as part of the uplink control information and is encoded separately from the PHR.

[ AUL + CA UE DEVICE ]

A second apparatus for reporting power headroom according to an embodiment of the present disclosure is disclosed herein. The second apparatus may be implemented by a UE, such as the remote unit 105 and/or the user equipment apparatus 400, configured for power headroom reporting in a mobile communication network for carrier aggregation using multiple serving cells. The second apparatus includes a processor that identifies a first transmission opportunity for an AUL transmission on an unlicensed serving cell. The processor generates a PHR MAC CE including power headroom information for each enabled serving cell configured with an uplink, wherein the power headroom information for the enabled serving cell is calculated for a predetermined PHR type in response to the serving cell being configured with two UL carriers. The second apparatus includes a transceiver that transmits the PHR MAC CE to a RAN node in the mobile communication network in an AUL transmission.

In some embodiments, the processor prioritizes transmission of the PHR MAC CE on the licensed cell over transmission of the PHR on the unlicensed serving cell.

[ AUL + CA UE method ]

A second method for reporting power headroom according to an embodiment of the present disclosure is disclosed herein. The second method may be performed by a UE, such as the remote unit 105 and/or the user equipment device 400, configured for power headroom reporting in a mobile communication network for carrier aggregation using multiple serving cells. The second method includes identifying a first transmission opportunity for AUL transmission on an unlicensed serving cell and generating a PHR MAC CE including power headroom information for each enabled serving cell configured with an uplink, wherein the power headroom information for the enabled serving cells is calculated for a predetermined PHR type in response to the serving cell being configured with two UL carriers. The second method comprises the following steps: the PHR MAC CE is transmitted to a RAN node in the mobile communication network in an AUL transmission.

In some embodiments, the second method further comprises prioritizing transmission of the PHR MAC CE on the licensed cell over transmission of the PHR on the unlicensed serving cell.

[ CA UE APPARATUS ]

A third apparatus for reporting power headroom according to an embodiment of the present disclosure is disclosed herein. The third apparatus may be implemented by a UE configured with carrier aggregation for power headroom reporting in a mobile communication network, such as the remote unit 105 and/or the user equipment apparatus 400. The third apparatus includes a processor that identifies a first transmission opportunity on a configured uplink grant resource and generates a PHR MAC CE that includes power headroom information for each enabled serving cell, wherein the power headroom information is calculated for a predetermined PHR type in response to the serving cell being configured with two UL carriers. The third apparatus includes a transceiver that transmits the PHR MAC CE in a configuration grant transmission to a RAN node in the mobile communication network.

In some embodiments, generating the PHR MAC CE comprises: reporting a virtual power headroom for each enabled serving cell in response to transmitting the PHR MAC CE on the configured uplink grant and further in response to the MAC entity of the apparatus being configured to lower prioritized uplink transmissions while supporting higher priority uplink transmissions. In these embodiments, preparing the PHR MAC CE includes: reporting the virtual PHR for a predefined PHR type in response to the serving cell being configured with two UL carriers.

In some embodiments, the apparatus is configured to use carrier aggregation of a plurality of enabled serving cells, wherein preparing the PHR MAC CE comprises: the actual PHR is reported for the serving cell on which the PHR MAC CE is to be transmitted, and the virtual PHR is reported for one or more other enabled serving cells.

[ CA UE method ]

A third method for reporting power headroom according to an embodiment of the present disclosure is disclosed herein. The third method may be performed by a UE configured with carrier aggregation for power headroom reporting in a mobile communication network, such as the remote unit 105 and/or the user equipment device 400. The third method includes identifying a first transmission opportunity on a configured uplink grant resource. The third method includes generating a PHR MAC CE including power headroom information for each enabled serving cell. Here, the power headroom information is calculated for a predetermined PHR type in response to the serving cell being configured with two UL carriers.

In some embodiments of the third method, generating the PHR MAC CE comprises: in response to transmitting the PHR MAC CE on the configured uplink grant and further in response to the MAC entity of the UE being configured to de-prioritize lower priority uplink transmissions while supporting higher priority uplink transmissions, reporting a virtual power headroom for each enabled serving cell. In these embodiments, preparing the PHR MAC CE includes: the virtual PHR is reported for a predefined PHR type in response to a serving cell configured with two UL carriers.

In some embodiments of the third method, the UE is configured to perform carrier aggregation using the plurality of enabled serving cells, wherein preparing the PHR MAC CE comprises: the actual PHR is reported for the serving cell on which the PHR MAC CE is to be transmitted, and the virtual PHR is reported for one or more other enabled serving cells.

Embodiments may be practiced in other specific forms. The above-described embodiments are to be considered in all respects as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Claims (20)

1. A method of a UE for power headroom reporting in a mobile communication network, the method comprising:

identifying a transmission opportunity for an autonomous uplink ("AUL") transmission on an unlicensed serving cell;

generating a power headroom report ("PHR") medium access control ("MAC") control element ("CE"); and

transmitting the PHR MAC CE to a radio access network ("RAN") node in the mobile communication network using AUL transmission,

wherein transmitting the PHR MAC CE comprises: indicating timing information corresponding to the PHR.

2. The method of claim 1, wherein the timing information provides the RAN node with information about a first transmission attempt of the PHR MAC CE.

3. The method of claim 1, wherein the timing information comprises a 1-bit flag, wherein a first value of the 1-bit flag indicates that the PHR MAC CE transmission corresponds to a first transmission attempt and a second value of the 1-bit flag indicates that the PHR MAC CE transmission corresponds to a subsequent transmission attempt.

4. The method of claim 1, wherein the timing information comprises an indication of a timing offset between the PHR MAC CE transmission and a first transmission attempt.

5. The method of claim 1, wherein the timing information is transmitted as part of uplink control information and is coded separately from the PHR.

6. A UE apparatus for power headroom reporting in a mobile communication network, the apparatus comprising:

a processor that:

identifying a transmission opportunity for an autonomous uplink ("AUL") transmission on an unlicensed serving cell, an

Generating a power headroom report ("PHR") medium access control ("MAC") control element ("CE"); and

a transceiver to transmit the PHR MAC CE to a radio access network ("RAN") node in the mobile communication network using AUL transmission,

wherein transmitting the PHR MAC CE comprises: indicating timing information corresponding to the PHR.

7. The apparatus of claim 6, wherein the timing information provides information to the RAN node regarding a first transmission attempt of the PHR MAC CE.

8. The apparatus of claim 6, wherein the timing information comprises a 1-bit flag, wherein a first value of the 1-bit flag indicates that the PHR MAC CE transmission corresponds to a first transmission attempt and a second value of the 1-bit flag indicates that the PHR MAC CE transmission corresponds to a subsequent transmission attempt.

9. The apparatus of claim 6, wherein the timing information comprises an indication of a timing offset between the PHR MAC CE transmission and a first transmission attempt.

10. The apparatus of claim 6, wherein the timing information is transmitted as part of uplink control information and is coded separately from the PHR.

11. A method for a UE configured for carrier aggregation using multiple serving cells for power headroom reporting in a mobile communication network, the method comprising:

identifying a transmission opportunity for an autonomous uplink ("AUL") transmission on an unlicensed serving cell;

generating a power headroom report ("PHR") medium access control ("MAC") control element ("CE"), the PHR MAC CE including power headroom information for each enabled serving cell configured with an uplink,

wherein power headroom information for an enabled serving cell is calculated for a predetermined PHR type in response to the serving cell being configured with two UL carriers; and

transmitting the PHR MAC CE to a radio access network ("RAN") node in the mobile communication network in an AUL transmission.

12. A UE apparatus configured for carrier aggregation using multiple serving cells for power headroom reporting in a mobile communication network, the apparatus comprising:

a processor that:

identifying a first transmission opportunity for an autonomous uplink ("AUL") transmission on an unlicensed serving cell, an

Generating a power headroom report ("PHR") medium access control ("MAC") control element ("CE"), the PHR MAC CE including power headroom information for each enabled serving cell configured with an uplink,

wherein power headroom information for an enabled serving cell is calculated for a predetermined PHR type in response to the serving cell being configured with two UL carriers; and

a transceiver to transmit the PHR MAC CE to a radio access network ("RAN") node in the mobile communication network in an AUL transmission.

13. A method of a UE configured with carrier aggregation for power headroom reporting in a mobile communication network, the method comprising:

identifying a first transmission opportunity on a configured uplink grant resource;

generating a power headroom report ("PHR") medium access control ("MAC") control element ("CE"), the PHR MAC CE including power headroom information for each enabled serving cell,

wherein the power headroom information is calculated for a predetermined PHR type in response to a serving cell being configured with two UL carriers; and

transmitting the PHR MAC CE to a radio access network ("RAN") node in the mobile communication network.

14. The method of claim 13, wherein generating the PHR MAC CE comprises: reporting a virtual power headroom for each enabled serving cell in response to transmitting the PHR MAC CE on a configured uplink grant and further in response to the MAC entity of the UE being configured to lower prioritized uplink transmissions while supporting higher priority uplink transmissions.

15. The method of claim 14, wherein preparing the PHR MAC CE comprises: the virtual PHR is reported for a predefined PHR type in response to the serving cell being configured with two UL carriers.

16. The method of claim 13, wherein the UE is configured for carrier aggregation using a plurality of enabled serving cells, wherein preparing the PHR MAC CE comprises: reporting an actual PHR for a serving cell on which the PHR MAC CE is to be transmitted and reporting a virtual PHR for one or more other enabled serving cells.

17. A UE apparatus configured with carrier aggregation for power headroom reporting in a mobile communication network, the apparatus comprising:

a processor that:

identifying a first transmission opportunity on a configured uplink grant resource; and

generating a power headroom report ("PHR") medium access control ("MAC") control element ("CE"), the PHR MAC CE including power headroom information for each enabled serving cell,

wherein the power headroom information is calculated for a predetermined PHR type in response to a serving cell being configured with two UL carriers; and

a transceiver to transmit the PHR MAC CE in a configuration authorization transmission to a radio access network ("RAN") node in the mobile communication network.

18. The apparatus of claim 17, wherein generating the PHR MAC CE comprises: reporting a virtual power headroom for each enabled serving cell in response to transmitting the PHR MAC CE on a configured uplink grant and further in response to a MAC entity of the apparatus being configured to lower prioritized uplink transmissions while supporting higher priority uplink transmissions.

19. The apparatus of claim 18, wherein preparing the PHR MAC CE comprises: reporting the virtual PHR for a predefined PHR type in response to the serving cell being configured with two UL carriers.

20. The apparatus of claim 17, wherein the apparatus is configured for carrier aggregation using a plurality of enabled serving cells, wherein preparing the PHR MAC CE comprises: reporting an actual PHR for a serving cell on which the PHR MAC CE is to be transmitted and reporting a virtual PHR for one or more other enabled serving cells.

Images