Method, apparatus and terminal for determining power control parameters

Abstract

This application discloses a power control parameter determination method, apparatus, and terminal, belonging to the field of communication technology. The power control parameter determination method of this application includes: when the serving cell of the terminal is configured with Multi-Physical Downlink Shared Channel (PDSCH) scheduling, the terminal determines a first power control parameter based on target information related to the Multi-PDSCH scheduling, wherein the first power control parameter includes the effective number of bits of Hybrid Automatic Repeat Request / Acknowledge (HARQ-ACK); the terminal determines the transmission power of the Physical Uplink Control Channel (PUCCH) carrying the HARQ-ACK based on the first power control parameter; and the terminal transmits the PUCCH to the network-side equipment based on the transmission power.

Description

Technical Field

[0001] This application belongs to the field of communication technology, and specifically relates to a method, apparatus and terminal for determining power control parameters. Background Technology

[0002] In some communication systems, Multi-PDSCH (Multi-Physical Downlink Shared Channel) scheduling transmission has been introduced. Multi-PDSCH scheduling refers to the ability of a single downlink control information (DCI) to schedule the transmission of multiple physical downlink shared channels (PDSCH) on the same carrier at one time.

[0003] In related technologies, for the first type of codebook (Type-1 codebook) corresponding to n HARQ-ACK The calculation does not consider the handling of multi-PDSCH scheduling and application time domain bundling. For n corresponding to the Type-2 codebook... HARQ-ACK The calculation did not consider the impact of the Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) corresponding to Multi-PDSCH scheduling. This resulted in an inconsistency in the calculated n. HARQ-ACK The value of n does not match the number of valid HARQ-ACK bits contained in the HARQ-ACK codebook, thus making it impossible to determine the value of n based on the number of valid HARQ-ACK bits contained in the codebook. HARQ-ACK If the transmission power of the Physical Uplink Control Channel (PUCCH) carrying HARQ-ACK is mismatched with the actual transmission power required by the terminal, the transmission performance of the PUCCH carrying HARQ-ACK will be reduced. Summary of the Invention

[0004] This application provides a method, apparatus, and terminal for determining power control parameters, which can solve the problem in related technologies where the transmission power of the PUCCH does not match the actual demand, resulting in reduced transmission performance of the PUCCH carrying HARQ-ACK.

[0005] Firstly, a method for determining power control parameters is provided, the method comprising:

[0006] When the serving cell of the terminal is configured with Multi-Physical Downlink Shared Channel (PDSCH) scheduling, the terminal determines a first power control parameter based on target information related to the Multi-PDSCH scheduling. The first power control parameter includes the number of effective bits of Hybrid Automatic Repeat Request Response (HARQ-ACK).

[0007] The terminal determines the transmission power of the physical uplink control channel PUCCH carrying the HARQ-ACK based on the first power control parameter.

[0008] The terminal sends the PUCCH to the network-side device according to the transmission power.

[0009] Secondly, a power control parameter determination device is provided for use in a terminal, the device comprising:

[0010] The first determining module is used to determine a first power control parameter based on target information related to the Multi-PDSCH scheduling when the serving cell of the terminal is configured with Multi-Physical Downlink Shared Channel (PDSCH) scheduling. The first power control parameter includes the number of effective bits of Hybrid Automatic Repeat Request Response (HARQ-ACK).

[0011] The second determining module is used to determine the transmission power of the physical uplink control channel PUCCH carrying the HARQ-ACK based on the first power control parameters.

[0012] The transmitting module is used to transmit the PUCCH to the network-side device according to the transmitting power.

[0013] Thirdly, a terminal is provided, comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method described in the first aspect.

[0014] Fourthly, a terminal is provided, including a processor and a communication interface, wherein the processor is configured to determine a first power control parameter based on target information related to the Multi-PDSCH scheduling when the serving cell of the terminal is configured with Multi-Physical Downlink Shared Channel (PDSCH) scheduling, wherein the first power control parameter includes the effective number of bits of Hybrid Automatic Repeat Request Response (HARQ-ACK) and a transmission power for determining the Physical Uplink Control Channel (PUCCH) carrying the HARQ-ACK based on the first power control parameter, and the communication interface is configured to transmit the PUCCH to a network-side device based on the transmission power.

[0015] Fifthly, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect.

[0016] In a sixth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being used to run programs or instructions to implement the method as described in the first aspect.

[0017] In a seventh aspect, a computer program / program product is provided, the computer program / program product being stored in a storage medium, the computer program / program product being executed by at least one processor to implement the steps of the power control parameter determination method as described in the first aspect.

[0018] In this embodiment, when the serving cell of the terminal is configured with Multi-Physical Downlink Shared Channel (PDSCH) scheduling, the terminal determines a first power control parameter based on target information related to the Multi-PDSCH scheduling. The first power control parameter includes the effective number of Hybrid Automatic Repeat Request (HARQ-ACK) bits. The terminal determines the transmission power of the Physical Uplink Control Channel (PUCCH) carrying the HARQ-ACK based on the first power control parameter. The terminal then transmits the PUCCH to the network-side equipment based on the transmission power. Thus, when the serving cell of the terminal is configured with Multi-PDSCH scheduling, the first power control parameter can be determined based on the target information related to the Multi-PDSCH scheduling, ensuring that the first power control parameter matches the effective number of HARQ-ACK bits contained in the HARQ-ACK codebook. This ensures that the transmission power of the PUCCH carrying the HARQ-ACK, determined according to the first power control parameter, matches the actual transmission power required by the terminal, thereby guaranteeing the transmission performance of the PUCCH carrying the HARQ-ACK. Attached Figure Description

[0019] Figure 1 This is a block diagram of a wireless communication system that can be applied to the embodiments of this application;

[0020] Figure 2 This is a flowchart of a power control parameter determination method provided in an embodiment of this application;

[0021] Figure 3 This is a schematic diagram of a power control parameter determination device provided in an embodiment of this application;

[0022] Figure 4 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0023] Figure 5 This is a schematic diagram of the structure of a terminal provided in an embodiment of this application. Detailed Implementation

[0024] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0025] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0026] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and NR terminology is used in most of the following description; however, these technologies can also be applied to applications other than NR systems, such as 6th generation (6G) radio systems. thGeneration 6G communication system.

[0027] Figure 1This diagram illustrates a block diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can be a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, vehicle-mounted device (VUE), pedestrian terminal (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. It should be noted that the specific type of terminal 11 is not limited in this embodiment. Network-side equipment 12 may include access network equipment or core network equipment. Access network equipment 12 may also be referred to as radio access network equipment, radio access network (RAN), radio access network function, or radio access network unit. Access network equipment 12 may include base stations, WLAN access points, or WiFi nodes, etc. Base stations may be referred to as Node B, evolved Node B (eNB), access point, base transceiver station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), home B node, home evolved B node, Transmitting Receiving Point (TRP), or any other suitable term in the field, as long as the same technical effect is achieved. The base station is not limited to specific technical terms. It should be noted that this application embodiment only uses a base station in an NR system as an example for description and does not limit the specific type of base station.

[0028] In related technologies, when a UE initiates a PUCCH transmission on the active uplink bandwidth part (BWP) b of carrier f in the primary cell c, the UE determines the transmission power P of this PUCCH transmission based on the following formula (1). PUCCH,b,f,c (i,q u ,q d ,l):

[0029]

[0030] Where i represents: PUCCH transmission opportunity index;

[0031] q u Indicates: UE-level P O Index, used to determine P O_UE_PUCCH (q u );

[0032] q d Indicates: The index of the reference signal used as a reference for path loss, used to determine PL b,f,c (q d );

[0033] l indicates: PUCCH closed-loop power control status index;

[0034] μ represents the subcarrier interval index corresponding to the PUCCH transmission;

[0035] P O_PUCCH,b,f,c (q u ) indicates: by P O_NOMINAL_PUCCH and P O_UE_PUCCH (q u The total P obtained by adding them together O Value, where P O_NOMINAL_PUCCH For public P O P O_UE_PUCCH (q u ) is for UE level P O ;

[0036] Indicates the number of resource blocks occupied by PUCCH transmission.

[0037] PL b,f,c (q d () indicates the estimated downlink path loss, in dB.

[0038] Δ F_PUCCH (F) indicates: power adjustment based on PUCCH format.

[0039] Δ TF,b,f,c (i) indicates the power adjustment amount based on the PUCCH transmission attributes.

[0040] g b,f,c (i,l) represents the PUCCH closed-loop power control adjustment amount.

[0041] For Δ TF,b,f,c (i) The calculation differs depending on the PUCCH format and the number of uplink control information (UCI) bits carried. For PUCCH transmissions based on PUCCH format 2 / 3 / 4, when the number of UCI bits carried does not exceed 11, Δ is calculated using the following formula (2). TF,b,f,c (i):

[0042] Δ TF,b,f,c (i) = 10 log 10 (K1·(n HARQ-ACK (i)+O SR (i)+O CSI (i))N RE (i))

[0043] Where K1 = 6;

[0044] n HARQ-ACK (i) represents the number of valid bits of HARQ-ACK information determined by the UE. The calculation process for different HARQ-ACK codebook types is described later. When no HARQ-ACK codebook type is configured for the UE, if the PUCCH transmission carries 1 bit of HARQ-ACK, then n HARQ-ACK (i) = 1, otherwise n HARQ-ACK (i) = 0;

[0045] O SR (i) is the number of SR information bits determined by the UE;

[0046] O CSI (i) is the number of CSI information bits determined by the UE;

[0047] N RE (i) represents the number of resource elements occupied by data information during PUCCH transmission. in, The number of subcarriers corresponding to each resource block, excluding subcarriers occupied by dedicated demodulation reference signals (DM-RS) transmission. This represents the number of symbols used for PUCCH transmissions, excluding symbols used for DM-RS transmissions.

[0048] It should be noted that when a User Equipment (UE) organization needs to report a HARQ-ACK bit sequence at a certain feedback time, based on predefined rules and the cases of PDSCH transmissions on one or more carriers that need to report HARQ-ACK at this feedback time and / or unscheduled PDSCH transmissions that need to report corresponding HARQ-ACK DCI indications, the correspondence between each PDSCH transmission and / or DCI indication and a certain bit in the organization's HARQ-ACK bit sequence is determined. This operation is called constructing the HARQ-ACK codebook or HARQ-ACK codebook scheme. NR Rel-15 uses two HARQ-ACK codebook schemes: semi-static codebook (Type-1 Codebook) and dynamic codebook (Type-2 Codebook).

[0049] The semi-static codebook is constructed from the perspective of possible PDSCH reception opportunities (Occasions). It is based on the feedback timing configuration table (i.e., the K1 Set configured by the higher layer, which contains one or at least two candidate K1s; K1 is used to indicate the time offset between PDSCH reception and its corresponding HARQ-ACK feedback, or the DCI indication of unscheduled PDSCH transmission but requiring feedback of the corresponding HARQ-ACK and its corresponding HARQ-ACK feedback, with a granularity of PUCCH slot) and the HARQ-ACK feedback time (i.e., the PUCCH slot where the semi-static codebook transmission is located). For each possible PDSCH reception opportunity (determined jointly by the Time Domain Resource Allocation (TDRA) table configured by the higher layer and the aforementioned K1 Set), corresponding HARQ-ACK bits are reserved (which can be understood as converting the set of Occasions composed of various possible Occasions into a sequence of HARQ-ACK bits). If, for a given PDSCH reception opportunity, the UE does not actually receive the corresponding PDSCH, or the UE does not actually detect the corresponding unscheduled PDSCH transmission but needs to feed back the corresponding HARQ-ACK DCI indication (e.g., SPS PDSCH release), then its corresponding HARQ-ACK bit is set to Negative Acknowledgement (NACK). Otherwise, when the UE receives the corresponding PDSCH, it sets the corresponding HARQ-ACK bit based on the decoding result of this PDSCH, and when the UE detects the corresponding DCI indication, it sets the corresponding HARQ-ACK bit to ACK.

[0050] And the above n HARQ-ACK The calculation of (i) differs depending on the type of HARQ-ACK codebook, which will be described below.

[0051] <For Type-1 codebook>

[0052] n can be calculated using the following formula (3). HARQ-ACK (i):

[0053]

[0054] Specifically, when PDSCH-CodeBlockGroupTransmission is configured (at this time, harq-ACK-SpatialBundlingPUCCH cannot be configured), This represents the number of CBGs received by the UE within PDSCH reception occasion m in serving cell c, and the PDSCH reception carrying these CBGs is scheduled by a DCI that supports CBG-based PDSCH reception (i.e., the corresponding non-fallback DCI); otherwise...

[0055] for The specific meaning and value of can be determined by distinguishing between the following cases (Case 1 and Case 2):

[0056] Case 1: When the UE receives the PDSCH within the PDSCH reception occasion m, it is further divided into Case 1-1 to Case 1-3. Here, the reception occasion can also be called the reception opportunity. For ease of explanation, it will be referred to as the reception occasion in the following embodiments.

[0057] Case 1-1: When neither harq-ACK-SpatialBundlingPUCCH nor PDSCH-CodeBlockGroupTransmission is configured, This represents the number of transport blocks received by the UE within the PDSCH receptionoccasion m of serving cell c.

[0058] Case 1-2: When PDSCH-CodeBlockGroupTransmission is configured (in this case, harq-ACK-SpatialBundlingPUCCH cannot be configured either), This represents the number of transport blocks received by the UE within the PDSCH reception occasion m of the serving cell c, and the PDSCH reception carrying these transport blocks is scheduled by a DCI that does not support CBG-based PDSCH reception (i.e., the corresponding fallback DCI).

[0059] Case 1-3: When harq-ACK-SpatialBundlingPUCCH is configured (at this time, PDSCH-CodeBlockGroupTransmission cannot be configured either), This represents the number of PDSCH receptions received by the UE within the PDSCH receptionoccasion m of serving cell c.

[0060] Case 2: When the UE receives an SPS PDSCH release for PDSCH reception occasion m of serving cell c, and sends back the corresponding HARQ-ACK in this Type-1 codebook for this SPS PDSCH release,

[0061] <For Type-2 codebook>

[0062] The Type-2 codebook involves three formulas (Formula (4), Formula (5), and Formula (6), with Formula (6) being the sum of Formula (4) and Formula (5). When the Type-2 codebook only involves HARQ-ACK based on transport block (TB-based) (each serving cell in the PUCCH cell group is not configured with code block group (CBG) transmission, i.e., none of them are configured with the higher-layer parameter PDSCH-ServingCellConfig->codeBlockGroupTransmission), only a single sub-codebook is involved, and n is calculated using Formula (4). HARQ-ACK When a Type-2 codebook involves both TB-based HARQ-ACK and CBG-based HARQ-ACK (i.e., at least one Serving cell in the PUCCH cell group is configured with CBG transmission and the higher-level parameter PDSCH-ServingCellConfig->codeBlockGroupTransmission is configured), then two Sub-codebooks are involved, and n is calculated using formula (6). HARQ-ACK .

[0063] Among them, n is calculated for TB-based HARQ-ACK. HARQ-ACK Formula (4) is:

[0064]

[0065] in, Indicates: the number of bits occupied by the downlink assignment index (DAI);

[0066] This indicates the number of serving cells configured with PDSCH transmission within the PUCCH cell group;

[0067] for Its meaning and values ​​can be distinguished in the following ways:

[0068] 1) When the UE does not detect any DCI in M ​​PDCCH monitoring occasions (this DCI can either schedule PDSCH reception or not schedule PDSCH reception but requires feedback of corresponding HARQ-ACK information; it does not distinguish which serving cell it is targeting),

[0069] 2) When hour, The value of the counter DAI carried by the last DCI detected by the UE within M PDCCH monitoring occasions. This last DCI can either schedule PDSCH reception or not schedule PDSCH reception but needs to feed back the corresponding HARQ-ACK information.

[0070] 3) When In this case, the following situations can be distinguished to determine the appropriate method.

[0071] 3-1) In M PDCCH monitoring occasions, for the last PDCCH monitoring occasion in which the UE detects at least one DCI (this DCI can either schedule PDSCH reception or not schedule PDSCH reception but needs to feed back the corresponding HARQ-ACK information; regardless of which serving cell it is for), if the UE does not detect any DCI carrying total DAI within this PDCCH monitoring occasion, then The value of the counter DAI carried by the last DCI detected by the UE during this PDCCH monitoring occasion;

[0072] 3-2) In M PDCCH monitoring occasions, for the last PDCCH monitoring occasion in which the UE detects at least one DCI (this DCI can either schedule PDSCH reception or not schedule PDSCH reception but needs to feed back the corresponding HARQ-ACK information; regardless of which serving cell it is for), if the UE detects at least one DCI carrying total DAI within this PDCCH monitoring occasion, then The total DAI value is the value of at least one DCI carrying total DAI detected by the UE during this PDCCH monitoring occasion (when the UE detects multiple DCIs carrying total DAI during this PDCCH monitoring occasion, the total DAI values ​​carried by these DCIs must be equal).

[0073] For U DAI,c Its meaning and value can be determined by distinguishing the following cases:

[0074] 1)U DAI,c For the UE to serve cell c, the total number of DCIs detected in M ​​PDCCH monitoring occasions. These DCIs can be scheduled for PDSCH reception or not scheduled for PDSCH reception but need to feed back the corresponding HARQ-ACK information.

[0075] 2) If, for serving cell c, the UE does not detect any DCI (this DCI can either schedule PDSCH reception or not schedule PDSCH reception but requires corresponding HARQ-ACK information) in M ​​PDCCH monitoring occasions, the UE... DAI,c =0;

[0076] for Its meaning and value can be determined by distinguishing the following cases:

[0077] When maxNrofCodeWordsScheduledByDCI is configured as 2 for any serving cell, and harq-ACK-SpatialBundlingPUCCH is not configured, Otherwise,

[0078] for Its meaning and value can be determined by distinguishing between the following cases (Case 1 and Case 2):

[0079] Case 1: When the UE receives the DCI for scheduling the PDSCH, it is specifically divided into the following Cases 1-1 to 1-2:

[0080] Case 1-1: When harq-ACK-SpatialBundlingPUCCH is not configured, This represents the number of transport blocks of the PDSCH carried by the DCI scheduled by the UE for the serving cell c within the PDCCH monitoring occasion m.

[0081] Case 1-2: When harq-ACK-SpatialBundlingPUCCH is configured, This represents the number of DCI-scheduled PDSCHs detected by the UE for serving cell c within PDCCH monitoring occasion m.

[0082] Case 2: This refers to the number of DCIs that the UE detects in serving cell c during PDCCH monitoring occasion m that do not schedule PDSCH reception but require feedback of the corresponding HARQ-ACK.

[0083] N SPS,c The UE needs to report the number of SPS PDSCH receptions corresponding to HARQ-ACK information within a certain PUCCH for serving cell c, and the UE also needs to report the corresponding HARQ-ACK information for PDSCH receptions scheduled within M PDCCH monitoring occasions within this PUCCH.

[0084] Specifically, n is calculated for CBG-based HARQ-ACK. HARQ-ACK Formula (5) is:

[0085]

[0086] This indicates the number of serving cells configured with PDSCH scheduling within the PUCCH cell group;

[0087] for Its meaning and values ​​can be distinguished in the following ways:

[0088] 1) When hour, The value of counter DAI is the last scheduled PDSCH received by the UE for any serving cell within M PDCCH monitoring occasions and carried by the DCI based on CBG.

[0089] 2) When hour, The value of total DAI is the DCI carried by the last scheduling-based PDSCH received by the UE for any serving cell within M PDCCH monitoring occasions.

[0090] 3) When the UE does not detect any DCI for CBG-based PDSCH reception for any serving cell within M PDCCH monitoring occasions,

[0091] for Its meaning and value can be determined by distinguishing the following cases:

[0092] 1) For the UE, the total number of DCIs received by the PDSCH based on the scheduling CBG are detected in M ​​PDCCH monitoring occasions for the serving cell c;

[0093] 2) When the UE does not detect any DCI for scheduling CBG-based PDSCH reception in M ​​PDCCH monitoring occasions for serving cell c,

[0094] The number of CBGs that the UE detects for serving cell c within PDCCH monitoring occasion m, which support CBG-based PDSCH reception and DCI scheduling of PDSCH bearers.

[0095] Formula (6) will calculate n for TB-based HARQ-ACK. HARQ-ACK and n calculated for CBG-based HARQ-ACK HARQ-ACK Adding them together, formula (6) becomes:

[0096] n HARQ-ACK =n HARQ-ACK,TB +n HARQ-ACK,CBG

[0097] The related technologies also include enhanced Type-2 codebook and Type-3 codebook.

[0098] <For enhancing the Type-2 codebook>

[0099] The UE determines the number of valid HARQ-ACK bits n for the corresponding PDSCH group g. HARQ-ACK,g And determine the number of valid bits n of HARQ-ACK information corresponding to PDSCH group (g+1) mod 2. HARQ-ACK,(g+1)mod2 It is important to note that N SPS,c Only included in n HARQ-ACK,g middle.

[0100] When q = 1 and At that time, UE settings According to this Determine n HARQ-ACK,(g+1)mod2 .

[0101] Specifically, n HARQ-ACK Determined based on the following process:

[0102] When q = 0, n HARQ-ACK =n HARQ-ACK,g ;

[0103] Otherwise, n HARQ-ACK =n HARQ-ACK,g +n HARQ-ACK,(g+1)mod2 .

[0104] The relevant parameters are described as follows:

[0105] g is indicated in the last non-fallback DCI corresponding to the enhanced Type-2 codebook, specifically by the PDSCH group index indication field of that DCI.

[0106] The last non-fallback DCI in the Type-2 codebook indicates, specifically, the total DAI indicator field corresponding to PDSCH group (g+1) mod2 (when this indicator field is configured; when this indicator field is not configured). To instruct

[0107] <For Type-3 codebook>

[0108] n HARQ-ACK (i)=O ACK (i), where O ACK (i) is the number of valid HARQ-ACK bits contained in the Type-3 codebook.

[0109] Calculate n from the above Type-1 codebook, Type-2 codebook, enhanced Type-3 codebook, and Type-3 codebook. HARQ-ACK From the process and the definition of each parameter in the calculation process, it can be seen that in related technologies, the calculation of n... HARQ-ACK At that time, the case of Multi-PUSCH scheduling was not considered. This may result in an error when introducing Multi-PUSCH scheduling, where the calculated n based on the calculation rules in the Type-1 codebook, Type-2 codebook, enhanced Type-3 codebook, and Type-3 codebook is incorrect. HARQ-ACK The value of this parameter does not match the actual situation of Multi-PUSCH scheduling.

[0110] For example, during the Rel-17 52.6–71 GHz characteristic study, it was confirmed that new sub-carrier spacing (SCS) was needed for the new NR deployment frequency band, including 480 kHz and 960 kHz. For these newly introduced SCS, PDCCH monitoring needs corresponding adjustments or enhancements, such as avoiding the need for the UE to monitor the PDCCH in every slot (or for a very short duration), thereby reducing UE implementation complexity. Accordingly, to fully utilize carrier time-domain resources, it is necessary to study / introduce Multi-PDSCH scheduling and Multi-PUSCH scheduling.

[0111] Multi-PDSCH scheduling refers to a single DCI scheduling multiple PDSCH transmissions on the same carrier at once. According to the NR protocol, these PDSCHs do not overlap in the time domain.

[0112] When a Serving cell configured for a UE supports Multi-PDSCH scheduling, at least one row in the TDRA table configured for this Serving cell must be configured with more than one Start and Length Indicator Value (SLIV). The Downlink Scheduling Center (DCI) schedules the PDSCH corresponding to each Entry / SLIV in the TDRA table for the UE by indicating a row in this table. Each Entry / SLIV provides the time-domain resource allocation information for the corresponding PDSCH.

[0113] In the study of Rel-17 characteristics from 52.6 to 71 GHz, the construction of Type-1 codebook and Type-2 codebook was mainly discussed for HARQ-ACK feedback of Multi-PDSCH scheduling.

[0114] <For Type-1 codebook>

[0115] When no Time domain bundling is configured for a particular Serving cell, based on the rows in the TDRA table configured for that Serving cell and the configured K1 set, the set of DL slots that may occur during PDSCH scheduling for that Serving cell when feeding back the Type-1 codebook within the specified PUCCH slot, and the set of SLIVs corresponding to the PDSCH that may exist within each DL slot, are determined. Based on the above DL slot set and the SLIV set corresponding to each DL slot, the Occasion set corresponding to this Serving cell is obtained using the Rel-15 / 16 pseudocode process, and the Occasion set is converted into the HARQ-ACK bit sequence corresponding to this Serving cell in the Type-1 codebook.

[0116] When applying Time domain bundling to a specific Serving cell, based on the Last SLIV of each row in the TDRA table configured for this Serving cell and the configured K1 set, the Occasion set corresponding to this Serving cell is obtained using the Rel-15 / 16 pseudocode process, and the Occasion set is converted into the HARQ-ACK bit sequence corresponding to this Serving cell in the Type-1 codebook.

[0117] It should be noted that each Serving cell configured within a certain PUCCH cell group can be independently configured to apply time domain bundling, and the corresponding HARQ-ACK bit sequence for each Serving cell in the Type-1 codebook is determined independently, and then the first and last bits are concatenated across Serving cells.

[0118] <For Type-2 codebook>

[0119] DAI counting based on DCI.

[0120] When Time domain bundling is not configured for a certain Serving cell, for this Serving cell, only a single PDSCH DCI is scheduled, or only a single HARQ-ACK bit is generated and no PDSCH DCI is scheduled. The corresponding HARQ-ACK is placed in the first sub-codebook. The HARQ-ACK corresponding to DCIs scheduled for more than one PDSCH is placed in the second sub-codebook. The two sub-codebooks are used for DAI counting respectively.

[0121] When time domain bundling is configured for a specific Serving cell, if the number of configured bundling groups is 1, the HARQ-ACK corresponding to DCIs that schedule more than one PDSCH for this Serving cell will be placed in the first sub-codebook; otherwise, they will be placed in the second sub-codebook. Other operations are exactly the same as when time domain bundling is not configured.

[0122] It should be noted that each Serving cell configured within a PUCCH cell group can be independently configured to apply Time domain bundling; DAI performs unified counting across Serving cells within a PUCCH cell group.

[0123] From the above construction rules for Type-1 and Type-2 codebooks supporting HARQ-ACK feedback for Multi-PDSCH scheduling, it can be seen that in related technologies, for the first type of codebook (Type-1 codebook) corresponding to n... HARQ-ACK The calculation did not consider the handling of multi-PDSCH scheduling and application time domain bundling, resulting in an inefficient calculation of n under this configuration. HARQ-ACK Inaccurate (i.e., the calculated n) HARQ-ACK This is not necessarily the number of valid HARQ-ACK bits in the codebook, and may even exceed the number of bits in the HARQ-ACK codebook, thus affecting the proper setting of PUCCH transmission power. For the type-2 codebook, the corresponding n... HARQ-ACKThe calculation does not take into account the impact of the feedback from the Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) corresponding to Multi-PDSCH scheduling, and therefore does not support Multi-PDSCH scheduling.

[0124] It is worth noting that in n HARQ-ACK If the value of n does not match the actual situation of Multi-PUSCH scheduling, it may cause problems based on this n. HARQ-ACK The calculated transmit power of the PUCCH carrying HARQ-ACK (i.e., P in formula (1)) PUCCH,b,f,c (i,q u ,q d The transmission power required by the terminal is inconsistent with the actual transmission power needed by the terminal. Therefore, if P... PUCCH,b,f,c (i,q u ,q d If the transmission power is greater than the actual transmission power required by the terminal and PUCCH is transmitted based on that power, it will cause the terminal to consume excessive power; if P PUCCH,b,f,c (i,q u ,q d If the transmission power is less than the actual power required by the terminal, it will reduce the transmission reliability of the PUCCH carrying HARQ-ACK. For example, it will reduce the detection performance of the network-side equipment for PUCCH reception, including leading to a higher probability of PUCCH missed detection and false detection.

[0125] The embodiments of this application can be implemented in n HARQ-ACK In the calculation process, target information related to Multi-PDSCH scheduling is considered, so that n determined based on this target information... HARQ-ACK It can accurately reflect the number of valid HARQ-ACK bits contained in the HARQ-ACK codebook, thereby improving the accuracy of data processing based on this number. HARQ-ACK Calculated P PUCCH,b,f,c (i,q u ,q d The accuracy of the PUCCH transmission power requirement or the degree of matching between the PUCCH transmission power requirement and the PUCCH carrying HARQ-ACK can be improved to reduce the power consumption of the terminal while improving the transmission reliability of the PUCCH carrying HARQ-ACK.

[0126] The following description, in conjunction with the accompanying drawings, details the power control parameter determination method, power control parameter determination device, and terminal provided in this application through some embodiments and application scenarios.

[0127] Please see Figure 2The power control parameter determination method provided in this application embodiment can be executed by a terminal, which may include, for example, Figure 1 The various terminals 11 listed in the illustrated embodiments may also include other terminals not listed herein, which are not specifically limited here, such as... Figure 2 As shown, the method for determining power control parameters may include the following steps:

[0128] Step 201: When the serving cell of the terminal is configured with Multi-Physical Downlink Shared Channel (PDSCH) scheduling, the terminal determines a first power control parameter based on the target information related to the Multi-PDSCH scheduling, wherein the first power control parameter includes the effective number of bits of Hybrid Automatic Repeat Request Response (HARQ-ACK).

[0129] Wherein, the first power control parameter mentioned above can be n in the above formula (2). HARQ-ACK , that n HARQ-ACK n calculated in related technologies HARQ-ACK The differences include: in this embodiment, n is determined based on target information related to Multi-PDSCH scheduling. HARQ-ACK Thus, the n HARQ-ACK The values ​​and meanings of n are similar to those calculated in related technologies. HARQ-ACK They are not the same, and the n determined in the embodiments of this application is different. HARQ-ACK It can accurately reflect the number of effective bits of HARQ-ACK information under Multi-PDSCH scheduling.

[0130] The target information may include at least one of the following: first configuration information for time-domain bound transmission, second configuration information for spatial-domain bound transmission, the codebook used by HARQ-ACK, and the sub-codebook used by HARQ-ACK.

[0131] Option 1: Based on the first configuration information above, it can be determined whether the terminal is configured to use time domain bundling for the HARQ-ACK transmission.

[0132] Option 2: Based on the second configuration information above, it can be determined whether the terminal is configured to use spatial bundling for the HARQ-ACK transmission.

[0133] Option 3: Based on the codebook used by HARQ-ACK, the type of HARQ-ACK codebook can be determined, such as: Type-1 codebook, Type-2 codebook, enhanced Type-2 codebook, or Type-3 codebook. In implementation, based on the type of HARQ-ACK codebook used, the calculation rules corresponding to that codebook type can be used to determine the aforementioned n. HARQ-ACK .

[0134] Option 4: For the Type-2 codebook, it can include two sub-codebooks. Based on the sub-codebook used in HARQ-ACK, the calculation rules corresponding to that sub-codebook can be used to determine the aforementioned n. HARQ-ACK In implementation, the sub-codebook used by HARQ-ACK can be determined based on the first configuration and / or the second configuration. For example, if no Serving cell in the PUCCH cell group corresponding to the serving cell is configured with Time domain bundling, the Type-2 codebook involves two sub-codebooks; if all Serving cells in this PUCCH cell group that are configured with Multi-PDSCH scheduling are configured with Time domain bundling and the number of configured Bundling groups is 1, then the Type-2 codebook involves only a single sub-codebook; if at least one Serving cell in this PUCCH cell group that is configured with Multi-PDSCH scheduling is configured with Time domain bundling and the number of configured Bundling groups is greater than 1, then the Type-2 codebook involves two sub-codebooks.

[0135] Step 202: The terminal determines the transmission power of the physical uplink control channel (PUCCH) carrying the HARQ-ACK based on the first power control parameter.

[0136] In this step, given the n determined in step 201 HARQ-ACK It can accurately reflect the number of effective bits of HARQ-ACK information under Multi-PDSCH scheduling, thereby enabling the calculation based on n HARQ-ACKThe transmission power of the PUCCH carrying the HARQ-ACK is determined to match the number of effective bits corresponding to the HARQ-ACK that the terminal needs to transmit.

[0137] The transmission power of the PUCCH mentioned above can be calculated according to formula (1). PUCCH,b,f,c (i,q u ,q d ,l), which will not be elaborated here.

[0138] Step 203: The terminal sends the PUCCH to the network-side device according to the transmission power.

[0139] In this step, the terminal sends the PUCCH with a transmission power that matches the number of effective bits of the HARQ-ACK that the terminal needs to send. This can ensure the reliability of PUCCH transmission while minimizing the power consumption caused by the terminal sending the PUCCH.

[0140] Corresponding to step 203, the network-side device corresponding to the serving cell of the terminal can determine the aforementioned n based on the PDSCH reception and / or DCI indication transmission status corresponding to the HARQ-ACK codebook, according to the same calculation rules. HARQ-ACK Then, according to formula (1), the PUCCH transmission power used by the terminal when sending the PUCCH carrying HARQ-ACK is estimated, thereby predicting the PUCCH reception performance and adjusting the corresponding closed-loop power control adjustment amount as needed. However, in actual network environments, there may be problems such as DCI missed detection and downlink path loss estimation errors, which will lead to the network-side equipment calculating n HARQ-ACK n calculated by the terminal HARQ-ACK There may be some error, and there may be some discrepancy between the PUCCH transmission power used by the terminal and the PUCCH transmission power expected by the network-side equipment. However, the above errors will only affect the PUCCH detection performance of the network-side equipment and the network-side equipment's control over PUCCH transmission performance to a certain extent, and will not cause the two sides to be unable to interact normally.

[0141] Given that different HARQ-ACK codebook types are used, the above n can be determined using the calculation rules corresponding to that codebook type. HARQ-ACK For ease of explanation, the following four embodiments are used in this application to distinguish the calculation rules corresponding to Type-1 codebook, Type-2 codebook, enhanced Type-2 codebook, or Type-3 codebook.

[0142] Example 1: n of the Type-1 codebook HARQ-ACK calculate

[0143] As an optional implementation, when the codebook used in the HARQ-ACK is a first type of codebook, the terminal determines the first power control parameter based on target information related to the Multi-PDSCH scheduling, including:

[0144] The terminal determines at least one of the first variable and the second variable based on the target information;

[0145] The terminal determines the first power control parameter according to at least one of the first variable and the second variable, and in accordance with the first calculation rule corresponding to the first type of codebook.

[0146] In practice, the first variable mentioned above can be regarded as The second variable mentioned above can be regarded as The determination of the first power control parameter based on at least one of the first and second variables, according to the first calculation rule corresponding to the first type of codebook, can be achieved by calculating n using the following formula. HARQ-ACK :

[0147]

[0148] It is worth noting that for n in the Type-1 codebook HARQ-ACK Calculations show that when the Type-1 codebook supports Multi-PDSCH scheduling, it can be assumed that one or at least two Serving cells in the configured Serving cell set corresponding to the PUCCH cell group are configured with Multi-PDSCH scheduling. At this time, there may still be Serving cells in the Serving cell set that are not configured with Multi-PDSCH scheduling, and CBG transmission may still be configured for these Serving cells. Considering that Multi-PDSCH scheduling and CBG transmission may coexist within the corresponding PUCCH cell group (but based on the current discussion, they cannot coexist within the same Serving cell), the first variable in the above formula... Second variable The meaning and value of can be determined based on the actual situation of Multi-PDSCH scheduling. A Serving cell configured with Multi-PDSCH scheduling can be understood as a Serving cell with at least one row in the TDRA table of at least one DL BWP configuration that is configured with more than one time-domain resource allocation record. The time-domain resource allocation record can be an Entry or an SLIV, or a single time-domain resource allocation record can correspond to or contain a single SLIV. For ease of explanation, the following examples use an SLIV as an example.

[0149] Optionally, if the codebook used in the HARQ-ACK is a first type of codebook, the terminal determines the second variable based on the target information, including:

[0150] The terminal determines that the second variable is equal to 0.

[0151] In implementation, for Serving cells configured with Multi-PDSCH scheduling (CBG transmission cannot be configured simultaneously), the UE can directly assume...

[0152] It should be noted that for a Serving cell without Multi-PDSCH scheduling configured, when PDSCH-CodeBlockGroupTransmission is configured (in which case harq-ACK-SpatialBundlingPUCCH cannot be configured), The number of CBGs received by the terminal within PDSCH reception occasion m in serving cell c, and the PDSCH reception carrying these CBGs is scheduled by a DCI that supports CBG-based PDSCH reception (i.e., the corresponding non-fallback DCI); otherwise

[0153] In implementation, for The value and meaning of can be determined by distinguishing the following cases:

[0154] Scenario 1

[0155] For a Serving cell configured with Multi-PDSCH scheduling (CBG transport cannot be configured simultaneously), when application time domain bundling is not configured, The meaning and value of can be determined by distinguishing between the following cases (Case 1 and Case 2):

[0156] Case 1: When the UE receives the PDSCH within the PDSCH reception occasion m, it is further divided into the following Case 1-1 to Case 1-2.

[0157] Case 1-1: When harq-ACK-SpatialBundlingPUCCH is not configured, This represents the number of TBs received by the UE within PDSCH reception occasion m in serving cell c.

[0158] Case 1-2: When harq-ACK-SpatialBundlingPUCCH is configured, This represents the number of PDSCH receptions received by the UE within PDSCH reception occasion m in serving cell c.

[0159] Case 2: When the UE receives an SPS PDSCH release for PDSCH reception occasion m of serving cell c, and sends back the corresponding HARQ-ACK in this Type-1 codebook for this SPS PDSCH release,

[0160] Scenario 2

[0161] For a Serving cell configured with Multi-PDSCH scheduling (CBG transmission cannot be configured simultaneously), when configuring application time domain bundling, it can be divided into the following two sub-cases (sub-case 1 and sub-case 2) for determination. The meaning and values ​​of .

[0162] In this case, sub-case 1 indicates that the terminal receives PDSCH within PDSCH reception occasion m (first opportunity); sub-case 2 indicates that the terminal needs to provide a corresponding HARQ-ACK for SPS PDSCH release within PDSCH reception occasion m.

[0163] For sub-case 2 above, when the UE receives an SPSPDSCH release for PDSCH reception occasion m of serving cell c, and sends back the corresponding HARQ-ACK in this Type-1 codebook for this SPSPDSCH release,

[0164] It should be noted that in practical applications, there may be application scenarios that do not satisfy either sub-case 1 or sub-case 2. For example, in the case where the UE neither receives the PDSCH within PDSCH reception occasion m, nor is there a need to provide a corresponding HARQ-ACK for the SPS PDSCH release. In this application embodiment, this situation can be covered by sub-case 1, or, if neither sub-case 1 nor sub-case 2 is satisfied, a separate determination can be made. The value of (i.e., determined) It does not affect Determining the final value.

[0165] The following is a detailed explanation of sub-case 1 based on the configuration of airspace binding:

[0166] When Spatial bundling is not configured to be applied>

[0167] As an optional implementation, when the HARQ-ACK is configured to use time-domain binding for transmission but not spatial-domain binding, if the terminal receives the PDSCH at the first opportune moment, the terminal determines the first variable based on the target information, including:

[0168] The terminal determines that the first variable is equal to the number of TBs corresponding to the target scheduling line;

[0169] The target scheduling line includes a scheduling line mapped to the first timing, or the target scheduling line includes a scheduling line determined based on the first PDSCH mapped to the first timing and the association relationship of the last time domain resource allocation record. The scheduling line includes: a row of the time domain resource allocation (TDRA) table in which the terminal is actually scheduled or configured.

[0170] The first timing mentioned above can be any PDSCH reception occasion m. The scheduling line in this embodiment can be understood as: a TDRA table line for which the current terminal is actually scheduled (i.e., the terminal receives a downlink scheduling DCI and indicates this TDRA table line) or configured (i.e., the configured and activated semi-persistent scheduling (SPS) configuration uses this TDRA table line), which has corresponding other 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 activated DCI).

[0171] Sub-case 1-1: The scheduling line mapped to the first timing mentioned above can be understood as: a scheduling line is mapped to PDSCH reception occasion m based on its Last SLIV, or in other words, the Last SLIV of a scheduling line is mapped to PDSCH reception occasion m. Typically, the number of scheduling lines mapped to PDSCH reception occasion m is 0 or 1; alternatively, the number of scheduling lines mapped to PDSCH reception occasion m can be greater than 1.

[0172] Here we assume that the number of scheduling lines mapped to PDSCH reception occasion m is M, where M can be an integer greater than or equal to 0.

[0173] Thus, when M=0, the number of TBs corresponding to the target scheduling line is 0;

[0174] When M>0, the number of TBs corresponding to the target scheduling line can be determined using any of the following methods:

[0175] The sum of the number of TBs opened in each of the M target scheduling lines;

[0176] The number of TBs opened for the M target scheduling lines;

[0177] The sum of the number of TBs configured for each of the M target scheduling lines;

[0178] The number of TBs configured for the M target scheduling lines.

[0179] Method 1

[0180] For M target scheduling lines, this is the sum of the number of TBs opened by each target scheduling line. The number of TBs opened by different target scheduling lines can be the same or different.

[0181] Optionally, if the serving cell is not configured to allow dual-codeword transmission, the number of TBs enabled by the target scheduling line is equal to 1; or,

[0182] When the serving cell is configured to allow dual-codeword transmission, the number of TBs enabled by the target scheduling line is equal to any of the following:

[0183] When the first TB is disabled, the number of TBs that are uniformly enabled in the downlink control information (DCI) corresponding to the target scheduling line;

[0184] When the second TB de-enable method is used, the number of TBs actually enabled in the DCI corresponding to the target scheduling line.

[0185] In implementation, TB disabling can be understood as follows: when the higher layer configuration allows dual codeword transmission (i.e., for a given Serving cell of the UE, the maximum number of codewords (maxNrofCodeWordsScheduledByDCI) for DCI scheduling is configured to be n2), it can be determined in some way whether a TB for one or at least two valid PDSCHs of a certain DCI scheduling is enabled (i.e. actually scheduled) or disabled (i.e. not actually scheduled).

[0186] In this context, a Valid PDSCH refers to a PDSCH among one or more PDSCHs scheduled by a single DCI that does not conflict with a semi-static UL symbol. It can also be understood as a scheduled PDSCH that can actually be transmitted. The opposite of a Valid PDSCH is an Invalid PDSCH, which refers to a PDSCH among one or more PDSCHs scheduled by a single DCI that conflicts with a semi-static UL symbol. It can also be understood as a scheduled PDSCH that cannot actually be transmitted. A Scheduled PDSCH can be understood as a PDSCH among one or more PDSCHs scheduled by a single DCI, corresponding to a specific Entry / SLIV configured in a row of the TDRA table indicated by the DCI. It may be either a Valid PDSCH or an Invalid PDSCH.

[0187] In implementation, TB disabling can include a first TB disabling method (which can also be called TB disabling method 1) and a second TB disabling method (which can also be called TB disabling method 2).

[0188] TB disabling mode 1 means that for a given TB (e.g., the first TB or the second TB), all valid PDSCHs scheduled by a single DCI uniformly determine their on / off state. For example, for a given TB, when the DCI indicates that the modulation and coding scheme (MCS) corresponding to this TB satisfies I... MCS=26, and the value of the redundancy version (RV) bit sequence corresponding to this TB in the DCI is a predefined 0 / 1 sequence (), which indicates that this TB of each valid PDSCH scheduled by this DCI is turned off; if the above conditions are not met, it is considered that this TB of each valid PDSCH scheduled by this DCI is turned on.

[0189] The RV bit sequence corresponding to a certain TB in the above DCI can be any of the following:

[0190] 1) It is formed by concatenating all the RV bits reserved for this TB in the DCI; for example, assuming that the maximum number of Entry / SLIV configured in a certain row of the TDRA table is M, when the number of PDSCH scheduled by a certain DCI is greater than 1, M RV bits are reserved for a certain TB in this DCI, that is, the RV bit sequence corresponding to this TB contains M bits.

[0191] 2) The RV bits reserved for this TB in the DCI are concatenated sequentially with all the RV bits corresponding to a certain Scheduled PDSCH scheduled by this DCI. For example, when the number N of PDSCHs scheduled by a certain DCI is greater than 1 (and N<=M), M RV bits are reserved for a certain TB in this DCI, of which only N RV bits are actually used to indicate the RV information of the Scheduled PDSCH, that is, the RV bit sequence corresponding to this TB contains N bits.

[0192] 3) The RV bits corresponding to a certain Valid PDSCH scheduled by this DCI are concatenated from all the RV bits reserved for this 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 it contains N1 Valid PDSCHs (and N1<=N), M RV bits are reserved for a certain TB in this DCI, of which only N1 RV bits are actually used to indicate the RV information of the Valid PDSCH, that is, the RV bit sequence corresponding to this TB contains N1 bits.

[0193] The predefined 0 / 1 sequence can be an all-0 or all-1 sequence of the same length as the RV bit sequence. For example, for mode 1), the predefined 0 / 1 sequence can be an all-1 sequence of length M; for mode 2), the predefined 0 / 1 sequence can be an all-1 sequence of length N; for mode 2), the predefined 0 / 1 sequence can be an all-1 sequence of length N1.

[0194] TB disabling mode 2 means that for a certain TB (e.g., the first TB or the second TB), each valid PDSCH of a single DCI scheduler independently determines its on / off state.

[0195] For example: For a certain TB and a certain Valid PDSCH, when the DCI indicates that the MCS corresponding to this TB satisfies I... MCS =26, and when the RV bit corresponding to this TB and this Valid PDSCH in the DCI is a predefined value, it indicates that this TB of this Valid PDSCH is turned off; when the above conditions are not met, it is considered that this TB of this Valid PDSCH is turned on.

[0196] For example, in DCI, the RV bit corresponding to a certain TB and a certain Valid PDSCH contains only a single bit, and the predefined value can be 1, or, along with RV... id =2.

[0197] In other words, in this embodiment, when the Serving cell is not configured to allow dual-codeword transmission, the number of TBs enabled for each target scheduling line can be considered as 1; when the Serving cell is configured to allow dual-codeword transmission, the number of TBs enabled for each target scheduling line can be determined by any of the following:

[0198] When using TB disabling method 1, the number of TBs uniformly enabled by DCI corresponding to this target scheduling line;

[0199] When using TB disabling method 2, the actual number of TBs enabled in the DCI corresponding to this target scheduling line.

[0200] Specifically, for a certain TB (e.g., the first TB or the second TB), if the DCI corresponding to this target scheduler enables this TB for at least one Valid PDSCH, it can be considered that this TB is actually enabled; otherwise, it is considered that this TB is actually disabled.

[0201] Method 2

[0202] The number of TBs opened for M target scheduling lines.

[0203] In some optional implementations, when the Serving cell is not configured to allow dual codeword transmission, the number of TBs opened for the M target scheduling lines is 1;

[0204] In some alternative implementations, the number of TBs opened for the M target scheduling lines includes:

[0205] The maximum number of TBs opened for each of the M target scheduling lines;

[0206] The number of TBs to be enabled is determined based on the M target scheduling lines.

[0207] Specifically, when the Serving cell configuration allows dual-codeword transmission, the number of TBs opened for the M target scheduling lines can be determined by any of the following:

[0208] 1) Take the maximum number of TBs opened for each target scheduling line.

[0209] In implementation, the number of TBs enabled for each target scheduling line can be determined in the same way as in Method 1 when dual codeword transmission is configured in the serving cell (e.g., by determining the number of TBs enabled for each target scheduling line according to the TB de-enabling method), which will not be elaborated here.

[0210] 2) Based on the above M target scheduling lines, determine the number of TBs that are enabled.

[0211] The number of TBs that are enabled is determined based on the activation status of each TB among the M target scheduling lines. Specifically, for a given TB (e.g., the first TB or the second TB), the TB is declared enabled when at least one of the M target scheduling lines has enabled it. It is understood that the number of TBs declared enabled is either 1 or 2.

[0212] Method 3

[0213] The sum of the number of TBs configured for each of the M target scheduling lines.

[0214] In implementation, if the serving cell is not configured to allow dual-codeword transmission, the number of TBs configured for the target scheduling line can be considered as 1; or,

[0215] When the serving cell is configured to allow dual codeword transmission, the number of TBs configured for the target scheduling line can be considered to be 2.

[0216] The sum of the number of TBs configured for each target scheduling line = M × the number of TBs configured for each scheduling line.

[0217] Method 4

[0218] The number of TBs configured for the M target scheduling lines. In implementation, the number of TBs configured for the M target scheduling lines can be directly determined based on whether the Serving cell is configured to allow dual-codeword transmission. Specifically, the value is 1 when dual-codeword transmission is not configured, and 2 otherwise.

[0219] In the above sub-case 1-1, This represents the number of TBs corresponding to the scheduling line mapped to PDSCH reception occasion m.

[0220] Sub-case 1-2: In the case where the target scheduling line includes a scheduling line determined based on the first PDSCH mapped to the first occasion and the association relationship based on the last time-domain resource allocation record, the first PDSCH can be mapped to the PDSCH reception occasion m based on its DLslot and its corresponding SLIV.

[0221] The first PDSCH can be a dynamically scheduled PDSCH or an SPS PDSCH, and the first PDSCH can be a Valid PDSCH or an Invalid PDSCH.

[0222] The first PDSCH mentioned above, which is based on the target scheduling line corresponding to the Last SLIV association, can be understood as follows: this first PDSCH is associated with or corresponds to the Last SLIV of the target scheduling line, or in other words, this PDSCH is the PDSCH corresponding to the last Entry / SLIV among one or more Entry / SLIVs configured in the scheduling line when scheduling / configuring this scheduling line.

[0223] It is understandable that the situation is determined in cases 1-2 of this notebook. The method is determined in sub-case 1-1 above. The main difference is that in sub-cases 1-2, it is assumed that when configuring application time domain bundling, PDSCH or its corresponding SLIV (including the DL slot where PDSCH / SLIV is located) is mapped to Occasion, rather than mapping TDRA table rows to Occasion. However, the difference is only in understanding or description, and their essence or output is the same.

[0224] In implementation, given that the scheduling line has corresponding other 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), after determining the PDSCH mapped to PDSCH reception occasion m, the scheduling line (e.g., M scheduling lines) corresponding to this or these PDSCHs mapped to PDSCH reception occasion m can be further determined based on the aforementioned other scheduling information or configuration information and the Last SLIV association. Then, the determination can be continued... The relevant operations in sub-case 1-1 (e.g., any one of methods 1 to 4) determine this. Values.

[0225] Optionally, when it is required that the PDSCH corresponding to the last time-domain resource allocation record of any scheduling line is a valid PDSCH, the terminal determines that the first variable is equal to the number of TBs corresponding to the target scheduling line, including:

[0226] 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, then the terminal determines that the target TB number is equal to the TB number enabled by the first PDSCH or the configured TB number.

[0227] If the first PDSCH does not exist, or if the first PDSCH is not associated with or corresponds to the last time-domain resource allocation record of any scheduling line, then the terminal determines that the first variable is equal to 0.

[0228] In implementation, when the PDSCH corresponding to the Last SLIV of any scheduling line is required to be a Valid PDSCH, if there exists 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, then the number of TBs enabled by this PDSCH (which must be a Valid PDSCH) can be directly used, or the configured number of TBs can be used as... The value of ; otherwise

[0229] When configuring Spatial bundling>

[0230] As an optional implementation, when the codebook used in the HARQ-ACK is a first type of codebook, and the first type of codebook is configured to be transmitted using time-domain binding and spatial-domain binding, if the terminal receives the PDSCH at the first opportune moment, the terminal determines the first variable based on the target information, including:

[0231] The terminal determines that the first variable is equal to the number of target scheduling lines;

[0232] The target scheduling line includes a scheduling line mapped to the first timing, or the target scheduling line includes a scheduling line determined based on the first PDSCH mapped to the first timing and the association relationship of the last time domain resource allocation record. The scheduling line includes: a row of the TDRA table in which the terminal is actually scheduled or configured.

[0233] In implementation, when the codebook used in HARQ-ACK is a first-type codebook, and the first-type codebook is configured to be transmitted using time-domain binding and spatial-domain binding, the following two methods can be used to determine... The possible values ​​of:

[0234] Method 1

[0235] The number of rows in the target scheduling line mapped to PDSCH reception occasion m.

[0236] In some implementations, assuming the number of target scheduling lines mapped to PDSCH reception occasion m is M, then

[0237] In other embodiments, when M=0, determine When M>0, determine

[0238] Method 2

[0239] The number of scheduling lines corresponding to the PDSCH based on the Last SLIV association that is mapped to PDSCH reception occasion m.

[0240] In implementation, after determining the corresponding target scheduling line (e.g., M target scheduling lines) based on the PDSCH mapped to PDSCH reception occasion m (or possibly based on scheduling information / configuration information of the scheduling line, etc.) and the Last SLIV association, the relevant operations in Method 1 of sub-case 2 above can be used to determine the target scheduling line. The values ​​will not be repeated here.

[0241] Optionally, when it is required that the PDSCH corresponding to the last time-domain resource allocation record of any scheduling line is a valid PDSCH, the terminal determines that the first variable is equal to the number of target scheduling lines, including any one of the following:

[0242] 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, then the terminal determines that the number of the target scheduling lines is equal to 1.

[0243] If the first PDSCH does not exist, or if the first PDSCH is not associated with or corresponds to the last time-domain resource allocation record of any scheduling line, then the terminal determines that the number of the target scheduling lines is equal to 0.

[0244] In this implementation, when the PDSCH corresponding to the Last SLIV of a scheduling line is always required to be a Valid PDSCH, if there exists 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, then it is determined that... Otherwise confirm

[0245] Example 2: n of the Type-2 codebook HARQ-ACK calculate

[0246] As an optional implementation, when the codebook used in the HARQ-ACK is a second type of codebook, the terminal determines the first power control parameter based on target information related to the Multi-PDSCH scheduling, including:

[0247] When no time-domain binding is configured in each cell of the PUCCH cell group, the terminal determines the first power control parameter based on the first subcodebook and the second subcodebook. The PUCCH cell group includes the serving cell of the terminal. The first subcodebook corresponds to a single HARQ-ACK granularity, and the second subcodebook corresponds to multiple HARQ-ACK granularities.

[0248] When all cells configured with Multi-PDSCH scheduling in the PUCCH cell group are configured with time-domain binding and the number of configured binding groups is equal to 1, the terminal determines the first power control parameter according to the first subcodebook.

[0249] If at least one of the cells configured with Multi-PDSCH scheduling in the PUCCH cell group is configured with time-domain binding and the number of configured binding groups is greater than 1, the terminal determines the first power control parameter based on the first subcodebook and the second subcodebook.

[0250] For n in the Type-2 codebook HARQ-ACK In Rel-15 / 16, the calculations are performed separately for each Sub-codebook, specifically including the Sub-codebook for HARQ-ACK feedback at the TB granularity and the Sub-codebook for HARQ-ACK feedback at the CBG granularity.

[0251] In this embodiment, when at least one Serving cell corresponding to a PUCCH cell group is configured with Multi-PDSCH scheduling, no CBG transmission can be configured for any Serving cell within this PUCCH cell group. Therefore, there is no need to consider n for the Sub-codebook based on CBG-granular HARQ-ACK feedback. HARQ-ACK calculate.

[0252] In this embodiment of the application, when at least one Serving cell corresponding to a certain PUCCH cell group is configured with Multi-PDSCH scheduling, the Sub-codebook settings can be distinguished into the following cases:

[0253] Scenario 1

[0254] Time domain bundling is not configured for any of the Serving cells corresponding to this PUCCH cell group.

[0255] In this case, the Type-2 codebook involves two sub-codebooks.

[0256] The first sub-codebook, also known as the first sub-codebook, corresponds to a single HARQ-ACK granularity, meaning only a single HARQ-ACK needs to be fed back for each DCI / SPS PDSCH. In implementation, at least one of the following can be included in the first sub-codebook:

[0257] Schedule the HARQ-ACK corresponding to the DCI of a single PDSCH;

[0258] HARQ-ACK corresponding to DCI that does not schedule PDSCH but needs to feed back HARQ-ACK;

[0259] HARQ-ACK corresponding to SPS PDSCH.

[0260] The aforementioned second sub-codebook can also be called the second sub-codebook. This second sub-codebook corresponds to multiple HARQ-ACK granularities, meaning that multiple HARQ-ACKs (i.e., more than one HARQ-ACK) need to be fed back for each DCI. The second sub-codebook can contain HARQ-ACKs corresponding to DCIs with scheduling greater than one PDSCH.

[0261] Scenario 2

[0262] All Serving cells configured with Multi-PDSCH scheduling within this PUCCH cell group are configured with Timedomain bundling, and the number of configured Bundling groups is 1.

[0263] The above scenario 2 can be understood as follows: all HARQ-ACKs corresponding to DCIs with scheduling greater than one PDSCH will undergo Time domain bundling operations and be placed into the first Sub-codebook. Therefore, in this case, the Type-2 codebook involves a single Sub-codebook.

[0264] In scenario two above, the (unique) first sub-codebook corresponds to a single HARQ-ACK granularity, meaning only a single HARQ-ACK needs to be fed back for each DCI / SPS PDSCH. Compared to scenario one, the first sub-codebook can also include bundled HARQ-ACKs corresponding to HARQ-ACKs of DCIs with scheduling greater than one PDSCH, or in other words, the first sub-codebook can also include HARQ-ACKs obtained by temporally binding the HARQ-ACKs of DCIs with scheduling greater than one PDSCH.

[0265] Scenario 3

[0266] Within this PUCCH cell group, at least one of the serving cells configured with Multi-PDSCH scheduling is configured with Time domain bundling, and the number of configured bundling groups is greater than 1.

[0267] The above scenario three can be understood as follows: there exists at least one DCI with a scheduling of more than one PDSCH whose corresponding HARQ-ACK undergoes a time domain bundling operation and is placed into the second sub-codebook.

[0268] In scenario three above, the Type-2 codebook involves two sub-codebooks. The first sub-codebook corresponds to a single HARQ-ACK granularity, meaning that only a single HARQ-ACK needs to be fed back for each DCI / SPS PDSCH. The second sub-codebook corresponds to a multi-HARQ-ACK granularity, meaning that multiple HARQ-ACKs (more than one HARQ-ACK) need to be fed back for each DCI.

[0269] For example: Suppose that there are N (N>0) Serving cells configured with Multi-PDSCH scheduling in this PUCCH cell group, of which M (M>0 and M<=N) Serving cells are configured with Time domain bundling; among these M Serving cells, M2 (M2>0 and M2<=M) Serving cells are configured with a number of Bundling groups greater than 1, and M1 (M1=M–M2) Serving cells are configured with a number of Bundling groups of 1. In this case, the second Sub-codebook can contain HARQ-ACKs corresponding to DCIs with scheduling more than one PDSCH (when N>M), and / or Bundled HARQ-ACKs corresponding to HARQ-ACKs corresponding to DCIs with scheduling more than one PDSCH (or, HARQ-ACKs obtained by time domain binding of HARQ-ACKs corresponding to DCIs with scheduling more than one PDSCH).

[0270] In implementation, the HARQ-ACKs corresponding to the M1 Serving cells with a Bundling group of 1 are placed in the first Sub-codebook. Therefore, compared to Case 1, Case 3 contains essentially the same HARQ-ACKs in the first Sub-codebook. The difference lies in the fact that when M1 > 0, the first Sub-codebook can also contain bundled HARQ-ACKs corresponding to the HARQ-ACKs of DCIs with scheduling greater than one PDSCH (or, the first Sub-codebook can also contain HARQ-ACKs obtained by time-domain binding of the HARQ-ACKs of DCIs with scheduling greater than one PDSCH).

[0271] Case 1 does not involve time domain bundling. Cases 2 and 3 both involve time domain bundling, and the difference between Case 2 and Case 3 is that: for DCIs with more than one PDSCH, the HARQ-ACKs obtained after time domain bundling are not placed in the second sub-codebook in Case 2, but can be placed in the second sub-codebook in Case 3.

[0272] In some implementations, when the Type-2 codebook contains only the first Sub-codebook, n is calculated only for the first Sub-codebook. HARQ-ACK .

[0273] In other implementations, 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 Then take the sum of the two.

[0274] Optionally, the terminal determines the first power control parameter based on the first subcodebook and the second subcodebook, including:

[0275] The terminal determines the first parameter according to the second calculation rule corresponding to the first sub-codebook, and determines the second parameter according to the third calculation rule corresponding to the second sub-codebook;

[0276] The terminal determines that the first power control parameter is equal to the sum of the first parameter and the second parameter.

[0277] The first parameter can be 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 second parameter mentioned above can be understood as n determined according to the third calculation rule corresponding to the second subcodebook. HARQ-ACK For ease of distinction, the second parameter will be referred to as n in the following embodiments. HARQ-ACK,second .

[0278] The following sections will discuss n. HARQ-ACK,first and n HARQ-ACK,second The process of determining [the value] will be explained as follows:

[0279] 1. For n HARQ-ACK,first Calculation

[0280] As an optional implementation, the terminal determines the first power control parameter based on the first subcodebook, including:

[0281] The terminal determines a third variable based on the target information;

[0282] The terminal determines the first power control parameter based on the second calculation rule and the third variable.

[0283] In practice, the third variable mentioned above can be the number of effective bits of HARQ-ACK determined by the terminal. Based on the foregoing analysis, the first sub-codebook corresponds to a single HARQ-ACK granularity. The first sub-codebook contains the HARQ-ACK corresponding to a DCI that schedules a single PDSCH, the HARQ-ACK corresponding to a DCI that does not schedule a PDSCH but requires HARQ-ACK feedback, and the HARQ-ACK corresponding to an SPS PDSCH. For cases two and three, the first sub-codebook can also contain the HARQ-ACK obtained by time-domain binding of the HARQ-ACK corresponding to a DCI that schedules more than one PDSCH.

[0284] In this embodiment of the application, the second calculation rule can be expressed by the following formula (7):

[0285]

[0286] Considering that "the first sub-codebook can also include the HARQ-ACK corresponding to DCIs with scheduling greater than one PDSCH, which is obtained after time-domain binding", the above formula (7) The determination method can be distinguished between the following cases 1.1 and 1.2:

[0287] Case 1.1

[0288] The terminal detected a DCI that scheduled PDSCH within PDCCH monitoring occasion m.

[0289] The DCI for scheduling PDSCH can include: a DCI that schedules only a single PDSCH; and a DCI used to schedule at least two PDSCHs. For cases two or three above, when serving cell c is configured with Multi-PDSCH scheduling, and Time domain bundling is configured with a Bundling group number of 1, the decoding results of at least two scheduled PDSCHs are used to obtain a single HARQ-ACK bit based on Time domain bundling, and this is placed in the first Sub-codebook. This will not be elaborated further here.

[0290] Among them, the above situation 1.1 can be further divided into the following situations 1.1.1 and 1.1.2:

[0291] Case 1.1.1

[0292] When Spatial bundling is not configured, you can determine this in the following ways.

[0293] As an optional implementation, if the terminal detects the DCI scheduling PDSCH within the second timing period and has not configured application space domain binding, the terminal determines a third variable based on the target information, including:

[0294] The terminal determines that the third variable is equal to the number of TBs actually enabled by the PDSCH scheduling DCI detected by the terminal during the second timing period.

[0295] The second timing mentioned above could be PDCCH monitoring occasion m, which is the third variable. This refers to the number of TBs that the terminal detected actually enabled for PDSCH scheduling DCI within PDCCH monitoring occasion m.

[0296] In implementation, if the serving cell is not configured to allow dual codeword transmission, the actual number of TBs enabled for each PDSCH scheduling DCI can be equal to 1; or,

[0297] The number of TBs actually enabled by each PDSCH scheduling DCI can be any of the following:

[0298] When the first TB is disabled, the number of TBs that are uniformly enabled by the DCI scheduler for each PDSCH is used.

[0299] When using the second TB de-enabling method, the number of TBs actually enabled by each PDSCH scheduling DCI is...

[0300] Specifically, for a certain TB (e.g., the first TB or the second TB), if this DCI enables this TB for at least one ValidPDSCH, it can be considered that this TB is actually enabled; otherwise, it is considered that this TB is actually disabled.

[0301] In implementation, when the terminal in PDCCH monitoring occasion m only allows the detection of a single PDSCH scheduling DCI for a single Serving cell, the actual number of TBs enabled for the detected single PDSCH scheduling DCI will be used as... When the terminal is allowed to detect more than one PDSCH scheduling DCI for a single Serving cell within PDCCH monitoring occasion m, the actual number of TBs activated for each detected PDSCH scheduling DCI will be summed as the result.

[0302] As another optional implementation, if the terminal detects the DCI scheduling PDSCH within the second timing period and has not configured application space domain binding, the terminal determines a third variable based on the target information, including:

[0303] The terminal determines that the third variable is equal to the number of TBs of the PDSCH scheduling DCI configuration detected by the terminal during the second timing period.

[0304] Similar to the third variable mentioned above being equal to the number of TBs actually enabled by the PDSCH scheduling DCI detected by the terminal during the second timing period, when the serving cell is not configured to allow dual codeword transmission, the number of TBs configured for each PDSCH scheduling DCI can be equal to 1.

[0305] Furthermore, when the serving cell configuration allows dual codeword transmission, the number of TBs configured for each PDSCH scheduling DCI can be equal to 2.

[0306] Optionally, the terminal determines a third variable based on the target information, including:

[0307] If, during the second timing period, the terminal is only allowed to detect a single PDSCH scheduling DCI for a single serving cell, the terminal determines that the third variable is equal to the number of TBs actually enabled or the configured number of TBs for the single PDSCH scheduling DCI detected by the terminal; or,

[0308] If, during the second timing period, the terminal is allowed to detect at least two PDSCH scheduling DCIs for a single serving cell, the terminal determines that the third variable is equal to the sum of the actual number of TBs or the configured number of all PDSCH scheduling DCIs detected by the terminal.

[0309] The second timing mentioned above can be PDCCH monitoring occasion m. When the terminal is only allowed to detect a single PDSCH scheduling DCI for a single Serving cell within PDCCH monitoring occasion m, the number of TBs configured for the detected single PDSCH scheduling DCI will be used as... When a terminal is allowed to detect more than one PDSCH scheduling DCI for a single Serving cell within a PDCCH monitoring occasion m, the TB number configured for each detected PDSCH scheduling DCI will be summed as the result. or,

[0310] Case 1.1.2

[0311] Optionally, if the terminal detects the DCI scheduling PDSCH within the second timing period and configures application space domain binding, the terminal determines a third variable based on the target information, including:

[0312] The terminal determines that the third variable is equal to the number of PDSCH scheduled DCIs detected by the terminal during the second timing period.

[0313] In this scenario 1.1.2, when Spatial bundling is configured, The number of PDSCH scheduling DCIs detected by the terminal within the PDCCH monitoring occasion m.

[0314] Case 1.2

[0315] The terminal detects a DCI that is not scheduled for PDSCH but requires HARQ-ACK feedback within PDCCH monitoring occasion m.

[0316] In the above situation 1.2, It can be the number of DCIs that the terminal detects in serving cell c during PDCCH monitoring occasion m, which are not scheduled PDSCH receptions but require feedback of the corresponding HARQ-ACK.

[0317] It should be noted that when only condition 1.1 or condition 1.2 is satisfied, the condition corresponding to satisfying condition 1.1 or condition 1.2 can be directly selected. When both condition 1.1 and condition 1.2 are satisfied, the corresponding conditions for each condition are... The sum is the final result. When neither condition 1.1 nor condition 1.2 is satisfied,

[0318] 2. For n HARQ-ACK,second Calculation

[0319] Based on the foregoing analysis, the second sub-codebook corresponds to multiple HARQ-ACK granularities. The second sub-codebook can contain HARQ-ACKs corresponding to DCIs with scheduling greater than one PDSCH, and / or HARQ-ACKs obtained by temporally binding the HARQ-ACKs corresponding to DCIs with scheduling greater than one PDSCH.

[0320] Optionally, the terminal determines the second parameter according to the third calculation rule corresponding to the second sub-codebook, including:

[0321] The terminal determines a fourth variable based on the target information;

[0322] The terminal determines the second parameter based on the third calculation rule and the fourth variable.

[0323] The fourth variable may include It is used to reflect the actual scheduling situation of the first type of DCI detected by the terminal for the serving cell c within the PDCCH detection time m (specifically as in case 2.1 below). The first type of DCI can be a DCI used to schedule more than one PDSCH.

[0324] In implementation, the third calculation rule mentioned above can be specifically divided into the following cases 2.1 and 2.2 for determining the second parameter:

[0325] Case 2.1

[0326] When the second sub-codebook does not involve or include the HARQ-ACK obtained after time-domain binding of the DCI corresponding to the scheduling of more than one PDSCH (corresponding to Case 1 / Case 2 above).

[0327] Optionally, the terminal determines the second parameter according to the third calculation rule corresponding to the second sub-codebook, including:

[0328] In the case where the second subcodebook does not include the target HARQ-ACK, and the target HARQ-ACK includes the HARQ-ACK obtained by time-domain binding of the first HARQ-ACK, the terminal determines the second parameter according to the following formula (7):

[0329]

[0330] Wherein, the first HARQ-ACK is the HARQ-ACK corresponding to the DCI used to schedule at least two PDSCHs, n HARQ-ACK,second This represents the second parameter determined according to the third calculation rule corresponding to the second subcodebook;

[0331] This indicates the number of bits occupied by the Counter (DAI) function;

[0332] This indicates the number of serving cells within the PUCCH cell group that are configured with Multi-PDSCH scheduling;

[0333] exist hour, This represents the value of the count DAI carried by the last first type DCI detected by the terminal for any serving cell within M PDCCH detection opportunities. The first type DCI includes DCIs used for scheduling more than one PDSCH.

[0334] exist hour, This represents the total DAI value carried by the last first type DCI detected by the terminal for any serving cell within M PDCCH detection opportunities;

[0335] When the terminal does not detect any of the first type of DCI for any serving cell within M PDCCH detection opportunities.

[0336] This represents the total number of the first type of DCI detected by the terminal in M ​​PDCCH detection opportunities for serving cell c;

[0337] Indicates traversal The service area received The maximum value;

[0338] For serving cell c, the maximum number of PDSCH receptions that can be scheduled for a single first-type DCI;

[0339] When application space binding is not configured The maximum number of codewords configured for DCI scheduling in serving cell c (i.e., the value of the parameter maxNrofCodeWordsScheduledByDCI); when application spatial binding is configured,

[0340] If no space domain binding is configured, then This represents the total number of transport blocks actually scheduled by the UE for the first type of DCI within the PDCCH detection time m for the serving cell c; if spatial binding is configured, then... The total number of valid PDSCHs of the first type of DCI scheduling detected by the UE for the serving cell c within the PDCCH detection time m.

[0341] In this embodiment, the fourth variable mentioned above may include The third calculation rule mentioned above can be expressed as formula (7) above. And in formula (7) above, for The following situations can be distinguished to determine:

[0342] Case 2.1.1

[0343] When Spatial bundling is not configured to be applied This represents the total number of TBs actually scheduled by the PDSCH scheduling DCI for Serving cell c within the PDCCH monitoring occasion m. For a single PDSCH scheduling DCI, the number of TBs carried by each Valid PDSCH scheduled can be determined based on whether Serving cell c is configured to allow dual codeword transmission and the TB disabling mode 1 / 2 (either 1 or 2). The actual number of TBs scheduled by this PDSCH scheduling DCI is the sum of the number of TBs carried by each Valid PDSCH it schedules.

[0344] Case 2.1.2

[0345] When configuring Spatial bundling application This represents the total number of valid PDSCH scheduling DCI schedulings detected by the UE for Serving cell c within the PDCCH monitoring occasion m, where more than one PDSCH is scheduled.

[0346] In implementation, when the UE is only allowed to detect a single PDSCH scheduling DCI for a single Serving cell within a PDCCH monitoring occasion m, the actual number of TBs scheduled for the detected single PDSCH scheduling DCI (when Spatial bundling is not configured) or the number of valid PDSCHs scheduled (when Spatial bundling is configured) will be used as the basis for determining the effective number of PDSCHs. When a UE is allowed to detect more than one PDSCH scheduling DCI for a single Serving cell within a PDCCH monitoring occasion m, the actual number of TBs scheduled for each detected PDSCH scheduling DCI (when Spatial bundling is not configured) or the number of valid PDSCHs scheduled (when Spatial bundling is configured) will be summed as follows:

[0347] Case 2.2

[0348] When the second sub-codebook involves or includes the HARQ-ACK corresponding to a DCI with a schedule greater than one PDSCH, which is obtained after time-domain binding.

[0349] Optionally, if the second subcodebook includes the target HARQ-ACK, the terminal determines the second parameter according to the following formula (8):

[0350]

[0351] in, This indicates the number of multi-feedback cells within the PUCCH cell group. The multi-feedback cells belong to either the first type of cell or the second type of cell. The first type of cell is a serving cell that is configured with Multi-PDSCH scheduling but not configured with time-domain binding (i.e., the numberOfHARQ-BundlingGroups parameter is not configured). The second type of cell is a serving cell that is configured with Multi-PDSCH scheduling and configured with time-domain binding, and the number of configured binding groups is greater than 1.

[0352] equal

[0353] For the first cell c, the corresponding first maximum value is based on calculate, The maximum number of PDSCH receptions that can be scheduled 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 that belongs to the first type of multiple feedback cell;

[0354] For the second cell c, the corresponding first maximum value is based on calculate, The number of binding groups configured for the second cell c; the second cell is Any one of the multiple feedback cells that belongs to the second type of multiple feedback cell;

[0355] For traversal The maximum value of the first maximum value corresponding to each of the multiple feedback cells.

[0356] In this embodiment, the fourth variable mentioned above may include The third calculation rule mentioned above can be expressed as formula (8) above.

[0357] In the above formula (8), The meaning and value of can be determined by distinguishing the following situations:

[0358] Case 2.2.1

[0359] When Spatial bundling is not configured to be applied This refers to the total number of Bundle groups actually scheduled for each TB by the PDSCH scheduling DCI (Distributed Packet Control Index) for Serving cell c when the UE detects scheduling of more than one PDSCH within PDCCH monitoring occasion m. For a single PDSCH scheduling DCI, the number of Bundle groups actually scheduled for a TB (either the first or second TB when Serving cell c is configured for dual-codeword transmission; or only the first TB when Serving cell c is not configured for dual-codeword transmission) can be understood as follows: a Bundle group is considered to be actually scheduled when it contains at least one Valid PDSCH and at least one Valid PDSCH enables this TB. Based on whether Serving cell c is configured to allow dual-codeword transmission and the applied Bundle group division method, the number of Bundle groups actually scheduled for a TB by a single PDSCH scheduling DCI can be determined. When Serving cell c is configured with 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 each of the two TBs respectively; when Serving cell c is not configured with dual codeword transmission, the number of Bundling groups actually scheduled by a single PDSCH scheduling DCI for each TB is the number of Bundling groups actually scheduled for the first TB.

[0360] Case 2.2.2

[0361] When configuring Spatial bundling application This represents the total number of binding groups actually scheduled by the UE for PDSCH scheduling DCIs that detect more than one PDSCH for Serving cell c within the PDSCH monitoring occasion m. For a single PDSCH scheduling DCI, the actual scheduling of a binding group can be understood as follows: when a binding group contains at least one valid PDSCH, it is considered that this binding group has been actually scheduled.

[0362] Case 2.2.3

[0363] When a UE is only allowed to detect a single PDSCH scheduling DCI for a single Serving cell within a PDCCH monitoring occasion m, the number of actual bundling groups for each TB (when Spatial bundling is not configured) or the number of actual bundling groups (when Spatial bundling is configured) for the detected single PDSCH scheduling DCI will be used as the basis for determining the number of actual bundling groups for each TB (when Spatial bundling is configured). When a UE is allowed to detect more than one PDSCH scheduling DCI for a single Serving cell within a PDCCH monitoring occasion m, the number of actual bundling groups scheduled for each TB for each detected PDSCH scheduling DCI (when Spatial bundling is not configured) or the number of actual bundling groups scheduled (when Spatial bundling is configured) will be summed as follows:

[0364] In addition, the meanings of the other parameters in formula (8) above, besides the fourth variable mentioned above, are described as follows:

[0365] Its meaning and values ​​can be distinguished in the following ways:

[0366] 1) When hour, The value of the counter DAI carried by the UE for the last Type II DCI detected by the UE for any serving cell within M PDCCH monitoring occasions;

[0367] 2) When hour, The value of total DAI is the last type 2 DCI carried by the UE for any serving cell within M PDCCH monitoring occasions.

[0368] 3) When the UE does not detect any Type 2 DCI for any serving cell within M PDCCH monitoring occasions,

[0369] The second type of DCI here needs to meet all of the following characteristics: (1) scheduling more than one PDSCH; (2) the Serving cell corresponding to the scheduled PDSCH is not configured with Time domain bundling, or it is configured with Time domain bundling and the number of configured Bundling groups is greater than 1.

[0370] Its meaning and value can be determined by distinguishing the following cases:

[0371] 1) For serving cell c, the total number of Type II DCIs detected by the UE in M ​​PDCCH monitoring occasions;

[0372] 2) When the UE does not detect any Type 2 DCI in M ​​PDCCH monitoring occasions for serving cell c,

[0373]

[0374] For scenario three, The number of Serving cells within a PUCCH cell group that are configured with Multi-PDSCH scheduling but not with Time domain bundling, and the number of Serving cells that are configured with Multi-PDSCH scheduling, with Time domain bundling, and with more than one Bundling group configured. In other words, The number of Serving cells configured for Multi-PDSCH scheduling within a PUCCH cell group is specified. When a Serving cell is configured with Time domain bundling, it is only included if the number of configured bundling groups is greater than 1. Inside. Note that at this time... The values ​​are as follows:

[0375] Optionally, Directly (Number of Serving cells corresponding to the PUCCH cell group). At this point, for Serving cells without Multi-PDSCH scheduling, or Serving cells with Multi-PDSCH scheduling configured, Time domain bundling configured, and a Bundling group number of 1, the corresponding...

[0376]

[0377] for Serving cell c in a serving cell, when numberOfHARQ-BundlingGroups is configured (i.e., time domain bundling is configured), uses As its corresponding value, when numberOfHARQ-BundlingGroups is not configured (i.e., time domain bundling is not configured), use As its corresponding value; traversal For each serving cell, obtain the maximum value corresponding to each serving cell;

[0378] The value of numberOfHARQ-BundlingGroups configured for serving cell c is the number of bundling groups configured when serving cell c is configured with Time domain bundling.

[0379]

[0380] When Spatial bundling is not configured to be applied The value of maxNrofCodeWordsScheduledByDCI configured for serving cell c; when configuring Spatial bundling,

[0381] In summary, when a Type-2 codebook contains two sub-codebooks, n can be calculated separately for the first and second sub-codebooks. HARQ-ACK Then take the sum of the two.

[0382] In other words, the terminal determines the first power control parameter based on the first sub-codebook and the second sub-codebook, including:

[0383] The terminal determines the first parameter according to the second calculation rule corresponding to the first sub-codebook, and determines the second parameter according to the third calculation rule corresponding to the second sub-codebook;

[0384] The terminal determines that the first power control parameter is equal to the sum of the first parameter and the second parameter.

[0385] The process of determining the first parameter according to the second calculation rule corresponding to the first sub-codebook is the same as the above-mentioned n. HARQ-ACK,first The meaning and determination process 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:

[0386] The terminal determines a third variable based on the target information;

[0387] The terminal determines the first parameter based on the second calculation rule and the third variable.

[0388] Furthermore, the process of determining the second parameter according to the third calculation rule corresponding to the second subcodebook is similar to the process of determining the second parameter according to the above-mentioned n. HARQ-ACK,second The meaning and determination process are the same, that is, the terminal determines the second parameter according to the third calculation rule corresponding to the second sub-codebook, including:

[0389] The terminal determines a fourth variable based on the target information;

[0390] The terminal determines the second parameter based on the third calculation rule and the fourth variable.

[0391] The process by which the terminal determines the first parameter based on the second calculation rule and the third variable, and the process by which the terminal determines the second parameter based on the third calculation rule and the fourth variable, will not be described again here.

[0392] Example 3: For enhancing the Type-2 codebook n HARQ-ACK Calculation

[0393] For the enhanced Type-2 codebook, the n corresponding to each PDSCH group involved is... HARQ-ACK The calculation can follow the method used in the embodiments of this application for n for the Type-2 codebook. HARQ-ACK The calculations and other rules are similar to the corresponding rules in Rel-16, and will not be repeated here.

[0394] Example 4: For n in the Type-3 codebook HARQ-ACK Calculation

[0395] The Type-3 codebook (including the enhanced Type-3 codebook) is constructed based on the HARQ process and is not affected by whether Multi-PDSCH scheduling and Time domain bundling are configured.

[0396] In this embodiment, when the serving cell of the terminal is configured with Multi-Physical Downlink Shared Channel (PDSCH) scheduling, the terminal determines a first power control parameter based on target information related to the Multi-PDSCH scheduling. The first power control parameter includes the effective number of Hybrid Automatic Repeat Request (HARQ-ACK) bits. The terminal determines the transmission power of the Physical Uplink Control Channel (PUCCH) carrying the HARQ-ACK based on the first power control parameter. The terminal then transmits the PUCCH to the network-side equipment based on the transmission power. Thus, when the serving cell of the terminal is configured with Multi-PDSCH scheduling, the first power control parameter can be determined based on the target information related to the Multi-PDSCH scheduling, ensuring that the first power control parameter matches the effective number of HARQ-ACK bits contained in the HARQ-ACK codebook. This allows the determined value of the first power control parameter to match the actual Multi-PDSCH scheduling transmission, thereby ensuring that the transmission power of the PUCCH carrying the HARQ-ACK, determined according to the first power control parameter, matches the actual transmission power required by the terminal, thus guaranteeing the transmission performance of the PUCCH carrying the HARQ-ACK.

[0397] The power control parameter determination method provided in this application can be executed by a power control parameter determination device. This application uses the example of a power control parameter determination device executing the power control parameter determination method to illustrate the power control parameter determination device provided in this application.

[0398] Please see Figure 3 The power control parameter determination device provided in this application embodiment can be applied to a terminal. As shown in FIG3, the power control parameter determination device 300 may include the following modules:

[0399] The first determining module 301 is used to determine a first power control parameter based on target information related to the Multi-PDSCH scheduling when the serving cell of the terminal is configured with Multi-Physical Downlink Shared Channel (PDSCH) scheduling. The first power control parameter includes the number of effective bits of Hybrid Automatic Repeat Request Response (HARQ-ACK).

[0400] The second determining module 302 is used to determine the transmission power of the physical uplink control channel PUCCH carrying the HARQ-ACK based on the first power control parameters.

[0401] The transmitting module 303 is used to transmit the PUCCH to the network-side device according to the transmitting power.

[0402] Optionally, the target information includes at least one of the following: first configuration information for time-domain bound transmission, second configuration information for spatial-domain bound transmission, the codebook used by HARQ-ACK, and the sub-codebook used by HARQ-ACK.

[0403] Optionally, if the codebook used in the HARQ-ACK is a first type of codebook, the first determining module 301 includes:

[0404] The first determining unit is configured to determine at least one of the first variable and the second variable based on the target information;

[0405] The second determining unit is used to determine the first power control parameter according to at least one of the first variable and the second variable, and according to the first calculation rule corresponding to the first type of codebook.

[0406] Optionally, when the HARQ-ACK is configured to transmit using time-domain binding but not spatial-domain binding, if the terminal receives the PDSCH at the first opportune moment, the first determining unit is specifically used for:

[0407] Determine that the first variable is equal to the number of TBs corresponding to the target scheduling line;

[0408] The target scheduling line includes a scheduling line mapped to the first timing, or the target scheduling line includes a scheduling line determined based on the first PDSCH mapped to the first timing and the association relationship of the last time domain resource allocation record. The scheduling line includes: a row of the time domain resource allocation (TDRA) table in which the terminal is actually scheduled or configured.

[0409] Optionally, the number of target scheduling lines is M. When M = 0, the number of TBs corresponding to the target scheduling lines is 0; or,

[0410] When M > 0, the number of TBs corresponding to the target scheduling line is any one of the following:

[0411] The sum of the number of TBs opened in each of the M target scheduling lines;

[0412] The number of TBs opened for the M target scheduling lines;

[0413] The sum of the number of TBs configured for each of the M target scheduling lines;

[0414] The number of TBs configured for the M target scheduling lines.

[0415] Optionally, if the serving cell is not configured to allow dual-codeword transmission, the number of TBs enabled by the target scheduling line is equal to 1; or,

[0416] When the serving cell is configured to allow dual-codeword transmission, the number of TBs enabled by the target scheduling line is equal to any of the following:

[0417] When the first TB is disabled, the number of TBs that are uniformly enabled in the downlink control information (DCI) corresponding to the target scheduling line;

[0418] When the second TB de-enable method is used, the number of TBs actually enabled in the DCI corresponding to the target scheduling line.

[0419] Optionally, the number of TBs opened for the M target scheduling lines includes:

[0420] The maximum number of TBs opened for each of the M target scheduling lines;

[0421] The number of TBs to be enabled is determined based on the M target scheduling lines.

[0422] Optionally, if the serving cell is not configured to allow dual codeword transmission, the number of TBs configured in the target scheduling line is equal to 1; or,

[0423] When the serving cell is configured to allow dual codeword transmission, the number of TBs configured for the target scheduling line is equal to 2.

[0424] Optionally, if it is required that the PDSCH corresponding to the last time-domain resource allocation record of any scheduling line is a valid PDSCH, the first determining unit includes:

[0425] The first determining subunit is configured to determine, 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, that the target TB number is equal to the TB number enabled by the first PDSCH or the configured TB number.

[0426] The second determining subunit is configured to determine that the first variable is equal to 0 if the first PDSCH does not exist, or if the first PDSCH is not associated with or corresponds to the last time-domain resource allocation record of any scheduling line.

[0427] Optionally, when the codebook used in the HARQ-ACK is a first type of codebook, and the first type of codebook is configured to transmit using time-domain binding and spatial-domain binding, if the terminal receives the PDSCH at the first opportune moment, then the first determining unit is specifically used for:

[0428] Determine that the first variable equals the number of target scheduling lines;

[0429] The target scheduling line includes a scheduling line mapped to the first timing, or the target scheduling line includes a scheduling line determined based on the first PDSCH mapped to the first timing and the association relationship of the last time domain resource allocation record. The scheduling line includes: a row of the TDRA table in which the terminal is actually scheduled or configured.

[0430] Optionally, if it is required that the PDSCH corresponding to the last time-domain resource allocation record of any scheduling line is a valid PDSCH, the first determining unit is specifically used to perform any of the following:

[0431] 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, then the number of the target scheduling lines is determined to be equal to 1.

[0432] If the first PDSCH does not exist, or if the first PDSCH is not associated with or corresponds to the last time-domain resource allocation record of any scheduling line, then the number of target scheduling lines is determined to be equal to 0.

[0433] Optionally, if the codebook used in the HARQ-ACK is a first type of codebook, the first determining unit is further configured to:

[0434] Determine that the second variable equals 0.

[0435] Optionally, if the codebook used in the HARQ-ACK is a second type of codebook, the first determining module 301 includes:

[0436] The third determining unit is used to determine the first power control parameter based on the first subcodebook and the second subcodebook when no time-domain binding is configured in each cell of the PUCCH cell group. The PUCCH cell group includes the serving cell of the terminal. The first subcodebook corresponds to a single HARQ-ACK granularity, and the second subcodebook corresponds to multiple HARQ-ACK granularities.

[0437] The fourth determining unit is used to determine the first power control parameter based on the first subcodebook when all cells configured with Multi-PDSCH scheduling in the PUCCH cell group are configured with time-domain binding and the number of configured binding groups is equal to 1.

[0438] The fifth determining unit is configured to determine the first power control parameter based on the first subcodebook and the second subcodebook when at least one of the cells configured with Multi-PDSCH scheduling in the PUCCH cell group is configured with time-domain binding and the number of configured binding groups is greater than 1.

[0439] Optionally, the third determining unit and / or the fifth determining unit include:

[0440] The third determining subunit is used to determine the first parameter according to the second calculation rule corresponding to the first subcodebook, and to determine the second parameter according to the third calculation rule corresponding to the second subcodebook.

[0441] The fourth determining subunit is used to determine that the first power control parameter is equal to the sum of the first parameter and the second parameter.

[0442] Optionally, the fourth determining unit includes:

[0443] The fifth determining subunit is used to determine the third variable based on the target information;

[0444] The sixth determining subunit is used to determine the first power control parameter based on the second calculation rule and the third variable.

[0445] Optionally, the third determining subunit includes:

[0446] The first determining subunit is used to determine the third variable based on the target information;

[0447] The second determining sub-unit is used to determine the first parameter based on the second calculation rule and the third variable;

[0448] And / or,

[0449] The third determining subunit further includes:

[0450] The third determining subunit is used to determine the fourth variable based on the target information;

[0451] The fourth determining sub-unit is used to determine the second parameter based on the third calculation rule and the fourth variable.

[0452] Optionally, if the terminal detects the DCI scheduling PDSCH within the second timing period and has not configured application space domain binding, the fifth determining subunit and / or the first determining subunit are specifically used for:

[0453] The third variable is determined to be equal to the number of TBs that the PDSCH scheduling DCI is actually enabled or the number of TBs that are configured, as detected by the terminal during the second timing period.

[0454] Optionally, if the serving cell is not configured to allow dual codeword transmission, the actual number of TBs enabled or the configured number of TBs for each PDSCH scheduling DCI is equal to 1; or,

[0455] When the serving cell is configured to allow dual codeword transmission, the number of TBs configured for each PDSCH scheduling DCI is equal to 2, or the number of TBs actually enabled for each PDSCH scheduling DCI is any one of the following:

[0456] When the first TB is disabled, the number of TBs that are uniformly enabled by the DCI scheduler for each PDSCH is used.

[0457] When using the second TB de-enable method, the number of TBs actually enabled by each PDSCH scheduling DCI.

[0458] Optionally, the fifth determined sub-unit and / or the first determined sub-unit are specifically used for:

[0459] If, during the second timing period, the terminal is only allowed to detect a single PDSCH scheduling DCI for a single serving cell, the third variable is determined to be equal to the number of TBs actually enabled or the configured number of TBs for the single PDSCH scheduling DCI detected by the terminal; or,

[0460] If, within the second timeframe, the terminal is allowed to detect at least two PDSCH scheduling DCIs for a single serving cell, the third variable is determined to be equal to the sum of the actual number of TBs or the configured number of all PDSCH scheduling DCIs detected by the terminal.

[0461] Optionally, if the terminal detects the DCI scheduling PDSCH within the second timing period and configures application space domain binding, the fifth determining subunit and / or the first determining subunit are specifically used for:

[0462] The third variable is determined to be equal to the number of PDSCH scheduled DCIs detected by the terminal during the second timing period.

[0463] Optionally, the third determining subunit is specifically used for:

[0464] When the second subcodebook does not include the target HARQ-ACK, and the target HARQ-ACK includes the HARQ-ACK obtained by time-domain binding of the first HARQ-ACK, the terminal determines the second parameter according to the following formula:

[0465]

[0466] Wherein, the first HARQ-ACK is the HARQ-ACK corresponding to the DCI used to schedule at least two PDSCHs, n HARQ-ACK,second This represents the second parameter determined according to the third calculation rule corresponding to the second subcodebook;

[0467] This indicates the number of bits occupied by the downlink allocation index DAI.

[0468] This indicates the number of serving cells within the PUCCH cell group that are configured with Multi-PDSCH scheduling;

[0469] exist hour, This represents the value of the count DAI carried by the last first type DCI detected by the terminal for any serving cell within M PDCCH detection opportunities. The first type DCI includes DCIs used for scheduling more than one PDSCH.

[0470] exist hour, This represents the total DAI value carried by the last first type DCI detected by the terminal for any serving cell within M PDCCH detection opportunities;

[0471] When the terminal does not detect any of the first type of DCI for any serving cell within M PDCCH detection opportunities.

[0472] This represents the total number of the first type of DCI detected by the terminal in M ​​PDCCH detection opportunities for serving cell c;

[0473] Indicates traversal The service area received The maximum value;

[0474] For serving cell c, the maximum number of PDSCH receptions that can be scheduled for a single first-type DCI;

[0475] When application space binding is not configured The maximum number of codewords configured for DCI scheduling in serving cell c; when application spatial binding is configured.

[0476] If no space domain binding is configured, then This represents the total number of transport blocks actually scheduled by the UE for the first type of DCI within the PDCCH detection time m for the serving cell c; if spatial binding is configured, then... The total number of valid PDSCHs of the first type of DCI scheduling detected by the UE for the serving cell c within the PDCCH detection time m;

[0477] And / or,

[0478] If the second subcodebook includes the target HARQ-ACK, the terminal determines the second parameter according to the following formula:

[0479]

[0480] in, This indicates the number of multi-feedback cells within the PUCCH cell group. The multi-feedback cells belong to either the first type of cell or the second type of cell. The first type of cell is a serving cell that is configured with Multi-PDSCH scheduling but not with time-domain binding. The second type of cell is a serving cell that is configured with Multi-PDSCH scheduling and with time-domain binding and a number of binding groups greater than 1.

[0481] equal

[0482] For the first cell c, the corresponding first maximum value is based on calculate, The maximum number of PDSCH receptions that can be scheduled 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 that belongs to the first type of multiple feedback cell;

[0483] For the second cell c, the corresponding first maximum value is based on calculate, The number of binding groups configured for the second cell c; the second cell is Any one of the multiple feedback cells that belongs to the second type of multiple feedback cell;

[0484] For traversal The maximum value of the first maximum value corresponding to each of the multiple feedback cells.

[0485] The power control parameter determination device 300 provided in this application embodiment is capable of performing, for example... Figure 2 The various processes in the power control parameter determination method shown are all effective and can achieve the same beneficial results. To avoid repetition, they will not be described in detail here.

[0486] The power control parameter determination device 300 in this embodiment can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal, or other devices besides a terminal. For example, the terminal can include, but is not limited to, the type of terminal 11 listed above; other devices can be servers, network attached storage (NAS), etc., and this embodiment does not impose specific limitations.

[0487] Optional, such as Figure 4 As shown, this application embodiment also provides a communication device 400, including a processor 401 and a memory 402. The memory 402 stores a program or instructions that can run on the processor 401. For example, when the communication device 400 is a terminal, the program or instructions executed by the processor 401 implement the various steps of the above-described power control parameter determination method embodiment and achieve the same technical effect. When the communication device 400 is a network-side device, the program or instructions executed by the processor 401 implement the various steps of the above-described power control parameter determination method embodiment and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0488] This application embodiment also provides a terminal, including a processor and a communication interface. The processor is used to determine a first power control parameter based on target information related to the Multi-PDSCH scheduling when the terminal's serving cell is configured with Multi-Physical Downlink Shared Channel (PDSCH) scheduling. The first power control parameter includes the effective number of bits for Hybrid Automatic Repeat Request (HARQ) ACK and a transmission power for determining the Physical Uplink Control Channel (PUCCH) carrying the HARQ-ACK based on the first power control parameter. The communication interface is used to transmit the PUCCH to the network-side device according to the transmission power. This terminal embodiment corresponds to the above-described terminal-side method embodiment. All implementation processes and methods of the above method embodiments can be applied to this terminal embodiment and achieve the same technical effect. Specifically, Figure 5 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0489] The terminal 500 includes, but is not limited to, at least some of the following components: radio frequency unit 501, network module 502, audio output unit 503, input unit 504, sensor 505, display unit 506, user input unit 507, interface unit 508, memory 509, and processor 510.

[0490] Those skilled in the art will understand that the terminal 500 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 510 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. Figure 5 The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0491] It should be understood that, in this embodiment, the input unit 504 may include a graphics processing unit (GPU) 5041 and a microphone 5042. The GPU 5041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 506 may include a display panel 5061, which 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. The touch panel 5071 is also called a touch screen. The touch panel 5071 may include a touch detection device and a touch controller. Other input devices 5072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0492] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 501 can transmit it to the processor 510 for processing; in addition, the radio frequency unit 501 can send uplink data to the network-side device. Typically, the radio frequency unit 501 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0493] The memory 509 can be used to store software programs or instructions, as well as various data. The memory 509 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 509 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 509 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0494] Processor 510 may include one or more processing units; optionally, processor 510 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 510.

[0495] The processor 510 is configured to determine a first power control parameter based on target information related to the Multi-PDSCH scheduling when the serving cell of the terminal 500 is configured with Multi-Physical Downlink Shared Channel (PDSCH) scheduling. The first power control parameter includes the number of effective bits of Hybrid Automatic Repeat Request Response (HARQ-ACK).

[0496] Processor 510 is further configured to determine the transmit power of the physical uplink control channel PUCCH carrying the HARQ-ACK based on the first power control parameter;

[0497] Radio frequency unit 501 is used to send the PUCCH to the network-side device according to the transmission power.

[0498] Optionally, the target information includes at least one of the following: first configuration information for time-domain bound transmission, second configuration information for spatial-domain bound transmission, the codebook used by HARQ-ACK, and the sub-codebook used by HARQ-ACK.

[0499] Optionally, when the codebook used in the HARQ-ACK is a first type of codebook, the step of determining the first power control parameter based on the target information related to the Multi-PDSCH scheduling executed by the processor 510 includes:

[0500] Processor 510 determines at least one of the first variable and the second variable based on the target information;

[0501] The processor 510 determines the first power control parameter according to at least one of the first variable and the second variable, and in accordance with the first calculation rule corresponding to the first type codebook.

[0502] Optionally, when the HARQ-ACK is configured to transmit using time-domain binding but not spatial-domain binding, if the terminal receives the PDSCH at the first opportune moment, the processor 510's execution of determining the first variable based on the target information includes:

[0503] Processor 510 determines that the first variable is equal to the number of TBs corresponding to the target scheduling line;

[0504] The target scheduling line includes a scheduling line mapped to the first timing, or the target scheduling line includes a scheduling line determined based on the first PDSCH mapped to the first timing and the association relationship of the last time domain resource allocation record. The scheduling line includes: a row of the time domain resource allocation (TDRA) table in which the terminal is actually scheduled or configured.

[0505] Optionally, the number of target scheduling lines is M, and when M=0, the number of TBs corresponding to the target scheduling lines is 0; or,

[0506] When M > 0, the number of TBs corresponding to the target scheduling line is any one of the following:

[0507] The sum of the number of TBs opened in each of the M target scheduling lines;

[0508] The number of TBs opened for the M target scheduling lines;

[0509] The sum of the number of TBs configured for each of the M target scheduling lines;

[0510] The number of TBs configured for the M target scheduling lines.

[0511] Optionally, if the serving cell is not configured to allow dual-codeword transmission, the number of TBs enabled by the target scheduling line is equal to 1; or,

[0512] When the serving cell is configured to allow dual-codeword transmission, the number of TBs enabled by the target scheduling line is equal to any of the following:

[0513] When the first TB is disabled, the number of TBs that are uniformly enabled in the downlink control information (DCI) corresponding to the target scheduling line;

[0514] When the second TB de-enable method is used, the number of TBs actually enabled in the DCI corresponding to the target scheduling line.

[0515] Optionally, the number of TBs opened for the M target scheduling lines includes:

[0516] The maximum number of TBs opened for each of the M target scheduling lines;

[0517] The number of TBs to be enabled is determined based on the M target scheduling lines.

[0518] Optionally, if the serving cell is not configured to allow dual-codeword transmission, the number of TBs configured in the target scheduling line is equal to 1; or,

[0519] When the serving cell is configured to allow dual codeword transmission, the number of TBs configured for the target scheduling line is equal to 2.

[0520] Optionally, when it is required that the PDSCH corresponding to the last time-domain resource allocation record of any scheduling line is a valid PDSCH, the determination of the first variable being equal to the number of TBs corresponding to the target scheduling line performed by the processor 510 includes:

[0521] 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, then the processor 510 determines that the target TB number is equal to the TB number enabled by the first PDSCH or the configured TB number.

[0522] If the first PDSCH does not exist, or if the first PDSCH is not associated with or corresponds to the last time-domain resource allocation record of any scheduling line, then the processor 510 determines that the first variable is equal to 0.

[0523] Optionally, when the codebook used in the HARQ-ACK is a first type of codebook, and the first type of codebook is configured to transmit using time-domain binding and spatial-domain binding, if the terminal receives the PDSCH at the first opportune moment, the processor 510's execution of determining the first variable based on the target information includes:

[0524] Processor 510 determines that the first variable is equal to the number of target scheduling lines;

[0525] The target scheduling line includes a scheduling line mapped to the first timing, or the target scheduling line includes a scheduling line determined based on the first PDSCH mapped to the first timing and the association relationship of the last time domain resource allocation record. The scheduling line includes: a row of the TDRA table in which the terminal is actually scheduled or configured.

[0526] Optionally, when it is required that the PDSCH corresponding to the last time-domain resource allocation record of any scheduling line is a valid PDSCH, the determination of the number of target scheduling lines by the processor 510 includes any of the following:

[0527] 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, then the processor 510 determines that the number of the target scheduling lines is equal to 1.

[0528] If the first PDSCH does not exist, or if the first PDSCH is not associated with or corresponds to the last time-domain resource allocation record of any scheduling line, then the processor 510 determines that the number of the target scheduling lines is equal to 0.

[0529] Optionally, if the codebook used in the HARQ-ACK is a first-type codebook, the step of determining the second variable based on the target information executed by the processor 510 includes:

[0530] Processor 510 determines that the second variable is equal to 0.

[0531] Optionally, when the codebook used in the HARQ-ACK is a second type of codebook, the step of determining the first power control parameter based on the target information related to the Multi-PDSCH scheduling executed by the processor 510 includes:

[0532] When no time-domain binding is configured in each cell of the PUCCH cell group, the processor 510 determines the first power control parameter based on the first subcodebook and the second subcodebook. The PUCCH cell group includes the serving cell of the terminal. The first subcodebook corresponds to a single HARQ-ACK granularity, and the second subcodebook corresponds to multiple HARQ-ACK granularities.

[0533] When all cells configured with Multi-PDSCH scheduling in the PUCCH cell group are configured with time-domain binding and the number of configured binding groups is equal to 1, the processor 510 determines the first power control parameter according to the first subcodebook.

[0534] If at least one of the cells configured with Multi-PDSCH scheduling in the PUCCH cell group is configured with time-domain binding and the number of configured binding groups is greater than 1, the processor 510 determines the first power control parameter based on the first subcodebook and the second subcodebook.

[0535] Optionally, the process of determining the first power control parameter based on the first subcodebook and the second subcodebook, executed by the processor 510, includes:

[0536] The processor 510 determines the first parameter according to the second calculation rule corresponding to the first sub-codebook, and determines the second parameter according to the third calculation rule corresponding to the second sub-codebook;

[0537] The processor 510 determines that the first power control parameter is equal to the sum of the first parameter and the second parameter.

[0538] Optionally, the process of determining the first power control parameter based on the first subcodebook, executed by the processor 510, includes:

[0539] Processor 510 determines the third variable based on the target information;

[0540] The processor 510 determines the first power control parameter based on the second calculation rule and the third variable.

[0541] Optionally, the step of determining the first parameter according to the second calculation rule corresponding to the first subcodebook, executed by the processor 510, includes:

[0542] Processor 510 determines the third variable based on the target information;

[0543] Processor 510 determines the first parameter based on the second calculation rule and the third variable;

[0544] And / or,

[0545] The process of determining the second parameter according to the third calculation rule corresponding to the second subcodebook, executed by processor 510, includes:

[0546] Processor 510 determines the fourth variable based on the target information;

[0547] The processor 510 determines the second parameter based on the third calculation rule and the fourth variable.

[0548] Optionally, if terminal 500 detects the DCI of scheduling PDSCH within the second timing period and application space domain binding is not configured, the processor 510's execution of determining the third variable based on the target information includes:

[0549] The processor 510 determines that the third variable is equal to the number of TBs actually enabled or configured by the PDSCH scheduling DCI detected by the terminal during the second timing period.

[0550] Optionally, if the serving cell is not configured to allow dual codeword transmission, the actual number of TBs enabled or the configured number of TBs for each PDSCH scheduling DCI is equal to 1; or,

[0551] When the serving cell is configured to allow dual codeword transmission, the number of TBs configured for each PDSCH scheduling DCI is equal to 2, or the number of TBs actually enabled for each PDSCH scheduling DCI is any one of the following:

[0552] When the first TB is disabled, the number of TBs that are uniformly enabled by the DCI scheduler for each PDSCH is used.

[0553] When using the second TB de-enable method, the number of TBs actually enabled by each PDSCH scheduling DCI.

[0554] Optionally, the process of determining the third variable based on the target information, executed by the processor 510, includes:

[0555] If, during the second timing period, the terminal is only allowed to detect a single PDSCH scheduling DCI for a single serving cell, the processor 510 determines that the third variable is equal to the number of TBs actually enabled or the configured number of TBs for the single PDSCH scheduling DCI detected by the terminal; or,

[0556] If, during the second timing period, the terminal is allowed to detect at least two PDSCH scheduling DCIs for a single serving cell, the processor 510 determines that the third variable is equal to the sum of the actual number of TBs or the configured number of all PDSCH scheduling DCIs detected by the terminal.

[0557] Optionally, if terminal 500 detects the DCI of scheduling PDSCH within the second timing period and configures application space domain binding, the processor 510's execution of determining the third variable based on the target information includes:

[0558] The processor 510 determines that the third variable is equal to the number of PDSCH scheduled DCIs detected by the terminal during the second timing period.

[0559] Optionally, the process of determining the second parameter according to the third calculation rule corresponding to the second subcodebook, executed by the processor 510, includes:

[0560] When the second subcodebook does not include the target HARQ-ACK, and the target HARQ-ACK includes the HARQ-ACK obtained by time-domain binding of the first HARQ-ACK, the processor 510 determines the second parameter according to the following formula:

[0561]

[0562] Wherein, the first HARQ-ACK is the HARQ-ACK corresponding to the DCI used to schedule at least two PDSCHs, n HARQ-ACK,second This represents the second parameter determined according to the third calculation rule corresponding to the second subcodebook;

[0563] This indicates the number of bits occupied by the downlink allocation index DAI.

[0564] This indicates the number of serving cells within the PUCCH cell group that are configured with Multi-PDSCH scheduling;

[0565] exist hour, This represents the value of the count DAI carried by the last first type DCI detected by the terminal for any serving cell within M PDCCH detection opportunities. The first type DCI includes DCIs used for scheduling more than one PDSCH.

[0566] exist hour, This represents the total DAI value carried by the last first type DCI detected by the terminal for any serving cell within M PDCCH detection opportunities;

[0567] When the terminal does not detect any of the first type of DCI for any serving cell within M PDCCH detection opportunities.

[0568] This represents the total number of the first type of DCI detected by the terminal in M ​​PDCCH detection opportunities for serving cell c;

[0569] Indicates traversal The service area received The maximum value;

[0570] For serving cell c, the maximum number of PDSCH receptions that can be scheduled for a single first-type DCI;

[0571] When application space binding is not configured The maximum number of codewords configured for DCI scheduling in serving cell c; when application spatial binding is configured.

[0572] If no space domain binding is configured, then This represents the total number of transport blocks actually scheduled by the UE for the first type of DCI within the PDCCH detection time m for the serving cell c; if spatial binding is configured, then... The total number of valid PDSCHs of the first type of DCI scheduling detected by the UE for the serving cell c within the PDCCH detection time m;

[0573] And / or,

[0574] If the second subcodebook includes the target HARQ-ACK, the processor 510 determines the second parameter according to the following formula:

[0575]

[0576] in, This indicates the number of multi-feedback cells within the PUCCH cell group. The multi-feedback cells belong to either the first type of cell or the second type of cell. The first type of cell is a serving cell that is configured with Multi-PDSCH scheduling but not with time-domain binding. The second type of cell is a serving cell that is configured with Multi-PDSCH scheduling and with time-domain binding and a number of binding groups greater than 1.

[0577] equal

[0578] For the first cell c, the corresponding first maximum value is based on calculate, The maximum number of PDSCH receptions that can be scheduled 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 that belongs to the first type of multiple feedback cell;

[0579] For the second cell c, the corresponding first maximum value is based on calculate, The number of binding groups configured for the second cell c; the second cell is Any one of the multiple feedback cells that belongs to the second type of multiple feedback cell;

[0580] For traversal The maximum value of the first maximum value corresponding to each of the multiple feedback cells.

[0581] The terminal 500 provided in this embodiment of the application can achieve the following: Figure 3 The various processes executed by the power control parameter determination device 300 shown are all capable of achieving the same beneficial effects, and will not be described again here to avoid repetition.

[0582] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described power control parameter determination method embodiment and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0583] The processor is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0584] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described power control parameter determination method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0585] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0586] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described power control parameter determination method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0587] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0588] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0589] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method for determining power control parameters, characterized in that, include: When the serving cell of the terminal is configured with Multi-PDSCH scheduling, the terminal determines a first power control parameter based on target information related to the Multi-PDSCH scheduling. The first power control parameter includes the effective number of bits of Hybrid Automatic Repeat Request Response (HARQ-ACK), and the target information includes the codebook used by the HARQ-ACK. The terminal determines the transmission power of the physical uplink control channel PUCCH carrying the HARQ-ACK based on the first power control parameter. The terminal sends the PUCCH to the network-side device according to the transmission power; The Multi-PDSCH scheduling refers to the ability of a single downlink control information (DCI) to schedule the transmission of multiple physical downlink shared channel (PDSCH) on the same carrier at one time.

2. The method according to claim 1, characterized in that, The target information also includes at least one of the following: first configuration information for time-domain binding transmission, second configuration information for spatial-domain binding transmission, and the subcodebook used by the HARQ-ACK.

3. The method according to claim 1 or 2, characterized in that, When the codebook used in the HARQ-ACK is of the first type, the terminal determines the first power control parameter based on the target information related to the Multi-PDSCH scheduling, including: The terminal determines at least one of the first variable and the second variable based on the target information; The terminal determines the first power control parameter according to at least one of the first variable and the second variable, and in accordance with the first calculation rule corresponding to the first type of codebook. The terminal determines the first power control parameter according to at least one of the first variable and the second variable, and in accordance with the first calculation rule corresponding to the first type of codebook, including calculating the first power control parameter according to the following formula. : ； For the first variable, For the second variable, This indicates the number of serving cells within the PUCCH cell group that are configured for PDSCH transmission. This indicates the number of PDSCH transmission opportunities for serving cell c.

4. The method according to claim 3, characterized in that, When the HARQ-ACK is configured to transmit using time-domain binding but not spatial-domain binding, if the terminal receives the PDSCH at the first opportune moment, the terminal determines the first variable based on the target information, including: The terminal determines that the first variable is equal to the number of transport blocks (TB) corresponding to the target scheduling line; The target scheduling line includes a scheduling line mapped to the first timing, or the target scheduling line includes a scheduling line determined based on the first PDSCH mapped to the first timing and the association relationship of the last time domain resource allocation record. The scheduling line includes: a row of the time domain resource allocation (TDRA) table in which the terminal is actually scheduled or configured.

5. The method according to claim 4, characterized in that, The number of target scheduling lines is M. When M=0, the number of TBs corresponding to the target scheduling lines is 0. or, When M > 0, the number of TBs corresponding to the target scheduling line is any one of the following: The sum of the number of TBs opened in each of the M target scheduling lines; The number of TBs opened for the M target scheduling lines; The sum of the number of TBs configured for each of the M target scheduling lines; The number of TBs configured for the M target scheduling lines.

6. The method according to claim 5, characterized in that, If the serving cell is not configured to allow dual-codeword transmission, the number of TBs enabled by the target scheduling line is equal to 1; or, When the serving cell is configured to allow dual-codeword transmission, the number of TBs enabled by the target scheduling line is equal to any of the following: When the first TB is disabled, the number of TBs that are uniformly enabled in the downlink control information (DCI) corresponding to the target scheduling line; When the second TB de-enable method is used, the number of TBs actually enabled in the DCI corresponding to the target scheduling line.

7. The method according to claim 5, characterized in that, The number of TBs opened for the M target scheduling lines includes: The maximum number of TBs opened for each of the M target scheduling lines; The number of TBs to be enabled is determined based on the M target scheduling lines.

8. The method according to claim 5, characterized in that, If the serving cell is not configured to allow dual-codeword transmission, the number of TBs configured in the target scheduling line is equal to 1; or, When the serving cell is configured to allow dual codeword transmission, the number of TBs configured for the target scheduling line is equal to 2.

9. The method according to any one of claims 4 to 8, characterized in that, When requiring the PDSCH corresponding to the last time-domain resource allocation record of any scheduling line to be a valid PDSCH, the terminal determines that the first variable is equal to the TB number corresponding to the target scheduling line, 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, then the terminal determines that the number of TBs corresponding to the target scheduling line is equal to the number of TBs enabled by the first PDSCH or the number of TBs configured. If the first PDSCH does not exist, or if the first PDSCH is not associated with or corresponds to the last time-domain resource allocation record of any scheduling line, then the terminal determines that the first variable is equal to 0.

10. The method according to claim 3, characterized in that, When the codebook used in the HARQ-ACK is a first type of codebook, and the first type of codebook is configured to transmit using time-domain binding and spatial-domain binding, if the terminal receives the PDSCH at the first opportune moment, the terminal determines the first variable based on the target information, including: The terminal determines that the first variable is equal to the number of target scheduling lines; The target scheduling line includes a scheduling line mapped to the first timing, or the target scheduling line includes a scheduling line determined based on the first PDSCH mapped to the first timing and the association relationship of the last time domain resource allocation record. The scheduling line includes: a row of the TDRA table in which the terminal is actually scheduled or configured.

11. The method according to claim 10, characterized in that, When requiring the PDSCH corresponding to the last time-domain resource allocation record of any scheduling line to be a valid PDSCH, the terminal determines that the first variable is equal to the number of target scheduling lines, 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 line, then the terminal determines that the number of the target scheduling lines is equal to 1. If the first PDSCH does not exist, or if the first PDSCH is not associated with or corresponds to the last time-domain resource allocation record of any scheduling line, then the terminal determines that the number of the target scheduling lines is equal to 0.

12. The method according to claim 3, characterized in that, When the codebook used in the HARQ-ACK is a first-type codebook, the terminal determines the second variable based on the target information, including: The terminal determines that the second variable is equal to 0.

13. The method according to claim 1 or 2, characterized in that, When the codebook used in the HARQ-ACK is the second type of codebook, the terminal determines the first power control parameter based on the target information related to the Multi-PDSCH scheduling, including: When no time-domain binding is configured in each cell of the PUCCH cell group, the terminal determines the first power control parameter based on the first subcodebook and the second subcodebook. The PUCCH cell group includes the serving cell of the terminal. The first subcodebook corresponds to a single HARQ-ACK granularity, and the second subcodebook corresponds to multiple HARQ-ACK granularities. When all cells configured with Multi-PDSCH scheduling in the PUCCH cell group are configured with time-domain binding and the number of configured binding groups is equal to 1, the terminal determines the first power control parameter based on the first subcodebook. If at least one of the cells configured with Multi-PDSCH scheduling in the PUCCH cell group is configured with time-domain binding and the number of configured binding groups is greater than 1, the terminal determines the first power control parameter based on the first subcodebook and the second subcodebook.

14. The method according to claim 13, characterized in that, The terminal determines the first power control parameter based on the first sub-codebook and the second sub-codebook, including: The terminal determines the first parameter according to the second calculation rule corresponding to the first sub-codebook, and determines the second parameter according to the third calculation rule corresponding to the second sub-codebook; The terminal determines that the first power control parameter is equal to the sum of the first parameter and the second parameter; The second calculation rule obtains the first parameter using the following formula. : ； This indicates the number of serving cells configured with PDSCH transmission within the PUCCH cell group; At the terminal If no DCI is detected during any of the PDCCH detection opportunities, ; exist In this case, For the terminal in The value of the downlink allocation index (DAI) carried by the last DCI detected within a PDCCH detection period; exist In the case of, In a PDCCH detection period, for the last PDCCH detection period in which the terminal detects at least one DCI, if the terminal does not detect any DCI carrying the total DAI within this PDCCH detection period, then This is the value of the count DAI carried by the last DCI detected by the terminal within this PDCCH detection period; if the terminal detects at least one DCI carrying the total DAI within this PDCCH detection period, then... The value of the total DAI carried in at least one DCI carrying the total DAI detected by the terminal during this PDCCH detection period; For the terminal targeting the serving cell ,exist The total number of DCIs detected in each PDCCH detection period; = , This indicates the number of bits occupied by the count DAI; When the maximum number of codewords (maxNrofCodeWordsScheduledByDCI) for DCI scheduling is configured to be 2 for any serving cell, and spatial binding harq-ACK-SpatialBundlingPUCCH is not configured, ;otherwise, ; These are variables determined based on the target information; For the terminal targeting the serving cell The terminal needs to report the number of semi-persistent scheduling (SPS) PDSCH receptions corresponding to HARQ-ACK information within the PUCCH, and the terminal needs to report the number of HARQ-ACK responses within the PUCCH. The PDSCH scheduled within each PDCCH detection time receives the corresponding HARQ-ACK information; The terminal determines the second parameter according to the third calculation rule corresponding to the second sub-codebook, including: When the second subcodebook does not include the target HARQ-ACK, and the target HARQ-ACK includes the HARQ-ACK obtained by time-domain binding of the first HARQ-ACK, the terminal determines the second parameter according to the following formula: ； The first HARQ-ACK is the HARQ-ACK corresponding to the DCI used to schedule at least two PDSCHs. This represents the second parameter determined according to the third calculation rule corresponding to the second subcodebook; = , This indicates the number of bits occupied by the downlink allocation index DAI. This indicates the number of serving cells within the PUCCH cell group that are configured with Multi-PDSCH scheduling; exist hour, This represents the value of the count DAI carried by the last first type DCI detected by the terminal for any serving cell within M PDCCH detection opportunities. The first type DCI includes DCIs used for scheduling more than one PDSCH. exist hour, This represents the total DAI value carried by the last first type DCI detected by the terminal for any serving cell within M PDCCH detection opportunities; When the terminal does not detect any of the first type of DCI for any serving cell within M PDCCH detection opportunities. ; This indicates that the terminal is targeting the serving cell. ,exist The total number of Type I DCIs detected in each PDCCH detection opportunity; Indicates traversal The service area received The maximum value; For the service community The maximum number of PDSCH receptions that can be scheduled for a single first-type DCI; When application space binding is not configured To serve the community The maximum number of codewords configured for DCI scheduling; when configuring application space domain binding, ; When application space binding is not configured For the terminal during PDCCH detection Internally targeting the service community The total number of transport blocks actually scheduled by the first type of DCI detected; when application space domain binding is configured, For the terminal during PDCCH detection Internally targeting the service community The total number of valid PDSCHs detected for the first type of DCI scheduling; And / or, If the second subcodebook includes the target HARQ-ACK, the terminal determines the second parameter according to the following formula: ； in, This indicates the number of multi-feedback cells within the PUCCH cell group. The multi-feedback cells belong to either the first type of cell or the second type of cell. The first type of cell is a serving cell that is configured with Multi-PDSCH scheduling but not with time-domain binding. The second type of cell is a serving cell that is configured with Multi-PDSCH scheduling and with time-domain binding and a number of binding groups greater than 1. equal ; For the first community The corresponding first maximum value is based on calculate, For the first cell The maximum number of PDSCH receptions that can be scheduled for a single first-type DCI; the first cell is Any one of the multiple feedback cells that belongs to the first type of multiple feedback cell; For the second community The corresponding first maximum value is based on calculate, For the second cell The number of configured binding groups; the second cell is Any one of the multiple feedback cells that belongs to the second type of multiple feedback cell; For traversal The maximum value of the first maximum value corresponding to each of the multiple feedback cells is obtained; When application space binding is not configured For the terminal during PDCCH detection Internally targeting the service community The detected PDSCH scheduling DCI with more than one PDSCH is the total number of binding groups for each TB's actual scheduling; wherein, a single PDSCH scheduling DCI for the target TB's actual scheduling binding group satisfies: the binding group contains at least one valid PDSCH, and at least one valid PDSCH enables the target TB; in the serving cell When dual-codeword transmission is configured, the target TB is either the first TB or the second TB; in the serving cell Without dual-codeword transmission configured, the target TB is the first TB; When configuring application space binding For the terminal during PDCCH detection Internally targeting the service community The total number of binding groups of PDSCH scheduling DCI actual scheduling that are detected to have more than one PDSCH; wherein, the binding group of a single PDSCH scheduling DCI actual scheduling satisfies that: the binding group contains at least one valid PDSCH.

15. The method according to claim 13, characterized in that, The terminal determines the first power control parameter based on the first sub-codebook, including: The terminal determines a third variable based on the target information; The terminal determines the first power control parameter based on the second calculation rule and the third variable; The second calculation rule obtains the first power control parameter using the following formula. : ； This indicates the number of serving cells configured with PDSCH transmission within the PUCCH cell group; At the terminal If no DCI is detected during any of the PDCCH detection opportunities, ; exist In this case, For the terminal in The value of the downlink allocation index (DAI) carried by the last DCI detected within a PDCCH detection period; exist In the case of, In a PDCCH detection period, for the last PDCCH detection period in which the terminal detects at least one DCI, if the terminal does not detect any DCI carrying the total DAI within this PDCCH detection period, then This is the value of the count DAI carried by the last DCI detected by the terminal within this PDCCH detection period; if the terminal detects at least one DCI carrying the total DAI within this PDCCH detection period, then... The value of the total DAI carried in at least one DCI carrying the total DAI detected by the terminal during this PDCCH detection period; For the terminal targeting the serving cell ,exist The total number of DCIs detected in each PDCCH detection period; = , This indicates the number of bits occupied by the count DAI; When the maximum number of codewords (maxNrofCodeWordsScheduledByDCI) for DCI scheduling is configured to be 2 for any serving cell, and spatial binding harq-ACK-SpatialBundlingPUCCH is not configured, ;otherwise, ; For the third variable; For the terminal targeting the serving cell The terminal needs to report the number of semi-persistent scheduling (SPS) PDSCH receptions corresponding to HARQ-ACK information within the PUCCH, and the terminal needs to report the number of HARQ-ACK responses within the PUCCH. The PDSCH scheduled within each PDCCH detection time receives the corresponding HARQ-ACK information.

16. The method according to claim 15, characterized in that, If the terminal detects the DCI scheduling PDSCH within the second timing period and has not configured application space domain binding, the terminal determines a third variable based on the target information, including: The terminal determines that the third variable is equal to the number of TBs actually enabled or the configured number of TBs detected by the terminal during the second timing period for PDSCH scheduling DCI.

17. The method according to claim 16, characterized in that, If the serving cell is not configured to allow dual codeword transmission, the actual number of TBs enabled or the configured number of TBs for each PDSCH scheduling DCI is equal to 1; or, When the serving cell is configured to allow dual codeword transmission, the number of TBs configured for each PDSCH scheduling DCI is equal to 2, or the number of TBs actually enabled for each PDSCH scheduling DCI is any one of the following: When the first TB is disabled, the number of TBs that are uniformly enabled by the DCI scheduler for each PDSCH is used. When using the second TB de-enable method, the number of TBs actually enabled by each PDSCH scheduling DCI.

18. The method according to claim 15, characterized in that, The terminal determines a third variable based on the target information, including: If, during the second timing period, the terminal is only allowed to detect a single PDSCH scheduling DCI for a single serving cell, the terminal determines that the third variable is equal to the number of TBs actually enabled or the configured number of TBs for the single PDSCH scheduling DCI detected by the terminal; or, If, within the second timeframe, the terminal is allowed to detect at least two PDSCH scheduling DCIs for a single serving cell, the terminal determines that the third variable is equal to the sum of the actual number of TBs or the configured number of all PDSCH scheduling DCIs detected by the terminal.

19. The method according to claim 15, characterized in that, If the terminal detects the DCI scheduling PDSCH within the second timing period and has configured application space domain binding, the terminal determines a third variable based on the target information, including: The terminal determines that the third variable is equal to the number of PDSCH scheduled DCIs detected by the terminal during the second timing period.

20. A power control parameter determination device, characterized in that, Applied to a terminal, the device includes: The first determining module is configured to determine a first power control parameter based on target information related to the Multi-PDSCH scheduling when the serving cell of the terminal is configured with Multi-PDSCH scheduling. The first power control parameter includes the effective number of bits of Hybrid Automatic Repeat Request Response (HARQ-ACK), and the target information includes the codebook used by the HARQ-ACK. The second determining module is used to determine the transmission power of the physical uplink control channel PUCCH carrying the HARQ-ACK based on the first power control parameters. The transmitting module is used to transmit the PUCCH to the network-side device according to the transmitting power; The Multi-PDSCH scheduling refers to the ability of a single downlink control information (DCI) to schedule the transmission of multiple physical downlink shared channel (PDSCH) on the same carrier at one time.

21. The apparatus according to claim 20, characterized in that, The target information also includes at least one of the following: first configuration information for time-domain binding transmission, second configuration information for spatial-domain binding transmission, and the subcodebook used by the HARQ-ACK.

22. The apparatus according to claim 20 or 21, characterized in that, When the codebook used in the HARQ-ACK is a first type of codebook, the first determining module includes: The first determining unit is configured to determine at least one of the first variable and the second variable based on the target information; The second determining unit is configured to determine the first power control parameter according to at least one of the first variable and the second variable, and according to the first calculation rule corresponding to the first type codebook. The terminal determines the first power control parameter according to at least one of the first variable and the second variable, and in accordance with the first calculation rule corresponding to the first type of codebook, including calculating the first power control parameter according to the following formula. : ； For the first variable, For the second variable, This indicates the number of serving cells within the PUCCH cell group that are configured for PDSCH transmission. This indicates the number of PDSCH transmission opportunities for serving cell c.

23. The apparatus according to claim 22, characterized in that, When the HARQ-ACK is configured to transmit using time-domain binding but not spatial-domain binding, if the terminal receives the PDSCH at the first opportune moment, the first determining unit is specifically used for: Determine that the first variable is equal to the number of TBs corresponding to the target scheduling line; The target scheduling line includes a scheduling line mapped to the first timing, or the target scheduling line includes a scheduling line determined based on the first PDSCH mapped to the first timing and the association relationship of the last time domain resource allocation record. The scheduling line includes: a row of the time domain resource allocation (TDRA) table in which the terminal is actually scheduled or configured.

24. The apparatus according to claim 23, characterized in that, The number of target scheduling lines is M. When M=0, the number of TBs corresponding to the target scheduling lines is 0. or, When M > 0, the number of TBs corresponding to the target scheduling line is any one of the following: The sum of the number of TBs opened in each of the M target scheduling lines; The number of TBs opened for the M target scheduling lines; The sum of the number of TBs configured for each of the M target scheduling lines; The number of TBs configured for the M target scheduling lines.

25. The apparatus according to claim 24, characterized in that, If the serving cell is not configured to allow dual-codeword transmission, the number of TBs enabled by the target scheduling line is equal to 1; or, When the serving cell is configured to allow dual-codeword transmission, the number of TBs enabled by the target scheduling line is equal to any of the following: When the first TB is disabled, the number of TBs that are uniformly enabled in the downlink control information (DCI) corresponding to the target scheduling line; When the second TB de-enable method is used, the number of TBs actually enabled in the DCI corresponding to the target scheduling line.

26. The apparatus according to claim 24, characterized in that, The number of TBs opened for the M target scheduling lines includes: The maximum number of TBs opened for each of the M target scheduling lines; The number of TBs to be enabled is determined based on the M target scheduling lines.

27. The apparatus according to claim 24, characterized in that, If the serving cell is not configured to allow dual-codeword transmission, the number of TBs configured in the target scheduling line is equal to 1; or, When the serving cell is configured to allow dual codeword transmission, the number of TBs configured for the target scheduling line is equal to 2.

28. The apparatus according to any one of claims 23 to 27, characterized in that, When it is required that the PDSCH corresponding to the last time-domain resource allocation record of any scheduling line is a valid PDSCH, the first determining unit includes: The first determining subunit is configured to determine, 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, that the number of TBs corresponding to the target scheduling line is equal to the number of TBs enabled by the first PDSCH or the number of TBs configured. The second determining subunit is configured to determine that the first variable is equal to 0 if the first PDSCH does not exist, or if the first PDSCH is not associated with or corresponds to the last time-domain resource allocation record of any scheduling line.

29. The apparatus according to claim 22, characterized in that, When the codebook used in the HARQ-ACK is a first type of codebook, and the first type of codebook is configured to transmit using time-domain binding and spatial-domain binding, if the terminal receives the PDSCH at the first opportune moment, then the first determining unit is specifically used for: Determine that the first variable equals the number of target scheduling lines; The target scheduling line includes a scheduling line mapped to the first timing, or the target scheduling line includes a scheduling line determined based on the first PDSCH mapped to the first timing and the association relationship of the last time domain resource allocation record. The scheduling line includes: a row of the TDRA table in which the terminal is actually scheduled or configured.

30. The apparatus according to claim 29, characterized in that, When it is required that the PDSCH corresponding to the last time-domain resource allocation record of any scheduling line is a valid PDSCH, the first determining unit is specifically used to perform any 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 line, then the number of the target scheduling lines is determined to be equal to 1. If the first PDSCH does not exist, or if the first PDSCH is not associated with or corresponds to the last time-domain resource allocation record of any scheduling line, then the number of target scheduling lines is determined to be equal to 0.

31. The apparatus according to claim 22, characterized in that, When the codebook used in the HARQ-ACK is a first type of codebook, the first determining unit is further configured to: Determine that the second variable equals 0.

32. The apparatus according to claim 20 or 21, characterized in that, When the codebook used in the HARQ-ACK is a second type of codebook, the first determining module includes: The third determining unit is used to determine the first power control parameter based on the first subcodebook and the second subcodebook when no time-domain binding is configured in each cell of the PUCCH cell group. The PUCCH cell group includes the serving cell of the terminal. The first subcodebook corresponds to a single HARQ-ACK granularity, and the second subcodebook corresponds to multiple HARQ-ACK granularities. The fourth determining unit is used to determine the first power control parameter based on the first subcodebook when all cells configured with Multi-PDSCH scheduling in the PUCCH cell group are configured with time-domain binding and the number of configured binding groups is equal to 1. The fifth determining unit is configured to determine the first power control parameter based on the first subcodebook and the second subcodebook when at least one of the cells configured with Multi-PDSCH scheduling in the PUCCH cell group is configured with time-domain binding and the number of configured binding groups is greater than 1.

33. The apparatus according to claim 32, characterized in that, The third determining unit and / or the fifth determining unit include: The third determining subunit is used to determine the first parameter according to the second calculation rule corresponding to the first subcodebook, and to determine the second parameter according to the third calculation rule corresponding to the second subcodebook. The fourth determining subunit is used to determine that the first power control parameter is equal to the sum of the first parameter and the second parameter; The second calculation rule obtains the first parameter using the following formula. : ； This indicates the number of serving cells configured with PDSCH transmission within the PUCCH cell group; At the terminal If no DCI is detected during any of the PDCCH detection opportunities, ; exist In this case, For the terminal in The value of the downlink allocation index (DAI) carried by the last DCI detected within a PDCCH detection period; exist In the case of, In a PDCCH detection period, for the last PDCCH detection period in which the terminal detects at least one DCI, if the terminal does not detect any DCI carrying the total DAI within this PDCCH detection period, then This is the value of the count DAI carried by the last DCI detected by the terminal within this PDCCH detection period; if the terminal detects at least one DCI carrying the total DAI within this PDCCH detection period, then... The value of the total DAI carried in at least one DCI carrying the total DAI detected by the terminal during this PDCCH detection period; For the terminal targeting the serving cell ,exist The total number of DCIs detected in each PDCCH detection period; = , This indicates the number of bits occupied by the count DAI; When the maximum number of codewords (maxNrofCodeWordsScheduledByDCI) for DCI scheduling is configured to be 2 for any serving cell, and spatial binding harq-ACK-SpatialBundlingPUCCH is not configured, ;otherwise, ; These are variables determined based on the target information; For the terminal targeting the serving cell The terminal needs to report the number of semi-persistent scheduling (SPS) PDSCH receptions corresponding to HARQ-ACK information within the PUCCH, and the terminal also needs to report the number of HARQ-ACKs received within this PUCCH. The PDSCH scheduled within each PDCCH detection time receives the corresponding HARQ-ACK information; The terminal determines the second parameter according to the third calculation rule corresponding to the second sub-codebook, including: When the second subcodebook does not include the target HARQ-ACK, and the target HARQ-ACK includes the HARQ-ACK obtained by time-domain binding of the first HARQ-ACK, the terminal determines the second parameter according to the following formula: ； The first HARQ-ACK is the HARQ-ACK corresponding to the DCI used to schedule at least two PDSCHs. This represents the second parameter determined according to the third calculation rule corresponding to the second subcodebook; = , This indicates the number of bits occupied by the downlink allocation index DAI. This indicates the number of serving cells within the PUCCH cell group that are configured with Multi-PDSCH scheduling; exist hour, This represents the value of the count DAI carried by the last first type DCI detected by the terminal for any serving cell within M PDCCH detection opportunities. The first type DCI includes DCIs used for scheduling more than one PDSCH. exist hour, This represents the total DAI value carried by the last first type DCI detected by the terminal for any serving cell within M PDCCH detection opportunities; When the terminal does not detect any of the first type of DCI for any serving cell within M PDCCH detection opportunities. ; This indicates that the terminal is targeting the serving cell. ,exist The total number of Type I DCIs detected in each PDCCH detection opportunity; Indicates traversal The service area received The maximum value; For the service community The maximum number of PDSCH receptions that can be scheduled for a single first-type DCI; When application space binding is not configured To serve the community The maximum number of codewords configured for DCI scheduling; when configuring application space domain binding, ; When application space binding is not configured For the terminal during PDCCH detection Internally targeting the service community The total number of transport blocks actually scheduled by the first type of DCI detected; when application space domain binding is configured, For the terminal during PDCCH detection Internally targeting the service community The total number of valid PDSCHs detected for the first type of DCI scheduling; And / or, If the second subcodebook includes the target HARQ-ACK, the terminal determines the second parameter according to the following formula: ； in, This indicates the number of multi-feedback cells within the PUCCH cell group. The multi-feedback cells belong to either the first type of cell or the second type of cell. The first type of cell is a serving cell that is configured with Multi-PDSCH scheduling but not with time-domain binding. The second type of cell is a serving cell that is configured with Multi-PDSCH scheduling and with time-domain binding and a number of binding groups greater than 1. equal ; For the first community The corresponding first maximum value is based on calculate, For the first cell The maximum number of PDSCH receptions that can be scheduled for a single first-type DCI; the first cell is Any one of the multiple feedback cells that belongs to the first type of multiple feedback cell; For the second community The corresponding first maximum value is based on calculate, For the second cell The number of configured binding groups; the second cell is Any one of the multiple feedback cells that belongs to the second type of multiple feedback cell; For traversal The maximum value of the first maximum value corresponding to each of the multiple feedback cells is obtained; When application space binding is not configured For the terminal during PDCCH detection Internally targeting the service community The detected PDSCH scheduling DCI with more than one PDSCH is the total number of binding groups for each TB's actual scheduling; wherein, a single PDSCH scheduling DCI for the target TB's actual scheduling binding group satisfies: the binding group contains at least one valid PDSCH, and at least one valid PDSCH enables the target TB; in the serving cell When dual-codeword transmission is configured, the target TB is either the first TB or the second TB; in the serving cell Without dual-codeword transmission configured, the target TB is the first TB; When configuring application space binding For the terminal during PDCCH detection Internally targeting the service community The total number of binding groups of PDSCH scheduling DCI actual scheduling that are detected to have more than one PDSCH; wherein, the binding group of a single PDSCH scheduling DCI actual scheduling satisfies that: the binding group contains at least one valid PDSCH.

34. The apparatus according to claim 32, characterized in that, The fourth determining unit includes: The fifth determining subunit is used to determine the third variable based on the target information; The sixth determining subunit is used to determine the first power control parameter based on the second calculation rule and the third variable; The second calculation rule obtains the first power control parameter using the following formula. : ； This indicates the number of serving cells configured with PDSCH transmission within the PUCCH cell group; At the terminal If no DCI is detected during any of the PDCCH detection opportunities, ; exist In this case, For the terminal in The value of the downlink allocation index (DAI) carried by the last DCI detected within a PDCCH detection period; exist In the case of, In a PDCCH detection period, for the last PDCCH detection period in which the terminal detects at least one DCI, if the terminal does not detect any DCI carrying the total DAI within this PDCCH detection period, then This is the value of the count DAI carried by the last DCI detected by the terminal within this PDCCH detection period; if the terminal detects at least one DCI carrying the total DAI within this PDCCH detection period, then... The value of the total DAI carried in at least one DCI carrying the total DAI detected by the terminal during this PDCCH detection period; For the terminal targeting the serving cell ,exist The total number of DCIs detected in each PDCCH detection period; = , This indicates the number of bits occupied by the count DAI; When the maximum number of codewords (maxNrofCodeWordsScheduledByDCI) for DCI scheduling is configured to be 2 for any serving cell, and spatial binding harq-ACK-SpatialBundlingPUCCH is not configured, ;otherwise, ; For the third variable; For the terminal targeting the serving cell The terminal needs to report the number of semi-persistent scheduling (SPS) PDSCH receptions corresponding to HARQ-ACK information within the PUCCH, and the terminal also needs to report the number of HARQ-ACKs received within this PUCCH. The PDSCH scheduled within each PDCCH detection time receives the corresponding HARQ-ACK information.

35. The apparatus according to claim 34, characterized in that, If the terminal detects the DCI scheduling PDSCH within the second timing period and has not configured application space domain binding, the fifth determining subunit and / or the first determining subunit are specifically used for: The third variable is determined to be equal to the number of TBs that the PDSCH scheduling DCI is actually enabled or the number of TBs that are configured, as detected by the terminal during the second timing period.

36. The apparatus according to claim 35, characterized in that, If the serving cell is not configured to allow dual codeword transmission, the actual number of TBs enabled or the configured number of TBs for each PDSCH scheduling DCI is equal to 1; or, When the serving cell is configured to allow dual codeword transmission, the number of TBs configured for each PDSCH scheduling DCI is equal to 2, or the number of TBs actually enabled for each PDSCH scheduling DCI is any one of the following: When the first TB is disabled, the number of TBs that are uniformly enabled by the DCI scheduler for each PDSCH is used. When using the second TB de-enable method, the number of TBs actually enabled by each PDSCH scheduling DCI.

37. The apparatus according to claim 34, characterized in that, The fifth determined sub-unit and / or the first determined secondary unit are specifically used for: If, during the second timing period, the terminal is only allowed to detect a single PDSCH scheduling DCI for a single serving cell, the third variable is determined to be equal to the number of TBs actually enabled or the configured number of TBs for the single PDSCH scheduling DCI detected by the terminal; or, If, within the second timeframe, the terminal is allowed to detect at least two PDSCH scheduling DCIs for a single serving cell, the third variable is determined to be equal to the sum of the actual number of TBs or the configured number of all PDSCH scheduling DCIs detected by the terminal.

38. The apparatus according to claim 34, characterized in that, If the terminal detects the DCI scheduling PDSCH within the second timing period and has configured application space domain binding, the fifth determining subunit and / or the first determining subunit are specifically used for: The third variable is determined to be equal to the number of PDSCH scheduled DCIs detected by the terminal during the second timing period.

39. A terminal, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the power control parameter determination method as described in any one of claims 1 to 19.

40. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the power control parameter determination method as described in any one of claims 1 to 19.

Images