Limiting the accumulation of transmit power control in beam-specific power control

Abstract

A method for determining whether a wireless device is power limited and performed by a wireless device (110, 500, 791, 792) is disclosed. The method includes receiving (1301) a transmit power control (TPC) command for one or more of a plurality of power control loops configured at the wireless device from a network node (160, 712). The method includes obtaining (1302) an indication of one or more of the plurality of power control loops to which the received TPC command applies. The method includes determining (1303) whether one or more conditions related to power control at the wireless device are satisfied based on the obtained indication. The method includes determining (1304) whether the wireless device is power limited based on whether the one or more conditions are satisfied.

Description

Technical Field

[0001] The present disclosure relates generally to wireless communications and, more particularly, to limiting accumulation of transmit power control, such as in beam-specific power control. Background Art

[0002] 1.1 Power Control

[0003] Setting the output power level of transmitters (e.g., base stations in downlink (DL) and user equipment (UE) in uplink (UL)) in mobile systems is generally referred to as power control. The goals of power control include improving capacity, coverage, improving system robustness, and reducing power consumption.

[0004] In Long Term Evolution (LTE), power control mechanisms can be divided into the groups (i) open loop, (ii) closed loop and (iii) combined open and closed loop. These differ in the inputs used to determine the transmit power. In the open loop case, the transmitter measures a certain signal sent from the receiver and sets its output power based on this. In the closed loop case, the receiver measures the signal from the transmitter and based on this sends a transmit power control (TPC) command to the transmitter, which then sets its transmit power accordingly. In the combined open and closed loop schemes, both inputs are used to set the transmit power.

[0005] In systems with multiple channels between the UE and the base station (e.g., traffic and control channels), different power control principles can be applied to different channels. Using different principles creates more freedom in adapting the power control principle to the needs of the individual channels. The disadvantage is the increased complexity of maintaining several principles.

[0006] 1.2 Power Control Loop

[0007] For example, in LTE Release 10, the UE initially performs power control on the Physical Random Access Channel (PRACH) using the following formula:

[0008] P PRACH =min{P CMAX,c (i),PREAMBLE_RECEIVED_TARGET_POWER+PL c}.

[0009] After a connection is established between a UE and an eNodeB (eNB), the UE may be configured to also perform UL power control on Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), and Sounding Reference Signal (SRS) transmissions. The UE transmit power for PUCCH transmissions may be set by:

[0010]

[0011] Where P PUCCH is the transmit power used in a given subframe, and PL c is the path loss estimated by the UE. For PUSCH, the following equation is used instead:

[0012]

[0013] Where c represents the serving cell, and P PUSCH，c is the transmit power used in a given subframe. For SRS, it is defined as:

[0014] P SRS，c (i) = min{P CMAX，c (i), P SRS_OFFSET，c (m)+10log 10 (M SRS，c )+P O_PUSCH，c (j)+α c (j) PL c +f c (i)}.

[0015] Note that PL c is part of setting the power level for UE transmissions, which corresponds to the open loop part of power control. It is clear from this that path loss estimation by the UE plays an important role in power control. The path loss must in turn be estimated from the DL transmission and is usually done by measuring on a reference signal.

[0016] 1.3 Closed-loop power control

[0017] In the above power control formula, there are two defined terms f(i) and g(i) corresponding to the closed loop part of the power control. These terms are controlled by signaling from a network node (e.g., a gNodeB (gNB)) using TPC commands (via a Medium Access Control (MAC) Control Element (CE) or Downlink Control Information (DCI)). By using this, the gNB will be able to influence the UE output power, which can be used, for example, to: counteract estimation errors that affect UL power control; remove bias; and / or adapt the UE output power to the current interference level at the gNB. If the interference is high, the gNB can be incentivized to increase the UE output power.

[0018] There are multiple ways to configure the operation of f(i). It can operate in "accumulation mode" or "absolute mode". If accumulation is enabled, for example based on the parameter "Accumulation-enabled" provided by the higher layer, then f(i) is given by:

[0019] f c (i) = fc (i-1)+δ PUSCH，c (iK PUSCH ),

[0020] where δ PUSCH，c is a correction value, also called a TPC command, and may take values ​​according to the following table (for more details on this, see the 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 36213 v.10.13.0). In addition, for serving cell c, when P O_UE_PUSCH，c When the value is changed by higher layers; and for the primary cell, when the UE receives a random access response message, the UE shall reset the accumulation.

[0021] Table 5.1.1.1-2: TPC command fields to absolute and cumulative delta in DCI format 0 / 3 / 4 PUSCH，c A map of values.

[0022]

[0023] Table 5.1.1.1-3: TPC command field to accumulated delta in DCI format 3A PUSCH，c A map of values.

[0024]

[0025] g(i) functions similarly and is defined by:

[0026]

[0027] Where g(i) is the current PUCCH power control adjustment state, and g(0) is the first value after reset. O_UE_PUCCH When the value is changed by the higher layer; and when the UE receives a random access response message, the UE shall reset the accumulation. PUCCH Given in the table below.

[0028] Table 5.1.2.1-1: TPC command fields to delta in DCI format 1A / 1B / 1D / 1 / 2A / 2B / 2C / 2 / 3 PUCCH A map of values.

[0029]

[0030] Table 5.1.2.1-2: TPC command fields to delta in DCI format 3A PUCCH A map of values.

[0031]

[0032] 1.3.1 TPC commands in UL authorization

[0033] Closed-loop power control adjustments (commonly referred to as TPC commands) may be sent to a UE as part of an UL grant scheduling a PUSCH transmission (e.g., using DCI formats 0 / 4 in LTE) or a DL assignment scheduling a PDSCH (in which case the TPC command is applicable to setting the transmit power of the PUCCH corresponding to the PDSCH scheduled by the DL assignment) (e.g., using DCI (e.g., formats 1A, 1, 2, 2A, etc. in LTE)).

[0034] 1.3.2 TPC commands sent to a group of UEs

[0035] The TPC command can also be sent to a group of UEs using a physical downlink control channel (PDCCH) addressed to the group. This can be done by assigning different bit field positions in the DCI of the PDCCH message to different UEs. For example, positions 1, 2 for a 2-bit TPC command to UE1, positions 3, 4 for a 2-bit TPC command to UE2, and so on. For N UEs, the DCI will have at least 2N bits. A cyclic redundancy check (CRC) scrambled by a radio network temporary identifier (RNTI) is also added to the DCI. Different groups of UEs can be assigned different RNTIs. For example, in LTE, the command is sent using DCI format 3 / 3A to adjust PUSCH power, and different groups of UEs are assigned different TPC-PUSCH-RNTIs. Similarly, for PUCCH power control, different groups of UEs are assigned different TPC-PUCCH-RNTIs. Similarly, SRS group-based TPC commands are sent using DCI format 3B in LTE.

[0036] 1.3.2.1 DCI format 3 in LTE

[0037] DCI format 3 in LTE is used for the transmission of TPC commands for PUCCH and PUSCH with 2-bit power adjustment. The following information is transmitted with the help of DCI format 3: TPC command number 1, TPC command number 2, ..., TPC command number N, where when format 0 is mapped to the common search space, And L 格式0 Equal to the payload size of format 0 before the CRC is appended, including any padding bits appended to format 0. The parameter tpc-Index or tpc-Index-PUCCH-SCell-r13 provided by higher layers determines the index of the TPC command for a given UE. If Then zero value bits should be appended to format 3.

[0038] 1.3.2.2 DCI format 3A in LTE

[0039] DCI format 3A in LTE is used for the transmission of TPC commands for PUCCH and PUSCH with single-bit power adjustment. The following information is sent with the help of DCI format 3A: TPC command number 1, TPC command number 2, ..., TPC command number M, where M = L when format 0 is mapped to the common search space 格式0 And L 格式0 Equal to the payload size of format 0 before the CRC is appended, including any padding bits appended to format 0. The parameter tpc-Index or tpc-Index-PUCCH-SCell-r13 provided by higher layers determines the index of the TPC command for a given UE.

[0040] 1.4 Beam-specific power control

[0041] It is agreed that New Radio (NR) supports beam-specific power control. Beam-specific power control can be, for example, a scheme that enables use cases where individual power control is maintained in multiple UE transmit (TX) and gNB receive (RX) beam pairs. Use cases include, for example: UE transmission to a transmit receive point (TRP) using a certain beam switches to another beam and then also switches from one power control loop to another power control loop; and UE transmission to a TRP switches to another TRP and then also switches from one power control loop to another power control loop.

[0042] It can be expected that power control of a specific beam will imply a set of power control loops as shown below for the case of PUSCH. Thus, there will be a set of power control loops, each of which is connected to a beam.

[0043] Table 1: Power Control (PC) loop Radio Resource Control (RRC) configured for UE

[0044]

[0045] In this case, the UL power control loop can be written as:

[0046]

[0047] Here, α k , The meaning of etc. is that these parameters may be configured in a beam-specific manner and may therefore depend on the beam index k. However, they may also be shared by the beam, such that for example α0=α1=…=α6=α, meaning that only α needs to be configured. The index k_PUCCH in the PUCCH refers to the beam used for PUCCH transmission. In addition, if PUCCH transmission is not performed, the k_PUCCH index can also be omitted.

[0048] also, It implies that the path loss estimation is based on a certain reference signal defined for power control loop k. Therefore, each time a reference signal corresponding to power control loop k is transmitted, the UE can use the reference signal in order to estimate This is usually done by performing a long term average, for example:

[0049]

[0050] where referenceSignalPower is defined by the network.

[0051] Finally, note that for beams not currently used for PUSCH, so M = 0, the equation can be defined instead as:

[0052]

[0053] 1.4.1 Beam-specific power control in NR

[0054] The exact details of how beam-specific power control should be described in NR are still under discussion, but the current recommendations are:

[0055]

[0056] Thus, as mentioned above, an index k can correspond to some set of indices {j, q, l} in NR. One way to think of this is that there will be a set of functions j(q), k(q), and l(q) that define {j, k, l} for a given q. Although similar to using the notation This is a general description of beam-specific power control, but the description here uses the notation P PUSCH，c (i, j, q, l). Still, it will be straightforward for one skilled in the art to convert equations between these two formats.

[0057] In addition, the description here uses the notation:

[0058]

[0059] The right side of the previous equation makes:

[0060]

[0061] Therefore, if the function is not affected by P CMAX，c (i) Restrictions, then Corresponding to P PUSCH，c The output power of (i, j, q, l).

[0062] There are certain challenges currently. For example, in LTE, the UE typically maintains one closed-loop power control adjustment state per serving cell for each physical channel (e.g., PUSCH / PUCCH) or signal (e.g., SRS) (i.e., f() for PUSCH and g() for PUCCH). In some cases, the UE may maintain different closed-loop power control adjustment states for different groups of subframes (e.g., f1() for a first group of subframes configured by radio resource control (RRC); f2() for a second group of subframes configured by RRC). In addition, if a set of TPC commands is received and the closed-loop power control is operated in accumulation mode, the specification specifies that if the UE has reached the maximum / minimum power, the positive / negative TPC commands should not be further accumulated.

[0063] In NR, a UE may be configured to have N=2 closed loops for PUSCH for a given serving cell, and multiple power control loops may use a given closed loop. Given this, when a UE receives a TPC command (e.g., using the group-based approach described above in Section 1.3.2), it is not trivial to decide whether the UE has reached maximum / minimum power; this makes it possible that some power control loops correspond to maximum / minimum power and some do not. Summary of the invention

[0064] To address the aforementioned problems of existing solutions, a method for determining whether the wireless device is power limited, performed by a wireless device, is disclosed. The method includes receiving a TPC command for one or more of a plurality of power control loops configured at the wireless device from a network node. The method includes obtaining an indication of one or more of the plurality of power control loops to which the received TPC command applies. The method includes determining, based on the obtained indication, whether one or more conditions related to power control at the wireless device are satisfied. The method includes determining whether the wireless device is power limited based on whether the one or more conditions are satisfied.

[0065] In certain embodiments, the indication may include at least one parameter associated with one or more of a plurality of power control loops configured at the wireless device.

[0066] In some embodiments, the method may further include, in response to determining that the wireless device is not power limited, accumulating the received TPC commands.

[0067] In some embodiments, the method may further include: in response to determining that the wireless device is power limited, determining whether to accumulate the received TPC command. In some embodiments, determining whether the wireless device is power limited may result in determining that the wireless device is maximum power limited, and determining whether to accumulate the received TPC command may include: determining whether the received TPC command is positive or negative; and performing one of the following operations: in response to determining that the received TPC command is positive, avoiding accumulating the received TPC command; and in response to determining that the received TPC command is negative, accumulating the received TPC command. In some embodiments, determining whether the wireless device is power limited may result in determining that the wireless device is minimum power limited, and determining whether to accumulate the received TPC command may include: determining whether the received TPC command is positive or negative; and performing one of the following operations: in response to determining that the received TPC command is negative, avoiding accumulating the received TPC command; and in response to determining that the received TPC command is positive, accumulating the received TPC command.

[0068] In some embodiments, the wireless device may be configured with two power control loops, each configured power control loop being associated with a different closed loop. Obtaining the indication may include receiving a power control loop index indicating that the received TPC command is applicable to a first power control loop of the two configured power control loops. Determining whether the one or more conditions are satisfied may be based on one or more parameters related to the first power control loop. In some embodiments, the power control loop index may be received implicitly. In some embodiments, the power control loop index may be received explicitly.

[0069] In some embodiments, the received TPC command may be received via a UL grant. In some embodiments, the power control loop index may be received via a UL grant.

[0070] In some embodiments, the wireless device may be configured with at least three power control loops, each power control loop being associated with one of the two closed loops, such that at least two of the configured three power control loops are associated with a first closed loop of the two closed loops. Obtaining the indication may include receiving a closed loop index indicating that the received TPC command is applicable to all configured power control loops associated with the first closed loop of the two closed loops. Determining whether the one or more conditions are satisfied may be based on one or more parameters related to at least one of the configured power control loops associated with the first closed loop.

[0071] In some embodiments, the received TPC command can be received as part of one or more TPC commands sent to a group of wireless devices. In some embodiments, the received TPC command can be received in a PDCCH DCI without an associated UL grant.

[0072] In some embodiments, one or more conditions may be a function of a closed loop index. In some embodiments, one or more conditions may include a function that depends on more than one power control loop. In some embodiments, one or more conditions may include the condition that all power control loops associated with the received closed loop index must be considered power limited in order to determine that the wireless device is power limited. In some embodiments, one or more conditions may include the condition that at least one power control loop associated with the received closed loop index must be considered power limited in order to determine that the wireless device is power limited. In some embodiments, one or more conditions may include the condition that all power control loops must be considered power limited in order to determine that the wireless device is power limited. In some embodiments, one or more conditions may include the condition that at least one power control loop must be considered power limited in order to determine that the wireless device is power limited.

[0073] In some embodiments, the method may further include determining whether a power control loop in the plurality of power control loops is classified as power limited. In some embodiments, determining whether a power control loop in the plurality of power control loops is classified as power limited may be based on a non-virtual output power. In some embodiments, determining whether a power control loop in the plurality of power control loops is classified as power limited may be based on a virtual output power. In some embodiments, determining whether a power control loop in the plurality of power control loops is classified as power limited may be based on a PUCCH transmit power. In some embodiments, determining whether a power control loop in the plurality of power control loops is classified as power limited may not be based on a PUCCH transmit power.

[0074] In certain embodiments, the multiple power control loops may include one or more of: one or more PUCCH power control loops; one or more SRS power control loops; and one or more PUSCH power control loops.

[0075] In certain embodiments, power limiting may include one or more of: maximum power limiting; and minimum power limiting.

[0076] A wireless device is also disclosed. The wireless device includes a receiver, a transmitter, and a processing circuit coupled to the receiver and the transmitter. The processing circuit is configured to receive a TPC command for one or more of a plurality of power control loops configured at the wireless device from a network node. The processing circuit is configured to obtain an indication of one or more of the plurality of power control loops to which the received TPC command applies. The processing circuit is configured to determine, based on the obtained indication, whether one or more conditions related to power control at the wireless device are satisfied. The processing circuit is configured to determine whether the wireless device is power limited based on whether the one or more conditions are satisfied.

[0077] In certain embodiments, the indication may include at least one parameter associated with one or more of a plurality of power control loops configured at the wireless device.

[0078] In some embodiments, the processing circuit may be further configured to accumulate the received TPC commands in response to determining that the wireless device is not power limited. In some embodiments, the processing circuit may be further configured to determine whether to accumulate the received TPC commands in response to determining that the wireless device is power limited.

[0079] In some embodiments, the processing circuit may be further configured to determine that the maximum power of the wireless device is limited, and the processing circuit configured to determine whether to accumulate the received TPC command may be further configured to: determine whether the received TPC command is positive or negative; and perform one of the following operations: in response to determining that the received TPC command is positive, avoid accumulating the received TPC command; and in response to determining that the received TPC command is negative, accumulate the received TPC command.

[0080] In some embodiments, the processing circuit may be further configured to determine that the wireless device is minimum power limited, and the processing circuit configured to determine whether to accumulate the received TPC command may be further configured to: determine whether the received TPC command is positive or negative; and perform one of the following operations: in response to determining that the received TPC command is negative, avoid accumulating the received TPC command; and in response to determining that the received TPC command is positive, accumulate the received TPC command.

[0081] In some embodiments, the wireless device may be configured with two power control loops, each configured power control loop being associated with a different closed loop. The processing circuit configured to obtain an indication may be further configured to receive a power control loop index indicating that the received TPC command is applicable to a first power control loop of the two configured power control loops. The processing circuit may be further configured to determine whether one or more conditions are satisfied based on one or more parameters related to the first power control loop.

[0082] In some embodiments, the processing circuitry may be configured to receive a TPC command via a UL grant. In some embodiments, the processing circuitry may be configured to receive a power control loop index via an uplink. In some embodiments, the processing circuitry may be configured to receive a power control loop index implicitly. In some embodiments, the processing circuitry may be configured to receive a power control loop index explicitly.

[0083] In some embodiments, the wireless device may be configured with at least three power control loops, each power control loop being associated with one of the two closed loops, such that at least two of the configured three power control loops are associated with a first closed loop of the two closed loops. The processing circuit configured to obtain the indication may be further configured to receive a closed loop index indicating that the received TPC command is applicable to all configured power control loops associated with the first closed loop of the two closed loops. The processing circuit may be further configured to determine whether one or more conditions are satisfied based on one or more parameters related to at least one of the configured power control loops associated with the first closed loop.

[0084] In certain embodiments, the processing circuitry may be configured to receive the TPC command as part of one or more TPC commands sent to a group of wireless devices. In certain embodiments, the processing circuitry may be configured to receive the TPC command in a PDCCH DCI without an associated UL grant.

[0085] In some embodiments, one or more conditions may be a function of a closed loop index. In some embodiments, one or more conditions may include a function that depends on more than one power control loop. In some embodiments, one or more conditions may include the condition that all power control loops associated with the received closed loop index must be considered power limited in order to determine that the wireless device is power limited. In some embodiments, one or more conditions may include the condition that at least one power control loop associated with the received closed loop index must be considered power limited in order to determine that the wireless device is power limited. In some embodiments, one or more conditions may include the condition that all power control loops must be considered power limited in order to determine that the wireless device is power limited. In some embodiments, one or more conditions may include the condition that at least one power control loop must be considered power limited in order to determine that the wireless device is power limited.

[0086] In some embodiments, the processing circuit may be further configured to determine whether a power control loop in the plurality of power control loops is classified as power limited. In some embodiments, the processing circuit may be further configured to determine whether a power control loop in the plurality of power control loops is classified as power limited based on a non-virtual output power. In some embodiments, the processing circuit may be further configured to determine whether a power control loop in the plurality of power control loops is classified as power limited based on a virtual output power. In some embodiments, the processing circuit may be further configured to determine whether a power control loop in the plurality of power control loops is classified as power limited based on a PUCCH transmit power. In some embodiments, the processing circuit may be further configured to determine whether a power control loop in the plurality of power control loops is classified as power limited not based on a PUCCH transmit power.

[0087] In some embodiments, the multiple power control loops include one or more of the following: one or more PUCCH power control loops; one or more SRS power control loops; and one or more PUSCH power control loops. In some embodiments, the power limitation may include one or more of the following: maximum power limitation; and minimum power limitation.

[0088] A computer program is also disclosed, the computer program comprising instructions configured to execute the above method in a wireless device.

[0089] A computer program product is also disclosed, the computer program product comprising a non-transitory computer-readable storage medium, the non-transitory computer-readable storage medium comprising a computer program, the computer program comprising computer-executable instructions, which when executed on a processor are configured to perform the above method in a wireless device.

[0090] Certain embodiments of the present disclosure may provide one or more technical advantages. As an example, certain embodiments may advantageously enable a wireless device configured with multiple closed loops to explicitly identify whether it is maximum / minimum power limited. Other advantages may be apparent to those skilled in the art. Certain embodiments may have no advantages, or have some or all of the advantages. BRIEF DESCRIPTION OF THE DRAWINGS

[0091] For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, in which:

[0092] Figure 1 illustrates an example wireless communication network in accordance with certain embodiments;

[0093] Figure 2 An example method in a UE according to some embodiments is shown;

[0094] Figure 3 Another example method in a UE according to certain embodiments is shown;

[0095] Figure 4 Another example method in a UE according to certain embodiments is shown;

[0096] Figure 5 An embodiment of a UE according to certain embodiments is shown;

[0097] Figure 6 is a schematic block diagram illustrating a virtualized environment according to some embodiments;

[0098] Figure 7 illustrates an example telecommunications network connected to a host computer via an intermediate network in accordance with certain embodiments;

[0099] Figure 8 illustrates an example of a host computer communicating with a UE via a base station over a partially wireless connection in accordance with certain embodiments;

[0100] Fig. 9 is a flow chart of a method implemented in a communication system according to certain embodiments;

[0101] Fig.10 is a flow chart of a method implemented in a communication system according to certain embodiments;

[0102] Fig.11 is a flow chart of a method implemented in a communication system according to certain embodiments;

[0103] Fig.12 is a flow chart of a method implemented in a communication system according to certain embodiments;

[0104] Fig.13 is a flow chart of a method in a wireless device according to some embodiments; and

[0105] Fig.14 is a schematic block diagram of a virtualization device according to some embodiments. DETAILED DESCRIPTION

[0106] Generally, unless clearly given and / or implied different meanings in the context of using terms, all terms used herein will be interpreted according to their common meanings in the relevant technical field. Unless otherwise clearly stated, all references to one / an / the element, device, assembly, part, step, etc. will be publicly interpreted as referring to at least one instance of the element, device, assembly, part, step, etc. Unless a step is clearly described as after or before another step, and / or a step must be after or before another step, the steps of any method disclosed herein do not have to be performed in the exact order disclosed. Where appropriate, any feature of any embodiment disclosed herein may be applied to any other embodiment. Likewise, any advantage of any embodiment may be applied to any other embodiment, and vice versa. By the following description, other purposes, features and advantages of the attached embodiments will be apparent.

[0107] Note that although terminology from 3GPP LTE has been used in this disclosure, this should not be seen as limiting the scope of the invention to only the above-mentioned systems. Other wireless systems, especially 5G / NR, WCDMA, WiMax, UMB and GSM, can also benefit from utilizing the concepts covered in this disclosure.

[0108] As described above, there are currently certain challenges regarding power control in NR systems. When a set of TPC commands is received by the UE and the closed-loop power control operates in accumulation mode, if the UE has reached the maximum (or minimum) power, the positive (or negative) TPC commands will no longer be accumulated. However, in NR, for a given serving cell, the UE can be configured to have N=2 closed loops for PUSCH. Multiple power control loops can use a given closed loop. In view of this, when a TPC command is received by the UE (for example, using the group-based method described above in Section 1.3.2), it is not easy to determine whether the UE has reached the maximum (or minimum) power. In fact, it is possible that some power control loops correspond to the maximum (or minimum) power, while others do not.

[0109] Certain aspects of the present disclosure and embodiments thereof may provide solutions to these or other challenges. In certain embodiments, whether a UE is maximum (or minimum) power limited may be determined by having a function obtain all defined power control loops or a subset of possibly all defined power control loops, and then defining whether the UE should be considered maximum (or minimum) power limited based on the state of these defined power control loops. For UEs configured with multiple closed loops, certain embodiments may advantageously enable the UE to explicitly identify whether it is maximum (or minimum) power limited.

[0110] Various embodiments are presented herein that address one or more of the issues disclosed herein. According to an example embodiment, a method performed by a wireless device (e.g., UE) for determining whether the wireless device is power limited is disclosed. The wireless device receives a TPC command for one or more of a plurality of power control loops configured at the wireless device from a network node. The wireless device obtains an indication of one or more of the plurality of power control loops to which the received TPC command applies. The wireless device determines whether one or more conditions related to power control at the wireless device are satisfied based on the obtained indication. The wireless device determines whether the wireless device is power limited based on whether the one or more conditions are satisfied.

[0111] In some embodiments, the indication may be (or include) at least one parameter associated with one or more of a plurality of power control loops configured at the wireless device. In some embodiments, in response to determining that the wireless device is not power limited, the wireless device may accumulate the received TPC commands. In some embodiments, in response to determining that the wireless device is power limited, the wireless device may determine whether to accumulate the received TPC commands.

[0112] In some embodiments, the wireless device may determine that the wireless device is maximum power limited. The wireless device may determine whether to accumulate the received TPC command by determining whether the received TPC command is positive or negative, and perform one of the following operations: in response to determining that the received TPC command is positive, avoid accumulating the received TPC command; and in response to determining that the received TPC command is negative, accumulate the received TPC command. In some embodiments, the wireless device may determine that the wireless device is minimum power limited. The wireless device may determine whether to accumulate the received TPC command by determining whether the received TPC command is positive or negative, and perform one of the following operations: in response to determining that the received TPC command is negative, avoid accumulating the received TPC command; and in response to determining that the received TPC command is positive, accumulate the received TPC command.

[0113] In some embodiments, there is at least one of the following conditions: a Boolean condition describing when the wireless device should accumulate TPC commands at an upper limit; and a Boolean condition describing when the wireless device should accumulate TPC commands at a lower limit. The condition may be a function of a closed loop index (e.g., 1). The condition may be a function that depends on more than one power control loop. The condition may indicate that all power control loops corresponding to the closed loop index should be considered power limited in order to satisfy the condition. The condition may indicate that at least one power control loop corresponding to the closed loop index should be considered power limited in order to satisfy the condition. The condition may indicate that all power control loops should be considered power limited in order to satisfy the condition. The power control loop may be classified as power limited or power not limited based on non-virtual or virtual output power. The PUSCH power control loop may be classified as power limited or not with or without regard to the PUCCH transmit power. The condition may involve both SRS and PUSCH power control loops.

[0114] Certain embodiments may provide one or more of the following technical advantages. For a UE configured with multiple closed loops, the proposed method may help the UE to clearly identify whether it is maximum / minimum power limited. Other advantages may be apparent to those skilled in the art. Certain embodiments may not have any advantages, or may have some or all of the advantages described.

[0115] Some embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited to the embodiments set forth herein; instead, these embodiments are provided merely as examples to convey the scope of the subject matter to those skilled in the art.

[0116] Figure 1 An example wireless communication network according to some embodiments is shown. Although the subject matter described herein may be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are generally described with respect to wireless networks such as Figure 1 For simplicity, Figure 1 The wireless network of FIG. 1 depicts only the network 106, the network nodes 160 and 160b, and the wireless devices (WD) 110, 110b, and 110c. In practice, the wireless network may further include any additional elements suitable for supporting communication between wireless devices or between a wireless device and another communication device (such as a fixed telephone, a service provider, or any other network node or terminal device). In the illustrated components, the network node 160 and the WD 110 are shown in more detail. The wireless network may provide communication and other types of services to one or more wireless devices, so that the wireless device can access the wireless network and / or use services provided by or via the wireless network.

[0117] A wireless network may include and / or interface with any type of communication, telecommunication, data, cellular and / or radio network or other similar type of system. In some embodiments, a wireless network may be configured to operate according to a specific standard or other type of predefined rules or procedures. Thus, specific embodiments of a wireless network may implement: communication standards such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards such as IEEE 802.11 standards; and / or any other suitable wireless communication standards such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, and / or ZigBee standards.

[0118] The network 106 may include one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks that enable communications between devices.

[0119] The network node 160 and the WD 110 include various components described in more detail below. These components work together to provide network node and / or wireless device functions, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may include any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components or systems that may facilitate or participate in data and / or signal communications via wired or wireless connections.

[0120] As used herein, a network node refers to a device that is capable, configured, arranged and / or operable to communicate directly or indirectly with a wireless device and / or with other network nodes or devices in a wireless network to enable and / or provide wireless access to the wireless device and / or perform other functions (e.g., management) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)). Base stations can be classified based on the amount of coverage they provide (or in other words, their transmit power levels), and can also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station can be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes also referred to as a remote radio head (RRH). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. Components of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Further examples of network nodes include multi-standard radio (MSR) equipment (such as an MSR BS), a network controller (such as a radio network controller (RNC) or a base station controller (BSC)), a base transceiver station (BTS), a transmission point, a transmission node, a multi-cell / multicast coordination entity (MCE), a core network node (e.g., MSC, MME), an O&M node, an OSS node, a SON node, a positioning node (e.g., E-SMLC), and / or an MDT. As another example, a network node may be a virtual network node as described in more detail below. However, more generally, a network node may represent any suitable device (or group of devices) that is capable, configured, arranged, and / or operable to enable and / or provide access to a wireless network to a wireless device, or to provide a certain service to a wireless device that has accessed a wireless network.

[0121] exist Figure 1 In the embodiment, the network node 160 includes a processing circuit 170, a device readable medium 180, an interface 190, an auxiliary device 184, a power supply 186, a power supply circuit 187, and an antenna 162. Figure 1The network node 160 shown in the example wireless network of can represent a device including the combination of hardware components shown, but other embodiments can include network nodes with different combinations of components. It should be understood that the network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. In addition, although the components of the network node 160 are depicted as a single box located within a larger box or nested within multiple boxes, in reality the network node can include multiple different physical components that make up the single shown component (for example, the device readable medium 180 can include multiple separate hard drives and multiple RAM modules).

[0122] Similarly, the network node 160 may be composed of multiple physically separated components (e.g., NodeB components and RNC components, or BTS components and BSC components, etc.), and the components may each have their own corresponding components. In certain scenarios where the network node 160 includes multiple separated components (e.g., BTS and BSC components), one or more separated components may be shared between multiple network nodes. For example, a single RNC may control components of multiple NodeBs. In such scenarios, in some instances, each unique NodeB and RNC pair may be considered as a single separated network node. In some embodiments, the network node 160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be replicated (e.g., separate device-readable media 180 for different RATs), and some components may be reused (e.g., the same antenna 162 may be shared by RATs). The network node 160 may also include multiple groups of various components shown for different wireless technologies (such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies) integrated into the network node 160. These wireless technologies may be integrated into the same or different chips or chipsets and other components within the network node 160 .

[0123] The processing circuit 170 may be configured to perform any determination, calculation, or similar operation (e.g., certain obtaining operations) described herein as being provided by the network node. Such operations performed by the processing circuit 170 may include, for example, processing information obtained by the processing circuit 170 by converting the obtained information into other information, comparing the obtained information or the converted information with information stored in the network node, and / or performing one or more operations based on the obtained information or the converted information, and making determinations as a result of the processing.

[0124] The processing circuitry 170 may include one or more of a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or a combination of encoded logic operable to provide, alone or in conjunction with other components of the network node 160 (such as the device readable medium 180), the functionality of the network node 160. For example, the processing circuitry 170 may execute instructions stored in the device readable medium 180 or in a memory within the processing circuitry 170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, the processing circuitry 170 may include a system on a chip (SOC).

[0125] In some embodiments, processing circuitry 170 may include one or more of radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174. In some embodiments, radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174 may be on separate chips (or chipsets), boards, or units (such as a radio unit and a digital unit). In alternative embodiments, some or all of RF transceiver circuitry 172 and baseband processing circuitry 174 may be on the same chip or chipset, board, or unit.

[0126] In some embodiments, some or all of the functions described herein as being provided by a network node, base station, eNB, or other such network device may be performed by processing circuit 170 executing instructions stored on device-readable medium 180 or memory within processing circuit 170. In alternative embodiments, some or all of the functions may be provided by processing circuit 170 without the need to execute instructions stored on a separate or discrete device-readable medium, such as in a hard-wired manner. In any of those embodiments, processing circuit 170 may be configured to perform the described functions regardless of whether instructions stored on a device-readable storage medium are executed. The benefits provided by such functions are not limited to individual processing circuits 170 or other components of network node 160, but are shared by network node 160 as a whole and / or generally by end users and wireless networks.

[0127] Device readable medium 180 may include any form of volatile or non-volatile computer readable memory, including but not limited to persistent memory, 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 drive, compact disk (CD) or digital video disk (DVD)), and / or any other volatile or non-volatile non-transitory device readable and / or computer executable memory device that stores information, data and / or instructions that can be used by processing circuit 170. Device readable medium 180 may store any suitable instructions, data or information including computer programs, software, applications including one or more of logic, rules, codes, tables, etc., and / or other instructions that can be executed by processing circuit 170 and utilized by network node 160. Device readable medium 180 may be used to store any calculations performed by processing circuit 170 and / or any data received via interface 190. In some embodiments, processing circuit 170 and device readable medium 180 may be considered integrated.

[0128] Interface 190 is used in wired or wireless communication of signaling and / or data between network node 160, network 106 and / or WD 110. As shown, interface 190 includes (multiple) ports / terminals 194 for sending data to network 106 and receiving data from network 106, for example, via a wired connection. Interface 190 also includes radio front-end circuit 192, which can be coupled to antenna 162, or is a part of antenna 162 in some embodiments. Radio front-end circuit 192 includes filter 198 and amplifier 196. Radio front-end circuit 192 can be connected to antenna 162 and processing circuit 170. Radio front-end circuit can be configured to adjust the signal communicated between antenna 162 and processing circuit 170. Radio front-end circuit 192 can receive digital data to be sent to other network nodes or WD via wireless connection. Radio front-end circuit 192 can use a combination of filter 198 and / or amplifier 196 to convert digital data into a radio signal with appropriate channel and bandwidth parameters. Then the radio signal can be sent via antenna 162. Similarly, when receiving data, antenna 162 may collect radio signals, which may then be converted into digital data by radio front end circuitry 192. The digital data may be passed to processing circuitry 170. In other embodiments, the interface may include different components and / or different combinations of components.

[0129] In some alternative embodiments, the network node 160 may not include a separate radio front end circuit 192, and instead the processing circuit 170 may include the radio front end circuit and may be connected to the antenna 162 without the separate radio front end circuit 192. Similarly, in some embodiments, all or some of the RF transceiver circuit 172 may be considered part of the interface 190. In still other embodiments, the interface 190 may include one or more ports or terminals 194, the radio front end circuit 192, and the RF transceiver circuit 172 as part of a radio unit (not shown), and the interface 190 may communicate with the baseband processing circuit 174 as part of a digital unit (not shown).

[0130] Antenna 162 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 162 may be coupled to radio front-end circuit 190 and may be any type of antenna capable of wirelessly sending and receiving data and / or signals. In some embodiments, antenna 162 may include one or more omnidirectional, sector or flat panel antennas operable to send / receive radio signals between, for example, 2 GHz and 66 GHz. Omnidirectional antennas may be used to send / receive radio signals in any direction, sector antennas may be used to send / receive radio signals from devices within a specific area, and flat panel antennas may be line of sight antennas for sending / receiving radio signals in a relatively straight line. In some instances, using more than one antenna may be referred to as MIMO. In some embodiments, antenna 162 may be separated from network node 160 and may be connected to network node 160 via an interface or port.

[0131] Antenna 162, interface 190 and / or processing circuit 170 can be configured to perform any receiving operation and / or certain obtaining operation described herein as being performed by a network node. Any information, data and / or signal can be received from a wireless device, another network node and / or any other network device. Similarly, antenna 162, interface 190 and / or processing circuit 170 can be configured to perform any sending operation described herein as being performed by a network node. Any information, data and / or signal can be sent to a wireless device, another network node and / or any other network device.

[0132] The power circuit 187 may include or be coupled to a power management circuit and is configured to provide power to the components of the network node 160 for performing the functions described herein. The power circuit 187 may receive power from the power supply 186. The power supply 186 and / or the power circuit 187 may be configured to provide power to the various components of the network node 160 in a form suitable for the respective components (e.g., at the voltage and current levels required for each respective component). The power supply 186 may be included in the power circuit 187 and / or the network node 160 or external thereto. For example, the network node 160 may be connected to an external power source (e.g., a power socket) via an input circuit or an interface such as a cable, whereby the external power source supplies power to the power circuit 187. As another example, the power supply 186 may include a power source in the form of a battery or a battery pack, which is connected to or integrated in the power circuit 187. If the external power source fails, the battery may provide backup power. Other types of power sources such as photovoltaic devices may also be used.

[0133] Alternative embodiments of network node 160 may include, in addition to Figure 1 Additional components beyond those shown in the drawings may be responsible for providing certain aspects of the functionality of the network node including any functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 160 may include a user interface device that allows information to be input into the network node 160 and allows information to be output from the network node 160. This may allow a user to perform diagnostics, maintenance, repair, and other management functions of the network node 160.

[0134] As used herein, a wireless device (WD) refers to a device that can, configure, arrange and / or operate to wirelessly communicate with a network node and / or other wireless devices. Unless otherwise specified, the term WD can be used interchangeably with a user equipment (UE) herein. Wireless communication may involve the use of electromagnetic waves, radio waves, infrared waves and / or other types of signals suitable for transmitting information through the air to send and / or receive wireless signals. In some embodiments, a WD may be configured to send and / or receive information without direct human interaction. For example, a WD may be designed to send information to a network according to a predetermined schedule when triggered by an internal or external event or in response to a request from a network. Examples of WD include, but are not limited to, smart phones, 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, tablet computers, laptop computers, laptop embedded devices (LEEs), laptop computer installation devices (LMEs), smart devices, wireless client devices (CPEs), vehicle-mounted wireless terminal devices, etc. WD can support device-to-device (D2D) communication, for example, by implementing 3GPP standards for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-everything (V2X), and in this case can be referred to as a D2D communication device. As another specific example, in an Internet of Things (IoT) scenario, WD can represent a machine or other device that performs monitoring and / or measurement and sends the results of such monitoring and / or measurement to another WD and / or network node. In this case, WD can be a machine-to-machine (M2M) device that can be referred to as an MTC device in the 3GPP context. As a specific example, WD can be a UE that implements the 3GPP narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or household or personal appliances (e.g., refrigerators, televisions, etc.), personal wearable devices (e.g., watches, fitness trackers, etc.). In other scenarios, WD can represent a vehicle or other device that can monitor and / or report its operating status or other functions associated with its operation. As described above, WD may represent an end point of a wireless connection, in which case the device may be referred to as a wireless terminal. In addition, as described above, WD may be mobile, in which case WD may also be referred to as a mobile device or a mobile terminal.

[0135] As shown, wireless device 110 includes antenna 111, interface 114, processing circuit 120, device readable medium 130, user interface device 132, auxiliary device 134, power supply 136 and power supply circuit 137. WD 110 may include multiple groups of one or more of the components shown for different wireless technologies supported by WD 110 (such as GSM, WCDMA, LTE, NR, WiFi, WiMAX or Bluetooth wireless technologies, to name a few). These wireless technologies may be integrated into the same or different chips or chipsets as other components within WD 110.

[0136] Antenna 111 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals, and is connected to interface 114. In some alternative embodiments, antenna 111 may be separated from WD 110 and may be connected to WD 110 via an interface or port. Antenna 111, interface 114 and / or processing circuit 120 may be configured to perform any receiving or transmitting operation described herein as being performed by WD. Any information, data and / or signal may be received from a network node and / or another WD. In some embodiments, radio front-end circuitry and / or antenna 111 may be considered as an interface.

[0137] As shown, the interface 114 includes a radio front-end circuit 112 and an antenna 111. The radio front-end circuit 112 includes one or more filters 118 and an amplifier 116. The radio front-end circuit 114 is connected to the antenna 111 and the processing circuit 120, and is configured to adjust the signal transmitted between the antenna 111 and the processing circuit 120. The radio front-end circuit 112 may be coupled to the antenna 111 or may be part of the antenna 111. In some embodiments, the WD 110 may not include a separate radio front-end circuit 112; instead, the processing circuit 120 may include a radio front-end circuit and may be connected to the antenna 111. Similarly, in some embodiments, some or all of the RF transceiver circuit 122 may be considered as part of the interface 114. The radio front-end circuit 112 may receive digital data to be sent to other network nodes or WDs via a wireless connection. The radio front-end circuit 112 may use a combination of filters 118 and / or amplifiers 116 to convert the digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal may then be sent via the antenna 111. Similarly, when receiving data, antenna 111 may collect radio signals, which may then be converted into digital data by radio front end circuit 112. The digital data may be passed to processing circuit 120. In other embodiments, the interface may include different components and / or different combinations of components.

[0138] The processing circuit 120 may include one or more of a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or a combination of encoded logic operable to provide WD 110 functionality alone or in conjunction with other WD 110 components (such as device readable medium 130). Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, the processing circuit 120 may execute instructions stored in the device readable medium 130 or in a memory within the processing circuit 120 to provide the functionality disclosed herein.

[0139] As shown, the processing circuit 120 includes one or more of the RF transceiver circuit 122, the baseband processing circuit 124, and the application processing circuit 126. In other embodiments, the processing circuit may include different components and / or different combinations of components. In some embodiments, the processing circuit 120 of the WD 110 may include a SOC. In some embodiments, the RF transceiver circuit 122, the baseband processing circuit 124, and the application processing circuit 126 may be on a separate chip or chipset. In an alternative embodiment, part or all of the baseband processing circuit 124 and the application processing circuit 126 may be combined into one chip or chipset, and the RF transceiver circuit 122 may be on a separate chip or chipset. In another alternative embodiment, part or all of the RF transceiver circuit 122 and the baseband processing circuit 124 may be on the same chip or chipset, and the application processing circuit 126 may be on a separate chip or chipset. In other alternative embodiments, part or all of the RF transceiver circuit 122, the baseband processing circuit 124, and the application processing circuit 126 may be combined in the same chip or chipset. In some embodiments, RF transceiver circuitry 122 may be part of interface 114. RF transceiver circuitry 122 may condition RF signals for processing circuitry 120.

[0140] In some embodiments, some or all of the functions described herein as being performed by the WD may be provided by the processing circuit 120 executing instructions stored on a device-readable medium 130, which may be a computer-readable storage medium in some embodiments. In alternative embodiments, some or all of the functions may be provided by the processing circuit 120 without the need to execute instructions stored on a separate or discrete device-readable storage medium, such as in a hardwired manner. In any of those specific embodiments, the processing circuit 120 may be configured to perform the described functions, regardless of whether the instructions stored on the device-readable storage medium are executed. The benefits provided by such functionality are not limited to separate processing circuits 120 or other components of the WD 110, but are shared by the WD 110 as a whole and / or generally by end users and wireless networks.

[0141] Processing circuit 120 may be configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being performed by WD. Such operations as performed by processing circuit 120 may include processing information obtained by processing circuit 120, for example, by converting the obtained information into other information, comparing the obtained information or the converted information with information stored by WD 110, and / or performing one or more operations based on the obtained information or the converted information, and making determinations as a result of the processing.

[0142] Device readable medium 130 is operable to store a computer program, software, application including one or more of logic, rules, code, tables, etc., and / or other instructions executable by processing circuit 120. Device readable medium 130 may include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., compact disk (CD) or digital video disk (DVD)), and / or any other volatile or non-volatile non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions usable by processing circuit 120. In some embodiments, processing circuit 120 and device readable medium 130 may be considered integrated.

[0143] The user interface device 132 can provide a component that allows a human user to interact with the WD 110. This interaction can have multiple forms such as vision, hearing, touch, etc. The user interface device 132 can be operable to generate output to the user and allow the user to provide input to the WD 110. The interaction type can vary depending on the type of user interface device 132 installed in the WD 110. For example, if the WD 110 is a smart phone, the interaction can be via a touch screen; if the WD 110 is a smart meter, the interaction can be through a screen that provides a usage rate (such as the number of gallons used) or a speaker that provides an audible alarm (such as if smoke is detected). The user interface device 132 may include an input interface, device and circuit and an output interface, device and circuit. The user interface device 132 may be configured to allow information to be input into the WD 110, and is connected to the processing circuit 120 to allow the processing circuit 120 to process the input information. The user interface device 132 may include, for example, a microphone, proximity or other sensor, key / button, touch display, one or more cameras, USB port or other input circuit. The user interface device 132 is also configured to allow information to be output from the WD 110 and to allow the processing circuit 120 to output information from the WD 110. The user interface device 132 may include, for example, a speaker, a display, a vibration circuit, a USB port, a headphone jack, or other output circuits. Using one or more input and output interfaces, devices, and circuits of the user interface device 132, the WD 110 can communicate with an end user and / or a wireless network and allow them to benefit from the functionality described herein.

[0144] Auxiliary device 134 is operable to provide more specific functionality that a WD may not normally perform. This may include specialized sensors for taking measurements for various purposes, interfaces for additional communication types such as wired communications, etc. The inclusion and types of components of auxiliary device 134 may vary depending on the embodiment and / or scenario.

[0145] In some embodiments, the power source 136 may be in the form of a battery or battery pack. Other types of power sources may also be used, such as an external power source (e.g., a power socket), a photovoltaic device, or a power battery. The WD 110 may further include a power circuit 137 for delivering power from the power source 136 to various parts of the WD 110, which require power from the power source 136 to perform any function described or indicated herein. In some embodiments, the power circuit 137 may include a power management circuit. The power circuit 137 may additionally or alternatively be operable to receive power from an external power source; in this case, the WD 110 may be connected to an external power source (such as a power socket) via an input circuit or interface (such as a power cable). In some embodiments, the power circuit 137 may also be operable to deliver power from an external power source to the power source 136. This may be used, for example, to charge the power source 136. The power circuit 137 may perform any formatting, conversion, or other modifications to the power from the power source 136 so that the power is suitable for the corresponding components of the WD 110 to be powered.

[0146] In some embodiments, such as Figure 1 The WD of the WD 110 in the example (e.g., from a WD such as Figure 1 The network node of the network node 160 in the example of WD 110 receives TPC commands for one or more of the multiple power control loops configured at WD 110. The multiple power control loops may include one or more of the following: one or more PUCCH power control loops; one or more SRS power control loops; and one or more PUSCH power control loops. In some embodiments, the power limitation may be one or more of maximum power limitation and minimum power limitation.

[0147] WD 110 may receive TPC commands in any suitable manner. As an example, WD 110 may receive TPC commands via UL authorization. As another example, in some embodiments, WD 110 may receive TPC commands via one of DCI formats 0, 1, 2, and 4 (or via similar formats of different RATs such as NR). As another example, in some embodiments, WD 110 may receive TPC commands via one of DCI formats 3 and 3A (or via similar formats of different RATs such as NR). As another example, in some embodiments, WD 110 may receive TPC commands as part of one or more TPC commands sent to a group of wireless devices. As another example, in some embodiments, WD 110 may receive TPC commands in a PDCCH DCI without an associated UL authorization.

[0148] WD 110 obtains an indication of one or more of the multiple power control loops to which the received TPC command applies. In some embodiments, the indication may include at least one parameter associated with one or more of the multiple power control loops configured at WD 110. As an example, in some embodiments, the indication of one or more of the multiple power control loops to which the received TPC command applies may be a power control loop index (e.g., k) indicating that the received TPC command applies to the first power control loop of the two configured power control loops. As another example, in some embodiments, the indication of one or more of the multiple power control loops to which the received TPC command applies may be a closed loop index (e.g., l) indicating that the received TPC command applies to all configured power control loops associated with the first closed loop of the two closed loops.

[0149] WD 110 determines whether one or more conditions related to power control at WD 110 are met based on the indication obtained. WD 110 determines whether WD 110 is power limited based on whether one or more conditions are met. In some embodiments, in response to determining that WD 110 power is not limited, WD 110 can accumulate the received TPC commands. In some embodiments, in response to determining that WD 110 power is limited, WD 110 can determine whether to accumulate the received TPC commands. Note that, as used in this disclosure, "in response to" can (but is not necessarily) be interpreted as "at..." For example, in some embodiments, WD 110 can accumulate the received TPC when it is determined that WD 110 power is not limited. As another example, in some embodiments, WD 110 can determine whether to accumulate the received TPC commands when it is determined that WD 110 power is limited.

[0150] In some embodiments, there is at least one of the following conditions: a Boolean condition describing when WD 110 should accumulate TPC commands at an upper limit, and a Boolean condition describing when WD 110 should accumulate TPC commands at a lower limit. In some cases, the condition may be a function of a closed loop index (e.g., l as described in more detail below). In some cases, the condition may be a function that depends on more than one power control loop. In some cases, the condition may indicate that all power control loops corresponding to a closed loop (e.g., l) should be considered power-limited in order to satisfy the condition. In some cases, the condition may indicate that at least one power control loop corresponding to a closed loop index should be considered power-limited in order to satisfy the condition. In some cases, the condition may indicate that all power control loops should be considered power-limited in order to satisfy the condition. In some cases, the condition may involve both SRS and PUSCH power control loops.

[0151] In some embodiments, WD 110 may determine whether a power control loop in a plurality of power control loops is classified as power limited. WD 110 may determine whether a power control loop in a plurality of power control loops is classified as power limited in any suitable manner. As an example, in some embodiments, WD 110 may determine whether a power control loop in a plurality of power control loops is classified as power limited based on a non-virtual output power. As another example, in some embodiments, WD 110 may determine whether a power control loop in a plurality of power control loops is classified as power limited based on a virtual output power.

[0152] In some embodiments, WD 110 may determine whether a power control loop among the plurality of power control loops is classified as power limited based on PUCCH transmit power. In some embodiments, WD 110 may not determine whether a power control loop among the plurality of power control loops is classified as power limited based on PUCCH transmit power. For example, a PUSCH power control loop may be classified as power limited with or without regard to PUCCH transmit power.

[0153] In some embodiments, determining whether WD 110 is power limited may result in determining that WD 110 is maximum power limited. In such scenarios, WD 110 may determine whether to accumulate received TPC commands. For example, in some embodiments, WD 110 may determine whether the received TPC command is positive or negative. In response to determining that the received TPC command is positive, WD 110 may avoid accumulating the received TPC command. In response to determining that the received TPC command is negative, WD 110 may accumulate the received TPC command.

[0154] In some embodiments, determining whether WD 110 is power limited may result in determining that WD 110 is minimum power limited. In such scenarios, WD 110 may determine whether to accumulate received TPC commands. For example, WD 110 may determine whether the received TPC command is positive or negative. In response to determining that the received TPC command is negative, WD 110 may avoid accumulating the received TPC command. In response to determining that the received TPC command is positive, WD 110 may accumulate the received TPC command.

[0155] In some embodiments, WD 110 may be configured with two power control loops. Each configured power control loop may be associated with a different closed loop. In some embodiments, the indication of one or more of the multiple power control loops to which the received TPC command obtained by WD 110 is applicable may be a power control loop index, which indicates that the received TPC command is applicable to the first power control loop of the two configured power control loops. In some embodiments, WD 110 may obtain an indication of one or more of the multiple power control loops to which the received TPC command is applicable by, for example, receiving an indication from a network node 160. In such scenarios, it may be determined whether one or more conditions are met based on one or more parameters related to the first power control loop. In some embodiments, WD 110 may implicitly receive a power control loop index. In some embodiments, WD 110 may explicitly receive a power control loop index.

[0156] To illustrate, consider a first example embodiment in which WD 110 is configured with two closed loops for transmit power control of PUSCH transmissions on a first serving cell c (eg, f1_c() and f2_c()). When WD 110 receives a PDCCH with a DCI associated with a UL grant, the open and closed loops used to set the transmit power of the PUSCH transmission corresponding to the UL grant (and thus (j, q, l)) can be based on explicit DCI bits indicating the specific open and closed loops to be used, or implicitly based on the beam / QCL configuration associated with the PUSCH transmission (e.g., as described in U.S. Provisional Patent Application No. 62 / 557,018, filed on September 11, 2017, entitled “Beam Indication for UL Power Control,” refiled on September 11, 2018 as International Patent Application No. PCT / IB2018 / 056935, and U.S. Provisional Patent Application No. 62 / 557,018, filed on September 11, 2017, entitled “Unified UL and DL Transmit Power Control,” refiled on September 10, 2018 as International Patent Application No. PCT / IB2018 / 056888, (described in U.S. Provisional Patent Application No. 62 / 556,940 entitled "BeamIndication", both of which are incorporated herein by reference in their entirety). In some embodiments, the TPC command included in the PDCCH DCI may be used to update the determined closed loop state. In the case of accumulation mode, this may correspond to:

[0157] fc(i,l)=fc(i-1,l)+δ PUSCH，c (iK PUSCH ).

[0158] However, special attention should be paid to the case where WD 110 is either maximum or minimum power limited. As used herein, WD 110 may be "power limited" when one or more conditions related to power control at a wireless device are met. In some cases, WD 110 (having multiple power control loops) may also be considered "power limited" in the context of the present disclosure, even if it still has the ability to transmit using other (j, q, 1) values.

[0159] In cases where the maximum power of the WD 110 is limited, e.g. In the sense that WD 110 can choose not to apply positive value δ PUSCH，c (iK PUSCH ). Therefore, in such cases, if δ PUSCH，c (iK PUSCH )>0, then fc(i,l)=fc(i-1,l) can be used.

[0160] In a similar way, we can also define a lower limit such that if Then WD 110 chooses not to accumulate negative TPC values. Therefore, in such cases, if δ PUsCH，c (iK PUSCH )<0, then fc(i,l)=fc(i-1,l) can be used.

[0161] In summary, in some embodiments, the cumulative function can be given as:

[0162] fc(i,l)=fc(i-1,l) If power_max_limited and δ PUSCH，c (iK PUSCH )>0

[0163] fc(i,l)=fc(i-1,l) If power_min_limited and δ PUSCH，c (iK PUSCH )<0 fc(i,l)=fc(i-1,l)+δ PUSCH，c (iK PUSCH ) Other situations

[0164] in

[0165]

[0166]

[0167] Note that P can be determined in a variety of ways. MINFor example, in some embodiments, P may be defined in a specification (eg, RAN4). MIN As another example, in some embodiments, P MIN can be defined as 0. As another example, in some embodiments, P MIN Can be defined by WD 110.

[0168] Figure 2 An example method 200 in a UE according to some embodiments is shown. At step 202, the UE receives a TPC command. In some embodiments, the UE may be configured with two closed loops for transmit power control of, for example, a PUSCH transmission on a first serving cell. At step 204, the UE implicitly or explicitly receives a power control loop index k (and therefore, j, q, l) (e.g., as described above with respect to Figure 1 In some embodiments, k may be received as part of a separate TPC command in an UL grant. For example, k may be received via one of DCI formats 0, 1, 2, and 4 in LTE. As another example, in some embodiments, the power control loop index (e.g., k) may be received via a similar format for a different radio access technology (RAT), such as NR. Figure 1 and Figure 3 In more detail, in some embodiments, a closed loop index 1 may be received. In some cases, the closed loop index 1 may be received via a similar format of a different RAT such as NR.

[0169] At step 206, the UE derives power_max_lim(j,q,l). Note that although Figure 2 The example of shows the determination of power_max_lim(j,q,l), but can be determined in the same way as above with respect to Figure 1 Determining power_min_lim(j,q,l) is performed in a similar manner as described.

[0170] If at step 206, the UE determines that the UE maximum power is not limited, the method proceeds to step 208 and the UE continues to accumulate. However, if at step 206, the UE determines that its maximum power is limited, then at step 210, the UE determines whether the value of δ (e.g., TPC command) is greater than zero (i.e., positive or negative). If at step 210, the UE determines that the value of δ is greater than zero (i.e., positive), the method proceeds to step 212, and the UE does not apply accumulation of positive values ​​of δ. However, if at step 110, the UE determines that δ is less than zero (i.e., negative), the method proceeds to step 208, and the UE continues to accumulate.

[0171] Return to Figure 1As described above, WD 110 may also receive TPC commands in a PDCCH DCI without an associated UL grant, for example, using a DCI format similar to LTE DCI format 3 / 3A (e.g., a similar format for a different RAT such as NR). In such cases, one or more methods described in U.S. Provisional Patent Application No. 62 / 567,044, entitled “TPC Command Indication for Multiple Closed Loops,” filed on October 2, 2017 and resubmitted as International Patent Application No. PCT / SE2018 / 050941 on September 17, 2018, which is incorporated herein by reference in its entirety, may be used to determine the closed loops to which the TPC command applies. In addition, whether accumulation is applied may be determined by one or more example embodiments described below.

[0172] In some embodiments, WD 110 may be configured with at least three power control loops. Each power control loop may be associated with one of the two closed loops, so that at least two of the configured three power control loops are associated with the same closed loop (e.g., the first closed loop of the two closed loops). In some embodiments, the indication of one or more of the multiple power control loops to which the received TPC command obtained by WD 110 is applicable may be a closed loop index (e.g., 1), which indicates that the received TPC command is applicable to all configured power control loops associated with the first closed loop of the two closed loops. In some embodiments, WD 110 may obtain an indication of one or more of the multiple power control loops to which the received TPC command is applicable by, for example, receiving an indication from network node 160. In such a scenario, determining whether one or more conditions are met may be based on one or more parameters related to at least one of the configured power control loops associated with the first closed loop.

[0173] In some embodiments, the received TPC command may be received as part of one or more TPC commands sent to a group of WDs. In some embodiments, the received TPC command may be received in a PDCCH DCI without an associated UL grant. In some embodiments, one or more conditions may be a function of a closed loop index. In some embodiments, one or more conditions may include a function that depends on more than one power control loop.

[0174] In some embodiments, the one or more conditions may include the condition that all power control loops associated with the received closed-loop index must be considered power limited in order to determine that WD 110 is power limited. In some embodiments, the one or more conditions may include the condition that at least one power control loop associated with the received closed-loop index must be considered power limited in order to determine that WD 110 is power limited. In some embodiments, the one or more conditions may include the condition that all power control loops must be considered power limited in order to determine that WD 110 is power limited. In some embodiments, the one or more conditions may include the condition that at least one power control loop must be considered power limited in order to determine that WD 110 is power limited.

[0175] To illustrate, consider a second example embodiment in which a set of power control loops k=1, 2, 3 has been defined and corresponds to the settings (j, q, l) of WD 110 according to Table 2 below.

[0176] Table 2

[0177] k j q l 1 1 1 1 2 1 2 1 3 1 1 2

[0178] If a TPC command in a PDCCH DCI without an associated UL grant (e.g., using a DCI format similar to LTE DCI format 3 / 3A) is given to update the closed loop f(i,2) (i.e., l=2), then WD 110 will implicitly know that (j,q,l)=(1,1,2) since there is only one power control loop using 1=2 in this particular configuration. WD 110 can therefore take advantage of this and use the same constraints as in the first example embodiment described above, thus:

[0179]

[0180]

[0181] However, if a TPC corresponding to closed loop f(i, 1) (i.e., 1=1) is given instead, the value of (j, q, l) is not implicitly given, because both power control loops (j, q, 1)=(1, 1, 1) and (j, q, 1)=(1, 2, 1) use l=1. However, WD 110 will be able to know the group of power control loops that use closed loop l=1. In some embodiments, WD 110 may require that all power control loops within the group should be power limited in order to take into account that WD 110 is power limited and thereby limit the accumulation of l=1.

[0182] More generally, for a given WD, a set of power control loops can be defined using closed loop l = l0 as Then all defined combinations of (j, q, l), where l = l0. In some embodiments, the limiting conditions powermax_limited and / or power_min_limited are functions defined from these sets. The cumulative function can therefore be defined as:

[0183] fc(i, l0) = fc(i-1, l0) If power_max_limited(l0) and δ PUSCH，c (iK PUSCH )>0

[0184] fc(i, l0) = fc(i-1, l0) If power_min_limited(l0) and δ PUSCH，c (iK PUsCH )<0 fc(i, l0)=fc(i-1, l0)+δ PUSCH，c (iK PUSCH ) Other situations

[0185] in

[0186]

[0187]

[0188] This means that the power limitation condition applies to all power control loops using closed loop l 0. Thus, a TPC command that may be associated with l = 1 will correspond to limiting the accumulation with respect to closed loop l = 1, whereas a TPC command associated with l = 2 will not limit the accumulation.

[0189] In some embodiments, the following restrictions may apply

[0190]

[0191]

[0192] This means that if a power control loop using I0 is considered power limited, then the closed loop I0 will limit the accumulation.

[0193] Figure 3Another example method 300 in a UE according to certain embodiments is shown. At step 302, the UE receives a TPC command. In certain embodiments, the UE may be configured with more than two closed loops for transmit power control of, for example, a PUSCH transmission on a first serving cell. At step 304, the UE implicitly or explicitly receives l. In certain embodiments, l may be received as part of one or more TPC commands sent to a group of UEs (e.g., using one PDCCH addressed to the group). As an example, l may be received via one of DCI formats 3 and 3A in LTE. As another example, l may be received via a similar format of a different RAT such as NR.

[0194] At step 306, the UE derives power_max_lim(1). Note that although Figure 3 The example of FIG. 1 shows determining power_max_lim(1), but the same may be used as above with respect to Figure 1 Determining power_min_lim(j, q, l) is performed in a similar manner as described above.

[0195] If the UE determines at step 306 that the UE maximum power is not limited, the method 300 proceeds to step 308 and the UE continues to accumulate. However, if the UE determines at step 306 that its maximum power is limited, then at step 310, the UE determines whether the δ value (e.g., TPC command) is greater than zero (i.e., positive or negative). If the UE determines at step 310 that δ is greater than zero (i.e., positive), the method 300 proceeds to step 312 and the UE does not apply accumulation of positive values ​​δ. However, if the UE determines at step 310 that δ is less than zero (i.e., negative), the method 300 proceeds to step 308 and the UE continues to accumulate.

[0196] return Figure 1 According to the third exemplary embodiment, the following restrictions may apply:

[0197]

[0198]

[0199] This means that if all power control loops used by the WD 110 are considered power limited, the WD 110 will limit the accumulation of all closed loops.

[0200] Figure 4Another example method 400 in a UE according to some embodiments is shown. At step 402, the UE receives a TPC command. In some embodiments, the UE may be configured with more than two closed loops for transmit power control of, for example, a PUSCH transmission on a first serving cell. At step 404, the UE derives power_max_lim. Note that although Figure 4 The example of FIG. 1 shows determining power_max_lim, but determining power_min_lim may be performed in the same manner as described above with respect to Figure 1 The same method as described above is used for execution.

[0201] If the UE determines at step 404 that the UE maximum power is not limited, the method 400 proceeds to step 406 and the UE continues to accumulate. However, if the UE determines at step 404 that its maximum power is limited, then at step 408, the UE determines whether the delta value (e.g., TPC command) is greater than zero (i.e., positive or negative). If the UE determines at step 408 that the delta value is greater than zero (i.e., positive), the method 400 proceeds to step 410 and the UE does not apply accumulation of positive values ​​of delta. However, if the UE determines at step 408 that delta is less than zero (i.e., negative), the method 400 proceeds to step 406 and the UE continues to accumulate.

[0202] return Figure 1 , WD 110 may determine whether to classify a power control loop in the plurality of power control loops as power limited in any suitable manner. As an example, in some embodiments, WD 110 may determine whether a power control loop in the plurality of power control loops is classified as power limited based on a non-virtual output power. As another example, in some embodiments, WD 110 may determine whether a power control loop in the plurality of power control loops is classified as power limited based on a virtual output power.

[0203] For illustration, consider the fourth example embodiment in which WD 110 is not currently transmitting PUSCH. In this scenario, the power limitation condition can then be derived from the virtual output power given by:

[0204]

[0205] And this output can be used to operate Other embodiments are

[0206] as well as

[0207]

[0208] They represent the non-virtual and virtual output powers respectively considering simultaneous transmission of PUCCH.

[0209] Although some of the above example embodiments are related to PUSCH, the present disclosure is not limited to the above example embodiments. Instead, the present disclosure contemplates that the various embodiments described herein may be applicable to other suitable scenarios. For example, the various embodiments described herein are equally applicable to PUCCH and SRS. For illustration, consider the fifth example embodiment, in which the closed loop fc(i, l) is shared between PUSCH and SRS. Thus, there will be a set of PUSCH power control loops (denoted as ) using closed loop l0. ), and there will be a set of SRS power control loops using closed loop l0 (expressed as ). The power limitation condition can then be expressed as and The joint condition of is given by Similar to Furthermore, power_max_limited(l0) can then be defined as:

[0210] power_max_limited(l0)=power_max-limited_PUSCH(l0) and

[0211] power_max_limited_SRS(l0)

[0212] in

[0213]

[0214]

[0215] The next section shows how one or more of the above embodiments can be implemented as a standard example method. The following description reflects one possible method, and the present disclosure is not limited to the examples described below. The exemplary methods described below may be modified, added, or omitted without departing from the scope of the present disclosure.

[0216] In RAN1#90bis, a lot of agreement was reached on closed-loop power control. However, since new features are introduced in NR that will affect the closed-loop part of the NR UL power control, more details need to be considered. For example, regarding the implicit reset of the closed-loop power control part, it was agreed in RAN1#90bis that for the closed-loop power control process, f(i) in the case of the accumulated TPC command mode can be reset by RRC reconfiguration of P_0 and alpha. The agreement states that (similar to LTE), the reconfiguration of P_0 and / or alpha can result in a reset of the accumulated closed-loop power control process. However, since multiple closed loops will be supported in NR, the exact meaning of this agreement needs to be further clarified. For example, given the support of beam-specific power control, a new power control loop can be modified and / or added that relies on a closed loop fc(i, l) already used by another power control loop. Therefore, in such cases, it is inappropriate to directly reset the closed loop fc(i, l) because it will also affect other power control loops. For example, assume that three power control loops b = 1, 2, and 3 have been defined according to Table 2-4 below. If P0_1 corresponding to j = 2 is reconfigured, resetting fc(i, 1) is not appropriate because this closed loop is also used by power control loop b = 1. If P0_1 is reconfigured, resetting fc(i, 2) will also be inappropriate because this closed loop is related to another beam, so fc(i, 2) is not relevant to j = 2.

[0217] Table 2-4. Configurations of the three power control loops represented by b = 1, 2, and 3.

[0218]

[0219] Based on this, there are multiple options to interpret the above protocol. The first option (Option A) is as follows. In the current 38.213 (v1.1.2_v2) draft, the protocol is embodied as

[0220] The UE shall reset the cumulative

[0221] When tP O_UE_PUSCH,c (j) When the value is changed by a higher level;

[0222] When α c (j) When the value is changed by a higher level;

[0223] This can be modified to

[0224] The UE shall reset the cumulative value of serving cell c for fc(I,1) and fc(I,2)

[0225] When tP O_UE_PUSCH,c (j) When changed by high-level and num-p0-alpha-sets<2;

[0226] When α c (j) When the value is changed by a higher layer and num-p0-alpha-sets<2;

[0227] where num-p0-alpha-sets is defined as: for j∈{2,...,,J-1}=S J , for all j∈S J P O_NOMINAL_PUSCH,c (j) The value is indicated by the higher-layer parameter p0-nominal-pusch-withgrant of the serving cell c, and a set of P O_UE_PUSCH,c The (j) value is indicated by a set of higher-level parameters p0-ue-pusch-withgrant for serving cell c, where the size of the set is J-2 and is indicated by the higher-level parameter num-p0-alpha-sets.

[0228] Therefore, this modification will mean that a reset is only performed if only one power control loop is defined for grant based UL power control.

[0229] The second option (Option B) is as follows: Support higher layer configuration so that reset by RRC reconfiguration of P_0 and alpha can be activated or deactivated.

[0230] The third option (Option C) is as follows: Support high-level configuration so that when configuring P_0 and alpha, a Boolean value indicating reset or not reset is also provided.

[0231] Therefore, the functionality to reset the accumulated TPC f(i,l) when reconfiguring P_0 and alpha should be i) only active when only one power control loop is defined for grant-based PUSCH, or ii) possibly activated or deactivated by higher layer configuration, or iii) explicitly indicated by higher layers when reconfiguring P_0.

[0232] Another issue with closed loop power control in NR regarding explicit reset of the closed loop power control part is that the new features introduced will imply situations that may arise when no TPC commands have been given for a long time. One example is the situation where aperiodic SRS has not been triggered and sent for a long time. This may imply that the closed loop part is out of date and thus (in case of accumulation mode) it would be beneficial to explicitly reset the closed loop part (instead of using outdated accumulated values). On the other hand, if the SRS has been sent recently, we would rather not reset the closed loop part. As another example, the same issue arises in beam specific power control when the gNB redirects its beam. For the new propagation environment in case of accumulation mode, this situation of the closed loop power control part of the beam corresponding to the old direction may be irrelevant. Therefore, it would also be beneficial to explicitly reset the closed PC loop part on selected occasions. As another example, since multiple closed loops are supported in case of beam specific power control, the situation when a beam has not been used for PUSCH for a long time means that the closed loop part may be out of date since TPC will be adapted to the PC loop used for PUSCH transmission. Therefore, there is a motivation to explicitly reset the closed loop power control part here as well.

[0233] Based on this, it is proposed to support explicit reset of the closed-loop power control part in case of accumulation mode.

[0234] Regarding multiple closed-loop power control procedures for PUSCH, according to recent agreements, in case of PUSCH, a set of PC parameters will be defined for NR and given by a set of indices {j,k,l}. Here, l refers to different closed-loop power control procedures, where fc(i,l) represents the closed-loop procedure that is controlled by signaling from the gNB using TPC commands. Therefore, in case there is more than one closed-loop procedure defined, when the gNB sends a TPC command, the command needs to be appended and applied to a certain index l. Two possible options for doing so are described below.

[0235] The first option (option 1) is as follows. The TPC command is implicitly connected to the index l by using the index l, which is used to set the output power in the PUSCH transmission. Therefore, if the current power control is based on the power control set corresponding to the index {j', k', l'}, the TPC command is applicable to the closed loop process corresponding to l = l'.

[0236] The second option (option 2) is as follows: The TPC command is explicitly linked to the index 1 by indicating it with the TPC command, or alternatively providing the index in a separate command.

[0237] In LTE, there are essentially two ways to send TPC commands: UE-specific (such as DCI formats 0, 1, 2 and 4) and group-based (such as formats 3 and 3A). This will also be supported for NR. For example, it has been agreed that NR will support closed power control commands through DL DCI for PUCCH power control and through UL grants for PUSCH power control (SRS is for further study). It has also been agreed that NR will support closed power control commands through group-common DCI with TPC-PUSCH-RNTI, TPC-PUCCH-RNTI and TPC-SRS-RNTI. Let's consider these cases from the perspective of option 1 and option 2.

[0238] For the UE-specific TPC case, a TPC is received by the UE and since the TPC command generated by the gNB will be based on the current output power setting of the UE, the TPC will be implicitly related to the currently used PC parameters {j', k', l'}. Therefore, option 1 provides sufficient functionality.

[0239] For the group-based TPC case, there are two potential approaches. One option (Option 2A) is to configure two TPC-PUSCH-RNTIs for the UE and then connect f(i,1) to TPC-PUSCH-RNTI1 and f(i,2) to TPC-PUSCH-RNTI2. The second option (Option 2B) is that the applicable l is explicitly indicated as part of the DCI. Therefore, a bit index is added to each TPC command in DCI 3 / 3A, which indicates the corresponding f(i,l) to which the command applies. Option 2A or Option 2B will meet the requirements in terms of explicitly associating the TPC command with the corresponding f(i,l). Option 2B may be more suitable when multiple closed loops are configured to process multiple beams (e.g., for multiple TRPs), while Option 2A is more suitable for distinguishing closed loop corrections between authorized PUSCH and unauthorized PUSCH.

[0240] Therefore, when the UE is configured with multiple loops (f_c(i,l)), l=1,2, the TPC command present in the group-based DCI (eg, similar to LTE 3 / 3A) should be explicitly / implicitly associated with one of the loops.

[0241] Based on the above, one way how one or more of the above embodiments may be implemented as a standard is that: (1) the functionality of resetting the accumulated TPC f(i,l) when reconfiguring P_0 and alpha should be (i) only active when only one power control loop is defined for grant-based PUSCH, or (ii) possibly activated or deactivated through high-level configuration, or (iii) explicitly indicated by high-level when reconfiguring P_0; (2) support explicit reset of the closed-loop power control part in case of accumulation mode; and (3) when the UE is configured with multiple closed-loops (f_c(i,l)), l=1,2, the TPC command present in the group-based DCI (e.g., similar to LTE 3 / 3A) should be explicitly and / or implicitly associated with one of the closed-loops.

[0242] However, please note that the above method is only an example of how one or more of the above embodiments can be implemented as a standard. The present disclosure is not limited to the above method. In fact, the above example method can be modified, added or omitted without departing from the scope of the present disclosure.

[0243] Figure 5 One embodiment of a UE in accordance with certain embodiments is shown. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and / or operates the associated device. Rather, a UE may represent a device that is intended to be sold to or operated by a human user, but that may not, or may not initially, be associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended to be sold to or operated by an end user, but that may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE 500 may be any UE identified by the 3rd Generation Partnership Project (3GPP), including a NB-IoT UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. As Figure 5 As shown in , UE 500 is an example of a WD configured to communicate according to one or more communication standards promulgated by the Third Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE and / or 5G standards. As previously mentioned, the terms WD and UE may be used interchangeably. Therefore, although Figure 5 It is UE, but the components discussed here are also applicable to WD and vice versa.

[0244] exist Figure 5In the embodiment, UE 500 includes a processing circuit 501, which is operably coupled to an input / output interface 505, a radio frequency (RF) interface 509, a network connection interface 511, a memory 515 including a random access memory (RAM) 517, a read-only memory (ROM) 519, and a storage medium 521, a communication subsystem 531, a power supply 513, and / or any other components, or any combination thereof. The storage medium 521 includes an operating system 523, an application 525, and data 527. In other embodiments, the storage medium 521 may include other similar types of information. Some UEs may utilize Figure 5 All components shown in, or only a subset of the components. The level of integration between components may vary from one UE to another. In addition, some UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0245] exist Figure 5 , processing circuit 501 may be configured to process computer instructions and data. Processing circuit 501 may be configured to implement any sequential state machine operable to execute machine instructions stored in memory as a machine-readable computer program, such as one or more hardware-implemented state machines (e.g., in the form of discrete logic, FPGA, ASIC, etc.); programmable logic and appropriate firmware; one or more stored programs, general-purpose processors (such as microprocessors or digital signal processors (DSPs)) and appropriate software; or any combination of the above. For example, processing circuit 501 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

[0246] In the depicted embodiment, the input / output interface 505 may be configured to provide a communication interface to an input device, an output device, or an input and output device. The UE 500 may be configured to use an output device via the input / output interface 505. The output device may use an interface port of the same type as the input device. For example, a USB port may be used to provide input to or output from the UE 500. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, a transmitter, a smart card, another output device, or any combination thereof. The UE 500 may be configured to use an input device via the input / output interface 505 to allow a user to capture information into the UE 500. The input device may include a touch-sensitive display or a presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a trackball, a steering wheel, a trackpad, a scroll wheel, a smart card, etc. The presence-sensitive display may include a capacitive or resistive touch sensor for sensing input from a user. The sensor can be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another similar sensor, or any combination thereof. For example, the input device can be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

[0247] exist Figure 5 In the embodiment of the present invention, the RF interface 509 can be configured to provide a communication interface to RF components (such as transmitters, receivers, and antennas). The network connection interface 511 can be configured to provide a communication interface to the network 543a. The network 543a can include a wired and / or wireless network, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof. For example, the network 543a can include a Wi-Fi network. The network connection interface 511 can be configured to include a receiver and a transmitter interface for communicating with one or more other devices through a communication network according to one or more communication protocols (such as Ethernet, TCP / IP, SONET, ATM, etc.). The network connection interface 511 can implement receiver and transmitter functions suitable for communication network links (e.g., optical, electrical, etc.). The transmitter and receiver functions can share circuit components, software, or firmware, or can alternatively be implemented separately.

[0248] RAM 517 can be configured to interface with processing circuit 501 via bus 502 to provide storage or cache of data or computer instructions during execution of software programs such as operating systems, applications, and device drivers. ROM 519 can be configured to provide computer instructions or data to processing circuit 501. For example, ROM 519 can be configured to store unchanged low-level system code or data for basic system functions (such as basic input and output (I / O), startup, or receiving keystrokes stored in non-volatile memory from a keyboard). Storage medium 521 can be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), disk, optical disk, floppy disk, hard disk, removable cassette or flash drive. In one example, storage medium 521 can be configured to include operating system 523, application 525 (such as a Web browser application, widget or gadget engine or another application) and data file 527. The storage medium 521 may store any of various operating systems or combinations of operating systems used by the UE 500 .

[0249] The storage medium 521 may be configured to include multiple physical drive units, such as a redundant array of independent disks (RAID), a floppy disk drive, a flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disk (HD-DVD) optical drive, an internal hard drive, a Blu-ray optical drive, a holographic digital data storage (HDDS) optical drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro DIMM SDRAM, a smart card memory (such as a user identity module or a removable user identity (SIM / RUIM) module), other memory or any combination thereof. The storage medium 521 may allow the UE 500 to access computer executable instructions, applications, etc. stored on a transient or non-transitory memory medium to unload data or upload data. An article of manufacture (such as an article of manufacture utilizing a communication system) may be tangibly embodied in a storage medium 521 including a device-readable medium.

[0250] exist Figure 5In the embodiment of the present invention, the processing circuit 501 may be configured to communicate with the network 543b using the communication subsystem 531. The network 543a and the network 543b may be the same one or more networks, or different one or more networks. The communication subsystem 531 may be configured to include one or more transceivers for communicating with the network 543b. For example, the communication subsystem 531 may be configured to include one or more transceivers for communicating with one or more remote transceivers of another device capable of wireless communication (such as another WD, UE or base station of the radio access network (RAN)) according to one or more communication protocols (such as IEEE 802.QQ2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc.). Each transceiver may include a transmitter 533 and / or a receiver 535 to respectively implement a transmitter or receiver function (e.g., frequency allocation, etc.) suitable for a RAN link. In addition, the transmitter 533 and the receiver 535 of each transceiver may share circuit components, software or firmware, or may alternatively be implemented separately.

[0251] In the illustrated embodiment, the communication functions of the communication subsystem 531 may include 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 the location, another similar communication function, or any combination thereof. For example, the communication subsystem 531 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network 543b may cover wired and / or wireless networks, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof. For example, the network 543b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply 513 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 500.

[0252] The features, benefits and / or functions described herein may be implemented in one of the components of UE 500, or may be split between multiple components of UE 500. In addition, the features, benefits and / or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, the communication subsystem 531 may be configured to include any component described herein. In addition, the processing circuit 501 may be configured to communicate with any such component via the bus 502. In another example, any such component may be represented by a program instruction stored in a memory, which implements the corresponding function described herein when executed by the processing circuit 501. In another example, the function of any such component may be divided between the processing circuit 501 and the communication subsystem 531. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware, while the computationally intensive functions may be implemented in hardware.

[0253] Figure 6 is a schematic block diagram illustrating a virtualized environment according to some embodiments. More specifically, Figure 6 600 is a schematic block diagram illustrating a virtualized environment in which the functions implemented by some embodiments may be virtualized. In the present context, virtualization means creating a virtual version of an apparatus or device, which may include virtualized hardware platforms, storage devices, and network resources. As used herein, virtualization may be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or a device (e.g., a UE, a wireless device, or any other type of communication device) or a component thereof, and relates to an implementation in which at least a portion of the functions are implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines, or containers executed on one or more physical processing nodes in one or more networks).

[0254] In some embodiments, some or all of the functionality described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 600 hosted by one or more hardware nodes 630. Furthermore, in embodiments where the virtual nodes are not radio access nodes or do not require radio connectivity (e.g., core network nodes), then the network nodes may be fully virtualized.

[0255] This functionality may be implemented by one or more applications 620 (which may be alternatively referred to as software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operable to implement some of the features, functions, and / or benefits of some embodiments disclosed herein. The applications 620 run in a virtualized environment 600 that provides hardware 630 including processing circuitry 660 and memory 690. The memory 690 contains instructions 695 executable by the processing circuitry 660, whereby the applications 620 are operable to provide one or more of the features, benefits, and / or functions disclosed herein.

[0256] The virtualized environment 600 includes a general or special network hardware device 630 including a set of one or more processors or processing circuits 660, which may be a commercial off-the-shelf (COTS) processor including digital or analog hardware components or a special processor, a special application-specific integrated circuit (ASIC), or any other type of processing circuit. Each hardware device may include a memory 690-1, which may be a non-permanent memory for temporarily storing instructions 695 or software executed by the processing circuit 660. Each hardware device may include one or more network interface controllers (NICs) 670, also known as network interface cards, including physical network interfaces 680. Each hardware device may also include a non-transitory persistent machine-readable storage medium 690-2 in which software 695 and / or instructions executable by the processing circuit 660 are stored. The software 695 may include any type of software including software for instantiating one or more virtualization layers 650 (also known as a hypervisor), software for executing virtual machines 640, and software that allows it to perform functions, features, and / or benefits associated with some embodiments described herein.

[0257] The virtual machine 640 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may be run by a corresponding virtualization layer 650 or hypervisor. Different embodiments of instances of the virtual device 620 may be implemented on one or more virtual machines 640 and may be implemented in different ways.

[0258] During operation, processing circuit 660 executes software 695 to instantiate a hypervisor or virtualization layer 650 , which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 650 may present what appears to be a virtual operating platform that networks hardware to virtual machines 640 .

[0259] like Figure 6As shown in , hardware 630 can be an independent network node with general or specialized components. Hardware 630 can include antenna 6225, and some functions can be implemented via virtualization. Alternatively, hardware 630 can be part of a larger hardware cluster (e.g., such as in a data center or customer premise equipment (CPE)), where many hardware nodes work together and are managed via management and orchestration (MANO) 6100 that oversees the lifecycle management of application 620, in particular.

[0260] In some contexts, virtualization of hardware is referred to as network function virtualization (NFV). NFV can be used to consolidate many network equipment types into industry-standard high-volume server hardware, physical switches, and physical storage devices that can be located in a data center, as well as client devices.

[0261] In the context of NFV, a virtual machine 640 may be a software implementation of a physical machine that runs a program as if the program were executed on a physical non-virtual machine. Each virtual machine 640 and the portion of the hardware 630 on which it executes (whether dedicated to the virtual machine and / or hardware shared by the virtual machine with other virtual machines 640) form a separate virtual network element (VNE).

[0262] Still in the context of NFV, a virtual network function (VNF) is responsible for handling specific network functions running in one or more virtual machines 640 on top of the hardware networking infrastructure 630 and interacting with the Figure 6 Corresponding to application 620 in.

[0263] In some embodiments, one or more radio units 6200, each including one or more transmitters 6220 and one or more receivers 6210, may be coupled to one or more antennas 6225. The radio units 6200 may communicate directly with the hardware nodes 630 via one or more appropriate network interfaces, and may be used in conjunction with virtual components for providing a virtual node with radio capabilities, such as a radio access node or base station.

[0264] In some embodiments, control system 6230 may be used to implement some signaling that may alternatively be used for communications between hardware node 630 and radio unit 6200 .

[0265] Figure 7 An example telecommunications network connected to a host computer via an intermediate network is shown in accordance with some embodiments. Figure 7According to an embodiment, a communication system includes a telecommunication network 710 such as a 3GPP type cellular network, which includes an access network 711 such as a radio access network and a core network 714. The access network 711 includes a plurality of base stations 712a, 712b, 712c such as NB, eNB, gNB or other types of wireless access points, each of which defines a corresponding coverage area 713a, 713b, 713c. Each base station 712a, 712b, 712c may be connected to the core network 714 via a wired or wireless connection 715. A first UE 791 located in the coverage area 713c is configured to be wirelessly connected to or paged by the corresponding base station 712c. A second UE 792 in the coverage area 713a may be wirelessly connected to the corresponding base station 712a. Although multiple UEs 791, 792 are shown in this example, the disclosed embodiments are equally applicable to situations where a single UE is in the coverage area or a single UE is connecting to the corresponding base station 712.

[0266] The telecommunications network 710 itself is connected to a host computer 730, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer 730 may be under the ownership or control of a service provider, or may be operated by or on behalf of a service provider. The connections 721, 722 between the telecommunications network 710 and the host computer 730 may extend directly from the core network 714 to the host computer 730, or may be made via an optional intermediate network 720. The intermediate network 720 may be a combination of one or more of a public network, a private network, or a managed network; the intermediate network 720 (if any) may be a backbone network or the Internet; in particular, the intermediate network 720 may include two or more sub-networks (not shown).

[0267] Figure 7The communication system as a whole implements the connection between the connected UE 791, 792 and the host computer 730. This connectivity can be described as an over-the-top (OTT) connection 750. The host computer 730 and the connected UE 791, 792 are configured to use the access network 711, the core network 714, any intermediate network 720 and possible other infrastructure (not shown) as an intermediary to transmit data and / or signaling via the OTT connection 750. The OTT connection 750 can be transparent in the sense that the participating communication devices through which the OTT connection 750 passes do not know the path of the uplink and downlink communication. For example, the base station 712 cannot or does not need to be informed about the past path of the incoming downlink communication with data originating from the host computer 730 to be forwarded (e.g., switched) to the connected UE 791. Similarly, the base station 712 does not need to know the future path of the outgoing uplink communication originating from the UE 791 to the host computer 730.

[0268] Figure 8 An example of a host computer communicating with a UE via a base station through a partially wireless connection according to some embodiments is shown. According to an embodiment, reference will now be made to Figure 8 Describe the example implementation of the UE, base station and host computer discussed in the previous paragraph. In the communication system 800, the host computer 810 includes hardware 815, which includes a communication interface 816 configured to establish and maintain a wired or wireless connection with different communication devices of the communication system 800. The host computer 810 further includes a processing circuit 818 that may have storage and / or processing capabilities. In particular, the processing circuit 818 may include one or more programmable processors, application-specific integrated circuits, field programmable gate arrays, or combinations of these suitable for executing instructions (not shown). The host computer 810 further includes software 811 stored in or accessible by the host computer 810 and executable by the processing circuit 818. The software 811 includes a host application 812. The host application 812 may be operable to provide services to remote users (such as UE 830 connected via an OTT connection 850 terminated at the UE 830 and the host computer 810). When providing services to remote users, the host application 812 can provide user data sent using the OTT connection 850.

[0269] The communication system 800 further comprises a base station 820, which is provided in the telecommunication system and comprises hardware 825 enabling it to communicate with the host computer 810 and the UE 830. The hardware 825 may comprise a communication interface 826 for establishing and maintaining a wired or wireless connection with interfaces of different communication devices of the communication system 800, and for establishing and maintaining a connection with at least a network located in a coverage area ( Figure 8The communication interface 826 may be configured to facilitate a connection 860 to the host computer 810. The connection 860 may be direct, or it may be through a core network (eg, a wireless network) of the telecommunications system. Figure 8 820) and / or through one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware 825 of the base station 820 further includes processing circuitry 828 that may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) suitable for executing instructions. The base station 820 further has software 821 stored internally or accessible via an external connection.

[0270] The communication system 800 further includes the UE 830 already mentioned. Its hardware 835 may include a radio interface 837, which is configured to establish and maintain a wireless connection 870 with a base station serving the coverage area where the UE 830 is currently located. The hardware 835 of the UE 830 further includes a processing circuit 838 that may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) suitable for executing instructions. The UE 830 further includes software 831 stored in the UE 830 or accessible by the UE 830 and executable by the processing circuit 838. The software 831 includes a client application 832. With the support of the host computer 810, the client application 832 may be operable to provide services to human or non-human users via the UE 830. In the host computer 810, the executed host application 812 can communicate with the executed client application 832 via an OTT connection 850 terminated at the UE 830 and the host computer 810. When providing services to users, the client application 832 can receive request data from the host application 812 and provide user data in response to the request data. The OTT connection 850 can transmit both the request data and the user data. The client application 832 can interact with the user to generate the user data it provides.

[0271] Notice, Figure 8 The host computer 810, base station 820 and UE 830 shown in FIG. Figure 7 The host computer 730, one of the base stations 712a, 712b, 712c, and one of the UEs 791, 792 may be similar or identical. That is, the internal operation of these entities may be similar to Figure 8 , and independent of its surrounding network topology can be Figure 7 The surrounding network topology.

[0272] exist Figure 88, an OTT connection 850 has been abstractly drawn showing communications between a host computer 810 and a UE 830 via a base station 820, without explicit reference to any intermediate devices and the precise path of the messages via these devices. The network infrastructure may determine a route that may be configured to be hidden from the UE 830 or from the service provider operating the host computer 810, or both. When the OTT connection 850 is active, the network infrastructure may further make decisions through which to dynamically change the route (e.g., based on load balancing considerations or reconfiguration of the network).

[0273] The wireless connection 870 between the UE 830 and the base station 820 is in accordance with the teachings of the embodiments described throughout the present disclosure. One or more of the various embodiments use the OTT connection 850 in which the wireless connection 870 forms the last segment to improve the performance of the OTT service provided to the UE 830. More precisely, the teachings of these embodiments can improve the ability of the UE 830 to clearly identify whether it is maximum / minimum power limited, and thereby provide benefits such as improved power control at the UE 830.

[0274] A measurement process may be provided for the purpose of monitoring data rates, latency, and other factors improved by one or more embodiments. There may further be an optional network function for reconfiguring the OTT connection 850 between the host computer 810 and the UE 830 in response to changes in the measurement results. The measurement process and / or network function for reconfiguring the OTT connection 850 may be implemented in the software 811 and hardware 815 of the host computer 810 or in the software 831 and hardware 835 of the UE 830 or in both. In an embodiment, a sensor (not shown) may be deployed in or associated with a communication device through which the OTT connection 850 passes; the sensor may participate in the measurement process by providing the value of the monitoring quantity exemplified above or providing the value of other physical quantities from which the software 811, 831 can calculate or estimate the monitoring quantity. The reconfiguration of the OTT connection 850 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not need to affect the base station 820 and may be unknown or imperceptible to the base station 820. Such processes and functions may be known and implemented in the art. In certain embodiments, the measurements may involve proprietary UE signaling that facilitates the host computer 810's measurements of throughput, propagation time, latency, etc. The measurements may be implemented in that the software 811 and 831 causes messages (particularly empty or "fake" messages) to be sent using the OTT connection 850 while monitoring propagation time, errors, etc.

[0275] Fig. 9 is a flow chart of a method implemented in a communication system according to some embodiments. Fig. 9 In the example, the communication system includes a reference Figure 7 and Figure 8 In order to simplify the present disclosure, only the host computers, base stations and UEs described in the present invention will be included in this section. Fig. 9 . In step 910, the host computer provides user data. In sub-step 911 of step 910 (which may be optional), the host computer provides the user data by executing a host application. In step 920, the host computer initiates a transmission to the UE carrying the user data. In step 930 (which may be optional), in accordance with the teachings of the embodiments described throughout the present disclosure, the base station sends the user data carried in the transmission initiated by the host computer to the UE. In step 940 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0276] Fig.10 is a flow chart of a method implemented in a communication system according to some embodiments. Fig.10 Examples of communication systems include those which may be referenced Figure 7 and Figure 8 The host computers, base stations and UEs described in the present invention are only included in this section. Fig.10 . In step 1010 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In step 1020, the host computer initiates a transmission to the UE carrying the user data. According to the teachings of the embodiments described throughout the present disclosure, the transmission may be delivered via a base station. In step 1030 (which may be optional), the UE receives the user data carried in the transmission.

[0277] Fig.11 is a flow chart of a method implemented in a communication system according to some embodiments. Fig.11 In the example, the communication system includes a reference Figure 7 and Figure 8 The host computers, base stations and UEs described in the present invention are only included in this section. Fig.11. In step 1110 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1120, the UE provides user data. In sub-step 1121 (which may be optional) of step 1120, the UE provides user data by executing a client application. In sub-step 1111 (which may be optional) of step 1110, the UE executes a client application that provides user data in response to the received input data provided by the host computer. When providing user data, the executed client application may further consider user input received from the user. Regardless of the specific manner of providing user data, the UE initiates the transmission of user data to the host computer in sub-step 1130 (which may be optional). In step 1140 of the method, in accordance with the teachings of the embodiments described throughout the present disclosure, the host computer receives user data sent from the UE.

[0278] Fig.12 is a flow chart of a method implemented in a communication system according to some embodiments. Fig.12 In the example, the communication system includes a reference Figure 7 and Figure 8 The host computers, base stations and UEs described in the present invention are only included in this section. Fig.12 In step 1210 (which may be optional), the base station receives user data from the UE in accordance with the teachings of the embodiments described throughout the present disclosure. In step 1220 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 1230 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0279] Fig.13 1 is a flow chart of a method 1300 in a wireless device according to some embodiments. The method 1300 begins at step 1301, where the wireless device receives a TPC command for one or more of a plurality of power control loops configured at the wireless device from a network node. In some embodiments, the plurality of power control loops may include one or more of: one or more PUCCH power control loops; one or more SRS power control loops; and one or more PUSCH power control loops.

[0280] At step 1302, the wireless device obtains an indication of one or more of a plurality of power control loops to which the received TPC command applies.

[0281] At step 1303, the wireless device determines whether one or more conditions related to power control at the wireless device are satisfied based on the obtained indication. In some embodiments, the indication may include at least one parameter associated with one or more of a plurality of power control loops configured at the wireless device.

[0282] At step 1304, the wireless device determines whether the wireless device is power limited based on whether one or more conditions are satisfied. In some embodiments, power limited may include one or more of: maximum power limited; and minimum power limited.

[0283] In some embodiments, the method may include, in response to determining that the wireless device is not power limited, accumulating the received TPC commands.

[0284] In some embodiments, the method may include: in response to determining that the wireless device is power limited, determining whether to accumulate the received TPC command. In some embodiments, determining whether the wireless device is power limited may result in determining that the wireless device is maximum power limited, and determining whether to accumulate the received TPC command may include determining whether the received TPC command is positive or negative, and performing one of the following operations: in response to determining that the received TPC command is positive, avoiding accumulating the received TPC command; in response to determining that the received TPC command is negative, accumulating the received TPC command. In some embodiments, determining whether the wireless device is power limited may result in determining that the wireless device is minimum power limited, and determining whether to accumulate the received TPC command may include determining whether the received TPC command is positive or negative, and performing one of the following operations: in response to determining that the received TPC command is negative, avoiding accumulating the received TPC command; in response to determining that the received TPC command is positive, accumulating the received TPC command.

[0285] In some embodiments, the wireless device may be configured with two power control loops, each configured power control loop being associated with a different closed loop. Obtaining the indication may include receiving a power control loop index (e.g., k) indicating that the received TPC command is applicable to a first power control loop of the two configured power control loops. In this scenario, it may be determined whether one or more conditions are satisfied based on one or more parameters related to the first power control loop. In some embodiments, the received TPC command may be received via a UL grant. In some embodiments, the received TPC command may be received via one of DCI formats 0, 1, 2, and 4 (or via a similar format of a different RAT such as NR). In some embodiments, the power control loop index may be received via a UL grant. In some embodiments, the power control loop index may be received implicitly. In some embodiments, the power control loop index may be received explicitly.

[0286] In some embodiments, the wireless device may be configured with at least three power control loops, each power control loop being associated with one of the two closed loops, such that at least two of the configured three power control loops are associated with the same closed loop (e.g., the first of the two closed loops). Obtaining the indication may include: receiving a closed loop index (e.g., 1) indicating that the received TPC command is applicable to all configured power control loops associated with the first of the two closed loops. In this scenario, it may be determined whether one or more conditions are satisfied based on one or more parameters related to at least one of the configured power control loops associated with the first closed loop. In some embodiments, the received TPC command may be received as part of one or more TPC commands sent to a group of wireless devices (e.g., UEs). In some embodiments, the received TPC command may be received via one of DCI formats 3 and 3A (or via a similar format of a different RAT such as NR). In some embodiments, the received TPC command may be received in a PDCCH DCI without an associated UL grant. In some embodiments, the one or more conditions may be a function of the closed loop index. In some embodiments, one or more conditions may include a function that depends on more than one power control loop.

[0287] In some embodiments, the one or more conditions may include the condition that all power control loops associated with the received closed loop index must be considered power limited in order to determine that the wireless device is power limited. In some embodiments, the one or more conditions may include the condition that at least one power control loop associated with the received closed loop index must be considered power limited in order to determine that the wireless device is power limited. In some embodiments, the one or more conditions may include the condition that all power control loops must be considered power limited in order to determine that the wireless device is power limited. In some embodiments, the one or more conditions may include the condition that at least one power control loop must be considered power limited in order to determine that the wireless device is power limited.

[0288] In some embodiments, the method may include determining whether a power control loop in a plurality of power control loops is classified as power limited. In some embodiments, determining whether a power control loop in a plurality of power control loops is classified as power limited may be based on a non-virtual output power. In some embodiments, determining whether a power control loop in a plurality of power control loops is classified as power limited may be based on a virtual output power. In some embodiments, determining whether a power control loop in a plurality of power control loops is classified as power limited may be based on a PUCCH transmit power. In some embodiments, determining whether a power control loop in a plurality of power control loops is classified as power limited may not be based on a PUCCH transmit power.

[0289] In certain embodiments, the method may include providing user data and forwarding the user data to a host computer via transmission to a base station.

[0290] Fig.14 is a schematic block diagram of a virtualization device according to some embodiments. More particularly, Fig.14 A wireless network (eg, Figure 1 1400 in a wireless network (e.g., Figure 1 The apparatus 1400 is operable to perform the reference Fig.13 The example methods described herein and any other processes or methods that may be disclosed herein. It should also be understood that Fig.13 The method does not have to be performed only by the apparatus 1400. At least some operations of the method may be performed by one or more other entities.

[0291] The virtual device 1400 may include: a processing circuit, which may include one or more microprocessors or microcontrollers; and other digital hardware, which may include a digital signal processor (DSP), dedicated digital logic, etc. The processing circuit may be configured to execute program code stored in a memory, which may include one or more types of memory, such as a read-only memory (ROM), a random access memory, a cache memory, a flash memory device, an optical storage device, etc. In several embodiments, the program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols, and instructions for executing one or more techniques described herein. In some implementations, the processing circuit may be used to cause the receiving unit 1402, the determining unit 1404, the communication unit 1406, and any other suitable unit of the device 1400 to perform corresponding functions according to one or more embodiments of the present disclosure, such as a method for determining whether a wireless device is power-limited as described above.

[0292] In some embodiments, the apparatus 1400 may be a UE. Fig.14 As shown in , the apparatus 1400 includes a receiving unit 1402, a determining unit 1404, and a communicating unit 1406. The receiving unit 1402 may be configured to perform the receiving function of the apparatus 1400. For example, the receiving unit 1402 may be configured to receive a TPC command for one or more of a plurality of power control loops configured at the apparatus 1400 from a network node. In some embodiments, the receiving unit 1402 may be configured to receive the TPC command via a UL grant. In some embodiments, the receiving unit 1402 may be configured to receive the TPC command via one of DCI formats 0, 1, 2, and 4 (or via a similar format of a different RAT such as NR). In some embodiments, the receiving unit 1402 may be configured to receive a TPC command as part of one or more TPC commands sent to a group of wireless devices. In some embodiments, the receiving unit 1402 may be configured to receive the TPC command via one of DCI formats 3 and 3A (or via a similar format of a different RAT such as NR). In some embodiments, the receiving unit 1402 may be configured to receive a TPC command in a PDCCH DCI without an associated UL grant.

[0293] As another example, the receiving unit 1402 may be configured to obtain an indication of one or more of a plurality of power control loops to which the received TPC command applies. In some embodiments, the receiving unit 1402 may be configured to receive one or more parameters associated with one or more of a plurality of power control loops configured at the apparatus 1400. In some embodiments, the receiving unit 1402 may be configured to receive a power control loop index (e.g., k) indicating that the received TPC command applies to a first power control loop of two configured power control loops. In some embodiments, the receiving unit 1402 may be configured to receive the power control loop index via a UL grant. In some embodiments, the receiving unit 1402 may be configured to implicitly receive the power control loop index. In some embodiments, the receiving unit 1402 may be configured to explicitly receive the power control loop index. In some embodiments, the receiving unit 1402 may be configured to receive a closed loop index (eg, 1) indicating that the received TPC command is applicable to all configured power control loops associated with the same closed loop (eg, the first of the two closed loops).

[0294] The receiving unit 1402 may receive any suitable information (eg, from a wireless device or another network node). The receiving unit 1402 may include a receiver and / or a transceiver, such as the one described above with reference to Figure 11400. The receiving unit 1402 may include a circuit configured to receive messages and / or signals (wireless or wired). In certain embodiments, the receiving unit 1402 may transmit the received messages and / or signals to the determining unit 1404 and / or any other suitable unit of the device 1400. In some embodiments, the functions of the receiving unit 1402 may be performed in one or more different units.

[0295] The determining unit 1404 may be configured to perform the processing functions of the apparatus 1400. For example, the determining unit 1404 may be configured to obtain an indication of one or more of a plurality of power control loops to which the received TPC command applies. In certain embodiments, the determining unit 1404 may be configured to obtain at least one parameter associated with one or more of a plurality of power control loops configured at the apparatus 1400. In certain embodiments, the determining unit 1404 may be configured to obtain a power control loop index (e.g., k) indicating that the received TPC command applies to a first power control loop of two configured power control loops. In certain embodiments, the determining unit 1404 may be configured to obtain the power control loop index implicitly. In certain embodiments, the determining unit 1404 may be configured to obtain the power control loop index explicitly. In some embodiments, the determining unit 1404 may be configured to obtain a closed-loop index (eg, 1) indicating that the received TPC command is applicable to all configured power control loops associated with the same closed loop (eg, the first of the two closed loops).

[0296] As another example, the determining unit 1404 may be configured to determine, based on the obtained indication, whether one or more conditions related to power control at the apparatus 1400 are satisfied. In some embodiments, the determining unit 1404 may be configured to determine, based on one or more parameters related to the first power control loop, whether the one or more conditions are satisfied. In some embodiments, the determining unit 1404 may be configured to determine, based on one or more parameters related to at least one of the configured power control loops associated with the first closed loop, whether the one or more conditions are satisfied.

[0297] As another example, the determining unit 1404 may be configured to determine whether the apparatus 1400 is power limited based on whether one or more conditions are satisfied. As another example, the determining unit 1404 may be configured to accumulate received TPC commands in response to determining that the apparatus 1400 is not power limited.

[0298] As another example, the determining unit 1404 may be configured to determine whether to accumulate the received TPC command in response to determining that the device 1400 is power limited. In some embodiments, determining whether the device 1400 is power limited may result in determining that the device 1400 is maximum power limited. In this scenario, the determining unit 1404 may be configured to determine whether to accumulate the received TPC command by determining whether the received TPC command is positive or negative, and perform one of the following operations: in response to determining that the received TPC command is positive, avoid accumulating the received TPC command; and in response to determining that the received TPC command is negative, accumulate the received TPC command. In some embodiments, determining whether the device 1400 is power limited may result in determining that the device 1400 is minimum power limited. In this scenario, the determination unit 1404 can be configured to determine whether to accumulate the received TPC command by determining whether the received TPC command is positive or negative, and perform one of the following operations: in response to determining that the received TPC command is negative, avoid accumulating the received TPC command; and in response to determining that the received TPC command is positive, accumulate the received TPC command.

[0299] As another example, the determining unit 1404 may be configured to determine whether a power control loop in a plurality of power control loops is classified as power limited. In some embodiments, the determining unit 1404 may be configured to determine whether a power control loop in a plurality of power control loops is classified as power limited based on a non-virtual output power. In some embodiments, the determining unit 1404 may be configured to determine whether a power control loop in a plurality of power control loops is classified as power limited based on a virtual output power. In some embodiments, the determining unit 1404 may be configured to determine whether a power control loop in a plurality of power control loops is classified as power limited based on a PUCCH transmit power. In some embodiments, the determining unit 1404 may be configured to determine whether a power control loop in a plurality of power control loops is classified as power limited not based on a PUCCH transmit power.

[0300] The determining unit 1404 may include or be included in one or more processors, such as the one or more processors described above. Figure 1 The determining unit 1404 may include analog and / or digital circuits configured to perform any of the functions of the determining unit 1404 and / or the processing circuit 120 described above. In some embodiments, the functions of the determining unit 1404 may be performed in one or more different units.

[0301] The communication unit 1406 may be configured to perform the transmission functions of the apparatus 1400. For example, the communication unit 1406 may be configured to forward user data to a host computer via transmission to a network node (eg, a base station).

[0302] The communication unit 1406 may include a transmitter and / or a transceiver, such as those described above with respect to Figure 1 1404. The communication unit 1406 may include circuits configured to send messages and / or signals (e.g., wirelessly or by wire). In certain embodiments, the communication unit 1406 may receive messages and / or signals from the determination unit 1404 or any other unit of the device 1400 for transmission. In some embodiments, the functions of the communication unit 1404 may be performed in one or more different units.

[0303] The term "unit" may have a traditional meaning in the field of electronic devices, electrical equipment and / or electronic equipment, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logical solid-state and / or discrete devices, computer programs or instructions for performing corresponding tasks, processes, calculations, output and / or display functions, etc., such as those described herein.

[0304] Certain example embodiments contemplated by the present disclosure are described below. Note that the embodiments listed below are for example purposes only, and the present disclosure is not limited to the example embodiments listed below.

[0305] Group A Embodiment

[0306] 1. A method performed by a wireless device for determining whether the wireless device is power limited, the method comprising:

[0307] - receiving, from a network node, a transmit power control (TPC) command for at least one of a plurality of power control loops configured at the wireless device;

[0308] - obtaining one or more parameters associated with one or more of a plurality of power control loops configured at the wireless device;

[0309] - based on the one or more parameters, determining whether one or more conditions are satisfied, the one or more conditions being related to power control at the wireless device; and

[0310] -Determining whether the wireless device is power limited based on whether one or more conditions are met.

[0311] 2. The method according to embodiment 1, further comprising:

[0312] - In response to determining that the wireless device is not power limited, accumulating the received TPC commands.

[0313] 3. The method according to any one of embodiments 1 or 2, further comprising:

[0314] - In response to determining that the wireless device is power limited, determining whether to accumulate received TPC commands.

[0315] 4. The method of embodiment 3, wherein:

[0316] - Determining that the wireless device has a maximum power limit; and

[0317] -Determining whether to accumulate the received TPC command comprises:

[0318] i. Determine whether the received TPC command is positive or negative; and

[0319] ii. Do one of the following:

[0320] 1. When determining that the received TPC command is positive, avoid accumulating the received TPC command; and

[0321] 2. When it is determined that the received TPC command is negative, accumulate the received TPC command.

[0322] 5. The method of any one of embodiments 3-4, wherein:

[0323] -determine the minimum power limit for wireless devices; and

[0324] -Determining whether to accumulate the received TPC command comprises:

[0325] i. Determine whether the received TPC command is positive or negative; and

[0326] ii. Do one of the following:

[0327] 1. upon determining that the received TPC command is negative, avoiding accumulating the received TPC command; and

[0328] 2. When it is determined that the received TPC command is positive, accumulate the received TPC command.

[0329] 6. The method of any one of embodiments 1-5, wherein:

[0330] - the wireless device is configured with two power control loops, each configured power control loop being associated with a different closed loop;

[0331] - the method further comprises: receiving an indication (k) indicating that the received TPC command is applicable to a first power control loop of the two configured power control loops; and

[0332] - wherein determining whether one or more conditions are met is based on one or more parameters related to the first power control loop.

[0333] 7. The method of embodiment 6, wherein the received TPC command is received via an uplink grant.

[0334] 8. The method of any one of embodiments 6-7, wherein the received TPC command is received via one of DCI formats 0, 1, 2, and 4.

[0335] 9. The method of any one of embodiments 6-8, wherein k:

[0336] - is received implicitly; or

[0337] - is explicitly received.

[0338] 10. The method of any one of embodiments 1-9, wherein:

[0339] - the wireless device is configured with at least three power control loops, each power control loop being associated with one of two possible closed loops, such that at least two of the three configured power control loops are associated with the same closed loop;

[0340] - The method further comprises: receiving a closed loop index (1) indicating that the received TPC command is applicable to all configured power control loops associated with a first closed loop, wherein the first closed loop is one of the two possible closed loops; and

[0341] - wherein whether one or more conditions are met is determined based on one or more parameters related to at least one of the configured power control loops associated with the first closed loop.

[0342] 11. The method of embodiment 10, wherein the received TPC command is received as part of one or more TPC commands sent to a group of wireless devices.

[0343] 12. The method of any one of embodiments 10-11, wherein the received TPC command is received via one of DCI formats 3 and 3A.

[0344] 13. A method according to any one of embodiments 10-12, wherein one or more conditions are a function of a closed-loop index (l).

[0345] 14. The method of any one of embodiments 10-13, wherein one or more conditions include a function that depends on more than one power control loop.

[0346] 15. The method of any one of embodiments 10-14, wherein the one or more conditions include the condition that all power control loops associated with the received closed loop index (l) must be considered as power limited in order to determine that the wireless device is power limited.

[0347] 16. A method according to any one of embodiments 10-14, wherein the one or more conditions include the following condition: at least one power control loop associated with the received closed loop index (l) must be considered as power limited in order to determine that the wireless device is power limited.

[0348] 17. The method of any one of embodiments 10-14, wherein the one or more conditions include the condition that all power control loops must be considered power limited in order to determine that the wireless device is power limited.

[0349] 18. The method of any one of embodiments 10-14, wherein the one or more conditions include the condition that at least one power control loop must be considered power limited in order to determine that the wireless device is power limited.

[0350] 19. The method of any one of embodiments 1-18, further comprising:

[0351] -Determining whether a power control loop among a plurality of power control loops is classified as power limited.

[0352] 20. The method of embodiment 19, wherein determining whether a power control loop among the plurality of power control loops is classified as power limited is based on the non-virtual output power.

[0353] 21. The method of embodiment 19, wherein determining whether a power control loop among the plurality of power control loops is classified as power limited is based on the virtual output power.

[0354] 22. The method of any one of embodiments 19-21, wherein determining whether a power control loop among the plurality of power control loops is classified as power limited is based on PUCCH transmit power.

[0355] 23. The method of any one of embodiments 19-21, wherein determining whether a power control loop among the plurality of power control loops is classified as power limited is not based on PUCCH transmit power.

[0356] 24. The method of any one of embodiments 1-23, wherein the plurality of power control loops include one or more of:

[0357] - One or more PUCCH power control loops;

[0358] - one or more SRS power control loops; and

[0359] - One or more PUSCH power control loops.

[0360] 25. The method of any one of embodiments 1-24, wherein power limiting includes one or more of the following:

[0361] - Maximum power limited; and

[0362] -Minimum power limited.

[0363] 26. The method of any one of embodiments 1-25, further comprising:

[0364] - provide user data; and

[0365] - Forwarding user data to a host computer via transmission to a network node.

[0366] Group B Example

[0367] 27. A wireless device for determining whether the wireless device is power limited, the wireless device comprising:

[0368] - a processing circuit configured to perform any of the steps of any of the embodiments of Group A; and

[0369] - A power circuit configured to supply power to the wireless device.

[0370] 28. A wireless device for determining whether a wireless device (UE) is power limited, the UE comprising:

[0371] - an antenna configured to send and receive wireless signals;

[0372] - a radio front end circuit connected to the antenna and the processing circuit and configured to condition signals transmitted between the antenna and the processing circuit;

[0373] - a processing circuit configured to perform any of the steps of any of the embodiments of Group A;

[0374] - an input interface connected to the processing circuitry and configured to allow information to be input into the UE for processing by the processing circuitry;

[0375] - an output interface connected to the processing circuit and configured to output information that has been processed by the processing circuit from the UE; and

[0376] - A battery connected to the processing circuit and configured to supply power to the UE.

[0377] 29. A communication system comprising a host computer, the host computer comprising:

[0378] - processing circuitry configured to provide user data; and

[0379] - a communication interface configured to forward user data to a cellular network for transmission to a wireless device (UE),

[0380] - wherein the cellular network comprises a network node having a radio interface and a processing circuit, the processing circuit of the network node being configured to perform any of the above steps.

[0381] 30. The communication system according to embodiment 29 further comprises a network node.

[0382] 31. The communication system according to any one of embodiments 29-30 further includes a UE, wherein the UE is configured to communicate with a network node.

[0383] 32. The communication system of any one of embodiments 29-31, wherein:

[0384] - the processing circuitry of the host computer is configured to execute a host application to provide user data; and

[0385] - The UE comprises a processing circuit configured to execute a client application associated with a host application.

[0386] 33. A method implemented in a communication system including a host computer, a network node and a wireless device (UE), the method comprising:

[0387] - at the host computer, providing user data; and

[0388] - at a host computer, initiating a transmission carrying user data to the UE via a cellular network comprising a network node, wherein the network node performs any of the steps above.

[0389] 34. The method of embodiment 33 further comprises sending user data at a network node.

[0390] 35. The method of any one of embodiments 33-34, wherein the user data is provided at the host computer by executing a host application, the method further comprising executing a client application associated with the host application at the UE.

[0391] 36. A wireless device (UE) configured to communicate with a network node, the UE comprising a radio interface and a processing circuit configured to perform any one of embodiments 1-35.

[0392] 37. A communication system comprising a host computer, the host computer comprising:

[0393] - processing circuitry configured to provide user data; and

[0394] - a communication interface configured to forward user data to a cellular network for transmission to a wireless device (UE),

[0395] - wherein the UE comprises a radio interface and a processing circuit, and the components of the UE are configured to perform any steps of any embodiment in Group A embodiments.

[0396] 38. The communication system of embodiment 37, wherein the cellular network further comprises a network node configured to communicate with the UE.

[0397] 39. The communication system of any one of embodiments 37-38, wherein:

[0398] - the processing circuitry of the host computer is configured to execute a host application to provide user data; and

[0399] - The processing circuitry of the UE is configured to execute a client application associated with the host application.

[0400] 40. A method implemented in a communication system including a host computer, a network node, and a wireless device (UE), the method comprising:

[0401] - at the host computer, providing user data; and

[0402] - At a host computer, initiating a transmission carrying user data to a UE via a cellular network including a network node, wherein the UE performs any steps of any of the embodiments in Group A.

[0403] 41. The method of embodiment 40 further comprises receiving user data at the UE from the network node.

[0404] 42. A communication system comprising a host computer, the host computer comprising:

[0405] - a communication interface configured to receive user data originating from a transmission from a wireless device (UE) to a network node,

[0406] - wherein the UE comprises a radio interface and a processing circuit, and the processing circuit of the UE is configured to perform any steps of any embodiment in Group A embodiments.

[0407] 43. The communication system according to embodiment 42 further includes a UE.

[0408] 44. The communication system according to any one of embodiments 42-43 further includes a network node, wherein the network node includes: a radio interface configured to communicate with the UE; and a communication interface configured to forward user data carried by the transmission from the UE to the network node to the host computer.

[0409] 45. The communication system of any one of embodiments 42-44, wherein:

[0410] - the processing circuitry of the host computer is configured to execute a host application; and

[0411] - The processing circuitry of the UE is configured to execute a client application associated with the host application, thereby providing user data.

[0412] 46. ​​The communication system of any one of embodiments 42-45, wherein:

[0413] - the processing circuitry of the host computer is configured to execute the host application to provide the requested data; and

[0414] - The processing circuitry of the UE is configured to execute a client application associated with the host application to provide user data in response to the request data.

[0415] 47. A method implemented in a communication system including a host computer, a network node, and a wireless device (UE), the method comprising:

[0416] - At a host computer, receiving user data sent to a network node from a UE, wherein the UE performs any steps of any of the embodiments in Group A.

[0417] 48. The method of embodiment 47 further comprises providing user data to the network node at the UE.

[0418] 49. The method of any one of embodiments 47-48, further comprising:

[0419] - executing a client application at the UE, thereby providing user data to be sent; and

[0420] -Executing a host application associated with the client application at a host computer.

[0421] 50. The method of any one of embodiments 47-49, further comprising:

[0422] - executing a client application at the UE; and

[0423] - receiving input data to the client application at the UE, the input data being provided at the host computer by executing a host application associated with the client application,

[0424] - wherein the user data to be sent is provided by the client application in response to the input data.

[0425] 51. A communication system comprising a host computer, the host computer comprising a communication interface, the communication interface being configured to receive user data originating from a transmission from a wireless device (UE) to a network node, wherein the network node comprises a radio interface and a processing circuit, the processing circuit of the network node being configured to perform any steps of any of embodiments 1-50.

[0426] 52. The communication system according to embodiment 51 further includes a network node.

[0427] 53. The communication system according to any one of embodiments 51-52 further includes a UE, wherein the UE is configured to communicate with a network node.

[0428] 54. The communication system of any one of embodiments 51-53, wherein:

[0429] - the processing circuitry of the host computer is configured to execute a host application;

[0430] - The UE is configured to execute a client application associated with a host application, thereby providing user data to be received by the host computer.

[0431] 55. A method implemented in a communication system including a host computer, a network node, and a wireless device (UE), the method comprising:

[0432] - receiving at a host computer from a network node user data originating from a transmission, the network node having received the transmission from a UE, wherein the UE performs any steps of any of the embodiments of Group A.

[0433] 56. The method of embodiment 55 further comprises receiving user data from the UE at the network node.

[0434] 57. The method of any one of embodiments 55-56, further comprising initiating, at the network node, transmission of the received user data to a host computer.

[0435] Any appropriate steps, methods, features, functions or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include a plurality of these functional units. These functional units may be implemented via a processing circuit, which may include one or more microprocessors or microcontrollers, and other digital hardware, which may include a digital signal processor (DSP), dedicated digital logic, etc. The processing circuit may be configured to execute program codes stored in a memory, which may include one or more types of memory, such as a read-only memory (ROM), a random access memory (RAM), a cache memory, a flash memory device, an optical storage device, etc. The program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols, and instructions for executing one or more technologies described herein. In some implementations, according to one or more embodiments of the present disclosure, a processing circuit may be used to cause a corresponding functional unit to perform a corresponding function.

[0436] Without departing from the scope of the present disclosure, the systems and devices described herein may be modified, added to, or omitted. The components of the systems and devices may be integrated or separated. In addition, the operations of the systems and devices may be performed by more, fewer, or other components. In addition, any suitable logic including software, hardware, and / or other logic may be used to perform the operations of the systems and devices. As used herein, "each" refers to each member of a set or each member of a subset of a set.

[0437] Without departing from the scope of the present disclosure, the methods described herein may be modified, added to, or omitted. The methods may include more, fewer, or other steps. In addition, the steps may be performed in any suitable order.

[0438] Although the present disclosure has been described according to certain embodiments, it will be apparent to those skilled in the art that the changes and substitutions of the embodiments will be apparent. Therefore, the above description of the embodiments does not limit the present disclosure. Other changes, substitutions and variations are possible without departing from the spirit and scope of the present disclosure as defined in the appended claims.

[0439] Abbreviations used in the preceding description include:

[0440] 1x RTT CDMA2000 1x Radio Transmission Technology

[0441] 3GPP Third Generation Partnership Project

[0442] 5G Fifth Generation

[0443] ABS Almost Blank Subframe

[0444] ARQ Automatic Repeat Request

[0445] AWGN Additive White Gaussian Noise

[0446] BCCH Broadcast Control Channel

[0447] BCH Broadcast Channel

[0448] CA Carrier Aggregation

[0449] CC Carrier Component

[0450] CCCH SDU Common Control Channel SDU

[0451] CDMA Code Division Multiple Access

[0452] CE Control Elements

[0453] CGI Cell Global Identifier

[0454] CIR Channel Impulse Response

[0455] CP Cyclic Prefix

[0456] CPICH Common Pilot Channel

[0457] CPICH Ec / No The CPICH received energy per chip divided by the power density in the band

[0458] CQI Channel Quality Information

[0459] CRC Cyclic Redundancy Check

[0460] C-RNTI Cell RNTI

[0461] CSI Channel State Information

[0462] DCCH Dedicated Control Channel

[0463] DCI Downlink Control Information

[0464] DL Downlink

[0465] DM Demodulation

[0466] DMRS Demodulation Reference Signal

[0467] DRX Discontinuous Reception

[0468] DTX Discontinuous Transmission

[0469] DTCH Dedicated Traffic Channel

[0470] DUT Device Under Test

[0471] E-CID Enhanced Cell ID (positioning method)

[0472] E-SMLC Evolved Service Mobile Location Center

[0473] ECGI Evolution CGI

[0474] eNB E-UTRANNode B

[0475] ePDCCH Enhanced Physical Downlink Control Channel

[0476] E-SMLC Evolved Service Mobile Location Center

[0477] E-UTRA Evolved UTRA

[0478] E-UTRAN Evolved UTRAN

[0479] FDD Frequency Division Duplex

[0480] FFS needs further study

[0481] GERAN GSM EDGE Radio Access Network

[0482] Base stations in gNB NR

[0483] GNSS Global Navigation Satellite System

[0484] GSM Global System for Mobile Communications

[0485] HARQ Hybrid Automatic Repeat Request

[0486] HO Handover

[0487] HSPA High Speed ​​Packet Access

[0488] HRPD High Rate Packet Data

[0489] LOS Line of Sight

[0490] LPP LTE Positioning Protocol

[0491] LTE Long Term Evolution

[0492] MAC Media Access Control

[0493] MBMS Multimedia Broadcast Multicast Service

[0494] MBSFN Multimedia Broadcast Multicast Service Single Frequency Network

[0495] MBSFN ABS MBSFN Almost Blank Subframe

[0496] MDT Minimized Drive Test

[0497] MIB Master Information Block

[0498] MME Mobility Management Entity

[0499] MSC Mobile Switching Center

[0500] NPDCCH Narrowband Physical Downlink Control Channel

[0501] NR New Radio

[0502] OCNG OFDMA Channel Noise Generator

[0503] OFDM Orthogonal Frequency Division Multiplexing

[0504] OFDMA Orthogonal Frequency Division Multiple Access

[0505] OSS Operation Support System

[0506] OTDOA Observed Time Difference of Arrival

[0507] O&M Operation and Maintenance

[0508] PBCH Physical Broadcast Channel

[0509] PC Power Control

[0510] P-CCPCH Primary Common Control Physical Channel

[0511] PCell Primary Cell

[0512] PCFICH Physical Control Format Indicator Channel

[0513] PDCCH Physical Downlink Control Channel

[0514] PDP Power Delay Profile

[0515] PDSCH Physical Downlink Shared Channel

[0516] PGW Packet Gateway

[0517] PHICH Physical Hybrid ARQ Indicator Channel

[0518] PLMN Public Land Mobile Network

[0519] PMI Precoder Matrix Indicator

[0520] PRACH Physical Random Access Channel

[0521] PRS Positioning Reference Signal

[0522] PSS Primary Synchronization Signal

[0523] PUCCH Physical Uplink Control Channel

[0524] PUSCH Physical Uplink Shared Channel

[0525] RACH Random Access Channel

[0526] QAM Quadrature Amplitude Modulation

[0527] RAN Radio Access Network

[0528] RAT Radio Access Technology

[0529] RLM Radio Link Management

[0530] RNC Radio Network Controller

[0531] RNTI Radio Network Temporary Identifier

[0532] RRC Radio Resource Control

[0533] RRM Radio Resource Management

[0534] RS reference signal

[0535] RSCP Received Signal Code Power

[0536] RSRP Reference Symbol Received Power or Reference Signal Received Power

[0537] RSRQ Reference Signal Received Quality or Reference Symbol Received Quality

[0538] RSSI Received Signal Strength Indicator

[0539] RSTD Reference Signal Time Difference

[0540] SCH Synchronization Channel

[0541] SCell Secondary Cell

[0542] SDU Service Data Unit

[0543] SFN System Frame Number

[0544] SGW Service Gateway

[0545] SI System Information

[0546] SIB System Information Block

[0547] SNR Signal to Noise Ratio

[0548] SON Self-Optimizing Network

[0549] SRS Sounding Reference Signal

[0550] SS Sync Signal

[0551] SSS Auxiliary Sync Signal

[0552] TDD Time Division Duplex

[0553] TDOA Time Difference of Arrival

[0554] TOA Time of Arrival

[0555] TPC Transmit Power Control

[0556] TRP Transmission Reception Point

[0557] TSS third synchronization signal

[0558] TTI Transmit Time Interval

[0559] UE User Equipment

[0560] UL Uplink

[0561] UMTS Universal Mobile Telecommunications System

[0562] USIM Universal Subscriber Identity Module

[0563] UTDOA Uplink Time Difference of Arrival

[0564] UTRA Universal Terrestrial Radio Access

[0565] UTRAN Universal Terrestrial Radio Access Network

[0566] WCDMA Wideband CDMA

[0567] WLAN Wide Area Network

Claims

1. A method performed by a wireless device (110, 500, 791, 792) for determining whether the wireless device is power limited, the method comprising: receiving (1301) a transmit power control (TPC) command for one or more power control loops of a plurality of power control loops configured at the wireless device from a network node (160, 712), wherein the plurality of power control loops configured at the wireless device comprises at least three power control loops, each power control loop being associated with one of two closed loops, such that at least two of the three configured power control loops are associated with a first of the two closed loops; obtaining (1302) an indication of the one or more power control loops of the plurality of power control loops to which the received TPC command applies, wherein the indication comprises a closed loop index indicating that the received TPC command applies to all configured power control loops associated with the first of the two closed loops; determining (1303) whether one or more conditions related to power control at the wireless device are satisfied based on one or more parameters related to at least one of the configured power control loops associated with the first closed loop; and Based on whether the one or more conditions are satisfied, it is determined (1304) whether the wireless device is power limited.

2. The method according to claim 1, further comprising: In response to determining that the wireless device is power limited, a determination is made whether to accumulate the received TPC commands.

3. The method according to claim 1, further comprising: In response to determining that the wireless device is not power limited, the received TPC commands are accumulated.

4. The method according to claim 2, wherein: Determining whether the wireless device is power limited results in determining that the wireless device is maximum power limited; as well as Determining whether to accumulate the received TPC command includes: determining whether the received TPC command is positive or negative; and Do one of the following: In response to determining that the received TPC command is positive, refraining from accumulating the received TPC command; and In response to determining that the received TPC command is negative, accumulating the received TPC command, or Determining whether the wireless device is power limited results in determining that the wireless device is minimum power limited; and Determining whether to accumulate the received TPC command comprises: determining whether the received TPC command is positive or negative; and Do one of the following: In response to determining that the received TPC command is negative, refraining from accumulating the received TPC command; and In response to determining that the received TPC command is positive, the received TPC command is accumulated.

5. The method according to claim 1, wherein: The received TPC command is received via an uplink grant.

6. The method according to claim 1, wherein: The received TPC command is received as part of one or more TPC commands sent to a group of wireless devices, and / or The received TPC command is received in a physical downlink control channel (PDCCH) downlink control information (DCI) without an associated uplink grant.

7. The method according to claim 1, wherein: The one or more conditions include a condition that at least one power control loop associated with the received closed loop index must be considered power limited in order to determine that the wireless device is power limited.

8. The method according to claim 1, wherein: The one or more conditions include a condition that at least one power control loop must be considered power limited in order to determine that the wireless device is power limited.

9. The method according to any one of claims 1 to 8, further comprising: A determination is made as to whether a power control loop of the plurality of power control loops is classified as power limited.

10. The method according to any one of claims 1 to 8, wherein: The plurality of power control loops include one or more of the following: One or more PUCCH power control loops; one or more sounding reference signal (SRS) power control loops; and One or more Physical Uplink Shared Channel (PUSCH) power control loops.

11. The method according to any one of claims 1 to 8, wherein: Power limitation includes one or more of the following: Maximum power is limited; and Minimum power limited.

12. A wireless device (110, 500, 791, 792), configured to determine whether the wireless device is power limited, the wireless device comprising: Receiver; transmitter; as well as A processing circuit (120) coupled to the receiver and the transmitter, the processing circuit being configured to: receiving (1301) a transmit power control (TPC) command for one or more power control loops of a plurality of power control loops configured at the wireless device from a network node (160, 712), wherein the plurality of power control loops configured at the wireless device comprises at least three power control loops, each power control loop being associated with one of two closed loops, such that at least two of the three configured power control loops are associated with a first of the two closed loops; obtaining (1302) an indication of the one or more power control loops of the plurality of power control loops to which the received TPC command applies, wherein the indication comprises a closed loop index indicating that the received TPC command applies to all configured power control loops associated with the first of the two closed loops; determining (1303) whether one or more conditions related to power control at the wireless device are satisfied based on one or more parameters related to at least one of the configured power control loops associated with the first closed loop; and Based on whether the one or more conditions are satisfied, it is determined (1304) whether the wireless device is power limited.

13. The wireless device of claim 12, wherein: The processing circuit is configured to perform the steps of the method according to any one of claims 2-11.

Images