Enabling user equipment to report power class usage

Abstract

Disclosed are systems, methods, apparatuses, and computer program products that enable a user equipment (UE) to report a used power class (PC). The method includes transmitting a message including user equipment capability information to a network element. The method also includes receiving, from the network element in response to the message, a configuration for reporting the power class information or a start timing and a length of the uplink duty cycle evaluation. The method further includes transmitting, in response to the configuration, a report including the power class information or a start timing and a length of the uplink duty cycle evaluation to the network element.

Description

[Technical Field]

[0001] This application claims priority to U.S. Provisional Application No. 63 / 395,510, filed August 5, 2022, which is incorporated herein by reference in its entirety.

[0002] Some exemplary embodiments relate generally to mobile or wireless communication systems, such as Long Term Evolution (LTE), or fifth generation (5G) New Radio (NR) access technologies, or 5G Beyond, or other communication systems. For example, certain exemplary embodiments relate to apparatus, systems, and / or methods for enabling user equipment (UE) to report used power class (PC). [Background technology]

[0003] Examples of mobile communication systems or wireless communication systems may include Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), LTE-Advanced (LTE-A), MultiFire, LTE-A Pro, and / or fifth-generation (5G) radio access technology or New Radio (NR) access technology. A fifth-generation (5G) radio system refers to the next-generation (NG) radio system and network architecture. While most 5G network technologies are based on New Radio (NR) technology, 5G (or NG) networks can also be built on E-UTRAN radio. NR is estimated to provide bit rates of 10–20 Gbit / s or more and support at least enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-based communications (mMTC). NR is expected to enable extremely high bandwidth, ultra-robust low-latency connectivity, and large-scale networking to support the Internet of Things (IoT). Summary of the Invention

[0004] Some example embodiments are directed to a method. The method may include transmitting a message including user equipment capability information to a network element. The method may also include receiving, in response to the message, from the network element, power class information or a configuration for reporting a start timing of an uplink duty cycle evaluation and a length of the uplink duty cycle evaluation. The method may further include, in response to the configuration, transmitting a report to the network element including the power class information or the start timing and length of the uplink duty cycle evaluation.

[0005] Another example embodiment is directed to an apparatus. The apparatus may include at least one processor and at least one memory containing computer program code. The at least one memory and the computer program code may be configured, by the at least one processor, to cause the apparatus to transmit a message including user equipment capability information to a network element. The apparatus may also be configured to receive, from the network element in response to the message, power class information or a configuration for reporting a start timing of an uplink duty cycle evaluation and a length of the uplink duty cycle evaluation. The apparatus may be further configured, in response to the configuration, to transmit a report including the power class information or the start timing and length of the uplink duty cycle evaluation to the network element.

[0006] Another example embodiment is directed to an apparatus. The apparatus may comprise means for transmitting a message including user equipment capability information to a network element. The apparatus may also comprise means for receiving, from the network element in response to the message, power class information or a configuration for reporting a start timing of an uplink duty cycle evaluation and a length of the uplink duty cycle evaluation. The apparatus may further comprise means for transmitting, in response to the configuration, a report including the power class information or the start timing and length of the uplink duty cycle evaluation to the network element.

[0007] In another example embodiment, a non-transitory computer-readable medium may be encoded with instructions that, when executed on hardware, may perform a method. The method may include transmitting a message to a network element including user equipment capability information. The method may also include receiving, from the network element in response to the message, power class information or a configuration for reporting a start timing of an uplink duty cycle evaluation and a length of the uplink duty cycle evaluation. The method may further include, in response to the configuration, transmitting a report to the network element including the power class information or the start timing and length of the uplink duty cycle evaluation.

[0008] Another example embodiment may be directed to a computer program product that performs a method. The method may include transmitting a message to a network element that includes user equipment capability information. The method may also include receiving, in response to the message, from the network element, power class information or a configuration for reporting a start timing of an uplink duty cycle evaluation and a length of the uplink duty cycle evaluation. The method may further include, in response to the configuration, transmitting a report to the network element that includes the power class information or the start timing and length of the uplink duty cycle evaluation.

[0009] Another example embodiment is directed to an apparatus including circuitry configured to measure a wireless altimeter signal at the apparatus. The apparatus may also include circuitry configured to transmit a message to a network element including user equipment capability information. The apparatus may also include circuitry configured to receive, in response to the message, from the network element, power class information or a configuration for reporting a start timing of an uplink duty cycle evaluation and a length of the uplink duty cycle evaluation. The apparatus may further include circuitry configured, in response to the configuration, to transmit a report to the network element including the power class information or the start timing and length of the uplink duty cycle evaluation.

[0010] An example embodiment is directed to a method. The method may include receiving, from a user equipment, a message including user equipment capability information. The method may also include, in response to the message, transmitting, to the user equipment, power class information or a configuration for reporting a start timing of an uplink duty cycle evaluation and a length of the uplink duty cycle evaluation. The method may further include receiving, from the user equipment, a report including the power class information or the start timing and length of the uplink duty cycle evaluation. Furthermore, the method may include scheduling resources for the user equipment based on the report.

[0011] Another example embodiment is directed to an apparatus. The apparatus may include at least one processor and at least one memory containing computer program code. The at least one memory and the computer program code may be configured, by the at least one processor, to cause the apparatus to receive, from a user equipment, a message including user equipment capability information. The apparatus may also be configured to transmit, in response to the message, to the user equipment, power class information or a configuration for reporting a start timing of an uplink duty cycle evaluation and a length of the uplink duty cycle evaluation. The apparatus may further be configured to receive, from the user equipment, a report including the power class information or a start timing and a length of the uplink duty cycle evaluation. The apparatus may further be configured to schedule resources for the user equipment based on the report.

[0012] Another example embodiment is directed to an apparatus. The apparatus may comprise means for receiving, from a user equipment, a message including user equipment capability information. The apparatus may also comprise means for transmitting, in response to the message, to the user equipment, power class information or a configuration for reporting a start timing of an uplink duty cycle evaluation and a length of the uplink duty cycle evaluation. The apparatus may further comprise means for receiving, from the user equipment, a report including the power class information or the start timing and length of the uplink duty cycle evaluation. Furthermore, the apparatus may comprise means for scheduling resources for the user equipment based on the report.

[0013] In another example embodiment, a non-transitory computer-readable medium may be encoded with instructions that, when executed in hardware, may perform a method. The method may include receiving, from a user equipment, a message including user equipment capability information. The method may also include, in response to the message, transmitting to the user equipment, power class information or a configuration for reporting a start timing of an uplink duty cycle evaluation and a length of the uplink duty cycle evaluation. The method may further include receiving, from the user equipment, a report including the power class information or a start timing and length of the uplink duty cycle evaluation. Further, the method may include scheduling resources for the user equipment based on the report.

[0014] Another example embodiment is directed to a computer program product that executes a method. The method may include receiving, from user equipment, a message including user equipment capability information. The method may also include transmitting, in response to the message, to the user equipment, power class information or a configuration for reporting a start timing of an uplink duty cycle evaluation and a length of the uplink duty cycle evaluation. The method may further include receiving, from the user equipment, a report including the power class information or a start timing and length of the uplink duty cycle evaluation. Furthermore, the method may include scheduling resources for the user equipment based on the report.

[0015] Another example embodiment is directed to an apparatus that may include circuitry configured to receive, from user equipment, a message including user equipment capability information. The apparatus may also include circuitry configured to transmit, in response to the message, power class information or a configuration for reporting a start timing and a length of uplink duty cycle evaluation to the user equipment. The apparatus may further include circuitry configured to receive, from the user equipment, a report including the power class information or a start timing and length of uplink duty cycle evaluation. Furthermore, the apparatus may include circuitry configured to schedule resources for the user equipment based on the report. [Brief explanation of the drawings]

[0016] For a proper understanding of the exemplary embodiments, please refer to the accompanying drawings. [Figure 1] FIG. 1 shows an example of the relationship between power class transition and full power mode. [Figure 2] FIG. 2 illustrates an example signal flow diagram according to an exemplary embodiment. [Figure 3] FIG. 3 illustrates an example flow diagram of a method according to an exemplary embodiment. [Figure 4] FIG. 4 illustrates an example flow diagram of another method in accordance with an exemplary embodiment. [Figure 5] FIG. 5 shows a set of devices in an exemplary embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0017] It will be readily understood that the components of certain exemplary embodiments as generally described and illustrated in the figures herein could be arranged and designed in a wide variety of different configurations. Following is a detailed description of several exemplary embodiments of systems, methods, apparatuses, and computer program products for enabling a user equipment (UE) to report a power class (PC) that will be used or that is currently being used.

[0018] The features, structures, or characteristics of the exemplary embodiments described throughout this specification may be combined in any suitable manner in one or more exemplary embodiments. For example, the use of the phrases "particular embodiment," "exemplary embodiment," "some embodiments," or other similar phrases throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment. Thus, the use of the phrases "in particular embodiment," "in exemplary embodiment," "in some embodiments," "in other embodiments," or other similar phrases throughout this specification do not necessarily refer to the same set of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more exemplary embodiments. Furthermore, the terms "cell," "node," "gNB," "network," or other similar terms may be used interchangeably throughout this specification.

[0019] As used herein, "at least one of: " and similar expressions such as "at least one of " mean at least any one of the elements, or at least any two or more of the elements, or at least all of the elements when a list of two or more elements is joined by "and" or "or."

[0020] The 3rd Generation Partnership Project (3GPP®) technical specifications introduce several power classes (PC) higher than the default PC to improve uplink (UL) coverage and capacity. For example, Table 1 shows an example of the definition of PC in Frequency Range 1 (FR1). [Table 1]

[0021] Due to regulatory requirements such as Specific Absorption Rate (SAR), UEs that support a PC higher than the default PC are permitted to fall back to a lower PC up to the FR1 default power class. Furthermore, many UE features are associated with P, and UE behavior may be defined in terms of falling back to a lower PC. However, exactly when a UE should fall back, and when a UE should return from a lower PC to a higher PC, has not previously been considered. Furthermore, without knowledge of the PC status, the network may not know how to handle these features appropriately.

[0022] Many of the UE's capabilities and capabilities may be associated with a UE PC per band or band combination (BC). For example, a single PC may be reported by the UE per band or BC, but the UE may occasionally fall back to a lower PC, returning to the declared PC or a PC between the default PC and the declared (i.e., highest) PC at a given time. However, there is currently no precise definition of when the UE falls back to a lower PC or default PC, or when the UE returns to the declared PC. There may be several conditions under which the UE can fall back, such as the UL duty cycle threshold or P-max in this embodiment. However, the evaluation period for the UL duty cycle is not clearly specified. Therefore, the network cannot know the exact PC being used at a given moment. This may lead to problems, such as the network configuring the UE with certain features associated with a PC even though the UE may not be in the expected PC at that time. As a result, the UE cannot follow instructions provided by the network. Another problem is that the network cannot schedule resources such as resource blocks (RBs) and modulation and coding schemes (MCS) according to the currently used PC, even though some of the UE's radio frequency (RF) performance requirements vary depending on the PC.

[0023] Figure 1 shows an example of the relationship between PC transitions (fallback / return) and full power mode. As shown in Figure 1, other issues may be related to the relationship between PC and the associated ul-FullPowerTransmission. The ul-FullPowerTransmission parameter can include various transmission modes, non-coherent and partially coherent codebook subsets, that can be used to overcome issues in UL codebook-based transmission. This may also be applicable to low-rank transmissions that cannot reach the maximum output power (declared by the UE) using a power scaling mechanism. Consider a UE supporting a PC1.5 (29 decibel milliwatts (dBm)) band for a certain band (e.g., n41). Since PC1.5 for n41 performance requirements was developed assuming the implementation of two 26 dBm-capable PAs, the UE can achieve TPMI=2, i.e.,

number

[0024] When PC1.5 falls back to PC2, the supported ul-FullPwr mode may be different (i.e., ul-FullPwrMode-r16), but the network cannot recognize the currently used PC. Therefore, the network cannot recognize whether the UE can determine which ul-FullPwr mode(s) are applied, and the network may erroneously configure the UE in ul-FullPwrMode1-r16 even if the UE is in PC2 state n41. In this case, if any of the port channel conditions are not good, the network may not configure the UE in ul-FullPwrMode1-r16.

number

number

[0025] Other issues related to the UE's PC per band or per BC can arise in relation to the PC and associated sounding reference signal (SRS) antenna switching. For example, assume a UE supports a PC1.5 (29 dBm) bandwidth for a band (e.g., n41). When the UE is in the PC1.5 state, the network may want to use 2T4R for antenna switching to reduce channel estimation time. On the other hand, the UE may be in the PC2 (26 dBm) state. In this case, if the network continues to configure the UE in 2T4R, the total power from the two antenna ports is limited to 26 dBm, potentially resulting in a power per antenna of 23 dBm or less. If the network knew the UE was in PC2, the network might want to configure the UE in 1T4R, increasing the power per antenna to 26 dBm at the expense of increased switching opportunities.

[0026] Furthermore, issues related to UE PC per band or per BC can arise in the relationship between PC fallback and UL resource allocation. In this case, if a UE falls back to PC2 state, it can continue to use PC2 as long as the percentage is less than or equal to 50%. Furthermore, performance requirements such as additional maximum power reduction (A-MPR), MPR, and maximum sensitivity degradation (MSD) may differ. If the network can recognize that the UE is in PC2 state, it can allocate an UL duty cycle not greater than 50%. This allows the network to avoid a situation in which the UE further falls back to PC3 and schedule / configure the UE with appropriate resources and / or capabilities according to PC2 performance requirements, such as MPR / A-MPR, which are one of the factors. Furthermore, although the network can infer the UE's PC state from the UL duty cycle, it cannot accurately recognize it because the exact evaluation period is not defined to allow flexibility in UE implementation.

[0027] Another issue related to per-band or per-BC UE PCs can arise in the relationship between PC fallback and reference sensitivity. Here, it is sometimes proposed to allow a UE supporting frequency division duplexing (FDD) PC2 bands to autonomously fall back to PC3 if its reference sensitivity is degraded by self-interference within the UE (mainly noise caused by nonlinearities from its own Tx power to its own Rx band), while preventing the network from recognizing the desensitization due to "self-interference." Therefore, if the UE autonomously falls back to PC3 or back to PC2, the network will not know whether the UE is in a PC2 or PC3 state.

[0028] In the context of PC fallback and Tx diversity, further issues may arise related to the UE's PC band per BC. In this case, the UE can indicate as a capability that if a PC2 UE with Tx diversity capability falls back to PC3, one Tx will be used. However, there is no way for the network to know which PC the UE is currently using. Therefore, this function alone may not be useful. Furthermore, P CMAX,f,c It has been pointed out that the power headroom (PHR) provided by CMAX,f,cは , P CMAX,f,c_L and P CMAX,f,c_H The ranges may overlap even if the UE is in different PC states at a given moment.

[0029] One way to solve the above problem is to allow the UE to report the in-use PC status (i.e., the currently in-use PC status) of a band or BC to the network at any instance when the in-use PC changes. However, allowing the UE to autonomously report PC information means that the network needs to reserve specific UL resources for the UE to report PC information, and since changes in PC status do not necessarily occur frequently under certain conditions, valuable UL resources will be used in an inefficient manner.

[0030] Another possible solution to the above problem is for the UE to share with the network the conditions for determining when the UL duty cycle evaluation period begins and its length. In this case, if the UL duty cycle exceeds a predetermined threshold that the UE reports to the network as a UE capability, the UE can fall back to a defined default PC. However, the exact evaluation period and start timing of the evaluation (or trigger event condition) are not specific. If the power is sufficiently low (however, this level may depend on the UE implementation), the UE may be able to meet regulatory requirements such as SAR without any issues and may not need to fall back to the default power class. In this case, the UE may not perform the evaluation at all. Thus, it may be difficult to define a single evaluation period and / or its start timing for the UE to report as a UE capability.

[0031] In view of the above problems, in an exemplary embodiment, a signaling mechanism may be established that allows the network to instruct the UE to report the currently used PC and / or UL duty cycle evaluation start timing and length for a band or BC at a given moment. This reporting may include a network-specified window as well as a frequency of reporting. For example, in a particular exemplary embodiment, a signaling mechanism may be established that allows the network to instruct the UE to report the currently used PC and / or UL duty cycle evaluation start timing and length for a band or BC at a given moment. The reporting may also include a network-specified window of reporting. For example, the window may correspond to a time window during which the UE is allowed to report the PC in use.

[0032] In another exemplary embodiment, the UE can report its UE capabilities to the network, and, if requested by the network, the UE can also report the PC that the UE is currently using and / or the UL duty cycle evaluation period and the length of the UL duty cycle evaluation period for fallback or return depending on the state of the PC.

[0033] According to some example embodiments, the UE may report to the network in terms of the PHR the threshold for triggering the UL duty cycle evaluation as a UE capability.

[0034] In an exemplary embodiment, when the network receives a report from the UE, the network can calculate the UL duty cycle and monitor whether the UL duty cycle exceeds or approaches the reported threshold. In some exemplary embodiments, the threshold may be reported by the UE to the network as one of the UE capabilities in the maxUplinkDutyCycle-PC2-FR1 parameter. According to certain exemplary embodiments, if the network determines that the UL duty cycle exceeds the threshold, the network can further consider how much power is remaining by utilizing PHR information, at which point the network may not initiate and monitor the UL duty cycle. Alternatively, if there is not much power remaining (i.e., a small amount of available power) and the PHR is approximately remaining, the network may initiate and monitor the UL duty cycle. Thus, in certain exemplary embodiments, from the calculation and monitoring of the UL duty cycle and / or the PHR information, the network may be able to estimate when the UE should change its PC. The network can then reduce the number of requests to the UE to report its PC.

[0035] In another exemplary embodiment, when the network receives a report from the UE, the network can calculate and monitor the UL duty cycle in a conservative manner (e.g., in response to PHR information) when there is not much power remaining (i.e., when the amount of available power is small). For example, the UL duty cycle may be calculated and monitored by sliding an evaluation window. According to certain exemplary embodiments, calculating and monitoring the UL duty cycle in a conservative manner may include calculating the UL duty cycle at a minimum evaluation period (e.g., one radio symbol) and / or taking a threshold in terms of PHR in a relaxed way (i.e., when the amount of available power may not be small). Furthermore, with respect to sliding the evaluation window, a window of one radio frame with m indices can be assumed, where each radio frame contains n symbols. The duty cycle can be calculated for each radio frame after sliding one symbol.

[0036] According to example embodiments, the network can report the PC currently used by the UE or the UL duty cycle evaluation start timing and its length as assistance information. According to some example embodiments, the UL duty cycle evaluation start timing and its length may be required because the PC reported by the UE may not still be the previous PC, but may be changing or may be changing as the UE evaluates the need for fallback or return. With such information, the network can more accurately predict when fallback / return will occur if a threshold is met and aperiodically request a PC from the UE as needed.

[0037] FIG. 2 shows an exemplary signal flow diagram in an exemplary embodiment. In a particular exemplary embodiment, the functions illustrated in FIG. 2 may be performed by an apparatus similar to one of apparatuses 10 or 20 illustrated in FIG. 5. At 200, the UE may send a report to the gNB, which may include UE capability information indicating that the UE supports reporting of its PC and / or evaluation period / start timing / evaluation trigger threshold. At 205, the gNB may determine whether to configure the UE with a particular capability, taking into account the UL duty cycle ratio and / or PHR status. In a particular exemplary embodiment, the PHR may be reported independently of the PC declared as a UE capability, and the PC may be reported according to the capability for which the UE is configured. At 210, the gNB may configure the UE to report the PC and / or UL duty cycle evaluation start timing and its length currently used by the UE. In a particular exemplary embodiment, the UE may report this information according to configuration by the gNB via radio resource control (RRC).

[0038] As further shown in FIG. 2, at 215, the UE may send a response to the gNB confirming the configuration provided by the gNB. At 220, the UE may determine that the condition is met. That is, in certain exemplary embodiments, if evaluation is not initiated, the UE may not need to report anything. Only the UE can recognize the condition; the network may inquire of the UE whether evaluation has been initiated or whether the PC has already changed, and the UE may then report such information to the network. At 225, the UE may also send a scheduling request (SR) to the gNB for an UL grant that the UE can use for data transmission. At 230, the gNB may determine whether to grant an UL grant to the UE based on the received scheduling request, taking into account the UL duty cycle ratio and / or PHR status. At 235, the gNB may send the UL grant to the UE via a physical downlink control channel (PDCCH). At 240, in response to the UL grant, the UE may send to the gNB a report of the PC currently used by the UE and / or the UL duty cycle evaluation start timing and its length. In certain exemplary embodiments, the declared PC may be reported as a UE capability. At 245, the gNB may schedule resources for the UE according to the received report.

[0039] 3 illustrates an exemplary flow diagram of a method in a particular exemplary embodiment. In an exemplary embodiment, the method of FIG. 3 may be performed by a network entity or a group of network elements in a 3GPP system, such as LTE or 5G-NR. For example, in an exemplary embodiment, the method of FIG. 3 may be performed by a UE similar to one of the devices 10 or 20 shown in FIG. 5.

[0040] According to certain example embodiments, the method of Figure 3 may include, at 300, transmitting a message including user equipment capability information to a network element. The method may also include, at 305, receiving, from the network element in response to the message, power class information or a configuration for reporting a start timing of an uplink duty cycle evaluation and a length of the uplink duty cycle evaluation. The method may further include, at 310, transmitting, in response to the configuration, a report including the power class information or a start timing and length of the uplink duty cycle evaluation to the network element.

[0041] According to example embodiments, the method may also include transmitting to the network element an evaluation threshold in the power headroom value for triggering an uplink duty cycle evaluation. According to some example embodiments, the method may further include receiving a configuration of user equipment capabilities in response to the power class information or the start timing and length of the uplink duty cycle evaluation. According to other example embodiments, the method may also include receiving a resource grant allocation for data transmission in response to the power class information or the start timing and length of the uplink duty cycle evaluation.

[0042] 4 illustrates an example flow diagram of another method in accordance with certain exemplary embodiments. In an exemplary embodiment, the method of FIG. 4 may be performed by a network entity or a group of network elements in a 3GPP system, such as LTE or 5G-NR. For example, in an exemplary embodiment, the method of FIG. 4 may be performed by a gNB, a network, a cell, or any other device similar to one of devices 10 or 20 shown in FIG. 5.

[0043] According to certain exemplary embodiments, the method of FIG. 4 may include, at 400, receiving a message from user equipment including user equipment capability information. The method may also include, at 405, transmitting to the user equipment, in response to the message, power class information or a configuration for reporting a start timing of an uplink duty cycle evaluation and a length of the uplink duty cycle evaluation. The method may further include, at 410, receiving from the user equipment a report including the power class information or a start timing and length of an uplink duty cycle evaluation. Further, the method may include, at 415, scheduling resources for the user equipment based on the report.

[0044] According to an exemplary embodiment, the method may also include receiving, from the user equipment, an evaluation threshold value for the power headroom value for triggering an uplink duty cycle evaluation. According to some exemplary embodiments, the resource may include a configuration for a user equipment capability or a resource grant allocation for data transmission. In an exemplary embodiment, the UL grant may include an MCS and a number of RBs for the data transmission. In further exemplary embodiments, the resource grant allocation may correspond to a resource grant allocation (i.e., an allocation of DL resources for transmitting a PDCCH to the UE). That is, it may correspond to a grant of (radio) resource allocation for data transmission. According to other exemplary embodiments, the method may further include determining whether the uplink duty cycle evaluation exceeds a predetermined threshold value. In an exemplary embodiment, based on the determination, the method may further include starting or stopping monitoring of the uplink duty cycle. In other exemplary embodiments, based on the determination, the method may further include determining the uplink duty cycle at a minimum evaluation period or by taking the threshold value in a relaxed manner with respect to the power headroom value.

[0045] 5 illustrates a set of devices 10 and 20 in a particular exemplary embodiment. In a particular exemplary embodiment, device 10 may be an element in a communication network or associated with such a network, such as a UE, mobile equipment (ME), mobile station, mobile device, fixed device, IoT device, or other device. Note that one skilled in the art will understand that device 10 may include components or features not illustrated in FIG. 5.

[0046] In some exemplary embodiments, device 10 may include one or more processors, one or more computer-readable storage media (e.g., memory, storage, etc.), one or more wireless access components (e.g., modems, transceivers, etc.), and / or a user interface. In some exemplary embodiments, device 10 may be configured to operate using one or more wireless access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MultiFire, and / or any other wireless access technology. Note that one skilled in the art may understand that device 10 may include components or features not shown in FIG. 5 .

[0047] As in the example of FIG. 5 , device 10 may include or be connected to processor 12 for processing information and executing instructions or operations. Processor 12 may be any type of general-purpose or special-purpose processor. Indeed, processor 12 may include, by way of example, one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture. While a single processor 12 is shown in FIG. 5 , multiple processors may be utilized according to other exemplary embodiments. For example, it should be understood that in certain exemplary embodiments, device 10 may include two or more processors that may form a multiprocessor system capable of supporting multiprocessing (e.g., processor 12 in this example represents a multiprocessor). According to certain exemplary embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0048] Processor 12 may perform functions related to the operation of device 10, including, as some examples, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming communication messages, formatting of information, and overall control of device 10, including the processes shown in Figures 1-4.

[0049] The device 10 may further include or be connected to a memory 14 (internal or external) that may be coupled to the processor 12 for storing information and instructions that may be executed by the processor 12. The memory 14 may be one or more memories and may be of any type suitable for the local application environment and may be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. For example, the memory 14 may be comprised of any combination of random access memory (RAM), read-only memory (ROM), static storage devices such as magnetic or optical disks, hard disk drives (HDDs), or any other type of non-transitory machine- or computer-readable medium. The instructions stored in the memory 14 may include program instructions or computer program code that, when executed by the processor 12, enable the device 10 to perform the tasks described herein.

[0050] In certain exemplary embodiments, device 10 may further include or be connected (internal or external) to a drive or port configured to accept and read an external computer-readable storage medium, such as an optical disk, a USB drive, a flash drive, or any other storage medium. For example, the external computer-readable storage medium may store computer programs or software for execution by processor 12 and / or device 10 to perform any of the methods shown in FIGS. 1-4.

[0051] In some demonstrative embodiments, device 10 also includes or is connected to one or more antennas 15 for receiving downlink signals and for transmitting from device 10 over the UL. Device 10 may further include a transceiver 18 configured to transmit and receive information. Transceiver 18 may also include a radio interface (e.g., a modem) coupled to antenna 15. The radio interface may support multiple radio access technologies, including one or more of GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, etc. The radio interface may include other components, such as filters, converters (e.g., digital-to-analog converters, etc.), symbol demappers, signal shaping components, inverse fast Fourier transform (IFFT) modules, etc., for processing symbols, such as OFDMA symbols, carried by the downlink or UL.

[0052] For example, transceiver 18 may be configured to modulate information onto a carrier waveform for transmission by antenna 15 and demodulate information received via antenna 15 for further processing by other elements of device 10. In other exemplary embodiments, transceiver 18 may directly transmit and receive signals or data. Additionally or alternatively, in exemplary embodiments, device 10 may include input and / or output devices (I / O devices). In exemplary embodiments, device 10 may further include a user interface, such as a graphical user interface or a touch screen.

[0053] In exemplary embodiments, memory 14 stores software modules that provide functionality when executed by processor 12. The modules may include, for example, an operating system that provides operating system functionality for device 10. The memory may also store one or more functional modules, such as applications or programs, for providing additional functionality to device 10. Components of device 10 may be implemented as hardware or any suitable combination of hardware and software. According to certain exemplary embodiments, device 10 may be configured to communicate with device 20 via a wireless or wired communication link 70, optionally according to any radio access technology, such as NR.

[0054] According to exemplary embodiments, the processor 12 and memory 14 may be included in or form part of processing or control circuitry. Additionally, the transceiver 18 in some exemplary embodiments may be included in or form part of transceiver circuitry.

[0055] For example, in an exemplary embodiment, apparatus 10 may be controlled by memory 14 and processor 12 to send a message including user equipment capability information to a network element. Apparatus 10 may also be controlled by memory 14 and processor 12 to receive, from the network element in response to the message, power class information or a configuration for reporting a start timing of an uplink duty cycle evaluation and a length of the uplink duty cycle evaluation. Apparatus 10 may further be controlled by memory 14 and processor 12 to send, in response to the configuration, a report including the power class information or a start timing and length of an uplink duty cycle evaluation to the network element.

[0056] As shown in the example of Figure 5, the device 20 may be a network, a core network element, or an element in a communications network or an element associated with such a network, such as a gNB. It should be noted that a person skilled in the art may understand that the device 20 may include components or features not shown in Figure 5.

[0057] As in the example of FIG. 5, device 20 may include a processor 22 for processing information and executing instructions or operations. Processor 22 may be any type of general-purpose or special-purpose processor. For example, processor 22 may include, by way of example, one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture. While a single processor 22 is shown in FIG. 5, multiple processors may be utilized according to other exemplary embodiments. For example, it should be understood that in certain exemplary embodiments, device 20 may include two or more processors that may form a multiprocessor system capable of supporting multiprocessing (e.g., processor 22 in this example represents a multiprocessor). In the exemplary embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0058] According to certain exemplary embodiments, processor 22 may perform functions related to the operation of device 20, including, for example, precoding antenna gain / phase parameters, encoding and decoding individual bits forming communication messages, formatting information, and overall control of device 20, including the processes illustrated in FIGS. 1-4.

[0059] The device 20 may further include or be connected to a memory 24 (internal or external) that may be coupled to the processor 22 for storing information and instructions that may be executed by the processor 22. The memory 24 may be one or more memories and may be of any type suitable for the local application environment and may be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. For example, the memory 24 may be comprised of any combination of random access memory (RAM), read-only memory (ROM), static storage devices such as magnetic or optical disks, hard disk drives (HDDs), or any other type of non-transitory machine- or computer-readable medium. The instructions stored in the memory 24 may include program instructions or computer program code that, when executed by the processor 22, enable the device 20 to perform tasks as described herein.

[0060] In certain exemplary embodiments, device 20 may further include or be connected (internal or external) to a drive or port configured to accept and read an external computer-readable storage medium, such as an optical disk, a USB drive, a flash drive, or any other storage medium. For example, the external computer-readable storage medium may store computer programs or software for execution by processor 22 and / or device 20 to perform the methods illustrated in FIGS. 1-4.

[0061] In an exemplary embodiment, device 20 may also include or be connected to one or more antennas 25 for transmitting and receiving signals and / or data to and from device 20. Device 20 may further include or be connected to a transceiver 28 configured to transmit and receive information. Transceiver 28 may include, for example, multiple wireless interfaces that may be connected to antenna(s) 25. The wireless interfaces may support multiple wireless access technologies, including one or more of GSM, NB-IoT, LTE, 5G, WLAN, Bluetooth, BT-LE, NFC, radio frequency identifier (RFID), ultra-wideband (UWB), MulteFire, etc. The wireless interfaces may include components such as filters, converters (e.g., digital-to-analog converters, etc.), mappers, fast Fourier transform (FFT) modules, etc., for generating symbols for transmission over one or more downlinks and receiving symbols (e.g., over the UL).

[0062] Thus, transceiver 28 may be configured to modulate information onto a carrier waveform for transmission by antenna 25, and to demodulate information received via antenna 25 for further processing by other elements of device 20. In other exemplary embodiments, transceiver 18 may transmit and receive signals or data directly. Additionally or alternatively, in exemplary embodiments, device 20 may include input and / or output devices (I / O devices).

[0063] In an exemplary embodiment, memory 24 may store software modules that provide functionality when executed by processor 22. The modules may include, for example, an operating system that provides operating system functionality for device 20. The memory may also store one or more functional modules, such as applications or programs, for providing additional functionality to device 20. Components of device 20 may be implemented in hardware or any suitable combination of hardware and software.

[0064] In some exemplary embodiments, the processor 22 and memory 24 may be included in or form part of processing or control circuitry. Further, in some exemplary embodiments, the transceiver 28 may be included in or form part of transceiver circuitry.

[0065] As used herein, the term "circuitry" may refer to a hardware-only circuit implementation (e.g., analog and / or digital circuitry), a combination of hardware circuitry and software, a combination of analog and / or digital hardware circuitry and software / firmware, any portion of a hardware processor having software (including a digital signal processor) that cooperates to cause a device (e.g., devices 10 and 20) to perform various functions, and / or a hardware circuit and / or processor, or portion thereof, that uses software for operation but may be absent if not necessary for operation. As a further example, the term "circuitry" in this embodiment may also cover simply a hardware circuit or processor (or multiple processors), or a portion of a hardware circuit or processor, and its associated software and / or firmware implementation. The term circuitry may also cover, for example, a baseband integrated circuit in a server, a cellular network node or device, or other computing or network device.

[0066] For example, in an exemplary embodiment, apparatus 20 may be controlled by memory 24 and processor 22 to receive a message from a user equipment including user equipment capability information. Apparatus 20 may also be controlled by memory 24 and processor 22 to transmit, in response to the message, power class information or configuration for reporting a start timing and a length of an uplink duty cycle evaluation to the user equipment. Apparatus 20 may further be controlled by memory 24 and processor 22 to receive, from the user equipment, a report including the power class information or a start timing and a length of an uplink duty cycle evaluation. Apparatus 20 may further be controlled by memory 24 and processor 22 to schedule resources for the user equipment based on the report.

[0067] In some exemplary embodiments, an apparatus (e.g., apparatus 10 and / or apparatus 20) may comprise means for performing any of the methods, processes, or variations described herein. Examples of means may include one or more processors, memories, controllers, transmitters, receivers, and / or computer program code for performing the operations.

[0068] Certain example embodiments are directed to an apparatus comprising means for performing any of the methods described herein, including, for example, means for transmitting a message to a network element including user equipment capability information. The apparatus may also comprise means for receiving, from the network element in response to the message, power class information or a configuration for reporting a start timing of an uplink duty cycle evaluation and a length of the uplink duty cycle evaluation. The apparatus may further comprise means for transmitting, in response to the configuration, a report to the network element including the power class information or the start timing and length of the uplink duty cycle evaluation.

[0069] Certain example embodiments are directed to an apparatus comprising means for receiving, from a user equipment, a message including user equipment capability information. The apparatus may also comprise means for transmitting, in response to the message, to the user equipment, power class information or a configuration for reporting a start timing and a length of an uplink duty cycle evaluation. The apparatus may further comprise means for receiving, from the user equipment, a report including the power class information or a start timing and a length of an uplink duty cycle evaluation. Furthermore, the apparatus may comprise means for scheduling resources for the user equipment based on the report.

[0070] Certain exemplary embodiments described herein provide several technical improvements, enhancements, and / or advantages. For example, in some exemplary embodiments, a signaling mechanism may be established that allows the network to instruct the UE to report the in-use PC and / or UL duty cycle evaluation start timing and length for a band or BC at a given time. In certain exemplary embodiments, the reporting may include the frequency of reporting as well as a network-specified window. In other exemplary embodiments, the network may be provided with the UE's accurate PC status and may be provided with such information in a more efficient manner.

[0071] The computer program product may include one or more computer-executable components configured to perform the exemplary embodiments when the program is executed. The one or more computer-executable components may be at least one software code or a portion thereof. The modifications and configurations required to perform the functionality of a particular exemplary embodiment may be implemented as a routine(s) or as additional or updated software routine(s). The software routines may be downloaded to the device.

[0072] By way of example, the software or computer program code, or portions thereof, may be in source code form, object code form, or any intermediate form, and may be stored on any carrier, distribution medium, or computer-readable medium, which may be any entity or device capable of carrying a program. Such carriers include, for example, recording media, computer memory, read-only memory, optical-electrical and / or electrical carrier signals, telecommunications signals, software distribution packages, and the like. Depending on the processing power required, the computer program may be executed in a single electronic digital computer or distributed across many computers. The computer-readable medium or computer-readable storage medium may be a non-transitory medium.

[0073] In other exemplary embodiments, the functions may be performed by hardware or circuitry included in a device (e.g., device 10 or device 20), for example, through the use of an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software. In yet other exemplary embodiments, the functions may be implemented as signals that are non-tangible means that may be conveyed by electromagnetic signals downloaded from the internet or other network.

[0074] According to certain exemplary embodiments, an apparatus such as a node, device, or corresponding component may be configured as a circuit, computer, or microprocessor such as a single-chip computer element, or as a chipset including at least a memory for providing storage capacity used for computational processing and a computational processor for performing computational processing.

[0075] Those skilled in the art will readily appreciate that the present disclosure as described above may be implemented using a different order of steps and / or hardware elements in different configurations than those disclosed. Thus, while the present disclosure has been described based on these exemplary embodiments, it will be apparent to those skilled in the art that certain modifications, variations, and alternative configurations will be apparent while remaining within the spirit and scope of the exemplary embodiments. Although the above embodiments are also referred to as 5G NR and LTE technologies, the above embodiments may also be applied to any other current or future 3GPP technologies, such as LTE-Advanced and / or fourth generation (4G) technologies.

[0076] Part of the glossary 3GPP (registered trademark) 3rd Generation Partnership Project 5G (5th Generation) 5GCN 5G Core Network 5GS 5G System A-MPR Additional Maximum Power Reduction BC band combination BS base station CPE Customer Premises Equipment DL Downlink eNB Enhanced Node B E-UTRAN Evolved UTRAN FDD Frequency Division Duplex FR Frequency Range gNB 5G or Next Generation Node B HPUE High Power UE LTE Long Term Evolution MCS modulation and coding scheme MPR maximum power reduction MSD maximum sensitivity degradation NR new radio NW Network PC Power Class PHR Power Headroom RRC Radio Resource Control Rx reception SAR Specific Absorption Rate TDD Time Division Duplex Tx transmission UE User Equipment UL Uplink

Claims

1. sending a message to a network element containing capability information of the user equipment; receiving, in response to the message, from the network element, a configuration for reporting power class information or a start timing of an uplink duty cycle evaluation and a length of the uplink duty cycle evaluation; sending a report to the network element based on the configuration, the report including the power class information or the start timing and the length of the uplink duty cycle evaluation; A method comprising:

2. transmitting to the network element an evaluation threshold value for a power headroom value for triggering the uplink duty cycle evaluation; The method of claim 1 further comprising:

3. receiving a configuration of a user equipment capability in response to the power class information or the start timing and the length of the uplink duty cycle evaluation; 3. The method of claim 1 or 2, further comprising:

4. receiving a resource grant allocation for data transmission in response to the power class information or the start timing and the length of the uplink duty cycle evaluation; The method of any one of claims 1 to 3, further comprising:

5. sending a response to the network element confirming the received configuration; The method of any one of claims 1 to 4, further comprising:

6. determining that at least one condition is satisfied; the report is sent if the at least one condition is met.

6. The method according to any one of claims 1 to 5.

7. sending a scheduling request to the network element if the at least one condition is met; and receiving an uplink grant from the network element; further comprising the report being transmitted in response to receiving the uplink grant. The method of claim 6.

8. 1. An apparatus comprising: at least one processor; at least one memory containing computer program code; Equipped with The at least one memory and the computer program code, when executed by the at least one processor, cause the device to perform at least: sending a message to a network element containing user equipment capability information; receiving, from the network element in response to the message, power class information or a configuration for reporting a start timing of an uplink duty cycle evaluation and a length of the uplink duty cycle evaluation; sending a report to the network element based on the configuration, the report including the power class information or the start timing and the length of the uplink duty cycle evaluation; An apparatus configured to cause the

9. The at least one memory and the computer program code, when executed by the at least one processor, cause the device to perform at least: transmitting to the network element an evaluation threshold value for a power headroom value for triggering the uplink duty cycle evaluation; The apparatus of claim 8 , further configured to cause the execution of:

10. The at least one memory and the computer program code, when executed by the at least one processor, cause the device to perform at least: receiving a configuration of a user equipment capability in response to the power class information or the start timing and the length of the uplink duty cycle evaluation; The apparatus of claim 8 , further configured to cause the execution of:

11. The at least one memory and the computer program code, when executed by the at least one processor, cause the device to perform at least: receiving a resource grant allocation for data transmission in response to the power class information or the start timing and the length of the uplink duty cycle evaluation; The apparatus of claim 8 , further configured to cause the execution of:

12. The at least one memory and the computer program code, when executed by the at least one processor, cause the device to perform at least: sending a response to the network element confirming the received configuration; The apparatus of claim 8 , further configured to cause the execution of:

13. The at least one memory and the computer program code, when executed by the at least one processor, cause the device to perform at least: determining that at least one condition is satisfied; and further configured to cause execution of the report is sent if the at least one condition is met.

9. The apparatus of claim 8.

14. The at least one memory and the computer program code, when executed by the at least one processor, cause the device to perform at least: sending a scheduling request to the network element if the at least one condition is met; and receiving an uplink grant from the network element; and further configured to cause execution of the report being transmitted in response to receiving the uplink grant.

9. The apparatus of claim 8.

15. 1. An apparatus comprising: at least one processor; at least one memory containing computer program code; Equipped with The at least one memory and the computer program code, when executed by the at least one processor, cause the device to perform at least: receiving a message from a user equipment including user equipment capability information; transmitting, in response to the message, to the user equipment, power class information or a configuration for reporting a start timing of an uplink duty cycle evaluation and a length of the uplink duty cycle evaluation; receiving from the user equipment a report including the power class information or the start timing and the length of the uplink duty cycle evaluation; scheduling resources for the user equipment based on the report; An apparatus configured to cause the

16. The at least one memory and the computer program code, when executed by the at least one processor, cause the device to perform at least: receiving, from the user equipment, an evaluation threshold value for a power headroom value for triggering the uplink duty cycle evaluation; The apparatus of claim 15 , further configured to cause the execution of:

17. The resource is: Configuring user equipment features, or resource grant allocation for data transmission; 16. The apparatus of claim 15, comprising:

18. The at least one memory and the computer program code, when executed by the at least one processor, cause the device to perform at least: determining whether the uplink duty cycle estimate exceeds a predetermined threshold; The apparatus of claim 15 , further configured to cause the execution of:

19. Based on the determination, the at least one memory and the computer program code, when executed by the at least one processor, store instructions that cause the device to at least: Starting or stopping monitoring of the uplink duty cycle; 20. The apparatus of claim 18, further configured to cause:

20. Based on the determination, the at least one memory and the computer program code, when executed by the at least one processor, store instructions that cause the device to at least: determining an uplink duty cycle at a minimum evaluation period or by taking a relaxed threshold on a power headroom value; 20. The apparatus of claim 18, further configured to cause:

21. receiving a message from a user equipment including user equipment capability information; transmitting, in response to the message, to the user equipment, power class information or a configuration for reporting a start timing of an uplink duty cycle evaluation and a length of the uplink duty cycle evaluation; receiving from the user equipment a report including the power class information or the start timing and the length of the uplink duty cycle evaluation; scheduling resources for the user equipment based on the report; A method comprising:

22. receiving, from the user equipment, an evaluation threshold value for a power headroom value for triggering the uplink duty cycle evaluation; 22. The method of claim 21 further comprising:

23. The resource is: Configuring user equipment features, or resource grant allocation for data transmission; 23. The method of claim 21 or 22, comprising:

24. determining whether the uplink duty cycle estimate exceeds a predetermined threshold; 24. The method of any of claims 21 to 23, further comprising:

25. Based on the above determination, Starting or stopping monitoring of the uplink duty cycle; 25. The method of claim 24, further comprising:

26. Based on the above determination, determining an uplink duty cycle at a minimum evaluation period or by relaxing a threshold on a power headroom value; 25. The method of claim 24, further comprising:

27. means for transmitting a message containing user equipment capability information to a network element; means for receiving, in response to the message, from the network element, power class information or a configuration for reporting a start timing of an uplink duty cycle evaluation and a length of the uplink duty cycle evaluation; means for transmitting a report to the network element based on the configuration, the report including the power class information or the start timing and the length of the uplink duty cycle evaluation; An apparatus comprising:

28. means for transmitting an evaluation threshold value for a power headroom value to the network element to trigger the uplink duty cycle evaluation; 28. The apparatus of claim 27, further comprising:

29. means for receiving a user equipment capability configuration in response to the power class information or the start timing and the length of the uplink duty cycle evaluation; 29. The apparatus of claim 27 or 28, further comprising:

30. means for receiving a resource grant allocation for data transmission in response to the power class information or the start timing and the length of the uplink duty cycle evaluation; 30. The apparatus of any of claims 27 to 29, further comprising:

31. means for receiving, from a user equipment, a message including user equipment capability information; means for transmitting, in response to the message, to the user equipment, power class information or a configuration for reporting a start timing of an uplink duty cycle evaluation and a length of the uplink duty cycle evaluation; means for receiving from the user equipment a report including the power class information or the start timing and the length of the uplink duty cycle evaluation; means for scheduling resources of the user equipment based on the report; An apparatus comprising:

32. means for receiving from the user equipment an evaluation threshold value for a power headroom value to trigger the uplink duty cycle evaluation; 32. The apparatus of claim 31, further comprising:

33. The resource is: Configuring user equipment features, or resource grant allocation for data transmission; 33. The apparatus of claim 31 or 32, comprising at least one of:

34. means for determining whether the uplink duty cycle estimate exceeds a predetermined threshold; 34. The apparatus of any of claims 31 to 33, further comprising:

35. means for starting or stopping monitoring of an uplink duty cycle based on said determining; 35. The apparatus of claim 34, further comprising:

36. means for determining an uplink duty cycle based on said determining, at a minimum evaluation period or by relaxing a threshold on a power headroom value; 36. The apparatus of claim 34 or 35, further comprising:

Images