HK1261762A1

HK1261762A1 - Methods and apparatuses for power control in a wireless communication system

Info

Publication number: HK1261762A1
Application number: HK19121660.5A
Authority: HK
Inventors: Jinhua Liu; Rui Fan; Hai Wang
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2017-01-26
Filing date: 2018-01-26
Publication date: 2020-01-03

Description

Method and apparatus for power control in a wireless communication system

Technical Field

Non-limiting and example embodiments of the present disclosure relate generally to the field of wireless communication technology and, in particular, relate to a method, apparatus and computer program for power control in a wireless communication network.

Background

This section introduces aspects that may facilitate a better understanding of the disclosure. Accordingly, the description in this section is to be read in this light, and not as an admission as to what is prior art or what is not prior art.

A fifth generation (5G) network such as NR (new radio) should provide different applications or services by using the same physical infrastructure. Fig. 1 schematically illustrates an example 5G network 100. As shown in fig. 1, network 100 may support multiple types of mobile network services, such as services 120-1, 120-2, 120-3, via a common Radio Access Network (RAN) 110. These different types of mobile network services 120-1, 120-2, 120-3 are independent of each other at a logical level, but may be implemented in the same physical infrastructure. Depending on different quality of service (QoS) requirements, these mobile network services can be divided into three main types: ultra-reliable and low latency communication (URLLC)120-1, enhanced mobile broadband (eMBB)120-2, and large-scale machine type communication (mMTC) 120-3.

URLLC 120-1, for example, used in automatic drive/automatic control, has strict QoS requirements, especially in terms of latency and reliability. However, such URLLC services also typically have relatively low data rates and possibly sparse data transmissions.

eMBB 120-2, for example, used in HD video services, requires a high data rate. The delay may be strict, but is generally less strict than URLLC.

Mtc 120-3, for example, used in smart farming, typically supports high connection density and requires long battery life, but does not require low latency or high data rates, often with small infrequent packets.

In order to meet QoS and delay requirements of different services, the uplink transmission power of the terminal device should be properly controlled.

Disclosure of Invention

Therefore, in order to meet different QoS requirements of different types of services, it is very important to provide a power control solution for uplink transmission in a wireless communication network.

To address at least a portion of the above issues, methods, apparatuses, and computer programs are provided in the present disclosure. It will be appreciated that embodiments of the present disclosure are not limited to a 5G scenario, but may be applied more broadly to any application scenario where similar issues exist.

Various embodiments of the present disclosure are generally directed to methods, apparatuses, and computer programs for power control. Other features and advantages of embodiments of the present disclosure will also be understood from the following description of specific embodiments, when read in conjunction with the accompanying drawings, which illustrate, by way of example, the principles of embodiments of the disclosure.

According to a first aspect of the present disclosure, a method implemented at a terminal device is provided. The method comprises the following steps: performing power control for at least a first type of traffic based on a first parameter configuration of a first power control loop; and performing power control for at least a second type of traffic based on a second parameter configuration of the second power control loop. The first parameter configuration of the first power control loop comprises at least one parameter different from the second parameter configuration of the second power control loop.

In accordance with one or more embodiments of the first aspect of the present disclosure, the method may further comprise receiving the first parameter configuration of the first power control loop and the second parameter configuration of the second power control loop from a network device via at least one radio resource control, RRC, signaling.

According to one or more embodiments of the first aspect of the present disclosure, the method may further include receiving downlink control information, DCI, carried in a physical downlink control channel, PDCCH, from a network device, wherein the DCI includes a first power control command for the first power control loop or a second power control command for the second power control loop. The first power control command or the second power control command may be applied to a corresponding power control loop to perform the power control for the respective type of service.

According to one or more embodiments of the first aspect of the present disclosure, the method may further comprise determining which power control loop the received DCI is associated with. In one embodiment, this may be determined based on the length of the time interval in which the DCI is used for scheduling. In another embodiment, this may be determined based on a search space of the PDCCH carrying the DCI. In yet another embodiment, this may be determined based on information in a field of the received DCI. In yet another embodiment, this may be determined based on the format of the received DCI.

In accordance with one or more embodiments of the first aspect of the present disclosure, the method may include receiving, from a network device, via at least one RRC signaling, the first parameter configuration of the first power control loop and a relative parameter configuration indicating a difference between the first parameter configuration of the first power control loop and the second parameter configuration of the second power control loop.

According to one or more embodiments of the first aspect of the present disclosure, the method may further include receiving DCI carried in the PDCCH from the network device, wherein the DCI includes a power control command of the first power control loop. The power control commands may be applied to the first or second power control loops depending on which power control loop the received DCI is associated with.

In accordance with one or more embodiments of the first aspect of the present disclosure, the method may further include determining the second power configuration based on the first parameter configuration and the relative parameter configuration in response to determining that the received DCI is associated with the second power control loop.

According to one or more embodiments of the first aspect of the present disclosure, the first type of traffic may comprise enhanced mobile broadband, eMBB, traffic and the second type of traffic may comprise ultra-reliable and low latency communication, URLLC, traffic.

According to a second aspect of the disclosure, a method implemented at a network device is provided. The method comprises the following steps: performing, for a terminal device, power control for at least a first type of traffic based on a first parameter configuration of a first power control loop; and for the terminal device, performing power control for at least a second type of traffic based on a second parameter configuration of a second power control loop, wherein the first parameter configuration of the first power control loop comprises at least one parameter different from the second parameter configuration of the second power control loop.

According to one or more embodiments of the second aspect of the disclosure, the method may further comprise sending the first parameter configuration of the first power control loop and the second parameter configuration of the second power control loop to the terminal device via at least one RRC signaling.

According to one or more embodiments of the second aspect of the present disclosure, the method may further comprise receiving a physical uplink shared channel, PUSCH, from the terminal device; determining a first power control command for the first power control loop or a second parameter configuration for the second power control loop based on the received PUSCH.

According to one or more embodiments of the second aspect of the present disclosure, it may be further determined with which power control loop the PUSCH is associated. In one embodiment, this may be determined based on the length of the time interval in which the PUSCH is transmitted. In another embodiment, this may be determined based on a timing relationship between an uplink grant and the PUSCH. In yet another embodiment, this may be determined based on a logical channel identifier in a media access control, MAC, header carried in the PUSCH.

According to one or more embodiments of the second aspect of the present disclosure, the method may further comprise transmitting DCI to the terminal device in the PDCCH, wherein the DCI comprises the first power control command of the first power control loop or the second power control command of the second power control loop depending on which power control loop the DCI is associated with.

According to one or more embodiments of the second aspect of the present disclosure, the method may further comprise sending, to a terminal device, via at least one RRC signaling, a first parameter configuration of the first power control loop and a relative parameter configuration indicating a difference between the first parameter configuration of the first power control loop and the second parameter configuration of the second power control loop.

According to one or more embodiments of the second aspect of the present disclosure, the method may further comprise receiving a PUSCH from the terminal device; determining a power control command for the first power control loop based on the received PUSCH.

According to one or more embodiments of the second aspect of the present disclosure, the method may further include transmitting DCI carried in a PDCCH to the terminal device, wherein the DCI includes the power control command of the first power control loop.

According to one or more embodiments of the second aspect of the present disclosure, the first type of traffic may include eMBB traffic and the second type of traffic may include URLLC traffic.

According to a third aspect of the present disclosure, a terminal device is provided. The terminal device includes: a first power control unit configured to perform power control for at least a first type of traffic based on a first parameter configuration of a first power control loop; a second power control unit configured to perform power control for at least a second type of traffic based on a second parameter configuration of a second power control loop, wherein the first parameter configuration of the first power control loop comprises at least one parameter different from the second parameter configuration of the second power control loop.

According to a fourth aspect of the present disclosure, a network device is provided. The network device includes: a first power control unit configured to perform power control for at least a first type of traffic for a terminal device based on a first parameter configuration of a first power control loop; a second power control unit configured to perform, for the terminal device, power control for at least a second type of traffic based on a second parameter configuration of a second power control loop, wherein the first parameter configuration of the first power control loop comprises at least one parameter different from the second parameter configuration of the second power control loop.

According to a fifth aspect of the present disclosure, a terminal device is provided. The terminal device includes a processor and a non-transitory machine-readable storage medium. The non-transitory machine-readable storage medium contains instructions that, when executed on the processor, cause the terminal device to perform a method according to an embodiment of the first aspect of the disclosure.

According to a sixth aspect of the present disclosure, a network device is provided. The network device includes a processor and a non-transitory machine-readable storage medium. The non-transitory machine-readable storage medium contains instructions that, when executed on the processor, cause the network device to perform a method according to an embodiment of the second aspect of the disclosure.

According to a seventh aspect of the present disclosure, there is provided a computer program comprising instructions which, when executed on one or more processors, cause the one or more processors to perform the method of one embodiment of the first aspect of the present disclosure.

According to an eighth aspect of the present disclosure there is provided a computer program comprising instructions which, when executed on one or more processors, cause the one or more processors to perform the method of one embodiment of the second aspect of the present disclosure.

Drawings

The above and other aspects, features and advantages of various embodiments of the present disclosure will become more fully apparent from the following detailed description, by way of example, with reference to the accompanying drawings in which like reference numerals or letters are used to designate like or equivalent elements. The accompanying drawings, which are included to provide a further understanding of embodiments of the disclosure and are not necessarily drawn to scale, are illustrated in the accompanying drawings:

fig. 1 illustrates an example wireless communication network 100 in which embodiments of the present disclosure may be implemented;

fig. 2 shows a flow diagram of a method 200 implemented at a terminal device in accordance with one or more embodiments of the present disclosure;

fig. 3 shows a flow diagram of a method 300 implemented at a network device in accordance with one or more embodiments of the present disclosure;

fig. 4 shows a schematic block diagram of an apparatus 400 implemented as/in a terminal device in accordance with one or more embodiments of the present disclosure;

fig. 5 shows a schematic block diagram of an apparatus 500 implemented as/in a network device in accordance with one or more embodiments of the present disclosure; and

fig. 6 shows a simplified block diagram of an apparatus 610, which may be embodied as/in a terminal device, and an apparatus 620, which may be embodied as/in a network device.

Detailed Description

Hereinafter, the principle and spirit of the present disclosure will be described with reference to illustrative embodiments. It is understood that all of these examples are given solely for the purpose of better understanding and further enabling those of ordinary skill in the art to practice the present disclosure, and are not intended to limit the scope of the present disclosure. For instance, features illustrated or described as part of one embodiment, can be used with another embodiment to yield a still further embodiment. In the interest of clarity, not all features of an actual implementation are described in this specification.

References in the specification to "one embodiment," "an embodiment," "one example embodiment," etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

It will be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a "first" element may also be referred to as a "second" element, and likewise, a "second" element may also be referred to as a "first" element, without departing from the scope of example embodiments. As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises," "comprising," "has," "having," "includes" and/or "including," when used herein, specify the presence of stated features, elements, and/or components, but do not preclude the presence or addition of one or more other features, elements, components, and/or groups thereof.

In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

As used herein, the term "wireless communication network" refers to a network that conforms to any suitable wireless communication standard, including, for example, LTE-Advanced (LTE-a), LTE, Wideband Code Division Multiple Access (WCDMA), High Speed Packet Access (HSPA), and the like. Further, communication between network devices in a wireless communication network may be performed according to any generation of suitable communication protocol, including, but not limited to, first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G) communication protocols, and/or any other protocol now known or later developed in the future.

As used herein, the term "network device" refers to a device in a wireless communication network via which a terminal device accesses the network and receives services therefrom. A network device may refer to a Base Station (BS) or an Access Point (AP), such as a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), a Remote Radio Unit (RRU), a Radio Head (RH), a Remote Radio Head (RRH), a relay, a low power node (e.g., femto, pico, etc.), depending on the terminology and technology applied.

Still further examples of network devices include multi-standard wireless (MSR) wireless devices (e.g., MSR BSs), network controllers (e.g., Radio Network Controllers (RNCs) or Base Station Controllers (BSCs)), Base Transceiver Stations (BTSs), transmission points, transmission nodes, multi-cell/Multicast Coordination Entities (MCEs), core network nodes (e.g., MSCs, MMEs), O & M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. More generally, however, a network device may represent any suitable device (or group of devices) that is capable of, configured to, arranged to, and/or operable to enable and/or provide access by a terminal device to a wireless communication network, or to provide some service to a terminal device that has access to a wireless communication network.

The term "terminal device" refers to any terminal device that can access a wireless communication network and receive services therefrom. By way of example, and not limitation, a terminal device may be referred to as a User Equipment (UE), a Subscriber Station (SS), a portable subscriber station, a Mobile Station (MS), or an Access Terminal (AT). The terminal devices may include, but are not limited to, mobile phones, cellular phones, smart phones, tablet computers, wearable devices, Personal Digital Assistants (PDAs), portable computers, image capture terminal devices (e.g., digital cameras), gaming terminal devices, music storage and playback devices, wearable terminal devices, vehicle mounted wireless terminal devices, and the like. In the following description, the terms "terminal device", "terminal", "user equipment" and "UE" may be used interchangeably.

The terminal device may support device-to-device (D2D) communication, for example by implementing the 3GPP standard for sidelink communication, and may be referred to in this case as a D2D communication device.

As yet another specific example, in an internet of things (IOT) scenario, the end device may represent the following machine or other device: which performs monitoring and/or measurement and transmits the results of such monitoring and/or measurement to another terminal device and/or network device. In this case, the terminal device may be a machine-to-machine (M2M) device, which may be referred to as a Machine Type Communication (MTC) device in the 3GPP context. As one particular example, the terminal device may be a UE implementing the 3GPP narrowband internet of things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices (e.g. power meters), industrial machines, or household or personal devices (e.g. refrigerators, televisions), personal wearable devices (e.g. watches), etc. In other scenarios, the terminal device may represent the following vehicle or other device: which is capable of monitoring and/or reporting its operational status or other functions associated with its operation.

As mentioned above, 5G networks such as NR are designed to support different types of services that have quite different performance requirements, e.g. QoS performance. For example, for the eMBB service, the QoS requirement is moderate, typically a 10% block error rate BLER, which is good enough for the first transmission. However, URLLC has very stringent requirements on delay and reliability. Only a 1% BLER or even lower target may be set for URLLC services. For the above reasons, the uplink transmission power required for URLLC and eMBB services may be quite different.

In prior art, such as long term evolution, LTE, networks, power control is typically implemented using one power control loop between the terminal device and the network device. For dynamic TDD, the terminal device and the network device may run two power control loops. However, in this case, two power control loops in the dynamic TDD system are distinguished according to the type of the subframe. It can be seen that in a dynamic TDD system, power control is performed using two power control loops without considering different types of uplink services.

In LTE networks, physical uplink shared channel, PUSCH, and physical uplink shared channel, PUCCH, power control needs to be performed between a terminal device and one or more network devices. In LTE, uplink power control is used to compensate for channel path loss variations. When there is high attenuation between the terminal device and the network device, the terminal device may increase its transmit power in order to maintain the receive power at the network device at a desired level. Otherwise, the terminal device may reduce the transmit power in order to reduce interference to other terminal devices.

The transmit power of different types of channels follows different power control rules. For example, if the terminal device transmits PUSCH without simultaneous PUCCH for serving cell c, the transmission power P for PUSCH transmission in subframe i of serving cell c_PUSCH,c(i) Given by equation 1):

wherein:

●P_CMAX,cis the configured UE transmit power and is,

●M_PUSCH,c(i) bandwidth, P, of PUSCH resource allocation expressed in number of resource blocks valid for subframe i and serving cell c_{O_PUSCH,c}(j) Is a parameter consisting of the sum of the following components: component P provided from higher layer_{O_NOMINAL_PUSCH,c}(j) (for j ═ 0 and 1); and component P provided by the higher layer of serving cell c_{O_UE_PUSCH,c}(j) (for j ═ 0 and 1),

●α_c∈ {0,0.4,0.5,0.6,0.7,0.8,0.9,1} is a 3-bit parameter provided by the higher layer of serving cell c,

●PL_cis a downlink path loss estimate calculated in terminal equipment of serving cell c, in dB

●Δ_TF,cIs the dynamic offset given by the higher layers,

●f_c(i) is a function representing the accumulation of Transmitter Power Control (TPC) commands.

○ if Accumulation is enabled based on the parameter Accumulation-enabled provided by higher layers, or if TPC commands_PUSCH,cIncluded in the PDCCH/EPDCCH with DCI Format 0 of serving cell C, where the Cyclic Redundancy Check (CRC) is scrambled by the temporary C-RNTI, then f_c(i)＝_PUSCH,c(i-K_PUSCH)。

○ if Accumulation is not enabled for serving cell c based on the parameter Accumulation-enabled provided by higher layers, f_c(i)＝_PUSCH,c(i-K_PUSCH)。

●_PUSCH,cIs a correction value (also referred to as a TPC command) and is included in the PDCCH/EPDCCH with DCI format 0/4 of serving cell c or is jointly encoded with other TPC commands in the PDCCH with DCI format 3/3a, the CRC check bits of which are scrambled with TPC-PUSCH-RNTI.

●, j is 0 for PUSCH (re) transmissions corresponding to semi-persistent grants, 1 for PUSCH (re) transmissions corresponding to dynamic scheduling grants, and 2 for PUSCH (re) transmissions corresponding to random access response grants.

However, as mentioned above, power control in LTE hardly meets the different performance requirements from URLLC and eMBB services at the same time. For example, using the same Transport Format (TF), URLLC services will require higher transmission power than eMBB services in order to achieve a lower BLER target and/or shorter transmission delay. When a terminal device has both eMBB and URLLC services provided by one operator and a single closed loop power control loop is applied to both eMBB and URLLC services, this will compromise URLLC performance when targeting a low quality target optimized for eMBB (e.g. a target for SINR, SIR, SNR, or received power level) and compromise URLLC performance when targeting a high quality target optimized for URLLC.

According to an embodiment of the present disclosure, the proposed power control solution is to run at least two different power control loops between the terminal device and the network device in order to meet different performance requirements of different services (e.g. URLLC and eMBB). The power control loops may be independent of each other or coupled to each other to enable power requirements of different types of services to be met.

Various embodiments of the present disclosure are described with reference to fig. 2-6. For purposes of brevity and clarity, the embodiments described below employ only two power control loops for different types of services. Those skilled in the art will appreciate that more than two power control loops may be run between the terminal device and the network device without departing from the spirit of the present disclosure.

Fig. 2 shows a flow diagram of a method 200 implemented at a terminal device in accordance with one or more embodiments of the present disclosure.

As shown in fig. 2, in step S210, the terminal device performs power control for at least a first type of traffic based on a first parameter configuration of a first power control loop. In step S220, the terminal device performs power control for at least a second type of traffic based on a second parameter configuration of the second power control loop. The first type of traffic may have different performance requirements (e.g., QoS requirements) than the second type of traffic. To meet different performance requirements, the first parameter configuration of the first power control loop includes at least one parameter that is different from the second parameter configuration of the second power control loop. The parameter configuration may be designed to include, for example, parameters for a semi-static configuration of power control, such as open loop operating point P0, path loss compensation factor a, power control step size, and/or other parameters as described in equation 1). It should be noted that the term "traffic" herein refers not only to the communication of data information, but also to the communication of control information and reference information. The data information communication may include communication on a data channel (e.g., PUSCH); the control information communication may include communication on a control channel (e.g., PDCCH); and the reference information communication may comprise transmission of sounding reference signaling, SRS.

According to one or more embodiments of the present disclosure, the first type of traffic may be eMBB traffic and the second type of traffic may be URLLC traffic. In 5G networks, because mtc traffic is delay tolerant, its reliability can be guaranteed by automatic repeat request mechanisms (e.g., medium access control automatic repeat request, MAC, ARQ, and radio link control automatic repeat request, RLC, ARQ). In one embodiment, mtc traffic may share a first power control loop with eMBB traffic. That is, in accordance with one or more embodiments of the present disclosure, one power control loop may serve several types of services provided that the performance requirements of those services can be met within the power control loop.

In one or more embodiments of the present disclosure, the first power control loop may operate between the terminal device and the network independently of the second power control loop. Thus, the terminal device may receive separate parameter configurations for the first and second power control loops and may also independently inform the terminal device of dynamic power control related parameters for the first and second power control loops from the network device.

According to some embodiments in which the first power control loop operates independently of the second power control loop, the terminal device may receive, from the network device, a first parameter configuration of the first power control loop and a second parameter configuration of the second power control loop via at least one radio resource control, RRC, signaling at step S230. The terminal device can know which power control loop the RRC signaling is associated with by means of information carried in the signaling.

According to certain embodiments of the present disclosure, the dynamic power control related parameter may be a power control command, e.g., a TPC command, included in the downlink control information. In step S240, the terminal device may receive DCI carried in a physical downlink control channel PDCCH from the network device. The DCI may include a first power control command for a first power control loop or a second power control command for a second power control loop depending on which power control loop the DCI is associated with. This means that the power control loop for the terminal device generates and transmits separate power control commands, respectively. The dynamic power control related parameters will then be applied to the respective first or second power control loop in order to perform power control for the corresponding service(s).

According to a further embodiment, the terminal device may need to determine which power control loop the received DCI is associated with in order to find out to which power control loop the specific power control command should be applied. The terminal device may have different ways to determine this information.

In one embodiment of the present disclosure, the terminal device may determine which power control loop the received DCI is associated with based on the length of the time interval in which the DCI is used for scheduling. As an example, in a 5G network, the design principle of eMBB and URLLC is that URLLC needs to transmit data using time intervals (also referred to as "transmission time intervals TTI") (a smaller number of OFDM symbols or numbers with less duration). The terminal device may infer the traffic type from the DCI in the PDCCH and then determine the corresponding power control loop associated with the DCI.

In another embodiment of the present disclosure, the terminal device may determine which power control loop the received DCI is associated with based on a search space of the PDCCH carrying the DCI. As one example, in a 5G network, the search spaces for the PDCCHs of the eMBB and URLLC may be different, then depending on where the PDCCH is detected, the terminal device may infer the traffic type from the DCI in the PDCCH, and then determine the power control loop associated with the DCI.

In yet another embodiment, the terminal device may determine which power control loop the received DCI is associated with based on information in a field of the received DCI.

In yet another embodiment, the terminal device may determine which power control loop the received DCI is associated with based on the format of the received DCI. Assuming that different DCI formats are used in the 5G network for URLLC and eMBB, respectively, the terminal device may distinguish power control commands between power control loops according to the DCI format differences. For example, DCI format a is configured for URLLC, and DCI format b is configured for eMBB, which are respectively scheduled for terminal devices. In this way, the power control loop associated with the DCI can be determined by directly checking DCI formats a and b.

In one or more embodiments of the present disclosure, the second power control loop may operate between the terminal device and the network in dependence on the first power control loop. For example, in a 5G network, eMBB traffic is continuous while URLLC traffic is scattered, it is reasonable to operate a first power control loop according to eMBB and a second power control loop for URLLC dependent on the first power control loop in order to save processing resources and transmit payload. Thus, the first power control loop and the second power control loop may operate dependently or jointly, as if there were only one operating power control loop that is consistent with power control parameters appropriate for one type of service (e.g., eMBB).

According to some embodiments in which the second power control loop operates in dependence on the first power control loop, the terminal device may receive, from the network device, via at least one RRC signaling, a first parameter configuration and a relative parameter configuration of the first power control loop, the relative parameter configuration indicating a difference between the first parameter configuration of the first power control loop and a second parameter configuration of the second power control loop, at step S230. Based on this first parameter configuration, the relative parameter configuration, and some predefined rules, the terminal device may calculate an additional power boost for the second type of traffic (e.g. URLLC).

According to certain embodiments of the present disclosure, the dynamic power control related parameter may be a power control command included in the DCI, e.g., a TPC command. In step S240, the terminal device may receive DCI carried in the PDCCH from the network device, where the DCI includes a power control command of the first power control loop. The power control command may be applied to either the first or second power control loops depending on which power control loop the received DCI is associated with. Specifically, if the DCI is associated with a first power control loop (e.g., an eMBB loop), it will apply transmit power according to the first power control loop. If the DCI is associated with a second power control loop (e.g., a URLLC loop), the terminal device may add additional power according to the relative parameter configuration for the second power control loop in addition to the transmission power calculated according to the first power control loop.

In one embodiment of the present disclosure, the terminal device may determine which power control loop the received DCI is associated with based on the length of the time interval in which the DCI is used for scheduling. In another embodiment, the terminal device may determine which power control loop the received DCI is associated with based on the search space of the PDCCH carrying the DCI. In yet another embodiment, the terminal device may determine which power control loop the received DCI is associated with based on information in a field of the received DCI. In yet another embodiment, the terminal device may determine which power control loop the received DCI is associated with based on the format of the received DCI.

In response to determining that the received DCI is associated with a second power control loop, the terminal device may determine a second power configuration based on the first parameter configuration and the relative parameter configuration to perform power control for the second type of traffic.

Fig. 3 shows a flow diagram of a method 300 implemented at a network device in accordance with one or more embodiments of the present disclosure.

As shown in fig. 3, in step S310, the network device performs power control for at least a first type of traffic for the terminal device based on a first parameter configuration of a first power control loop. In step S320, the network device performs power control of at least a second type of traffic for the terminal device based on a second parameter configuration of the second control loop. The first type of traffic may have different QoS requirements than the second type of traffic. In order to meet QoS requirements of different QoS requirements, the first parameter configuration of the first power control loop comprises at least one parameter different from the second parameter configuration of the second power control loop. The parameter configuration may be designed, for example, to include parameters of a semi-static configuration, such as the open loop operating point P0, the path loss compensation factor α, the power control step size, and/or other parameters as described in equation 1).

According to one or more embodiments of the present disclosure, the first type of traffic may be eMBB traffic and the second type of traffic may be URLLC traffic. mtc traffic may share a first power control loop with eMBB traffic.

In one or more embodiments in which the first power control loop may operate independently of the second power control loop between the terminal device and the network, the network device may send the first parameter configuration of the first power control loop and the second parameter configuration of the second power control loop to the terminal device via at least one RRC signaling at step S330. In step S340, the network device may transmit DCI to the terminal device in the PDCCH, where the DCI includes a first power control command of a first power control loop or a second power control command of a second power control loop depending on which power control loop the DCI is associated with.

Since the network device may need to generate accurate power control commands for each loop independently, the network device has to know from which power control loop the PUSCH or physical uplink control channel PUCCH received in the uplink, so that the network device can compare the received power with the correct target and generate the correct dynamic power control commands for the corresponding power control loops. In accordance with one or more embodiments, a network device may receive a physical uplink shared channel, PUSCH, or PUCCH, from a terminal device and determine a first power control command for a first power control loop or a second power configuration for a second power control loop based on the received PUSCH or PUCCH. The network device may further determine which power control loop the PUSCH or PUCCH is associated with.

In one embodiment of the present disclosure, the terminal device may determine which power control loop the PUSCH or PUCCH is associated with based on the length of the time interval in which the PUSCH or PUCCH is transmitted. The network device may check the length of the time domain of the PUSCH or PUCCH, transmit the PUSCH or PUCCH using the short TTI or the long TTI, and if configured such that the short TTI is used for the second type of service (e.g., URLLC) and the long TTI length is used for the first type of service (e.g., eMBB service), the network device may identify which loop the PUSCH or PUCCH corresponds to by checking the length of the period in which the PUSCH is transmitted.

In another embodiment of the present disclosure, the network device may determine which power control loop the PUSCH or PUCCH is associated with based on the timing relationship between the uplink grant and the PUSCH or PUCCH. In 5G networks, in principle, there is a shorter time interval between the UL grant transmission and the corresponding PUSCH or PUCCH transmission for shorter TTIs. Thus, by checking the relationship between the uplink grant and the received PUSCH or PUCCH, the network device can identify which power control loop the PUSCH or PUCCH is associated with.

In yet another embodiment of the present disclosure, the network device may determine which power control loop the PUSCH or PUCCH is associated with based on a logical channel identifier in a media access control MAC header carried in the PUSCH or PUCCH. For example, in a 5G network, URLLC and eMBB traffic belong to different logical channels, the NW may also identify the type of PUSCH or PUCCH by checking the logical channel ID in the MAC header.

Once the network device knows the type of PUSCH or PUCCH, it can compare the measured power to the correct target and generate the correct control power command. According to certain embodiments of the present disclosure, the network may transmit DCI to the terminal device in the PDCCH in step S340. The DCI may include a first power control command for a first power control loop or a second power control command for a second power control loop depending on which power control loop the DCI is associated with.

In one or more embodiments of the present disclosure, the second power control loop may operate between the terminal device and the network in dependence on the first power control loop. For example, in a 5G network, eMBB traffic is continuous while URLLC traffic is scattered, it is reasonable to operate a first power control loop according to eMBB and a second power control loop for URLLC dependent on the first power control loop in order to save processing resources for signaling and to transmit payload. Thus, the first power control loop and the second power control loop may operate dependently or jointly, as if there were only one operating power control loop that is consistent with power control parameters appropriate for one type of service (e.g., eMBB).

According to some embodiments in which the second power control loop operates in dependence on the first power control loop, the network device may send, to the terminal device, via at least one RRC signaling, a first parameter configuration and a relative parameter configuration of the first power control loop, the relative parameter configuration indicating a difference between the first parameter configuration of the first power control loop and the second parameter configuration of the second power control loop, at step S330. Based on the relative parameter configuration, the first parameter configuration, and some predefined rules, the terminal device may calculate an additional power boost for the second type of service (e.g. URLLC traffic).

In certain embodiments of the present disclosure, the network device may receive a PUSCH or PUCCH from the terminal device and determine a power control command for the first power control loop based on the received PUSCH or PUCCH.

According to some embodiments, the dynamic power control related parameter may be a power control command, e.g. a TPC command, included in the downlink control information. In step S340, the network device may transmit DCI carried in the PDCCH to the terminal device. The DCI may include a power control command generated from the first power control loop. In this embodiment, the control power command generation may be based on a first type of traffic, e.g., eMBB traffic. The network device may further determine which power control loop the PUSCH or PUCCH is associated with.

In one embodiment, the terminal device may determine which power control loop the PUSCH or PUCCH is associated with based on the length of the time interval in which the PUSCH or PUCCH is transmitted.

In another embodiment, the network device may determine which power control loop the PUSCH or PUCCH is associated with based on the timing relationship between the uplink grant and the PUSCH or PUCCH.

In yet another embodiment, the network device may determine which power control loop the PUSCH or PUCCH is associated with based on a logical channel identifier in a media access control MAC header carried in the PUSCH or PUCCH.

If it is determined that the PUSCH or PUCCH corresponds to the first power control loop for the first type of traffic (e.g., eMBB traffic), the control power command will be generated by directly comparing the measured power to a target. If it corresponds to a second power control loop for a second type of traffic (e.g., URLLC traffic), then in one embodiment, no TPC is generated, or in another embodiment, the measured power is first reduced by an offset calculated from the relative parameter configuration and then compared to a target to generate TPC commands. In this way, the TPC sent to the terminal device is adapted for use in a first power control loop for a first type of traffic (e.g., eMBB).

Fig. 4 shows a schematic block diagram of an apparatus 400 implemented as/in a terminal device in accordance with one or more embodiments of the present disclosure. As shown in fig. 4, a terminal device 400 (e.g., a UE) is configured to communicate with one or more network devices (e.g., enodebs). The terminal device 400 includes a first power control unit 410, a second power control unit 420. Terminal device 400 may include a suitable radio frequency transceiver for wireless communication with one or more network devices via one or more antennas (not shown in fig. 4). The first power control unit 410 is configured to perform power control for at least a first type of traffic based on a first parameter configuration of the first power control loop. The second power control unit 420 is configured to perform power control for at least a second type of traffic based on a second parameter configuration of the second control loop. The first parameter configuration of the first power control loop includes at least one parameter different from the second parameter configuration of the second power control loop. For example, the first type of traffic may be eMBB traffic and the first power control loop may be adapted to meet QoS requirements of the eMBB traffic. The second type of traffic may be URLLC traffic and the second power control loop may be adapted to meet QoS requirements of the URLLC traffic. In the 5G system, since the mtc traffic has delay tolerance, its reliability can be guaranteed by MAC ARQ and RLC ARQ. In one embodiment, mtc traffic may share a first power control loop with eMBB traffic.

In one or more embodiments, the first power control loop and the second power control loop may operate independently to perform power control of the respective service traffic. The terminal device 400 may further comprise a receiving unit (not shown in fig. 4) configured to receive, from the network device via at least one RRC signaling, a first parameter configuration of the first power control loop and a second parameter configuration of the second power control loop. The receiving unit may further receive DCI carried in the PDCCH from the network device. The DCI may include a first power control command for a first power control loop or a second power control command for a second power control loop depending on which power control loop the received DCI is associated with. The power control commands may be applied to the respective first or second power control loops such that the corresponding power control unit 410 or 420 may perform power control based on the corresponding parameter configuration and power control commands.

According to one or more embodiments of the present disclosure, the terminal device 400 may include a determination unit for determining which power control loop the received DCI is associated with. In one embodiment, the determination unit may make this determination based on the length of the time interval in which the received DCI is used for scheduling. In another embodiment, the determination unit may make this determination based on the search space of the PDCCH carrying the DCI. In yet another embodiment, the determining unit may rely on information in a field of the received DCI. In yet another embodiment, the determining unit may determine which power control loop the DCI is associated with based on a format of the received DCI.

In one or more embodiments, the first power control loop and the second power control loop may operate dependently to perform power control for respective service traffic. Nevertheless, the first power control unit 410 may be directly or indirectly coupled to the second power control unit 420 such that certain parameter(s) may be reused between the two power control loops. The terminal device 400 may further comprise a receiving unit configured to receive, via at least one RRC signaling, a first parameter configuration and a relative parameter configuration of the first power control loop from the network device, the relative parameter configuration indicating a difference between the first parameter configuration of the first power control loop and the second parameter configuration of the second power control loop. The receiving unit may further receive DCI carried in the PDCCH from the network device, wherein the DCI includes power control commands of the first power control loop. The power control command may be applied to the first power control loop or the second power control loop depending on which power control loop the received DCI is associated with.

In one embodiment, in response to determining that the received DCI is associated with a second power control loop, a second parameter configuration may be determined based on the first parameter configuration and the relative parameter configuration.

Terminal device 400 may include a processor 40 including one or more microprocessors or microcontrollers, as well as other digital hardware, which may include a Digital Signal Processor (DSP), dedicated digital logic, or the like. The processor 40 may be configured to execute program code stored in memory (not shown in fig. 4), which may include one or more types of memory, such as Read Only Memory (ROM), random access memory, cache memory, flash memory devices, optical storage devices, and so forth. In several embodiments, the program code stored in the memory includes program instructions for executing one or more telecommunications and/or data communications protocols, as well as instructions for performing one or more of the techniques described herein. In some implementations, processor 40 may be configured to cause first power control unit 410, second power control unit 420, optional receiving unit, determining unit (not shown), and any other suitable unit of terminal device 400 to perform corresponding functions in accordance with one or more embodiments of the present disclosure.

Fig. 5 shows a schematic block diagram of an apparatus 500 implemented as/in a network device in accordance with one or more embodiments of the present disclosure. As shown in fig. 5, a network device 500 (e.g., an eNodeB) is configured to communicate with one or more terminal devices (e.g., UEs). The network device 500 includes a first power control unit 510, a second power control unit 520. Network device 500 may include a suitable radio frequency transceiver for wireless communication with one or more terminal devices via one or more antennas (not shown in fig. 5). The first power control unit 510 is configured to perform power control for at least a first type of traffic for the terminal device based on a first parameter configuration of a first power control loop. The second power control unit 520 is configured to perform power control for at least a second type of traffic for the terminal device based on a second parameter configuration of the second control loop. The first parameter configuration of the first power control loop includes at least one parameter different from the second parameter configuration of the second power control loop. For example, the first type of traffic may be eMBB traffic and the first power control loop may be adapted to meet QoS requirements of the eMBB traffic. The second type of traffic may be URLLC traffic and the second power control loop may be adapted to meet QoS requirements of the URLLC traffic. In the 5G system, since the mtc traffic has delay tolerance, its reliability can be guaranteed by MAC ARQ and RLC ARQ. In one embodiment, mtc traffic may share a first power control loop with eMBB traffic.

In one or more embodiments of the present disclosure, the first power control loop and the second power control loop may operate independently to perform power control of the respective service traffic. The network device 500 may further comprise a transmitting unit (not shown in fig. 5) configured to transmit the first parameter configuration of the first power control loop and the second parameter configuration of the second power control loop to the terminal device via at least one RRC signaling.

According to some embodiments of the present disclosure, the network device 500 may further include a receiving unit (not shown in fig. 5) and a determining unit (not shown in fig. 5). The receiving unit may be configured to receive a PUSCH or PUCCH from the terminal device. The determining unit is configured to determine a first power control command of the first power control loop or a second power configuration of the second power control loop based on the received PUSCH or PUCCH, depending on which power control loop the received PUSCH or PUCCH is associated with. For example, the determining unit may determine which power control loop the PUSCH or PUCCH is associated with further based on the length of the time interval in which the PUSCH or PUCCH is transmitted. In another embodiment, the determining unit may make such a determination based on a timing relationship between the uplink grant and the PUSCH or PUCCH. In yet another embodiment, the determining unit may make this determination based on a logical channel identifier in a medium access control MAC header carried in the PUSCH or PUCCH.

According to one embodiment of the present disclosure, the network device 500 may include a transmission unit configured to transmit DCI in a PDCCH to a terminal device. The DCI may include a first power control command for a first power control loop or a second power control command for a second power control loop depending on which power control loop the DCI is associated with.

In one or more embodiments of the present disclosure, the first power control loop and the second power control loop may operate dependently to perform power control for respective service traffic. Nevertheless, the first power control unit 510 may be directly or indirectly coupled to the second power control unit 520 such that certain parameter(s) may be reused between the two power control loops. The network device 500 may further comprise a transmitting unit configured to transmit, to the terminal device via at least one RRC signaling, the first parameter configuration of the first power control loop and a relative parameter configuration indicating a difference between the first parameter configuration of the first power control loop and the second parameter configuration of the second power control loop.

According to some embodiments, the network device 500 may further comprise a receiving unit (not shown in fig. 5) and a determining unit (not shown in fig. 5). The receiving unit may be configured to receive a PUSCH or PUCCH from the terminal device. The determining unit may be configured to determine a power control command of the first power control loop based on the received PUSCH or PUCCH. The power control commands may be used to control power in the first power control loop or the second power control loop depending on which power control loop the PUSCH or PUCCH is associated with, although it is generated from the first power control loop. The network device 500 may further include a transmitting unit configured to transmit DCI carried in the PDCCH to the terminal device, where the DCI includes the power control command of the first power control loop.

Network device 500 may include a processor 50 including one or more microprocessors or microcontrollers, as well as other digital hardware, which may include a Digital Signal Processor (DSP), dedicated digital logic, or the like. The processor 50 may be configured to execute program code stored in memory (not shown in fig. 5), which may include one or more types of memory, such as Read Only Memory (ROM), random access memory, cache memory, flash memory devices, optical storage devices, and so forth. In several embodiments, the program code stored in the memory includes program instructions for executing one or more telecommunications and/or data communications protocols, as well as instructions for performing one or more of the techniques described herein. In some implementations, processor 50 may be configured to cause first power control unit 510, second power control unit 520, optional receiving unit, transmitting unit, determining unit (not shown), and any other suitable unit of network device 500 to perform corresponding functions in accordance with one or more embodiments of the present disclosure.

Fig. 6 shows a simplified block diagram of an apparatus 610, which may be embodied as/in a terminal device (e.g., terminal device 400), and an apparatus 620, which may be embodied as/in a network device (e.g., terminal device 500).

The apparatus 610 may include one or more processors 611 (e.g., a Data Processor (DP)) and one or more memories (MEM)612 coupled to the processors 611. The apparatus 610 may further include a transmitter TX and a receiver RX 613 coupled to the processor 611. The MEM612 may be a non-transitory machine-readable storage medium and may store a Program (PROG) 614. The PROG 614 may include instructions that, when executed on the associated processor 611, enable the apparatus 610 to operate in accordance with embodiments of the present disclosure, such as to perform the method 200. The combination of the one or more processors 611 and the one or more MEMs 612 may form a processing device 615 suitable for implementing various embodiments of the present disclosure.

The device 620 includes one or more processors 621 (e.g., DP) and one or more MEMs 622 coupled to the processors 621. Means 620 may further comprise a suitable TX/RX 623 coupled to processor 621. The MEM 622 may be a non-transitory machine-readable storage medium and may store the PROG 624. The PROG 624 may include instructions that, when executed on the associated processor 621, enable the apparatus 620 to operate in accordance with embodiments of the disclosure, such as to perform the method 300. The combination of the one or more processors 621 and the one or more MEMs 622 may form a processing device 625 suitable for implementing various embodiments of the present disclosure.

Various embodiments of the disclosure may be implemented by a computer program executable by one or more of the processors 611 and 621, software, firmware, hardware, or by a combination thereof.

The MEMs 612 and 622 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, including by way of non-limiting example semiconductor-based memory terminal devices, magnetic memory terminal devices and systems, optical memory terminal devices and systems, fixed memory and removable memory.

The processors 611 and 612 may be of any type suitable to the local technical environment, and may include, by way of non-limiting example, one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors, DSPs, and processors based on a multi-core processor architecture.

While some of the above description is made in the context of a wireless system that supports scenarios for both URLLC and eMBB services, it should not be construed as limiting the spirit and scope of the present disclosure. The principles and concepts of the present disclosure may be more generally applicable to other scenarios.

According to embodiments of the present disclosure, at least two power control loops may be implemented between a terminal device and a network device. Thus, power control for different types of services may be performed independently or dependently. In this way, different performance requirements for these services can be guaranteed.

Additionally, the present disclosure may also provide a memory containing a computer program as described above, including a machine-readable medium and a machine-readable transmission medium. The machine-readable medium may also be referred to as a computer-readable medium and may include a machine-readable storage medium, such as a magnetic disk, magnetic tape, optical disk, phase change memory, or an electronic storage terminal device, such as Random Access Memory (RAM), Read Only Memory (ROM), flash memory device, CD-ROM, DVD, Blu-ray disk, etc. A machine-readable transmission medium may also be referred to as a carrier, and may include, for example, electrical, optical, wireless, acoustic, or other form of propagated signals, such as carrier waves, infrared signals, etc.

The techniques described herein may be implemented by various means, so that an apparatus implementing one or more functions of a corresponding apparatus described using one embodiment includes not only prior art means but also means for implementing one or more functions of a corresponding apparatus described using the embodiment, and it may include separate means for each separate function or means that may be configured to perform two or more functions. For example, these techniques may be implemented in hardware (one or more devices), firmware (one or more devices), software (one or more modules), or a combination thereof. For firmware or software, implementation can be through modules (e.g., procedures, functions, and so on) that perform the functions described herein.

The example embodiments herein have been described above with reference to block diagrams and flowchart illustrations of methods and apparatus. It will be understood that each block of the block diagrams and flowchart illustrations, and combinations of blocks in the block diagrams and flowchart illustrations, respectively, can be implemented by various means, including hardware, software, firmware, and combinations thereof. For example, in one embodiment, each block of the block diagrams and flowchart illustrations, and combinations of blocks in the block diagrams and flowchart illustrations, can be implemented by computer program instructions. These computer program instructions may be loaded onto a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions which execute on the computer or other programmable data processing apparatus create means for implementing the functions specified in the flowchart block or blocks.

Further, while operations are shown in a particular order, it should not be understood that these operations need to be performed in the particular order shown or in sequential order, or that all illustrated operations need to be performed, to achieve desirable results. In some cases, multitasking and parallel processing may be advantageous. Also, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the subject matter described herein, but rather as descriptions of features that may be specific to particular embodiments. In this specification, certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Furthermore, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

It will be obvious to a person skilled in the art that with the advancement of technology, the inventive concept may be implemented in various ways. The above-described embodiments are given for the purpose of illustration and not limitation of the present disclosure, and it is to be understood that modifications and variations may be resorted to without departing from the spirit and scope of the disclosure as those skilled in the art readily understand. Such modifications and variations are considered to be within the scope of the disclosure and the appended claims. The scope of the disclosure is defined by the appended claims.

Claims

1. A method (200) implemented at a terminal device, comprising:

performing (S210) power control of at least a first type of traffic based on a first parameter configuration of a first power control loop; and

performing (S220) power control for at least a second type of traffic based on a second parameter configuration of a second power control loop,

wherein the first parameter configuration of the first power control loop comprises at least one parameter different from the second parameter configuration of the second power control loop, an

Wherein the first type of traffic comprises enhanced mobile broadband, eMBB, data and control information communications, and the second type of traffic comprises ultra-reliable and low-latency communications, URLLC, data and control information communications.

2. The method of claim 1, further comprising:

receiving (S230) the first parameter configuration of the first power control loop and the second parameter configuration of the second power control loop from a network device via at least one radio resource control, RRC, signaling.

3. The method according to any one of claims 1-2, further comprising:

receiving (S240), from a network device, downlink control information, DCI, carried in a physical downlink control channel, PDCCH, wherein the DCI comprises a first power control command for the first power control loop or a second power control command for the second power control loop,

wherein the first or the second power control command is applied to the respective first or second power control loop.

4. The method of claim 3, further comprising:

determining which power control loop the received DCI is associated with based on a length of a time interval in which the DCI is used for scheduling.

5. The method of claim 3, further comprising:

determining which power control loop the DCI is associated with based on a search space of a PDCCH carrying the received DCI.

6. The method of claim 3, further comprising:

determining which power control loop the received DCI is associated with based on information in a field of the received DCI.

7. The method of claim 3, further comprising:

determining which power control loop the received DCI is associated with based on a format of the received DCI.

8. The method of claim 1, further comprising:

receiving (S230), via at least one RRC signaling, the first parameter configuration of the first power control loop and a relative parameter configuration from a network device, the relative parameter configuration indicating a difference between the first parameter configuration of the first power control loop and the second parameter configuration of the second power control loop.

9. The method of claim 8, further comprising:

receiving (S240), from the network device, DCI carried in a PDCCH, wherein the DCI comprises power control commands of the first power control loop,

wherein the power control command is applied to the first or second power control loop depending on which power control loop the received DCI is associated with.

10. The method of claim 9, further comprising:

11. The method of claim 9, further comprising:

12. The method of claim 9, further comprising:

13. The method of claim 9, further comprising:

14. The method according to any one of claims 9-13, further comprising:

determining the second power configuration based on the first parameter configuration and the relative parameter configuration in response to determining that the received DCI is associated with the second power control loop.

15. A method (300) implemented at a network device, comprising:

performing (S310), for the terminal device, power control of at least a first type of traffic based on a first parameter configuration of a first power control loop; and

performing (S320), for the terminal device, power control for at least a second type of traffic based on a second parameter configuration of a second power control loop,

16. The method of claim 15, further comprising:

transmitting (S330) the first parameter configuration of the first power control loop and the second parameter configuration of the second power control loop to the terminal device via at least one radio resource control, RRC, signaling.

17. The method according to any one of claims 15-16, further comprising:

receiving a physical uplink shared channel, PUSCH, or a physical uplink control channel, PUCCH, from the terminal device;

determining a first power control command of the first power control loop or a second power control command of the second power control loop based on the received PUSCH or PUCCH.

18. The method of claim 17, wherein determining the first power control command of the first power control loop or the second power control command of the second power control loop based on the received PUSCH or PUCCH further comprises:

determining which power control loop the PUSCH or PUCCH is associated with based on a length of a time interval in which the PUSCH or PUCCH is transmitted.

19. The method of claim 17, wherein determining the first power control command of the first power control loop or the second power control command of the second power control loop based on the received PUSCH or PUCCH further comprises:

determining which power control loop the PUSCH or PUCCH is associated with based on a timing relationship between an uplink grant and the PUSCH or PUCCH.

20. The method of claim 17, wherein determining the first power control command of the first power control loop or the second power control command of the second power control loop based on the received PUSCH or PUCCH further comprises:

determining which power control loop the PUSCH or PUCCH is associated with based on a logical channel identifier in a Media Access Control (MAC) header carried in the PUSCH or PUCCH.

21. The method of claim 16, further comprising:

transmitting (S340) DCI to the terminal device in the PDCCH, wherein the DCI comprises a first power control command of the first power control loop or a second power control command of the second power control loop, depending on which power control loop the DCI is associated with.

22. The method of claim 15, further comprising:

sending (S330) the first parameter configuration of the first power control loop and a relative parameter configuration to the terminal device via at least one RRC signaling, the relative parameter configuration indicating a difference between the first parameter configuration of the first power control loop and the second parameter configuration of the second power control loop.

23. The method of claim 22, further comprising:

determining a power control command for the first power control loop based on the received PUSCH or PUCCH.

24. The method of claim 23, further comprising:

transmitting (S340), to the terminal device, DCI carried in a PDCCH, wherein the DCI comprises the power control commands of the first power control loop.

25. A terminal device (400) comprising:

a first power control unit (410) configured to perform power control for at least a first type of traffic based on a first power configuration of a first power control loop;

a second power control unit (420) configured to perform power control for at least a second type of traffic based on a second power configuration of a second power control loop,

wherein the first power configuration of the first power control loop comprises at least one parameter different from the second power configuration of the second power control loop, an

26. A network device (500), comprising:

a first power control unit (510) configured to perform power control for at least a first type of traffic for the terminal device based on a first power configuration of a first power control loop;

a second power control unit (520) configured to perform power control for at least a second type of traffic for the terminal device based on a second power configuration of a second power control loop,

27. A terminal device (400) comprising a processor (40) and a non-transitory machine-readable storage medium containing instructions that when executed on the processor cause the terminal device to perform the method of any of claims 1-14.

28. A network device (500) comprising a processor (50) and a non-transitory machine-readable storage medium containing instructions that when executed on the processor cause the network device to perform the method of any of claims 15-24.

29. A computer-readable medium storing computer program instructions that, when executed on one or more processors, cause the one or more processors to perform the method of any one of claims 1-14.

30. A computer readable medium storing computer program instructions that, when executed on one or more processors, cause the one or more processors to perform the method of any one of claims 15 to 24.