CN116437449A - Power control parameter determining method, device and terminal - Google Patents
Power control parameter determining method, device and terminal Download PDFInfo
- Publication number
- CN116437449A CN116437449A CN202111673190.XA CN202111673190A CN116437449A CN 116437449 A CN116437449 A CN 116437449A CN 202111673190 A CN202111673190 A CN 202111673190A CN 116437449 A CN116437449 A CN 116437449A
- Authority
- CN
- China
- Prior art keywords
- pdsch
- scheduling
- codebook
- harq
- terminal
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 121
- 230000005540 biological transmission Effects 0.000 claims abstract description 133
- 230000004044 response Effects 0.000 claims abstract description 3
- 238000004364 calculation method Methods 0.000 claims description 87
- 238000001514 detection method Methods 0.000 claims description 51
- 230000008569 process Effects 0.000 claims description 49
- 238000013468 resource allocation Methods 0.000 claims description 48
- 230000009977 dual effect Effects 0.000 claims description 40
- 235000019580 granularity Nutrition 0.000 claims description 21
- 239000004973 liquid crystal related substance Substances 0.000 claims description 13
- 239000000523 sample Substances 0.000 claims 3
- 238000004891 communication Methods 0.000 abstract description 21
- 238000012544 monitoring process Methods 0.000 description 51
- 230000006870 function Effects 0.000 description 10
- 230000000694 effects Effects 0.000 description 8
- 238000012545 processing Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 238000004590 computer program Methods 0.000 description 4
- 241001633942 Dais Species 0.000 description 3
- 239000000969 carrier Substances 0.000 description 3
- 238000010276 construction Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000004913 activation Effects 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 2
- 230000003190 augmentative effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 101000741965 Homo sapiens Inactive tyrosine-protein kinase PRAG1 Proteins 0.000 description 1
- 102100038659 Inactive tyrosine-protein kinase PRAG1 Human genes 0.000 description 1
- 241000764238 Isis Species 0.000 description 1
- 238000007599 discharging Methods 0.000 description 1
- RFHAOTPXVQNOHP-UHFFFAOYSA-N fluconazole Chemical compound C1=NC=NN1CC(C=1C(=CC(F)=CC=1)F)(O)CN1C=NC=N1 RFHAOTPXVQNOHP-UHFFFAOYSA-N 0.000 description 1
- 239000011521 glass Substances 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000005406 washing Methods 0.000 description 1
- 210000000707 wrist Anatomy 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
- H04W72/044—Wireless resource allocation based on the type of the allocated resource
- H04W72/0473—Wireless resource allocation based on the type of the allocated resource the resource being transmission power
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
-
- 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
-
- 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/0053—Allocation of signaling, i.e. of overhead other than pilot signals
- H04L5/0055—Physical resource allocation for ACK/NACK
-
- 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
-
- 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
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
- H04W72/044—Wireless resource allocation based on the type of the allocated resource
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/12—Wireless traffic scheduling
Abstract
The application discloses a method, a device and a terminal for determining power control parameters, which belong to the technical field of communication, and the method for determining the power control parameters in the embodiment of the application comprises the following steps: under the condition that a serving cell of a terminal is configured with Multi-Physical Downlink Shared Channel (PDSCH) scheduling, the terminal determines a first power control parameter according to target information related to the Multi-PDSCH scheduling, wherein the first power control parameter comprises the effective bit number of hybrid automatic repeat request response (HARQ-ACK); the terminal determines the transmission power of a Physical Uplink Control Channel (PUCCH) carrying the HARQ-ACK according to the first power control parameter; and the terminal sends the PUCCH to network side equipment according to the sending power.
Description
Technical Field
The application belongs to the technical field of communication, and particularly relates to a method, a device and a terminal for determining power control parameters.
Background
In some communication systems, multi-physical downlink shared channel (Multi-PDSCH) scheduling transmissions are introduced, where Multi-PDSCH scheduling refers to the ability of a single downlink control information (Downlink Control Information, DCI) to schedule multiple physical downlink shared channel (Physical downlink shared channel, PDSCH) transmissions on the same carrier at once.
In the related art, forN corresponding to a first Type codebook (Type-1 codebook) HARQ-ACK The computation does not consider the process when introducing Multi-PDSCH scheduling and configuring application time domain bundling (Time domain bundling). N corresponding to the second codebook (Type-2 codebook) HARQ-ACK The calculation does not take into account the impact of the hybrid automatic repeat request acknowledgement (Hybrid automatic repeat request acknowledgement, HARQ-ACK) corresponding to the Multi-PDSCH scheduling. Thereby creating a calculated n HARQ-ACK The value of (2) is not matched with the effective HARQ-ACK bit number contained in the HARQ-ACK codebook, thereby leading to the following n HARQ-ACK The determined transmission power of the physical uplink control channel (Physical Uplink Control Channel, PUCCH) carrying HARQ-ACK is not matched with the transmission power actually required by the terminal, which will reduce the transmission performance of the PUCCH carrying HARQ-ACK.
Disclosure of Invention
The embodiment of the application provides a power control parameter determining method, a power control parameter determining device and a power control parameter determining terminal, which can solve the problem of transmission performance reduction of a PUCCH carrying HARQ-ACK caused by mismatching of the transmission power of the PUCCH in the related technology with actual requirements.
In a first aspect, a method for determining a power control parameter is provided, the method comprising:
under the condition that a serving cell of a terminal is configured with Multi-Physical Downlink Shared Channel (PDSCH) scheduling, the terminal determines a first power control parameter according to target information related to the Multi-PDSCH scheduling, wherein the first power control parameter comprises the effective bit number of hybrid automatic repeat request response (HARQ-ACK);
The terminal determines the transmission power of a Physical Uplink Control Channel (PUCCH) carrying the HARQ-ACK according to the first power control parameter;
and the terminal sends the PUCCH to network side equipment according to the sending power.
In a second aspect, there is provided a power control parameter determining apparatus applied to a terminal, the apparatus comprising:
a first determining module, configured to determine a first power control parameter according to target information related to Multi-physical downlink shared channel PDSCH scheduling when a serving cell of a terminal is configured with the Multi-PDSCH scheduling, where the first power control parameter includes a valid bit number of hybrid automatic repeat request acknowledgement HARQ-ACK;
a second determining module, configured to determine, according to the first power control parameter, a transmission power of a physical uplink control channel PUCCH carrying the HARQ-ACK;
and the sending module is used for sending the PUCCH to the network side equipment according to the sending power.
In a third aspect, there is provided a terminal comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implement the steps of the method as described in the first aspect.
In a fourth aspect, a terminal is provided, including a processor and a communication interface, where the processor is configured to determine a first power control parameter according to target information related to Multi-physical downlink shared channel PDSCH scheduling in a serving cell of the terminal, where the first power control parameter includes a valid bit number of hybrid automatic repeat request acknowledgement HARQ-ACK, and determine, according to the first power control parameter, a transmission power of a physical uplink control channel PUCCH carrying the HARQ-ACK, and the communication interface is configured to transmit the PUCCH to a network side device according to the transmission power.
In a fifth aspect, there is provided a readable storage medium having stored thereon a program or instructions which when executed by a processor realizes the steps of the method according to the first aspect.
In a sixth aspect, there is provided a chip comprising a processor and a communication interface coupled to the processor for running a program or instructions to implement the method of the first aspect.
In a seventh aspect, a computer program/program product is provided, stored in a storage medium, which is executed by at least one processor to implement the steps of the power control parameter determination method according to the first aspect.
In the embodiment of the application, under the condition that a serving cell of a terminal is configured with Multi-Physical Downlink Shared Channel (PDSCH) scheduling, the terminal determines a first power control parameter according to target information related to the Multi-PDSCH scheduling, wherein the first power control parameter comprises the effective bit number of hybrid automatic repeat request (HARQ-ACK); the terminal determines the transmission power of a Physical Uplink Control Channel (PUCCH) carrying the HARQ-ACK according to the first power control parameter; and the terminal sends the PUCCH to network side equipment according to the sending power. In this way, when the service cell of the terminal is configured with Multi-PDSCH scheduling, the first power control parameter can be determined according to the target information related to the Multi-PDSCH scheduling, so that the first power control parameter is matched with the effective HARQ-ACK bit number contained in the HARQ-ACK codebook, the transmission power of the PUCCH carrying HARQ-ACK determined according to the first power control parameter is matched with the transmission power actually required by the terminal, and the transmission performance of the PUCCH carrying HARQ-ACK is further ensured.
Drawings
Fig. 1 is a block diagram of a wireless communication system to which embodiments of the present application can be applied;
Fig. 2 is a flowchart of a method for determining a power control parameter according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of a power control parameter determining apparatus according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of a communication device according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a terminal according to an embodiment of the present application.
Detailed Description
The technical solutions of the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some of the embodiments of the present application, but not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application are within the scope of the protection of the present application.
The terms first, second and the like in the description and in the claims, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in sequences other than those illustrated or otherwise described herein, and that the terms "first" and "second" are generally intended to be used in a generic sense and not to limit the number of objects, for example, the first object may be one or more. Furthermore, in the description and claims, "and/or" means at least one of the connected objects, and the character "/" generally means a relationship in which the associated object is an "or" before and after.
It is noted that the techniques described in embodiments of the present application are not limited to long term evolution (Long Term Evolution, LTE)/LTE evolution (LTE-Advanced, LTE-a) systems, but may also be used in other wireless communication systems, such as code division multiple access (Code Division Multiple Access, CDMA), time division multiple access (Time Division Multiple Access, TDMA), frequency division multiple access (Frequency Division Multiple Access, FDMA), orthogonal frequency division multiple access (Orthogonal Frequency Division Multiple Access, OFDMA), single-carrier frequency division multiple access (Single-carrier Frequency Division Multiple Access, SC-FDMA), and other systems. The terms "system" and "network" in embodiments of the present application are often used interchangeably, and the techniques described may be used for both the above-mentioned systems and radio technologies, as well as other systems and radio technologies. The following description describes a New air interface (NR) system for purposes of example and uses NR terminology in much of the description that follows, but these techniques are also applicable to applications other than NR system applications, such as generation 6 (6) th Generation, 6G) communication system.
Fig. 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable. The wireless communication system includes a terminal 11 and a network device 12. The terminal 11 may be a mobile phone, a tablet (Tablet Personal Computer), a Laptop (Laptop Computer) or a terminal-side Device called a notebook, a personal digital assistant (Personal Digital Assistant, PDA), a palm top, a netbook, an ultra-mobile personal Computer (ultra-mobile personal Computer, UMPC), a mobile internet appliance (Mobile Internet Device, MID), an augmented reality (augmented reality, AR)/Virtual Reality (VR) Device, a robot, a Wearable Device (weather Device), a vehicle-mounted Device (VUE), a pedestrian terminal (PUE), a smart home (home Device with a wireless communication function, such as a refrigerator, a television, a washing machine, or a home appliance), a game machine, a personal Computer (personal Computer, PC), a teller machine, or a self-service machine, and the Wearable Device includes: intelligent wrist-watch, intelligent bracelet, intelligent earphone, intelligent glasses, intelligent ornament (intelligent bracelet, intelligent ring, intelligent necklace, intelligent anklet, intelligent foot chain etc.), intelligent wrist strap, intelligent clothing etc.. Note that, the specific type of the terminal 11 is not limited in the embodiment of the present application. The network-side device 12 may comprise an access network device or a core network device, wherein the access network device 12 may also be referred to as a radio access network device, a radio access network (Radio Access Network, RAN), a radio access network function or a radio access network element. Access network device 12 may include base stations, WLAN access points, wiFi nodes, etc., which may be referred to as node bs, evolved node bs (enbs), access points, base transceiver stations (Base Transceiver Station, BTSs), radio base stations, radio transceivers, basic service sets (Basic Service Set, BSS), extended service sets (Extended Service Set, ESS), home node bs, home evolved node bs, transmit receive points (Transmitting Receiving Point, TRP), or some other suitable terminology in the art, and the base stations are not limited to a particular technical vocabulary so long as the same technical effect is achieved, and it should be noted that in the embodiments of the present application, only base stations in the NR system are described by way of example, and the specific types of base stations are not limited.
In the related art, when the UE activates the uplink Bandwidth portion (Bandwidth Part,upon initiating a PUCCH transmission on BWP) b, the UE determines the transmit power P of this PUCCH transmission based on the following equation (1) PUCCH,b,f,c (i,q u ,q d ,l)：
Wherein i represents: PUCCH transmission opportunity index;
q u the representation is: UE level P O Index for determining P O_UE_PUCCH (q u )；
q d The representation is: index of reference signal as path loss reference for determining PL b,f,c (q d )；
l represents: PUCCH closed loop power control state index;
μ represents: transmitting corresponding subcarrier interval indexes by the PUCCH;
P O_PUCCH,b,f,c (q u ) The representation is: from P O_NOMINAL_PUCCH And P O_UE_PUCCH (q u ) Total P obtained by addition O Value, where P O_NOMINAL_PUCCH Is public P O ，P O_UE_PUCCH (q u ) For UE level P O ；
PL b,f,c (q d ) The representation is: the estimated downlink loss is in dB.
Δ F_PUCCH (F) The representation is: the amount of power adjustment based on the PUCCH format.
Δ TF,b,f,c (i) The representation is: the amount of power adjustment based on the PUCCH transmission properties.
g b,f,c (i, l) represents: PUCCH closed loop power control adjustment.
For delta TF,b,f,c (i) The number of uplink control information (Uplink Control Information, UCI) bits calculated to distinguish between PUCCH format (format) and bearer is different. For P-basedPUCCH transmission of UCCH format 2/3/4, when the number of UCI bits carried does not exceed 11 (For a PUCCH transmission using PUCCH format 2 or PUCCH format 3 or PUCCH format 4 and for a number of UCI bits smaller than or equal to 11), delta is calculated by the following formula (2) TF,b,f,c (i)：
Δ TF,b,f,c (i)＝10 log 10 (K 1 ·(n HARQ-ACK (i)+O SR (i)+O CSI (i))N RE (i))
Wherein K is 1 ＝6；
n HARQ-ACK (i) For the number of effective bits of HARQ-ACK information determined by the UE, the calculation procedure is described later for different HARQ-ACK codebook types. When the HARQ-ACK codebook type is not configured for the UE, if 1-bit HARQ-ACK is carried in the PUCCH transmission, n HARQ-ACK (i) =1, otherwise n HARQ-ACK (i)＝0；
O SR (i) The number of SR information bits determined for the UE;
O CSI (i) A CSI information bit number determined for the UE;
N RE (i) For the number of resource elements (occupied by data information in PUCCH transmission,
wherein (1)>
For the number of sub-carriers corresponding to each resource block, the occupied sub-carriers of the dedicated demodulation reference signal (Dedicated demodulation reference signals, DM-RS) transmission are excluded, & lt/EN & gt>
The number of symbols occupied for PUCCH transmission is eliminated from the symbols occupied for DM-RS transmission.
It should be noted that, when a User Equipment (UE) organizes a HARQ-ACK bit sequence that needs to be reported at a certain feedback time, based on a predefined rule and a case where PDSCH transmissions on a single/multiple carriers of the HARQ-ACK need to be reported at the feedback time and/or PDSCH transmissions are not scheduled but DCI indications corresponding to the HARQ-ACK need to be fed back, determining a correspondence between each PDSCH transmission and/or DCI indication and a certain bit in the organized HARQ-ACK bit sequence is referred to as constructing a HARQ-ACK Codebook (Codebook) or a HARQ-ACK Codebook scheme. NR Rel-15 employs two HARQ-ACK Codebook schemes: semi-static Codebook (Type-1 Codebook) and dynamic Codebook (Type-2 Codebook).
The semi-static codebook is constructed from the perspective of possible PDSCH reception opportunities (acknowledgement), and based on a feedback Timing (Timing) configuration Table (i.e., a K1 Set configured by a higher layer, which contains one or at least two candidates K1; K1 is used to indicate a time offset between PDSCH reception and its corresponding HARQ-ACK feedback, or a DCI that does not schedule PDSCH transmission but needs feedback of the corresponding HARQ-ACK indicates a time offset between its corresponding HARQ-ACK feedback, whose granularity is PUCCH slots (slots)) and HARQ-ACK feedback moments (i.e., PUCCH slots where the semi-static codebook transmission is located), a corresponding HARQ-ACK bit is reserved for each possible PDSCH reception opportunity (determined jointly based on a time domain resource allocation (Time Domain Resource Allocation, TDRA) Table (Table) configured by a higher layer and the aforementioned K1 Set) (which can be understood as converting the HARQ-ACK bit Set formed by each possible acknowledgement into an ACK bit sequence). If for a certain PDSCH receiver, the UE does not actually receive the corresponding PDSCH, or the UE does not actually detect an unscheduled PDSCH transmission corresponding thereto but needs to feed back a DCI indication (e.g., SPS PDSCH release) of the corresponding HARQ-ACK, then its corresponding HARQ-ACK bit is set to a negative acknowledgement (Negative Acknowledgement, NACK), otherwise the corresponding HARQ-ACK bit is set based on the decoding result of the PDSCH when the UE receives the corresponding PDSCH, and the corresponding HARQ-ACK bit is set to ACK when the UE detects the corresponding DCI indication.
And n is as above HARQ-ACK (i) Different HARQ-ACK codebook types are distinguished by the calculation of (a) and (b), respectively, are described below.
< for Type-1 codebook >
N can be calculated using the following equation (3) HARQ-ACK (i)：
Wherein when PDSCH-CodeBlockGroupTransmsision is configured (when it is necessary to not reconfigure harq-ACK-SpatialBundlingPUCCH),
the number of CBGs received for the UE within PDSCH reception occasion m of serving cell c, and PDSCH reception carrying these CBGs is scheduled by DCI supporting CBG-based PDSCH reception (i.e., corresponding non-fallback DCI); otherwise->
For the following
Which can be determined by distinguishing between the following cases (Case 1 and Case 2):
case 1: when the UE receives the PDSCH in the PDSCH reception timing (reception occasion) m, it is further specifically classified into cases 1-1 to 1-3 below. The reception timing may be referred to as a reception timing, and for convenience of description, the following embodiments are collectively referred to as a reception timing.
Case 1-1: when neither harq-ACK-spatlbundlingpucch nor PDSCH-codeblockgrouptransision is configured,
the number of transport blocks received by the UE within PDSCH reception occasion m of serving cell c.
Case 1-2: when PDSCH-codeblockgrouptannsmision is configured (when harq-ACK-SpatialBundlingPUCCH must not be reconfigured), 
PDSCH reception occasion m for UE in serving cell cThe number of transport blocks received in, and PDSCH reception carrying these transport blocks is scheduled by DCI not supporting CBG-based PDSCH reception (i.e., corresponding fallback DCI).
Case 1-3: when the harq-ACK-spatlbundlingpucch is configured (PDSCH-codeblockgrouptannision must not be reconfigured at this time),
the number of PDSCH receptions received for the UE within PDSCH reception occasion m of serving cell c.
Case 2: when the UE receives SPS PDSCH release for the PDSCH reception occasion m serving cell c, and feeds back the corresponding HARQ-ACK in this Type-1 codebook for this SPS PDSCH release,
< for Type-2 codebook >
The Type-2 codebook refers to three formulas (formula (4), formula (5) and formula (6), and formula (6) is the sum of formula (4) and formula (5). When Type-2 codebook only involves transmission block (Transport Block based, TB-based) HARQ-ACK (Code block group (CBG) transmission is not configured for each Serving cell (Serving cell) within a PUCCH cell group (cell group)), i.e. the high-level parameter PDSCH-Serving cell Config->codeBlockGroupTransmsision), in which case only a single Sub-codebook (Sub-codebook) is involved, n is calculated using equation (4) HARQ-ACK The method comprises the steps of carrying out a first treatment on the surface of the When Type-2 codebook refers to both HARQ-ACK of TB-based and HARQ-ACK of CBG-based (i.e. at least one Serving cell in the PUCCH cell group is configured with CBG transmission and with high-level parameters PDSCH-servingCellConfig->codeBlockGroupTransmsision) in which case two Sub-codebooks are involved, n is calculated using equation (6) HARQ-ACK 。
Wherein n is calculated for TB-based HARQ-ACK HARQ-ACK Equation (4) of (2) is:
wherein, the liquid crystal display device comprises a liquid crystal display device,
the representation is: counting (counter) the number of bits occupied by the downlink allocation index (Downlink assignment index, DAI);
for the following
The meaning and value can distinguish the following cases:
1) When the UE does not detect any DCI in M PDCCH monitoring occasion (the DCI may schedule PDSCH reception or may not schedule PDSCH reception but needs to feed back corresponding HARQ-ACK information; not distinguishing which serving cell to use for),
2) When (when)
When (I)>
The value of the counter DAI carried by the last DCI detected by the UE in the M PDCCH detection opportunities (monitoring occasion) can be used for scheduling PDSCH reception or not scheduling PDSCH reception but feeding back corresponding HARQ-ACK information;
3) When (when)
In this case, it is possible to distinguish between the cases in which +.>
3-1) at least one DCI is detected for the UE among M PDCCH monitoring occasion (this DCI may or may not schedule PDSCH reception but requires feedback of the corresponding HARQ-ACK information; does not distinguish the last PDCCH monitoring occasion in PDCCH monitoring occasion for which serving cell), if the UE does not detect any DCI carrying a total DAI within this PDCCH monitoring occasion
The value of the counter DAI carried by the last DCI detected by the UE in PDCCH monitoring occasion;
3-2) at least one DCI is detected for the UE among M PDCCH monitoring occasion (this DCI may or may not schedule PDSCH reception but requires feedback of the corresponding HARQ-ACK information; without distinguishing which serving cell to target) the last PDCCH monitoring occasion in PDCCH monitoring occasion, if the UE detects at least one DCI carrying a total DAI within this PDCCH monitoring occasion
The value of the total DAI carried in at least one DCI carrying a total DAI detected by the UE in this PDCCH monitoring occasion (when the UE detects multiple DCIs carrying total DAIs in this PDCCH monitoring occasion, the values of the total DAIs carried by these DCIs must be equal);
For U DAI,c The meaning and value can be determined by distinguishing the following cases:
1)U DAI,c for the UE to target the serving cell c, the total number of DCIs detected in M PDCCH monitoring occasion, where the DCIs may schedule PDSCH reception, or may not schedule PDSCH reception but need to feed back corresponding HARQ-ACK information;
2) The UE detects no DCI in M PDCCH monitoring occasion for serving cell c (this DCI may or may not schedule PDSCH reception but requires feedbackCorresponding HARQ-ACK information), U DAI,c ＝0；
For the following
The meaning and value can be determined by distinguishing the following cases:
when maxnrofcodewordsschedule bydci is 2 for any one serving cell, and harq-ACK-spatialbundling pucch is not configured,
otherwise, other wise, ">
For the following
The meaning and value of which can be determined by distinguishing between the following cases (Case 1 and Case 2):
case 1: when the UE receives DCI for scheduling PDSCH, it is specifically classified into the following cases 1-1 to 1-2:
case 1-1: when the harq-ACK-SpatialBundlingPUCCH is not configured,
the number of transport blocks of PDSCH bearers scheduled for DCI detected by serving cell c for the UE within PDCCH detection occasion (monitoring occasion) m.
Case 1-2: when the harq-ACK-spatialbundling pucch is configured, 
The number of PDSCH scheduled for the DCI detected by the UE for serving cell c within PDCCH monitoring occasion m.
Case 2：
Unscheduled PDSCH reception detected for serving cell c in PDCCH monitoring occasion m for UE but requiredThe number of DCIs corresponding to the HARQ-ACK is fed back.
N SPS,c The number of SPS PDSCH receptions for the corresponding HARQ-ACK information needs to be fed back in a certain PUCCH for the serving cell c, and the UE also feeds back HARQ-ACK information for PDSCH receptions scheduled in M PDCCH monitoring occasion in this PUCCH.
Wherein n is calculated for CBG-based HARQ-ACK HARQ-ACK Equation (5) of (2) is:
for the following
The meaning and value can distinguish the following cases:
1) When (when)
When (I)>
The value of the counter DAI carried by DCI which is detected by the UE in M PDCCH monitoring occasion aiming at any service cell and is received by the PDSCH based on CBG;
2) When (when)
When (I)>
The value of the total DAI carried by DCI received by the PDSCH based on CBG is scheduled for the last scheduling detected by the UE in M PDCCH monitoring occasion aiming at any service cell;
3) When the UE does not detect any DCI scheduling CBG-based PDSCH reception for any serving cell within M PDCCH monitoring occasion, 
For the following
The meaning and value can be determined by distinguishing the following cases:
1)
for the UE, for serving cell c, the total number of DCI received by the CBG-based PDSCH detected in M PDCCH monitoring occasion;
2) When the UE detects no DCI scheduling CBG-based PDSCH reception in M PDCCH monitoring occasion for the serving cell c,
Wherein equation (6) will calculate n for TB-based HARQ-ACK HARQ-ACK And n calculated for CBG-based HARQ-ACK HARQ-ACK The addition, equation (6), is:
n HARQ-ACK ＝n HARQ-ACK,TB +n HARQ-ACK,CBG
in the related art, enhanced Type-2 codebook and Type-3 codebook have also been introduced.
< for enhanced Type-2 codebook >
The UE determines the corresponding effective bit number n of HARQ-ACK information aiming at the PDSCH group g HARQ-ACK,g And determining a pair for PDSCH group (g+1) mod2Number n of effective bits of HARQ-ACK information HARQ-ACK,(g+1)mod2 . Note that N SPS,c Is contained in n only HARQ-ACK,g Is a kind of medium.
When q=1 and
when the UE sets->
To according to the
Determination of n HARQ-ACK,(g+1)mod2 。
Specifically, n HARQ-ACK The method is determined based on the following steps:
when q=0, n HARQ-ACK ＝n HARQ-ACK,g ；
Otherwise, n HARQ-ACK ＝n HARQ-ACK,g +n HARQ-ACK,(g+1)mod2 。
The relevant parameters are described as follows:
g is indicated in the last non-fallback (DCI corresponding to the enhanced Type-2 codebook, specifically, indicated by the PDSCH group index (group index) indication field of the DCI.
< for Type-3 codebook >
n HARQ-ACK (i)＝O ACK (i) Wherein O is ACK (i) Is the number of valid HARQ-ACK bits contained in the Type-3 codebook.
Calculating n from the above Type-1 codebook, type-2 codebook, enhanced Type-3 codebook and Type-3 codebook HARQ-ACK The definition of each parameter in the process of (a) and the process of calculating (b) is known, and n is calculated in the related art HARQ-ACK When Multi-PUSCH scheduling is introduced, n calculated according to the calculation rules in Type-1 codebook, type-2 codebook, enhanced Type-3 codebook, and Type-3 codebook described above may exist HARQ-ACK The value of (3) is not matched with the actual condition of Multi-PUSCH scheduling.
For example: in the Rel-17.6-71 GHz characteristic research process, it is confirmed that a new subcarrier Spacing (SCS) including 480kHz and 960kHz needs to be introduced for a new NR deployment frequency band. For these newly introduced SCS, PDCCH monitoring needs to be correspondingly adjusted or enhanced, for example: the need for monitoring the PDCCH in each Slot (or a short duration) by the UE is avoided, so that the complexity of UE implementation is reduced. Accordingly, multi-PDSCH scheduling and Multi-PUSCH scheduling need to be explored/introduced in order to fully utilize carrier time domain resources.
Wherein, multi-PDSCH scheduling refers to that a single DCI can schedule multiple PDSCH transmissions on the same carrier at once. The PDSCH is not overlapped with each other in the time domain according to the protocol of NR.
When a Serving cell configured for a UE supports Multi-PDSCH scheduling, at least one row in the TDRA table configured for that Serving cell is configured with more than one start indication (Entry)/start and length indication values (Start and Length Indicator Value, SLIV). The downlink scheduling DCI schedules PDSCH corresponding to each Entry/SLIV in the indication row for the UE by indicating one row in the TDRA table, and one Entry/SLIV gives time domain resource allocation information of the corresponding PDSCH.
In the Rel-17.6-71 GHz characteristic study procedure, the construction of Type-1 codebook and Type-2 codebook is mainly discussed for HARQ-ACK feedback for Multi-PDSCH scheduling.
< for Type-1 codebook >
When the application Time domain bundling is not configured for a certain Serving cell, determining, based on each row in the TDRA table configured for the Serving cell and the configured K1 set, a DL slot set in which PDSCH scheduling for the Serving cell may occur and a set of SLIVs corresponding to PDSCH that may exist in each DL slot in the DL slot set when feeding back Type-1 codebook in a specified PUCCH slot. Based on the DL slot sets and the SLIV sets corresponding to each DL slot, obtaining an Occasion set corresponding to the Serving cell along with a Rel-15/16 pseudo code flow, and converting the Occasion set into a HARQ-ACK bit sequence corresponding to the Serving cell in a Type-1 codebook.
When an application Time domain bundling is configured for a certain Serving cell, based on Last SLIV of each row in a TDRA table configured for the Serving cell and configured K1 set, a Recl-15/16 pseudo code flow is used to obtain an occupancy set corresponding to the Serving cell, and the occupancy set is converted into a HARQ-ACK bit sequence corresponding to the Serving cell in a Type-1 codebook.
It should be noted that, whether to apply Time domain bundling can be independently configured for each Serving cell configured in a certain PUCCH cell group, and the corresponding HARQ-ACK bit sequence of each Serving cell in the Type-1 codebook is independently determined, and then end-to-end cascading is performed across Serving cells.
< for Type-2 codebook >
DAI counting is performed based on DCI.
When the application Time domain bundling is not configured for a certain Serving cell, only the DCI of a single PDSCH is scheduled, or only a single HARQ-ACK bit is generated and no DCI of a PDSCH is scheduled for the Serving cell, the corresponding HARQ-ACK is put into a first sub-codebook, the HARQ-ACKs corresponding to the DCI of more than one PDSCH are scheduled into a second sub-codebook, and the two sub-codebooks respectively count DAIs.
When configuring an application Time domain Bundling for a certain Serving cell, if the number of configured Bundling groups is 1, scheduling HARQ-ACK corresponding to DCI of more than one PDSCH for the Serving cell, and putting the HARQ-ACK in a first sub-codebook, otherwise, putting the HARQ-ACK in a second sub-codebook; other operations are fully consistent with when the application Time domain bundling is not configured.
It should be noted that, whether to apply Time domain bundling can be configured independently for each Serving cell configured in a certain PUCCH cell group; DAI is counted uniformly across Serving cells in a certain PUCCH cell group.
From the above construction rules for Type-1 codebook and Type-2 codebook for HARQ-ACK feedback supporting Multi-PDSCH scheduling, n corresponds to the first Type codebook (Type-1 codebook) in the related art HARQ-ACK Processing when introducing Multi-PDSCH scheduling and configuring application time domain bundling (Time domain bundling) is not considered for computation, resulting in n being computed in this configuration case HARQ-ACK Inaccuracy (i.e. calculated n HARQ-ACK Not the number of valid HARQ-ACK bits contained in the codebook) and may even exceed the number of bits of the HARQ-ACK codebook, thereby affecting a reasonable setting of PUCCH transmit power. N corresponding to the second codebook (Type-2 codebook) HARQ-ACK The calculation does not take into account the effect of the hybrid automatic repeat request acknowledgement (Hybrid automatic repeat request acknowledgement, HARQ-ACK) feedback corresponding to the Multi-PDSCH scheduling, and thus does not support Multi-PDSCH scheduling.
Notably, at n HARQ-ACK In case the value of (a) does not match the actual situation of Multi-PUSCH scheduling, it may be caused to depend on n HARQ-ACK The calculated transmit power of the PUCCH carrying HARQ-ACK (i.e., P in equation (1) PUCCH,b,f,c (i,q u ,q d I) is not consistent with the actually required transmission power of the terminal, if P PUCCH,b,f,c (i,q u ,q d L) is larger than the actually required transmission power of the terminal and transmits PUCCH based on the transmission power, excessive consumption of electric energy by the terminal can be caused; if P PUCCH,b,f,c (i,q u ,q d L) is smaller than the actually required transmission power of the terminal, the transmission reliability of the PUCCH carrying HARQ-ACK may be reduced, for example: the detection performance of the network side equipment on the PUCCH reception is reduced, including PUCCH missed detection, false detection and the like which cause a larger probability.
While embodiments of the present application may be described in n HARQ-ACK In the calculation process of (1), the target information related to Multi-PDSCH scheduling is considered, so that n is determined according to the target information HARQ-ACK The effective HARQ-ACK bit number contained in the HARQ-ACK codebook can be accurately reflected, and the method is further improved according to the n HARQ-ACK Calculated P PUCCH,b,f,c (i,q u ,q d L) or the matching degree between the transmission power requirement of the PUCCH, so that the transmission reliability of the PUCCH carrying the HARQ-ACK is improved, and the power consumption of the terminal can be reduced.
The power control parameter determining method, the power control parameter determining device and the terminal provided by the embodiment of the application are described in detail below through some embodiments and application scenes thereof with reference to the accompanying drawings.
Referring to fig. 2, the execution body of the power control parameter determining method provided in the embodiment of the present application may be a terminal, where the terminal may include various terminals 11 as listed in the embodiment shown in fig. 1, or may also include other terminals not listed, and the power control parameter determining method may include, as shown in fig. 2, the following steps:
Wherein the first power control parameter may be n in the formula (2) HARQ-ACK The n is HARQ-ACK Calculated n in correlation technique HARQ-ACK The differences of (a) include: in the embodiment of the application, n is determined according to the target information related to Multi-PDSCH scheduling HARQ-ACK Thereby making the n HARQ-ACK The value and meaning of n calculated in the related art HARQ-ACK Is not the same and n is determined in the examples of the present application HARQ-ACK The effective bit number of the HARQ-ACK information under the Multi-PDSCH scheduling can be accurately reflected.
Wherein the target information may include at least one of: the method comprises the steps of carrying out first configuration information of time domain binding transmission, second configuration information of space domain binding transmission, a codebook adopted by the HARQ-ACK and a sub-codebook adopted by the HARQ-ACK.
Option one: it may be determined whether the terminal is configured to transmit the HARQ-ACK using time domain bundling (Time domain bundling) according to the first configuration information.
Option two: and determining whether the terminal is configured to transmit the HARQ-ACK by adopting Spatial bundling according to the second configuration information.
Option three: from the codebook used by HARQ-ACK described above, the HARQ-ACK codebook type used by the HARQ-ACK may be determined, for example: type-1 codebook, type-2 codebook, enhanced Type-2 codebook, or Type-3 codebook. In practice, according to the HARQ-ACK codebook type adopted by the HARQ-ACK, the calculation rule corresponding to the codebook type can be adopted to determine the n HARQ-ACK 。
Option four: for Type-2 codebook, which may include two Sub-codebooks (Sub-codebooks), according to the Sub-codebook adopted by the HARQ-ACK, the calculation rule corresponding to the Sub-codebook may be adopted to determine the n HARQ-ACK . In implementation, the sub-codebook used by the HARQ-ACK may be determined according to the first configuration and/or the second configuration, for example: in the case that Time domain bundling is not configured in any Serving cell corresponding to a PUCCH cell group (cell group) corresponding to the Serving cell, the Type-2 codebook refers to two Sub-codebooks; if Time domain Bundling is configured in all Serving cells configured with Multi-PDSCH scheduling in the PUCCH cell group, and the number of configured Bundling groups is 1, the Type-2 codebook only relates to a single Sub-codebook; if at least one Serving cell of the Serving cells configured with Multi-PDSCH scheduling in the PUCCH cell group is configured with Time domain Bundling, and the number of configured Bundling groups is greater than 1, then the Type-2 codebook refers to two Sub-codebooks.
In this step, n determined in step 201 is considered HARQ-ACK The effective bit number of HARQ-ACK information under Multi-PDSCH scheduling can be accurately reflected, so that the number of the effective bits of HARQ-ACK information can be reduced according to the n HARQ-ACK And the determined sending power of the PUCCH carrying the HARQ-ACK is matched with the effective bit number corresponding to the HARQ-ACK which is required to be sent by the terminal.
Wherein, the transmission power of the PUCCH may be P calculated according to formula (1) PUCCH,b,f,c (i,q u ,q d L), and are not described in detail herein.
In this step, the terminal transmits the PUCCH according to the transmission power matching the number of valid bits of the HARQ-ACK to be transmitted by the terminal, so that the power loss caused by the terminal transmitting the PUCCH can be reduced as much as possible while ensuring the transmission reliability of the PUCCH.
Corresponding to this step 203, the network side device corresponding to the serving cell of the terminal may determine the n according to the same calculation rule based on PDSCH reception and/or DCI indication transmission conditions corresponding to the HARQ-ACK codebook HARQ-ACK And further, according to a formula (1), estimating the PUCCH transmitting power used by the terminal when transmitting the PUCCH carrying the HARQ-ACK, so as to predict the PUCCH receiving performance and adjust the corresponding closed-loop power control adjustment amount according to the requirement. However, in an actual network environment, there may be problems such as DCI missed detection and downlink path loss estimation error, which results in n calculated by the network side device HARQ-ACK N calculated with the terminal HARQ-ACK There may be a certain error, and there is a certain error between the PUCCH transmission power used by the terminal and the PUCCH transmission power used by the network side device expects the terminal. However, the error only affects the PUCCH detection performance of the network side device to a certain extent, and the control of the network side device on the PUCCH transmission performance does not cause the two sides to be unable to interact normally.
In view of HARQ employing different HARQ-ACK codebook typesACK, the calculation rule corresponding to the codebook type can be used to determine the above n HARQ-ACK For convenience of explanation, in the embodiments of the present application, the following 4 embodiments are used to distinguish the calculation rules corresponding to Type-1 codebook, type-2 codebook, enhanced Type-2 codebook or Type-3 codebook, respectively.
Example 1 Type-1 codebook n HARQ-ACK Calculation of
As an optional implementation manner, in a case that the codebook adopted by the HARQ-ACK is a first type codebook, the determining, by the terminal, a first power control parameter according to target information related to the Multi-PDSCH scheduling includes:
the terminal determines at least one of a first variable and a second variable according to the target information;
and the terminal determines the first power control parameter according to at least one of the first variable and the second variable and a first calculation rule corresponding to the first type codebook.
In practice, the first variable mentioned above can be regarded as
The second variable mentioned above can be regarded as +.>
The determining the first power control parameter according to the first calculation rule corresponding to the first codebook according to at least one of the first variable and the second variable may be calculating n according to the following formula HARQ-ACK ：
Notably, n for Type-1 codebook HARQ-ACK When the Type-1 codebook supports Multi-PDSCH scheduling, it may be considered that one or at least two Serving cells in the configuration Serving cell set corresponding to the corresponding PUCCH cell group may be configured with Multi-PDSCH scheduling. At this time, servThere may still be Serving cells in the set of Serving cells that are not configured with Multi-PDSCH scheduling for which CBG transmissions may still be configured. Considering that Multi-PDSCH scheduling and CBG transmission may coexist in the corresponding PUCCH cell group (but cannot coexist in the same Serving cell based on the current discussion conclusion), the first variable in the above equation 
And a second variable->
The meaning and value of (c) can be determined according to the actual situation of Multi-PDSCH scheduling. The Serving cell configured with Multi-PDSCH scheduling may be understood that at least one row of the TDRA table configured with at least one DL BWP is configured with a Serving cell with more than one time domain resource allocation record, where the time domain resource allocation record may be an Entry or an SLIV, or a single time domain resource allocation record corresponds to or includes a single SLIV, for convenience of explanation, the following embodiments take the time domain resource allocation record as an example of an SLIV.
Optionally, in the case that the codebook adopted by the HARQ-ACK is a first type codebook, the determining, by the terminal, a second variable according to the target information includes:
the terminal determines that the second variable is equal to 0.
In implementation, for Serving cells configured with Multi-PDSCH scheduling (CBG transmissions cannot be configured at the same time at this time), the UE can directly assume
In the case of a Serving cell in which Multi-PDSCH scheduling is not configured, when PDSCH-codeblockgrouptransision is configured (when it is necessary to not reconfigure harq-ACK-spatlbundlingpucch),
for the terminal The number of CBGs received by the end within PDSCH reception occasion m of serving cell c, and the PDSCH carrying these CBGs receives DCI (i.e. corresponding non-fallback DCI) scheduling received by the PDSCH supporting CBG based; otherwise->
In practice, for
Can be determined by distinguishing the following cases:
case one
For Serving cells configured with Multi-PDSCH scheduling (CBG transmissions cannot be configured at the same time at this time), when the application Time domain bundling is not configured,
the meaning and value of (a) can be determined by distinguishing between the following cases (Case 1 and Case 2):
case 1: when the UE receives the PDSCH in PDSCH reception occasion m, it is further specifically classified into cases 1-1 to Case 1-2 below.
Case 1-1: when the harq-ACK-SpatialBundlingPUCCH is not configured,
the number of TBs received by the UE within PDSCH reception occasion m of serving cell c.
Case 1-2: when the harq-ACK-spatialbundling pucch is configured,
the number of PDSCH receptions received for the UE within PDSCH reception occasion m of serving cell c.
Case 2: when the UE receives SPS PDSCH release for the PDSCH reception occasion m serving cell c, and feeds back the corresponding HARQ-ACK in this Type-1 codebook for this SPS PDSCH release, 
Case two
For Serving cells configured with Multi-PDSCH scheduling (CBG transmission cannot be configured at the same time at this time), when the application Time domain bundling is configured, it can be determined separately in the following two sub-cases (sub-case 1 and sub-case 2)
Meaning and value of (a).
Sub-case 1 indicates that the terminal receives PDSCH in PDSCH reception occasion m (first occasion); sub-case 2 indicates that the terminal needs to feed back the corresponding HARQ-ACK for SPS PDSCH release (release) in PDSCH reception occasion m.
For sub-case 2 above, when the UE receives SPS PDSCH release for serving cell c PDSCH reception occasion m, and feeds back the corresponding HARQ-ACK in this Type-1 codebook for this SPS PDSCH release,
it should be noted that, in practical applications, application scenarios may also occur that do not satisfy either the above sub-case 1 or the above sub-case 2, for example: the UE does not receive PDSCH nor does it need to feed back the corresponding HARQ-ACK for SPS PDSCH release in PDSCH reception occasion m. This case may be covered by the above sub-case 1 in the embodiment of the present application, or, in the case where neither the above sub-case 1 nor the above sub-case 2 is satisfied, it is independently determined 
Is to take on the value (i.e. determine +.>
) It does not affect +.>
And finally determining the value.
The sub-case 1 is described in detail below according to the configuration of airspace binding:
< when application Spatial bundling is not configured >
As an optional implementation manner, in a case where the HARQ-ACK is configured to transmit with time domain bundling and without space domain bundling, if the terminal receives the PDSCH at the first time, the determining, by the terminal, the first variable according to the target information includes:
the terminal determines that a first variable is equal to the TB number corresponding to the target scheduling line;
wherein the target scheduling row includes a scheduling row mapped to the first occasion, or the target scheduling row includes a scheduling row determined according to a first PDSCH mapped to the first occasion and based on a last time domain resource allocation record association relationship, the scheduling row including: the terminal is actually scheduled or configured to allocate rows of a TDRA table.
The first timing may be any one PDSCH reception occasion m. The scheduling row in the embodiment of the present application can be understood as: for the TDRA table row that the current terminal is actually scheduled (i.e., the terminal receives the downlink scheduling DCI and indicates this TDRA table row) or configured (i.e., configured and activated Semi-persistent scheduling (Semi-Persistent Scheduling, SPS) configuration (Config) uses this TDRA table row), there is corresponding other scheduling information (e.g., other indication information in the scheduling DCI) or configuration information (e.g., corresponding configuration information in SPS Config), and other indication information in the activation DCI).
Sub-case 1-1: the above-mentioned scheduling row mapped to the first occasion can be understood as: a certain scheduling line is mapped to PDSCH reception occasion m based on its Last SLIV, or, alternatively, a certain scheduling line's Last SLIV is mapped to PDSCH reception occasion m. Typically, the number of scheduling rows mapped to PDSCH reception occasion m is 0 or 1; alternatively, the number of scheduling rows mapped to PDSCH reception occasion m may be greater than 1.
It is assumed here that the number of scheduling rows mapped to PDSCH reception occasion M is M, which may be an integer greater than or equal to 0.
Thus, in the case where m=0, the TB number corresponding to the target scheduling line is 0;
in the case where M >0, the TB number corresponding to the target scheduling line may be determined in any of the following manners:
the sum of the number of TB opened by each target scheduling line in the M target scheduling lines;
the TB number of the M target scheduling lines;
the sum of TB numbers configured by each target scheduling row in the M target scheduling rows;
and the TB numbers configured by the M target scheduling lines.
Mode 1
For each of the M target schedule lines, the sum of the number of TB's that each target schedule line was turned on. The number of TBs opened by different target scheduling lines may be the same or different.
Optionally, in a case that the serving cell is not configured to allow dual codeword transmission, the number of TBs that the target scheduling row opens is equal to 1; or alternatively, the process may be performed,
in the case that the serving cell configuration allows dual codeword transmission, the number of TBs that the target scheduling row opens equals any one of:
under the condition of adopting a first TB disabling mode, the downlink control information DCI corresponding to the target scheduling row is the unified starting TB number;
and under the condition of adopting a second TB disabling mode, the DCI corresponding to the target scheduling line is actually started to obtain the TB number.
In practice, TB disable mode (TB disable) can be understood as: when the higher layer configuration allows dual codeword transmission (i.e., a maximum codeword number (maxnrofcodewordsschedule bydci) for which DCI scheduling is configured for its Active DL BWP is n 2) for a given Serving cell of a UE), it may be determined in some way whether a certain TB of one or at least two Valid (Valid) PDSCH for a certain DCI scheduling is on (i.e., actually scheduled) or off (i.e., actually not scheduled).
Wherein, valid PDSCH represents: one or at least two PDSCH of a single DCI schedule, a certain PDSCH that does not collide with Semi-static UL symbol (Semi-static UL symbol), may also be understood as a Scheduled (Scheduled) PDSCH that can be actually transmitted; opposite to Valid PDSCH is an Invalid (Invalid) PDSCH, which represents: one or at least two PDSCH of a single DCI schedule, which may be understood as a Scheduled PDSCH that cannot be actually transmitted, may collide with a Semi-static UL symbol. Among them, the Scheduled PDSCH can be understood as: one or some PDSCH of at least two PDSCHs of a single DCI schedule, which corresponds to some Entry/SLIV configured in a certain row in the TDRA table indicated by the DCI, may be Valid PDSCH or Invalid PDSCH.
In implementation, TB disable may include a first TB disable mode (which may also be referred to as TB disable mode 1) and a second TB disable mode (which may also be referred to as TB disable mode 2).
TB disable mode 1 indicates: for a certain TB (e.g., the first TB or the second TB), all Valid PDSCHs scheduled by a single DCI collectively determine the on/off state. For example: for a certain TB, when the modulation and coding scheme (Modulation and Coding Scheme, MCS) corresponding to this TB is indicated in the DCI to satisfy I MCS When the value of the redundancy version (Redundancy Version, RV) bit sequence corresponding to the TB in the DCI is a predefined 0/1 sequence (), the TB indicating each Valid PDSCH scheduled by the DCI is turned off; when the above condition is not satisfied, the TB of each Valid PDSCH of the DCI schedule is considered to be turned on.
The RV bit sequence corresponding to a certain TB in the DCI may be any one of the following:
1) All RV bits reserved for the TB in the DCI are sequentially cascaded; for example, assuming that the maximum number of Entry/SLIV configured in a certain row in the TDRA table is M, when the number of PDSCH scheduled by a certain DCI is greater than 1, reserving M RV bits for a certain TB in the DCI, i.e. the RV bit sequence corresponding to the TB comprises M bits;
2) All RV bits corresponding to a certain Scheduled PDSCH Scheduled by the DCI are sequentially cascaded from all RV bits reserved for the TB in the DCI; for example: when the number N of PDSCH Scheduled by a certain DCI is greater than 1 (and N < =m), reserving M RV bits for a certain TB in the DCI, where only N RV bits are actually used to indicate RV information of the Scheduled PDSCH, i.e. an RV bit sequence corresponding to the TB includes N bits;
3) All RV bits corresponding to a certain Valid PDSCH scheduled by the DCI are sequentially cascaded from all RV bits reserved by the TB in the DCI; for example: when the number N of PDSCHs scheduled by a certain DCI is greater than 1 (and N < =m), and N1 Valid PDSCHs are included therein (and N1< =n), M RV bits are reserved for a certain TB in the DCI, wherein only N1 RV bits are actually used to indicate RV information of the Valid PDSCH, i.e. an RV bit sequence corresponding to the TB includes N1 bits.
The predefined 0/1 sequence may be an all 0 or all 1 sequence with equal length to the RV bit sequence, for example: for mode 1), the predefined 0/1 sequence may be a full 1 sequence of length M; for mode 2), the predetermined 0/1 sequence may be a full 1 sequence of length N; for mode 2), the predefined 0/1 sequence may be an all 1 sequence of length N1.
TB disable mode 2 represents: for a certain TB (e.g., the first TB or the second TB), each Valid PDSCH of a single DCI schedule independently determines an on/off state.
For example: for a certain TB and a certain Valid PDSCH, when the MCS corresponding to the TB is indicated in the DCI to satisfy I MCS When the value of RV bit corresponding to the TB and the Valid PDSCH in DCI is a predefined value, the TB of the Valid PDSCH is indicated to be turned off; when the above condition is not satisfied, the TB of the Valid PDSCH is considered to be on.
For another example: the RV bits corresponding to a certain TB and a certain Valid PDSCH in the DCI include only a single bit, and the predefined value may be 1, or may be equal to RV id Value corresponding to=2.
In other words, in this embodiment, when the Serving cell is not configured to allow dual codeword transmission, the number of TBs opened per target scheduling row may be regarded as 1; when the Serving cell configuration allows dual codeword transmission, the determination of the TB number that is turned on for each target scheduling row may be any of the following:
when the TB disable mode 1 is adopted, the DCI corresponding to the target scheduling line uniformly opens the TB number;
when the TB disable mode 2 is adopted, the actual starting TB number of the DCI corresponding to the target scheduling line,
For a certain TB (e.g., the first TB or the second TB), when the DCI corresponding to the target scheduling row turns on the TB for at least one Valid PDSCH, the TB may be considered to be actually turned on, otherwise the TB is considered to be actually turned off.
Mode 2
The number of TBs that are turned on for the M target schedule lines.
In some optional embodiments, in a case that the Serving cell is not configured to allow dual codeword transmission, the number of TBs opened by the M target scheduling rows is 1;
in other alternative embodiments, the number of TBs that are turned on by the M target schedule lines includes:
maximum value of TB number of the M target scheduling lines respectively opened;
and determining the number of the turned-on TB according to the M target scheduling lines.
Specifically, in the case that the Serving cell configuration allows dual codeword transmission, the number of TBs that are turned on by the M target scheduling rows may be determined by any one of the following:
1) And taking the maximum value of the number of the TB opened by each target scheduling line.
In implementation, the number of TBs that are turned on by each target scheduling line may be determined in the same manner as the number of TBs that are turned on by the target scheduling line in the case where the serving cell configuration allows dual codeword transmission in mode 1 (e.g., the number of TBs that are turned on by each target scheduling line is determined in a TB disable manner), which is not described in detail herein.
2) Based on the M target scheduling lines, the number of the turned-on TB is judged.
I.e. the number of turned-on TBs is determined according to the situation that each TB is turned on by the M target scheduling lines. Wherein, for a certain TB (e.g., the first TB or the second TB), when at least one of the M target scheduling lines turns on the TB, the TB decision is turned on. It will be appreciated that the number of TBs for which decisions are turned on is 1 or 2.
Mode 3
And for the M target scheduling lines, the sum of the TB numbers configured by each target scheduling line.
In implementation, in the case that the serving cell is not configured to allow dual codeword transmission, the TB number configured by the target scheduling row may be considered as 1; or alternatively, the process may be performed,
in case the serving cell configuration allows for dual codeword transmission, the TB number of the target scheduling row configuration may be considered as 2.
Sum of TB number allocated for each target scheduling line=m×tb number allocated for each scheduling line.
Mode 4
And the TB numbers are configured for the M target scheduling lines. In an implementation, the TB number configured by the M target scheduling rows may be determined directly based on whether the Serving cell is configured to allow dual-codeword transmission, specifically, the TB number is 1 when the Serving cell is not configured to allow dual-codeword transmission, or the TB number is 2.
In the above-described sub-case 1-1,
for the number of TBs corresponding to the scheduled row mapped to PDSCH reception occasion m.
Sub-cases 1-2: in the case that the target scheduling row includes a scheduling row determined according to the first PDSCH mapped to the first occasion and based on the last time domain resource allocation record association relationship, the first PDSCH may be mapped to PDSCH reception occasion m based on the DL slot where it is located and its corresponding SLIV.
The first PDSCH may be a dynamic scheduling PDSCH or an SPS PDSCH, and the first PDSCH may be a Valid PDSCH or an Invalid PDSCH.
The target scheduling row corresponding to the first PDSCH based on the Last SLIV association relationship may be understood as: the first PDSCH is associated with or corresponds to a Last slot of the target scheduling line, or, when the PDSCH is a PDSCH corresponding to a Last Entry/slot of one to a plurality of entries/slots configured in the scheduling line.
It will be appreciated that in cases 1-2, the determination is made
Ways of determining (1) and (1-1) above
Is mainly different in that: in cases 1-2, it is considered that PDSCH or its corresponding SLIV (including DL slot where PDSCH/SLIV is located) is mapped to occupancy when configuring application Time domain bundling, instead of mapping TDRA table row to occupancy, but both are just differences in understanding or description, and their essence or output are consistent.
In implementations, other corresponding scheduling information (e.g., other indication information in the scheduling DCI) or configuration information (e.g., configuration information in the corresponding SPS Config, and other indication information in the activation DCI) exists in view of the scheduling row. In this way, after determining the PDSCH mapped to PDSCH reception occasion M, the scheduling row(s) corresponding to the PDSCH mapped to PDSCH reception occasion M (e.g., M scheduling rows) may be further determined based on the Last SLIV association based on the other scheduling information or configuration information, and the determination may be followed
Is determined by the relevant operation (e.g., any one of modes 1 to 4) in sub-case 1-1 of (a)>
And (5) taking a value.
Optionally, in the case that the PDSCH corresponding to the last time domain resource allocation record of any scheduling line is required to be a valid PDSCH, the determining, by the terminal, that the first variable is equal to the TB number corresponding to the target scheduling line includes:
if the first PDSCH exists and the first PDSCH is associated with or corresponds to the last time domain resource allocation record of the target scheduling line, the terminal determines that the target TB number is equal to the number of TBs opened by the first PDSCH or the configured TB number;
If the first PDSCH does not exist or the first PDSCH is not associated with or corresponds to the last time domain resource allocation record of any scheduling row, the terminal determines that the first variable is equal to 0.
In practice, when the PDSCH corresponding to the Last SLIV of any scheduling line is required to be Valid PDSCH, if there is a PDSCH mapped to PDSCH reception occasion m and the PDSCH is associated with or corresponds to the Last SLIV of a certain scheduling line, the number of TBs turned on by the PDSCH (inevitably Valid PDSCH) or the configured number of TBs may be used as it is
Is a value of (2); otherwise->
< when configuring application Spatial bundling >
As an optional implementation manner, in a case that the codebook adopted by the HARQ-ACK is a first type codebook, where the first type codebook is configured to adopt time domain bundling and adopt space domain bundling for transmission, if the terminal receives the PDSCH at the first time, the determining, by the terminal, a first variable according to the target information includes:
the terminal determines that a first variable is equal to the number of target scheduling lines;
wherein the target scheduling row includes a scheduling row mapped to the first occasion, or the target scheduling row includes a scheduling row determined according to a first PDSCH mapped to the first occasion and based on a last time domain resource allocation record association relationship, the scheduling row including: the terminal is actually scheduled or configured with rows of the TDRA table.
In an implementation, the codebook employed at the HARQ-ACK isA first codebook, where the first codebook is configured to transmit using time domain bundling and using space domain bundling, may be determined in two ways
Is a value of (1):
mode 1
In some implementations, assuming the number of target schedule lines mapped to PDSCH reception occasion M is M, then
In other embodiments, when m=0, it is determined that
When M>At 0, determine +.>
Mode 2
In an implementation, after determining its corresponding target scheduling line (e.g., M target scheduling lines) based on PDSCH mapped to PDSCH reception occasion M (may also be based on scheduling information/configuration information of the scheduling line, etc.) and based on Last SLIV association, the determination may be performed along with the related operation in mode 1 in the above-mentioned sub-case 2
Take on values, no longer being repeated hereSaid.
Optionally, in the case that the PDSCH corresponding to the last time domain resource allocation record of any scheduling row is required to be a valid PDSCH, the terminal determines that the first variable is equal to the number of target scheduling rows, including any one of the following:
If the first PDSCH exists and is associated with or corresponds to the last time domain resource allocation record of the target scheduling line, the terminal determines that the number of the target scheduling lines is equal to 1;
if the first PDSCH does not exist or the first PDSCH is not associated with or corresponds to the last time domain resource allocation record of any scheduling row, the terminal determines that the number of target scheduling rows is equal to 0.
In the present embodiment, when the PDSCH corresponding to the Last SLIV of the scheduling line is always required to be Valid PDSCH, if there is a PDSCH mapped to PDSCH reception occasion m and this PDSCH is associated with or corresponds to the Last SLIV of a certain scheduling line, it is determined that
Otherwise determine->
Example 2 Type-2 codebook n HARQ-ACK Calculation of
As an optional implementation manner, in a case that the codebook adopted by the HARQ-ACK is the second type codebook, the determining, by the terminal, the first power control parameter according to the target information related to the Multi-PDSCH scheduling includes:
under the condition that each cell in a PUCCH cell group is not configured with time domain binding, the terminal determines a first power control parameter according to a first sub-codebook and a second sub-codebook, wherein the PUCCH cell group comprises a serving cell of the terminal, the first sub-codebook corresponds to a single HARQ-ACK granularity, and the second sub-codebook corresponds to a plurality of HARQ-ACK granularities;
The terminal determines a first power control parameter according to the first sub-codebook under the condition that all cells configured with Multi-PDSCH scheduling in the PUCCH cell group are configured with time domain binding and the number of the configured binding groups is equal to 1;
and under the condition that at least one of cells configured with Multi-PDSCH scheduling in the PUCCH cell group is configured with time domain binding and the number of the configured binding groups is greater than 1, the terminal determines a first power control parameter according to the first sub-codebook and the second sub-codebook.
N for Type-2 codebook HARQ-ACK The calculations, in Rel-15/16 are calculated separately for each Sub-codebook, specifically including Sub-codebooks for HARQ-ACK feedback for TB granularity and Sub-codebooks for HARQ-ACK feedback for CBG granularity.
In the embodiment of the present application, when at least one Serving cell corresponding to a certain PUCCH cell group configures Multi-PDSCH scheduling, CBG transmission cannot be configured for any Serving cell in the PUCCH cell group any more, so n for Sub-codebook based on CBG granularity HARQ-ACK feedback need not be considered HARQ-ACK And (5) calculating.
In this embodiment, when at least one Serving cell corresponding to a certain PUCCH cell group configures Multi-PDSCH scheduling, the following cases may be distinguished for the Sub-codebook setting:
Case one
Any Serving cell corresponding to the PUCCH cell group is not configured Time domain bundling.
In this case, type-2 codebook refers to two Sub-codebooks.
The first Sub-codebook may be referred to as a first Sub-codebook, where the first Sub-codebook corresponds to a single HARQ-ACK granularity, i.e. only a single HARQ-ACK needs to be fed back for each DCI/SPS PDSCH. In practice, at least one of the following may be placed in the first Sub-codebook:
scheduling HARQ-ACK corresponding to DCI of a single PDSCH;
HARQ-ACK corresponding to DCI which does not schedule PDSCH but needs feedback HARQ-ACK;
HARQ-ACK corresponding to SPS PDSCH.
The second Sub-codebook may be referred to as a second Sub-codebook, where the second Sub-codebook corresponds to multiple HARQ-ACK granularity, i.e. multiple HARQ-ACKs (i.e. more than one HARQ-ACK) need to be fed back for each DCI. HARQ-ACKs corresponding to DCIs scheduling more than one PDSCH may be placed in the second Sub-codebook.
Case two
The Serving cells configured with Multi-PDSCH scheduling in the PUCCH cell group are configured with Time domain Bundling, and the number of configured Bundling groups is 1.
The second case can be understood as follows: all HARQ-ACKs corresponding to DCIs scheduling more than one PDSCH are operated via Time domain bundling and put into the first Sub-codebook, so in this case, type-2 codebook refers to a single Sub-codebook.
In the second case above, the (unique) first Sub-codebook corresponds to a single HARQ-ACK granularity, i.e. only a single HARQ-ACK needs to be fed back for each DCI/SPS PDSCH. Compared with the first case, the first Sub-codebook can be additionally provided with the Bundled HARQ-ACK corresponding to the DCI which is scheduled to be more than one PDSCH, or the first Sub-codebook can be additionally provided with the HARQ-ACK which is scheduled to be more than one PDSCH and is obtained after time domain binding.
Case three
At least one Serving cell configured Time domain Bundling in the Serving cells configured with Multi-PDSCH scheduling in the PUCCH cell group, and the number of configured Bundling groups is larger than 1.
The third case can be understood as follows: at least HARQ-ACKs corresponding to DCIs scheduling more than one PDSCH are operated via Time domain bundling and placed in a second Sub-codebook.
In the third case, the Type-2 codebook refers to two Sub-codebooks, wherein the first Sub-codebook corresponds to a single HARQ-ACK granularity, i.e. only a single HARQ-ACK needs to be fed back for each DCI/SPS PDSCH. While the second Sub-codebook corresponds to multiple HARQ-ACK granularity, i.e., multiple HARQ-ACKs (i.e., more than one HARQ-ACK) need to be fed back for each DCI.
For example: assuming that N (N > 0) Serving cells in the PUCCH cell group configure Multi-PDSCH scheduling, where M (M >0 and M < =n) Serving cells configure Time domain bundling; the M Serving cells further have M2 (M2 >0 and M2< = M) Serving cells with a number of grouping groups greater than 1, and the M1 (M1 = M-M2) Serving cells with a number of grouping groups of 1. At this time, HARQ-ACKs corresponding to DCIs scheduling more than one PDSCH (when N > M) and/or Bundled HARQ-ACKs corresponding to DCIs scheduling more than one PDSCH (or HARQ-ACKs obtained by time-domain bundling scheduling more than one HARQ-ACK corresponding to DCIs scheduling) may be placed in the second Sub-codebook.
In implementation, the HARQ-ACK corresponding to the Serving cell with the number of the Bundling groups of 1 configured by M1 is placed in the first Sub-codebook. As can be seen from the above, in the above case three phases, compared with the case one, the HARQ-ACKs placed in the first Sub-codebook are basically identical, except that when M1>0, the Bundled HARQ-ACKs corresponding to the DCI scheduled to be greater than one PDSCH may be additionally placed in the first Sub-codebook (or, the HARQ-ACKs obtained by time-domain bundling the HARQ-ACKs corresponding to the DCI scheduled to be greater than one PDSCH may be additionally placed in the first Sub-codebook).
None of the above cases relates to Time domain bundling operation. Both case two and case three involve Time domain bundling operations, and the difference between case two and case three is: and scheduling the HARQ-ACK which is obtained after the HARQ-ACK corresponding to the DCI of more than one PDSCH is subjected to time domain binding, wherein the second Sub-codebook is not placed in the case II, and the second Sub-codebook is placed in the case III.
In some embodiments, when the Type-2 codebook contains only the first Sub-codebook, n is calculated only for the first Sub-codebook HARQ-ACK 。
In other embodiments, when the Type-2 codebook contains two Sub-codebooks, n is calculated for the first Sub-codebook and the second Sub-codebook, respectively HARQ-ACK And then taking the sum of the two.
Optionally, the determining, by the terminal, a first power control parameter according to the first sub-codebook and the second sub-codebook includes:
the terminal determines a first parameter according to a second calculation rule corresponding to the first sub-codebook, and determines a second parameter according to a third calculation rule corresponding to the second sub-codebook;
the terminal determines that the first power control parameter is equal to a sum of the first parameter and the second parameter.
Wherein the first parameter is understood as n determined according to the second calculation rule corresponding to the first sub-codebook HARQ-ACK For ease of distinction, the first parameter will be referred to as n in the following embodiments HARQ-ACK,first The method comprises the steps of carrying out a first treatment on the surface of the The second parameter may be understood as n determined according to a third calculation rule corresponding to the second sub-codebook HARQ-ACK For ease of distinction, the second parameter will be referred to as n in the following embodiments HARQ-ACK,second 。
The following are respectively to n HARQ-ACK,first And n HARQ-ACK,second The determination process of (1) is described:
1. for n HARQ-ACK,first Calculation of (2)
As an optional implementation manner, the determining, by the terminal, a first power control parameter according to the first sub-codebook includes:
the terminal determines a third variable according to the target information;
the terminal determines the first power control parameter based on a second calculation rule and the third variable.
In an implementation, the third variable may be the effective number of bits of the HARQ-ACK determined by the terminal
Based on the foregoing analysis, the first Sub-codebook corresponds to a single HARQ-ACK granularity. And putting the HARQ-ACK corresponding to the DCI for scheduling the single PDSCH, the HARQ-ACK corresponding to the DCI for which the PDSCH is not scheduled but the HARQ-ACK needs to be fed back, and the HARQ-ACK corresponding to the SPS PDSCH into the first Sub-codebook. For cases two/three, in the first And the HARQ-ACK obtained by time domain binding of the HARQ-ACK corresponding to the DCI which is scheduled to be more than one PDSCH can be also put into one Sub-codebook.
In the embodiment of the present application, the second calculation rule may be represented by the following formula (7):
considering "the HARQ-ACK obtained by time-domain bundling the HARQ-ACK corresponding to DCI scheduling more than one PDSCH may be further put in the first Sub-codebook", the above formula (7)
The determination of (2) can be distinguished between the following cases 1.1 and 1.2:
case 1.1
The terminal detects DCI scheduling PDSCH within PDCCH monitoring occasion m.
Wherein, the DCI scheduling the PDSCH may include: DCI scheduling only a single PDSCH; DCI for scheduling at least two PDSCH. For the second or third case, when the serving cell c configures Multi-PDSCH scheduling and Time domain Bundling and the number of configured Bundling groups is 1, the decoding result of at least two PDSCHs of the scheduling obtains a single HARQ-ACK bit based on Time domain Bundling and is put into the first Sub-codebook, which is not described herein again.
The above case 1.1 can be further specifically divided into the following case 1.1.1 and case 1.1.2:
Case 1.1.1
When the application Spatial bundling is not configured, it can be determined by
As an optional implementation manner, when the terminal detects DCI for scheduling PDSCH in the second occasion and no spatial bundling is configured, the determining, by the terminal, a third variable according to the target information includes:
and the terminal determines that the third variable is equal to the TB number actually opened by the PDSCH scheduling DCI detected by the terminal in the second time.
Wherein the second time may be PDCCH monitoring occasion m, that is, the third variable
And scheduling the actual number of the opened TB of the DCI for the PDSCH detected by the terminal in PDCCH monitoring occasion m.
In an implementation, in a case that the serving cell is not configured to allow dual codeword transmission, the number of TBs actually turned on by each PDSCH scheduling DCI may be equal to 1; or alternatively, the process may be performed,
the actual number of TBs turned on per PDSCH scheduling DCI may be any one of the following:
under the condition of adopting a first TB disabling mode, each PDSCH schedules the unified starting TB number of DCI;
in the case of the second TB de-enabling mode, each PDSCH schedules the actual number of TBs that are turned on by DCI,
Wherein, for a certain TB (e.g., the first TB or the second TB), when the DCI turns on the TB for at least one Valid PDSCH, the TB may be considered to be actually turned on, otherwise the TB is considered to be actually turned off.
In an implementation, when the terminal in PDCCH monitoring occasion m only allows detection of a single PDSCH scheduling DCI for a single Serving cell, the actual number of TBs that are turned on for the detected single PDSCH scheduling DCI is taken as
When the terminal in PDCCH monitoring occasion m allows detection of more than one PDSCH scheduling DCI for a single Serving cell, adding the actually opened TB number for each detected PDSCH scheduling DCI as +.>
As another optional implementation manner, when the terminal detects DCI for scheduling PDSCH in the second occasion and no spatial bundling is configured, the determining, by the terminal, a third variable according to the target information includes:
and the terminal determines that the third variable is equal to the TB number configured by PDSCH scheduling DCI detected by the terminal in the second occasion.
Similar to the third variable described above, which is equal to the number of TBs actually opened by the PDSCH scheduling DCI detected by the terminal in the second occasion, in a case where the serving cell is not configured to allow dual codeword transmission, the number of TBs configured by each PDSCH scheduling DCI may be equal to 1.
Further, in case the serving cell configuration allows dual codeword transmission, the number of TBs per PDSCH scheduling DCI configuration may be equal to 2.
Optionally, the determining, by the terminal, a third variable according to the target information includes:
in the second occasion, under the condition that the terminal only allows detection of single PDSCH scheduling DCI for a single serving cell, the terminal determines that the third variable is equal to the number of TBs actually opened or the number of TBs configured by the single PDSCH scheduling DCI detected by the terminal; or alternatively, the process may be performed,
in the case that the terminal allows detection of at least two PDSCH scheduling DCIs for a single serving cell in the second occasion, the terminal determines that the third variable is equal to the sum of the number of TBs actually turned on or the number of TBs configured by all PDSCH scheduling DCIs detected by the terminal.
Wherein, the second time may be PDCCH monitoring occasion m, and when the terminal in PDCCH monitoring occasion m only allows detecting a single PDSCH scheduling DCI for a single Serving cell, the number of TBs configured for the detected single PDSCH scheduling DCI is taken as the number of TBs
When the terminal in PDCCH monitoring occasion m allows detection of more than one PDSCH scheduling DCI for a single Serving cell, it will schedule DCI for each detected Sum of TB numbers allocated to PDSCH scheduling DCI as +.>
Or (F)>
Case 1.1.2
Optionally, when the terminal detects DCI for scheduling PDSCH in the second occasion and configures application of spatial bundling, the determining, by the terminal, a third variable according to the target information includes:
the terminal determines that the third variable is equal to the number of PDSCH scheduling DCIs detected by the terminal in the second occasion.
In this case 1.1.2, when the application Spatial bundling is configured,
the DCI number is scheduled for the PDSCH detected by the terminal in PDCCH monitoring occasion m.
Case 1.2
The terminal detects DCI without scheduling PDSCH but requiring feedback HARQ-ACK within PDCCH monitoring occasion m.
In the case 1.2 described above,
the terminal may detect the number of DCIs for serving cell c that do not schedule PDSCH reception but require feedback for the corresponding HARQ-ACK within PDCCH monitoring occasion m.
When only case 1.1 or case 1.2 is satisfied, case 1.1 or case 1.2 may be satisfied
When both cases 1.1 and 1.2 are satisfied, each case will beCondition-related +.>
Added as final +.>
When neither case 1.1 nor case 1.2 is satisfied, the +_ >
2. For n HARQ-ACK,second Calculation of (2)
Based on the foregoing analysis, the second Sub-codebook corresponds to multiple HARQ-ACK granularity. And (3) putting the HARQ-ACK corresponding to the DCI which is scheduled to be more than one PDSCH into the second Sub-codebook, and/or carrying out time domain bundling on the HARQ-ACK corresponding to the DCI which is scheduled to be more than one PDSCH.
Optionally, the determining, by the terminal, the second parameter according to a third calculation rule corresponding to the second sub-codebook includes:
the terminal determines a fourth variable according to the target information;
the terminal determines a second parameter based on a third calculation rule and the fourth variable.
Wherein the fourth variable may include
The method is used for reflecting the actual scheduling situation (particularly, the following situation 2.1) of the first type of DCI detected by the terminal in the PDCCH detection occasion m for the serving cell c, wherein the first type of DCI can be DCI used for scheduling more than one PDSCH.
In implementation, for the third calculation rule, the following cases 2.1 and 2.2 may be specifically divided to determine the second parameter respectively:
case 2.1
When the second Sub-codebook does not involve or put in the HARQ-ACK obtained by time-domain bundling the HARQ-ACKs corresponding to the DCIs scheduling more than one PDSCH (corresponding to the above case one/case two).
Optionally, the determining, by the terminal, the second parameter according to a third calculation rule corresponding to the second sub-codebook includes:
in the case that the second sub-codebook does not include the target HARQ-ACK including the HARQ-ACK obtained by time-domain bundling the first HARQ-ACK, the terminal determines the second parameter according to the following formula (7):
wherein the first HARQ-ACK is HARQ-ACK corresponding to DCI for scheduling at least two PDSCH, n HARQ-ACK,second Representing a second parameter determined according to a third calculation rule corresponding to the second sub-codebook;
at the position of
When (I)>
Representing the value of a count DAI carried by the last first DCI detected by the terminal in M PDCCH detection occasions for any service cell, wherein the first DCI comprises DCIs for scheduling more than one PDSCH;
at the position of
When (I)>
Representing the value of the total DAI carried by the last first DCI detected by the terminal in the M PDCCH detection occasions aiming at any service cell;
when the terminal does not detect any of the first type DCI for any serving cell within M PDCCH detection occasions, 
when the spatial bundling is not configured to be applied,
the maximum codeword number (i.e., the value of parameter maxnrofcodewordsschedule bydci) of DCI schedule configured for serving cell c; when configuring application airspace binding, +.>
If airspace binding is not configured, then
The total number of actually scheduled transmission blocks of the first type DCI detected by the UE for the serving cell c in the PDCCH detection opportunity m; if airspace binding is configured, +.>
The total number of valid PDSCH scheduled for the first type of DCI detected by the UE for serving cell c within PDCCH detection occasion m.
In this embodiment, the fourth variable may include
The third calculation rule may be expressed as the above formula (7). And in the above formula (7), for +.>
The following case determinations can be distinguished:
case 2.1.1
When the application Spatial bundling is not configured,
the total number of TBs actually scheduled by DCI is scheduled for PDSCH scheduling more than one PDSCH detected by the UE for Serving cell c within PDCCH monitoring occasion m. For a single PDSCH scheduling DCI, each Valid PDSCH scheduled by the single PDSCH scheduling DCI may determine the number of TBs (1 or 2) carried based on whether Serving cell c is configured to allow transmission of a Xu Shuang codeword and the TB disable mode 1/2, where the number of TBs actually scheduled by the PDSCH scheduling DCI is the sum of the number of TBs carried by each Valid PDSCH scheduled by the PDSCH scheduling DCI.
Case 2.1.2
When configuring an application Spatial bundling,
for UE in PDCCH monitoring occasion m for Serving cell c detected PDSCH scheduling DCI scheduling Valid PDSCH total number of more than one PDSCH. />
In an implementation, when the UE in PDCCH monitoring occasion m only allows detecting a single PDSCH to schedule DCI for a single Serving cell, the number of TBs actually scheduled (when Spatial bundling is not configured to be applied) or the number of Valid PDSCHs scheduled (when Spatial bundling is configured to be applied) for the detected single PDSCH to schedule DCI is taken as
When the UE allows detection of more than one PDSCH scheduling DCI for a single Serving cell in PDCCH monitoring occasion m, the number of TB actually scheduled (when Spatial bundling is not configured to be applied) or the number of Valid PDSCH scheduled (when Spatial bundling is configured to be applied) for each detected PDSCH scheduling DCI is added as->
Case 2.2
When the second Sub-codebook refers to or puts in the HARQ-ACK obtained after time domain bundling of the HARQ-ACK corresponding to the DCI scheduled for more than one PDSCH.
Optionally, in the case that the second sub-codebook includes the target HARQ-ACK, the terminal determines the second parameter according to the following formula (8):
Wherein, the liquid crystal display device comprises a liquid crystal display device,
representing the number of Multi-feedback cells in the PUCCH cell group, wherein the Multi-feedback cells belong to a first type cell or a second type cell, the first type cell is a service cell configured with Multi-PDSCH scheduling and not configured with time domain bundling (i.e. not configured with number OfHARQ-bundling groups parameters), the second type cell is a service cell configured with Multi-PDSCH scheduling,and configured time domain binding service cells with the number of the configured binding groups being greater than 1;
For the first cell c, the corresponding first maximum value is based on
Calculation of->
A maximum number of PDSCH receptions schedulable for a single DCI of the first type corresponding to the first cell c; the first cell is
Any one of the multiple feedback cells belongs to the multiple feedback cells of the first type of cells;
for the second cell c, the corresponding first maximum is based on
Calculation of->
The number of binding groups configured for the second cell c; the second cell is +>
Any one of the multiple feedback cells belongs to the multiple feedback cells of the second type of cells;
In this embodiment, the fourth variable may include 
The third calculation rule may be expressed as the above formula (8).
In the above-mentioned formula (8),
meaning and value of (c) can be determined by distinguishing between:
case 2.2.1
When the application Spatial bundling is not configured,
and (3) scheduling the total number of Bundling groups actually scheduled by DCIs (downlink control channel) for each TB for the PDSCH which is detected by the UE for the Serving cell c in PDCCH monitoring occasion m and used for scheduling more than one PDSCH. For single PDSCH scheduling DCI, the Bundling group actually scheduled for a certain TB (first TB or second TB when Serving cell c is configured with dual codeword transmission; only first TB when Serving cell c is not configured with dual codeword transmission) may be understood as: when a Bundling group contains at least one Valid PDSCH, and at least one Valid PDSCH opens the TB, the Bundling group is considered to be actually scheduled. Based on whether Serving cell c is configured to allow dual codeword transmission and the Bundling group division mode applied, the Bundling group number actually scheduled by a single PDSCH scheduling DCI for a certain TB can be determined. When Serving cell c configures dual-codeword transmission, the number of Bundling groups actually scheduled by a single PDSCH scheduling DCI for each TB is the sum of the number of Bundling groups actually scheduled for two TBs respectively; when the Serving cell c is not configured with dual-codeword transmission, the number of Bundling groups actually scheduled by the single PDSCH scheduling DCI for each TB is the number of Bundling groups actually scheduled for the first TB.
Case 2.2.2
When configuring an application Spatial bundling,
and scheduling a total number of Bundling groups (DCIs) actually scheduled for PDSCH detected by the UE for Serving cell c to schedule more than one PDSCH in PDCCH monitoring occasion m. For single PDSCH scheduling DCI, the actual scheduled Bundling group can be interpreted as: when a Bundling group contains at least one Valid PDSCH, the Bundling group is considered to be actually scheduled.
Case 2.2.3
When the UE in PDCCH monitoring occasion m only allows detection of a single PDSCH scheduling DCI for a single Serving cell, the number of Bundling groups actually scheduled for each TB (when Spatial Bundling is not configured) or the number of Bundling groups actually scheduled (when Spatial Bundling is configured) for the detected single PDSCH scheduling DCI is taken as
When the UE in PDCCH monitoring occasion m allows detecting more than one PDSCH scheduling DCI for a single Serving cell, the number of Bundling groups actually scheduled for each TB (when Spatial Bundling is not configured to be applied) or the number of Bundling groups actually scheduled (when Spatial Bundling is configured to be applied) for each detected PDSCH scheduling DCI is added as ∈ >
In addition, the meaning of the other parameters in the above formula (8) other than the above fourth variable is described as follows:
1) When (when)
When (I)>
The value of the counter DAI carried by the last second type DCI detected by the UE in M PDCCH monitoring occasion aiming at any service cell is calculated;
2) When (when)
When (I)>
The value of total DAI carried by the last second type DCI detected by the UE in M PDCCH monitoring occasion aiming at any serving cell is calculated;
3) When the UE does not detect any second type of DCI for any serving cell within M PDCCH monitoring occasion,
the second type of DCI here needs to satisfy all of the following features: (1) scheduling more than one PDSCH; (2) The Serving cell corresponding to the scheduled PDSCH is not configured Time domain Bundling, or Time domain Bundling is configured and the number of configured Bundling groups is greater than 1.
1)
for the UE, for serving cell c, the total number of second-type DCIs detected in M PDCCH monitoring occasion;
2) When the UE detects no second type of DCI in M PDCCH monitoring occasion for serving cell c, 
In the case of the third case of the present invention,
a Serving cell with Multi-PDSCH scheduling and no Serving cell Time domain Bundling is configured in the PUCCH cell group, a Serving cell with Multi-PDSCH scheduling and Time domain Bundling and a Bundling group number greater than 1 is configured, or stated otherwise,
the number of Serving cells with Multi-PDSCH scheduling is configured in the PUCCH cell group, when a certain Serving cell is configured with Time domain Bundling, the number is only included in +.>
And (3) inner part. Note that +.>
The values are the following +.>
Alternatively, the process may be carried out in a single-stage,
directly is->
(number of Serving cells corresponding to PUCCH cell group), at this time, for Serving cells not configured with Multi-PDSCH scheduling, or Serving cells configured with Multi-PDSCH scheduling, time domain Bundling and configured with 1 number of Bundling groups, corresponding to
For the following
Serving cell c of the individual serving cells, when number ofharq-bundling groups are configured (i.e. Time domain bundling is configured), use +.>
As its corresponding value, use +.A when no NumberOfHARQ-BundlingGroups is configured (i.e. Time domain bundling is not configured)>
As its corresponding value; walk- >
Obtaining the maximum value of the value corresponding to each service cell;
when the application Spatial bundling is not configured,
the value of maxnrofcodewordsschedule bydci configured for serving cell c; when configuring application Spatial bundling +.>
In summary, when the Type-2 codebook contains two Sub-codebooks, n can be calculated for the first Sub-codebook and the second Sub-codebook, respectively HARQ-ACK And then taking the sum of the two.
That is, the terminal determining a first power control parameter according to the first sub-codebook and the second sub-codebook includes:
the terminal determines a first parameter according to a second calculation rule corresponding to the first sub-codebook, and determines a second parameter according to a third calculation rule corresponding to the second sub-codebook;
the terminal determines that the first power control parameter is equal to a sum of the first parameter and the second parameter.
Wherein the process of determining the first parameter according to the second calculation rule corresponding to the first sub-codebook and the n HARQ-ACK,first The meaning and the determining process of the first sub-codebook are the same, that is, the terminal determines the first parameter according to the second calculation rule corresponding to the first sub-codebook, which may include:
The terminal determines a third variable according to the target information;
the terminal determines a first parameter based on a second calculation rule and the third variable.
In addition, the process of determining the second parameter according to the third calculation rule corresponding to the second sub-codebook and the n HARQ-ACK,second The meaning of the second sub-codebook is the same as the determining process, namely the terminal determines a second parameter according to a third computing rule corresponding to the second sub-codebook, including:
the terminal determines a fourth variable according to the target information;
the terminal determines a second parameter based on a third calculation rule and the fourth variable.
The process of determining the first parameter by the terminal based on the second calculation rule and the third variable and the process of determining the second parameter by the terminal based on the third calculation rule and the fourth variable are not described in detail.
Example 3 n for enhanced Type-2 codebook HARQ-ACK Calculation of (2)
For enhanced Type-2 codebook, each PDSCH group referred to by it corresponds to n HARQ-ACK The calculation may be along n for Type-2 codebook in embodiments of the present application HARQ-ACK The other rules may be similar to the corresponding rules in Rel-16 and are not described in detail herein.
Example 4 n for Type-3 codebook HARQ-ACK Calculation of (2)
For Type-3 codebook (including enhanced Type-3 codebook), it is based on HARQ process construction, and is not affected by whether Multi-PDSCH scheduling and Time domain bundling are configured.
In the embodiment of the application, under the condition that a serving cell of a terminal is configured with Multi-Physical Downlink Shared Channel (PDSCH) scheduling, the terminal determines a first power control parameter according to target information related to the Multi-PDSCH scheduling, wherein the first power control parameter comprises the effective bit number of hybrid automatic repeat request (HARQ-ACK); the terminal determines the transmission power of a Physical Uplink Control Channel (PUCCH) carrying the HARQ-ACK according to the first power control parameter; and the terminal sends the PUCCH to network side equipment according to the sending power. In this way, when the service cell of the terminal is configured with Multi-PDSCH scheduling, the first power control parameter can be determined according to the target information related to the Multi-PDSCH scheduling, so that the first power control parameter is matched with the effective HARQ-ACK bit number contained in the HARQ-ACK codebook, and the value of the determined first power control parameter is matched with the actual Multi-PDSCH scheduling transmission, so that the transmission power of the PUCCH carrying HARQ-ACK determined according to the first power control parameter is matched with the transmission power actually required by the terminal, and further the transmission performance of the PUCCH carrying HARQ-ACK is ensured.
According to the power control parameter determining method provided by the embodiment of the application, the execution body can be the power control parameter determining device. In the embodiment of the present application, a method for determining a power control parameter by using a power control parameter determining device is taken as an example, and the power control parameter determining device provided in the embodiment of the present application is described.
Referring to fig. 3, a power control parameter determining apparatus provided in the embodiments of the present application may be applied to a terminal, and as shown in fig. 3, the power control parameter determining apparatus 300 may include the following modules:
a first determining module 301, configured to determine a first power control parameter according to target information related to Multi-PDSCH scheduling when a serving cell of a terminal is configured with Multi-physical downlink shared channel PDSCH scheduling, where the first power control parameter includes a valid bit number of hybrid automatic repeat request acknowledgement HARQ-ACK;
a second determining module 302, configured to determine, according to the first power control parameter, a transmission power of a physical uplink control channel PUCCH carrying the HARQ-ACK;
and a sending module 303, configured to send the PUCCH to a network side device according to the sending power.
Optionally, the target information includes at least one of: the method comprises the steps of carrying out first configuration information of time domain binding transmission, carrying out second configuration information of space domain binding transmission, adopting a codebook for HARQ-ACK and adopting a sub-codebook for HARQ-ACK.
Optionally, in the case that the codebook adopted by the HARQ-ACK is a first type codebook, the first determining module 301 includes:
a first determining unit configured to determine at least one of a first variable and a second variable according to the target information;
and the second determining unit is used for determining the first power control parameter according to at least one of the first variable and the second variable and a first calculation rule corresponding to the first codebook.
Optionally, in the case where the HARQ-ACK is configured to transmit with time domain bundling and without spatial domain bundling, if the terminal receives the PDSCH in the first time slot, the first determining unit is specifically configured to:
determining that a first variable is equal to the TB number corresponding to the target scheduling line;
wherein the target scheduling row includes a scheduling row mapped to the first occasion, or the target scheduling row includes a scheduling row determined according to a first PDSCH mapped to the first occasion and based on a last time domain resource allocation record association relationship, the scheduling row including: the terminal is actually scheduled or configured to allocate rows of a TDRA table.
Optionally, the number of the target scheduling lines is M, and in the case of m=0, the number of TBs corresponding to the target scheduling lines is 0; or alternatively, the process may be performed,
In the case where M > 0, the TB number corresponding to the target scheduling line is any one of the following:
the sum of the number of TB opened by each target scheduling line in the M target scheduling lines;
the TB number of the M target scheduling lines;
the sum of TB numbers configured by each target scheduling row in the M target scheduling rows;
and the TB numbers configured by the M target scheduling lines.
Optionally, in the case that the serving cell is not configured to allow dual codeword transmission, the number of TBs opened by the target scheduling row is equal to 1; or alternatively, the process may be performed,
in the case that the serving cell configuration allows dual codeword transmission, the number of TBs that the target scheduling row opens equals any one of:
under the condition of adopting a first TB disabling mode, the downlink control information DCI corresponding to the target scheduling row is the unified starting TB number;
and under the condition of adopting a second TB disabling mode, the DCI corresponding to the target scheduling line is actually started to obtain the TB number.
Optionally, the number of TBs opened by the M target scheduling rows includes:
maximum value of TB number of the M target scheduling lines respectively opened;
and determining the number of the turned-on TB according to the M target scheduling lines.
Optionally, in a case that the serving cell is not configured to allow dual codeword transmission, the TB number configured by the target scheduling row is equal to 1; or alternatively, the process may be performed,
In the case that the serving cell configuration allows dual codeword transmission, the TB number of the target scheduling row configuration is equal to 2.
Optionally, in a case that a PDSCH corresponding to a last time domain resource allocation record of any scheduling row is required to be a valid PDSCH, the first determining unit includes:
a first determining subunit, configured to determine that, if the first PDSCH exists and the first PDSCH is associated with or corresponds to a last time domain resource allocation record of a target scheduling row, the target TB number is equal to an opened TB number or a configured TB number of the first PDSCH;
a second determining subunit, configured to determine that the first variable is equal to 0 if the first PDSCH does not exist or the first PDSCH is not associated with or corresponds to a last time domain resource allocation record of any scheduling row.
Optionally, when the codebook adopted by the HARQ-ACK is a first type codebook, and the first type codebook is configured to adopt time domain binding and adopt space domain binding for transmission, if the terminal receives the PDSCH in the first time, the first determining unit is specifically configured to:
determining that the first variable is equal to the number of target scheduling rows;
wherein the target scheduling row includes a scheduling row mapped to the first occasion, or the target scheduling row includes a scheduling row determined according to a first PDSCH mapped to the first occasion and based on a last time domain resource allocation record association relationship, the scheduling row including: the terminal is actually scheduled or configured with rows of the TDRA table.
Optionally, in a case that a PDSCH corresponding to a last time domain resource allocation record of any scheduling row is required to be a valid PDSCH, the first determining unit is specifically configured to execute any one of the following:
if the first PDSCH exists and is associated with or corresponds to the last time domain resource allocation record of the target scheduling line, determining that the number of the target scheduling lines is equal to 1;
if the first PDSCH does not exist or the first PDSCH is not associated with or corresponds to the last time domain resource allocation record of any scheduling row, determining that the number of target scheduling rows is equal to 0.
Optionally, in case the codebook adopted by the HARQ-ACK is a first type codebook, the first determining unit is further configured to:
determining that the second variable is equal to 0.
Optionally, in the case that the codebook adopted by the HARQ-ACK is the second type codebook, the first determining module 301 includes:
a third determining unit, configured to determine, according to a first sub-codebook and a second sub-codebook, a first power control parameter when each cell in a PUCCH cell group is not configured with time domain bundling, where the PUCCH cell group includes a serving cell of the terminal, the first sub-codebook corresponds to a single HARQ-ACK granularity, and the second sub-codebook corresponds to multiple HARQ-ACK granularities;
A fourth determining unit, configured to determine a first power control parameter according to the first sub-codebook when all cells configured with Multi-PDSCH scheduling in the PUCCH cell group are configured with time domain bundling and the number of configured bundling groups is equal to 1;
a fifth determining unit, configured to determine a first power control parameter according to the first sub-codebook and the second sub-codebook when at least one of cells configured with Multi-PDSCH scheduling is configured with time domain bundling in the PUCCH cell group and the number of configured bundling groups is greater than 1.
Optionally, the third determining unit and/or the fifth determining unit includes:
a third determining subunit, configured to determine a first parameter according to a second calculation rule corresponding to the first sub-codebook, and determine a second parameter according to a third calculation rule corresponding to the second sub-codebook;
and a fourth determining subunit configured to determine that the first power control parameter is equal to a sum of the first parameter and the second parameter.
Optionally, the fourth determining unit includes:
a fifth determining subunit, configured to determine a third variable according to the target information;
a sixth determination subunit configured to determine the first power control parameter based on a second calculation rule and the third variable.
Optionally, the third determining subunit includes:
a first determining subunit, configured to determine a third variable according to the target information;
a second determining subunit configured to determine a first parameter based on a second calculation rule and the third variable;
and/or the number of the groups of groups,
the third determining subunit further includes:
a third determination subunit, configured to determine a fourth variable according to the target information;
and a fourth determining subunit configured to determine the second parameter based on the third calculation rule and the fourth variable.
Optionally, when the terminal detects DCI for scheduling PDSCH in the second occasion and the application of spatial bundling is not configured, the fifth determining subunit and/or the first determining subunit are specifically configured to:
and determining that the third variable is equal to the actual number of the opened TB or the configured number of the TB of the PDSCH scheduling DCI detected by the terminal in the second time.
Optionally, in the case that the serving cell is not configured to allow dual codeword transmission, each PDSCH schedules the actual number of TBs opened by DCI or the number of TBs configured to be equal to 1; or alternatively, the process may be performed,
in the case that the serving cell configuration allows dual codeword transmission, the TB number of each PDSCH scheduling DCI configuration is equal to 2, or the TB number actually turned on by each PDSCH scheduling DCI is any one of the following:
Under the condition of adopting a first TB disabling mode, each PDSCH schedules the unified starting TB number of DCI;
and under the condition of adopting a second TB disabling mode, each PDSCH schedules the actual number of the turned-on TB of the DCI.
Optionally, the fifth determining subunit and/or the first determining subunit are specifically configured to:
in the second occasion, under the condition that the terminal only allows detecting single PDSCH scheduling DCI for a single serving cell, determining that the third variable is equal to the number of TBs actually opened or the number of TBs configured by the single PDSCH scheduling DCI detected by the terminal; or alternatively, the process may be performed,
and in the second occasion, under the condition that the terminal allows detection of at least two PDSCH scheduling DCIs for a single serving cell, determining that the third variable is equal to the sum of the actually opened TB numbers or the configured TB numbers of all PDSCH scheduling DCIs detected by the terminal.
Optionally, when the terminal detects DCI for scheduling PDSCH in the second occasion and configures application of spatial bundling, the fifth determining subunit and/or the first determining subunit are specifically configured to:
and determining that the third variable is equal to the number of PDSCH scheduling DCIs detected by the terminal in the second occasion.
Optionally, the third determining subunit is specifically configured to:
in the case that the second sub-codebook does not include the target HARQ-ACK, where the target HARQ-ACK includes the HARQ-ACK obtained by time-domain bundling the first HARQ-ACK, the terminal determines the second parameter according to the following formula:
wherein the first HARQ-ACK is HARQ-ACK corresponding to DCI for scheduling at least two PDSCH, n HARQ-ACK,second Representing a second parameter determined according to a third calculation rule corresponding to the second sub-codebook;
at the position of
When (I)>
Representing the value of a count DAI carried by the last first DCI detected by the terminal in M PDCCH detection occasions for any service cell, wherein the first DCI comprises DCIs for scheduling more than one PDSCH;
at the position of
When (I)>
Representing the value of the total DAI carried by the last first DCI detected by the terminal in the M PDCCH detection occasions aiming at any service cell;
when the terminal does not detect any of the first type DCI for any serving cell within M PDCCH detection occasions, 
when the spatial bundling is not configured to be applied,
the maximum codeword number of DCI scheduling configured for serving cell c; when configuring application airspace binding, +.>
If airspace binding is not configured, then
The total number of actually scheduled transmission blocks of the first type DCI detected by the UE for the serving cell c in the PDCCH detection opportunity m; if airspace binding is configured, +.>
The total number of the effective PDSCH scheduled by the UE aiming at the first DCI detected by the serving cell c in the PDCCH detection time m;
and/or the number of the groups of groups,
in case the second sub-codebook comprises the target HARQ-ACK, the terminal determines the second parameter according to the following formula:
wherein, the liquid crystal display device comprises a liquid crystal display device,
representing the number of Multi-feedback cells in the PUCCH cell group, wherein the Multi-feedback cells belong to a first type cell or a second type cell, the first type cell is a service cell configured with Multi-PDSCH scheduling and not configured with time domain bundling, and the second type cell is a service cell configured with Multi-PDSCH scheduling and configured with time domain bundling and with the number of configured bundling groups being more than 1;
For the first cell c, the corresponding first maximum value is based on
Calculation of->
A maximum number of PDSCH receptions schedulable for a single DCI of the first type corresponding to the first cell c; the first cell is
Any one of the multiple feedback cells belongs to the multiple feedback cells of the first type of cells;
for the second cell c, the corresponding first maximum is based on
Calculation of->
The number of binding groups configured for the second cell c; the second cell is +>
Any one of multiple feedback cells belongs to multiple feedback cells of second type cell；
The power control parameter determining apparatus 300 provided in the embodiment of the present application can execute each process in the power control parameter determining method shown in fig. 2, and can obtain the same beneficial effects, and for avoiding repetition, the description is omitted herein.
The power control parameter determining apparatus 300 in the embodiment of the present application may be an electronic device, for example, an electronic device with an operating system, or may be a component in an electronic device, for example, an integrated circuit or a chip. The electronic device may be a terminal, or may be other devices than a terminal. By way of example, terminals may include, but are not limited to, the types of terminals 11 listed above, other devices may be servers, network attached storage (Network Attached Storage, NAS), etc., and embodiments of the application are not specifically limited.
Optionally, as shown in fig. 4, the embodiment of the present application further provides a communication device 400, including a processor 401 and a memory 402, where the memory 402 stores a program or an instruction that can be executed on the processor 401, for example, when the communication device 400 is a terminal, the program or the instruction is executed by the processor 401 to implement each step of the above-mentioned embodiment of the method for determining a power control parameter, and the same technical effects can be achieved. When the communication device 400 is a network side device, the program or instruction, when executed by the processor 401, implements the steps of the above-described method embodiment for determining a power control parameter, and the same technical effects can be achieved, so that repetition is avoided, and no further description is given here.
The embodiment of the application also provides a terminal, which comprises a processor and a communication interface, wherein the processor is used for determining a first power control parameter according to target information related to Multi-Physical Downlink Shared Channel (PDSCH) scheduling when a service cell of the terminal is configured with the Multi-Physical Downlink Shared Channel (PDSCH) scheduling, the first power control parameter comprises the effective bit number of hybrid automatic repeat request acknowledgement (HARQ-ACK), and is used for determining the transmission power of a Physical Uplink Control Channel (PUCCH) carrying the HARQ-ACK according to the first power control parameter, and the communication interface is used for transmitting the PUCCH to network side equipment according to the transmission power. The terminal embodiment corresponds to the terminal-side method embodiment, and each implementation process and implementation manner of the method embodiment are applicable to the terminal embodiment and can achieve the same technical effects. Specifically, fig. 5 is a schematic hardware structure of a terminal for implementing an embodiment of the present application.
The terminal 500 includes, but is not limited to: at least some of the components of the radio frequency unit 501, the network module 502, the audio output unit 503, the input unit 504, the sensor 505, the display unit 506, the user input unit 507, the interface unit 508, the memory 509, and the processor 510.
Those skilled in the art will appreciate that the terminal 500 may further include a power source (e.g., a battery) for powering the various components, and the power source may be logically connected to the processor 510 by a power management system for performing functions such as managing charging, discharging, and power consumption by the power management system. The terminal structure shown in fig. 5 does not constitute a limitation of the terminal, and the terminal may include more or less components than shown, or may combine certain components, or may be arranged in different components, which will not be described in detail herein.
It should be appreciated that in embodiments of the present application, the input unit 504 may include a graphics processing unit (Graphics Processing Unit, GPU) 5041 and a microphone 5042, with the graphics processor 5041 processing image data of still pictures or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The display unit 506 may include a display panel 5061, and the display panel 5061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 507 includes at least one of a touch panel 5071 and other input devices 5072. Touch panel 5071, also referred to as a touch screen. Touch panel 5071 may include two parts, a touch detection device and a touch controller. Other input devices 5072 may include, but are not limited to, physical keyboards, function keys (e.g., volume control keys, switch keys, etc.), trackballs, mouse marks, and joysticks, which are not further described herein.
In this embodiment, after receiving downlink data from the network side device, the radio frequency unit 501 may transmit the downlink data to the processor 510 for processing; in addition, the radio frequency unit 501 may send uplink data to the network side device. Typically, the radio frequency unit 501 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
The memory 509 may be used to store software programs or instructions as well as various data. The memory 509 may mainly include a first storage area storing programs or instructions and a second storage area storing data, wherein the first storage area may store an operating system, application programs or instructions (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like. Further, the memory 509 may include volatile memory or nonvolatile memory, or the memory 509 may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM), static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (ddr SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), and Direct RAM (DRRAM). Memory 509 in embodiments of the present application includes, but is not limited to, these and any other suitable types of memory.
The processor 510 is configured to determine a first power control parameter according to target information related to Multi-PDSCH scheduling when the serving cell of the terminal 500 is configured with Multi-physical downlink shared channel PDSCH scheduling, where the first power control parameter includes a valid bit number of hybrid automatic repeat request acknowledgement HARQ-ACK;
the processor 510 is further configured to determine, according to the first power control parameter, a transmission power of a physical uplink control channel PUCCH carrying the HARQ-ACK;
and the radio frequency unit 501 is configured to send the PUCCH to a network side device according to the sending power.
Optionally, the target information includes at least one of: the method comprises the steps of carrying out first configuration information of time domain binding transmission, carrying out second configuration information of space domain binding transmission, adopting a codebook for HARQ-ACK and adopting a sub-codebook for HARQ-ACK.
Optionally, in a case that the codebook adopted by the HARQ-ACK is a first type codebook, the determining, by the processor 510, a first power control parameter according to target information related to the Multi-PDSCH scheduling includes:
Optionally, in a case where the HARQ-ACK is configured to transmit with time domain bundling and without space domain bundling, if the terminal receives the PDSCH at the first time, the determining, by the processor 510, the first variable according to the target information includes:
wherein the target scheduling row includes a scheduling row mapped to the first occasion, or the target scheduling row includes a scheduling row determined according to a first PDSCH mapped to the first occasion and based on a last time domain resource allocation record association relationship, the scheduling row including: the terminal is actually scheduled or configured to allocate rows of a TDRA table.
Optionally, the number of the target scheduling lines is M, and in the case of m=0, the number of TBs corresponding to the target scheduling lines is 0; or alternatively, the process may be performed,
in the case where M > 0, the TB number corresponding to the target scheduling line is any one of the following:
the sum of the number of TB opened by each target scheduling line in the M target scheduling lines;
the TB number of the M target scheduling lines;
the sum of TB numbers configured by each target scheduling row in the M target scheduling rows;
and the TB numbers configured by the M target scheduling lines.
Optionally, in a case that the serving cell is not configured to allow dual codeword transmission, the number of TBs that the target scheduling row opens is equal to 1; or alternatively, the process may be performed,
in the case that the serving cell configuration allows dual codeword transmission, the number of TBs that the target scheduling row opens equals any one of:
under the condition of adopting a first TB disabling mode, the downlink control information DCI corresponding to the target scheduling row is the unified starting TB number;
and under the condition of adopting a second TB disabling mode, the DCI corresponding to the target scheduling line is actually started to obtain the TB number.
Optionally, the number of TBs opened by the M target scheduling rows includes:
maximum value of TB number of the M target scheduling lines respectively opened;
And determining the number of the turned-on TB according to the M target scheduling lines.
Optionally, in a case that the serving cell is not configured to allow dual codeword transmission, the TB number configured by the target scheduling row is equal to 1; or alternatively, the process may be performed,
in the case that the serving cell configuration allows dual codeword transmission, the TB number of the target scheduling row configuration is equal to 2.
Optionally, in the case that the PDSCH corresponding to the last time domain resource allocation record of any scheduling line is required to be a valid PDSCH, the determining that the first variable is equal to the TB number corresponding to the target scheduling line by the processor 510 includes:
if the first PDSCH exists and the first PDSCH is associated with or corresponds to the last time domain resource allocation record of the target scheduling row, the processor 510 determines that the target TB number is equal to the number of TBs turned on or configured by the first PDSCH;
if the first PDSCH is not present or is not associated with or corresponds to the last time domain resource allocation record of any scheduling row, the processor 510 determines that the first variable is equal to 0.
Optionally, in a case where the codebook adopted by the HARQ-ACK is a first type codebook, where the first type codebook is configured to transmit using time domain bundling and using space domain bundling, if the terminal receives the PDSCH in the first time, the determining, by the processor 510, the first variable according to the target information includes:
wherein the target scheduling row includes a scheduling row mapped to the first occasion, or the target scheduling row includes a scheduling row determined according to a first PDSCH mapped to the first occasion and based on a last time domain resource allocation record association relationship, the scheduling row including: the terminal is actually scheduled or configured with rows of the TDRA table.
Optionally, in a case where the PDSCH corresponding to the last time domain resource allocation record of any scheduling row is required to be a valid PDSCH, the determining performed by the processor 510 is performed by the number of target scheduling rows, including any one of the following:
if the first PDSCH exists and the first PDSCH is associated with or corresponds to the last time domain resource allocation record of the target scheduling row, then the processor 510 determines that the number of target scheduling rows is equal to 1;
if the first PDSCH is not present or is not associated with or corresponds to the last time domain resource allocation record of any scheduling row, the processor 510 determines that the number of target scheduling rows is equal to 0.
Optionally, in the case that the codebook adopted by the HARQ-ACK is a first type codebook, the determining, by the processor 510, a second variable according to the target information includes:
Optionally, in the case that the codebook adopted by the HARQ-ACK is the second type codebook, the determining, by the processor 510, the first power control parameter according to the target information related to the Multi-PDSCH scheduling includes:
in the case that each cell in the PUCCH cell group is not configured with time domain bundling, the processor 510 determines a first power control parameter according to a first sub-codebook and a second sub-codebook, where the PUCCH cell group includes a serving cell of the terminal, and the first sub-codebook corresponds to a single HARQ-ACK granularity, and the second sub-codebook corresponds to multiple HARQ-ACK granularities;
when all cells configured with Multi-PDSCH scheduling in the PUCCH cell group are configured with time domain bundling and the number of configured bundling groups is equal to 1, the processor 510 determines a first power control parameter according to the first sub-codebook;
in the case that at least one of the cells configured with Multi-PDSCH scheduling within the PUCCH cell group is configured with time domain bundling and the number of configured bundling groups is greater than 1, the processor 510 determines a first power control parameter according to the first sub-codebook and the second sub-codebook.
Optionally, the determining, by the processor 510, the first power control parameter according to the first sub-codebook and the second sub-codebook includes:
the processor 510 determines the first parameter according to a second calculation rule corresponding to the first sub-codebook, and determines the second parameter according to a third calculation rule corresponding to the second sub-codebook;
Optionally, the determining, by the processor 510, the first power control parameter according to the first sub-codebook includes:
Optionally, the determining, by the processor 510, the first parameter according to the second calculation rule corresponding to the first sub-codebook includes:
and/or the number of the groups of groups,
the determining, by the processor 510, the second parameter according to the third calculation rule corresponding to the second sub-codebook includes:
Optionally, when the terminal 500 detects DCI for scheduling PDSCH in the second occasion and the spatial bundling is not configured, the determining, by the processor 510, a third variable according to the target information includes:
Optionally, in a case that the serving cell is not configured to allow dual codeword transmission, each PDSCH schedules the actual number of TBs turned on by DCI or the configured number of TBs to be equal to 1; or alternatively, the process may be performed,
in the case that the serving cell configuration allows dual codeword transmission, the TB number of each PDSCH scheduling DCI configuration is equal to 2, or the TB number actually turned on by each PDSCH scheduling DCI is any one of the following:
under the condition of adopting a first TB disabling mode, each PDSCH schedules the unified starting TB number of DCI;
and under the condition of adopting a second TB disabling mode, each PDSCH schedules the actual number of the turned-on TB of the DCI.
Optionally, the determining, by the processor 510, a third variable according to the target information includes:
in the case that the terminal only allows detection of a single PDSCH scheduling DCI for a single serving cell in the second occasion, the processor 510 determines that the third variable is equal to the number of TBs actually turned on or the number of TBs configured by the single PDSCH scheduling DCI detected by the terminal; or alternatively, the process may be performed,
in the case that the terminal allows detection of at least two PDSCH scheduling DCIs for a single serving cell in the second occasion, the processor 510 determines that the third variable is equal to the sum of the number of TBs actually turned on or the number of TBs configured for all PDSCH scheduling DCIs detected by the terminal.
Optionally, in a case that the terminal 500 detects DCI for scheduling PDSCH in the second occasion and configures application of spatial bundling, the determining, by the processor 510, a third variable according to the target information includes:
Optionally, the determining, by the processor 510, the second parameter according to the third calculation rule corresponding to the second sub-codebook includes:
in the case that the second sub-codebook does not include the target HARQ-ACK including the HARQ-ACK obtained by time-domain bundling the first HARQ-ACK, the processor 510 determines the second parameter according to the following formula:
Wherein the first HARQ-ACK is HARQ-ACK corresponding to DCI for scheduling at least two PDSCH, n HARQ-ACK,second Representing a second parameter determined according to a third calculation rule corresponding to the second sub-codebook;
at the position of
When (I)>
Representing the value of a count DAI carried by the last first DCI detected by the terminal in M PDCCH detection occasions for any service cell, wherein the first DCI comprises DCIs for scheduling more than one PDSCH;
at the position of
When (I)>
Representing the value of the total DAI carried by the last first DCI detected by the terminal in the M PDCCH detection occasions aiming at any service cell;
detecting at the terminal at M PDCCHsWhen no DCI of the first type is detected for any serving cell within an opportunity,
When the spatial bundling is not configured to be applied,
the maximum codeword number of DCI scheduling configured for serving cell c; when configuring application airspace binding, +.>
If airspace binding is not configured, then
The total number of actually scheduled transmission blocks of the first type DCI detected by the UE for the serving cell c in the PDCCH detection opportunity m; if airspace binding is configured, +.>
The total number of the effective PDSCH scheduled by the UE aiming at the first DCI detected by the serving cell c in the PDCCH detection time m;
and/or the number of the groups of groups,
in the case that the second sub-codebook includes the target HARQ-ACK, the processor 510 determines the second parameter according to the following formula:
wherein, the liquid crystal display device comprises a liquid crystal display device,
representing the number of Multi-feedback cells in the PUCCH cell group, wherein the Multi-feedback cells belong to a first type cell or a second type cell, the first type cell is a service cell configured with Multi-PDSCH scheduling and not configured with time domain bundling, and the second type cell is a service cell configured with Multi-PDSCH scheduling and configured with time domain bundling and with the number of configured bundling groups being more than 1;
For the first cell c, the corresponding first maximum value is based on
Calculation of->
A maximum number of PDSCH receptions schedulable for a single DCI of the first type corresponding to the first cell c; the first cell is 
Any one of the multiple feedback cells belongs to the multiple feedback cells of the first type of cells;
for the second cell c, the corresponding first maximum is based on
Calculation of->
The number of binding groups configured for the second cell c; the second cell is +>
Any one of the multiple feedback cells belongs to the multiple feedback cells of the second type of cells;
The terminal 500 provided in this embodiment of the present application can implement each process executed by the power control parameter determining device 300 shown in fig. 3, and can obtain the same beneficial effects, so that repetition is avoided, and detailed descriptions are omitted here.
The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored, and when the program or the instruction is executed by a processor, the processes of the embodiment of the method for determining a power control parameter are implemented, and the same technical effects can be achieved, so that repetition is avoided, and no redundant description is provided herein.
Wherein the processor is a processor in the terminal described in the above embodiment. The readable storage medium includes computer readable storage medium such as computer readable memory ROM, random access memory RAM, magnetic or optical disk, etc.
The embodiment of the application further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled with the processor, and the processor is configured to run a program or an instruction, implement each process of the above embodiment of the method for determining a power control parameter, and achieve the same technical effect, so that repetition is avoided, and no further description is provided herein.
It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.
The embodiments of the present application further provide a computer program/program product, where the computer program/program product is stored in a storage medium, and the computer program/program product is executed by at least one processor to implement each process of the above-mentioned embodiments of the method for determining a power control parameter, and the same technical effects can be achieved, so that repetition is avoided, and details are not repeated herein.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of the present application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in an opposite order depending on the functions involved, e.g., the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solutions of the present application may be embodied essentially or in part in the form of a computer software product stored on a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and including instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the methods described in the embodiments of the present application.
The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative, not restrictive, and many modifications may be made by one of ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which fall within the protection of the present application.
Claims (44)
1. A method for determining a power control parameter, comprising:
under the condition that a serving cell of a terminal is configured with Multi-Physical Downlink Shared Channel (PDSCH) scheduling, the terminal determines a first power control parameter according to target information related to the Multi-PDSCH scheduling, wherein the first power control parameter comprises the effective bit number of hybrid automatic repeat request response (HARQ-ACK);
the terminal determines the transmission power of a Physical Uplink Control Channel (PUCCH) carrying the HARQ-ACK according to the first power control parameter;
and the terminal sends the PUCCH to network side equipment according to the sending power.
2. The method of claim 1, wherein the target information comprises at least one of: the method comprises the steps of carrying out first configuration information of time domain binding transmission, carrying out second configuration information of space domain binding transmission, adopting a codebook for HARQ-ACK and adopting a sub-codebook for HARQ-ACK.
3. The method of claim 2, wherein the determining, by the terminal, a first power control parameter according to target information related to the Multi-PDSCH scheduling in the case where the codebook employed by the HARQ-ACK is a first type codebook comprises:
The terminal determines at least one of a first variable and a second variable according to the target information;
and the terminal determines the first power control parameter according to at least one of the first variable and the second variable and a first calculation rule corresponding to the first codebook.
4. The method of claim 3, wherein if the terminal receives the PDSCH at the first time, if the HARQ-ACK is configured to transmit with time domain bundling and without space domain bundling, the terminal determining the first variable according to the target information comprises:
the terminal determines that a first variable is equal to the TB number corresponding to the target scheduling line;
wherein the target scheduling line includes a scheduling line mapped to the first occasion, or the target scheduling line includes a scheduling line determined according to a first PDSCH mapped to the first occasion and based on a last time domain resource allocation record association relationship, the scheduling line including: the terminal is actually scheduled or configured to allocate rows of a TDRA table.
5. The method of claim 4, wherein the number of target scheduling lines is M, and the number of TBs corresponding to the target scheduling lines is 0 if m=0; or alternatively, the process may be performed,
In the case where M > 0, the TB number corresponding to the target scheduling line is any one of the following:
the sum of the number of TB opened by each target scheduling line in the M target scheduling lines;
the TB number of the M target scheduling lines;
the sum of TB numbers configured by each target scheduling row in the M target scheduling rows;
and the TB numbers configured by the M target scheduling lines.
6. The method of claim 5, wherein the step of determining the position of the probe is performed,
in the case that the serving cell is not configured to allow dual codeword transmission, the number of TBs opened by the target scheduling row is equal to 1; or alternatively, the process may be performed,
in the case that the serving cell configuration allows dual codeword transmission, the number of TBs that the target scheduling row opens equals any one of:
under the condition of adopting a first TB disabling mode, the downlink control information DCI corresponding to the target scheduling row is the unified starting TB number;
and under the condition of adopting a second TB disabling mode, the DCI corresponding to the target scheduling line is actually started to obtain the TB number.
7. The method of claim 5 wherein the number of TBs that the M target schedule lines open comprises:
maximum value of TB number of the M target scheduling lines respectively opened;
and determining the number of the turned-on TB according to the M target scheduling lines.
8. The method of claim 5, wherein the step of determining the position of the probe is performed,
in the case that the serving cell is not configured to allow dual codeword transmission, the TB number configured by the target scheduling row is equal to 1; or alternatively, the process may be performed,
in the case that the serving cell configuration allows dual codeword transmission, the TB number of the target scheduling row configuration is equal to 2.
9. The method according to any one of claims 4 to 8, wherein, in the case where the PDSCH corresponding to the last time domain resource allocation record of any scheduling row is required to be a valid PDSCH, the terminal determines that the first variable is equal to the TB number corresponding to the target scheduling row, including:
if the first PDSCH exists and the first PDSCH is associated with or corresponds to the last time domain resource allocation record of the target scheduling line, the terminal determines that the target TB number is equal to the number of TBs opened by the first PDSCH or the configured TB number;
if the first PDSCH does not exist or the first PDSCH is not associated with or corresponds to the last time domain resource allocation record of any scheduling row, the terminal determines that the first variable is equal to 0.
10. The method of claim 3, wherein if the terminal receives the PDSCH at the first time, the terminal determining the first variable according to the target information if the codebook used for the HARQ-ACK is a first type codebook, the first type codebook being configured to use time domain bundling and to use spatial domain bundling for transmission, comprising:
The terminal determines that a first variable is equal to the number of target scheduling lines;
wherein the target scheduling line includes a scheduling line mapped to the first occasion, or the target scheduling line includes a scheduling line determined according to a first PDSCH mapped to the first occasion and based on a last time domain resource allocation record association relationship, the scheduling line including: the terminal is actually scheduled or configured with rows of the TDRA table.
11. The method according to claim 10, wherein the terminal determines that the first variable is equal to the number of target scheduling rows in case the PDSCH corresponding to the last time domain resource allocation record of any scheduling row is a valid PDSCH, comprising any one of:
if the first PDSCH exists and is associated with or corresponds to the last time domain resource allocation record of the target scheduling line, the terminal determines that the number of the target scheduling lines is equal to 1;
if the first PDSCH does not exist or the first PDSCH is not associated with or corresponds to the last time domain resource allocation record of any scheduling row, the terminal determines that the number of target scheduling rows is equal to 0.
12. The method according to claim 3, wherein in the case that the codebook adopted by the HARQ-ACK is a first type codebook, the determining, by the terminal, a second variable according to the target information includes:
The terminal determines that the second variable is equal to 0.
13. The method according to claim 2, wherein in case the codebook employed by the HARQ-ACK is a second type codebook, the terminal determining a first power control parameter according to target information related to the Multi-PDSCH scheduling, comprising:
under the condition that each cell in a PUCCH cell group is not configured with time domain binding, the terminal determines a first power control parameter according to a first sub-codebook and a second sub-codebook, wherein the PUCCH cell group comprises a serving cell of the terminal, the first sub-codebook corresponds to a single HARQ-ACK granularity, and the second sub-codebook corresponds to a plurality of HARQ-ACK granularities;
the terminal determines a first power control parameter according to the first sub-codebook under the condition that all cells configured with Multi-PDSCH scheduling in the PUCCH cell group are configured with time domain binding and the number of the configured binding groups is equal to 1;
and under the condition that at least one of cells configured with Multi-PDSCH scheduling in the PUCCH cell group is configured with time domain binding and the number of the configured binding groups is greater than 1, the terminal determines a first power control parameter according to the first sub-codebook and the second sub-codebook.
14. The method of claim 13, wherein the terminal determining a first power control parameter from the first sub-codebook and the second sub-codebook comprises:
the terminal determines a first parameter according to a second calculation rule corresponding to the first sub-codebook, and determines a second parameter according to a third calculation rule corresponding to the second sub-codebook;
the terminal determines that the first power control parameter is equal to a sum of the first parameter and the second parameter.
15. The method of claim 13, wherein the terminal determining a first power control parameter from the first sub-codebook comprises:
the terminal determines a third variable according to the target information;
the terminal determines the first power control parameter based on a second calculation rule and the third variable.
16. The method of claim 14, wherein the step of providing the first information comprises,
the terminal determines a first parameter according to a second calculation rule corresponding to the first sub-codebook, including:
the terminal determines a third variable according to the target information;
the terminal determines a first parameter based on a second calculation rule and the third variable;
And/or the number of the groups of groups,
the terminal determines a second parameter according to a third calculation rule corresponding to the second sub-codebook, including:
the terminal determines a fourth variable according to the target information;
the terminal determines a second parameter based on a third calculation rule and the fourth variable.
17. The method according to claim 15 or 16, wherein the terminal detects DCI of the scheduled PDSCH in the second occasion, and in the case that no spatial bundling is configured to be applied, the terminal determines a third variable according to the target information, including:
and the terminal determines that the third variable is equal to the actual number of the opened TB or the configured number of the TB of the PDSCH scheduling DCI detected by the terminal in the second time.
18. The method of claim 17, wherein the step of determining the position of the probe is performed,
in the case that the serving cell is not configured to allow dual codeword transmission, each PDSCH schedules the actual number of TBs opened by DCI or the number of TBs configured to be equal to 1; or alternatively, the process may be performed,
in the case that the serving cell configuration allows dual codeword transmission, the TB number of each PDSCH scheduling DCI configuration is equal to 2, or the TB number actually turned on by each PDSCH scheduling DCI is any one of the following:
under the condition of adopting a first TB disabling mode, each PDSCH schedules the unified starting TB number of DCI;
And under the condition of adopting a second TB disabling mode, each PDSCH schedules the actual number of the turned-on TB of the DCI.
19. The method according to claim 15 or 16, wherein the terminal determining a third variable from the target information comprises:
in the second occasion, under the condition that the terminal only allows detection of single PDSCH scheduling DCI for a single serving cell, the terminal determines that the third variable is equal to the number of TBs actually opened or the number of TBs configured by the single PDSCH scheduling DCI detected by the terminal; or alternatively, the process may be performed,
in the case that the terminal allows detection of at least two PDSCH scheduling DCIs for a single serving cell in the second occasion, the terminal determines that the third variable is equal to the sum of the number of TBs actually turned on or the number of TBs configured by all PDSCH scheduling DCIs detected by the terminal.
20. The method according to claim 15 or 16, wherein in the case that the terminal detects DCI of the scheduled PDSCH in the second occasion and configures application of spatial bundling, the terminal determines a third variable according to the target information, including:
the terminal determines that the third variable is equal to the number of PDSCH scheduling DCIs detected by the terminal in the second occasion.
21. The method of claim 14, wherein the determining, by the terminal, the second parameter according to a third calculation rule corresponding to the second sub-codebook comprises:
in the case that the second sub-codebook does not include the target HARQ-ACK, where the target HARQ-ACK includes the HARQ-ACK obtained by time-domain bundling the first HARQ-ACK, the terminal determines the second parameter according to the following formula:
wherein the first HARQ-ACK is HARQ-ACK corresponding to DCI for scheduling at least two PDSCH, n HARQ-ACK,second Representing a second parameter determined according to a third calculation rule corresponding to the second sub-codebook;
at the position of
When (I)>
Indicating the value of a count DAI carried by the last first DCI detected by the terminal for any serving cell in M PDCCH detection occasions, wherein the first DCI is a data packet in a downlink control channel (DCI)One class of DCI includes DCI for scheduling more than one PDSCH;
at the position of
When (I)>
Representing the value of the total DAI carried by the last first DCI detected by the terminal in the M PDCCH detection occasions aiming at any service cell;
When the terminal does not detect any of the first type DCI for any serving cell within M PDCCH detection occasions,
when the spatial bundling is not configured to be applied,
the maximum codeword number of DCI scheduling configured for serving cell c; when configuring application airspace binding, +.>
If airspace binding is not configured, then
The total number of actually scheduled transmission blocks of the first type DCI detected by the UE for the serving cell c in the PDCCH detection opportunity m; if airspace binding is configured, +.>
The total number of the effective PDSCH scheduled by the UE for the first type DCI detected by the serving cell c in the PDCCH detection opportunity m;
and/or the number of the groups of groups,
in case the second sub-codebook comprises the target HARQ-ACK, the terminal determines the second parameter according to the following formula:
wherein, the liquid crystal display device comprises a liquid crystal display device,
representing the number of Multi-feedback cells in the PUCCH cell group, wherein the Multi-feedback cells belong to a first type cell or a second type cell, the first type cell is a service cell configured with Multi-PDSCH scheduling and not configured with time domain bundling, and the second type cell is a service cell configured with Multi-PDSCH scheduling and configured with time domain bundling and with the number of configured bundling groups being more than 1;
For the first cell c, the corresponding first maximum value is based on
Calculation of->
A maximum number of PDSCH receptions schedulable for a single DCI of the first type corresponding to the first cell c; the first cell is +.>
Any one of the multiple feedback cells belongs to the multiple feedback cells of the first type of cells;
for the second cell c, the corresponding first maximum is based on
Calculation of->
The number of binding groups configured for the second cell c; the second cell is +>
Any one of the multiple feedback cells belongs to the multiple feedback cells of the second type of cells;
22. A power control parameter determining apparatus, applied to a terminal, comprising:
a first determining module, configured to determine a first power control parameter according to target information related to Multi-physical downlink shared channel PDSCH scheduling when a serving cell of a terminal is configured with the Multi-PDSCH scheduling, where the first power control parameter includes a valid bit number of hybrid automatic repeat request acknowledgement HARQ-ACK;
a second determining module, configured to determine, according to the first power control parameter, a transmission power of a physical uplink control channel PUCCH carrying the HARQ-ACK;
And the sending module is used for sending the PUCCH to the network side equipment according to the sending power.
23. The apparatus of claim 22, wherein the target information comprises at least one of: the method comprises the steps of carrying out first configuration information of time domain binding transmission, carrying out second configuration information of space domain binding transmission, adopting a codebook for HARQ-ACK and adopting a sub-codebook for HARQ-ACK.
24. The apparatus of claim 23, wherein the first determining module, in the case where the codebook used by the HARQ-ACK is a first type codebook, comprises:
a first determining unit configured to determine at least one of a first variable and a second variable according to the target information;
and the second determining unit is used for determining the first power control parameter according to at least one of the first variable and the second variable and a first calculation rule corresponding to the first codebook.
25. The apparatus of claim 24, wherein, in the case where the HARQ-ACK is configured to transmit with time domain bundling and without spatial domain bundling, if the terminal receives the PDSCH on a first time instant, the first determining unit is specifically configured to:
Determining that a first variable is equal to the TB number corresponding to the target scheduling line;
wherein the target scheduling line includes a scheduling line mapped to the first occasion, or the target scheduling line includes a scheduling line determined according to a first PDSCH mapped to the first occasion and based on a last time domain resource allocation record association relationship, the scheduling line including: the terminal is actually scheduled or configured to allocate rows of a TDRA table.
26. The apparatus of claim 25, wherein the number of target scheduling lines is M, and wherein the number of TBs corresponding to the target scheduling lines is 0 if M = 0; or alternatively, the process may be performed,
in the case where M > 0, the TB number corresponding to the target scheduling line is any one of the following:
the sum of the number of TB opened by each target scheduling line in the M target scheduling lines;
the TB number of the M target scheduling lines;
the sum of TB numbers configured by each target scheduling row in the M target scheduling rows;
and the TB numbers configured by the M target scheduling lines.
27. The apparatus of claim 26, wherein the device comprises a plurality of sensors,
in the case that the serving cell is not configured to allow dual codeword transmission, the number of TBs opened by the target scheduling row is equal to 1; or alternatively, the process may be performed,
In the case that the serving cell configuration allows dual codeword transmission, the number of TBs that the target scheduling row opens equals any one of:
under the condition of adopting a first TB disabling mode, the downlink control information DCI corresponding to the target scheduling row is the unified starting TB number;
and under the condition of adopting a second TB disabling mode, the DCI corresponding to the target scheduling line is actually started to obtain the TB number.
28. The apparatus of claim 26, wherein the number of TBs for which the M target schedule lines are on comprises:
maximum value of TB number of the M target scheduling lines respectively opened;
and determining the number of the turned-on TB according to the M target scheduling lines.
29. The apparatus of claim 26, wherein the device comprises a plurality of sensors,
in the case that the serving cell is not configured to allow dual codeword transmission, the TB number configured by the target scheduling row is equal to 1; or alternatively, the process may be performed,
in the case that the serving cell configuration allows dual codeword transmission, the TB number of the target scheduling row configuration is equal to 2.
30. The apparatus according to any one of claims 25 to 29, wherein the first determining unit, in a case where a PDSCH corresponding to a last time domain resource allocation record requiring any one scheduling row is a valid PDSCH, includes:
A first determining subunit, configured to determine that, if the first PDSCH exists and the first PDSCH is associated with or corresponds to a last time domain resource allocation record of a target scheduling row, the target TB number is equal to an opened TB number or a configured TB number of the first PDSCH;
a second determining subunit, configured to determine that the first variable is equal to 0 if the first PDSCH does not exist or the first PDSCH is not associated with or corresponds to a last time domain resource allocation record of any scheduling row.
31. The apparatus of claim 24, wherein, in a case where the codebook used by the HARQ-ACK is a first type codebook, the first type codebook is configured to use time domain bundling and transmit using space domain bundling, if the terminal receives the PDSCH at a first time, the first determining unit is specifically configured to:
determining that the first variable is equal to the number of target scheduling rows;
wherein the target scheduling line includes a scheduling line mapped to the first occasion, or the target scheduling line includes a scheduling line determined according to a first PDSCH mapped to the first occasion and based on a last time domain resource allocation record association relationship, the scheduling line including: the terminal is actually scheduled or configured with rows of the TDRA table.
32. The apparatus of claim 31, wherein, in a case where a PDSCH corresponding to a last time domain resource allocation record of any scheduling row is required to be a valid PDSCH, the first determining unit is specifically configured to perform any one of the following:
if the first PDSCH exists and is associated with or corresponds to the last time domain resource allocation record of the target scheduling line, determining that the number of the target scheduling lines is equal to 1;
if the first PDSCH does not exist or the first PDSCH is not associated with or corresponds to the last time domain resource allocation record of any scheduling row, determining that the number of target scheduling rows is equal to 0.
33. The apparatus of claim 24, wherein the first determining unit is further configured to, in a case where the codebook employed by the HARQ-ACK is a first type codebook:
determining that the second variable is equal to 0.
34. The apparatus of claim 23, wherein the first determining module, in the case where the codebook used by the HARQ-ACK is a second type codebook, comprises:
a third determining unit, configured to determine, according to a first sub-codebook and a second sub-codebook, a first power control parameter when each cell in a PUCCH cell group is not configured with time domain bundling, where the PUCCH cell group includes a serving cell of the terminal, the first sub-codebook corresponds to a single HARQ-ACK granularity, and the second sub-codebook corresponds to multiple HARQ-ACK granularities;
A fourth determining unit, configured to determine a first power control parameter according to the first sub-codebook when all cells configured with Multi-PDSCH scheduling in the PUCCH cell group are configured with time domain bundling and the number of configured bundling groups is equal to 1;
a fifth determining unit, configured to determine a first power control parameter according to the first sub-codebook and the second sub-codebook when at least one of the cells configured with Multi-PDSCH scheduling in the PUCCH cell group is configured with time domain bundling and the number of configured bundling groups is greater than 1.
35. The apparatus according to claim 34, wherein the third determination unit and/or the fifth determination unit comprises:
a third determining subunit, configured to determine a first parameter according to a second calculation rule corresponding to the first sub-codebook, and determine a second parameter according to a third calculation rule corresponding to the second sub-codebook;
and a fourth determining subunit configured to determine that the first power control parameter is equal to a sum of the first parameter and the second parameter.
36. The apparatus of claim 34, wherein the fourth determination unit comprises:
a fifth determining subunit, configured to determine a third variable according to the target information;
A sixth determining subunit, configured to determine the first power control parameter based on a second calculation rule and the third variable.
37. The apparatus of claim 35, wherein the device comprises a plurality of sensors,
the third determination subunit includes:
a first determining subunit, configured to determine a third variable according to the target information;
a second determining subunit configured to determine a first parameter based on a second calculation rule and the third variable;
and/or the number of the groups of groups,
the third determining subunit further includes:
a third determination subunit, configured to determine a fourth variable according to the target information;
and a fourth determining subunit configured to determine the second parameter based on the third calculation rule and the fourth variable.
38. The apparatus of claim 36 or 37, wherein the terminal detects DCI for scheduling PDSCH in the second occasion, and the fifth determining subunit and/or the first determining subunit is configured to:
and determining that the third variable is equal to the actual number of the opened TB or the configured number of the TB of the PDSCH scheduling DCI detected by the terminal in the second time.
39. The apparatus of claim 38, wherein the device comprises a plurality of sensors,
In the case that the serving cell is not configured to allow dual codeword transmission, each PDSCH schedules the actual number of TBs opened by DCI or the number of TBs configured to be equal to 1; or alternatively, the process may be performed,
in the case that the serving cell configuration allows dual codeword transmission, the TB number of each PDSCH scheduling DCI configuration is equal to 2, or the TB number actually turned on by each PDSCH scheduling DCI is any one of the following:
under the condition of adopting a first TB disabling mode, each PDSCH schedules the unified starting TB number of DCI;
and under the condition of adopting a second TB disabling mode, each PDSCH schedules the actual number of the turned-on TB of the DCI.
40. The apparatus according to claim 36 or 37, wherein the fifth determination subunit and/or the first determination subunit is specifically configured to:
in the second occasion, under the condition that the terminal only allows detecting single PDSCH scheduling DCI for a single serving cell, determining that the third variable is equal to the number of TBs actually opened or the number of TBs configured by the single PDSCH scheduling DCI detected by the terminal; or alternatively, the process may be performed,
and in the second occasion, under the condition that the terminal allows detection of at least two PDSCH scheduling DCIs for a single serving cell, determining that the third variable is equal to the sum of the actually opened TB numbers or the configured TB numbers of all PDSCH scheduling DCIs detected by the terminal.
41. The apparatus of claim 36 or 37, wherein the fifth determining subunit and/or the first determining subunit is configured, in the case that the terminal detects DCI for scheduling PDSCH in the second occasion and configures application of spatial bundling, to specifically:
and determining that the third variable is equal to the number of PDSCH scheduling DCIs detected by the terminal in the second occasion.
42. The apparatus of claim 35, wherein the third determining subunit is specifically configured to:
in the case that the second sub-codebook does not include the target HARQ-ACK, where the target HARQ-ACK includes the HARQ-ACK obtained by time-domain bundling the first HARQ-ACK, the terminal determines the second parameter according to the following formula:
wherein the first HARQ-ACK is HARQ-ACK corresponding to DCI for scheduling at least two PDSCH, n HARQ-ACK,second Representing a second parameter determined according to a third calculation rule corresponding to the second sub-codebook;
at the position of
When (I)>
Representing the value of a count DAI carried by the last first DCI detected by the terminal in M PDCCH detection occasions for any service cell, wherein the first DCI comprises DCIs for scheduling more than one PDSCH;
At the position of
When (I)>
Representing the value of the total DAI carried by the last first DCI detected by the terminal in the M PDCCH detection occasions aiming at any service cell;
when the terminal does not detect any of the first type DCI for any serving cell within M PDCCH detection occasions,
when the spatial bundling is not configured to be applied,
the maximum codeword number of DCI scheduling configured for serving cell c; when configuring application airspace binding, +.>
If airspace binding is not configured, then
The total number of actually scheduled transmission blocks of the first type DCI detected by the UE for the serving cell c in the PDCCH detection opportunity m; if airspace binding is configured, +.>
The total number of the effective PDSCH scheduled by the UE for the first type DCI detected by the serving cell c in the PDCCH detection opportunity m;
and/or the number of the groups of groups,
in case the second sub-codebook comprises the target HARQ-ACK, the terminal determines the second parameter according to the following formula:
Wherein, the liquid crystal display device comprises a liquid crystal display device,
representing the number of Multi-feedback cells in the PUCCH cell group, wherein the Multi-feedback cells belong to a first type cell or a second type cell, the first type cell is a service cell configured with Multi-PDSCH scheduling and not configured with time domain bundling, and the second type cell is a service cell configured with Multi-PDSCH scheduling and configured with time domain bundling and with the number of configured bundling groups being more than 1;
For the first cell c, the corresponding first maximum value is based on
Calculation of->
A maximum number of PDSCH receptions schedulable for a single DCI of the first type corresponding to the first cell c; the first cell is +.>
Any one of the multiple feedback cells belongs to the multiple feedback cells of the first type of cells;
for the second cell c, the corresponding first maximum is based on
Calculation of->
The number of binding groups configured for the second cell c; the second cell is +>
Any one of the multiple feedback cells belongs to the multiple feedback cells of the second type of cells;
43. A terminal comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implement the steps of the power control parameter determination method of any one of claims 1 to 21.
44. A readable storage medium, characterized in that the readable storage medium has stored thereon a program or instructions which, when executed by a processor, implement the steps of the power control parameter determination method according to any one of claims 1 to 21.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111673190.XA CN116437449A (en) | 2021-12-31 | 2021-12-31 | Power control parameter determining method, device and terminal |
| PCT/CN2022/144041 WO2023125959A1 (en) | 2021-12-31 | 2022-12-30 | Power control parameter determination method and apparatus, and terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111673190.XA CN116437449A (en) | 2021-12-31 | 2021-12-31 | Power control parameter determining method, device and terminal |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116437449A true CN116437449A (en) | 2023-07-14 |
Family
ID=86998201
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111673190.XA Pending CN116437449A (en) | 2021-12-31 | 2021-12-31 | Power control parameter determining method, device and terminal |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN116437449A (en) |
| WO (1) | WO2023125959A1 (en) |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102480775B (en) * | 2010-11-22 | 2014-01-08 | 大唐移动通信设备有限公司 | Power control method and equipment of physical uplink control channel |
| CN102740433B (en) * | 2011-04-02 | 2017-06-13 | 中兴通讯股份有限公司 | The Poewr control method and device of a kind of Physical Uplink Control Channel |
| CN103580823B (en) * | 2012-08-02 | 2017-05-03 | 上海贝尔股份有限公司 | Method for processing uplink HARQ feedback |
| CN116405165A (en) * | 2017-01-09 | 2023-07-07 | 北京三星通信技术研究有限公司 | Method and equipment for transmitting HARQ-ACK/NACK and downlink transmission method and equipment |
| CN108289015B (en) * | 2017-01-09 | 2023-04-07 | 北京三星通信技术研究有限公司 | Method and equipment for sending HARQ-ACK/NACK (hybrid automatic repeat request/acknowledgement) and downlink transmission method and equipment |
-
2021
- 2021-12-31 CN CN202111673190.XA patent/CN116437449A/en active Pending
-
2022
- 2022-12-30 WO PCT/CN2022/144041 patent/WO2023125959A1/en unknown
Also Published As
| Publication number | Publication date |
|---|---|
| WO2023125959A1 (en) | 2023-07-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20200044791A1 (en) | Group-based hybrid automatic repeat request (harq) acknowledgement feedback | |
| CN110168987A (en) | Expansible feedback report | |
| US20230362912A1 (en) | Channel information sending method, channel information receiving method, and related device | |
| CN110447271A (en) | Method and apparatus for up-link power control in radio honeycomb communication system | |
| CN116437449A (en) | Power control parameter determining method, device and terminal | |
| CN116419409A (en) | Method, device and terminal for determining resource transmission direction | |
| CN109150457A (en) | Control the transmission method and terminal device of information | |
| WO2023198045A1 (en) | Harq ack feedback method and apparatus, terminal, and network side device | |
| CN115333670B (en) | Dynamic HARQ-ACK codebook processing method, device, equipment and readable storage medium | |
| WO2022028606A1 (en) | Information determination method, information indication method, terminal, and network-side device | |
| WO2023125912A1 (en) | Frequency hopping method and apparatus for uplink transmission, indication method and apparatus, and terminal and network side device | |
| WO2023125953A1 (en) | Time-domain binding processing method, terminal, and network side device | |
| US20240080847A1 (en) | Information transmission method and apparatus, terminal, and storage medium | |
| CN115150026B (en) | Information reporting method, device and terminal | |
| WO2023280043A1 (en) | Beam reporting method and terminal | |
| CN116981084A (en) | Parameter determination method, device, terminal and readable storage medium | |
| CN117479212A (en) | Cross link interference measurement and reporting method, device and readable storage medium | |
| CN116707726A (en) | Transmission method, terminal and network side equipment | |
| CN117177217A (en) | Beam information transmission method and related equipment | |
| CN118041497A (en) | Transmission method, user Equipment (UE) and readable storage medium | |
| CN117545091A (en) | Uplink transmission method, device, terminal and medium | |
| CN116781218A (en) | Method, device and terminal for simultaneously transmitting Physical Uplink Shared Channel (PUSCH) | |
| CN117528798A (en) | Information configuration method, device, terminal, network equipment and readable storage medium | |
| CN116633509A (en) | Uplink TCI state determining method, device, terminal and network equipment | |
| CN117294407A (en) | Information determination method, apparatus, communication device and readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |