Implementation of reporting of power consumption classes by user equipment.

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 the priority of U.S. Provisional Application No. 63 / 395,510, filed on August 5, 2022, the entire content of which is incorporated herein by reference.

[0002] Some exemplary embodiments generally relate to mobile or wireless communication systems such as Long-Term Evolution (LTE), or 5th Generation (5G) New Radio (NR) access technology, or 5G Beyond, or other communication systems. For example, certain exemplary embodiments relate to an apparatus, system, and / or method for enabling a user equipment (UE) to report the power class (PC) used.

Background Art

[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 5th Generation (5G) wireless access technology, or New Radio (NR) access technology. The 5th Generation (5G) wireless system refers to the next generation (NG) wireless system and network architecture. Most 5G network technologies are based on New Radio (NR) technology, but 5G (or NG) networks can also be built based on E-UTRAN radio. NR is expected to provide bitrates of 10 to 20 Gbit / s or more and support at least enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC). NR is expected to enable extremely wideband and ultra-robust low-latency connections and massive networking to support the Internet of Things (IoT).

Summary of the Invention

[0004] Several exemplary embodiments relate to the method. The method may include sending a message containing user equipment capability information to a network element. The method may also include receiving from the network element in response to the message power class information or a setting to report the start timing and length of the uplink duty cycle evaluation. The method may further include sending a report to the network element in response to the setting, containing power class information or the start timing and length of the uplink duty cycle evaluation.

[0005] Other exemplary embodiments relate to a device, which may comprise 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 at least one processor, to cause the device to send messages containing user equipment capability information to a network element. The device may also be configured to receive from the network element, in response to the messages, power class information or settings to report the start timing and length of the uplink duty cycle evaluation. The device may further be configured to send to the network element, in response to the settings, a report containing power class information or the start timing and length of the uplink duty cycle evaluation.

[0006] Other exemplary embodiments relate to a device. This device may include means for sending a message containing user equipment capability information to a network element. The device may also include means for receiving from the network element, in response to the message, power class information or settings for reporting the start timing and length of the uplink duty cycle evaluation. The device may further include means for sending a report to the network element, in response to the settings, containing power class information or the start timing and length of the uplink duty cycle evaluation.

[0007] In other exemplary embodiments, a non-transient computer-readable medium may be encoded with instructions that, when executed in hardware, can perform the method. The method may include sending a message containing user equipment capability information to a network element. The method may also include receiving from the network element in response to the message power class information or a setting to report the start timing and length of the uplink duty cycle evaluation. The method may further include sending a report to the network element in response to the setting, containing power class information or the start timing and length of the uplink duty cycle evaluation.

[0008] Other exemplary embodiments may be directed to a computer program product that performs the method. The method may include sending a message containing user equipment capability information to a network element. The method may also include receiving from the network element in response to the message power class information or settings to report the start timing and length of the uplink duty cycle evaluation. The method may further include sending a report to the network element in response to the settings, containing power class information or the start timing and length of the uplink duty cycle evaluation.

[0009] Other exemplary embodiments relate to a device that includes circuitry configured to measure a radio altimeter signal. The device may also include circuitry configured to transmit a message containing user equipment capability information to a network element. The device may also include circuitry configured to receive from the network element, in response to the message, power class information or settings to report the start timing and length of the uplink duty cycle evaluation. The device may further include circuitry configured to transmit a report to the network element, in response to the settings, containing power class information or the start timing and length of the uplink duty cycle evaluation.

[0010] Exemplary embodiments relate to the method. The method may include receiving a message from user equipment containing user equipment capability information. The method may also include, in response to the message, sending to the user equipment settings for reporting power class information or the start timing and length of the uplink duty cycle evaluation. The method may further include receiving a report from the user equipment containing power class information or the start timing and length of the uplink duty cycle evaluation. Furthermore, the method may include scheduling the user equipment's resources based on the report.

[0011] Other exemplary embodiments relate to a device, which 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 at least one processor to cause the device to receive messages from user equipment containing user equipment capability information. The device may also be configured to respond to messages by sending settings to the user equipment to report power class information or the start timing and length of the uplink duty cycle evaluation. The device may further be configured to receive reports from the user equipment containing power class information or the start timing and length of the uplink duty cycle evaluation. The device may further be configured to schedule the user equipment's resources based on the reports.

[0012] Other exemplary embodiments relate to the apparatus. The apparatus may include means for receiving messages from user equipment, including user equipment capability information. The apparatus may also include means for transmitting to the user equipment, in response to the messages, settings for reporting power class information or the start timing and length of the uplink duty cycle evaluation. The apparatus may further include means for receiving reports from user equipment, including power class information or the start timing and length of the uplink duty cycle evaluation. Furthermore, the apparatus may include means for scheduling the user equipment's resources based on the reports.

[0013] In other exemplary embodiments, a non-transient computer-readable medium, when executed in hardware, may be encoded with instructions that enable the method to be executed. The method may include receiving a message from user equipment containing user equipment capability information. The method may also include, in response to the message, sending to the user equipment settings for reporting power class information or the start timing and length of the uplink duty cycle evaluation. The method may further include receiving a report from the user equipment containing power class information or the start timing and length of the uplink duty cycle evaluation. Furthermore, the method may include scheduling the user equipment's resources based on the report.

[0014] Other exemplary embodiments relate to computer program products that perform the method. The method may include receiving a message from user equipment containing user equipment capability information. The method may also include, in response to the message, sending to the user equipment settings to report power class information or the start timing and length of the uplink duty cycle evaluation. The method may further include receiving a report from the user equipment containing power class information or the start timing and length of the uplink duty cycle evaluation. Furthermore, the method may include scheduling the resources of the user equipment based on the report.

[0015] Other exemplary embodiments relate to a device that may include circuitry configured to receive a message from user equipment containing user equipment capability information. The device may also include circuitry configured to send to the user equipment, in response to the message, power class information or settings to report the start timing and length of the uplink duty cycle evaluation. The device may further include circuitry configured to receive a report from the user equipment containing power class information or the start timing and length of the uplink duty cycle evaluation. Furthermore, the device may include circuitry configured to schedule the user equipment's resources based on the report. [Brief explanation of the drawing]

[0016] Please refer to the attached drawings for a proper understanding of the exemplary embodiments. [Figure 1] Figure 1 shows an example of the relationship between power class transitions and full power mode. [Figure 2] Figure 2 shows an example of a signal flow diagram according to an exemplary embodiment. [Figure 3] Figure 3 shows an example of a flowchart of the method according to an exemplary embodiment. [Figure 4] Figure 4 shows an example of a flowchart for another method in an exemplary embodiment. [Figure 5] Figure 5 shows a set of devices in an exemplary embodiment. [Modes for carrying out the invention]

[0017] It will be readily apparent that components of certain exemplary embodiments, as generally described and illustrated in the figures of this embodiment, can be arranged and designed in a wide variety of different configurations. The following is a detailed description of some exemplary embodiments of systems, methods, apparatus, and computer program products for enabling user equipment (UE) to report the power class (PC) to be used, or the PC currently in use.

[0018] The features, structures, or characteristics of the exemplary embodiments described throughout this specification may be combined in any suitable way in one or more exemplary embodiments. For example, the use of “a particular embodiment,” “an exemplary embodiment,” “several embodiments,” or other similar phrases throughout this specification refers to the fact that certain features, structures, or characteristics described in relation to an embodiment may be included in at least one embodiment. Thus, “in a particular embodiment,” “in an exemplary embodiment,” “in several embodiments,” “in other embodiments,” or other similar expressions 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 way in one or more exemplary embodiments. Furthermore, throughout this specification, “cell,” “node,” “gNB,” “network,” or other similar terms may be used interchangeably.

[0019] Where used herein, expressions such as “at least one of the following, <list of two or more elements>” and “at least one of <list of two or more elements>” mean at least one of the elements, or at least two or more of the elements, or at least all of the elements, when the lists of two or more elements are joined by “and” or “or”.

[0020] In the technical specifications of the 3rd Generation Partnership Project (3GPP (registered trademark)), several power classes (PCs) higher than the default PC are introduced to improve the uplink (UL) coverage and capacity. For example, Table 1 shows a definition example of the PC in Frequency Range 1 (FR1).

Table 1

[0021] Due to regulatory requirements such as the Specific Absorption Rate (SAR), a UE that supports a PC higher than the default PC is permitted to fallback to a PC lower than the default power class of FR1. Furthermore, many UE functions are associated with P, and the operation of the UE may be defined from the perspective of fallback to a lower PC. However, when exactly the UE should fallback and when the UE should return from a lower PC to a higher PC has not been studied so far. Furthermore, if the status of the PC is not recognized, the network may not recognize how to appropriately handle these functions.

[0022] Many of the capabilities of a UE and the UE's performance according to the capabilities may be associated with the UE PC for each band or for each combination of bands (BC). For example, one PC may be reported by the UE for each band or for each BC, but the UE may in some cases fallback to a lower PC and is permitted to return to a PC between the declared PC or the PC declared as the default (i.e., the highest) PC at a certain point. However, there is currently no exact definition of when the UE will fallback to the lower or default PC or when the UE will return to the declared PC. There may be some conditions for the UE to fallback, such as the threshold of the UL duty cycle and P-max in this embodiment. However, the evaluation period of the UL duty cycle is not clearly specified. Therefore, the network cannot recognize exactly what the PC being used at a certain moment is. As a result, problems may occur, such as the network setting a specific function associated with the PC for the UE even though the UE may not be at the PC expected at that time. Therefore, the UE cannot follow the instructions provided by the network. Another problem is that although some of the radio frequency (RF) performance requirements of the UE vary depending on the PC, the network cannot schedule resources such as resource blocks (RB) and modulation and coding schemes (MCS) according to the currently used 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 relate to the relationship between PC and the associated ul-FullPowerTransmission. The ul-FullPowerTransmission parameter can include various transmit modes, non-coherent and partially coherent codebook subsets, which can be used to overcome problems in UL codebook-based transmits. This may also apply to lower-rank transmits that cannot reach the maximum output power (declared by the UE) using power scaling mechanisms. Assuming a UE that supports a bandwidth of PC1.5 (29 decibel milliwatts (dBm)) for a certain bandwidth (e.g., n41), since PC1.5 for the performance requirements of n41 was developed assuming an implementation of 26dBm responsive PA × 2, the UE would have TPMI=2, i.e.,

number

[0024] If PC1.5 falls back to PC2, the supported ul-FullPwr mode may be different (i.e., ul-FullPwrMode-r16), while the network cannot recognize the PC currently in use. Therefore, the network cannot determine whether the UE is able to determine which ul-FullPwr mode(s) are applied, and even if the UE is in the PC2 state of n41, the network may incorrectly configure the UE with ul-FullPwrMode1-r16. In this case, if either port channel state is poor, the network will...

number

number

[0025] Other issues related to PCs in a UE per band or per BC can arise in relation to the switching of PCs and associated Sounding Reference Signal (SRS) antennas. For example, assuming a UE supports a PC1.5 (29dBm) bandwidth for a band (e.g., n41), when the UE is in PC1.5 state, the network might want to use 2T4R for antenna switching to reduce channel evaluation time. On the other hand, the UE might also be in PC2 (26dBm) state. In this case, if the network continues to configure the UE with 2T4R, the total power from the two antenna ports will be limited to 26dBm, potentially resulting in power per antenna being 23dBm or less. If the network is aware that the UE is in PC2 state, the network might want to configure the UE with 1T4R to increase the power per antenna to 26dBm at the cost of more switching opportunities.

[0026] Furthermore, issues related to UE PCs per bandwidth or per BC may arise in relation to PC fallback and UL resource allocation. In this case, if the UE is in the PC2 state due to fallback, the UE can continue to use PC2 as long as the proportion is less than or equal to 50%. Additionally, 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 the PC2 state, the network can avoid allocating more than 50% of the UL duty cycle. This allows the network to avoid a situation where the UE falls back further to PC3 and schedule / configure the UE with appropriate resources and / or functions according to the performance requirements of PC2, such as MPR / A-MPR, which is one of the contributing factors. Furthermore, while the network can infer the UE's PC state from the UL duty cycle, it cannot recognize it precisely because an accurate evaluation period is not defined to leave flexibility in the UE implementation.

[0027] Another issue related to UE PCs per band or per BC can arise in the relationship between PC fallback and reference sensitivity. Here, it is sometimes proposed that a UE supporting a frequency division duplex (FDD) PC2 band be allowed to autonomously fall back to PC3 if its reference sensitivity degrades due to self-interference within the same UE (mainly noise resulting from nonlinearity from its own Tx power to its own Rx band), while the network is unable to recognize the sensitivity degradation due to "self-interference". Therefore, if a UE autonomously falls back to PC3 or returns to PC2, the network cannot know whether the UE is in a PC2 state or a PC3 state.

[0028] The relationship between PC fallback and Tx diversity can lead to further issues related to the PC bandwidth of each UE per BC. In this case, the UE can, as a capability, indicate that if a PC2 UE with Tx diversity functionality falls back to PC3, one Tx will be used. However, the network has no way of knowing which PC the UE is using at that moment. Therefore, this functionality alone may not be useful. Furthermore, P CMAX,f,c It has been pointed out that a clear PC cannot be obtained from power headroom (PHR) calculated using P. CMAX,f,cは , P CMAX,f,c_L and P CMAX,f,c_H This is the value that the UE takes between these two states, and this range 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 PC status (i.e., the currently used PC status) of the instance's bandwidth or BC to the network whenever the PC being used changes. However, allowing the UE to autonomously report PC information would mean that the network would need to reserve specific UL resources for the UE to report the PC information, and since PC status changes do not occur frequently under specific conditions, valuable UL resources would be used in an inefficient manner.

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

[0031] In view of the above issues, in exemplary embodiments, a signaling mechanism can be established that enables the network to instruct the UE to report the PCs currently in use and / or the timing and duration of the UL duty cycle evaluation for a given moment in time. This report may include a reporting frequency as well as a window specified by the network. For example, in certain exemplary embodiments, a signaling mechanism can be established that enables the network to instruct the UE to report the PCs currently in use and / or the timing and duration of the UL duty cycle evaluation for a given moment in time

[0032] In other exemplary embodiments, the UE may report its capabilities to the network. The UE may also, if requested by the network, report the PC currently in use by the UE, 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 exemplary embodiments, the UE can report to the network, in terms of the PHR, thresholds for triggering a UL duty cycle evaluation as a UE capability.

[0034] In an exemplary embodiment, when the network receives a report from the UE, it can calculate the UL duty cycle and monitor whether the UL duty cycle exceeds or approaches a reported threshold. In some exemplary embodiments, the threshold may be reported to the network by the UE as one of the UE capabilities in the maxUplinkDutyCycle-PC2-FR1 parameter. According to a particular exemplary embodiment, if the network determines that the UL duty cycle exceeds the threshold, the network can further consider how much power remains by utilizing PHR information, and at that point, the network does not need to start and monitor the UL duty cycle. Alternatively, if not much power remains (i.e., little power is available) and the PHR is almost full, the network can start and monitor the UL duty cycle. Thus, in a particular exemplary embodiment, 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 the PC.

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

[0036] In exemplary embodiments, the network may report the PC currently in use by the UE, or the timing and duration of the UL duty cycle evaluation as supporting information. In some exemplary embodiments, the timing and duration of the UL duty cycle evaluation may be necessary because, at the time reported by the UE, the PC may not still be the previous PC, and the UE may be evaluating the need for a fallback or return, and the PC may be about to be changed or may be changed. With such information, the network can more accurately predict when a fallback / return will occur when a threshold is met, and can request the UE to use a PC aperiodically as needed.

[0037] Figure 2 shows an exemplary signal flow diagram in an exemplary embodiment. In a particular exemplary embodiment, the functions illustrated in Figure 2 may be performed by an apparatus similar to one of the apparatus 10 or 20 illustrated in Figure 5. In 200, the UE may send a report to the gNB that may include UE capability information indicating that the UE supports reporting its PC and / or evaluation period / start timing / evaluation trigger threshold. In 205, the gNB may determine whether the UE should configure a particular function, 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 by the function in which the UE is configured. In 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 a configuration by the gNB via Radio Resource Control (RRC).

[0038] As further shown in Figure 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 a particular exemplary embodiment, if the evaluation is not initiated, the UE may not need to report anything. Only the UE can be aware of the condition, and the network may query the UE whether the evaluation has been initiated or whether the PC has already been changed, and the UE may then report such information to the network. At 225, the UE may also send a scheduling request (SR) for a UL grant that the UE can use to transmit data to the gNB. At 230, based on the scheduling request received, the gNB may decide whether it should grant a UL grant to the UE, taking into account the status of the UL duty cycle ratio and / or PHR. At 235, the gNB may send a UL grant to the UE via the physical downlink control channel (PDCCH). In 240, in response to the UL grant, the UE may send a report to the gNB of the PCs currently in use by the UE, and / or the UL duty cycle evaluation start timing and its length. In certain exemplary embodiments, the declared PCs may be reported as UE capabilities. In 245, the gNB may schedule the UE's resources according to the received report.

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

[0040] According to a particular exemplary embodiment, the method shown in Figure 3 may include, in 300, sending a message containing user equipment capability information to a network element. The method may also include, in 305, receiving from the network element, in response to the message, power class information or a setting to report the start timing and length of the uplink duty cycle evaluation. The method may further include, in 310, sending a report to the network element in response to the setting, containing power class information or the start timing and length of the uplink duty cycle evaluation.

[0041] According to exemplary embodiments, the method may also include transmitting an evaluation threshold in power headroom values ​​to a network element to trigger an uplink duty cycle evaluation. According to some exemplary embodiments, the method may further include receiving user equipment functionality settings in response to power class information or the start timing and duration of the uplink duty cycle evaluation. According to other exemplary embodiments, the method may also include receiving resource grant allocations for data transmission in response to power class information or the start timing and duration of the uplink duty cycle evaluation.

[0042] Figure 4 shows an example of a flowchart of another method in a particular exemplary embodiment. In the exemplary embodiment, the method of Figure 4 may be performed by a network entity or a group of multiple network elements in a 3GPP® system such as LTE or 5G-NR. For example, in the exemplary embodiment, the method of Figure 4 may be performed by a gNB, a network, a cell, or any other device similar to one of the devices 10 or 20 shown in Figure 5.

[0043] According to a particular exemplary embodiment, the method in Figure 4 may include, at 400, receiving a message from the user equipment containing user equipment capability information. The method may also include, at 405, sending to the user equipment, in response to the message, power class information or settings for reporting the start timing and length of the uplink duty cycle evaluation. The method may further include, at 410, receiving a report from the user equipment containing power class information or the start timing and length of the uplink duty cycle evaluation. Furthermore, the method may include, at 415, scheduling the resources of the user equipment based on the report.

[0044] According to exemplary embodiments, the method may also include receiving an evaluation threshold in a power headroom value from the user equipment to trigger an uplink duty cycle evaluation. According to some exemplary embodiments, resources may include settings for the functionality of the user equipment or resource grant allocations for data transmission. In exemplary embodiments, UL grants may include a number of MCSs and RBs for data transmission. In further exemplary embodiments, resource grant allocations may correspond to resource grant allocations (i.e., allocations of DL resources to transmit PDCCHs to the UE), i.e., grants of (radio) resource allocations for data transmission. According to other exemplary embodiments, the method may further include determining whether the uplink duty cycle evaluation exceeds a predetermined threshold. In exemplary embodiments, 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 by taking the threshold in a minimum evaluation period or in a relaxed manner with respect to the power headroom value.

[0045] Figure 5 shows 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 related to such a network, such as a UE, mobile equipment (ME), mobile station, mobile device, fixed device, IoT device, or other device. Those skilled in the art should note that device 10 may include components or features not shown in Figure 5.

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

[0047] As shown in the example in Figure 5, the device 10 may include, or be connected to, a processor 12 for processing information and executing instructions or operations. The processor 12 may be any type of general-purpose or application-specific processor. In fact, the processor 12 may include, for example, one or more of the following: 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 multicore processor architecture. Although Figure 5 shows a single processor 12, multiple processors may also be utilized according to other exemplary embodiments. For example, in a particular exemplary embodiment, the device 10 may include two or more processors that can form a multiprocessor system capable of supporting multiprocessing (for example, in this embodiment, processor 12 represents a multiprocessor). According to a particular exemplary embodiment, the multiprocessor system may be tightly coupled or loosely coupled (for example, to form a computer cluster).

[0048] The processor 12 can perform functions related to the operation of the device 10, including, as some examples, precoding antenna gain / phase parameters, encoding and decoding individual bits that form a communication message, formatting information, and overall control of the 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 can be coupled to the processor 12 for storing information and instructions that can be executed by the processor 12. The memory 14 may be one or more memories 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 consist of random access memory (RAM), read-only memory (ROM), static storage devices such as magnetic disks or optical disks, hard disk drives (HDDs), or any other type of non-transient mechanical or computer-readable media in any combination. 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, the device 10 may further include, or be connected to (internally or externally), a drive or port configured to accept and read an external computer-readable storage medium, such as an optical disc, a USB drive, a flash® drive, or any other storage medium. For example, the external computer-readable storage medium may store a computer program or software for execution by the processor 12 and / or the device 10, and execute in any of the ways shown in Figures 1 to 4.

[0051] In some exemplary embodiments, the device 10 also includes, or is connected to, one or more antennas 15 for receiving downlink signals and transmitting from the device 10 via UL. The device 10 may further include a transceiver 18 configured to send and receive information. The transceiver 18 may also include a radio interface (e.g., a modem) coupled to the antennas 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 for processing symbols, such as OFDMA symbols carried by downlink or UL, converters (e.g., digital-to-analog converters), symbol demappers, signal shaping components, and inverse fast Fourier transform (IFFT) modules.

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

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

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

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

[0056] As shown in the example in Figure 5, the device 20 may be a network, a core network element, or an element in a communication network, or an element related to such a network, such as a gNB. It should be noted that those skilled in the art will understand that the device 20 may include components or features not shown in Figure 5.

[0057] As shown in the example in Figure 5, the device 20 may include a processor 22 for processing information and executing instructions or operations. The processor 22 may be any type of general-purpose or application-specific processor. For example, the processor 22 may include, as an example, one or more of the following: 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 multicore processor architecture. Although Figure 5 shows a single processor 22, multiple processors may also be utilized according to other exemplary embodiments. For example, in a particular exemplary embodiment, the device 20 may include two or more processors that can form a multiprocessor system capable of supporting multiprocessing (for example, in this embodiment, processor 22 represents a multiprocessor). In the exemplary embodiment, the multiprocessor system may be tightly coupled or loosely coupled (for example, to form a computer cluster).

[0058] According to certain exemplary embodiments, the processor 22 can perform functions related to the operation of the device 20, which include, for example, precoding antenna gain / phase parameters, encoding and decoding individual bits that form a communication message, formatting information, and overall control of the device 20, including the processes illustrated in Figures 1-4.

[0059] The device 20 may further include, or be connected to, a memory 24 (internal or external) that can be coupled to the processor 22 for storing information and instructions that can be executed by the processor 22. The memory 24 may be one or more memories 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 consist of random access memory (RAM), read-only memory (ROM), static storage devices such as magnetic disks or optical disks, hard disk drives (HDDs), or any other type of non-transient mechanical or computer-readable media in any combination. 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 such as those described herein.

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

[0061] In exemplary embodiments, the device 20 may also include, or be connected to, one or more antennas 25 for sending and receiving signals and / or data to and from the device 20. The device 20 may further include, or be connected to, a transceiver 28 configured to send and receive information. The transceiver 28 may include, for example, a plurality of radio interfaces that can be connected to the antennas (one or more) 25. The radio interfaces may support a plurality of radio access technologies, including one or more such as GSM, NB-IoT, LTE, 5G, WLAN, Bluetooth®, BT-LE, NFC, Radio Frequency Identifier (RFID), Ultra Wideband (UWB), and MulteFire. The radio interfaces may include components such as filters, converters (e.g., digital-to-analog converters), mappers, and Fast Fourier Transform (FFT) modules for generating symbols for transmission over one or more downlinks and receiving symbols (e.g., via UL).

[0062] Thus, the transceiver 28 may be configured to modulate information into a carrier waveform for transmission by the antenna 25 and to demodulate the information received via the antenna 25 for further processing by other elements of the device 20. In other exemplary embodiments, the transceiver 18 may directly transmit or receive signals or data. Furthermore, or alternatively, in exemplary embodiments, the 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. These modules may include, for example, an operating system that provides operating system functionality to the device 20. Memory may also store one or more functional modules, such as applications or programs, to provide additional functionality to the device 20. The components of the device 20 may be implemented in hardware or as 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 a processing circuit or control circuit. Furthermore, in some exemplary embodiments, the transceiver 28 may be included in or form part of a transceiver circuit.

[0065] As used herein, the term “circuit” may refer to a hardware-only circuit implementation (e.g., an analog circuit and / or a digital circuit), a combination of a hardware circuit and software, a combination of an analog and / or digital hardware circuit and software / firmware, any part of a hardware processor having software (including a digital signal processor) that works together to cause a device (e.g., devices 10 and 20) to perform various functions, and / or a hardware circuit and / or processor, or part thereof, that uses software for operation but may not have software if it is not necessary for operation. As a further example, the term “circuit” in this embodiment may also cover a hardware circuit or processor (or multiple processors), or a part of a hardware circuit or processor, and the accompanying software and / or firmware implementation. The term “circuit” may also refer to a baseband integrated circuit in, for example, a server, a cellular network node or device, or other computing or network device.

[0066] For example, in an exemplary embodiment, the device 20 may be controlled by memory 24 and processor 22 to receive a message from user equipment containing user equipment capability information. The device 20 may also be controlled by memory 24 and processor 22 to respond to the message by sending to the user equipment power class information or settings for reporting the start timing and length of the uplink duty cycle evaluation. The device 20 may further be controlled by memory 24 and processor 22 to receive a report from user equipment containing power class information or the start timing and length of the uplink duty cycle evaluation. Furthermore, the device 20 may further be controlled by memory 24 and processor 22 to schedule the resources of the user equipment based on the report.

[0067] In some exemplary embodiments, the apparatus (e.g., apparatus 10 and / or apparatus 20) may include means for performing any of the methods, processes, or modifications described in this embodiment. Examples of means may include one or more processors, memory, controllers, transmitters, receivers, and / or computer program code for performing the operation.

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

[0069] Certain exemplary embodiments relate to a device that includes means for receiving a message from user equipment containing user equipment capability information. The device may also include means for transmitting to the user equipment, in response to the message, power class information or settings for reporting the start timing and length of the uplink duty cycle evaluation. The device may further include means for receiving a report from the user equipment containing power class information or the start timing and length of the uplink duty cycle evaluation. Furthermore, the device may include means for scheduling the user equipment's resources based on the report.

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

[0071] A computer program product may include one or more computer-executable components configured to perform exemplary embodiments when the program is executed. One or more computer-executable components may be at least one piece of software code or a portion thereof. Changes and configurations necessary to perform the functionality of a particular exemplary embodiment may be performed as routines, or as additional or updated software routines. Software routines may be downloaded to the device.

[0072] For example, software or computer program code or any part thereof may be in source code format, object code format, or some intermediate format, and may be stored in some carrier, distribution medium, or computer-readable medium, which may be any entity or device capable of carrying the program. Such carriers include, for example, recording media, computer memory, read-only memory, optoelectric and / or electrical carrier signals, telecommunication signals, and software distribution packages. Depending on the processing power required, a computer program may be executed on a single electronic digital computer or distributed across multiple computers. The computer-readable medium or computer-readable storage medium may be a non-transient medium.

[0073] In other exemplary embodiments, the function may be performed by hardware or circuitry included in the device (e.g., device 10 or device 20), for example, through the use of application-specific integrated circuits (ASICs), programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), or any other combination of hardware and software. In yet another exemplary embodiment, the function may be implemented as a signal, which is an intangible means that can be transmitted by electromagnetic signals downloaded from the Internet or other networks.

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

[0075] Those skilled in the art will readily understand that the present disclosure as described above may be implemented using procedures in a different order and / or hardware elements in configurations different from those disclosed. Therefore, although 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 are evident, while remaining within the spirit and scope of the exemplary embodiments. While the above embodiments are also referred to as 5G NR and LTE technologies, they may also be applicable to any other current or future 3GPP® technologies, such as LTE-Advanced and / or 4G technologies.

[0076] Part of the glossary 3GPP (Registered Trademark) Third 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 Facilities DL Downlink eNB Enhanced Node B E-UTRAN - Evolved UTRAN FDD Frequency Division Duplexing FR frequency range gNB 5G or Next Generation Node B HPUE High Power UE LTE Long-Term Evolution MCS Modulation Scheme and Encoding 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 Receiver SAR specific absorption rate TDD time division duplex Tx transmission UE User Equipment UL Uplink

Claims

1. Sending a message containing user device capability information to a network element, In response to the aforementioned message, the network element receives power class information, or settings for reporting the start timing of the uplink duty cycle evaluation and the length of the uplink duty cycle evaluation. Sending a response to the network element to confirm the received settings, Based on the above settings, a report including the power class information, or the start timing and length of the uplink duty cycle evaluation, is transmitted to the network element. Methods that include...

2. To transmit an evaluation threshold for the power headroom value to the network element for triggering the uplink duty cycle evaluation, The method according to claim 1, further comprising:

3. Receiving the settings of user equipment functions in response to the power class information, or the start timing and length of the uplink duty cycle evaluation. The method according to claim 1, further comprising:

4. 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. The method according to claim 1, further comprising:

5. This further includes determining that at least one condition is met, The report is sent if at least one of the above conditions is met. The method according to claim 1.

6. The network element sends a scheduling request if at least one of the above conditions is met. Receiving an uplink grant from the aforementioned network element, It further includes, In response to the receipt of the uplink grant, the report is transmitted. The method according to claim 5.

7. It is a device, At least one processor, At least one memory containing computer program code, Equipped with, When the at least one memory and the computer program code are executed by the at least one processor, the stored instructions will cause the device to, at least, Sending a message containing user device capability information to a network element, In response to the aforementioned message, the network element receives power class information, or settings for reporting the start timing of the uplink duty cycle evaluation and the length of the uplink duty cycle evaluation. Sending a response to the network element to confirm the received settings, Based on the above settings, a report including the power class information, or the start timing and length of the uplink duty cycle evaluation, is transmitted to the network element. A device configured to perform a certain action.

8. When the at least one memory and the computer program code are executed by the at least one processor, the stored instructions will cause the device to, at least, To transmit an evaluation threshold for the power headroom value to the network element for triggering the uplink duty cycle evaluation, The apparatus according to claim 7, further configured to perform the following:

9. When the at least one memory and the computer program code are executed by the at least one processor, the stored instructions will cause the device to, at least, Receiving the settings of user equipment functions in response to the power class information, or the start timing and length of the uplink duty cycle evaluation. The apparatus according to claim 7, further configured to perform the following:

10. When the at least one memory and the computer program code are executed by the at least one processor, the stored instructions will cause the device to, at least, 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. The apparatus according to claim 7, further configured to perform the following:

11. When the at least one memory and the computer program code are executed by the at least one processor, the stored instructions will cause the device to, at least, To determine that at least one condition is met, Further configured to perform, The report is sent if at least one of the above conditions is met. The apparatus according to claim 7.

12. When the at least one memory and the computer program code are executed by the at least one processor, the stored instructions will cause the device to, at least, If at least one of the above conditions is met, a scheduling request is sent to the network element. Receiving an uplink grant from the aforementioned network element, Further configured to perform, The aforementioned report is transmitted in response to the receipt of the uplink grant. The apparatus according to claim 11.

13. It is a device, At least one processor, At least one memory containing computer program code, Equipped with, When the at least one memory and the computer program code are executed by the at least one processor, the stored instructions will cause the device to, at least, Receiving a message from the user's device containing user device capability information, In response to the aforementioned message, the user device is sent power class information, or a setting to report the start timing of the uplink duty cycle evaluation and the length of the uplink duty cycle evaluation. The user device receives a response from which the transmitted settings have been confirmed, Receiving a report from the user equipment including the power class information, or the start timing and length of the uplink duty cycle evaluation, Based on the above report, the resources of the user equipment will be scheduled, A device configured to perform a certain action.

14. When the at least one memory and the computer program code are executed by the at least one processor, the stored instructions will cause the device to, at least, The user device receives an evaluation threshold for the power headroom value to trigger the uplink duty cycle evaluation. The apparatus according to claim 13, further configured to perform the following.

15. The aforementioned resources are User device function settings, or Resource grant allocation for data transmission, The apparatus according to claim 13, including the apparatus described in claim 13.

16. When the at least one memory and the computer program code are executed by the at least one processor, the stored instructions will cause the device to, at least, To determine whether the uplink duty cycle evaluation exceeds a predetermined threshold, The apparatus according to claim 13, further configured to perform the following.

17. Based on the above determination, when the at least one memory and the computer program code are executed by the at least one processor, the stored instructions will cause the device to, at least, Based on the above determination, start or stop monitoring the uplink duty cycle. The apparatus according to claim 16, further configured to perform the following.

18. Based on the above determination, when the at least one memory and the computer program code are executed by the at least one processor, the stored instructions will cause the device to, at least, Based on the above determination, the uplink duty cycle is determined in the minimum evaluation period, or by taking a relaxed threshold with respect to the power headroom value. The apparatus according to claim 16, further configured to perform the following.

Images