WO2024011453A1 - Procédé, dispositif et support de stockage informatique de communication - Google Patents

Procédé, dispositif et support de stockage informatique de communication Download PDF

Info

Publication number
WO2024011453A1
WO2024011453A1 PCT/CN2022/105483 CN2022105483W WO2024011453A1 WO 2024011453 A1 WO2024011453 A1 WO 2024011453A1 CN 2022105483 W CN2022105483 W CN 2022105483W WO 2024011453 A1 WO2024011453 A1 WO 2024011453A1
Authority
WO
WIPO (PCT)
Prior art keywords
transmissions
dci
sps
harq
pdsch
Prior art date
Application number
PCT/CN2022/105483
Other languages
English (en)
Inventor
Xiaohong Zhang
Lin Liang
Gang Wang
Original Assignee
Nec Corporation
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 Nec Corporation filed Critical Nec Corporation
Priority to PCT/CN2022/105483 priority Critical patent/WO2024011453A1/fr
Publication of WO2024011453A1 publication Critical patent/WO2024011453A1/fr

Links

Images

Classifications

    • 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
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/11—Semi-persistent scheduling
    • 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

Definitions

  • Embodiments of the present disclosure generally relate to the field of telecommunication, and in particular, to methods, devices and computer storage media of communication.
  • SPS PDSCH semi-persistent scheduling physical downlink shared channel
  • CG PUSCH configured grant physical uplink shared channel
  • embodiments of the present disclosure provide methods, devices and computer storage media of communication for a scheme for multi-TB transmission per SPS/CG periodicity.
  • a method of communication comprises: transmitting to a terminal device or receiving from the terminal device, at a network device, N transmissions for a set of different transport blocks (TBs) in a period for a semi-persistent scheduling (SPS) configuration or a configured grant (CG) configuration, wherein N>1; and in accordance with failure of M transmissions among the N transmissions in the period, transmitting, to the terminal device, downlink control information (DCI) in a physical downlink control channel (PDCCH) with CRC scrambled by CS-RNTI for scheduling retransmissions of the M transmissions, wherein 1 ⁇ M ⁇ N.
  • DCI downlink control information
  • PDCCH physical downlink control channel
  • a method of communication comprises: transmitting, at a network device and to a terminal device, a plurality of semi-persistent scheduling physical downlink shared channel (SPS PDSCH) transmissions in a period for a SPS configuration; receiving, from the terminal device, a hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook in a physical uplink control channel (PUCCH) , the HARQ-ACK codebook comprising HARQ-ACK for the plurality of SPS PDSCH transmissions; and in accordance with a determination that HARQ-ACK for the plurality of SPS PDSCH transmissions is multiplexed with HARQ-ACK for at least one dynamic scheduled PDSCH transmission in the PUCCH, determining HARQ-ACK positions for the plurality of SPS PDSCH transmissions in the HARQ-ACK codebook.
  • SPS PDSCH semi-persistent scheduling physical downlink shared channel
  • a method of communication comprises: receiving from a network device or transmitting to the network device, at a terminal device, N transmissions for a set of different transport blocks (TBs) in a period for a semi-persistent scheduling (SPS) configuration or a configured grant (CG) configuration, wherein N>1; receiving, from the network device, downlink control information (DCI) in a physical downlink control channel (PDCCH) with CRC scrambled by CS-RNTI for scheduling retransmissions of M transmissions among N transmissions in the period, wherein 1 ⁇ M ⁇ N; and determining hybrid automatic repeat request (HARQ) process numbers of the M transmissions based on the DCI.
  • DCI downlink control information
  • PDCCH physical downlink control channel
  • HARQ hybrid automatic repeat request
  • the method comprises: receiving, at a terminal device and from a network device, a plurality of semi-persistent scheduling physical downlink shared channel (SPS PDSCH) transmissions in a period for a SPS configuration; in accordance with a determination that HARQ-ACK for the plurality of SPS PDSCH transmissions is multiplexed with HARQ-ACK for at least one dynamic scheduled data transmissions in a physical uplink control channel (PUCCH) , determining a HARQ-ACK codebook comprising HARQ-ACK for the plurality of SPS PDSCH transmissions and HARQ-ACK for the at least one dynamic scheduled PDSCH transmission; and transmitting the HARQ-ACK codebook to a network device in the PUCCH.
  • SPS PDSCH semi-persistent scheduling physical downlink shared channel
  • a network device comprising a processor and a memory coupled to the processor and storing instructions thereon.
  • the instructions when executed by the processor, cause the network device to perform the method according to the third or fourth aspect of the present disclosure.
  • a terminal device comprising a processor and a memory coupled to the processor and storing instructions thereon.
  • the instructions when executed by the processor, cause the terminal device to perform the method according to the first or second aspect of the present disclosure.
  • a computer readable medium having instructions stored thereon.
  • the instructions when executed on at least one processor, cause the at least one processor to perform the method according to the first or second aspect of the present disclosure or the method according to the third or fourth aspect of the present disclosure.
  • FIG. 1 illustrates a schematic diagram of an example communication network in which some embodiments of the present disclosure can be implemented
  • FIG. 2 illustrates a signaling flow for communications in an example scenario with a SPS configuration
  • FIG. 3A illustrates a simplified block diagram of an example construction of a type-1 HARQ-ACK codebook for DG PDSCH in a related solution
  • FIG. 3B illustrates a simplified block diagram of an example scenario where HARQ-ACK for multi-SPS PDSCHs and HARQ-ACK for DG PDSCH are multiplexed in a PUCCH;
  • FIG. 4 illustrate a signaling flow for communications according to some embodiments of the present disclosure
  • FIG. 5A illustrates a simplified block diagram of an example scenario where HARQ-ACK for multi-SPS PDSCHs and HARQ-ACK for DG PDSCH are multiplexed;
  • FIGs. 5B and 5C illustrate simplified block diagrams of HARQ-ACK codebooks in the scenario of FIG. 5A according to some embodiments of the present disclosure
  • FIG. 6 illustrate a signaling flow for communications according to some embodiments of the present disclosure
  • FIGs. 7A-7E illustrate simplified block diagrams of scheduling retransmissions of multiple SPS PDSCHs in a period by a single DCI according to some embodiments of the present disclosure
  • FIG. 8 illustrate a signaling flow for communications according to some embodiments of the present disclosure
  • FIG. 9 illustrates a simplified block diagram of scheduling retransmissions of multiple CG PUSCHs in a period by a single DCI according to some embodiments of the present disclosure
  • FIG. 10 illustrates an example method of communication implemented at a network device in accordance with some embodiments of the present disclosure
  • FIG. 11 illustrates another example method of communication implemented at a network device in accordance with some embodiments of the present disclosure.
  • FIG. 12 illustrates an example method of communication implemented at a terminal device in accordance with some embodiments of the present disclosure
  • FIG. 13 illustrates another example method of communication implemented at a terminal device in accordance with some embodiments of the present disclosure
  • FIG. 14 is a simplified block diagram of a device that is suitable for implementing embodiments of the present disclosure.
  • terminal device refers to any device having wireless or wired communication capabilities.
  • the terminal device include, but not limited to, user equipment (UE) , personal computers, desktops, mobile phones, cellular phones, smart phones, personal digital assistants (PDAs) , portable computers, tablets, wearable devices, internet of things (IoT) devices, Ultra-reliable and Low Latency Communications (URLLC) devices, Internet of Everything (IoE) devices, machine type communication (MTC) devices, device on vehicle for V2X communication where X means pedestrian, vehicle, or infrastructure/network, devices for Integrated Access and Backhaul (IAB) , Small Data Transmission (SDT) , mobility, Multicast and Broadcast Services (MBS) , positioning, dynamic/flexible duplex in commercial networks, reduced capability (RedCap) , Space borne vehicles or Air borne vehicles in Non-terrestrial networks (NTN) including Satellites and High Altitude Platforms (HAPs) encompassing Unmanned Aircraft Systems (UAS) , eX
  • UE user equipment
  • the ‘terminal device’ can further has ‘multicast/broadcast’ feature, to support public safety and mission critical, V2X applications, transparent IPv4/IPv6 multicast delivery, IPTV, smart TV, radio services, software delivery over wireless, group communications and IoT applications. It may also incorporate one or multiple Subscriber Identity Module (SIM) as known as Multi-SIM.
  • SIM Subscriber Identity Module
  • the term “terminal device” can be used interchangeably with a UE, a mobile station, a subscriber station, a mobile terminal, a user terminal or a wireless device.
  • network device refers to a device which is capable of providing or hosting a cell or coverage where terminal devices can communicate.
  • a network device include, but not limited to, a Node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a next generation NodeB (gNB) , a transmission reception point (TRP) , a remote radio unit (RRU) , a radio head (RH) , a remote radio head (RRH) , an IAB node, a low power node such as a femto node, a pico node, a reconfigurable intelligent surface (RIS) , Network-controlled Repeaters, and the like.
  • NodeB Node B
  • eNodeB or eNB evolved NodeB
  • gNB next generation NodeB
  • TRP transmission reception point
  • RRU remote radio unit
  • RH radio head
  • RRH remote radio head
  • IAB node a low power node such
  • the terminal device or the network device may have Artificial intelligence (AI) or Machine learning capability. It generally includes a model which has been trained from numerous collected data for a specific function, and can be used to predict some information.
  • AI Artificial intelligence
  • Machine learning capability it generally includes a model which has been trained from numerous collected data for a specific function, and can be used to predict some information.
  • the terminal or the network device may work on several frequency ranges, e.g. FR1 (410 MHz to 7125 MHz) , FR2 (24.25GHz to 71GHz) , frequency band larger than 100GHz as well as Tera Hertz (THz) . It can further work on licensed/unlicensed/shared spectrum.
  • the terminal device may have more than one connection with the network devices under Multi-Radio Dual Connectivity (MR-DC) application scenario.
  • MR-DC Multi-Radio Dual Connectivity
  • the terminal device or the network device can work on full duplex, flexible duplex and cross division duplex modes.
  • the network device may have the function of network energy saving, Self-Organising Networks (SON) /Minimization of Drive Tests (MDT) .
  • the terminal may have the function of power saving.
  • test equipment e.g. signal generator, signal analyzer, spectrum analyzer, network analyzer, test terminal device, test network device, channel emulator.
  • the embodiments of the present disclosure may be performed according to any generation communication protocols either currently known or to be developed in the future.
  • Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, 5.5G, 5G-Advanced networks, or the sixth generation (6G) networks.
  • the terminal device may be connected with a first network device and a second network device.
  • One of the first network device and the second network device may be a master node and the other one may be a secondary node.
  • the first network device and the second network device may use different radio access technologies (RATs) .
  • the first network device may be a first RAT device and the second network device may be a second RAT device.
  • the first RAT device is eNB and the second RAT device is gNB.
  • Information related with different RATs may be transmitted to the terminal device from at least one of the first network device or the second network device.
  • first information may be transmitted to the terminal device from the first network device and second information may be transmitted to the terminal device from the second network device directly or via the first network device.
  • information related with configuration for the terminal device configured by the second network device may be transmitted from the second network device via the first network device.
  • Information related with reconfiguration for the terminal device configured by the second network device may be transmitted to the terminal device from the second network device directly or via the first network device.
  • the singular forms ‘a’ , ‘an’ and ‘the’ are intended to include the plural forms as well, unless the context clearly indicates otherwise.
  • the term ‘includes’ and its variants are to be read as open terms that mean ‘includes, but is not limited to. ’
  • the term ‘based on’ is to be read as ‘at least in part based on. ’
  • the term ‘one embodiment’ and ‘an embodiment’ are to be read as ‘at least one embodiment. ’
  • the term ‘another embodiment’ is to be read as ‘at least one other embodiment. ’
  • the terms ‘first, ’ ‘second, ’ and the like may refer to different or same objects. Other definitions, explicit and implicit, may be included below.
  • values, procedures, or apparatus are referred to as ‘best, ’ ‘lowest, ’ ‘highest, ’ ‘minimum, ’ ‘maximum, ’ or the like. It will be appreciated that such descriptions are intended to indicate that a selection among many used functional alternatives can be made, and such selections need not be better, smaller, higher, or otherwise preferable to other selections.
  • the term “occasion” refers to any of the following: 1) a time domain resource and frequency domain resource assigned, configured or granted for a data transmission, for example, the time domain resource may include one or more slots, one or more mini-slots, or one or more symbols; 2) one or more slots in which a DL assignment, UL grant or sidelink grant occurs; 3) one or more symbols in which a DL assignment, UL grant or sidelink grant occurs.
  • the term “HARQ codebook” may be interchangeably used with “HARQ-ACK codebook” .
  • the term “slot” used herein refers to a dynamic scheduling unit. One slot comprises a predetermined number of symbols.
  • the term “downlink (DL) sub-slot” may refer to a virtual sub-slot constructed based on uplink (UL) sub-slot.
  • the DL sub-slot may comprise fewer symbols than one DL slot.
  • the slot used herein may refer to a normal slot which comprises a predetermined number of symbols and may also refer to a sub-slot which comprises fewer symbols than the predetermined number of symbols.
  • SPS Semi persistent scheduling
  • Type-1 HARQ-ACK codebook construction with semi-static codebook size is mainly based on RRC parameters:
  • the terminal device determines the HARQ-ACK bit position for the SPS PDSCH based on the K1 value and the SLIV of the SPS PDSCH, which are indicated by the activation DCI.
  • SLIV is the Start and Length Indicator for the time domain allocation for PDSCH and defines the start symbol and the number of consecutive symbols for PDSCH allocation.
  • multiple SPS PDSCH transmission occasions in a period may be supported for XR traffic with large packet size to improve system capacity.
  • HARQ-ACK for multi-SPS PDSCHs and HARQ-ACK for DG PDSCH are multiplexed in a PUCCH
  • enhancements for HARQ-ACK codebook construction for multiplexing multi-SPS HARQ-ACK and DG HARQ-ACK are needed.
  • FIG. 1 illustrates a schematic diagram of an example communication network 100 in which some embodiments of the present disclosure can be implemented.
  • the communication network 100 may include a terminal device 110 and a network device 120.
  • the network device 120 may provide a serving cell (also referred to as a cell herein)
  • the terminal device 110 may be located in the cell and may be served by the network device 120.
  • the communication network 100 may include any suitable number of network devices and/or terminal devices and/cells adapted for implementing implementations of the present disclosure.
  • the terminal device 110 may communicate with the network device 120 via a channel such as a wireless communication channel.
  • the communications in the communication network 100 may conform to any suitable standards including, but not limited to, Global System for Mobile Communications (GSM) , Long Term Evolution (LTE) , LTE-Evolution, LTE-Advanced (LTE-A) , New Radio (NR) , Wideband Code Division Multiple Access (WCDMA) , Code Division Multiple Access (CDMA) , GSM EDGE Radio Access Network (GERAN) , Machine Type Communication (MTC) and the like.
  • GSM Global System for Mobile Communications
  • LTE Long Term Evolution
  • LTE-Evolution LTE-Advanced
  • NR New Radio
  • WCDMA Wideband Code Division Multiple Access
  • CDMA Code Division Multiple Access
  • GERAN GSM EDGE Radio Access Network
  • MTC Machine Type Communication
  • Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, 5.5G, 5G-Advanced networks, or the sixth generation (6G) networks.
  • the wireless communication channel may comprise a physical uplink control channel (PUCCH) , a physical uplink shared channel (PUSCH) , a physical random-access channel (PRACH) , a physical downlink control channel (PDCCH) , a physical downlink shared channel (PDSCH) , and a physical broadcast channel (PBCH) .
  • PUCCH physical uplink control channel
  • PUSCH physical uplink shared channel
  • PRACH physical random-access channel
  • PDCCH physical downlink control channel
  • PDSCH physical downlink shared channel
  • PBCH physical broadcast channel
  • the terminal device 110 may transmit UL data to the network device 120 via a UL data channel transmission.
  • the UL data channel transmission may be a physical uplink shared channel (PUSCH) transmission.
  • PUSCH physical uplink shared channel
  • the terminal device 110 may receive DL data from the network device 120 via a DL data channel transmission.
  • the DL data channel transmission may be a physical downlink shared channel (PDSCH) transmission.
  • PDSCH physical downlink shared channel
  • the terminal device 110 may receive, from the network device 120, downlink control information (DCI) via a DL control channel transmission.
  • DCI downlink control information
  • the DL control channel transmission may be a PDCCH transmission.
  • PDCCH Physical Downlink Control Channel
  • the terminal device 110 may transmit uplink control information (UCI) , e.g., HARQ feedback information, to the network device 120 via an UL control channel transmission.
  • UCI uplink control information
  • the UL control channel transmission may be a PUCCH transmission.
  • any other suitable forms are also feasible.
  • FIG. 2 shows a signaling chart illustrating process 200 of communication in an example scenario with a SPS configuration. Only for the purpose of discussion, the process 200 will be described with reference to FIG. 1.
  • the process 200 may involve the terminal device 110 and the network device 120 in FIG. 1.
  • the network device 120 may transmit 202 control information 204 to the terminal device 110.
  • the control information may indicate a SPS configuration with a set of SPS PDSCH occasions for data transmission per periodicity of the transmission configuration.
  • the control information may indicate a CG configuration with a set of CG PUSCH occasions for data transmission per periodicity of the transmission configuration. Only for the purpose of illustrations, embodiments of the present disclosure are described with the reference to the SPS configuration.
  • the control information may indicate a pattern of a set of SPS PDSCH occasions for data transmission per periodicity of a transmission configuration.
  • the pattern may comprise the number of the set of SPS PDSCH occasions per SPS periodicity, a time domain location and/or a frequency domain location of the set of SPS PDSCH occasions. In other embodiments, the pattern can comprise the number of the set of CG PUSCH occasions per CG periodicity, a time domain location and/or a frequency domain location of the set of CG PUSCH occasions.
  • the control information can be transmitted in the RRC configuration for configuring the terminal device 110 with a SPS configuration with multiple PDSCH occasions per periodicity. Alternatively, the control information can be transmitted in a DCI for activating or updating the SPS configuration.
  • the terminal device 110 may receive 206 the control information 204.
  • the network device 120 may transmit 208 multiple SPS PDSCHs 210 for a set of different transport blocks (TBs) at corresponding SPS PDSCH occasions in a period for the SPS configuration.
  • the terminal device 110 may receive 212 the multiple SPS PDSCHs at corresponding SPS PDSCH occasions based on the control information 204.
  • the terminal device 110 may transmit 214 a HARQ-ACK codebook 216 in a PUCCH to the network device 120.
  • the HARQ-ACK codebook 216 comprises HARQ-ACK feedback information for the multiple SPS PDSCHs.
  • the network device 120 may receive 218 the HARQ-ACK feedback information 216.
  • the network device 120 may transmit 220 a DCI 222 for scheduling retransmissions of the set of SPS PDSCHs in the period.
  • the terminal device 110 may receive 224 the DCI and wait for the retransmissions of the set of SPS PDSCHs.
  • the network device 120 may transmit 226 retransmissions 228 of the set of SPS PDSCHs.
  • the terminal device 110 may receive 230 retransmissions of the set of SPS PDSCHs based on the DCI 222.
  • FIG. 3A illustrates a simplified block diagram of an example construction 300A of a type-1 HARQ codebook for DG PDSCH in a related solution.
  • K1 set is ⁇ 1, 2, 3, 4 ⁇ and the number of start and length indicator values (SLIVs) in the indicated row index in the configured time domain resource allocation (TDRA) table is 2 and the two SLIVs are not overlapped in time domain.
  • TDRA time domain resource allocation
  • a type-1 HARQ-ACK codebook with 8 HARQ-ACK positions may be constructed, each HARQ-ACK position is corresponding to a combination of a K1 value and a SLIV.
  • the terminal device may always be able to determine a HARQ-ACK position for a PDSCH reception based on the corresponding K1 value and SLIV in the HARQ-ACK codebook.
  • FIG. 3B illustrates a simplified block diagram of an example scenario 300B where HARQ-ACK for multi-SPS PDSCHs and HARQ-ACK for DG PDSCH are multiplexed in a PUCCH.
  • a SPS configuration with multiple SPS PDSCH occasions in a period is supported. Only one K1 value is indicated for the multiple SPS PDSCH occasions. For example, only the slot/sub-slot offset between slot/sub-slot of the last SPS PDSCH occasion and slot/sub-slot of the PUCCH for HARQ-ACK bits of multi-SPS PDSCHs is indicated.
  • the terminal device 110 cannot determine multiple HARQ-ACK positions for the multiple SPS PDSCH receptions in a Type-1 HARQ-ACK codebook based on only an indicated K1 value of the multiple SPS PDSCH receptions. Therefore, how to construct the HARQ-ACK codebook for the multi-SPS PDSCHs 0-3 and the DG PDSCH1 is unclear for the terminal device.
  • some embodiments of the present disclosure provide a solution of constructing a HARQ-ACK codebook for HARQ-ACK for multi-SPS PDSCHs.
  • the solution will be described in detail with reference to FIGs. 4 to 5C below.
  • FIG. 4 shows a signaling chart illustrating process 400 of communication according to some embodiments of the present disclosure.
  • the process 400 will be described with reference to FIG. 1.
  • the process 400 may involve the terminal device 110 and the network device 120 in FIG. 1.
  • the same reference numerals are used to denote the steps or components described in FIG. 4 having the same operations as the steps or components described in FIG. 2, and detailed description thereof will be omitted.
  • the steps and the order of the steps in FIG. 4 are merely for illustration, and not for limitation. For example, the order of the steps may be changed. Some of the steps may be omitted or any other suitable additional steps may be added.
  • the network device 120 transmits 208, to the terminal device 110, multiple SPS PDSCH transmissions 210 in a period for a SPS configuration.
  • the terminal device 110 receives 212 the multiple SPS PDSCH transmissions 404.
  • the terminal device 110 determines 408 a HARQ-ACK codebook 412 comprising HARQ-ACK for the multiple SPS PDSCH transmissions.
  • HARQ-ACK bits for the multiple TBs per SPS periodicity are multiplexed on a PUCCH
  • the slot for PUCCH resource may be determined based on the HARQ-ACK timing value K1 in activation DCI and the slot/sub-slot for the last SPS PDSCH reception.
  • the HARQ-ACK codebook 412 may be constructed to comprise HARQ-ACK for the plurality of SPS PDSCH transmissions and HARQ-ACK for the at least one dynamic scheduled PDSCH transmission.
  • the terminal device 110 transmits 410 the HARQ-ACK codebook 412 to the network device 120 in the PUCCH.
  • the network device 120 receives 414 the HARQ-ACK codebook 412 in the PUCCH and determines 416 HARQ-ACK positions for the plurality of SPS PDSCH transmissions in the HARQ-ACK codebook 412.
  • the network device 120 may obtain the HARQ-ACK for the plurality of SPS PDSCH transmissions and determine whether the terminal device 110 successfully decoded the plurality of SPS PDSCH transmissions and which of the plurality of SPS PDSCH transmission need to be retransmitted. In this way, multiplexing HARQ-ACK information for multi-SPS PDSCHs in a period for SPS configuration and HARQ-ACK information for DG PDSCH (s) in a PUCCH may be supported, which is beneficial to improve the spectrum efficiency.
  • the HARQ-ACK codebook may be constructed as a Type-1 HARQ-ACK codebook. If the terminal device 110 is configured to support a plurality of PDSCH transmissions dynamically scheduled in a physical downlink control channel (PDCCH) , the HARQ-ACK positions for the plurality of SPS PDSCH transmissions in the HARQ-ACK codebook 412 may be determined based on SLIV associated with each of the plurality of SPS PDSCH transmission, a slot offset between a last SPS PDSCH transmission among the plurality of SPS PDSCH transmissions and the PUCCH and a slot offset between each of the plurality of SPS PDSCH transmissions and the last SPS PDSCH transmission. In this way, construction rules for Type-1 HARQ-ACK CB for HARQ-ACK for multi-SPS PDSCHs may be defined.
  • PUCCH physical downlink control channel
  • the terminal device 110 may be configured with a parameter PDSCH-TimeDomainResourceAllocationListForMultiPDSCH, and a SPS configuration with multi-SPS PDSCH occasions in a period may be activated by network device 120 with an activation DCI indicating a row contain multiple SLIVs for multiple PDSCHs.
  • a codebook for multi-SPS PDSCHs in a period may be constructed based on SLIV of each SPS PDSCH, the K1 value in activation DCI and the slot offset between the n th SPS PDSCH and the last SPS PDSCH. This solution has less specification impact.
  • FIG. 5A shows an example scenario 500A where HARQ-ACK for multi-SPS PDSCHs and HARQ-ACK for DG PDSCH are multiplexed.
  • a SPS configuration with 4-SPS PDSCH occasions in a period is activated.
  • the SPS PDSCH transmissions in the previous SPS period and the corresponding PUCCH for HARQ-ACK feedback are not shown.
  • HARQ-ACK for DG PDSCH #2 and DG PDSCH #3 and HARQ-ACK for SPS PDSCHs #4 -#7 are multiplexed in the same PUCCH.
  • FIG. 5B shows a simplified block diagram of an example HARQ-ACK codebook 500B in the scenario of FIG. 5A according to some embodiments of the present disclosure.
  • the terminal device 110 may determine K1’ values of the PDSCHs #4 -#6 to be 2, 3 and 4 based on the K1 value of the last SPS PDSCH #7 and the slot offset between the corresponding SPS PDSCH transmission and the last SPS PDSCH #7.
  • a type-1 HARQ-ACK codebook may be constructed based on SLIV of each SPS PDSCH and a merge of the initial K1 set ⁇ 1, 3, 5, 7 ⁇ , the dummy K1’ values ⁇ 2, 3, 4 ⁇ .
  • DG PDSCH #2, DG PDSCH #3 are both single PDSCH scheduled by a DCI
  • the concepts of these embodiments may also be applied to scenarios where HARQ-ACK for multiple SPS PDSCHs multiplexed with HARQ-ACK for multiple DG PDSCHs scheduled by a DCI.
  • the HARQ-ACK positions for the plurality of SPS PDSCH transmissions may be placed before or after HARQ-ACK positions for the at least one dynamic scheduled PDSCH transmission.
  • HARQ-ACK bits for the plurality of SPS PDSCH transmissions are appended to the HARQ-ACK codebook for DG PDSCHs.
  • Bit order of the HARQ-ACK positions for the plurality of SPS PDSCH transmissions may be based on slot index of the plurality of SPS PDSCH transmissions. It should be understood that the concepts of these embodiments may also be applied to scenarios where the terminal device is not configured to support a plurality of PDSCH transmissions dynamically scheduled in a PDCCH. This solution is very simple. It also provides a unified rule for multiplexing HARQ-ACK information for multi-SPS PDSCHs in a period on both Type-1 HARQ-ACK codebook and Type-2 HARQ-ACK codebook.
  • the terminal device 110 may not be configured with a parameter PDSCH-TimeDomainResourceAllocationListForMultiPDSCH, and a SPS configuration with multi-SPS PDSCH occasions (e.g., N occasions, N>0) in a period may be activated by network device 120 with an activation DCI.
  • the terminal device 110 may generate N HARQ-ACK positions for separately reporting valid HARQ-ACK/NACK for N SPS PDSCHs and places the N HARQ-ACK positions before/after the Type-1 CB for single-PDSCH scheduling and/or single SPS PDSCH occasion in a period.
  • the bit order for N SPS PDSCHs in the constructed Type-1 CB may be based on an order of DL slot indexes of the N SPS PDSCHs. For example, the HARQ-ACK position of the SPS PDSCH with the lower DL slot index is place before the HARQ-ACK position of the SPS PDSCH with the higher DL slot index.
  • FIG. 5C shows a simplified block diagram of an example HARQ-ACK codebook 500C in the scenario of FIG. 5A according to some embodiments of the present disclosure. As shown in FIG. 5C, HARQ-ACK positions for the plurality of SPS PDSCHs #4 -#7 are sequentially placed after the Type-1 CB for DG PDSCH #2 and DG PDSCH #3.
  • Type-1 HARQ-ACK codebook determination may be embodied as follows: .
  • one HARQ-ACK position for the plurality of SPS PDSCH transmissions may be determined based on SLIV associated with a last or first SPS PDSCH transmission among the plurality of SPS PDSCH transmissions and a slot offset indication between the last or first SPS PDSCH transmission and the PUCCH.
  • the HARQ-ACK position for the plurality of SPS PDSCH transmissions may be used for reporting bundling HARQ-ACK for the plurality of SPS PDSCH transmissions.
  • the terminal device will generate only one HARQ-ACK bit for the plurality of SPS PDSCH transmissions by operate AND operation for multiple HARQ-ACK bits of the plurality of SPS PDSCH transmissions and report the one HARQ-ACK bit in the corresponding HARQ-ACK position.
  • the concepts of these embodiments may also be applied to scenarios where the terminal device is not configured to support a plurality of PDSCH transmissions dynamically scheduled in a PDCCH.
  • one HARQ-ACK position for SPS PDSCHs #4 -#7 may be determined based on the K1 value and SLIV for SPS PDSCH #7.
  • the HARQ-ACK information for the SPS PDSCHs #4 -#7 may be determined to be NACK. This solution is simple and has less specification impact at cost of spectrum efficiency reduction.
  • the HARQ-ACK codebook may be constructed as a Type-2 HARQ-ACK codebook. If the network device 120 transmits a plurality of PDSCH transmissions dynamically scheduled in a PDCCH to the terminal device 110 and in case that the at least one dynamic scheduled PDSCH transmission comprises the plurality of PDSCH transmissions, the HARQ-ACK positions for the plurality of SPS PDSCH transmissions with or without PDCCH may be placed after sub-codebook for multiple-PDSCH scheduling for the plurality of PDSCH transmissions.
  • HARQ-ACK positions for the plurality of SPS PDSCH transmissions with or without PDCCH may be placed after sub-codebook for single-PDSCH scheduling for the at least one dynamic scheduled PDSCH transmission.
  • bit order of the HARQ-ACK positions for the plurality of SPS PDSCH transmissions may be based on slot index of the plurality of SPS PDSCH transmissions. In this way, construction rules for Type-2 HARQ-ACK CB for HARQ-ACK for multi-SPS PDSCHs may be enhanced.
  • the terminal device may generate N HARQ-ACK positions for separately reporting valid HARQ-ACK/NACK for N SPS PDSCHs with/without activation DCI and place the N HARQ-ACK positions after the sub-codebook for multi-PDSCH scheduling or sub-codebook for single-PDSCH scheduling.
  • the bit order for N SPS PDSCHs in the constructed Type-2 CB may be based on an order of DL slot indexes of the N SPS PDSCHs.
  • the terminal device may generate N HARQ-ACK positions for separately reporting valid HARQ-ACK/NACK for N SPS PDSCHs with/without activation DCI and place the N HARQ-ACK positions after the TB based codebook for single PDSCH scheduling.
  • the bit order for N SPS PDSCHs in the constructed Type-2 CB may be based on an order of DL slot indexes of the N SPS PDSCHs.
  • the terminal device when multiple PDSCH scheduling by a DCI is configured, while a SPS configuration with multiple SPS PDSCH occasions is activated by a DCI indicating a time domain row index with only a SLIV, when HARQ-ACK information for multiple SPS PDSCHs of the SPS configuration and HARQ-ACK information for DG PDSCHs including single PDSCH scheduling and multiple PDSCH scheduling are multiplexed on Type-2 HARQ-ACK codebook, the terminal device will generate one first sub-codebook for single PDSCH scheduling and one second sub-codebook for multiple PDSCH scheduling, and place HARQ-ACK information bits of the multiple SPS PDSCHs after the first sub-codebook and before the second sub-codebook.
  • This solution gives more scheduling flexibility for gNB to activate the SPS configuration.
  • the HARQ-ACK feedback information might indicate that among the multiple SPS PDSCHs 210 in a period for the SPS configuration, more than one SPS PDSCH fails to be decoded successfully by the terminal device 110.
  • more than one CG PUSCH may fails to be decoded successfully by the network device 110.
  • a scheme supporting multi-SPS PDSCH retransmission or multiple CG PUSCH retransmission scheduled by a DCI may be developed.
  • Some embodiments of the present disclosure provide a solution of supporting multi-SPS PDSCH retransmission or multiple CG PUSCH retransmission scheduled by a DCI.
  • a design for a DCI format scheduling multiple SPS PDSCH or CG PUSCHs retransmissions is provided. The solution will be described in detail with reference to FIGs. 6 to 9 below.
  • FIG. 6 shows a signaling chart illustrating process 600 of communication according to some embodiments of the present disclosure.
  • the process 600 will be described with reference to FIG. 1.
  • the process 600 may involve the terminal device 110 and the network device 120 in FIG. 1.
  • the same reference numerals are used to denote the steps or components described in FIG. 6 having the same operations as the steps or components described in FIGs. 2 and 4, and detailed description thereof will be omitted.
  • the steps and the order of the steps in FIG. 6 are merely for illustration, and not for limitation. For example, the order of the steps may be changed. Some of the steps may be omitted or any other suitable additional steps may be added.
  • the network device 120 transmits 208, to the terminal device 110, multiple SPS PDSCH transmissions 210 in a period for a SPS configuration.
  • the multiple SPS PDSCH transmissions 210 may be N transmissions for a set of different transport blocks TB, wherein N>1. In other words, the number of SPS PDSCH occasions in a period is N. If the network device 120 determines, e.g.
  • the network device 120 transmits 614, to the terminal device 110, a DCI 616 with CRC scrambled by CS-RNTI for scheduling retransmissions of the M transmissions, wherein 1 ⁇ M ⁇ N.
  • the terminal device 110 receives 618 the DCI 616 for scheduling retransmissions of the M transmissions and determines 620 HARQ process numbers (HPN) of the M transmissions based on the DCI 616, HARQ process number here refers HARQ process ID of a data transmission.
  • the network device 120 may transmit 202 control information 204 to the terminal device 110.
  • the control information 204 indicates the SPS configuration with N SPS PDSCH occasions for data transmission per periodicity.
  • the terminal device 110 may receive 618 a DCI for scheduling retransmissions of the M transmissions and determine 620 the HARQ process numbers for the M SPS PDSCH retransmissions based on some indication information in the DCI.
  • the DCI 616 may comprise an indication of a HARQ process number of a first transmission among the N transmissions or a first transmission among the M transmissions. In some embodiments, the DCI 616 may further comprise additional information for determining HARQ process numbers of the M transmissions. In some embodiments, the additional information may comprise N bits. A value of each bit among the N bits indicates whether retransmission of a corresponding transmission among the N transmissions is scheduled or not. In some embodiments, the DCI 616 may further comprise an indication of whether the DCI is for scheduling SPS PDSCH retransmissions or not.
  • the indication of a HARQ process number of a first transmission among the N transmissions or a first transmission among the M transmissions may be represented by the bit value in the HARQ process number field in the DCI.
  • the indication of whether the DCI is for scheduling SPS PDSCH retransmissions or not may be represented in the first MSB bit in the NDI field in the DCI.
  • MSB means most significant bit in an indicator field
  • LSB means least significant bit in an indicator field.
  • the N bits in the NDI field following the first MSB bit may indicate whether retransmission of a corresponding transmission among the N transmissions is scheduled or not.
  • the terminal device may determine the HARQ process numbers of the M transmissions for transmission based on the DCI comprising the indication in HARQ process number field of a HARQ process number of a first transmission among the N transmissions or a first transmission among the M transmissions; an indication in first MSB bit in new data indicator (NDI) field of whether the DCI is for scheduling SPS PDSCH retransmissions or not; and N bits, the value of each bit indicating whether retransmission of a corresponding transmission among the N transmissions is scheduled.
  • the additional information N bits can also be carried in other DCI field, e.g., introduce a new indicator field or other unused field. This solution reduces the PDCCH transmissions and scheduling latency, which further improves the system capacity.
  • the configured SPS PDSCH occasions are always for initial DL data transmission.
  • the network device may schedule the multi-SPS PDSCH retransmission by a single DCI.
  • the bit value in the HARQ process number field in the DCI indicates that the HARQ process ID of the first SPS PDSCH in the corresponding period, or the HARQ process ID of the first retransmitted SPS PDSCH in the corresponding period, .
  • the bit width of NDI field in the DCI format may be determined based on at least the number N.
  • the bit width B of the NDI field may be a maximum value between N+1 and K, wherein K is the maximum number of schedulable PDSCHs among all entries in the higher layer parameter pdsch-TimeDomainResourceAllocationListForMultiPDSCH if provided.
  • the first MSB bit of the NDI field indicates the NDI value for activating SPS configuration or for scheduling retransmissions of SPS PDSCHs. For example, if the value of the first bit of the NDI field is 1, the scheduled PDSCHs are for SPS PDSCH retransmissions in the corresponding SPS configuration; and if the value of the first bit of the NDI field is 0, the DCI is used for activating SPS PDSCH transmissions in the corresponding SPS configuration, the HARQ process number indicator field and the (B-1) LSB bits in the NDI field may be indicated with value 0.
  • the following N bits of the NDI field indicate a bit-mapping for whether the corresponding SPS PDSCH in the period is retransmitted or not.
  • the LSB B-1-N bits are padding bits if any.
  • the terminal device may determine the HARQ process numbers of the multi-SPS PDSCHs scheduled to be retransmitted based on the HPN field and NDI field in scheduling DCI.
  • FIG. 7A illustrates a simplified block diagram 700A of scheduling retransmissions of multiple SPS PDSCHs in a period by a single DCI according to some embodiments of the present disclosure.
  • the terminal device receives a DCI for activating a SPS configuration with 4 SPS PDSCH occasions in a period.
  • the first MSB bit in the NDI field in DCI for activating a SPS configuration has a value of 0.
  • the SPS PDSCHs #0 -#3 in the first period are decoded successfully by the terminal device.
  • the SPS PDSCHs #4 -#7 in the second period the SPS PDSCHs #5 and #7 fail to be decoded successfully by the terminal device.
  • the network device Based on HARQ-ACK feedback information, the network device transmits a DCI for scheduling retransmissions of the SPS PDSCHs #5 and #7.
  • Table 1 shows the indicator values of the DCI for scheduling retransmissions of multiple SPS PDSCHs in the example embodiment of FIG. 7A.
  • Table 1 DCI field re-interpretation in the DL DCI format for multi-SPS PDSCH retransmission
  • the value of the HARQ process number field “0101” indicates that the first retransmitted SPS PDSCH has a HARQ process ID of 5.
  • the bit value in the HARQ process number field in the DCI may indicate the HARQ process number of the first SPS PDSCH in the corresponding period, i.e., SPS PDSCH #4 in the second period, and thus the value of HARQ process number field in the DCI may be “0100” .
  • the value of the first bit in the NDI field is “1” , indicating that the DCI is for SPS PDSCH retransmitting.
  • an example implementation for scheduling retransmissions of multiple SPS PDSCHs may be embodied as follows:
  • an example implementation for the NDI field in the DCI may be embodied as follows:
  • the DCI 616 may comprise an indication of a HARQ process number of a first transmission among the N transmissions or a first transmission among the M transmissions and N bits, the value of each bit indicating whether retransmission of a corresponding transmission among the N transmissions is scheduled.
  • the DCI 616 may not include a dedicated bit in the NDI field indicating whether the DCI is for scheduling SPS PDSCH retransmissions or not. Whether the DCI is for scheduling SPS PDSCH retransmissions for a SPS configuration or not may be implicitly indicated by the N bits in the NDI field.
  • the N bits all indicate value 0 that none of the N transmissions is scheduled to be retransmitted, it means that the DCI 616 is not for scheduling SPS PDSCH retransmissions but for activating a SPS configuration. If at least one of the N bits indicates value 1 that the corresponding transmission of the N transmissions is scheduled to be retransmitted, it means that the DCI 616 is for scheduling SPS PDSCH retransmissions.
  • the information N bits can also be carried in other DCI field, e.g., introduce a new indicator field or other unused field. This solution uses less control information bits for scheduling multiple SPS PDSCH retransmissions, which reduces the control overhead.
  • the network device schedules retransmissions of M SPS PDSCHs in a period by DCI format 1_1 in PDCCH with CRC scrambled by CS-RNTI with M bits in the NDI field NDI having a value of 1 (M ⁇ 1) , which means that the DCI schedules M SPS PDSCH retransmissions in the period.
  • the bit value in the HARQ process number field in the DCI indicates the HARQ process number of the first (or first retransmitted) SPS PDSCH in the corresponding period.
  • the bit width of the NDI field in the DCI format is determined based on at least the number N.
  • the bit width B of the NDI field may be a maximum value between N and K, wherein K is the maximum number of schedulable PDSCH among all entries in the higher layer parameter pdsch-TimeDomainResourceAllocationListForMultiPDSCH if provided.
  • the N MSB bits of the NDI field indicate a bit-mapping for whether the corresponding SPS PDSCH in the period is retransmitted or not.
  • the LSB B-N bits are padding bits if any.
  • the terminal device may determine whether and how many SPS PDSCHs are scheduled to be retransmitted by the DCI based on the number of bits in the N MSB bits of the NDI field with a value of 1. For example, if the value of the first bit of the NDI field is 1, retransmission of the first SPS PDSCH in corresponding period is scheduled by the DCI.
  • the terminal device may determine the HARQ process numbers of the multi-SPS PDSCHs scheduled to be retransmitted based on the HPN field and NDI field in scheduling DCI.
  • FIG. 7B illustrates a simplified block diagram 700B of scheduling retransmissions of multiple SPS PDSCHs in a period by a single DCI according to some embodiments of the present disclosure.
  • Table 2 shows the format of the DCI for scheduling retransmissions of multiple SPS PDSCHs in the example embodiment of FIG. 7B.
  • the definition of HARQ process number field in this embodiment is the similar with that in the embodiment in FIG. 7 and Table 1.
  • the definition of the first bit to the N th bit in the NDI field in this embodiment is the similar with the definition of the second bit to the N+1 th bit in the NDI field in the embodiment in FIG. 7 and Table 1.
  • Whether the DCI is for activating a SPS configuration or for scheduling SPS PDSCH retransmissions is indicated based on whether any of the first to the N th bits of the NDI field has a value of 1. If the values of the first 4 bits in the NDI field are “0000” , it means that the DCI is for activating a SPS configuration with multi-SPS PDSCH occasions in a period.
  • an example implementation for scheduling retransmissions of multiple SPS PDSCHs may be embodied as follows:
  • an example implementation for the NDI field in the DCI may be embodied as follows:
  • the DCI may comprise an indication of whether the DCI is for scheduling SPS PDSCH retransmissions, an indication of whether one transmission or more than one transmission is scheduled in the DCI and an indication of a HARQ process number of a first transmission among the N transmissions.
  • the network device may transmit a DCI for scheduling retransmissions of all the N transmissions.
  • the terminal device may determine the HARQ process numbers of the N transmissions for transmission based on the indication of a HARQ process number of a first transmission among the N transmissions in the DCI.
  • the indication of a HARQ process number of a first transmission among the N transmissions may be represented by the bit value in the HARQ process number field in the DCI. This solution also reduces control overhead and has less specification impact, but it may degrade the spectrum efficiency when only M SPS PDSCHs are decoded unsuccessfully (1 ⁇ M ⁇ N) .
  • the terminal device may determine whether the scheduling DCI is for scheduling retransmissions of a single SPS PDSCH or multiple SPS PDSCHs based on an implicit indication in the DCI or an explicit indication in the DCI.
  • the terminal device determines that retransmissions of multiple SPS PDSCHs is scheduled.
  • some field in the DCI may be re-interpreted or one-bit new indicator field may be introduced to explicitly indicate whether the scheduling DCI is for scheduling retransmission of a single SPS PDSCH or multiple SPS PDSCHs. If multi-SPS PDSCH retransmissions are scheduled, the value in the HPN field in the DCI indicates the HARQ process ID of the first SPS PDSCH in the corresponding period.
  • the reception of SPS PDSCH retransmissions depends on the implementation of the terminal device. For example, the terminal device may only receive the retransmissions of SPS PDSCHs corresponding to the TBs that fail to be decoded. In this way, it is beneficial for UE power saving. Alternatively, the terminal device may receive the retransmissions of all the SPS PDSCHs regardless of whether the corresponding TB is decoded successfully or not. In this way, it can improve reliability performance of the SPS PDSCH transmission.
  • FIG. 7C illustrates a simplified block diagram 700C of scheduling retransmissions of multiple SPS PDSCHs in a period by a single DCI according to some embodiments of the present disclosure.
  • the network device may transmit a DCI for scheduling retransmissions of SPS PDSCHs #4 -#7.
  • the terminal device may only receive retransmissions of SPS PDSCHs #5 and #7.
  • the terminal device may receive retransmissions of SPS PDSCHs #4 -#7.
  • an example implementation for scheduling retransmissions of multiple SPS PDSCHs may be embodied as follows:
  • the network device may transmit a single DCI for scheduling retransmissions of the M transmissions.
  • the terminal device may receive the single DCI for scheduling retransmissions of the M consecutive transmissions with consecutive HARQ process numbers.
  • the network device may transmit a plurality of DCIs for scheduling retransmissions of the M transmissions respectively.
  • the terminal device may receive the plurality of DCIs for scheduling retransmissions of the M transmissions respectively.
  • the terminal device determines the number of retransmitted SPS PDSCHs based on an implicit indication (e.g., a time domain row index with more than one SLIVs) or an explicit indication (the number of scheduled SPS PDSCH retransmissions) and the corresponding HARQ process number for the retransmitted SPS PDSCHs based on HPN field that indicates the HARQ process ID of the first scheduled SPS PDSCH retransmission.
  • an implicit indication e.g., a time domain row index with more than one SLIVs
  • an explicit indication the number of scheduled SPS PDSCH retransmissions
  • FIGs. 7D and 7E illustrate simplified block diagrams 700D and 700E of scheduling retransmissions of multiple nonconsecutive SPS PDSCHs in a period by multiple DCIs and scheduling retransmissions of multiple consecutive SPS PDSCHs in a period by a single DCI according to some embodiments of the present disclosure.
  • the terminal device fails to decode SPS PDSCHs #5 and #7 which have nonconsecutive HARQ process numbers.
  • the network device may transmit a DCI for scheduling retransmission of SPS PDSCH #5 and another DCI for scheduling retransmission of SPS PDSCH #7.
  • FIG. 7D the terminal device fails to decode SPS PDSCHs #5 and #7 which have nonconsecutive HARQ process numbers.
  • the network device may transmit a DCI for scheduling retransmission of SPS PDSCH #5 and another DCI for scheduling retransmission of SPS PDSCH #7.
  • the terminal device fails to decode SPS PDSCHs #5, #6 and #7 which have consecutive HARQ process numbers. Based on the HARQ-ARQ feedback information, the network device may transmit a single DCI for scheduling retransmissions of SPS PDSCHs #5, #6 and #7.
  • an example implementation for scheduling retransmissions of multiple SPS PDSCHs may be embodied as follows:
  • the DCI 616 may comprise an indication of whether the DCI is for scheduling SPS PDSCH retransmissions, an indication of the number of scheduled M transmissions, an indication of a HARQ process number of a first transmission among the M transmissions and an indication of additional information for determining HARQ process numbers of the M transmissions.
  • the terminal device may determine that the HARQ process numbers of the M transmissions based on the indication of the number of scheduled M transmissions, the indication of a HARQ process number of a first transmission among the M transmissions and the indication of additional information for determining HARQ process numbers of the M transmissions in the DCI.
  • the indication of the number of scheduled M transmissions may be an implicit indication in the DCI or an explicit indication in the DCI.
  • the indication of the number of scheduled M transmissions may implicitly represented by the number of indicated SLIVs in the row of the pdsch-TimeDomainAllocationListForMultiPDSCH-r17 if provided.
  • some field in the DCI may be re-interpreted or one-bit new indicator field may be introduced to explicitly indicate the number of scheduled M transmissions.
  • the value in the HARQ process number field in the DCI indicates the HARQ process number of the first retransmitted SPS PDSCH in the corresponding period.
  • the two LSB bits of the NDI field indicates the assistant information of determination of HARQ process ID for the multi-retransmitted SPS PDSCHs, in other words the two bits in NDI field indicate a mapping relation between the number of scheduled SPS PDSCH retransmissions and the HARQ process IDs of the corresponding SPS PDSCH retransmissions.
  • the terminal device may determine the HARQ process ID for the multi-retransmitted SPS PDSCH based on the number of scheduled SPS PDSCH retransmission and the HPN field and NDI field indication. This solution is a little complicated, but it has less DCI overhead and larger scheduling flexibility.
  • Table 3 lists all scenarios of the DCI for scheduling retransmissions of SPS PDSCHs when the number of SPS PDSCH occasions in a period is 4 in some example embodiments.
  • the HARQ process numbers of the four SPS PDSCHs #0 -#3 in the period are assumed to be 0, 1, 2 and 3 respectively.
  • the first 3MSB bits indicates the HARQ process ID of the first scheduled SPS PDSCH retransmission in time domain
  • the second 3MSB bits indicates the HARQ process ID of the second scheduled SPS PDSCH retransmission in time domain
  • the two HARQ process IDs can be discontinuous. This solution may increase the size of DCI field, but it can also reduce PDCCH transmission and improves scheduling flexibility for gNB.
  • the terminal device may be configured with a CG configuration with a set of CG PUSCH occasions for data transmission per periodicity of the transmission configuration.
  • the design rules for DL DCI in the embodiments of the present disclosure for SPS configuration may also be applied to UL DCI (e.g., DCI format 0_1) for scheduling retransmission of the CG configuration, other new DCI format is also included.
  • FIG. 8 shows a signaling chart illustrating process 800 of communication according to some embodiments of the present disclosure.
  • the process 800 may involve the terminal device 110 and the network device 120 in FIG. 1. Similar reference numerals are used to denote the steps or components described in FIG. 8 having similar or corresponding operations as the steps or components described in FIGs. 2 and 6, and detailed description thereof will be omitted. Solutions in embodiments described in FIGs. 6-7E with respect to a SPS configuration may also be applied in embodiments of FIG. 8 with respect to a CG configuration. It is to be understood that the steps and the order of the steps in FIG. 8 are merely for illustration, and not for limitation. For example, the order of the steps may be changed. Some of the steps may be omitted or any other suitable additional steps may be added.
  • the terminal device 110 transmits 808, to the network device 120, N CG PUSCH transmissions 810 in a period for a CG configuration.
  • the network device 120 receives the N CG PUSCH transmissions 810 for different TBs.
  • the network device 120 may transmit 802 control information 804 to the terminal device 110.
  • the control information 804 indicates the CG configuration with N CG PUSCH occasions for data transmission per periodicity.
  • the terminal device 110 may transmit the N CG PUSCH transmissions 810 for different TBs in corresponding CG PUSCH occasions.
  • the terminal device 110 may receive 806 the control information 804 for the CG configuration.
  • the control information may be transmitted in a DCI for activating or updating the CG configuration.
  • the network device 120 may determine whether and which transmissions among the N CG PUSCH transmissions 810 need to be retransmitted based on the reception of the N CG PUSCH transmissions 810 by the network device 120.
  • the network device 120 transmits 814, to the terminal device 110, a DCI 816 with CRC scrambled by CS-RNTI for scheduling retransmissions of the M transmissions, wherein 1 ⁇ M ⁇ N.
  • the terminal device 110 receives the DCI 816 for scheduling retransmissions of the M transmissions and determines 820 HARQ process numbers of the M transmissions based on the DCI 816.
  • the terminal device 110 may transmit 826 retransmission 828 of the M CG PUSCHs based on the DCI 222.
  • the network device 120 may receive 830 retransmissions of the M CG PUSCHs. In this way, a scheme for scheduling multi-CG PUSCHs retransmission by a single DCI may be supported, which is beneficial to reduce the control overhead and improve the system capacity.
  • FIG. 9 illustrates a simplified block diagram 900 of scheduling retransmissions of multiple CG PUSCHs in a period by a single DCI according to some embodiments of the present disclosure.
  • the terminal device receives a DCI for activating a CG configuration with 4 CG PUSCH occasions in a period.
  • the CG PUSCHs #0 -#3 in the first period are transmitted by the terminal device to the network device and decoded successfully by the network device.
  • the CG PUSCHs #4 -#7 in the second period the CG PUSCHs #5 and #7 are decoded unsuccessfully by the network device.
  • the network device transmits a DCI for scheduling retransmissions of the CG PUSCHs #5 and #7.
  • Solutions in embodiments described in FIGs. 7A-7E with respect to retransmission scheduling of multiple SPS PDSCHs may also be applied in embodiments of FIG. 9 with respect to retransmission scheduling of multiple CG PUSCHs.
  • all the solutions described for retransmission scheduling of DL SPS PDSCH may also be applied to a configured grant Type 1 or Type 2. i.e., for a CG configuration with multi-CG PUSCH occasions in a period.
  • Multi-CG PUSCH retransmission by a DCI format 0_1 scrambled by CS-RNTI may also supported.
  • the NDI and HPN field design for DL DCI format 1_1 can also be applied for UL DCI format 0_1.
  • embodiments of the present disclosure provide methods of communication implemented at a terminal device and a network device. These methods will be described below with reference to FIGs. 10-13.
  • FIG. 10 illustrates an example method 1000 of communication implemented at a network device in accordance with some embodiments of the present disclosure.
  • the method 1000 may be performed at the network device 120 as shown in FIG. 1.
  • the method 1000 will be described with reference to FIG. 1. It is to be understood that the method 1000 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.
  • the network device 120 transmits to a terminal device 110 or receives from the terminal device 110, N transmissions for a set of different TBs in a period for a SPS configuration or a CG configuration, wherein N>1.
  • the network device 120 transmits, to the terminal device 110, a DCI in a PDCCH with CRC scrambled by CS-RNTI for scheduling retransmissions of the M transmissions, wherein 1 ⁇ M ⁇ N.
  • a scheme for scheduling multi-SPS PDSCHs retransmission or multi-CG PUSCHs retransmission by a single DCI may be supported, which is beneficial to reduce the control overhead.
  • the network device 120 may transmit control information to the terminal device.
  • the control information may indicate the SPS configuration with N SPS PDSCH occasions for data transmission per periodicity.
  • the control information may indicate the CG configuration with N CG PUSCH occasions for data transmission per periodicity.
  • the DCI may comprise an indication of a HARQ process number of a first transmission among the N transmissions or a first transmission among the M transmissions.
  • the DCI may further comprise additional information for determining HARQ process numbers of the M transmissions.
  • the additional information may comprise N bits. A value of each bit among the N bits may indicate whether a corresponding transmission among the N transmissions is scheduled to be retransmitted.
  • the DCI may further comprise an indication of whether the DCI is for scheduling SPS PDSCH or CG PUSCH retransmissions.
  • the network device 120 may transmit the DCI for scheduling retransmissions of the N transmissions in accordance with determining that M >1.
  • the DCI may comprise an indication of whether the DCI is for scheduling SPS PDSCH or CG PUSCH retransmissions, an indication of whether one transmission or more than one transmission is scheduled in the DCI, and an indication of a HARQ process number of a first transmission among the N transmissions.
  • the network device 120 may transmit the DCI for scheduling retransmissions of the N transmissions.
  • the network device 120 may transmit a plurality of DCIs for scheduling retransmissions of the M transmissions respectively in accordance with failure of the M transmissions among the N transmissions in the period and if the M transmissions are nonconsecutive transmissions with nonconsecutive HARQ process numbers.
  • the DCI may comprise an indication of whether the DCI is for scheduling SPS PDSCH or CG PUSCH retransmissions, an indication of the number of scheduled M transmissions, an indication of a HARQ process number of a first transmission among the M transmissions, and an indication of additional information for determining HARQ process numbers of the M transmissions.
  • the DCI may comprise an indication in a HARQ process number indicator field of HARQ process numbers of the M transmissions.
  • FIG. 11 illustrates another example method 1100 of communication implemented at a network device in accordance with some embodiments of the present disclosure.
  • the method 1100 may be performed at the network device 120 as shown in FIG. 1.
  • the method 1100 will be described with reference to FIG. 1. It is to be understood that the method 1100 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.
  • the network device 120 transmits, to a terminal device 110, a plurality of SPS PDSCH transmissions in a period for a SPS configuration.
  • the network device 120 receives, from the terminal device, a HARQ-ACK codebook in a PUCCH.
  • the HARQ-ACK codebook comprises HARQ-ACK for the plurality of SPS PDSCH transmissions.
  • the network device 120 determines HARQ-ACK positions for the plurality of SPS PDSCH transmissions in the HARQ-ACK codebook.
  • multiplexing HARQ-ACK information for multi-SPS PDSCHs in a period for a SPS configuration and HARQ-ACK information for DG PDSCH (s) in a PUCCH may be supported, which is beneficial to improve the spectrum efficiency.
  • the HARQ-ACK codebook may be a Type-1 HARQ-ACK codebook.
  • the network device 120 may determining HARQ-ACK positions for the plurality of SPS PDSCH transmissions based on a start and length indicator value (SLIV) associated with each of the plurality of SPS PDSCH transmissions, a slot offset between a last or a first SPS PDSCH transmission among the plurality of SPS PDSCH transmissions and the PUCCH, and a slot offset between each of the plurality of SPS PDSCH transmissions and the last or first SPS PDSCH transmission.
  • SIV start and length indicator value
  • the HARQ-ACK positions for the plurality of SPS PDSCH transmissions may be placed before or after HARQ-ACK positions for the at least one dynamic scheduled PDSCH transmission.
  • bit order of the HARQ-ACK positions for the plurality of SPS PDSCH transmissions may be based on slot index of the plurality of SPS PDSCH transmissions.
  • the network device 120 may determine one HARQ-ACK position for the plurality of SPS PDSCH transmissions based on a start and length indicator value (SLIV) associated with a last or a first SPS PDSCH transmission among the plurality of SPS PDSCH transmissions, and a slot offset indication between the last or first SPS PDSCH transmission and the PUCCH.
  • the HARQ-ACK position for the plurality of SPS PDSCH transmissions may be for reporting bundling HARQ-ACK for the plurality of SPS PDSCH transmissions.
  • the at least one dynamic scheduled PDSCH transmission may comprise one dynamic scheduled PDSCH transmission. If the terminal device is not configured to support a plurality of PDSCH transmissions dynamically scheduled in a PDCCH, the network device 120 may determine the HARQ-ACK positions for the plurality of SPS PDSCH transmissions.
  • the HARQ-ACK codebook may be a Type-2 HARQ-ACK codebook. If the network device transmits a plurality of PDSCH transmissions dynamically scheduled in a PDCCH to the terminal device and if the at least one dynamic scheduled PDSCH transmission comprises the plurality of PDSCH transmissions, the network device 120 may determine that the HARQ-ACK positions for the plurality of SPS PDSCH transmissions with or without PDCCH are placed after sub-codebook for multiple-PDSCH scheduling for the plurality of PDSCH transmissions.
  • the network device 120 may determine that the HARQ-ACK positions for the plurality of SPS PDSCH transmissions are placed after sub-codebook for single-PDSCH scheduling for the at least one dynamic scheduled PDSCH transmission.
  • bit order of the HARQ-ACK positions for the plurality of SPS PDSCH transmissions may be based on slot index of the plurality of SPS PDSCH transmissions.
  • FIG. 12 illustrates an example method 1200 of communication implemented at a terminal device in accordance with some embodiments of the present disclosure.
  • the method 1200 may be performed at the terminal device 110 as shown in FIG. 1.
  • the method 1200 will be described with reference to FIG. 1. It is to be understood that the method 1200 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.
  • the terminal device 110 receives from a network device 120 or transmit to the network device 120, N transmissions for a set of different TBs in a period for a SPS configuration or a CG configuration, wherein N>1.
  • the terminal device 110 receives, from the network device, a DCI in a PDCCH with CRC scrambled by CS-RNTI for scheduling retransmissions of M transmissions among N transmissions in the period, wherein 1 ⁇ M ⁇ N.
  • the terminal device 110 determines HARQ process numbers of the M transmissions based on the DCI. With the method of FIG. 12, a scheme for scheduling multi-SPS PDSCHs retransmission or multi-CG PUSCHs retransmission by a single DCI may be supported, which is beneficial to reduce the control overhead and improve the system capacity.
  • the terminal device 110 may receive control information from the network device.
  • the control information may indicate the SPS configuration with N SPS PDSCH occasions for data transmission per periodicity.
  • the control information may indicate the CG configuration with N CG PUSCH occasions for data transmission per periodicity.
  • the terminal device 110 may receive from the network device or transmit to the network device the retransmissions of the M transmissions based on the DCI and the determined HARQ process numbers.
  • the terminal device 110 may determine the HARQ process numbers of the M transmissions based on the DCI comprising an indication in HARQ process number field of a HARQ process number of a first transmission among the N transmissions or a first transmission among the M transmissions and additional information for determining the HARQ process numbers of the M transmissions.
  • the additional information may comprise N bits in new data indicator field. A value of each bit among the N bits may indicate whether a corresponding transmission among the N transmissions is scheduled to be retransmitted.
  • the DCI may further comprise an indication in first MSB bit in new data indicator field of whether the DCI is for scheduling SPS PDSCH or CG PUSCH retransmissions.
  • the DCI may comprise an indication of whether the DCI is for scheduling SPS PDSCH or CG PUSCH retransmissions, and an indication of whether one transmission or more than one transmission is scheduled in the DCI. In some embodiments, if more than one retransmission of SPS PDSCH or CG PUSCH are scheduled in the DCI, the terminal device 110 may determine that retransmissions of the N transmissions are scheduled in the DCI. In some embodiments, the terminal device 110 may determine HARQ process numbers of the N transmissions based on the DCI comprising an indication of a HARQ process number of a first transmission among the N transmissions. In some embodiments, the terminal device 110 may receive from the network device or transmit to the network device the retransmissions of the N transmissions based on the DCI and the determined HARQ process numbers of the N transmissions.
  • the terminal device 110 may receive the DCI for scheduling retransmissions of the M transmissions, wherein the M transmissions are consecutive transmissions with consecutive HARQ process numbers. In some embodiments, the terminal device 110 may receive a plurality of DCIs for scheduling retransmissions of the M transmissions respectively, wherein the M transmissions are nonconsecutive transmissions with nonconsecutive HARQ process numbers.
  • the terminal device 110 may determine the HARQ process numbers of the M transmissions based on the DCI comprising an indication of the number of scheduled M transmissions, an indication of a HARQ process number of a first transmission among the M transmissions, and an indication of additional information for determining HARQ process numbers of the M transmissions.
  • the DCI may further comprise an indication of whether the DCI is for scheduling SPS PDSCH or CG PUSCH retransmissions.
  • the DCI may comprise an indication in a HARQ process number indicator field of HARQ process numbers of the M transmissions.
  • FIG. 13 illustrates another example method 1300 of communication implemented at a terminal device in accordance with some embodiments of the present disclosure.
  • the method 1300 may be performed at the terminal device 110 as shown in FIG. 1.
  • the method 1300 will be described with reference to FIG. 1. It is to be understood that the method 1300 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.
  • the terminal device 110 receives, from a network device 120, a plurality of SPS PDSCH transmissions in a period for a SPS configuration.
  • the terminal device 110 determines a HARQ-ACK codebook comprising HARQ-ACK for the plurality of SPS PDSCH transmissions and HARQ-ACK for the at least one dynamic scheduled PDSCH transmission.
  • the terminal device 110 transmits the HARQ-ACK codebook to a network device in the PUCCH.
  • multiplexing HARQ-ACK information for multi-SPS PDSCHs in a period for SPS configuration and HARQ-ACK information for DG PDSCH (s) in a PUCCH may be supported, which is beneficial to improve the spectrum efficiency.
  • the HARQ-ACK codebook may be a Type-1 HARQ-ACK codebook.
  • the terminal device 110 may determine HARQ-ACK positions for the plurality of SPS PDSCH transmissions based on a start and length indicator value (SLIV) associated with each of the plurality of SPS PDSCH transmission, a slot offset indication between a last SPS PDSCH transmission among the plurality of SPS PDSCH transmissions and the PUCCH, and a slot offset between each of the plurality of SPS PDSCH transmissions and the last SPS PDSCH transmission.
  • SLIV start and length indicator value
  • the terminal device 110 may place HARQ-ACK positions for the plurality of SPS PDSCH transmissions before or after HARQ-ACK positions for the at least one dynamic scheduled PDSCH transmission.
  • bit order of the HARQ-ACK positions for the plurality of SPS PDSCH transmissions may be based on slot index of the plurality of SPS PDSCH transmissions.
  • the terminal device 110 may determine one HARQ-ACK position for the plurality of SPS PDSCH transmissions based on a start and length indicator value (SLIV) associated with a last SPS PDSCH transmission among the plurality of SPS PDSCH transmissions, and a slot offset indication between the last SPS PDSCH transmission and the PUCCH.
  • the HARQ-ACK position for the plurality of SPS PDSCH transmissions may be for reporting bundling HARQ-ACK for the plurality of SPS PDSCH transmissions.
  • the at least one dynamic scheduled PDSCH transmission may comprise one dynamic scheduled PDSCH transmission. If the terminal device is not configured to support a plurality of PDSCH transmissions dynamically scheduled in a PDCCH, the terminal device 110 may determine the HARQ-ACK codebook.
  • the HARQ-ACK codebook may be a Type-2 HARQ-ACK codebook. If the terminal device receives a plurality of PDSCH transmissions dynamically scheduled in a PDCCH from the network device and if the at least one dynamic scheduled PDSCH transmission comprises the plurality of PDSCH transmissions, the terminal device 110 may place HARQ-ACK positions for the plurality of SPS PDSCH transmissions after sub-codebook for multiple-PDSCH scheduling for the plurality of PDSCH transmissions.
  • the terminal device 110 may place HARQ-ACK positions for the plurality of SPS PDSCH transmissions after sub-codebook for single-PDSCH scheduling for the at least one dynamic scheduled PDSCH transmission.
  • bit order of the HARQ-ACK positions for the plurality of SPS PDSCH transmissions may be based on slot index of the plurality of SPS PDSCH transmissions.
  • FIG. 14 is a simplified block diagram of a device 1400 that is suitable for implementing embodiments of the present disclosure.
  • the device 1400 can be considered as a further example implementation of the terminal device 110 or the network device 120 as shown in FIG. 1. Accordingly, the device 1400 can be implemented at or as at least a part of the terminal device 110 or the network device 120.
  • the device 1400 includes a processor 1410, a memory 1420 coupled to the processor 1410, a suitable transmitter (TX) and receiver (RX) 1440 coupled to the processor 1410, and a communication interface coupled to the TX/RX 1440.
  • the memory 910 stores at least a part of a program 1430.
  • the TX/RX 1440 is for bidirectional communications.
  • the TX/RX 1440 has at least one antenna to facilitate communication, though in practice an Access Node mentioned in this application may have several ones.
  • the communication interface may represent any interface that is necessary for communication with other network elements, such as X2/Xn interface for bidirectional communications between eNBs/gNBs, S1/NG interface for communication between a Mobility Management Entity (MME) /Access and Mobility Management Function (AMF) /SGW/UPF and the eNB/gNB, Un interface for communication between the eNB/gNB and a relay node (RN) , or Uu interface for communication between the eNB/gNB and a terminal device.
  • MME Mobility Management Entity
  • AMF Access and Mobility Management Function
  • RN relay node
  • Uu interface for communication between the eNB/gNB and a terminal device.
  • the program 1430 is assumed to include program instructions that, when executed by the associated processor 1410, enable the device 1400 to operate in accordance with the embodiments of the present disclosure, as discussed herein with reference to FIGs. 1 to 9.
  • the embodiments herein may be implemented by computer software executable by the processor 1410 of the device 1400, or by hardware, or by a combination of software and hardware.
  • the processor 1410 may be configured to implement various embodiments of the present disclosure.
  • a combination of the processor 1410 and memory 1420 may form processing means 1450 adapted to implement various embodiments of the present disclosure.
  • the memory 1420 may be of any type suitable to the local technical network and may be implemented using any suitable data storage technology, such as a non-transitory computer readable storage medium, semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. While only one memory 1420 is shown in the device 1400, there may be several physically distinct memory modules in the device 1400.
  • the processor 1410 may be of any type suitable to the local technical network, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.
  • the device 1400 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
  • a network device comprises circuitry configured to perform method 1000. In some embodiments, a network device comprises circuitry configured to perform method 1100. In some embodiments, a terminal device comprises circuitry configured to perform method 1200. In some embodiments, a terminal device comprises circuitry configured to perform method 1300.
  • the components included in the apparatuses and/or devices of the present disclosure may be implemented in various manners, including software, hardware, firmware, or any combination thereof.
  • one or more units may be implemented using software and/or firmware, for example, machine-executable instructions stored on the storage medium.
  • parts or all of the units in the apparatuses and/or devices may be implemented, at least in part, by one or more hardware logic components.
  • FPGAs Field-programmable Gate Arrays
  • ASICs Application-specific Integrated Circuits
  • ASSPs Application-specific Standard Products
  • SOCs System-on-a-chip systems
  • CPLDs Complex Programmable Logic Devices
  • circuitry used herein may refer to hardware circuits and/or combinations of hardware circuits and software.
  • the circuitry may be a combination of analog and/or digital hardware circuits with software/firmware.
  • the circuitry may be any portions of hardware processors with software including digital signal processor (s) , software, and memory (ies) that work together to cause an apparatus, such as a terminal device or a network device, to perform various functions.
  • the circuitry may be hardware circuits and or processors, such as a microprocessor or a portion of a microprocessor, that requires software/firmware for operation, but the software may not be present when it is not needed for operation.
  • the term circuitry also covers an implementation of merely a hardware circuit or processor (s) or a portion of a hardware circuit or processor (s) and its (or their) accompanying software and/or firmware.
  • various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representation, it will be appreciated that the blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
  • the present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium.
  • the computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the process or method as described above with reference to FIGs. 1 to 9.
  • program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types.
  • the functionality of the program modules may be combined or split between program modules as desired in various embodiments.
  • Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
  • Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented.
  • the program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
  • the above program code may be embodied on a machine readable medium, which may be any tangible medium that may contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
  • the machine readable medium may be a machine readable signal medium or a machine readable storage medium.
  • a machine readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
  • machine readable storage medium More specific examples of the machine readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
  • RAM random access memory
  • ROM read-only memory
  • EPROM or Flash memory erasable programmable read-only memory
  • CD-ROM portable compact disc read-only memory
  • magnetic storage device or any suitable combination of the foregoing.
  • embodiments of the present disclosure may provide the following solutions.
  • a method of communication comprises: transmitting to a terminal device or receiving from the terminal device, at a network device, N transmissions for a set of different transport blocks (TBs) in a period for a semi-persistent scheduling (SPS) configuration or a configured grant (CG) configuration, wherein N>1; and in accordance with failure of M transmissions among the N transmissions in the period, transmitting, to the terminal device, downlink control information (DCI) in a physical downlink control channel (PDCCH) with CRC scrambled by CS-RNTI for scheduling retransmissions of the M transmissions, wherein 1 ⁇ M ⁇ N.
  • DCI downlink control information
  • PDCCH physical downlink control channel
  • the method as above further comprises: transmitting control information to the terminal device, the control information indicating the SPS configuration with N SPS physical downlink shared channel (PDSCH) occasions for data transmission per periodicity or indicating the CG configuration with N CG physical uplink shared channel (PUSCH) occasions for data transmission per periodicity.
  • PDSCH physical downlink shared channel
  • PUSCH physical uplink shared channel
  • the DCI comprises: an indication of a hybrid automatic repeat request (HARQ) process number of a first transmission among the N transmissions or a first transmission among the M transmissions.
  • HARQ hybrid automatic repeat request
  • the DCI further comprises: additional information for determining HARQ process numbers of the M transmissions.
  • the additional information comprises N bits, a value of each bit among the N bits indicating whether a corresponding transmission among the N transmissions is scheduled to be retransmitted.
  • the DCI further comprises: an indication of whether the DCI is for scheduling SPS PDSCH or CG PUSCH retransmissions.
  • transmitting the DCI comprises: in accordance with determining that M >1, transmitting the DCI for scheduling retransmissions of the N transmissions.
  • the DCI comprises: an indication of whether the DCI is for scheduling SPS PDSCH or CG PUSCH retransmissions, an indication of whether one transmission or more than one transmission is scheduled in the DCI, and an indication of a HARQ process number of a first transmission among the N transmissions.
  • transmitting the DCI comprises: in accordance with a determination that the M transmissions are consecutive transmissions with consecutive HARQ process numbers, transmitting the DCI for scheduling retransmissions of the M transmissions.
  • the method as above further comprises: in accordance with failure of the M transmissions among the N transmissions in the period and a determination that the M transmissions are nonconsecutive transmissions with nonconsecutive HARQ process numbers, transmitting a plurality of DCIs for scheduling retransmissions of the M transmissions respectively.
  • the DCI comprises: an indication of whether the DCI is for scheduling SPS PDSCH or CG PUSCH retransmissions, an indication of the number of scheduled M transmissions, an indication of a HARQ process number of a first transmission among the M transmissions, and an indication of additional information for determining HARQ process numbers of the M transmissions.
  • the DCI comprises: an indication in a HARQ process number indicator field of HARQ process numbers of the M transmissions.
  • a method of communication comprises: transmitting, at a network device and to a terminal device, a plurality of semi-persistent scheduling physical downlink shared channel (SPS PDSCH) transmissions in a period for a SPS configuration; receiving, from the terminal device, a hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook in a physical uplink control channel (PUCCH) , the HARQ-ACK codebook comprising HARQ-ACK for the plurality of SPS PDSCH transmissions; and in accordance with a determination that HARQ-ACK for the plurality of SPS PDSCH transmissions is multiplexed with HARQ-ACK for at least one dynamic scheduled PDSCH transmission in the PUCCH, determining HARQ-ACK positions for the plurality of SPS PDSCH transmissions in the HARQ-ACK codebook.
  • SPS PDSCH semi-persistent scheduling physical downlink shared channel
  • the HARQ-ACK codebook is a Type-1 HARQ-ACK codebook.
  • determining the HARQ-ACK positions for the plurality of SPS PDSCH transmissions comprises: in accordance with a determination that the terminal device is configured to support a plurality of PDSCH transmissions dynamically scheduled in a physical downlink control channel (PDCCH) , determining HARQ-ACK positions for the plurality of SPS PDSCH transmissions based on: a start and length indicator value (SLIV) associated with each of the plurality of SPS PDSCH transmissions, a slot offset between a last or a first SPS PDSCH transmission among the plurality of SPS PDSCH transmissions and the PUCCH, and a slot offset between each of the plurality of SPS PDSCH transmissions and the last or first SPS PDSCH transmission.
  • SLIV start and length indicator value
  • the HARQ-ACK positions for the plurality of SPS PDSCH transmissions are placed before or after HARQ-ACK positions for the at least one dynamic scheduled PDSCH transmission.
  • bit order of the HARQ-ACK positions for the plurality of SPS PDSCH transmissions is based on slot index of the plurality of SPS PDSCH transmissions.
  • determining the HARQ-ACK positions for the plurality of SPS PDSCH transmissions comprises: determining one HARQ-ACK position for the plurality of SPS PDSCH transmissions based on: a start and length indicator value (SLIV) associated with a last or first SPS PDSCH transmission among the plurality of SPS PDSCH transmissions, and a slot offset indication between the last or first SPS PDSCH transmission and the PUCCH.
  • SLIV start and length indicator value
  • the HARQ-ACK position for the plurality of SPS PDSCH transmissions is for reporting bundling HARQ-ACK for the plurality of SPS PDSCH transmissions.
  • the at least one dynamic scheduled PDSCH transmission comprises one dynamic scheduled PDSCH transmission
  • determining the HARQ-ACK positions for the plurality of SPS PDSCH transmissions comprises: in accordance with a determination that the terminal device is not configured to support a plurality of PDSCH transmissions dynamically scheduled in a PDCCH, determining the HARQ-ACK positions for the plurality of SPS PDSCH transmissions and reporting HARQ-ACK information for the plurality of SPS PDSCH transmissions on the HARQ-ACK positions.
  • the HARQ-ACK codebook is a Type-2 HARQ-ACK codebook
  • determining the HARQ-ACK positions for the plurality of SPS PDSCH transmissions comprises: in accordance with a determination that the network device transmits a plurality of PDSCH transmissions dynamically scheduled in a PDCCH to the terminal device and that the at least one dynamic scheduled PDSCH transmission comprises the plurality of PDSCH transmissions, determining that the HARQ-ACK positions for the plurality of SPS PDSCH transmissions are placed after sub-codebook for multiple-PDSCH scheduling for the plurality of PDSCH transmissions; and in accordance with a determination that the terminal device is configured to support a plurality of PDSCH transmissions dynamically scheduled in a PDCCH and that the at least one dynamic scheduled PDSCH transmission does not comprise the plurality of PDSCH transmissions dynamically scheduled in a PDCCH, determining that the HARQ-ACK positions for the plurality of SPS PDSCH transmissions are placed after sub-codebook for
  • bit order of the HARQ-ACK positions for the plurality of SPS PDSCH transmissions is based on slot index of the plurality of SPS PDSCH transmissions.
  • a method of communication comprises: receiving from a network device or transmitting to the network device, at a terminal device, N transmissions for a set of different transport blocks (TBs) in a period for a semi-persistent scheduling (SPS) configuration or a configured grant (CG) configuration, wherein N>1; receiving, from the network device, downlink control information (DCI) in a physical downlink control channel (PDCCH) with CRC scrambled by CS-RNTI for scheduling retransmissions of M transmissions among N transmissions in the period, wherein 1 ⁇ M ⁇ N; and determining hybrid automatic repeat request (HARQ) process numbers of the M transmissions based on the DCI.
  • DCI downlink control information
  • PDCCH physical downlink control channel
  • HARQ hybrid automatic repeat request
  • the method as above further comprises: receiving control information from the network device, the control information indicating the SPS configuration with N SPS physical downlink shared channel (PDSCH) occasions for data transmission per periodicity or the CG configuration with N CG physical uplink shared channel (PUSCH) occasions for data transmission per periodicity.
  • PDSCH physical downlink shared channel
  • PUSCH physical uplink shared channel
  • the method as above further comprises: receiving from the network device or transmitting to the network device the retransmissions of the M transmissions based on the DCI and the determined HARQ process numbers.
  • determining the HARQ process numbers of the M transmissions comprises: determining the HARQ process numbers of the M transmissions based on the DCI comprising an indication in HARQ process number field of a HARQ process number of a first transmission among the N transmissions or a first transmission among the M transmissions and additional information for determining the HARQ process numbers of the M transmissions.
  • the additional information comprises N bits in new data indicator field, a value of each bit among the N bits indicating whether a corresponding transmission among the N transmissions is scheduled to be retransmitted.
  • the DCI further comprises: an indication in first MSB bit in new data indicator field of whether the DCI is for scheduling SPS PDSCH or CG PUSCH retransmissions.
  • the DCI comprises: an indication of whether the DCI is for scheduling SPS PDSCH or CG PUSCH retransmissions, and an indication of whether one transmission or more than one transmission is scheduled in the DCI.
  • the method as above further comprises: in accordance with determining that more than one retransmission of SPS PDSCH or CG PUSCH are scheduled in the DCI, determining that retransmissions of the N transmissions are scheduled in the DCI.
  • determining the HARQ process numbers of the M transmissions comprises: determining HARQ process numbers of the N transmissions based on the DCI comprising an indication of a HARQ process number of a first transmission among the N transmissions.
  • the method as above further comprises: receiving from the network device or transmitting to the network device the retransmissions of the N transmissions based on the DCI and the determined HARQ process numbers of the N transmissions.
  • the method as above further comprises: receiving from the network device or transmitting to the network device the retransmissions of the M transmissions based on the DCI and the determined HARQ process numbers of the M transmissions.
  • receiving the DCI comprises: receiving the DCI for scheduling retransmissions of the M transmissions, the M transmissions being consecutive transmissions with consecutive HARQ process numbers.
  • the method as above further comprises: receiving a plurality of DCIs for scheduling retransmissions of the M transmissions respectively, the M transmissions being nonconsecutive transmissions with nonconsecutive HARQ process numbers.
  • determining the HARQ process numbers of the M transmissions comprises: determining the HARQ process numbers of the M transmissions based on the DCI comprising: an indication of the number of scheduled M transmissions, an indication of a HARQ process number of a first transmission among the M transmissions, and an indication of additional information for determining HARQ process numbers of the M transmissions.
  • the DCI further comprises: an indication of whether the DCI is for scheduling SPS PDSCH or CG PUSCH retransmissions.
  • the DCI comprises: an indication in HARQ process number field of HARQ process numbers of the M transmissions.
  • a method of communication comprises: receiving, at a terminal device and from a network device, a plurality of semi-persistent scheduling physical downlink shared channel (SPS PDSCH) transmissions in a period for a SPS configuration; in accordance with a determination that HARQ-ACK for the plurality of SPS PDSCH transmissions is multiplexed with HARQ-ACK for at least one dynamic scheduled data transmissions in a physical uplink control channel (PUCCH) , determining a HARQ-ACK codebook comprising HARQ-ACK for the plurality of SPS PDSCH transmissions and HARQ-ACK for the at least one dynamic scheduled PDSCH transmission; and transmitting the HARQ-ACK codebook to a network device in the PUCCH.
  • SPS PDSCH semi-persistent scheduling physical downlink shared channel
  • the HARQ-ACK codebook is a Type-1 HARQ-ACK codebook.
  • determining the HARQ-ACK codebook comprises: in accordance with a determination that the terminal device is configured to support a plurality of PDSCH transmissions dynamically scheduled in a physical downlink control channel (PDCCH) , determining HARQ-ACK positions for the plurality of SPS PDSCH transmissions based on: a start and length indicator value (SLIV) associated with each of the plurality of SPS PDSCH transmission, a slot offset indication between a last SPS PDSCH transmission among the plurality of SPS PDSCH transmissions and the PUCCH, and a slot offset between each of the plurality of SPS PDSCH transmissions and the last SPS PDSCH transmission.
  • SLIV start and length indicator value
  • determining the HARQ-ACK codebook comprises: placing HARQ-ACK positions for the plurality of SPS PDSCH transmissions before or after HARQ-ACK positions for the at least one dynamic scheduled PDSCH transmission.
  • bit order of the HARQ-ACK positions for the plurality of SPS PDSCH transmissions is based on slot index of the plurality of SPS PDSCH transmissions.
  • determining the HARQ-ACK codebook comprises: determining one HARQ-ACK position for the plurality of SPS PDSCH transmissions based on:a start and length indicator value (SLIV) associated with a last SPS PDSCH transmission among the plurality of SPS PDSCH transmissions, and a slot offset indication between the last SPS PDSCH transmission among the plurality of SPS PDSCH transmissions and the PUCCH.
  • SLIV start and length indicator value
  • the HARQ-ACK position for the plurality of SPS PDSCH transmissions is for reporting bundling HARQ-ACK for the plurality of SPS PDSCH transmissions.
  • the at least one dynamic scheduled PDSCH transmission comprises one dynamic scheduled PDSCH transmission
  • determining the HARQ-ACK codebook comprises: in accordance with a determination that the terminal device is not configured to support a plurality of PDSCH transmissions dynamically scheduled in a PDCCH, determining the HARQ-ACK codebook.
  • the HARQ-ACK codebook is a Type-2 HARQ-ACK codebook
  • determining the HARQ-ACK codebook comprises: in accordance with a determination that the terminal device receives a plurality of PDSCH transmissions dynamically scheduled in a PDCCH from the network device and that the at least one dynamic scheduled PDSCH transmission comprises the plurality of PDSCH transmissions, placing HARQ-ACK positions for the plurality of SPS PDSCH transmissions after sub-codebook for multiple-PDSCH scheduling for the plurality of PDSCH transmissions; and in accordance with a determination that the terminal device is configured to support a plurality of PDSCH transmissions dynamically scheduled in a PDCCH and that the at least one dynamic scheduled PDSCH transmission does not comprise the plurality of PDSCH transmissions dynamically scheduled in a PDCCH, placing HARQ-ACK positions for the plurality of SPS PDSCH transmissions after sub-codebook for single-PDSCH scheduling for the at least one dynamic scheduled PDSCH transmission.
  • bit order of the HARQ-ACK positions for the plurality of SPS PDSCH transmissions is based on slot index of the plurality of SPS PDSCH transmissions.
  • a network device comprising: a processor; and a memory coupled to the processor and storing instructions thereon, the instructions, when executed by the processor, causing the second network device to perform acts comprising the method according to any of the above embodiments.
  • a terminal device comprises: a processor; and a memory coupled to the processor and storing instructions thereon, the instructions, when executed by the processor, causing the terminal device to perform acts comprising the method according to any of the above embodiments.
  • a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to perform the method according to any of the above embodiments.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des modes de réalisation de la présente divulgation concernent des procédés, des dispositifs et des supports lisibles par ordinateur de communication. Un dispositif de réseau transmet à un dispositif terminal ou reçoit du dispositif terminal, au niveau d'un dispositif de réseau, N transmissions pour un ensemble de TB différents dans une période pour une configuration SPS ou une configuration CG, avec N > 1. Conformément à une défaillance de M transmissions parmi les N transmissions dans la période, le dispositif de réseau transmet, au dispositif terminal, une DCI dans un PDCCH avec CRC brouillé par CS-RNTI pour programmer des retransmissions des M transmissions, avec 1 ≤ M ≤ N. De cette manière, l'efficacité de spectre peut être améliorée.
PCT/CN2022/105483 2022-07-13 2022-07-13 Procédé, dispositif et support de stockage informatique de communication WO2024011453A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/105483 WO2024011453A1 (fr) 2022-07-13 2022-07-13 Procédé, dispositif et support de stockage informatique de communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/105483 WO2024011453A1 (fr) 2022-07-13 2022-07-13 Procédé, dispositif et support de stockage informatique de communication

Publications (1)

Publication Number Publication Date
WO2024011453A1 true WO2024011453A1 (fr) 2024-01-18

Family

ID=89535296

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/105483 WO2024011453A1 (fr) 2022-07-13 2022-07-13 Procédé, dispositif et support de stockage informatique de communication

Country Status (1)

Country Link
WO (1) WO2024011453A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020263490A1 (fr) * 2019-06-28 2020-12-30 Qualcomm Incorporated Techniques de signalisation d'un faisceau pour des communications périodiques
US20210250973A1 (en) * 2018-09-26 2021-08-12 Apple Inc. Enhanced hybrid automatic retransmission request (harq) for semi-persistent scheduled (sps) data transmission
CN114008964A (zh) * 2021-09-24 2022-02-01 北京小米移动软件有限公司 Mbs业务中sps对应hpn的确定方法及其装置
CN114499771A (zh) * 2020-11-13 2022-05-13 成都鼎桥通信技术有限公司 Mbs的ack/nack信息的反馈与重传方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210250973A1 (en) * 2018-09-26 2021-08-12 Apple Inc. Enhanced hybrid automatic retransmission request (harq) for semi-persistent scheduled (sps) data transmission
WO2020263490A1 (fr) * 2019-06-28 2020-12-30 Qualcomm Incorporated Techniques de signalisation d'un faisceau pour des communications périodiques
CN114499771A (zh) * 2020-11-13 2022-05-13 成都鼎桥通信技术有限公司 Mbs的ack/nack信息的反馈与重传方法和装置
CN114008964A (zh) * 2021-09-24 2022-02-01 北京小米移动软件有限公司 Mbs业务中sps对应hpn的确定方法及其装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ZTE: "Consideration on scheduling enhancement for NB-IoT", 3GPP TSG RAN WG1 MEETING #94 R1- 1808642, 24 August 2018 (2018-08-24), XP051516018 *

Similar Documents

Publication Publication Date Title
WO2021007862A1 (fr) Rapport de rétroaction harq dans une transmission de liaison latérale
AU2019451382B2 (en) Report of HARQ feedback in sidelink transmission
WO2023184273A1 (fr) Procédé, dispositif, et support de stockage informatique destinés à la communication
WO2023044912A1 (fr) Procédé, dispositif et support de stockage informatique pour la communication
WO2022217606A1 (fr) Procédés de communication, dispositif terminal, dispositif réseau et supports lisibles par ordinateur
WO2024011453A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2022027645A1 (fr) Support lisible par ordinateur, procédés, et dispositifs de communication
WO2022141647A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2023056629A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2024065771A1 (fr) Procédés, dispositifs et support de communication
WO2024031591A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2023245510A1 (fr) Procédés, dispositifs et support de communication
WO2024007314A1 (fr) Procédés, dispositifs et support destinés aux communications
WO2023150981A1 (fr) Procédés, dispositifs, et support lisible par ordinateur pour des communications
WO2023272723A1 (fr) Procédé, dispositif et support de stockage informatique de communication
US20240146468A1 (en) Method, device and computer storage medium of communication
WO2023019439A1 (fr) Procédés, dispositifs, et support lisible par ordinateur de communication
WO2023115349A1 (fr) Procédés, dispositifs, et support lisible par ordinateur de communication
WO2022095037A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2023050077A1 (fr) Procédés, dispositifs et support lisible par ordinateur pour des communications
WO2023236211A1 (fr) Procédés, dispositifs et support de communication
WO2024044907A1 (fr) Procédés, dispositifs et support lisible par ordinateur destiné aux communications
WO2023245669A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2022205451A1 (fr) Procédé, dispositif et support lisible par ordinateur pour la communication
WO2023184354A1 (fr) Retransmissions harq pour rétroaction harq

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: 22950579

Country of ref document: EP

Kind code of ref document: A1