Information feedback method and device

Abstract

An embodiment of the present application provides an information feedback method, a scheduling configuration method and an apparatus, in which the information feedback device includes: a second determining unit for determining a candidate PDSCH receiving timing set; and a fourth processing unit for determining a bit of HARQ-ACK information in a HARQ-ACK codebook according to a number of scheduled PDSCHs and / or a number of scheduled valid PDSCHs, and sending a codebook including HARQ-ACK information corresponding to the candidate PDSCH receiving timing set.

Description

[Technical Field]

[0001] TECHNICAL FIELD Embodiments of the present application relate to the field of communications technology. [Background technology]

[0002] A Physical Downlink Shared Channel (PDSCH) is a type of physical downlink channel in a wireless communication system and is used to transmit downlink data. The PDSCH can be scheduled by downlink control information (DCI). The DCI for scheduling the PDSCH includes at least information indicating the resource of the PDSCH. In current new radio (NR) systems, multiple DCI formats for scheduling the PDSCH, such as DCI format 1_0 (PDSCH), DCI format 1_1 (PDSCH), and DCI format 1_2 (PDSCH), are defined. The specific information and / or size included in the DCI of different DCI formats meet different scheduling requirements.

[0003] The PDSCH may be semi-statically configured or semi-persistently scheduled. In new radio NR, for example, a semi-statically configured or semi-persistently scheduled PDSCH is referred to as a semi-statically scheduled (SPS) PDSCH (SPS PDSCH). In some cases, after providing the SPS configuration via radio resource control (RRC) signaling, the network device must also activate the SPS configuration via DCI, so that the terminal device receives the SPS PDSCH accordingly. In addition to scheduling the PDSCH and activating the SPS, the DCI may also activate the SPS, a dormant cell, etc. The semi-static configuration, i.e., the configuration is configured by a cell-level upper layer parameter (tdd-UL-DL-ConfigurationCommon) and configures the transmission direction type of each symbol within one cycle. And / or, the transmission direction type of each symbol in the resource set by the upper layer parameter (tdd-UL-DL-ConfigurationDedicated) at the user-specific level and whose transmission direction type is set to "X" at the next higher layer is set.

[0004] In order to allow a network device to determine whether a terminal device has successfully received downlink data and / or control information, the terminal device generally needs to feed back Hybrid Automatic Repeat Request (HARQ) feedback information (e.g., ACK / NACK). Depending on the scheduling of the network device, the HARQ feedback information may be transmitted via a Physical Uplink Control Channel (PUCCH) or a Physical Uplink Shared Channel (PUSCH). Generally, one PUCCH or PUSCH may transmit one HARQ feedback codebook, which includes one or more HARQ feedback information bits.

[0005] It should be noted that the above description of the technical background is provided to clearly and completely explain the technical aspects of the present invention and to facilitate the understanding of those skilled in the art, and it cannot be assumed that the technical aspects are known to those skilled in the art just because they are described in the background section of this application. Summary of the Invention

[0006] Currently, the NR system supports scheduling multiple PDSCHs using one DCI (PDCCH), but how to support such a scheduling mode and corresponding HARQ-ACK feedback extensions is still under discussion. However, when the HARQ feedback codebook enables time domain bundling through RRC signaling, it is currently unclear whether / how to support transmission / reception of multiple PDSCHs in one slot, whether / how to support one physical downlink control channel (PDCCH) indicating / scheduling multiple PDSCHs with only one active PDSCH, whether / how to support associating one candidate PDSCH reception timing with multiple PDSCHs scheduled by different DCIs or different methods, and the HARQ feedback method in the above cases is also unclear. That is, the network device and the terminal device may have different understandings of whether the above PDSCH scheduling is permitted, and therefore, if the above situation occurs when the network device schedules the PDSCH, the terminal device may not be able to correctly receive the scheduled PDSCH and / or feed back corresponding HARQ-ACK information, which may result in unnecessary retransmissions and wasted resources.

[0007] To address at least one of the above problems, embodiments of the present application provide an information feedback method, a scheduling setting method, and an information setting method and device.

[0008] According to one aspect of an embodiment of the present application, there is provided an information feedback device applied to a terminal device, comprising: a first determining unit for determining a set of candidate PDSCH reception timings based on whether time domain bundling is configured, and / or whether multi-PDSCH scheduling is configured, and / or whether a subcarrier spacing of a downlink BWP is configured, and / or whether there is a capability to receive multiple PDSCHs in one slot; a first processing unit for generating and transmitting a HARQ-ACK codebook including HARQ-ACK information corresponding to the candidate PDSCH receiving timing set.

[0009] According to another aspect of an embodiment of the present application, there is provided an information feedback device applied to a terminal device, comprising: a second determining unit for determining a set of candidate PDSCH receive timings; and a fourth processing unit that determines bits of HARQ-ACK information in a HARQ-ACK codebook based on the number of scheduled PDSCHs and / or the number of scheduled valid PDSCHs, and transmits a codebook including HARQ-ACK information corresponding to the candidate PDSCH reception timing set.

[0010] One beneficial effect of the embodiments of the present application is that when time domain bundling is configured, it becomes clear whether / how to support transmission / reception of multiple PDSCHs in one slot, whether / how to support one physical downlink control channel (PDCCH) indicating / scheduling multiple PDSCHs with only one valid PDSCH, or whether / how to support association of one candidate PDSCH reception timing with multiple PDSCHs scheduled in different DCIs or different methods, and the HARQ feedback method in the above cases. Therefore, the network device and the terminal device can similarly understand whether the above PDSCH scheduling is permitted, and if the above situation occurs when the network device schedules a PDSCH, the terminal device can correctly receive the scheduled PDSCH and / or feedback corresponding HARQ-ACK information, thereby avoiding unnecessary retransmission and resource waste.

[0011] With reference to the following description and drawings, particular embodiments of the present application are disclosed in detail, illustrating the manner in which the principles of the present application may be employed. The embodiments of the present application are to be understood as not restrictive in scope. Many alterations, modifications, and equivalents are encompassed within the spirit and terms of the appended claims.

[0012] Features described and / or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, or may be combined with or substituted for feature information in other embodiments.

[0013] It should be emphasized that the term "comprising" as used herein refers to the presence of a feature, whole, step or assembly, but does not exclude the presence or addition of one or more other features, wholes, steps or assemblies.

[0014] Elements and features described in one drawing or one embodiment of the examples of this application may be combined with elements and features shown in one or more other drawings or embodiments. Furthermore, in the drawings, like reference numerals may be used to indicate corresponding parts in the several drawings and to designate corresponding parts used in one or more embodiments. [Brief explanation of the drawings]

[0015] [Figure 1] 1 is a schematic diagram of a communication system according to an embodiment of the present application; [Figure 2] 1 is a schematic diagram of an information feedback method according to an embodiment of the present application; [Figure 3] FIG. 1 is a schematic diagram of a scheduling setting method according to an embodiment of the present application; [Figure 4] FIG. 1 is a schematic diagram of a scheduling setting method according to an embodiment of the present application; [Figure 5A] FIG. 2 is a schematic diagram of a set of candidate PDSCH receiving timings according to an embodiment of the present application; [Figure 5B] FIG. 2 is a schematic diagram of a set of candidate PDSCH receiving timings according to an embodiment of the present application; [Figure 5C] FIG. 2 is a schematic diagram of a set of candidate PDSCH receiving timings according to an embodiment of the present application; [Figure 5D] FIG. 2 is a schematic diagram of a set of candidate PDSCH receiving timings according to an embodiment of the present application; [Figure 5E] FIG. 2 is a schematic diagram of a set of candidate PDSCH receiving timings according to an embodiment of the present application; [Figure 6] FIG. 1 is a schematic diagram of a scheduling setting method according to an embodiment of the present application; [Figure 7] FIG. 1 is a schematic diagram of a scheduling setting method according to an embodiment of the present application; [Figure 8] 1 is a schematic diagram of an information feedback method according to an embodiment of the present application; [Figure 9] FIG. 1 is a schematic diagram of an information setting method according to an embodiment of the present application. [Figure 10]FIG. 1 is a schematic diagram of an information setting method according to an embodiment of the present application. [Figure 11] 1 is a schematic diagram of an information feedback method according to an embodiment of the present application; [Figure 12] 1 is a schematic diagram of an information feedback device according to an embodiment of the present application; [Figure 13] 1 is a schematic diagram of a scheduling setting device according to an embodiment of the present application; [Figure 14] 1 is a schematic diagram of a scheduling setting device according to an embodiment of the present application; [Figure 15] 1 is a schematic diagram of an information feedback device according to an embodiment of the present application; [Figure 16] 1 is a schematic diagram of an information setting device according to an embodiment of the present application; [Figure 17] 1 is a schematic diagram of an information feedback device according to an embodiment of the present application; [Figure 18] 1 is a schematic diagram of a scheduling setting device according to an embodiment of the present application; [Figure 19] 1 is a schematic diagram of a scheduling setting device according to an embodiment of the present application; [Figure 20] 1 is a schematic diagram of an information setting device according to an embodiment of the present application; [Figure 21] FIG. 1 is a schematic diagram of a network device according to an embodiment of the present application; [Figure 22] 1 is a schematic diagram of a terminal device according to an embodiment of the present application; DETAILED DESCRIPTION OF THE INVENTION

[0016] The foregoing and other features of the present application will become apparent from the following specification, with reference to the drawings. Particular embodiments of the present application are specifically disclosed in the specification and drawings, illustrating some of the embodiments in which the principles of the present application may be employed. The present application is not limited to the disclosed embodiments, but rather includes all modifications, variations, and equivalents falling within the scope of the appended claims.

[0017] In the examples of this application, the terms "first," "second," etc. are used to distinguish different elements from the title, but do not indicate the spatial arrangement or chronological order of these elements, and these elements should not be limited to these terms. The term "and / or" includes any and all combinations of one or more of the associated listed terms. Terms such as "including," "comprising," "having," and the like refer to the presence of stated features, elements, parts, or assemblies but do not exclude the presence or addition of one or more other features, elements, parts, or assemblies.

[0018] In the examples of this application, the singular forms "a," "the," etc., include the plural and should be understood broadly to mean "one of," or "a type of," and not limited to "one." Furthermore, the term "said" includes both the singular and the plural, unless the context clearly indicates otherwise. Furthermore, unless the context clearly indicates otherwise, the term "according to" should be understood as "at least in part according to," and the term "based on" should be understood as "based at least in part on."

[0019] In the embodiments of the present application, the terms "communications network" or "wireless communication network" refer to a network conforming to any suitable communications standard, such as, for example, Long Term Evolution (LTE), Long Term Evolution Advanced (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0020] Additionally, communication between devices in a communication system may be accomplished via any suitable generation of communication protocol, including, but not limited to, 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, and 5G, New Radio (NR), etc., and / or other currently known or later developed communication protocols.

[0021] In the embodiments of the present application, the term "network equipment" refers to a device that allows a terminal device to access a communication network and provides services to the terminal device, for example, in a communication system. The network equipment may include, but is not limited to, devices such as a base station (BS), an access point (AP), a transmission reception point (TRP), a broadcast transmitter, a mobile management entity (MME), a gateway, a server, a radio network controller (RNC), a base station controller (BSC), etc.

[0022] Among them, a base station may include, but is not limited to, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), a 5G base station (gNB), etc., as well as a remote radio head (RRH), a remote radio unit (RRU), a relay, or a low-power node (e.g., femto, pico, etc.). Furthermore, the term "base station" may include some or all of these functions, and each base station may provide communication coverage for a particular geographic area. The term "cell" may refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0023] In the embodiments of the present application, the term "User Equipment" (UE) or "Terminal Equipment" (TE) refers to a device that accesses a communication network and receives network services via, for example, a network device. The terminal device may be fixed or mobile, and may also be referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), a station, etc.

[0024] Among them, the terminal device may include, but is not limited to, a cellular phone, a personal digital assistant (PDA), a wireless modulation / demodulation device, a wireless communication device, a handheld device, a machine-type communication device, a laptop computer, a cordless phone, a wearable device, a smartphone, a smart watch, a digital camera, etc.

[0025] Furthermore, in a scenario such as the Internet of Things (IoT), the terminal device may be a device or apparatus that performs monitoring or measurement, including, but not limited to, a Machine Type Communication (MTC) terminal, an in-vehicle communication terminal, an industrial wireless device, a surveillance camera, a Device to Device (D2D) terminal, a Machine to Machine (M2M) terminal, etc.

[0026] Furthermore, the term "network side" or "network device side" refers to the side of a network, which may be a base station or a core network device, or may include one or more of the network devices mentioned above. The term "user side" or "terminal side" or "terminal device side" refers to the side of a user or terminal, which may be a UE or may include one or more of the terminal devices mentioned above. In this specification, unless otherwise specified, "device" may refer to a network device or a terminal device.

[0027] In an embodiment of the present invention, the time unit may be a subframe, a slot, or at least one set of time-domain symbols. The at least one set of time-domain symbols may be referred to as a mini-slot or a non-slot. For example, in an embodiment of the present invention, a subframe and a slot may be used interchangeably, and a "slot" may be replaced with a "subframe," but the present invention is not limited thereto. For convenience of explanation, the following description will be given using a "slot" as an example, but other time units may be used instead. Furthermore, the terms "time-domain resource" and "resource" may be used interchangeably.

[0028] In the following description, unless confusion arises, the terms "uplink control signal" and "uplink control information (UCI)" or "physical uplink control channel (PUCCH)" are interchangeable, and the terms "uplink data signal" and "uplink data information" or "physical uplink shared channel (PUSCH)" are interchangeable.

[0029] The terms "downlink control signal" and "Downlink Control Information (DCI)" or "Physical Downlink Control Channel (PDCCH)" are interchangeable, and the terms "downlink data signal" and "downlink data information" or "Physical Downlink Shared Channel (PDSCH)" are interchangeable.

[0030] Furthermore, transmitting or receiving a PUSCH may be understood as transmitting or receiving uplink data carried by the PUSCH, transmitting or receiving a PUCCH may be understood as transmitting or receiving uplink information (e.g., UCI) carried by the PUCCH, transmitting or receiving a PRACH may be understood as transmitting or receiving a preamble carried by the PRACH, transmitting or receiving a PDSCH may be understood as transmitting or receiving downlink data carried by the PDSCH, and transmitting or receiving a PDCCH may be understood as transmitting or receiving downlink information (e.g., DCI) carried by the PDCCH.

[0031] In an embodiment of the present invention, the higher layer signaling may be, for example, Radio Resource Control (RRC) signaling, for example, referred to as an RRC message, including, for example, a Master Information Block (MIB), system information, and dedicated RRC messages, or referred to as an RRC information element (RRC IE). The higher layer signaling may also be, for example, Medium Access Control (MAC) signaling, or referred to as a MAC control element (MAC CE). However, the present invention is not limited thereto.

[0032] The following describes a scenario in an embodiment of the present invention through an example, but the present invention is not limited thereto.

[0033] 1 is a schematic diagram of a communication system according to an embodiment of the present application, and will be described using a terminal device and a network device as an example. As shown in FIG. 1, a communication system 100 may include a network device 101 and terminal devices 102 and 103. For convenience, FIG. 1 illustrates an example in which only two terminal devices and only one network device are used, but the embodiment of the present invention is not limited thereto.

[0034] In an embodiment of the present invention, existing or future services may be transmitted between the network device 101 and the terminal devices 102 and 103. For example, these services may include, but are not limited to, enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), Ultra-Reliable and Low-Latency Communication (URLLC), and communications related to degraded devices.

[0035] 1 shows that both of the two terminal devices 102 and 103 are located within the coverage of the network device 101, but the present invention is not limited to this. Neither of the two terminal devices 102 and 103 may be located within the coverage of the network device 101, or one terminal device 102 may be located within the coverage of the network device 101 and the other terminal device 103 may be located outside the coverage of the network device 101.

[0036] In the embodiments of the present invention, the transport blocks carried by different PDSCHs may be the same or different, so hereinafter, "multiple PDSCHs" or "at least two PDSCHs" refers to different PDSCHs carrying different transport blocks. More specifically, the transport blocks carried by different PDSCHs correspond to the same or different HARQ processes, where different HARQ processes are identified by different HARQ processes.

[0037] In some embodiments, a PDSCH time domain resource allocation (TDRA) table (or simply referred to as a TDRA table) includes at least one row. Hereinafter, for convenience of explanation, one row represents one PDSCH TDRA setting (or simply referred to as a TDRA setting). That is, the PDSCH TDRA table includes at least one PDSCH TDRA setting. The PDSCH TDRA setting includes at least one PDSCH time domain resource setting (or simply referred to as a time domain resource setting) including at least a symbol position setting within a slot (start symbol + length). Furthermore, one PDSCH TDRA setting may include at least one slot offset set K0 setting representing a slot offset set between the PDSCH and the PDCCH. The K0 setting may or may not be included in the PDSCH time domain resource setting. The one PDSCH TDRA setting may include other information that may or may not be included in the PDSCH time domain resource setting. The embodiments of the present application are not limited thereto. Here, the symbol position setting within a slot includes, for example, a start and length indicator SLIV, which corresponds to a valid combination of a starting symbol (S) and a length (L), or, for example, a starting symbol setting and a length setting, which is a valid combination.

[0038] In the existing method, when determining an HARQ feedback codebook (for example, referred to as a Type-1 HARQ-ACK codebook or a semi-static HARQ-ACK codebook), a set of candidate PDSCH reception occasions is first determined, and then a bit of HARQ feedback (hereinafter also referred to as HARQ-ACK) information corresponding to the candidate PDSCH reception occasion is determined. When determining the set of candidate PDSCH reception occasions, if at least one row in the TDRA table includes an SLIV (each row includes one SLIV) that does not collide with a semi-statically configured uplink symbol, the candidate PDSCH reception occasion is reserved.

[0039] Rel-17 supports scheduling multiple PDSCHs (mutli-PDSCH scheduling) via one DCI (PDCCH), and the extension of the HARQ feedback codebook is under discussion. Here, time domain bundling may be supported for the HARQ feedback codebook (called Type-1 HARQ-ACK codebook or semi-static HARQ-ACK codebook). For example, when time domain bundling is enabled by RRC signaling for a Type-1 HARQ-ACK codebook, when determining a set of candidate PDSCH reception timings, if a row in the TDRA table includes (or corresponds to) an SLIV that does not collide with a semi-statically configured uplink symbol (a row includes one or more SLIVs, and at least one SLIV does not collide with a semi-statically configured uplink symbol, i.e., the row includes an SLIV that does not collide with a semi-statically configured uplink symbol), the row is reserved, i.e., if at least one row in the TDRA table includes an SLIV that does not collide with a semi-statically configured uplink symbol, the corresponding candidate PDSCH reception timing is reserved. Furthermore, when multiple valid PDSCHs are scheduled by one DCI for a certain candidate PDSCH reception timing, the bit value of the corresponding HARQ feedback information is the logical OR value of valid PDSCHs associated with the PDSCH, where the valid PDSCH is a PDSCH that does not collide with the time domain resource configuration (e.g., SLIV) corresponding to the PDSCH and a semi-statically configured uplink symbol (or a PDSCH that does not overlap with one semi-statically configured uplink symbol). For example, if there are two associated valid PDSCHs, one of which is not successfully received (NACK / 0) and the other is successfully received (ACK / 1), the bit value of the HARQ feedback information is the logical OR of the two values, i.e., (NACK / 0).As shown in FIG. 5A, for candidate PDSCH reception timing 0, since it is associated with a valid PDSCH scheduled by the same DCI, the bit value of the corresponding HARQ feedback information is the logical OR of the corresponding HARQ-ACK information bits of the two PDSCHs.

[0040] However, for PDSCH scheduling, the following scheduling situations may exist while time domain bundling is configured, but it is currently unclear how HARQ-ACK feedback is supported for these situations. Furthermore, the terminal device may not be able to correctly feedback the corresponding HARQ-ACK information, which may result in unnecessary retransmissions and resource waste.

[0041] 1. One candidate PDSCH reception timing is associated with multiple PDSCHs scheduled by multiple DCIs respectively (as shown in FIG. 5C).

[0042] 2. One candidate PDSCH reception timing is associated with multiple PDSCHs scheduled by one or more DCIs and by SPS, respectively (as shown in FIG. 5D).

[0043] 3. One candidate PDSCH reception timing is associated with multiple valid PDSCHs, and the DCI that schedules this one valid PDSCH schedules multiple PDSCHs, of which only one is valid (as shown in FIG. 5B). The above-mentioned problems 1 to 3 will be described with reference to the fourth to ninth embodiments.

[0044] On the other hand, as mentioned above, it is currently not yet clear whether / how to support transmission / reception of multiple PDSCHs in one slot, and the corresponding HARQ feedback method is not yet clear (for specific explanations, see the examples of the first to third aspects).

[0045] 5A to 5E, it is assumed that the uplink and downlink subcarrier spacing (the subcarrier spacing of the PDSCH and the subcarrier spacing of the PUCCH / PUSCH for transmitting the corresponding HARQ-ACK information) is the same, but they may be different. When the uplink and downlink subcarrier spacing is different, one K1 value may correspond to multiple downlink slots. Downlink slot n in FIGS. 5A to 5E D means a slot corresponding to a downlink subcarrier spacing (or a subcarrier spacing of a PDSCH), where the specific transmission direction (downlink / uplink) of the symbol is not limited. For example, in Figures 5A to 5E, downlink slots (Slots) n-1 and n-2 include uplink symbols. Furthermore, in Figures 5A to 5E, it is assumed that the TDRA table has only two rows, row 0 and row 1, where row 0 includes two PDSCH time domain resource configurations SLIV0_0 and SLIV0_1, and row 1 includes three PDSCH time domain resource configurations SLIV1_0, SLIV1_1, and SLIV1_2, and the K1 set is {1, 2}, but this application is not limited thereto.

[0046] Note that the following embodiments are applicable both when ca-SlotOffset is set and when ca-SlotOffset is not set. This ca-SlotOffset refers to the offset value of a different carrier feedback slot, and the specific embodiments of the following methods used in the two cases may be the same or different. Note that the embodiments of the present application are applied to FR2-2 (52.6 GHz to 71 GHz), but are not limited thereto. In the embodiments of the present application, the subcarrier spacing of the PDSCH is 120 kHz, 480 kHz, or 960 kHz, but is not limited thereto.

[0047] Example of the first aspect In the embodiment of the present application, an information feedback method is provided and explained from the terminal device side.

[0048] FIG. 2 is a schematic diagram of an information feedback method according to an embodiment of the present application. As shown in FIG. 2, the method includes: 201: Determining a candidate PDSCH reception timing set based on whether the terminal device configures time domain bundling, and / or whether PDSCH scheduling (multi-PDSCH scheduling) is configured, and / or whether a subcarrier spacing of a downlink BWP is configured, and / or whether the terminal device is capable of receiving multiple PDSCHs in one slot; and 202: The terminal device generates and transmits a HARQ-ACK codebook including HARQ-ACK information corresponding to the candidate PDSCH reception timing set.

[0049] In some embodiments, the terminal device needs to perform HARQ-ACK feedback for the received PDSCH (e.g., a PDSCH scheduled by DCI or a PDSCH for SPS) and / or DCI (e.g., a DCI for deactivating SPS), and the HARQ-ACK feedback information may be carried by a HARQ-ACK codebook (e.g., a Type-1 HARQ-ACK codebook or a semi-static HARQ-ACK codebook) that may include HARQ-ACK information bits of one or more serving cells. The following only describes how to determine the HARQ-ACK information bits of one serving cell. If the codebook includes HARQ-ACK information bits of multiple serving cells, the method for determining the HARQ-ACK information bits of each serving cell is the same as the method for determining the HARQ-ACK information bits of the one serving cell, and the HARQ-ACK information bits of the multiple serving cells are arranged in a certain order in the codebook, which will not be described here in detail. Below, "HARQ-ACK", "HARQ feedback" and "HARQ-ACK feedback" are interchangeable, and "HARQ-ACK information" and "bits of HARQ-ACK information" are interchangeable.

[0050] In some embodiments, the codebook includes bits of HARQ-ACK information corresponding to a second number (A) of candidate PDSCH reception occasions (occasions for candidate PDSCH reception), where the second number is a natural number, and the second number (A) of candidate PDSCH reception occasions correspond to the same serving cell (i.e., the one serving cell), that is, the second number (A) of candidate PDSCH reception occasions are included in a set M of candidate PDSCH reception occasions of the serving cell. A,C In the prior art (introduced in Rel-16), when determining the candidate PDSCH reception timing set, one downlink slot n D For R, first, a first allocation table including a set of schedulable rows (row indexes and / or time domain resource configurations (e.g., SLIVs), etc.) is determined. If the terminal device is not capable of receiving multiple PDSCHs in one slot (or the terminal device does not indicate the ability to receive multiple PDSCHs in one slot), it is determined to add one candidate PDSCH reception timing. If the terminal device is capable of receiving multiple PDSCHs in one slot, it is necessary to add one or more candidate PDSCH reception timings according to the number of time domain resource configurations (e.g., SLIVs) (or the number of time domain resource configuration sets (e.g., the number of SLIV sets)) that are independent of each other (have no overlap) in the first allocation table R.

[0051] However, the above method does not consider the case of multi-PDSCH scheduling and / or time domain bundling. Here, time domain bundling is usually configurable only when multi-PDSCH scheduling is configured. When time domain bundling is configured, rows that may be scheduled are rows that have at least one time domain resource configuration (e.g., SLIV) that does not collide with uplink symbols configured semi-statically. That is, for example, it is assumed that the initial value of the first allocation table R includes all rows (row indexes and / or time domain resource configurations (e.g., SLIVs), etc.), and one row among them corresponds to one or more SLIVs. For each of these rows, if all time domain resource configurations (e.g., SLIVs) conflict with semi-statically configured uplink symbols, the row (row index and / or time domain resource configurations (e.g., SLIVs)) is excluded / deleted from the first allocation table; otherwise, the row is not excluded / deleted. Therefore, the SLIVs corresponding to one row of the reduced first allocation table R may span slots (the row includes multiple SLIVs in different slots), and the above conventional method is applicable only when each row includes only one SLIV (because only single-PDSCH scheduling is considered), but not when one row of the above first allocation table corresponds to multiple SLIVs. In other words, when multi-PDSCH scheduling and / or time domain bundling are configured, the above conventional method for determining a candidate PDSCH reception timing set cannot be used.

[0052] In the embodiments of the present application, in order to support scheduling of multiple PDSCHs using one DCI and correctly feeding back HARQ-ACK information when time domain bundling is configured, it is necessary to further consider whether time domain bundling is configured, and / or whether multiple PDSCH scheduling (multi-PDSCH scheduling) is configured, and / or whether subcarrier spacing of downlink BWP is configured when determining a candidate PDSCH reception timing set, as will be described in detail below.

[0053] In some embodiments, before determining the candidate PDSCH reception timing, the terminal device needs to determine the HARQ-ACK information feedback timing (i.e., the terminal device needs to determine the slot (uplink slot) in which to transmit the HARQ-ACK information).

[0054] In some embodiments, a terminal device receives a DCI, the DCI including a first information field which may be a time domain resource assignment, the first information field indicating a PDSCH time domain resource by indicating an index (row index, e.g., the row index value is 1 or greater) corresponding to a PDSCH TDRA setting in a PDSCH TDRA table to be applied by the DCI. In other words, the DCI schedules a PDSCH by indicating a PDSCH TDRA setting in the PDSCH TDRA table to be applied by the DCI, hereinafter referred to as a DCI-scheduled PDSCH or DCI-indicated PDSCH. For example, a value m (assuming m is an integer greater than or equal to 0) in the first information field of the DCI corresponds to a PDSCH TDRA setting indicating that the index m+1 (i.e., the m+1th row) in the PDSCH TDRA table to be applied by the DCI.

[0055] In some embodiments, the PDSCH TDRA table may be predefined or configured by higher layer signaling, and the table supports scheduling multiple PDSCHs by one DCI, or one or more rows of the table include multiple time domain resource configurations (SLIVs). For example, if one DCI supports scheduling multiple PDSCHs, but when a DCI applies the table, the table further includes one or more rows including only one time domain resource configuration (SLIV), the DCI may indicate / schedule one PDSCH (e.g., the row of the TDRA table indicated by the first information field in the DCI includes only one SLIV), or may indicate / schedule multiple PDSCHs (e.g., the row of the TDRA table indicated by the first information field in the DCI includes multiple SLIVs).

[0056] In some embodiments, the TDRA table is configured by RRC signaling (e.g., pdsch-TimeDomainAllocationListForMultiPDSCH-r17 provided in PDSCH-Config), and when the TDRA table is configured, it applies / corresponds to DCI format 1_1.

[0057] In some embodiments, the DCI includes a second information field (PDSCH-to-HARQ_feedback timing indicator field) used to indicate the feedback timing k of the HARQ-ACK information, where the feedback timing k of the HARQ-ACK information represents an offset between the feedback timing of the HARQ-ACK information and the slot n in which the scheduled PDSCH exists, and the terminal device determines the slot in which to transmit the HARQ-ACK information based on the second information field.

[0058] In some embodiments, the DCI may not include the second information field, and the terminal device receives second configuration information of higher layer signaling configuration (e.g., dl-DataToUL-ACK or dl-DataToUL-ACKForDCIFormat1_2 for DCI format 1_2) for indicating feedback timing k of HARQ acknowledgement (HARQ-ACK) information, or the terminal device receives second configuration information of higher layer signaling configuration (e.g., dl-DataToUL-ACK or dl-DataToUL-ACKForDCIFormat1_2 for DCI format 1_2) for setting feedback timing k of multiple HARQ acknowledgement (HARQ-ACK) information, and the DCI includes the second information field for indicating feedback timing of one HARQ acknowledgement (HARQ-ACK) information from the multiple feedback timings set by the second configuration information.

[0059] In some embodiments, HARQ-ACK information (or HARQ-ACK codebook) is carried by PUCCH or PUSCH. In the following, HARQ-ACK feedback timing will be described using an example in which HARQ-ACK information is carried by PUCCH. Alternatively, the PUCCH below may be replaced with PUSCH, and this application is not limited thereto. For how to determine whether to use PUCCH or PUSCH, reference may be made to the prior art.

[0060] In some embodiments, HARQ-ACK information corresponding to one or more PDSCHs scheduled by the DCI may be fed back in the same PUCCH.

[0061] For example, HARQ-ACK information of multiple PDSCHs may be fed back in one PUCCH.

number

[0062] In some embodiments, after determining the time domain position or slot for feeding back the HARQ-ACK information, the terminal device may determine candidate PDSCH reception timings and generate a corresponding codebook. The following describes how to determine candidate PDSCH reception timings when mutli-PDSCH scheduling and time domain bundling are not considered.

[0063] In some embodiments, to determine a set of candidate PDSCH receive timings, it is necessary to determine downlink slots that may contain (or correspond to) the candidate PDSCH receive timings.

[0064] In some embodiments, the downlink slot is determined based on a slot timing value K1.

[0065] For example, the slot in which the HARQ-ACK information should be transmitted, e.g., uplink slot n u , based on the set of slot timing values ​​K1 associated with the active uplink partial bandwidth UL BWP, one or more downlink slots n corresponding to each K1 in the set K1 are selected. D where K1 is the HARQ-ACK information feedback slot n of PDSCH. D(i.e., the k value that can be indicated by the DCI). When determining one or more downlink slots corresponding to each K1, the subcarrier spacing of the uplink and downlink partial bandwidth may optionally be taken into consideration, and one K1 may correspond to multiple downlink slots. For details, see the prior art, and this is not limited in the embodiments of the present invention. Here, the subcarrier spacing of the downlink partial bandwidth (DL BWP) refers, for example, to the subcarrier spacing of an active DL BWP (or the subcarrier spacing of a PDSCH that needs to feed back HARQ-ACK information in the uplink slot), and the subcarrier spacing of the uplink partial bandwidth (UL BWP) refers, for example, to the subcarrier spacing for transmitting the HARQ-ACK information (active) UL BWP (or the subcarrier spacing of a PUCCH or PUSCH that needs to transmit the HARQ-ACK information).

[0066] In some embodiments, the determination of the K1 set associated with the active uplink fractional bandwidth UL BWP may refer to prior art.

[0067] For example, for a downlink slot, first determine a first allocation table (including a set of rows that can be scheduled, each row including a row index and / or a setting such as SLIV), and then determine whether the slot has a corresponding candidate PDSCH receive timing, thereby determining a set of candidate PDSCH receive timings. Note that the above determination of each downlink slot and the PDSCH time domain resource allocation corresponding to the slot may be performed one after the other or simultaneously, and the present application is not limited thereto.

[0068] The following first describes how to determine the first allocation table, which is used to determine candidate PDSCH reception timings and / or schedule PDSCHs.

[0069] In some embodiments, the PDSCH TDRA configuration and / or an index corresponding to the configuration may be included in a first allocation table. For example, the first allocation table may be determined based on a PDSCH TDRA table to which each DCI format can be applied, and the first allocation table is also associated with an active DL BWP. For example, for a serving cell c, a row (e.g., a row index and / or a corresponding SLIV configuration) of the first first allocation table corresponds to a TDRA configuration of a row of a union of time domain resource allocation tables of DCI formats that the terminal device needs to wait on configured on the serving cell c. Furthermore, for example, the first allocation table may include a union of all rows of PDSCH TDRA tables that apply to the DCI formats to be waited on, and the configuration of each row is the same as the PDSCH TDRA table. For example, for a specific active DL BWP, Table 1 is an example of the first allocation table, representing one PDSCH TDRA configuration (corresponding to one row of the first allocation table), as shown in Table 1 below. Furthermore, one PDSCH TDRA configuration may (optionally) include a slot offset K0 configuration indicating a slot offset between the PDSCH and the PDCCH. Furthermore, one PDSCH TDRA configuration may include other information (e.g., a mapping mode), and the other information configuration may be included in the PDSCH time domain resource configuration or may not be included in the PDSCH time domain resource configuration. Furthermore, when ReferenceofSLIV-ForDCIFormat1_2 is configured in the terminal device, a new row needs to be added above the PDSCH TDRA table for DCI_format 1_2; however, a specific example is not provided here, and reference may be made to the prior art for specific examples. Table 1

[0070] [Table 1] In some embodiments, if the terminal device is not capable of receiving multiple PDSCHs in one slot (or does not indicate the ability to receive multiple PDSCHs in one slot), it is determined to add one candidate PDSCH reception timing. If the terminal device is capable of receiving multiple PDSCHs in one slot, it is necessary to add one or more candidate PDSCH reception timings according to the number of time domain resource configurations (e.g., SLIVs) (or time domain resource configuration sets (e.g., the number of SLIV sets)) that are independent of each other (have no overlap) in the first allocation table R.

[0071] The above describes how to determine candidate PDSCH reception timings when multi-PDSCH scheduling and time domain bundling are not taken into consideration. Hereinafter, only differences will be described regarding how candidate PDSCH reception timings are determined in the case of multi-PDSCH scheduling and time domain bundling, and redundant description will be omitted. In some embodiments, a terminal device may be pre-defined and / or pre-configured by RRC signaling to standby for / detect / receive one or more DCI formats. Different DCI formats may be applied and the corresponding TDRA tables may be the same or different. For example, one or more rows in a TDRA table applied by DCI format 1_1 include multiple SLIVs (one or more rows may include only one SLIV), and each row in a TDRA table applied by DCI format 1_0 or 1_1 includes only one SLIV.

[0072] In some embodiments, when multi-PDSCH scheduling is configured but time domain bundling is not configured, one or more rows of the first allocation table include / correspond to multiple SLIVs. The first allocation table may be processed so that one row of the processed first allocation table (hereinafter referred to as a third allocation table) corresponds to one SLIV, and candidate PDSCH reception timings are determined based on the third allocation table. Referring now to Figure 5E, Figure 5E is a schematic diagram of candidate PDSCH reception timings. As shown in Figure 5E, assume that the first allocation table has only two rows, row 0 and row 1, where row 0 includes two PDSCH time domain resource configurations SLIV0_0 and SLIV0_1, and row 1 includes three PDSCH time domain resource configurations SLIV1_0, SLIV1_1, and SLIV1_2, and is divided to obtain a third allocation table, each row of which corresponds to SLIV0_0, SLIV0_1, SLIV1_0, SLIV1_1, and SLIV1_2. uFor K1, the set K1 includes {1, 2}, and may further include {3, 4} when expanded by the first allocation table (before the above processing). Here, all symbols in downlink slot Slot n-2 are uplink symbols (semi-static setting), some symbols in downlink slot n-1 are uplink symbols, some symbols are uplink (UL) symbols, and all symbols in the other downlink slots are downlink (DL) symbols. Therefore, for slot n-1 (corresponding to K1=1), SLIV0_1 is a valid PDSCH / SLIV in the row corresponding to the third allocation table, for slot n-2 (corresponding to K1=2), there is no valid PDSCH / SLIV in the row corresponding to the third allocation table, and for slot n-3 (corresponding to K1'=3), SLIV0_0 and SLIV1_1 are valid PDSCH / SLIV in the row corresponding to the third allocation table. For n-4 (corresponding to K1′=4), since SLIV1_0 is a valid PDSCH / SLIV in the row corresponding to the third allocation table, there are candidate PDSCH reception timings 2 corresponding to downlink slot n-1 (corresponding to K1=1), candidate PDSCH reception timing 1 corresponding to downlink slot n-3 (corresponding to K1′=3), and candidate PDSCH reception timing 0 corresponding to downlink slot n-4 (corresponding to K1′=4). In some embodiments, when time domain bundling is configured (time domain bundling is typically only configurable when multi-PDSCH scheduling is configured), one or more rows of the first allocation table include / correspond to multiple SLIs, and the first allocation table may be processed based on whether the SLIV of each row conflicts with a semi-statically configured uplink symbol. The first allocation table after this processing is called the second allocation table, and for example, for each row, if all time domain resource settings (e.g., SLIV) conflict with semi-statically configured uplink symbols, the row (row index and / or time domain resource setting (e.g., SLIV), etc.) is excluded / deleted in the first allocation table.That is, when time domain bundling is configured, a row that may be scheduled is a row in which at least one SLIV does not collide with a semi-statically configured uplink symbol. Therefore, the second allocation table does not include any row that satisfies the condition that all corresponding SLIVs collide with semi-statically arranged uplink symbols. If at least one row in the second allocation table includes / corresponds to an SLIV that does not collide with a semi-statically configured uplink symbol, the corresponding candidate PDSCH reception timing is reserved. Figure 5A is a schematic diagram of candidate PDSCH reception timing. As shown in Figure 5A, assume that the first allocation table only has two rows, row 0 and row 1, where row 0 includes two PDSCH time domain resource configurations SLIV0_0 and SLIV0_1, and row 1 includes three PDSCH time domain resource configurations SLIV1_0, SLIV1_1, and SLIV1_2. After comparison, the two rows all remain in the first allocation table, and a second allocation table is obtained (i.e., the same as the first allocation table), and HARQ feedback slot n is obtained. u For K1, the K1 set includes {1, 2}, where all symbols in downlink slot Slot n-2 are uplink symbols (semi-static setting), some symbols in downlink ring slot Slot n-1 are uplink symbols and some symbols are uplink (UL) symbols, and all symbols in the other downlink ring slots are downlink (DL) symbols. Therefore, when SLIV0_1 and SLIV1_0 are valid PDSCH / SLIV for slot n-1 (corresponding to K1=1), and SLIV0_0, SLIV1_0, and SLIV 1_1 are valid PDSCH / SLIV for slot n-2 (corresponding to K1=2), there exists candidate PDSCH reception timing 1 corresponding to slot n-1 (corresponding to K1=1) and candidate PDSCH reception timing 0 corresponding to slot n-2 (corresponding to K1=2).

[0073] In some embodiments, for each downlink slot, the corresponding candidate PDSCH receive timing is determined based on the first allocation table and the second allocation table, respectively.

[0074] Therefore, whether the time domain has a corresponding candidate PDSCH reception timing may be determined based on whether time domain bundling is configured and / or whether the terminal device is capable of receiving multiple PDSCHs in one slot. For example, if time domain bundling is configured or if the terminal device is not capable of receiving multiple PDSCHs in one slot, one PDSCH reception timing may be added. If time domain bundling is not configured and the terminal device is capable of receiving multiple PDSCHs in one slot, adding one candidate PDSCH reception timing or multiple candidate PDSCH reception timings to the candidate PDSCH reception timing set based on the number of mutually independent PDSCH time domain resource configurations in the first allocation table will be described in detail below.

[0075] For example, when time domain bundling is configured or when the terminal device is not capable of receiving multiple PDSCHs in one slot, one PDSCH reception timing is added. For example, when time domain bundling is configured, the allocation table used when determining the candidate PDSCH reception timing is the second allocation table, which is described below with an example of pseudocode.

[0076] [Table 2] That is, if the second allocation table is not blank, when time domain bundling is configured in the terminal device or the terminal device is not capable of receiving multiple PDSCHs in one slot, one PDSCH reception timing (j=j+1) is added to the candidate PDSCH reception timing set M A,c Add to.

[0077] Otherwise, if time domain bundling is not configured and the terminal device is capable of receiving multiple PDSCHs in one slot, one candidate PDSCH reception timing or multiple candidate PDSCH reception timings are added to the candidate PDSCH reception timing set based on the number of mutually independent PDSCH time domain resource configurations in the first allocation table, as described below with reference to an example pseudocode.

[0078] [Table 3] That is, for each row of the third allocation table (which is not blank), the number of SLIVs or sets of SLIVs that are independent of each other (without any overlap) in the SLIVs corresponding to each row is determined in order, and one or more candidate PDSCH reception timings are added.

[0079] In some embodiments, the terminal device may take into account whether multi-PDSCH scheduling is configured and / or whether subcarrier spacing of the downlink BWP is configured when determining the PDSCH reception timing set.

[0080] In some embodiments, some subcarrier spacings (e.g., 120 kHz) support scheduling of multiple PDSCHs in one slot, and some subcarrier spacings (e.g., 480 / 960 kHz) do not support scheduling of multiple PDSCHs in one slot. When the subcarrier spacing of the downlink BWP is 120 kHz, if multiple PDSCH scheduling is configured, an allocation table (second allocation table) including only rows corresponding to schedulable TDRA configurations is determined, and then the above method (i.e., determining the PDSCH reception timing set depending on whether time domain bunding is configured) is adopted. However, when the subcarrier spacing of the downlink BWP is 480 / 960 kHz, the above method does not need to be adopted (i.e., determining the PDSCH reception timing set depending on whether time domain bunding is configured).

[0081] In some examples, the above-described various methods for determining candidate PDSCH receive timings may be implemented alone or in combination, and embodiments of the present application are not limited thereto.

[0082] In some embodiments, after determining the candidate PDSCH receive timing sets in 202, a HARQ-ACK codebook is further generated, which includes HARQ-ACK information corresponding to the candidate PDSCH receive timing sets. The following will further describe how the codebook is generated based on the candidate PDSCH receive timing sets.

[0083] In some embodiments, the size of the codebook is determined based on a preset (e.g., higher layer signaling configuration) or predefined parameter, rather than dynamically changing according to the actual data scheduling situation. In the following, we will only describe how to determine the bits of the HARQ-ACK information of the serving cell.

[0084] In some embodiments, the number of bits of HARQ-ACK information corresponding to the candidate PDSCH reception timing of one serving cell is related to the HARQ spatial bundling parameter (harq-ACK-SpatialBundlingPUCCH), the code block group (CBG) configuration parameter (PDSCH-CodeBlockGroupTransmission), and the maximum supported codeword parameter (maxNrofCodeWordsScheduledByDCI) configured by the cell, and is exemplified by feeding back the HARQ-ACK information on PUCCH as shown in Table 2. Table 2

[0085] [Table 4] The above is merely an example, and the method for determining the number of bits of HARQ-ACK information corresponding to candidate PDSCH reception timings of one serving cell is not limited to this. Furthermore, the method for determining the bit value of information in the HARQ-ACK codebook is not limited in this application, but for example, conventional technology (for example, whether time domain bundling is set or not, all existing methods for determining HARQ-ACK information are applicable) may be used, or the determination may be made based on Examples 4 to 9 described below.

[0086] In some embodiments, the bits of the HARQ-ACK information corresponding to each candidate PDSCH reception timing are arranged in the order of the second candidate PDSCH reception timings in the set of candidate PDSCH reception timings to obtain the bits of the HARQ-ACK information of one serving cell, where if one of the candidate PDSCH reception timings does not have a corresponding (or associated) PDSCH, the bit padding of the corresponding HARQ-ACK information is a NACK. As described above, when a codebook includes HARQ-ACK information bits of one serving cell, the HARQ-ACK information bits of the one serving cell are fed back as a codebook. When a codebook includes HARQ-ACK information bits of multiple serving cells, the method of determining the HARQ-ACK information bits of each serving cell is the same as the method of determining the HARQ-ACK information bits of one serving cell. However, when specifically determining the HARQ-ACK information bits, other parameters such as PDSCH TDRA configuration corresponding to each serving cell may be the same or different. For example, the above parameters may be individually configured for each serving cell, but this embodiment is not limited thereto. The HARQ-ACK information bits corresponding to each serving cell may be arranged in ascending order of serving cell index to generate a codebook for feedback.

[0087] In some embodiments, the terminal device may receive enabled time domain bundling configuration information sent from the network device, for example, transmit enableTimeDomainHARQ-Bundling (enabled time domain bundling configuration information) by RRC signaling, and receiving the enabled time domain bundling configuration information indicates that time domain bundling is configured in the terminal device.

[0088] As can be seen from the above embodiment, when one DCI supports scheduling multiple PDSCHs and supports the configuration of time domain bundling, multiple PDSCHs may be transmitted / received in one slot and corresponding HARQ-ACK information may be fed back. Therefore, the network device and the terminal device can similarly understand whether the above PDSCH scheduling is permitted. If the above situation occurs when the network device schedules a PDSCH, the terminal device can correctly receive the scheduled PDSCH and / or feed back corresponding HARQ-ACK information, thereby avoiding unnecessary retransmission and resource waste.

[0089] Example of the second aspect According to the method in the embodiment of the first aspect, if one DCI schedules multiple PDSCHs and / or supports time domain bundling configuration, multiple PDSCHs may be transmitted / received in one slot and corresponding HARQ-ACK information feedback may be performed; conversely, in the embodiment of the second aspect, if the terminal device is capable of receiving multiple PDSCHs in one slot, the network device does not configure multi-PDSCH scheduling and / or time domain bundling, and according to this embodiment, does not support transmitting / receiving multiple PDSCHs in one slot, as will be described in detail below.

[0090] In the embodiment of the present application, a scheduling configuration method is provided and explained from the network device side.

[0091] FIG. 3 is a schematic diagram of a scheduling setting method according to an embodiment of the present application. As shown in FIG. 3, the method includes: 301: A network device receives capability indication information sent by a terminal device, the capability indication information indicating that the terminal device is capable of receiving multiple PDSCHs in one slot; and 302: The network device does not send enable time domain bundling configuration information to the terminal device, and / or does not send first indication information for configuring a PDSCH time domain resource allocation table to the terminal device.

[0092] In some embodiments, when the network device receives the capability indication information in 301, the capability indication information indicates that the terminal device can (is capable of) receiving multiple PDSCHs in one slot (or indicates that the terminal device is capable of receiving multiple PDSCHs in one slot). In this case, the network device cannot configure multi-PDSCH scheduling and / or time domain bundling, i.e., the network device does not transmit first indication information for configuring enabled time domain bundling configuration information and / or a PDSCH time domain resource allocation table to the terminal device. In other words, only when the network device has not received the capability indication information (when the terminal device cannot (is not capable of) receiving multiple PDSCHs in one slot), the network device can configure multi-PDSCH scheduling and / or time domain bundling, i.e., the network device may transmit first indication information for configuring enabled time domain bundling configuration information and / or a PDSCH time domain resource allocation table to the terminal device.

[0093] For example, if the terminal device can receive (has the capability to receive) multiple PDSCHs in one slot (or indicates the capability to receive multiple PDSCHs in one slot), the network device cannot configure multi-PDSCH scheduling and / or time domain bundling, i.e., the network device does not transmit the first indication information and / or the enabled time domain bundling information.

[0094] Furthermore, for example, if the terminal device can receive (has the capability to receive) multiple PDSCHs in one slot (or indicates the capability to receive multiple PDSCHs in one slot) and multi-PDSCH scheduling is configured in the network device, the network device cannot configure time domain bundling, i.e., the network device transmits first indication information but does not transmit enabled time domain bundling information.

[0095] In some embodiments, the network device transmits enableTimeDomainHARQ-Bundling (enable time domain bundling configuration information) through RRC signaling, and indicates that time domain bundling is configured in the terminal device when the network device receives the enable time domain bundling configuration information. If the network device does not transmit the enable time domain bundling configuration information, it indicates that time domain bundling is not configured in the terminal device.

[0096] In some embodiments, the network device transmits first indication information pdsch-TimeDomainAllocationListForMultiPDSCH via RRC signaling, the first indication information being for configuring a time domain resource allocation table supporting scheduling of multiple PDSCHs using one DCI. Receiving the first indication information indicates that multi-PDSCH scheduling is configured for the terminal device. Not transmitting the first indication information from the network device indicates that multi-PDSCH scheduling is not configured for the terminal device.

[0097] In some embodiments, when a time domain resource allocation table is configured to support scheduling of multiple PDSCHs by one DCI, the TDRA table applies / corresponds to DCI format 1_1.

[0098] As can be seen from the above embodiments, when one DCI schedules multiple PDSCHs and / or supports the configuration of time domain bundling, it is clear that it does not support transmitting / receiving multiple PDSCHs in one slot. Therefore, when one DCI schedules multiple PDSCHs and / or supports the configuration of time domain bundling, it can avoid a situation where the network device transmits multiple PDSCHs in one slot but the terminal device cannot receive and / or feed back corresponding HARQ-ACK information, thereby avoiding unnecessary retransmissions and wasting resources.

[0099] Example of the third aspect In the embodiment of the present application, a scheduling setting method is provided, and is described from the terminal device side, where the overlapping parts with the embodiment of the second aspect are omitted.

[0100] FIG. 4 is a schematic diagram of a scheduling setting method according to an embodiment of the present application. As shown in FIG. 4, the method includes: 401: A terminal device sends capability indication information to a network device to indicate that the terminal device is capable of receiving multiple PDSCHs in one slot; and 402: The terminal device does not receive enable time domain bundling configuration information configured by the network device, and / or the network device does not receive first indication information for configuring a PDSCH time domain resource allocation table.

[0101] In some examples, the embodiments 401-402 correspond to the embodiments 301-302 in the second aspect, and redundant explanations will be omitted.

[0102] In some embodiments, if a terminal device is capable of receiving multiple PDSCHs in one time slot (or if the terminal device indicates an ability to receive multiple PDSCHs in one time slot), the network device cannot configure multi-PDSCH scheduling and / or time domain bundling for the terminal device, i.e., in such a case, the terminal device does not receive (does not want to receive (does not expect to receive) first indication information for configuring enabled time domain bundling configuration information and / or a PDSCH time domain resource allocation table transmitted from the network device. That is, the network device can configure multi-PDSCH scheduling and / or time domain bundling for the terminal device only if the terminal device is not capable of receiving multiple PDSCHs in one slot. That is, the terminal device can receive first indication information for configuring enabled time domain bundling configuration information and / or a PDSCH time domain resource allocation table transmitted from the network device.

[0103] For example, if a terminal device is capable of receiving multiple PDSCHs in one slot (or indicates the ability to receive multiple PDSCHs in one slot), multi-PDSCH scheduling and / or time domain bundling is not configured for the terminal device by the network device, i.e., enabled time domain bundling information and / or first indication information is not received.

[0104] Furthermore, for example, if a terminal device can receive (has the capability to receive) multiple PDSCHs in one slot (or indicates the capability to receive multiple PDSCHs in one slot) and multi-PDSCH scheduling is configured for the terminal device, time domain bundling is not configured for the terminal device by the network device, i.e., the terminal device receives first indication information but does not receive enabled time domain bundling information.

[0105] The embodiments of the enabled time domain bundling configuration and the first indication information can refer to the examples of the second aspect, and the description thereof will be omitted here.

[0106] In some embodiments, if the network device configures multi-PDSCH scheduling and / or time domain bundling, the method may further include the terminal device determining a candidate PDSCH receive timing set and generating a corresponding HARQ feedback codebook, where the method for determining the candidate PDSCH receive timing set in the existing Rel17 may be reused or the method for determining the candidate PDSCH receive timing set in the embodiments of the first aspect may be used, but the specific methods are as described above and will not be described again.Furthermore, generating the corresponding HARQ feedback codebook may reuse the existing Rel17 method or use the method in the embodiments of the sixth aspect, but will not be described again.

[0107] As can be seen from the above embodiments, when one DCI schedules multiple PDSCHs and / or supports the configuration of time domain bundling, it is clear that it does not support transmitting / receiving multiple PDSCHs in one slot. Therefore, when one DCI schedules multiple PDSCHs and / or supports the configuration of time domain bundling, it can avoid a situation where the network device transmits multiple PDSCHs in one slot but the terminal device cannot receive and / or feed back corresponding HARQ-ACK information, thereby avoiding unnecessary retransmissions and wasting resources.

[0108] Note that the above Figures 2 to 4 merely provide a rough description of the embodiments of the present application, and the present application is not limited thereto. For example, the execution procedure between each operation can be appropriately adjusted, and further, some other operations may be added or some operations may be omitted. Those skilled in the art are not limited to the description of the above Figures 2 to 4, and can make appropriate modifications in accordance with the above content.

[0109] The above-described various embodiments are merely illustrative of the embodiments of the present application, and the present application is not limited thereto. Appropriate modifications may be made based on the above-described various embodiments. For example, the above-described various embodiments may be used individually, or one or more of the above-described various embodiments may be combined.

[0110] Example of the fourth aspect In the embodiment of the present application, a scheduling configuration method is provided and explained from the network device side.

[0111] FIG. 6 is a schematic diagram of a scheduling setting method according to an embodiment of the present application. As shown in FIG. 6, the method includes: 601: A network device sends enable time domain bundling configuration information to the terminal device; and 602: The network device sends downlink control information to the terminal device, the downlink control information scheduling one PDSCH or scheduling multiple PDSCHs having multiple valid PDSCHs.

[0112] In some embodiments, in 601, the network device transmits enableTimeDomainHARQ-Bundling (enable time domain bundling configuration information) by RRC signaling, and upon receiving the enable time domain bundling configuration information, indicates that time domain bundling is configured in the terminal device.

[0113] In some embodiments, in 602, the DCI includes a first information field, which may be a time domain resource assignment, and the first information field indicates a PDSCH time domain resource by indicating an index (row index, e.g., the value of the row index is 1 or more) corresponding to a PDSCH TDRA setting in a PDSCH TDRA table to which the DCI applies. In other words, the DCI schedules a PDSCH by indicating a PDSCH TDRA setting in a PDSCH TDRA table to which the DCI applies, hereinafter referred to as a DCI-scheduled PDSCH, i.e., a DCI-indicated PDSCH. For example, a value m (assuming m is an integer 0 or more) of the first information field of the DCI corresponds to a PDSCH TDRA setting indicating that the index m+1 (i.e., the m+1th row) in the PDSCH TDRA table to which the DCI applies is

[0114] In some embodiments, the PDSCH TDRA table may be predefined or configured by higher layer signaling, and the table supports scheduling multiple PDSCHs by one DCI, or one or more rows of the table include multiple time domain resource configurations (SLIVs). For example, if time domain bundling is configured (for example, if the enable time domain bundling configuration information is sent in 601), the table supports scheduling multiple PDSCHs by one DCI, but when the DCI applies the table, it may indicate / schedule only one PDSCH (for example, the row of the TDRA table indicated by the first information field in the DCI includes only one SLIV), or it may indicate / schedule multiple PDSCHs (for example, the row of the TDRA table indicated by the first information field in the DCI includes multiple SLIVs), among which there are multiple valid PDSCHs; in other words, the DCI cannot indicate / schedule multiple PDSCHs, among which there is only one valid PDSCH. That is, the network device indicates / schedules multiple PDSCHs and does not transmit DCI with only one valid PDSCH to the terminal device.

[0115] As can be seen from the above embodiments, when time domain bundling is configured, it is not supported that multiple PDSCHs are indicated / scheduled via one physical downlink control channel (PDCCH) and only one PDSCH is valid; when time domain bundling is configured, the base station indicates / schedules multiple PDSCHs via one physical downlink control channel (PDCCH), but only one PDSCH is valid, so that the terminal device does not receive and / or feed back corresponding HARQ-ACK information, thereby avoiding unnecessary retransmission and resource waste.

[0116] Example of the fifth aspect In the embodiments of the present application, a scheduling setting method is provided, and the description will be given from the terminal device side, and the description overlapping with the embodiments of the fourth aspect will be omitted.

[0117] FIG. 7 is a schematic diagram of a scheduling setting method according to an embodiment of the present application. As shown in FIG. 7, the method includes: 701: A terminal device receives enable time domain bundling configuration information sent from a network device; and 702: The terminal device receives downlink control information, transmitted from the network device, for scheduling one PDSCH or for scheduling multiple PDSCHs including the multiple valid PDSCHs.

[0118] In some examples, the embodiments 701 to 702 correspond to 601 to 602 in the fourth aspect example, and overlapping explanations will be omitted.

[0119] In some embodiments, when time domain bundling is configured (when the enabled time domain bundling configuration information is received in 701), the one DCI may indicate / schedule only one PDSCH (e.g., the row of the TDRA table indicated by the first information field in the DCI includes only one SLIV), or may indicate / schedule multiple PDSCHs (e.g., the row of the TDRA table indicated by the first information field in the DCI includes multiple SLIVs), among which there are multiple valid PDSCHs. In other words, the DCI cannot indicate / schedule multiple PDSCHs, among which there is only one valid PDSCH. That is, the terminal device does not receive (is not expected to receive) a DCI that indicates / schedules multiple PDSCHs and has only one valid PDSCH.

[0120] In some embodiments, if the network device configures time domain bundling, the method may further include the terminal device determining a candidate PDSCH receive timing set and generating a corresponding HARQ feedback codebook. Specifically, the terminal device may reuse the existing Rel17 method for determining the candidate PDSCH receive timing set or use the method for determining the candidate PDSCH receive timing set in the embodiments of the first aspect, but the specific methods are as described above and will not be described here. Furthermore, the terminal device may reuse the existing Rel17 method or use the method in the embodiments of the sixth aspect for generating the corresponding HARQ feedback codebook, but the specific methods are not described here.

[0121] As can be seen from the above embodiments, when time domain bundling is configured, it is not supported that multiple PDSCHs are indicated / scheduled via one physical downlink control channel (PDCCH) and only one PDSCH is valid; when time domain bundling is configured, the base station indicates / schedules multiple PDSCHs via one physical downlink control channel (PDCCH), but only one PDSCH is valid, so that the terminal device does not receive and / or feed back corresponding HARQ-ACK information, thereby avoiding unnecessary retransmission and resource waste.

[0122] Example of the sixth aspect According to the methods in the embodiments of the fourth and fifth aspects, when time domain bundling is configured, multiple PDSCHs are indicated / scheduled via one physical downlink control channel (PDCCH) and only one active PDSCH is not supported, whereas in the embodiment of the sixth aspect, when time domain bundling is configured, multiple PDSCHs are indicated / scheduled via one physical downlink control channel (PDCCH) and only one active PDSCH is supported, and it is clear whether / how to support associating one candidate PDSCH reception timing with multiple PDSCHs scheduled with different DCIs or different methods, and to provide corresponding HARQ-ACK information feedback, which will be described in detail below.

[0123] In the embodiment of the present application, an information feedback method is provided and explained from the terminal device side.

[0124] FIG. 8 is a schematic diagram of an information feedback method according to an embodiment of the present application. As shown in FIG. 8, the method includes: 801: A terminal device determines a candidate PDSCH reception timing set; and 802: The terminal device determines a bit of HARQ-ACK information in a HARQ-ACK codebook based on the number of scheduled PDSCHs and / or the number of scheduled valid PDSCHs, and transmits a codebook including HARQ-ACK information corresponding to the candidate PDSCH reception timing set.

[0125] In some embodiments, in 801, the terminal device may reuse the method for determining the candidate PDSCH reception timing set in the existing Rel17, or may use the method for determining the candidate PDSCH reception timing set in the embodiments of the first aspect, but the specific method is as described above and will not be described here.

[0126] In some embodiments, when determining the candidate PDSCH reception timing set, the HARQ-ACK information bits corresponding to each candidate PDSCH reception timing may be arranged in the order of the second candidate PDSCH reception timings in the candidate PDSCH reception timing set, thereby obtaining the HARQ-ACK information bits of one serving cell. As described above, when the codebook includes the HARQ-ACK information bits of one serving cell, the HARQ-ACK information bits of the one serving cell are fed back as the codebook. When the codebook includes the HARQ-ACK information bits of multiple serving cells, the method of determining the HARQ-ACK information bits of each serving cell is the same as the method of determining the HARQ-ACK information bits of one serving cell. However, when specifically determining the HARQ-ACK information bits, other parameters such as PDSCH TDRA configuration corresponding to each serving cell may be the same or different. For example, the above parameters may be individually set for each serving cell, but this embodiment is not limited thereto. The bits of HARQ-ACK information corresponding to each serving cell may be arranged in ascending order of the serving cell index to generate a codebook for feedback.

[0127] In some embodiments, at 802, the scheduled PDSCH includes DCI and / or an SPS scheduled PDSCH.

[0128] Hereinafter, it will be described how to determine the bit value of the HARQ-ACK information corresponding to one candidate PDSCH reception timing.

[0129] In some embodiments, for one candidate PDSCH reception timing among the set of candidate PDSCH reception timings, the terminal device determines a bit of HARQ-ACK information corresponding to the one candidate PDSCH reception timing based on the number of scheduled PDSCHs associated with the one candidate PDSCH reception timing and / or the number of valid PDSCHs associated with the one candidate PDSCH reception timing.

[0130] In some embodiments, when the number of scheduled PDSCHs and / or the number of associated valid PDSCHs associated with the one candidate PDSCH reception timing is 1, the bits of HARQ-ACK information corresponding to the one candidate PDSCH reception timing are equal to the bits of HARQ-ACK information corresponding to the associated number of scheduled PDSCHs and / or the associated valid PDSCHs.

[0131] In some embodiments, when the number of scheduled PDSCHs and / or the number of associated valid PDSCHs associated with the one candidate PDSCH reception timing are plural, the bit of HARQ-ACK information corresponding to the one candidate PDSCH reception timing is equal to the logical sum of the bits of HARQ-ACK information corresponding to the number of associated scheduled PDSCHs and / or the associated valid PDSCHs.

[0132] This supports the situation where multiple PDSCHs are indicated / scheduled via one physical downlink control channel (PDCCH) and only one PDSCH is active.

[0133] In some embodiments, PDSCHs or valid PDSCHs associated with the same candidate PDSCH reception timing are scheduled by the same DCI, for example, when there are multiple valid PDSCHs associated with the same candidate PDSCH reception timing, all of the multiple valid PDSCHs are scheduled by the same DCI, that is, it is not supported that multiple PDSCHs are associated with one candidate PDSCH reception timing and the multiple PDSCHs are scheduled by different DCIs or in different ways.

[0134] For example, when a terminal device indicates / schedules multiple PDSCHs for one candidate PDSCH reception timing and receives DCI with only one valid PDSCH among them, the bit value corresponding to the one candidate PDSCH reception timing in the HARQ-ACK codebook is the bit of HARQ-ACK information corresponding to the valid PDSCH.When a terminal device indicates / schedules multiple PDSCHs and receives DCI with multiple valid PDSCHs among them, the bit value corresponding to the one candidate PDSCH reception timing in the HARQ-ACK codebook is the logical sum of the bits of HARQ-ACK information corresponding to the multiple valid PDSCHs.

[0135] The following explains this together with pseudocode example 1.

[0136] [Table 5] TIFF0007823761000007.tif249170 TIFF0007823761000008.tif232170 TIFF0007823761000009.tif219170 That is, when time domain bundling is configured, it is determined in turn whether to configure harq-ACK-SpatialBundlingPUCCH and PDSCH-CodeBlockGroupTransmission, etc., and under different configuration assumptions, it is determined whether multiple PDSCHs are associated with one candidate PDSCH reception timing, and whether there are multiple valid PDSCHs or one valid PDSCH, and when there are multiple valid PDSCHs in the HARQ-ACK codebook, the bit value corresponding to this one candidate PDSCH reception timing is the logical sum of the HARQ-ACK information bits corresponding to the multiple valid PDSCHs; otherwise, when there is one valid PDSCH, the bit value corresponding to this one candidate PDSCH reception timing is the HARQ-ACK information bit corresponding to the valid PDSCH.

[0137] The following explains this with pseudocode example 2.

[0138] [Table 6] TIFF0007823761000011.tif239170 TIFF0007823761000012.tif238170 TIFF0007823761000013.tif78170 That is, when time domain bundling is configured, multiple PDSCHs are associated with one candidate PDSCH reception timing, and the multiple PDSCHs are scheduled by one DCI. Under this premise, it is determined in order whether to configure harq-ACK-SpatialBundlingPUCCH, PDSCH-CodeBlockGroupTransmission, etc., and when there are multiple valid PDSCHs in the HARQ-ACK codebook, the bit value corresponding to the one candidate PDSCH reception timing is equal to the logical OR of the HARQ-ACK information bits corresponding to the multiple valid PDSCHs. Otherwise, when there is only one valid PDSCH associated with the one candidate PDSCH reception timing, the bit value corresponding to the one candidate PDSCH reception timing is equal to the HARQ-ACK information bit corresponding to the valid PDSCH.

[0139] As can be seen from the above embodiment, a situation in which multiple PDSCHs are associated with one candidate PDSCH reception timing and the multiple PDSCHs are scheduled with different DCIs or different methods is not supported, that is, a situation in which multiple PDSCHs are associated with one candidate PDSCH reception timing and the multiple PDSCHs are scheduled with the same DCI is only supported. This avoids a situation in which a terminal device cannot receive and / or feed back corresponding HARQ-ACK information when multiple PDSCHs are associated with one candidate PDSCH reception timing and the multiple PDSCHs are scheduled with different DCIs or different methods, thereby avoiding unnecessary retransmission and resource waste.

[0140] In some embodiments, when multiple PDSCHs are associated with one candidate PDSCH reception timing and the multiple PDSCHs are scheduled with different DCIs or in different ways, it may be possible to support a situation in which corresponding HARQ-ACK information feedback is performed, as will be described in detail below.

[0141] For example, multiple PDSCHs associated with the same candidate PDSCH reception timing or multiple associated valid PDSCHs are scheduled by different DCIs, or some of them are scheduled by DCIs and some of them are SPS PDSCHs (configured by SPS and activated by DCIs), and the bit of HARQ-ACK information corresponding to one candidate PDSCH reception timing is equal to the logical OR of the bits of HARQ-ACK information corresponding to the associated multiple PDSCHs or multiple associated valid PDSCHs.

[0142] For example, if one or more SPS PDSCHs are included in the multiple PDSCHs associated with the same candidate PDSCH reception timing, the PDSCH associated with the one candidate PDSCH reception timing includes a PDSCH scheduled by DCI. That is, if there is one candidate PDSCH reception timing associated with one or more SPS PDSCHs, there is no need to re-schedule the PDSCH associated with the one candidate PDSCH reception timing by DCI, and all of the multiple PDSCHs associated with the one candidate PDSCH reception timing are SPS PDSCHs. When one SPS PDSCH is associated with one candidate PDSCH reception timing, the bit of the HARQ-ACK information corresponding to the one candidate PDSCH reception timing is equal to the bit of the HARQ-ACK information corresponding to the one SPS PDSCH, and when multiple SPS PDSCHs are associated with one candidate PDSCH reception timing, the bit of the HARQ-ACK information corresponding to the multiple SPS PDSCHs is equal to the logical OR of the bits of the HARQ-ACK information corresponding to the multiple SPS PDSCHs. The multiple SPS PDSCHs may correspond to the same or different SPS configurations and / or may be activated by different DCIs. This example can avoid the scenario of Figure 5C.

[0143] For example, if one or more SPS PDSCHs are included in the multiple PDSCHs associated with the same candidate PDSCH reception timing, the PDSCH associated with the one candidate PDSCH reception timing may include a PDSCH scheduled by a DCI. In other words, if there is one candidate PDSCH reception timing associated with one or more SPS PDSCHs, when a terminal device receives DCI for scheduling one or more PDSCHs associated with the one candidate PDSCH reception timing, the terminal device does not receive the SPS PDSCH (in other words, the terminal device cancels reception of the SPS PDSCH). In other words, the multiple PDSCHs associated with the one candidate PDSCH reception timing include an SPS PDSCH and a PDSCH scheduled by DCI, but there is no need to feed back HARQ feedback information for the SPS PDSCH, and the bit of the HARQ-ACK information corresponding to the one candidate PDSCH reception timing is equal to the bit of the HARQ-ACK information corresponding to the PDSCH scheduled by the DCI or the bit OR of the HARQ-ACK information. For example, when the DCI schedules one PDSCH, the bit of the HARQ-ACK information corresponding to the one candidate PDSCH reception timing is equal to the bit of the HARQ-ACK information corresponding to the PDSCH scheduled by the DCI, and when the DCI schedules multiple PDSCHs, the bit of the HARQ-ACK information corresponding to the one candidate PDSCH reception timing is equal to the bit OR of the HARQ-ACK information corresponding to the multiple PDSCHs scheduled by the DCI.

[0144] Wherein, the SPS PDSCH is located before, after, or between the PDSCH scheduled by the DCI in the time domain, and the HARQ process ID corresponding to the SPS PDSCH is different from the HARQ process ID of the PDSCH scheduled by the DCI or is the same as the HARQ process ID of one of the PDSCHs scheduled by the DCI.

[0145] In the above example, the method further includes the terminal device receiving one or more DCIs for scheduling PDSCH and / or one or more DCIs for activating SPS. The above examples may be implemented independently or in combination, and the embodiments of the present application are not limited thereto.

[0146] In some embodiments, the method further includes the terminal device receiving DCI for deactivating an SPS, and the terminal device further needs to determine HARQ-ACK information for the DCI, where a bit of the HARQ-ACK information for feeding back the DCI in the codebook is a bit of HARQ-ACK information corresponding to a candidate PDSCH reception timing associated with an SPS PDSCH corresponding to an SPS to be deactivated by the DCI, or a bit of the HARQ-ACK information for feeding back the DCI in the codebook is a bit of HARQ-ACK information corresponding to a candidate PDSCH reception timing associated with an SPS PDSCH corresponding to an SPS with a smallest index among the multiple deactivated SPSs.

[0147] For example, if the terminal device needs to further upload HARQ-ACK information of another DCI and / or PDSCH, the bit (position) of the HARQ-ACK information for feeding back the DCI in the codebook is equal to the bit (position) of the HARQ-ACK information corresponding to the candidate PDSCH reception timing associated with the SPS PDSCH corresponding to the deactivated SPS. If the DCI is used to deactivate multiple SPSs, the bit of the HARQ-ACK information for feeding back the DCI in the codebook is equal to the bit of the HARQ-ACK information corresponding to the candidate PDSCH reception timing associated with the SPS PDSCH corresponding to the SPS with the smallest index among the multiple deactivated SPSs.

[0148] In some embodiments, the method further includes the terminal device receiving enable time domain bundling configuration information sent from the network device (not shown). The network device transmits enableTimeDomainHARQ-Bundling (enable time domain bundling configuration information) through RRC signaling, and upon receiving the enable time domain bundling configuration information, indicates that time domain bundling is configured in the terminal device, and generates the codebook using the above method only if time domain bundling is configured in the terminal device.

[0149] In some embodiments, the method for transmitting the codebook can refer to the embodiments of the first aspect, and the description thereof will be omitted here.

[0150] As can be seen from the above embodiment, when multiple PDSCHs are associated with one candidate PDSCH reception timing and the multiple PDSCHs are scheduled with different DCIs or in different methods, a situation in which corresponding HARQ-ACK information feedback is performed may be supported. This avoids a situation in which a terminal device cannot receive and / or feed back corresponding HARQ-ACK information when multiple PDSCHs are associated with one candidate PDSCH reception timing and the multiple PDSCHs are scheduled with different DCIs or in different methods, thereby avoiding unnecessary retransmission and resource waste.

[0151] Example of the seventh aspect In an embodiment of the sixth aspect, even when time domain bundling is configured, configuring and / or activating SPS is still supported, and a situation in which multiple PDSCHs are associated with one candidate PDSCH reception timing and the multiple PDSCHs are scheduled in different ways may be supported. In contrast, in an embodiment of the seventh aspect, configuring and / or activating SPS is not supported when time domain bundling is configured.

[0152] In the embodiment of the present application, an information setting method is provided and explained from the network device side.

[0153] FIG. 9 is a schematic diagram of an information setting method according to an embodiment of the present application. As shown in FIG. 9, the method includes: 901: A network device sends enable time domain bundling configuration information to the terminal device; and 902: The network device does not send SPS setting information to the terminal device and / or does not send DCI for activating SPS to the terminal device.

[0154] In some embodiments, activation of the DCI to activate the SPS must satisfy the following conditions:

[0155] 1) The CRC of the DCI is scrambled with the CS-RNTI.

[0156] 2) The value of the new data indication field in the DCI becomes 0.

[0157] 3) If the DCI includes a PDSCH-to-HARQ_feedback timing indicator field, the PDSCH-to-HARQ_feedback timing indicator field does not provide an inapplicable value for dl-DataToUL-ACK-r16. (The HARQ feedback may not exist. If it does not exist or if dl-DataToUL-ACK-r16 does not contain an inappropriate value, condition 3 does not need to be considered.) When a single SPS configuration is provided to a terminal device, the DCI for SPS activation must further satisfy the following condition: all bits in the HARQ process number field have a value of 0 (i.e., this field is filled entirely with '0's), and all bits in the redundancy version field (or, if the DCI format is DCI format 1_1, all bits of enabled TBs in the redundancy version field) have a value of 0 (i.e., if the DCI format is DCI format 1_1, all bits for enabled TBs in the redundancy version field have a value of 0 (i.e., this field is filled entirely with '0's). When multiple SPS configurations are provided to a terminal device, the DCI for SPS activation must further satisfy the following condition: all bits in the redundancy version field (or, if the DCI format is DCI format 1_1, all bits of enabled TBs in the redundancy version field) have a value of 0 (i.e., this field is filled entirely with '0's).

[0158] In some embodiments, the SPS setting information SPS-Config includes an SPS cycle periodicity, a PDSCH repetition count pdsch-AggregationFactor, a number of HARQ processes nrofHARQ-Processes, and an offset between HARQ process IDs harq-ProcID-Offset, and may further include other SPS settings, specifically, reference may be made to prior art, and description thereof will be omitted here.

[0159] In some embodiments, in 901, the network device transmits enableTimeDomainHARQ-Bundling (enable time domain bundling configuration information) by RRC signaling, and upon receiving the enable time domain bundling configuration information, it indicates that time domain bundling is configured in the terminal device. If time domain bundling is configured in the terminal device, the network device cannot configure and / or activate SPS, so in 902, the network device does not transmit the SPS configuration information to the terminal device and / or does not transmit the DCI for activating SPS to the terminal device.

[0160] As can be seen from the above embodiments, when time domain bundling is configured, configuring and / or activating SPS is not supported, and a situation in which multiple PDSCHs are associated with one candidate PDSCH reception timing and the multiple PDSCHs are scheduled in different ways is not supported. This avoids a situation in which a terminal device cannot receive and / or feed back corresponding HARQ-ACK information when multiple PDSCHs are associated with one candidate PDSCH reception timing and the multiple PDSCHs are scheduled with different DCIs or in different ways, thereby avoiding unnecessary retransmission and resource waste.

[0161] Example of the eighth aspect In the embodiment of the present application, an information setting method is provided, and the explanation is given from the terminal device side, and the explanation overlapping with the embodiment of the seventh aspect will be omitted.

[0162] FIG. 10 is a schematic diagram of an information setting method according to an embodiment of the present application. As shown in FIG. 10, this method includes: 1001: A terminal device receives enable time domain bundling configuration information; and 1002: The terminal device does not receive SPS configuration information and / or DCI for activating SPS.

[0163] In some examples, the embodiments 1001 to 1002 correspond to 901 to 902 in the examples of the seventh aspect, and overlapping explanations will be omitted.

[0164] In some embodiments, in 1001, the network device transmits enableTimeDomainHARQ-Bundling (enable time-domain bundling configuration information) by RRC signaling. Receiving the enable time-domain bundling configuration information indicates that time-domain bundling is configured in the terminal device. When time-domain bundling is configured in the terminal device, the network device cannot configure and / or activate SPS, and the terminal device does not receive (does not want to receive) SPS configuration information and / or does not send DCI for activating SPS to the terminal device. For the SPS configuration information and / or DCI for activating SPS, refer to the embodiments of the seventh aspect, and description thereof will be omitted here.

[0165] In some embodiments, if the network device configures time domain bundling, the method may further include the terminal device determining a candidate PDSCH receive timing set and generating a corresponding HARQ feedback codebook, where the method for determining the candidate PDSCH receive timing set in the existing Rel17 may be reused or the method for determining the candidate PDSCH receive timing set in the embodiments of the first aspect may be used, but the specific method is as described above and will not be described here. Furthermore, generating the corresponding HARQ feedback codebook may reuse the method in the existing Rel17 or may use some of the methods in the embodiments of the sixth aspect, but will not be described here.

[0166] As can be seen from the above embodiments, when time domain bundling is configured, configuring and / or activating SPS is not supported, and a situation in which multiple PDSCHs are associated with one candidate PDSCH reception timing and the multiple PDSCHs are scheduled in different ways is not supported. This avoids a situation in which a terminal device cannot receive and / or feed back corresponding HARQ-ACK information when multiple PDSCHs are associated with one candidate PDSCH reception timing and the multiple PDSCHs are scheduled with different DCIs or in different ways, thereby avoiding unnecessary retransmission and resource waste.

[0167] Example of the ninth aspect In the embodiment of the present application, an information feedback method is provided and explained from the terminal device side.

[0168] FIG. 11 is a schematic diagram of an information feedback method according to an embodiment of the present application. As shown in FIG. 11, the method includes: 1101: A terminal device determines a candidate PDSCH receiving timing set; 1102: The terminal device receives a DCI for deactivating SPS; 1103: The terminal device determines a bit of HARQ-ACK information in a HARQ-ACK codebook, and sends the codebook, where all bits of the codebook are HARQ-ACK information of the DCI; or The bit of the HARQ-ACK information for feeding back the DCI in the codebook is the bit of the HARQ-ACK information corresponding to the candidate PDSCH reception timing associated with the SPS PDSCH corresponding to the SPS deactivated by the DCI, or The bit of the HARQ-ACK information for feeding back the DCI in the codebook is the bit of the HARQ-ACK information corresponding to the candidate PDSCH reception timing associated with the SPS PDSCH corresponding to the SPS with the smallest index among the multiple deactivated SPSs.

[0169] In some examples, the embodiment of 1101 may refer to the example of the sixth aspect, but redundant explanations will be omitted.

[0170] For example, if the terminal device only needs to upload the HARQ-ACK information of the above DCI for deactivating SPS (i.e., the terminal device only receives the DCI), then each of all bits included in the codebook = the HARQ-ACK information of the DCI.

[0171] For example, if the terminal device needs to further upload HARQ-ACK information of another DCI and / or PDSCH, the bit (position) of the HARQ-ACK information for feeding back the DCI in the codebook is equal to the bit (position) of the HARQ-ACK information corresponding to the candidate PDSCH reception timing associated with the SPS PDSCH corresponding to the deactivated SPS. If the DCI is used to deactivate multiple SPSs, the bit of the HARQ-ACK information for feeding back the DCI in the codebook is equal to the bit of the HARQ-ACK information corresponding to the candidate PDSCH reception timing associated with the SPS PDSCH corresponding to the SPS with the smallest index among the multiple deactivated SPSs.

[0172] In some embodiments, the method further includes the terminal device receiving enable time domain bundling configuration information sent from the network device (not shown). The network device transmits enableTimeDomainHARQ-Bundling (enable time domain bundling configuration information) through RRC signaling, and upon receiving the enable time domain bundling configuration information, indicates that time domain bundling is configured in the terminal device, and generates the codebook using the above method only if time domain bundling is configured in the terminal device.

[0173] In some embodiments, the method for transmitting the codebook can refer to the embodiments of the first aspect, and the description thereof will be omitted here.

[0174] Example of the 10th aspect In an embodiment of the present application, an information feedback device is provided, which may be, for example, a terminal device, or one or a part of a component or assembly disposed in the terminal device, and the same content as in the embodiment of the first aspect is omitted.

[0175] FIG. 12 is another schematic diagram of an information feedback device according to an embodiment of the present application. As shown in FIG. 12, the information feedback device 1200 includes: a first determining unit 1201, which determines a set of candidate PDSCH reception timings according to whether time domain bundling is configured, and / or whether multi-PDSCH scheduling is configured, and / or whether a subcarrier spacing of a downlink BWP is configured, and / or whether there is a capability to receive multiple PDSCHs in one slot; and a first processing unit 1202 for generating and sending a HARQ-ACK codebook including HARQ-ACK information corresponding to the candidate PDSCH receiving timing set.

[0176] In some embodiments, the first determination unit 1201 and the first processing unit 1202 may be implemented by referring to 201-202 in the first aspect of the invention, and redundant explanations will be omitted.

[0177] If time domain bundling is configured, the first determining unit adds one PDSCH receiving timing to the set of candidate PDSCH receiving timings.

[0178] In some embodiments, when time domain bundling is not configured and the terminal device is capable of receiving multiple PDSCHs in one slot, the first determination unit adds one candidate PDSCH reception timing or multiple candidate PDSCH reception timings to the candidate PDSCH reception timing set based on the number of mutually independent PDSCH time domain resource configurations in the first allocation table.

[0179] In an embodiment of the present application, a scheduling setting device is provided, which may be, for example, a terminal device, or may be one or a part of a component or assembly disposed in the terminal device, and the same content as in the embodiment of the third aspect is omitted.

[0180] FIG. 13 is another schematic diagram of a scheduling setting device according to an embodiment of the present application. As shown in FIG. 13, the scheduling setting device 1300 includes: a first sending unit 1301 for sending capability indication information to a network device to indicate that the terminal device is capable of receiving multiple PDSCHs in one slot; and a third processing unit 1302 when the network device does not receive the configured enable time domain bundling configuration information and / or when the network device does not receive the first indication information for configuring a PDSCH time domain resource allocation table.

[0181] In some embodiments, the first transmitting unit 1301 and the third processing unit 1302 may be implemented by referring to 401 to 402 in the embodiments of the third aspect, but redundant explanations will be omitted.

[0182] In an embodiment of the present application, a scheduling setting device is provided, which may be, for example, a terminal device, or one or a part of a component or assembly disposed in the terminal device, and the same content as in the embodiment of the fifth aspect is omitted.

[0183] FIG. 14 is another schematic diagram of a scheduling setting device according to an embodiment of the present application. As shown in FIG. 14, the scheduling setting device 1400 includes: a second receiving unit 1401 for receiving enable time domain bundling configuration information sent from a network device; and a third receiving unit 1402 for receiving downlink control information for scheduling one PDSCH or for scheduling multiple PDSCHs having multiple valid PDSCHs sent from the network device.

[0184] In some embodiments, the second receiving unit 1401 and the third receiving unit 1402 may be implemented by referring to 701 and 702 in the embodiments of the fifth aspect, but redundant explanations will be omitted.

[0185] In an embodiment of the present application, an information feedback device is provided, which may be, for example, a terminal device, or one or a part of a component or assembly disposed in the terminal device, and the same content as in the embodiment of the sixth aspect is omitted.

[0186] FIG. 15 is another schematic diagram of an information feedback device according to an embodiment of the present application. As shown in FIG. 15, the information feedback device 1500 includes: a second determining unit 1501 for determining a set of candidate PDSCH receive timings; and a fourth processing unit 1502 that determines bits of HARQ-ACK information in a HARQ-ACK codebook based on the number of scheduled PDSCHs and / or the number of scheduled valid PDSCHs, and transmits a codebook including HARQ-ACK information corresponding to the candidate PDSCH reception timing set.

[0187] In some embodiments, for one candidate PDSCH reception timing of the set of candidate PDSCH reception timings, the fourth processing unit determines a bit of HARQ-ACK information corresponding to the one candidate PDSCH reception timing based on the number of scheduled PDSCHs and / or the number of valid PDSCHs associated with the one candidate PDSCH reception timing.

[0188] In some embodiments, when the number of scheduled PDSCHs and / or the number of associated valid PDSCHs associated with the one candidate PDSCH reception timing is 1, the bits of HARQ-ACK information corresponding to the one candidate PDSCH reception timing are equal to the bits of HARQ-ACK information corresponding to the associated number of scheduled PDSCHs and / or the associated valid PDSCHs.

[0189] In some embodiments, when the number of scheduled PDSCHs and / or the number of associated valid PDSCHs associated with the one candidate PDSCH reception timing are multiple, the bit of HARQ-ACK information corresponding to the one candidate PDSCH reception timing is equal to the logical sum of the bits of HARQ-ACK information corresponding to the number of associated scheduled PDSCHs and / or the associated valid PDSCHs.

[0190] In some embodiments, PDSCHs associated with the same candidate PDSCH reception timing or valid PDSCHs are scheduled with the same DCI.

[0191] In some embodiments, multiple PDSCHs associated with the same candidate PDSCH reception timing, or multiple associated valid PDSCHs, are scheduled by different DCIs, or some are scheduled by DCIs and some are SPS PDSCHs.

[0192] In some embodiments, for one candidate PDSCH receive timing in the set of candidate PDSCH receive timings, the PDSCHs associated with the one candidate PDSCH receive timing include one or more SPS PDSCHs.

[0193] In some embodiments, the bit of HARQ-ACK information corresponding to the one candidate PDSCH reception timing is equal to the bit of HARQ-ACK information corresponding to the one SPS PDSCH or the logical sum of the bits of HARQ-ACK information corresponding to the multiple SPS PDSCHs.

[0194] In some embodiments, the multiple SPS PDSCHs correspond to the same or different SPS configurations and / or are activated by different DCIs.

[0195] In some embodiments, the PDSCH associated with the one candidate PDSCH reception timing does not include a PDSCH scheduled by DCI.

[0196] In some embodiments, the PDSCHs associated with the one candidate PDSCH reception timing further include one or more PDSCHs scheduled by DCI.

[0197] In some embodiments, the bit of HARQ-ACK information corresponding to the one candidate PDSCH reception timing is equal to the bit of HARQ-ACK information corresponding to the PDSCH scheduled by the DCI or the bit OR of the HARQ-ACK information.

[0198] In some embodiments, the device comprises: It further includes a fifth processing unit (not shown) that does not receive the SPS PDSCH.

[0199] In some embodiments, the SPS PDSCH is located before, after, or between the PDSCH scheduled by the DCI in the time domain.

[0200] In some embodiments, the HARQ process ID corresponding to the SPS PDSCH is different from the HARQ process ID of the PDSCH scheduled by the DCI, or is the same as the HARQ process ID of one of the PDSCHs scheduled by the DCI.

[0201] In some embodiments, the device comprises: It further includes a fourth receiving unit (not shown) for receiving one or more DCIs for scheduling the PDSCH and / or one or more DCIs for activating the SPS.

[0202] In some embodiments, the device comprises: a fifth receiving unit for receiving a DCI for deactivating the SPS; Wherein, the fourth processing unit is configured to: the bit of HARQ-ACK information for feeding back the DCI in the codebook is a bit of HARQ-ACK information corresponding to a candidate PDSCH reception timing associated with an SPS PDSCH corresponding to the SPS deactivated by the one DCI; or The HARQ-ACK information bit for feeding back DCI in the codebook is determined to be the HARQ-ACK information bit corresponding to the candidate PDSCH reception timing associated with the SPS PDSCH corresponding to the SPS with the smallest index among the multiple deactivated SPSs (not shown).

[0203] In some embodiments, the second determining unit determines the candidate PDSCH reception timing set based on whether time domain bundling is configured, and / or whether multi-PDSCH scheduling is configured, and / or whether subcarrier spacing of downlink BWP is configured, and / or whether there is a capability to receive multiple PDSCHs in one slot.

[0204] In some embodiments, the device comprises: The network device further includes a sixth receiving unit (not shown) for receiving the enabled time domain bundling setting information sent from the network device.

[0205] In some embodiments, the second determination unit 1501 and the fourth processing unit 1502 may be implemented by referring to 801 to 802 in the embodiment of the sixth aspect, but redundant explanations will be omitted.

[0206] In an embodiment of the present application, an information setting device is provided, which may be, for example, a terminal device, or may be one or a part of a component or assembly disposed in the terminal device, and the same content as in the embodiment of the eighth aspect is omitted.

[0207] FIG. 16 is another schematic diagram of an information setting device according to an embodiment of the present application. As shown in FIG. 16, the information setting device 1600 includes: a seventh receiving unit 1601 for receiving enable time domain bundling configuration information; and a seventh receiving unit 1602 that does not receive SPS configuration information and / or DCI for activating SPS.

[0208] In some embodiments, the seventh receiving unit 1601 and the seventh processing unit 1602 may refer to 1001 and 1002 in the embodiment of the eighth aspect, and redundant explanations will be omitted.

[0209] In an embodiment of the present application, an information feedback device is provided, which may be, for example, a terminal device, or one or a part of a component or assembly disposed in the terminal device, and the same content as in the embodiment of the ninth aspect is omitted.

[0210] FIG. 17 is another schematic diagram of an information feedback device according to an embodiment of the present application. As shown in FIG. 17, the information feedback device 1700 includes: a third determining unit 1701 for determining a set of candidate PDSCH receive timings; a seventh receiving unit 1702 for receiving a DCI for deactivating the SPS; an eighth processing unit 1703 for determining bits of HARQ-ACK information in a HARQ-ACK codebook and sending the codebook, where all bits of the codebook are HARQ-ACK information of the DCI; or The bit of the HARQ-ACK information for feeding back the DCI in the codebook is the bit of the HARQ-ACK information corresponding to the candidate PDSCH reception timing associated with the SPS PDSCH corresponding to the SPS deactivated by the DCI, or The bit of the HARQ-ACK information for feeding back the DCI in the codebook is the bit of the HARQ-ACK information corresponding to the candidate PDSCH reception timing associated with the SPS PDSCH corresponding to the SPS with the smallest index among the multiple deactivated SPSs.

[0211] In some embodiments, the device comprises: The network device further includes an eighth processing unit (not shown) for receiving the enabled time domain bundling setting information sent from the network device.

[0212] In some embodiments, the third determination unit 1701, the seventh receiving unit 1702, and the eighth processing unit 1703 may be implemented by referring to 1101 to 1103 in the embodiments of the ninth aspect, and redundant descriptions will be omitted.

[0213] As can be seen from the above embodiments, when time domain bundling is configured, it is clear whether / how to support transmission / reception of multiple PDSCHs in one slot, or whether / how to support one physical downlink control channel (PDCCH) indicating / scheduling multiple PDSCHs with only one valid PDSCH, or whether / how to support association of one candidate PDSCH reception timing with multiple PDSCHs scheduled by different DCIs or different methods, and the HARQ feedback method in the above cases is also clear. Therefore, the network device and the terminal device can similarly understand whether the above PDSCH scheduling is permitted, and if the above situation occurs when the network device schedules a PDSCH, the terminal device can correctly receive the scheduled PDSCH and / or feedback corresponding HARQ-ACK information, thereby avoiding unnecessary retransmission and resource waste.

[0214] Example of the eleventh aspect In an embodiment of the present application, a scheduling device is provided, which may be, for example, a network device, or may be one or a part of a component or assembly disposed in the network device, and the same content as in the embodiment of the second aspect is omitted.

[0215] FIG. 18 is another schematic diagram of a scheduling setting device according to an embodiment of the present application. As shown in FIG. 18, the scheduling setting device 1800: A first receiving unit 1801 receives capability indication information transmitted by a terminal device, the capability indication information indicating that the terminal device is capable of receiving multiple PDSCHs in one slot; and a second processing unit 1802 that does not send enabled time domain bundling configuration information to the terminal device and / or does not send first indication information for configuring a PDSCH time domain resource allocation table to the terminal device.

[0216] In some embodiments, the first receiving unit 1801 and the second processing unit 1802 may be implemented by referring to 301 to 302 in the second embodiment, and redundant explanations will be omitted.

[0217] In some embodiments, the PDSCH time domain resource allocation table supports scheduling multiple PDSCHs over one DCI.

[0218] In an embodiment of the present application, a scheduling device is provided, which may be, for example, a network device, or may be one or a part of a component or assembly disposed in the network device, and the same content as in the embodiment of the fourth aspect is omitted.

[0219] FIG. 19 is another schematic diagram of a scheduling setting device according to an embodiment of the present application. As shown in FIG. 19, the scheduling setting device 1900: a second sending unit 1901 for sending enabled time domain bundling configuration information to the terminal device; and a third transmitting unit 1902 for transmitting downlink control information for scheduling one PDSCH or for scheduling multiple PDSCHs having multiple valid PDSCHs to the terminal device.

[0220] In some embodiments, the second transmitting unit 1901 and the third transmitting unit 1902 may be implemented by referring to 601 and 602 in the embodiments of the fourth aspect, but redundant explanations will be omitted. In an embodiment of the present application, an information setting device is provided, which may be, for example, a network device, or may be one or a part of a component or assembly disposed in the network device, and the same content as in the embodiment of the seventh aspect is omitted.

[0221] FIG. 20 is another schematic diagram of an information setting device according to an embodiment of the present application. As shown in FIG. 20, the information setting device 2000 includes: a fourth sending unit 2001 for sending enabled time domain bundling configuration information to the terminal device; and a sixth processing unit 2002 that does not send SPS configuration information to the terminal device and / or does not send DCI for activating SPS to the terminal device.

[0222] In some embodiments, the fourth transmitting unit 2001 and the sixth processing unit 2002 may be implemented by referring to 801 to 802 in the seventh embodiment, but redundant explanations will be omitted.

[0223] As can be seen from the above embodiments, when time domain bundling is configured, it becomes clear whether / how to support transmission / reception of multiple PDSCHs in one slot, or whether / how to support one physical downlink control channel (PDCCH) indicating / scheduling multiple PDSCHs with only one active PDSCH, or whether / how to support association of one candidate PDSCH reception timing with multiple PDSCHs scheduled with different DCIs or in different ways, and the HARQ feedback method in the above cases also becomes clear.

[0224] The above-described various embodiments are merely illustrative of the embodiments of the present application, and the present application is not limited thereto. Appropriate modifications may be made based on the above-described various embodiments. For example, the above-described various embodiments may be used individually, or one or more of the above-described various embodiments may be combined.

[0225] Although the above describes only various components or modules related to the present application, the present application is not limited thereto. The devices 1200 to 2000 may further include other components or modules, and the specific contents of these components or modules may be found in the related art.

[0226] Furthermore, for the sake of simplicity, Figures 12 to 20 only exemplify the connection relationships or signal directions between various components or modules, but it will be apparent to those skilled in the art that various related technologies, such as bus connections, may also be applied. The various components or modules described above may be realized by hardware equipment, such as a processor, memory, transmitter, receiver, etc. The implementation of the present application is not limited thereto.

[0227] Example of the 12th aspect In an embodiment of the present application, a communication system is further provided, which may refer to FIG. 1, but the same contents as those in the embodiments of the first to eleventh aspects are omitted.

[0228] In some embodiments, the communication system 100 may include at least a terminal device 102 and a network device 101 .

[0229] In some embodiments, an embodiment of the terminal device 102 may refer to the terminal device 1100, and an embodiment of the network device may refer to the network device 100, and redundant descriptions will be omitted.

[0230] In the embodiment of the present application, a network device is further provided, which may be, for example, a base station, but the present application is not limited thereto and may be other network devices.

[0231] 21 is a schematic diagram of a network device according to an embodiment of the present application. As shown in FIG. 21, the network device 2100 may include a processor 2110 (e.g., a central processor CPU) and a memory 2120, which is coupled to the processor 2110. The memory 2120 can store various data, and further stores a program 2130 for information processing, and executes the program 2130 under the control of the processor 2110.

[0232] For example, the processor 2110 may be configured to execute a program to implement the methods described in the examples of the second, fourth and seventh aspects.

[0233] Furthermore, as shown in Fig. 21, the network device 2100 may further include a transceiver 2140, an antenna 2150, etc. Here, the functions of the above components are similar to those of the prior art, and the description thereof will be omitted here. Note that the network device 2100 does not need to include all the components shown in Fig. 21. Furthermore, the network device 2100 may further include components not shown in Fig. 21, and may refer to the prior art.

[0234] In the embodiment of the present application, a terminal device is further provided, but the present application is not limited thereto and may be other devices.

[0235] 22 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in FIG. 22, the terminal device 2200 may include a processor 2210 and a memory 2220, where the memory 2220 stores data and programs and is coupled to the processor 2210. It should be noted that the diagram is illustrative and that other types of structures may be used to supplement or replace the structures so as to realize telecommunication functions or other functions.

[0236] For example, the processor 2210 may be configured to execute a program to implement the methods described in the examples of the first, third, fifth, sixth, eighth and ninth aspects.

[0237] As shown in Fig. 22, the terminal device 2200 may further include a communication module 2230, an input unit 2240, a display 2250, and a power supply 2260. Here, the functions of the above components are similar to those of the prior art, and description thereof will be omitted here. Note that the terminal device 2200 does not need to include all of the components shown in Fig. 22, and the components are not essential. Furthermore, the terminal device 2200 may further include components not shown in Fig. 22, and prior art may be referenced.

[0238] In an embodiment of the present application, there is further provided a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to perform the methods described in the embodiments of the first, third, fifth, sixth, eighth and ninth aspects.

[0239] In an embodiment of the present application, a storage medium is provided having a computer program stored thereon, wherein the computer program causes a terminal device to perform a method according to the embodiments of the first, third, fifth, sixth, eighth and ninth aspects.

[0240] In an embodiment of the present application, there is further provided a computer program, wherein when the program is executed in a network device, the program causes the network device to perform the methods described in the embodiments of the second, fourth and seventh aspects.

[0241] In an embodiment of the present application, there is further provided a storage medium storing a computer program, wherein the computer program causes a network device to perform the methods described in the embodiments of the second, fourth and seventh aspects.

[0242] The above-described apparatus and methods of the present application may be realized by hardware or a combination of hardware and software. The present application relates to a computer-readable program that, when executed by a logic element, causes the logic element to implement the above-described apparatus or components or to implement the various methods or steps. The present application also relates to a storage medium for storing the program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0243] The methods / apparatuses described with reference to the embodiments of the present application may be embodied directly in hardware, as software modules executed by a processor, or as a combination of both. For example, one or more functional blocks and / or one or more combinations of functional blocks in the functional block diagrams shown in the figures may correspond to software modules in a computer program flow or hardware modules. These software modules may correspond to steps shown in the figures. These hardware modules may be implemented by implementing these software modules in hardware using, for example, a field programmable gate array (FPGA).

[0244] The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. The storage medium may be coupled to the processor such that the processor can read information from, and write information to, the storage medium, or the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The software module may be stored in memory of the mobile terminal or in a memory card insertable into the mobile terminal. For example, if a device (e.g., a mobile terminal) uses a relatively large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0245] One or more functional blocks and / or one or more combinations of functional blocks in the functional block diagrams set forth in the figures may be implemented with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any suitable combination thereof to perform the functions described herein. One or more functional blocks and / or one or more combinations of functional blocks in the functional block diagrams set forth in the figures may also be implemented with a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a DSP communication, or any other configuration.

[0246] Although the present invention has been described above with reference to specific embodiments, it is obvious to those skilled in the art that the above description is merely illustrative and does not limit the scope of protection of the present invention. Those skilled in the art may make various modifications and amendments to the present invention based on the spirit and principles of this application, and these modifications and amendments also fall within the scope of the present invention.

[0247] The following supplementary notes are further disclosed regarding the embodiments including the above examples.

[0248] (Appendix 1) 1. An information feedback method, comprising: Determining a candidate PDSCH reception timing set based on whether the terminal device has configured time domain bundling, and / or whether multiple PDSCH scheduling is configured, and / or whether a subcarrier spacing of a downlink BWP is configured, and / or whether the terminal device is capable of receiving multiple PDSCHs in one slot; and The method includes the terminal device generating and transmitting a HARQ-ACK codebook including HARQ-ACK information corresponding to the candidate PDSCH reception timing set.

[0249] (Appendix 2) Determining a candidate PDSCH reception timing set based on whether the terminal device has configured time domain bundling includes: 2. The method of claim 1, further comprising adding one PDSCH reception timing to the candidate PDSCH reception timing set when time domain bundling is configured.

[0250] (Appendix 3) 3. The method according to claim 1, wherein, when time domain bundling is not configured and the terminal device is capable of receiving multiple PDSCHs in one slot, one candidate PDSCH reception timing or multiple candidate PDSCH reception timings are added to the candidate PDSCH reception timing set based on the number of mutually independent PDSCH time domain resource configurations in the first allocation table.

[0251] (Appendix 4) A scheduling method, comprising: A network device receives capability indication information sent by a terminal device, the capability indication information indicating that the terminal device is capable of receiving multiple PDSCHs in one slot; and A scheduling configuration method, characterized in that the network device does not send enabled time domain bundling configuration information to the terminal device and / or does not send first indication information for setting a PDSCH time domain resource allocation table to the terminal device.

[0252] (Appendix 5) 5. The method of claim 4, wherein the PDSCH time domain resource allocation table supports scheduling of multiple PDSCHs via one DCI.

[0253] (Appendix 6) The terminal device transmits capability indication information to the network device to indicate that the terminal device is capable of receiving multiple PDSCHs in one slot; and The method includes the terminal device not receiving enable time domain bundling configuration information configured by the network device, and / or the network device not receiving first indication information for configuring a PDSCH time domain resource allocation table.

[0254] (Appendix 7) A scheduling method, comprising: A network device sends enable time domain bundling configuration information to the terminal device; and The method includes the network device transmitting downlink control information to the terminal device, the downlink control information scheduling one PDSCH or scheduling multiple PDSCHs having multiple valid PDSCHs.

[0255] (Appendix 8) A scheduling method, comprising: The network device receives enable time domain bundling configuration information sent from the network device; and The method includes receiving, by the terminal device, downlink control information transmitted from the network device for scheduling one PDSCH or for scheduling multiple PDSCHs including the multiple valid PDSCHs.

[0256] (Appendix 9) 1. An information feedback method, comprising: The terminal device determines a candidate PDSCH reception timing set; a terminal device determining a bit of HARQ-ACK information in a HARQ-ACK codebook based on the number of scheduled PDSCHs and / or the number of scheduled valid PDSCHs, and transmitting the codebook including HARQ-ACK information corresponding to the candidate PDSCH reception timing set.

[0257] (Appendix 10) The method described in Supplementary Note 9, wherein for one candidate PDSCH reception timing among the set of candidate PDSCH reception timings, the terminal device determines a bit of HARQ-ACK information corresponding to the one candidate PDSCH reception timing based on the number of scheduled PDSCHs and / or the number of associated valid PDSCHs associated with the one candidate PDSCH reception timing.

[0258] (Appendix 11) 11. The method of claim 10, wherein, when the number of scheduled PDSCHs and / or the number of associated valid PDSCHs associated with the one candidate PDSCH reception timing is 1, the bits of HARQ-ACK information corresponding to the one candidate PDSCH reception timing are equal to the bits of HARQ-ACK information corresponding to the associated number of scheduled PDSCHs and / or the associated valid PDSCHs.

[0259] (Appendix 12) 11. The method of claim 10, wherein, when the number of scheduled PDSCHs and / or the number of associated valid PDSCHs associated with the one candidate PDSCH reception timing are plural, the bit of HARQ-ACK information corresponding to the one candidate PDSCH reception timing is equal to the logical sum of the bits of HARQ-ACK information corresponding to the number of scheduled PDSCHs and / or the associated valid PDSCHs.

[0260] (Appendix 13) 13. The method according to any one of Supplementary Notes 10 to 12, wherein PDSCHs or active PDSCHs associated with the same candidate PDSCH reception timing are scheduled by the same DCI.

[0261] (Appendix 14) 11. The method of claim 10, wherein multiple PDSCHs associated with the same candidate PDSCH reception timing or multiple associated valid PDSCHs are scheduled by different DCIs, or some of them are scheduled by DCIs and some of them are SPS PDSCHs.

[0262] (Appendix 15) 10. The method of claim 9, wherein, for one candidate PDSCH reception timing among the set of candidate PDSCH reception timings, a PDSCH associated with the one candidate PDSCH reception timing includes one or more SPS PDSCHs.

[0263] (Appendix 16) Supplementary note 16. The method of claim 15, wherein the bit of the HARQ-ACK information corresponding to the one candidate PDSCH reception timing is equal to the bit of the HARQ-ACK information corresponding to the one SPS PDSCH or the logical sum of the bits of the HARQ-ACK information corresponding to the plurality of SPS PDSCHs.

[0264] (Appendix 17) 16. The method of claim 15, wherein the multiple SPS PDSCHs correspond to the same or different SPS configurations and / or are activated by different DCIs.

[0265] (Appendix 18) 18. The method according to any one of Supplementary Notes 15 to 17, wherein the PDSCH associated with the one candidate PDSCH reception timing does not include a PDSCH scheduled by DCI.

[0266] (Appendix 19) 16. The method of claim 15, wherein the PDSCH associated with the one candidate PDSCH reception timing further includes one or more PDSCHs scheduled by DCI.

[0267] (Appendix 20) 20. The method of claim 19, wherein the bit of HARQ-ACK information corresponding to the one candidate PDSCH reception timing is equal to the bit of HARQ-ACK information corresponding to the PDSCH scheduled by the DCI or the bit OR of the HARQ-ACK information.

[0268] (Appendix 21) 21. The method of claim 19 or 20, further comprising the terminal device not receiving an SPS PDSCH.

[0269] (Appendix 22) 22. The method of any one of Supplementary statements 19 to 21, wherein the SPS PDSCH is located before, after or in the middle of the PDSCH scheduled by the DCI in the time domain.

[0270] (Appendix 23) 23. The method according to any one of Supplementary Notes 19 to 22, wherein a HARQ process ID corresponding to the SPS PDSCH is different from a HARQ process ID of a PDSCH scheduled by the DCI, or is the same as a HARQ process ID of one PDSCH among a plurality of PDSCHs scheduled by the DCI.

[0271] (Appendix 24) 24. The method of any one of Supplementary Notes 13 to 23, further comprising the terminal device receiving one or more DCIs for scheduling a PDSCH and / or one or more DCIs for activating an SPS.

[0272] (Appendix 25) The terminal device receives a DCI for deactivating SPS; The bit of the HARQ-ACK information for feeding back the DCI in the codebook is a bit of HARQ-ACK information corresponding to a candidate PDSCH reception timing associated with an SPS PDSCH corresponding to an SPS deactivated by the DCI, or The method of Supplementary Note 9, wherein the bit of HARQ-ACK information for feeding back the DCI in the codebook is a bit of HARQ-ACK information corresponding to a candidate PDSCH reception timing associated with an SPS PDSCH corresponding to an SPS with the smallest index among a plurality of deactivated SPSs.

[0273] (Appendix 26) 26. The method according to any one of Supplementary Notes 9 to 25, wherein the terminal device determines a candidate PDSCH reception timing set based on whether time domain bundling is configured, and / or whether multiple PDSCH scheduling is configured, and / or whether a subcarrier spacing of a downlink BWP is configured, and / or whether there is a capability to receive multiple PDSCHs in one slot.

[0274] (Appendix 27) 27. The method of any one of Supplementary Notes 8 to 26, further comprising receiving, by the terminal device, enabled time domain bundling configuration information sent from the network device.

[0275] (Appendix 28) A network device sends enable time domain bundling configuration information to the terminal device; and An information setting method, characterized in that the network device does not send SPS setting information to the terminal device and / or does not send DCI for activating SPS to the terminal device.

[0276] (Appendix 29) The terminal device receives enable time domain bundling configuration information; and An information setting method including the terminal device not receiving SPS setting information and / or DCI for activating SPS.

[0277] (Appendix 30) The terminal device determines a candidate PDSCH reception timing set; The terminal device receives a DCI for deactivating SPS; The terminal device determines bits of HARQ-ACK information in a HARQ-ACK codebook and transmits the codebook, where all bits of the codebook are HARQ-ACK information of the DCI; or The bit of the HARQ-ACK information for feeding back the DCI in the codebook is a bit of HARQ-ACK information corresponding to a candidate PDSCH reception timing associated with an SPS PDSCH corresponding to an SPS deactivated by the DCI, or the bit of HARQ-ACK information for feeding back the DCI in the codebook is the bit of HARQ-ACK information corresponding to the candidate PDSCH reception timing associated with the SPS PDSCH corresponding to the SPS with the smallest index among a plurality of deactivated SPSs.

[0278] (Appendix 31) 31. The method of claim 30, further comprising receiving, by the terminal device, enabled time domain bundling configuration information sent from the network device.

[0279] (Appendix 32) 10. A network device comprising: a memory having a computer program stored therein; and a processor configured to execute the computer program and to implement a method according to any one of claims 4, 5, 7 and 28.

[0280] (Appendix 33) A memory in which a computer program is stored, and a terminal device that executes the computer program and is described in any one of Supplementary Notes 1 to 3, 6, 8 to 27, and 29 to 31. (Appendix 34) A communication system comprising a terminal device according to Supplementary Note 33 and / or a network device according to Supplementary Note 32.

[0281] The following supplementary notes are further disclosed regarding the embodiments including the above examples.

[0282] (Appendix 1) An information feedback device applied to a terminal device, a first determining unit for determining a set of candidate PDSCH reception timings based on whether time domain bundling is configured, and / or whether multi-PDSCH scheduling is configured, and / or whether a subcarrier spacing of a downlink BWP is configured, and / or whether there is a capability to receive multiple PDSCHs in one slot; a first processing unit for generating and transmitting a HARQ-ACK codebook including HARQ-ACK information corresponding to the candidate PDSCH reception timing set.

[0283] (Appendix 2) 2. The method of claim 1, wherein, when time domain bundling is configured, the first determination unit adds one PDSCH reception timing to the candidate PDSCH reception timing set.

[0284] (Appendix 3) 3. The method according to claim 1, wherein, when time domain bundling is not configured and the terminal device is capable of receiving multiple PDSCHs in one slot, the first determination unit adds one or more candidate PDSCH reception timings to the candidate PDSCH reception timing set based on the number of mutually independent PDSCH time domain resource configurations in the first allocation table.

[0285] (Appendix 4) A scheduling setting device applied to a network device, comprising: A first receiving unit receives capability indication information transmitted by a terminal device, the capability indication information indicating that the terminal device is capable of receiving multiple PDSCHs in one slot; and a second processing unit that does not transmit enabled time domain bundling setting information to the terminal device and / or does not transmit first indication information for setting a PDSCH time domain resource allocation table to the terminal device.

[0286] (Appendix 5) 5. The apparatus of claim 4, wherein the PDSCH time domain resource allocation table supports scheduling of multiple PDSCHs over one DCI.

[0287] (Appendix 6) A scheduling setting device applied to a terminal device, a first transmitting unit for transmitting capability indication information to a network device to indicate that the terminal device is capable of receiving multiple PDSCHs in one slot; and a third processing unit when the network device does not receive the configured enable time domain bundling configuration information and / or when the network device does not receive the first indication information for configuring a PDSCH time domain resource allocation table.

[0288] (Appendix 7) A scheduling setting device applied to a network device, comprising: a second sending unit for sending enabled time domain bundling configuration information to the terminal device; and a third transmitting unit configured to transmit downlink control information for scheduling one PDSCH or for scheduling multiple PDSCHs having multiple valid PDSCHs to the terminal device.

[0289] (Appendix 8) A scheduling setting device applied to a terminal device, a second receiving unit for receiving the enabled time domain bundling configuration information sent from the network device; and a third receiving unit for receiving downlink control information for scheduling one PDSCH or for scheduling multiple PDSCHs having multiple valid PDSCHs, transmitted from the network device.

[0290] (Appendix 9) An information feedback device applied to a terminal device, comprising: a second determining unit for determining a set of candidate PDSCH receive timings; and a fourth processing unit that determines a bit of HARQ-ACK information in a HARQ-ACK codebook based on the number of scheduled PDSCHs and / or the number of scheduled valid PDSCHs, and transmits the codebook including the HARQ-ACK information corresponding to the candidate PDSCH reception timing set.

[0291] (Appendix 10) The apparatus of Supplementary Note 9, wherein for one candidate PDSCH reception timing among the set of candidate PDSCH reception timings, the fourth processing unit determines a bit of HARQ-ACK information corresponding to the one candidate PDSCH reception timing based on the number of scheduled PDSCHs and / or the number of associated valid PDSCHs associated with the one candidate PDSCH reception timing.

[0292] (Appendix 11) The apparatus of claim 10, wherein, when the number of scheduled PDSCHs and / or the number of associated valid PDSCHs associated with the one candidate PDSCH reception timing is 1, the bits of HARQ-ACK information corresponding to the one candidate PDSCH reception timing are equal to the bits of HARQ-ACK information corresponding to the associated number of scheduled PDSCHs and / or the associated valid PDSCHs.

[0293] (Appendix 12) The apparatus of claim 10, wherein, when the number of scheduled PDSCHs and / or the number of associated valid PDSCHs associated with the one candidate PDSCH reception timing are plural, the bit of HARQ-ACK information corresponding to the one candidate PDSCH reception timing is equal to the logical sum of the bits of HARQ-ACK information corresponding to the number of scheduled PDSCHs and / or the associated valid PDSCHs.

[0294] (Appendix 13) 13. The apparatus of any one of Supplementary Notes 10 to 12, wherein PDSCHs or active PDSCHs associated with the same candidate PDSCH reception timing are scheduled by the same DCI.

[0295] (Appendix 14) 11. The apparatus of claim 10, wherein multiple PDSCHs associated with the same candidate PDSCH reception timing or multiple associated valid PDSCHs are scheduled by different DCIs, or some of them are scheduled by DCIs and some of them are SPS PDSCHs.

[0296] (Appendix 15) 10. The apparatus of claim 9, wherein, for one candidate PDSCH reception timing among the set of candidate PDSCH reception timings, a PDSCH associated with the one candidate PDSCH reception timing includes one or more SPS PDSCHs.

[0297] (Appendix 16) 16. The apparatus of claim 15, wherein the bit of the HARQ-ACK information corresponding to the one candidate PDSCH reception timing is equal to the bit of the HARQ-ACK information corresponding to the one SPS PDSCH or a logical sum of the bits of the HARQ-ACK information corresponding to the plurality of SPS PDSCHs.

[0298] (Appendix 17) 16. The apparatus of claim 15, wherein the multiple SPS PDSCHs correspond to the same or different SPS configurations and / or are activated by different DCIs.

[0299] (Appendix 18) 18. The apparatus according to any one of Supplementary Notes 15 to 17, wherein the PDSCH associated with the one candidate PDSCH reception timing does not include a PDSCH scheduled by DCI.

[0300] (Appendix 19) 16. The apparatus of claim 15, wherein the PDSCH associated with the one candidate PDSCH reception timing further includes one or more PDSCHs scheduled by DCI.

[0301] (Appendix 20) The apparatus of claim 19, wherein the bit of HARQ-ACK information corresponding to the one candidate PDSCH reception timing is equal to the bit of HARQ-ACK information corresponding to the PDSCH scheduled by the DCI or a bit OR of HARQ-ACK information.

[0302] (Appendix 21) 21. The apparatus of claim 19 or 20, further comprising a fifth processing unit that does not receive an SPS PDSCH.

[0303] (Appendix 22) 22. The apparatus of any one of Supplementary statements 19 to 21, wherein the SPS PDSCH is located before, after, or in the middle of the PDSCH scheduled by the DCI in the time domain.

[0304] (Appendix 23) Supplementary Note 19 to 22, wherein the HARQ process ID corresponding to the SPS PDSCH is different from the HARQ process ID of the PDSCH scheduled by the DCI, or is the same as the HARQ process ID of one PDSCH among a plurality of PDSCHs scheduled by the DCI.

[0305] (Appendix 24) 24. The apparatus of any one of Supplementary Notes 13 to 23, further comprising a fourth receiving unit configured to receive one or more DCIs for scheduling a PDSCH and / or one or more DCIs for activating an SPS.

[0306] (Appendix 25) a fifth receiving unit for receiving a DCI for deactivating the SPS; Wherein, the fourth processing unit is configured such that the bit of the HARQ-ACK information for feeding back the DCI in the codebook is a bit of HARQ-ACK information corresponding to a candidate PDSCH reception timing associated with an SPS PDSCH corresponding to an SPS deactivated by the one DCI; or The apparatus of Supplementary Note 9, wherein the HARQ-ACK information bit for feeding back DCI in the codebook is a HARQ-ACK information bit corresponding to a candidate PDSCH reception timing associated with an SPS PDSCH corresponding to an SPS with a smallest index among a plurality of deactivated SPSs.

[0307] (Appendix 26) 26. The apparatus according to any one of Supplementary Notes 9 to 25, wherein the second determination unit determines the candidate PDSCH reception timing set based on whether time domain bundling is configured, and / or whether multiple PDSCH scheduling is configured, and / or whether a subcarrier spacing of a downlink BWP is configured, and / or whether there is a capability to receive multiple PDSCHs in one slot.

[0308] (Appendix 27) 27. The apparatus of any one of claims 8 to 26, further comprising a sixth receiving unit for receiving enabled time domain bundling configuration information sent from the network device.

[0309] (Appendix 28) An information setting device applied to a network device, a fourth sending unit for sending enabled time domain bundling configuration information to the terminal device; An information setting device, characterized in that it includes a sixth processing unit that does not send SPS setting information to the terminal device and / or does not send DCI for activating SPS to the terminal device.

[0310] (Appendix 29) An information setting device applied to a terminal device, a seventh receiving unit for receiving enable time domain bundling setting information; and a seventh receiving unit that does not receive SPS setting information and / or DCI for activating SPS.

[0311] (Appendix 30) An information feedback device applied to a terminal device, comprising: a third determining unit for determining a set of candidate PDSCH receive timings; a seventh receiving unit for receiving a DCI for deactivating the SPS; an eighth processing unit for determining bits of HARQ-ACK information in a HARQ-ACK codebook and sending the codebook, wherein all bits of the codebook are HARQ-ACK information of the DCI; or The bit of the HARQ-ACK information for feeding back the DCI in the codebook is a bit of HARQ-ACK information corresponding to a candidate PDSCH reception timing associated with an SPS PDSCH corresponding to an SPS deactivated by the DCI, or the bit of HARQ-ACK information for feeding back the DCI in the codebook is a bit of HARQ-ACK information corresponding to a candidate PDSCH reception timing associated with an SPS PDSCH corresponding to an SPS with a smallest index among a plurality of deactivated SPSs.

[0312] (Appendix 31) 31. The apparatus of claim 30, further comprising an eighth processing unit that receives enabled time domain bundling configuration information sent from the network device.

Claims

1. An apparatus for feeding back information that can be applied to a terminal device, comprising: a processor for determining a set of candidate PDSCH reception occasions and determining a bit of HARQ-ACK information in a HARQ-ACK codebook based on the number of PDSCHs to be scheduled and / or the number of valid PDSCHs to be scheduled; and a transmitter for transmitting the HARQ-ACK codebook; The HARQ-ACK codebook includes HARQ-ACK information corresponding to the selected PDSCH reception timing set; When the number of PDSCHs scheduled by a single downlink control information (DCI) associated with one candidate PDSCH reception timing is greater than 1 and the number of valid PDSCHs scheduled by the single downlink control information associated with the one candidate PDSCH reception timing is 1, a bit of HARQ-ACK information corresponding to the one candidate PDSCH reception timing is equal to a bit of HARQ-ACK information corresponding to the associated valid PDSCH; When the number of PDSCHs scheduled by the single downlink control information associated with the one candidate PDSCH reception timing is greater than 1 and the number of valid PDSCHs scheduled by the single downlink control information associated with the one candidate PDSCH reception timing is greater than 1, a bit of HARQ-ACK information corresponding to the one candidate PDSCH reception timing is equal to a binary AND of bits of HARQ-ACK information corresponding to the associated valid PDSCH.

2. 10. The apparatus of claim 1, For one candidate PDSCH reception timing in the candidate PDSCH reception timing set, a PDSCH associated with the one candidate PDSCH reception timing includes one or more SPS PDSCHs.

3. 3. The apparatus of claim 2, The device, wherein the HARQ-ACK information bit corresponding to the one selected PDSCH reception timing is equal to the HARQ-ACK information bit corresponding to the one SPS PDSCH or the logical sum of the HARQ-ACK information bits corresponding to the multiple SPS PDSCHs.

4. 3. The apparatus of claim 2, The apparatus, wherein the multiple SPS PDSCHs correspond to the same or different SPS configurations and / or are activated by different DCIs.

5. 3. The apparatus of claim 2, The apparatus, wherein the PDSCHs associated with the one candidate PDSCH reception timing do not include a PDSCH scheduled by the DCI.

6. 3. The apparatus of claim 2, The PDSCH associated with the one candidate PDSCH reception timing further includes one or more PDSCHs scheduled by the DCI.

7. 7. The apparatus of claim 6, The HARQ-ACK information bit corresponding to one of the candidate PDSCH reception timings is equal to the HARQ-ACK information bit corresponding to the PDSCH scheduled by the DCI or the logical sum of the HARQ-ACK information bits.

8. 7. The apparatus of claim 6, The processor further controls the apparatus so as not to receive the SPS PDSCH.

9. 7. The apparatus of claim 6, The apparatus, wherein the SPS PDSCH is located before, after, or in the middle of a PDSCH scheduled by the DCI in the time domain.

10. 7. The apparatus of claim 6, The HARQ process ID corresponding to the SPS PDSCH is different from the HARQ process ID of a PDSCH scheduled by the DCI or is the same as the HARQ process ID of one PDSCH among a plurality of PDSCHs scheduled by the DCI.

11. 10. The apparatus of claim 1, further comprising: An apparatus comprising: a receiver for receiving one or more DCIs for scheduling a PDSCH and / or one or more DCIs for activating an SPS.

12. 10. The apparatus of claim 1, further comprising: a receiver for receiving a DCI for deactivating an SPS; The processor includes: In the HARQ-ACK codebook, the HARQ-ACK information bit for feedback of the DCI is a HARQ-ACK information bit corresponding to a candidate PDSCH reception timing associated with an SPS PDSCH corresponding to the SPS deactivated by the DCI; or In the HARQ-ACK codebook, the HARQ-ACK information bit for feedback of the DCI is the HARQ-ACK information bit corresponding to the candidate PDSCH reception timing associated with the SPS PDSCH corresponding to the SPS with the smallest index among the plurality of SPSs deactivated by the DCI. A device that determines:

13. 10. The apparatus of claim 1, The processor includes: time domain bundling is configured; and / or whether multi-PDSCH scheduling and / or downlink BWP subcarrier spacing is configured; and / or Is it possible to receive multiple PDSCHs in one slot? and determining the candidate PDSCH receive timing set based on the selected PDSCH receive timing set.

14. A network device, a transmitter for transmitting a PDSCH; and a receiver for receiving a HARQ-ACK codebook; the HARQ-ACK codebook includes HARQ-ACK information corresponding to a set of candidate PDSCH reception occasions, and bits of the HARQ-ACK information in the HARQ-ACK codebook are determined based on the number of PDSCHs to be scheduled and / or the number of valid PDSCHs to be scheduled; When the number of PDSCHs scheduled by a single downlink control information (DCI) associated with one candidate PDSCH reception timing is greater than 1 and the number of valid PDSCHs scheduled by the single downlink control information associated with the one candidate PDSCH reception timing is 1, a bit of HARQ-ACK information corresponding to the one candidate PDSCH reception timing is equal to a bit of HARQ-ACK information corresponding to the associated valid PDSCH; the network device, wherein when the number of PDSCHs scheduled by the single downlink control information associated with the one candidate PDSCH reception timing is greater than 1 and the number of valid PDSCHs scheduled by the single downlink control information associated with the one candidate PDSCH reception timing is greater than 1, a bit of HARQ-ACK information corresponding to the one candidate PDSCH reception timing is equal to a binary OR of bits of HARQ-ACK information corresponding to the associated valid PDSCHs.

15. An apparatus for feeding back information that can be applied to a terminal device, comprising: A processor for determining a set of candidate PDSCH reception occasions based on whether time domain bundling is configured, and / or whether multi-PDSCH scheduling and / or subcarrier spacing of downlink BWP is configured, and / or whether there is an ability to receive multiple PDSCHs in one slot; and a transmitter for transmitting a HARQ-ACK codebook; The HARQ-ACK codebook includes HARQ-ACK information corresponding to the selected PDSCH reception timing set; When the number of PDSCHs scheduled by a single downlink control information (DCI) associated with one candidate PDSCH reception timing is greater than 1 and the number of valid PDSCHs scheduled by the single downlink control information associated with the one candidate PDSCH reception timing is 1, a bit of HARQ-ACK information corresponding to the one candidate PDSCH reception timing is equal to a bit of HARQ-ACK information corresponding to the associated valid PDSCH; When the number of PDSCHs scheduled by the single downlink control information associated with the one candidate PDSCH reception timing is greater than 1 and the number of valid PDSCHs scheduled by the single downlink control information associated with the one candidate PDSCH reception timing is greater than 1, a bit of HARQ-ACK information corresponding to the one candidate PDSCH reception timing is equal to a binary AND of bits of HARQ-ACK information corresponding to the associated valid PDSCH.

Images