WO2022077367A1 - 反馈信息的发送和接收方法以及装置 - Google Patents

反馈信息的发送和接收方法以及装置 Download PDF

Info

Publication number
WO2022077367A1
WO2022077367A1 PCT/CN2020/121236 CN2020121236W WO2022077367A1 WO 2022077367 A1 WO2022077367 A1 WO 2022077367A1 CN 2020121236 W CN2020121236 W CN 2020121236W WO 2022077367 A1 WO2022077367 A1 WO 2022077367A1
Authority
WO
WIPO (PCT)
Prior art keywords
physical downlink
shared channel
downlink shared
max
carrier
Prior art date
Application number
PCT/CN2020/121236
Other languages
English (en)
French (fr)
Inventor
张健
蒋琴艳
陈哲
张磊
Original Assignee
富士通株式会社
张健
蒋琴艳
陈哲
张磊
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 富士通株式会社, 张健, 蒋琴艳, 陈哲, 张磊 filed Critical 富士通株式会社
Priority to KR1020237011832A priority Critical patent/KR20230065311A/ko
Priority to CN202080104979.0A priority patent/CN116114193B/zh
Priority to JP2023521053A priority patent/JP2023545705A/ja
Priority to PCT/CN2020/121236 priority patent/WO2022077367A1/zh
Priority to EP20957146.2A priority patent/EP4231753A4/en
Publication of WO2022077367A1 publication Critical patent/WO2022077367A1/zh
Priority to US18/125,235 priority patent/US20230232411A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/232—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0613—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission
    • H04B7/0615—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal
    • H04B7/0619—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal using feedback from receiving side
    • H04B7/0636—Feedback format
    • H04B7/0639—Using selective indices, e.g. of a codebook, e.g. pre-distortion matrix index [PMI] or for beam selection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1854—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1861—Physical mapping arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1887—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A) or DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A) or DMT the frequencies being arranged in component carriers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK

Definitions

  • the embodiments of the present application relate to the field of communication technologies.
  • the physical downlink control channel (PDCCH, Physical Downlink Control Channel) / physical downlink shared channel (PDSCH, Physical Downlink Shared Channel)
  • PDCCH Physical Downlink Control Channel
  • PDSCH Physical Downlink shared channel
  • SCS Subcarrier Spacing
  • one downlink control information can only schedule one PDSCH (hereinafter referred to as single-PDSCH scheduling).
  • the terminal device can feed back feedback information for PDSCH scheduled by one or more DCIs within a period of time, for example, the feedback information is a hybrid automatic repeat request (HARQ, Hybrid Automatic Repeat reQuest) codebook (codebook), also known as HARQ- ACK or HARQ-ACK codebook.
  • HARQ Hybrid Automatic Repeat reQuest
  • codebook also known as HARQ- ACK or HARQ-ACK codebook.
  • NR Rel-17 is currently researching support for higher frequencies (52.6GHz to 71GHz). Higher frequencies require additional support for larger SCSs (greater than 120kHz), and larger SCSs mean shorter slot lengths. Due to the limitation of processing capability, the processing time of the terminal equipment cannot be reduced proportionally with the length of the time slot. Therefore, the processing requirements of terminal devices operating at higher frequencies are somewhat relaxed compared to those at lower frequencies. For example, the terminal device cannot blindly detect the PDCCH too frequently. In this case, there may be more time slots between two adjacent PDCCH blind detection opportunities, that is, the scheduling opportunities for a certain terminal device are reduced to a certain extent.
  • NR Rel-17 is studying support for multi-PDSCH (multi-PDSCH) scheduling.
  • multi-PDSCH scheduling one DCI can schedule more than one PDSCH.
  • terminal devices operating at high frequencies eg, 52.6 GHz to 71 GHz
  • supporting multi-PDSCH scheduling is beneficial to achieve a compromise between PDSCH scheduling flexibility and device processing capability, and can reduce DCI scheduling overhead. Therefore, multi-PDSCH scheduling may become a new feature supported when operating at 52.6GHz to 71GHz.
  • embodiments of the present application provide a method and apparatus for sending and receiving feedback information.
  • a method for sending feedback information including:
  • the terminal device receives the downlink control information sent by the network device;
  • the feedback information for the physical downlink shared channel on the multiple physical downlink shared channel carriers is included in at least two sub-codebooks, and one of the sub-codebooks includes feedback information for the following physical downlink shared channels: the physical downlink shared channel Channels are scheduled based on a single physical downlink shared channel and transport blocks on multiple physical downlink shared channel carriers.
  • an apparatus for sending feedback information including:
  • a receiving unit which receives downlink control information sent by a network device, and receives a physical downlink shared channel sent by the network device according to the downlink control information;
  • a sending unit which feeds back the feedback information for the physical downlink shared channel to the network device
  • the feedback information for the physical downlink shared channel on the multiple physical downlink shared channel carriers is included in at least two sub-codebooks, and one of the sub-codebooks includes feedback information for the following physical downlink shared channels: the physical downlink shared channel Channels are scheduled based on a single physical downlink shared channel and transport blocks on multiple physical downlink shared channel carriers.
  • a method for receiving feedback information including:
  • the network device sends downlink control information to the terminal device
  • the feedback information for the physical downlink shared channel on the multiple physical downlink shared channel carriers is included in at least two sub-codebooks, and one of the sub-codebooks includes feedback information for the following physical downlink shared channels: the physical downlink shared channel Channels are scheduled based on a single physical downlink shared channel and transport blocks on multiple physical downlink shared channel carriers
  • a device for receiving feedback information including:
  • a sending unit which sends downlink control information to a terminal device; sends a physical downlink shared channel to the terminal device;
  • a receiving unit which receives the feedback information of the terminal equipment for the physical downlink shared channel
  • the feedback information for the physical downlink shared channel on the multiple physical downlink shared channel carriers is included in at least two sub-codebooks, and one of the sub-codebooks includes feedback information for the following physical downlink shared channels: the physical downlink shared channel Channels are scheduled based on a single physical downlink shared channel and transport blocks on multiple physical downlink shared channel carriers.
  • a communication system including:
  • a network device sending downlink control information to a terminal device; sending a physical downlink shared channel to the terminal device; and receiving feedback information from the terminal device for the physical downlink shared channel;
  • a terminal device which receives the downlink control information sent by the network device, and receives the physical downlink shared channel sent by the network device according to the downlink control information; The feedback information of the shared channel;
  • the feedback information for the physical downlink shared channel on the multiple physical downlink shared channel carriers is included in at least two sub-codebooks, and one of the sub-codebooks includes feedback information for the following physical downlink shared channels: the physical downlink shared channel Channels are scheduled based on a single physical downlink shared channel and transport blocks on multiple physical downlink shared channel carriers.
  • One of the beneficial effects of the embodiments of the present application is: for a carrier with multi-PDSCH scheduling enabled, based on information such as whether to use multi-PDSCH scheduling and/or whether to use Code Block Group (CBG, Code Block Group) transmission Generate multiple sub-codebooks; thus not only can support multi-PDSCH-based feedback, but also by dividing the sub-codebooks, the size of the Type 2 HARQ-ACK codebook can be reduced, and the feedback overhead of HARQ-ACK can be reduced.
  • CBG Code Block Group
  • FIG. 1 is a schematic diagram of a communication system according to an embodiment of the present application.
  • 2A is an example diagram of dynamically determining feedback information using DAI according to an embodiment of the present application
  • FIG. 2B is an example diagram of multi-PDSCH scheduling according to an embodiment of the present application.
  • FIG. 3 is an example diagram of a carrier aggregation scenario according to an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a method for sending feedback information according to an embodiment of the present application.
  • FIG. 5 is an exemplary diagram of a first sub-codebook according to an embodiment of the present application.
  • FIG. 6 is an exemplary diagram of a second sub-codebook according to an embodiment of the present application.
  • FIG. 7 is an exemplary diagram of a third sub-codebook according to an embodiment of the present application.
  • FIG. 8 is another example diagram of the second sub-codebook in an embodiment of the present application.
  • Fig. 9 is another example diagram of the second sub-codebook of an embodiment of the present application.
  • FIG. 10 is another example diagram of the third sub-codebook in the embodiment of the present application.
  • FIG. 11 is another example diagram of the first sub-codebook according to an embodiment of the present application.
  • FIG. 12 is another example diagram of the second sub-codebook according to an embodiment of the present application.
  • FIG. 13 is another example diagram of the third sub-codebook in the embodiment of the present application.
  • FIG. 14 is another example diagram of the first sub-codebook according to an embodiment of the present application.
  • FIG. 15 is another example diagram of the second sub-codebook according to an embodiment of the present application.
  • 16 is a schematic diagram of a method for receiving feedback information according to an embodiment of the present application.
  • FIG. 17 is a schematic diagram of an apparatus for sending feedback information according to an embodiment of the present application.
  • FIG. 18 is a schematic diagram of an apparatus for receiving feedback information according to an embodiment of the present application.
  • FIG. 19 is a schematic diagram of a network device according to an embodiment of the present application.
  • FIG. 20 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • the terms “first”, “second”, etc. are used to distinguish different elements in terms of numelation, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be referred to by these terms restricted.
  • the term “and/or” includes any and all combinations of one or more of the associated listed items.
  • the terms “comprising”, “including”, “having”, etc. refer to the presence of stated features, elements, elements or components, but do not preclude the presence or addition of one or more other features, elements, elements or components.
  • the term "communication network” or “wireless communication network” may refer to a network that conforms to any of the following communication standards, such as Long Term Evolution (LTE, Long Term Evolution), Long Term Evolution Enhanced (LTE-A, LTE- Advanced), Wideband Code Division Multiple Access (WCDMA, Wideband Code Division Multiple Access), High-Speed Packet Access (HSPA, High-Speed Packet Access) and so on.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution Enhanced
  • WCDMA Wideband Code Division Multiple Access
  • High-Speed Packet Access High-Speed Packet Access
  • HSPA High-Speed Packet Access
  • the communication between devices in the communication system can be carried out according to communication protocols at any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G , New Radio (NR, New Radio), etc., and/or other communication protocols currently known or to be developed in the future.
  • Network device refers to, for example, a device in a communication system that connects a terminal device to a communication network and provides services for the terminal device.
  • Network devices may include but are not limited to the following devices: base station (BS, Base Station), access point (AP, Access Point), transmission and reception point (TRP, Transmission Reception Point), broadcast transmitter, mobility management entity (MME, Mobile Management Entity), gateway, server, radio network controller (RNC, Radio Network Controller), base station controller (BSC, Base Station Controller) and so on.
  • the base station may include but is not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB), and 5G base station (gNB), etc., and may also include a remote radio head (RRH, Remote Radio Head) , Remote Radio Unit (RRU, Remote Radio Unit), relay (relay) or low power node (eg femeto, pico, etc.).
  • RRH Remote Radio Head
  • RRU Remote Radio Unit
  • relay relay
  • low power node eg femeto, pico, etc.
  • base station may include some or all of their functions, 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.
  • the term "user equipment” (UE, User Equipment) or “terminal equipment” (TE, Terminal Equipment or Terminal Device), for example, refers to a device that accesses a communication network through a network device and receives network services.
  • a terminal device may be fixed or mobile, and may also be referred to as a mobile station (MS, Mobile Station), a terminal, a subscriber station (SS, Subscriber Station), an access terminal (AT, Access Terminal), a station, and the like.
  • the terminal device may include but is not limited to the following devices: Cellular Phone (Cellular Phone), Personal Digital Assistant (PDA, Personal Digital Assistant), wireless modem, wireless communication device, handheld device, machine type communication device, laptop computer, Cordless phones, smartphones, smart watches, digital cameras, and more.
  • Cellular Phone Cellular Phone
  • PDA Personal Digital Assistant
  • wireless modem wireless communication device
  • handheld device machine type communication device
  • laptop computer Cordless phones, smartphones, smart watches, digital cameras, and more.
  • the terminal device may also be a machine or device that performs monitoring or measurement, such as but not limited to: Machine Type Communication (MTC, Machine Type Communication) terminals, In-vehicle communication terminals, device-to-device (D2D, Device to Device) terminals, machine-to-machine (M2M, Machine to Machine) terminals, etc.
  • MTC Machine Type Communication
  • D2D Device to Device
  • M2M Machine to Machine
  • network side refers to one side of the network, which may be a certain base station, and may also include one or more network devices as described above.
  • user side or “terminal side” or “terminal device side” refers to the side of a user or terminal, which may be a certain UE, or may include one or more terminal devices as above.
  • equipment may refer to network equipment or terminal equipment.
  • FIG. 1 is a schematic diagram of a communication system according to an embodiment of the present application, which schematically illustrates a situation in which a terminal device and a network device are used as an example.
  • a communication system 100 may include a network device 101 and a terminal device 102 .
  • FIG. 1 only takes one terminal device and one network device as an example for description, but the embodiment of the present application is not limited to this, for example, there may also be multiple terminal devices.
  • Enhanced Mobile Broadband eMBB, enhanced Mobile Broadband
  • Massive Machine Type Communication mMTC, massive Machine Type Communication
  • Ultra-Reliable and Low Latency Communication URLLC, Ultra-Reliable and Low.
  • -Latency Communication etc.
  • NR Rel-15 and Rel-16 provide support for Type 2 HARQ-ACK codebooks, and can use the Downlink Assignment Index (DAI, Downlink Assignment Index) mechanism to dynamically determine the number of HARQ-ACK bits fed back.
  • the Type 2 HARQ-ACK codebook is a dynamic HARQ-ACK codebook.
  • the terminal device generates the Type 2 HARQ-ACK codebook according to the counter DAI and total DAI indicated by the DCI.
  • FIG. 2A is an example diagram of dynamically determining feedback information using DAI according to an embodiment of the present application, which schematically illustrates the Type 2 HARQ-ACK codebook.
  • counter DAI continuously counts the carrier and DCI
  • total DAI indicates the total number of DCI accumulated in the current time slot (slot).
  • the Type 2 HARQ-ACK codebook consists of two sub-codebooks, corresponding to TB-based transmission and CBG-based transmission, respectively.
  • TB-based transmission is equivalent to "CBG-based transmission” not enabled.
  • Counter DAI and total DAI are counted independently within the subcodebook.
  • counter DAI and total DAI in Figure 2A indicate absolute values of counts.
  • the number of HARQ-ACK bits scheduled for each DCI is determined according to the largest number of HARQ-ACK bits among all carriers included in the sub-codebook.
  • a carrier included in the sub-codebook means that the carrier can generate feedback information in the sub-codebook, or the sub-codebook includes feedback information for the carrier.
  • CC represents a component carrier (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 the carrier can support.
  • the first sub-codebook includes HARQ-ACK for 6 schedulings. Since the maximum number of HARQ-ACK bits is 2, a total of 12 bits of HARQ-ACK are required; the second sub-codebook includes HARQ-ACK for 7 For the secondary scheduled HARQ-ACK, since the maximum number of HARQ-ACK bits is 8, a total of 56 bits of HARQ-ACK are required.
  • the first sub-codebook includes feedback information for PDSCH scheduled by fallback DCI (DCI format 1_0) on a carrier that enables CBG-based transmission.
  • the final Type 2 HARQ-ACK codebook is obtained by concatenating two sub-codebooks, including a total of 68-bit HARQ-ACK.
  • the type 2 HARQ-ACK codebook For the type 2 HARQ-ACK codebook, if the terminal device misses the DCI detection, it will be inconsistent with the network device's understanding of the codebook size. To avoid this problem, the type 2 HARQ-ACK codebook generates 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 to NACK.
  • FIG. 2B is an example diagram of multi-PDSCH scheduling according to an embodiment of the present application.
  • one DCI schedules multiple PDSCHs (eg PDSCH#0, PDSCH#1, PDSCH#2...), and feedback information for the multiple PDSCHs is sent to the network device at the same time.
  • a multi-PDSCH carrier is a carrier with the function of scheduling multiple PDSCHs through one DCI (multi-PDSCH function) enabled (multi-PDSCH function); a single-PDSCH carrier is disabled (disabled) through a The DCI schedules multiple carriers for the function of PDSCH.
  • the carrier (Carrier) in the embodiments of the present application may be replaced by a carrier component (CC, Component Carrier), a serving cell (serving cell), a cell (cell), etc., and the present application is not limited thereto.
  • one carrier is a multi-PDSCH carrier or a single-PDSCH carrier.
  • one DCI can schedule one or more PDSCHs; for a single-PDSCH carrier, one DCI can schedule only one PDSCH.
  • One PDSCH can carry one or more TBs. According to the NR standard, one PDSCH can carry at most two TBs.
  • the carrier can be determined according to a time-domain resource allocation table configured by Radio Resource Control (RRC, Radio Resource Control) or System Information Block (SIB, System Information Block).
  • RRC Radio Resource Control
  • SIB System Information Block
  • a row in the table can indicate the time domain resources and/or mapping types of multiple PDSCHs, for example, multiple SLIV (Start and length indicator values) and/or mapping types ( mapping type)
  • the carrier is a multi-PDSCH carrier, otherwise the carrier is a single-PDSCH carrier.
  • the carrier is a multi-PDSCH carrier, otherwise the carrier is a single-PDSCH carrier.
  • NDI New Data Indicator
  • RV Redundancy Version
  • a carrier is configured with multi-PDSCH parameters, it means that the carrier is enabled with the multi-PDSCH function, then the carrier is a multi-PDSCH carrier; otherwise, the carrier is a single-PDSCH carrier.
  • scheduling based on multi-PDSCH refers to scheduling more than one PDSCH with one DCI; scheduling based on single-PDSCH refers to scheduling one PDSCH with one DCI.
  • a single-PDSCH carrier can only support scheduling based on single-PDSCH; a multi-PDSCH carrier can support scheduling based on multi-PDSCH and scheduling based on single-PDSCH. Assuming that a certain DCI schedules the PDSCH on carrier c, the DCI may come from carrier c or other carriers different from carrier c (cross-carrier scheduling).
  • scheduling based on multi-PDSCH may be replaced with “scheduling based on multi-PDSCH”; “scheduling based on single-PDSCH” may be replaced with “scheduling based on single-PDSCH”.
  • a DCI scheduling a multi-PDSCH carrier may not always schedule more than one PDSCH. The DCI can dynamically switch to schedule one PDSCH or schedule multiple PDSCHs.
  • feedback information for scheduling based on multi-PDSCH (ie, feedback information for multiple PDSCHs) is sent from the terminal device to the network device at the same time.
  • the first DCI is used for scheduling based on multi-PDSCH
  • the second DCI is used for scheduling based on single-PDSCH
  • the DCI formats of the first DCI and the second DCI are different.
  • DCI formats may be used to schedule multi-PDSCH carriers, one DCI format (a newly defined DCI format to support multi-PDSCH) may indicate multi-PDSCH-based scheduling, 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 is beneficial for system robustness and compatibility, for example, fallback DCI (DCI format 1_0) can be used for scheduling when channel conditions are poor.
  • DCI format 1_0 can be used for scheduling when channel conditions are poor.
  • the fields in the DCI indicate multi-PDSCH based scheduling or single-PDSCH based scheduling.
  • the DCI indicates multi-PDSCH-based scheduling. Even if the newly defined DCI format to support multi-PDSCH is used, a single PDSCH resource can be indicated in one row of the time domain resource allocation table configured by RRC, and multiple PDSCH resources can be indicated in another row, and then different fields can be dynamically indicated through DCI. , you can flexibly switch between scheduling based on multi-PDSCH and scheduling based on single-PDSCH.
  • DCI includes multiple New Data Indicator (NDI, New Data Indicator) and/or Redundancy Version (RV, Redundancy Version) fields for indicating the NDI and RV of multiple PDSCHs, then the DCI indication is based on multi-PDSCH scheduling.
  • NDI New Data Indicator
  • RV Redundancy Version
  • the terminal device identifies scheduling based on single-PDSCH and scheduling based on multi-PDSCH is not limited.
  • the terminal equipment can be identified according to the DCI format.
  • the terminal device can know that these DCI scheduling is based on single-PDSCH transmission.
  • the terminal device can know that the DCI schedules transmission based on multi-PDSCH.
  • the terminal device may judge according to the DCI field and distinguish between scheduling based on single-PDSCH and scheduling based on multi-PDSCH according to the specific signaling content of the DCI.
  • the terminal device may also be identified based on a combination of the above two manners.
  • FIG. 3 is an example diagram of a carrier aggregation scenario according to an embodiment of the present application.
  • a carrier element (CC, Component Carrier) of carrier aggregation includes:
  • 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.
  • N TB_max,c represents the maximum number of TBs that carrier c can support
  • 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 .
  • N TB_max,c represents the maximum number of TBs that each PDSCH of carrier c can support
  • N multi_PDSCH_max,c represents the maximum number of PDSCHs that can be scheduled by one DCI that carrier c can support.
  • N TB_max,c is also referred to as the maximum number of TBs that carrier c can support.
  • N TB_max,c represents the maximum number of TBs that each PDSCH of carrier c can support
  • N CBG_max_TB,c represents the maximum number of CBGs that each TB of carrier c can support
  • N multi_PDSCH_max,c represents the carrier c
  • N TB_max,c is also referred to as the maximum number of TBs that carrier c can support.
  • the carrier aggregation of Figure 3 includes all types of carriers. When a certain type of carrier does not exist, carrier aggregation becomes a special case of FIG. 3 .
  • PDSCH can only be scheduled based on TB.
  • the PDSCH can be scheduled based on CBG or TB.
  • “Scheduling based on TB” can be replaced with “Scheduling in TB mode”; “Scheduling based on CBG” can be replaced with "Scheduling in CBG mode”.
  • transmitting or receiving PDCCH can be understood as sending or receiving downlink control information carried by PDCCH; sending or receiving PDSCH can be understood as sending or receiving downlink data carried by PDSCH.
  • An embodiment of the present application provides a method for sending feedback information, which is described from a terminal device.
  • FIG. 4 is a schematic diagram of a method for sending feedback information according to an embodiment of the present application. As shown in FIG. 4 , the method includes:
  • the terminal device receives downlink control information (DCI) sent by the network device,
  • DCI downlink control information
  • the terminal device receives, according to the downlink control information, a physical downlink shared channel (PDSCH) sent by the network device; and
  • PDSCH physical downlink shared channel
  • the terminal device feeds back the feedback information for the physical downlink shared channel to the network device;
  • the feedback information for PDSCH on the multi-PDSCH carrier is included in at least two sub-codebooks, and one of the sub-codebooks includes feedback information for PDSCH as follows: the PDSCH is based on single-PDSCH on the multi-PDSCH carrier and Transport Blocks (TBs) are scheduled.
  • TBs Transport Blocks
  • FIG. 4 only schematically illustrates the embodiment of the present application, but the present application is not limited thereto.
  • the execution order of the various operations can be adjusted appropriately, and other operations can be added or some of the operations can be reduced.
  • Those skilled in the art can make appropriate modifications according to the above content, and are not limited to the description of the above-mentioned FIG. 3 .
  • the HARQ-ACK codebook includes a first sub-codebook, a second sub-codebook, and a third sub-codebook.
  • the first subcodebook includes feedback information for PDSCH: the physical downlink shared channel is scheduled on a single physical downlink shared channel carrier based on transport blocks, and/or the physical downlink shared channel Scheduling is based on a single physical downlink shared channel and transport block on multiple physical downlink shared channel carriers.
  • the first sub-codebook includes HARQ-ACK for the following PDSCH:
  • FIG. 5 is an example diagram of the first sub-codebook according to the embodiment of the present application, and shows the situation of the carrier set divided corresponding to FIG. 3 .
  • the first sub-codebook includes HARQ-ACK for the following PDSCH:
  • the sub-codebook naturally does not include the HARQ-ACK related to the carrier.
  • C0 and C1 may not be included in the carrier of carrier aggregation, and at this time, the first subcodebook does not include HARQ-ACK related to C0 and C1.
  • C3 may not be included in the carrier of carrier aggregation, and in this case, the first subcodebook does not include HARQ-ACK related to C3. Similar situations are not listed here.
  • the first sub-codebook includes feedback information for at least one of the following on a single physical downlink shared channel carrier and/or multiple physical downlink shared channel carriers: semi-persistent scheduling physical downlink shared channel release (SPS PDSCH release ), semi-persistent scheduling physical downlink shared channel (SPS PDSCH reception), downlink control information indicating secondary cell dormancy (DCI indicating SCell dormancy).
  • SPS PDSCH release semi-persistent scheduling physical downlink shared channel release
  • SPS PDSCH reception semi-persistent scheduling physical downlink shared channel (SPS PDSCH reception)
  • DCI downlink control information indicating secondary cell dormancy
  • the first sub-codebook may also include HARQ-ACK for the following information:
  • SPS PDSCH release Semi-persistent scheduling physical downlink shared channel release
  • SPS PDSCH Physical Downlink Shared Channel
  • DCI indicating SCell dormancy DCI indicating SCell dormancy
  • the DCI may indicate the SPS PDSCH release for which the HARQ-ACK is included in the first subcodebook.
  • the SPS PDSCH may not have a DCI schedule associated with it, and the HARQ-ACK for the SPS PDSCH is included in the first subcodebook.
  • DCI may indicate secondary cell dormancy, for example, DCI format 1_1 indicates secondary cell dormancy, and the HARQ-ACK for this DCI is included in the first subcodebook. If certain information related to the above-mentioned determination of the sub-codebook does not exist, the sub-codebook naturally does not include the HARQ-ACK related to the information.
  • N c N TB_max,c .
  • N max bits Reserving according to the maximum possible number of HARQ-ACK bits can avoid the ambiguity of the size of the HARQ-ACK codebook between the terminal device and the network device when DCI is missed.
  • the second sub-codebook includes feedback information for a physical downlink shared channel that is scheduled on a single physical downlink shared channel carrier based on a code block group (CBG), and/or , the physical downlink shared channel is scheduled based on a single physical downlink shared channel and a code block group (CBG) on multiple physical downlink shared channel carriers.
  • CBG code block group
  • the second sub-codebook includes HARQ-ACK for the following PDSCH:
  • FIG. 6 is an example diagram of a second sub-codebook according to an embodiment of the present application, and shows a situation of a carrier set divided corresponding to FIG. 3 .
  • the second sub-codebook includes HARQ-ACK for the following PDSCH:
  • the sub-codebook naturally does not include the HARQ-ACK related to 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 subcodebook does not include the HARQ-ACK related to the PDSCH.
  • N c N TB_max,c ⁇ N CBG_max_TB,c .
  • the third subcodebook includes feedback information for a physical downlink shared channel: the physical downlink shared channel is scheduled on the multi-physical downlink shared channel carrier based on the multi-physical downlink shared channel.
  • the third sub-codebook includes HARQ-ACK for the following PDSCH:
  • FIG. 7 is an example diagram of a third sub-codebook according to an embodiment of the present application, and shows a situation of a carrier set divided corresponding to FIG. 3 .
  • the third sub-codebook includes HARQ-ACK for the following PDSCH:
  • the subcodebook does not include HARQ-ACK for this PDSCH. For example, if the carriers in set C3 do not support multi-PDSCH and TB based scheduling, the subcodebook does not include HARQ-ACK for that scheduling.
  • N c N TB_max,c ⁇ N multi_PDSCH_max,c ;
  • 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 transport blocks (TB) that carrier c can support
  • N CBG_max_TB,c is the maximum number of code block groups (CBGs) that each transport block (TB) on carrier c can support
  • N multi_PDSCH_max, c is the maximum number of physical downlink shared channels on carrier c that can be scheduled by downlink control information (DCI).
  • DCI downlink control information
  • N c N TB_max,c ⁇ N multi_PDSCH_max,c .
  • N c N TB_max,c ⁇ N CBG_max_TB,c ⁇ N multi_PDSCH_max,c .
  • counter DAI and total DAI are independently counted within each sub-codebook.
  • the HARQ-ACK codebook sent by the terminal device to the network device is obtained by concatenating the foregoing sub-codebooks.
  • This embodiment of the present application does not limit the cascading order of the sub-codebooks, for example, the cascading is performed in the order of the first, second, and third sub-codebooks. Therefore, 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.
  • multiple sub-codebooks are generated based on information such as whether to use multi-PDSCH scheduling and/or whether to use CBG transmission; PDSCH feedback, and by dividing the sub-codebook, the size of the Type 2 HARQ-ACK codebook can be reduced, and the feedback overhead of HARQ-ACK can be reduced.
  • the HARQ-ACK codebook may include a first sub-codebook and a second sub-codebook.
  • the first subcodebook includes feedback information for PDSCH: the physical downlink shared channel is scheduled on a single physical downlink shared channel carrier based on transport blocks, and/or the physical downlink shared channel Scheduling is based on a single physical downlink shared channel and transport block on multiple physical downlink shared channel carriers.
  • the first sub-codebook includes HARQ-ACK for the following PDSCH:
  • the second sub-codebook includes feedback information for a physical downlink shared channel that is scheduled on a single physical downlink shared channel carrier based on a code block group (CBG), and/or , the physical downlink shared channel is scheduled on multiple physical downlink shared channel carriers based on a single physical downlink shared channel and a code block group (CBG), and/or the physical downlink shared channel is based on multiple physical downlink shared channel carriers. Multiple physical downlink shared channels are scheduled.
  • CBG code block group
  • the second sub-codebook includes HARQ-ACK for the following PDSCH:
  • FIG. 8 is an example diagram of a second sub-codebook according to an embodiment of the present application, and shows a situation of a carrier set divided corresponding to FIG. 3 .
  • the second sub-codebook includes HARQ-ACK for the following PDSCH:
  • N c N TB_max,c ⁇ N CBG_max_TB,c ;
  • 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 transport blocks (TB) that carrier c can support
  • N CBG_max_TB,c is the maximum number of code block groups (CBGs) that each transport block (TB) on carrier c can support
  • N multi_PDSCH_max, c is the maximum number of physical downlink shared channels on carrier c that can be scheduled by downlink control information (DCI).
  • DCI downlink control information
  • N c N TB_max,c ⁇ N CBG_max_TB,c .
  • N c N TB_max,c ⁇ N multi_PDSCH_max,c .
  • N c N TB_max,c ⁇ N CBG_max_TB,c ⁇ N multi_PDSCH_max,c .
  • counter DAI and total DAI are independently counted within each sub-codebook.
  • the HARQ-ACK codebook sent by the terminal device to the network device is obtained by concatenating the foregoing sub-codebooks.
  • This embodiment of the present application does not limit the cascading order of the sub-codebooks, for example, the cascading is performed according to the order of the first and second sub-codebooks. Therefore, 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.
  • multiple sub-codebooks are generated based on information such as whether to use multi-PDSCH scheduling and/or whether to use CBG transmission; PDSCH feedback, and by dividing the sub-codebook, the size of the Type 2 HARQ-ACK codebook can be reduced, and the feedback overhead of HARQ-ACK can be reduced.
  • the HARQ-ACK codebook may include a first sub-codebook, a second sub-codebook, and a third sub-codebook.
  • the first subcodebook includes feedback information for PDSCH: the physical downlink shared channel is scheduled on a single physical downlink shared channel carrier based on transport blocks, and/or the physical downlink shared channel Scheduling is based on a single physical downlink shared channel and transport block on multiple physical downlink shared channel carriers.
  • the first sub-codebook includes HARQ-ACK for the following PDSCH:
  • the second sub-codebook includes feedback information for the physical downlink shared channel: the physical downlink shared channel is scheduled on a single physical downlink shared channel carrier based on a code block group (CBG).
  • CBG code block group
  • the second sub-codebook includes HARQ-ACK for the following PDSCH:
  • FIG. 9 is an example diagram of a second sub-codebook according to an embodiment of the present application, and shows a situation of a carrier set divided corresponding to FIG. 3 .
  • the second sub-codebook includes HARQ-ACK for the following PDSCH:
  • N c N TB_max,c ⁇ N CBG_max_TB,c .
  • the third sub-codebook includes feedback information for a physical downlink shared channel: the physical downlink shared channel is based on a single physical downlink shared channel and a code block group (CBG) on multiple physical downlink shared channel carriers is scheduled, and/or the physical downlink shared channel is scheduled on the multi-physical downlink shared channel carrier based on the multi-physical downlink shared channel.
  • CBG code block group
  • the third sub-codebook includes HARQ-ACK for the following PDSCH:
  • FIG. 10 is an example diagram of a third sub-codebook according to an embodiment of the present application, and shows a situation of a carrier set divided corresponding to FIG. 3 .
  • the third sub-codebook includes HARQ-ACK for the following PDSCH:
  • N c N TB_max,c ⁇ N multi_PDSCH_max,c ;
  • 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 transport blocks (TB) that carrier c can support
  • N CBG_max_TB,c is the maximum number of code block groups (CBGs) that each transport block (TB) on carrier c can support
  • N multi_PDSCH_max, c is the maximum number of physical downlink shared channels on carrier c that can be scheduled by downlink control information (DCI).
  • DCI downlink control information
  • N c N TB_max,c ⁇ N multi_PDSCH_max,c .
  • N c N TB_max,c ⁇ N CBG_max_TB,c ⁇ N multi_PDSCH_max,c .
  • counter DAI and total DAI are independently counted within each sub-codebook.
  • the HARQ-ACK codebook sent by the terminal device to the network device is obtained by concatenating the foregoing sub-codebooks.
  • This embodiment of the present application does not limit the cascading order of the sub-codebooks, for example, the cascading is performed in the order of the first, second sub-codebook, and third codebook. Therefore, 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.
  • multiple sub-codebooks are generated based on information such as whether to use multi-PDSCH scheduling and/or whether to use CBG transmission; PDSCH feedback, and by dividing the sub-codebook, the size of the Type 2 HARQ-ACK codebook can be reduced, and the feedback overhead of HARQ-ACK can be reduced.
  • the feedback information for the first physical downlink shared channel and the feedback information for the second physical downlink shared channel are in different subcodebooks, and the first physical downlink shared channel is in multiple physical downlink shared channels (The second physical downlink shared channel is scheduled on a single physical downlink shared channel (single-PDSCH) carrier.
  • the HARQ-ACK codebook may include a first sub-codebook, a second sub-codebook, and a third sub-codebook.
  • the first subcodebook 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.
  • TB transport block
  • the first sub-codebook includes HARQ-ACK for the following PDSCH:
  • FIG. 11 is an example diagram of the first sub-codebook according to the embodiment of the present application, and shows the situation of the carrier set divided corresponding to FIG. 3 .
  • the first sub-codebook includes HARQ-ACK for the following PDSCH:
  • N c N TB_max,c .
  • the second sub-codebook includes feedback information for a physical downlink shared channel that is scheduled on a single physical downlink shared channel carrier based on a code block group (CBG).
  • CBG code block group
  • the second sub-codebook includes HARQ-ACK for the following PDSCH:
  • FIG. 12 is an example diagram of the second sub-codebook according to the embodiment of the present application, and shows the situation of the carrier set divided corresponding to FIG. 3 .
  • the second sub-codebook includes HARQ-ACK for the following PDSCH:
  • N c N TB_max,c ⁇ N CBG_max_TB,c .
  • the third subcodebook includes feedback information for a physical downlink shared channel: the physical downlink shared channel is scheduled on multiple physical downlink shared channel carriers.
  • the third sub-codebook includes HARQ-ACK for the following PDSCH:
  • FIG. 13 is an example diagram of the third sub-codebook according to the embodiment of the present application, and shows the situation of the carrier set divided corresponding to FIG. 3 .
  • the third sub-codebook includes HARQ-ACK for the following PDSCH:
  • N c N TB_max,c ⁇ N multi_PDSCH_max,c .
  • N c N TB_max,c ⁇ N CBG_max_TB,c ⁇ N multi_PDSCH_max,c .
  • counter DAI and total DAI are independently counted within each sub-codebook.
  • the HARQ-ACK codebook sent by the terminal device to the network device is obtained by concatenating the foregoing sub-codebooks.
  • This embodiment of the present application does not limit the cascading order of the sub-codebooks, for example, the cascading is performed in the order of the first, second sub-codebook, and third codebook. Therefore, 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.
  • multiple sub-codebooks are generated based on information such as whether to use multi-PDSCH scheduling and/or whether to use CBG transmission; PDSCH feedback, and by dividing the sub-codebook, the size of the Type 2 HARQ-ACK codebook can be reduced, and the feedback overhead of HARQ-ACK can be reduced.
  • the feedback information for the third physical downlink shared channel and the feedback information for the fourth physical downlink shared channel are in different subcodebooks, and the third physical downlink shared channel is in multiple physical downlink shared channels (The second physical downlink shared channel is scheduled based on a code block group (CBG) on a multi-PDSCH carrier.
  • CBG code block group
  • the HARQ-ACK codebook may include a first sub-codebook and a second sub-codebook.
  • the first subcodebook includes feedback information for a physical downlink shared channel: the physical downlink shared channel is scheduled on a single physical downlink shared channel carrier based on transport blocks (TB) and/or, so The physical downlink shared channel is scheduled on a transport block (TB) basis on multiple physical downlink shared channel carriers.
  • TB transport blocks
  • the first sub-codebook includes HARQ-ACK for the following PDSCH:
  • FIG. 14 is an example diagram of the first sub-codebook according to the embodiment of the present application, and shows the situation of the carrier set divided corresponding to FIG. 3 .
  • the first sub-codebook includes HARQ-ACK for the following PDSCH:
  • the second sub-codebook includes feedback information for a physical downlink shared channel that is scheduled on a single physical downlink shared channel carrier based on a code block group (CBG), and/or , the physical downlink shared channel is scheduled based on a code block group (CBG) on multiple physical downlink shared channel carriers.
  • CBG code block group
  • the second sub-codebook includes HARQ-ACK for the following PDSCH:
  • FIG. 15 is an example diagram of the second sub-codebook according to the embodiment of the present application, and shows the situation of the carrier set divided corresponding to FIG. 3 .
  • the second sub-codebook includes HARQ-ACK for the following PDSCH:
  • N c N TB_max,c ⁇ N CBG_max_TB,c .
  • N c N TB_max,c ⁇ N CBG_max_TB,c ⁇ N multi_PDSCH_max,c .
  • counter DAI and total DAI are independently counted within each sub-codebook.
  • the HARQ-ACK codebook sent by the terminal device to the network device is obtained by concatenating the foregoing sub-codebooks.
  • This embodiment of the present application does not limit the cascading order of the sub-codebooks, for example, the cascading is performed according to the order of the first and second sub-codebooks. Therefore, 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.
  • multiple sub-codebooks are generated based on information such as whether to use multi-PDSCH scheduling and/or whether to use CBG transmission; PDSCH feedback, and by dividing the sub-codebook, the size of the Type 2 HARQ-ACK codebook can be reduced, and the feedback overhead of HARQ-ACK can be reduced.
  • An embodiment of the present application provides a method for receiving feedback information, which is described from a network device, and the same content as the embodiments of the first to fifth aspects will not be repeated.
  • FIG. 16 is a schematic diagram of a method for receiving feedback information according to an embodiment of the present application. As shown in FIG. 16 , the method includes:
  • the network device sends downlink control information (DCI) to the terminal device;
  • DCI downlink control information
  • FIG. 16 only schematically illustrates the embodiment of the present application, but the present application is not limited thereto.
  • the execution order of the various operations can be adjusted appropriately, and other operations can be added or some of the operations can be reduced.
  • Those skilled in the art can make appropriate modifications according to the above content, and are not limited to the description of the above-mentioned FIG. 16 .
  • the feedback information for the physical downlink shared channel on the multiple physical downlink shared channel carriers is included in at least two sub-codebooks, wherein one sub-codebook includes the feedback information for the following physical downlink shared channels: all The physical downlink shared channel is scheduled based on a single physical downlink shared channel and transport blocks on multiple physical downlink shared channel carriers.
  • the at least two sub-codebooks include:
  • the first sub-codebook includes feedback information for the following physical downlink shared channel: the physical downlink shared channel is scheduled on a single physical downlink shared channel carrier based on transport blocks, and/or, so The physical downlink shared channel is scheduled based on a single physical downlink shared channel and a transport block on multiple physical downlink shared channel carriers;
  • the second sub-codebook includes feedback information for a physical downlink shared channel that is scheduled on a single physical downlink shared channel carrier based on code block groups (CBGs), and or, the physical downlink shared channel is scheduled based on a single physical downlink shared channel and a code block group (CBG) on multiple physical downlink shared channel carriers;
  • CBGs code block groups
  • CBGs code block groups
  • a third sub-codebook; the third sub-codebook includes feedback information for the following physical downlink shared channel: the physical downlink shared channel is scheduled on the multi-physical downlink shared channel carrier based on the multi-physical downlink shared channel.
  • the at least two sub-codebooks include:
  • the first sub-codebook includes feedback information for the following physical downlink shared channel: the physical downlink shared channel is scheduled on a single physical downlink shared channel carrier based on transport blocks, and/or, so The physical downlink shared channel is scheduled based on a single physical downlink shared channel and a transport block on multiple physical downlink shared channel carriers;
  • the second sub-codebook includes feedback information for a physical downlink shared channel that is scheduled on a single physical downlink shared channel carrier based on code block groups (CBGs), and /or, the physical downlink shared channel is scheduled on multiple physical downlink shared channel carriers based on a single physical downlink shared channel and a code block group (CBG), and/or the physical downlink shared channel is scheduled on multiple physical downlink shared channel carriers is scheduled based on multiple physical downlink shared channels.
  • CBGs code block groups
  • CBGs code block groups
  • the at least two sub-codebooks include:
  • the first sub-codebook includes feedback information for the following physical downlink shared channel: the physical downlink shared channel is scheduled on a single physical downlink shared channel carrier based on transport blocks, and/or, so The physical downlink shared channel is scheduled based on a single physical downlink shared channel and a transport block on multiple physical downlink shared channel carriers;
  • the second sub-codebook includes feedback information for the following physical downlink shared channel: the physical downlink shared channel is scheduled based on a code block group (CBG) on a single physical downlink shared channel carrier;
  • CBG code block group
  • the third sub-codebook includes feedback information for the following physical downlink shared channel: the physical downlink shared channel is based on a single physical downlink shared channel and a code block group ( CBG) is scheduled, and/or the physical downlink shared channel is scheduled on the multi-physical downlink shared channel carrier based on the multi-physical downlink shared channel.
  • CBG code block group
  • the feedback information for the first physical downlink shared channel and the feedback information for the second physical downlink shared channel are in different subcodebooks, and the first physical downlink shared channel is in multiple physical downlink shared channels (The second physical downlink shared channel is scheduled on a single physical downlink shared channel (single-PDSCH) carrier.
  • the sub-codebook includes:
  • the first sub-codebook includes feedback information for the following physical downlink shared channel: the physical downlink shared channel is scheduled on a single physical downlink shared channel carrier based on a transport block (TB);
  • TB transport block
  • the second sub-codebook includes feedback information for the following physical downlink shared channel: the physical downlink shared channel is scheduled based on a code block group (CBG) on a single physical downlink shared channel carrier;
  • CBG code block group
  • a third sub-codebook; the third sub-codebook includes feedback information for the following physical downlink shared channel: the physical downlink shared channel is scheduled on multiple physical downlink shared channel carriers.
  • the feedback information for the third physical downlink shared channel and the feedback information for the fourth physical downlink shared channel are in different subcodebooks, and the third physical downlink shared channel is in multiple physical downlink shared channels (The second physical downlink shared channel is scheduled based on a code block group (CBG) on a multi-PDSCH carrier.
  • CBG code block group
  • the sub-codebook includes:
  • the first sub-codebook includes feedback information for a physical downlink shared channel: the physical downlink shared channel is scheduled on a single physical downlink shared channel carrier based on a transport block (TB) and/or , the physical downlink shared channel is scheduled based on transport blocks (TBs) on multiple physical downlink shared channel carriers;
  • TB transport block
  • TBs transport blocks
  • the second sub-codebook includes feedback information for a physical downlink shared channel that is scheduled on a single physical downlink shared channel carrier based on code block groups (CBGs), and or, the physical downlink shared channel is scheduled based on a code block group (CBG) on multiple physical downlink shared channel carriers.
  • CBGs code block groups
  • CBG code block group
  • multiple sub-codebooks are generated based on information such as whether to use multi-PDSCH scheduling and/or whether to use CBG transmission; PDSCH feedback, and by dividing the sub-codebook, the size of the Type 2 HARQ-ACK codebook can be reduced, and the feedback overhead of HARQ-ACK can be reduced.
  • An embodiment of the present application provides an apparatus for sending feedback information.
  • the apparatus may be, for example, a terminal device, or may be one or some components or components configured in the terminal device, and the same content as the embodiments of the first to fifth aspects will not be repeated.
  • FIG. 17 is a schematic diagram of an apparatus for sending feedback information according to an embodiment of the present application.
  • the apparatus 1700 for sending feedback information includes:
  • a receiving unit 1701 which receives downlink control information sent by a network device, and receives a physical downlink shared channel sent by the network device according to the downlink control information;
  • a sending unit 1702 which feeds back the feedback information for the physical downlink shared channel to the network device.
  • the feedback information for the physical downlink shared channel on the multiple physical downlink shared channel carriers is included in at least two sub-codebooks, wherein one sub-codebook includes the feedback information for the physical downlink shared channel as follows: The physical downlink shared channel is scheduled based on a single physical downlink shared channel and transport blocks on multiple physical downlink shared channel carriers.
  • the first downlink control information is used for scheduling based on multiple physical downlink shared channels
  • the second downlink control information is used for scheduling based on a single physical downlink shared channel; the first downlink control information and The downlink control information formats of the second downlink control information are different.
  • the at least two sub-codebooks include: a first sub-codebook; the first sub-codebook includes feedback information for the following physical downlink shared channel: the physical downlink shared channel is in a single physical downlink The shared channel carrier is scheduled based on transport blocks, and/or the physical downlink shared channel is scheduled based on a single physical downlink shared channel and transport blocks on multiple physical downlink shared channel carriers.
  • the first subcodebook includes feedback information for at least one of the following on a single physical downlink shared channel carrier and/or multiple physical downlink shared channel carriers: semi-persistent scheduling physical downlink shared channel release, semi-persistent scheduling physical downlink shared channel release, semi-persistent Continuous scheduling of the physical downlink shared channel and downlink control information indicating the sleep of the secondary cell.
  • the carrier of the feedback information, N TB_max,c is the maximum number of transport blocks that the carrier c can support.
  • the at least two sub-codebooks further include: a second sub-codebook; the second sub-codebook includes feedback information for the following physical downlink shared channel: the physical downlink shared channel is in a single physical The downlink shared channel carrier is scheduled based on code block groups, and/or the physical downlink shared channel is scheduled based on a single physical downlink shared channel and code block group on multiple physical downlink shared channel carriers.
  • the at least two sub-codebooks further include: a third sub-codebook; the third sub-codebook includes feedback information for the following physical downlink shared channel: the physical downlink shared channel is in multi-physical The downlink shared channel carrier is scheduled based on multiple physical downlink shared channels.
  • N c N TB_max,c ⁇ N multi_PDSCH_max,c ;
  • 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 transport blocks that carrier c can support
  • N CBG_max_TB,c is the maximum number of code block groups that each transport block on carrier c can support
  • N multi_PDSCH_max,c is the carrier that can be scheduled by downlink control information Maximum number of physical downlink shared channels on c.
  • the at least two sub-codebooks further include: a second sub-codebook; the second sub-codebook includes feedback information for the following physical downlink shared channel: the physical downlink shared channel is in a single physical The downlink shared channel carrier is scheduled based on code block groups, and/or the physical downlink shared channel is scheduled based on a single physical downlink shared channel and a code block group on multiple physical downlink shared channel carriers, and/or the physical downlink shared channel is scheduled based on the code block group. The downlink shared channel is scheduled on the multi-physical downlink shared channel carrier based on the multi-physical downlink shared channel.
  • N c N TB_max,c ⁇ N CBG_max_TB,c ;
  • 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 transport blocks that carrier c can support
  • N CBG_max_TB,c is the maximum number of code block groups that each transport block on carrier c can support
  • N multi_PDSCH_max,c is the carrier that can be scheduled by downlink control information Maximum number of physical downlink shared channels on c.
  • the at least two sub-codebooks further include: a second sub-codebook; the second sub-codebook includes feedback information for the following physical downlink shared channel: the physical downlink shared channel is in a single physical The downlink shared channel carrier is scheduled based on code block groups.
  • the at least two sub-codebooks further include: a third sub-codebook; the third sub-codebook includes feedback information for the following physical downlink shared channel: the physical downlink shared channel is in multi-physical The downlink shared channel carrier is scheduled based on a single physical downlink shared channel and a code block group, and/or the physical downlink shared channel is scheduled on a multiple physical downlink shared channel carrier based on multiple physical downlink shared channels.
  • N c N TB_max,c ⁇ N multi_PDSCH_max,c ;
  • 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 transport blocks that carrier c can support
  • N CBG_max_TB,c is the maximum number of code block groups that each transport block on carrier c can support
  • N multi_PDSCH_max,c is the carrier that can be scheduled by downlink control information Maximum number of physical downlink shared channels on c.
  • the feedback information for the first physical downlink shared channel and the feedback information for the second physical downlink shared channel are in different subcodebooks, and the first physical downlink shared channel is in multiple physical downlink shared channel carriers The second physical downlink shared channel is scheduled on the single physical downlink shared channel carrier.
  • the sub-codebook includes:
  • the first sub-codebook includes feedback information for the following physical downlink shared channel: the physical downlink shared channel is scheduled on a single physical downlink shared channel carrier based on transport blocks;
  • the second sub-codebook includes feedback information for the following physical downlink shared channel: the physical downlink shared channel is scheduled on a single physical downlink shared channel carrier based on code block groups;
  • a third sub-codebook; the third sub-codebook includes feedback information for the following physical downlink shared channel: the physical downlink shared channel is scheduled on multiple physical downlink shared channel carriers.
  • the feedback information for the third physical downlink shared channel and the feedback information for the fourth physical downlink shared channel are in different subcodebooks, and the third physical downlink shared channel is in multiple physical downlink shared channel carriers The second physical downlink shared channel is scheduled based on the code block group on the multiple physical downlink shared channel carrier.
  • the sub-codebook includes:
  • the first sub-codebook includes feedback information for the following physical downlink shared channel: the physical downlink shared channel is scheduled on a single physical downlink shared channel carrier based on transport blocks and/or, the The physical downlink shared channel is scheduled based on transport blocks on multiple physical downlink shared channel carriers;
  • the second sub-codebook; the second sub-codebook includes feedback information for the physical downlink shared channel: the physical downlink shared channel is scheduled on a single physical downlink shared channel carrier based on code block groups, and/or, The physical downlink shared channel is scheduled based on code block groups on multiple physical downlink shared channel carriers.
  • the apparatus 1700 for sending feedback information may further include other components or modules.
  • the apparatus 1700 for sending feedback information may further include other components or modules.
  • FIG. 17 only exemplarily shows the connection relationship or signal direction between various components or modules, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used.
  • the above-mentioned components or modules may be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc. The implementation of this application does not limit this.
  • multiple sub-codebooks are generated based on information such as whether to use multi-PDSCH scheduling and/or whether to use CBG transmission; PDSCH feedback, and by dividing the sub-codebook, the size of the Type 2 HARQ-ACK codebook can be reduced, and the feedback overhead of HARQ-ACK can be reduced.
  • An embodiment of the present application provides an apparatus for receiving feedback information.
  • the apparatus may be, for example, a network device, or may be some or some components or components configured in the network device, and the same content as the embodiment of the sixth aspect will not be repeated.
  • FIG. 18 is a schematic diagram of an apparatus for receiving feedback information according to an embodiment of the present application.
  • the apparatus 1800 for receiving feedback information includes:
  • a sending unit 1801 which sends downlink control information to a terminal device; sends a physical downlink shared channel to the terminal device;
  • a receiving unit 1802 which receives the feedback information of the terminal equipment for the physical downlink shared channel.
  • the feedback information for the physical downlink shared channel on the multiple physical downlink shared channel carriers is included in at least two sub-codebooks, wherein one sub-codebook includes the feedback information for the physical downlink shared channel as follows: The physical downlink shared channel is scheduled based on a single physical downlink shared channel and transport blocks on multiple physical downlink shared channel carriers.
  • the feedback information for the first physical downlink shared channel and the feedback information for the second physical downlink shared channel are in different subcodebooks, and the first physical downlink shared channel is in multiple physical downlink shared channel carriers The second physical downlink shared channel is scheduled on the single physical downlink shared channel carrier.
  • the feedback information for the third physical downlink shared channel and the feedback information for the fourth physical downlink shared channel are in different subcodebooks, and the third physical downlink shared channel is in multiple physical downlink shared channel carriers The second physical downlink shared channel is scheduled based on the code block group on the multiple physical downlink shared channel carrier.
  • the apparatus 1800 for receiving feedback information may further include other components or modules.
  • the apparatus 1800 for receiving feedback information may further include other components or modules.
  • FIG. 18 only exemplarily shows the connection relationship or signal direction between various components or modules, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used.
  • the above-mentioned components or modules may be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc. The implementation of this application does not limit this.
  • multiple sub-codebooks are generated based on information such as whether to use multi-PDSCH scheduling and/or whether to use CBG transmission; PDSCH feedback, and by dividing the sub-codebook, the size of the Type 2 HARQ-ACK codebook can be reduced, and the feedback overhead of HARQ-ACK can be reduced.
  • An embodiment of the present application further provides a communication system, and reference may be made to FIG. 1 , and the same content as the embodiments of the first aspect to the eighth aspect will not be repeated.
  • the communication system 100 may include at least:
  • the network device 101 sends downlink control information to a terminal device; sends a physical downlink shared channel to the terminal device; and receives feedback information from the terminal device on the physical downlink shared channel;
  • the terminal device 102 which receives the downlink control information sent by the network device, and receives the physical downlink shared channel sent by the network device according to the downlink control information; and feeds back the physical downlink shared channel to the network device channel feedback information;
  • the feedback information for the physical downlink shared channel on the multiple physical downlink shared channel carriers is included in at least two sub-codebooks, and one of the sub-codebooks includes feedback information for the following physical downlink shared channels: the physical downlink shared channel Channels are scheduled based on a single physical downlink shared channel and transport blocks on multiple physical downlink shared channel carriers.
  • the communication system 100 may include at least:
  • the network device 101 sends downlink control information to a terminal device; sends a physical downlink shared channel to the terminal device; and receives feedback information from the terminal device on the physical downlink shared channel;
  • the terminal device 102 which receives the downlink control information sent by the network device, and receives the physical downlink shared channel sent by the network device according to the downlink control information; and feeds back the physical downlink shared channel to the network device channel feedback information;
  • the feedback information for the first physical downlink shared channel and the feedback information for the second physical downlink shared channel are in different subcodebooks, and the first physical downlink shared channel is scheduled on multiple physical downlink shared channel carriers, The second physical downlink shared channel is scheduled on a single physical downlink shared channel carrier.
  • the communication system 100 may include at least:
  • the network device 101 sends downlink control information to a terminal device; sends a physical downlink shared channel to the terminal device; and receives feedback information from the terminal device on the physical downlink shared channel;
  • the terminal device 102 which receives the downlink control information sent by the network device, and receives the physical downlink shared channel sent by the network device according to the downlink control information; and feeds back the physical downlink shared channel to the network device channel feedback information;
  • the feedback information for the third physical downlink shared channel and the feedback information for the fourth physical downlink shared channel are in different subcodebooks, and the third physical downlink shared channel is based on transport blocks on multiple physical downlink shared channel carriers. is scheduled, and the second physical downlink shared channel is scheduled on a multi-physical downlink shared channel carrier based on code block groups.
  • the embodiment of the present application also provides a network device, which may be, for example, a base station, but the present application is not limited to this, and may also be other network devices.
  • a network device which may be, for example, a base station, but the present application is not limited to this, and may also be other network devices.
  • FIG. 19 is a schematic structural diagram of a network device according to an embodiment of the present application.
  • the network device 1900 may include: a processor 1910 (eg, a central processing unit CPU) and a memory 1920 ; the memory 1920 is coupled to the processor 1910 .
  • the memory 1920 can store various data; in addition, a program 1930 for information processing is also stored, and the program 1930 is executed under the control of the processor 1910 .
  • the processor 1910 may be configured to execute a program to implement the method for receiving feedback information according to the embodiment of the sixth aspect.
  • the processor 1910 may be configured to perform the following controls: send downlink control information to a terminal device; send a physical downlink shared channel to the terminal device; and receive feedback information from the terminal device on the physical downlink shared channel;
  • the feedback information for the physical downlink shared channel on the multiple physical downlink shared channel carriers is included in at least two sub-codebooks, and one of the sub-codebooks includes feedback information for the following physical downlink shared channels: the physical downlink shared channel Channels are scheduled on multiple physical downlink shared channel carriers based on a single physical downlink shared channel and transport block;
  • the feedback information for the first physical downlink shared channel and the feedback information for the second physical downlink shared channel are in different subcodebooks, and the first physical downlink shared channel is scheduled on multiple physical downlink shared channel carriers, the second physical downlink shared channel is scheduled on a single physical downlink shared channel carrier;
  • the feedback information for the third physical downlink shared channel and the feedback information for the fourth physical downlink shared channel are in different subcodebooks, and the third physical downlink shared channel is based on transport blocks on multiple physical downlink shared channel carriers is scheduled, and the second physical downlink shared channel is scheduled on a multi-physical downlink shared channel carrier based on code block groups.
  • the network device 1900 may further include: a transceiver 1940, an antenna 1950, etc.; wherein, the functions of the above components are similar to those in the prior art, and details are not repeated here. It is worth noting that the network device 1900 does not necessarily include all the components shown in FIG. 19 ; in addition, the network device 1900 may also include components not shown in FIG. 19 , and reference may be made to the prior art.
  • the embodiment of the present application also provides a terminal device, but the present application is not limited to this, and may also be other devices.
  • FIG. 20 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • the terminal device 2000 may include a processor 2010 and a memory 2020 ; the memory 2020 stores data and programs, and is coupled to the processor 2010 .
  • this figure is exemplary; other types of structures may be used in addition to or in place of this structure to implement telecommunication functions or other functions.
  • the processor 2010 may be configured to execute a program to implement the method for sending feedback information according to the embodiments of the first to fifth aspects.
  • the processor 2010 may be configured to perform the following controls: receive downlink control information sent by a network device, and receive a physical downlink shared channel sent by the network device according to the downlink control information; the feedback information of the physical downlink shared channel;
  • the feedback information for the physical downlink shared channel on the multiple physical downlink shared channel carriers is included in at least two sub-codebooks, and one of the sub-codebooks includes feedback information for the following physical downlink shared channels: the physical downlink shared channel Channels are scheduled on multiple physical downlink shared channel carriers based on a single physical downlink shared channel and transport block;
  • the feedback information for the first physical downlink shared channel and the feedback information for the second physical downlink shared channel are in different subcodebooks, and the first physical downlink shared channel is scheduled on multiple physical downlink shared channel carriers, the second physical downlink shared channel is scheduled on a single physical downlink shared channel carrier;
  • the feedback information for the third physical downlink shared channel and the feedback information for the fourth physical downlink shared channel are in different subcodebooks, and the third physical downlink shared channel is based on transport blocks on multiple physical downlink shared channel carriers is scheduled, and the second physical downlink shared channel is scheduled on a multi-physical downlink shared channel carrier based on code block groups.
  • the terminal device 2000 may further include: a communication module 2030 , an input unit 2040 , a display 2050 , and a power supply 2060 .
  • the functions of the above components are similar to those in the prior art, and details are not repeated here. It is worth noting that the terminal device 2000 does not necessarily include all the components shown in FIG. 20 , and the above components are not required; in addition, the terminal device 2000 may also include components not shown in FIG. 20 . There is technology.
  • An embodiment of the present application further provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to execute the method for sending feedback information according to the embodiments of the first to fifth aspects.
  • An embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program enables a terminal device to execute the method for sending feedback information described in the embodiments of the first to fifth aspects.
  • the embodiment of the present application further provides a computer program, wherein when the program is executed in a network device, the program causes the network device to execute the method for receiving feedback information according to the embodiment of the sixth aspect.
  • the embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program causes the network device to execute the method for receiving feedback information according to the embodiment of the sixth aspect.
  • the apparatuses and methods above in the present application may be implemented by hardware, or may be implemented by hardware combined with software.
  • the present application relates to a computer-readable program that, when executed by logic components, enables the logic components to implement the above-described apparatus or constituent components, or causes the logic components to implement the above-described various methods or steps.
  • the present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, and the like.
  • the method/apparatus described in conjunction with the embodiments of this application may be directly embodied as hardware, a software module executed by a processor, or a combination of the two.
  • one or more of the functional block diagrams shown in the figures and/or one or more combinations of the functional block diagrams may correspond to either software modules or hardware modules of the computer program flow.
  • These software modules may respectively correspond to the various steps shown in the figure.
  • These hardware modules can be implemented by, for example, solidifying these software modules using a Field Programmable Gate Array (FPGA).
  • FPGA Field Programmable Gate Array
  • a software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.
  • a storage medium can be coupled to the processor, such that the processor can read information from, and write information to, the storage medium; or the storage medium can be an integral part of the processor.
  • the processor and storage medium may reside in an ASIC.
  • the software module can be stored in the memory of the mobile terminal, or can be stored in a memory card that can be inserted into the mobile terminal.
  • the software module can be stored in the MEGA-SIM card or a large-capacity flash memory device.
  • the functional blocks and/or one or more combinations of the functional blocks described in the figures can be implemented as a general-purpose processor, a digital signal processor (DSP) for performing the functions described in this application ), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any suitable combination thereof.
  • DSP digital signal processor
  • ASICs Application Specific Integrated Circuits
  • FPGAs Field Programmable Gate Arrays
  • One or more of the functional blocks and/or one or more combinations of the functional blocks described with respect to the figures can also be implemented as a combination of computing devices, eg, a combination of a DSP and a microprocessor, multiple microprocessors processor, one or more microprocessors in communication with the DSP, or any other such configuration.
  • a method for sending feedback information comprising:
  • the terminal device receives downlink control information (DCI) sent by the network device,
  • PDSCH physical downlink shared channel
  • the feedback information for the physical downlink shared channel on the multi-PDSCH carrier is included in at least two sub-codebooks, and one of the sub-codebooks includes the following feedback information for the physical downlink shared channel:
  • the physical downlink shared channel is scheduled based on a single physical downlink shared channel (single-PDSCH) and a transport block (TB) on multiple physical downlink shared channel carriers.
  • Supplement 2 The method according to Supplement 1, wherein the first downlink control information is used for scheduling based on a multi-physical downlink shared channel (multi-PDSCH), and the second downlink control information is used for scheduling based on a single physical downlink A shared channel (single-PDSCH) is used for scheduling; the formats of downlink control information (DCI) of the first downlink control information and the second downlink control information are different.
  • multi-PDSCH multi-physical downlink shared channel
  • single-PDSCH single physical downlink A shared channel
  • Supplement 3 The method according to Supplement 1 or 2, wherein the at least two sub-codebooks include: a first sub-codebook; and the first sub-codebook includes feedback information for the following physical downlink shared channel : the physical downlink shared channel is scheduled on a single physical downlink shared channel carrier based on transport blocks, and/or the physical downlink shared channel is scheduled on multiple physical downlink shared channel carriers based on a single physical downlink shared channel and transport blocks .
  • Supplement 4 The method according to Supplement 3, wherein the first sub-codebook includes feedback information for at least one of the following on a single physical downlink shared channel carrier and/or multiple physical downlink shared channel carriers: half Persistent scheduling physical downlink shared channel release (SPS PDSCH release), semi-persistent scheduling physical downlink shared channel (SPS PDSCH reception), downlink control information indicating secondary cell dormancy (DCI indicating SCell dormancy).
  • SPS PDSCH release half Persistent scheduling physical downlink shared channel release
  • SPS PDSCH reception semi-persistent scheduling physical downlink shared channel
  • DCI downlink control information indicating secondary cell dormancy
  • the at least two sub-codebooks further include: a second sub-codebook; the second sub-codebook includes the following physical downlink sharing Channel feedback information: the physical downlink shared channel is scheduled based on a code block group (CBG) on a single physical downlink shared channel carrier, and/or the physical downlink shared channel is based on a single physical downlink shared channel carrier on multiple physical downlink shared channels.
  • CBG code block group
  • CBGs Downlink Shared Channel and Code Block Groups
  • N max max c ⁇ N TB_max,c ⁇ N CBG_max_TB,c ⁇
  • carrier c is a carrier capable of generating feedback information in the second subcodebook
  • N TB_max,c is the maximum number of transport blocks (TB) that carrier c can support
  • N CBG_max_TB,c is each transport block on carrier c (TB)
  • CBGs code block groups
  • Supplement 8 The method according to any one of Supplements 3 to 7, wherein the at least two sub-codebooks further include: a third sub-codebook; the third sub-codebook includes the following physical downlink sharing Feedback information of the channel: the physical downlink shared channel is scheduled on the multi-physical downlink shared channel carrier based on the multi-physical downlink shared channel.
  • N c N TB_max,c ⁇ N multi_PDSCH_max,c ;
  • 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 transport blocks (TB) that carrier c can support
  • N CBG_max_TB,c is the maximum number of code block groups (CBGs) that each transport block (TB) on carrier c can support
  • N multi_PDSCH_max, c is the maximum number of physical downlink shared channels on carrier c that can be scheduled by downlink control information (DCI).
  • DCI downlink control information
  • the at least two sub-codebooks further include: a second sub-codebook; the second sub-codebook includes the following physical downlink sharing Channel feedback information: the physical downlink shared channel is scheduled based on a code block group (CBG) on a single physical downlink shared channel carrier, and/or the physical downlink shared channel is based on a single physical downlink shared channel carrier on multiple physical downlink shared channels.
  • CBG code block group
  • Downlink shared channels and code block groups (CBGs) are scheduled, and/or the physical downlink shared channels are scheduled on multiple physical downlink shared channel carriers based on multiple physical downlink shared channels.
  • N c N TB_max,c ⁇ N CBG_max_TB,c ;
  • 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 transport blocks (TB) that carrier c can support
  • N CBG_max_TB,c is the maximum number of code block groups (CBGs) that each transport block (TB) on carrier c can support
  • N multi_PDSCH_max, c is the maximum number of physical downlink shared channels on carrier c that can be scheduled by downlink control information (DCI).
  • DCI downlink control information
  • the at least two sub-codebooks further include: a second sub-codebook; the second sub-codebook includes the following physical downlink sharing Feedback information of the channel: the physical downlink shared channel is scheduled on a single physical downlink shared channel carrier based on a code block group (CBG).
  • CBG code block group
  • N max max c ⁇ N TB_max,c ⁇ N CBG_max_TB,c ⁇
  • carrier c is a carrier capable of generating feedback information in the second subcodebook
  • N TB_max,c is the maximum number of transport blocks (TB) that carrier c can support
  • N CBG_max_TB,c is each transport block on carrier c (TB)
  • CBGs code block groups
  • Supplement 14 The method according to Supplement 12 or 13, wherein the at least two sub-codebooks further include: a third sub-codebook; and the third sub-codebook includes feedback for the following physical downlink shared channel Information:
  • the physical downlink shared channel is 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 the physical downlink shared channel is on a multi-physical downlink shared channel carrier. Scheduled based on multiple physical downlink shared channels.
  • CBG code block group
  • N c N TB_max,c ⁇ N multi_PDSCH_max,c ;
  • 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 transport blocks (TB) that carrier c can support
  • N CBG_max_TB,c is the maximum number of code block groups (CBGs) that each transport block (TB) on carrier c can support
  • N multi_PDSCH_max, c is the maximum number of physical downlink shared channels on carrier c that can be scheduled by downlink control information (DCI).
  • DCI downlink control information
  • a method for sending feedback information comprising:
  • the terminal device receives downlink control information (DCI) sent by the network device,
  • PDSCH physical downlink shared channel
  • the feedback information for the first physical downlink shared channel and the feedback information for the second physical downlink shared channel are in different subcodebooks, and the first physical downlink shared channel is in a multi-physical downlink shared channel (multi-PDSCH)
  • the second physical downlink shared channel is scheduled on a single physical downlink shared channel (single-PDSCH) carrier.
  • Supplement 17 The method according to Supplement 16, wherein the sub-codebook comprises:
  • the first sub-codebook includes feedback information for the following physical downlink shared channel: the physical downlink shared channel is scheduled on a single physical downlink shared channel carrier based on a transport block (TB);
  • TB transport block
  • the second sub-codebook includes feedback information for the following physical downlink shared channel: the physical downlink shared channel is scheduled based on a code block group (CBG) on a single physical downlink shared channel carrier;
  • CBG code block group
  • a third sub-codebook; the third sub-codebook includes feedback information for the following physical downlink shared channel: the physical downlink shared channel is scheduled on multiple physical downlink shared channel carriers.
  • a method for sending feedback information comprising:
  • the terminal device receives downlink control information (DCI) sent by the network device,
  • PDSCH physical downlink shared channel
  • the feedback information for the third physical downlink shared channel and the feedback information for the fourth physical downlink shared channel are in different subcodebooks, and the third physical downlink shared channel is in a multi-physical downlink shared channel (multi-PDSCH)
  • the carrier is scheduled on a transport block (TB) basis, and the second physical downlink shared channel is scheduled on a multi-physical downlink shared channel (multi-PDSCH) carrier based on a code block group (CBG).
  • CBG code block group
  • the first sub-codebook includes feedback information for a physical downlink shared channel: the physical downlink shared channel is scheduled on a single physical downlink shared channel carrier based on a transport block (TB) and/or , the physical downlink shared channel is scheduled based on transport blocks (TBs) on multiple physical downlink shared channel carriers;
  • TB transport block
  • TBs transport blocks
  • the second sub-codebook includes feedback information for a physical downlink shared channel that is scheduled on a single physical downlink shared channel carrier based on code block groups (CBGs), and or, the physical downlink shared channel is scheduled based on a code block group (CBG) on multiple physical downlink shared channel carriers.
  • CBGs code block groups
  • CBG code block group
  • a method for receiving feedback information comprising:
  • the network device sends downlink control information (DCI) to the terminal device;
  • DCI downlink control information
  • PDSCH physical downlink shared channel
  • the feedback information for the physical downlink shared channel on the multiple physical downlink shared channel carriers is included in at least two sub-codebooks, and one of the sub-codebooks includes feedback information for the following physical downlink shared channels: the physical downlink shared channel Channels are scheduled based on a single physical downlink shared channel and transport blocks on multiple physical downlink shared channel carriers.
  • a method for receiving feedback information comprising:
  • the network device sends downlink control information (DCI) to the terminal device;
  • DCI downlink control information
  • PDSCH physical downlink shared channel
  • the feedback information for the first physical downlink shared channel and the feedback information for the second physical downlink shared channel are in different subcodebooks, and the first physical downlink shared channel is in a multi-physical downlink shared channel (multi-PDSCH)
  • the second physical downlink shared channel is scheduled on a single physical downlink shared channel (single-PDSCH) carrier.
  • a method for receiving feedback information comprising:
  • the network device sends downlink control information (DCI) to the terminal device;
  • DCI downlink control information
  • PDSCH physical downlink shared channel
  • 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 in a multi-physical downlink shared channel (multi-PDSCH)
  • the carrier is scheduled on a transport block (TB) basis, and the second physical downlink shared channel is scheduled on a multi-physical downlink shared channel (multi-PDSCH) carrier based on a code block group (CBG).
  • TB transport block
  • CBG code block group
  • a terminal device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the feedback according to any one of Supplementary Notes 1 to 19 The method of sending the information.
  • Supplement 24 A network device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the feedback according to any one of Supplements 20 to 22 The method of receiving the information.
  • a communication system comprising:
  • a network device sending downlink control information to a terminal device; sending a physical downlink shared channel to the terminal device; and receiving feedback information from the terminal device for the physical downlink shared channel;
  • a terminal device which receives the downlink control information sent by the network device, and receives the physical downlink shared channel sent by the network device according to the downlink control information; and feeds back the physical downlink shared channel to the network device feedback information;
  • the feedback information for the physical downlink shared channel on the multiple physical downlink shared channel carriers is included in at least two sub-codebooks, and one of the sub-codebooks includes feedback information for the following physical downlink shared channels: the physical downlink shared channel Channels are scheduled based on a single physical downlink shared channel and transport blocks on multiple physical downlink shared channel carriers.
  • a communication system comprising:
  • a network device sending downlink control information to a terminal device; sending a physical downlink shared channel to the terminal device; and receiving feedback information from the terminal device for the physical downlink shared channel;
  • a terminal device which receives the downlink control information sent by the network device, and receives the physical downlink shared channel sent by the network device according to the downlink control information; and feeds back the physical downlink shared channel to the network device feedback information;
  • the feedback information for the first physical downlink shared channel and the feedback information for the second physical downlink shared channel are in different subcodebooks, and the first physical downlink shared channel is scheduled on multiple physical downlink shared channel carriers, The second physical downlink shared channel is scheduled on a single physical downlink shared channel carrier.
  • a communication system comprising:
  • a network device sending downlink control information to a terminal device; sending a physical downlink shared channel to the terminal device; and receiving feedback information from the terminal device for the physical downlink shared channel;
  • a terminal device which receives the downlink control information sent by the network device, and receives the physical downlink shared channel sent by the network device according to the downlink control information; and feeds back the physical downlink shared channel to the network device feedback information;
  • the feedback information for the third physical downlink shared channel and the feedback information for the fourth physical downlink shared channel are in different subcodebooks, and the third physical downlink shared channel is based on transport blocks on multiple physical downlink shared channel carriers. is scheduled, and the second physical downlink shared channel is scheduled on a multi-physical downlink shared channel carrier based on code block groups.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Physics & Mathematics (AREA)
  • Mathematical Physics (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Detection And Prevention Of Errors In Transmission (AREA)

Abstract

本申请实施例提供一种反馈信息的发送和接收方法以及装置。所述方法包括：终端设备接收网络设备发送的下行控制信息，并根据所述下行控制信息接收所述网络设备发送的物理下行共享信道；以及向所述网络设备反馈针对所述物理下行共享信道的反馈信息；其中，针对多物理下行共享信道载波上的物理下行共享信道的反馈信息被包括在至少两个子码书中，其中一个子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和传输块被调度。

Description

反馈信息的发送和接收方法以及装置 技术领域
本申请实施例涉及通信技术领域。
背景技术
对于新无线(NR，New Radio)Rel-15、Rel-16，由于对FR2频率的支持，物理下行控制信道(PDCCH，Physical Downlink Control Channel)/物理下行共享信道(PDSCH，Physical Downlink Shared Channel)的子载波间隔(SCS，Subcarrier Spacing)最大可以达到120kHz。
对于NR Rel-15、Rel-16，一个下行控制信息(DCI，Downlink Control Information)只能调度一个PDSCH(以下简称为single-PDSCH调度)。终端设备可以反馈针对一段时间内一个或多个DCI调度的PDSCH的反馈信息，该反馈信息例如为混合自动重传请求(HARQ，Hybrid Automatic Repeat reQuest)码书(codebook)，也可称为HARQ-ACK或HARQ-ACK码书。
NR Rel-17目前正在研究对更高频率(52.6GHz～71GHz)的支持。更高的频率需要额外支持更大的SCS(大于120kHz)，更大的SCS意味着更短的时隙(slot)长度。由于处理能力的限制，终端设备的处理时间不能随着时隙长度等比例地减小。因此，工作在更高频率的终端设备的处理要求相比于低频时存在一定程度的放松。例如，终端设备不能过于频繁地盲检PDCCH。在这种情况下，两个相邻的PDCCH盲检机会之间可能间隔更多的时隙，即在一定程度上减少了对于某个终端设备的调度机会。
应该注意，上面对技术背景的介绍只是为了方便对本申请的技术方案进行清楚、完整的说明，并方便本领域技术人员的理解而阐述的。不能仅仅因为这些方案在本申请的背景技术部分进行了阐述而认为上述技术方案为本领域技术人员所公知。
发明内容
为了提供更加及时的PDSCH调度，NR Rel-17正在研究对多PDSCH(multi-PDSCH)调度的支持。对于multi-PDSCH调度，一个DCI能够调度多于一个的PDSCH。对于工作在高频(例如52.6GHz～71GHz)的终端设备，支持multi-PDSCH调度有利于实现PDSCH调度灵活性和设备处理能力之间的折中，并且能够降低DCI调度开销。因此， multi-PDSCH调度可能成为工作在52.6GHz～71GHz时支持的新特性。
但是，发明人发现：NR Rel-15和Rel-16标准中没有提供对multi-PDSCH调度的支持。目前，如何针对multi-PDSCH调度生成和发送反馈信息(例如Type 2 HARQ-ACK码书)仍然是一个开放性问题。
针对上述问题的至少之一，本申请实施例提供一种反馈信息的发送和接收方法以及装置。
根据本申请实施例的一个方面，提供一种反馈信息的发送方法，包括：
终端设备接收网络设备发送的下行控制信息；
根据所述下行控制信息接收所述网络设备发送的物理下行共享信道；以及
向所述网络设备反馈针对所述物理下行共享信道的反馈信息；
其中，针对多物理下行共享信道载波上的物理下行共享信道的反馈信息被包括在至少两个子码书中，其中一个子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和传输块被调度。
根据本申请实施例的另一个方面，提供一种反馈信息的发送装置，包括：
接收单元，其接收网络设备发送的下行控制信息，并根据所述下行控制信息接收所述网络设备发送的物理下行共享信道；以及
发送单元，其向所述网络设备反馈针对所述物理下行共享信道的反馈信息；
其中，针对多物理下行共享信道载波上的物理下行共享信道的反馈信息被包括在至少两个子码书中，其中一个子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和传输块被调度。
根据本申请实施例的另一个方面，提供一种反馈信息的接收方法，包括：
网络设备向终端设备发送下行控制信息；
向所述终端设备发送物理下行共享信道；以及
接收所述终端设备针对所述物理下行共享信道的反馈信息；
其中，针对多物理下行共享信道载波上的物理下行共享信道的反馈信息被包括在至少两个子码书中，其中一个子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和传输块被调度
根据本申请实施例的另一个方面，提供一种反馈信息的接收装置，包括：
发送单元，其向终端设备发送下行控制信息；向所述终端设备发送物理下行共享信道；以及
接收单元，其接收所述终端设备针对所述物理下行共享信道的反馈信息；
其中，针对多物理下行共享信道载波上的物理下行共享信道的反馈信息被包括在至少两个子码书中，其中一个子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和传输块被调度。
根据本申请实施例的另一个方面，提供一种通信系统，包括：
网络设备，向终端设备发送下行控制信息；向所述终端设备发送物理下行共享信道；以及接收所述终端设备针对所述物理下行共享信道的反馈信息；
终端设备，其接收所述网络设备发送的所述下行控制信息，并根据所述下行控制信息接收所述网络设备发送的所述物理下行共享信道；以及向所述网络设备反馈针对所述物理下行共享信道的反馈信息；
其中，针对多物理下行共享信道载波上的物理下行共享信道的反馈信息被包括在至少两个子码书中，其中一个子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和传输块被调度。
本申请实施例的有益效果之一在于：对于使能了(enabled)multi-PDSCH调度的载波，基于是否使用multi-PDSCH调度和/或是否使用码块组(CBG，Code Block Group)传输等信息生成多个子码书；由此不仅能够支持基于multi-PDSCH的反馈，而且通过划分子码书，能够减小Type 2 HARQ-ACK码书的尺寸，降低HARQ-ACK的反馈开销。
参照后文的说明和附图，详细公开了本申请的特定实施方式，指明了本申请的原理可以被采用的方式。应该理解，本申请的实施方式在范围上并不因而受到限制。在所附权利要求的精神和条款的范围内，本申请的实施方式包括许多改变、修改和等同。
针对一种实施方式描述和/或示出的特征可以以相同或类似的方式在一个或更多个其它实施方式中使用，与其它实施方式中的特征相组合，或替代其它实施方式中的特征。
应该强调，术语“包括/包含”在本文使用时指特征、整件、步骤或组件的存在，但并不排除一个或更多个其它特征、整件、步骤或组件的存在或附加。
附图说明
在本申请实施例的一个附图或一种实施方式中描述的元素和特征可以与一个或更多个其它附图或实施方式中示出的元素和特征相结合。此外，在附图中，类似的标号表示几个附图中对应的部件，并可用于指示多于一种实施方式中使用的对应部件。
图1是本申请实施例的通信系统的示意图；
图2A是本申请实施例的使用DAI动态决定反馈信息的一示例图；
图2B是本申请实施例的multi-PDSCH调度的一示例图；
图3是本申请实施例的载波聚合场景的一示例图；
图4是本申请实施例的反馈信息的发送方法的一示意图；
图5是本申请实施例的第一子码书的一示例图；
图6是本申请实施例的第二子码书的一示例图；
图7是本申请实施例的第三子码书的一示例图；
图8是本申请实施例的第二子码书的另一示例图；
图9是本申请实施例的第二子码书的另一示例图；
图10是本申请实施例的第三子码书的另一示例图；
图11是本申请实施例的第一子码书的另一示例图；
图12是本申请实施例的第二子码书的另一示例图；
图13是本申请实施例的第三子码书的另一示例图；
图14是本申请实施例的第一子码书的另一示例图；
图15是本申请实施例的第二子码书的另一示例图；
图16是本申请实施例的反馈信息的接收方法的一示意图；
图17是本申请实施例的反馈信息的发送装置的一示意图；
图18是本申请实施例的反馈信息的接收装置的一示意图；
图19是本申请实施例的网络设备的示意图；
图20是本申请实施例的终端设备的示意图。
具体实施方式
参照附图，通过下面的说明书，本申请的前述以及其它特征将变得明显。在说明书和附图中，具体公开了本申请的特定实施方式，其表明了其中可以采用本申请的原则的部分实施方式，应了解的是，本申请不限于所描述的实施方式，相反，本申请包括落入 所附权利要求的范围内的全部修改、变型以及等同物。
在本申请实施例中，术语“第一”、“第二”等用于对不同元素从称谓上进行区分，但并不表示这些元素的空间排列或时间顺序等，这些元素不应被这些术语所限制。术语“和/或”包括相关联列出的术语的一种或多个中的任何一个和所有组合。术语“包含”、“包括”、“具有”等是指所陈述的特征、元素、元件或组件的存在，但并不排除存在或添加一个或多个其他特征、元素、元件或组件。
在本申请实施例中，单数形式“一”、“该”等包括复数形式，应广义地理解为“一种”或“一类”而并不是限定为“一个”的含义；此外术语“所述”应理解为既包括单数形式也包括复数形式，除非上下文另外明确指出。此外术语“根据”应理解为“至少部分根据……”，术语“基于”应理解为“至少部分基于……”，除非上下文另外明确指出。
在本申请实施例中，术语“通信网络”或“无线通信网络”可以指符合如下任意通信标准的网络，例如长期演进(LTE，Long Term Evolution)、增强的长期演进(LTE-A，LTE-Advanced)、宽带码分多址接入(WCDMA，Wideband Code Division Multiple Access)、高速报文接入(HSPA，High-Speed Packet Access)等等。
并且，通信系统中设备之间的通信可以根据任意阶段的通信协议进行，例如可以包括但不限于如下通信协议：1G(generation)、2G、2.5G、2.75G、3G、4G、4.5G以及5G、新无线(NR，New Radio)等等，和/或其他目前已知或未来将被开发的通信协议。
在本申请实施例中，术语“网络设备”例如是指通信系统中将终端设备接入通信网络并为该终端设备提供服务的设备。网络设备可以包括但不限于如下设备：基站(BS，Base Station)、接入点(AP、Access Point)、发送接收点(TRP，Transmission Reception Point)、广播发射机、移动管理实体(MME、Mobile Management Entity)、网关、服务器、无线网络控制器(RNC，Radio Network Controller)、基站控制器(BSC，Base Station Controller)等等。
其中，基站可以包括但不限于：节点B(NodeB或NB)、演进节点B(eNodeB或eNB)以及5G基站(gNB)，等等，此外还可包括远端无线头(RRH，Remote Radio Head)、远端无线单元(RRU，Remote Radio Unit)、中继(relay)或者低功率节点(例如femeto、pico等等)。并且术语“基站”可以包括它们的一些或所有功能，每个基站可以对特定的地理区域提供通信覆盖。术语“小区”可以指的是基站和/或其覆盖区域，这取决于使用该术语的上下文。
在本申请实施例中，术语“用户设备”(UE，User Equipment)或者“终端设备”(TE， Terminal Equipment或Terminal Device)例如是指通过网络设备接入通信网络并接收网络服务的设备。终端设备可以是固定的或移动的，并且也可以称为移动台(MS，Mobile Station)、终端、用户台(SS，Subscriber Station)、接入终端(AT，Access Terminal)、站，等等。
其中，终端设备可以包括但不限于如下设备：蜂窝电话(Cellular Phone)、个人数字助理(PDA，Personal Digital Assistant)、无线调制解调器、无线通信设备、手持设备、机器型通信设备、膝上型计算机、无绳电话、智能手机、智能手表、数字相机，等等。
再例如，在物联网(IoT，Internet of Things)等场景下，终端设备还可以是进行监控或测量的机器或装置，例如可以包括但不限于：机器类通信(MTC，Machine Type Communication)终端、车载通信终端、设备到设备(D2D，Device to Device)终端、机器到机器(M2M，Machine to Machine)终端，等等。
此外，术语“网络侧”或“网络设备侧”是指网络的一侧，可以是某一基站，也可以包括如上的一个或多个网络设备。术语“用户侧”或“终端侧”或“终端设备侧”是指用户或终端的一侧，可以是某一UE，也可以包括如上的一个或多个终端设备。本文在没有特别指出的情况下，“设备”可以指网络设备，也可以指终端设备。
以下通过示例对本申请实施例的场景进行说明，但本申请不限于此。
图1是本申请实施例的通信系统的示意图，示意性说明了以终端设备和网络设备为例的情况，如图1所示，通信系统100可以包括网络设备101和终端设备102。为简单起见，图1仅以一个终端设备和一个网络设备为例进行说明，但本申请实施例不限于此，例如还可以有多个终端设备。
在本申请实施例中，网络设备101和终端设备102之间可以进行现有的业务或者未来可实施的业务发送。例如，这些业务可以包括但不限于：增强的移动宽带(eMBB，enhanced Mobile Broadband)、大规模机器类型通信(mMTC，massive Machine Type Communication)和高可靠低时延通信(URLLC，Ultra-Reliable and Low-Latency Communication)，等等。
NR Rel-15和Rel-16提供对Type 2 HARQ-ACK码书的支持，可以使用下行分配索引(DAI，Downlink Assignment Index)机制来动态地决定反馈的HARQ-ACK比特数目。Type 2 HARQ-ACK码书是一种动态HARQ-ACK码书，终端设备根据DCI指示的counter DAI和total DAI生成Type 2 HARQ-ACK码书。
图2A是本申请实施例的使用DAI动态决定反馈信息的一示例图，对Type 2 HARQ-ACK码书进行了示意性说明。其中，counter DAI对载波和DCI进行连续计数， total DAI指示的是当前时隙(slot)累积的DCI的总数。
如图2A所示，Type 2 HARQ-ACK码书由两个子码书(sub-codebook)组成，分别对应基于TB的传输和基于CBG的传输。这里，“基于TB的传输”等价于没有使能“基于CBG的传输”。counter DAI和total DAI在子码书内独立计数。为便于说明，图2A中的counter DAI和total DAI指示的是计数的绝对值。
在每个子码书中，根据子码书包括的所有载波中最大的HARQ-ACK比特数确定针对每次DCI调度的HARQ-ACK比特数。这里“子码书包括的载波”意味着该载波能够产生子码书中的反馈信息，或者说子码书包括针对该载波的反馈信息。CC表示载波聚合中的载波单元(Component Carrier)。N TB_max表示载波能够支持的最大TB数，N CBG_max_TB表示载波的每个TB能够支持的最大CBG数。
如图2A所示，第一个子码书包括针对6次调度的HARQ-ACK，由于最大的HARQ-ACK比特数为2，总共需要12比特的HARQ-ACK；第二个子码书包括针对7次调度的HARQ-ACK，由于最大的HARQ-ACK比特数为8，总共需要56比特的HARQ-ACK。这里第一子码书包括针对以下PDSCH的反馈信息，其中PDSCH在使能了基于CBG的传输的载波上被fallback DCI(DCI format 1_0)调度。最终的Type 2 HARQ-ACK码书通过将两个子码书级联后获得，总共包括68比特的HARQ-ACK。
NR Rel-15和Rel-16标准中没有提供对multi-PDSCH调度的支持。目前，如何针对multi-PDSCH调度生成和发送反馈信息(例如Type 2 HARQ-ACK码书)仍然是一个开放性问题。
对于type 2 HARQ-ACK码书，终端设备漏检DCI会导致其与网络设备对码书大小的理解不一致。为避免这一问题，type 2 HARQ-ACK码书按照载波中最大的HARQ-ACK比特数为每个载波产生HARQ-ACK，多余出来的HARQ-ACK比特被置为NACK。
图2B是本申请实施例的multi-PDSCH调度的一示例图。如图2B所示，一个DCI调度多个PDSCH(例如PDSCH#0、PDSCH#1、PDSCH#2……)，针对多个PDSCH的反馈信息在同一时刻被发送给网络设备。
由于multi-PDSCH的引入，终端设备需要在同一时刻反馈针对多个PDSCH的HARQ-ACK，因此最大的HARQ-ACK比特数可能成倍增长，按照最大的HARQ-ACK比特数产生HARQ-ACK，将导致type 2 HARQ-ACK码书的比特数大大增加，从而增加反馈开销。
在本申请实施例中，multi-PDSCH载波是使能了(enabled)通过一个DCI调度多个 PDSCH这一功能(multi-PDSCH功能)的载波；single-PDSCH载波是没有使能(disabled)通过一个DCI调度多个PDSCH这一功能的载波。本申请实施例中的载波(Carrier)可以被替换为载波单元(CC，Component Carrier)、服务小区(serving cell)、小区(cell)，等等，本申请不限于此。
在本申请实施例中，一个载波是multi-PDSCH载波或者single-PDSCH载波。对于multi-PDSCH载波，一个DCI可以调度一个或多个PDSCH；对于single-PDSCH载波，一个DCI只能调度一个PDSCH。一个PDSCH可以承载一个或多个TB。根据NR标准，一个PDSCH最多承载两个TB。
在本申请实施例中，对于如何确定一个载波是否是multi-PDSCH载波不做限制。
例如，可以根据无线资源控制(RRC，Radio Resource Control)或系统信息块(SIB，System Information Block)配置的时域资源分配表确定。对于某一载波，如果该表中的某一行能够指示多个PDSCH的时域资源和/或映射类型(mapping type)，例如指示了多个SLIV(Start and length indicator value)和/或映射类型(mapping type)，则该载波为multi-PDSCH载波，否则该载波为single-PDSCH载波。
又例如，可以根据该载波支持的DCI格式确定。如果支持的DCI格式包括多个新数据指示(NDI，New Data Indicator)和/或冗余版本(RV，Redundancy Version)字段，则该载波为multi-PDSCH载波，否则该载波为single-PDSCH载波。
又例如，可以根据RRC配置的multi-PDSCH参数确定。一个载波如果配置了multi-PDSCH参数，表示该载波使能了multi-PDSCH功能，则该载波为multi-PDSCH载波；否则，该载波为single-PDSCH载波。
在本申请实施例中，基于multi-PDSCH的调度指一个DCI调度多于一个PDSCH；基于single-PDSCH的调度指一个DCI调度一个PDSCH。single-PDSCH载波只能支持基于single-PDSCH的调度；multi-PDSCH载波能支持基于multi-PDSCH的调度，也能支持基于single-PDSCH的调度。假设某一DCI调度了载波c上的PDSCH，该DCI可以来自载波c，也可以来自其他不同于载波c的载波(跨载波调度)。
在本申请实施例中，“基于multi-PDSCH调度”可以替换为“以multi-PDSCH方式调度”；“基于single-PDSCH调度”可以替换为“以single-PDSCH方式调度”。调度multi-PDSCH载波的DCI不一定总是调度多于一个PDSCH。DCI可以动态切换调度一个PDSCH还是调度多个PDSCH。
在本申请实施例中，针对基于multi-PDSCH调度的反馈信息(即针对多个PDSCH 的反馈信息)在同一时刻从终端设备发送给网络设备。
在一些实施例中，第一DCI被用于基于multi-PDSCH进行调度，第二DCI被用于基于single-PDSCH进行调度；所述第一DCI和所述第二DCI的DCI格式不同。
例如，调度multi-PDSCH载波的可以是不同的DCI格式(DCI format)，一种DCI格式(为支持multi-PDSCH新定义的DCI格式)可以指示基于multi-PDSCH的调度，另一种DCI格式(传统DCI格式，包括：DCI format 1_0、DCI format 1_1、DCI format 1_2等)可以指示基于single-PDSCH的调度。支持传统DCI格式对于系统的鲁棒性和兼容性是有好处的，例如，在信道条件差时可以使用fallback DCI(DCI format 1_0)进行调度。
在一些实施例中，DCI中的字段指示基于multi-PDSCH调度或者基于single-PDSCH调度。
例如，DCI的字段指示了多个SLIV和/或映射类型(mapping type)，用于指示多个PDSCH的SLIV和映射类型，则该DCI指示基于multi-PDSCH的调度。即使使用为支持multi-PDSCH新定义的DCI格式，也可以在RRC配置的时域资源分配表的某一行指示单个PDSCH资源，在另一行指示多个PDSCH资源，然后通过DCI中的字段动态指示不同的行，即可在基于multi-PDSCH的调度和基于single-PDSCH的调度之间灵活切换。
又例如，DCI包含多个新数据指示(NDI，New Data Indicator)和/或冗余版本(RV，Redundancy Version)字段，用于指示多个PDSCH的NDI和RV，则该DCI指示基于multi-PDSCH的调度。
在本申请实施例中，对终端设备如何识别基于single-PDSCH调度和基于multi-PDSCH调度不做限制。如前所述，例如，终端设备可以根据DCI格式进行识别。当接收到DCI format 1_0、DCI format 1_1、DCI format 1_2等传统DCI格式时，终端设备即可知晓这些DCI调度的是基于single-PDSCH的发送。当接收到为支持multi-PDSCH而新定义的DCI格式时，终端设备可知晓该DCI调度的是基于multi-PDSCH的发送。又例如，终端设备可以根据DCI字段判断，通过DCI的具体信令内容来区分基于single-PDSCH调度和基于multi-PDSCH调度。又例如，终端设备也可以基于以上两种方式的结合进行识别。
图3是本申请实施例的载波聚合场景的一示例图，如图3所示，载波聚合的载波单元(CC，Component Carrier)包括：
-single-PDSCH载波集合C0：C0中的载波没有被配置基于CBG的传输。换句话说，载波没有被使能基于CBG的传输。简单起见，将“没有被使能基于CBG的传输”简称为“基于TB调度”，将“使能了基于CBG的传输”简称为“基于CBG调度”。对于集合C0中的载波c，N TB_max,c表示载波c能够支持的最大TB数。根据NR标准，1≤N TB_max,c≤2。
-single-PDSCH载波集合C1：C1中的载波被配置基于CBG的传输，简称为基于CBG调度。对于集合C1中的载波c，N TB_max,c表示载波c能够支持的最大TB数，N CBG_max_TB,c表示载波c的每个TB能够支持的最大CBG数。根据NR标准，2≤N TB_max,c×N CBG_max_TB,c≤8。
-multi-PDSCH载波集合C2：C2中的载波没有被配置基于CBG的传输，简称为基于TB调度。对于集合C2中的载波c，N TB_max,c表示载波c的每个PDSCH能够支持的最大TB数，N multi_PDSCH_max,c表示载波c能够支持的一个DCI能够调度的最大PDSCH数。简单起见，将N TB_max,c也称为载波c能够支持的最大TB数。
-multi-PDSCH载波集合C3：C3中的载波被配置基于CBG的传输，简称为基于CBG调度。对于集合C3中的载波c，N TB_max,c表示载波c的每个PDSCH能够支持的最大TB数，N CBG_max_TB,c表示载波c的每个TB能够支持的最大CBG数，N multi_PDSCH_max,c表示载波c能够支持的一个DCI能够调度的最大PDSCH数。简单起见，将N TB_max,c也称为载波c能够支持的最大TB数。
图3的载波聚合包括了所有类型的载波。当不存在某一类载波时，载波聚合变为图3的一种特例。
在本申请实施例中，对于“基于TB调度”的载波(即没有使能基于CBG传输的载波)，PDSCH只能基于TB调度。对于“基于CBG调度”的载波(即使能了基于CBG传输的载波)，PDSCH可以基于CBG调度，也可以基于TB调度。“基于TB调度”可以替换为“以TB方式调度”；“基于CBG调度”可以替换为“以CBG方式调度”。
以上对于multi-PDSCH和single-PDSCH等进行了示意性说明，以下将对本申请实施例进行进一步说明。在以下的说明中，发送(transmitting)或接收(receiving)PDCCH可以理解为发送或接收由PDCCH承载的下行控制信息；发送或接收PDSCH可以理解 为发送或接收由PDSCH承载的下行数据。
第一方面的实施例
本申请实施例提供一种反馈信息的发送方法，从终端设备进行说明。
图4是本申请实施例的反馈信息的发送方法的一示意图，如图4所示，该方法包括：
401，终端设备接收网络设备发送的下行控制信息(DCI)，
402，终端设备根据所述下行控制信息接收所述网络设备发送的物理下行共享信道(PDSCH)；以及
403，终端设备向所述网络设备反馈针对所述物理下行共享信道的反馈信息；
其中，针对multi-PDSCH载波上的PDSCH的反馈信息被包括在至少两个子码书中，其中一个子码书中包括针对如下PDSCH的反馈信息：所述PDSCH在multi-PDSCH载波上基于single-PDSCH和传输块(TB)被调度。
值得注意的是，以上附图4仅对本申请实施例进行了示意性说明，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图3的记载。
在一些实施例中，HARQ-ACK码书包括第一子码书、第二子码书和第三子码书。
在一些实施例中，第一子码书中包括针对如下PDSCH的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于传输块被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和传输块被调度。
即，第一子码书包括针对以下PDSCH的HARQ-ACK：
-single-PDSCH载波上以TB方式调度的PDSCH。
-multi-PDSCH载波上以single-PDSCH方式和TB方式调度的PDSCH。
图5是本申请实施例的第一子码书的一示例图，示出了对应图3划分的载波集合的情况。如图5所示，第一子码书包括针对以下PDSCH的HARQ-ACK：
-集合C0的载波上调度的PDSCH；
-集合C1的载波上以TB方式调度的PDSCH；
-集合C2的载波上以single-PDSCH方式调度的PDSCH；
-集合C3的载波上以single-PDSCH方式和TB方式调度的PDSCH。
在本申请实施例中，如果与上述确定子码书有关的某个载波不存在，则子码书自然 不包括与该载波相关的HARQ-ACK。例如，载波聚合的载波中可能不包括C0和C1，此时第一子码书不包括与C0、C1相关的HARQ-ACK。又例如，载波聚合的载波中可能不包括C3，此时第一子码书不包括与C3相关的HARQ-ACK。类似的情况，在此不一一列举。
在一些实施例中，第一子码书包括针对单物理下行共享信道载波和/或多物理下行共享信道载波上的如下至少之一的反馈信息：半持续调度物理下行共享信道释放(SPS PDSCH release)、半持续调度物理下行共享信道(SPS PDSCH reception)、指示辅小区休眠的下行控制信息(DCI indicating SCell dormancy)。
例如，第一子码书还可以包括针对以下信息的HARQ-ACK：
-半持续调度物理下行共享信道释放(SPS PDSCH release)。
-半持续调度物理下行共享信道(SPS PDSCH)。
-指示辅小区休眠的DCI(DCI indicating SCell dormancy)。
例如，DCI可以指示SPS PDSCH release，针对该DCI的HARQ-ACK被包括在第一子码书中。SPS PDSCH可能没有与之关联的DCI调度，针对SPS PDSCH的HARQ-ACK被包括在第一子码书中。DCI可以指示辅小区休眠，例如DCI format 1_1指示辅小区休眠，针对该DCI的HARQ-ACK被包括在第一子码书中。如果与上述确定子码书有关的某一信息不存在，则子码书自然不包括与该信息相关的HARQ-ACK。
在一些实施例中，第一子码书中针对一次下行调度的反馈信息的比特数为N max＝max c{N TB_max,c}，载波c是能够产生所述第一子码书中反馈信息的载波，N TB_max,c为载波c能够支持的最大传输块(TB)的数目。
例如，对于第一子码书中的每次可能的PDSCH调度，假设其对应的HARQ-ACK比特数为
Figure PCTCN2020121236-appb-000001
其中N c＝N TB_max,c。换句话说，counter DAI或total DAI的数值每增加1，HARQ-ACK比特数增加N max比特。按照最大可能的HARQ-ACK比特数进行预留，可以避免在漏检DCI时，终端设备和网络设备对HARQ-ACK码书的大小产生歧义。
在一些实施例中，第二子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于码块组(CBG)被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和码块组(CBG)被调度。
即，第二子码书包括针对以下PDSCH的HARQ-ACK：
-single-PDSCH载波上以CBG方式调度的PDSCH。
-multi-PDSCH载波上以single-PDSCH方式和CBG方式调度的PDSCH。
图6是本申请实施例的第二子码书的一示例图，示出了对应图3划分的载波集合的情况。如图6所示，第二子码书包括针对以下PDSCH的HARQ-ACK：
-集合C1的载波上以CBG方式调度的PDSCH。
-集合C3的载波上以single-PDSCH方式和CBG方式调度的PDSCH。
在本申请实施例中，如果与上述确定子码书有关的某种PDSCH调度不存在，则子码书自然不包括与该PDSCH相关的HARQ-ACK。例如，如果C3的载波不支持以single-PDSCH方式和CBG方式调度的PDSCH，则第二子码书不包括与该PDSCH相关的HARQ-ACK。
在一些实施例中，所述第二子码书中针对一次下行调度的反馈信息的比特数为N max＝max c{N TB_max,c×N CBG_max_TB,c}，载波c是能够产生所述第二子码书中反馈信息的载波，N TB_max,c为载波c能够支持的最大传输块(TB)的数目，N CBG_max_TB,c为载波c上每个传输块(TB)能够支持的最大码块组(CBG)的数目。
例如，对于第二子码书中的每次可能的PDSCH调度，假设其对应的HARQ-ACK比特数为
Figure PCTCN2020121236-appb-000002
其中N c＝N TB_max,c×N CBG_max_TB,c。
在一些实施例中，第三子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在多物理下行共享信道载波上基于多物理下行共享信道被调度。
即，第三子码书包括针对以下PDSCH的HARQ-ACK：
-multi-PDSCH载波上以multi-PDSCH方式调度的PDSCH。
图7是本申请实施例的第三子码书的一示例图，示出了对应图3划分的载波集合的情况。如图7所示，第三子码书包括针对以下PDSCH的HARQ-ACK：
-集合C2的载波上以multi-PDSCH方式调度的PDSCH。
-集合C3的载波上以multi-PDSCH方式调度的PDSCH。
对于集合C3的载波上基于multi-PDSCH调度的PDSCH，其包括基于multi-PDSCH和CBG调度的PDSCH，也包括基于multi-PDSCH和TB调度的PDSCH。如果某一种PDSCH不存在，则子码书不包括针对该PDSCH的HARQ-ACK。例如，如果集合C3中的载波不支持基于multi-PDSCH和TB的调度，则子码书不包括针对该调度的 HARQ-ACK。
在一些实施例中，所述第三子码书中针对一次下行调度的反馈信息的比特数为N max＝max c{N c}；载波c是能够产生所述第三子码书中反馈信息的载波；
对于没有被使能基于码块组传输的载波c，N c＝N TB_max,c×N multi_PDSCH_max,c；对于使能了基于码块组传输的载波c，N c＝N TB_max,c×N CBG_max_TB,c×N multi_PDSCH_max,c；
N TB_max,c为载波c能够支持的最大传输块(TB)的数目，N CBG_max_TB,c为载波c上每个传输块(TB)能够支持的最大码块组(CBG)的数目，N multi_PDSCH_max,c为下行控制信息(DCI)能够调度的载波c上的最大物理下行共享信道的数目。
例如，对于第三子码书中的每次可能的PDSCH调度，假设其对应的HARQ-ACK比特数为
Figure PCTCN2020121236-appb-000003
对于集合C2中的载波c，N c＝N TB_max,c×N multi_PDSCH_max,c。对于集合C3中的载波c，N c＝N TB_max,c×N CBG_max_TB,c×N multi_PDSCH_max,c。
在本申请实施例中，counter DAI和total DAI在每个子码书内部独立计数。终端设备向网络设备发送的HARQ-ACK码书通过将上述各个子码书级联获得。本申请实施例对子码书的级联顺序不做限制，例如按照第一、第二、第三子码书的顺序进行级联。由此，通过划分子码书，可以减小Type 2 HARQ-ACK码书的尺寸，降低HARQ-ACK反馈开销。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
由上述实施例可知，对于使能了(enabled)multi-PDSCH调度的载波，基于是否使用multi-PDSCH调度和/或是否使用CBG传输等信息生成多个子码书；由此不仅能够支持基于multi-PDSCH的反馈，而且通过划分子码书，能够减小Type 2 HARQ-ACK码书的尺寸，降低HARQ-ACK的反馈开销。
第二方面的实施例
在第一方面的实施例的基础上，本申请实施例从终端设备继续进行说明，与第一方 面的实施例相同的内容不再赘述。
在一些实施例中，HARQ-ACK码书可以包括第一子码书和第二子码书。
在一些实施例中，第一子码书中包括针对如下PDSCH的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于传输块被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和传输块被调度。
即，第一子码书包括针对以下PDSCH的HARQ-ACK：
-single-PDSCH载波上以TB方式调度的PDSCH。
-multi-PDSCH载波上以single-PDSCH方式和TB方式调度的PDSCH。
具体还可以参考第一方面的实施例中的第一子码书。
在一些实施例中，第二子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于码块组(CBG)被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和码块组(CBG)被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于多物理下行共享信道被调度。
即，第二子码书包括针对以下PDSCH的HARQ-ACK：
-single-PDSCH载波上以CBG方式调度的PDSCH。
-multi-PDSCH载波上以single-PDSCH方式和CBG方式调度的PDSCH。
-multi-PDSCH载波上以multi-PDSCH方式调度的PDSCH。
图8是本申请实施例的第二子码书的一示例图，示出了对应图3划分的载波集合的情况。如图8所示，第二子码书包括针对以下PDSCH的HARQ-ACK：
-集合C1的载波上以CBG方式调度的PDSCH。
-集合C2的载波上以multi-PDSCH方式调度的PDSCH。
-集合C3的载波上以single-PDSCH方式和CBG方式调度的PDSCH、以multi-PDSCH方式调度的PDSCH。
在一些实施例中，所述第二子码书中针对一次下行调度的反馈信息的比特数为N max＝max c{N c}；载波c是能够产生第所述二子码书中反馈信息的载波；
对于使能了基于码块组传输的单物理下行共享信道载波c，N c＝N TB_max,c×N CBG_max_TB,c；对于没有使能基于码块组传输的多物理下行共享信道载波c，N c＝N TB_max,c×N multi_PDSCH_max,c；对于使能了基于码块组传输的多物理下行共享信道 载波c，N c＝N TB_max,c×N CBG_max_TB,c×N multi_PDSCH_max,c；
N TB_max,c为载波c能够支持的最大传输块(TB)的数目，N CBG_max_TB,c为载波c上每个传输块(TB)能够支持的最大码块组(CBG)的数目，N multi_PDSCH_max,c为下行控制信息(DCI)能够调度的载波c上的最大物理下行共享信道的数目。
例如，对于第二子码书中的每次可能的PDSCH调度，假设其对应的HARQ-ACK比特数为
Figure PCTCN2020121236-appb-000004
对于集合C1中的载波c，N c＝N TB_max,c×N CBG_max_TB,c。对于集合C2中的载波c，N c＝N TB_max,c×N multi_PDSCH_max,c。对于集合C3中的载波c，N c＝N TB_max,c×N CBG_max_TB,c×N multi_PDSCH_max,c。
在本申请实施例中，counter DAI和total DAI在每个子码书内部独立计数。终端设备向网络设备发送的HARQ-ACK码书通过将上述各个子码书级联获得。本申请实施例对子码书的级联顺序不做限制，例如按照第一、第二子码书的顺序进行级联。由此，通过划分子码书，可以减小Type 2 HARQ-ACK码书的尺寸，降低HARQ-ACK反馈开销。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
由上述实施例可知，对于使能了(enabled)multi-PDSCH调度的载波，基于是否使用multi-PDSCH调度和/或是否使用CBG传输等信息生成多个子码书；由此不仅能够支持基于multi-PDSCH的反馈，而且通过划分子码书，能够减小Type 2 HARQ-ACK码书的尺寸，降低HARQ-ACK的反馈开销。
第三方面的实施例
在第一、二方面的实施例的基础上，本申请实施例从终端设备继续进行说明，与第一、二方面的实施例相同的内容不再赘述。
在一些实施例中，HARQ-ACK码书可包括第一子码书、第二子码书和第三子码书。
在一些实施例中，第一子码书中包括针对如下PDSCH的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于传输块被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和传输块被调度。
即，第一子码书包括针对以下PDSCH的HARQ-ACK：
-single-PDSCH载波上以TB方式调度的PDSCH。
-multi-PDSCH载波上以single-PDSCH方式和TB方式调度的PDSCH。
具体还可以参考第一方面的实施例中的第一子码书。
第二子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于码块组(CBG)被调度。
即，第二子码书包括针对以下PDSCH的HARQ-ACK：
-single-PDSCH载波上以CBG方式调度的PDSCH。
图9是本申请实施例的第二子码书的一示例图，示出了对应图3划分的载波集合的情况。如图9所示，第二子码书包括针对以下PDSCH的HARQ-ACK：
-集合C1的载波上以CBG方式调度的PDSCH。
在一些实施例中，所述第二子码书中针对一次下行调度的反馈信息的比特数为N max＝max c{N TB_max,c×N CBG_max_TB,c}，载波c是能够产生所述第二子码书中反馈信息的载波，N TB_max,c为载波c能够支持的最大传输块(TB)的数目，N CBG_max_TB,c为载波c上每个传输块(TB)能够支持的最大码块组(CBG)的数目。
例如，对于第二子码书中的每次可能的PDSCH调度，假设其对应的HARQ-ACK比特数为
Figure PCTCN2020121236-appb-000005
其中N c＝N TB_max,c×N CBG_max_TB,c。
在一些实施例中，第三子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和码块组(CBG)被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于多物理下行共享信道被调度。
即，第三子码书包括针对以下PDSCH的HARQ-ACK：
-multi-PDSCH载波上以single-PDSCH方式和CBG方式调度的PDSCH。
-multi-PDSCH载波上以multi-PDSCH方式调度的PDSCH。
图10是本申请实施例的第三子码书的一示例图，示出了对应图3划分的载波集合的情况。如图10所示，第三子码书包括针对以下PDSCH的HARQ-ACK：
-集合C2的载波上以multi-PDSCH方式调度的PDSCH。
-集合C3的载波上以single-PDSCH方式和CBG方式调度的PDSCH、以multi-PDSCH方式调度的PDSCH。
在一些实施例中，所述第三子码书中针对一次下行调度的反馈信息的比特数为 N max＝max c{N c}；载波c是能够产生所述第三子码书中反馈信息的载波；
对于没有使能基于码块组传输的多物理下行共享信道载波c，N c＝N TB_max,c×N multi_PDSCH_max,c；对于使能了基于码块组传输的多物理下行共享信道载波c，N c＝N TB_max,c×N CBG_max_TB,c×N multi_PDSCH_max,c；
N TB_max,c为载波c能够支持的最大传输块(TB)的数目，N CBG_max_TB,c为载波c上每个传输块(TB)能够支持的最大码块组(CBG)的数目，N multi_PDSCH_max,c为下行控制信息(DCI)能够调度的载波c上的最大物理下行共享信道的数目。
例如，对于第三子码书中的每次可能的PDSCH调度，假设其对应的HARQ-ACK比特数为
Figure PCTCN2020121236-appb-000006
对于集合C2中的载波c，N c＝N TB_max,c×N multi_PDSCH_max,c。对于集合C3中的载波c，N c＝N TB_max,c×N CBG_max_TB,c×N multi_PDSCH_max,c。
在本申请实施例中，counter DAI和total DAI在每个子码书内部独立计数。终端设备向网络设备发送的HARQ-ACK码书通过将上述各个子码书级联获得。本申请实施例对子码书的级联顺序不做限制，例如按照第一、第二子码书和第三码书的顺序进行级联。由此，通过划分子码书，可以减小Type 2 HARQ-ACK码书的尺寸，降低HARQ-ACK反馈开销。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
由上述实施例可知，对于使能了(enabled)multi-PDSCH调度的载波，基于是否使用multi-PDSCH调度和/或是否使用CBG传输等信息生成多个子码书；由此不仅能够支持基于multi-PDSCH的反馈，而且通过划分子码书，能够减小Type 2 HARQ-ACK码书的尺寸，降低HARQ-ACK的反馈开销。
第四方面的实施例
在第一至三方面的实施例的基础上，本申请实施例从终端设备继续进行说明，与第一至三方面的实施例相同的内容不再赘述。
在一些实施例中，针对第一物理下行共享信道的反馈信息和针对第二物理下行共享信道的反馈信息在不同的子码书中，所述第一物理下行共享信道在多物理下行共享信道(multi-PDSCH)载波上被调度，所述第二物理下行共享信道在单物理下行共享信道(single-PDSCH)载波上被调度。
在一些实施例中，HARQ-ACK码书可包括第一子码书、第二子码书和第三子码书。
在一些实施例中，第一子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于传输块(TB)被调度。
即，第一子码书包括针对以下PDSCH的HARQ-ACK：
-single-PDSCH载波上以TB方式调度的PDSCH。
图11是本申请实施例的第一子码书的一示例图，示出了对应图3划分的载波集合的情况。如图11所示，第一子码书包括针对以下PDSCH的HARQ-ACK：
-集合C0的载波上调度的PDSCH。
-集合C1的载波上以TB方式调度的PDSCH。
例如，对于第一子码书中的每次可能的PDSCH调度，假设其对应的HARQ-ACK比特数为
Figure PCTCN2020121236-appb-000007
其中，N c＝N TB_max,c。
在一些实施例中，第二子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于码块组(CBG)被调度。
即，第二子码书包括针对以下PDSCH的HARQ-ACK：
-single-PDSCH载波上以CBG方式调度的PDSCH。
图12是本申请实施例的第二子码书的一示例图，示出了对应图3划分的载波集合的情况。如图12所示，第二子码书包括针对以下PDSCH的HARQ-ACK：
-集合C1的载波上以CBG方式调度的PDSCH。
例如，对于第二子码书中的每次可能的PDSCH调度，假设其对应的HARQ-ACK比特数为
Figure PCTCN2020121236-appb-000008
其中N c＝N TB_max,c×N CBG_max_TB,c。
在一些实施例中，第三子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在多物理下行共享信道载波上被调度。
即，第三子码书包括针对以下PDSCH的HARQ-ACK：
-multi-PDSCH载波上调度的PDSCH。
图13是本申请实施例的第三子码书的一示例图，示出了对应图3划分的载波集合 的情况。如图13所示，第三子码书包括针对以下PDSCH的HARQ-ACK：
-集合C2的载波上调度的PDSCH。
-集合C3的载波上调度的PDSCH。
例如，对于第三子码书中的每次可能的PDSCH调度，假设其对应的HARQ-ACK比特数为
Figure PCTCN2020121236-appb-000009
对于集合C2中的载波c，N c＝N TB_max,c×N multi_PDSCH_max,c。对于集合C3中的载波c，N c＝N TB_max,c×N CBG_max_TB,c×N multi_PDSCH_max,c。
在本申请实施例中，counter DAI和total DAI在每个子码书内部独立计数。终端设备向网络设备发送的HARQ-ACK码书通过将上述各个子码书级联获得。本申请实施例对子码书的级联顺序不做限制，例如按照第一、第二子码书和第三码书的顺序进行级联。由此，通过划分子码书，可以减小Type 2 HARQ-ACK码书的尺寸，降低HARQ-ACK反馈开销。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
由上述实施例可知，对于使能了(enabled)multi-PDSCH调度的载波，基于是否使用multi-PDSCH调度和/或是否使用CBG传输等信息生成多个子码书；由此不仅能够支持基于multi-PDSCH的反馈，而且通过划分子码书，能够减小Type 2 HARQ-ACK码书的尺寸，降低HARQ-ACK的反馈开销。
第五方面的实施例
在第一至四方面的实施例的基础上，本申请实施例从终端设备继续进行说明，与第一至四方面的实施例相同的内容不再赘述。
在一些实施例中，针对第三物理下行共享信道的反馈信息和针对第四物理下行共享信道的反馈信息在不同的子码书中，所述第三物理下行共享信道在多物理下行共享信道(multi-PDSCH)载波上基于传输块(TB)被调度，所述第二物理下行共享信道在多物理下行共享信道(multi-PDSCH)载波上基于码块组(CBG)被调度。
在一些实施例中，HARQ-ACK码书可以包括第一子码书和第二子码书。
在一些实施例中，第一子码书中包括针对如下物理下行共享信道的反馈信息：所述 物理下行共享信道在单物理下行共享信道载波上基于传输块(TB)被调度和/或，所述物理下行共享信道在多物理下行共享信道载波上基于传输块(TB)被调度。
即，第一子码书包括针对以下PDSCH的HARQ-ACK：
-single-PDSCH载波上以TB方式调度的PDSCH。
-multi-PDSCH载波上以TB方式调度的PDSCH。
图14是本申请实施例的第一子码书的一示例图，示出了对应图3划分的载波集合的情况。如图14所示，第一子码书包括针对以下PDSCH的HARQ-ACK：
-集合C0的载波上调度的PDSCH。
-集合C1的载波上以TB方式调度的PDSCH。
-集合C2的载波上调度的PDSCH。
-集合C3的载波上以TB方式调度的PDSCH。
例如，对于第一子码书中的每次可能的PDSCH调度，假设其对应的HARQ-ACK比特数为
Figure PCTCN2020121236-appb-000010
对于集合C0、C1中的载波c，N c＝N TB_max,c。对于集合C2、C3中的载波c，N c＝N TB_max,c×N multi_PDSCH_max,c。
在一些实施例中，第二子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于码块组(CBG)被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于码块组(CBG)被调度。
即，第二子码书包括针对以下PDSCH的HARQ-ACK：
-single-PDSCH载波上以CBG方式调度的PDSCH。
-multi-PDSCH载波上以CBG方式调度的PDSCH。
图15是本申请实施例的第二子码书的一示例图，示出了对应图3划分的载波集合的情况。如图15所示，第二子码书包括针对以下PDSCH的HARQ-ACK：
-集合C1的载波上以CBG方式调度的PDSCH。
-集合C3的载波上以CBG方式调度的PDSCH。
例如，对于第二子码书中的每次可能的PDSCH调度，假设其对应的HARQ-ACK比特数为
Figure PCTCN2020121236-appb-000011
对于集合C1中的载波c，N c＝N TB_max,c×N CBG_max_TB,c。对于集合C3中的载波c，N c＝N TB_max,c×N CBG_max_TB,c×N multi_PDSCH_max,c。
在本申请实施例中，counter DAI和total DAI在每个子码书内部独立计数。终端设备向网络设备发送的HARQ-ACK码书通过将上述各个子码书级联获得。本申请实施例对子码书的级联顺序不做限制，例如按照第一、第二子码书的顺序进行级联。由此，通过划分子码书，可以减小Type 2 HARQ-ACK码书的尺寸，降低HARQ-ACK反馈开销。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
由上述实施例可知，对于使能了(enabled)multi-PDSCH调度的载波，基于是否使用multi-PDSCH调度和/或是否使用CBG传输等信息生成多个子码书；由此不仅能够支持基于multi-PDSCH的反馈，而且通过划分子码书，能够减小Type 2 HARQ-ACK码书的尺寸，降低HARQ-ACK的反馈开销。
第六方面的实施例
本申请实施例提供一种反馈信息的接收方法，从网络设备进行说明，与第一至五方面的实施例相同的内容不再赘述。
图16是本申请实施例的反馈信息的接收方法的一示意图，如图16所示，该方法包括：
1601，网络设备向终端设备发送下行控制信息(DCI)；
1602，向所述终端设备发送物理下行共享信道(PDSCH)；以及
1603，接收所述终端设备针对所述物理下行共享信道的反馈信息。
值得注意的是，以上附图16仅对本申请实施例进行了示意性说明，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图16的记载。
在一些实施例中，针对多物理下行共享信道载波上的物理下行共享信道的反馈信息被包括在至少两个子码书中，其中一个子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和传输块被调度。
例如，所述至少两个子码书包括：
第一子码书；所述第一子码书中包括针对如下物理下行共享信道的反馈信息：所述 物理下行共享信道在单物理下行共享信道载波上基于传输块被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和传输块被调度；
第二子码书；所述第二子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于码块组(CBG)被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和码块组(CBG)被调度；
第三子码书；所述第三子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在多物理下行共享信道载波上基于多物理下行共享信道被调度。
再例如，所述至少两个子码书包括：
第一子码书；所述第一子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于传输块被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和传输块被调度；
第二子码书；所述第二子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于码块组(CBG)被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和码块组(CBG)被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于多物理下行共享信道被调度。
再例如，所述至少两个子码书包括：
第一子码书；所述第一子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于传输块被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和传输块被调度；
第二子码书；所述第二子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于码块组(CBG)被调度；
第三子码书；所述第三子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和码块组(CBG)被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于多物理下行共享信道被调度。
在一些实施例中，针对第一物理下行共享信道的反馈信息和针对第二物理下行共享信道的反馈信息在不同的子码书中，所述第一物理下行共享信道在多物理下行共享信道(multi-PDSCH)载波上被调度，所述第二物理下行共享信道在单物理下行共享信道 (single-PDSCH)载波上被调度。
例如，所述子码书包括：
第一子码书；所述第一子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于传输块(TB)被调度；
第二子码书；所述第二子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于码块组(CBG)被调度；
第三子码书；所述第三子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在多物理下行共享信道载波上被调度。
在一些实施例中，针对第三物理下行共享信道的反馈信息和针对第四物理下行共享信道的反馈信息在不同的子码书中，所述第三物理下行共享信道在多物理下行共享信道(multi-PDSCH)载波上基于传输块(TB)被调度，所述第二物理下行共享信道在多物理下行共享信道(multi-PDSCH)载波上基于码块组(CBG)被调度。
例如，所述子码书包括：
第一子码书；所述第一子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于传输块(TB)被调度和/或，所述物理下行共享信道在多物理下行共享信道载波上基于传输块(TB)被调度；
第二子码书；所述第二子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于码块组(CBG)被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于码块组(CBG)被调度。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
由上述实施例可知，对于使能了(enabled)multi-PDSCH调度的载波，基于是否使用multi-PDSCH调度和/或是否使用CBG传输等信息生成多个子码书；由此不仅能够支持基于multi-PDSCH的反馈，而且通过划分子码书，能够减小Type 2 HARQ-ACK码书的尺寸，降低HARQ-ACK的反馈开销。
第七方面的实施例
本申请实施例提供一种反馈信息的发送装置。该装置例如可以是终端设备，也可以是配置于终端设备的某个或某些部件或者组件，与第一至五方面的实施例相同的内容不 再赘述。
图17是本申请实施例的反馈信息的发送装置的一示意图。如图17所示，反馈信息的发送装置1700包括：
接收单元1701，其接收网络设备发送的下行控制信息，并根据所述下行控制信息接收所述网络设备发送的物理下行共享信道；以及
发送单元1702，其向所述网络设备反馈针对所述物理下行共享信道的反馈信息。
在一些实施例中，针对多物理下行共享信道载波上的物理下行共享信道的反馈信息被包括在至少两个子码书中，其中一个子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和传输块被调度。
在一些实施例中，第一下行控制信息被用于基于多物理下行共享信道进行调度，第二下行控制信息被用于基于单物理下行共享信道进行调度；所述第一下行控制信息和所述第二下行控制信息的下行控制信息格式不同。
在一些实施例中，所述至少两个子码书包括：第一子码书；所述第一子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于传输块被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和传输块被调度。
在一些实施例中，所述第一子码书包括针对单物理下行共享信道载波和/或多物理下行共享信道载波上的如下至少之一的反馈信息：半持续调度物理下行共享信道释放、半持续调度物理下行共享信道、指示辅小区休眠的下行控制信息。
在一些实施例中，所述第一子码书中针对一次下行调度的反馈信息的比特数为N max＝max c{N TB_max,c}，载波c是能够产生所述第一子码书中反馈信息的载波，N TB_max,c为载波c能够支持的最大传输块的数目。
在一些实施例中，所述至少两个子码书还包括：第二子码书；所述第二子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于码块组被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和码块组被调度。
在一些实施例中，所述第二子码书中针对一次下行调度的反馈信息的比特数为N max＝max c{N TB_max,c×N CBG_max_TB,c}，载波c是能够产生所述第二子码书中反馈信息 的载波，N TB_max,c为载波c能够支持的最大传输块的数目，N CBG_max_TB,c为载波c上每个传输块能够支持的最大码块组的数目。
在一些实施例中，所述至少两个子码书还包括：第三子码书；所述第三子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在多物理下行共享信道载波上基于多物理下行共享信道被调度。
在一些实施例中，所述第三子码书中针对一次下行调度的反馈信息的比特数为N max＝max c{N c}；载波c是能够产生所述第三子码书中反馈信息的载波；
对于没有被使能基于码块组传输的载波c，N c＝N TB_max,c×N multi_PDSCH_max,c；对于使能了基于码块组传输的载波c，N c＝N TB_max,c×N CBG_max_TB,c×N multi_PDSCH_max,c；
N TB_max,c为载波c能够支持的最大传输块的数目，N CBG_max_TB,c为载波c上每个传输块能够支持的最大码块组的数目，N multi_PDSCH_max,c为下行控制信息能够调度的载波c上的最大物理下行共享信道的数目。
在一些实施例中，所述至少两个子码书还包括：第二子码书；所述第二子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于码块组被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和码块组被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于多物理下行共享信道被调度。
在一些实施例中，所述第二子码书中针对一次下行调度的反馈信息的比特数为N max＝max c{N c}；载波c是能够产生第所述二子码书中反馈信息的载波；
对于使能了基于码块组传输的单物理下行共享信道载波c，N c＝N TB_max,c×N CBG_max_TB,c；对于没有使能基于码块组传输的多物理下行共享信道载波c，N c＝N TB_max,c×N multi_PDSCH_max,c；对于使能了基于码块组传输的多物理下行共享信道载波c，N c＝N TB_max,c×N CBG_max_TB,c×N multi_PDSCH_max,c；
N TB_max,c为载波c能够支持的最大传输块的数目，N CBG_max_TB,c为载波c上每个传输块能够支持的最大码块组的数目，N multi_PDSCH_max,c为下行控制信息能够调度的载波c上的最大物理下行共享信道的数目。
在一些实施例中，所述至少两个子码书还包括：第二子码书；所述第二子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于码块组被调度。
在一些实施例中，所述第二子码书中针对一次下行调度的反馈信息的比特数为N max＝max c{N TB_max,c×N CBG_max_TB,c}，载波c是能够产生所述第二子码书中反馈信息的载波，N TB_max,c为载波c能够支持的最大传输块的数目，N CBG_max_TB,c为载波c上每个传输块能够支持的最大码块组的数目。
在一些实施例中，所述至少两个子码书还包括：第三子码书；所述第三子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和码块组被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于多物理下行共享信道被调度。
在一些实施例中，所述第三子码书中针对一次下行调度的反馈信息的比特数为N max＝max c{N c}；载波c是能够产生所述第三子码书中反馈信息的载波；
对于没有使能基于码块组传输的多物理下行共享信道载波c，N c＝N TB_max,c×N multi_PDSCH_max,c；对于使能了基于码块组传输的多物理下行共享信道载波c，N c＝N TB_max,c×N CBG_max_TB,c×N multi_PDSCH_max,c；
N TB_max,c为载波c能够支持的最大传输块的数目，N CBG_max_TB,c为载波c上每个传输块能够支持的最大码块组的数目，N multi_PDSCH_max,c为下行控制信息能够调度的载波c上的最大物理下行共享信道的数目。
在一些实施例中，针对第一物理下行共享信道的反馈信息和针对第二物理下行共享信道的反馈信息在不同的子码书中，所述第一物理下行共享信道在多物理下行共享信道载波上被调度，所述第二物理下行共享信道在单物理下行共享信道载波上被调度。
在一些实施例中，所述子码书包括：
第一子码书；所述第一子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于传输块被调度；
第二子码书；所述第二子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于码块组被调度；
第三子码书；所述第三子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在多物理下行共享信道载波上被调度。
在一些实施例中，针对第三物理下行共享信道的反馈信息和针对第四物理下行共享信道的反馈信息在不同的子码书中，所述第三物理下行共享信道在多物理下行共享信道载波上基于传输块被调度，所述第二物理下行共享信道在多物理下行共享信道载波上基于码块组被调度。
在一些实施例中，，所述子码书包括：
第一子码书；所述第一子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于传输块被调度和/或，所述物理下行共享信道在多物理下行共享信道载波上基于传输块被调度；
第二子码书；所述第二子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于码块组被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于码块组被调度。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
值得注意的是，以上仅对与本申请相关的各部件或模块进行了说明，但本申请不限于此。反馈信息的发送装置1700还可以包括其他部件或者模块，关于这些部件或者模块的具体内容，可以参考相关技术。
此外，为了简单起见，图17中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
由上述实施例可知，对于使能了(enabled)multi-PDSCH调度的载波，基于是否使用multi-PDSCH调度和/或是否使用CBG传输等信息生成多个子码书；由此不仅能够支持基于multi-PDSCH的反馈，而且通过划分子码书，能够减小Type 2 HARQ-ACK码书的尺寸，降低HARQ-ACK的反馈开销。
第八方面的实施例
本申请实施例提供一种反馈信息的接收装置。该装置例如可以是网络设备，也可以 是配置于网络设备的某个或某些部件或者组件，与第六方面的实施例相同的内容不再赘述。
图18是本申请实施例的反馈信息的接收装置的一示意图。如图18所示，反馈信息的接收装置1800包括：
发送单元1801，其向终端设备发送下行控制信息；向所述终端设备发送物理下行共享信道；以及
接收单元1802，其接收所述终端设备针对所述物理下行共享信道的反馈信息。
在一些实施例中，针对多物理下行共享信道载波上的物理下行共享信道的反馈信息被包括在至少两个子码书中，其中一个子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和传输块被调度。
在一些实施例中，针对第一物理下行共享信道的反馈信息和针对第二物理下行共享信道的反馈信息在不同的子码书中，所述第一物理下行共享信道在多物理下行共享信道载波上被调度，所述第二物理下行共享信道在单物理下行共享信道载波上被调度。
在一些实施例中，针对第三物理下行共享信道的反馈信息和针对第四物理下行共享信道的反馈信息在不同的子码书中，所述第三物理下行共享信道在多物理下行共享信道载波上基于传输块被调度，所述第二物理下行共享信道在多物理下行共享信道载波上基于码块组被调度。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
值得注意的是，以上仅对与本申请相关的各部件或模块进行了说明，但本申请不限于此。反馈信息的接收装置1800还可以包括其他部件或者模块，关于这些部件或者模块的具体内容，可以参考相关技术。
此外，为了简单起见，图18中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
由上述实施例可知，对于使能了(enabled)multi-PDSCH调度的载波，基于是否使用multi-PDSCH调度和/或是否使用CBG传输等信息生成多个子码书；由此不仅能够支 持基于multi-PDSCH的反馈，而且通过划分子码书，能够减小Type 2 HARQ-ACK码书的尺寸，降低HARQ-ACK的反馈开销。
第九方面的实施例
本申请实施例还提供一种通信系统，可以参考图1，与第一方面至第八方面的实施例相同的内容不再赘述。
在一些实施例中，通信系统100至少可以包括：
网络设备101，向终端设备发送下行控制信息；向所述终端设备发送物理下行共享信道；以及接收所述终端设备针对所述物理下行共享信道的反馈信息；
终端设备102，其接收网络设备发送的所述下行控制信息，并根据所述下行控制信息接收所述网络设备发送的所述物理下行共享信道；以及向所述网络设备反馈针对所述物理下行共享信道的反馈信息；
其中，针对多物理下行共享信道载波上的物理下行共享信道的反馈信息被包括在至少两个子码书中，其中一个子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和传输块被调度。
在一些实施例中，通信系统100至少可以包括：
网络设备101，向终端设备发送下行控制信息；向所述终端设备发送物理下行共享信道；以及接收所述终端设备针对所述物理下行共享信道的反馈信息；
终端设备102，其接收网络设备发送的所述下行控制信息，并根据所述下行控制信息接收所述网络设备发送的所述物理下行共享信道；以及向所述网络设备反馈针对所述物理下行共享信道的反馈信息；
其中，针对第一物理下行共享信道的反馈信息和针对第二物理下行共享信道的反馈信息在不同的子码书中，所述第一物理下行共享信道在多物理下行共享信道载波上被调度，所述第二物理下行共享信道在单物理下行共享信道载波上被调度。
在一些实施例中，通信系统100至少可以包括：
网络设备101，向终端设备发送下行控制信息；向所述终端设备发送物理下行共享信道；以及接收所述终端设备针对所述物理下行共享信道的反馈信息；
终端设备102，其接收网络设备发送的所述下行控制信息，并根据所述下行控制信息接收所述网络设备发送的所述物理下行共享信道；以及向所述网络设备反馈针对所述物 理下行共享信道的反馈信息；
其中，针对第三物理下行共享信道的反馈信息和针对第四物理下行共享信道的反馈信息在不同的子码书中，所述第三物理下行共享信道在多物理下行共享信道载波上基于传输块被调度，所述第二物理下行共享信道在多物理下行共享信道载波上基于码块组被调度。
本申请实施例还提供一种网络设备，例如可以是基站，但本申请不限于此，还可以是其他的网络设备。
图19是本申请实施例的网络设备的构成示意图。如图19所示，网络设备1900可以包括：处理器1910(例如中央处理器CPU)和存储器1920；存储器1920耦合到处理器1910。其中该存储器1920可存储各种数据；此外还存储信息处理的程序1930，并且在处理器1910的控制下执行该程序1930。
例如，处理器1910可以被配置为执行程序而实现如第六方面的实施例所述的反馈信息的接收方法。例如处理器1910可以被配置为进行如下的控制：向终端设备发送下行控制信息；向所述终端设备发送物理下行共享信道；以及接收所述终端设备针对所述物理下行共享信道的反馈信息；
其中，针对多物理下行共享信道载波上的物理下行共享信道的反馈信息被包括在至少两个子码书中，其中一个子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和传输块被调度；
或者，针对第一物理下行共享信道的反馈信息和针对第二物理下行共享信道的反馈信息在不同的子码书中，所述第一物理下行共享信道在多物理下行共享信道载波上被调度，所述第二物理下行共享信道在单物理下行共享信道载波上被调度；
或者，针对第三物理下行共享信道的反馈信息和针对第四物理下行共享信道的反馈信息在不同的子码书中，所述第三物理下行共享信道在多物理下行共享信道载波上基于传输块被调度，所述第二物理下行共享信道在多物理下行共享信道载波上基于码块组被调度。
此外，如图19所示，网络设备1900还可以包括：收发机1940和天线1950等；其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，网络设备1900也并不是必须要包括图19中所示的所有部件；此外，网络设备1900还可以包括图19中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种终端设备，但本申请不限于此，还可以是其他的设备。
图20是本申请实施例的终端设备的示意图。如图20所示，该终端设备2000可以包括处理器2010和存储器2020；存储器2020存储有数据和程序，并耦合到处理器2010。值得注意的是，该图是示例性的；还可以使用其他类型的结构，来补充或代替该结构，以实现电信功能或其他功能。
例如，处理器2010可以被配置为执行程序而实现如第一至五方面的实施例所述的反馈信息的发送方法。例如处理器2010可以被配置为进行如下的控制：接收网络设备发送的下行控制信息，并根据所述下行控制信息接收所述网络设备发送的物理下行共享信道；以及向所述网络设备反馈针对所述物理下行共享信道的反馈信息；
其中，针对多物理下行共享信道载波上的物理下行共享信道的反馈信息被包括在至少两个子码书中，其中一个子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和传输块被调度；
或者，针对第一物理下行共享信道的反馈信息和针对第二物理下行共享信道的反馈信息在不同的子码书中，所述第一物理下行共享信道在多物理下行共享信道载波上被调度，所述第二物理下行共享信道在单物理下行共享信道载波上被调度；
或者，针对第三物理下行共享信道的反馈信息和针对第四物理下行共享信道的反馈信息在不同的子码书中，所述第三物理下行共享信道在多物理下行共享信道载波上基于传输块被调度，所述第二物理下行共享信道在多物理下行共享信道载波上基于码块组被调度。
如图20所示，该终端设备2000还可以包括：通信模块2030、输入单元2040、显示器2050、电源2060。其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，终端设备2000也并不是必须要包括图20中所示的所有部件，上述部件并不是必需的；此外，终端设备2000还可以包括图20中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种计算机程序，其中当在终端设备中执行所述程序时，所述程序使得所述终端设备执行第一至五方面的实施例所述的反馈信息的发送方法。
本申请实施例还提供一种存储有计算机程序的存储介质，其中所述计算机程序使得终端设备执行第一至五方面的实施例所述的反馈信息的发送方法。
本申请实施例还提供一种计算机程序，其中当在网络设备中执行所述程序时，所述 程序使得所述网络设备执行第六方面的实施例所述的反馈信息的接收方法。
本申请实施例还提供一种存储有计算机程序的存储介质，其中所述计算机程序使得网络设备执行第六方面的实施例所述的反馈信息的接收方法。
本申请以上的装置和方法可以由硬件实现，也可以由硬件结合软件实现。本申请涉及这样的计算机可读程序，当该程序被逻辑部件所执行时，能够使该逻辑部件实现上文所述的装置或构成部件，或使该逻辑部件实现上文所述的各种方法或步骤。本申请还涉及用于存储以上程序的存储介质，如硬盘、磁盘、光盘、DVD、flash存储器等。
结合本申请实施例描述的方法/装置可直接体现为硬件、由处理器执行的软件模块或二者组合。例如，图中所示的功能框图中的一个或多个和/或功能框图的一个或多个组合，既可以对应于计算机程序流程的各个软件模块，亦可以对应于各个硬件模块。这些软件模块，可以分别对应于图中所示的各个步骤。这些硬件模块例如可利用现场可编程门阵列(FPGA)将这些软件模块固化而实现。
软件模块可以位于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动磁盘、CD-ROM或者本领域已知的任何其它形式的存储介质。可以将一种存储介质耦接至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息；或者该存储介质可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。该软件模块可以存储在移动终端的存储器中，也可以存储在可插入移动终端的存储卡中。例如，若设备(如移动终端)采用的是较大容量的MEGA-SIM卡或者大容量的闪存装置，则该软件模块可存储在该MEGA-SIM卡或者大容量的闪存装置中。
针对附图中描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，可以实现为用于执行本申请所描述功能的通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件或者其任意适当组合。针对附图描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，还可以实现为计算设备的组合，例如，DSP和微处理器的组合、多个微处理器、与DSP通信结合的一个或多个微处理器或者任何其它这种配置。
以上结合具体的实施方式对本申请进行了描述，但本领域技术人员应该清楚，这些描述都是示例性的，并不是对本申请保护范围的限制。本领域技术人员可以根据本申请 的精神和原理对本申请做出各种变型和修改，这些变型和修改也在本申请的范围内。
关于包括以上实施例的实施方式，还公开下述的附记：
附记1.一种反馈信息的发送方法，包括：
终端设备接收网络设备发送的下行控制信息(DCI)，
根据所述下行控制信息接收所述网络设备发送的物理下行共享信道(PDSCH)；以及
向所述网络设备反馈针对所述物理下行共享信道的反馈信息；
其中，针对多物理下行共享信道(multi-PDSCH)载波上的物理下行共享信道的反馈信息被包括在至少两个子码书中，其中一个子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道(single-PDSCH)和传输块(TB)被调度。
附记2.根据附记1所述的方法，其中，第一下行控制信息被用于基于多物理下行共享信道(multi-PDSCH)进行调度，第二下行控制信息被用于基于单物理下行共享信道(single-PDSCH)进行调度；所述第一下行控制信息和所述第二下行控制信息的下行控制信息(DCI)格式不同。
附记3.根据附记1或2所述的方法，其中，所述至少两个子码书包括：第一子码书；所述第一子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于传输块被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和传输块被调度。
附记4.根据附记3所述的方法，其中，所述第一子码书包括针对单物理下行共享信道载波和/或多物理下行共享信道载波上的如下至少之一的反馈信息：半持续调度物理下行共享信道释放(SPS PDSCH release)、半持续调度物理下行共享信道(SPS PDSCH reception)、指示辅小区休眠的下行控制信息(DCI indicating SCell dormancy)。
附记5.根据附记3或4所述的方法，其中，所述第一子码书中针对一次下行调度的反馈信息的比特数为N max＝max c{N TB_max,c}，载波c是能够产生所述第一子码书中反馈信息的载波，N TB_max,c为载波c能够支持的最大传输块(TB)的数目。
附记6.根据附记3至5任一项所述的方法，其中，所述至少两个子码书还包括：第二子码书；所述第二子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于码块组(CBG)被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和码块组 (CBG)被调度。
附记7.根据附记6所述的方法，其中，所述第二子码书中针对一次下行调度的反馈信息的比特数为N max＝max c{N TB_max,c×N CBG_max_TB,c}，载波c是能够产生所述第二子码书中反馈信息的载波，N TB_max,c为载波c能够支持的最大传输块(TB)的数目，N CBG_max_TB,c为载波c上每个传输块(TB)能够支持的最大码块组(CBG)的数目。
附记8.根据附记3至7任一项所述的方法，其中，所述至少两个子码书还包括：第三子码书；所述第三子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在多物理下行共享信道载波上基于多物理下行共享信道被调度。
附记9.根据附记8所述的方法，其中，所述第三子码书中针对一次下行调度的反馈信息的比特数为N max＝max c{N c}；载波c是能够产生所述第三子码书中反馈信息的载波；
对于没有被使能基于码块组传输的载波c，N c＝N TB_max,c×N multi_PDSCH_max,c；对于使能了基于码块组传输的载波c，N c＝N TB_max,c×N CBG_max_TB,c×N multi_PDSCH_max,c；
N TB_max,c为载波c能够支持的最大传输块(TB)的数目，N CBG_max_TB,c为载波c上每个传输块(TB)能够支持的最大码块组(CBG)的数目，N multi_PDSCH_max,c为下行控制信息(DCI)能够调度的载波c上的最大物理下行共享信道的数目。
附记10.根据附记3至5任一项所述的方法，其中，所述至少两个子码书还包括：第二子码书；所述第二子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于码块组(CBG)被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和码块组(CBG)被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于多物理下行共享信道被调度。
附记11.根据附记10所述的方法，其中，所述第二子码书中针对一次下行调度的反馈信息的比特数为N max＝max c{N c}；载波c是能够产生第所述二子码书中反馈信息的载波；
对于使能了基于码块组传输的单物理下行共享信道载波c，N c＝N TB_max,c×N CBG_max_TB,c；对于没有使能基于码块组传输的多物理下行共享信道载波c， N c＝N TB_max,c×N multi_PDSCH_max,c；对于使能了基于码块组传输的多物理下行共享信道载波c，N c＝N TB_max,c×N CBG_max_TB,c×N multi_PDSCH_max,c；
N TB_max,c为载波c能够支持的最大传输块(TB)的数目，N CBG_max_TB,c为载波c上每个传输块(TB)能够支持的最大码块组(CBG)的数目，N multi_PDSCH_max,c为下行控制信息(DCI)能够调度的载波c上的最大物理下行共享信道的数目。
附记12.根据附记3至5任一项所述的方法，其中，所述至少两个子码书还包括：第二子码书；所述第二子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于码块组(CBG)被调度。
附记13.根据附记12所述的方法，其中，所述第二子码书中针对一次下行调度的反馈信息的比特数为N max＝max c{N TB_max,c×N CBG_max_TB,c}，载波c是能够产生所述第二子码书中反馈信息的载波，N TB_max,c为载波c能够支持的最大传输块(TB)的数目，N CBG_max_TB,c为载波c上每个传输块(TB)能够支持的最大码块组(CBG)的数目。
附记14.根据附记12或13所述的方法，其中，所述至少两个子码书还包括：第三子码书；所述第三子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和码块组(CBG)被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于多物理下行共享信道被调度。
附记15.根据附记14所述的方法，其中，所述第三子码书中针对一次下行调度的反馈信息的比特数为N max＝max c{N c}；载波c是能够产生所述第三子码书中反馈信息的载波；
对于没有使能基于码块组传输的多物理下行共享信道载波c，N c＝N TB_max,c×N multi_PDSCH_max,c；对于使能了基于码块组传输的多物理下行共享信道载波c，N c＝N TB_max,c×N CBG_max_TB,c×N multi_PDSCH_max,c；
N TB_max,c为载波c能够支持的最大传输块(TB)的数目，N CBG_max_TB,c为载波c上每个传输块(TB)能够支持的最大码块组(CBG)的数目，N multi_PDSCH_max,c为下行控制信息(DCI)能够调度的载波c上的最大物理下行共享信道的数目。
附记16.一种反馈信息的发送方法，包括：
终端设备接收网络设备发送的下行控制信息(DCI)，
根据所述下行控制信息接收所述网络设备发送的物理下行共享信道(PDSCH)；以及
向所述网络设备反馈针对所述物理下行共享信道的反馈信息；
其中，针对第一物理下行共享信道的反馈信息和针对第二物理下行共享信道的反馈信息在不同的子码书中，所述第一物理下行共享信道在多物理下行共享信道(multi-PDSCH)载波上被调度，所述第二物理下行共享信道在单物理下行共享信道(single-PDSCH)载波上被调度。
附记17.根据附记16所述的方法，其中，所述子码书包括：
第一子码书；所述第一子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于传输块(TB)被调度；
第二子码书；所述第二子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于码块组(CBG)被调度；
第三子码书；所述第三子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在多物理下行共享信道载波上被调度。
附记18.一种反馈信息的发送方法，包括：
终端设备接收网络设备发送的下行控制信息(DCI)，
根据所述下行控制信息接收所述网络设备发送的物理下行共享信道(PDSCH)；以及
向所述网络设备反馈针对所述物理下行共享信道的反馈信息；
其中，针对第三物理下行共享信道的反馈信息和针对第四物理下行共享信道的反馈信息在不同的子码书中，所述第三物理下行共享信道在多物理下行共享信道(multi-PDSCH)载波上基于传输块(TB)被调度，所述第二物理下行共享信道在多物理下行共享信道(multi-PDSCH)载波上基于码块组(CBG)被调度。
附记19.根据附记18所述的方法，其中，所述子码书包括：
第一子码书；所述第一子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于传输块(TB)被调度和/或，所述物理下行共享信道在多物理下行共享信道载波上基于传输块(TB)被调度；
第二子码书；所述第二子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于码块组(CBG)被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于码块组(CBG)被调度。
附记20.一种反馈信息的接收方法，包括：
网络设备向终端设备发送下行控制信息(DCI)；
向所述终端设备发送物理下行共享信道(PDSCH)；以及
接收所述终端设备针对所述物理下行共享信道的反馈信息；
其中，针对多物理下行共享信道载波上的物理下行共享信道的反馈信息被包括在至少两个子码书中，其中一个子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和传输块被调度。
附记21.一种反馈信息的接收方法，包括：
网络设备向终端设备发送下行控制信息(DCI)；
向所述终端设备发送物理下行共享信道(PDSCH)；以及
接收所述终端设备针对所述物理下行共享信道的反馈信息；
其中，针对第一物理下行共享信道的反馈信息和针对第二物理下行共享信道的反馈信息在不同的子码书中，所述第一物理下行共享信道在多物理下行共享信道(multi-PDSCH)载波上被调度，所述第二物理下行共享信道在单物理下行共享信道(single-PDSCH)载波上被调度。
附记22.一种反馈信息的接收方法，包括：
网络设备向终端设备发送下行控制信息(DCI)；
向所述终端设备发送物理下行共享信道(PDSCH)；以及
接收所述终端设备针对所述物理下行共享信道的反馈信息；
其中，针对第三物理下行共享信道的反馈信息和针对第四物理下行共享信道的反馈信息在不同的子码书中，所述第三物理下行共享信道在多物理下行共享信道(multi-PDSCH)载波上基于传输块(TB)被调度，所述第二物理下行共享信道在多物理下行共享信道(multi-PDSCH)载波上基于码块组(CBG)被调度。
附记23.一种终端设备，包括存储器和处理器，所述存储器存储有计算机程序，所述处理器被配置为执行所述计算机程序而实现如附记1至19任一项所述的反馈信息的发送方法。
附记24.一种网络设备，包括存储器和处理器，所述存储器存储有计算机程序，所述处理器被配置为执行所述计算机程序而实现如附记20至22任一项所述的反馈信息的接收方法。
附记25.一种通信系统，包括：
网络设备，向终端设备发送下行控制信息；向所述终端设备发送物理下行共享信道；以及接收所述终端设备针对所述物理下行共享信道的反馈信息；
终端设备，其接收网络设备发送的所述下行控制信息，并根据所述下行控制信息接收所述网络设备发送的所述物理下行共享信道；以及向所述网络设备反馈针对所述物理下行共享信道的反馈信息；
其中，针对多物理下行共享信道载波上的物理下行共享信道的反馈信息被包括在至少两个子码书中，其中一个子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和传输块被调度。
附记26.一种通信系统，包括：
网络设备，向终端设备发送下行控制信息；向所述终端设备发送物理下行共享信道；以及接收所述终端设备针对所述物理下行共享信道的反馈信息；
终端设备，其接收网络设备发送的所述下行控制信息，并根据所述下行控制信息接收所述网络设备发送的所述物理下行共享信道；以及向所述网络设备反馈针对所述物理下行共享信道的反馈信息；
其中，针对第一物理下行共享信道的反馈信息和针对第二物理下行共享信道的反馈信息在不同的子码书中，所述第一物理下行共享信道在多物理下行共享信道载波上被调度，所述第二物理下行共享信道在单物理下行共享信道载波上被调度。
附记27.一种通信系统，包括：
网络设备，向终端设备发送下行控制信息；向所述终端设备发送物理下行共享信道；以及接收所述终端设备针对所述物理下行共享信道的反馈信息；
终端设备，其接收网络设备发送的所述下行控制信息，并根据所述下行控制信息接收所述网络设备发送的所述物理下行共享信道；以及向所述网络设备反馈针对所述物理下行共享信道的反馈信息；
其中，针对第三物理下行共享信道的反馈信息和针对第四物理下行共享信道的反馈信息在不同的子码书中，所述第三物理下行共享信道在多物理下行共享信道载波上基于传输块被调度，所述第二物理下行共享信道在多物理下行共享信道载波上基于码块组被调度。

Claims (17)

  1. 一种反馈信息的发送装置，包括：
    接收单元，其接收网络设备发送的下行控制信息，并根据所述下行控制信息接收所述网络设备发送的物理下行共享信道；以及
    发送单元，其向所述网络设备反馈针对所述物理下行共享信道的反馈信息；
    其中，针对多物理下行共享信道载波上的物理下行共享信道的反馈信息被包括在至少两个子码书中，其中一个子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和传输块被调度。
  2. 根据权利要求1所述的装置，其中，第一下行控制信息被用于基于多物理下行共享信道进行调度，第二下行控制信息被用于基于单物理下行共享信道进行调度；所述第一下行控制信息和所述第二下行控制信息的下行控制信息格式不同。
  3. 根据权利要求1所述的装置，其中，所述至少两个子码书包括：第一子码书；所述第一子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于传输块被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和传输块被调度。
  4. 根据权利要求3所述的装置，其中，所述第一子码书包括针对单物理下行共享信道载波和/或多物理下行共享信道载波上的如下至少之一的反馈信息：半持续调度物理下行共享信道释放、半持续调度物理下行共享信道、指示辅小区休眠的下行控制信息。
  5. 根据权利要求3所述的装置，其中，所述第一子码书中针对一次下行调度的反馈信息的比特数为N max＝max c{N TB_max,c}，载波c是能够产生所述第一子码书中反馈信息的载波，N TB_max,c为载波c能够支持的最大传输块的数目。
  6. 根据权利要求3所述的装置，其中，所述至少两个子码书还包括：第二子码书；所述第二子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于码块组被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和码块组被调度。
  7. 根据权利要求6所述的装置，其中，所述第二子码书中针对一次下行调度的反馈信息的比特数为N max＝max c{N TB_max,c×N CBG_max_TB,c}，载波c是能够产生所述第二 子码书中反馈信息的载波，N TB_max,c为载波c能够支持的最大传输块的数目，N CBG_max_TB,c为载波c上每个传输块能够支持的最大码块组的数目。
  8. 根据权利要求6所述的装置，其中，所述至少两个子码书还包括：第三子码书；所述第三子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在多物理下行共享信道载波上基于多物理下行共享信道被调度。
  9. 根据权利要求8所述的装置，其中，所述第三子码书中针对一次下行调度的反馈信息的比特数为N max＝max c{N c}；载波c是能够产生所述第三子码书中反馈信息的载波；
    对于没有被使能基于码块组传输的载波c，N c＝N TB_max,c×N multi_PDSCH_max,c；对于使能了基于码块组传输的载波c，N c＝N TB_max,c×N CBG_max_TB,c×N multi_PDSCH_max,c；
    N TB_max,c为载波c能够支持的最大传输块的数目，N CBG_max_TB,c为载波c上每个传输块能够支持的最大码块组的数目，N multi_PDSCH_max,c为下行控制信息能够调度的载波c上的最大物理下行共享信道的数目。
  10. 根据权利要求3所述的装置，其中，所述至少两个子码书还包括：第二子码书；所述第二子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于码块组被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和码块组被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于多物理下行共享信道被调度。
  11. 根据权利要求10所述的装置，其中，所述第二子码书中针对一次下行调度的反馈信息的比特数为N max＝max c{N c}；载波c是能够产生第所述二子码书中反馈信息的载波；
    对于使能了基于码块组传输的单物理下行共享信道载波c，N c＝N TB_max,c×N CBG_max_TB,c；对于没有使能基于码块组传输的多物理下行共享信道载波c，N c＝N TB_max,c×N multi_PDSCH_max,c；对于使能了基于码块组传输的多物理下行共享信道载波c，N c＝N TB_max,c×N CBG_max_TB,c×N multi_PDSCH_max,c；
    N TB_max,c为载波c能够支持的最大传输块的数目，N CBG_max_TB,c为载波c上每个传 输块能够支持的最大码块组的数目，N multi_PDSCH_max,c为下行控制信息能够调度的载波c上的最大物理下行共享信道的数目。
  12. 根据权利要求3所述的装置，其中，所述至少两个子码书还包括：第二子码书；所述第二子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在单物理下行共享信道载波上基于码块组被调度。
  13. 根据权利要求12所述的装置，其中，所述第二子码书中针对一次下行调度的反馈信息的比特数为N max＝max c{N TB_max,c×N CBG_max_TB,c}，载波c是能够产生所述第二子码书中反馈信息的载波，N TB_max,c为载波c能够支持的最大传输块的数目，N CBG_max_TB,c为载波c上每个传输块能够支持的最大码块组的数目。
  14. 根据权利要求12所述的装置，其中，所述至少两个子码书还包括：第三子码书；所述第三子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和码块组被调度，和/或，所述物理下行共享信道在多物理下行共享信道载波上基于多物理下行共享信道被调度。
  15. 根据权利要求14所述的装置，其中，所述第三子码书中针对一次下行调度的反馈信息的比特数为N max＝max c{N c}；载波c是能够产生所述第三子码书中反馈信息的载波；
    对于没有使能基于码块组传输的多物理下行共享信道载波c，N c＝N TB_max,c×N multi_PDSCH_max,c；对于使能了基于码块组传输的多物理下行共享信道载波c，N c＝N TB_max,c×N CBG_max_TB,c×N multi_PDSCH_max,c；
    N TB_max,c为载波c能够支持的最大传输块的数目，N CBG_max_TB,c为载波c上每个传输块能够支持的最大码块组的数目，N multi_PDSCH_max,c为下行控制信息能够调度的载波c上的最大物理下行共享信道的数目。
  16. 一种反馈信息的接收装置，包括：
    发送单元，其向终端设备发送下行控制信息；向所述终端设备发送物理下行共享信道；以及
    接收单元，其接收所述终端设备针对所述物理下行共享信道的反馈信息；
    其中，针对多物理下行共享信道载波上的物理下行共享信道的反馈信息被包括在至 少两个子码书中，其中一个子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和传输块被调度。
  17. 一种通信系统，包括：
    网络设备，向终端设备发送下行控制信息；向所述终端设备发送物理下行共享信道；以及接收所述终端设备针对所述物理下行共享信道的反馈信息；
    终端设备，其接收所述网络设备发送的所述下行控制信息，并根据所述下行控制信息接收所述网络设备发送的所述物理下行共享信道；以及向所述网络设备反馈针对所述物理下行共享信道的反馈信息；
    其中，针对多物理下行共享信道载波上的物理下行共享信道的反馈信息被包括在至少两个子码书中，其中一个子码书中包括针对如下物理下行共享信道的反馈信息：所述物理下行共享信道在多物理下行共享信道载波上基于单物理下行共享信道和传输块被调度。
PCT/CN2020/121236 2020-10-15 2020-10-15 反馈信息的发送和接收方法以及装置 WO2022077367A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
KR1020237011832A KR20230065311A (ko) 2020-10-15 2020-10-15 피드백 정보 송신 방법 및 장치와 피드백 정보 수신 방법 및 장치
CN202080104979.0A CN116114193B (zh) 2020-10-15 2020-10-15 反馈信息的发送和接收方法以及装置
JP2023521053A JP2023545705A (ja) 2020-10-15 2020-10-15 フィードバック情報の送受信方法及び装置
PCT/CN2020/121236 WO2022077367A1 (zh) 2020-10-15 2020-10-15 反馈信息的发送和接收方法以及装置
EP20957146.2A EP4231753A4 (en) 2020-10-15 2020-10-15 METHOD AND APPARATUS FOR SENDING FEEDBACK INFORMATION AND METHOD AND APPARATUS FOR RECEIVING FEEDBACK INFORMATION
US18/125,235 US20230232411A1 (en) 2020-10-15 2023-03-23 Feedback information transmitting method and apparatus and feedback information receiving method and apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/121236 WO2022077367A1 (zh) 2020-10-15 2020-10-15 反馈信息的发送和接收方法以及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/125,235 Continuation US20230232411A1 (en) 2020-10-15 2023-03-23 Feedback information transmitting method and apparatus and feedback information receiving method and apparatus

Publications (1)

Publication Number Publication Date
WO2022077367A1 true WO2022077367A1 (zh) 2022-04-21

Family

ID=81208693

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/121236 WO2022077367A1 (zh) 2020-10-15 2020-10-15 反馈信息的发送和接收方法以及装置

Country Status (6)

Country Link
US (1) US20230232411A1 (zh)
EP (1) EP4231753A4 (zh)
JP (1) JP2023545705A (zh)
KR (1) KR20230065311A (zh)
CN (1) CN116114193B (zh)
WO (1) WO2022077367A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180324845A1 (en) * 2017-05-04 2018-11-08 At&T Intellectual Property I, L.P. Facilitating incremental downlink control information design to support downlink control information scheduling
CN110574319A (zh) * 2017-05-03 2019-12-13 Idac控股公司 用于在受到低时延业务量影响时提升增强移动宽带(eMBB)的混合自动重复请求(HARQ)反馈性能的方法和装置
WO2020141994A1 (en) * 2019-01-03 2020-07-09 Telefonaktiebolaget Lm Ericsson (Publ) Harq handling for single-dci multi-slot scheduling

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110086583B (zh) * 2018-01-26 2021-05-07 电信科学技术研究院有限公司 一种dai的指示方法、用户终端和网络侧设备
CN110351018B (zh) * 2018-04-04 2021-12-24 展讯通信（上海）有限公司 Harq-ack反馈信息发送、接收方法及装置、存储介质、发送终端、接收终端
CN110830174B (zh) * 2018-08-10 2020-11-27 北京紫光展锐通信技术有限公司 半静态harq-ack码本的生成方法、用户终端、可读存储介质
US12127192B2 (en) * 2019-03-29 2024-10-22 Lg Electronics Inc. Method and apparatus for transmitting or receiving wireless signals in wireless communication system
CN111277388B (zh) * 2019-11-07 2022-01-28 维沃移动通信有限公司 Harq-ack码本生成方法、信息发送方法及设备
CN113543348B (zh) * 2020-04-15 2024-08-16 大唐移动通信设备有限公司 一种harq-ack传输方法、终端及网络侧设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110574319A (zh) * 2017-05-03 2019-12-13 Idac控股公司 用于在受到低时延业务量影响时提升增强移动宽带(eMBB)的混合自动重复请求(HARQ)反馈性能的方法和装置
US20180324845A1 (en) * 2017-05-04 2018-11-08 At&T Intellectual Property I, L.P. Facilitating incremental downlink control information design to support downlink control information scheduling
WO2020141994A1 (en) * 2019-01-03 2020-07-09 Telefonaktiebolaget Lm Ericsson (Publ) Harq handling for single-dci multi-slot scheduling

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
PANASONIC: "HARQ enhancement for NR-U", 3GPP DRAFT; R1-1906263 NR-U HARQ, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Reno, US; 20190513 - 20190517, 3 May 2019 (2019-05-03), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051708301 *
See also references of EP4231753A4 *

Also Published As

Publication number Publication date
CN116114193A (zh) 2023-05-12
KR20230065311A (ko) 2023-05-11
CN116114193B (zh) 2024-09-17
US20230232411A1 (en) 2023-07-20
JP2023545705A (ja) 2023-10-31
EP4231753A4 (en) 2023-11-29
EP4231753A1 (en) 2023-08-23

Similar Documents

Publication Publication Date Title
US10812243B2 (en) Feedback information transmission and reception method and apparatus and communication system
CN109150456B (zh) 一种无线通信方法和设备
JP7093856B2 (ja) フィードバック情報の伝送方法及び装置
JP7371761B2 (ja) 信号送信方法、装置及びシステム
EP3905573A1 (en) Communication method, communication apparatus, and storage medium
US11832236B2 (en) Resource configuration method, resource determination method, apparatuses thereof and communication system
WO2019028767A1 (zh) 分配和接收频域资源的方法、装置及通信系统
US11013018B2 (en) Data multiplexing apparatus and method and communication system
JP2023520705A (ja) データ送信方法、装置及び通信システム
WO2020142987A1 (zh) 边链路信息的发送和接收方法以及装置
WO2022077410A1 (zh) 信息反馈方法以及装置
WO2021088260A1 (zh) 传输反馈信息的方法、终端设备和网络设备
WO2018223399A1 (zh) 无线通信方法和设备
WO2018141091A1 (zh) 发送信息的方法、接收信息的方法和装置
WO2022077367A1 (zh) 反馈信息的发送和接收方法以及装置
WO2022032515A1 (zh) 无线通信方法、终端设备和网络设备
JP2023544762A (ja) データ受信方法及び装置
WO2019028775A1 (zh) 反馈信息的发送和接收方法、装置及通信系统
WO2023151048A1 (zh) 信息反馈方法以及装置
WO2024031696A1 (zh) 信道状态信息的上报方法和装置
WO2022198421A1 (zh) 一种信息传输方法、电子设备及存储介质
WO2023206306A1 (zh) 数据接收方法、数据发送方法以及装置
WO2023150985A1 (zh) 信息反馈方法、信息接收方法以及装置
WO2022213293A1 (zh) 随机接入前导序列的发送和配置方法以及装置
WO2023093531A1 (zh) 一种通信方法及装置

Legal Events

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

Ref document number: 20957146

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202337023728

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2023521053

Country of ref document: JP

ENP Entry into the national phase

Ref document number: 20237011832

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020957146

Country of ref document: EP

Effective date: 20230515