User equipment, network node and methods performed therein for uplink transmission (s)

Abstract

A method of a user equipment, UE, for performing uplink, UL, transmissions, a method of a network node for scheduling UL transmissions, a user equipment and a network node are disclosed. The method of a UE for performing UL transmission comprises: determining an uplink UL duty cycle of the UL transmission comprising an unscheduled transmission; determining an actual transmit power for performing the UL transmission in response to the UL duty cycle being greater than capability information reported by the UE and applying a power fallback setting to the transmit power for the UL transmission in order to comply with an electromagnetic power density exposure requirement; and transmitting the UL transmission using the actual transmit power.

Description

Technical Field

[0001] This disclosure relates to wireless communication, and in particular to user equipment and network nodes in a communication network, and to methods performed in the user equipment for performing one or more uplink UL transmissions and methods performed in the network node for scheduling one or more uplink UL transmissions. Background Technology

[0002] RACH repetition was introduced in Rel-13 WI for “Further LTE Physical Layer Enhancement for MTC” and “Narrowband IoT (NB-IoT)” to extend coverage.

[0003] RACH repeats LTE eMTC, NB-IoT Information repetition is a technique used to achieve coverage enhancement. It is used to enhance coverage across all physical channels available to the UE, namely M-PDCCH, PBCH, PDSCH, PUCCH, PUSCH, and PRACH.

[0004] The UE determines the repetition level for the initial PRACH transmission. The repetition levels supported by the cell (e.g., 5, 10, and 15 dB) are included in the system information, and the UE selects one of these repetition levels based on, for example, the estimated channel quality.

[0005] During the initial random access: › UE measurement DL quality; › The UE selects the appropriate repetition level from four levels for its initial PRACH preamble transmission; › If the UE does not receive a Random Access Response (RAR), it increases its PRACH repetition level; and The number of repeats of the RAR and subsequent messages will depend on the level of the successful PRACH.

[0006] Coverage enhancement for the physical random access PRACH preamble can be achieved partly by relaxing the required PRACH false detection probability and partly by repeating the traditional PRACH format (e.g., PRACH repetition). Up to three different repetition levels (plus coverage enhancement level zero) can be configured, each with its own configurable number of repetitions and attempts to adapt to the UE's coverage conditions. For initial random access, the UE selects its repetition level based on RSRP measurements. If the UE does not receive a RAR after the maximum number of attempts at its current level, it moves to the next higher level. No power ramping is used for large repetition levels; otherwise, the current procedure is used. Different coverage levels correspond to different PRACH resources (e.g., different combinations of preamble sequences, timing, and narrowband), and available resources are signaled in the SIB.

[0007] RAR messages are scheduled via M-PDCCH and associated PDSCH. The UE knows the repetition level of M-PDCCH, the possible start subframe, and frequency resources from its most recent PRACH transmission (combined with information signaled in the SIB).

[0008] To enable different operating modes depending on the UE's coverage extension needs, two coverage enhancement modes have been introduced for RRC_CONNECTED UEs: • CE mode A, used for no coverage enhancement or small coverage enhancement, requires several (e.g., up to dozens) repetitions. • CE mode B, used for medium to large coverage enhancement, requires several (e.g., hundreds) repetitions. The network sends a signal to the UE to notify it of CE mode.

[0009] Coverage Enhancement Mode: As mentioned earlier, when signaled, the UE moves from no coverage enhancement or small coverage enhancement (CE Mode A) to large coverage enhancement (CE Mode B). The idea is that if the UE cannot use small coverage operations for synchronization acquisition, system information acquisition, random access, or data transmission, then the UE will remain in CE Mode B. In enhanced coverage operations, the number of repetitions can be adapted according to the UE's coverage status.

[0010] In 3GPP specification 36.321 v17.2.0: • If the UE is a BL UE or a UE within enhanced coverage: O If the random access preamble is transmitted over a non-terrestrial network: - The RA response window begins at the end of the subframe containing the last preamble repeat plus 3+UE-eNB RTT subframes, as specified in Clause XX of TS 36.213 [6], and has a length for the corresponding enhanced coverage level. ra- ResponseWindowSize ; Otherwise: - The RA response window begins at the end of the frame containing the last preamble repeat plus three subframes, and has a length for the corresponding enhancement coverage level. ra-ResponseWindowSize . • If the UE is an NB-IoT UE: O If the random access preamble is transmitted over a non-terrestrial network: - The RA response window begins at the end of the subframe containing the last preamble repeat plus the X+UE-eNB RTT subframe, as specified in Clause XX of TS 36.213 [6], and has a length for the corresponding enhanced coverage level. ra-ResponseWindowSize The value X is determined from Table 5.1.4-1 based on the preamble format used and the number of NPRACH repetitions; Otherwise: - The RA response window begins at the end of the frame containing the last preamble repeat plus X subframes, and has a length for the corresponding enhancement coverage level. ra-ResponseWindowSize The value X is determined from Table 5.1.4-1 based on the preamble format used and the number of NPRACH repetitions.

[0011] The RA-RNTI associated with PRACH (in which the random access preamble is transmitted) is calculated as follows: Where t_id is the index of the first subframe of the specified PRACH (0 ≤ t_id < 10), and f_id is the index of the specified PRACH within that subframe (in ascending frequency domain order, except for NB-IoT UEs, BL UEs, or UEs in enhanced coverage areas, 0 ≤ f_id < 6)). If the PRACH resource is on a TDD carrier, then f_id is set to... ,in Defined in Clause 5.7.1 of TS 36.211[7].

[0012] For BL UEs and UEs within enhanced coverage, the RA-RNTI associated with PRACH (where the random access pre-synchronization code is transmitted) is calculated as follows: Where t_id is the index of the first subframe of the specified PRACH (0 ≤ t_id < 10), f_id is the index of the specified PRACH within that subframe (in ascending frequency order (0 ≤ f_id < 6)), SFN_id is the index of the first radio frame of the specified PRACH, and Wmax is 400 (the maximum possible RAR window size in the subframe for BL UEs or UEs in enhanced coverage). If the PRACH resource is on a TDD carrier, f_id is set to... ,in Defined in Clause 5.7.1 of TS 36.211.

[0013] For NB-IoT UEs, the RA-RNTI associated with PRACH (in which the random access pre-synchronization code is transmitted) is calculated as follows: Where SFN_id is the index of the first radio frame of the specified PRACH, and carrier_id is the index of the UL carrier associated with the specified PRACH. The carrier_id of the anchor carrier is 0.

[0014] For BL / CE UEs, for each PRACH coverage enhancement level, there exists a PRACH configuration index configured by a higher layer ( prach-ConfigurationIndex PRACH frequency offset ( prach -FrequencyOffset ), number of PRACH repetitions per attempt ( numRepetitionPerPreambleAttempt ) and optionally, PRACH start subframe periodicity ( prach-StartingSubframe The PRACH configuration is as follows. PRACH codes 0-3 in preamble format are transmitted. The PRACH of preamble format 4 is transmitted only once, whereas the PRACH of preamble format 4 is transmitted only once.

[0015] For BL / CE UEs and for each PRACH coverage enhancement level, if frequency hopping is performed through higher layer parameters... prach-HoppingConfig When enabled for PRACH configuration, the parameter The value depends on the SFN and PRACH configuration indexes and is given by the following formula: - Configure the index in PRACH such that when calculated from Table 5.7.1-2 or Table 5.7.1-4 as follows PRACH resources available Now in each radio frame In this case, - Otherwise in, It is the system frame number corresponding to the first subframe of each PRACH repetition, and Corresponding to the higher-level parameters specific to the community prach-HoppingOffset If frequency hopping is not enabled for PRACH configuration, then .

[0016] For frame structure type 1 with preamble formats 0-3, for each of the PRACH configurations, there is at most one random access resource per subframe.

[0017] For frame structure type 2 with preamble formats 0-4, for each PRACH configuration, depending on the UL / DL configuration [see Table 4.2-2], there may be multiple random access resources (or UpPTS for preamble format 4) in the UL subframe. Table 5.7.1-3 lists the allowed PRACH configurations for frame structure type 2, where the configuration index corresponds to the preamble format, PRACH density value, and so on. and version index A certain combination.

[0018] For frame structure type 2 with PRACH configuration indices 51, 53, 54, 55, 56, 57 or PRACH configuration indices 0, 1, 2, 20, 21, 22, 30, 31, 32, 40, 41, 42, 48, 49, 50 in UL / DL configurations 3, 4, 5, the UE may assume, for handover purposes, that the absolute value of the relative time difference between radio frames in the current cell and the target cell is less than [a certain value]. .

[0019] Table 5.7.1-3: Random Access Configuration for Frame Structure Type 2 for Preamble Formats 0-4 .

[0020] Table 5.7.1-4 lists the values ​​used for a given PRACH density value. Mapping of the physical resources required for different random access opportunities. Each quadruple in the format... Indicates the location of a specific random access resource, where It is the frequency resource index within the time instance under consideration. These indicate whether the resource reappears in all radio frames, in even-numbered radio frames, or in odd-numbered radio frames, respectively. Indicate whether the random access resources are located in the first half-frame or the second half-frame; and in which This is the uplink subframe number, where the preamble is counted from 0 at the first uplink subframe between two consecutive downlink-to-uplink switching points, except for preamble format 4 (where... Except as shown in (*). The start of the random access preamble format 0-3 is aligned with the start of the corresponding uplink subframe at the UE (assuming...). ), and random access preamble format 4 before the end of UpPTS at the UE. Initially, UpPTS references the UE's uplink frame timing (assuming...). ).

[0021] Random access opportunities for each PRACH configuration should be allocated first in time and then in frequency, only if time reuse is insufficient to maintain all opportunities for the PRACH configuration required for a given density value without temporal overlap. For preamble formats 0-3, frequency reuse should be performed according to the following formula: in This refers to the number of uplink resource blocks. It is the first physical resource block allocated to the considered PRACH opportunity, and in which It is the first physical resource block available for PRACH.

[0022] For BL / CE UEs, only a subset of subframes permitted for preamble transmission are allowed as a basis for... A repeating start subframe. The allowed start subframes for PRACH configuration are determined as follows: - List the subframes allowed for preamble transmission for PRACH configuration as follows ,in and These correspond to the minimum and maximum absolute subframe numbers allowed, respectively. The two subframes are transmitted using the preamble. - If PRACH starts subframe periodicity If not provided by a higher layer, then the periodicity of the allowed start subframe is based on the subframes permitted for preamble transmission. .exist The allowed start subframes defined within are determined by (in j = 0,1,2,… (This is given.) - If PRACH starts subframe periodicity Provided by a higher layer, it indicates the periodicity of the allowed start subframe based on the subframes permitted for preamble transmission. The allowed start subframes defined within are determined by (in j = 0,1,2,… (This is given.) - exist The lack of a defined start subframe makes Permitted.

[0023] Each random access preamble occupies the bandwidth corresponding to six consecutive resource blocks used for both frame structures.

[0024] Table 5.7.1-4: Frame Structure Type 2 Random Access Preamble Mapping in Time and Frequency .

[0025] NB-IoT (Section 10.1.6 of version 36.211 v17.2.0) The physical layer random access preamble is based on a single subcarrier frequency hopping symbol group. Figure 10 The symbol group is shown in .1.6.1-1, which consists of a length of cyclic prefix and a series N 1 equivalent symbol (with a total length) The total number of symbol groups in the preamble repetition unit is composed of... P The number of time-continuous symbol groups is represented by... G Provided.

[0026] Table 10.1.6.1-2: Random Access Preamble Parameters for Frame Structure Type 2 .

[0027] Depend on P The preamble consisting of 1 symbol group should be transmitted. For frame structure type 2, when invalid uplink subframes overlap without gaps... G When transmitting a group of symbols, discard the... G A group of symbols. For frame structure type 2, G The transmission of each symbol group is aligned with the subframe boundary.

[0028] When configured as described in Table 10.1.6.1-1, the frequency position of NPRACH transmission is constrained to... Within each subcarrier and in Within 12 and 36 subcarriers, when configured as described in Table 10.1.6.1-1 preamble format 2, frequency hopping should be used within 12 and 36 subcarriers, where the frequency position of the i-th symbol group is determined by... Given, among which .quantity It depends on the frame structure.

[0029] Msg1 power determination The determination of Msg1 power is discussed in section 7.4 of version 38.213 v17.4.0.

[0030] Using the selected PRACH format, transmit power over the indicated PRACH resources. By serving the community c carrier f BWP b To send PRACH. .

[0031] If, within the random access response window, as described in Clause 8.2, the UE does not receive a random access response containing a preamble identifier corresponding to the preamble sequence transmitted by the UE, the UE determines the transmission power for subsequent PRACH transmissions (if any), as described in [11, TS 38.321].

[0032] If the UE before PRACH retransmission Change the spatial domain transport filter Then layer 1 notifies the higher layers. Pause power slope Variable counter As described in [11, TS 38.321].

[0033] 38.321 v17.3.0 of version 5.1.3.

[0034] Msg3 transmission power 38.213 v17.4.0 7.1.1 discusses Msg3 transmission power.

[0035] If the UE uses an index j Parameter set configuration and index l PUSCH power control adjustment status in the serving cell c carrier f UL BWP activities b If the UE transmits the PUSCH, then the timing of the PUSCH transmission is as follows: i PUSCH transmission power in Determined as [dBm] Among them, for the timing of PUSCH transmission i China's service communities c carrier f UL BWP activities b The PUSCH power control adjustment state, if the UE responds to the serving cell c carrier f UL BWP activities b Upon receiving a random access response message via PRACH transmission, as described in Clause 8 - ,inl =0, and - In the corresponding serving cell c carrier f UL BWP activities b The TPC command value indicated in the random access response grant of the random access response message transmitted via PRACH, and - and Provided by a higher layer and corresponding to the information provided by the higher layer from the serving cell c carrier in f The total power ramp requested by the first to the last random access preamble. It is used for serving the community c carrier f UL BWP activities b The bandwidth of the PUSCH resource allocation is expressed by the number of resource blocks transmitted in the first PUSCH, and It serves the community c carrier f UL BWP activities b The power adjustment of the first PUSCH transmission.

[0036] Beam failure recovery Section 9.2.8 of version 38.300 V17.3.0 discusses beam failure recovery.

[0037] For beam failure detection, the gNB configures the UE via a beam failure detection reference signal (SSB or CSI-RS), and the UE declares a beam failure when the number of beam failure instances indicated from the physical layer reaches a configured threshold before the configured timer expires. SSB-based beam failure detection is based on the SSB associated with the initial DL BWP and can only be configured for the initial DL BWP and for DL ​​BWPs containing an SSB associated with the initial DL BWP. For other DL BWPs, beam failure detection can only be performed based on CSI-RS.

[0038] After detecting beam failure, the UE: - Trigger beam failure recovery by initiating a random access procedure on the PCell; - Select the appropriate beam to perform beam failure recovery (if the gNB has provided dedicated random access resources for certain beams, those beams will be prioritized by the UE).

[0039] When the random access procedure is completed, the beam failure recovery is considered complete. Summary of the Invention

[0040] The embodiments described herein are intended to address at least some of the problems and issues outlined herein. These and other objectives can be achieved by using user equipment, network nodes, methods executed in the user equipment for performing one or more uplink transmissions, and methods executed in the network node for scheduling one or more uplink transmissions.

[0041] According to a first aspect of the embodiments herein, the objective is achieved by a user equipment (UE) method for performing uplink UL transmission, the method comprising: determining an uplink UL duty cycle of the UL transmission including unscheduled transmissions; determining an actual transmission power for performing the UL transmission in response to the UL duty cycle being greater than capability information reported by the UE and applying a power backoff setting to the transmission power for the UL transmission to comply with electromagnetic power density exposure requirements; and using the actual transmission power to transmit the UL transmission.

[0042] According to a second aspect of the embodiments herein, the objective is achieved by a network node for scheduling uplink UL transmissions, the method comprising: receiving capability information reported by a user equipment (UE); scheduling the UL transmissions based on the reported capability information; and receiving from the UE the UL transmissions using actual transmission power for performing the UL transmissions; wherein the actual transmission power is obtained by applying a power backoff setting to the transmission power for the UL transmissions in response to the UL transmissions including unscheduled transmissions having a UL duty cycle greater than the capability information.

[0043] According to a third aspect of the embodiments herein, the objective is achieved by a user equipment (UE) for performing uplink UL transmission, the UE including: an antenna configured to transmit and receive wireless signals; The processing circuitry is configured to perform the following operations: determine the uplink UL duty cycle of the UL transmission, including unscheduled transmissions; in response to the UL duty cycle being greater than the capability information reported by the UE, apply a power backoff setting to the transmission power used for the UL transmission to meet electromagnetic power density exposure requirements, determine the actual transmission power used to perform the UL transmission; and use the actual transmission power to transmit the UL transmission.

[0044] According to a fourth aspect of the embodiments herein, the objective is achieved by a network node for scheduling uplink UL transmissions, the network node comprising: an antenna configured to transmit and receive wireless signals; A processing circuit configured to perform the following operations: receiving capability information reported by a user equipment (UE); scheduling the UL transmission based on the reported capability information; and receiving from the UE the UL transmission using actual transmission power for performing the UL transmission; wherein the actual transmission power is obtained by applying a power backoff setting to the transmission power for the UL transmission in response to the UL duty cycle of the UL transmission, which includes unscheduled transmissions, being greater than the capability information.

[0045] Embodiments of this disclosure can improve PRACH coverage and save UE power. Embodiments of this disclosure can also reduce the duration of processes involving PRACH transmissions, such as cell changes (e.g., handover), RRC connection release with redirection, RRC connection reconstruction, obtaining a time advance command when synchronization with the serving cell is lost, etc. Attached Figure Description

[0046] A more complete understanding of this embodiment and its accompanying advantages and features will be more readily apparent by referring to the following detailed description (when considered in conjunction with the accompanying drawings), in which: Figure 1 A flowchart illustrating a possible method embodiment under this disclosure is shown.

[0047] Figure 2 Another flowchart of a possible method embodiment under this disclosure is shown.

[0048] Figure 3 Another flowchart of a possible method embodiment under this disclosure is shown.

[0049] Figure 4 Another flowchart of a possible method embodiment under this disclosure is shown.

[0050] Figure 5 Another flowchart of a possible method embodiment under this disclosure is shown.

[0051] Figure 6 Another flowchart of a possible method embodiment under this disclosure is shown.

[0052] Figure 7 Another flowchart of a possible method embodiment under this disclosure is shown.

[0053] Figure 8 An example of a communication system QQ100 according to some embodiments is shown.

[0054] Figure 9 A UE QQ200 according to some embodiments is shown.

[0055] Figure 10A network node QQ300 according to some embodiments is shown.

[0056] Figure 11 Based on the block diagram of the host QQ400 described in this article, it can be... Figure 8 An example of the host QQ116.

[0057] Figure 12 This is a block diagram illustrating a virtualized environment QQ500 in which the functionality implemented through some embodiments can be virtualized.

[0058] Figure 13 The diagram illustrates a communication between host QQ602 and UE QQ606 via network node QQ604 through a partial wireless connection, according to some embodiments. Detailed Implementation

[0059] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. The embodiments are provided as examples to convey the scope of the subject matter to those skilled in the art.

[0060] Several challenges exist. 3GPP specifications define UE behavior related to Maximum Allowable Exposure (MPE) requirements (e.g., Specific Absorption Rate (SAR), which is a regulatory requirement). One approach is to set the Power Management Maximum Power Reduction (P-MPR) for the scheduled uplink based on the calculated uplink duty cycle. However, such mechanisms are used by the network to schedule uplink transmissions, and since PRACH is not scheduled by the network, the UE can apply P-MPR to meet regulatory requirements.

[0061] To ensure that devices operating on carrier frequencies above 10 GHz (e.g., UEs) meet the Maximum Permissible Exposure (MPE) requirement, the incident power density measurement time is several seconds. For devices operating on carrier frequencies below or equal to 10 GHz (e.g., UEs), the SAR requirement will be applied over an average time of 6 minutes. UEs are allowed to transmit at higher transmission rates, provided that the average measurement within the evaluation time window meets the MPE limit.

[0062] When a UE applies P-MPR to PRACH, there is a coverage penalty for PRACH because the transmitted output power is reduced, and therefore a method is needed to avoid or minimize the reduction in PRACH coverage.

[0063] In Rel-18, 3GPP introduced multiple PRACH transmissions. If P-MPR is applied to a PRACH transmission and the network fails to receive the PRACH, it may waste PRACH opportunity (RO) resources and increase interference with the PRACH success rate of other UEs. UE behavior for MPE used for unscheduled transmissions needs to be specified to further improve PRACH coverage in the network.

[0064] Certain aspects of this disclosure and its embodiments may provide solutions to these or other challenges. Some embodiments of this disclosure describe methods for enabling a UE to avoid setting power back-off due to satisfying the MPE (P-MPR = 0) for PRACH transmission.

[0065] In some embodiments, the UE determines the P-MPR of the transmission power used for PRACH transmission based on one or more of the following factors or criteria: 1. The number of (one or more) PRACH transmissions 2. Operating frequency (>10 GHz, or <10 GHz) 3. RACH type, such as two-step RACH or four-step RACH, contention-based RACH, or non-contention-based RACH, etc. 4. PRACH retransmission 5. PRACH repeat 6. Coexistence with other technologies (WIFI, Bluetooth, 2G / 3G / 4G / 5G) 7. The type of procedure or operation associated with PRACH transmission, such as switching, beam failure recovery, or timing acquisition when the time alignment timer (TAT) expires.

[0066] The UE applies the determined value of P-MPR (β) to the estimated power (P1) used for PRACH transmission to determine the actual power (P2) used to perform the PRACH transmission. The UE further uses the determined power P2 to transmit the PRACH transmission. In one example, P1 (in dBm), P2 (in dBm), and β (in dB) are related by the following function (in one case, P1 = PCmax). P2 = P1–β.

[0067] This disclosure also includes methods for the UE to calculate the UL duty cycle and for the UE to determine the P-MPR setting for unscheduled transmissions (e.g., PRACH). It applies to both single-PRACH and multi-PRACH transmissions. Whether the UE can set the P-MPR for unscheduled transmissions when the maxUplinkDutyCycle capability exists can be based on the following factors: 1. Percentage of uplink symbols including scheduled and / or unscheduled symbols. 2. The threshold of maxUplinkDutyCyle indicates whether both scheduled and unscheduled signal dutyCycles are included.

[0068] By specifying UE behavior for PRACH transmission using MPE, the network can improve PRACH coverage.

[0069] Some embodiments may provide one or more of the following technical advantages: Improve PRACH coverage and save UE power. O reduces the duration of processes involving PRACH transmissions, such as cell changes (e.g., handover), RRC connection release with redirection, RRC connection reconstruction, and obtaining time advance commands when synchronization with the serving cell is lost.

[0070] To ensure a UE meets MPE requirements, measurements of power density or ratio (the rate at which a human body absorbs energy per unit mass when exposed to a radio frequency (RF) electromagnetic field) (e.g., specific absorptivity) can be averaged over a certain time window. For UEs operating below 10 GHz, measurements of SAR (specific absorptivity) limits can be averaged over a 6-minute time window. For UEs operating above 10 GHz, measurements of incident power density can be averaged over several seconds. If the UE transmits higher output power over a short time period, the time-averaged measurement can be used as long as it meets SAR limits (W / kg) or power density (W / m³). 2 Within a given time slot, higher power transmission is permitted. This makes it possible to predefine the UE backoff power for a single or multiple transmissions (such as PRACH transmissions) that occur intermittently to meet exposure requirements. Since PRACH transmissions can occur only in the configured time slots to enable UE access to the network, this PRACH symbol can occupy only a small fraction of the total transmission symbols for a typical eMBB UE.

[0071] In one embodiment, the backoff power (P-MPR) applied to the maximum transmit power used for PRACH transmission (e.g., Pcmax as defined in TS 38.101-1 or TS 38.101-2) is a function of the scaling factor K dB (which may be predefined or configured by the network node, e.g., by the UE's serving BS) or depends on the scaling factor K dB. In one example, after applying P-MPR, the UE transmit power (P2) (dBm) used for PRACH transmission is determined as follows: P2 = PCmax – K The UE uses transmission power P2 to transmit PRACH.

[0072] For a first PRACH transmission without repetition, K = 0 dB when there is no simultaneous transmission from another radio access technology (e.g., Wi-Fi / Bluetooth / 2G / 3G / 4G) coexisting with the UE in the device (i.e., simultaneous transmission of the UE's PRACH and another signal). Any two uplink transmissions through the same UE are considered simultaneous if they overlap at least partially with respect to each other in time. When simultaneous transmissions occur, K can also be set to 0 dB if the UE can compensate for the time-averaged output power in one or more subsequent consecutive transmissions. In another case, K can be set to K > 0 dB (e.g., X1 dB), which can further depend on simultaneous transmissions from other technologies, such as the transmission power of those other technologies. For example, if the UE's total transmission power exceeds SAR or power density requirements due to simultaneous transmissions from different transmitters for different technologies or from different transmitters of the same technology, and if the UE applies a scaling factor to reduce its total transmission power, such a scaling factor needs to be compared with K dB and should be less than K dB for PRACH transmissions. In another case, K can be set to X2 dB, depending on the simultaneous transmission of a PRACH signal on one carrier frequency (F1) and a non-PRACH signal on another carrier frequency (e.g., F2). Examples of non-PRACH signals are UL reference signals (e.g., SRS, DMRS, etc.), UL control channels (e.g., PUCCH), UL data channels (e.g., PUSCH), etc. In one example, X2 is below a certain threshold. In another example, X2 is above a certain threshold. In yet another example, X2 = 0 dB.

[0073] In another embodiment, the back-back power (P-MPR) is not applied to the first PRACH transmission, but can be applied to the maximum transmission power for one or more PRACH transmissions (e.g., subsequent transmissions) other than the first PRACH transmission. This can be set by the UE, and in some cases, the UE can set the P-MPR by adding a scaling factor M dB. This M dB can be associated with the back-back power for other PRACH transmissions besides the first transmission. For example, for PRACH transmissions where transmission power is ramped up for retry or retransmission, additional M dB is allowed in the aforementioned cases (e.g., simultaneous transmission of the UE's PRACH and other uplink signals).

[0074] P-MPR for other PRACH transmissions = K dB + M dB.

[0075] In this case, P2 is determined as follows: P2 = PCmax – (K + M) This will compensate for the high transmission power used for the first PRACH transmission. In one example, M can be predefined or configured by the network node. In another example, K and / or M can be reported by the UE to the network node as UE capabilities, which depend on the UE power level and / or the number of coexisting technologies supported on the same UE device. In yet another example, K and / or M can be reported by the UE to the network node as part of UE Assistance Information (UAI). In this case, the values ​​of K and / or M can vary semi-statically or dynamically over time. For example, the values ​​of K and / or M may depend on the currently used UE power level and / or the number of coexisting technologies currently used on the same UE device.

[0076] The above equation is based on the assumption that the first and subsequent PRACH transmissions are multiple PRACH transmissions of the same RACH attempt, which apply the same power ramp counter according to the following agreement in RAN1#112. agreement For multiple PRACH transmissions through the same Tx beam in a single RACH attempt, no transmission power ramping shall be applied within a single RACH attempt.

[0077] In another embodiment, if a subsequent PRACH is a retransmission of the first PRACH transmission and has a greater value than the first transmission... PREAMBLE_POWER_RAMPING_COUNTER 1 of PREAMBLE_POWER_RAMPING_COUNTER 1 Then P2 is determined as follows: P2 = min(PCmax – (K+M), previous transmitted power + power ramp step size).

[0078] In another embodiment, the P-MPR applied to the transmission power of each PRACH transmission used for PRACH transmission depends on the number of PRACH transmissions (Np). The parameter Np may correspond to the maximum number of PRACH transmissions or the maximum number of PRACH retransmissions configured by the network node. For example, the P-MPR value (L) per PRACH transmission or per PRACH retransmission can be expressed as follows: L = H / Np Where H is the aggregated amount or total amount of P-MPR that the UE can apply during all PRACH transmissions or all PRACH retransmissions. In one example, H is expressed in dB. In another example, H is expressed as a linear scalar.

[0079] The UE determines and applies P2 as follows during each PRACH transmission or each PRACH retransmission, where L is in dB: P2 = P1–L Where P1 is the UE transmission power or estimated transmission power used for PRACH.

[0080] In another embodiment, the P-MPR of the transmission power applied to the PRACH transmission is adapted or adjusted based on or depending on the purpose of the PRACH transmission. The purpose depends on the type of process during which the PRACH is transmitted or the type of process that triggers the UE to perform the PRACH transmission. In one example, for at least the first PRACH transmission associated with one or more critical operations, no P-MPR is applied (i.e., P-MPR = 0) or the P-MPR applied to the PRACH transmission power is below a threshold (e.g., no more than 2 dB). The UE transmits PRACH during some operations within a critical operation or in response to the occurrence of a critical operation. Examples of such critical operations are cell change, timing advance (TA) command expiration, RRC connection re-establishment, beam failure detection (BFD), beam failure recovery (BFR), tracking area or registration area update, etc. Examples of cell changes are handover, cell reselection, RRC connection release with redirection, serving cell (e.g., SCell, PSCell, etc.) change, etc. For example, the P-MPR of the transmission power applied to the PRACH transmission for normal operations (i.e., non-critical operations) could be X1 dB. On the other hand, the P-MPR for the transmission power applied to PRACH transmissions for critical operations can be X2 dB; where X1 > X2, for example, X1 = 3 dB and X2 = 1 dB, or X1 = 2 dB and X2 = 0 dB. The value of P-MPR (e.g., X2) can further depend on the type of critical operation, for example, X2 = 2 dB for PRACH transmissions during switching, X2 = 1 dB for PRACH transmissions during BFR procedures, X2 = 0 dB for PRACH transmissions when the TA command expires, etc. The TA command expires or becomes invalid when the time alignment timer (TAT) expires.

[0081] In another embodiment, the P-MPR applied to the transmission power of the PRACH transmission is adapted or adjusted based on or depending on the type of PRACH procedure used for PRACH transmission. The UE applies the adapted P-MPR value to the estimated PRACH transmission power (P1) to determine the actual PRACH transmission power (P2). The UE further uses the determined value of P1 to transmit the PRACH. Examples of PRACH procedure types are: contention-based RACH, non-contention-based RACH, 2-step RACH, 4-step RACH, etc. This is explained through the following example: • In one example, the P-MPR value for the transmission power used for contention-based PRACH transmission (e.g., Y1 dB) is lower than the P-MPR value for the transmission power used for non-contention-based PRACH transmission (e.g., Y2 dB). • In another example, the P-MPR value for the transmission power used for PRACH transmission (e.g., Y1 dB) is higher than the P-MPR value for the transmission power used for non-contention-based PRACH transmission (e.g., Y2 dB). • In another example, the different magnitudes between Y1 and Y2 are greater than a certain threshold (G1), for example (│Y1-Y2│>G1). • In another example, the different magnitudes between Y1 and Y2 are less than or equal to a certain threshold (G2) but greater than 0 dB, for example (0 < |Y1-Y2| ≤ G2). • In another example, the P-MPR value for the transmission power used in a 2-step PRACH transmission (e.g., Y3 dB) is lower than the P-MPR value for the transmission power used in a 4-step PRACH transmission (e.g., Y4 dB). • In another example, the P-MPR value for the transmission power used in a 2-step PRACH transmission (e.g., Y3 dB) is higher than the P-MPR value for the transmission power used in a 4-step PRACH transmission (e.g., Y4 dB). • In another example, the different magnitudes between Y3 and Y4 are greater than a certain threshold (G3), for example (│Y3-Y4│>G3). • In another example, the different magnitudes between Y3 and Y4 are less than or equal to a certain threshold (G4) but greater than 0 dB, for example (0 < |Y3-Y4| ≤ G4).

[0082] In another embodiment, during a PRACH process, if the aggregated value (Z) of the P-MPR applied to the transmission power of one or more PRACH transmissions exceeds a certain threshold (H2), the UE performs one or more operational tasks. The aggregated value of the P-MPR is determined based on one or more functions (e.g., summation, maximization, product, rounding up, etc.). For example, if the P-MPR values ​​corresponding to z1, z2, and z3 are applied by the UE to the transmission power of the first, second, and third PRACH transmissions, respectively, then in one example, the aggregated value (Z) of the P-MPR is expressed as: Z = z1 + z2 + z3.

[0083] An example of one or more operational tasks is: • In one example, the UE stops performing PRACH transmission; for example, the UE abandons or discards the PRACH process. • In another example, the UE restarts the PRACH procedure. In this case, the UE abandons or discards the previous PRACH procedure. • In another example, the UE switches to another PRACH procedure. In one example, if the UE performs a 2-step RACH, then when Z exceeds H2, the UE switches to a 4-step RACH. In this case, the UE further uses the 4-step RACH to begin the PRACH procedure. In another example, if the UE performs a 4-step RACH, then when Z exceeds H2, the UE switches to a 2-step RACH. In this case, the UE further uses the 2-step RACH to begin the PRACH procedure. • In another example, if Z exceeds H2, the UE switches to another PRACH procedure, and the UE does not receive any Random Access Response (RAR) messages from the network node. In one example, if the UE performs a 2-step RACH, then when Z exceeds H2 and no RAR message is received, the UE switches to a 4-step RACH. In this case, the UE further uses the 4-step RACH to begin the PRACH procedure. In another example, if the UE performs a 4-step RACH, then when Z exceeds H2 and no RAR message is received, the UE switches to a 2-step RACH. In this case, the UE further uses the 2-step RACH to begin the PRACH procedure.

[0084] Examples of enhancing duty cycle capabilities In 38.306, the UE capability maxUplinkDutyCycle-FR2 is defined as follows. This parameter is for gNB scheduling purposes. If the gNB schedules this percentage of UL transmissions equal to the reported capability during the evaluation period, no UE transmission power backoff is expected.

[0085] According to TS 38.101-2 below, if the UE reports... maxUplinkDutyCycle-FR2 If so, it will perform a two-step process. In step 1, it calculates the uplink duty cycle, which is the percentage of uplink symbols transmitted in any 1-second evaluation period. If it exceeds the threshold provided by the UE, then in step 2, the UE can apply P-MPR. • If UE capability field maxUplinkDutyCycle-FR2 The percentage of uplink symbols present and transmitted within any 1-second evaluation period is greater than [a certain percentage]. maxUplinkDutyCycle-FR2Then the UE follows uplink scheduling and can apply P-MPR. f,c . • If UE capability field maxUplinkDutyCycle-FR2 If it is missing, compliance with electromagnetic power density exposure requirements can be ensured by scaling down the power density or by other means.

[0086] Assuming that the maxUplinkDutyCycle capability is only used for scheduled uplink resources (as specified in 38.306v17.3.0), meaning the gNB schedules UL deliveries based on the reported capability, and no UE deliverable power backoff is expected, we have the following implementation.

[0087] One implementation is that when maxUplinkDutyCycle-FR2 is present, the UE will calculate the UL duty cycle including both scheduled and unscheduled symbols. In other words, all transmitted UL symbols are considered in the UE's calculation of the UL duty cycle, regardless of whether they are scheduled.

[0088] For example, the modified specifications in TS 38.306 could be: maxUplinkDutyCycle-FR2 The indication can be scheduled for use within 1 second. Including unscheduled deliveries (if any). The maximum percentage of uplink symbols transmitted at the UE's maximum transmit power is used to ensure compliance with applicable electromagnetic power density exposure requirements provided by the regulatory authority. This field applies to all power class UEs as specified in FR2 in TS 38.101-2 [3]. Value n15 corresponds to 15%, value n20 corresponds to 20%, and so on. If the field is missing or the percentage of uplink symbols transmitted in any 1s evaluation period is greater than 15%, the maximum percentage of uplink symbols transmitted at the UE's maximum transmit power is used to ensure compliance with applicable electromagnetic power density exposure requirements provided by the regulatory authority. This field applies to all power class UEs as specified in FR2 in TS 38.101-2 [3]. Value n15 corresponds to 15%, value n20 corresponds to 20%, and so on. maxUplinkDutyCycle-FR2 If so, the UE behavior is specified in TS 38.101-2 [3]. This capability is not applicable to IAB-MT.

[0089] Alternatively, another example of the specification modified in TS 38.101-2 could be: If UE capability field maxUplinkDutyCycle-FR2 The percentage of uplink symbols present and transmitted within any 1-second evaluation period is greater than [a certain percentage]. maxUplinkDutyCycle-FR2 Then the UE follows uplink scheduling ( If there are talk ), and P-MPR can be applied f,c .

[0090] Alternatively, the modified specification in TS 38.101-2 could be: If UE capability field maxUplinkDutyCycle-FR2The percentage of uplink symbols present and transmitted within any 1-second evaluation period is greater than [a certain percentage]. maxUplinkDutyCycle-FR2 Then the UE can apply P-MPR f,c .

[0091] An example of the modified specification in TS 38.101-2 could be: If UE capability field maxUplinkDutyCycle-FR2 The percentage of uplink symbols, including any unscheduled symbols, transmitted within any 1-second evaluation period is greater than [a certain percentage]. maxUplinkDutyCycle-FR2 Then the UE follows uplink scheduling and can apply P-MPR. f,c .

[0092] Another embodiment is that UE reporting is used for capabilities different from existing ones. maxUplinkDutyCycle-FR2 A new capability for duty cycle cascading. This capability may only involve P-MPR settings for autonomous transmissions (such as PRACH) used by the UE.

[0093] Figure 1 A flowchart of a possible method embodiment under this disclosure is shown. Method 100 is a method performed by a UE for improving power usage. Step 110 is to determine a reduced power P2 for the PRACH transmission based on the estimated power P1 and one or more applicable factors from a set of factors, the set of factors consisting of: the number of PRACH transmissions(s), operating frequency, RACH type, PRACH retransmission, PRACH repetition, coexistence with other technologies, and the type of process or operation associated with the PRACH transmission. Step 120 is to transmit the PRACH with the reduced power P2. Method 100 may include a variety of additional or alternative steps.

[0094] Figure 2Another flowchart of a possible method embodiment under this disclosure is shown. Method 300 is a method for a UE to calculate an uplink duty cycle and determine a P-MPR setting for unscheduled transmissions. Step 310 is to determine an estimated duty cycle and an estimated P-MPR setting. Step 320 is, when a maxUplinkDutyCycle capability exists, to determine an adjusted duty cycle and an adjusted P-MPR setting based on the estimated duty cycle, the estimated P-MPR setting, and one or more applicable factors from a set of factors consisting of: the percentage of uplink symbols including scheduled and / or unscheduled symbols, and a threshold indication of maxUplinkDutyCycle indicating whether both scheduled and unscheduled signal duty cycles are included. Step 330 is to perform one or more unscheduled transmissions using the adjusted uplink duty cycle and the adjusted P-MPR setting. Method 300 may include a variety of additional or alternative steps.

[0095] Figure 3 Another flowchart of a possible method embodiment under this disclosure is shown. Method 500 is a (computer-implemented) method for improving power usage of a user equipment. Step 510 is to determine an estimated power P1 for PRACH transmission. Step 520 is to determine a reduced power P2 for the PRACH transmission based on the estimated power P1 and one or more applicable factors from a set of factors, the set of factors consisting of: the number of PRACH transmissions(s), operating frequency, RACH type, PRACH retransmission, PRACH repetition, coexistence with other technologies, and the type of process or operation associated with the PRACH transmission. Step 530 is to transmit the PRACH at the reduced power P2. Method 500 may include a variety of additional or alternative steps.

[0096] Figure 4 Another flowchart of a possible method embodiment under this disclosure is shown. Method 700 is a method for improving power usage performed by a network node. Step 710 is to determine an estimated power P1 for PRACH transmission. Step 720 is to determine a reduced power P2 for the PRACH transmission based on the estimated power P1 and one or more applicable factors from a set of factors, the set of factors consisting of: the number of PRACH transmissions(s), operating frequency, RACH type, PRACH retransmission, PRACH repetition, coexistence with other technologies, and the type of process or operation associated with the PRACH transmission. Step 730 is to transmit the PRACH at the reduced power P2. Method 700 may include a variety of additional or alternative steps.

[0097] Figure 5 Another flowchart of a possible method embodiment under this disclosure is shown. Method 900 is a method performed by a network node to calculate the uplink duty cycle and determine the P-MPR setting for unscheduled transmissions. Step 910 is to determine an estimated duty cycle and an estimated P-MPR setting. Step 920 is to determine an adjusted duty cycle and an adjusted P-MPR setting, based on the estimated duty cycle, the estimated P-MPR setting, and one or more applicable factors from a set of factors, when a maxUplinkDutyCycle capability exists. The set of factors consists of: the percentage of uplink symbols including scheduled and / or unscheduled symbols; and a threshold of the maxUplinkDutyCycle indicating whether both scheduled and unscheduled signal duty cycles are included. Step 930 is to perform one or more unscheduled transmissions using the adjusted uplink duty cycle and the adjusted P-MPR setting. Method 900 may include a variety of additional or alternative steps.

[0098] Figure 6 Another flowchart of a possible method embodiment under this disclosure is shown. Method 1100 is a method for performing UL transmission executed by a UE. Method 1100 includes: Step 1110: Determine the UL duty cycle of the UL transmission, including unscheduled transmissions.

[0099] Step 1120: In response to the UL duty cycle being greater than the capability information reported by the UE, a power backoff setting is applied to the transmission power used for the UL transmission to determine the actual transmission power used to perform the UL transmission. The power backoff is applied to comply with electromagnetic power density exposure requirements.

[0100] Step 1130: Use the actual transmission power to transmit the UL transmission.

[0101] In some embodiments, the unscheduled transmission includes Physical Random Access Channel (PRACH) transmission.

[0102] In some embodiments, the capability information indicates the maximum percentage of symbols that can be scheduled for the UL transmission at maximum UE transmission power during a 1s period.

[0103] In some embodiments, the power back-off setting includes Power Management Maximum Power Reduction (P-MPR).

[0104] In some embodiments, the actual transmission power used to perform the UL transmission is a reduced power from the transmission power used for the UL transmission.

[0105] In some embodiments, the transmission power is one of the maximum UE transmission power or the transmission power estimated by the UE.

[0106] In some embodiments, the power backoff settings are adjusted based on one or more of the following factors: the purpose of the PRACH transmission, the number of PRACH transmissions, the operating frequency, the type of RACH process, PRACH retransmission, PRACH repetition, coexistence with other technologies, and the type of process or operation associated with the PRACH transmission.

[0107] Figure 7 Another flowchart of a possible method embodiment under this disclosure is shown. Method 1300 is a method for scheduling UL transmissions performed by a network node. Method 1300 includes: Step 1310: Receive capability information reported by the UE.

[0108] Step 1320: Schedule the UL transmission based on the reported capability information.

[0109] Step 1330: Receive from the UE the UL transmission using the actual transmission power used to perform the UL transmission.

[0110] In method 1300, the actual transmission power is obtained by applying a power backoff setting to the transmission power for the UL transmission in response to the UL transmission including unscheduled transmissions having a UL duty cycle greater than the capability information.

[0111] In some embodiments, the unscheduled transmission includes Physical Random Access Channel (PRACH) transmission.

[0112] In some embodiments, the capability information indicates the maximum percentage of symbols that can be scheduled for the UL transmission at maximum UE transmission power during a 1s period.

[0113] In some embodiments, the power back-off setting includes Power Management Maximum Power Reduction (P-MPR).

[0114] In some embodiments, the actual transmission power used to perform the UL transmission is a reduced power from the transmission power used for the UL transmission.

[0115] In some embodiments, the transmission power is one of the maximum UE transmission power or the transmission power estimated by the UE.

[0116] In some embodiments, the power backoff settings are adjusted based on one or more of the following factors: the purpose of the PRACH transmission, the number of PRACH transmissions, the operating frequency, the type of RACH process, PRACH retransmission, PRACH repetition, coexistence with other technologies, and the type of process or operation associated with the PRACH transmission.

[0117] According to some embodiments of this application, a UE is provided for performing one or more UL transmissions. The UE includes: an antenna configured to transmit and receive wireless signals; and processing circuitry configured to: determine an uplink UL duty cycle for the UL transmission, including unscheduled transmissions; determine an actual transmission power for performing the UL transmission in response to the UL duty cycle being greater than capability information reported by the UE, applying a power backoff setting to the transmission power for the UL transmission to comply with electromagnetic power density exposure requirements; and use the actual transmission power to transmit the UL transmission.

[0118] An example of this type of UE could be Figure 9 The UE QQ200 is shown in the image. For example, the UE QQ200 can be configured to perform actions based on... Figure 6 The above actions.

[0119] According to some embodiments of this application, a network node for scheduling one or more UL transmissions is provided. The network node includes: an antenna configured to transmit and receive wireless signals; and processing circuitry configured to perform the following operations: receiving capability information reported by a user equipment (UE); scheduling the UL transmissions based on the reported capability information; and receiving from the UE the UL transmissions transmitted using actual transmission power for performing the UL transmissions; wherein the actual transmission power is obtained by applying a power backoff setting to the transmission power used for the UL transmissions in response to the UL duty cycle of the UL transmissions, including unscheduled transmissions, being greater than the capability information.

[0120] An example of such a network node could be Figure 10 The network node QQ300 is shown in the image. For example, the network node QQ300 can be configured to perform actions based on... Figure 7 The above actions.

[0121] Figure 8 An example of a communication system QQ100 according to some embodiments is shown.

[0122] In this example, the communication system QQ100 includes a telecommunications network QQ102, which includes an access network QQ104 such as a radio access network (RAN) and a core network QQ106, which includes one or more core network nodes QQ108. The access network QQ104 includes one or more access network nodes, such as network nodes QQ110a and QQ110b (one or more of which may be generally referred to as network node QQ110), or any other similar 3GPP access node or non-3GPP access point. Network node QQ110 facilitates direct or indirect connections of user equipment (UEs), such as connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may be generally referred to as UE QQ112) to the core network QQ106 via one or more radio connections.

[0123] Exemplary wireless communications via wireless connections include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information without the use of wires, cables, or other conductors. Furthermore, in various embodiments, the communication system QQ100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that can facilitate or participate in the transmission of data and / or signals, whether via wired or wireless connections. The communication system QQ100 may include any type of communication, telecommunications, data, cellular, radio network, and / or other similar system and / or be connected to any type of communication, telecommunications, data, cellular, radio network, and / or other similar system via an interface.

[0124] UE QQ112 can be any communication device of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with network node QQ110 and other communication devices. Similarly, network node QQ110 is arranged, capable, configured, and / or operable to communicate directly or indirectly with UE QQ112 and / or with other network nodes or devices in telecommunication network QQ102 to enable and / or provide network access (such as wireless network access) and / or perform other functions (such as management in telecommunication network QQ102).

[0125] In the depicted example, core network QQ106 connects network node QQ110 to one or more hosts (such as host QQ116). These connections can be direct or indirect, via one or more intermediate networks or devices. In other examples, network nodes can be directly coupled to hosts. Core network QQ106 includes one or more core network nodes (e.g., core network node QQ108) constructed from hardware and software components. The characteristics of these components can be substantially similar to those described with respect to the UE, network nodes, and / or hosts, such that the description generally applies to the corresponding components of core network node QQ108. Example core network nodes include functions of one or more of the following: Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-hiding Function (SIDF), Unified Data Management (UDM), Secure Edge Protection Agent (SEPP), Network Open Function (NEF), and / or User Plane Function (UPF).

[0126] The host QQ116 may be owned or controlled by a service provider other than the operator or provider of the telecommunications network QQ102 and / or the access network QQ104, and may be operated by or on behalf of the service provider. The host QQ116 may host various applications to provide one or more services. Examples of such applications include real-time and pre-recorded audio / video content, data collection services (such as retrieving and compiling data about various environmental conditions detected by multiple UEs), analytics functionality, social media, functionality for controlling or otherwise interacting with remote devices, functionality for alarm and monitoring centers, or any other such functionality performed by the server.

[0127] on the whole, Figure 8 The QQ100 communication system enables connectivity between UEs, network nodes, and hosts. In that sense, the communication system can be configured to operate according to predefined rules or procedures, such as specific standards, including but not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi); and / or any other suitable wireless communication standards, such as WiMax, Bluetooth, Z-Wave, Near Field Communication (NFC), ZigBee, LiFi, and / or any Low Power Wide Area Network (LPWAN) standards such as LoRa and Sigfox.

[0128] In some examples, the QQ102 telecommunications network is a cellular network implementing 3GPP standardized features. Therefore, the QQ102 network can support network slicing to provide different logical networks to different devices connected to it. For example, the QQ102 network can provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs while providing enhanced mobile broadband (eMBB) services to other UEs, and / or provide massive machine-type communication (mMTC) / massive IoT services to other remaining UEs.

[0129] In some examples, UE QQ112 is configured to transmit and / or receive information without direct human interaction. For example, the UE may be designed to transmit information to access network QQ104 on a predetermined schedule when triggered by internal or external events or in response to requests from access network QQ104. Additionally, the UE may be configured to operate in single-RAT, multi-RAT, or multi-standard modes. For example, the UE may operate with any or a combination of Wi-Fi, NR (New Radio), and LTE, i.e., configured for multiple radio dual connectivity (MR-DC), such as E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) NR-Dual Connectivity (EN-DC).

[0130] In this example, the central hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112c and / or QQ112d) and a network node (e.g., network node QQ110b). In some examples, the central hub QQ114 can be a controller, router, content source, and analysis tool, or any other communication device described herein with respect to the UE. For example, the central hub QQ114 can be a broadband router for enabling access to the core network QQ106 for the UE. As another example, the central hub QQ114 can be a controller that sends commands or instructions to one or more actuators in the UE. Commands or instructions can be received from the UE, network node QQ110, or through executable code, scripts, procedures, or other instructions in the central hub QQ114. As another example, the central hub QQ114 can be a data collector that acts as a temporary storage device for UE data, and in some embodiments, it can perform data analysis or other processing. As another example, the central hub QQ114 can be a content source. For example, for a UE that is a VR headset, display, speaker, or other media delivery device, the central QQ114 can retrieve VR assets, videos, audio, or other media or data related to sensory information via network nodes. The central QQ114 then provides the VR assets, videos, audio, or other media or data related to sensory information to the UE either directly, after performing local processing, and / or after adding additional local content. In another example, the central QQ114 acts as a proxy server or orchestrator for the UE, particularly if one or more of the UEs are low-power IoT devices.

[0131] The central hub QQ114 may have a constant / persistent or intermittent connection to network node 110b. The central hub QQ114 may also consider different communication schemes and / or scheduling between the central hub QQ114 and the UE (e.g., UE QQ112c and / or QQ112d) and between the central hub QQ114 and the core network QQ106. In other examples, the central hub QQ114 is connected to the core network QQ106 and / or one or more UEs via a wired connection. Furthermore, the central hub QQ114 may be configured to connect to an M2M service provider via access network QQ104 and / or to another UE via a direct connection. In some scenarios, a UE can establish a wireless connection to network node QQ110 while still being connected via the central hub QQ114, either via a wired or wireless connection. In some embodiments, the central hub QQ114 may be a dedicated hub, i.e., a hub whose primary function is to route communication from network node QQ110b to the UE / to route communication from the UE to network node QQ110b. In other embodiments, the central hub QQ114 may be a non-dedicated hub, that is, a device capable of operating to route communication between the UE and the network node QQ110b, but also capable of operating as a communication start and / or end point for certain data channels.

[0132] Figure 9 A UE QQ200 according to some embodiments is illustrated. As used herein, UE refers to a device capable of, configured to, arranged to, and / or operable to wirelessly communicate with network nodes and / or other UEs. Examples of UEs include, but are not limited to, smartphones, mobile phones, cellular phones, Voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptops, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless customer premises equipment (CPEs), vehicle-mounted or vehicle-embedded / integrated wireless devices, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including Narrowband Internet of Things (NB-IoT) UEs, Machine Type Communication (MTC) UEs, and / or Enhanced MTC (eMTC) UEs.

[0133] The UE can support device-to-device (D2D) communication, for example, by implementing 3GPP standards for cut-through link communication, Dedicated Short Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, the UE may not necessarily be a user in the sense of a human user who owns and / or operates the associated device. Instead, the UE may represent a device intended for sale to or operated by a human user but which may not or can not initially be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, the UE may represent a device not intended for sale to or operated by an end user but which may be associated with or operated for the benefit of a user (e.g., a smart meter).

[0134] UE QQ200 includes processing circuitry QQ202, which is operatively coupled via bus QQ204 to input / output interface QQ206, power supply QQ208, memory QQ210, communication interface QQ212, and / or any other component, or any combination thereof. Some UEs may utilize... Figure 9 All or a subset of the components shown. The level of integration between components can vary from one UE to another. Furthermore, some UEs may contain multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0135] The processing circuit QQ202 is configured to process instructions and data and can be configured to implement any sequential state machine whose operations are used to execute instructions stored in memory QQ210 as a machine-readable computer program. The processing circuit QQ202 can be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, a general-purpose processor such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuit QQ202 may include multiple central processing units (CPUs).

[0136] In this example, the input / output interface QQ206 can be configured to provide interfaces or multiple interfaces to input devices, output devices, or one or more input and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, transmitters, smart cards, other output devices, or any combination thereof. Input devices can allow users to capture information into the UE QQ200. Examples of input devices include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital camcorders, webcams, etc.), microphones, sensors, mice, trackballs, orientation pads, trackpads, scroll wheels, smart cards, and the like. Presence-sensitive displays may include capacitive or resistive touch sensors to sense input from the user. Sensors may be, for example, accelerometers, gyroscopes, tilt sensors, force sensors, magnetometers, light sensors, proximity sensors, biosensors, etc., or any combination thereof. Output devices can use the same type of interface port as input devices. For example, a Universal Serial Bus (USB) port can be used to provide input and output devices.

[0137] In some embodiments, the power source QQ208 is configured as a battery or battery pack. Other types of power sources, such as external power sources (e.g., electrical outlets), photovoltaic devices, or power cells, can be used. The power source QQ208 may further include power circuitry for delivering power from the power source QQ208 itself and / or external power sources to various parts of the UE QQ200 via an interface or input circuitry such as a power cable. The power delivery may be used, for example, for charging the power source QQ208. The power circuitry may perform any formatting, conversion, or other modifications on the power from the power source QQ208 to suit the power for the corresponding components of the powered UE QQ200.

[0138] The memory QQ210 can be or is configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), disk, optical disk, hard disk, removable cassette tape, flash drive, etc. In one example, the memory QQ210 includes one or more application programs QQ214 (such as an operating system, web browser application, widget, gadget engine, or other application) and corresponding data QQ216. The memory QQ210 can store any operating system or combination of operating systems from a wide variety of different operating systems used by the UE QQ200.

[0139] The QQ210 memory can be configured to include multiple physical drive units such as a redundant array of independent disks (RAID), flash memory, USB flash drive, external hard drive, thumb drive, pen drive, key drive, high-density digital universal disc (HD-DVD) optical disc drive, internal hard drive, Blu-ray disc drive, holographic digital data storage (HDDS) optical disc drive, external mini dual in-line memory modules (DIMM), synchronous dynamic random access memory (SDRAM), external micro DIMM SDRAM, tamper-proof smart card memory such as a Universal Integrated Circuit Card (UICC) (including one or more subscriber identity modules (SIM) such as USIM and / or ISIM), other memory, or any combination thereof. The UICC can be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly referred to as a "SIM card". The QQ210 memory can allow the UE QQ200 to access instructions, applications, and such to unload or upload data stored on transient or non-transient storage media. Articles of manufacture, such as those utilizing communication systems, may be tangibly implemented as or contained in a memory QQ210, which may be or include a device-readable storage medium.

[0140] The processing circuitry QQ202 can be configured to communicate with an access network or other network using a communication interface QQ212. The communication interface QQ212 may include one or more communication subsystems and may include or be communicatively coupled to an antenna QQ222. The communication interface QQ212 may include one or more transceivers for communication, such as through communication with another device capable of wireless communication (e.g., a network node in the access network or another UE). Each transceiver may include a transmitter QQ218 and / or a receiver QQ220 adapted to provide network communication (e.g., optical, electrical, frequency allocation, etc.). Furthermore, the transmitter QQ218 and receiver QQ220 may be coupled to one or more antennas (e.g., antenna QQ222) and may share circuit components, software, or firmware, or alternatively, the transmitter QQ218 and receiver QQ220 may be implemented separately.

[0141] In the illustrated embodiment, the communication functions of the communication interface QQ212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication such as using a Global Positioning System (GPS) to determine location, another similar communication function, or any combination thereof. Communication may be implemented according to one or more communication protocols and / or standards such as IEEE 802.11, Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), etc.

[0142] Regardless of the sensor type, the UE can provide the output of data captured by its sensors via its communication interface QQ212, through a wireless connection to a network node. Data captured by a UE's sensors can be transmitted via another UE, also through a wireless connection to a network node. The output can be periodic (e.g., every 14 minutes if it reports sensed temperature), random (e.g., balancing the load of reports from several sensors), responsive to a triggered event (e.g., sending an alarm when humidity is detected), responsive to a request (e.g., a user-initiated request), or a continuous stream (e.g., real-time video feed of a patient).

[0143] As another example, the UE includes actuators, motors, or switches associated with a communication interface configured to receive wireless input from a network node via a wireless connection. The state of the actuator, motor, or switch can change in response to the received wireless input. For example, the UE may include control surfaces or rotors of a drone in flight that adjust based on the received input, or motors of a robotic arm performing medical procedures that adjust based on the received input.

[0144] When a UE is in the form of an Internet of Things (IoT) device, it can be a device for use in one or more application domains, including but not limited to urban wearable technology, extended industrial applications, and healthcare. Non-limiting examples of such IoT devices are devices or devices embedded in the following: connected refrigerators or freezers, TVs, connected lighting devices, electricity meters, robotic vacuum cleaners, voice-controlled smart speakers, home security cameras, motion detectors, thermostats, smoke detectors, door / window sensors, flood / humidity sensors, electric door locks, connected doorbells, heat pump-like air conditioning systems, autonomous vehicles, monitoring systems, weather monitoring devices, vehicle parking monitoring devices, electric vehicle charging stations, smartwatches, fitness trackers, head-mounted displays for augmented reality (AR) or virtual reality (VR), wearable devices for haptic or sensory enhancement, sprinklers, animal or object tracking devices, sensors for monitoring plants or animals, industrial robots, unmanned aerial vehicles (UAVs), and any kind of medical device such as heart rate monitors or remotely controlled surgical robots. (Except as per the above...) Figure 9 In addition to the other components described in UE QQ200 shown, UEs in the form of IoT devices include circuitry and / or software that depend on the intended application of the IoT device.

[0145] As another specific example, in IoT scenarios, a UE can represent a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to another UE and / or network node. In this case, the UE can be an M2M device, which may be referred to as an MTC device in the 3GPP context. As a specific example, the UE can implement the 3GPP NB-IoT standard. In other scenarios, the UE can represent a vehicle, such as a car, bus, truck, ship, or aircraft, or other device capable of monitoring and / or reporting its operational status or other functions associated with its operation.

[0146] In practice, any number of UEs can be used together for a single use case. For example, the first UE can be an unmanned aerial vehicle (UAV) or can be integrated into an UAV and provide the UAV's speed information (obtained via a speed sensor) to a second UE, which acts as a remote controller for operating the UAV. When the user makes a change from the remote controller, the first UE can adjust a throttle valve on the UAV (e.g., by controlling an actuator) to increase or decrease the UAV's speed. The first and / or second UEs can also include more than one of the functionalities described above. For example, the UE can include sensors and actuators and handle the transmission of data from both the speed sensor and the actuator.

[0147] Figure 10A network node QQ300 according to some embodiments is illustrated. As used herein, a network node refers to a device that is capable of, configured to, arranged to, and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or devices in a telecommunications network. Examples of network nodes include, but are not limited to, access points (Ap) (e.g., radio access points) and base stations (BS) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)).

[0148] Base stations can be classified based on the coverage they provide (or, in other words, their transmission power levels), and therefore, depending on the coverage provided, a base station can be referred to as a femtocell, picocell, microcell, or macrocell. A base station can be a relay node or a relay donor node controlling a relay. A network node can also include one or more (or all) portions of a distributed radio base station such as a centralized digital unit and / or a remote radio unit (RRU) sometimes referred to as a remote radio headend (RRH). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio device. A portion of a distributed radio base station can also be referred to as a node in a distributed antenna system (DAS).

[0149] Other examples of network nodes include multi-transport point (multi-TRP) 5G access nodes, multi-standard radio (MSR) devices such as MSR BS, network controllers such as radio network controllers (RNC) or base station controllers (BSC), base transceiver stations (BTS), transport points, transport nodes, multi-cell / multicast coordination entities (MCE), operation and maintenance (O&M) nodes, operation support system (OSS) nodes, self-organizing network (SON) nodes, location nodes (such as evolved servicing mobile location centers (E-SMLC)), and / or minimized drive tests (MDT).

[0150] Network node QQ300 includes processing circuitry QQ302, memory QQ304, communication interface QQ306, and power supply QQ308. Network node QQ300 may consist of multiple physically separate components (e.g., NodeB components and RNC components, or BTS components and BSC components, etc.), each of which may have its own corresponding components. In some scenarios where network node QQ300 includes multiple separate components (e.g., BTS and BSC components), one or more of these separate components may be shared among several network nodes. For example, a single RNC can control multiple NodeBs. In such scenarios, each unique NodeB and RNC pair may be considered a single independent network node in some instances. In some embodiments, network node QQ300 may be configured to support multiple Radio Access Technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory QQ304 for different RATs) and some components may be reused (e.g., the same antenna QQ310 may be shared by different RATs). The network node QQ300 may also include multiple sets of components for integrating various wireless technologies, such as GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, RFID, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chips or chipsets and other components within the network node QQ300.

[0151] The processing circuitry QQ302 may include a combination of one or more of the following: a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array or any other suitable computing device, resource, or combination of hardware, software and / or coding logic, which is operable to provide network node QQ300 functionality, either alone or in combination with other network node QQ300 components such as memory QQ304.

[0152] In some embodiments, the processing circuit QQ302 includes a system-on-a-chip (SOC). In some embodiments, the processing circuit QQ302 includes one or more of a radio frequency (RF) transceiver circuit QQ312 and a baseband processing circuit QQ314. In some embodiments, the RF transceiver circuit QQ312 and the baseband processing circuit QQ314 may be on separate chips (or chipsets), boards, or units such as radio units and digital units. In alternative embodiments, some or all of the RF transceiver circuit QQ312 and the baseband processing circuit QQ314 may be on the same chip or chipset, board, or unit.

[0153] The memory QQ304 may include any form of volatile or non-volatile computer-readable memory, including but not limited to persistent storage devices, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drives, CDs, or DVDs), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory that stores information, data, and / or instructions that can be used by the processing circuitry QQ302. The memory QQ304 may store any suitable instructions, data, or information, including computer programs, software, applications (including logic, rules, code, tables, or one or more), and / or other instructions that can be executed by the processing circuitry QQ302 and utilized by the network node QQ300. The memory QQ304 may be used to store any calculations performed by the processing circuitry QQ302 and / or any data received via the communication interface QQ306. In some embodiments, the processing circuitry QQ302 and the memory QQ304 are integrated.

[0154] A communication interface QQ306 is used for wired or wireless transmission of signaling and / or data between network nodes, access networks, and / or UEs. As shown, the communication interface QQ306 includes one or more ports / terminals QQ316 for transmitting data to and receiving data from the network, for example, via a wired connection. The communication interface QQ306 also includes a radio front-end circuit QQ318 that can be coupled to or is part of the antenna QQ310 in some embodiments. The radio front-end circuit QQ318 includes a filter QQ320 and an amplifier QQ322. The radio front-end circuit QQ318 can be connected to the antenna QQ310 and the processing circuit QQ302. The radio front-end circuit can be configured to modulate the signal transmitted between the antenna QQ310 and the processing circuit QQ302. The radio front-end circuit QQ318 can receive digital data to be transmitted to other network nodes or UEs via a wireless connection. The radio front-end circuit QQ318 can use a combination of the filter QQ320 and / or the amplifier QQ322 to convert the digital data into radio signals with appropriate channel and bandwidth parameters. Radio signals can then be transmitted via antenna QQ310. Similarly, upon receiving data, antenna QQ310 can collect radio signals and then convert them into digital data via radio front-end circuitry QQ318. The digital data can then be transmitted to processing circuitry QQ302. In other embodiments, the communication interface may include different components and / or different combinations of components.

[0155] In some alternative embodiments, network node QQ300 does not include a separate radio front-end circuit QQ318; instead, processing circuitry QQ302 includes the radio front-end circuitry and is connected to antenna QQ310. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ312 is part of communication interface QQ306. In other embodiments, communication interface QQ306 includes one or more ports or terminals QQ316, radio front-end circuitry QQ318, and RF transceiver circuitry QQ312 as part of a radio unit (not shown), and communication interface QQ306 communicates with baseband processing circuitry QQ314, which is part of a digital unit (not shown).

[0156] Antenna QQ310 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna QQ310 may be coupled to radio front-end circuitry QQ318 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna QQ310 is decoupled from network node QQ300 and may be connected to network node QQ300 via an interface or port.

[0157] Antenna QQ310, communication interface QQ306, and / or processing circuitry QQ302 can be configured to perform any receive operation and / or certain acquire operation described herein as being performed by a network node. Any information, data, and / or signals can be received from the UE, another network node, and / or any other network device. Similarly, antenna QQ310, communication interface QQ306, and / or processing circuitry QQ302 can be configured to perform any transmit operation described herein as being performed by a network node. Any information, data, and / or signals can be transmitted to the UE, another network node, and / or any other network device.

[0158] Power source QQ308 provides power to the various components of network node QQ300 in a form suitable for the respective components (e.g., at the voltage and current levels required by each respective component). Power source QQ308 may further include or be coupled to power management circuitry to power the components of network node QQ300 for performing the functionality described herein. For example, network node QQ300 may be connected to an external power source (e.g., the power grid, electrical outlet) via input circuitry or interface such as a cable, thereby supplying power to the electrical circuitry of power source QQ308. As another example, power source QQ308 may include a power source in the form of a battery or battery pack, connected to or integrated into the electrical circuitry. The battery can provide backup power in the event of an external power source failure.

[0159] Implementations of the network node QQ300 may include, except Figure 10 Additional components beyond those shown herein are used to provide certain aspects of the functionality of the network node, including any functionality described herein and / or any functionality necessary to support the topics described herein. For example, the network node QQ300 may include user interface devices for allowing information to be input to and output from the network node QQ300. This allows the user to perform diagnostic, maintenance, repair, and other management functions for the network node QQ300.

[0160] Figure 11 This is a block diagram of the QQ400 host based on the various aspects described in this article. The QQ400 host can be... Figure 8 The embodiment of host QQ116. As used herein, host QQ400 can be or includes various combinations of hardware and / or software, including standalone servers, blade servers, cloud-implemented servers, distributed servers, virtual machines, containers, or processing resources in a server farm. Host QQ400 can provide one or more services to one or more UEs.

[0161] The host QQ400 includes processing circuitry QQ402, which is operatively coupled via bus QQ404 to input / output interface QQ406, network interface QQ408, power supply QQ410, and memory QQ412. Other components may be included in other embodiments. The characteristics of these components may be substantially similar to those described with respect to the apparatus of the previous figures (such as Figures QQ2 and QQ3), such that the description generally applies to the corresponding components of the host QQ400.

[0162] Memory QQ412 may contain one or more computer programs, including one or more host applications QQ414 and data QQ416. Data QQ416 may contain user data, such as data generated by the UE for the host QQ400 or data generated by the host QQ400 for the UE. Embodiments of the host QQ400 may utilize only a subset or all of the components shown. The host application QQ414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Universal Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, and g.711), including transcoding for multiple different categories, types, or implementations of the UE (e.g., mobile phones, desktop computers, wearable display systems, head-up display systems). The host application QQ414 may also provide user authentication and authorization checks and may periodically report health, routing, and content availability to a central node (such as a device in the core network or at the edge). Therefore, the host QQ400 can select and / or indicate different hosts for the UE to use for overhead services. The host application QQ414 can support various protocols, such as HTTP Live Streaming (HLS), Real-time Messaging Protocol (RTMP), Real-time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0163] Figure 12 This is a block diagram illustrating a virtualization environment QQ500 in which functionality implemented by some embodiments can be virtualized. In this context, virtualization means creating a virtual version of a device or apparatus, which may include a virtualized hardware platform, storage device, and networking resources. As used herein, virtualization can be applied to any apparatus or component thereof described herein and relates to the implementation of at least a portion of its functionality as one or more virtual components. Some or all of the functionality described herein can be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments QQ500 hosted by one or more hardware nodes, such as hardware computing devices operating as network nodes, UEs, core network nodes, or hosts. Furthermore, in embodiments where virtual nodes do not require radio connectivity (e.g., core network nodes or hosts), the nodes can be fully virtualized.

[0164] Running the application QQ502 (which may alternatively be referred to as a software instance, virtual device, network function, virtual node, virtual network function, etc.) in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0165] The hardware QQ504 includes processing circuitry, memory storing software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices as described herein, such as network interfaces, input / output interfaces, etc. The processing circuitry can execute software to instantiate one or more virtualization layers QQ506 (also referred to as a hypervisor or virtual machine monitor (VMM)), provide VMs QQ508a and QQ508b (one or more of which may be commonly referred to as VM QQ508), and / or perform any of the functions, features, and / or benefits described in relation to some embodiments described herein. The virtualization layer QQ506 can present a virtual operating platform to the VM QQ508 that appears to be networked hardware.

[0166] VM QQ508 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage devices, and can run through the corresponding virtualization layer QQ506. Different embodiments of instances of virtual device QQ502 can be implemented on one or more VMs in VM QQ508, and can be implemented in different ways. Hardware virtualization is referred to as Network Functions Virtualization (NFV) in some contexts. NFV can be used to consolidate many types of network devices into industry-standard high-capacity server hardware, physical switches, and physical storage devices that can be located in data centers and customer premises.

[0167] In the context of NFV, a VM QQ508 can be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each VM in a VM QQ508, and the portion of the hardware QQ504 that executes that VM—whether it's hardware dedicated to that VM and / or hardware shared by that VM and other VMs within it—forms an independent virtual network element. Still within the NFV context, the virtual network function is responsible for handling specific network functions running on top of the hardware QQ504 in one or more VM QQ508s and corresponds to the application QQ502.

[0168] Hardware QQ504 can be implemented in standalone network nodes with general or specific components. Hardware QQ504 can utilize virtualization to achieve some of its functions. Alternatively, hardware QQ504 can be part of a larger hardware cluster (e.g., in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration QQ510, which in particular also oversees the lifecycle management of application QQ502. In some embodiments, hardware QQ504 is coupled to one or more radio units, each including one or more transmitters and one or more receivers that can be coupled to one or more antennas. The radio units can communicate directly with other hardware nodes via one or more suitable network interfaces and can be combined with virtual components to provide radio capabilities to virtual nodes, such as radio access nodes or base stations. In some embodiments, a control system QQ512 can be used to provide signaling, which can alternatively be used for communication between hardware nodes and radio units.

[0169] Figure 13 A communication diagram is shown illustrating communication between host QQ602 and UE QQ606 via a partial wireless connection through network node QQ604, according to some embodiments. Reference will now be made to... Figure 13 Describe the UEs discussed in the preceding paragraphs (such as...) Figure 8 UE QQ112a and / or Figure 9 UE QQ200), network nodes (such as Figure 8 Network node QQ110a and / or Figure 10 Network node QQ300) and host (such as Figure 8 The host QQ116 and / or Figure 11 Example implementations of the host QQ400 according to various embodiments.

[0170] Similar to host QQ400, embodiments of host QQ602 include hardware such as a communication interface, processing circuitry, and memory. Host QQ602 also includes software stored in or accessible by host QQ602 and executable by the processing circuitry. This software includes a host application operable to provide services to remote users, such as UE QQ606 connected via an over-the-top (OTT) connection QQ650 extended between UE QQ606 and host QQ602. When providing services to remote users, the host application can provide user data transmitted using the OTT connection QQ650.

[0171] Network node QQ604 contains the hardware that enables it to communicate with host QQ602 and UE QQ606. Connection to QQ660 can be direct or via a core network (like...). Figure 8 The core network (QQ106) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network could be a backbone network or the Internet.

[0172] The UE QQ606 comprises hardware and software stored within or accessible by the UE QQ606 and executable by the UE processing circuitry. The software includes client applications, such as web browsers or carrier-specific "apps," operable to provide services to human or non-human users via the UE QQ606 with the support of the host QQ602. In the host QQ602, the executing host application can communicate with the executing client application via an OTT connection QQ650 terminated between the UE QQ606 and the host QQ602. When providing services to a user, the UE's client application can receive request data from the host application of the host and provide user data in response to that request data. The OTT connection QQ650 can transmit both request data and user data. The UE's client application can interact with the user to generate user data, which it then provides to the host application via the OTT connection QQ650.

[0173] The OTT connection QQ650 can be extended via connection QQ660 between host QQ602 and network node QQ604, and via wireless connection QQ670 between network node QQ604 and UE QQ606, to provide connectivity between host QQ602 and UE QQ606. Connection QQ660 and wireless connection QQ670, on which the OTT connection QQ650 can be provided, have been abstractly drawn to illustrate communication between host QQ602 and UE QQ606 via network node QQ604, without explicitly referring to any intermediate devices and the precise routing of messages via these devices.

[0174] As an example of data transmission via OTT connection QQ650, in step QQ608, host QQ602 provides user data, which can be performed by executing a host application. In some embodiments, the user data is associated with a specific human user interacting with UE QQ606. In other embodiments, the user data is associated with UE QQ606, which shares data with host QQ602 without explicit human interaction. In step QQ610, host QQ602 initiates a transmission carrying user data toward UE QQ606. Host QQ602 may initiate the transmission in response to a request transmitted by UE QQ606. This request may be caused by human interaction with UE QQ606 or by operation of a client application executed on UE QQ606. According to the teachings of the embodiments described throughout this disclosure, the transmission may be carried out via network node QQ604. Therefore, in step QQ612, according to the teachings of the embodiments described throughout this disclosure, network node QQ604 transmits the user data carried in the transmission initiated by host QQ602 to UE QQ606. In step QQ614, UE QQ606 receives the user data carried in the transmission, which can be performed by a client application running on UE QQ606 associated with a host application running with host QQ602.

[0175] In some examples, UE QQ606 executes a client application that provides user data to host QQ602. The user data can be provided as a response or reaction to data received from host QQ602. Therefore, in step QQ616, UE QQ606 can provide user data, which can be done by executing the client application. When providing user data, the client application may also consider user input received from a user via the input / output interface of UE QQ606. Regardless of the specific manner in which the user data is provided, in step QQ618, UE QQ606 initiates the transmission of user data to host QQ602 via network node QQ604. In step QQ620, in accordance with the teachings of the embodiments described throughout this disclosure, network node QQ604 receives user data from UE QQ606 and initiates the transmission of the received user data to host QQ602. In step QQ622, host QQ602 receives the user data carried in the transmission initiated by UE QQ606.

[0176] One or more embodiments in various implementations use an OTT connection QQ650 to improve the performance of OTT services provided to the UE QQ606, wherein a wireless connection QQ670 forms the final segment. More specifically, the teachings of these embodiments can improve data rates, latency, or power consumption, and thus provide benefits such as reduced user wait times, more lenient restrictions on file size, improved content resolution, better responsiveness, and extended battery life.

[0177] In the example scenario, factory status information can be collected and analyzed by the host QQ602. As another example, the host QQ602 can process audio and video data already acquired from the UE for map creation. As another example, the host QQ602 can collect and analyze real-time data to help control traffic congestion (e.g., control traffic lights). As another example, the host QQ602 can store surveillance video uploaded by the UE. As another example, the host QQ602 can store or control access to media content, such as video, audio, VR, or AR, which can be broadcast, multicast, or unicast to the UE. As other examples, the host QQ602 can be used for energy pricing, remote control of non-time-critical electrical loads to balance generation demand, location services, presentation services (such as compiled maps based on data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing, and / or transmitting data.

[0178] In some examples, measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors that improve upon one or more of the embodiments. Optional network functionality may also be available for reconfiguring the OTT connection QQ650 between host QQ602 and UE QQ606 in response to changes in measurement results. Measurement procedures and / or network functionality for reconfiguring the OTT connection may be implemented in the software and hardware of host QQ602 and / or in the software and hardware of UE QQ606. In some embodiments, sensors (not shown) may be deployed in or associated with other devices traversed by the OTT connection QQ650; the sensors may participate in the measurement procedure by supplying values ​​of the monitored quantities as described above or by supplying values ​​of other physical quantities from which the software can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection QQ650 may include message formats, retransmission settings, preferred routing, etc.; reconfiguration does not require direct changes to the operation of network node QQ604. Such procedures and functionality may be known and practiced in the art. In some embodiments, the measurements may involve dedicated UE signaling, which helps the host QQ602 to measure throughput, propagation time, latency, and the like. These measurements can be implemented because the software uses an OTT connection to QQ650 to transmit messages (especially empty or "fake" messages) while monitoring propagation time, errors, etc.

[0179] While the computing devices described herein (e.g., UE, network node, host) may comprise combinations of the hardware components shown, other examples may include computing devices with different combinations of components. It should be understood that these computing devices may include any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. The determination, calculation, acquisition, or similar operations described herein may be performed by processing circuitry that processes information by, for example, converting acquired information into other information, comparing the acquired or converted information with information stored in a network node, and / or performing one or more operations based on the acquired or converted information, and making a determination as a result of said processing. Furthermore, although components are depicted as individual boxes located within larger boxes or nested within multiple boxes, in practice, a computing device may comprise multiple different physical components constituting a single illustrated component, and functionality may be partitioned among the individual components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any such component may be implemented in software or firmware, and computationally intensive functions may be implemented in hardware.

[0180] In some embodiments, some or all of the functionality described herein may be provided by processing circuitry that executes instructions stored in memory, which in some embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, the processing circuitry may be configured to perform the described functionality regardless of whether instructions stored on a non-transitory computer-readable storage medium are executed. The benefits provided by such functionality are not limited to individual processing circuitry or other components of the computing device, but are enjoyed by the computing device as a whole and / or generally by the end user and wireless network.

[0181] Some exemplary embodiments of this disclosure are as follows: Example

[0182] Group A Implementation Examples 1. A method for improving power utilization, performed by a user equipment, the method comprising: Determine the estimated power P1 for PRACH transmission; The reduced power P2 for the PRACH transmission is determined based on the estimated power P1 and one or more applicable factors from a set of factors consisting of the following: The number of PRACH transmissions (one or more) Operating frequency RACH type, PRACH retransmission PRACH repeats, Coexistence with other technologies, and The type of process or operation associated with the PRACH transmission; and The PRACH is transmitted at the reduced power P2.

[0183] 2. The method as described in Example 1, wherein the reduced power P2 is calculated as the difference between the estimated power P1 and the power P2, wherein the difference is determined based on the one or more factors.

[0184] 3. The method as described in Example 2, wherein the estimated power P1 and the reduced power P2 are determined in dBm, and the difference is measured in dB.

[0185] 4. A method for a user equipment to calculate the uplink duty cycle and determine the P-MPR setting for unscheduled transmissions, the method comprising the following steps: Determine the estimated duty cycle and the estimated P-MPR settings; When the capacity maxUplinkDutyCycle exists, the adjusted duty cycle and the adjusted P-MPR setting are determined based on the estimated duty cycle, the estimated P-MPR setting, and one or more applicable factors from a set of factors consisting of the following: The percentage of uplink symbols, including scheduled and / or unscheduled symbols; and The threshold indication of maxUplinkDutyCycle includes both scheduled and unscheduled signal dutyCycles; and Use the adjusted uplink duty cycle and adjusted P-MPR settings to perform one or more unscheduled transmissions.

[0186] 5. The method as described in any of the foregoing embodiments further includes: Provide user data; and The user data is forwarded to the host via transmission to network nodes.

[0187] 6. A (computer-implemented) method for improving power usage of user equipment, comprising: Determine the estimated power P1 for PRACH transmission; The reduced power P2 for the PRACH transmission is determined based on the estimated power P1 and one or more applicable factors from a set of factors consisting of the following: The number of PRACH transmissions (one or more) Operating frequency RACH type, PRACH retransmission PRACH repeats, Coexistence with other technologies, and The type of process or operation associated with the PRACH transmission; and The PRACH is transmitted at the reduced power P2.

[0188] 7. A system for improving power utilization, comprising processing circuitry and a memory, the memory containing instructions executable by the processing circuitry, thereby enabling the system / device to: Determine the estimated power P1 for PRACH transmission; The reduced power P2 for the PRACH transmission is determined based on the estimated power P1 and one or more applicable factors from a set of factors consisting of the following: The number of PRACH transmissions (one or more) Operating frequency RACH type, PRACH retransmission PRACH repeats, Coexistence with other technologies, and The type of process or operation associated with the PRACH transmission; and The PRACH is transmitted at the reduced power P2.

[0189] Group B Implementation Example 8. A method for improving power utilization, performed by a network node, the method comprising: Determine the estimated power P1 for PRACH transmission; The reduced power P2 for the PRACH transmission is determined based on the estimated power P1 and one or more applicable factors from a set of factors consisting of the following: The number of PRACH transmissions (one or more) Operating frequency RACH type, PRACH retransmission PRACH repeats, Coexistence with other technologies, and The type of process or operation associated with the PRACH transmission; and The PRACH is transmitted at the reduced power P2.

[0190] 9. The method as described in Example 8, wherein the reduced power P2 is calculated as the difference between the estimated power P1 and the power P2, wherein the difference is determined based on the one or more factors.

[0191] 10. The method as described in Example 9, wherein the estimated power P1 and the reduced power P2 are determined in dBm, and the difference is measured in dB.

[0192] 11. A method for calculating uplink duty cycle and determining P-MPR settings for unscheduled transmissions, performed by a network node, the method comprising the steps of: Determine the estimated duty cycle and the estimated P-MPR settings; When the capacity maxUplinkDutyCycle exists, the adjusted duty cycle and the adjusted P-MPR setting are determined based on the estimated duty cycle, the estimated P-MPR setting, and one or more applicable factors from a set of factors consisting of the following: The percentage of uplink symbols, including scheduled and / or unscheduled symbols; and The threshold indication of maxUplinkDutyCycle includes both scheduled and unscheduled signal dutyCycles; and Use the adjusted uplink duty cycle and adjusted P-MPR settings to perform one or more unscheduled transmissions.

[0193] 12. The method as described in any of the foregoing embodiments further includes: Obtaining user data; and Forward the user data to the host or user device.

[0194] Group C Implementation Example 13. A user equipment for improving power utilization, comprising: Processing circuitry configured to perform any step as described in any of the embodiments of group A; and A power supply circuit configured to supply power to the processing circuit.

[0195] 14. A network node for improved power utilization, the network node comprising: Processing circuitry configured to perform any of the steps described in any of the Group B embodiments; A power supply circuit configured to supply power to the processing circuit.

[0196] 15. A user equipment (UE) for improved power utilization, the UE comprising: An antenna configured to transmit and receive wireless signals; A radio front-end circuit, which is connected to the antenna and to the processing circuit, and configured to modulate the signal transmitted between the antenna and the processing circuit; The processing circuitry is configured to perform any step as described in any of the embodiments of Group A; An input interface, which is connected to the processing circuitry and configured to allow input of information to be processed by the processing circuitry into the UE; An output interface, connected to the processing circuit, and configured to output information from the UE that has been processed by the processing circuit; and A battery, which is connected to the processing circuit and configured to supply power to the UE.

[0197] 16. A host configured to operate in a communication system to provide over-the-top (OTT) services, the host comprising: Processing circuitry configured to provide user data; and A network interface configured to initiate the transmission of the user data to a cellular network for transmission to a user equipment (UE). The UE includes a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any step as described in any of the embodiments of Group A to receive the user data from the host.

[0198] 17. The host as described in the preceding embodiment, wherein the cellular network further includes network nodes configured to communicate with the UE to transmit the user data from the host to the UE.

[0199] 18. The host as described in any one of the two embodiments above, wherein: The host's processing circuitry is configured to execute a host application, thereby providing the user data; and The host application is configured to interact with a client application running on the UE, the client application being associated with the host application.

[0200] 19. A method implemented by a host operating in a communication system further comprising network nodes and user equipment (UE), the method comprising: Provide user data for the UE; and The transmission of the user data to the UE is initiated via a cellular network including the network node, wherein the UE performs any operation as described in any of the Group A embodiments to receive the user data from the host.

[0201] 20. The method as described in the foregoing embodiment further includes: On the host, a host application associated with a client application running on the UE is executed to receive the user data from the UE.

[0202] 21. The method as described in the foregoing embodiment further includes: On the host, input data is transmitted to the client running on the UE, the input data being provided by executing the host application. The user data is provided via the client application in response to the input data from the host application.

[0203] 22. A host configured to operate in a communication system to provide over-the-top (OTT) services, the host comprising: Processing circuitry configured to provide user data; and A network interface configured to initiate the transmission of the user data to a cellular network for transmission to a user equipment (UE). The UE includes a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps described in any of the Group A embodiments to transmit the user data to the host.

[0204] 23. The host as described in the preceding embodiment, wherein the cellular network further includes network nodes configured to communicate with the UE to transmit the user data from the UE to the host.

[0205] 24. The host as described in any one of the two embodiments above, wherein: The host's processing circuitry is configured to execute a host application, thereby providing the user data; and The host application is configured to interact with a client application running on the UE, the client application being associated with the host application.

[0206] 25. A method implemented by a host configured to operate in a communication system further comprising network nodes and user equipment (UE), the method comprising: The host receives user data transmitted by the UE to the host via the network node, wherein the UE performs any of the steps as described in any of the Group A embodiments to transmit the user data to the host.

[0207] 26. The method as described in the foregoing embodiment further includes: On the host, a host application associated with a client application running on the UE is executed to receive the user data from the UE.

[0208] 27. The method as described in the foregoing embodiment further includes: On the host, input data is transmitted to the client running on the UE, the input data being provided by executing the host application. The user data is provided via the client application in response to the input data from the host application.

[0209] 28. A host configured to operate in a communication system to provide over-the-top (OTT) services, the host comprising: Processing circuitry configured to provide user data; and A network interface configured to initiate the transmission of user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node being configured to perform any of the operations described in any of the Group B embodiments to transmit the user data from the host to the UE.

[0210] 29. The host as described in the preceding embodiment, wherein: The processing circuitry of the host is configured to execute a host application that provides the user data; and The UE includes processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.

[0211] 30. A method implemented in a host configured to operate in a communication system further comprising network nodes and user equipment (UE), the method comprising: Provide user data for the UE; and Initiate a transmission carrying the user data to the UE via a cellular network including the network node, wherein the network node performs any of the operations described in any of the Group B embodiments to transmit the user data from the host to the UE.

[0212] 31. The method as described in the preceding embodiment further includes, at the network node, transmitting the user data provided by the host to the UE.

[0213] 32. The method of any one of the foregoing two embodiments, wherein the user data is provided on the host by executing a host application that interacts with a client application executed on the UE, the client application being associated with the host application.

[0214] 33. A communication system configured to provide overhead services, the communication system comprising: The host includes: Processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the overlay service; and A network interface configured to initiate the transmission of user data to a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node being configured to perform any of the operations described in any of the Group B embodiments to transmit the user data from the host to the UE.

[0215] 34. The communication system as described in the foregoing embodiment further includes: The network node; and / or The user equipment.

[0216] 35. A host configured to operate in a communication system to provide over-the-top (OTT) services, the host comprising: Processing circuitry configured to initiate the reception of user data; and A network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node being configured to perform any operation as described in any of the Group B embodiments to receive the user data from the user equipment (UE) for the host.

[0217] 36. The host as described in the two embodiments above, wherein: The host's processing circuitry is configured to execute a host application, thereby providing the user data; and The host application is configured to interact with a client application running on the UE, the client application being associated with the host application.

[0218] 37. The host as described in any one of the two embodiments above, wherein the initiated reception of the user data includes requesting the user data.

[0219] 38. A method implemented by a host configured to operate in a communication system further comprising network nodes and user equipment (UE), the method comprising: The host initiates the reception of user data from the UE, the user data originating from a transmission that the network node has already received from the UE, wherein the network node performs any of the steps as described in any of the Group B embodiments to receive the user data from the UE for the host.

[0220] 39. The method as described in the foregoing embodiments further includes, at the network node, transmitting the received user data to the host.

[0221] abbreviations At least some of the following abbreviations may be used in this disclosure. In the event of inconsistencies between abbreviations, priority shall be given to the abbreviation used above. If an abbreviation is listed multiple times below, the first listing shall take precedence over any subsequent listing(s).

[0222] BWP bandwidth portion CBRA (Content-Based Random Access) CE Coverage Expansion CFRA (Contest-Free Random Access) CP cyclic prefix CSI Channel State Information DL downlink DMRS demodulation reference signal FDM (Frequency Division Multiplexing) FFT (Fast Fourier Transform) Base stations in gNB NR LTE Long Term Evolution MAC Media Access Control NB-IoT Narrowband IoT NUL Normal Uplink PDSCH (Physical Downlink Shared Channel) PBCH (Physical Broadcast Channel) PRACH (Physical Random Access Channel) PUSCH Physical Uplink Shared Channel BWP bandwidth portion CBRA (Content-Based Random Access) CE Coverage Expansion CFRA (Contest-Free Random Access) CP cyclic prefix CSI Channel State Information DL downlink DMRS demodulation reference signal FDM (Frequency Division Multiplexing) FFT (Fast Fourier Transform) LTE Long Term Evolution MAC Media Access Control NB-IoT Narrowband IoT NUL Normal Uplink PDSCH (Physical Downlink Shared Channel) PBCH (Physical Broadcast Channel) PRACH (Physical Random Access Channel) PUSCH Physical Uplink Shared Channel QCL Quasi-co-located RAR Random Access Response RSRP reference signal received power RO PRACH timing or PRACH transmission timing RAPID (Random Access Preamble) identifier RNTI (Radio Network Temporary Identifier) SI System Information SIB System Information Block SSB Synchronization Signal Beam SUL supplements uplink TA scheduled in advance TDM (Time Division Multiplexing) TPC Transmission Power Control UL uplink

Claims

1. A method for performing uplink UL transmission for a user equipment (UE), the method comprising: Determine the uplink UL duty cycle of the UL transmission, including unscheduled transmissions; In response to the UL duty cycle being greater than the capability information reported by the UE, a power backoff setting is applied to the transmission power used for the UL transmission in order to comply with electromagnetic power density exposure requirements, thereby determining the actual transmission power used to perform the UL transmission; as well as The UL transmission is transmitted using the actual transmission power.

2. The method of claim 1, wherein, The unscheduled transmissions include Physical Random Access Channel (PRACH) transmissions.

3. The method as described in claim 1 or 2, wherein, The capability information indicates the maximum percentage of symbols that can be scheduled for the UL transmission at maximum UE transmission power during a 1s period.

4. The method according to any one of claims 1-3, wherein, The power back-off settings include Power Management Maximum Power Reduction (P-MPR).

5. The method according to any one of claims 1-4, wherein, The actual transmission power used to perform the UL transmission is a reduced power from the transmission power used for the UL transmission.

6. The method according to any one of claims 1-5, wherein, The transmission power is either the maximum UE transmission power or the transmission power estimated by the UE.

7. The method according to any one of claims 1-6, wherein, The power back-off settings are adjusted based on one or more of the following factors: The purpose of PRACH transmission The number of PRACH transmissions. Operating frequency Types of Random Access Channel (RACH) procedures PRACH retransmission PRACH repeats, Coexistence with other technologies, and The type of process or operation associated with the PRACH transmission.

8. A method for scheduling network nodes for uplink UL transmission, the method comprising: Receive capability information reported by the user equipment (UE); The UL delivery is scheduled based on the reported capability information; as well as Receive the UL transmission from the UE using the actual transmission power used to perform the UL transmission; The actual transmission power is obtained by applying a power backoff setting to the transmission power used for the UL transmission in response to the UL transmission having a UL duty cycle greater than the capability information, including unscheduled transmissions.

9. The method of claim 8, wherein, The unscheduled transmissions include Physical Random Access Channel (PRACH) transmissions.

10. The method of claim 8 or 9, wherein, The capability information indicates the maximum percentage of symbols that can be scheduled for the UL transmission at maximum UE transmission power during a 1s period.

11. The method according to any one of claims 8-10, wherein, The power back-off settings include Power Management Maximum Power Reduction (P-MPR).

12. The method according to any one of claims 8-11, wherein, The actual transmission power used to perform the UL transmission is a reduced power from the transmission power used for the UL transmission.

13. The method according to any one of claims 8-12, wherein, The transmission power is one of the maximum UE transmission power or the transmission power estimated by the UE.

14. The method according to any one of claims 8-13, wherein, The power back-off settings are adjusted based on one or more of the following factors: The purpose of PRACH transmission The number of PRACH transmissions. Operating frequency Types of Random Access Channel (RACH) procedures PRACH retransmission PRACH repeats, Coexistence with other technologies, and The type of process or operation associated with the PRACH transmission.

15. A user equipment (UE) for performing uplink UL transmission, the UE comprising: Antenna configured to transmit and receive wireless signals; Processing circuitry configured to perform the following operations: Determine the uplink UL duty cycle of the UL transmission, including unscheduled transmissions; In response to the UL duty cycle being greater than the capability information reported by the UE, a power backoff setting is applied to the transmission power used for the UL transmission in order to comply with electromagnetic power density exposure requirements, thereby determining the actual transmission power used to perform the UL transmission; as well as The UL transmission is transmitted using the actual transmission power.

16. The UE as claimed in claim 15, wherein, The unscheduled transmissions include Physical Random Access Channel (PRACH) transmissions.

17. The UE as claimed in claim 15 or 16, wherein, The capability information indicates the maximum percentage of symbols that can be scheduled for the UL transmission at maximum UE transmission power during a 1s period.

18. The UE as claimed in any one of claims 15-17, wherein, The power back-off settings include Power Management Maximum Power Reduction (P-MPR).

19. The UE as claimed in any one of claims 15-18, wherein, The actual transmission power used to perform the UL transmission is a reduced power from the transmission power used for the UL transmission.

20. The UE as claimed in any one of claims 15-19, wherein, The transmission power is one of the maximum UE transmission power or the transmission power estimated by the UE.

21. The UE as claimed in any one of claims 15-20, wherein, The power back-off setting is adjusted based on one or more of the following factors: The purpose of PRACH transmission The number of PRACH transmissions. Operating frequency Types of Random Access Channel (RACH) procedures PRACH retransmission PRACH repeats, Coexistence with other technologies, and The type of process or operation associated with the PRACH transmission.

22. A network node for scheduling uplink UL transmissions, the network node comprising: Antenna configured to transmit and receive wireless signals; Processing circuitry configured to perform the following operations: Receive capability information reported by the user equipment (UE); Schedule the UL delivery based on the reported capability information; and Receive the UL transmission from the UE using the actual transmission power used to perform the UL transmission; The actual transmission power is obtained by applying a power backoff setting to the transmission power used for the UL transmission in response to the UL transmission having a UL duty cycle greater than the capacity information, including unscheduled transmissions.

23. The network node as described in claim 22, wherein, The unscheduled transmissions include Physical Random Access Channel (PRACH) transmissions.

24. The network node as described in claim 22 or 23, wherein, The capability information indicates the maximum percentage of symbols that can be scheduled for the UL transmission at maximum UE transmission power during a 1s period.

25. The network node as claimed in any one of claims 22-24, wherein, The power back-off settings include Power Management Maximum Power Reduction (P-MPR).

26. The network node as described in any one of claims 22-25, wherein, The actual transmission power used to perform the UL transmission is a reduced power from the transmission power used for the UL transmission.

27. The network node as claimed in any one of claims 22-26, wherein, The transmission power is one of the maximum UE transmission power or the transmission power estimated by the UE.

28. The network node as claimed in any one of claims 22-27, wherein, The power back-off setting is adjusted based on one or more of the following factors: The purpose of PRACH transmission The number of PRACH transmissions. Operating frequency Types of Random Access Channel (RACH) procedures PRACH retransmission PRACH repeats, Coexistence with other technologies, and The type of process or operation associated with the PRACH transmission.

Images