WO2023150981A1 - Procédés, dispositifs, et support lisible par ordinateur pour des communications - Google Patents

Procédés, dispositifs, et support lisible par ordinateur pour des communications Download PDF

Info

Publication number
WO2023150981A1
WO2023150981A1 PCT/CN2022/075917 CN2022075917W WO2023150981A1 WO 2023150981 A1 WO2023150981 A1 WO 2023150981A1 CN 2022075917 W CN2022075917 W CN 2022075917W WO 2023150981 A1 WO2023150981 A1 WO 2023150981A1
Authority
WO
WIPO (PCT)
Prior art keywords
tbs
cyclic shift
shift value
combination
mapped
Prior art date
Application number
PCT/CN2022/075917
Other languages
English (en)
Inventor
Gang Wang
Yukai GAO
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/075917 priority Critical patent/WO2023150981A1/fr
Publication of WO2023150981A1 publication Critical patent/WO2023150981A1/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/1829—Arrangements specially adapted for the receiver end
    • H04L1/1861—Physical mapping arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1896—ARQ related signaling
    • 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
    • H04L2001/0092—Error control systems characterised by the topology of the transmission link
    • H04L2001/0093—Point-to-multipoint
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK

Definitions

  • Embodiments of the present disclosure generally relate to the field of telecommunication, and in particular, to methods, devices, and computer readable medium for communication.
  • HARQ Hybrid Automatic Repeat Request
  • a receiver transmits HARQ feedback information to a transmitter to indicate whether a data transmission from the transmitter is detected successfully. Then, a transmitter performs a new transmission or a retransmission depending on whether the HARQ feedback indicates the data transmission is successfully detected or not.
  • a terminal device can support a Multicast and Broadcast Service (MBS) in addition to a unicast service with a network device.
  • MBS Multicast and Broadcast Service
  • a terminal device may be configured into one or more multicast groups of terminal devices, and a network device may transmit one or more transport blocks (TBs) to a multicast group of terminal devices.
  • TBs transport blocks
  • example embodiments of the present disclosure provide a solution for communication.
  • a communication method comprises: determining, at a terminal device, that a negative acknowledgment (NACK) feedback is to be transmitted for at least one of a set of transport blocks (TBs) transmitted from a network device; selecting, from a mapping table associated with the set of TBs, a cyclic shift value mapped to a combination of the at least one TB; generating a sequence at least based on the selected cyclic shift value; and transmitting, to the network device, the NACK feedback for the at least one TB using the generated sequence.
  • NACK negative acknowledgment
  • a communication method comprises: transmitting, at a network device, a set of transport blocks (TBs) to at least one multicast group of terminal devices; receiving, from a terminal device, a negative acknowledgment (NACK) feedback using a sequence, the terminal device being comprised in the at least one multicast group; decoding the sequence to obtain at least a cyclic shift value used for generating the sequence; determining, from a mapping table associated with the set of TBs, a combination of at least one TB mapped to the cyclic shift value; determining that the NACK feedback is for the at least one TB.
  • NACK negative acknowledgment
  • a terminal device comprising a processing unit; and a memory coupled to the processing unit and storing instructions thereon, the instructions, when executed by the processing unit, causing the terminal device to perform the method according to the first aspect.
  • a network device comprising a processing unit; and a memory coupled to the processing unit and storing instructions thereon, the instructions, when executed by the processing unit, causing the network device to perform the method according to the second aspect.
  • 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 the first aspect.
  • 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 the third aspect.
  • Fig. 1 is a schematic diagram of a communication system in which embodiments of the present disclosure can be implemented
  • Fig. 2 illustrates a signaling flow for communications in accordance with some embodiments of the present disclosure
  • Fig. 3A illustrates an example scenario of TB transmission for terminal devices included in a multicast group in accordance with some embodiments of the present disclosure
  • Fig. 3B illustrates an example scenario of TB transmission for terminal devices included in a multicast group in accordance with some other embodiments of the present disclosure
  • Fig. 4 illustrates a further example scenario of TB transmission for terminal devices included in a multicast group in accordance with some embodiments of the present disclosure
  • Fig. 5 is a flowchart of an example method implemented at a terminal device in accordance with some embodiments of the present disclosure
  • Fig. 6 is a flowchart of an example method implemented at a network device in accordance with some embodiments of the present disclosure.
  • Fig. 7 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.
  • the terms “terminal device” , “communication device” , “terminal” , “user equipment” and “UE” may be used interchangeably.
  • 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 –7125 MHz) , FR2 (24.25GHz to 71GHz) , frequency band above 71 GHz, frequency band larger than 100GHz as well as Terahertz (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 and 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.
  • Communications discussed herein may use conform to any suitable standards including, but not limited to, New Radio Access (NR) , Long Term Evolution (LTE) , LTE-Evolution, LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , Code Division Multiple Access (CDMA) , cdma2000, and Global System for Mobile Communications (GSM) and the like.
  • NR New Radio Access
  • LTE Long Term Evolution
  • LTE-Evolution LTE-Advanced
  • LTE-A LTE-Advanced
  • WCDMA Wideband Code Division Multiple Access
  • CDMA Code Division Multiple Access
  • GSM Global System for Mobile Communications
  • Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.85G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) , and the sixth (6G) communication protocols.
  • the techniques described herein may be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies.
  • 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.
  • 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.
  • 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.
  • Fig. 1 illustrates a schematic diagram of a communication system in which embodiments of the present disclosure can be implemented.
  • the communication system 100 which is a part of a communication network, comprises a terminal device 110-1, a terminal device 110-2, a terminal device 110-3, ..., a terminal device 110-N, which can be collectively or individually referred to as “terminal device (s) 110. ”
  • the number N can be any suitable integer number.
  • the numbers of terminal devices shown in Fig. 1 are given for the purpose of illustration without suggesting any limitations.
  • the communication system 100 further comprises a network device 120.
  • the network device 120 and the terminal devices 110 can communicate data and control information with each other.
  • a link from the network device 120 to a terminal device 110 is referred to as a downlink (DL)
  • a link from a terminal device 110 to the network device 120 is referred to as an uplink (UL) .
  • the network device 120 is a transmitting (TX) device (or a transmitter) and the terminal device 110 is a receiving (RX) device (or a receiver) .
  • TX transmitting
  • RX receiving
  • the terminal device 110 is a TX device (or a transmitter) and the network device 120 is a RX device (or a receiver) .
  • Communications in the communication system 100 may be implemented according to any proper communication protocol (s) , comprising, but not limited to, cellular communication protocols of the first generation (1G) , the second generation (2G) , the third generation (3G) , the fourth generation (4G) and the fifth generation (5G) and on the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and/or any other protocols currently known or to be developed in the future.
  • s cellular communication protocols of the first generation (1G) , the second generation (2G) , the third generation (3G) , the fourth generation (4G) and the fifth generation (5G) and on the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and/or any other protocols currently known or to be developed in the future.
  • IEEE Institute for Electrical and Electronics Engineers
  • the communication may utilize any proper wireless communication technology, comprising but not limited to: Code Divided Multiple Address (CDMA) , Frequency Divided Multiple Address (FDMA) , Time Divided Multiple Address (TDMA) , Frequency Divided Duplexer (FDD) , Time Divided Duplexer (TDD) , Multiple-Input Multiple-Output (MIMO) , Orthogonal Frequency Divided Multiple Access (OFDMA) and/or any other technologies currently known or to be developed in the future.
  • CDMA Code Divided Multiple Address
  • FDMA Frequency Divided Multiple Address
  • TDMA Time Divided Multiple Address
  • FDD Frequency Divided Duplexer
  • TDD Time Divided Duplexer
  • MIMO Multiple-Input Multiple-Output
  • OFDMA Orthogonal Frequency Divided Multiple Access
  • Embodiments of the present disclosure can be applied to any suitable scenarios.
  • embodiments of the present disclosure can be implemented at reduced capability NR devices.
  • embodiments of the present disclosure can be implemented in one of the followings: NR multiple-input and multiple-output (MIMO) , NR sidelink enhancements, NR systems with frequency above 52.6GHz, an extending NR operation up to 71GHz, narrow band-Internet of Thing (NB-IOT) /enhanced Machine Type Communication (eMTC) over non-terrestrial networks (NTN) , NTN, UE power saving enhancements, NR coverage enhancement, NB-IoT and LTE-MTC, Integrated Access and Backhaul (IAB) , NR Multicast and Broadcast Services, or enhancements on Multi-Radio Dual-Connectivity.
  • MIMO multiple-input and multiple-output
  • NR sidelink enhancements NR systems with frequency above 52.6GHz, an extending NR operation up to 71GHz
  • NB-IOT narrow band-Internet of
  • slot refers to a dynamic scheduling unit.
  • One slot comprises a predetermined number of symbols.
  • the slot used herein may refer to a normal slot which comprises a predetermined number of symbols and also refer to a sub-slot which comprises fewer symbols than the predetermined number of symbols.
  • a terminal device 110 supports a unicast service and/or Multicast and Broadcast Service (MBS) with the network device 120.
  • MMS Multicast and Broadcast Service
  • the network device 120 may communicate with the terminal device 110 using a certain DL resource.
  • the communication from the network device 120 may occur in a certain DL resource, such as a Physical Downlink Shared Channel (PDSCH) occasion, and the corresponding reception at the terminal device 110 may be referred to as a candidate PDSCH reception for a unicast service.
  • a PDSCH reception may also be referred to as a Group Common-PDSCH (GC-PDSCH) .
  • GC-PDSCH Group Common-PDSCH
  • MBS may include a multicast service and a broadcast service.
  • a multicast service one or more multicast groups may be configured, each group comprising one or more than one terminal device 110.
  • the terminal devices 110-1 and 110-2 may be included in a multicast group 130-1
  • the terminal devices 110-2, and 110-3 may be included in a multicast group 130-2
  • the terminal devices 110-3 and 110-N may be included in a multicast group 130-3
  • the terminal device 110-N and possibly other terminal devices may be included in a multicast group 130-4.
  • the multicast groups 130-1, 130-2, 130-3, 130-4 may be collectively or individually referred to as “multicast group (s) 130. ”
  • a terminal device 110 may be involved in two or more multicast groups for different multicast services.
  • the terminal device 110-2 is included in both the multicast groups 130-1 and 130-2
  • the terminal device 110-3 is included in both the multicast groups 130-2 and 130-3.
  • the network device 120 may communicate the same data with the terminal device (s) 110 in a same multicast group 130 using a certain DL resource.
  • the data transmission from the network device 120 may occur in a certain DL resource, such as a PDSCH occasion, and the corresponding reception at the terminal device 110 may be referred to as a PDSCH reception for a multicast service.
  • the data transmission may include one or more transport blocks (TBs) .
  • the network device 120 may transmit one or more TBs to the terminal device (s) 110 included therein.
  • the network device 120 may transmit the same or different TBs to the terminal devices 110 included other multicast groups 130 using corresponding DL resources.
  • a TB (s) addressed to one multicast group may be scheduled over a channel, e.g., a Physical Downlink Control Channel (PDCCH) scrambled with a specific Group-Radio Network Temporary Identity (G-RNTI) .
  • a multicast group of terminal devices may be configured with a G-RNTI.
  • Each terminal device 110 comprised in the multicast group may be configured with the G-RNTI to de-scramble the data transmitted by the network device 120 to the multicast group.
  • the terminal device 110 may be configured with a plurality of G-RNTIs for the plurality of multicast groups.
  • a Hybrid Automatic Repeat Request (HARQ) mechanism is applied in data communication between the network device 120 and the terminal devices 110.
  • a receiver e.g., the terminal device 110
  • may transmit a HARQ feedback to a transmitter e.g., the network device 120
  • the transmitter may decide whether to perform a new transmission or a retransmission.
  • the HARQ feedback may be conveyed using a sequence and transmitted over a Physical Uplink Control Channel (PUCCH) .
  • the sequence is generated for a certain PUCCH format, including PUCCH format 0, PUCCH format 1, PUCCH format 1a, PUCCH format 1b, PUCCH format 2, PUCCH format 3, PUCCH format 4, and so on.
  • PUCCH format may include sequences carrying a certain number of information bits.
  • both a positive acknowledgement (ACK) /negative acknowledgement (NACK) based feedback mode and a NACK-only based feedback mode may be configured per G-RNTI (or per multicast group) .
  • ACK/NACK based feedback mode a terminal device 110 may transmit an ACK feedback to the network device 120 if a TB from the network device is detected correctly, and transmit a NACK feedback if a TB is not correctly detected or missed.
  • the terminal device 110 may transmit a NACK feedback only if a TB is not correctly detected or missed, and do not transmit an ACK feedback if all TBs are correctly detected.
  • the NACK-only based feedback mode it is still pending about how to transmit the NACK feedback for various combinations of TBs which are not correctly detected or missed.
  • the NACK-only based feedback may apply for certain PUCCH formats that can carry a limit number of information bits, such as PUCCH format 0 and PUCCH format 1 (which can carry no more than 2 bits) . If the current mechanism is directly applied, the terminal device 110 may only be able to transmit NACK-only feedbacks for the combinations of up to two TBs within a slot.
  • a terminal device determines that a negative acknowledgment (NACK) feedback is to be transmitted for at least one of a set of transport blocks (TBs) transmitted from a network device.
  • the terminal device selects, from a mapping table associated with the set of TBs, a cyclic shift value (and/or an OCC) mapped to a combination of the at least one TB (s)
  • the mapping table may indicate a mapping between different cyclic shift values (and/or different OCCs) and different combinations of TBs among the set of TBs.
  • the terminal device generates a sequence at least based on the selected cyclic shift value (and/or the selected OCC) and transmits, to the network device, the NACK feedback for the at least one TB using the generated sequence.
  • the network device transmits a set of transport blocks (TBs) to at least one multicast group of terminal devices, and receives, from a terminal device, a negative acknowledgment (NACK) feedback using a sequence, the terminal device being comprised in the at least one multicast group.
  • the network device decodes the sequence to obtain at least a cyclic shift value (and/or a OCC) used for generating the sequence; determining, from a mapping table associated with the set of TBs, a combination of at least one TB (s) mapped to the cyclic shift value (and/or the OCC) .
  • the mapping table may indicate a mapping between different cyclic shift values (and/or different OCCs) and different combinations of TBs among the set of TBs.
  • the network device determines that the NACK feedback is for the at least one TB (s) .
  • NACK feedbacks for different combinations of TBs may be transmitted by the terminal device and identified by the network device.
  • Fig. 2 shows a signaling flow 200 for communications between a terminal device and a network device according to those embodiments of the present disclosure.
  • the signaling flow 200 may involve a terminal device 110 and the network device 120 in Fig. 1. Any of the terminal devices 110 in the environment 100 that supports multicast communication can be involved in the signaling flow 200.
  • the terminal device 110 involved in the signaling flow 200 may be comprised in one or more of the multicast groups 130.
  • the terminal device 110 is configured with NACK-only feedback for HARQ communication with the network device. It is proposed to configure a mapping table for a set of TBs to be transmitted from the network device 120 to the terminal device 110.
  • the mapping table indicates a mapping between different combinations of the set of TBs and one or more parameter values used to generate sequences for conveying a NACK feedback.
  • Each of the different combinations of the TBs comprises one or more of TBs.
  • the terminal device 110 can select the mapped parameter value (s) to generate a sequence to indicate the NACK feedback.
  • the network device 120 decodes the corresponding parameter value (s) from the received sequence and thus determines that a NACK feedback is for the combination of TBs.
  • different parameter values used in generating the sequence are utilized to indicate the TB (s) for which the NACK feedback is transmitted by the terminal device 110.
  • the parameter (s) concerned in the mapping table can be varied.
  • the parameter (s) at least include a cyclic shift. The details will be discussed in the following.
  • the network device 120 transmits 205 a set of TBs to at least one multicast group of terminal devices, including the terminal device 110 involved in the signaling flow 200.
  • the set of TBs may include more than one TB.
  • Each of the TBs may convey DL data or information to the terminal device 110.
  • the set of TBs may include TBs for a same multicast group of terminal devices, and the terminal device 110 involved in the signaling flow 200 may be included in that multicast group.
  • the set of TBs are scheduled by a Physical Downlink Control Channel (PDCCH) scrambled with a same G-RNTI.
  • the set of TBs may include TBs for a plurality of multicast groups of terminal devices, and the terminal device 110 involved in the signaling flow 200 may be included in each of the plurality of multicast groups. In this case, among the set of TBs, different sub-sets of TBs are scheduled by PDCCH scrambled with different G-RNTs.
  • the set of TBs comprising at least a first sub-set of TBs and a second sub-set of TBs.
  • a first PDCH scheduling the first sub-set of TBs is scrambled with a first G-RNTI
  • a second PDCH scheduling the second sub-set of TBs is scrambled with a second G-RNTI different from the first G-RNTI, and so on.
  • the network device 120 may further transmit TBs to one or more other multicast groups of terminal devices.
  • the terminal device 110 may receive and detect the sets of TBs from the network device 120 on the corresponding PDCCH.
  • the terminal device 110 may utilize the G-RNTI (s) to de-scramble the PDCCH in order to detect the set of TBs.
  • the terminal device 110 may fail to detect or may miss at least one of the set of TBs. In this case, the terminal device 110 determines 210 that a NACK feedback is to be transmitted for the at least one TB transmitted from a network device 120.
  • the terminal device 110 relies on a mapping table associated with the set of TBs to generate a sequence and transmits the NACK feedback using the sequence.
  • the mapping table associated with the set of TBs indicates at least a mapping between at least different cyclic shift values and different combinations of TBs among the set of TBs.
  • a cyclic shift is a parameter considered in generating a sequence, and different cyclic shift values may be used to generate different sequences.
  • a sequence is a resource in a code domain for PUCCH.
  • a PUCCH resource may be related to a resource in the time domain, frequency domain, and code domain.
  • a combination of TBs may include one or more TBs. Two combinations of TBs are considered as different from each other if at least one TB included in one combination is not included in the other combination.
  • the terminal device 110 may need to indicate the TB or TBs for which NACK is needed.
  • the terminal device 110 selects 215, from the mapping table associated with the set of TBs, a cyclic shift value mapped to a combination of the at least one TB for which a NACK feedback is determined to be transmitted.
  • the terminal device 110 then generates 220 a sequence at least based on the selected cyclic shift value.
  • a sequence may be generated for various PUCCH formats, which may require different parameters including the cyclic shift.
  • the sequence used to convey the NACK feedback may be transmitted in one of PUCCH format 0 and PUCCH format 1, which can carry no more than 2 bits.
  • sequence generation for PUCCH format 0 and PUCCH format 1 is first introduced, which may also be found in 3GPP specification TS38.211.
  • a sequence x (n) shall be generated according to:
  • the cyclic shift ⁇ varies as a function of the symbol and slot number according to
  • - l′ is the index of the OFDM symbol in the slot that corresponds to the first OFDM symbol of the PUCCH transmission in the slot given by [5, TS 38.213]
  • PUCCH shall use interlaced mapping according to any of the higher-layer parameters useInterlacePUCCH-PUSCH in BWP-UplinkCommon or useInterlacePUCCH-PUSCH in BWP-UplinkDedicated, where is the resource block number within the interlace;
  • the complex-valued symbol d (0) shall be multiplied with a sequence according to
  • Intra-slot frequency hopping shall be assumed when the higher-layer parameter intraSlotFrequencyHopping is provided, regardless of whether the frequency-hop distance is zero or not, and interlaced mapping is not enabled, otherwise no intra-slot frequency hopping shall be assumed.
  • the orthogonal sequence w i (m) is given by Table 6.3.2.4.1-2 of 3GPP specification TS38.211, where i is the index of the orthogonal sequence to use according to clause 9.2.1 of [5, TS 38.213] .
  • i is the index of the orthogonal sequence to use according to clause 9.2.1 of [5, TS 38.213] .
  • the complex-valued symbol d (0) is repeated for the subsequent slots.
  • a final sequence z is generated.
  • sequence generation for PUCCH format 0 the information conveyed by an orthogonal sequence is transmitted through a different cyclic shift value ⁇ , which varies at least based on specific values of cyclic shifts m 0 and m CS .
  • ⁇ cyclic shift value
  • sequence generation for PUCCH format 1 the information conveyed by an orthogonal sequence is transmitted through a different cyclic shift value ⁇ and/or a different orthogonal cover code (OCC) in the time domain.
  • OCC orthogonal cover code
  • the OCC is used to define the orthogonal sequence w i (m) . That is, if at least one of the cyclic shift value ⁇ and the orthogonal sequence w i (m) , a different sequence z is generated for PUCCH format 1.
  • PUCCH resources for NACK-only are group-common, if a group of terminal devices are scrambled by the same G-RNTI, there is no necessary to ensure the PUCCH resources from different terminal devices are orthogonal, thus these orthogonal PUCCH resources can be mapped to the different combinations of TBs with NACK-only feedback. It can carry combinations of up to TBs with NACK-only feedback at most.
  • the mapping table may be configured based on PUCCH format (e.g., PUCCH format 0 or PUCCH format 1) . If the terminal device 110 is configured to support both PUCCH format 0 and PUCCH format 1, the terminal device 110 may determine which format is used. For different PUCCH formats, different mapping tables may be configured as associated with the corresponding PUCCH formats.
  • PUCCH format e.g., PUCCH format 0 or PUCCH format 1
  • the terminal device 110 may be configured in such a way that more than one NACK-only feedback corresponding to different G-RNTIs cannot be transmitted in the same slot for PUCCH (also referred to as PUCCH slot) .
  • the set of TBs may include TBs for the same G-RNTI.
  • the terminal device 110 transmits a NACK feedback for a combination of TB (s) from the set of TBs within the PUCCH slot, as described below.
  • the terminal device 110 may generate a sequence in a similar way as discussed above and transmit the NACK feedback using the generated sequence within another PUCCH slot. It is first described below some embodiments related to the configuration of disabling the terminal device 110 to transmit more than one NACK-only feedback corresponding to different G-RNTIs in a same PUCCH slot.
  • the mapping table associated with the set of transmitted TB may also be associated with PUCCH format 0.
  • the mapping table may indicate a mapping between different cyclic shift values and different combinations of TBs among the set of TBs.
  • the cyclic shifts m 0 and m CS used for sequence generation in Eq. (s) are considered for PUCCH format 0.
  • a cyclic shift value included in the mapping table is a sum of values of cyclic shifts m 0 and m CS .
  • a different cyclic shift value is mapped to a different combination of TB (s) , to represent a NACK feedback for this combination of TB (s) .
  • the information is carried by different values for m cs , and multiple terminal devices may be multiplexed by configured with different UE-specific m 0 .
  • the orthogonal PUCCH resources (corresponding to different sequences) can represent different combinations of TBs with NACK-only feedback. Therefore, in some embodiments of the present disclosure, for NACK-only based feedback mode, it is proposed to use different sums of values of cyclic shifts m 0 and m CS to generate different sequences, so as to represent different NACK feedbacks for different combination of TBs.
  • Fig. 3A illustrates an example scenario of TB transmission for terminal devices (e.g., terminal devices 110-1, 110-2) included in a multicast group (e.g., multicast group 130-1) .
  • the network device 120 transmits TB1, TB2, TB3 to the multicast group 130-1.
  • a PDCCH scheduling the three TB is scrambled with the same G-RNTI, e.g., G-RNTI1.
  • G-RNTI e.g., G-RNTI1.
  • a sum of values of cyclic shifts m 0 and m CS is referred to as a cyclic shift value in the mapping table and used to generate a sequence.
  • the terminal device 110-1 or 110-2 may select a cyclic shift value of “4” for the sum of m 0 and m CS . Then the terminal device 110-1 or 110-2 may generate a sequence for PUCCH format 0 based on the selected cyclic shift value.
  • the sequence generation for PUCCH format 0 may be performed in a similar way as described above.
  • the values of a sum of cyclic shifts m 0 and m CS provided in Mapping Table 1 is provided as an example.
  • the sum of cyclic shifts m 0 and m CS may be varied in a range of [0, 11] , meaning that there are 12 different values in the range [0, 11] .
  • different values from the range of [0, 11] than those in Mapping Table 1 may be assigned to be mapped to different combinations of TBs.
  • the set of TBs may be identified or indexed by a reception order of those TBs. Accordingly, the cyclic shift values mapped to different combinations of TBs may also be identified or indexed based on the reception order of the set of TBs. For example, in the example of Fig. 3A and Mapping Table 1, it is assumed that the three TBs are received in a sequential reception order of TB1, TB2, and TB3. In Mapping Table 1, mapping pairs of cyclic shift value and combination of TBs may be ordered based on the reception order of the three TBs and the number of TBs in each combination.
  • the sequences generated based on the two cyclic shift values may have relatively high orthogonality.
  • the total number of different cyclic shift values (by m 0 and m CS ) is limited (e.g., 12 different values) , to assign the cyclic shift values to different combinations of TBs, it is expected that a difference between cyclic shift values mapped to combinations each including more than one TB is large enough.
  • the mapping table may be set in such a way that there is a relative large difference between any two of cyclic shift values mapped to a combination of TB1 and TB2, a combination of TB1 and TB3, a combination of TB2 and TB3, and a combination of TB1, TB2, and TB3.
  • the difference between cyclic shift values mapped any two of those combinations is larger than or equal to 2 (e.g., 4 mapped to the combination of TB1 and TB2, and 6 mapped to the combination of TB1 and TB3) .
  • a difference between any two of cyclic shift values mapped to combinations of single TBs may be relatively small, for example, smaller than the difference between cyclic shift values mapped to combinations including more than one TB.
  • the difference between cyclic shift values mapped the combination of TB1 and the combination of TB2 is 1, which is smaller than the difference between cyclic shift values mapped to the combination of TB1 and TB2 and the combination of TB1 and TB3.
  • a difference between this cyclic shift value and any other cyclic shift value in the mapping table is larger than or equal to 2.
  • a difference between this cyclic shift value and any other cyclic shift value in the mapping table is larger than or equal to 2.
  • a cyclic shift value of 4 which has different from any other cyclic shift value in the Mapping Table 1, with a different of at least 2.
  • the mapping table comprises a first cyclic shift value mapped to a combination of a first number of TBs, a second cyclic shift value mapped to a combination of a second number of TBs, and a third cyclic shift value mapped to a combination of a third number of TBs, where the first number is the largest one, i.e., larger than the second number and the third number.
  • the three cyclic shift values may be assigned in such a way that a difference (e.g., 3) between the first cyclic shift value (e.g., 4 for the combination of TB1 and TB2) and the second cyclic shift value (e.g., 1 for the combination of TB1) or a difference (e.g., 2) between the first cyclic shift value and the third cyclic shift value (e.g., 2 for the combination of TB2) is larger than a difference (e.g., 1) between the first cyclic shift value and the third cyclic shift value.
  • the mapping table further comprises a fourth cyclic shift value mapped to a combination of a fourth number of TBs, the first number and the second number each being larger than both the third number and the fourth number.
  • the four cyclic shift values may be assigned a difference (e.g., 2) between the first cyclic shift value (e.g., 4 for the combination of TB1 and TB2) and the second cyclic shift value (e.g., 6 for the combination of TB1 and TB3) is larger than a difference (e.g., 1) between the third cyclic shift value (e.g., 1 for the combination of TB1) and the fourth cyclic shift value (e.g., 2 for the combination of TB2) .
  • a different mapping table may be configured for the different number of TBs. For example, if the network device 120 is about to transmit two TBs for a multicast group of terminal devices, then the terminal devices within this multicast group may be configured with a mapping table indicating a mapping between three different combinations of TBs and three different cyclic shift values, as indicated in below Mapping Table 2.
  • mapping table associated with the set of transmitted TB may also be associated with PUCCH format 1.
  • the mapping table may indicate a mapping between the different combinations of TBs, and different combinations of cyclic shift values and OCCs.
  • Each combination of TBs is mapped to a different combination of a cyclic shift value and an OCC.
  • the OCC is used to define the orthogonal sequence w i (m) used for generating the sequence.
  • two combinations of cyclic shift values and OCCs are considered as different from each other if a cyclic shift value, an OCC, or both of them included in one combination is not included in the other combination.
  • a total number of OCCs is 8, valued from a range of [0, 7] .
  • the total number of different cyclic shift values (sums of m 0 and m CS ) is 12, valued from a range of [0, 11] .
  • the sequences generated based on the two OCCs may have relatively high orthogonality. Therefore, when configuring the mapping table, the values of OCCs may be first varied with a higher priority than the cyclic shift values, to be mapped to different combinations of TBs.
  • a total number of different combinations of TBs may be different (for example, a total of seven combinations for a set of three TBs, and a total of 63 combinations for a set of six TBs) .
  • the total number of the different combinations of TBs is less than or equal to the total number of different OCCs (e.g., 8) , each combination of TBs may be mapped to a different OCC.
  • the mapping table may include no cyclic shift value for the different combinations of TBs because the OCCs can represent different sequences (or different NACK feedbacks) for different combinations of TBs.
  • a default cyclic shift value or a cyclic shift value configured by the network device 120 may be used.
  • the mapping table may also include cyclic shift values mapped the different combinations of TBs.
  • the cyclic shift values may be a same cyclic shift value (which may be default or configured by the network device 120) , or may be different.
  • the network device 120 transmits TB1, TB2, TB3 to the multicast group 130-1, and the terminal device 110 generate the sequence for PUCCH format 1.
  • the total number of different TB combinations is seven.
  • the mapping table may be configured as below.
  • the terminal device 110-1 or 110-2 may select a cyclic shift value of “0” for the sum of m 0 and m CS and an OCC of “3. ” Then the terminal device 110-1 or 110-2 may generate a sequence for PUCCH format 1 based on the selected cyclic shift value and OCC.
  • the sequence generation for PUCCH format 1 may be performed in a similar way as described above.
  • mapping Table 3 different OCCs and the same cyclic shift value are mapped to the seven different combinations of TBs. It would be appreciated that the mapping in Mapping Table 3 is provide for the purpose of illustration only. In other embodiments, the OCCs may be assigned in other ways and the cyclic shift values may be omitted or may be set as different value (s) .
  • all the different OCCs may be first assigned to different combinations of TBs, and then different cyclic shift values may be assigned to the combinations of TBs so as to make sure that a combination of the OCC and the cyclic shift value is varied for different combinations of TBs.
  • different cyclic shift values may be assigned to the combinations of TBs so as to make sure that a combination of the OCC and the cyclic shift value is varied for different combinations of TBs.
  • the number of such combinations of TBs is equal to the total number of different OCCs (e.g., 8) .
  • a same OCC may be assigned to more than one combination of TBs if the total number of combinations of TBs is larger than the total number of different OCCs.
  • Fig. 3B illustrates another example scenario of TB transmission for terminal devices included (e.g., terminal devices 110-1, 110-2) in a multicast group (e.g., terminal devices 110-1, 110-2) .
  • the network device 120 transmits TB1, TB2, TB3, TB4, TB5, TB6 to the multicast group 130-1.
  • a PDCCH scheduling the three TB is scrambled with the same G-RNTI, e.g., G-RNTI1.
  • the combinations of TBs for which NACK feedbacks are possibly transmitted may be relatively large, i.e., equal to 63.
  • all the eight different OCCs may be assigned to different combinations of TBs, and then the cyclic shift values are also varied to allow that different combinations of OCCs and cyclic shift values are mapped to different combinations of TBs.
  • mapping table associated with the six TBs may be configured as below.
  • the terminal device 110-1 or 110-2 may select a cyclic shift value of “1” for the sum of m 0 and m CS and an OCC of “6. ” Then the terminal device 110-1 or 110-2 may generate a sequence for PUCCH format 1 based on the selected cyclic shift value and OCC.
  • the sequence generation for PUCCH format 1 may be performed in a similar way as described above. It would be appreciated that the mapping in Mapping Table 3 is provide for the purpose of illustration only. In other embodiments, the OCCs and cyclic shift values may be assigned in other ways.
  • the mapping table there may be some combinations of TBs mapped to the same OCC. In this case, the cyclic shift values mapped to those combinations may be selected as having relatively large differences. In some embodiments, for some combinations of TBs mapped to different OCCs, the cyclic shift values mapped to those combinations may be selected as having relatively small differences or may even be the same.
  • the mapping table comprises a first combination of a first cyclic shift value and a first OCC mapped to a first combination of TBs, a second combination of a second cyclic shift value and the first OCC mapped to a second combination of TBs, and a third combination of a third cyclic shift value and a second OCC mapped to a third combination of TBs. That is, the first combination of TBs and the second combination of TBs are mapped to the same first OCC, but the third combination of TBs is mapped to a different second OCC. In this case, a difference between the first cyclic shift value and the second cyclic shift value is larger than a difference between the first cyclic shift value and the third cyclic shift value.
  • mapping table comprises a number of combinations of TBs mapped to a same OCC
  • different cyclic shift values are evenly selected from a total number of different cyclic shift values and then mapped to the number of combinations of TBs that are mapped to the same OCC.
  • cyclic shift values are valued from a range of [0, 11] , and the different cyclic shift values are selected from this range such that a difference between any two consecutive selected cyclic shift values has substantially the same difference. In this way, it is possible to ensure highest orthogonality of the sequences generated for those combinations of TBs.
  • a different mapping table may be configured for a different number of TBs. For example, if the network device 120 is about to transmit four TBs for a multicast group of terminal devices and six TBs for another multicast group of terminal devices, two mapping tables may be defined. If a certain terminal device 110 is included in both the two multicast group, it may be configured with both the two mapping tables.
  • mapping the different combinations of cyclic shift values and OCCs to the different combinations of TBs are provided above.
  • the different combinations of cyclic shift values and OCCs may be mapped to the different combinations of TBs in other ways as long as a combination of a cyclic shift value and an OCC can be used to represent a NACK feedback for a combination of TBs.
  • a PUCCH resource configured with a certain time-frequency position for PUCCH format can extend to 12 orthogonal PUCCH resources by configured with different cyclic shift values, in which it can carry combinations of up to TBs with NACK-only feedback at most.
  • a PUCCH resource configured with a certain time-frequency position for PUCCH format 1 it can carry combinations of up to TBs with NACK-only feedback at most.
  • the terminal device 110 may select whether PUCCH format 0 or PUCCH format 1 is used to generate the sequence based on the number of TBs for which the NACK feedback is to be transmitted.
  • the terminal device 110 may generate a sequence for PUCCH format 0 based on the selected cyclic shift value. In some examples, if the number of TBs for which the NACK feedback is larger than three and smaller than or equal to six, the terminal device 110 may generate a sequence for PUCCH format 0 based on the selected cyclic shift value.
  • the terminal device 110 may generate a sequence for PUCCH format 1 based on the selected cyclic shift value if the number of TBs for which the NACK feedback is less than or equal to six.
  • the terminal device 110 is configured to not transmit more than one NACK-only feedback corresponding to different G-RNTIs in a same PUCCH slot.
  • the terminal device 110 may be configured in such a way that more than one NACK-only feedback corresponding to different G-RNTIs can be transmitted in the same slot for PUCCH (also referred to as PUCCH slot) .
  • the set of TBs may include TBs for different G-RNTIs.
  • the set of transmitted TBs may include TBs for a plurality of multicast groups of terminal devices, and the terminal device 110 involved in the signaling flow 200 may be included in each of the plurality of multicast groups.
  • the set of TBs are scheduled by PDCCH scrambled with different G-RNTs.
  • the set of TBs comprising at least a first sub-set of TBs and a second sub-set of TBs.
  • the terminal device 110 may be allowed to transmit more than one NACK-only feedback corresponding to different G-RNTIs in a same PUCCH slot, within the mapping table associated with the set of TBs (which may associated with different G-RNTIs) , different cyclic shift values (for PUCCH format 0) or different combinations of cyclic shift values and OCCs may be mapped to different combinations of TBs among the set of TB.
  • different cyclic shift values for PUCCH format 0
  • different combinations of cyclic shift values and OCCs may be mapped to different combinations of TBs among the set of TB.
  • the terminal device 110 may be able to generate a sequence to transmit the NACK feedback for any combination of TBs and transmit the NACK feedback within the same slot.
  • the terminal device 110 may generate different sequences for different combinations of TBs scrambled by different G-RNTI.
  • it may also be able to identify the TB (s) for which multicast group scrambled by a certain G-RN
  • Fig. 4 illustrates an example scenario of TB transmission for terminal devices (e.g., terminal devices 110-2, 110-3) included in the multicast group 130-2.
  • the terminal device 110-2 is also included in the multicast group 130-1
  • the terminal device 110-3 is also included in the multicast group 130-3.
  • the network device 120 transmits TB1 and TB2 to the multicast group 130-2, where PDCCH scheduling TB1 and TB2 is scrambled by G-RNTI1; the network device 120 transmits TB4 to the multicast group 130-1, where PDCCH scheduling TB4 is scrambled by G-RNTI2; the network device 120 also transmits TB3 and TB5 to the multicast group 130-3, where PDCCH scheduling TB3 and TB5 is scrambled by G-RNTI3.
  • the terminal device 110-2 At the side of the terminal device 110-2, it may need to receive TB1, TB2 for the multicast group 130-2 and receive TB4 for the multicast group 130-1. At the side of the terminal device 110-3, it may need to receive TB1, TB2 for the multicast group 130-2 and receive TB3 and TB5 for the multicast group 130-3.
  • the terminal device 110-2 or 110-3 may fail to correctly detect or may miss any one, two, or all of the TBs it is supposed to receive.
  • the mapping table associated with PUCCH format 0 For the terminal device 110-2, for the three TBs (TB1, TB2, and TB4) , it is supposed to receive, the mapping table associated with PUCCH format 0 may be configured as below.
  • mapping Table 5 shows only to indicate the G-RNTI (s) related to the combination of TBs, and it may not be specifically included in the mapping table because both the terminal device 110 and the network device 130 may determine which TB is related to which G-RNTI.
  • the terminal device 110-2 determines that a NACK feedback is to be transmitted for TB1 and TB4 which are scheduled by PDCCH scrambled by different G-RNTI (e.g., G-RNTI1 and G-RNTI2) , then the terminal device 110-2 select a cyclic shift value of “0” for generating a sequence for PUCCH format 0.
  • the terminal device 110-2 may transmit the NACK feedback using the generated sequence within a same PUCCH slot. With such sequence generation, the network device 120, after decoding the sequence to obtain the cyclic shift value, it may be able to identify, from the same Mapping Table 5, that the NACK feedback is for TB1 and TB4.
  • the terminal device 110-2 may also be configured with a different mapping table for the three TBs and the mapping table may be configured in a similar way as discussed above for PUCCH format 1.
  • mapping table associated with the four TBs and PUCCH format 1 may also be configured. This mapping table may be configured in a similar way as discussed above for PUCCH format 1.
  • the network device 120 may configure the mapping table and notify the mapping table to the terminal device 110. In some embodiments, the network device 120 may configure one or more mapping tables associated with one or more different sets of TBs.
  • a network device may transmit, to a terminal device, configuration information about PUCCH format 0, which at least indicate a UE-specific cyclic shift value for m 0 .
  • the terminal device may select the value for the cyclic shift m cs .
  • a traditional example structure of the configuration information is as below:
  • initialCyclichShift is used to set the value for m 0 .
  • configuration information about PUCCH format 1 may further indicate an OCC for the terminal device.
  • OCC For PUCCH format 1, in addition to the UE-specific cyclic shift value for m 0 (initialCyclichShift) , configuration information about PUCCH format 1 may further indicate an OCC for the terminal device.
  • a traditional example structure of the configuration information is as below:
  • initialCyclichShift is used to set the value for m 0
  • timeDomainOCC is used to set the OCC
  • the terminal device 110 for PUCCH format 0, it is the terminal device 110 which decide a sum of values of m 0 and m cs based on which combination of TB (s) needs the NACK feedback.
  • the terminal device 110 For PUCCH format 0, it is also the terminal device 110 which decide the OCC and possibly a sum of values of m 0 and m cs based on which combination of TB (s) needs the NACK feedback.
  • the network device 120 may not need to configure the value for m 0 in the configuration information about PUCCH format 0; for PUCCH format 1, the network device 120 may not need to configure the OCC and the value for m 0 in the configuration information about PUCCH format 1. Therefore, the configuration information about PUCCH format 0 may indicate no cyclic shift value for the terminal device 110, and the configuration information about PUCCH format 1, the configuration information indicating no cyclic shift value and no OCC for the terminal device.
  • the terminal device 110 transmits 225, to the network device 120, the NACK feedback for the at least one TB (which is not detected correctly or is missed by the terminal device 110) using the generated sequence.
  • the terminal device 110 may transmit the NACK feedback using the generated sequence within a time slot.
  • the terminal device 110 may transmit the NACK feedback for the at least one TB which is scheduled by PDCCH scrambled with the same G-RNTI. In some embodiments, the terminal device 110 may transmit the NACK feedback for TBs which are scheduled by PDCCH scrambled with the different G-RNTIs.
  • the network device 120 receives 230, from the terminal device 110, the NACK feedback using a sequence.
  • the network device 120 decodes 235 the sequence to obtain at least a cyclic shift value used for generating the sequence.
  • the network device 120 further determines 240, from a mapping table associated with the set of transmitted TBs, a combination of at least one TB that is mapped to the cyclic shift value.
  • the network device 120 may also be aware of the mapping table that is associated with the set of transmitted TBs.
  • the cyclic shift value (the sum of m 0 and m CS ) may be used to find the mapped combination of at least one TB from the mapping table associated with PUCCH format 0.
  • the network device 120 may decode the cyclic shift value and the OCC from the sequence and use the two values to find the mapped combination of at least one TB from the mapping table associated with PUCCH format 1.
  • the network device 120 determines 245 that the NACK feedback is for the at least one TB.
  • the network device 120 may also be able to determine that other TBs than the at least one TB are successfully received by the terminal device 110.
  • the network device 120 may decide whether to retransmit the at least one TB for which the NACK feedback is received.
  • the network device 120 may receive, in a certain time slot, NACK feedbacks from a plurality of terminal devices included in the same multicast group or from different multicast groups.
  • the network device 120 may be able to determine the specific TB (s) which is failed to be correctly detected by each of the terminal devices.
  • Fig. 5 is a flowchart of an example method 500 implemented at a terminal device in accordance with some embodiments of the present disclosure. For the convenience of discussion, the method 500 is described with reference to Fig. 1 and thus can be implemented by the terminal device 110.
  • the terminal device 110 determines that a negative acknowledgment (NACK) feedback is to be transmitted for at least one of a set of transport blocks (TBs) transmitted from a network device.
  • NACK negative acknowledgment
  • the terminal device 110 selects, from a mapping table associated with the set of TBs, a cyclic shift value mapped to a combination of the at least one TB.
  • the mapping table indicates a mapping between at least different cyclic shift values and different combinations of TBs among the set of TBs.
  • the terminal device 110 generates a sequence at least based on the selected cyclic shift value.
  • the terminal device 110 transmits, to the network device, the NACK feedback for the at least one TB using the generated sequence.
  • the sequence is to be generated for Physical Uplink Control Channel (PUCCH) format 0, and the mapping table is associated with PUCCH format 0.
  • PUCCH Physical Uplink Control Channel
  • a Physical Downlink Control Channel (PDCCH) scheduling the set of TBs is scrambled with a Group-Radio Network Temporary Identity (G-RNTI.
  • the mapping table comprises a first cyclic shift value mapped to a combination of a first number of TBs, a second cyclic shift value mapped to a combination of a second number of TBs, a third cyclic shift value mapped to a combination of a third number of TBs, and a fourth cyclic shift value mapped to a combination of a fourth number of TBs, the first number and the second number each being larger than both the third number and the fourth number.
  • a difference between the first cyclic shift value and the second cyclic shift value is larger than a difference between the third cyclic shift value and the fourth cyclic shift value.
  • the mapping table comprises a fifth cyclic shift value mapped to a combination of more than one TB, a difference between the fifth cyclic shift value and any cyclic shift value in the mapping table is larger than or equal to 2.
  • a PDCCH scheduling the set of TBs is scrambled with a G-RNTI.
  • generating the sequence comprises: in accordance with a determination that the number of the at least one TB is less than or equal to three, generating a sequence for PUCCH format 0 based on the selected cyclic shift value.
  • generating the sequence comprises: receiving, from the network device, configuration information about PUCCH format 0, the configuration information indicating no cyclic shift value for the terminal device; and generating the sequence based on the configuration information.
  • the sequence is to be generated for PUCCH format 1.
  • the mapping table is associated with PUCCH format 1 and indicates a mapping between different combinations of TBs, and different combinations of cyclic shift values and orthogonal cover codes (OCCs) , each combination of TBs being mapped to a different combination of a cyclic shift value and an OCC.
  • OCCs orthogonal cover codes
  • a combination of a cyclic shift value and an OCC mapped to a combination of the at least one TB is selected from the mapping table, and the sequence is generated based on the selected combination of the cyclic shift value and the OCC.
  • each combination of TBs is mapped to a combination of a cyclic shift value and a different OCC of the total numbers of OCCs.
  • the total number of combinations of TBs comprises a first number of combinations of TBs each mapped to a combination of a cyclic shift value and a different OCC, the first number of combinations of TBs being equal to the total number of OCCs.
  • a PDCCH scheduling the set of TBs is scrambled with a G-RNTI.
  • the mapping table comprises a second number of combinations of TBs mapped to a same OCC, and different cyclic shift values are evenly selected from a total number of cyclic shift values and mapped to the second number of combinations of TBs.
  • a PDCCH scheduling the set of TBs is scrambled with a G-RNTI.
  • generating the sequence comprises: in accordance with a determination that the number of the at least one TB is less than or equal to six, generating a sequence for PUCCH format 1 based on the selected cyclic shift value.
  • generating the sequence comprises: receiving, from the network device, configuration information about PUCCH format 1, the configuration information indicating no cyclic shift value and no OCC for the terminal device; and generating the sequence based on the configuration information.
  • the set of TBs comprising at least a first sub-set of TBs and a second sub-set of TBs, a first PDCH scheduling the first sub-set of TBs is scrambled with a first G-RNTI, and a second PDCH scheduling the second sub-set of TBs is scrambled with a second G-RNTI different from the first G-RNTI.
  • the set of TBs are indexed in the mapping table based on a reception order of the set of TBs.
  • Fig. 6 is a flowchart of an example method 600 implemented at a network device in accordance with some embodiments of the present disclosure. For the convenience of discussion, the method 600 is described with reference to Fig. 1 and thus can be implemented by the network device 120.
  • the network device 120 transmits a set of transport blocks (TBs) to at least one multicast group of terminal devices.
  • the network device 120 receives, from a terminal device, a negative acknowledgment (NACK) feedback using a sequence, the terminal device being comprised in the at least one multicast group.
  • the network device 120 decodes the sequence to obtain at least a cyclic shift value used for generating the sequence.
  • the network device 120 determines, from a mapping table associated with the set of TBs, a combination of at least one TB mapped to the cyclic shift value.
  • the mapping table indicates a mapping between at least different cyclic shift values and different combinations of TBs among the set of TBs.
  • the network device 120 determines that the NACK feedback is for the at least one TB.
  • the sequence is generated for Physical Uplink Control Channel (PUCCH) format 0, and the mapping table is associated with PUCCH format 0.
  • PUCCH Physical Uplink Control Channel
  • a Physical Downlink Control Channel (PDCCH) scheduling the set of TBs is scrambled with a Group-Radio Network Temporary Identity (G-RNTI) .
  • the mapping table comprises a first cyclic shift value mapped to a combination of a first number of TBs, a second cyclic shift value mapped to a combination of a second number of TBs, a third cyclic shift value mapped to a combination of a third number of TBs, and a fourth cyclic shift value mapped to a combination of a fourth number of TBs, the first number and the second number each being larger than both the third number and the fourth number.
  • a difference between the first cyclic shift value and the second cyclic shift value is larger than a difference between the third cyclic shift value and the fourth cyclic shift value.
  • the mapping table comprises a fifth cyclic shift value mapped to a combination of more than one TB, a difference between the fifth cyclic shift value and any cyclic shift value in the mapping table is larger than or equal to 2.
  • the method 600 further comprises transmitting, to the terminal device, configuration information about PUCCH format 0, the configuration information indicating no cyclic shift value for the terminal device.
  • the sequence is generated for PUCCH format 1.
  • the mapping table is associated with PUCCH format 1 and indicates a mapping between different combinations of TBs and different combinations of both cyclic shift values and orthogonal cover codes (OCCs) , each combination of TBs being mapped to a different combination of a cyclic shift value and an OCC.
  • the sequence is decoded to obtain a combination of a cyclic shift value and an OCC used for generating the sequence, and a combination of at least one TB mapped to the combination of a cyclic shift value and an OCC is determined from the mapping table.
  • each combination of TBs is mapped to a combination of a cyclic shift value and a different OCC of the total numbers of OCCs.
  • the total number of combinations of TBs comprises a first number of combinations of TBs each mapped to a combination of a cyclic shift value and a different OCC, the first number of combinations of TBs being equal to the total number of OCCs.
  • a PDCCH scheduling the set of TBs is scrambled with a G-RNTI.
  • the mapping table comprises a second number of combinations of TBs mapped to a same OCC, and different cyclic shift values are evenly selected from a total number of cyclic shift values and mapped to the second number of combinations of TBs.
  • the method 600 further comprises transmitting, to the terminal device, configuration information about PUCCH format 1, the configuration information indicating no cyclic shift value and no OCC for the terminal device.
  • the set of TBs comprising at least a first sub-set of TBs and a second sub-set of TBs, a first PDCH scheduling the first sub-set of TBs is scrambled with a first G-RNTI, and a second PDCH scheduling the second sub-set of TBs is scrambled with a second G-RNTI different from the first G-RNTI.
  • the set of TBs are indexed in the mapping table based on a reception order of the set of TBs.
  • Fig. 7 is a simplified block diagram of a device 700 that is suitable for implementing embodiments of the present disclosure.
  • the device 700 can be considered as an example implementation of the terminal device 110 or the network device 120 as shown in Fig. 1. Accordingly, the device 700 can be implemented at or as at least a part of the terminal device 110 or the network device 120.
  • the device 700 includes a processor 710, a memory 720 coupled to the processor 710, a suitable transmitter (TX) and receiver (RX) 740 coupled to the processor 710, and a communication interface coupled to the TX/RX 740.
  • the memory 720 stores at least a part of a program 730.
  • the TX/RX 740 is for bidirectional communications.
  • the TX/RX 740 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 interface for bidirectional communications between eNBs, S1 interface for communication between a Mobility Management Entity (MME) /Serving Gateway (S-GW) and the eNB, Un interface for communication between the eNB and a relay node (RN) , or Uu interface for communication between the eNB and a terminal device.
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • Un interface for communication between the eNB and a relay node (RN)
  • Uu interface for communication between the eNB and a terminal device.
  • the program 730 is assumed to include program instructions that, when executed by the associated processor 710, enable the device 700 to operate in accordance with the embodiments of the present disclosure, as discussed herein with reference to Fig. 2 to 6.
  • the embodiments herein may be implemented by computer software executable by the processor 710 of the device 700, or by hardware, or by a combination of software and hardware.
  • the processor 710 may be configured to implement various embodiments of the present disclosure.
  • a combination of the processor 710 and memory 720 may form processing means 750 adapted to implement various embodiments of the present disclosure.
  • the memory 720 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 720 is shown in the device 700, there may be several physically distinct memory modules in the device 700.
  • the processor 710 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 700 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.
  • 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. 2 to 10.
  • 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.

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 un support lisible par ordinateur pour des communications. Selon certains modes de réalisation, un procédé consiste à déterminer, au niveau d'un dispositif terminal, qu'une rétroaction d'accusé de réception négatif (NACK) doit être transmise pour au moins un bloc de transport parmi un ensemble de blocs de transport (TB) transmis à partir d'un dispositif de réseau ; à sélectionner, à partir d'une table de mappage associée à l'ensemble de TB, une valeur de décalage cyclique mappée à une combinaison du ou des TB ; à générer une séquence au moins sur la base de la valeur de décalage cyclique sélectionnée ; et à transmettre, au dispositif de réseau, la rétroaction de NACK pour le ou les TB à l'aide de la séquence générée.
PCT/CN2022/075917 2022-02-10 2022-02-10 Procédés, dispositifs, et support lisible par ordinateur pour des communications WO2023150981A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/075917 WO2023150981A1 (fr) 2022-02-10 2022-02-10 Procédés, dispositifs, et support lisible par ordinateur pour des communications

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/075917 WO2023150981A1 (fr) 2022-02-10 2022-02-10 Procédés, dispositifs, et support lisible par ordinateur pour des communications

Publications (1)

Publication Number Publication Date
WO2023150981A1 true WO2023150981A1 (fr) 2023-08-17

Family

ID=87563457

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/075917 WO2023150981A1 (fr) 2022-02-10 2022-02-10 Procédés, dispositifs, et support lisible par ordinateur pour des communications

Country Status (1)

Country Link
WO (1) WO2023150981A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020146580A1 (fr) * 2019-01-09 2020-07-16 Idac Holdings, Inc. Canaux de rétroaction de liaison latérale
WO2021083260A1 (fr) * 2019-10-30 2021-05-06 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Équipement utilisateur et procédé de signalisation de requête automatique de répétition hybride
US20210376966A1 (en) * 2020-05-27 2021-12-02 Qualcomm Incorporated Multiplexing multicast and unicast feedback

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020146580A1 (fr) * 2019-01-09 2020-07-16 Idac Holdings, Inc. Canaux de rétroaction de liaison latérale
WO2021083260A1 (fr) * 2019-10-30 2021-05-06 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Équipement utilisateur et procédé de signalisation de requête automatique de répétition hybride
US20210376966A1 (en) * 2020-05-27 2021-12-02 Qualcomm Incorporated Multiplexing multicast and unicast feedback

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
MODERATOR (LG ELECTRONICS): "Text proposal from Email discussion thread #3 for AI 7.2.4.5 Physical layer procedures for sidelink", 3GPP DRAFT; R1-2004933, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20200525 - 20200605, 6 June 2020 (2020-06-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051893647 *
SAMSUNG: "Corrections on Sidelink", 3GPP DRAFT; R1-2001458, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20200224 - 20200306, 10 March 2020 (2020-03-10), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051863839 *

Similar Documents

Publication Publication Date Title
WO2023184273A1 (fr) Procédé, dispositif, et support de stockage informatique destinés à la communication
WO2023123379A1 (fr) Procédés, dispositifs et support lisible par ordinateur destinés à des communications
WO2023044912A1 (fr) Procédé, dispositif et support de stockage informatique pour la communication
WO2023150981A1 (fr) Procédés, dispositifs, et support lisible par ordinateur pour des communications
WO2023115349A1 (fr) Procédés, dispositifs, et support lisible par ordinateur de communication
CN109150459B (zh) Uci的发送和接收方法、设备以及计算机可读介质
WO2024065771A1 (fr) Procédés, dispositifs et support de communication
WO2023245510A1 (fr) Procédés, dispositifs et support 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
WO2023050096A1 (fr) Procédé, dispositif et support lisible par ordinateur pour la communication
WO2024007314A1 (fr) Procédés, dispositifs et support destinés aux communications
WO2023056629A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2023168610A1 (fr) Procédé, dispositif et support lisible par ordinateur pour la gestion d'interférence de liaison croisée
WO2024011453A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2023122996A1 (fr) Procédé, dispositif et support lisible par ordinateur pour des communications
WO2023141904A1 (fr) Procédés, dispositifs et support lisible par ordinateur pour des communications
WO2023123609A1 (fr) Procédés, dispositifs et support lisible par ordinateur pour des communications
WO2023173341A1 (fr) Procédés, dispositifs, et support lisible par ordinateur pour la communication
WO2022133658A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2024060246A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2022241696A1 (fr) Procédé, dispositif et support lisible par ordinateur pour la communication
WO2023133829A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2024130610A1 (fr) Procédé, dispositif et support lisible par ordinateur destinés à des communications
WO2024119435A1 (fr) Procédé, dispositif et support de stockage informatique de communication

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

Country of ref document: EP

Kind code of ref document: A1