Method and device for transmitting and receiving feedback information

Abstract

An embodiment of the present invention provides a method and device for transmitting and receiving feedback information, the method including: a terminal device receiving downlink control information sent by a network device, and receiving a physical downlink shared channel sent by the network device based on the downlink control information; and a terminal device feeding back feedback information about the physical downlink shared channel to the network device, wherein the feedback information about the physical downlink shared channel on a multi-physical downlink shared channel carrier is included in at least two sub-codebooks, one of which includes feedback information about a single physical downlink shared channel on a multi-physical downlink shared channel carrier and a physical downlink shared channel scheduled based on a transport block.

Description

[Technical field]

[0001] FIELD OF THE DISCLOSURE The present invention relates to the field of communications technology. [Background technology]

[0002] In New Radio (NR) Rel-15 and Rel-16, with support for FR2 frequencies, the subcarrier spacing (SCS) of the Physical Downlink Control Channel (PDCCH) / Physical Downlink Shared Channel (PDSCH) can reach up to 120 kHz.

[0003] In NR Rel-15 and Rel-16, one Downlink Control Information (DCI) can schedule only one PDSCH (hereinafter referred to as single-PDSCH scheduling). A terminal device can feed back feedback information about PDSCHs scheduled by one or more DCIs within a certain period. The feedback information is, for example, a Hybrid Automatic Repeat reQuest (HARQ) codebook, and is also referred to as a HARQ-ACK or a HARQ-ACK codebook.

[0004] NR Rel-17 is currently considering support for higher frequencies (52.6 GHz to 71 GHz). Higher frequencies require additional support for larger SCS (greater than 120 kHz), and larger SCS means shorter slot length. Due to processing power limitations, the processing time of the terminal device cannot be reduced proportionally to the slot length. Therefore, compared to the case of low frequencies, there is some relaxation in the processing requirements of the terminal device operating at high frequencies. For example, the terminal device cannot blindly detect the PDCCH too frequently. In this case, there may be more slots between the blind detection occasions of two adjacent PDCCHs. That is, the scheduling occasions of a particular terminal device are reduced to a certain extent.

[0005] The above description of the background art is merely for the purpose of more clearly and completely explaining the configurations of the present invention and for the understanding of those skilled in the art, and should not be construed as meaning that these configurations are well known to those skilled in the art just because they are described in the background art of the present invention. Summary of the Invention [Problem to be solved by the invention]

[0006] To provide more timely PDSCH scheduling, support for multi-PDSCH scheduling is being considered in NR Rel-17. In multi-PDSCH scheduling, multiple PDSCHs can be scheduled in one DCI. For terminal devices operating at high frequencies (e.g., 52.6 GHz to 71 GHz), supporting multi-PDSCH scheduling can easily achieve a compromise between PDSCH scheduling flexibility and device processing power, and reduce DCI scheduling overhead. Therefore, multi-PDSCH scheduling is likely to become a new feature supported when operating at 52.6 GHz to 71 GHz.

[0007] However, according to the discovery of the inventors of the present invention, the NR Rel-15 and Rel-16 standards do not support multi-PDSCH scheduling. Currently, how to generate and transmit feedback information (e.g., Type 2 HARQ-ACK codebook) for multi-PDSCH scheduling is still an unsolved problem.

[0008] In view of at least one of the above problems, embodiments of the present invention provide a method and apparatus for transmitting and receiving feedback information. [Means for solving the problem]

[0009] In one aspect of an embodiment of the present invention, a method for transmitting feedback information is provided, the method including: a terminal device receiving downlink control information transmitted by a network device, receiving a physical downlink shared channel transmitted by the network device based on the downlink control information; and feeding back feedback information about the physical downlink shared channel to the network device, wherein the feedback information about the physical downlink shared channel on a multi-physical downlink shared channel carrier is included in at least two sub-codebooks, one of which includes feedback information about a single physical downlink shared channel on a multi-physical downlink shared channel carrier and a physical downlink shared channel scheduled based on a transport block.

[0010] Another aspect of an embodiment of the present invention provides a feedback information transmitting device, the device including: a receiving unit that receives downlink control information transmitted by a network device and receives a physical downlink shared channel transmitted by the network device based on the downlink control information; and a transmitting unit that feeds back feedback information about the physical downlink shared channel to the network device, wherein the feedback information about the physical downlink shared channel on a multi-physical downlink shared channel carrier is included in at least two sub-codebooks, one of which includes feedback information about a single physical downlink shared channel on a multi-physical downlink shared channel carrier and a physical downlink shared channel scheduled based on a transport block.

[0011] Another aspect of an embodiment of the present invention provides a method for receiving feedback information, the method comprising: a step of a network device transmitting downlink control information to a terminal device and transmitting a physical downlink shared channel to the terminal device; and a step of receiving feedback information about the physical downlink shared channel fed back by the terminal device, wherein the feedback information about the physical downlink shared channel on a multi-physical downlink shared channel carrier is included in at least two sub-codebooks, one of which includes feedback information about a single physical downlink shared channel on a multi-physical downlink shared channel carrier and a physical downlink shared channel scheduled based on a transport block.

[0012] Another aspect of an embodiment of the present invention provides a feedback information receiving device, the device including: a transmitting unit that transmits downlink control information to a terminal device and transmits a physical downlink shared channel to the terminal device; and a receiving unit that receives feedback information about the physical downlink shared channel fed back by the terminal device, wherein the feedback information about the physical downlink shared channel on a multi-physical downlink shared channel carrier is included in at least two sub-codebooks, one of which includes feedback information about a single physical downlink shared channel on a multi-physical downlink shared channel carrier and a physical downlink shared channel scheduled based on a transport block.

[0013] Another aspect of an embodiment of the present invention provides a communication system including a network device and a terminal device, wherein the network device transmits downlink control information to the terminal device, transmits a physical downlink shared channel to the terminal device, and receives feedback information about the physical downlink shared channel fed back by the terminal device, and the terminal device receives the downlink control information transmitted by the network device, receives the physical downlink shared channel transmitted by the network device based on the downlink control information, and feeds back feedback information about the physical downlink shared channel to the network device, and the feedback information about the physical downlink shared channel on a multi-physical downlink shared channel carrier is included in at least two sub-codebooks, one of which includes feedback information about a single physical downlink shared channel on a multi-physical downlink shared channel carrier and a physical downlink shared channel scheduled based on a transport block.

[0014] One of the advantageous effects of the embodiment of the present invention is as follows: For a carrier on which multi-PDSCH scheduling is enabled, multiple sub-codebooks are generated based on information such as whether multi-PDSCH scheduling is used and / or whether Code Block Group (CBG) is used, thereby supporting feedback based on multi-PDSCH, and the size of the Type 2 HARQ-ACK codebook can be reduced by dividing the sub-codebook, thereby reducing the feedback overhead of HARQ-ACK.

[0015] As shown in the following description and drawings, certain embodiments of the present invention are disclosed in detail to show the manner in which the principles of the present invention can be employed. However, the scope of the embodiments of the present invention is not limited to these. The embodiments of the present invention include modifications, alterations and equivalents within the spirit and scope of the appended claims.

[0016] Features described and / or illustrated in one embodiment may be used in the same or similar manner in one or more other embodiments and may be combined with or substituted for features in the other embodiments.

[0017] It should be noted that in this text, the term "including / having" means the presence of a feature, element, step or component, and does not exclude the presence or addition of one or more other features, elements, steps or components. [Brief description of the drawings]

[0018] Elements and features depicted in one drawing and one embodiment of the present invention may be combined with elements and features shown in one or more drawings or embodiments, and in the drawings, like reference numerals may designate corresponding elements in multiple drawings and may designate corresponding elements used in more than one embodiment. [Figure 1]1 is a schematic diagram of a communication system according to an embodiment of the present invention; [Figure 2A] FIG. 2 is a schematic diagram of an example of dynamically determining feedback information using DAI in an embodiment of the present invention. [Figure 2B] 2 is a schematic diagram of an example of multi-PDSCH scheduling according to an embodiment of the present invention; [Diagram 3] FIG. 2 is a schematic diagram of an example of a carrier aggregation scenario according to an embodiment of the present invention; [Figure 4] 2 is a schematic diagram of an example of a method for transmitting feedback information according to an embodiment of the present invention; [Diagram 5] FIG. 4 is a schematic diagram of an example of a first sub-codebook according to an embodiment of the present invention; [Figure 6] FIG. 4 is a schematic diagram of an example of a second sub-codebook according to an embodiment of the present invention; [Figure 7] FIG. 11 is a schematic diagram of an example of a third sub-codebook according to an embodiment of the present invention; [Figure 8] FIG. 11 is a schematic diagram of another example of the second sub-codebook in the embodiment of the present invention. [Figure 9] FIG. 11 is a schematic diagram of another example of the second sub-codebook in the embodiment of the present invention. [Figure 10] FIG. 13 is a schematic diagram of another example of the third sub-codebook in the embodiment of the present invention; [Figure 11] FIG. 11 is a schematic diagram of another example of the first sub-codebook in the embodiment of the present invention; [Figure 12] FIG. 11 is a schematic diagram of another example of the second sub-codebook in the embodiment of the present invention. [Figure 13] FIG. 13 is a schematic diagram of another example of the third sub-codebook in the embodiment of the present invention; [Figure 14] FIG. 11 is a schematic diagram of another example of the first sub-codebook in the embodiment of the present invention; [Figure 15] FIG. 11 is a schematic diagram of another example of the second sub-codebook in the embodiment of the present invention. [Figure 16] FIG. 2 is a schematic diagram of an example of a method for receiving feedback information according to an embodiment of the present invention; [Figure 17]FIG. 2 is a schematic diagram of an example of a feedback information transmitting device according to an embodiment of the present invention; [Figure 18] FIG. 2 is a schematic diagram of an example of a feedback information receiving device according to an embodiment of the present invention; [Figure 19] FIG. 2 is a schematic diagram of a network device according to an embodiment of the present invention. [Figure 20] FIG. 2 is a schematic diagram of a terminal device according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0019] The above and other features of the present invention will become apparent from the following description. In the specification and drawings, specific embodiments of the present invention are disclosed in detail, and some of the embodiments in which the principles of the present invention can be adopted are shown. However, the present invention is not limited to the described embodiments. The present invention includes all modifications, variations, and equivalents within the scope of the appended claims. Each embodiment of the present invention will be described below with reference to the drawings. These embodiments are merely illustrative and do not limit the present invention.

[0020] In embodiments of the present invention, the terms "first", "second", etc. are used in the title to distinguish different elements, but do not represent the spatial arrangement or temporal order of these elements, and these elements are not limited to these terms. The term "and / or" includes any and all combinations of one or more of the terms listed in the associated list. The terms "including", "comprising", "having", etc. refer to the presence of listed features, elements, elements or components, but do not exclude the presence or addition of one or more other features, elements, elements or components.

[0021] In the embodiments of the present invention, the singular forms "a", "the", etc., include the plural forms and should be understood broadly as "one kind" or "a class", and are not limited to "one". In addition, the term "said" should be understood to include both the singular and the plural forms, unless the context clearly indicates otherwise. In addition, the term "described in" should be understood to mean "described at least in part", and the term "based on" should be understood to mean "based at least in part on", unless the context clearly indicates otherwise.

[0022] In an embodiment of the present invention, the term "communication network" or "wireless communication network" may refer to a network conforming to any communication standard, such as, for example, Long Term Evolution (LTE), Advanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0023] Additionally, communications between devices in a communication system may occur according to any stage of communication protocols, including, but not limited to, 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, and 5G, New Radio (NR), and / or other currently known or future developed communication protocols.

[0024] In the embodiment of the present invention, the term "network device" refers to a device in a communication system, for example, allowing a terminal device to access the communication system and providing a service to the terminal device. The network device may include, but is not limited to, a base station (BS), an access point (AP), a transmission reception point (TRP), a broadcast transmitter, a mobility management entity (MME), a gateway, a server, a radio network controller (RNC), a base station controller (BSC), etc.

[0025] Among them, the base station may include, but is not limited to, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), and 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.). Also, the term "base station" may include some or all of the functions thereof, 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.

[0026] In the embodiment of the present invention, the term "User Equipment" (UE) or "Terminal Equipment" (TE) refers to an apparatus that accesses a communication network and receives a network service via, for example, a network device. The terminal apparatus may be fixed or mobile, and may be called a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), a station, etc.

[0027] Among them, the terminal device may include, but is not limited to, a mobile 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 smartphone, a smart watch, a digital camera, and the like.

[0028] For example, in a scenario such as the Internet of Things (IoT), the user equipment may be a monitoring or measuring device or equipment, including, but not limited to, a Machine Type Communication (MTC) terminal, an in-vehicle communication terminal, a Device to Device (D2D) terminal, a Machine to Machine (M2M) terminal, etc.

[0029] Furthermore, the term "network side" or "network device side" refers to the side of a network, which may be a base station 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 may refer to a terminal device.

[0030] The following describes an embodiment scenario of the present invention with reference to an example, but the present invention is not limited thereto.

[0031] 1 is a schematic diagram of a communication system according to an embodiment of the present invention, and shows an example of a user device and a network device. As shown in FIG. 1, a communication system 100 may include a network device 101 and a terminal device 102. For convenience of explanation, FIG. 1 shows only one terminal device and one network device as an example, but the embodiment of the present invention is not limited thereto, and may include, for example, multiple terminal devices.

[0032] In the embodiment of the present invention, existing services or services that can be implemented in the future can be performed between the network device 101 and the terminal device 102. For example, these services include, but are not limited to, enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra-Reliable and Low-Latency Communication (URLLC).

[0033] NR Rel-15 and Rel-16 support Type 2 HARQ-ACK codebooks and can dynamically determine the number of HARQ-ACK bits to be fed back using a Downlink Assignment Index (DAI) mechanism. The Type 2 HARQ-ACK codebook is a dynamic HARQ-ACK codebook, and the terminal device generates the Type 2 HARQ-ACK codebook based on the counter DAI and total DAI indicated by the DCI.

[0034] 2A is a schematic diagram of an example of dynamically determining feedback information using DAI in an embodiment of the present invention, and shows a schematic Type 2 HARQ-ACK codebook, where counter DAI continuously counts carriers and DCIs, and total DAI indicates the total number of DCIs accumulated in the current slot.

[0035] As shown in Figure 2A, the Type 2 HARQ-ACK codebook is composed of two sub-codebooks, which correspond to TB-based transmission and CBG-based transmission, respectively. Here, "TB-based transmission" corresponds to not enabling "CBG-based transmission". The counter DAI and total DAI are counted separately in the sub-codebooks. For ease of explanation, the counter DAI and total DAI in Figure 2A indicate the absolute value of the count.

[0036] In each sub-codebook, the number of HARQ-ACK bits scheduled for each DCI is determined according to the maximum number of HARQ-ACK bits in all carriers included in the sub-codebook. Here, "carriers included in the sub-codebook" means that the carriers can generate feedback information in the sub-codebook or that the sub-codebook includes feedback information about the carriers. CC stands for component carrier in carrier aggregation. N TB_max represents the maximum number of TBs that the carrier can support, and N CBG_max_TB represents the maximum number of CBGs that each TB of a carrier can support.

[0037] As shown in FIG. 2A, the first sub-codebook includes HARQ-ACK for 6 schedulings, and the maximum number of HARQ-ACK bits is 2, so a total of 12 bits of HARQ-ACK are required. The second sub-codebook includes HARQ-ACK for 7 schedulings, and the maximum number of HARQ-ACK bits is 8, so a total of 56 bits of HARQ-ACK are required. Here, the first sub-codebook includes feedback information for the following PDSCHs, where the PDSCHs are scheduled by fallback DCI (DCI format 1_0) on carriers where CBG-based transmission is enabled. The final Type 2 HARQ-ACK codebook is obtained by cascading the two sub-codebooks, and includes a total of 68 bits of HARQ-ACK.

[0038] The NR Rel-15 and Rel-16 standards do not support multi-PDSCH scheduling. Currently, how to generate and transmit feedback information (e.g., Type 2 HARQ-ACK codebook) for multi-PDSCH scheduling is still an unsolved problem.

[0039] For the Type 2 HARQ-ACK codebook, the failure to detect DCI by the terminal device causes a misunderstanding of the codebook size between the terminal device and the network device. To avoid this problem, the Type 2 HARQ-ACK codebook generates a HARQ-ACK for each carrier according to the maximum number of HARQ-ACK bits in the carrier, and the excess HARQ-ACK bits are set as NACK.

[0040] Figure 2B is a schematic diagram of an example of multi-PDSCH scheduling according to an embodiment of the present invention. As shown in Figure 2B, one DCI schedules multiple PDSCHs (e.g., PDSCH#0, PDSCH#1, PDSCH#2...), and feedback information for multiple PDSCHs is sent to a network device at the same timing.

[0041] With the introduction of multi-PDSCH, the terminal device needs to simultaneously feed back HARQ-ACK for multiple PDSCHs, so the maximum number of HARQ-ACK bits may increase exponentially, and HARQ-ACK is generated according to the maximum number of HARQ-ACK bits. As a result, the number of bits of the Type 2 HARQ-ACK codebook increases significantly, and the feedback overhead increases.

[0042] In an embodiment of the present invention, a multi-PDSCH carrier is a carrier in which a function (multi-PDSCH function) of scheduling multiple PDSCHs via one DCI is enabled. A single-PDSCH carrier is a carrier in which a function of scheduling multiple PDSCHs via one DCI is not enabled. A carrier in an embodiment of the present invention may be replaced with a component carrier (CC), a serving cell, a cell, etc., and the present invention is not limited thereto.

[0043] In the embodiment of the present invention, one carrier is a multi-PDSCH carrier or a single-PDSCH carrier. In the case of a multi-PDSCH carrier, one or more PDSCHs can be scheduled in one DCI. In the case of a single-PDSCH carrier, only one PDSCH can be scheduled in one DCI. One PDSCH can carry one or more TBs. According to the NR standard, one PDSCH carries a maximum of two TBs.

[0044] The embodiment of the present invention is not limited to a method for determining whether a carrier is a multi-PDSCH carrier.

[0045] For example, it may be determined according to a time domain resource allocation table configured in a Radio Resource Control (RRC) or System Information Block (SIB). If for a particular carrier, a row in the table can indicate multiple PDSCH time domain resources and / or mapping types, e.g., multiple Start and length indicator values ​​(SLIVs) and / or mapping types, then the carrier is a multi-PDSCH carrier, otherwise the carrier is a single-PDSCH carrier.

[0046] As another example, it can be determined according to the DCI format supported by the carrier: if the supported DCI format contains multiple New Data Indicator (NDI) and / or Redundancy Version (RV) fields, the carrier is a multi-PDSCH carrier, otherwise the carrier is a single-PDSCH carrier.

[0047] As another example, it may be determined according to a multi-PDSCH parameter configured by RRC: if a carrier is configured with the multi-PDSCH parameter, it means that the multi-PDSCH function is enabled for the carrier, and the carrier is a multi-PDSCH carrier; otherwise, the carrier is a single-PDSCH carrier.

[0048] In the embodiment of the present invention, the scheduling based on multi-PDSCH means that one DCI schedules two or more PDSCHs, and the scheduling based on single-PDSCH means that one DCI schedules one PDSCH. A single-PDSCH carrier can only support the scheduling based on single-PDSCH. A multi-PDSCH carrier can support the scheduling based on multi-PDSCH and can also support the scheduling based on single-PDSCH. Suppose a DCI schedules a PDSCH on carrier c, the DCI may be from carrier c or may be from another carrier different from carrier c (cross-carrier scheduling).

[0049] In the embodiment of the present invention, "scheduling based on multi-PDSCH" can be replaced with "scheduling by multi-PDSCH", and "scheduling based on single-PDSCH" can be replaced with "scheduling by single-PDSCH". DCI that schedules multi-PDSCH carriers does not always schedule multiple PDSCHs. DCI can dynamically switch between scheduling one PDSCH and scheduling multiple PDSCHs.

[0050] In an embodiment of the present invention, feedback information about scheduling based on multi-PDSCH (ie, feedback information about multiple PDSCHs) is simultaneously transmitted from a terminal device to a network device.

[0051] In some aspects, a first DCI is used for multi-PDSCH based scheduling, and a second DCI is used for single-PDSCH based scheduling, and the first DCI and the second DCI have different DCI formats.

[0052] For example, different DCI formats can be used to schedule multi-PDSCH carriers. One DCI format (a newly defined DCI format to support multi-PDSCH) can indicate scheduling based on multi-PDSCH, and another DCI format (legacy DCI formats including DCI format 1_0, DCI format 1_1, DCI format 1_2, etc.) can indicate scheduling based on single-PDSCH. Supporting legacy DCI formats provides better system robustness and compatibility. For example, fallback DCI (DCI format 1_0) can be used for scheduling when channel conditions are poor.

[0053] In some aspects, a field in the DCI indicates multi-PDSCH based scheduling or single-PDSCH based scheduling.

[0054] For example, when a DCI field indicates multiple SLIVs and / or mapping types used to indicate the SLIVs and mapping types of multiple PDSCHs, the DCI indicates multi-PDSCH-based scheduling. Even when using a newly defined DCI format to support multi-PDSCH, a single PDSCH resource can be indicated in one row of a time domain resource allocation table configured by RRC, and multiple PDSCH resources can be indicated in another row. Then, by dynamically indicating different rows using a field in the DCI, it is possible to flexibly switch between multi-PDSCH-based scheduling and single-PDSCH-based scheduling.

[0055] In another example, if the DCI includes multiple New Data Indicator (NDI) and / or Redundancy Version (RV) fields used to indicate the NDI and RV of multiple PDSCHs, the DCI indicates scheduling based on multi-PDSCH.

[0056] In the embodiment of the present invention, the terminal device is not limited to a method for identifying the single-PDSCH-based scheduling and the multi-PDSCH-based scheduling. As described above, for example, the terminal device may identify according to the DCI format. When a conventional DCI format such as DCI format 1_0, DCI format 1_1, or DCI format 1_2 is received, the terminal device may know that these DCIs schedule transmissions based on the single-PDSCH. When a DCI format newly defined to support the multi-PDSCH is received, the terminal device may know that the DCI schedules transmissions based on the multi-PDSCH. As another example, the terminal device may determine based on the DCI field and distinguish between the single-PDSCH-based scheduling and the multi-PDSCH-based scheduling through specific signaling content of the DCI. As another example, the terminal device may identify based on a combination of the above two methods.

[0057] FIG. 3 is a schematic diagram of an example of a carrier aggregation scenario according to an embodiment of the present invention. As shown in FIG. 3, component carriers (CC) of carrier aggregation include the following: -single-PDSCH carrier set C0: A carrier in C0 is not configured for CBG-based transmission. In other words, the carrier is not enabled for CBG-based transmission. For simplicity, "CBG-based transmission is not enabled" is abbreviated as "TB-based scheduling" and "CBG-based transmission is enabled" is abbreviated as "CBG-based scheduling". For a carrier c in set C0, N TB_max,c represents the maximum number of TBs that carrier c can support. According to the NR standard, 1 ≤ N TB_max,c <= 2. - single-PDSCH carrier set C1: the carriers in C1 are configured for CBG-based transmission, which is abbreviated as CBG-based scheduling. For a carrier c in set C1, N TB_max,c represents the maximum number of TBs that carrier c can support, and N CBG_max_TB,c represents the maximum number of CBGs that each TB of carrier c can support. According to the NR standard, 2 ≤ N TB_max,c ×N CBG_max_TB,c <=8. - Multi-PDSCH carrier set C2: The carriers in C2 are not configured for CBG-based transmission, abbreviated as TB-based scheduling. For carrier c in set C2, N TB_max,c represents the maximum number of TBs that each PDSCH of carrier c can support, and N multi_PDSCH_max,c represents the maximum number of PDSCHs that one DCI can schedule that carrier c can support. For simplicity, N TB_max,c is also referred to as the maximum number of TBs that carrier c can support. - multi-PDSCH carrier set C3: the carriers in C3 are configured for CBG-based transmission, abbreviated as CBG-based scheduling. For a carrier c in set C3, N TB_max,c represents the maximum number of TBs that each PDSCH of carrier c can support, and N CBG_max_TB,c represents the maximum number of CBGs that each TB of carrier c can support, and N multi_PDSCH_max,c represents the maximum number of PDSCHs that can be scheduled in one DCI that carrier c can support. For simplicity, N TB_max,c is also referred to as the maximum number of TBs that carrier c can support.

[0058] The carrier aggregation in Figure 3 includes all types of carriers. If a specific type of carrier does not exist, the carrier aggregation becomes a special case of Figure 3.

[0059] In an embodiment of the present invention, for a carrier that is "scheduled based on TB" (i.e., a carrier where CBG-based transmission is not enabled), the PDSCH is scheduled only based on TB. For a carrier that is "scheduled based on CBG" (i.e., a carrier where CBG-based transmission is enabled), the PDSCH may be scheduled based on CBG or may be scheduled based on TB. "Scheduled based on TB" can be replaced with "scheduled in TB mode" and "scheduled based on CBG" can be replaced with "scheduled in CBG mode".

[0060] Above, multi-PDSCH and single-PDSCH have been briefly described, and the following will further describe the embodiments of the present invention. In the following description, transmitting or receiving a PDCCH can be understood as transmitting or receiving downlink control information carried by the PDCCH, and transmitting or receiving a PDSCH can be understood as transmitting or receiving downlink data carried by the PDSCH.

[0061] <Example 1> An embodiment of the present invention provides a method for transmitting feedback information, which is described from the terminal device side.

[0062] 4 is a schematic diagram of an example of a feedback information sending method according to an embodiment of the present invention. As shown in FIG. 4, the method includes the following steps:

[0063] Step 401: A terminal device receives downlink control information (DCI) sent by a network device.

[0064] Step 402: The terminal device receives a physical downlink shared channel (PDSCH) sent by the network device according to the downlink control information.

[0065] Step 403: The terminal device feeds back feedback information about the physical downlink shared channel to the network device.

[0066] Here, the feedback information for the PDSCH on the multi-PDSCH carrier is included in at least two sub-codebooks, one of which includes feedback information for the single-PDSCH on the multi-PDSCH carrier and the PDSCH scheduled based on a transport block (TB).

[0067] It should be noted that the above FIG. 4 only shows a schematic diagram of an embodiment of the present invention, but the present invention is not limited thereto. For example, the execution order between various steps may be appropriately adjusted, some other steps may be added, and some steps may be removed. Those skilled in the art may make appropriate modifications based on the above content, and are not limited to the description of the above FIG. 4.

[0068] In some aspects, the HARQ-ACK codebook includes a first sub-codebook, a second sub-codebook, and a third sub-codebook.

[0069] In some aspects, the first sub-codebook includes feedback information for a physical downlink shared channel (PDSCH) scheduled based on a transport block on a single physical downlink shared channel carrier and / or feedback information for a physical downlink shared channel (PDSCH) scheduled based on a single physical downlink shared channel and a transport block on a multi-physical downlink shared channel carrier.

[0070] That is, the first sub-codebook includes the HARQ-ACK for the next PDSCH. - PDSCH scheduled in TB mode on a single-PDSCH carrier. - PDSCH scheduled in single-PDSCH mode and TB mode on multi-PDSCH carriers.

[0071] Figure 5 is a schematic diagram of an example of a first sub-codebook in an embodiment of the present invention, illustrating a situation corresponding to the divided carrier set in Figure 3. As shown in Figure 5, the first sub-codebook includes HARQ-ACK for the next PDSCH. - PDSCH scheduled on carriers in set C0. - PDSCH scheduled in TB mode on carriers in set C1. - A PDSCH scheduled in single-PDSCH mode on carriers in set C2. - PDSCH scheduled in single-PDSCH mode and TB mode on carriers in set C3.

[0072] In the embodiment of the present invention, if there is no specific carrier related to the above determined sub-codebook, the sub-codebook naturally does not include the HARQ-ACK related to the carrier. For example, the carrier aggregation carrier may not include C0 and C1, in which case the first sub-codebook does not include the HARQ-ACK related to C0 and C1. As another example, the carrier aggregation carrier may not include C3, in which case the first sub-codebook does not include the HARQ-ACK related to C3. The description of the similar situation is omitted here.

[0073] In some aspects, the first sub-codebook includes feedback information for at least one of a semi-persistent scheduling physical downlink shared channel release (SPS PDSCH release) on a single physical downlink shared channel carrier and / or a multi-physical downlink shared channel carrier, a semi-persistent scheduling physical downlink shared channel (SPS PDSCH reception), or a downlink control information indicating a secondary cell is dormant (DCI indicating SCell dormancy).

[0074] For example, the first sub-codebook may further include HARQ-ACK for the following information: -Semi-persistent scheduling physical downlink shared channel release (SPS PDSCH release). - Semi-persistent scheduling physical downlink shared channel (SPS PDSCH reception). - DCI indicating SCell dormancy.

[0075] For example, the DCI may indicate an SPS PDSCH release, and the HARQ-ACK for the DCI is included in the first sub-codebook. The SPS PDSCH may not have DCI scheduling associated with it, and the HARQ-ACK for the SPS PDSCH is included in the first sub-codebook. The DCI may indicate that a secondary cell is out of service, for example, DCI format 1_1 indicates that a secondary cell is out of service, and the HARQ-ACK for this DCI is included in the first sub-codebook. If there is no specific information associated with the above determined sub-codebook, the sub-codebook naturally does not include a HARQ-ACK associated with the information.

[0076] In some aspects, the number of bits of feedback information for one downlink scheduling in the first sub-codebook is Nmax =max c {N TB_max,c}, where carrier c is a carrier capable of generating feedback information in the first sub-codebook, and N TB_max,c is the maximum number of transmission blocks (TB) that carrier c can support.

[0077] For example, for each possible PDSCH scheduling in the first sub-codebook, the number of corresponding HARQ-ACK bits is (outside 1) Assume the file is TIFF0007632604000001.tif1582, where N c =N TB_max,c In other words, every time the value of counter DAI or total DAI is increased by 1, the number of HARQ-ACK bits is increased by N max By reserving according to the maximum possible number of HARQ-ACK bits, it is possible to avoid a mismatch between the terminal device and the network device regarding the size of the HARQ-ACK codebook in case of DCI missed detection.

[0078] In some aspects, the second sub-codebook includes feedback information for a physical downlink shared channel scheduled based on a code block group (CBG) on a single physical downlink shared channel carrier and / or feedback information for a single physical downlink shared channel and a physical downlink shared channel scheduled based on a code block group (CBG) on a multi-physical downlink shared channel carrier.

[0079] That is, the second sub-codebook includes the HARQ-ACK for the next PDSCH. - PDSCH scheduled in CBG mode on a single-PDSCH carrier. - PDSCH scheduled in single-PDSCH mode and CBG mode on multi-PDSCH carriers.

[0080] Figure 6 is a schematic diagram of an example of a second sub-codebook in an embodiment of the present invention, which shows a situation corresponding to the division of the carrier set in Figure 3. As shown in Figure 6, the second sub-codebook includes HARQ-ACK for the next PDSCH. - PDSCH scheduled in CBG mode on carriers in set C1. - PDSCH scheduled in single-PDSCH mode and CBG mode on carriers in set C3.

[0081] In the embodiment of the present invention, if there is no specific PDSCH scheduling associated with the determined sub-codebook, the sub-codebook naturally does not include the HARQ-ACK associated with the PDSCH. For example, if the carrier of C3 does not support the PDSCH scheduled in the single-PDSCH mode and the CBG mode, the second sub-codebook does not include the HARQ-ACK associated with the PDSCH.

[0082] In some aspects, the number of bits of feedback information for one downlink scheduling in the second sub-codebook is N max =max c {N TB_max,c ×N CBG_max_TB,c}, where carrier c is a carrier capable of generating feedback information in the second sub-codebook, and N TB_max,c is the maximum number of transmission blocks (TB) that carrier c can support, and N CBG_max_TB,c is the maximum number of code block groups (CBGs) that each transport block can support on carrier c.

[0083] For example, for each possible PDSCH scheduling in the second sub-codebook, the number of corresponding HARQ-ACK bits is (outside 2) TIFF0007632604000002.tif1782, where N c =N TB_max,c ×N CBG_max_TB,c .

[0084] In some aspects, the third sub-codebook includes feedback information for a physical downlink shared channel that is scheduled based on the multiple physical downlink shared channel on the multiple physical downlink shared channel carrier.

[0085] That is, the third sub-codebook includes the HARQ-ACK for the next PDSCH. - PDSCH scheduled in multi-PDSCH mode on multi-PDSCH carriers.

[0086] Figure 7 is a schematic diagram of an example of a third sub-codebook in an embodiment of the present invention, illustrating a situation corresponding to the division of the carrier set in Figure 3. As shown in Figure 7, the third sub-codebook includes HARQ-ACK for the next PDSCH. - PDSCH scheduled in multi-PDSCH mode on carriers in set C2. - PDSCH scheduled in multi-PDSCH mode on carriers in set C3.

[0087] The PDSCH scheduled based on multi-PDSCH on carriers in set C3 includes PDSCH scheduled based on multi-PDSCH and CBG, and also PDSCH scheduled based on multi-PDSCH and TB. If a specific PDSCH does not exist, the sub-codebook does not include HARQ-ACK for the PDSCH. For example, if a carrier in set C3 does not support scheduling based on multi-PDSCH and TB, the sub-codebook does not include HARQ-ACK for the scheduling.

[0088] In some aspects, the number of bits of feedback information for one downlink scheduling in the third sub-codebook is N max =max c {Nc}, and carrier c is the carrier capable of generating feedback information in the third sub-codebook.

[0089] For a carrier c where transmission based on the code block group is not enabled, N c =N TB_max,c ×N multi_PDSCH_max,c , for a carrier c for which code block group-based transmission is enabled, N c =N TB_max,c ×N CBG_max_TB,c ×N multi_PDSCH_max,c) .

[0090] N TB_max,c is the maximum number of transmission blocks that carrier c can support, and N CBG_max_TB,c is the maximum number of code block groups (CBGs) that each transport block (TB) can support on carrier c, and N multi_PDSCH_max,c is the maximum number of physical downlink shared channels on carrier c for which downlink control information (DCI) can be scheduled.

[0091] For example, for each possible PDSCH scheduling in the third sub-codebook, the number of corresponding HARQ-ACK bits is (Outside 3) TIFF0007632604000003.tif1682. For carrier c in set C2, N c =N TB_max,c ×N multi_PDSCH_max,c For carrier c in set C3, N c =N TB_max,c ×N CBG_max_TB,c ×N multi_PDSCH_max,c It is.

[0092] In an embodiment of the present invention, the counter DAI and the total DAI are counted independently in each sub-codebook. The HARQ-ACK codebook sent by the terminal device to the network device is obtained by cascading the above sub-codebooks. The embodiment of the present invention is not limited to the cascading order of the sub-codebooks, for example, the first, second, and third sub-codebooks are cascaded in this order. Thus, by dividing the sub-codebooks, the size of the Type 2 HARQ-ACK codebook can be reduced, and the HARQ-ACK feedback overhead can be reduced.

[0093] The above embodiments are merely illustrative of the present invention, and the present invention is not limited thereto, and appropriate modifications may be made based on the above embodiments. For example, each of the above embodiments may be used alone, or one or more of the above embodiments may be used in combination.

[0094] According to this embodiment, for carriers for which multi-PDSCH scheduling is enabled, multiple sub-codebooks are generated based on information such as whether multi-PDSCH scheduling is used and / or whether code block groups (CBGs) are used, thereby making it possible to support feedback based on multi-PDSCH, and by dividing the sub-codebooks, it is possible to reduce the size of the Type 2 HARQ-ACK codebook and reduce the feedback overhead of HARQ-ACK.

[0095] <Example 2> Based on the first embodiment, the description of the embodiment of the present invention will be continued from the terminal device, and the description of the same contents as the first embodiment will be omitted.

[0096] In some aspects, the HARQ-ACK codebook may include a first sub-codebook and a second sub-codebook.

[0097] In some aspects, the first sub-codebook includes feedback information for a physical downlink shared channel (PDSCH) scheduled based on a transport block on a single physical downlink shared channel carrier and / or feedback information for a physical downlink shared channel (PDSCH) scheduled based on a single physical downlink shared channel and a transport block on a multi-physical downlink shared channel carrier.

[0098] That is, the first sub-codebook includes the HARQ-ACK for the next PDSCH. - PDSCH scheduled in TB mode on a single-PDSCH carrier. - PDSCH scheduled in single-PDSCH mode and TB mode on multi-PDSCH carriers.

[0099] For details, refer to the first sub-codebook in the first embodiment.

[0100] In some aspects, the second sub-codebook includes feedback information for a physical downlink shared channel scheduled based on a code block group (CBG) on a single physical downlink shared channel carrier, and / or feedback information for a physical downlink shared channel scheduled based on a single physical downlink shared channel and a code block group (CBG) on a multi-physical downlink shared channel carrier, and / or feedback information for a physical downlink shared channel scheduled based on a multi-physical downlink shared channel on a multi-physical downlink shared channel carrier.

[0101] That is, the second sub-codebook includes the HARQ-ACK for the next PDSCH. - PDSCH scheduled in CBG mode on a single-PDSCH carrier. - PDSCH scheduled in single-PDSCH mode and CBG mode on multi-PDSCH carriers. - PDSCH scheduled in multi-PDSCH mode on multi-PDSCH carriers.

[0102] Figure 8 is a schematic diagram of another example of the second sub-codebook in the embodiment of the present invention, illustrating a situation corresponding to the division of the carrier set in Figure 3. As shown in Figure 8, the second sub-codebook includes HARQ-ACK for the next PDSCH. - PDSCH scheduled in CBG mode on carriers in set C1. - PDSCH scheduled in multi-PDSCH mode on carriers in set C2. - PDSCH scheduled in single-PDSCH mode and CBG mode on carriers in set C3 and PDSCH scheduled in multi-PDSCH mode.

[0103] In some aspects, the number of bits of feedback information for one downlink scheduling in the second sub-codebook is N max =max c {N c}, and carrier c is the carrier capable of generating feedback information in the second sub-codebook.

[0104] For a single physical downlink shared channel carrier c on which code block group-based transmission is enabled, N c =N TB_max,c ×N CBG_max_TB,c , for a multi-physical downlink shared channel carrier c for which code block group-based transmission is not enabled, N c =N TB_max,c ×N multi_PDSCH_max,c , for a multi-physical downlink shared channel carrier c for which code block group-based transmission is enabled, N c =N TB_max,c ×NCBG_max_TB,c ×N multi_PDSCH_max,c .

[0105] N TB_max,c is the maximum number of transmission blocks (TB) that carrier c can support, and N CBG_max_TB,c is the maximum number of code block groups (CBGs) that each transport block (TB) can support on carrier c, and N multi_PDSCH_max,c is the maximum number of physical downlink shared channels on carrier c for which downlink control information (DCI) can be scheduled.

[0106] For example, for each possible PDSCH scheduling in the second sub-codebook, the number of corresponding HARQ-ACK bits is (outside 4) TIFF0007632604000004.tif1682. For carrier c in set C1, N c =N TB_max,c ×N CBG_max_TB,c For carrier c in set C2, N c =N TB_max,c ×N multi_PDSCH_max,c For carrier c in set C3, N c =N TB_max,c ×N CBG_max_TB,c ×N multi_PDSCH_max,c .

[0107] In an embodiment of the present invention, the counter DAI and the total DAI are counted independently in each sub-codebook. The HARQ-ACK codebook sent by the terminal device to the network device is obtained by cascading the above sub-codebooks. The embodiment of the present invention is not limited to the cascading order of the sub-codebooks, for example, the first sub-codebook is cascaded, and the second sub-codebook is cascaded. Thus, by dividing the sub-codebook, the size of the Type 2 HARQ-ACK codebook can be reduced and the HARQ-ACK feedback overhead can be reduced.

[0108] The above embodiments are merely illustrative of the present invention, and the present invention is not limited thereto, and appropriate modifications may be made based on the above embodiments. For example, each of the above embodiments may be used alone, or one or more of the above embodiments may be used in combination.

[0109] According to this embodiment, for carriers for which multi-PDSCH scheduling is enabled, multiple sub-codebooks are generated based on information such as whether multi-PDSCH scheduling is used and / or whether code block groups (CBGs) are used, thereby making it possible to support feedback based on multi-PDSCH, and by dividing the sub-codebooks, it is possible to reduce the size of the Type 2 HARQ-ACK codebook and reduce the feedback overhead of HARQ-ACK.

[0110] <Example 3> Based on the first and second embodiments, the description of the embodiment of the present invention will be continued from the terminal device, and the description of the same contents as the first and second embodiments will be omitted.

[0111] In some aspects, the HARQ-ACK codebook may include a first sub-codebook, a second sub-codebook, and a third sub-codebook.

[0112] In some aspects, the first sub-codebook includes feedback information for a physical downlink shared channel (PDSCH) scheduled based on a transport block on a single physical downlink shared channel carrier and / or feedback information for a physical downlink shared channel (PDSCH) scheduled based on a single physical downlink shared channel and a transport block on a multi-physical downlink shared channel carrier.

[0113] That is, the first sub-codebook includes the HARQ-ACK for the next PDSCH. - PDSCH scheduled in TB mode on a single-PDSCH carrier. - PDSCH scheduled in single-PDSCH mode and TB mode on multi-PDSCH carriers.

[0114] For details, refer to the first sub-codebook in the first embodiment.

[0115] The second sub-codebook includes feedback information for a physical downlink shared channel that is scheduled based on a code block group (CBG) on a single physical downlink shared channel carrier.

[0116] That is, the second sub-codebook includes the HARQ-ACK for the next PDSCH. - PDSCH scheduled in CBG mode on a single-PDSCH carrier.

[0117] Figure 9 is a schematic diagram of another example of the second sub-codebook in the embodiment of the present invention, illustrating a situation corresponding to the division of the carrier set in Figure 3. As shown in Figure 9, the second sub-codebook includes HARQ-ACK for the next PDSCH. - PDSCH scheduled in CBG mode on carriers in set C1.

[0118] In some aspects, the number of bits of feedback information for one downlink scheduling in the second sub-codebook is N max =max c {N TB_max,c ×N CBG_max_TB,c}, where carrier c is a carrier capable of generating feedback information in the second sub-codebook, and N TB_max,c is the maximum number of transmission blocks (TB) that carrier c can support, and N CBG_max_TB,c is the maximum number of code block groups (CBGs) that each transport block (TB) can support on carrier c.

[0119] For example, for each possible PDSCH scheduling in the second sub-codebook, the number of corresponding HARQ-ACK bits is (outside 5) TIFF0007632604000005.tif1582, where N c =N TB_max,c ×N CBG_max_TB,c .

[0120] In some aspects, the third sub-codebook includes feedback information for a single physical downlink shared channel and a physical downlink shared channel scheduled based on a code block group (CBG) on a multi-physical downlink shared channel carrier, and / or feedback information for a physical downlink shared channel scheduled based on a multi-physical downlink shared channel on a multi-physical downlink shared channel carrier.

[0121] That is, the third sub-codebook includes the HARQ-ACK for the next PDSCH. - PDSCH scheduled in single-PDSCH mode and CBG mode on multi-PDSCH carriers. - PDSCH scheduled in multi-PDSCH mode on multi-PDSCH carriers.

[0122] Figure 10 is a schematic diagram of another example of the third sub-codebook in the embodiment of the present invention, illustrating a situation corresponding to the division of the carrier set in Figure 3. As shown in Figure 10, the third sub-codebook includes HARQ-ACK for the next PDSCH. - PDSCH scheduled in multi-PDSCH mode on carriers in set C2. - PDSCH scheduled in single-PDSCH mode and CBG mode on carriers in set C3 and PDSCH scheduled in multi-PDSCH mode.

[0123] In some aspects, the number of bits of feedback information for one downlink scheduling in the third sub-codebook is N max =max c {N c}, and carrier c is the carrier capable of generating feedback information in the third sub-codebook.

[0124] For a multi-physical downlink shared channel carrier c for which code block group-based transmission is not enabled, N c =N TB_max,c ×N multi_PDSCH_max,c , for a multi-physical downlink shared channel carrier c for which code block group-based transmission is enabled, N c =N TB_max,c ×N CBG_max_TB,c ×N multi_PDSCH_max,c .

[0125] N TB_max,c is the maximum number of transmission blocks (TB) that carrier c can support, and N CBG_max_TB,c is the maximum number of code block groups (CBGs) that each transport block (TB) can support on carrier c, and N multi_PDSCH_max,c is the maximum number of physical downlink shared channels on carrier c for which downlink control information (DCI) can be scheduled.

[0126] For example, for each possible PDSCH scheduling in the third sub-codebook, the number of corresponding HARQ-ACK bits is (outside 6) TIFF0007632604000006.tif1582. For carrier c in set C2, N c =N TB_max,c ×N multi_PDSCH_max,c For carrier c in set C3, N c =N TB_max,c ×N CBG_max_TB,c ×N multi_PDSCH_max,c .

[0127] In an embodiment of the present invention, the counter DAI and the total DAI are counted independently in each sub-codebook. The HARQ-ACK codebook sent by the terminal device to the network device is obtained by cascading the above sub-codebooks. The embodiment of the present invention is not limited to the cascading order of the sub-codebooks, for example, the first, second, and third sub-codebooks are cascaded in this order. Thus, by dividing the sub-codebooks, the size of the Type 2 HARQ-ACK codebook can be reduced, and the HARQ-ACK feedback overhead can be reduced.

[0128] The above embodiments are merely illustrative of the present invention, and the present invention is not limited thereto, and appropriate modifications may be made based on the above embodiments. For example, each of the above embodiments may be used alone, or one or more of the above embodiments may be used in combination.

[0129] According to this embodiment, for carriers for which multi-PDSCH scheduling is enabled, multiple sub-codebooks are generated based on information such as whether multi-PDSCH scheduling is used and / or whether code block groups (CBGs) are used, thereby making it possible to support feedback based on multi-PDSCH, and by dividing the sub-codebooks, it is possible to reduce the size of the Type 2 HARQ-ACK codebook and reduce the feedback overhead of HARQ-ACK.

[0130] <Example 4> Based on the first to third embodiments, the description of the embodiments of the present invention will be continued from the terminal device, and the description of the same contents as the first to third embodiments will be omitted.

[0131] In some aspects, the feedback information for the first physical downlink shared channel and the feedback information for the second physical downlink shared channel are in different sub-codebooks, the first physical downlink shared channel is scheduled on a multi-physical downlink shared channel (multi-PDSCH) carrier, and the second physical downlink shared channel is scheduled on a single-physical downlink shared channel (single-PDSCH) carrier.

[0132] In some aspects, the HARQ-ACK codebook may include a first sub-codebook, a second sub-codebook, and a third sub-codebook.

[0133] In some aspects, the first sub-codebook includes feedback information for a physical downlink shared channel that is scheduled on a transport block (TB) basis on a single physical downlink shared channel carrier.

[0134] That is, the first sub-codebook includes the HARQ-ACK for the next PDSCH. - PDSCH scheduled with TB on a single-PDSCH carrier.

[0135] Figure 11 is a schematic diagram of another example of the first sub-codebook in the embodiment of the present invention, illustrating a situation corresponding to the division of the carrier set in Figure 3. As shown in Figure 11, the first sub-codebook includes HARQ-ACK for the next PDSCH. - PDSCH scheduled on carriers in set C0. - PDSCH scheduled in TB mode on carriers in set C1.

[0136] For example, for each possible PDSCH scheduling in the first sub-codebook, the number of corresponding HARQ-ACK bits is (outer 7) TIFF0007632604000007.tif1882, where N c =N TB_max,c .

[0137] In some aspects, the second sub-codebook includes feedback information for a physical downlink shared channel that is scheduled on a code block group (CBG) basis on a single physical downlink shared channel carrier.

[0138] That is, the second sub-codebook includes the HARQ-ACK for the next PDSCH. - PDSCH scheduled in CBG mode on a single-PDSCH carrier.

[0139] Figure 12 is a schematic diagram of another example of the second sub-codebook in the embodiment of the present invention, illustrating a situation corresponding to the division of the carrier set in Figure 3. As shown in Figure 12, the second sub-codebook includes HARQ-ACK for the next PDSCH. - PDSCH scheduled in CBG mode on carriers in set C1.

[0140] For example, for each possible PDSCH scheduling in the second sub-codebook, the number of corresponding HARQ-ACK bits is (outside 8) TIFF0007632604000008.tif1782, where N c = NTB_max,c ×N CBG_max_TB,c .

[0141] In some aspects, the third sub-codebook includes feedback information for a physical downlink shared channel scheduled on multiple physical downlink shared channel carriers.

[0142] That is, the third sub-codebook includes the HARQ-ACK for the next PDSCH. - PDSCH scheduled on multi-PDSCH carriers.

[0143] Figure 13 is a schematic diagram of another example of the third sub-codebook in the embodiment of the present invention, illustrating a situation corresponding to the division of the carrier set in Figure 3. As shown in Figure 13, the third sub-codebook includes HARQ-ACK for the next PDSCH. - PDSCH scheduled on carriers in set C2. - PDSCH scheduled on carriers in set C3.

[0144] For example, for each possible PDSCH scheduling in the third sub-codebook, the corresponding number of HARQ-ACK bits is (outer 9) TIFF0007632604000009.tif1789. For carrier c in set C2, N c =N TB_max,c ×N multi_PDSCH_max,c For carrier c in set C3, N c =N TB_max,c ×N CBG_max_TB,c ×N multi_PDSCH_max,c .

[0145] In an embodiment of the present invention, the counter DAI and the total DAI are counted independently in each sub-codebook. The HARQ-ACK codebook sent by the terminal device to the network device is obtained by cascading the above sub-codebooks. The embodiment of the present invention is not limited to the cascading order of the sub-codebooks, for example, the first, second, and third sub-codebooks are cascaded in this order. Thus, by dividing the sub-codebooks, the size of the Type 2 HARQ-ACK codebook can be reduced, and the HARQ-ACK feedback overhead can be reduced.

[0146] The above embodiments are merely illustrative of the present invention, and the present invention is not limited thereto, and appropriate modifications may be made based on the above embodiments. For example, each of the above embodiments may be used alone, or one or more of the above embodiments may be used in combination.

[0147] According to this embodiment, for carriers for which multi-PDSCH scheduling is enabled, multiple sub-codebooks are generated based on information such as whether multi-PDSCH scheduling is used and / or whether code block groups (CBGs) are used, thereby making it possible to support feedback based on multi-PDSCH, and by dividing the sub-codebooks, it is possible to reduce the size of the Type 2 HARQ-ACK codebook and reduce the feedback overhead of HARQ-ACK.

[0148] <Example 5> Based on the first to fourth embodiments, the description of the embodiments of the present invention will be continued from the terminal device, and the description of the same contents as the first to fourth embodiments will be omitted.

[0149] In some aspects, the feedback information for the third physical downlink shared channel and the feedback information for the fourth physical downlink shared channel are in different sub-codebooks, the third physical downlink shared channel is scheduled on a multi-physical downlink shared channel (multi-PDSCH) carrier based on a transport block (TB), and the fourth physical downlink shared channel is scheduled on a multi-physical downlink shared channel (multi-PDSCH) carrier based on a code block group (CBG).

[0150] In some aspects, the HARQ-ACK codebook may include a first sub-codebook and a second sub-codebook.

[0151] In some aspects, the first sub-codebook includes feedback information for a physical downlink shared channel that is scheduled on a transport block (TB) basis on a single physical downlink shared channel carrier and / or feedback information for a physical downlink shared channel that is scheduled on a transport block (TB) basis on a multi-physical downlink shared channel carrier.

[0152] That is, the first sub-codebook includes the HARQ-ACK for the next PDSCH. - PDSCH scheduled in TB mode on a single-PDSCH carrier. - PDSCH scheduled in TB mode on multi-PDSCH carriers.

[0153] Figure 14 is a schematic diagram of another example of the first sub-codebook in the embodiment of the present invention, illustrating a situation corresponding to the division of the carrier set in Figure 3. As shown in Figure 14, the first sub-codebook includes HARQ-ACK for the next PDSCH. - PDSCH scheduled on carriers in set C0. - PDSCH scheduled in TB mode on carriers in set C1. - PDSCH scheduled on carriers in set C2. - PDSCH scheduled in TB mode on carriers in set C3.

[0154] For example, for each possible PDSCH scheduling in the first sub-codebook, the number of corresponding HARQ-ACK bits is (Outside 10) TIFF0007632604000010.tif1989. For carrier c in sets C0, C1, N c =N TB_max,c For carrier c in sets C2 and C3, N c =N TB_max,c ×N multi_PDSCH_max,c .

[0155] In some aspects, the second sub-codebook includes feedback information for a physical downlink shared channel scheduled based on a code block group (CBG) on a single physical downlink shared channel carrier and / or feedback information for a physical downlink shared channel scheduled based on a code block group (CBG) on multiple physical downlink shared channel carriers.

[0156] That is, the second sub-codebook includes the HARQ-ACK for the next PDSCH. - PDSCH scheduled in CBG mode on a single-PDSCH carrier. - PDSCH scheduled in CBG mode on multi-PDSCH carriers.

[0157] Figure 15 is a schematic diagram of another example of the second sub-codebook in the embodiment of the present invention, illustrating a situation corresponding to the division of the carrier set in Figure 3. As shown in Figure 15, the second sub-codebook includes HARQ-ACK for the next PDSCH. - PDSCH scheduled in CBG mode on carriers in set C1. - PDSCH scheduled in CBG mode on carriers in set C3.

[0158] For example, for each possible PDSCH scheduling in the second sub-codebook, the number of corresponding HARQ-ACK bits is (Outside 11) TIFF0007632604000011.tif1889. For carrier c in set C1, N c =N TB_max,c ×N CBG_max_TB,c For carrier c in set C3, N c =N TB_max,c ×N CBG_max_TB,c ×N multi_PDSCH_max,c .

[0159] In an embodiment of the present invention, the counter DAI and the total DAI are counted independently in each sub-codebook. The HARQ-ACK codebook sent by the terminal device to the network device is obtained by cascading the above sub-codebooks. The embodiment of the present invention is not limited to the cascading order of the sub-codebooks, for example, the first sub-codebook is cascaded, and the second sub-codebook is cascaded. Thus, by dividing the sub-codebook, the size of the Type 2 HARQ-ACK codebook can be reduced and the HARQ-ACK feedback overhead can be reduced.

[0160] The above embodiments are merely illustrative of the present invention, and the present invention is not limited thereto, and appropriate modifications may be made based on the above embodiments. For example, each of the above embodiments may be used alone, or one or more of the above embodiments may be used in combination.

[0161] According to this embodiment, for carriers for which multi-PDSCH scheduling is enabled, multiple sub-codebooks are generated based on information such as whether multi-PDSCH scheduling is used and / or whether code block groups (CBGs) are used, thereby making it possible to support feedback based on multi-PDSCH, and by dividing the sub-codebooks, it is possible to reduce the size of the Type 2 HARQ-ACK codebook and reduce the feedback overhead of HARQ-ACK.

[0162] <Example 6> The embodiment of the present invention provides a method for receiving feedback information, and will be described from the network device side. Descriptions of contents similar to those of the first to fifth embodiments will be omitted.

[0163] 16 is a schematic diagram of an example of a method for receiving feedback information in an embodiment of the present invention. As shown in FIG. 16, the method includes the following steps:

[0164] Step 1601: A network device sends downlink control information (DCI) to a terminal device.

[0165] Step 1602: The network device transmits a physical downlink shared channel (PDSCH) to the terminal device.

[0166] Step 1603: The network device receives feedback information about the physical downlink shared channel fed back by the terminal device.

[0167] It should be noted that the above FIG. 16 only shows a schematic example of the embodiment of the present invention, but the present invention is not limited thereto. For example, the execution order between various steps may be appropriately adjusted, some other steps may be added, and some steps may be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description of the above FIG. 16.

[0168] In some aspects, feedback information for a physical downlink shared channel on a multi-physical downlink shared channel carrier is included in at least two sub-codebooks, one of which includes feedback information for a single physical downlink shared channel on a multi-physical downlink shared channel carrier and a physical downlink shared channel scheduled based on a transport block.

[0169] For example, the at least two sub-codebooks include a first sub-codebook, a second sub-codebook and a third sub-codebook.

[0170] The first sub-codebook includes feedback information for a physical downlink shared channel scheduled based on a transport block on a single physical downlink shared channel carrier and / or feedback information for a physical downlink shared channel scheduled based on a single physical downlink shared channel and a transport block on a multi-physical downlink shared channel carrier.

[0171] The second sub-codebook includes feedback information for a physical downlink shared channel scheduled based on a code block group (CBG) on a single physical downlink shared channel carrier and / or feedback information for a single physical downlink shared channel and a physical downlink shared channel scheduled based on a code block group (CBG) on a multi-physical downlink shared channel carrier.

[0172] The third sub-codebook includes feedback information for a physical downlink shared channel scheduled on the multi-physical downlink shared channel carrier based on the multi-physical downlink shared channel.

[0173] As another example, the at least two sub-codebooks include a first sub-codebook and a second sub-codebook.

[0174] The first sub-codebook includes feedback information for a physical downlink shared channel scheduled based on a transport block on a single physical downlink shared channel carrier and / or feedback information for a physical downlink shared channel scheduled based on a single physical downlink shared channel and a transport block on a multi-physical downlink shared channel carrier.

[0175] The second sub-codebook includes feedback information for a physical downlink shared channel scheduled based on a code block group (CBG) on a single physical downlink shared channel carrier, and / or feedback information for a physical downlink shared channel scheduled based on a single physical downlink shared channel and a code block group (CBG) on a multi-physical downlink shared channel carrier, and / or feedback information for a physical downlink shared channel scheduled based on a multi-physical downlink shared channel on a multi-physical downlink shared channel carrier.

[0176] As another example, the at least two sub-codebooks include a first sub-codebook, a second sub-codebook, and a third sub-codebook.

[0177] The first sub-codebook includes feedback information for a physical downlink shared channel scheduled based on a transport block on a single physical downlink shared channel carrier and / or feedback information for a physical downlink shared channel scheduled based on a single physical downlink shared channel and a transport block on a multi-physical downlink shared channel carrier.

[0178] The second sub-codebook includes feedback information for a physical downlink shared channel that is scheduled based on a code block group (CBG) on a single physical downlink shared channel carrier.

[0179] The third sub-codebook includes feedback information for a single physical downlink shared channel and a physical downlink shared channel scheduled based on a code block group (CBG) on a multi-physical downlink shared channel carrier, and / or feedback information for a physical downlink shared channel scheduled based on a multi-physical downlink shared channel on a multi-physical downlink shared channel carrier.

[0180] In some aspects, the feedback information for the first physical downlink shared channel and the feedback information for the second physical downlink shared channel are in different sub-codebooks, and the first physical downlink shared channel is scheduled on a multi-physical downlink shared channel (multi-PDSCH) carrier and the second physical downlink shared channel is scheduled on a single-physical downlink shared channel (single-PDSCH) carrier.

[0181] For example, the sub-codebook includes a first sub-codebook, a second sub-codebook and a third sub-codebook.

[0182] The first sub-codebook includes feedback information for a physical downlink shared channel that is scheduled on a transport block (TB) basis on a single physical downlink shared channel carrier.

[0183] The second sub-codebook includes feedback information for a physical downlink shared channel that is scheduled based on a code block group (CBG) on a single physical downlink shared channel carrier.

[0184] The third sub-codebook includes feedback information for the physical downlink shared channel scheduled on the multiple physical downlink shared channel carriers.

[0185] In some aspects, the feedback information for the third physical downlink shared channel and the feedback information for the fourth physical downlink shared channel are in different sub-codebooks, the third physical downlink shared channel is scheduled on a multi-physical downlink shared channel (multi-PDSCH) carrier based on a transport block (TB), and the fourth physical downlink shared channel is scheduled on a multi-physical downlink shared channel (multi-PDSCH) carrier based on a code block group (CBG).

[0186] For example, the sub-codebook includes a first sub-codebook and a second sub-codebook.

[0187] The first sub-codebook includes feedback information for a physical downlink shared channel scheduled on a transport block (TB) basis on a single physical downlink shared channel carrier and / or feedback information for a physical downlink shared channel scheduled on a transport block (TB) basis on a multi-physical downlink shared channel carrier.

[0188] The second sub-codebook includes feedback information for a physical downlink shared channel scheduled based on a code block group (CBG) on a single physical downlink shared channel carrier and / or feedback information for a physical downlink shared channel scheduled based on a code block group (CBG) on a multi-physical downlink shared channel carrier.

[0189] The above embodiments are merely illustrative of the present invention, and the present invention is not limited thereto, and appropriate modifications may be made based on the above embodiments. For example, each of the above embodiments may be used alone, or one or more of the above embodiments may be used in combination.

[0190] According to this embodiment, for carriers for which multi-PDSCH scheduling is enabled, multiple sub-codebooks are generated based on information such as whether multi-PDSCH scheduling is used and / or whether code block groups (CBGs) are used, thereby making it possible to support feedback based on multi-PDSCH, and by dividing the sub-codebooks, it is possible to reduce the size of the Type 2 HARQ-ACK codebook and reduce the feedback overhead of HARQ-ACK.

[0191] <Example 7> The embodiment of the present invention provides a feedback information transmission device. The device may be, for example, a terminal device, or one or more elements or components configured in the terminal device. Descriptions of the same contents as those in the first to fifth embodiments will be omitted.

[0192] 17 is a schematic diagram of an example of a feedback information transmitting device according to an embodiment of the present invention. As shown in FIG. 17, the feedback information transmitting device 1700 includes the following units:

[0193] The receiving unit 1701 receives downlink control information transmitted by a network device, and receives a physical downlink shared channel transmitted by the network device based on the downlink control information.

[0194] The transmitting unit 1702 feeds back feedback information about the physical downlink shared channel to the network device.

[0195] In some aspects, feedback information for a physical downlink shared channel on a multi-physical downlink shared channel carrier is included in at least two sub-codebooks, one of which includes feedback information for a single physical downlink shared channel on a multi-physical downlink shared channel carrier and a physical downlink shared channel scheduled based on a transport block.

[0196] In some aspects, the first downlink control information is used for scheduling based on a multi-physical downlink shared channel, and the second downlink control information is used for scheduling based on a single-physical downlink shared channel, and a downlink control information format of the first downlink control information and a downlink control information format of the second downlink control information are different.

[0197] In some aspects, the at least two sub-codebooks include a first sub-codebook that includes feedback information for a physical downlink shared channel scheduled based on a transport block on a single physical downlink shared channel carrier and / or feedback information for a physical downlink shared channel scheduled based on a single physical downlink shared channel and a transport block on a multi-physical downlink shared channel carrier.

[0198] In some aspects, the first sub-codebook includes feedback information for at least one of semi-persistent scheduling physical downlink shared channel release on a single physical downlink shared channel carrier and / or a multi-physical downlink shared channel carrier, a semi-persistent scheduling physical downlink shared channel, or downlink control information indicating that the secondary cell is idle.

[0199] In some aspects, the number of bits of feedback information for one downlink scheduling in the first sub-codebook is N max =max c {N TB_max,c}, where carrier c is a carrier capable of generating feedback information in the first sub-codebook, and N TB_max,c is the maximum number of transmission blocks that carrier c can support.

[0200] In some aspects, the at least two sub-codebooks further include a second sub-codebook, the second sub-codebook including feedback information for a physical downlink shared channel scheduled based on a code block group on a single physical downlink shared channel carrier and / or feedback information for a physical downlink shared channel scheduled based on a single physical downlink shared channel and a code block group on a multi-physical downlink shared channel carrier.

[0201] In some aspects, the number of bits of feedback information for one downlink scheduling in the second sub-codebook is N max =max c {N TB_max,c ×N CBG_max_TB,c}, where carrier c is a carrier capable of generating feedback information in the second sub-codebook, and N TB_max,c is the maximum number of transmission blocks that carrier c can support, and N CBG_max_TB,c is the maximum number of code block groups that each transport block can support on carrier c.

[0202] In some aspects, the at least two sub-codebooks further include a third sub-codebook, the third sub-codebook including feedback information for a physical downlink shared channel scheduled based on the multi-physical downlink shared channel on the multi-physical downlink shared channel carrier.

[0203] In some aspects, the number of bits of feedback information for one downlink scheduling in the third sub-codebook is N max =max c {N c}, and carrier c is the carrier capable of generating feedback information in the third sub-codebook.

[0204] For a carrier c where transmission based on the code block group is not enabled, N c =N TB_max,c ×N multi_PDSCH_max,c , for a carrier c for which code block group-based transmission is enabled, N c =N TB_max,c ×N CBG_max_TB,c ×N multi_PDSCH_max,c) .

[0205] N TB_max,c is the maximum number of transmission blocks that carrier c can support, and N CBG_max_TB,c is the maximum number of code block groups that each transmission block can support on carrier c, and N multi_PDSCH_max,c is the maximum number of physical downlink shared channels on carrier c for which downlink control information can be scheduled.

[0206] In some aspects, the at least two sub-codebooks further include a second sub-codebook, where the second sub-codebook includes feedback information for a physical downlink shared channel scheduled based on a code block group on a single physical downlink shared channel carrier, and / or feedback information for a physical downlink shared channel scheduled based on a single physical downlink shared channel and a code block group on a multiple physical downlink shared channel carrier, and / or feedback information for a physical downlink shared channel scheduled based on a multiple physical downlink shared channel on the multiple physical downlink shared channel carriers.

[0207] In some aspects, the number of bits of feedback information for one downlink scheduling in the second sub-codebook is N max =max c {N c}, and carrier c is the carrier capable of generating feedback information in the second sub-codebook.

[0208] For a single physical downlink shared channel carrier c on which code block group-based transmission is enabled, N c =N TB_max,c ×N CBG_max_TB,c , for a multi-physical downlink shared channel carrier c for which code block group-based transmission is not enabled, N c =N TB_max,c ×N multi_PDSCH_max,c , for a multi-physical downlink shared channel carrier c for which code block group-based transmission is enabled, N c =N TB_max,c ×N CBG_max_TB,c ×N multi_PDSCH_max,c .

[0209] N TB_max,c is the maximum number of transmission blocks that carrier c can support, and N CBG_max_TB,c is the maximum number of code block groups that each transmission block can support on carrier c, and N multi_PDSCH_max,c is the maximum number of physical downlink shared channels on carrier c for which downlink control information can be scheduled.

[0210] In some aspects, the at least two sub-codebooks further include a second sub-codebook, the second sub-codebook including feedback information for a physical downlink shared channel scheduled based on the code block group on a single physical downlink shared channel carrier.

[0211] In some aspects, the number of bits of feedback information for one downlink scheduling in the second sub-codebook is N max =max c {N TB_max,c ×N CBG_max_TB,c}, where carrier c is a carrier capable of generating feedback information in the second sub-codebook, and N TB_max,c is the maximum number of transmission blocks that carrier c can support, and N CBG_max_TB,c is the maximum number of code block groups that each transport block can support on carrier c.

[0212] In some aspects, the at least two sub-codebooks further include a third sub-codebook, the third sub-codebook including feedback information for a physical downlink shared channel scheduled based on a single physical downlink shared channel and a code block group on a multi-physical downlink shared channel carrier, and / or feedback information for a physical downlink shared channel scheduled based on a multi-physical downlink shared channel on a multi-physical downlink shared channel carrier.

[0213] In some aspects, the number of bits of feedback information for one downlink scheduling in the third sub-codebook is N max =max c {N c}, and carrier c is the carrier capable of generating feedback information in the third sub-codebook.

[0214] For a multi-physical downlink shared channel carrier c for which code block group-based transmission is not enabled, N c =N TB_max,c ×N multi_PDSCH_max,c , for a multi-physical downlink shared channel carrier c for which code block group-based transmission is enabled, N c =N TB_max,c ×N CBG_max_TB,c ×Nmulti_PDSCH_max,c .

[0215] N TB_max,c is the maximum number of transmission blocks that carrier c can support, and N CBG_max_TB,c is the maximum number of code block groups that each transmission block can support on carrier c, and N multi_PDSCH_max,c is the maximum number of physical downlink shared channels on carrier c for which downlink control information can be scheduled.

[0216] In some aspects, the feedback information for the first physical downlink shared channel and the feedback information for the second physical downlink shared channel are in different sub-codebooks, and the first physical downlink shared channel is scheduled on a multi-physical downlink shared channel carrier and the second physical downlink shared channel is scheduled on a single physical downlink shared channel carrier.

[0217] In some aspects, the sub-codebook includes a first sub-codebook, a second sub-codebook, and a third sub-codebook, where the first sub-codebook includes feedback information for a physical downlink shared channel scheduled based on a transmission block on a single physical downlink shared channel carrier, the second sub-codebook includes feedback information for a physical downlink shared channel scheduled based on a code block group on a single physical downlink shared channel carrier, and the third sub-codebook includes feedback information for a physical downlink shared channel scheduled on multiple physical downlink shared channel carriers.

[0218] In some aspects, the method, wherein the feedback information for the third physical downlink shared channel and the feedback information for the fourth physical downlink shared channel are in different sub-codebooks, the third physical downlink shared channel is scheduled based on a transmission block on the multi-physical downlink shared channel carrier, and the fourth physical downlink shared channel is scheduled based on a code block group on the multi-physical downlink shared channel carrier.

[0219] In some aspects, the sub-codebook includes a first sub-codebook and a second sub-codebook, where the first sub-codebook includes feedback information for a physical downlink shared channel scheduled on a transmission block (TB) basis on a single physical downlink shared channel carrier and / or feedback information for a physical downlink shared channel scheduled on a transmission block (TB) basis on a multiple physical downlink shared channel carrier, and the second sub-codebook includes feedback information for a physical downlink shared channel scheduled on a code block group (CBG) basis on a single physical downlink shared channel carrier and / or feedback information for a physical downlink shared channel scheduled on a code block group (CBG) basis on a multiple physical downlink shared channel carrier.

[0220] The above-mentioned embodiments are merely illustrative of the present invention, and the present invention is not limited thereto, and appropriate modifications can be made based on the above-mentioned embodiments. For example, each of the above-mentioned embodiments can be used alone, or one or more of the above-mentioned embodiments can be used in combination.

[0221] It should be noted that, although only the components or modules related to the present invention are described above, the present invention is not limited thereto. The feedback information transmitting device 1700 may further include other components or modules. For specific contents of these components or modules, reference may be made to the related art.

[0222] Furthermore, for convenience of explanation, Fig. 17 only exemplarily illustrates the connection relationships or signal directions between various components or modules, but it is clear to those skilled in the art that various related technologies such as bus connections can be used. The above-mentioned various components or modules may be implemented by hardware devices such as a processor, a memory, a transmitter, and a receiver, and the present invention is not limited thereto.

[0223] According to this embodiment, for carriers for which multi-PDSCH scheduling is enabled, multiple sub-codebooks are generated based on information such as whether multi-PDSCH scheduling is used and / or whether code block groups (CBGs) are used, thereby making it possible to support feedback based on multi-PDSCH, and by dividing the sub-codebooks, it is possible to reduce the size of the Type 2 HARQ-ACK codebook and reduce the feedback overhead of HARQ-ACK.

[0224] <Example 8> An embodiment of the present invention provides a feedback information receiving device. The device may be, for example, a network device, or one or more elements or components configured in the network device. The description of the same contents as those in the sixth embodiment will be omitted.

[0225] 18 is a schematic diagram of an example of a feedback information receiving apparatus according to an embodiment of the present invention. As shown in FIG. 18, the feedback information receiving apparatus 1800 includes the following units:

[0226] The transmitter 1801 transmits downlink control information to the terminal device and transmits a physical downlink shared channel to the terminal device.

[0227] The receiving unit 1802 receives feedback information about the physical downlink shared channel fed back by the terminal device.

[0228] In some aspects, feedback information for a physical downlink shared channel on a multi-physical downlink shared channel carrier is included in at least two sub-codebooks, one of which includes feedback information for a single physical downlink shared channel on a multi-physical downlink shared channel carrier and a physical downlink shared channel scheduled based on a transport block.

[0229] In some aspects, the feedback information for the first physical downlink shared channel and the feedback information for the second physical downlink shared channel are in different sub-codebooks, and the first physical downlink shared channel is scheduled on a multi-physical downlink shared channel carrier and the second physical downlink shared channel is scheduled on a single physical downlink shared channel carrier.

[0230] In some aspects, the feedback information for the third physical downlink shared channel and the feedback information for the fourth physical downlink shared channel are in different sub-codebooks, and the third physical downlink shared channel is scheduled on a multi-physical downlink shared channel carrier based on a transport block (TB), and the fourth physical downlink shared channel is scheduled on a multi-physical downlink shared channel (multi-PDSCH) carrier based on a code block group (CBG).

[0231] The above-mentioned embodiments are merely illustrative of the present invention, and the present invention is not limited thereto, and appropriate modifications can be made based on the above-mentioned embodiments. For example, each of the above-mentioned embodiments can be used alone, or one or more of the above-mentioned embodiments can be used in combination.

[0232] It should be noted that, although only the components or modules related to the present invention are described above, the present invention is not limited thereto. The feedback information receiving device 1800 may further include other components or modules. For specific contents of these components or modules, reference may be made to the related art.

[0233] Furthermore, for convenience of explanation, Fig. 18 only exemplarily illustrates the connection relationships or signal directions between various components or modules, but it is clear to those skilled in the art that various related technologies such as bus connections can be used. The above-mentioned various components or modules may be implemented by hardware devices such as a processor, a memory, a transmitter, and a receiver, and the present invention is not limited thereto.

[0234] According to this embodiment, for carriers for which multi-PDSCH scheduling is enabled, multiple sub-codebooks are generated based on information such as whether multi-PDSCH scheduling is used and / or whether code block groups (CBGs) are used, thereby making it possible to support feedback based on multi-PDSCH, and by dividing the sub-codebooks, it is possible to reduce the size of the Type 2 HARQ-ACK codebook and reduce the feedback overhead of HARQ-ACK.

[0235] <Example 9> The embodiment of the present invention further provides a communication system, and may refer to FIG. 1. Descriptions of contents similar to those of the first to eighth embodiments will be omitted.

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

[0237] The network device 101 transmits downlink control information to the terminal device, transmits a physical downlink shared channel to the terminal device, and receives feedback information about the physical downlink shared channel fed back by the terminal device.

[0238] The terminal device 102 receives downlink control information transmitted by the network device, receives a physical downlink shared channel transmitted by the network device based on the downlink control information, and feeds back feedback information about the physical downlink shared channel to the network device.

[0239] Here, the feedback information for the physical downlink shared channel on the multi-physical downlink shared channel carrier is included in at least two sub-codebooks, one of which includes feedback information for the single physical downlink shared channel on the multi-physical downlink shared channel carrier and the physical downlink shared channel scheduled based on the transport block.

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

[0241] The network device 101 transmits downlink control information to the terminal device, transmits a physical downlink shared channel to the terminal device, and receives feedback information about the physical downlink shared channel fed back by the terminal device.

[0242] The terminal device 102 receives downlink control information transmitted by the network device, receives a physical downlink shared channel transmitted by the network device based on the downlink control information, and feeds back feedback information about the physical downlink shared channel to the network device.

[0243] Here, the feedback information for the first physical downlink shared channel and the feedback information for the second physical downlink shared channel are in different sub-codebooks, and the first physical downlink shared channel is scheduled on a multi-physical downlink shared channel carrier, and the second physical downlink shared channel is scheduled on a single physical downlink shared channel carrier.

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

[0245] The network device 101 transmits downlink control information to the terminal device, transmits a physical downlink shared channel to the terminal device, and receives feedback information about the physical downlink shared channel fed back by the terminal device.

[0246] The terminal device 102 receives downlink control information transmitted by the network device, receives a physical downlink shared channel transmitted by the network device based on the downlink control information, and feeds back feedback information about the physical downlink shared channel to the network device.

[0247] Here, the feedback information for the third physical downlink shared channel and the feedback information for the fourth physical downlink shared channel are in different sub-codebooks, the third physical downlink shared channel is scheduled based on a transmission block on the multi-physical downlink shared channel carrier, and the fourth physical downlink shared channel is scheduled based on a code block group on the multi-physical downlink shared channel carrier.

[0248] An embodiment of the present invention further provides a network device, which may be, for example, a base station, but the present invention is not limited thereto and may be other network devices.

[0249] Fig. 19 is a schematic diagram of a network device according to an embodiment of the present invention. As shown in Fig. 19, the network device 1900 may include a processor 1910 (e.g., a central processing unit (CPU)) and a memory 1920, which is connected to the processor 1910. The memory 1920 may store various data, and may further store an information processing program 1930 and execute the program 1930 under the control of the processor 1910.

[0250] For example, the processor 1910 may execute a program to realize the feedback information receiving method described in Example 6. For example, the processor 1910 may be configured to send downlink control information to a terminal device, send a physical downlink shared channel to the terminal device, and receive feedback information about the physical downlink shared channel fed back by the terminal device.

[0251] Here, the feedback information for the physical downlink shared channel on the multi-physical downlink shared channel carrier is included in at least two sub-codebooks, one of which includes feedback information for the single physical downlink shared channel on the multi-physical downlink shared channel carrier and the physical downlink shared channel scheduled based on the transport block.

[0252] Alternatively, the feedback information for the first physical downlink shared channel and the feedback information for the second physical downlink shared channel are in different sub-codebooks, and the first physical downlink shared channel is scheduled on a multi-physical downlink shared channel carrier, and the second physical downlink shared channel is scheduled on a single physical downlink shared channel carrier.

[0253] Alternatively, the feedback information for the third physical downlink shared channel and the feedback information for the fourth physical downlink shared channel are in different sub-codebooks, and the third physical downlink shared channel is scheduled based on a transmission block on the multi-physical downlink shared channel carrier, and the fourth physical downlink shared channel is scheduled based on a code block group on the multi-physical downlink shared channel carrier.

[0254] Also, as shown in Fig. 19, the network device 1900 may further include a transceiver 1940 and an antenna 1950. The functions of the above members are similar to those of the prior art, and the description thereof will be omitted here. It is not necessary for the network device 1900 to include all the units shown in Fig. 19. Also, the network device 1900 may further include units not shown in Fig. 19, and may refer to the prior art.

[0255] The embodiment of the present invention further provides a terminal device, but the present invention is not limited thereto and may be other devices.

[0256] Fig. 20 is a schematic diagram of a terminal device according to an embodiment of the present invention. As shown in Fig. 20, the terminal device 2000 may include a processor 2010 and a memory 2020, where the memory 2020 stores data and programs and is connected to the processor 2010. It should be noted that this diagram is exemplary, and other types of structures may be used to supplement or replace this structure to realize communication functions or other functions.

[0257] For example, the processor 2010 may execute a program to realize the feedback information transmission method described in the embodiments 1 to 5. For example, the processor 2010 may be configured to receive downlink control information transmitted by a network device, receive a physical downlink shared channel transmitted by the network device based on the downlink control information, and feed back feedback information about the physical downlink shared channel to the network device.

[0258] Here, the feedback information for the physical downlink shared channel on the multi-physical downlink shared channel carrier is included in at least two sub-codebooks, one of which includes feedback information for the single physical downlink shared channel on the multi-physical downlink shared channel carrier and the physical downlink shared channel scheduled based on the transport block.

[0259] Alternatively, the feedback information for the first physical downlink shared channel and the feedback information for the second physical downlink shared channel are in different sub-codebooks, and the first physical downlink shared channel is scheduled on a multi-physical downlink shared channel carrier, and the second physical downlink shared channel is scheduled on a single physical downlink shared channel carrier.

[0260] Alternatively, the feedback information for the third physical downlink shared channel and the feedback information for the fourth physical downlink shared channel are in different sub-codebooks, and the third physical downlink shared channel is scheduled based on a transmission block on the multi-physical downlink shared channel carrier, and the fourth physical downlink shared channel is scheduled based on a code block group on the multi-physical downlink shared channel carrier.

[0261] 20, the terminal device 2000 may further include a communication module 2030, an input unit 2040, a display 2050, a power supply 2060, and the like. Here, the functions of the above units are similar to those of the prior art, and the description thereof will be omitted here. Note that the terminal device 2000 does not need to include all the units shown in FIG. 20. The terminal device 2000 may further include units not shown in FIG. 20, and may refer to the prior art.

[0262] In an embodiment of the present invention, there is further provided a computer-readable program that, when executed in a terminal device, causes the terminal device to execute the feedback information transmission method described in any of the first to fifth embodiments.

[0263] An embodiment of the present invention further provides a storage medium having a computer-readable program stored therein, the storage medium causing a terminal device to execute the feedback information transmission method described in embodiments 1 to 5 when the program is executed.

[0264] In an embodiment of the present invention, there is further provided a computer-readable program, which, when executed in a network device, causes the network device to perform the method for receiving feedback information described in embodiment 6.

[0265] An embodiment of the present invention further provides a storage medium having a computer-readable program stored thereon, the storage medium causing a network device to perform the feedback information receiving method described in embodiment 6 when the program is executed.

[0266] The above-mentioned apparatus and method of the present invention may be realized by hardware or by a combination of hardware and software.The present invention relates to a computer readable program which, when executed by a logic unit, causes the logic unit to realize the above-mentioned apparatus or components, or to realize the above-mentioned various methods or steps.The present invention relates to a storage medium for storing the above-mentioned program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0267] Each processing method in each device described with reference to the embodiments of the present invention may be implemented by hardware, a software module executed by a processor, or a combination of both. For example, one or more of the functional block diagrams shown in the drawings, or one or more combinations of the functional block diagrams, may correspond to each software module in a computer program flow, or each hardware module. These software modules may correspond to each step shown in the drawings. These hardware modules may be realized by implementing these software modules in hardware, for example, using a field programmable gate array (FPGA).

[0268] The software module may be located in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a mobile hard disk, a CD-ROM, or any other form of storage medium known to those skilled in the art. The storage medium may be connected to the processor so that the processor reads information from the storage medium and writes information to the storage medium, or the storage medium may be a component of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the mobile terminal, or in a memory card inserted in the mobile terminal. For example, if the device (e.g., a mobile terminal) uses a MEGA-SIM card or a large capacity flash memory device with a relatively large capacity, the software module may be stored in the MEGA-SIM card or the large capacity flash memory device.

[0269] One or more of the functional blocks and / or one or more combinations of functional blocks in the functional block diagrams illustrated in the drawings 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 of the functional blocks and / or one or more combinations of functional blocks in the functional block diagrams illustrated in the drawings may be implemented with, for example, a combination of computing devices, such as a combination of a DSP and a microprocessor, a combination of multiple microprocessors, one or more microprocessors in combination with a DSP communication, or any other configuration.

[0270] Although the present invention has been described above with reference to specific embodiments, the above description is merely illustrative and does not limit the scope of protection of the present invention. Various modifications and changes may be made to the present invention without departing from the spirit and principles of the present invention, and these modifications and changes are also within the scope of the present invention.

[0271] Furthermore, the following supplementary notes are disclosed regarding the embodiments including the above examples. (Appendix 1) A method for transmitting feedback information, comprising the steps of: A terminal device receives downlink control information (DCI) transmitted by a network device, and receives a physical downlink shared channel (PDSCH) transmitted by the network device based on the downlink control information; and feeding back feedback information about the physical downlink shared channel to the network device; 1. A method for providing a method for a mobile station, comprising: providing a plurality of sub-codebooks for a plurality of physical downlink shared channels (PDSCHs) on a mobile station; and transmitting the plurality of sub-codebooks for a plurality of physical downlink shared channels (PDSCHs) on a mobile station; (Appendix 2) 2. The method of claim 1, wherein first downlink control information is used for scheduling based on a multi-physical downlink shared channel (multi-PDSCH), and second downlink control information is used for scheduling based on a single-physical downlink shared channel (single-PDSCH), and a downlink control information (DCI) format of the first downlink control information and a downlink control information format of the second downlink control information are different. (Appendix 3) 3. The method of claim 1 or 2, wherein the at least two sub-codebooks include a first sub-codebook, the first sub-codebook including feedback information for a physical downlink shared channel scheduled based on a transport block on a single physical downlink shared channel carrier and / or feedback information for a physical downlink shared channel scheduled based on a single physical downlink shared channel and a transport block on a multi-physical downlink shared channel carrier. (Appendix 4) 4. The method of claim 3, wherein the first sub-codebook includes feedback information for at least one of semi-persistent scheduling physical downlink shared channel release (SPS PDSCH release), semi-persistent scheduling physical downlink shared channel (SPS PDSCH reception), or downlink control information indicating a secondary cell is dormant (DCI indicating SCell dormancy) on a single physical downlink shared channel carrier and / or a multi-physical downlink shared channel carrier. (Appendix 5) The number of bits of feedback information for one downlink scheduling in the first sub-codebook is N max =max c {N TB_max,c}, where carrier c is a carrier capable of generating feedback information in the first sub-codebook, and N TB_max,c 5. The method of claim 3 or 4, wherein: c is the maximum number of transmission blocks (TB) that carrier c can support. (Appendix 6) 6. The method of claim 3, wherein the at least two sub-codebooks further include a second sub-codebook, the second sub-codebook including feedback information for a physical downlink shared channel scheduled on a single physical downlink shared channel carrier based on a code block group (CBG), and / or feedback information for a single physical downlink shared channel and a physical downlink shared channel scheduled on a multi-physical downlink shared channel carrier based on a code block group (CBG). (Appendix 7) The number of feedback information bits for one downlink scheduling in the second sub-codebook is N max =max c {N TB_max,c ×N CBG_max_TB,c}, where carrier c is a carrier capable of generating feedback information in the second sub-codebook, and N TB_max,c is the maximum number of transmission blocks (TB) that carrier c can support, and N CBG_max_TB,c The method described in Supplementary Note 6, wherein, is the maximum number of code block groups (CBGs) that each transport block (TB) can support on carrier c. (Appendix 8) 8. The method of claim 3, wherein the at least two sub-codebooks further include a third sub-codebook, the third sub-codebook including feedback information for a physical downlink shared channel scheduled based on a multi-physical downlink shared channel on a multi-physical downlink shared channel carrier. (Appendix 9) The number of bits of feedback information for one downlink scheduling in the third sub-codebook is N max =max c {N c}, and carrier c is a carrier capable of generating feedback information in the third sub-codebook; For a carrier c where transmission based on the code block group is not enabled, N c =N TB_max,c ×N multi_PDSCH_max,c , for a carrier c for which code block group-based transmission is enabled, N c =N TB_max,c ×N CBG_max_TB,c ×N multi_PDSCH_max,c) , N TB_max,c is the maximum number of transmission blocks (TB) that carrier c can support, and N CBG_max_TB,c is the maximum number of code block groups (CBGs) that each transport block (TB) can support on carrier c, and N multi_PDSCH_max,c 9. The method of claim 8, wherein c is the maximum number of physical downlink shared channels on carrier c for which downlink control information (DCI) can be scheduled. (Appendix 10) 6. The method of claim 3, wherein the at least two sub-codebooks further include a second sub-codebook, the second sub-codebook including feedback information for a physical downlink shared channel scheduled on a single physical downlink shared channel carrier based on a code block group (CBG), and / or feedback information for a single physical downlink shared channel and a physical downlink shared channel scheduled on a multi-physical downlink shared channel carrier based on a code block group (CBG), and / or feedback information for a physical downlink shared channel scheduled on a multi-physical downlink shared channel carrier based on a multi-physical downlink shared channel. (Appendix 11) The number of feedback information bits for one downlink scheduling in the second sub-codebook is N max =max c {N c}, and carrier c is a carrier capable of generating feedback information in the second sub-codebook; For a single physical downlink shared channel carrier c on which code block group-based transmission is enabled, N c =N TB_max,c ×N CBG_max_TB,c , for a multi-physical downlink shared channel carrier c for which code block group-based transmission is not enabled, N c =N TB_max,c ×N multi_PDSCH_max,c , for a multi-physical downlink shared channel carrier c for which code block group-based transmission is enabled, N c =N TB_max,c ×N CBG_max_TB,c ×N multi_PDSCH_max,c , N TB_max,c is the maximum number of transmission blocks (TB) that carrier c can support, and N CBG_max_TB,c is the maximum number of code block groups (CBGs) that each transport block (TB) can support on carrier c, and N multi_PDSCH_max,c 11. The method of claim 10, wherein c is the maximum number of physical downlink shared channels on carrier c for which downlink control information (DCI) can be scheduled. (Appendix 12) 6. The method of claim 3, wherein the at least two sub-codebooks further include a second sub-codebook, the second sub-codebook including feedback information for a physical downlink shared channel scheduled based on a code block group (CBG) on a single physical downlink shared channel carrier. (Appendix 13) The number of feedback information bits for one downlink scheduling in the second sub-codebook is N max =max c {N TB_max,c ×N CBG_max_TB,c}, where carrier c is a carrier capable of generating feedback information in the second sub-codebook, and N TB_max,c is the maximum number of transmission blocks (TB) that carrier c can support, and N CBG_max_TB,c13. The method of claim 12, wherein, c is the maximum number of code block groups (CBGs) that each transport block (TB) can support on carrier c. (Appendix 14) 14. The method of claim 12 or 13, wherein the at least two sub-codebooks further include a third sub-codebook, the third sub-codebook including feedback information for a single physical downlink shared channel and a physical downlink shared channel scheduled on a multi-physical downlink shared channel carrier based on a code block group (CBG), and / or feedback information for a physical downlink shared channel scheduled on a multi-physical downlink shared channel carrier based on a multi-physical downlink shared channel. (Appendix 15) The number of bits of feedback information for one downlink scheduling in the third sub-codebook is N max =max c {N c}, and carrier c is a carrier capable of generating feedback information in the third sub-codebook; For a multi-physical downlink shared channel carrier c for which code block group-based transmission is not enabled, N c =N TB_max,c ×N multi_PDSCH_max,c , for a multi-physical downlink shared channel carrier c for which code block group-based transmission is enabled, N c =N TB_max,c ×N CBG_max_TB,c ×N multi_PDSCH_max,c , N TB_max,c is the maximum number of transmission blocks (TB) that carrier c can support, and N CBG_max_TB,c is the maximum number of code block groups (CBGs) that each transport block (TB) can support on carrier c, and N multi_PDSCH_max,c is the maximum number of physical downlink shared channels on carrier c for which downlink control information (DCI) can be scheduled. (Appendix 16) A method for transmitting feedback information, comprising the steps of: A terminal device receives downlink control information (DCI) transmitted by a network device, and receives a physical downlink shared channel (PDSCH) transmitted by the network device based on the downlink control information; and feeding back feedback information about the physical downlink shared channel to the network device; 11. A method for providing a method for providing a first physical downlink shared channel and a second physical downlink shared channel, the feedback information for a first physical downlink shared channel and the feedback information for a second physical downlink shared channel being in different sub-codebooks, the first physical downlink shared channel being scheduled on a multi-physical downlink shared channel (multi-PDSCH) carrier, and the second physical downlink shared channel being scheduled on a single-physical downlink shared channel (single-PDSCH) carrier. (Appendix 17) the sub-codebook includes a first sub-codebook, a second sub-codebook and a third sub-codebook; The first sub-codebook includes feedback information for a physical downlink shared channel scheduled based on a transport block (TB) on a single physical downlink shared channel carrier; the second sub-codebook includes feedback information for a physical downlink shared channel scheduled based on a code block group (CBG) on a single physical downlink shared channel carrier; 17. The method of claim 16, wherein the third sub-codebook includes feedback information for a physical downlink shared channel scheduled on multiple physical downlink shared channel carriers. (Appendix 18) A method for transmitting feedback information, comprising the steps of: A terminal device receives downlink control information (DCI) transmitted by a network device, and receives a physical downlink shared channel (PDSCH) transmitted by the network device based on the downlink control information; and feeding back feedback information about the physical downlink shared channel to the network device; and wherein feedback information for a third physical downlink shared channel and feedback information for a fourth physical downlink shared channel are in different sub-codebooks, the third physical downlink shared channel is scheduled on a multi-physical downlink shared channel (multi-PDSCH) carrier based on a transport block (TB), and the fourth physical downlink shared channel is scheduled on a multi-physical downlink shared channel (multi-PDSCH) carrier based on a code block group (CBG). (Appendix 19) the sub-codebook includes a first sub-codebook and a second sub-codebook; The first sub-codebook includes feedback information for a physical downlink shared channel scheduled based on a transport block (TB) on a single physical downlink shared channel carrier and / or feedback information for a physical downlink shared channel scheduled based on a transport block (TB) on a multi-physical downlink shared channel carrier; 19. The method of claim 18, wherein the second sub-codebook includes feedback information for a physical downlink shared channel scheduled on a code block group (CBG) basis on a single physical downlink shared channel carrier and / or feedback information for a physical downlink shared channel scheduled on a code block group (CBG) basis on multiple physical downlink shared channel carriers. (Appendix 20) A method for receiving feedback information, comprising the steps of: A network device transmits downlink control information (DCI) to a terminal device and transmits a physical downlink shared channel (PDSCH) to the terminal device; receiving feedback information about the physical downlink shared channel fed back by the terminal device; 11. A method according to claim 10, wherein feedback information for a physical downlink shared channel on a multi-physical downlink shared channel carrier is included in at least two sub-codebooks, one of which includes feedback information for a single physical downlink shared channel on a multi-physical downlink shared channel carrier and a physical downlink shared channel scheduled based on a transport block. (Appendix 21) A method for receiving feedback information, comprising the steps of: A network device transmits downlink control information (DCI) to a terminal device and transmits a physical downlink shared channel (PDSCH) to the terminal device; receiving feedback information about the physical downlink shared channel fed back by the terminal device; 11. A method for providing a method for providing a first physical downlink shared channel and a second physical downlink shared channel, the feedback information for a first physical downlink shared channel and the feedback information for a second physical downlink shared channel being in different sub-codebooks, the first physical downlink shared channel being scheduled on a multi-physical downlink shared channel (multi-PDSCH) carrier, and the second physical downlink shared channel being scheduled on a single-physical downlink shared channel (single-PDSCH) carrier. (Appendix 22) A method for receiving feedback information, comprising the steps of: A network device transmits downlink control information (DCI) to a terminal device and transmits a physical downlink shared channel (PDSCH) to the terminal device; receiving feedback information about the physical downlink shared channel fed back by the terminal device; and wherein feedback information for a third physical downlink shared channel and feedback information for a fourth physical downlink shared channel are in different sub-codebooks, the third physical downlink shared channel is scheduled on a multi-physical downlink shared channel (multi-PDSCH) carrier based on a transport block (TB), and the fourth physical downlink shared channel is scheduled on a multi-physical downlink shared channel (multi-PDSCH) carrier based on a code block group (CBG). (Appendix 23) A terminal device including a memory in which a computer program is stored and a processor, the processor being configured to execute the computer program to realize a method for transmitting feedback information according to any one of appendices 1 to 19. (Appendix 24) A network device comprising: a memory having a computer program stored therein; and a processor, the processor being configured to execute the computer program to realize a method for receiving feedback information according to any one of appendices 20 to 22. (Appendix 25) A communication system including a network device and a terminal device, The network device transmits downlink control information to the terminal device, transmits a physical downlink shared channel to the terminal device, and receives feedback information about the physical downlink shared channel fed back by the terminal device; The terminal device receives downlink control information transmitted by the network device, receives a physical downlink shared channel transmitted by the network device based on the downlink control information, and feeds back feedback information about the physical downlink shared channel to the network device; A communication system, wherein feedback information for a physical downlink shared channel on a multi-physical downlink shared channel carrier is included in at least two sub-codebooks, one of which includes feedback information for a single physical downlink shared channel on the multi-physical downlink shared channel carrier and a physical downlink shared channel scheduled based on a transmission block. (Appendix 26) A communication system including a network device and a terminal device, The network device transmits downlink control information to the terminal device, transmits a physical downlink shared channel to the terminal device, and receives feedback information about the physical downlink shared channel fed back by the terminal device; The terminal device receives downlink control information transmitted by the network device, receives a physical downlink shared channel transmitted by the network device based on the downlink control information, and feeds back feedback information about the physical downlink shared channel to the network device; A communication system, wherein feedback information for a first physical downlink shared channel and feedback information for a second physical downlink shared channel are in different sub-codebooks, the first physical downlink shared channel is scheduled on a multi-physical downlink shared channel carrier, and the second physical downlink shared channel is scheduled on a single physical downlink shared channel carrier. (Appendix 27) A communication system including a network device and a terminal device, The network device transmits downlink control information to the terminal device, transmits a physical downlink shared channel to the terminal device, and receives feedback information about the physical downlink shared channel fed back by the terminal device; The terminal device receives downlink control information transmitted by the network device, receives a physical downlink shared channel transmitted by the network device based on the downlink control information, and feeds back feedback information about the physical downlink shared channel to the network device; a third physical downlink shared channel and a fourth physical downlink shared channel, the feedback information being in different sub-codebooks, the third physical downlink shared channel being scheduled based on a transmission block on a multi-physical downlink shared channel carrier, and the fourth physical downlink shared channel being scheduled based on a code block group on a multi-physical downlink shared channel carrier.

Claims

1. A feedback information transmitting device, a receiver for receiving downlink control information transmitted by a network device, and receiving a physical downlink shared channel transmitted by the network device based on the downlink control information; a transmitter for feeding back feedback information about the physical downlink shared channel to the network device; Feedback information for multiple types of physical downlink shared channels in a multi-physical downlink shared channel cell is included in two sub-codebooks, one of which includes feedback information for a first type of physical downlink shared channel scheduled based on single physical downlink shared channel scheduling and a transport block in the multi-physical downlink shared channel cell; The first-type physical downlink shared channel is scheduled in the multi-physical downlink shared channel cell based on single physical downlink shared channel scheduling and a transport block, at least 11. An apparatus, wherein downlink control information indicates a first row including one SLIV in a configured time domain resource allocation table, the table including at least the first row and a second row including a plurality of SLIVs.

2. 2. The apparatus of claim 1, wherein first downlink control information is used for multi-physical downlink shared channel scheduling and second downlink control information is used for single-physical downlink shared channel scheduling, and a downlink control information format of the first downlink control information and a downlink control information format of the second downlink control information are different.

3. 2. The apparatus of claim 1, wherein the two sub-codebooks include a first sub-codebook that includes feedback information for a physical downlink shared channel that is scheduled based on a transport block in a single physical downlink shared channel cell and feedback information for a first type physical downlink shared channel that is scheduled based on a single physical downlink shared channel scheduling and a transport block in a multi-physical downlink shared channel cell.

4. 4. The apparatus of claim 3, wherein the first sub-codebook includes feedback information for at least one of semi-persistent scheduling physical downlink shared channel release in a single physical downlink shared channel cell and / or a multi-physical downlink shared channel cell, a semi-persistent scheduling physical downlink shared channel, or downlink control information indicating a secondary cell is idle.

5. 4. The apparatus of claim 3, wherein the two sub-codebooks further include a second sub-codebook, the second sub-codebook including feedback information for a physical downlink shared channel scheduled based on code block groups in a single physical downlink shared channel cell and / or feedback information for a physical downlink shared channel scheduled based on single physical downlink shared channel scheduling and code block groups in a multi-physical downlink shared channel cell.

6. 6. The apparatus of claim 5, wherein the two sub-codebooks further include a third sub-codebook, the third sub-codebook including feedback information for a physical downlink shared channel scheduled based on multi-physical downlink shared channel scheduling in a multi-physical downlink shared channel cell.

7. 4. The apparatus of claim 3, wherein the two sub-codebooks further include a second sub-codebook, the second sub-codebook including feedback information for a physical downlink shared channel scheduled based on multi-physical downlink shared channel scheduling in a multi-physical downlink shared channel cell.

8. 4. The apparatus of claim 3, wherein the two sub-codebooks further include a second sub-codebook, the second sub-codebook including feedback information for a second type of physical downlink shared channel scheduled based on code block groups in a single physical downlink shared channel cell.

9. The number of bits of feedback information for one downlink scheduling in the second sub-codebook is N ｍａｘ = max ｃ {N ＴＢ＿ｍａｘ，ｃ ×N ＣＢＧ＿ｍａｘ＿ＴＢ，ｃ }, cell c is a cell capable of generating feedback information in the second sub-codebook, and N ＴＢ＿ｍａｘ，ｃ is the maximum number of transmission blocks that cell c can support, and N ＣＢＧ＿ｍａｘ＿ＴＢ，ｃ 9. The apparatus of claim 8, wherein x is the maximum number of code block groups that each transport block can support in cell c.

10. 9. The apparatus of claim 8, wherein the two sub-codebooks further include a third sub-codebook, the third sub-codebook including feedback information for a physical downlink shared channel scheduled based on a single physical downlink shared channel and a code block group in a multi-physical downlink shared channel cell, and / or feedback information for a physical downlink shared channel scheduled based on a multi-physical downlink shared channel in a multi-physical downlink shared channel cell.

11. The number of bits of feedback information for one downlink scheduling in the third sub-codebook is N ｍａｘ = max ｃ {N ｃ }, and cell c is a cell capable of generating feedback information in the third sub-codebook; For a multi-physical downlink shared channel cell c where code block group-based transmission is not enabled, ｃ = N ＴＢ＿ｍａｘ，ｃ ×N ｍｕｌｔｉ＿ＰＤＳＣＨ＿ｍａｘ，ｃ , for a multi-physical downlink shared channel cell c in which code block group-based transmission is enabled, N ｃ = N ＴＢ＿ｍａｘ，ｃ ×N ＣＢＧ＿ｍａｘ＿ＴＢ，ｃ ×N ｍｕｌｔｉ＿ＰＤＳＣＨ＿ｍａｘ，ｃ , N ＴＢ＿ｍａｘ，ｃ is the maximum number of transmission blocks that cell c can support, and N ＣＢＧ＿ｍａｘ＿ＴＢ，ｃ is the maximum number of code block groups that each transmission block can support in cell c, and N ｍｕｌｔｉ＿ＰＤＳＣＨ＿ｍａｘ，ｃ 11. The apparatus of claim 10, wherein: ##EQU1## is a maximum number of physical downlink shared channels in cell c for which downlink control information can be scheduled.

12. A feedback information receiving device, a transmitter for transmitting downlink control information to a terminal device and transmitting a physical downlink shared channel to the terminal device; a receiver for receiving feedback information about the physical downlink shared channel fed back by the terminal device; Feedback information for multiple types of physical downlink shared channels in a multi-physical downlink shared channel cell is included in two sub-codebooks, one of which includes feedback information for a first type of physical downlink shared channel scheduled based on single physical downlink shared channel scheduling and a transport block in the multi-physical downlink shared channel cell; The first-type physical downlink shared channel is scheduled in the multi-physical downlink shared channel cell based on single physical downlink shared channel scheduling and a transport block, at least 11. An apparatus, wherein downlink control information indicates a first row including one SLIV in a configured time domain resource allocation table, the table including at least the first row and a second row including a plurality of SLIVs.

13. A communication system including a network device and a terminal device, The network device transmits downlink control information to the terminal device, transmits a physical downlink shared channel to the terminal device, and receives feedback information about the physical downlink shared channel fed back by the terminal device; The terminal device receives downlink control information transmitted by the network device, receives a physical downlink shared channel transmitted by the network device based on the downlink control information, and feeds back feedback information about the physical downlink shared channel to the network device; Feedback information for multiple types of physical downlink shared channels in a multi-physical downlink shared channel cell is included in two sub-codebooks, one of which includes feedback information for a first type of physical downlink shared channel scheduled based on single physical downlink shared channel scheduling and a transport block in the multi-physical downlink shared channel cell; The first-type physical downlink shared channel is scheduled in the multi-physical downlink shared channel cell based on single physical downlink shared channel scheduling and a transport block, at least 1. A communication system, wherein downlink control information indicates a first row including one SLIV in a configured time domain resource allocation table, the table including at least the first row and a second row including a plurality of SLIVs.

Images