WO2019196114A1 - 一种上行功率控制方法、终端设备及网络设备 - Google Patents

一种上行功率控制方法、终端设备及网络设备 Download PDF

Info

Publication number
WO2019196114A1
WO2019196114A1 PCT/CN2018/083092 CN2018083092W WO2019196114A1 WO 2019196114 A1 WO2019196114 A1 WO 2019196114A1 CN 2018083092 W CN2018083092 W CN 2018083092W WO 2019196114 A1 WO2019196114 A1 WO 2019196114A1
Authority
WO
WIPO (PCT)
Prior art keywords
uplink signal
power control
loop power
closed loop
terminal device
Prior art date
Application number
PCT/CN2018/083092
Other languages
English (en)
French (fr)
Inventor
陈文洪
史志华
Original Assignee
Oppo广东移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to PCT/CN2018/083092 priority Critical patent/WO2019196114A1/zh
Priority to IL271001A priority patent/IL271001B1/en
Priority to EP22155637.6A priority patent/EP4037390A1/en
Priority to KR1020197036274A priority patent/KR102475094B1/ko
Priority to EP18914290.4A priority patent/EP3627912B1/en
Priority to AU2018418095A priority patent/AU2018418095B8/en
Priority to SG11201911426YA priority patent/SG11201911426YA/en
Priority to CN201911303137.3A priority patent/CN111132295B/zh
Application filed by Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to ES18914290T priority patent/ES2912355T3/es
Priority to CA3065621A priority patent/CA3065621C/en
Priority to CN201880031781.7A priority patent/CN110637484B/zh
Priority to JP2019568084A priority patent/JP7080906B2/ja
Priority to RU2019142488A priority patent/RU2758467C1/ru
Priority to BR112019027113-9A priority patent/BR112019027113A2/pt
Publication of WO2019196114A1 publication Critical patent/WO2019196114A1/zh
Priority to US16/694,132 priority patent/US10880838B2/en
Priority to PH12019502691A priority patent/PH12019502691A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—TPC
    • H04W52/06—TPC algorithms
    • H04W52/08—Closed loop power control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L25/00—Baseband systems
    • H04L25/02—Details ; arrangements for supplying electrical power along data transmission lines
    • H04L25/0202—Channel estimation
    • H04L25/0224—Channel estimation using sounding signals
    • H04L25/0226—Channel estimation using sounding signals sounding signals per se
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H04L5/0051—Allocation of pilot signals, i.e. of signals known to the receiver of dedicated pilots, i.e. pilots destined for a single user or terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0092—Indication of how the channel is divided
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—TPC
    • H04W52/06—TPC algorithms
    • H04W52/14—Separate analysis of uplink or downlink
    • H04W52/146—Uplink power control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—TPC
    • H04W52/38—TPC being performed in particular situations
    • H04W52/50—TPC being performed in particular situations at the moment of starting communication in a multiple access environment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—TPC
    • H04W52/54—Signalisation aspects of the TPC commands, e.g. frame structure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—TPC
    • H04W52/54—Signalisation aspects of the TPC commands, e.g. frame structure
    • H04W52/545—Signalisation aspects of the TPC commands, e.g. frame structure modifying TPC bits in special situations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—TPC
    • H04W52/54—Signalisation aspects of the TPC commands, e.g. frame structure
    • H04W52/58—Format of the TPC bits
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/085—Upper layer protocols involving different upper layer protocol versions, e.g. LCS - SUPL or WSN-SOA-WSDP

Definitions

  • the present invention relates to the field of information processing technologies, and in particular, to an uplink power control method, a terminal device, a network device, and a computer storage medium.
  • the current transmit power of the PUSCH can be calculated by the following formula:
  • i denotes the index of the primary PUSCH transmission
  • j is the index of the open loop power control parameter
  • P O_PUSCH, f,c (j) and ⁇ f,c (j) are open loop power control parameters
  • PL f,c (q d ) is the path loss estimated value measured based on the downlink reference signal
  • f f,c (i,l) is the closed-loop power adjustment factor
  • l is the index of the closed-loop power control process.
  • the value of j, l and the downlink reference signal used to measure the path loss estimation value PL f,c (q d ) may be obtained based on SRI (SRS Resource Indicator) information included in the DCI.
  • SRI SRS Resource Indicator
  • the network side pre-configures the correspondence between different PUCCH-Spatial relation Info and ⁇ j, qd, l ⁇ , and determines the current PUCCH transmission by using the currently used PUCCH spatial correlation information. ⁇ j,qd,l ⁇ .
  • the network side indicates all available PUCCH spatial related information through RRC signaling, and then indicates the currently used PUCCH spatial related information by using the MAC CE.
  • the TPC command can be obtained by dedicated Downlink Control Information (DCI) dedicated to carrying Transmit Power Control (TPC) commands to determine the closed loop power adjustment factor.
  • DCI Downlink Control Information
  • TPC Transmit Power Control
  • the DCI adopts the DCI format 2-2 and performs scrambling using the PUSCH-TPC-RNTI or the PUCCH-TPC-RNTI, and may include TPC commands of multiple terminals.
  • PUSCH and PUCCH may be transmitted simultaneously on multiple BWPs, and both can support multiple closed-loop power control processes. In this case, how to obtain the respective TPC commands of each closed-loop power control process on each BWP is a need to be solved. The problem.
  • an embodiment of the present invention provides an uplink power control method, a terminal device, a network device, and a computer storage medium.
  • An embodiment of the present invention provides an uplink power control method, which is applied to a terminal device, where the method includes:
  • the embodiment of the invention provides an uplink power control method, which is applied to a network device, and the method includes:
  • the embodiment of the invention provides a terminal device, where the terminal device includes:
  • the first processing unit Determining, by the first processing unit, the number of bits of the transmission power control TPC command field of the terminal device in the downlink control information DCI according to the number of the bandwidth part BWP that sends the uplink signal or the number of closed loop power control processes associated with the uplink signal ;
  • the embodiment of the invention provides a network device, including:
  • the second processing unit determines the number of bits of the transmit power control TPC command field of the terminal device in the downlink control information DCI according to the number of the bandwidth part BWP that sends the uplink signal or the number of closed loop power control processes associated with the uplink signal;
  • the second communication unit sends the TPC command field to the terminal device by using the DCI.
  • a terminal device provided by an embodiment of the present invention includes: a processor and a memory for storing a computer program capable of running on a processor,
  • processor is configured to perform the steps of the foregoing method when the computer program is run.
  • a network device provided by an embodiment of the present invention includes: a processor and a memory for storing a computer program capable of running on a processor,
  • processor is configured to perform the steps of the foregoing method when the computer program is run.
  • a computer storage medium is provided by the embodiment of the present invention.
  • the computer storage medium stores computer executable instructions, and the foregoing method steps are implemented when the computer executable instructions are executed.
  • the corresponding TPC command can be determined according to the number of uplink signal BWPs or the number of closed loop power control processes, and the power adjustment factor corresponding to the uplink signal is determined according to the TPC command, thereby reducing one terminal as much as possible.
  • the DCI overhead of the TPC command saves unnecessary DCI overhead, and performs closed-loop power control of more terminals and more BWPs through one DCI.
  • FIG. 1 is a schematic flowchart 1 of an uplink power control method according to an embodiment of the present invention
  • FIG. 2 is a schematic flowchart 2 of an uplink power control method according to an embodiment of the present invention
  • FIG. 3 is a schematic structural diagram of a terminal device according to an embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of a network device according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of a hardware architecture according to an embodiment of the present invention.
  • An embodiment of the present invention provides an uplink power control method, which is applied to a terminal device, as shown in FIG. 1 , and includes:
  • Step 101 Determine, according to the number of the bandwidth part BWP that sends the uplink signal, or the number of closed loop power control processes associated with the uplink signal, the number of bits of the transmission power control TPC command field of the terminal equipment in the downlink control information DCI;
  • Step 102 Determine, according to the TPC command in the TPC command domain, a closed loop power adjustment factor for transmitting at least one BWP of the uplink signal or at least one closed loop power control process associated with the uplink signal.
  • the terminal device in this embodiment can be understood as a terminal having a communication function in a communication system, such as a mobile phone or the like.
  • the method for determining the number of closed loop power control processes associated with the uplink signal may include at least one of the following:
  • the uplink signal is a PUCCH
  • the uplink signal is an SRS
  • the determining, according to the transmission type of the current uplink signal, the number of closed loop power control processes associated with the uplink signal including:
  • the corresponding number is determined based on this type. For example, the number of closed loop power control processes associated with grant-free based uplink signals is one; the number of closed loop power control processes based on scheduling associations is 2 or network side configured values.
  • the terminal device configures at least one BWP, determine the number of closed loop power control processes for each BWP according to the transmission type on each BWP in the at least one BWP; wherein at least one can be understood as one of course, and more .
  • the foregoing determines the number of closed loop power control processes associated with the uplink signal according to the high layer signaling configuration, and may independently configure the number for the PUSCH and the PUCCH. If the terminal is configured with multiple BWPs, the network side can configure the number of closed loop power control processes for each BWP.
  • the number of the BWPs that send the uplink signal may be one of: the number of BWPs that simultaneously send the uplink signal; the number of currently activated uplink BWPs; and the number of uplink BWPs that the network side configures for the terminal.
  • these BWPs may not be used to simultaneously transmit the uplink signal, and only one or a part of the BWPs may be used to transmit the uplink signal at the same time.
  • the terminal may send the uplink signal by using different BWPs at different times.
  • the uplink signal is a PUSCH
  • the number of the closed loop power control processes associated with the uplink signal including at least one of the following three conditions:
  • the first correspondence indicates that all SRI states correspond to the same closed-loop power control process, and the number of closed-loop power control processes is 1. If the correspondence indicates that part of the SRI state corresponds to the closed-loop power control process 0, The other SRI states correspond to the closed loop power control process 1, and the number of closed loop power control processes is two.
  • the terminal device When the uplink signal is a PUSCH, and the terminal device is not configured with the SRI, or the first correspondence is not configured, determining that the number of closed loop power control processes associated with the uplink signal is 1;
  • the terminal device When the uplink signal is a PUSCH, and the terminal device is not configured with the SRI, or the first correspondence is not configured, determining that the number of closed loop power control processes associated with the uplink signal is 1, that is, if the terminal does not have The SRI or the correspondence between the SRI state and the closed loop power control process is configured, and the number of closed loop power control processes is 1.
  • the terminal device configures at least one BWP
  • the number of closed loop power control processes associated with the uplink signal is determined according to a first correspondence relationship of each BWP configuration in the at least one BWP.
  • the terminal device Determining, according to the first correspondence of each BWP configuration in the at least one BWP, the number of closed loop power control processes associated with the uplink signal, that is, when the uplink signal is a PUSCH, and the terminal device is configured with at least one BWP, that is, If the terminal is configured with multiple BWPs, the number can be determined according to the corresponding relationship configured on each BWP.
  • the first correspondence may be understood as a correspondence between the SRI state and the closed-loop power control process, where the SRI is an SRS resource indicator, and the acquiring manner may be performed by scheduling the PUSCH.
  • the DCI is to carry the SRI.
  • the number of closed-loop power control processes associated with the uplink signal that is, if the uplink signal is a PUCCH, according to the high-layer signaling, when the uplink signal is a PUCCH
  • the correspondence between the configured PUCCH-Spatial Relation Info and the closed-loop power control process is determined. Specifically, at least one of the following three cases may be included:
  • the terminal may determine, by the number of different closed loop power control processes included in the second correspondence, the number of closed loop power control processes associated with the uplink signal;
  • the correspondence indicates that all PUCCH spatial related information corresponds to the same closed loop power control process, and the number of closed loop power control processes is 1; if the second correspondence indicates that the partial PUCCH spatial correlation information corresponds to closed loop power Control process 0, other PUCCH space related information corresponds to closed loop power control process 1, then the number of closed loop power control processes is 2.
  • the terminal device When the uplink signal is a PUCCH, if the terminal device does not configure the PUCCH space related information, or the second correspondence is not configured, determine that the number of closed loop power control processes associated with the uplink signal is 1. ;
  • the number of closed loop power control processes is 1;
  • the number of closed loop power control processes associated with the uplink signal is determined according to a second correspondence relationship configured on each BWP in the at least one BWP. That is to say, if the terminal is configured with multiple BWPs, the number can be determined according to the second correspondence configured on each BWP.
  • the correspondence between the configured SRS-Spatial Relation Info and the closed-loop power control process is determined. Specifically, it may include at least one of the following three situations:
  • the terminal may determine the number of different closed loop power control processes included in the third correspondence as the number of closed loop power control processes associated with the uplink signal.
  • the third correspondence indicates that all SRS spatial related information corresponds to the same closed loop power control process, and the number of closed loop power control processes is 1. If the third correspondence indicates that part of the SRS space related information corresponds to The closed loop power control process is 0, and the other SRS space related information corresponds to the closed loop power control process 1, and the number of closed loop power control processes is 2.
  • the terminal device When the uplink signal is SRS, if the terminal device does not configure the SRS space related information, or the third correspondence is not configured, determine that the number of closed loop power control processes associated with the uplink signal is 1;
  • the number of closed loop power control processes is 1.
  • the number of BWPs that send the uplink signal is the number of BWPs that simultaneously send the uplink signal, or the number of uplink BWPs that are currently activated, or the number of uplink BWPs that the network side configures for the terminal; for the latter two cases, these BWPs It is not always possible to transmit the uplink signal at the same time, and only one or a part of the BWPs can be used to transmit the uplink signal at the same time.
  • the terminal may send the uplink signal by using different BWPs at different times.
  • the method further includes determining that the number of bits of the TPC command field in the DCI is 2.
  • the DCI includes a TPC command field of the terminal. For example, before the terminal receives the number of BWPs configured on the network side or the number of closed loop power control processes associated with the uplink signal, the terminal assumes that the number of bits of the TPC command field in the DCI is 2.
  • the method includes determining that the number of bits in the TPC command field is 2*N or 2+ if the number of BWPs transmitting the uplink signal is N, or the number of closed loop power control processes associated with the uplink signal is N. Log2(N).
  • the DCI is at least one of: a DCI carrying a TPC command of a PUSCH; a DCI carrying a TPC command of a PUCCH; and a DCI of a TPC command carrying an SRS.
  • the format of the DCI may be: DCI format 2-2 or DCI format 2-3; and the DCI is scrambled by using PUSCH-TPC-RNTI or PUCCH-TPC-RNTI or SRS-TPC-RNTI. .
  • the DCI can be used to indicate a TPC command on a BWP, and can also be used to indicate a TPC command on a different BWP.
  • the uplink signal is one of the following: PUSCH, PUCCH, and SRS.
  • the DCI format is DCI format 2-2, and is scrambled by PUSCH-TPC-RNTI or PUCCH-TPC-RNTI; if the uplink signal is SRS, then The DCI format is DCI format 2-3 and is scrambled by SRS-TPC-RNTI.
  • the embodiment may further provide a processing method for further determining the TPC command domain.
  • the method may further include: according to the TPC command location index indicated by the network side, and the number of bits of the TPC command domain, from the DCI. Determining a TPC command field of the terminal device.
  • the method for obtaining the TPC command location index may be: receiving the TPC command location index indicated by the RRC signaling on the network side, where the TPC command location index is used to indicate that the TPC command domain of the terminal device is in the The starting bit in the DCI.
  • the location index may be in units of 1 bit, that is, the start bit of the TPC command field may be in any position in the DCI; or the location index may be in units of 2 bits, that is, from the TPC command field.
  • the start bit may be any even bit of the DCI bits (eg, the bit index is 0, 2, 4, ).
  • the TPC command location index includes a location index of at least one TPC command; wherein each TPC command corresponds to one BWP or a closed loop power control process corresponding to one BWP.
  • the TPC command field includes a location index of multiple TPC commands, and each TPC command corresponds to a BWP or a closed loop power control process on a BWP, the network side may configure an independent location index for the multiple TPC commands. That is, the network side can independently configure the TPC command location index for each BWP or each closed-loop power control process.
  • the kth location index corresponds to the TPC command of the kth BWP or the kth closed loop power control process.
  • the TPC command field occupies consecutive bits in the DCI. For example, if the TPC command field contains 2 TPC commands, then the two TPC commands are two consecutive TPC commands in the DCI.
  • the TPC command location index indicates the kth bit, and the number of bits in the TPC command field is M, and the bit occupied by the TPC command field of the terminal is the ⁇ k, k+1, ..., k in the DCI. +M-1 ⁇ bits.
  • the TPC command field is 2*N bits, it includes N 2-bit TPC commands, and the n-th TPC command is used for the n-th BWP or the n-th closed-loop power control process;
  • the TPC command field is 2+log2(N) bits, and the first two bits are TPC commands, followed by log2(N) bits indicating the BWP or closed loop power control process corresponding to the TPC command, or the last two bits are TPC.
  • the pre-log2 (N) bits indicate the BWP or closed-loop power control process corresponding to the TPC command.
  • the embodiment may further include the following steps:
  • the method for determining the transmission power of the uplink signal may be calculated based on any closed-loop power adjustment factor, and the manner of calculation is not described herein.
  • the corresponding TPC command can be determined according to the number of uplink signal BWPs or the number of closed loop power control processes, and the power adjustment factor corresponding to the uplink signal is determined according to the TPC command, thereby reducing the terminal as much as possible.
  • the DCI overhead of the TPC command saves unnecessary DCI overhead, and performs closed-loop power control of more terminals and more BWPs through one DCI.
  • An embodiment of the present invention provides an uplink power control method, which is applied to a network device. As shown in FIG. 2, the method includes:
  • Step 201 Determine the number of bits of the transmit power control TPC command field of the terminal device in the downlink control information DCI according to the number of the bandwidth part BWP that sends the uplink signal, or according to the number of closed loop power control processes associated with the uplink signal;
  • Step 202 Send the TPC command domain to the terminal device by using the DCI.
  • the terminal device in this embodiment can be understood as a terminal having a communication function in a communication system, such as a mobile phone or the like.
  • the above method for determining the number of closed loop power control processes associated with the uplink signal may include at least one of the following:
  • the uplink signal is a PUCCH
  • the uplink signal is an SRS
  • the determining, according to the transmission type of the current uplink signal, the number of closed loop power control processes associated with the uplink signal including:
  • the terminal device configures at least one BWP, determine the number of closed loop power control processes for each BWP according to the transmission type on each BWP in the at least one BWP; wherein at least one can be understood as one of course, and more .
  • the foregoing determines the number of closed loop power control processes associated with the uplink signal according to the high layer signaling configuration, and may independently configure the number for the PUSCH and the PUCCH. If the terminal is configured with multiple BWPs, the network side can configure the number of closed loop power control processes for each BWP.
  • the number of the BWPs that send the uplink signal may be one of: the number of BWPs that simultaneously send the uplink signal; the number of currently activated uplink BWPs; and the number of uplink BWPs that the network side configures for the terminal.
  • these BWPs may not be used to simultaneously transmit the uplink signal, and only one or a part of the BWPs may be used to transmit the uplink signal at the same time.
  • the terminal may send the uplink signal by using different BWPs at different times.
  • the uplink signal is a PUSCH
  • the number of the closed loop power control processes associated with the uplink signal including at least one of the following three conditions:
  • the first correspondence indicates that all SRI states correspond to the same closed-loop power control process, and the number of closed-loop power control processes is 1. If the correspondence indicates that part of the SRI state corresponds to the closed-loop power control process 0, The other SRI states correspond to the closed loop power control process 1, and the number of closed loop power control processes is two.
  • the terminal device When the uplink signal is a PUSCH, and the terminal device is not configured with the SRI, or the first correspondence is not configured, determining that the number of closed loop power control processes associated with the uplink signal is 1;
  • the terminal device When the uplink signal is a PUSCH, and the terminal device is not configured with the SRI, or the first correspondence is not configured, determining that the number of closed loop power control processes associated with the uplink signal is 1, that is, if the terminal does not have The SRI or the correspondence between the SRI state and the closed loop power control process is configured, and the number of closed loop power control processes is 1.
  • the terminal device configures at least one BWP, determining, according to the first correspondence of each BWP configuration in the at least one BWP, the number of closed loop power control processes associated with the uplink signal.
  • the terminal device Determining, according to the first correspondence of each BWP configuration in the at least one BWP, the number of closed loop power control processes associated with the uplink signal, that is, when the uplink signal is a PUSCH, and the terminal device is configured with at least one BWP, that is, If the terminal is configured with multiple BWPs, the number can be determined according to the corresponding relationship configured on each BWP.
  • the first correspondence relationship may be understood as a correspondence between the SRI state and the closed-loop power control process, where the SRI is an SRS resource indicator (SRS Resource Indicator), and the acquiring manner may be performed by scheduling
  • the DCI of the PUSCH carries the SRI.
  • the number of closed-loop power control processes associated with the uplink signal that is, if the uplink signal is a PUCCH, according to the high-layer signaling, when the uplink signal is a PUCCH
  • the correspondence between the configured PUCCH-Spatial Relation Info and the closed-loop power control process determines the number of different closed-loop power control processes included in the correspondence. Specifically, at least one of the following three cases may be included:
  • the terminal may determine, by the number of different closed loop power control processes included in the second correspondence, the number of closed loop power control processes associated with the uplink signal;
  • the correspondence indicates that all PUCCH spatial related information corresponds to the same closed loop power control process, and the number of closed loop power control processes is 1; if the second correspondence indicates that the partial PUCCH spatial correlation information corresponds to closed loop power Control process 0, other PUCCH space related information corresponds to closed loop power control process 1, then the number of closed loop power control processes is 2.
  • the terminal device When the uplink signal is a PUCCH, if the terminal device does not configure the PUCCH space related information, or the second correspondence is not configured, determine that the number of closed loop power control processes associated with the uplink signal is 1. ;
  • the number of closed loop power control processes is 1;
  • the number of closed loop power control processes associated with the uplink signal is determined according to a second correspondence relationship configured on each BWP in the at least one BWP. That is to say, if the terminal is configured with multiple BWPs, the number can be determined according to the second correspondence configured on each BWP.
  • the correspondence between the configured SRS-Spatial Relation Info and the closed-loop power control process determines the number of different closed-loop power control processes included in the correspondence. Specifically, it may include at least one of the following three situations:
  • the terminal may determine the number of different closed loop power control processes included in the third correspondence as the number of closed loop power control processes associated with the uplink signal.
  • the third correspondence indicates that all SRS spatial related information corresponds to the same closed loop power control process, and the number of closed loop power control processes is 1. If the third correspondence indicates that part of the SRS space related information corresponds to The closed loop power control process is 0, and the other SRS space related information corresponds to the closed loop power control process 1, and the number of closed loop power control processes is 2.
  • the terminal device When the uplink signal is SRS, if the terminal device does not configure the SRS space related information, or the third correspondence is not configured, determine that the number of closed loop power control processes associated with the uplink signal is 1;
  • the number of closed loop power control processes is 1.
  • the number of BWPs that send the uplink signal is: the number of BWPs that simultaneously send the uplink signal; or the number of currently activated uplink BWPs; or the number of uplink BWPs configured for the terminal device;
  • these BWPs may not be able to simultaneously transmit the uplink signal, and only one or a part of the BWPs may be used to transmit the uplink signal at the same time.
  • the terminal may send the uplink signal by using different BWPs at different times.
  • the method further includes determining that the number of bits of the TPC command field in the DCI is 2.
  • the DCI includes a TPC command field of the terminal. For example, before the terminal receives the number of BWPs configured on the network side or the number of closed loop power control processes associated with the uplink signal, the terminal assumes that the number of bits of the TPC command field in the DCI is 2.
  • the method includes determining that the number of bits in the TPC command field is 2*N or 2+ if the number of BWPs transmitting the uplink signal is N, or the number of closed loop power control processes associated with the uplink signal is N. Log2(N).
  • the DCI is at least one of: a DCI carrying a TPC command of a PUSCH; a DCI carrying a TPC command of a PUCCH; and a DCI of a TPC command carrying an SRS.
  • the format of the DCI may be: DCI format 2-2 or DCI format 2-3; and the DCI is scrambled by using PUSCH-TPC-RNTI or PUCCH-TPC-RNTI or SRS-TPC-RNTI. .
  • the DCI can be used to indicate a TPC command on a BWP, and can also be used to indicate a TPC command on a different BWP.
  • the uplink signal is one of the following: PUSCH, PUCCH, and SRS.
  • the DCI format is DCI format 2-2, and is scrambled by PUSCH-TPC-RNTI or PUCCH-TPC-RNTI; if the uplink signal is SRS, then The DCI format is DCI format 2-3 and is scrambled by SRS-TPC-RNTI.
  • the embodiment may further provide a processing method for further determining the TPC command domain.
  • the method may further include: indicating a TPC command location index to the terminal device, so that the terminal device is based on the TPC command location and the TPC command. The number of bits in the domain from which the TPC command field is determined.
  • the method for obtaining a TPC command location index may be: the TPC command location index indicated by the network device by using RRC signaling; wherein the TPC command location index is used to indicate that the TPC command domain of the terminal device is The starting bit in the DCI.
  • the location index may be in units of 1 bit, that is, the start bit of the TPC command field may be in any position in the DCI; or the location index may be in units of 2 bits, that is, from the TPC command field.
  • the start bit may be any even bit of the DCI bits (eg, the bit index is 0, 2, 4, ).
  • the TPC command location index includes a location index of at least one TPC command; wherein each TPC command corresponds to one BWP or a closed loop power control process corresponding to one BWP.
  • the TPC command field includes a location index of multiple TPC commands, each TPC command corresponds to a BWP or a closed loop power control process on a BWP, the network side may configure an independent location index for the multiple TPC commands. That is, the network side can independently configure the TPC command location index for each BWP or each closed-loop power control process.
  • the kth location index corresponds to the TPC command of the kth BWP or the kth closed loop power control process.
  • the TPC command field occupies consecutive bits in the DCI. For example, if the TPC command field contains 2 TPC commands, then the two TPC commands are two consecutive TPC commands in the DCI.
  • the TPC command location index indicates the kth bit, and the number of bits in the TPC command field is M, and the bit occupied by the TPC command field of the terminal is the ⁇ k, k+1, ..., k in the DCI. +M-1 ⁇ bits.
  • the method for determining the transmission power of the uplink signal may be calculated based on any closed-loop power adjustment factor, and the manner of calculation is not described herein.
  • the corresponding TPC command can be determined according to the number of uplink signal BWPs or the number of closed loop power control processes, and the power adjustment factor corresponding to the uplink signal is determined according to the TPC command, thereby reducing the terminal as much as possible.
  • the DCI overhead of the TPC command saves unnecessary DCI overhead, and performs closed-loop power control of more terminals and more BWPs through one DCI.
  • An embodiment of the present invention provides a terminal device, as shown in FIG. 3, including:
  • the first processing unit 31 determines, according to the number of bandwidth portions BWP that transmit the uplink signal, or the number of closed-loop power control processes associated with the uplink signal, the bit of the transmission power control TPC command field of the terminal device in the downlink control information DCI. And determining, according to the TPC command in the TPC command domain, a closed loop power adjustment factor for transmitting at least one BWP of the uplink signal or at least one closed loop power control process associated with the uplink signal.
  • the terminal device in this embodiment can be understood as a terminal having a communication function in a communication system, such as a mobile phone or the like.
  • the first processing unit 31 may perform at least one of the following:
  • the uplink signal is a PUCCH
  • the uplink signal is an SRS
  • the first processing unit 31 determines, according to the uplink signal, an exemption type or a scheduling type, the number of closed loop power control processes associated with the uplink signal; for example, based on grant-free (terminal autonomous transmission)
  • the uplink signal is still based on the scheduled uplink signal, and the corresponding number is determined based on this type.
  • the number of closed loop power control processes associated with the grant-free uplink signal is 1; the number of closed loop power control processes based on the scheduling association is 2 or the value configured on the network side;
  • the terminal device configures at least one BWP, determine the number of closed loop power control processes for each BWP according to the transmission type on each BWP in the at least one BWP; wherein at least one can be understood as one of course, and more .
  • the number of closed loop power control processes associated with the uplink signal determined according to the high layer signaling configuration may be independently configured for the PUSCH and the PUCCH. If the terminal is configured with multiple BWPs, the network side can configure the number of closed loop power control processes for each BWP.
  • the first processing unit 31 uses the total number of closed-loop power control processes included in all BWPs that send the uplink signal as the number of closed-loop power control processes associated with the uplink signal.
  • the number of the BWPs that send the uplink signal may be one of: the number of BWPs that simultaneously send the uplink signal; the number of currently activated uplink BWPs; and the number of uplink BWPs that the network side configures for the terminal.
  • these BWPs may not be used to simultaneously transmit the uplink signal, and only one or a part of the BWPs may be used to transmit the uplink signal at the same time.
  • the terminal may send the uplink signal by using different BWPs at different times.
  • the first processing unit 31 performs at least one of the following three types:
  • the first correspondence indicates that all SRI states correspond to the same closed-loop power control process, and the number of closed-loop power control processes is 1. If the correspondence indicates that part of the SRI state corresponds to the closed-loop power control process 0, The other SRI states correspond to the closed loop power control process 1, and the number of closed loop power control processes is two.
  • the terminal device When the uplink signal is a PUSCH, and the terminal device is not configured with the SRI, or the first correspondence is not configured, determining that the number of closed loop power control processes associated with the uplink signal is 1;
  • the terminal device When the uplink signal is a PUSCH, and the terminal device is not configured with the SRI, or the first correspondence is not configured, determining that the number of closed loop power control processes associated with the uplink signal is 1, that is, if the terminal does not have The SRI or the correspondence between the SRI state and the closed loop power control process is configured, and the number of closed loop power control processes is 1.
  • the terminal device configures at least one BWP, determining, according to the first correspondence of each BWP configuration in the at least one BWP, the number of closed loop power control processes associated with the uplink signal.
  • the terminal device Determining, according to the first correspondence of each BWP configuration in the at least one BWP, the number of closed loop power control processes associated with the uplink signal, that is, when the uplink signal is a PUSCH, and the terminal device is configured with at least one BWP, that is, If the terminal is configured with multiple BWPs, the number can be determined according to the corresponding relationship configured on each BWP.
  • the first correspondence relationship may be understood as a correspondence between the SRI state and the closed-loop power control process, where the SRI is an SRS resource indicator (SRS Resource Indicator), and the acquiring manner may be performed by scheduling
  • the DCI of the PUSCH carries the SRI.
  • the number of closed-loop power control processes associated with the uplink signal that is, if the uplink signal is a PUCCH, according to the high-layer signaling, when the uplink signal is a PUCCH
  • the correspondence between the configured PUCCH spatial correlation information (PUCCH-SpatialRelationInfo) and the closed loop power control process determines the number of different closed loop power control processes included in the correspondence. Specifically, it may include:
  • the first processing unit 31 can perform at least one of the following three situations:
  • the terminal may determine, by the number of different closed loop power control processes included in the second correspondence, the number of closed loop power control processes associated with the uplink signal;
  • the correspondence indicates that all PUCCH spatial related information corresponds to the same closed loop power control process, and the number of closed loop power control processes is 1; if the second correspondence indicates that the partial PUCCH spatial correlation information corresponds to closed loop power Control process 0, other PUCCH space related information corresponds to closed loop power control process 1, then the number of closed loop power control processes is 2.
  • the terminal device When the uplink signal is a PUCCH, if the terminal device does not configure the PUCCH space related information, or the second correspondence is not configured, determine that the number of closed loop power control processes associated with the uplink signal is 1. ;
  • the number of closed loop power control processes is 1;
  • a first processing unit 31 when the uplink signal is a PUCCH, and the terminal device configures at least one BWP, determining, according to a second correspondence relationship configured on each BWP in the at least one BWP, a closed loop of the uplink signal association
  • the number of power control processes That is to say, if the terminal is configured with multiple BWPs, the number can be determined according to the second correspondence configured on each BWP.
  • the first processing unit 31 can perform at least one of the following three situations:
  • the terminal may determine the number of different closed loop power control processes included in the third correspondence as the number of closed loop power control processes associated with the uplink signal.
  • the third correspondence indicates that all SRS spatial related information corresponds to the same closed loop power control process, and the number of closed loop power control processes is 1. If the third correspondence indicates that part of the SRS space related information corresponds to The closed loop power control process is 0, and the other SRS space related information corresponds to the closed loop power control process 1, and the number of closed loop power control processes is 2.
  • the terminal device When the uplink signal is SRS, if the terminal device does not configure the SRS space related information, or the third correspondence is not configured, determine that the number of closed loop power control processes associated with the uplink signal is 1;
  • the number of closed loop power control processes is 1.
  • a first processing unit 31 when the uplink signal is an SRS, and the terminal device configures at least one BWP, determining, according to a third correspondence relationship configured on each BWP in the at least one BWP, a closed loop of the uplink signal association
  • the number of power control processes that is, if the terminal is configured with multiple BWPs, the number can be determined according to the corresponding relationship configured on each BWP.
  • the number of BWPs that send the uplink signal is the number of BWPs that simultaneously send the uplink signal, or the number of uplink BWPs that are currently activated, or the number of uplink BWPs that the network side configures for the terminal; for the latter two cases, these BWPs It is not always possible to transmit the uplink signal at the same time, and only one or a part of the BWPs can be used to transmit the uplink signal at the same time.
  • the terminal may send the uplink signal by using different BWPs at different times.
  • the method further includes determining that the number of bits of the TPC command field in the DCI is 2.
  • the DCI includes a TPC command field of the terminal. For example, before the terminal receives the number of BWPs configured on the network side or the number of closed loop power control processes associated with the uplink signal, the terminal assumes that the number of bits of the TPC command field in the DCI is 2.
  • the number of BWPs for transmitting the uplink signal is N, or the number of closed loop power control processes associated with the uplink signal is N, determining that the number of bits in the TPC command field is 2*N or 2+log2(N) .
  • the DCI is at least one of: a DCI carrying a TPC command of a PUSCH; a DCI carrying a TPC command of a PUCCH; and a DCI of a TPC command carrying an SRS.
  • the format of the DCI may be: DCI format 2-2 or DCI format 2-3; and the DCI is scrambled by using PUSCH-TPC-RNTI or PUCCH-TPC-RNTI or SRS-TPC-RNTI. .
  • the DCI can be used to indicate a TPC command on a BWP, and can also be used to indicate a TPC command on a different BWP.
  • the uplink signal is one of the following: PUSCH, PUCCH, and SRS.
  • the DCI format is DCI format 2-2, and is scrambled by PUSCH-TPC-RNTI or PUCCH-TPC-RNTI; if the uplink signal is SRS, then The DCI format is DCI format 2-3 and is scrambled by SRS-TPC-RNTI.
  • the embodiment may further provide a processing method for further determining the TPC command domain.
  • the method may further include: according to the TPC command location index indicated by the network side, and the number of bits of the TPC command domain, from the DCI. Determining a TPC command field of the terminal device.
  • the method for how to obtain a location index of a TPC command further includes:
  • the first communication unit 32 receives the TPC command location index indicated by the RRC signaling on the network side;
  • the TPC command location index indicated by the RRC signaling is used to indicate a start bit of the TPC command domain of the terminal device in the DCI.
  • the location index may be in units of 1 bit, that is, the start bit of the TPC command field may be in any position in the DCI; or the location index may be in units of 2 bits, that is, from the TPC command field.
  • the start bit may be any even bit of the DCI bits (eg, the bit index is 0, 2, 4, ).
  • the TPC command location index includes a location index of at least one TPC command; wherein each TPC command corresponds to one BWP or a closed loop power control process corresponding to one BWP.
  • the TPC command field includes a location index of multiple TPC commands, and each TPC command corresponds to a BWP or a closed loop power control process on a BWP, the network side may configure an independent location index for the multiple TPC commands. That is, the network side can independently configure the TPC command location index for each BWP or each closed-loop power control process.
  • the kth location index corresponds to the TPC command of the kth BWP or the kth closed loop power control process.
  • the TPC command field occupies consecutive bits in the DCI. For example, if the TPC command field contains 2 TPC commands, then the two TPC commands are two consecutive TPC commands in the DCI.
  • the TPC command location index indicates the kth bit, and the number of bits in the TPC command field is M, and the bit occupied by the TPC command field of the terminal is the ⁇ k, k+1, ..., k in the DCI. +M-1 ⁇ bits.
  • the TPC command field is 2*N bits, it includes N 2-bit TPC commands, and the nth TPC command is used for the nth BWP or the nth closed-loop power control process; if the TPC command field is 2+log2(N) bits, the first two bits are TPC commands, followed by log2(N) bits indicating the BWP or closed-loop power control process corresponding to the TPC command, or the last two bits are TPC commands, pre-log2 ( N) bits indicate the BWP or closed loop power control process corresponding to the TPC command.
  • the first communication unit sends the uplink signal according to the determined transmit power
  • the first processing unit determines the transmit power of the uplink signal according to a closed loop power adjustment factor of the BWP currently transmitting the uplink signal or a closed loop power adjustment factor of the closed loop power control process currently used by the uplink signal.
  • the corresponding TPC command can be determined according to the number of uplink signal BWPs or the number of closed loop power control processes, and the power adjustment factor corresponding to the uplink signal is determined according to the TPC command, thereby reducing the terminal as much as possible.
  • the DCI overhead of the TPC command saves unnecessary DCI overhead, and performs closed-loop power control of more terminals and more BWPs through one DCI.
  • An embodiment of the present invention provides a network device, as shown in FIG. 4, including:
  • the second processing unit 41 determines, according to the number of bandwidth portions BWP that transmit the uplink signal, or the number of closed loop power control processes associated with the uplink signal, the number of bits of the transmission power control TPC command field of the terminal device in the downlink control information DCI;
  • the second communication unit 42 sends the TPC command field to the terminal device by using the DCI.
  • the terminal device in this embodiment can be understood as a terminal having a communication function in a communication system, such as a mobile phone or the like.
  • the second processing unit 41 performs at least one of the following:
  • the uplink signal is a PUCCH
  • the uplink signal is an SRS
  • the second processing unit 41 determines, according to the uplink signal, an exemption type or a scheduling type, the number of closed loop power control processes associated with the uplink signal; for example, based on grant-free (terminal autonomous transmission)
  • the uplink signal is still based on the scheduled uplink signal, and the corresponding number is determined based on this type.
  • the number of closed loop power control processes associated with the grant-free uplink signal is 1; the number of closed loop power control processes based on the scheduling association is 2 or the value configured on the network side;
  • the terminal device configures at least one BWP, determine the number of closed loop power control processes for each BWP according to the transmission type on each BWP in the at least one BWP; wherein at least one can be understood as one of course, and more .
  • the foregoing determines the number of closed loop power control processes associated with the uplink signal according to the high layer signaling configuration, and may independently configure the number for the PUSCH and the PUCCH. If the terminal is configured with multiple BWPs, the network side can configure the number of closed loop power control processes for each BWP.
  • the second processing unit 41 uses the total number of closed loop power control processes included in all BWPs transmitting the uplink signal as the number of closed loop power control processes associated with the uplink signal.
  • the number of the BWPs that send the uplink signal may be one of: the number of BWPs that simultaneously send the uplink signal; the number of currently activated uplink BWPs; and the number of uplink BWPs that the network side configures for the terminal.
  • these BWPs may not be used to simultaneously transmit the uplink signal, and only one or a part of the BWPs may be used to transmit the uplink signal at the same time.
  • the terminal may send the uplink signal by using different BWPs at different times.
  • the second processing unit 41 performs at least one of the following three types:
  • the first correspondence indicates that all SRI states correspond to the same closed-loop power control process, and the number of closed-loop power control processes is 1. If the correspondence indicates that part of the SRI state corresponds to the closed-loop power control process 0, The other SRI states correspond to the closed loop power control process 1, and the number of closed loop power control processes is two.
  • the terminal device When the uplink signal is a PUSCH, and the terminal device is not configured with the SRI, or the first correspondence is not configured, determining that the number of closed loop power control processes associated with the uplink signal is 1;
  • the terminal device When the uplink signal is a PUSCH, and the terminal device is not configured with the SRI, or the first correspondence is not configured, determining that the number of closed loop power control processes associated with the uplink signal is 1, that is, if the terminal does not have The SRI or the correspondence between the SRI state and the closed loop power control process is configured, and the number of closed loop power control processes is 1.
  • the terminal device configures at least one BWP, determining, according to the first correspondence of each BWP configuration in the at least one BWP, the number of closed loop power control processes associated with the uplink signal.
  • the terminal device Determining, according to the first correspondence of each BWP configuration in the at least one BWP, the number of closed loop power control processes associated with the uplink signal, that is, when the uplink signal is a PUSCH, and the terminal device is configured with at least one BWP, that is, If the terminal is configured with multiple BWPs, the number can be determined according to the corresponding relationship configured on each BWP.
  • the first correspondence relationship may be understood as a correspondence between the SRI state and the closed-loop power control process, where the SRI is an SRS resource indicator (SRS Resource Indicator), and the acquiring manner may be performed by scheduling
  • the DCI of the PUSCH carries the SRI.
  • the number of closed-loop power control processes associated with the uplink signal that is, if the uplink signal is a PUCCH, according to the high-layer signaling, when the uplink signal is a PUCCH
  • the correspondence between the configured PUCCH spatial correlation information (PUCCH-SpatialRelationInfo) and the closed loop power control process determines the number of different closed loop power control processes included in the correspondence. Specifically, it may include:
  • the second processing unit 41 can perform at least one of the following three situations:
  • the terminal may determine, by the number of different closed loop power control processes included in the second correspondence, the number of closed loop power control processes associated with the uplink signal;
  • the correspondence indicates that all PUCCH spatial related information corresponds to the same closed loop power control process, and the number of closed loop power control processes is 1; if the second correspondence indicates that the partial PUCCH spatial correlation information corresponds to closed loop power Control process 0, other PUCCH space related information corresponds to closed loop power control process 1, then the number of closed loop power control processes is 2.
  • the terminal device When the uplink signal is a PUCCH, if the terminal device does not configure the PUCCH space related information, or the second correspondence is not configured, determine that the number of closed loop power control processes associated with the uplink signal is 1. ;
  • the number of closed loop power control processes is 1;
  • a second processing unit 41 when the uplink signal is a PUCCH, and the terminal device configures at least one BWP, determining a closed loop of the uplink signal association according to a second correspondence relationship configured on each BWP in the at least one BWP The number of power control processes. That is to say, if the terminal is configured with multiple BWPs, the number can be determined according to the second correspondence configured on each BWP.
  • the second processing unit 41 can perform at least one of the following three situations:
  • the terminal may determine the number of different closed loop power control processes included in the third correspondence as the number of closed loop power control processes associated with the uplink signal.
  • the third correspondence indicates that all SRS spatial related information corresponds to the same closed loop power control process, and the number of closed loop power control processes is 1. If the third correspondence indicates that part of the SRS space related information corresponds to The closed loop power control process is 0, and the other SRS space related information corresponds to the closed loop power control process 1, and the number of closed loop power control processes is 2.
  • the terminal device When the uplink signal is SRS, if the terminal device does not configure the SRS space related information, or the third correspondence is not configured, determine that the number of closed loop power control processes associated with the uplink signal is 1;
  • the number of closed loop power control processes is 1.
  • a second processing unit 41 when the uplink signal is an SRS, and the terminal device configures at least one BWP, determining a closed loop of the uplink signal association according to a third correspondence relationship configured on each BWP in the at least one BWP
  • the number of power control processes that is, if the terminal is configured with multiple BWPs, the number can be determined according to the corresponding relationship configured on each BWP.
  • the number of BWPs that send the uplink signal is the number of BWPs that simultaneously send the uplink signal, or the number of uplink BWPs that are currently activated, or the number of uplink BWPs that the network side configures for the terminal; for the latter two cases, these BWPs It is not always possible to transmit the uplink signal at the same time, and only one or a part of the BWPs can be used to transmit the uplink signal at the same time.
  • the terminal may send the uplink signal by using different BWPs at different times.
  • the method further includes determining that the number of bits of the TPC command field in the DCI is 2.
  • the DCI includes a TPC command field of the terminal. For example, before the terminal receives the number of BWPs configured on the network side or the number of closed loop power control processes associated with the uplink signal, the terminal assumes that the number of bits of the TPC command field in the DCI is 2.
  • the number of BWPs for transmitting the uplink signal is N, or the number of closed loop power control processes associated with the uplink signal is N, determining that the number of bits in the TPC command field is 2*N or 2+log2(N) .
  • the DCI is at least one of: a DCI carrying a TPC command of a PUSCH; a DCI carrying a TPC command of a PUCCH; and a DCI of a TPC command carrying an SRS.
  • the format of the DCI may be: DCI format 2-2 or DCI format 2-3; and the DCI is scrambled by using PUSCH-TPC-RNTI or PUCCH-TPC-RNTI or SRS-TPC-RNTI. .
  • the DCI can be used to indicate a TPC command on a BWP, and can also be used to indicate a TPC command on a different BWP.
  • the uplink signal is one of the following: PUSCH, PUCCH, and SRS.
  • the DCI format is DCI format 2-2, and is scrambled by PUSCH-TPC-RNTI or PUCCH-TPC-RNTI; if the uplink signal is SRS, then The DCI format is DCI format 2-3 and is scrambled by SRS-TPC-RNTI.
  • the embodiment may further provide a processing method for further determining the TPC command domain.
  • the method may further include: indicating a TPC command location index to the terminal device, so that the terminal device is based on the TPC command location and the TPC command. The number of bits in the domain from which the TPC command field is determined.
  • the method for obtaining a TPC command location index may be: the TPC command location index indicated by the network device by using RRC signaling; wherein the TPC command location index is used to indicate that the TPC command domain of the terminal device is The starting bit in the DCI.
  • the location index may be in units of 1 bit, that is, the start bit of the TPC command field may be in any position in the DCI; or the location index may be in units of 2 bits, that is, from the TPC command field.
  • the start bit may be any even bit of the DCI bits (eg, the bit index is 0, 2, 4, ).
  • the TPC command location index includes a location index of at least one TPC command; wherein each TPC command corresponds to one BWP or a closed loop power control process corresponding to one BWP.
  • the TPC command field includes a location index of multiple TPC commands, and each TPC command corresponds to a BWP or a closed loop power control process on a BWP, the network side may configure an independent location index for the multiple TPC commands. That is, the network side can independently configure the TPC command location index for each BWP or each closed-loop power control process.
  • the kth location index corresponds to the TPC command of the kth BWP or the kth closed loop power control process.
  • the TPC command field occupies consecutive bits in the DCI. For example, if the TPC command field contains 2 TPC commands, then the two TPC commands are two consecutive TPC commands in the DCI.
  • the TPC command location index indicates the kth bit, and the number of bits in the TPC command field is M, and the bit occupied by the TPC command field of the terminal is the ⁇ k, k+1, ..., k in the DCI. +M-1 ⁇ bits.
  • the second processing unit 41 determines, according to the closed loop power adjustment factor of the BWP that the current terminal device sends the uplink signal, or the closed loop power adjustment factor of the closed loop power control process currently used by the terminal device to send the uplink signal, to determine the uplink of the terminal device.
  • the second communication unit 41 receives the uplink signal sent by the terminal device according to the determined transmit power.
  • the corresponding TPC command can be determined according to the number of uplink signal BWPs or the number of closed loop power control processes, and the power adjustment factor corresponding to the uplink signal is determined according to the TPC command, thereby reducing the terminal as much as possible.
  • the DCI overhead of the TPC command saves unnecessary DCI overhead, and performs closed-loop power control of more terminals and more BWPs through one DCI.
  • the embodiment of the present invention further provides a terminal device, or a hardware component architecture of the network device.
  • the method includes at least one processor 51, a memory 52, and at least one network interface 53.
  • the various components are coupled together by a bus system 54.
  • bus system 54 is used to implement connection communication between these components.
  • the bus system 54 includes, in addition to the data bus, a power bus, a control bus, and a status signal bus.
  • various buses are labeled as bus system 54 in FIG.
  • the memory 52 in the embodiments of the present invention may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • memory 52 stores elements, executable modules or data structures, or a subset thereof, or their extension set:
  • the processor 51 is configured to be able to process the method steps of the first embodiment or the second embodiment, and details are not described herein.
  • Embodiments of the Invention may be stored in a computer readable storage medium if it is implemented in the form of a software function module and sold or used as a standalone product. Based on such understanding, the technical solution of the embodiments of the present invention may be embodied in the form of a software product in essence or in the form of a software product stored in a storage medium, including a plurality of instructions.
  • a computer device (which may be a personal computer, server, or network device, etc.) is caused to perform all or part of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read only memory (ROM), a magnetic disk, or an optical disk.
  • embodiments of the invention are not limited to any specific combination of hardware and software.
  • a computer storage medium is provided by the embodiment of the present invention.
  • the computer storage medium stores computer executable instructions. When the computer executable instructions are executed, the method steps of the first embodiment or the second embodiment are implemented.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Power Engineering (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明公开了一种上行功率控制方法、终端设备、网络设备及计算机存储介质，其中方法包括：根据发送上行信号的带宽部分BWP的数量、或者、根据上行信号关联的闭环功率控制进程的数量，确定下行控制信息DCI中所述终端设备的发送功率控制TPC命令域的比特数；根据所述TPC命令域中的TPC命令，确定发送所述上行信号的至少一个BWP或者所述上行信号关联的至少一个闭环功率控制进程的闭环功率调整因子。

Description

一种上行功率控制方法、终端设备及网络设备 技术领域
本发明涉及信息处理技术领域，尤其涉及一种上行功率控制方法、终端设备、网络设备及计算机存储介质。
背景技术
目前PUSCH的发送功率可以通过如下公式计算：
Figure PCTCN2018083092-appb-000001
其中，i表示一次PUSCH传输的索引，j为开环功率控制参数的索引，P O_PUSCH,f,c(j)和α f,c(j)是开环功率控制参数，PL f,c(q d)是基于下行参考信号进行测量得到的路损估计值，f f,c(i,l)是闭环功率调整因子，l是闭环功率控制进程的索引。其中，j,l的取值和用于测量路损估计值PL f,c(q d)的下行参考信号可以基于DCI中包含的SRI(SRS Resource Indicator，SRS资源指示信息)信息得到。网络侧预先配置不同的SRI状态和{j,qd,l}的对应关系，再通过SRI来指示当前传输所使用的{j,qd,l}。
对于PUCCH，网络侧会预先配置不同的PUCCH空间相关信息(PUCCH-Spatial relation Info)和{j,qd,l}的对应关系，再通过当前使用的PUCCH空间相关信息来确定当前PUCCH传输所使用的{j,qd,l}。其中，网络侧通过RRC信令指示所有可用的PUCCH空间相关信息，再通过MAC CE指示当前使用的PUCCH空间相关信息。
对于PUSCH和PUCCH，可以通过专门用于携带发送功率控制(TPC)命令的专用下行控制信息(DCI)来获得TPC命令，从而确定闭环功率调整因子。其中，所述DCI采用DCI格式2-2，使用PUSCH-TPC-RNTI或者PUCCH-TPC-RNTI进行加扰，可以包含多个终端的TPC命令。在NR中，PUSCH和PUCCH可能在多个BWP上同时传输，且都可以支持多个闭环功率控制进程，此时终端如何获得每个BWP上的每个闭环功率控制进程各自的TPC命令是个需要解决的问题。
发明内容
为解决上述技术问题，本发明实施例提供了一种上行功率控制方法、终端设备、网络设备及计算机存储介质。
本发明实施例提供一种上行功率控制方法，应用于终端设备，所述方法包括：
根据发送上行信号的带宽部分BWP的数量、或者、根据上行信号关联的闭环功率控制进程的数量，确定下行控制信息DCI中所述终端设备的发送功率控制TPC命令域的比特数；
根据所述TPC命令域中的TPC命令，确定发送所述上行信号的至少一个BWP或者所述上行信号关联的至少一个闭环功率控制进程的闭环功率调整因子。
本发明实施例提供一种上行功率控制方法，应用于网络设备，所述方法包括：
根据发送上行信号的带宽部分BWP的数量、或者、根据上行信号关联的闭环功率控制进程的数量，确定下行控制信息DCI中终端设备的发送功率控制TPC命令域的比特数；
通过所述DCI向所述终端设备发送所述TPC命令域。
本发明实施例提供一种终端设备，所述终端设备包括：
第一处理单元，根据发送上行信号的带宽部分BWP的数量、或者、根据上行信号关联的闭环功率控制进程的数量，确定下行控制信息DCI中所述终端设备的发送功率控制TPC命令域的比特数；
根据所述TPC命令域中的TPC命令，确定发送所述上行信号的至少一个BWP或者所述上行信号关联的至少一个闭环功率控制进程的闭环功率调整因子。
本发明实施例提供一种网络设备，包括：
第二处理单元，根据发送上行信号的带宽部分BWP的数量、或者、根据上行信号关联的闭环功率控制进程的数量，确定下行控制信息DCI中终端设备的发送功率控制TPC命令域的比特数；
第二通信单元，通过所述DCI向所述终端设备发送所述TPC命令域。
本发明实施例提供的一种终端设备，包括：处理器和用于存储能够在处理器上运行的计算机程序的存储器，
其中，所述处理器用于运行所述计算机程序时，执行前述方法的步骤。
本发明实施例提供的一种网络设备，包括：处理器和用于存储能够在处理器上运行的计算机程序的存储器，
其中，所述处理器用于运行所述计算机程序时，执行前述方法的步骤。
本发明实施例提供的一种计算机存储介质，所述计算机存储介质存储有计算机可执行指令，所述计算机可执行指令被执行时实现前述方法步骤。
本发明实施例的技术方案，就能够根据上行信号BWP的数量或者闭环功率控制进程的数量，确定对应的TPC命令，并根据TPC命令确定上行信号对应的功率调整因子，从而，尽可能降低一个终端的TPC命令的DCI开销，节约不必要的DCI开销，通过一个DCI进行更多终端和更多BWP的闭环功率控制。
附图说明
图1为本发明实施例提供的一种上行功率控制方法流程示意图1；
图2为本发明实施例提供的一种上行功率控制方法流程示意图2；
图3为本发明实施例终端设备组成结构示意图；
图4为本发明实施例网络设备组成结构示意图；
图5为本发明实施例的一种硬件架构示意图。
具体实施方式
为了能够更加详尽地了解本发明实施例的特点与技术内容，下面结合附图对本发明实施例的实现进行详细阐述，所附附图仅供参考说明之用，并非用来限定本发明实施例。
实施例一、
本发明实施例提供了一种上行功率控制方法，应用于终端设备，如图1所示，包括：
步骤101：根据发送上行信号的带宽部分BWP的数量、或者、根据上行信号关联的闭环功率控制进程的数量，确定下行控制信息DCI中所述终端设备的发送功率控制TPC命令域的比特数；
步骤102：根据所述TPC命令域中的TPC命令，确定发送所述上行信号的至少一个BWP或者所述上行信号关联的至少一个闭环功率控制进程的闭环功率调整因子。
本实施例中所述终端设备可以理解为通信系统中具备通信功能的终端，比如，手机等。
上述步骤101中，关于如何确定上行信号关联的闭环功率控制进程的数量的方法，可以包括以下至少之一：
根据所述上行信号当前的传输类型确定所述上行信号关联的闭环功率控制进程的数量；也就是说，根据当前上行信号的传输类型确定。
根据高层信令配置确定所述上行信号关联的闭环功率控制进程的数量；
根据发送所述上行信号的BWP的数量以及发送所述上行信号的各个BWP上的闭环功率控制进程的数量，确定所述上行信号关联的闭环功率控制进程的数量；
当所述上行信号为PUSCH时，根据高层信令配置的第一对应关系确定所述上行信号关联的闭环功率控制进程的数量，其中，所述第一对应关系为SRI状态和闭环功率控制进程的对应关系；
当所述上行信号为PUCCH时，根据高层信令配置的第二对应关系确定所述上行信号关联的闭环功率控制进程的数量，其中，所述第二对应关系为PUCCH空间相关信息和闭环功率控制进程的对应关系；
当所述上行信号为SRS时，根据高层信令配置的第三对应关系确定所述上行信号关联的闭环功率控制进程的数量，其中，所述第三对应关系为SRS空间相关信息和闭环功率控制进程的对应关系。
进一步，所述根据当前上行信号的传输类型确定所述上行信号关联的闭环功率控制进程的数量，包括：
基于所述上行信号为免授权类型或基于调度类型，确定所述上行信号关联的闭环功率控制进程的数量；比如，是基于grant-free(终端自主发送)的上行信号还是基于调度的上行信号，基于这种类型来确定对应的数量。例如，基于grant-free的上行信号关联的闭环功率控制进程的数量为1；基于调度的关联的闭环功率控制进程的数量为2或者网络侧配置的值。
和/或，
当所述终端设备配置至少一个BWP时，根据所述至少一个BWP中各个BWP上的传输类型为每一个BWP确定闭环功率控制进程的数量；其中，至少一个可以理解为一个当然还可以为更多。
上述根据高层信令配置确定所述上行信号关联的闭环功率控制进程的数量，可以为PUSCH和PUCCH独立配置数量。如果终端被配置了多个BWP，网络侧可以为各个BWP分别配置闭环功率控制进程的数量。
所述根据发送所述上行信号的BWP的数量以及各个上行信号的BWP上的闭环功率控制进程的数量，确定所述上行信号关联的闭环功率控制进程的数量，包括：将发送所述上行信号的所有BWP中包含的闭环功率控制进程的总数量，作为所述上行信号关联的闭环功率控制进程的数量。
即根据发送所述上行信号的BWP的数量及各个BWP上的闭环功率控制进程的数量确定。
具体来说，所述发送上行信号的BWP的数量可以为以下之一：同时发送所述上行信号的BWP的数量；当前激活的上行BWP的数量；网络侧为终端配置的上行BWP的数量。
需要指出的是，对于后两种情况，这些BWP不一定能够同时用于发送所述上行信号，同一时刻可以只有一个或部分BWP能用于发送所述上行信号。终端可以在不同时间采用不同BWP发送所述上行信号。
所述当所述上行信号为PUSCH时，根据高层信令配置的第一对应关系，确定所述上行信号关联的闭环功率控制进程的数量，包括以下三种情况至少一种：
情况1：
将所述第一对应关系中包含的不同闭环功率控制进程的数量，确定为所述上行信号关联的闭环功率控制进程的数量；
例如，所述第一对应关系指示了所有的SRI状态对应相同的一个闭环功率控制进程，则闭环功率控制进程的数量为1；如果所述对应关系指示了部分SRI状态对应闭环功率控制进程0，其他SRI状态对应闭环功率控制进程1，则闭环功率控制进程的数量为2。
情况2：
当所述上行信号为PUSCH、且所述终端设备未配置所述SRI、或者未配置所述第一对应关系时，确定所述上行信号关联的闭环功率控制进程的数量为1；
当所述上行信号为PUSCH、且所述终端设备未配置所述SRI、或者未配置所述第一对应关系时，确定所述上行信号关联的闭环功率控制进程的数量为1，即如果终端没有被配置SRI或者所述SRI状态和闭环功率控制进程的对应关系，则闭环功率控制进程的数量为1。
情况3：
当所述上行信号为PUSCH、且所述终端设备配置至少一个BWP时，根据所述至少一个BWP 中各个BWP配置的第一对应关系，确定所述上行信号关联的闭环功率控制进程的数量。
当所述上行信号为PUSCH、且所述终端设备配置至少一个BWP时，根据所述至少一个BWP中各个BWP配置的第一对应关系，确定所述上行信号关联的闭环功率控制进程的数量，即如果终端被配置了多个BWP，可以根据各个BWP上配置的对应关系分别确定数量。
需要说明的是，关于第一对应关系，可以理解为SRI状态和闭环功率控制进程之间的对应关系；其中，SRI为SRS资源指示信息(SRS Resource Indicator)，其获取方式可以通过调度所述PUSCH的DCI来携带SRI。
所述当所述上行信号为PUCCH时，根据高层信令配置的第二对应关系，确定所述上行信号关联的闭环功率控制进程的数量，即如果所述上行信号是PUCCH，可以根据高层信令配置的PUCCH空间相关信息(PUCCH-Spatial Relation Info)和闭环功率控制进程的对应关系确定。具体的，可以包括以下三种情况至少一种：
情况1：
终端可以将所述第二对应关系中包含的不同闭环功率控制进程的数量，确定为所述上行信号关联的闭环功率控制进程的数量；
例如，所述对应关系指示了所有的PUCCH空间相关信息对应相同的一个闭环功率控制进程，则闭环功率控制进程的数量为1；如果所述第二对应关系指示了部分PUCCH空间相关信息对应闭环功率控制进程0，其他PUCCH空间相关信息对应闭环功率控制进程1，则闭环功率控制进程的数量为2。
情况2：
当所述上行信号为PUCCH时，若所述终端设备未配置所述PUCCH空间相关信息、或者、未配置所述第二对应关系，则确定所述上行信号关联的闭环功率控制进程的数量为1；
如果终端没有被配置PUCCH空间相关信息或者PUCCH空间相关信息和闭环功率控制进程的第二对应关系，则闭环功率控制进程的数量为1；
情况3：
当所述上行信号为PUCCH、且所述终端设备配置至少一个BWP时，根据所述至少一个BWP中各个BWP上配置的第二对应关系，确定所述上行信号关联的闭环功率控制进程的数量。也就是说，如果终端被配置了多个BWP，可以根据各个BWP上配置的第二对应关系分别确定数量。
所述当所述上行信号为SRS时，根据高层信令配置的第三对应关系，确定所述上行信号关联的闭环功率控制进程的数量，即如果所述上行信号是SRS，可以根据高层信令配置的SRS空间相关信息(SRS-Spatial Relation Info)和闭环功率控制进程的对应关系确定。具体来说，可以包括以下三种情况中的至少一种：
情况一：
终端可以将所述第三对应关系中包含的不同闭环功率控制进程的数量，确定为所述上行信号关联的闭环功率控制进程的数量。
例如，所述第三对应关系指示了所有的SRS空间相关信息对应相同的一个闭环功率控制进程，则闭环功率控制进程的数量为1；如果所述第三对应关系指示了部分SRS空间相关信息对应闭环功率控制进程0，其他SRS空间相关信息对应闭环功率控制进程1，则闭环功率控制进程的数量为2。
情况二：
当所述上行信号为SRS时，若所述终端设备未配置所述SRS空间相关信息、或者未配置所述第三对应关系，则确定所述上行信号关联的闭环功率控制进程的数量为1；
即如果终端没有被配置SRS空间相关信息或者SRS空间相关信息和闭环功率控制进程的第三对应关系，则闭环功率控制进程的数量为1。
情况三：
当所述上行信号为SRS、且所述终端设备配置至少一个BWP时，根据所述至少一个BWP中各个BWP上配置的第三对应关系，确定所述上行信号关联的闭环功率控制进程的数量；也就是说，如果终端被配置了多个BWP，可以根据各个BWP上配置的对应关系分别确定数量。
所述发送上行信号的BWP的数量是同时发送所述上行信号的BWP的数量，或者当前激活的上行BWP的数量，或者网络侧为终端配置的上行BWP的数量；对于后两种情况，这些BWP不一定能够同时用于发送所述上行信号，同一时刻可以只有一个或部分BWP能用于发送所述上行信号。终端可以在不同时间采用不同BWP发送所述上行信号。
在确定发送上行信号的BWP的数量或所述上行信号关联的闭环功率控制进程的数量之前，所述方法还包括：确定所述DCI中的TPC命令域的比特数为2。具体的，该DCI中包含该终端的一个TPC命令域。例如，在终端接收到网络侧配置的BWP的数量或者所述上行信号关联的闭环功率控制进程的数量之前，终端假设所述DCI中的TPC命令域的比特数为2。
该方法包括，如果所述发送上行信号的BWP的数量为N、或所述上行信号关联的闭环功率控制进程的数量为N，则确定所述TPC命令域的比特数为2*N或2+log2(N)。
所述DCI为以下至少一：携带PUSCH的TPC命令的DCI；携带PUCCH的TPC命令的DCI；携带SRS的TPC命令的DCI。
需要说明的是，所述DCI的格式可以为：DCI format 2-2或DCI format 2-3；并且，所述DCI采用PUSCH-TPC-RNTI或者PUCCH-TPC-RNTI或SRS-TPC-RNTI加扰。所述DCI可以用于指示一个BWP上的TPC命令，也可以用于指示不同BWP上的TPC命令。
所述上行信号为以下之一：PUSCH、PUCCH、SRS。
具体的，如果所述上行信号为PUSCH或者PUCCH，则所述DCI格式为DCI format 2-2，且通过PUSCH-TPC-RNTI或者PUCCH-TPC-RNTI加扰；如果所述上行信号为SRS，则所述DCI格式为DCI format 2-3，且通过SRS-TPC-RNTI加扰。
基于上述方案，本实施例还可以提供进一步确定TPC命令域的处理方法，比如，还可以包括：根据网络侧指示的TPC命令位置索引、以及所述TPC命令域的比特数，从所述DCI中确定所述终端设备的TPC命令域。
关于如何获取TPC命令位置索引的方法，可以为：接收网络侧通过RRC信令指示的所述TPC命令位置索引；其中，所述TPC命令位置索引用于指示所述终端设备的TPC命令域在所述DCI中的起始比特。
具体的，所述位置索引可以以1比特为单位，即TPC命令域的起始比特可以在所述DCI中的任意位置；或者所述位置索引可以以2比特为单位，即TPC命令域的起始比特可以是所述DCI比特中的任意偶数比特(例如，比特索引为0,2,4,…)。
所述TPC命令位置索引中包含至少一个TPC命令的位置索引；其中，每一个TPC命令对应一个BWP或者对应一个BWP的一个闭环功率控制进程。如果所述TPC命令域包含多个TPC命令的位置索引，每个TPC命令对应一个BWP或者一个BWP上的一个闭环功率控制进程，则网络侧可以为所述多个TPC命令配置独立的位置索引。即网络侧可以为每个BWP或者每个闭环功率控制进程独立配置TPC命令位置索引。例如，第k个位置索引对应第k个BWP或者第k个闭环功率控制进程的TPC命令。
典型的，所述TPC命令域占用所述DCI中的连续比特位。例如，如果所述TPC命令域包含2个TPC命令，则这两个TPC命令为所述DCI中两个连续的TPC命令。
所述TPC命令位置索引指示了第k个比特，所述TPC命令域的比特数为M，则所述终端的TPC命令域占用的比特为DCI中的第{k,k+1,…,k+M-1}个比特。
上述步骤102中，如果所述TPC命令域为2*N比特，则其中包含N个2比特的TPC命令，第n个TPC命令用于第n个BWP或者第n个闭环功率控制进程；如果所述TPC命令域为2+log2(N)比特，则前两个比特为TPC命令，后面log2(N)个比特指示所述TPC命令对应的BWP或者闭环功率控制进程，或者后两个比特为TPC命令，前log2(N)个比特指示所述TPC命令对应的BWP或者闭环功率控制进程。
基于步骤102，本实施例还可以包括以下步骤：
根据当前发送所述上行信号的BWP的闭环功率调整因子、或者所述上行信号当前使用的闭环功率控制进程的闭环功率调整因子，确定所述上行信号的发送功率；根据确定的所述发送功率发送所 述上行信号。关于如何确定上行信号的发送功率的方法，可以为基于任意一种闭环功率调整因子进行计算，计算的方式这里不进行赘述。
可见，通过采用上述方案，就能够根据上行信号BWP的数量或者闭环功率控制进程的数量，确定对应的TPC命令，并根据TPC命令确定上行信号对应的功率调整因子，从而，尽可能降低一个终端的TPC命令的DCI开销，节约不必要的DCI开销，通过一个DCI进行更多终端和更多BWP的闭环功率控制。
实施例二、
本发明实施例提供了一种上行功率控制方法，应用于网络设备，如图2所示，所述方法包括：
步骤201：根据发送上行信号的带宽部分BWP的数量、或者、根据上行信号关联的闭环功率控制进程的数量，确定下行控制信息DCI中终端设备的发送功率控制TPC命令域的比特数；
步骤202：通过所述DCI向所述终端设备发送所述TPC命令域。
本实施例中所述终端设备可以理解为通信系统中具备通信功能的终端，比如，手机等。
上述关于如何确定上行信号关联的闭环功率控制进程的数量的方法，可以包括以下至少之一：
根据所述上行信号当前的传输类型确定所述上行信号关联的闭环功率控制进程的数量；也就是说，根据当前上行信号的传输类型确定。
根据高层信令配置确定所述上行信号关联的闭环功率控制进程的数量；
根据发送所述上行信号的BWP的数量以及发送所述上行信号的各个BWP上的闭环功率控制进程的数量，确定所述上行信号关联的闭环功率控制进程的数量；
当所述上行信号为PUSCH时，根据高层信令配置的第一对应关系确定所述上行信号关联的闭环功率控制进程的数量，其中，所述第一对应关系为SRI状态和闭环功率控制进程的对应关系；
当所述上行信号为PUCCH时，根据高层信令配置的第二对应关系确定所述上行信号关联的闭环功率控制进程的数量，其中，所述第二对应关系为PUCCH空间相关信息和闭环功率控制进程的对应关系；
当所述上行信号为SRS时，根据高层信令配置的第三对应关系确定所述上行信号关联的闭环功率控制进程的数量，其中，所述第三对应关系为SRS空间相关信息和闭环功率控制进程的对应关系。
进一步，所述根据当前上行信号的传输类型确定所述上行信号关联的闭环功率控制进程的数量，包括：
基于所述上行信号为免授权类型或基于调度类型，确定所述上行信号关联的闭环功率控制进程的数量；比如，是基于grant-free(终端自主发送)的上行信号还是基于调度的上行信号，基于这种类型来确定对应的数量。例如，基于grant-free的上行信号关联的闭环功率控制进程的数量为1；基于调度的关联的闭环功率控制进程的数量为2或者网络侧配置的值；
和/或，
当所述终端设备配置至少一个BWP时，根据所述至少一个BWP中各个BWP上的传输类型为每一个BWP确定闭环功率控制进程的数量；其中，至少一个可以理解为一个当然还可以为更多。
上述根据高层信令配置确定所述上行信号关联的闭环功率控制进程的数量，可以为PUSCH和PUCCH独立配置数量。如果终端被配置了多个BWP，网络侧可以为各个BWP分别配置闭环功率控制进程的数量。
所述根据发送所述上行信号的BWP的数量以及各个上行信号的BWP上的闭环功率控制进程的数量，确定所述上行信号关联的闭环功率控制进程的数量，包括：将发送所述上行信号的所有BWP中包含的闭环功率控制进程的总数量，作为所述上行信号关联的闭环功率控制进程的数量。
即根据发送所述上行信号的BWP的数量及各个BWP上的闭环功率控制进程的数量确定。
具体来说，所述发送上行信号的BWP的数量可以为以下之一：同时发送所述上行信号的BWP的数量；当前激活的上行BWP的数量；网络侧为终端配置的上行BWP的数量。
需要指出的是，对于后两种情况，这些BWP不一定能够同时用于发送所述上行信号，同一时刻可以只有一个或部分BWP能用于发送所述上行信号。终端可以在不同时间采用不同BWP发送所述上行信号。
所述当所述上行信号为PUSCH时，根据高层信令配置的第一对应关系，确定所述上行信号关联的闭环功率控制进程的数量，包括以下三种情况至少一种：
情况1：
将所述第一对应关系中包含的不同闭环功率控制进程的数量，确定为所述上行信号关联的闭环功率控制进程的数量；
例如，所述第一对应关系指示了所有的SRI状态对应相同的一个闭环功率控制进程，则闭环功率控制进程的数量为1；如果所述对应关系指示了部分SRI状态对应闭环功率控制进程0，其他SRI状态对应闭环功率控制进程1，则闭环功率控制进程的数量为2。
情况2：
当所述上行信号为PUSCH、且所述终端设备未配置所述SRI、或者未配置所述第一对应关系时，确定所述上行信号关联的闭环功率控制进程的数量为1；
当所述上行信号为PUSCH、且所述终端设备未配置所述SRI、或者未配置所述第一对应关系时，确定所述上行信号关联的闭环功率控制进程的数量为1，即如果终端没有被配置SRI或者所述SRI状态和闭环功率控制进程的对应关系，则闭环功率控制进程的数量为1。
情况3：
当所述上行信号为PUSCH、且所述终端设备配置至少一个BWP时，根据所述至少一个BWP中各个BWP配置的第一对应关系，确定所述上行信号关联的闭环功率控制进程的数量。
当所述上行信号为PUSCH、且所述终端设备配置至少一个BWP时，根据所述至少一个BWP中各个BWP配置的第一对应关系，确定所述上行信号关联的闭环功率控制进程的数量，即如果终端被配置了多个BWP，可以根据各个BWP上配置的对应关系分别确定数量。
需要说明的是，关于第一对应关系，可以理解为SRI状态和闭环功率控制进程之间的对应关系；其中，SRI为SRS资源指示信息(SRS Resource Indicator，)，其获取方式可以通过调度所述PUSCH的DCI来携带SRI。
所述当所述上行信号为PUCCH时，根据高层信令配置的第二对应关系，确定所述上行信号关联的闭环功率控制进程的数量，即如果所述上行信号是PUCCH，可以根据高层信令配置的PUCCH空间相关信息(PUCCH-Spatial Relation Info)和闭环功率控制进程的对应关系确定，该对应关系中包含的不同闭环功率控制进程的数量。具体的，可以包括以下三种情况至少一种：
情况1：
终端可以将所述第二对应关系中包含的不同闭环功率控制进程的数量，确定为所述上行信号关联的闭环功率控制进程的数量；
例如，所述对应关系指示了所有的PUCCH空间相关信息对应相同的一个闭环功率控制进程，则闭环功率控制进程的数量为1；如果所述第二对应关系指示了部分PUCCH空间相关信息对应闭环功率控制进程0，其他PUCCH空间相关信息对应闭环功率控制进程1，则闭环功率控制进程的数量为2。
情况2：
当所述上行信号为PUCCH时，若所述终端设备未配置所述PUCCH空间相关信息、或者、未配置所述第二对应关系，则确定所述上行信号关联的闭环功率控制进程的数量为1；
如果终端没有被配置PUCCH空间相关信息或者PUCCH空间相关信息和闭环功率控制进程的第二对应关系，则闭环功率控制进程的数量为1；
情况3：
当所述上行信号为PUCCH、且所述终端设备配置至少一个BWP时，根据所述至少一个BWP中各个BWP上配置的第二对应关系，确定所述上行信号关联的闭环功率控制进程的数量。也就是说，如果终端被配置了多个BWP，可以根据各个BWP上配置的第二对应关系分别确定数量。
所述当所述上行信号为SRS时，根据高层信令配置的第三对应关系，确定所述上行信号关联的闭环功率控制进程的数量，即如果所述上行信号是SRS，可以根据高层信令配置的SRS空间相关信息(SRS-Spatial Relation Info)和闭环功率控制进程的对应关系确定，该对应关系中包含的不同闭环 功率控制进程的数量。具体来说，可以包括以下三种情况中的至少一种：
情况一：
终端可以将所述第三对应关系中包含的不同闭环功率控制进程的数量，确定为所述上行信号关联的闭环功率控制进程的数量。
例如，所述第三对应关系指示了所有的SRS空间相关信息对应相同的一个闭环功率控制进程，则闭环功率控制进程的数量为1；如果所述第三对应关系指示了部分SRS空间相关信息对应闭环功率控制进程0，其他SRS空间相关信息对应闭环功率控制进程1，则闭环功率控制进程的数量为2。
情况二：
当所述上行信号为SRS时，若所述终端设备未配置所述SRS空间相关信息、或者未配置所述第三对应关系，则确定所述上行信号关联的闭环功率控制进程的数量为1；
即如果终端没有被配置SRS空间相关信息或者SRS空间相关信息和闭环功率控制进程的第三对应关系，则闭环功率控制进程的数量为1。
情况三：
当所述上行信号为SRS、且所述终端设备配置至少一个BWP时，根据所述至少一个BWP中各个BWP上配置的第三对应关系，确定所述上行信号关联的闭环功率控制进程的数量；也就是说，如果终端被配置了多个BWP，可以根据各个BWP上配置的对应关系分别确定数量。
所述发送上行信号的BWP的数量，为：同时发送所述上行信号的BWP的数量；或者，当前激活的上行BWP的数量；或者，为所述终端设备配置的上行BWP的数量；
对于后两种情况，这些BWP不一定能够同时用于发送所述上行信号，同一时刻可以只有一个或部分BWP能用于发送所述上行信号。终端可以在不同时间采用不同BWP发送所述上行信号。
在确定发送上行信号的BWP的数量或所述上行信号关联的闭环功率控制进程的数量之前，所述方法还包括：确定所述DCI中的TPC命令域的比特数为2。具体的，该DCI中包含该终端的一个TPC命令域。例如，在终端接收到网络侧配置的BWP的数量或者所述上行信号关联的闭环功率控制进程的数量之前，终端假设所述DCI中的TPC命令域的比特数为2。
该方法包括，如果所述发送上行信号的BWP的数量为N、或所述上行信号关联的闭环功率控制进程的数量为N，则确定所述TPC命令域的比特数为2*N或2+log2(N)。
所述DCI为以下至少一：携带PUSCH的TPC命令的DCI；携带PUCCH的TPC命令的DCI；携带SRS的TPC命令的DCI。
需要说明的是，所述DCI的格式可以为：DCI format 2-2或DCI format 2-3；并且，所述DCI采用PUSCH-TPC-RNTI或者PUCCH-TPC-RNTI或SRS-TPC-RNTI加扰。所述DCI可以用于指示一个BWP上的TPC命令，也可以用于指示不同BWP上的TPC命令。
所述上行信号为以下之一：PUSCH、PUCCH、SRS。
具体的，如果所述上行信号为PUSCH或者PUCCH，则所述DCI格式为DCI format 2-2，且通过PUSCH-TPC-RNTI或者PUCCH-TPC-RNTI加扰；如果所述上行信号为SRS，则所述DCI格式为DCI format 2-3，且通过SRS-TPC-RNTI加扰。
基于上述方案，本实施例还可以提供进一步确定TPC命令域的处理方法，比如，还可以包括：向终端设备指示TPC命令位置索引，以使终端设备基于所述TPC命令位置所以以及所述TPC命令域的比特数，从所述DCI中确定TPC命令域。
关于如何获取TPC命令位置索引的方法，可以为：所述网络设备通过RRC信令指示的所述TPC命令位置索引；其中，所述TPC命令位置索引用于指示所述终端设备的TPC命令域在所述DCI中的起始比特。
具体的，所述位置索引可以以1比特为单位，即TPC命令域的起始比特可以在所述DCI中的任意位置；或者所述位置索引可以以2比特为单位，即TPC命令域的起始比特可以是所述DCI比特中的任意偶数比特(例如，比特索引为0,2,4,…)。
所述TPC命令位置索引中包含至少一个TPC命令的位置索引；其中，每一个TPC命令对应一个BWP或者对应一个BWP的一个闭环功率控制进程。如果所述TPC命令域包含多个TPC命令的 位置索引，每个TPC命令对应一个BWP或者一个BWP上的一个闭环功率控制进程，则网络侧可以为所述多个TPC命令配置独立的位置索引。即网络侧可以为每个BWP或者每个闭环功率控制进程独立配置TPC命令位置索引。例如，第k个位置索引对应第k个BWP或者第k个闭环功率控制进程的TPC命令。
典型的，所述TPC命令域占用所述DCI中的连续比特位。例如，如果所述TPC命令域包含2个TPC命令，则这两个TPC命令为所述DCI中两个连续的TPC命令。
所述TPC命令位置索引指示了第k个比特，所述TPC命令域的比特数为M，则所述终端的TPC命令域占用的比特为DCI中的第{k,k+1,…,k+M-1}个比特。
本实施例还可以包括以下步骤：
根据当前终端设备发送所述上行信号的BWP的闭环功率调整因子、或者终端设备发送所述上行信号当前使用的闭环功率控制进程的闭环功率调整因子，确定终端设备上行信号的发送功率；根据确定的所述发送功率接收所述终端设备发来的所述上行信号。关于如何确定上行信号的发送功率的方法，可以为基于任意一种闭环功率调整因子进行计算，计算的方式这里不进行赘述。
可见，通过采用上述方案，就能够根据上行信号BWP的数量或者闭环功率控制进程的数量，确定对应的TPC命令，并根据TPC命令确定上行信号对应的功率调整因子，从而，尽可能降低一个终端的TPC命令的DCI开销，节约不必要的DCI开销，通过一个DCI进行更多终端和更多BWP的闭环功率控制。
实施例三、
本发明实施例提供了一种终端设备，如图3所示，包括：
第一处理单元31，根据发送上行信号的带宽部分BWP的数量、或者、根据上行信号关联的闭环功率控制进程的数量，确定下行控制信息DCI中所述终端设备的发送功率控制TPC命令域的比特数；根据所述TPC命令域中的TPC命令，确定发送所述上行信号的至少一个BWP或者所述上行信号关联的至少一个闭环功率控制进程的闭环功率调整因子。
本实施例中所述终端设备可以理解为通信系统中具备通信功能的终端，比如，手机等。
上述第一处理单元31，可以执行以下至少之一：
根据所述上行信号当前的传输类型确定所述上行信号关联的闭环功率控制进程的数量；也就是说，根据当前上行信号的传输类型确定。
根据高层信令配置确定所述上行信号关联的闭环功率控制进程的数量；
根据发送所述上行信号的BWP的数量以及发送所述上行信号的各个BWP上的闭环功率控制进程的数量，确定所述上行信号关联的闭环功率控制进程的数量；
当所述上行信号为PUSCH时，根据高层信令配置的第一对应关系确定所述上行信号关联的闭环功率控制进程的数量，其中，所述第一对应关系为SRI状态和闭环功率控制进程的对应关系；
当所述上行信号为PUCCH时，根据高层信令配置的第二对应关系确定所述上行信号关联的闭环功率控制进程的数量，其中，所述第二对应关系为PUCCH空间相关信息和闭环功率控制进程的对应关系；
当所述上行信号为SRS时，根据高层信令配置的第三对应关系确定所述上行信号关联的闭环功率控制进程的数量，其中，所述第三对应关系为SRS空间相关信息和闭环功率控制进程的对应关系。
进一步，所述第一处理单元31，基于所述上行信号为免授权类型或基于调度类型，确定所述上行信号关联的闭环功率控制进程的数量；比如，是基于grant-free(终端自主发送)的上行信号还是基于调度的上行信号，基于这种类型来确定对应的数量。例如，基于grant-free的上行信号关联的闭环功率控制进程的数量为1；基于调度的关联的闭环功率控制进程的数量为2或者网络侧配置的值；
和/或，
当所述终端设备配置至少一个BWP时，根据所述至少一个BWP中各个BWP上的传输类型为每一个BWP确定闭环功率控制进程的数量；其中，至少一个可以理解为一个当然还可以为更多。
上述根据高层信令配置确定所述上行信号关联的闭环功率控制进程的数量，可以为PUSCH和 PUCCH独立配置数量。如果终端被配置了多个BWP，网络侧可以为各个BWP分别配置闭环功率控制进程的数量。
所述第一处理单元31，将发送所述上行信号的所有BWP中包含的闭环功率控制进程的总数量，作为所述上行信号关联的闭环功率控制进程的数量。
即根据发送所述上行信号的BWP的数量及各个BWP上的闭环功率控制进程的数量确定。
具体来说，所述发送上行信号的BWP的数量可以为以下之一：同时发送所述上行信号的BWP的数量；当前激活的上行BWP的数量；网络侧为终端配置的上行BWP的数量。
需要指出的是，对于后两种情况，这些BWP不一定能够同时用于发送所述上行信号，同一时刻可以只有一个或部分BWP能用于发送所述上行信号。终端可以在不同时间采用不同BWP发送所述上行信号。
所述第一处理单元31执行以下三种至少之一：
情况1：
将所述第一对应关系中包含的不同闭环功率控制进程的数量，确定为所述上行信号关联的闭环功率控制进程的数量；
例如，所述第一对应关系指示了所有的SRI状态对应相同的一个闭环功率控制进程，则闭环功率控制进程的数量为1；如果所述对应关系指示了部分SRI状态对应闭环功率控制进程0，其他SRI状态对应闭环功率控制进程1，则闭环功率控制进程的数量为2。
情况2：
当所述上行信号为PUSCH、且所述终端设备未配置所述SRI、或者未配置所述第一对应关系时，确定所述上行信号关联的闭环功率控制进程的数量为1；
当所述上行信号为PUSCH、且所述终端设备未配置所述SRI、或者未配置所述第一对应关系时，确定所述上行信号关联的闭环功率控制进程的数量为1，即如果终端没有被配置SRI或者所述SRI状态和闭环功率控制进程的对应关系，则闭环功率控制进程的数量为1。
情况3：
当所述上行信号为PUSCH、且所述终端设备配置至少一个BWP时，根据所述至少一个BWP中各个BWP配置的第一对应关系，确定所述上行信号关联的闭环功率控制进程的数量。
当所述上行信号为PUSCH、且所述终端设备配置至少一个BWP时，根据所述至少一个BWP中各个BWP配置的第一对应关系，确定所述上行信号关联的闭环功率控制进程的数量，即如果终端被配置了多个BWP，可以根据各个BWP上配置的对应关系分别确定数量。
需要说明的是，关于第一对应关系，可以理解为SRI状态和闭环功率控制进程之间的对应关系；其中，SRI为SRS资源指示信息(SRS Resource Indicator，)，其获取方式可以通过调度所述PUSCH的DCI来携带SRI。
所述当所述上行信号为PUCCH时，根据高层信令配置的第二对应关系，确定所述上行信号关联的闭环功率控制进程的数量，即如果所述上行信号是PUCCH，可以根据高层信令配置的PUCCH空间相关信息(PUCCH-SpatialRelationInfo)和闭环功率控制进程的对应关系确定，该对应关系中包含的不同闭环功率控制进程的数量。具体的，可以包括：
第一处理单元31可以执行以下三种情况至少一种：
情况1：
终端可以将所述第二对应关系中包含的不同闭环功率控制进程的数量，确定为所述上行信号关联的闭环功率控制进程的数量；
例如，所述对应关系指示了所有的PUCCH空间相关信息对应相同的一个闭环功率控制进程，则闭环功率控制进程的数量为1；如果所述第二对应关系指示了部分PUCCH空间相关信息对应闭环功率控制进程0，其他PUCCH空间相关信息对应闭环功率控制进程1，则闭环功率控制进程的数量为2。
情况2：
当所述上行信号为PUCCH时，若所述终端设备未配置所述PUCCH空间相关信息、或者、未配 置所述第二对应关系，则确定所述上行信号关联的闭环功率控制进程的数量为1；
如果终端没有被配置PUCCH空间相关信息或者PUCCH空间相关信息和闭环功率控制进程的第二对应关系，则闭环功率控制进程的数量为1；
情况3：
第一处理单元31，当所述上行信号为PUCCH、且所述终端设备配置至少一个BWP时，根据所述至少一个BWP中各个BWP上配置的第二对应关系，确定所述上行信号关联的闭环功率控制进程的数量。也就是说，如果终端被配置了多个BWP，可以根据各个BWP上配置的第二对应关系分别确定数量。
所述当所述上行信号为SRS时，根据高层信令配置的第三对应关系，确定所述上行信号关联的闭环功率控制进程的数量，即如果所述上行信号是SRS，可以根据高层信令配置的SRS空间相关信息(SRS-Spatial Relation Info)和闭环功率控制进程的对应关系确定，该对应关系中包含的不同闭环功率控制进程的数量。具体来说，第一处理单元31可以执行以下三种情况中的至少一种：
情况一：
终端可以将所述第三对应关系中包含的不同闭环功率控制进程的数量，确定为所述上行信号关联的闭环功率控制进程的数量。
例如，所述第三对应关系指示了所有的SRS空间相关信息对应相同的一个闭环功率控制进程，则闭环功率控制进程的数量为1；如果所述第三对应关系指示了部分SRS空间相关信息对应闭环功率控制进程0，其他SRS空间相关信息对应闭环功率控制进程1，则闭环功率控制进程的数量为2。
情况二：
当所述上行信号为SRS时，若所述终端设备未配置所述SRS空间相关信息、或者未配置所述第三对应关系，则确定所述上行信号关联的闭环功率控制进程的数量为1；
即如果终端没有被配置SRS空间相关信息或者SRS空间相关信息和闭环功率控制进程的第三对应关系，则闭环功率控制进程的数量为1。
情况三：
第一处理单元31，当所述上行信号为SRS、且所述终端设备配置至少一个BWP时，根据所述至少一个BWP中各个BWP上配置的第三对应关系，确定所述上行信号关联的闭环功率控制进程的数量；也就是说，如果终端被配置了多个BWP，可以根据各个BWP上配置的对应关系分别确定数量。
所述发送上行信号的BWP的数量是同时发送所述上行信号的BWP的数量，或者当前激活的上行BWP的数量，或者网络侧为终端配置的上行BWP的数量；对于后两种情况，这些BWP不一定能够同时用于发送所述上行信号，同一时刻可以只有一个或部分BWP能用于发送所述上行信号。终端可以在不同时间采用不同BWP发送所述上行信号。
在确定发送上行信号的BWP的数量或所述上行信号关联的闭环功率控制进程的数量之前，所述方法还包括：确定所述DCI中的TPC命令域的比特数为2。具体的，该DCI中包含该终端的一个TPC命令域。例如，在终端接收到网络侧配置的BWP的数量或者所述上行信号关联的闭环功率控制进程的数量之前，终端假设所述DCI中的TPC命令域的比特数为2。
如果所述发送上行信号的BWP的数量为N、或所述上行信号关联的闭环功率控制进程的数量为N，则确定所述TPC命令域的比特数为2*N或2+log2(N)。
所述DCI为以下至少一：携带PUSCH的TPC命令的DCI；携带PUCCH的TPC命令的DCI；携带SRS的TPC命令的DCI。
需要说明的是，所述DCI的格式可以为：DCI format 2-2或DCI format 2-3；并且，所述DCI采用PUSCH-TPC-RNTI或者PUCCH-TPC-RNTI或SRS-TPC-RNTI加扰。所述DCI可以用于指示一个BWP上的TPC命令，也可以用于指示不同BWP上的TPC命令。
所述上行信号为以下之一：PUSCH、PUCCH、SRS。
具体的，如果所述上行信号为PUSCH或者PUCCH，则所述DCI格式为DCI format 2-2，且通过PUSCH-TPC-RNTI或者PUCCH-TPC-RNTI加扰；如果所述上行信号为SRS，则所述DCI格式为 DCI format 2-3，且通过SRS-TPC-RNTI加扰。
基于上述方案，本实施例还可以提供进一步确定TPC命令域的处理方法，比如，还可以包括：根据网络侧指示的TPC命令位置索引、以及所述TPC命令域的比特数，从所述DCI中确定所述终端设备的TPC命令域。
关于如何获取TPC命令位置索引的方法，所述终端设备还包括：
第一通信单元32，接收网络侧通过RRC信令指示的所述TPC命令位置索引；
接收网络侧通过RRC信令指示的所述TPC命令位置索引；其中，所述TPC命令位置索引用于指示所述终端设备的TPC命令域在所述DCI中的起始比特。
具体的，所述位置索引可以以1比特为单位，即TPC命令域的起始比特可以在所述DCI中的任意位置；或者所述位置索引可以以2比特为单位，即TPC命令域的起始比特可以是所述DCI比特中的任意偶数比特(例如，比特索引为0,2,4,…)。
所述TPC命令位置索引中包含至少一个TPC命令的位置索引；其中，每一个TPC命令对应一个BWP或者对应一个BWP的一个闭环功率控制进程。如果所述TPC命令域包含多个TPC命令的位置索引，每个TPC命令对应一个BWP或者一个BWP上的一个闭环功率控制进程，则网络侧可以为所述多个TPC命令配置独立的位置索引。即网络侧可以为每个BWP或者每个闭环功率控制进程独立配置TPC命令位置索引。例如，第k个位置索引对应第k个BWP或者第k个闭环功率控制进程的TPC命令。
典型的，所述TPC命令域占用所述DCI中的连续比特位。例如，如果所述TPC命令域包含2个TPC命令，则这两个TPC命令为所述DCI中两个连续的TPC命令。
所述TPC命令位置索引指示了第k个比特，所述TPC命令域的比特数为M，则所述终端的TPC命令域占用的比特为DCI中的第{k,k+1,…,k+M-1}个比特。
如果所述TPC命令域为2*N比特，则其中包含N个2比特的TPC命令，第n个TPC命令用于第n个BWP或者第n个闭环功率控制进程；如果所述TPC命令域为2+log2(N)比特，则前两个比特为TPC命令，后面log2(N)个比特指示所述TPC命令对应的BWP或者闭环功率控制进程，或者后两个比特为TPC命令，前log2(N)个比特指示所述TPC命令对应的BWP或者闭环功率控制进程。
本实施例还可以包括以下步骤：
第一通信单元，根据确定的所述发送功率发送所述上行信号；
所述第一处理单元，根据当前发送所述上行信号的BWP的闭环功率调整因子、或者所述上行信号当前使用的闭环功率控制进程的闭环功率调整因子，确定所述上行信号的发送功率。
可见，通过采用上述方案，就能够根据上行信号BWP的数量或者闭环功率控制进程的数量，确定对应的TPC命令，并根据TPC命令确定上行信号对应的功率调整因子，从而，尽可能降低一个终端的TPC命令的DCI开销，节约不必要的DCI开销，通过一个DCI进行更多终端和更多BWP的闭环功率控制。
实施例四、
本发明实施例提供了一种网络设备，如图4所示，包括：
第二处理单元41，根据发送上行信号的带宽部分BWP的数量、或者、根据上行信号关联的闭环功率控制进程的数量，确定下行控制信息DCI中终端设备的发送功率控制TPC命令域的比特数；
第二通信单元42，通过所述DCI向所述终端设备发送所述TPC命令域。本实施例中所述终端设备可以理解为通信系统中具备通信功能的终端，比如，手机等。
上述第二处理单元41，执行以下至少之一：
根据所述上行信号当前的传输类型确定所述上行信号关联的闭环功率控制进程的数量；也就是说，根据当前上行信号的传输类型确定。
根据高层信令配置确定所述上行信号关联的闭环功率控制进程的数量；
根据发送所述上行信号的BWP的数量以及发送所述上行信号的各个BWP上的闭环功率控制进程的数量，确定所述上行信号关联的闭环功率控制进程的数量；
当所述上行信号为PUSCH时，根据高层信令配置的第一对应关系确定所述上行信号关联的闭 环功率控制进程的数量，其中，所述第一对应关系为SRI状态和闭环功率控制进程的对应关系；
当所述上行信号为PUCCH时，根据高层信令配置的第二对应关系确定所述上行信号关联的闭环功率控制进程的数量，其中，所述第二对应关系为PUCCH空间相关信息和闭环功率控制进程的对应关系；
当所述上行信号为SRS时，根据高层信令配置的第三对应关系确定所述上行信号关联的闭环功率控制进程的数量，其中，所述第三对应关系为SRS空间相关信息和闭环功率控制进程的对应关系。
进一步，所述第二处理单元41，基于所述上行信号为免授权类型或基于调度类型，确定所述上行信号关联的闭环功率控制进程的数量；比如，是基于grant-free(终端自主发送)的上行信号还是基于调度的上行信号，基于这种类型来确定对应的数量。例如，基于grant-free的上行信号关联的闭环功率控制进程的数量为1；基于调度的关联的闭环功率控制进程的数量为2或者网络侧配置的值；
和/或，
当所述终端设备配置至少一个BWP时，根据所述至少一个BWP中各个BWP上的传输类型为每一个BWP确定闭环功率控制进程的数量；其中，至少一个可以理解为一个当然还可以为更多。
上述根据高层信令配置确定所述上行信号关联的闭环功率控制进程的数量，可以为PUSCH和PUCCH独立配置数量。如果终端被配置了多个BWP，网络侧可以为各个BWP分别配置闭环功率控制进程的数量。
所述第二处理单元41，将发送所述上行信号的所有BWP中包含的闭环功率控制进程的总数量，作为所述上行信号关联的闭环功率控制进程的数量。
即根据发送所述上行信号的BWP的数量及各个BWP上的闭环功率控制进程的数量确定。
具体来说，所述发送上行信号的BWP的数量可以为以下之一：同时发送所述上行信号的BWP的数量；当前激活的上行BWP的数量；网络侧为终端配置的上行BWP的数量。
需要指出的是，对于后两种情况，这些BWP不一定能够同时用于发送所述上行信号，同一时刻可以只有一个或部分BWP能用于发送所述上行信号。终端可以在不同时间采用不同BWP发送所述上行信号。
所述第二处理单元41，执行以下三种至少之一：
情况1：
将所述第一对应关系中包含的不同闭环功率控制进程的数量，确定为所述上行信号关联的闭环功率控制进程的数量；
例如，所述第一对应关系指示了所有的SRI状态对应相同的一个闭环功率控制进程，则闭环功率控制进程的数量为1；如果所述对应关系指示了部分SRI状态对应闭环功率控制进程0，其他SRI状态对应闭环功率控制进程1，则闭环功率控制进程的数量为2。
情况2：
当所述上行信号为PUSCH、且所述终端设备未配置所述SRI、或者未配置所述第一对应关系时，确定所述上行信号关联的闭环功率控制进程的数量为1；
当所述上行信号为PUSCH、且所述终端设备未配置所述SRI、或者未配置所述第一对应关系时，确定所述上行信号关联的闭环功率控制进程的数量为1，即如果终端没有被配置SRI或者所述SRI状态和闭环功率控制进程的对应关系，则闭环功率控制进程的数量为1。
情况3：
当所述上行信号为PUSCH、且所述终端设备配置至少一个BWP时，根据所述至少一个BWP中各个BWP配置的第一对应关系，确定所述上行信号关联的闭环功率控制进程的数量。
当所述上行信号为PUSCH、且所述终端设备配置至少一个BWP时，根据所述至少一个BWP中各个BWP配置的第一对应关系，确定所述上行信号关联的闭环功率控制进程的数量，即如果终端被配置了多个BWP，可以根据各个BWP上配置的对应关系分别确定数量。
需要说明的是，关于第一对应关系，可以理解为SRI状态和闭环功率控制进程之间的对应关系；其中，SRI为SRS资源指示信息(SRS Resource Indicator，)，其获取方式可以通过调度所述PUSCH的DCI来携带SRI。
所述当所述上行信号为PUCCH时，根据高层信令配置的第二对应关系，确定所述上行信号关联的闭环功率控制进程的数量，即如果所述上行信号是PUCCH，可以根据高层信令配置的PUCCH空间相关信息(PUCCH-SpatialRelationInfo)和闭环功率控制进程的对应关系确定，该对应关系中包含的不同闭环功率控制进程的数量。具体的，可以包括：
第二处理单元41，可以执行以下三种情况至少一种：
情况1：
终端可以将所述第二对应关系中包含的不同闭环功率控制进程的数量，确定为所述上行信号关联的闭环功率控制进程的数量；
例如，所述对应关系指示了所有的PUCCH空间相关信息对应相同的一个闭环功率控制进程，则闭环功率控制进程的数量为1；如果所述第二对应关系指示了部分PUCCH空间相关信息对应闭环功率控制进程0，其他PUCCH空间相关信息对应闭环功率控制进程1，则闭环功率控制进程的数量为2。
情况2：
当所述上行信号为PUCCH时，若所述终端设备未配置所述PUCCH空间相关信息、或者、未配置所述第二对应关系，则确定所述上行信号关联的闭环功率控制进程的数量为1；
如果终端没有被配置PUCCH空间相关信息或者PUCCH空间相关信息和闭环功率控制进程的第二对应关系，则闭环功率控制进程的数量为1；
情况3：
第二处理单元41，当所述上行信号为PUCCH、且所述终端设备配置至少一个BWP时，根据所述至少一个BWP中各个BWP上配置的第二对应关系，确定所述上行信号关联的闭环功率控制进程的数量。也就是说，如果终端被配置了多个BWP，可以根据各个BWP上配置的第二对应关系分别确定数量。
所述当所述上行信号为SRS时，根据高层信令配置的第三对应关系，确定所述上行信号关联的闭环功率控制进程的数量，即如果所述上行信号是SRS，可以根据高层信令配置的SRS空间相关信息(SRS-Spatial Relation Info)和闭环功率控制进程的对应关系确定，该对应关系中包含的不同闭环功率控制进程的数量。具体来说，第二处理单元41，可以执行以下三种情况中的至少一种：
情况一：
终端可以将所述第三对应关系中包含的不同闭环功率控制进程的数量，确定为所述上行信号关联的闭环功率控制进程的数量。
例如，所述第三对应关系指示了所有的SRS空间相关信息对应相同的一个闭环功率控制进程，则闭环功率控制进程的数量为1；如果所述第三对应关系指示了部分SRS空间相关信息对应闭环功率控制进程0，其他SRS空间相关信息对应闭环功率控制进程1，则闭环功率控制进程的数量为2。
情况二：
当所述上行信号为SRS时，若所述终端设备未配置所述SRS空间相关信息、或者未配置所述第三对应关系，则确定所述上行信号关联的闭环功率控制进程的数量为1；
即如果终端没有被配置SRS空间相关信息或者SRS空间相关信息和闭环功率控制进程的第三对应关系，则闭环功率控制进程的数量为1。
情况三：
第二处理单元41，当所述上行信号为SRS、且所述终端设备配置至少一个BWP时，根据所述至少一个BWP中各个BWP上配置的第三对应关系，确定所述上行信号关联的闭环功率控制进程的数量；也就是说，如果终端被配置了多个BWP，可以根据各个BWP上配置的对应关系分别确定数量。
所述发送上行信号的BWP的数量是同时发送所述上行信号的BWP的数量，或者当前激活的上行BWP的数量，或者网络侧为终端配置的上行BWP的数量；对于后两种情况，这些BWP不一定能够同时用于发送所述上行信号，同一时刻可以只有一个或部分BWP能用于发送所述上行信号。终端可以在不同时间采用不同BWP发送所述上行信号。
在确定发送上行信号的BWP的数量或所述上行信号关联的闭环功率控制进程的数量之前，所述方法还包括：确定所述DCI中的TPC命令域的比特数为2。具体的，该DCI中包含该终端的一个TPC命令域。例如，在终端接收到网络侧配置的BWP的数量或者所述上行信号关联的闭环功率控制进程的数量之前，终端假设所述DCI中的TPC命令域的比特数为2。
如果所述发送上行信号的BWP的数量为N、或所述上行信号关联的闭环功率控制进程的数量为N，则确定所述TPC命令域的比特数为2*N或2+log2(N)。
所述DCI为以下至少一：携带PUSCH的TPC命令的DCI；携带PUCCH的TPC命令的DCI；携带SRS的TPC命令的DCI。
需要说明的是，所述DCI的格式可以为：DCI format 2-2或DCI format 2-3；并且，所述DCI采用PUSCH-TPC-RNTI或者PUCCH-TPC-RNTI或SRS-TPC-RNTI加扰。所述DCI可以用于指示一个BWP上的TPC命令，也可以用于指示不同BWP上的TPC命令。
所述上行信号为以下之一：PUSCH、PUCCH、SRS。
具体的，如果所述上行信号为PUSCH或者PUCCH，则所述DCI格式为DCI format 2-2，且通过PUSCH-TPC-RNTI或者PUCCH-TPC-RNTI加扰；如果所述上行信号为SRS，则所述DCI格式为DCI format 2-3，且通过SRS-TPC-RNTI加扰。
基于上述方案，本实施例还可以提供进一步确定TPC命令域的处理方法，比如，还可以包括：向终端设备指示TPC命令位置索引，以使终端设备基于所述TPC命令位置所以以及所述TPC命令域的比特数，从所述DCI中确定TPC命令域。
关于如何获取TPC命令位置索引的方法，可以为：所述网络设备通过RRC信令指示的所述TPC命令位置索引；其中，所述TPC命令位置索引用于指示所述终端设备的TPC命令域在所述DCI中的起始比特。
具体的，所述位置索引可以以1比特为单位，即TPC命令域的起始比特可以在所述DCI中的任意位置；或者所述位置索引可以以2比特为单位，即TPC命令域的起始比特可以是所述DCI比特中的任意偶数比特(例如，比特索引为0,2,4,…)。
所述TPC命令位置索引中包含至少一个TPC命令的位置索引；其中，每一个TPC命令对应一个BWP或者对应一个BWP的一个闭环功率控制进程。如果所述TPC命令域包含多个TPC命令的位置索引，每个TPC命令对应一个BWP或者一个BWP上的一个闭环功率控制进程，则网络侧可以为所述多个TPC命令配置独立的位置索引。即网络侧可以为每个BWP或者每个闭环功率控制进程独立配置TPC命令位置索引。例如，第k个位置索引对应第k个BWP或者第k个闭环功率控制进程的TPC命令。
典型的，所述TPC命令域占用所述DCI中的连续比特位。例如，如果所述TPC命令域包含2个TPC命令，则这两个TPC命令为所述DCI中两个连续的TPC命令。
所述TPC命令位置索引指示了第k个比特，所述TPC命令域的比特数为M，则所述终端的TPC命令域占用的比特为DCI中的第{k,k+1,…,k+M-1}个比特。
本实施例还可以包括：
所述第二处理单元41，根据当前终端设备发送所述上行信号的BWP的闭环功率调整因子、或者终端设备发送所述上行信号当前使用的闭环功率控制进程的闭环功率调整因子，确定终端设备上行信号的发送功率；
所述第二通信单元41，根据确定的所述发送功率接收所述终端设备发来的所述上行信号。
可见，通过采用上述方案，就能够根据上行信号BWP的数量或者闭环功率控制进程的数量，确定对应的TPC命令，并根据TPC命令确定上行信号对应的功率调整因子，从而，尽可能降低一个终端的TPC命令的DCI开销，节约不必要的DCI开销，通过一个DCI进行更多终端和更多BWP的闭环功率控制。
本发明实施例还提供了一种终端设备、或网络设备的硬件组成架构，如图5所示，包括：至少一个处理器51、存储器52、至少一个网络接口53。各个组件通过总线系统54耦合在一起。可理解， 总线系统54用于实现这些组件之间的连接通信。总线系统54除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图5中将各种总线都标为总线系统54。
可以理解，本发明实施例中的存储器52可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。
在一些实施方式中，存储器52存储了如下的元素，可执行模块或者数据结构，或者他们的子集，或者他们的扩展集：
操作系统521和应用程序522。
其中，所述处理器51配置为：能够处理前述实施例一或二的方法步骤，这里不再进行赘述。
本发明实施例上述装置如果以软件功能模块的形式实现并作为独立的产品销售或使用时，也可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明实施例的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机、服务器、或者网络设备等)执行本发明各个实施例所述方法的全部或部分。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read Only Memory)、磁碟或者光盘等各种可以存储程序代码的介质。这样，本发明实施例不限制于任何特定的硬件和软件结合。
本发明实施例提供的一种计算机存储介质，所述计算机存储介质存储有计算机可执行指令，所述计算机可执行指令被执行时实施前述实施例一或二的方法步骤。
尽管为示例目的，已经公开了本发明的优选实施例，本领域的技术人员将意识到各种改进、增加和取代也是可能的，因此，本发明的范围应当不限于上述实施例。

Claims (57)

  1. 一种上行功率控制方法，应用于终端设备，所述方法包括：
    根据发送上行信号的带宽部分BWP的数量、或者、根据上行信号关联的闭环功率控制进程的数量，确定下行控制信息DCI中所述终端设备的发送功率控制TPC命令域的比特数；
    根据所述TPC命令域中的TPC命令，确定发送所述上行信号的至少一个BWP或者所述上行信号关联的至少一个闭环功率控制进程的闭环功率调整因子。
  2. 根据权利要求1所述的方法，其中，所述方法还包括以下至少之一：
    根据所述上行信号当前的传输类型确定所述上行信号关联的闭环功率控制进程的数量；
    根据高层信令配置确定所述上行信号关联的闭环功率控制进程的数量；
    根据发送所述上行信号的BWP的数量以及发送所述上行信号的各个BWP上的闭环功率控制进程的数量，确定所述上行信号关联的闭环功率控制进程的数量；
    当所述上行信号为PUSCH时，根据高层信令配置的第一对应关系确定所述上行信号关联的闭环功率控制进程的数量，其中，所述第一对应关系为SRI状态和闭环功率控制进程的对应关系；
    当所述上行信号为PUCCH时，根据高层信令配置的第二对应关系确定所述上行信号关联的闭环功率控制进程的数量，其中，所述第二对应关系为PUCCH空间相关信息和闭环功率控制进程的对应关系；
    当所述上行信号为SRS时，根据高层信令配置的第三对应关系确定所述上行信号关联的闭环功率控制进程的数量，其中，所述第三对应关系为SRS空间相关信息和闭环功率控制进程的对应关系。
  3. 根据权利要求2所述的方法，其中，所述根据当前上行信号的传输类型确定所述上行信号关联的闭环功率控制进程的数量，包括：
    基于所述上行信号为免授权类型或基于调度类型，确定所述上行信号关联的闭环功率控制进程的数量；
    和/或，
    当所述终端设备配置至少一个BWP时，根据所述至少一个BWP中各个BWP上的传输类型为每一个BWP确定闭环功率控制进程的数量。
  4. 根据权利要求2所述的方法，其中，所述根据发送所述上行信号的BWP的数量以及各个上行信号的BWP上的闭环功率控制进程的数量，确定所述上行信号关联的闭环功率控制进程的数量，包括：
    将发送所述上行信号的所有BWP中包含的闭环功率控制进程的总数量，作为所述上行信号关联的闭环功率控制进程的数量。
  5. 根据权利要求2所述的方法，其中，所述当所述上行信号为PUSCH时，根据高层信令配置的第一对应关系，确定所述上行信号关联的闭环功率控制进程的数量，包括以下至少之一：
    将所述第一对应关系中包含的不同闭环功率控制进程的数量，确定为所述上行信号关联的闭环功率控制进程的数量；
    当所述上行信号为PUSCH、且所述终端设备未配置所述SRI、或者未配置所述第一对应关系时，确定所述上行信号关联的闭环功率控制进程的数量为1；
    当所述上行信号为PUSCH、且所述终端设备配置至少一个BWP时，根据所述至少一个BWP中各个BWP配置的第一对应关系，确定所述上行信号关联的闭环功率控制进程的数量。
  6. 根据权利要求2所述的方法，其中，所述当所述上行信号为PUCCH时，根据高层信令配置的第二对应关系，确定所述上行信号关联的闭环功率控制进程的数量，包括以下至少之一：
    将所述第二对应关系中包含的不同闭环功率控制进程的数量，确定为所述上行信号关联的闭环 功率控制进程的数量；
    当所述上行信号为PUCCH时，若所述终端设备未配置所述PUCCH空间相关信息、或者、未配置所述第二对应关系，则确定所述上行信号关联的闭环功率控制进程的数量为1；
    当所述上行信号为PUCCH、且所述终端设备配置至少一个BWP时，根据所述至少一个BWP中各个BWP上配置的第二对应关系，确定所述上行信号关联的闭环功率控制进程的数量。
  7. 根据权利要求2所述的方法，其中，所述当所述上行信号为SRS时，根据高层信令配置的第三对应关系，确定所述上行信号关联的闭环功率控制进程的数量，包括以下至少之一：
    将所述第三对应关系中包含的不同闭环功率控制进程的数量，确定为所述上行信号关联的闭环功率控制进程的数量；
    当所述上行信号为SRS时，若所述终端设备未配置所述SRS空间相关信息、或者未配置所述第三对应关系，则确定所述上行信号关联的闭环功率控制进程的数量为1；
    当所述上行信号为SRS、且所述终端设备配置至少一个BWP时，根据所述至少一个BWP中各个BWP上配置的第三对应关系，确定所述上行信号关联的闭环功率控制进程的数量。
  8. 根据权利要求1-7任一项所述的方法，其中，所述发送上行信号的BWP的数量，为：
    同时发送所述上行信号的BWP的数量；
    或者，当前激活的上行BWP的数量，
    或者，网络侧为所述终端设备配置的上行BWP的数量。
  9. 根据权利要求1所述的方法，其中，在确定发送上行信号的BWP的数量或所述上行信号关联的闭环功率控制进程的数量之前，所述方法还包括：
    确定所述DCI中的TPC命令域的比特数为2。
  10. 根据权利要求9所述的方法，其中，所述DCI中包含所述终端设备的1个TPC命令域。
  11. 根据权利要求1-8任一项所述的方法，其中，所述方法还包括：
    如果所述发送上行信号的BWP的数量为N、或所述上行信号关联的闭环功率控制进程的数量为N，则确定所述TPC命令域的比特数为2*N或2+log2(N)。
  12. 根据权利要求1-11任一项所述的方法，其中，所述DCI为以下至少一：
    携带PUSCH的TPC命令的DCI；
    携带PUCCH的TPC命令的DCI；
    携带SRS的TPC命令的DCI。
  13. 根据权利要求1-12任一项所述的方法，其中，所述上行信号为以下之一：PUSCH、PUCCH、SRS。
  14. 根据权利要求1-13任一项所述的方法，其中，所述方法还包括：
    根据网络侧指示的TPC命令位置索引、以及所述TPC命令域的比特数，从所述DCI中确定所述终端设备的TPC命令域。
  15. 根据权利要求14所述的方法，其中，所述方法还包括：
    接收网络侧通过RRC信令指示的所述TPC命令位置索引；
    其中，所述TPC命令位置索引用于指示所述终端设备的TPC命令域在所述DCI中的起始比特。
  16. 根据权利要求14所述的方法，其中，所述TPC命令位置索引中包含至少一个TPC命令的位置索引；其中，每一个TPC命令对应一个BWP或者对应一个BWP的一个闭环功率控制进程。
  17. 根据权利要求1-16中任一项所述的方法，其中，所述TPC命令域占用所述DCI中的连续比特位。
  18. 根据权利要求1所述的方法，其中，所述方法还包括：
    根据当前发送所述上行信号的BWP的闭环功率调整因子、或者所述上行信号当前使用的闭环功率控制进程的闭环功率调整因子，确定所述上行信号的发送功率；
    根据确定的所述发送功率发送所述上行信号。
  19. 一种上行功率控制方法，应用于网络设备，所述方法包括：
    根据发送上行信号的带宽部分BWP的数量、或者、根据上行信号关联的闭环功率控制进程的数量，确定下行控制信息DCI中终端设备的发送功率控制TPC命令域的比特数；
    通过所述DCI向所述终端设备发送所述TPC命令域。
  20. 根据权利要求19所述的方法，其中，所述方法还包括以下至少之一：
    根据所述上行信号当前的传输类型确定所述上行信号关联的闭环功率控制进程的数量；
    根据高层信令配置确定所述上行信号关联的闭环功率控制进程的数量；
    根据发送所述上行信号的BWP的数量以及发送所述上行信号的各个BWP上的闭环功率控制进程的数量，确定所述上行信号关联的闭环功率控制进程的数量；
    当所述上行信号为PUSCH时，根据高层信令配置的第一对应关系确定所述上行信号关联的闭环功率控制进程的数量，其中，所述第一对应关系为SRI状态和闭环功率控制进程的对应关系；
    当所述上行信号为PUCCH时，根据高层信令配置的第二对应关系确定所述上行信号关联的闭环功率控制进程的数量，其中，所述第二对应关系为PUCCH空间相关信息和闭环功率控制进程的对应关系；
    当所述上行信号为SRS时，根据高层信令配置的第三对应关系确定所述上行信号关联的闭环功率控制进程的数量，其中，所述第三对应关系为SRS空间相关信息和闭环功率控制进程的对应关系。
  21. 根据权利要求19或20所述的方法，其中，所述发送上行信号的BWP的数量，为：
    同时发送所述上行信号的BWP的数量；
    或者，当前激活的上行BWP的数量；
    或者，为所述终端设备配置的上行BWP的数量。
  22. 根据权利要求19所述的方法，其中，在确定发送上行信号的BWP的数量或所述上行信号关联的闭环功率控制进程的数量之前，所述方法还包括：
    确定所述DCI中的TPC命令域的比特数为2。
  23. 根据权利要求19-22任一项所述的方法，其中，所述方法还包括：
    如果所述发送上行信号的BWP的数量为N、或所述上行信号关联的闭环功率控制进程的数量为N，则确定所述TPC命令域的比特数为2*N或2+log2(N)。
  24. 根据权利要求19-23任一项所述的方法，其中，所述DCI为以下至少一：
    携带PUSCH的TPC命令的DCI；
    携带PUCCH的TPC命令的DCI；
    携带SRS的TPC命令的DCI。
  25. 根据权利要求19-24任一项所述的方法，其中，所述上行信号为以下之一：PUSCH、PUCCH、SRS。
  26. 根据权利要求19-25任一项所述的方法，其中，所述方法还包括：
    向终端设备指示TPC命令位置索引，以使终端设备基于所述TPC命令位置所以以及所述TPC命令域的比特数，从所述DCI中确定TPC命令域。
  27. 根据权利要求19所述的方法，其中，所述方法还包括：
    根据当前终端设备发送所述上行信号的BWP的闭环功率调整因子、或者终端设备发送所述上行信号当前使用的闭环功率控制进程的闭环功率调整因子，确定终端设备上行信号的发送功率；根据确定的所述发送功率接收所述终端设备发来的所述上行信号。
  28. 一种终端设备，所述终端设备包括：
    第一处理单元，根据发送上行信号的带宽部分BWP的数量、或者、根据上行信号关联的闭环功率控制进程的数量，确定下行控制信息DCI中所述终端设备的发送功率控制TPC命令域的比特数；
    根据所述TPC命令域中的TPC命令，确定发送所述上行信号的至少一个BWP或者所述上行信号关联的至少一个闭环功率控制进程的闭环功率调整因子。
  29. 根据权利要求28所述的终端设备，其中，所述第一处理单元，执行以下至少之一：
    根据所述上行信号当前的传输类型确定所述上行信号关联的闭环功率控制进程的数量；
    根据高层信令配置确定所述上行信号关联的闭环功率控制进程的数量；
    根据发送所述上行信号的BWP的数量以及发送所述上行信号的各个BWP上的闭环功率控制进程的数量，确定所述上行信号关联的闭环功率控制进程的数量；
    当所述上行信号为PUSCH时，根据高层信令配置的第一对应关系确定所述上行信号关联的闭环功率控制进程的数量，其中，所述第一对应关系为SRI状态和闭环功率控制进程的对应关系；
    当所述上行信号为PUCCH时，根据高层信令配置的第二对应关系确定所述上行信号关联的闭环功率控制进程的数量，其中，所述第二对应关系为PUCCH空间相关信息和闭环功率控制进程的对应关系；
    当所述上行信号为SRS时，根据高层信令配置的第三对应关系确定所述上行信号关联的闭环功率控制进程的数量，其中，所述第三对应关系为SRS空间相关信息和闭环功率控制进程的对应关系。
  30. 根据权利要求29所述的终端设备，其中，所述第一处理单元，基于所述上行信号为免授权类型或基于调度类型，确定所述上行信号关联的闭环功率控制进程的数量；
    和/或，
    当所述终端设备配置至少一个BWP时，根据所述至少一个BWP中各个BWP上的传输类型为每一个BWP确定闭环功率控制进程的数量。
  31. 根据权利要求29所述的终端设备，其中，所述第一处理单元，将发送所述上行信号的所有BWP中包含的闭环功率控制进程的总数量，作为所述上行信号关联的闭环功率控制进程的数量。
  32. 根据权利要求29所述的终端设备，其中，所述第一处理单元执行以下至少之一：
    将所述第一对应关系中包含的不同闭环功率控制进程的数量，确定为所述上行信号关联的闭环功率控制进程的数量；
    当所述上行信号为PUSCH、且所述终端设备未配置所述SRI、或者未配置所述第一对应关系时，确定所述上行信号关联的闭环功率控制进程的数量为1；
    当所述上行信号为PUSCH、且所述终端设备配置至少一个BWP时，根据所述至少一个BWP中各个BWP配置的第一对应关系，确定所述上行信号关联的闭环功率控制进程的数量。
  33. 根据权利要求29所述的终端设备，其中，所述第一处理单元执行以下至少之一：
    将所述第二对应关系中包含的不同闭环功率控制进程的数量，确定为所述上行信号关联的闭环功率控制进程的数量；
    当所述上行信号为PUCCH时，若所述终端设备未配置所述PUCCH空间相关信息、或者、未配置所述第二对应关系，则确定所述上行信号关联的闭环功率控制进程的数量为1；
    当所述上行信号为PUCCH、且所述终端设备配置至少一个BWP时，根据所述至少一个BWP中各个BWP上配置的第二对应关系，确定所述上行信号关联的闭环功率控制进程的数量。
  34. 根据权利要求29所述的终端设备，其中，所述第一处理单元执行以下至少之一：
    将所述第三对应关系中包含的不同闭环功率控制进程的数量，确定为所述上行信号关联的闭环功率控制进程的数量；
    当所述上行信号为SRS时，若所述终端设备未配置所述SRS空间相关信息、或者未配置所述第三对应关系，则确定所述上行信号关联的闭环功率控制进程的数量为1；
    当所述上行信号为SRS、且所述终端设备配置至少一个BWP时，根据所述至少一个BWP中各个BWP上配置的第三对应关系，确定所述上行信号关联的闭环功率控制进程的数量。
  35. 根据权利要求28-34任一项所述的终端设备，其中，所述发送上行信号的BWP的数量，为：
    同时发送所述上行信号的BWP的数量；
    或者，当前激活的上行BWP的数量，
    或者，网络侧为所述终端设备配置的上行BWP的数量。
  36. 根据权利要求28所述的终端设备，其中，所述第一处理单元，确定所述DCI中的TPC命令域的比特数为2。
  37. 根据权利要求36所述的终端设备，其中，所述DCI中包含所述终端设备的1个TPC命令域。
  38. 根据权利要求28-37任一项所述的终端设备，其中，所述第一处理单元，如果所述发送上行信号的BWP的数量为N、或所述上行信号关联的闭环功率控制进程的数量为N，则确定所述TPC命令域的比特数为2*N或2+log2(N)。
  39. 根据权利要求28-38任一项所述的终端设备，其中，所述DCI为以下至少一：
    携带PUSCH的TPC命令的DCI；
    携带PUCCH的TPC命令的DCI；
    携带SRS的TPC命令的DCI。
  40. 根据权利要求28-39任一项所述的终端设备，其中，所述上行信号为以下之一：PUSCH、PUCCH、SRS。
  41. 根据权利要求28-39任一项所述的终端设备，其中，所述第一处理单元，根据网络侧指示的TPC命令位置索引、以及所述TPC命令域的比特数，从所述DCI中确定所述终端设备的TPC命令域。
  42. 根据权利要求41所述的终端设备，其中，所述终端设备还包括：
    第一通信单元，接收网络侧通过RRC信令指示的所述TPC命令位置索引；
    其中，所述TPC命令位置索引用于指示所述终端设备的TPC命令域在所述DCI中的起始比特。
  43. 根据权利要求41所述的终端设备，其中，所述TPC命令位置索引中包含至少一个TPC命令的位置索引；其中，每一个TPC命令对应一个BWP或者对应一个BWP的一个闭环功率控制进程。
  44. 根据权利要求28-43中任一项所述的终端设备，其中，所述TPC命令域占用所述DCI中的连续比特位。
  45. 根据权利要求28所述的终端设备，其中，所述终端设备，还包括：
    第一通信单元，根据确定的所述发送功率发送所述上行信号；
    所述第一处理单元，根据当前发送所述上行信号的BWP的闭环功率调整因子、或者所述上行信号当前使用的闭环功率控制进程的闭环功率调整因子，确定所述上行信号的发送功率。
  46. 一种网络设备，包括：
    第二处理单元，根据发送上行信号的带宽部分BWP的数量、或者、根据上行信号关联的闭环功率控制进程的数量，确定下行控制信息DCI中终端设备的发送功率控制TPC命令域的比特数；
    第二通信单元，通过所述DCI向所述终端设备发送所述TPC命令域。
  47. 根据权利要求46所述的网络设备，其中，所述第二处理单元，执行以下至少之一：
    根据所述上行信号当前的传输类型确定所述上行信号关联的闭环功率控制进程的数量；
    根据高层信令配置确定所述上行信号关联的闭环功率控制进程的数量；
    根据发送所述上行信号的BWP的数量以及发送所述上行信号的各个BWP上的闭环功率控制进程的数量，确定所述上行信号关联的闭环功率控制进程的数量；
    当所述上行信号为PUSCH时，根据高层信令配置的第一对应关系确定所述上行信号关联的闭环功率控制进程的数量，其中，所述第一对应关系为SRI状态和闭环功率控制进程的对应关系；
    当所述上行信号为PUCCH时，根据高层信令配置的第二对应关系确定所述上行信号关联的闭环功率控制进程的数量，其中，所述第二对应关系为PUCCH空间相关信息和闭环功率控制进程的 对应关系；
    当所述上行信号为SRS时，根据高层信令配置的第三对应关系确定所述上行信号关联的闭环功率控制进程的数量，其中，所述第三对应关系为SRS空间相关信息和闭环功率控制进程的对应关系。
  48. 根据权利要求46或47所述的网络设备，其中，所述发送上行信号的BWP的数量，为：
    同时发送所述上行信号的BWP的数量；
    或者，当前激活的上行BWP的数量；
    或者，为所述终端设备配置的上行BWP的数量。
  49. 根据权利要求46所述的网络设备，其中，在确定发送上行信号的BWP的数量或所述上行信号关联的闭环功率控制进程的数量之前，所述第二处理单元，确定所述DCI中的TPC命令域的比特数为2。
  50. 根据权利要求46-49任一项所述的网络设备，其中，所述第二处理单元，如果所述发送上行信号的BWP的数量为N、或所述上行信号关联的闭环功率控制进程的数量为N，则确定所述TPC命令域的比特数为2*N或2+log2(N)。
  51. 根据权利要求46-50任一项所述的网络设备，其中，所述DCI为以下至少一：
    携带PUSCH的TPC命令的DCI；
    携带PUCCH的TPC命令的DCI；
    携带SRS的TPC命令的DCI。
  52. 根据权利要求46-51任一项所述的网络设备，其中，所述上行信号为以下之一：PUSCH、PUCCH、SRS。
  53. 根据权利要求46-52任一项所述的网络设备，其中，所述第二通信单元，向终端设备指示TPC命令位置索引，以使终端设备基于所述TPC命令位置所以以及所述TPC命令域的比特数，从所述DCI中确定TPC命令域。
  54. 根据权利要求46所述的网络设备，其中，
    所述第二处理单元，根据当前终端设备发送所述上行信号的BWP的闭环功率调整因子、或者终端设备发送所述上行信号当前使用的闭环功率控制进程的闭环功率调整因子，确定终端设备上行信号的发送功率；
    所述第二通信单元，根据确定的所述发送功率接收所述终端设备发来的所述上行信号。
  55. 一种终端设备，包括：处理器和用于存储能够在处理器上运行的计算机程序的存储器，
    其中，所述处理器用于运行所述计算机程序时，执行权利要求1-18任一项所述方法的步骤。
  56. 一种网络设备，包括：处理器和用于存储能够在处理器上运行的计算机程序的存储器，
    其中，所述处理器用于运行所述计算机程序时，执行权利要求19-27任一项所述方法的步骤。
  57. 一种计算机存储介质，所述计算机存储介质存储有计算机可执行指令，所述计算机可执行指令被执行时实现权利要求1-27任一项所述的方法步骤。
PCT/CN2018/083092 2018-04-13 2018-04-13 一种上行功率控制方法、终端设备及网络设备 WO2019196114A1 (zh)

Priority Applications (16)

Application Number Priority Date Filing Date Title
ES18914290T ES2912355T3 (es) 2018-04-13 2018-04-13 Método de control de potencia de enlace ascendente y dispositivo terminal
IL271001A IL271001B1 (en) 2018-04-13 2018-04-13 Connection power control method, end unit device and network device
CA3065621A CA3065621C (en) 2018-04-13 2018-04-13 Method of uplink power control, terminal device and network device
EP18914290.4A EP3627912B1 (en) 2018-04-13 2018-04-13 Uplink power control method and terminal device
AU2018418095A AU2018418095B8 (en) 2018-04-13 2018-04-13 Method of uplink power control, terminal device, and network device
SG11201911426YA SG11201911426YA (en) 2018-04-13 2018-04-13 Method of uplink power control, terminal device and network device
CN201911303137.3A CN111132295B (zh) 2018-04-13 2018-04-13 一种上行功率控制方法、终端设备及网络设备
PCT/CN2018/083092 WO2019196114A1 (zh) 2018-04-13 2018-04-13 一种上行功率控制方法、终端设备及网络设备
EP22155637.6A EP4037390A1 (en) 2018-04-13 2018-04-13 Method of uplink power control and network device
KR1020197036274A KR102475094B1 (ko) 2018-04-13 2018-04-13 상향 전력 제어 방법, 단말기 디바이스 및 네트워크 디바이스
CN201880031781.7A CN110637484B (zh) 2018-04-13 2018-04-13 一种上行功率控制方法、终端设备及网络设备
JP2019568084A JP7080906B2 (ja) 2018-04-13 2018-04-13 上り電力の制御方法、端末デバイス及びネットワークデバイス
RU2019142488A RU2758467C1 (ru) 2018-04-13 2018-04-13 Способ управления мощностью восходящей линии связи, терминальное устройство и сетевое устройство
BR112019027113-9A BR112019027113A2 (pt) 2018-04-13 2018-04-13 Método de controle de potência de uplink, dispositivo terminal e dispositivo de rede
US16/694,132 US10880838B2 (en) 2018-04-13 2019-11-25 Method of uplink power control, terminal device and network device
PH12019502691A PH12019502691A1 (en) 2018-04-13 2019-11-28 Uplink power control method, terminal device, and network device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/083092 WO2019196114A1 (zh) 2018-04-13 2018-04-13 一种上行功率控制方法、终端设备及网络设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/694,132 Continuation US10880838B2 (en) 2018-04-13 2019-11-25 Method of uplink power control, terminal device and network device

Publications (1)

Publication Number Publication Date
WO2019196114A1 true WO2019196114A1 (zh) 2019-10-17

Family

ID=68163840

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/083092 WO2019196114A1 (zh) 2018-04-13 2018-04-13 一种上行功率控制方法、终端设备及网络设备

Country Status (14)

Country Link
US (1) US10880838B2 (zh)
EP (2) EP3627912B1 (zh)
JP (1) JP7080906B2 (zh)
KR (1) KR102475094B1 (zh)
CN (2) CN110637484B (zh)
AU (1) AU2018418095B8 (zh)
BR (1) BR112019027113A2 (zh)
CA (1) CA3065621C (zh)
ES (1) ES2912355T3 (zh)
IL (1) IL271001B1 (zh)
PH (1) PH12019502691A1 (zh)
RU (1) RU2758467C1 (zh)
SG (1) SG11201911426YA (zh)
WO (1) WO2019196114A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2023517032A (ja) * 2020-03-04 2023-04-21 日本電気株式会社 ネットワーク装置、端末装置、及び方法

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108135028B (zh) * 2018-02-27 2022-08-19 中兴通讯股份有限公司 一种功率控制方法、装置及通信节点
US11924819B2 (en) * 2019-05-24 2024-03-05 Qualcomm Incorporated Power limits based on signal type for managing maximum permissible exposure
WO2022029912A1 (ja) * 2020-08-05 2022-02-10 株式会社Ｎｔｔドコモ 端末、無線通信方法及び基地局
US11800455B2 (en) * 2020-09-04 2023-10-24 Qualcomm Incorporated Methods for power control in ultra wide bandwidth beamforming systems

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013119167A1 (en) * 2012-02-08 2013-08-15 Telefonaktiebolaget L M Ericsson (Publ) Closed loop power control commands for srs
CN104039000A (zh) * 2013-03-07 2014-09-10 中兴通讯股份有限公司 一种功率调整的方法及基站
CN104837191A (zh) * 2014-02-08 2015-08-12 上海贝尔股份有限公司 一种在TDD eIMTA中控制上行子帧传输功率的方法及其装置

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3694262A1 (en) * 2006-10-03 2020-08-12 InterDigital Technology Corporation Combined open loop/closed lopp (cqi-based) uplink transmit power control with interference mitigation for e-utra
US9763197B2 (en) * 2009-10-05 2017-09-12 Qualcomm Incorporated Component carrier power control in multi-carrier wireless network
EP2343934A1 (en) * 2010-01-11 2011-07-13 Panasonic Corporation Transmit power control signaling for communication systems using carrier aggregation
CN103379605A (zh) * 2012-04-26 2013-10-30 电信科学技术研究院 一种上行功率控制方法、装置及系统
EP3550897A1 (en) * 2013-01-03 2019-10-09 LG Electronics Inc. Method and apparatus for transmitting uplink signals in wireless communication system
US9191930B2 (en) * 2013-03-13 2015-11-17 Samsung Electronics Co., Ltd. Transmission of acknowledgement information in adaptively configured TDD communication systems
KR101642361B1 (ko) * 2014-03-20 2016-08-10 주식회사 엘지유플러스 무선통신시스템에서 단말의 전송전력 제어 방법 및 이를 수행하는 장치
CN106797530A (zh) * 2014-08-14 2017-05-31 Lg 电子株式会社 无线通信系统中控制传输功率的方法和设备
US9955465B2 (en) * 2014-10-03 2018-04-24 Intel IP Corporation Downlink control information (DCI) design for LTE devices
CN107529209A (zh) * 2016-06-22 2017-12-29 深圳市中兴微电子技术有限公司 控制wifi热点省电的方法及其装置
US10548096B2 (en) * 2017-04-21 2020-01-28 Samsung Electronics Co., Ltd. Information type multiplexing and power control
US10945172B2 (en) * 2017-11-16 2021-03-09 Comcast Cable Communications, Llc Power control for bandwidth part switching

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013119167A1 (en) * 2012-02-08 2013-08-15 Telefonaktiebolaget L M Ericsson (Publ) Closed loop power control commands for srs
CN104039000A (zh) * 2013-03-07 2014-09-10 中兴通讯股份有限公司 一种功率调整的方法及基站
CN104837191A (zh) * 2014-02-08 2015-08-12 上海贝尔股份有限公司 一种在TDD eIMTA中控制上行子帧传输功率的方法及其装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
See also references of EP3627912A4 *
VIVO: "Remaining issues on NR UL power control", 3GPP TSG RAN WG1 MEETING #92 R1-1801546, 15 February 2018 (2018-02-15), pages 2 - 3, XP051396798 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2023517032A (ja) * 2020-03-04 2023-04-21 日本電気株式会社 ネットワーク装置、端末装置、及び方法
JP7468678B2 (ja) 2020-03-04 2024-04-16 日本電気株式会社 ネットワーク装置、端末装置、及び方法

Also Published As

Publication number Publication date
JP2021523582A (ja) 2021-09-02
CN110637484A (zh) 2019-12-31
CN110637484B (zh) 2024-03-15
ES2912355T3 (es) 2022-05-25
RU2758467C1 (ru) 2021-10-28
CN111132295B (zh) 2021-03-09
CA3065621C (en) 2022-10-18
US20200092820A1 (en) 2020-03-19
EP3627912A1 (en) 2020-03-25
KR20200142444A (ko) 2020-12-22
US10880838B2 (en) 2020-12-29
IL271001A (en) 2020-01-30
AU2018418095B8 (en) 2023-01-19
KR102475094B1 (ko) 2022-12-07
CA3065621A1 (en) 2019-10-17
AU2018418095A1 (en) 2019-12-19
CN111132295A (zh) 2020-05-08
AU2018418095B2 (en) 2023-01-05
SG11201911426YA (en) 2020-01-30
JP7080906B2 (ja) 2022-06-06
IL271001B1 (en) 2024-02-01
PH12019502691A1 (en) 2020-09-28
EP3627912A4 (en) 2020-08-12
EP4037390A1 (en) 2022-08-03
BR112019027113A2 (pt) 2020-12-08
EP3627912B1 (en) 2022-03-09

Similar Documents

Publication Publication Date Title
WO2019196114A1 (zh) 一种上行功率控制方法、终端设备及网络设备
CN110138514B (zh) 一种进行混合自动重传请求反馈的方法和终端
WO2019090775A1 (en) Methods and devices for beam report transmission and receiving
JP7043615B2 (ja) Ｄｃｉにおける情報ドメイン値を特定する方法及び装置
WO2019169590A1 (zh) Srs功率余量上报的方法、终端设备及计算机存储介质
CN110167126B (zh) 一种多波束传输时pucch功率的控制方法及装置
WO2017133012A1 (zh) 一种上行控制信息传输的方法及装置
WO2019157851A1 (zh) 一种上行物理共享信道功率控制方法和终端
WO2022052053A1 (en) Positioning measurement reporting in unlicensed spectrum
WO2019080132A1 (zh) 传输数据的方法、终端设备和网络设备
TW202215887A (zh) 使用者設備以及由使用者設備進行資源分配的方法
JP5761450B2 (ja) 最大構成出力パワーの報告方法及び端末装置
TW202044895A (zh) 新無線電移動通信中具有波束管理的輔小區激活
EP3332594A1 (en) Methods and apparatuses for performing uplink transmission and receiving
WO2018010488A1 (zh) 发射功率确定方法、终端、网络设备和系统
CN111526574A (zh) 用于功率控制的方法及设备
WO2021083247A1 (zh) 上行传输的方法、上行传输指示的方法和设备
CN117044144A (zh) Harq-ack码本处理
TWI803945B (zh) 用於波束故障恢復的通訊方法、裝置及電腦可讀媒體
TW202410669A (zh) 與多個傳送及接收點通訊的方法和使用者設備裝置
CN115696534A (zh) 信息指示方法、装置、相关设备及存储介质
JP2022159347A5 (ja) アクセサリ装置、撮像装置、制御方法、記憶媒体、およびレンズ装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18914290

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 271001

Country of ref document: IL

ENP Entry into the national phase

Ref document number: 3065621

Country of ref document: CA

ENP Entry into the national phase

Ref document number: 2019568084

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2018418095

Country of ref document: AU

Date of ref document: 20180413

Kind code of ref document: A

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112019027113

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 2018914290

Country of ref document: EP

Effective date: 20191218

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 112019027113

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20191218