Reporting parameters for adjusting maximum output power for a given power class

Abstract

A power headroom report (PHR) includes reporting a parameter for adjustment to the maximum output power for a given power class. The parameter is determined by the user equipment (UE) based on an evaluation of the duty cycle and is reported when triggered by a duty cycle being exceeded in a new event or based on the expiration of a timer for a legacy event. The parameter may be ΔPPowerClass, which is reported and used to achieve high-power uplink transmission.

Description

[Technical Field]

[0001] This specification is generally directed to wireless communications. More specifically, there may be extensions to power headroom reporting (PHR) that include reporting of parameters for adjustments to maximum output power for a given power class. [Background technology]

[0002] Wireless communication technologies are moving the world toward an increasingly connected and networked society. Wireless communication relies on efficient network resource management and allocation between user mobile stations and wireless access network nodes (including, but not limited to, wireless base stations). New generation networks are expected to provide high-speed, low-latency, and ultra-reliable communication capabilities and meet requirements from different industries and users. User mobile stations or user equipment (UE) are becoming more complex, and the amount of data communicated is constantly increasing. Communication improvements should be made to improve communication and meet the reliability requirements of vertical industries as well as support new generation network services.

[0003] In wireless communications, a user equipment (UE) may have the capability to support one or more power classes different from a default UE power class for a band, where the supported power classes allow a maximum output power higher than that of the default power class. If the percentage of uplink symbols transmitted in a certain evaluation period (e.g., duty cycle) is greater than a threshold (e.g., maximum duty cycle), the UE may apply all requirements for the default power class to the supported power class. There are various issues / challenges associated with this implementation. For example, one issue / challenge may be that the evaluation period is one or more radio frames, but the base station may not know the exact evaluation period used by the UE or the duration of the applied default power class, which may lead to some ambiguity issues regarding uplink power control. Summary of the Invention [Means for solving the problem]

[0004] This document relates to methods, systems, and devices for wireless communications including power headroom reporting (PHR), where the PHR includes reporting of a parameter for adjustment to the maximum output power for a given power class. The parameter is determined by a user equipment (UE) based on an evaluation of the duty cycle, and the parameter is reported when triggered by the duty cycle being exceeded on a new event or based on the expiration of a timer for a legacy event. The parameter may be ΔPPowerClass, which is reported and used to achieve high-power uplink transmission.

[0005] In one embodiment, a method for wireless communication includes determining, by a device, parameters of an adjustment to a maximum output power for a given power class based on a comparison of duty cycles, and reporting the parameters when triggered by one or more events, the one or more events including a duty cycle being exceeded due to a first new event or expiration of a timer for a legacy event.

[0006] In one embodiment, a wireless communication device comprises a processor and a memory, the processor configured to read code from the memory and to implement any of the aforementioned embodiments.

[0007] In one embodiment, a computer program product includes a computer readable program medium having stored thereon code that, when executed by a processor, causes the processor to perform any of the previously described embodiments.

[0008] In some embodiments, a wireless communication device is provided that includes a processor and a memory, the processor configured to read code from the memory and perform any of the methods described in any of the embodiments. In some embodiments, a computer program product includes computer-readable program medium code stored thereon, the code, when executed by the processor, causing the processor to perform any of the methods described in any of the embodiments. These and other aspects and their implementations are described in more detail in the drawings, this specification, and the claims. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 shows an example of a base station.

[0010] [Figure 2] FIG. 2 illustrates an example of a random access (RA) messaging environment.

[0011] [Figure 3] FIG. 3 illustrates one embodiment of a wireless network system architecture.

[0012] [Figure 4A] FIG. 4a illustrates an example of a power headroom reporting (PHR) structure.

[0013] [Figure 4B] FIG. 4b illustrates another example of a PHR structure with parameters for adjustment to the maximum output power for a given power class.

[0014] [Figure 4C] FIG. 4c illustrates another example of a PHR structure with parameters for adjustment to the maximum output power for a given power class.

[0015] [Figure 5] FIG. 5 illustrates a timing example for the PC2 band.

[0016] [Figure 6] FIG. 6 illustrates a timing example for the PC1.5 band.

[0017] [Figure 7] FIG. 7 illustrates a timing example for another PC1.5 band.

[0018] [Figure 8] FIG. 8 illustrates example timing for bands where the duration of the PC fallback is not equal to the evaluation period. DETAILED DESCRIPTION OF THE INVENTION

[0019] The present disclosure will now be described in detail hereinafter with reference to the accompanying drawings, which form a part hereof, and which show, by way of illustration, specific examples of embodiments. It should be noted, however, that the present disclosure may be embodied in a variety of different forms, and therefore, the subject matter as directed or claimed should not be construed as limited to any of the embodiments set forth below.

[0020] Throughout this specification and the claims, terms may have subtly different meanings suggested or implied in context beyond their explicitly stated meaning. Similarly, the phrases "in one embodiment" or "in some embodiments" used herein do not necessarily refer to the same embodiment, and the phrases "in another embodiment" or "in other embodiments" used herein do not necessarily refer to different embodiments. The phrases "in one implementation" or "in some implementations" used herein do not necessarily refer to the same implementation, and the phrases "in another implementation" or "in other implementations" used herein do not necessarily refer to different implementations. For example, the claimed subject matter is intended to include combinations of example embodiments or implementations, in whole or in part.

[0021] Generally, terminology can be understood, at least in part, from its usage in context. For example, terms such as "and," "or," and "and / or," as used herein, can include a variety of meanings that may depend, at least in part, on the context in which such terms are used. Typically, "or," when used to relate a list such as A, B, or C, is intended to refer not only to A, B, and C, which are used herein in an inclusive sense, but also to A, B, or C, which are used herein in an exclusive sense. Furthermore, as used herein, the terms "one or more" or "at least one" can be used to describe any feature, structure, or characteristic in a singular sense, or can be used to describe a combination of features, structures, or characteristics in a plural sense, depending, at least in part, on the context. Similarly, terms such as "a," "an," "the," and the like can also be understood to convey a singular usage or a plural usage, depending, at least in part, on the context. Furthermore, the terms "based on" or "determined by" may be understood as not necessarily intended to convey an exclusive set of factors, but instead may allow for the existence of additional factors not necessarily explicitly described, again depending at least in part on the context.

[0022] New generation (NG) mobile communication systems are moving the world towards an increasingly connected and networked society. High-speed and low-latency wireless communications rely on efficient network resource management and allocation between user equipment and wireless access network nodes (including, but not limited to, wireless base stations). New generation networks are expected to provide high-speed, low-latency, and ultra-reliable communication capabilities and meet requirements from different industries and users.

[0023] Radio Resource Control ("RRC") is a protocol layer between a UE and a base station at the Internet Protocol (IP) level (network layer). Various Radio Resource Control (RRC) states are possible, such as RRC_CONNECTED, RRC_INACTIVE, and RRC_IDLE. RRC messages are carried via the Packet Data Convergence Protocol ("PDCP"). As described, a UE can transmit data via a random access channel ("RACH") protocol or a configuration grant ("CG") scheme. CG can be used to reduce waste of periodically allocated resources by allowing multiple devices to share the periodic resources. A base station or node can allocate CG resources to eliminate packet transmission delays and increase utilization of allocated periodic radio resources. The CG scheme is only one example of a protocol scheme for communication; other examples, including but not limited to RACH, are possible. Wireless communication described herein may be via radio access.

[0024] Improvements in wireless or mobile communication technologies bring about increased demand. Based on current development trends, systems are developing support for enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC) features. Full duplex may be a requirement for 5G and subsequent communication systems. In wireless communications, network devices such as user equipment (UE) may perform uplink (UL) transmitter (Tx) switching between bands. For multi-carrier operation, a network device transmitting with two transmitters (also called a 2Tx user device) may transmit in two UL bands. Which two bands are used may be changed by radio resource control (RRC) reconfiguration.

[0025] In a wireless communication system, a user equipment (UE) may have the capability to support one or more power classes different from the default UE power class of a band, where the supported power classes allow a higher maximum output power than the default power class. If the percentage of uplink symbols transmitted in a certain evaluation period (e.g., duty cycle) is greater than a threshold (e.g., maximum duty cycle), the UE may apply all requirements for the default power class to the supported power class. There are various problems / challenges associated with this implementation. For example, one problem / challenge may be that, although the evaluation period is one or more radio frames, the base station (or wireless communication node) does not know the exact evaluation period used by the UE or the duration of the applied default power class, which may lead to some ambiguity issues regarding uplink power control. Another problem / challenge may include uncertainty about how to calculate the percentage of uplink symbols transmitted in a certain evaluation period when non-overlapping sub-band full duplex is applied, in which uplink sub-bands are introduced into the downlink or flexible symbols. The present disclosure describes various embodiments for reporting parameters for adjustment to maximum output power for a given power class, which addresses at least one of the problems / issues discussed in the present disclosure.

[0026] 1 illustrates an exemplary base station 102. A base station may also be referred to as a network device or a wireless network node. In a mobile communications context, the base station 102 may be further distinguished as a Node B (NB, e.g., eNB or gNB). The exemplary base station may include wireless Tx / Rx circuitry 113 for receiving and transmitting to and from a user equipment (UE) 104. The base station may include network interface circuitry 116, e.g., optical or wired interconnects, Ethernet, and / or other data transmission media / protocols, for coupling the base station to a core network 110.

[0027] The base station may also include system circuitry 122. The system circuitry 122 may include one or more processors 124 and / or memory 126. The memory 126 may include operations 128 and control parameters 130. The operations 128 may include instructions for execution on one or more of the processors 124 to support the functionality of the base station. For example, the operations may process random access transmission requests from multiple UEs. The control parameters 130 may include parameters or support the execution of the operations 128. For example, the control parameters may include network protocol settings, random access messaging formatting rules, bandwidth parameters, radio frequency mapping assignments, and / or other parameters.

[0028] Furthermore, signals communicated between communication nodes in the system 100 may be characterized or defined as data signals or control signals. Generally, data signals are signals that contain (or carry) data, such as multimedia data (e.g., voice and / or image data), and control signals are signals that carry control information that configure communication nodes in a certain way to communicate with each other or that control how communication nodes communicate data signals with each other. Certain signals may also be defined or characterized by a combination of data / control and uplink / downlink / sidelink, including uplink control signals, uplink data signals, downlink control signals, downlink data signals, sidelink control signals, and sidelink data signals. Particular signals may also be characterized or defined as either uplink (UL) signals, downlink (DL) signals, or sidelink (SL) signals. Uplink signals are signals transmitted from a UE 104 to a base station 102. Downlink signals are signals transmitted from a base station 102 to a UE 104. Sidelink signals are signals transmitted from one UE 104 to another UE 104.

[0029] For at least some specifications, such as 5G New Radio (NR), data and control signals are transmitted and / or carried on physical channels. Generally, a physical channel corresponds to a set of time-frequency resources used for the transmission of signals. Different types of physical channels may be used to transmit different types of signals. For example, a physical data channel (or simply a data channel), also referred to herein as a traffic channel, is used to transmit data signals, and a physical control channel (or simply a control channel) is used to transmit control signals. Examples of types of traffic channels (or physical data channels) include, but are not limited to, a physical downlink shared channel (PDSCH) used to communicate downlink data signals, a physical uplink shared channel (PUSCH) used to communicate uplink data signals, and a physical sidelink shared channel (PSSCH) used to communicate sidelink data signals. In addition, examples of types of physical control channels include, but are not limited to, a physical downlink control channel (PDCCH) used to communicate downlink control signals, a physical uplink control channel (PUCCH) used to communicate uplink control signals, and a physical sidelink control channel (PSCCH) used to communicate sidelink control signals. As used herein for simplicity, unless otherwise specified, a physical channel of a particular type is also used to refer to a signal transmitted on that physical channel of that particular type and / or a transmission on that transmission of that particular type. By way of example, a PDSCH refers to the physical downlink shared channel itself, a downlink data signal transmitted on the PDSCH, or a downlink data transmission. Thus, a communication node transmitting or receiving a PDSCH means that the communication node is transmitting or receiving a signal on the PDSCH.

[0030] Additionally, for at least some specifications, such as 5GNR, and / or for at least some types of control signals, control signals transmitted by communication nodes may include control information containing information necessary to enable transmission of one or more data signals between communication nodes and / or to schedule one or more data channels (or one or more transmissions on a data channel). For example, such control information may include information necessary for proper reception, decoding, and demodulation of data signals received on a physical data channel during a data transmission, and / or for uplink scheduling grants that inform user devices about resources and transport formats to use for uplink data transmissions. In some embodiments, the control information includes downlink control information (DCI) transmitted in the downlink direction from the base station 102 to the UE 104. In other embodiments, the control information includes uplink control information (UCI) transmitted in the uplink direction from the UE 104 to the base station 102, or sidelink control information (SCI) transmitted in the sidelink direction from one UE 104 to another UE 104.

[0031] Additionally, in some embodiments, the UE 104 may be configured to support at least one simultaneous UL transmission mode across a band pair for UL transmission. In a first simultaneous UL transmission mode (also referred to as a switched UL mode), the UE 104 does not support simultaneous UL transmission across a band pair. Thus, when the UE 104 transmits a UL transmission in the first simultaneous UL transmission mode, the UE 104 transmits the UL transmission without simultaneously transmitting across the band pair. Additionally, in a second simultaneous UL transmission mode (also referred to as a dual UL mode), the UE 104 supports simultaneous UL transmission across the band pair. Thus, when the UE 104 transmits a UL transmission in the second simultaneous UL transmission mode, the UE 104 may transmit the UL transmission by simultaneously transmitting across the band pair.

[0032] In some embodiments, the UE 104 may report a simultaneous UL transmission mode to the base station 102. That is, the UE 104 may report to the base station 102 that the UE supports simultaneous UL transmission over a band pair, that the UE does not support simultaneous UL transmission over a band pair, or that the UE both supports and does not support simultaneous UL transmission over a band pair. In certain of these embodiments, the UE 104 may report whether or not it supports simultaneous UL transmission over a band pair (BC) for each band combination. Furthermore, the base station 102 may configure a simultaneous UL transmission mode (e.g., switchedUL or dualUL) per cell group, which may be considered per BC or per band pair in embodiments where a 2-Tx user device supports only two bands. That is, one available band pair in a band combination may support one simultaneous UL transmission mode.

[0033] Additionally, generally, as used herein, a band combination may include multiple bands (e.g., five bands). Additionally, as used herein, a band group may include up to three or four bands. A given band group may be included in or may be part of a band combination. A band combination and / or band group may include at least one band pair, where a band pair includes two bands.

[0034] 2 illustrates an exemplary random access messaging environment 200. In the random access messaging environment, a UE 104 may communicate with a base station 102 via a random access channel 252. In this example, the UE 104 supports one or more subscriber identity modules (SIMs), such as SIM1 202. An electrical and physical interface 206 connects SIM1 202 to the rest of the user equipment hardware, for example, via a system bus 210.

[0035] The mobile device 200 includes a communications interface 212, system logic 214, and a user interface 218. The system logic 214 may include any combination of hardware, software, firmware, or other logic. The system logic 214 may be implemented using, for example, one or more systems on a chip (SoC), application-specific integrated circuits (ASICs), discrete analog and digital circuits, and other circuits. The system logic 214 is part of the implementation of any desired functionality in the UE 104. In this regard, the system logic 214 may include, by way of example, logic to facilitate music and video decoding and playback, e.g., MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playback; application execution; acceptance of user input; storage and retrieval of application data; establishment, maintenance, and termination of data connections, such as for cellular telephone calls or Internet connections; establishment, maintenance, and termination of wireless network connections, Bluetooth® connections, or other connections; and display of related information on the user interface 218. The user interface 218 and input 228 may include a graphical user interface, a touch-sensitive display, haptic feedback or other tactile output, voice or facial recognition input, buttons, switches, speakers, and other user interface elements. Further examples of input 228 include microphones, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headset and microphone input / output jacks, universal serial bus (USB) connectors, memory card slots, radiation sensors (such as IR sensors), and other types of input.

[0036] The system logic 214 may include one or more processors 216 and a memory 220. The memory 220 stores, for example, control instructions 222 that the processor 216 executes to perform desired functions of the UE 104. Control parameters 224 provide and specify configuration and operation options for the control instructions 222. The memory 220 may also store BT, WiFi, 3G, 4G, 5G, or other data 226 that the UE 104 transmits or receives via the communication interface 212. In various implementations, system power may be provided by a power storage device, such as a battery 282.

[0037] In the communications interface 212, radio frequency (RF) transmit (Tx) and receive (Rx) circuitry 230 handles the transmission and reception of signals via one or more antennas 232. The communications interface 212 may include one or more transceivers. A transceiver may be a wireless transceiver that includes modulation / demodulation circuitry, digital-to-analog converters (DACs), shaping tables, analog-to-digital converters (ADCs), filters, waveform shapers, filters, preamplifiers, power amplifiers, and / or other logic for transmitting and receiving via one or more antennas or (in the case of some devices) over a physical (e.g., wired) medium.

[0038] The transmitted and received signals may conform to any of a wide variety of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), frequency channels, bit rates, and coding. As one specific example, communication interface 212 may include a transceiver supporting transmission and reception in 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS), High-Speed ​​Packet Access (HSPA)+, and 4G / Long Term Evolution (LTE) standards. However, the techniques described below are also applicable to other wireless communication technologies, whether they originate from the 3rd Generation Partnership Project (3GPP), GSM Association, 3GPP2, IEEE, or other partnerships or standards bodies.

[0039] Multiple RAN nodes (eNBs, gNBs, etc.) of the same or different radio access technologies ("RATs") can be deployed in a particular geographic area on the same or different frequency carriers, and these RAN nodes can cooperate with each other through dual connectivity operation to provide joint communication services for the same (one or more) target UEs. A multi-RAT dual connectivity ("MR-DC") architecture may have a non-co-located master node ("MN") and secondary node (SN). The access mobility management function ("AMF") and session management function ("SMF") may be control plane entities, and the user plane function ("UPF") is the user plane entity in New Radio ("NR") or 5GC.

[0040] Figure 3 illustrates one embodiment of a wireless network system architecture. This architecture is merely an example, and there may be more or fewer components for implementing the embodiments described herein. Interconnections or communications between components are identified as N1, N2, N4, N6, N7, N8, N10, and N11, which may be referenced herein or in other figures. Figure 2 illustrates an exemplary user equipment ("UE") 104. The UE 302 is a device that accesses a wireless network (e.g., 5GS) and obtains service through an NG-RAN node or base station 304. The UE 302 interacts with the core network's Access and Mobility Control Function ("AMF") 306 via NAS signaling. Figure 1 illustrates an exemplary base station, i.e., NG-RAN 102. The base station 304, which may also be referred to as a Next Generation Radio Access Network ("NG-RAN") node, may provide time synchronization signals to the user equipment (UE). There may be an AI model or processing method that is part of the UE 302, and information may be provided by the UE to the components shown in FIG. 3 as described in the following embodiments.

[0041] The AMF 306 includes the following functions: registration management, connection management, reachability management, and mobility management. The AMF 306 also performs access authentication and access authorization. The AMF 306 is the NAS security termination and relays session management NAS between the UE 302 and the SMF 308, etc. The SMF 308 includes the following functions: session management (e.g., session establishment, modification, and release), UE IP address allocation and management (including optional authorization), uplink function selection and control, downlink data notification, etc. The User Plane Function ("UPF") 310 includes the following functions: anchor point for intra-RAT / inter-RAT mobility, packet routing and forwarding, traffic usage reporting, QoS processing for the user plane, downlink packet buffering and downlink data notification triggering, etc. The Unified Data Management ("UDM") 312 manages subscription profiles for the UE. Subscriptions include data used for mobility management (e.g., restricted areas), session management (e.g., QoS profiles), etc. The subscription data also includes slice selection parameters used by the AMF 306 to select the appropriate SMF 308. The AMF 306 and SMF 308 obtain subscriptions from the UDM 312. The subscription data may be stored in a unified data repository with the UDM 312, and the UDM 312 uses such data when it receives a request from the AMF 306 or SMF 308. The Policy Control Function (“PCF”) 314 includes the following functions: supporting a unified policy framework for managing network behavior, providing policy rules for control plane functions to enforce the policy rules, and implementing a front end for accessing subscription information associated with policy decisions in the user data repository. The Network Exposure Function (“NEF”) 316 is optionally deployed to exchange information with external third parties. In one embodiment, the Application Function (“AF”) 316 can store application information in the unified data repository via the NEF.The UPF 310 is in communication with a data network 318 .

[0042] The embodiments described below may include the UE determining parameters for adjustment to the maximum output power for a given power class based on an evaluation cycle and then reporting the parameters to the network / base station. The given power class (PC) may also be referred to as a declared power class (PC) or a supported power class (PC), and these terms may be used interchangeably. This may be in the context of the network / wireless communication environment shown in Figures 1-3. This reporting may be triggered by a duty cycle being exceeded with a new event or based on the expiration of a timer for a legacy event. The parameters may include ΔPPowerClass, which is reported and used to achieve high-power uplink transmission.

[0043] (Power Headroom Report) In some embodiments of a wireless communications system, for a single uplink (UL) carrier, a UE may be enabled to set its configured maximum output power PCMAX,f,c for carrier f of serving cell c. The configured maximum output power PCMAX,f,c may be set within the following bounds: PCMAX_L,f,c≦PCMAX,f,c≦PCMAX_H,f,c, where PCMAX_L,f,c and PCMAX_H,f,c depend on PPowerClass, and PPowerClass,c is the linear value of the maximum UE power for serving cell c without considering a tolerance, or ue-PowerClass.

[0044] In some embodiments of a wireless communication system, for uplink (UL) carrier aggregation (CA), a UE may be enabled to set the sum of the configured maximum output power P CMAX,c for a serving cell c and the configured maximum output power P CMAX. The configured total maximum output power P CMAX may be set within the following bound: P CMAX_L≦P CMAX ≦P CMAX_H, where P CMAX_L and P CMAX_H depend on the P PowerClass of the CA. The maximum power class (PC) of P PowerClass, CA may be PC2, and the power usable in UL CA is limited by P PowerClass, CA. In some cases, P PowerClass, CA is replaced by 10log10Σp PowerClass,c, which is also named the aggregate power of UL CA, and P PowerClass,c is the linear value of the maximum UE power for serving cell c without considering the tolerance, or ue-PowerClass.

[0045] In some embodiments, the power headroom (PHR) calculation may be performed as follows:

number

[0046] where:

number

number

number

number

number

[0047] where:

number

number

number

[0048]

number

number

[0049] where:

number

[0050] K S Regarding =1.25

number

number

[0051] A Power Headroom Report (PHR) may be triggered if any of the following legacy events occur: When the phr-ProhibitTimer has expired or is expiring and the MAC entity has UL resources for a new transmission, the path loss for at least one RS used as a path loss criterion for one activated serving cell of any MAC entity that is not a dormant BWP has changed by more than phr-Tx-PowerFactorChange dB since the last transmission of a PHR at this MAC entity; ● phr-PeriodicTimer expires; ● When configuring or reconfiguring the power headroom reporting function by a higher layer that is not being used to disable the function; ● Activation of an SCell of any MAC entity with a configured uplink whose firstActiveDownlinkBWP-Id is not set to dormant BWP; Activation of the SCG; and Addition of a PSCell (i.e., a PSCell is newly added or changed) except when the SCG is deactivated. (UE maximum output power)

[0052] In some systems, the UE may support a power class different from the band's default UE power class, where the supported power class allows a higher maximum output power than the default power class. In one embodiment, the supported power class requirement may be applied, and in one embodiment, a configured transmit power may be set so that the UE is enabled to set its configured maximum output power PCMAX,f,c for carrier f of serving cell c in each slot. The configured maximum output power PCMAX,f,c may be set within the following bounds: P CMAX_L,f,c ≦P CMAX,f,c ≦P CMAX_H,f,c , where: P CMAX_L,f,c =MIN{P EMAX,c -ΔT C,c ,(P PowerClass -ΔP PowerClass )-MAX(MAX(MPR c ,A-MPR c )+ΔT IB,c +ΔT C,c +ΔT RxSRS ,P-MPR c )} P CMAX_H,f,c =MIN{P EMAX,c ,P PowerClass -ΔP PowerClass}

[0053] In some embodiments, the parameter ΔP PowerClass can be set as follows: ● If a P-max of 3dB for a power class 2 capable UE or 6dB for a power class 1.5 UE is indicated: 23dBm or less; or if the UE capability maxUplinkDutyCycle-PC2-FR1 field is not present and the UE capability maxUplinkDutyCycle-PC1dot5-MPE-FR1 field is not present and the percentage of uplink symbols transmitted in an evaluation period is greater than 50%; or if the UE capability maxUplinkDutyCycle-PC2-FR1 field is not present and the percentage of uplink symbols transmitted in an evaluation period is greater than maxUplinkDutyCycle-PC2-FR1, or if the UE capability maxUplinkDutyCycle-PC1dot5-MPE-FR1 field is not present and half of the percentage of uplink symbols transmitted in an evaluation period is greater than maxUplinkDutyCycle-PC1dot5-MPE-FR1. The exact evaluation period may be one radio frame or more. 3dB for Power Class 1.5 capable UE when: If a P-max between 23 dBm and 26 dB is indicated; or if the UE capability maxUplinkDutyCycle-PC2-FR1 field is not present, the UE capability maxUplinkDutyCycle-PC1dot5-MPE-FR1 field is not present, and the percentage of uplink symbols transmitted in an evaluation period is between 25% and 50%; or if the UE capability maxUplinkDutyCycle-PC2-FR1 field is not present and the percentage of uplink symbols transmitted in an evaluation period is between maxUplinkDutyCycle-PC2-FR1 and maxUplinkDutyCycle-PC2-FR1 / 2, or if the UE capability maxUplinkDutyCycle-PC1dot5-MPE-FR1 field is not present and the percentage of uplink symbols transmitted in an evaluation period is greater than maxUplinkDutyCycle-PC1dot5-MPE-FR1. The exact evaluation period may be one radio frame or more. ● 3 dB if: the UE is configured in an SUL configuration and the default power class requirements apply to bands for which the UE indicates power class 2. ● If a PC2-enabled UE or PC1.5-enabled UE with txDiversity-r16 capability further indicates SRS-TxSwitch capability "t1r2" or "t1r4" or "t1r1-t1r2" or "t1r1-t1r2-t1r4", then 3 dB applies during SRS transmission opportunities where the usage in the SRS-ResourceSet is configured as "antennaSwitching" with the configured SRS resources in each SRS resource set consisting of one SRS port; or ● Otherwise, 0dB.

[0054] In some embodiments, if the UE can support a power class different from the default UE power class for the band and the supported power class allows a higher maximum output power than the default power class, the following may be implemented: If the UE capability maxUplinkDutyCycle-PC2-FR1 field is not present and the UE capability maxUplinkDutyCycle-PC1dot5-MPE-FR1 field is not present and the percentage of uplink symbols transmitted in a certain evaluation period is greater than 50% (the exact evaluation period is greater than or equal to one radio frame); or If the UE capability maxUplinkDutyCycle-PC2-FR1 field is not present and the percentage of uplink symbols transmitted in a given evaluation period is greater than maxUplinkDutyCycle-PC2-FR1; or If the UE capability maxUplinkDutyCycle-PC1dot5-MPE-FR1 field is not present and half of the percentage of uplink symbols transmitted in a certain evaluation period is greater than maxUplinkDutyCycle-PC1dot5-MPE-FR1; or If IE P-Max is provided and set to the maximum output power below the default power class.

[0055] In one embodiment, all requirements of the default power class may apply to the supported power class, and the configured transmit power is set accordingly. This may occur if the UE does not support a power class with a higher maximum output power than PC2. In some embodiments, if the UE can support a power class different from the default UE power class for the band, and the supported power class allows a higher maximum output power than the default power class, the following may be implemented: If the UE capability maxUplinkDutyCycle-PC2-FR1 field is not present and the UE capability maxUplinkDutyCycle-PC1dot5-MPE-FR1 field is not present and the percentage of uplink symbols transmitted in an evaluation period is greater than 25%; or ● If the UE capability maxUplinkDutyCycle-PC2-FR1 field is not present and the percentage of uplink symbols transmitted in a certain evaluation period is greater than 0.5*maxUplinkDutyCycle-PC2-FR1; If the UE capability maxUplinkDutyCycle-PC1dot5-MPE-FR1 is not present and the percentage of uplink symbols transmitted in a given evaluation period is greater than maxUplinkDutyCycle-PC1dot5-MPE-FR1; or If IE P-Max is provided and set to the maximum output power of power class 2 or less; or ● All requirements for Power Class 2 may apply to the supported power classes and the configured transmit power is set. (Parameter reporting in PHR)

[0056] A power headroom report (PHR) includes reporting a parameter for adjustment to the maximum output power for a given power class. This parameter may be referred to as ΔPPowerClass, which is reported and used to achieve high-power uplink transmission. The parameter is determined by the user equipment (UE) based on an evaluation of the duty cycle and reported to the network / base station when triggered by the duty cycle being exceeded by a new event or based on the expiration of a timer for a legacy event. The following embodiments include examples of parameter determination and reporting, including event triggers.

[0057] Figure 4a illustrates one example of a power headroom reporting (PHR) structure. Figure 4b illustrates another example of a PHR structure with parameters for adjustment to the maximum output power for a given power class. For power headroom reporting, there may be several PHR MAC Control Elements (CEs), including: a single-entry PHR MAC CE, a multi-entry PHR MAC CE, an enhanced single-entry PHR MAC CE, an enhanced single-entry PHR for an enhanced multi-entry PHR MAC CE, or an enhanced multi-entry PHR for a multi-TRP MAC CE. Using a single-entry PHR MAC CE as an example, for the 2-bit MPE field, it may be used for FR2 and reserved for FR1, but can be reused for FR1. R is a reserved bit, and MPE is reserved for FR1. ΔPPowerClass may apply for FR1. Since two bits may be required for the UE to report ΔPPowerClass, the MPE field for FR2 may be reused to report ΔPPowerClass for FR1. Figure 4b illustrates that this field has been replaced with a parameter for adjustment to the maximum output power for a given power class, referred to as ΔPPowerClass. Figure 4c illustrates another example of a PHR structure with a parameter for adjustment to the maximum output power for a given power class, which uses some or all bits in a separate octet to report ΔPPowerClass. For example, compared to Figure 4a, the third octet is used, and X bits are used to report ΔPPowerClass, where X can be 1, 2, 3, 4, 5, 6, 7, or 8.

[0058] If mpe-Reporting-FR2 is configured and the serving cell (SC) operates in FR2, this field may indicate the applied power backoff to meet MPE requirements if the P field is set to 1. The field is 2 bits in length. If mpe-Reporting-FR2 is not configured, or the SC operates in FR1, or the P field is set to 0, the R bit may be present instead.

[0059] With enhanced information exchange / communication between the UE and the base station, scheduling and network performance can be improved when using higher power. Thus, providing improved communication and providing reporting on power usage, specifically enabling the UE to report on ΔPPowerClass, can indicate which power class requirement the UE is referring to when the configured duty cycle is exceeded. In some embodiments, reporting can be limited to when the configured duty cycle is exceeded, which can be referred to as an event. There can be different triggering events, as described herein.

[0060] In addition to the configured duty cycle, there may be a default duty cycle case. For example, if the UECapabilitymaxUplinkDutyCycle-PC2-FR1 field is not present, the UECapabilitymaxUplinkDutyCycle-PC1dot5-MPE-FR1 field is not present, and the percentage of uplink symbols transmitted in an evaluation period is greater than 50%, ΔPPowerClass is 3 dB for a power class 2-capable UE or 6 dB for a power class 1.5 UE. If the default duty cycle is exceeded, ΔPPowerClass may be reported. For example, if the UECapabilitymaxUplinkDutyCycle-PC2-FR1 field is not present, the UECapabilitymaxUplinkDutyCycle-PC1dot5-MPE-FR1 field is not present, and the percentage of uplink symbols transmitted in an evaluation period is greater than 50%, ΔPPowerClass may be reported because the power class requirement to which the UE is referring is reduced, which is similar to the configured duty cycle case.

[0061] In other embodiments, the default / configured duty cycle may be partially exceeded. For example, if the UE capability maxUplinkDutyCycle-PC2-FR1 field is not present, the UE capability maxUplinkDutyCycle-PC1dot5-MPE-FR1 field is not present, and the percentage of uplink symbols transmitted in a certain evaluation period is between 25% and 50%, or if the UE capability maxUplinkDutyCycle-PC2-FR1 field is not present, and the percentage of uplink symbols transmitted in a certain evaluation period is between maxUplinkDutyCycle-PC2-FR1 and maxUplinkDutyCycle-PC2-FR1 / 2, the parameter ΔPPowerClass is 3 dB for a power class 1.5 UE. ΔPPowerClass may be reported if the default / configured duty cycle is partially exceeded. Partially exceeded may include, in one example, 25-50%, but may also include other percentages less than 25 and greater than 50%. For example, if the UE capability maxUplinkDutyCycle-PC2-FR1 field is not present and the UE capability maxUplinkDutyCycle-PC1dot5-MPE-FR1 field is not present and the percentage of uplink symbols transmitted in an evaluation period is between 25% and 50%, then the parameter ΔPPowerClass may be reported as the power class requirement to which the UE is referring is reduced, which is similar to the above example when the duty cycle is completely exceeded.

[0062] In other embodiments, the configured duty cycle may be exceeded by half the percentage of uplink symbols transmitted in a certain evaluation period. For example, if the UE capability maxUplinkDutyCycle-PC1dot5-MPE-FR1 field is not present and half the percentage of uplink symbols transmitted in a certain evaluation period is greater than maxUplinkDutyCycle-PC1dot5-MPE-FR1, then the parameter ΔPPowerClass is 6 dB for a power class 1.5 UE. ΔPPowerClass may be reported if the default / configured duty cycle is exceeded by half the percentage of uplink symbols transmitted in a certain evaluation period. For example, if the UE capability maxUplinkDutyCycle-PC1dot5-MPE-FR1 field is not present and half of the percentage of uplink symbols transmitted in a certain evaluation period is greater than maxUplinkDutyCycle-PC1dot5-MPE-FR1, then the parameter ΔPPowerClass may be reported since the power class requirement to which the UE is referring is reduced. This may be similar to the above example where the duty cycle is exceeded entirely or by the percentage of uplink symbols transmitted in a certain evaluation period.

[0063] Embodiments may enable the UE to properly report on the parameter ΔPPowerClass to indicate which power class requirement the UE is referring to, not only when the configured duty cycle is exceeded, but also when the default duty cycle is exceeded or when the default / configured duty cycle is partially exceeded. At the very least, the reduced power class can be known for both the network / base station and the UE. This may enable better utilization of the UE's maximum power and improve network / base station scheduling decisions.

[0064] Transmission of parameters for adjustments to the maximum output power for a given power class can be used to improve scheduling and network performance when using higher power. This reporting of ΔPPowerClass by the UE can indicate which power class requirement the UE is referring to when the default / configured duty cycle is partially / fully exceeded. Reporting can be limited to when the configured duty cycle is exceeded. Since the enhanced PHR includes an indication of ΔPPowerClass, embodiments for how to report ΔPPowerClass in the PHR are described herein. In some examples, the reported value of ΔPPowerClass is a cumulative value or an absolute value. Furthermore, the reported value of ΔPPowerClass can be different when triggered by a legacy event.

[0065] A PHR with an actual value for ΔPPowerClass can only be triggered by a new event. Otherwise, there can be a default value of 0 dB for ΔPPowerClass. A new event can include when a configured duty cycle is exceeded. If the PHR is triggered by a legacy event, it can contain a value of 0 dB for ΔPPowerClass. The actual value for ΔPPowerClass can be an absolute value or a cumulative value. The potential indications for ΔPPowerClass can be shown in Table 1, which shows a 2-bit indication, or Tables 2 or 3, which show a 1-bit indication. [Table 1] [Table 2] [Table 3]

[0066] FIG. 5 illustrates a timing example for the PC2 band. In this example, ΔPPowerClass = 3 dB is reported at t0 - t1 in FIG. 5, and otherwise, 0 dB is reported. The duration of the power class fallback is equal to the evaluation period. If the duty cycle is exceeded in the first evaluation period, a new event triggers ΔPPowerClass = 3 dB in the PHR at t0. As a result, PC3 can be assumed in the second evaluation period. During t0 < t < t1, ΔPPowerClass = 0 dB in the PHR is triggered if triggered by a legacy event. After the duration of the power class fallback, if the PHR is triggered by a legacy event or another new event that returns to the declared PC2, ΔPPowerClass = 0 dB in the PHR. If the duty cycle is not exceeded after the evaluation period, ΔPPowerClass = 0 dB in the PHR when triggered by a legacy event. The summary of the detailed reported values is listed in Table 4. [Table 4]

[0067] Figure 6 illustrates a timing example for the PC1.5 band. This includes the duration of the PC fallback compared to the evaluation period. In this example, ΔPPowerClass = 6 dB at t0 - t1, and otherwise, 0 dB is reported. PC1.5 can have potential values of 0, 3, or 6 dB. As shown, the duration of the power class fallback is equal to the evaluation period. If the duty cycle is exceeded by half of the percentage of uplink symbols transmitted in a certain evaluation period during the first evaluation period, a new event triggers ΔPPowerClass = 6 B in the PHR at t0. As a result, PC3 can be assumed in the second evaluation period. During t0 < t < t1, ΔPPowerClass = 0 dB in the PHR is triggered if it is triggered by a legacy event. After the duration of the power class fallback, if the PHR is triggered by a legacy event or another new event that returns to the declared PC1.5, ΔPPowerClass = 0 dB in the PHR. After the duration of the power class fallback, if the PHR is triggered by a legacy event or another new event that returns to the declared PC2, and the percentage of uplink symbols transmitted in a certain evaluation period is greater than the duty cycle, ΔPPowerClass = 3 dB in the PHR. If the duty cycle is not exceeded after the evaluation period when triggered by a legacy event, ΔPPowerClass = 0 dB in the PHR. An overview of the detailed reported values is listed in Table 5.

Table 5

[0068] Figure 7 illustrates a timing example for another PC1.5 band. In this example, in the first evaluation period, since the duty cycle is exceeded, 3 dB is set. In the second evaluation period, the duty cycle is exceeded and then it is set to 6 dB. As shown, the duration of the power class fallback is equal to the evaluation period. If the duty cycle is exceeded by the percentage of uplink symbols transmitted in a certain evaluation period in the first evaluation period, a new event triggers ΔPPowerClass = 3 dB in the PHR at t0. As a result, PC2 can be assumed in the second evaluation period. When ΔPPowerClass = 0 dB in the PHR is triggered by a legacy event during t0 < t < t1. After the duration of PC2, if the duty cycle is exceeded by the percentage of uplink symbols transmitted in a certain evaluation period in the second evaluation period, ΔPPowerClass = 3 dB (cumulative value) or 6 dB (absolute value) in the PHR is triggered at t1 by a new event. As a result, PC3 can be assumed in the third evaluation period. If the PHR is triggered by a legacy event or another new event that returns to the declared PC1.5, ΔPPowerClass = 0 dB in the PHR. After the duration of the power class fallback, if the PHR is triggered by a legacy event or another new event that returns to the declared PC2, and the percentage of uplink symbols transmitted in a certain evaluation period is greater than the duty cycle, ΔPPowerClass = 3 dB in the PHR. If the duty cycle is not exceeded after the evaluation period and it is triggered by a legacy event, ΔPPowerClass = 0 dB in the PHR. An overview of the detailed reported values is listed in Table 6.

Table 6

[0069] The described embodiment allows the UE to report the actual value for ΔPPowerClass to indicate which power class requirement the UE is referring to when the configured duty cycle is exceeded. Otherwise, the value is 0 dB. This reporting allows the reduced power class to be known for both the network / base station and the UE. It may be more efficient to utilize the UE's maximum power to improve base station scheduling decisions.

[0070] In some embodiments, the trigger may be modified. The examples described below include further examples illustrating triggers. A PHR with an actual value for ΔPPowerClass may be triggered by any one of a new event and a legacy event. The actual value for ΔPPowerClass (absolute, not cumulative) may be reported. A new event may include when a configured duty cycle is exceeded. The actual value for ΔPPowerClass may be an absolute value. Potential indications for ΔPPowerClass may be shown in Table 1 with a 2-bit indication, or Table 2 or Table 3 with a 1-bit indication.

[0071] The embodiments shown in Figures 5-7 and Tables 1-6 include different values ​​for ΔPPowerClass. The following embodiments rely on Figures 5-7 but illustrate different tables that include different values ​​for the parameters. Reference is made back to Figures 5-7 discussed above, but It is performed in the context of the table presented below. FIG. 5 illustrates a timing example for the PC2 band, and the duration of the PC fallback is equal to the evaluation period. As shown, ΔPPowerClass = 3 dB at t0 or t0 < t < t1. As shown, the duration of the power class fallback is equal to the evaluation period. If the duty cycle is exceeded in the first evaluation period, a new event triggers ΔPPowerClass = 3 dB in the PHR at t0. As a result, PC3 can be assumed in the second evaluation period. During t0 < t < t1, ΔPPowerClass = 3 dB in the PHR is triggered if triggered by a legacy event. After the duration of the power class fallback, if the PHR is triggered by a legacy event or another new event that returns to the declared PC2, ΔPPowerClass = 0 dB in the PHR. If the duty cycle is not exceeded after the evaluation period and is triggered by a legacy event, ΔPPowerClass = 0 dB in the PHR. An overview of the detailed reported values is listed in Table 7.

Table 7

[0072] FIG. 6 illustrates the timing of a PC1.5 band example where the duration of the PC fallback is equal to the evaluation period. FIG. 6 illustrates the timing of a PC2 band example where the duration of the PC fallback is equal to the evaluation period. As shown, ΔPPowerClass = 6 dB at t0 or t0 < t < t1. As shown, the duration of the power class fallback is equal to the evaluation period. If the duty cycle is exceeded by half of the percentage of uplink symbols transmitted in a certain evaluation period in the first evaluation period, a new event triggers ΔPPowerClass = 6 dB in the PHR at t0. As a result, PC3 can be assumed in the second evaluation period. During t0 < t < t1, ΔPPowerClass = 6 dB in the PHR is triggered if triggered by a legacy event. After the duration of the power class fallback, if the PHR is triggered by a legacy event or another new event that returns to the declared PC1.5, ΔPPowerClass = 0 dB in the PHR. After the duration of the power class fallback, if the PHR is triggered by a legacy event or another new event that returns to the declared PC2, and the percentage of uplink symbols transmitted in a certain evaluation period is greater than the duty cycle, ΔPPowerClass = 3 dB in the PHR. If the duty cycle is not exceeded after the evaluation period and is triggered by a legacy event, ΔPPowerClass = 0 dB in the PHR. An overview of the detailed reported values is listed in Table 8.

Table 8

[0073] Figure 7 illustrates the timing of another PC 1.5 band example where the duration of the PC fallback is equal to the evaluation period. As shown in the illustration, the duration of the power class fallback is equal to the evaluation period. If the duty cycle is exceeded by the percentage of uplink symbols transmitted in a certain evaluation period in the first evaluation period, a new event triggers ΔPPowerClass = 3 dB in the PHR at t0. As a result, PC2 can be assumed in the second evaluation period. During t0 < t < t1, ΔPPowerClass = 3 dB in the PHR is triggered if it is triggered by a legacy event. After the duration of PC2, if the duty cycle is exceeded by the percentage of uplink symbols transmitted in a certain evaluation period within the second evaluation period, ΔPPowerClass = 6 dB (absolute value), 3 dB (cumulative value) is triggered at t1 by a new event in the PHR. As a result, PC3 can be assumed in the third evaluation period. During t1 < t < t2, ΔPPowerClass = 6 dB in the PHR is triggered if it is triggered by a legacy event. If the PHR is triggered by a legacy event or another new event that returns to the declared PC 1.5, ΔPPowerClass = 0 dB in the PHR. After the duration of the power class fallback, if the PHR is triggered by a legacy event or another new event that returns to the declared PC2, and the percentage of uplink symbols transmitted in a certain evaluation period is greater than the duty cycle, ΔPPowerClass = 3 dB in the PHR. If the duty cycle is not exceeded after the evaluation period and it is triggered by a legacy event, ΔPPowerClass = 0 dB in the PHR. An overview of the detailed reported values is listed in Table 9.

Table 9

[0074] Embodiments may enable the UE to report on the actual value for ΔPPowerClass to indicate which power class requirement the UE is referring to when the configured duty cycle is exceeded or when triggered by a legacy event. The reduced power class may be known for both the network / base station and the UE. This may enable greater efficiency and utilization of the UE's maximum power to improve network / base station scheduling decisions. (Legacy Event Triggers)

[0075] The embodiments and Tables 1-6 shown in Figures 5-7 include different trigger examples. The following embodiments rely on Figures 5-7 but illustrate different tables including different values ​​and different triggers for the parameters. Reference is made back to Figures 5-7 discussed above, but in the context of the tables presented below. A PHR with an actual value for ΔPPowerClass is triggered by a new event; if the PHR is triggered by a legacy event, the value of ΔPPowerClass is not reported (which means the PHR is triggered by a legacy event). As described in the following embodiments, a separate reservation state for ΔPPowerClass can be used. A new event can be when the configured duty cycle is exceeded. The actual value for ΔPPowerClass can be an absolute value or a cumulative value. Potential indications of ΔPPowerClass can be shown in Tables 10-13 for various embodiments with a 2-bit indication or a 1-bit indication. [Table 10] [Table 11] [Table 12] [Table 13]

[0076] As shown in FIG. 5, the duration of the power class fallback is equal to the evaluation period. When the duty cycle is exceeded during the first evaluation period, a new event triggers ΔPPowerClass = 3 dB in the PHR at t0. As a result, PC3 can be assumed in the second evaluation period. When triggered by a legacy event during t0 < t < t1, ΔPPowerClass = reserved in the PHR is triggered. After the duration of the power class fallback, if the PHR is triggered by a legacy event or another new event that returns to the declared PC2, ΔPPowerClass = reserved or 0 dB in the PHR. If the duty cycle is not exceeded after the evaluation period and is triggered by a legacy event, ΔPPowerClass = reserved in the PHR. An overview of the detailed reported values is listed in Table 14.

Table 14

[0077] As shown in FIG. 6, the duration of the power class fallback is equal to the evaluation period. If the duty cycle is exceeded by half of the percentage of uplink symbols transmitted in a certain evaluation period in the first evaluation period, a new event triggers ΔPPowerClass = 6 dB in the PHR at t0. As a result, PC3 can be assumed in the second evaluation period. When triggered by a legacy event during t0 < t < t1, ΔPPowerClass = reserved in the PHR is triggered. After the duration of the power class fallback, if the PHR is triggered by a legacy event or another new event returning to the declared PC1.5, ΔPPowerClass = reserved or 0 dB in the PHR. After the duration of the power class fallback, if the PHR is triggered by a legacy event or another new event returning to the declared PC2, and the percentage of uplink symbols transmitted in a certain evaluation period is greater than the duty cycle, ΔPPowerClass = 3 dB in the PHR. If the duty cycle is not exceeded after the evaluation period and is triggered by a legacy event, ΔPPowerClass = reserved in the PHR. An overview of the detailed reported values is listed in Table 15.

Table 15

[0078] As shown in Figure 7, the duration of the power class fallback is equal to the evaluation period. If the duty cycle is exceeded by the percentage of uplink symbols transmitted in a certain evaluation period during the first evaluation period, a new event triggers ΔPPowerClass = 3 dB in the PHR at t0. As a result, PC2 is assumed in the second evaluation period. When triggered by a legacy event during t0 < t < t1, ΔPPowerClass = reserved is triggered in the PHR. After the duration of PC2, if the duty cycle is exceeded by the percentage of uplink symbols transmitted in a certain evaluation period within the second evaluation period, ΔPPowerClass = 6 dB (absolute value) or 3 dB (cumulative value) is triggered at t1 by a new event in the PHR. As a result, PC3 can be assumed in the third evaluation period. When triggered by a legacy event during t1 < t < t2, ΔPPowerClass = reserved in the PHR. If the PHR is triggered by a legacy event or another new event that returns to the declared PC1.5, ΔPPowerClass = reserved or 0 dB in the PHR. After the duration of the power class fallback, if the PHR is triggered by a legacy event or another new event that returns to the declared PC2, and the percentage of uplink symbols transmitted in a certain evaluation period is greater than the duty cycle, ΔPPowerClass = 3 dB in the PHR. If the duty cycle is not exceeded after the evaluation period and is triggered by a legacy event, ΔPPowerClass = reserved in the PHR. An overview of the detailed reported values is listed in Table 16.

Table 16

[0079] Embodiments may enable the UE to report on the actual value for ΔPPowerClass to indicate which power class requirement the UE is referring to when the configured duty cycle is exceeded or triggered by a legacy event. The reduced power class may be understood for both the network / base station and the UE. This may enable greater efficiency and utilization of the UE's maximum power to improve network / base station scheduling decisions.

[0080] Improved / enhanced information exchange between the UE and the network / base station can improve scheduling and network performance when using higher power by allowing the UE to report on ΔPPowerClass to indicate which power class requirement the UE is referring to when the default / configured duty cycle is partially / fully exceeded. The timing of the report may be limited to when the configured duty cycle is exceeded. Since the actual value for ΔPPowerClass or 0 dB or reserved status may be reported upon a legacy event, the PHR may need to modify how it reports ΔPPowerClass if both a new event and a legacy event are triggered simultaneously. In a first embodiment, reporting may be triggered by a new event as priority, and the actual value for ΔPPowerClass is reported. In a second embodiment, reporting may be triggered by a legacy event as priority, and the actual value for ΔPPowerClass or 0 dB or reserved status is reported.

[0081] FIG. 8 illustrates a timing example for a band in which the duration of PC fallback is not equal to the evaluation period. After reporting ΔPPowerClass, there may be a question of how long the power class fallback lasts. If no new event is introduced to return to the declared PC and no PHR is transmitted when returning to the declared PC, the network / base station may not know the exact PC. As shown in FIG. 8, if the UE were able to return to the declared PC2 at t1 / t2 / t3, the network / base station would schedule the UE assuming PC3 in the band until the next PHR assumed at t4. There may be two conditions for the relationship between the duration of PC fallback and the evaluation period. The first condition involves the duration of PC fallback being equal to the evaluation period. The second condition involves the duration of PC fallback not being equal to the evaluation period. When the default / configured duty cycle is partially / fully exceeded, in addition to enabling the UE reporting ΔPPowerClass to indicate which power class requirement the UE is referring to, one of the following embodiments may be used. The PHR is triggered by a new event to return to the declared PC (for any condition); or ● PHR is triggered by a legacy event to return to the PC declared by a timer that is approximately equal to the evaluation period (for the first condition), less than the evaluation period (for the second condition), or less than the evaluation period. For example, the phr-PeriodicTimer expires and you configure a smaller phr-PeriodicTimer to be equal to or less than the evaluation period (including configuring phr-PeriodicTimer=sf10). The declared PC will be returned after a certain time offset from the PHR triggered by a new event (e.g. the configured duty cycle is exceeded). The time offset can be determined in different examples: ○ Timer for the first condition (intent equals evaluation period); ○ A predetermined / reported / configured value for the second condition (intent is less than the evaluation period); or A timer defined to return to the declared PC for any condition. This timer is started when the PHR is triggered by a new event (e.g., the configured duty cycle is exceeded), and returns to the declared PC when the timer expires and resets to 0. If another report is triggered after a time offset from the PHR triggered by a new event (e.g. the configured duty cycle is exceeded), the declared PC is returned. The following alternatives are possible: ○ Timer for the first condition (intent equals evaluation period); ○ A predetermined / reported / configured value for the second condition (intent is less than the evaluation period); or o A timer defined to return to the declared PC for any condition. The timer is started when the PHR is triggered by a new event (e.g., the configured duty cycle is exceeded), and may trigger another report when the timer expires and resets to 0. For example, as shown in Figure 8, a timer is started when the PHR is triggered by a new event at t0, and another PHR is generated for ΔP PowerClass = 3 dB and the timer expires at t1. The power class fallback still applies, there is no return to the declared PC, and the timer is reset and started. Another PHR is triggered at t3, when ΔP PowerClass When the timer expires at .times..times..timer.=0dB, it will be triggered and the declared PC will then be returned.

[0082] In some embodiments, there may be a full-power MIMO transmission capability report corresponding to the current power class. Three modes of full-power MIMO transmission capability may include full-power, full-power mode 1, or full-power mode 2. Mode 0 (full-power) may target UEs with a full-rated PA. Using a 2-Tx PC3 non-coherent UE as an example, the UE is equipped with two 23 dBm PAs. The UE transmits the UL PUSCH using one antenna if the indicated TPMI is {1 0} with a power scaling factor s=1. This means that the transmit power is divided equally between the non-zero PUSCH antennas, thereby allowing the UE to provide maximum output power. Mode 1 (full-powerMode1) includes a new TPMI subset that is added. For UEs that support non-coherent capability, a non-antenna selection TPMI is added with the same power scaling as legacy. The new codebook subsets for rank=1 include {1 0}, {0 1}, and {1 1}. For precoder {1 1}, a PC3 UE can transmit with a total maximum output power of 23 dBm on the PUSCH. However, precoders {1 0} and {0 1} do not provide maximum output power. Mode 2 (full-power mode 2) includes providing maximum output power through TPMI reporting and antenna virtualization. Multiple SRS resources configured in a set with different numbers of SRS ports (up to four SRS resources can be configured in a set) may include, for example, using a 2-Tx non-coherent UE. The base station may configure two SRS resources in a set, one SRS resource configured with one port and another SRS resource configured with two ports. The base station indicates an SRI corresponding to one-port SRS when scheduling a single-layer transmission and an SRI corresponding to two-port SRS when scheduling a two-layer transmission. The UE may indicate a full-power TPMI / TPMI group. As an example, we use a 2 Tx non-coherent PC3 UE with a PA architecture where one PA is 23 dBm and the other PA is 20 dBm.The UE indicates TPMI=0 (i.e., precoder {1 0}) as full-power TPMI. If the base station indicates full-power TPMI while scheduling the PUSCH, the UE assumes power scaling factor s=1. If the base station indicates non-full-power TPMI while scheduling the PUSCH, the UE assumes the power scaling mechanism. For a 2-Tx UE, the UE can report two bits, bitmapped as {TPMI=0, TPMI=1}. For a 4-Tx UE, seven TPMI groups {G0, G1, G2, G3, G4, G5, G6} can be specified to support non-coherent and partially coherent implementations. A 4-Tx non-coherent UE can report its capability to indicate two-port TMPI using a two-bit bitmap and one of the four-port non-coherent TPMI groups from G0 to G3. A 4-Tx partially coherent UE can report its capability to indicate 2-port TMPI using a 2-bit bitmap, one of the 4-port non-coherent TPMI groups from G0 to G3, and one of the 4-port partially coherent TPMI groups from G0 to G6.

[0083] Since there are three modes of full-power MIMO transmission capability, it may be necessary to combine the reporting of ΔPPowerClass with the mode of full-power MIMO transmission. Since there are a maximum of two or three bits reserved for the FR1 PHR for a cell, there may not be enough bits to report ΔPPowerClass and the UL full-power mode independently. For example, two bits for ΔPPowerClass and two bits for the UL full-power mode may not be enough. For a multi-entry PHR MAC CE, a maximum of two bits may be reserved for the FR1 PHR for a cell.

[0084] This can be done by an independent instruction or a joint instruction. For the independent instruction, there can be a 2-bit ΔPPowerClass and a 1-bit UL full-power mode. One bit can be used to indicate maintaining the current mode or changing to another configured mode (e.g., the current mode is mode 1, the configured mode is mode 0, and one bit indicates one of mode 0 and mode 1). One of the three modes can be reported, and the other two of the three modes can be dynamically indicated. For example, only mode 0 or 2 can be dynamically indicated. When returning to the declared PC, if full-power mode 1 is configured, mode 1 will also be returned. In another independent instruction, the 1-bit ΔPPowerClass and 2-bit UL full-power mode can include one of the three modes indicated by the two bits and a 1-bit ΔPPowerClass instruction. In another independent instruction, the 1-bit ΔPPowerClass and 1-bit UL full-power mode can include a 1-bit ΔPPowerClass instruction as described above.

[0085] For joint indication, there may be a joint RRC configuration table or a predefined table for the combination of ΔPPowerClass and UL full power mode. Since there may be up to nine states for joint indication, at least one state may not be indicated. For example, as shown in Table 20, a non-zero ΔPPowerClass with mode 1 may not be included. For example, as shown in Table 21, a 2-bit joint indication is used. [Table 17] [Table 18]

[0086] In another example, based on FIG. 4c, the independent or joint indication of ΔPPowerClass and UL full power mode may be supported by separate octets. For example, compared to FIG. 4a, the third octet may be used, and an X bit may be used to report the joint indication of ΔPPowerClass and UL full power mode, where X may be 1, 2, 3, 4, 5, 6, 7, or 8. Alternatively, the third octet may be used, and an X1 bit may be used to report ΔPPowerClass, and an X2 bit may be used to report UL full power mode, where X1 or X2 may be 1, 2, 3, 4, 5, 6, 7, or 8, and X1 + X2 may be less than or equal to 8.

[0087] The systems and processes described above may be encoded in a computer-readable medium, such as a signal-bearing medium or memory, programmed into one or more integrated circuits, one or more processors, or processed by a controller or computer. The data may be analyzed in a computer system and used to generate a spectrum. If the method is performed by software, the software may reside in a non-volatile or volatile memory in communication with or interfaced to a storage device, synchronizer, communication interface, or transmitter. The circuit or electronic device is designed to transmit data to another location. The memory may contain an ordered list of executable instructions for implementing logical functions. The described logical functions or any system elements may be implemented via optical circuitry, digital circuitry, source code, analog circuitry, analog sources such as analog electrical signals, audio signals, video signals, or any combination thereof. The software may be embodied in any computer-readable or signal-bearing medium for use by or in connection with an instruction-executable system, apparatus, or device. Such a system may include a computer-based system, a system including a processor, or another system that may selectively fetch instructions from an instruction-executable system, apparatus, or device that may also execute the instructions.

[0088] "Computer-readable medium," "machine-readable medium," "propagating signal" medium, and / or "signal-bearing medium" may include any device that contains, stores, communicates, propagates, or carries software for use by or in connection with an instruction-executable system, apparatus, or device. The machine-readable medium may selectively be, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. A non-exhaustive list of examples of machine-readable media includes an electrically connected "electronic" having one or more wires, a portable magnetic or optical disk, a volatile memory such as random access memory "RAM," a read-only memory "ROM," an erasable programmable read-only memory (EPROM or flash memory), or an optical fiber. Machine-readable media may also include tangible media on which software is printed, when the software is stored electronically as an image or in another format (e.g., via optical scanning) and can then be compiled and / or interpreted or otherwise processed. The processed medium may then be stored in computer and / or machine memory.

[0089] The illustrations of the embodiments described herein are intended to provide a general understanding of the structure of various embodiments. These illustrations are not intended to serve as a complete description of all elements and features of apparatus and systems that utilize the structures or methods described herein. Many other embodiments will be apparent to those skilled in the art upon reviewing the present disclosure. Other embodiments may be utilized and derived from the present disclosure, whereby structural and logical substitutions and changes may be made without departing from the scope of the present disclosure. Furthermore, the illustrations are merely representational and may not be drawn to scale. Certain parts within the illustrations may be exaggerated, while other parts may be minimized. Therefore, the present disclosure and the figures should be considered illustrative and not limiting.

[0090] One or more embodiments of the present disclosure may be individually and / or collectively referred to herein by the term "invention," merely for convenience and without any intention to intentionally limit the scope of the present application to any particular invention or inventive concept. Furthermore, while specific embodiments have been illustrated and described herein, it should be understood that any subsequent configurations designed to achieve the same or similar purpose may be substituted for the specific embodiment shown. The present disclosure is intended to cover any and all subsequent adaptations or modifications of the various embodiments. Combinations of the above embodiments, as well as other embodiments not specifically described herein, will be apparent to those skilled in the art upon reviewing the description.

[0091] The phrase "coupled with" is defined to mean directly connected or indirectly connected through one or more intermediate components. Such intermediate components may include both hardware-based and software-based components. Changes in the arrangement and type of components may be made without departing from the spirit or scope of the claims set forth herein. Additional, different, or fewer components may be provided.

[0092] The subject matter disclosed above should be considered illustrative rather than limiting, and the appended claims are intended to cover all such modifications, extensions, and other embodiments that fall within the true spirit and scope of the invention. Accordingly, to the maximum extent permitted by law, the scope of the invention should be determined by the broadest permissible interpretation of the following claims and their equivalents, and not be limited or constrained by the foregoing detailed description. While various embodiments of the invention have been described, it will be apparent to those skilled in the art that many more embodiments and implementations are possible within the scope of the invention. Accordingly, the invention should not be limited except in light of the appended claims and their equivalents.

Claims

1. 1. A method for wireless communication, the method comprising: determining, by the device, parameters of an adjustment to a maximum output power for a given power class based on a comparison of the duty cycles; reporting said parameters when triggered by one or more events; Including, The method, wherein the one or more events include the duty cycle being exceeded due to a first new event or the expiration of a timer for a legacy event.

2. The method of claim 1 , wherein the reporting comprises a power headroom reporting (PHR) control element containing the parameter together with the available power headroom at the UE, or a separate control element containing the parameter.

3. 3. The method of claim 2, wherein the event includes the first new event and triggers the PHR with an actual value for the parameter, and the event includes the legacy event and triggers the PHR with a default value of 0 dB for the parameter, and further wherein the actual value includes an absolute value or a cumulative value.

4. 3. The method of claim 2, wherein the events include the first new event and the legacy event and trigger the PHR with an actual value for the parameter, the actual value including an absolute value or a cumulative value.

5. 3. The method of claim 2, wherein the event includes the first new event and triggers the PHR with an actual value for the parameter, and the event includes the legacy event and triggers the PHR with a reservation state for the parameter or the PHR with no value for the parameter, and the actual value includes an absolute value or a cumulative value.

6. 3. The method of claim 2, wherein when the PHR is triggered by the first new event and a legacy event simultaneously, the parameters in the PHR are determined based on the trigger by the first new event with an actual value, the actual value including an absolute value or a cumulative value.

7. 10. The method of claim 1, wherein after an adjustment to a maximum output power for a given power class, the given power class is changed back by a second new event or based on a time offset to return to the given power class.

8. 8. The method of claim 7, wherein the time offset is determined by a reported or configured value or another timer that starts and expires when the PHR is triggered by the first new event.

9. 9. The method of claim 8, wherein the given power class is returned after the time offset, or the given power class is returned based on another report triggered after the time offset from the PHR triggered by the first new event.

10. 10. The method of claim 9, wherein the given power class is returned if the parameter in the report includes 0 decibels (dB) or a reserved state.

11. 10. The method of claim 9, wherein the given power class is not returned when the parameter in the report is greater than 0 decibels (dB).

12. The method of claim 11 , wherein the reporting is triggered again after the time offset or after another time offset.

13. 2. The method of claim 1, wherein the report includes a power headroom report (PHR) control element including the parameters and an uplink (UL) total power mode along with a power headroom available at the UE, or a separate control element including the parameters and an uplink (UL) total power mode.

14. The method of claim 13 , wherein the parameters and the UL full power mode are reported by independent or joint indications.

15. The method according to claim 1 or 14, wherein the parameter is indicated by one or two bits.

16. 16. The method of claim 15, wherein the two states of the one-bit indication include either 0 (dB) and a non-zero value (dB), or a reserved state and an actual value (dB).

17. The method of claim 14 , wherein the UL full power mode is indicated by one or two bits.

18. 18. The method of claim 17, wherein the two states of the one-bit indication include either maintaining the reported mode and changing to another configured mode, or responding to two of three modes excluding the reported mode.

19. The method of claim 1 , wherein the first new event comprises when a configured or default duty cycle is at least partially exceeded.

20. 2. The method of claim 1, wherein the first new event comprises when the configured or default duty cycle is exceeded by half of the percentage of uplink symbols transmitted in a certain evaluation period.

21. 21. A wireless communications device comprising a processor and a memory, the processor configured to read code from the memory and to perform a method according to any preceding claim.

22. 21. A computer program product comprising computer readable program medium code stored thereon, the code, when executed by a processor, causing the processor to perform the method of any of claims 1 to 20.

Images