Reporting of parameters for adjusting to 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 generally applies to wireless communications. More specifically, it may extend to power headroom reporting (PHR), which includes reporting of parameters for adjusting to the maximum output power for a given power class. [Background technology]

[0002] Wireless communication technology is driving the world towards 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). Next-generation networks are expected to provide high-speed, low-latency, and ultra-high-reliability communication capabilities, meeting the requirements of diverse industries and users. User mobile stations or user equipment (UEs) are becoming more complex, and the amount of data transmitted is constantly increasing. Communication improvements should be made to enhance communication, meet the reliability requirements of vertical industries, and support next-generation network services.

[0003] In wireless communications, a user equipment (UE) may have the capability to support one or more power classes different from the default UE power class for a bandwidth, and the supported power classes may allow for a maximum output power higher than the maximum output power of the default power class. If the percentage of uplink symbols transmitted during a certain evaluation period (e.g., duty cycle) is greater than a threshold (e.g., maximum duty cycle), the UE may apply all the 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 the evaluation period is one or more radio frames, but the base station may not know the exact evaluation period used by the UE, nor the duration of the default power class that applies, which can lead to some ambiguity issues regarding uplink power control. [Overview of the project] [Means for solving the problem]

[0004] This document relates to methods, systems, and devices for wireless communications, including Power Headroom Reporting (PHR), which includes reporting of parameters for adjusting to the maximum output power for a given power class. The parameters are determined by the user equipment (UE) based on duty cycle evaluation and are reported when triggered by duty cycle overruns in new events or based on the expiration of a legacy event timer. 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 a device determining, based on a comparison of duty cycles, parameters for adjustment to the maximum output power for a given power class, and reporting the parameters when triggered by one or more events, the one or more events including the exceeding of a duty cycle for a first new event or the expiration of a timer for a legacy event.

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

[0007] In one embodiment, the computer program product stores and includes computer-readable program media code, which, when executed by a processor, causes the processor to implement any of the embodiments described above.

[0008] In some embodiments, a wireless communication device comprising a processor and a memory is provided, the processor being configured to read code from the memory and implement any of the methods described in any of the embodiments. In some embodiments, a computer program product stores and includes computer-readable program medium code that, when executed by a processor, causes the processor to implement any of the methods described in any of the embodiments. The above and other aspects and their implementations are described in more detail in the drawings, the specification, and the claims. The present invention provides, for example, the following: (Item 1) A method for wireless communication, wherein the method is Depending on the device, the parameters for adjusting the maximum output power for a given power class are determined based on a comparison of duty cycles. When triggered by one or more events, the aforementioned parameters are reported. Includes, The method includes the one or more events being caused by the duty cycle being exceeded for a first new event, or the expiration of a timer for a legacy event. (Item 2) The method according to item 1, wherein the reporting includes a power headroom reporting (PHR) control element that includes the power headroom available in the UE along with the parameters, or an independent control element that includes the parameters. (Item 3) The method according to item 2, wherein the event includes the first new event which triggers the PHR with an actual value for the parameter, and the event includes the legacy event which triggers the PHR with a default value of 0 dB for the parameter, and further, the actual value includes an absolute value or a cumulative value. (Item 4) The method according to item 2, wherein the event includes the first new event and the legacy event, triggering the PHR with an actual value for the parameter, the actual value including an absolute value or a cumulative value. (Item 5) The method according to item 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 reserved state for the parameter, or the PHR without a value for the parameter, and the actual value includes an absolute value or a cumulative value. (Item 6) If the PHR is triggered simultaneously by the first new event and the legacy event, the parameters in the PHR are determined based on the trigger by the first new event with actual values, the actual values ​​including absolute or cumulative values, as described in item 2. (Item 7) The method according to item 1, wherein, after adjustment for the maximum output power for a given power class, the given power class is returned to the given power class by a second new event or based on a time offset. (Item 8) The method according to item 7, wherein the time offset is determined by a reported or configured value or by another timer, the other timer starts and expires when the PHR is triggered by the first new event. (Item 9) The method according to item 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. (Item 10) The given power class is returned as described in item 9 if the parameter in the report includes 0 decibels (dB) or a reserved state. (Item 11) The given power class is not returned when the parameter in the report is greater than 0 decibels (dB), as described in item 9. (Item 12) The method described in item 11, wherein the report is triggered again after the aforementioned time offset or after another time offset. (Item 13) The method according to item 1, wherein the report includes a power headroom reporting (PHR) control element that includes the parameters and uplink (UL) full power mode along with the power headroom available in the UE, or an independent control element that includes the parameters and uplink (UL) full power mode. (Item 14) The parameters and the UL total power mode are reported by separate or joint instructions, as described in item 13. (Item 15) The parameter is represented by one or two bits, as described in item 1 or 14. (Item 16) The method according to item 15, wherein the two states of the 1-bit instruction include either 0 (dB) and a non-zero value (dB), or a reserved state and an actual value (dB). (Item 17) The UL full power mode is as described in item 14, indicated by one or two bits. (Item 18) The method according to item 17, wherein the two states of the 1-bit instruction include maintaining the reported mode and changing to another configured mode, or corresponding to two of the three modes other than the reported mode. (Item 19) The method described in item 1, wherein the first new event includes when the configured or default duty cycle is at least partially exceeded. (Item 20) The method according to item 1, wherein the first new event is when the configured or default duty cycle is exceeded by half of the percentage of uplink symbols transmitted during a certain evaluation period. (Item 21) A wireless communication device comprising a processor and memory, wherein the processor is configured to read code from the memory and perform the method described in any of items 1 to 20. (Item 22) A computer program product comprising a computer-readable program medium code stored thereon, wherein the code, when executed by a processor, causes the processor to perform any of the methods described in items 1 to 20. [Brief explanation of the drawing]

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

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

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

[0012] [Figure 4A] Figure 4a illustrates an example of a Power Headroom Report (PHR) structure.

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

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

[0015] [Figure 5] Figure 5 illustrates an example of timing for the PC2 bandwidth.

[0016] [Figure 6] Figure 6 illustrates an example of timing for the PC1.5 bandwidth.

[0017] [Figure 7] Figure 7 illustrates an example of timing for another PC1.5 bandwidth.

[0018] [Figure 8] Figure 8 illustrates a timing example for bandwidths where the PC fallback duration is not equal to the evaluation period. [Modes for carrying out the invention]

[0019] Hereafter, the Disclosure will be described in detail with reference to the accompanying drawings, which form part of the Disclosure and illustrate specific examples of embodiments. However, it should be noted that the Disclosure may be embodied in various different forms, and therefore the subject matter covered or claimed is not limited to any of the embodiments described below.

[0020] Throughout this specification and the claims, terms may have subtly different meanings implied or suggested in context beyond their expressly stated meanings. Similarly, the phrases “in one embodiment” or “in several embodiments” used herein do not necessarily refer to the same embodiment, and the expressions “in another embodiment” or “in other embodiments” used herein do not necessarily refer to different embodiments. The phrases “in one implementation” or “in several implementations” used herein do not necessarily refer to the same implementation, and the expressions “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, in whole or in part, exemplary embodiments or combinations of implementations.

[0021] In general, technical terms can be understood at least partially from their usage in context. For example, terms such as “and,” “or,” and “and / or,” when used herein, may have various meanings that may at least partially depend on the context in which such terms are used. Typically, when “or” is used to relate a list such as A, B, or C, it is intended to mean not only A, B, and C, which is used here in an inclusive sense, but also A, B, or C, which is used here in an exclusive sense. Furthermore, the terms “one or more” or “at least one” as used herein may, at least partially depending on the context, be used to describe any feature, structure, or characteristic in a singular sense, or to describe a combination of features, structures, or characteristics in a plural sense. Similarly, terms such as “a,” “an,” and “the” can also be understood, at least partially depending on the context, to convey either a singular or plural usage. Furthermore, the terms "based on" or "determined by" can be understood not necessarily as being intended to convey an exclusive set of factors, but rather, depending at least partially on the context, may allow for the presence of additional factors that are not necessarily explicitly stated.

[0022] Next-generation (NG) mobile communication systems are driving the world towards an increasingly connected and networked society. High-speed and low-latency wireless communication relies on efficient network resource management and allocation between user equipment and wireless access network nodes (including, but not limited to, wireless base stations). Next-generation networks are expected to provide high-speed, low-latency, and ultra-high-reliability communication capabilities, meeting the requirements of diverse industries and users.

[0023] Radio Resource Control ("RRC") is a protocol layer between the UE and the base station at the Internet Protocol (IP) level (network layer). There can be various Radio Resource Control (RRC) states, including the RRC_CONNECTED state, the RRC_INACTIVE state, and the RRC_IDLE state. RRC messages are carried via the Packet Data Convergence Protocol ("PDCP"). As described, the UE can transmit data by the Random Access Channel ("RACH") protocol scheme or the Configuration Grant ("CG") scheme. CG can be used to reduce waste of periodically allocated resources by allowing multiple devices to share periodic resources. A base station or node may allocate CG resources to eliminate packet transmission delay and increase the utilization of allocated periodic radio resources. The CG scheme is just 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 are driving increased demand. Based on current development trends, systems are developing support for features such as advanced mobile broadband (eMBB), ultra-high reliability low latency communication (URLLC), and massive machine-type communication (mMTC). Full duplex may be a requirement for 5G and subsequent communication systems. In wireless communications, network devices such as user equipment (UE) can perform uplink (UL) transmitter (Tx) switching between bands. For multi-carrier operation, a network device that transmits using two transmitters (also called a 2Tx user device) can transmit in two UL bands. Which two bands are used can 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 for a bandwidth, and the supported power classes may enable a higher maximum output power than the default power class. If the percentage of uplink symbols transmitted during a certain evaluation period (e.g., duty cycle) is greater than a threshold (e.g., maximum duty cycle), the UE may apply all the 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 the evaluation period is one or more radio frames, but the base station (or wireless communication node) does not know the exact evaluation period used by the UE, nor the duration of the applied default power class, which can lead to some ambiguity issues regarding uplink power control. Another problem / challenge may include uncertainty in how to calculate the percentage of uplink symbols transmitted during a certain evaluation period when non-overlapping subband full-duplex is applied, where the uplink subband is introduced into the downlink or flexible symbols. This disclosure describes various embodiments for reporting parameters for adjusting to maximum output power for a given power class and addresses at least one of the issues / challenges discussed herein.

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

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

[0028] Furthermore, signals communicated between communication nodes within 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., audio and / or image data), while control signals are signals that carry control information that constitutes communication nodes in a certain way for them 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. Certain signals may also be characterized or defined as uplink (UL) signals, downlink (DL) signals, or sidelink (SL) signals. Uplink signals are signals transmitted from UE 104 to base station 102. Downlink signals are signals transmitted from base station 102 to 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 over physical channels. Generally, a physical channel corresponds to a set of time-frequency resources used for signal transmission. Different types of physical channels may be used to transmit different types of signals. For example, a physical data channel (or simply data channel), also referred to herein as a traffic channel, is used to transmit data signals, and a physical control channel (or simply control channel) is used to transmit control signals. Examples of types of traffic channels (or physical data channels) include, but are not limited to, physical downlink shared channels (PDSCH) used to communicate downlink data signals, physical uplink shared channels (PUSCH) used to communicate uplink data signals, and physical sidelink shared channels (PSSCH) used to communicate sidelink data signals. In addition, examples of types of physical control channels include, but are not limited to, physical downlink control channels (PDCCH) used to communicate downlink control signals, physical uplink control channels (PUCCH) used to communicate uplink control signals, and physical sidelink control channels (PSCCH) used to communicate sidelink control signals. For the sake of simplification as used herein, unless otherwise specified, a particular type of physical channel is also used to refer to the signals transmitted over that particular type of physical channel, and / or the transmissions over that particular type of transmission. For example, PDSCH refers to the physical downlink shared channel itself, the downlink data signals transmitted over the PDSCH, or the downlink data transmission. Therefore, when a communication node transmits or receives a PDSCH, it means that the communication node is transmitting or receiving signals over the PDSCH.

[0030] Furthermore, for at least some specifications such as 5GNR, and / or for at least some types of control signals, the control signals transmitted by a communication node may include control information that includes information necessary to enable the 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 uplink scheduling authorization that informs a user device about the resources and transport format to be used for proper reception, decoding, and demodulation of data signals received on a physical data channel during data transmission, and / or for uplink data transmission. In some embodiments, the control information includes downlink control information (DCI) transmitted in the downlink direction from base station 102 to UE 104. In other embodiments, the control information includes uplink control information (UCI) transmitted in the uplink direction from UE 104 to base station 102, or sidelink control information (SCI) transmitted in the sidelink direction from one UE 104 to another UE 104.

[0031] In addition, in some embodiments, the UE104 may be configured to support at least one simultaneous UL transmission mode across a bandwidth pair for UL transmission. In a first simultaneous UL transmission mode (also called switched UL mode), the UE104 does not support simultaneous UL transmission across a bandwidth pair. Therefore, when the UE104 transmits a UL transmission in the first simultaneous UL transmission mode, the UE104 transmits the UL transmission without simultaneously transmitting across a bandwidth pair. In addition, in a second simultaneous UL transmission mode (also called dual UL mode), the UE104 supports simultaneous UL transmission across a bandwidth pair. Therefore, when the UE104 transmits a UL transmission in the second simultaneous UL transmission mode, the UE104 can transmit the UL transmission by simultaneously transmitting across a bandwidth pair.

[0032] In some embodiments, the UE 104 may report the 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 across a band pair, that the UE does not support simultaneous UL transmission across a band pair, or that the UE supports and does not support simultaneous UL transmission across a band pair. In certain of these embodiments, the UE 104 may report whether or not it supports simultaneous UL transmission across a band pair (BC) per band combination. Furthermore, the base station 102 may configure a simultaneous UL transmission mode per cell group (e.g., switchedUL or dualUL), which can be thought of as per BC or per band pair in embodiments where a 2Tx user device supports only two bands. That is, one available band pair in a band combination may support one simultaneous UL transmission mode.

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

[0034] Figure 2 shows an exemplary random access messaging environment 200. In this random access messaging environment, UE 104 can communicate with base station 102 via random access channel 252. In this example, UE 104 supports one or more subscriber identification modules (SIMs), such as SIM1 202. Electrical and physical interfaces 206 connect SIM1 202 to the rest of the user equipment hardware, for example, via system bus 210.

[0035] The mobile device 200 includes a communication 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, for example, using one or more system-on-a-chip (SoCs), application-specific integrated circuits (ASICs), discrete analog and digital circuits, and other circuits. The system logic 214 is part of an implementation of any desired function in the UE 104. In this regard, the system logic 214 may include, for example, decoding and playing music and video, e.g., decoding and playing MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV; running applications; accepting user input; saving and retrieving application data; establishing, maintaining, and terminating data connections for cellular phone calls or, as an example, internet connections; establishing, maintaining, and terminating wireless network connections, Bluetooth® connections, or other connections; and logic to facilitate the display of relevant information on the user interface 218. User interfaces 218 and inputs 228 may include graphical user interfaces, touch-sensitive displays, haptic feedback or other haptic outputs, voice or facial recognition inputs, buttons, switches, speakers, and other user interface elements. Further examples of inputs 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 inputs.

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

[0037] In the communication interface 212, the radio frequency (RF) transmission (Tx) and reception (Rx) circuit 230 handles the transmission and reception of signals via one or more antennas 232. The communication interface 212 may include one or more transceivers. A transceiver may be a wireless transceiver that includes a modulation / demodulation circuit, a digital-to-analog converter (DAC), a shaping table, an analog-to-digital converter (ADC), a filter, a waveform shaper, a filter, a preamplifier, a power amplifier, and / or other logic for transmission and reception via one or more antennas or (for some devices) via a physical (e.g., wired) medium.

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

[0039] Multiple RAN nodes (eNB, gNB, etc.) of the same or different radio access technologies ("RAT") can be deployed in a given geographical area on the same or different frequency carriers, and these RAN nodes can cooperate with each other through dual connectivity operation to provide a joint communication service for the same (one or more) target UEs. A multi-RAT dual connectivity ("MR-DC") architecture may have master nodes ("MN") and secondary nodes (SN) that are not located in the same place. Access mobility management functions ("AMF") and session management functions ("SMF") may be control plane entities, and user plane functions ("UPF") may be user plane entities in new radio ("NR") or 5GC.

[0040] Figure 3 shows one embodiment of a wireless network system architecture. This architecture is merely an example, and there may be more or fewer components to implement 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 in the text or other figures. Figure 2 illustrates an exemplary user equipment ("UE") 104. UE 302 is a device that accesses a wireless network (e.g., 5GS) and obtains services via an NG-RAN node or base station 304. 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., an NG-RAN 102. Base station 304 may also be referred to as a Next Generation Radio Access Network ("NG-RAN") node and can provide time synchronization signals to user equipment (UE). An AI model or processing method may be part of UE302, and information may be provided by the UE to the components shown in Figure 3, as described in the following embodiments.

[0041] The AMF306 includes the following functions: registration management, connection management, reachability management, and mobility management. The AMF306 also performs access authentication and access permission. The AMF306 is the NAS security termination and relays session management NAS between the UE302 and SMF308, etc. The SMF308 includes the following functions: session management (e.g., session establishment, modification, and release), UE IP address assignment and management (including optional permission), uplink function selection and control, downlink data notification, etc. The User Plane Function ("UPF") 310 includes the following functions: anchor points for RAT / inter-RAT mobility, packet routing and forwarding, traffic usage reporting, QoS processing for the user plane, downlink packet buffering, and triggering downlink data notification, etc. The Integrated Data Management ("UDM") 312 manages subscription profiles for UEs. Subscriptions include data used for mobility management (e.g., restricted areas) and session management (e.g., QoS profiles). The subscription data also includes slice selection parameters used by AMF306 to select the appropriate SMF308. AMF306 and SMF308 obtain subscriptions from UDM312. The subscription data may be stored in an integrated data repository with UDM312, which uses such data when it receives a request from AMF306 or SMF308. The policy control function ("PCF") 314 includes the following functions: the ability to support an integrated policy framework for managing network behavior; the ability to provide policy rules for controlling plain functions to enforce policy rules; and the ability to implement a front-end for accessing subscription information associated with policy decisions in the user data repository. The network exposure function ("NEF") 316 may be optionally configured to exchange information with external third parties. In one embodiment, the application function ("AF") 316 may store application information in the integrated data repository via the NEF.UPF310 communicates with data network 318.

[0042] The embodiments described below may include the UE determining parameters for adjusting the maximum output power for a given power class based on an evaluation cycle, and then reporting these parameters to the network / base station. A 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 relation to the network / wireless communication environment shown in Figures 1-3. This reporting may be triggered by the duty cycle being exceeded by 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 communication system, for a single uplink (UL) carrier, the UE may be allowed to set its configured maximum power PCMAX,f,c for the carrier f of serving cell c. The configured maximum power PCMAX,f,c may be set within the following boundary: PCMAX_L,f,c ≤ PCMAX,f,c ≤ PCMAX_H,f,c, where PCMAX_L,f,c and PCMAX_H,f,c depend on PPowerClass, where PPowerClass,c is a linear value of the maximum UE power for serving cell c, without considering tolerances, or UE-PowerClass.

[0044] In some embodiments of wireless communication systems, for uplink (UL) carrier aggregation (CA), the UE may be enabled to set a configured maximum output power PCMAX,c for serving cell c and the sum of the configured maximum output power PCMAX. The configured sum of maximum output power PCMAX may be set within the following boundary, i.e., PCMAX_L ≤ PCMAX ≤ PCMAX_H, where PCMAX_L and PCMAX_H depend on the PPowerClass of the CA. The maximum power class (PC) of the CA, PPowerClass, can be PC2, and the power available in the UL CA is limited by PPowerClass,CA. In some cases, PPowerClass,CA is replaced by 10log10ΣpPowerClass,c, which is also named the aggregated power of the UL CA, and PPowerClass,c is the linear value of the maximum UE power for serving cell c without considering tolerances, or UE-PowerClass.

[0045] In some embodiments, power headroom (PHR) calculations can be performed as follows:

number

[0046] Here,

number

number

number

number

number

[0047] Here,

number

number

number

[0048]

number

number

[0049] Here,

number

[0050] K S Regarding =1.25

number

number

[0051] Power Headroom Reporting (PHR) may be triggered if any of the following legacy events occur: ●When phr-ProhibitTimer has expired or is about to expire, and the MAC entity has UL resources for a new transmission, the path loss has changed by more than phr-Tx-PowerFactorChange dB with respect to at least one RS used as the path loss criterion for one activated serving cell of any MAC entity that is not a dormant BWP since the last transmission of PHR in this MAC entity; ● The phr-PeriodicTimer expires; ●When configuring or reconfiguring power headroom reporting functionality by a higher layer that is not being used to disable the function; ●Activation of the SCell of any MAC entity with a configured uplink where firstActiveDownlinkBWP-Id is not set to an inactive BWP; ●Activation of the SCG; and ●Addition of a PSCell (i.e., the 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 default UE power class of the band, and the supported power class enables a maximum output power higher than the default power class. In one embodiment, the requirements of the supported power class may be applied, and in one embodiment, a configured transmission power is set, such that the UE is enabled to set its configured maximum output power PCMAX,f,c for carrier f of serving cell c within each slot. The configured maximum output power PCMAX,f,c may be set within the following boundaries. 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 may be set as follows: ●In the following cases, if a P-max of 3dB or less is indicated for a power class 2 compliant UE, or 6dB or less for a power class 1.5 UE: ​​23dBm or less; or if the UE capability maxUplinkDutyCycle-PC2-FR1 field does not exist, the UE capability maxUplinkDutyCycle-PC1dot5-MPE-FR1 field does not exist, and the percentage of uplink symbols transmitted during a given evaluation period is greater than 50%; or if the UE capability maxUplinkDutyCycle-PC2-FR1 field does not exist, and the percentage of uplink symbols transmitted during a given evaluation period is greater than maxUplinkDutyCycle-PC1dot5-MPE-FR1; or if the UE capability maxUplinkDutyCycle-PC1dot5-MPE-FR1 field does not exist, and half of the percentage of uplink symbols transmitted during a given evaluation period is greater than maxUplinkDutyCycle-PC1dot5-MPE-FR1. The precise evaluation period may be one wireless frame or longer. ●In the following cases, 3dB for a power class 1.5 compliant UE: If the P-max is shown to be between 23 dBm and 26 dB; 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 during a given 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 during a given 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 during a given evaluation period is greater than maxUplinkDutyCycle-PC1dot5-MPE-FR1. The precise evaluation period may be one wireless frame or longer. ●3dB applies in the following cases: UE is configured in a SUL configuration and the requirements of the default power class apply to the bandwidth where the UE is in power class 2. ●If a PC2-enabled UE or PC1.5-enabled UE with txDiversity-r16 capability further indicates SRS-TxSwitch capability "t1r2", "t1r4", "t1r1-t1r2", or "t1r1-t1r2-t1r4", then 3dB is applied during an SRS transmission opportunity configured as "antennaSwitching" with configured SRS resources in each SRS resource set consisting of one SRS port in the SRS-ResourceSet; or, ● Otherwise, 0dB.

[0054] In some embodiments, if the UE can support a power class different from the default UE power class for the bandwidth, and the supported power class allows for a higher maximum output power than the default power class, the following may be implemented: ●If the UE capability maxUplinkDutyCycle-PC2-FR1 field does not exist, the UE capability maxUplinkDutyCycle-PC1dot5-MPE-FR1 field does not exist, and the percentage of uplink symbols transmitted during a certain evaluation period is greater than 50% (the exact evaluation period is one wireless frame or more); or ●If the UE capability maxUplinkDutyCycle-PC2-FR1 field does not exist and the percentage of uplink symbols transmitted during a certain evaluation period is greater than maxUplinkDutyCycle-PC2-FR1; or ● The field maxUplinkDutyCycle-PC1dot5-MPE-FR1 does not exist, and half of the percentage of uplink symbols transmitted during a certain evaluation period is greater than maxUplinkDutyCycle-PC1dot5-MPE-FR1; or ●When IE P-Max is provided and set to a maximum output power of less than or equal to 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 transmission power is set accordingly. This can 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 bandwidth, and the supported power class allows for a higher maximum output power than the default power class, the following may be implemented: ●If the field maxUplinkDutyCycle-PC2-FR1 does not exist, the field maxUplinkDutyCycle-PC1dot5-MPE-FR1 does not exist, and the percentage of uplink symbols transmitted during a certain evaluation period is greater than 25%; or ●If the UE capability maxUplinkDutyCycle-PC2-FR1 field does not exist, and the percentage of uplink symbols transmitted during a certain evaluation period is greater than 0.5*maxUplinkDutyCycle-PC2-FR1; ●If the UE capability maxUplinkDutyCycle-PC1dot5-MPE-FR1 does not exist and the percentage of uplink symbols transmitted during a certain evaluation period is greater than maxUplinkDutyCycle-PC1dot5-MPE-FR1; or ●When IE P Max is provided and set to a maximum output power of power class 2 or less; or ● All requirements of power class 2 may apply to the supported power class, and the configured transmission power is set accordingly. (Parameter reporting in PHR)

[0056] Power Headroom Reporting (PHR) includes reporting of a parameter for adjusting 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 a duty cycle evaluation and reported to the network / base station when the duty cycle is exceeded by a new event or triggered based on the expiration of a legacy event timer. The following embodiments include examples of parameter determination and reporting, and event triggering.

[0057] Figure 4a illustrates an example of a Power Headroom Report (PHR) structure. Figure 4b illustrates another example of a PHR structure with parameters for adjusting the maximum output power for a given power class. For power headroom reporting, there can be several PHR MAC control elements (CEs), including: single-entry PHR MAC CE, multi-entry PHR MAC CE, enhanced single-entry PHR MAC CE, enhanced single-entry PHR for enhanced multi-entry PHR MAC CE, or enhanced multi-entry PHR for multi-TRP MAC CE. Using a single-entry PHR MAC CE as an example, with respect to 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 the MPE is reserved for FR1. ΔPPowerClass may be applied for FR1. Since 2 bits may be required for the UE to report ΔPPowerClass, the MPE field for FR2 can be reused to report ΔPPowerClass for FR1. Figure 4b illustrates that this field is replaced by a parameter for adjusting the maximum output power for a given power class, called ΔPPowerClass. Figure 4c illustrates another example of a PHR structure with a parameter for adjusting the maximum output power for a given power class, which uses partial or all bits in a separate octet to report ΔPPowerClass. For example, compared to Figure 4a, a third octet is used, where bit X is used to report ΔPPowerClass, and 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, the P field, if set to 1, may indicate the applied power backoff to satisfy the MPE requirement. The field length is 2 bits. If mpe-Reporting-FR2 is not configured, or if the SC operates in FR1, or if the P field is set to 0, the R bit may be present instead.

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

[0060] In addition to the configured duty cycles, there may be default duty cycle cases. For example, if the UE capability maxUplinkDutyCycle-PC2-FR1 field is absent, the UE capability maxUplinkDutyCycle-PC1dot5-MPE-FR1 field is absent, and the percentage of uplink symbols transmitted during a given evaluation period is greater than 50%, then ΔPPowerClass is 3dB for a power class 2 compliant UE or 6dB for a power class 1.5 UE. If the default duty cycle is exceeded, ΔPPowerClass may be reported. For example, if the UE capability maxUplinkDutyCycle-PC2-FR1 field is absent, the UE capability maxUplinkDutyCycle-PC1dot5-MPE-FR1 field is absent, and the percentage of uplink symbols transmitted during a given evaluation period is greater than 50%, then ΔPPowerClass may be reported because the power class requirement that the UE is referencing is reduced, and it is similar to the configured duty cycle cases.

[0061] In other embodiments, there may be a partially exceeded default / configured duty cycle. For example, if the field UE capability maxUplinkDutyCycle-PC2-FR1 is absent and the field UE capability maxUplinkDutyCycle-PC1dot5-MPE-FR1 is absent and the percentage of uplink symbols transmitted during a certain evaluation period is between 25% and 50%, or if the field UE capability maxUplinkDutyCycle-PC2-FR1 is absent and the percentage of uplink symbols transmitted during a certain evaluation period is between maxUplinkDutyCycle-PC2-FR1 and maxUplinkDutyCycle-PC2-FR1 / 2, then the parameter ΔPPowerClass is 3dB for power class 1.5UE. If the default / configured duty cycle is partially exceeded, ΔPPowerClass may be reported. Partial exceedance 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 does not exist, and the UE capability maxUplinkDutyCycle-PC1dot5-MPE-FR1 field does not exist, and the percentage of uplink symbols transmitted during a certain evaluation period is between 25% and 50%, then the parameter ΔPPowerClass may be reported because the power class requirement that the UE is referencing is reduced, which is similar to the example above where 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 during a given evaluation period. For example, if the field maxUplinkDutyCycle-PC1dot5-MPE-FR1 does not exist and half the percentage of uplink symbols transmitted during a given evaluation period is greater than maxUplinkDutyCycle-PC1dot5-MPE-FR1, then the parameter ΔPPowerClass is 6dB for power class 1.5UE. If the default / configured duty cycle is exceeded by half the percentage of uplink symbols transmitted during a given evaluation period, then ΔPPowerClass may be reported. For example, if the UE capability field maxUplinkDutyCycle-PC1dot5-MPE-FR1 does not exist, and half of the percentage of uplink symbols transmitted during a certain evaluation period is greater than maxUplinkDutyCycle-PC1dot5-MPE-FR1, the power class requirement that the UE is referencing is reduced, and therefore the parameter ΔPPowerClass may be reported. This may be similar to the above example where the duty cycle is completely exceeded, or exceeded by a percentage of uplink symbols transmitted during a certain evaluation period.

[0063] The embodiment can enable the UE to appropriately report 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 a minimum, the reduced power class can be understood for both the network / base station and the UE. This can enable better utilization of the UE's maximum power and improve network / base station scheduling decisions.

[0064] The transmission of parameters for adjusting 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 requirements the UE is referring to when the default / configured duty cycle is partially / fully exceeded. Reporting may be limited to when the configured duty cycle is exceeded. Since the Enhanced PHR includes an indication of ΔPPowerClass, embodiments for reporting ΔPPowerClass in the PHR are described here. In some examples, the reported value of ΔPPowerClass is a cumulative or absolute value. Furthermore, the reported value of ΔPPowerClass may differ when triggered by a legacy event.

[0065] The PHR with an actual value for ΔPPowerClass can only be triggered by a new event. Otherwise, there may be a default value of 0dB for ΔPPowerClass. A new event may include when the configured duty cycle is exceeded. If triggered by a legacy event, the PHR may contain a value of 0dB for ΔPPowerClass. The actual value for ΔPPowerClass may be an absolute value or a cumulative value. Potential indications for ΔPPowerClass may be shown in Table 1, which shows a 2-bit indication, or in 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, when triggered by a legacy event, ΔPPowerClass = 0 dB in the PHR. An overview 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 from 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 in the first evaluation period, a new event triggers ΔPPowerClass = 6B 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] FIG. 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 in the figure, 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 = 0 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 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 an 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 understood for both the network / base station and the UE. Utilizing the UE's maximum power to improve base station scheduling decisions may be more efficient.

[0070] In some embodiments, the trigger may be modified. The examples described below include further examples illustrating the trigger. The PHR with an actual value for ΔPPowerClass may be triggered by either a new event or a legacy event. The actual value (absolute value, not cumulative) for ΔPPowerClass may be reported. A new event may include when the 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 in 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 with different values ​​for the parameters. References are made by returning to Figures 5-7 discussed above. It is performed in the context of the table presented below. Figure 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 when 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, at t0 or t0 < t < t1, ΔPPowerClass = 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 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 if 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, 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 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 in the PHR by a new event. 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 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 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] The embodiment may allow the UE to report on an actual value for ΔPPowerClass to indicate which power class requirement the UE is referencing when the configured duty cycle is exceeded or when triggered by a legacy event. The reduced power class may be understood for both the network / base station and the UE. This may allow for more efficient utilization of the UE's maximum power to improve network / base station scheduling decisions. (Legacy event trigger)

[0075] The embodiments shown in Figures 5-7 and Tables 1-6 include different trigger examples. The following embodiments rely on Figures 5-7 but illustrate different tables with different parameter values ​​and different triggers. References are 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, and if the PHR is triggered by a legacy event, the value of ΔPPowerClass is not reported (meaning the PHR is triggered by a legacy event). A separate reserved state for ΔPPowerClass may be used, as described in the following embodiments. A new event may occur when the configured duty cycle is exceeded. The actual value for ΔPPowerClass may be an absolute or cumulative value. Potential indications for ΔPPowerClass may be shown in Tables 10-13 for various embodiments with 2-bit or 1-bit indications. [Table 10] [Table 11] [Table 12] [Table 13]

[0076] As shown in Figure 5, the duration of the power class fallback is equal to the evaluation period. If 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 during 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 is triggered 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 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 15.

Table 15

[0078] As shown in FIG. 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 in 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 in the PHR is triggered. 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 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 16.

Table 16

[0079] The embodiment allows the UE to report on an actual value for ΔPPowerClass to indicate which power class requirement the UE is referencing when the configured duty cycle is exceeded or triggered by a legacy event. The reduced power class can be understood for both the network / base station and the UE. This may enable more efficient 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 about ΔPPowerClass to indicate which power class requirements 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 or 0dB or reserved state for ΔPPowerClass may be reported during legacy events, the PHR may need to modify how it reports ΔPPowerClass if both new and legacy events are triggered simultaneously. In the first embodiment, the report may be triggered by the new event as preferred, and the actual value for ΔPPowerClass is reported. In the second embodiment, the report may be triggered by the legacy event as preferred, and the actual value or 0dB or reserved state for ΔPPowerClass is reported.

[0081] Figure 8 illustrates a timing example for bandwidth where the duration of PC fallback is not equal to the evaluation period. After reporting ΔPPowerClass, there may be an issue of how long the power class fallback lasts. If no new event is introduced to return to the declared PC and there is no PHR sent when returning to the declared PC, the network / base station may not know the exact PC. As illustrated in Figure 8, if the UE was able to return the declared PC2 at t1 / t2 / t3, the network / base station would schedule the UE to assume PC3 in the bandwidth until the next PHR assumed at t4. Due to the relationship between the duration of PC fallback and the evaluation period, there may be two conditions. The first condition includes the duration of PC fallback being equal to the evaluation period. The second condition includes the duration of PC fallback being not equal to the evaluation period. In addition to enabling UE reporting on ΔPPowerClass to indicate which power class requirement the UE is referring to when the default / configured duty cycle is partially / fully exceeded, one of the following embodiments may be used. ●PHR is triggered by a new event that returns to the declared PC (for any condition); or ● PHR is triggered by legacy events that return to a PC declared by a timer that is approximately equal to or less than the evaluation period (in the first condition), or less than or equal to the evaluation period (in the second condition). For example, when phr-PeriodicTimer expires and a phr-PeriodicTimer is set to a smaller value because it is equal to or less than the evaluation period (including setting phr-PeriodicTimer=sf10). ● A 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 (intended to be equal to the evaluation period); ○The specified / reported / configured value for the second condition (intended to be less than the evaluation period); or ○ A timer defined to return to the declared PC due to any of the following conditions. 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 ends and is reset to 0. ●If another report is triggered by a new event (e.g., the configured duty cycle is exceeded) some time offset from the PHR, the declared PC is returned. The following alternatives are possible: ○ Timer for the first condition (intended to be equal to the evaluation period); ○The specified / reported / configured value for the second condition (intended to be less than the evaluation period); or ○ A timer defined to return to the declared PHR for any of the conditions. The timer is started when the PHR is triggered by a new event (e.g., the configured duty cycle is exceeded), and when the timer ends and is reset to 0, it may trigger another report. For example, as shown in Figure 8, the timer is started when the PHR is triggered by a new event at t0, and another PHR is triggered by ΔP PowerClass When the timer ends at t1 with =3dB, it is triggered. Power class fallback is still applied, there is no return to the declared PC, the timer is reset and started. Another PHR is triggered at t3, ΔP PowerClass When the timer ends at =0dB, it will be triggered, and then the declared PC will be returned.

[0082] In some embodiments, there may be a full-power MIMO transmission capability report corresponding to the current power class. The three modes of full-power MIMO transmission capability may include fullpower, fullpower mode 1, or fullpower mode 2. Mode 0 (fullpower) can target a UE with a fully rated PA. Using a 2 Tx PC3 non-coherent UE as an example, the UE is equipped with two 23dBm PAs. The UE transmits UL PUSCH using one antenna if the indicated TPMI is {1 0} with a power scaling factor s=1. This means that the transmitted power is equally divided between the non-zero PUSCH antennas, thereby allowing the UE to deliver maximum output power. Mode 1 (fullpowerMode1) includes a new subset of TPMIs that are added. For UEs supporting non-coherent capability, a non-antenna-selective TPMI is added with the same power scaling as the legacy. The new codebook subset for rank=1 includes {1 0}, {0 1}, and {1 1}. In the case of precoder {1 1}, the PC3 UE can transmit at a total maximum output power of 23 dBm in PUSCH. However, precoders {1 0} and {0 1} do not supply maximum output power. Mode 2 (fullpower mode 2) includes supplying maximum output power through TPMI reporting and antenna virtualization. Multiple SRS resources configured in sets with different numbers of SRS ports (up to four SRS resources can be configured in a set) may include, as an example, the use of a 2Tx non-coherent UE. A base station may configure two SRS resources in a set, one SRS resource consisting of one port and the other SRS resource consisting of two ports. The base station indicates an SRI corresponding to one port SRS while scheduling single-layer transmission, and an SRI corresponding to two port SRS while scheduling 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 is 20 dBm.The UE indicates TPMI=0 (i.e., precoder {1 0}) as the full-power TPMI. If the base station indicates full-power TPMI while scheduling a push, the UE assumes a power scaling factor s=1; if the base station indicates non-full-power TPMI while scheduling a push, the UE assumes a power scaling mechanism. For a 2Tx UE, the UE can report 2 bits, bitmapped as {TPMI=0, TPMI=1}. For a 4-Tx UE, seven TPMI groups {G0, G1, G2, G3, G4, G5, G6} may be specified to support non-coherent and partially coherent implementation forms. A 4-Tx non-coherent UE can report its ability to indicate 2-port TPMI using a 2-bit bitmap and one of the 4-port non-coherent TPMI groups from G0-G3. A 4-Tx partially coherent UE can report its ability to exhibit a 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. Because there are up to 2 or 3 bits reserved for the FR1 PHR for a cell, the bits may not be sufficient to independently report ΔPPowerClass and UL full-power mode. For example, 2 bits for ΔPPowerClass and 2 bits for UL full-power mode may not be sufficient. For multi-entry PHR MAC CEs, up to 2 bits may be reserved for the FR1 PHR for a cell.

[0084] This can be done by independent or joint instructions. For independent instructions, there may be a 2-bit ΔPPowerClass and a 1-bit UL full power mode. The 1-bit can be used to indicate maintaining the current mode or changing to another configured mode (for example, the current mode is mode 1, the configured mode is mode 0, and the 1-bit indicates one of mode 0 and mode 1). One of the three modes may be reported, and the other two of the three modes may be indicated dynamically. For example, only mode 0 or 2 may be indicated dynamically. When returning to the declared PC, if fullpower 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 may include one of the three modes indicated by the 2 bits and the 1-bit ΔPPowerClass instruction. In another independent instruction, the 1-bit ΔPPowerClass and 1-bit UL full power mode may include the 1-bit ΔPPowerClass instruction as described above.

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

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

[0087] The systems and processes described above may be encoded in computer-readable media such as signal-holding media or memory, programmed in devices such as one or more integrated circuits or 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 non-volatile or volatile memory communicating with storage devices, synchronous devices, communication interfaces, or transmitters, or in memory interfaced to them. Circuits or electronic devices are designed to transmit data to another location. Memory may contain an ordered list of executable instructions for implementing logical functions. The logical functions or any system elements described may be implemented via optical circuits, digital circuits, source code, analog circuits, analog sources such as analog electrical signals, audio signals, video signals, or combinations thereof. Software may be embodied by or in any computer-readable or signal-holding medium for use with instruction-executable systems, apparatus, or devices. Such a system may include a computer-based system, a system including a processor, or another system capable of selectively fetching instructions from an instruction-executable system, apparatus, or device that can also execute instructions.

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

[0089] The illustrative diagrams of the embodiments described herein are intended to provide a general understanding of the structures of various embodiments. These illustrative diagrams are not intended to serve as a complete description of all elements and features of devices and systems utilizing the structures or methods described herein. Many other embodiments will be apparent to those skilled in the art upon consideration of this disclosure. Other embodiments may be utilized and derived from this disclosure, thereby making structural and logical substitutions and modifications without departing from the scope of this disclosure. Furthermore, the illustrative diagrams are merely representations and may not be drawn to scale. Certain parts in the illustrative diagrams may be exaggerated, while others may be minimized. Therefore, this disclosure and the diagrams should be considered illustrative, not limiting.

[0090] One or more embodiments of this disclosure may be referred to herein individually and / or collectively by the term “invention” for convenience only and without the intention of voluntarily limiting the scope of this application to any particular invention or inventive concept. Furthermore, while certain embodiments are illustrated and described herein, it should be understood that any subsequent configuration designed to achieve the same or similar objectives may be used instead of the specific embodiments shown. This disclosure is intended to cover all possible subsequent adaptations or variations of various embodiments. Combinations of the embodiments described herein, and other embodiments not specifically described herein, will be apparent to those skilled in the art upon consideration of the description.

[0091] The phrase "combined with ~" is defined as meaning directly connected or indirectly connected through one or more intermediate components. Such intermediate components may include both hardware-based and software-based components. Modifications to the arrangement and types of components may be made without departing from the idea or scope of the claims described herein. Additional components, different components, or fewer components may be provided.

[0092] The subject matter disclosed above should be considered illustrative rather than restrictive, 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. Therefore, 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 limited or restricted 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. Therefore, the invention should not be limited except in light of the appended claims and their equivalents.

Claims

1. A method for wireless communication, wherein the method is The user equipment (UE) determines the parameters for adjustment to the maximum output power for a given power class based on a comparison of duty cycles associated with the uplink symbol, In response to the occurrence of at least one event, the UE is triggered to report a Power Headroom Report (PHR). Includes, The PHR includes the parameters, A method wherein the at least one event includes at least one of a first event, which includes the duty cycle being exceeded, or a second event, which includes returning to the given power class.

2. The method according to claim 1, wherein the PHR includes a PHR control element that includes the power headroom available in the UE together with the parameters.

3. The at least one event includes the first event, triggering the PHR with an actual value for the parameter, the actual value including an absolute value; or, The at least one event includes the second event, which triggers the PHR with an actual value for the parameter, the actual value including an absolute value; or, The method according to claim 2, wherein the at least one event includes the legacy event and triggers the PHR with a reserved state for the parameter.

4. The method according to claim 2, wherein, after adjustment for the maximum output power for a given power class, the given power class is returned by the second event for returning to the given power class, or based on a time offset.

5. The parameter is represented by four 2-bit values, including 0 (00), 1 (01), 2 (10), and 3 (11). The aforementioned value 0 (00) is a reserved value, The aforementioned value 1(01) corresponds to the adjustment with respect to the maximum output power which is 0 dB, The aforementioned value 2 (10) corresponds to the adjustment for the maximum output power which is 3 dB, The method according to claim 1, wherein the value 3(11) corresponds to the adjustment for a maximum output power of 6 dB.

6. A user equipment (UE) device, wherein the UE device is Memory for storing instructions, At least one processor for executing the aforementioned instructions and Equipped with, The aforementioned at least one processor is Based on a comparison of duty cycles associated with uplink symbols, the parameters for adjustment to the maximum output power for a given power class are determined. To trigger the reporting of a Power Headroom Report (PHR) in response to the occurrence of at least one event. The UE device is made to perform this, The PHR includes the parameters, The UE device wherein the at least one event includes at least one of a first event, which includes the duty cycle being exceeded, and a second event, which includes returning to the given power class.

7. The UE device according to claim 6, wherein the UE device reports the PHR including a PHR control element that includes power headroom available in the UE, along with the parameters.

8. The at least one event includes the first event, triggering the PHR with an actual value for the parameter, the actual value including an absolute value; or, The at least one event includes the second event, which triggers the PHR with an actual value for the parameter, the actual value including an absolute value; or, The UE device according to claim 7, wherein the at least one event includes the legacy event and triggers the PHR with a reserved state for the parameter.

9. The UE apparatus according to claim 7, wherein, after adjustment to the maximum output power for a given power class, the given power class is returned to the given power class by the second event for returning to the given power class or based on a time offset.

10. The parameter is represented by four 2-bit values, including 0 (00), 1 (01), 2 (10), and 3 (11). The aforementioned value 0 (00) is a reserved value, The aforementioned value 1(01) corresponds to the adjustment with respect to the maximum output power which is 0 dB, The aforementioned value 2 (10) corresponds to the adjustment for the maximum output power which is 3 dB, The UE device according to claim 6, wherein the value 3(11) corresponds to the adjustment for a maximum output power of 6 dB.

11. A base station (BS) device, wherein the BS device is Memory for storing instructions, At least one processor for executing the aforementioned instructions and Equipped with, The at least one processor causes the BS device to receive a power headroom report (PHR) reported by the user equipment (UE). The PHR includes parameters for adjustment to the maximum output power for a given power class, determined by the UE based on a comparison of duty cycles associated with the uplink symbols. The reporting of the aforementioned PHR is triggered in response to the occurrence of at least one event. A BS device in which the at least one event includes at least one of a first event, which includes the duty cycle being exceeded, and a second event, which includes returning to the given power class.

12. The BS device according to claim 11, wherein the BS device receives the PHR, and the PHR includes a PHR control element that includes power headroom available in the UE along with the parameters.

13. The at least one event includes the first event, triggering the PHR with an actual value for the parameter, the actual value including an absolute value; or, The at least one event includes the second event, which triggers the PHR with an actual value for the parameter, the actual value including an absolute value; or, The BS apparatus according to claim 12, wherein the at least one event includes the legacy event and triggers the PHR with a reserved state for the parameter.

14. The BS device according to claim 11, wherein, after adjustment to the maximum output power for a given power class, the given power class is returned to the given power class by the second event for returning to the given power class or based on a time offset.

15. The parameter is represented by four 2-bit values, including 0 (00), 1 (01), 2 (10), and 3 (11). The aforementioned value 0 (00) is a reserved value, The aforementioned value 1(01) corresponds to the adjustment with respect to the maximum output power which is 0 dB, The aforementioned value 2 (10) corresponds to the adjustment for the maximum output power which is 3 dB, The BS device according to claim 11, wherein the value 3(11) corresponds to the adjustment for a maximum output power of 6 dB.

Images