WO2023077418A1 - Procédé et système de gestion de communications en multidiffusion dans des réseaux de communication sans fil - Google Patents

Procédé et système de gestion de communications en multidiffusion dans des réseaux de communication sans fil Download PDF

Info

Publication number
WO2023077418A1
WO2023077418A1 PCT/CN2021/128963 CN2021128963W WO2023077418A1 WO 2023077418 A1 WO2023077418 A1 WO 2023077418A1 CN 2021128963 W CN2021128963 W CN 2021128963W WO 2023077418 A1 WO2023077418 A1 WO 2023077418A1
Authority
WO
WIPO (PCT)
Prior art keywords
feedback
nack
transmission
sps
pdcch
Prior art date
Application number
PCT/CN2021/128963
Other languages
English (en)
Inventor
Xing Liu
Peng Hao
Xingguang WEI
Shuaihua KOU
Wei Gou
Jian Li
Original Assignee
Zte 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 Zte Corporation filed Critical Zte Corporation
Priority to CN202180103807.6A priority Critical patent/CN118176686A/zh
Priority to PCT/CN2021/128963 priority patent/WO2023077418A1/fr
Publication of WO2023077418A1 publication Critical patent/WO2023077418A1/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/1854—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1664—Details of the supervisory signal the supervisory signal being transmitted together with payload signals; piggybacking
    • 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

Definitions

  • the present implementations relate generally to wireless communications, and more particularly to systems, methods, apparatuses, and non-transitory computer-readable media for managing multicast communications in wireless communication networks.
  • a wireless communication method includes receiving, by a wireless communication device from a network, a first Semi Persistent Scheduling (SPS) transmission and a second SPS transmission.
  • a first feedback mode is configured for the first SPS transmission.
  • a second feedback mode is configured for the second SPS transmission.
  • the wireless communication device sends to the network feedback for at least a part of the first SPS transmissions using the second feedback mode.
  • SPS Semi Persistent Scheduling
  • a wireless communication method includes sending, by a network to a wireless communication device, a first SPS transmission and a second SPS transmission.
  • a first feedback mode is configured for the first SPS transmission.
  • a second feedback mode is configured for the second SPS transmission.
  • the network receives from the wireless communication device feedback for at least a part of the first SPS transmissions using the second feedback mode.
  • FIG. 1A is a diagram illustrating an example wireless communication network, according to various arrangements.
  • FIG. 1B is a diagram illustrating a block diagram of an example wireless communication system for transmitting and receiving downlink and uplink communication signals, according to various arrangements.
  • FIG. 2 is a diagram illustrating a transmission mode, according to various arrangements.
  • FIG. 3 is a table illustrating cases for feedback mode combinations, according to various arrangements.
  • FIG. 4A is a diagram illustrating a transmission mode, according to various arrangements.
  • FIG. 4B is a diagram illustrating a transmission mode, according to various arrangements.
  • FIG. 5 is a flowchart diagram that illustrates a method for managing SPS-based MBS communications, according to various arrangements.
  • Implementations described as being implemented in software should not be limited thereto, but can include implementations implemented in hardware, or combinations of software and hardware, and vice-versa, as is apparent to those skilled in the art, unless otherwise specified herein.
  • an implementation showing a singular component should not be considered limiting. Rather, the present disclosure is intended to encompass other implementations including a plurality of the same component, and vice-versa, unless explicitly stated otherwise herein.
  • the present implementations encompass present and future known equivalents to the known components referred to herein by way of illustration.
  • FIG. 1A shows an example wireless communication network 100.
  • the wireless communication network 100 corresponds to a group communication within a cellular network.
  • a network-side communication node or a base station can include one or more of a next Generation Node B (gNB) , an E-Utran Node B (also known as Evolved Node B, eNodeB or eNB) , a pico station, a femto station, a Transmission/Reception Point (TRP) , an Access Point (AP) , or the like.
  • gNB next Generation Node B
  • E-Utran Node B also known as Evolved Node B, eNodeB or eNB
  • TRP Transmission/Reception Point
  • AP Access Point
  • a terminal-side node or a user equipment can include a long range communication system (such as but not limited to, a mobile device, a smart phone, a Personal Digital Assistant (PDA) , a tablet, a laptop computer) or a short range communication system (such as but not limited to, a wearable device, a vehicle with a vehicular communication system, or the like) .
  • a network-side communication node is represented by a BS 102
  • a terminal-side communication node is represented by a UE 104a or 104b.
  • the BS 102 is sometimes referred to as a “wireless communication node
  • the UE 104a/104b is sometimes referred to as a “wireless communication device. ”
  • the BS 102 can provide wireless communication services to the UEs 104a and 104b within a cell 101.
  • the UE 104a can communicate with the BS 102 via a communication channel 103a.
  • the UE 104b can communicate with the BS 102 via a communication channel 103b.
  • the communication channels (e.g., 103a and 103b) can be through interfaces such as but not limited to, an Uu interface which is also known as Universal Mobile Telecommunication System (UMTS) air interface.
  • the BS 102 is connected to a Core Network (CN) 108 through an external interface 107, e.g., an Iu interface.
  • CN Core Network
  • FIG. 1B illustrates a block diagram of an example wireless communication system 150 for transmitting and receiving downlink and uplink communication signals, in accordance with some arrangements of the present disclosure.
  • the system 150 is a portion of the network 100.
  • data symbols can be transmitted and received in a wireless communication environment such as the wireless communication network 100 of FIG. 1A.
  • the system 150 generally includes the BS 102 and UEs 104a and 104b.
  • the BS 102 includes a BS transceiver module 110, a BS antenna 112, a BS memory module 116, a BS processor module 114, and a network communication module 118.
  • the modules/components are coupled and interconnected with one another as needed via a data communication bus 120.
  • the UE 104a includes a UE transceiver module 130a, a UE antenna 132a, a UE memory module 134a, and a UE processor module 136a.
  • the modules/components are coupled and interconnected with one another as needed via a data communication bus 140a.
  • the UE 104b includes a UE transceiver module 130b, a UE antenna 132b, a UE memory module 134b, and a UE processor module 136b.
  • the modules/components are coupled and interconnected with one another as needed via a data communication bus 140b.
  • the BS 102 communicates with the UEs 104a and 104b via communication channels 155, which can be any wireless channel or other medium known in the art suitable for transmission of data as described herein.
  • the system 150 can further include any number of modules/elements other than the modules/elements shown in FIG. 1B.
  • the various illustrative blocks, modules, elements, circuits, and processing logic described in connection with the arrangements disclosed herein can be implemented in hardware, computer-readable software, firmware, or any practical combination thereof.
  • various illustrative components, blocks, modules, circuits, and steps are described generally in terms of their functionalities. Whether such functionalities are implemented as hardware, firmware, or software depends upon the particular application and design constraints imposed on the overall system. Those familiar with the concepts described herein may implement such functionalities in a suitable manner for each particular application, but such implementation decisions should not be interpreted as limiting the scope of the present disclosure.
  • a wireless transmission from an antenna of each of the UEs 104a and 104b to an antenna of the BS 102 is known as an uplink transmission
  • a wireless transmission from an antenna of the BS 102 to an antenna of each of the UEs 104a and 104b is known as a downlink transmission.
  • each of the UE transceiver modules 130a and 130b may be referred to herein as an uplink transceiver, or UE transceiver.
  • the uplink transceiver can include a transmitter circuitry and receiver circuitry that are each coupled to the respective antenna 132a and 132b.
  • a duplex switch may alternatively couple the uplink transmitter or receiver to the uplink antenna in time duplex fashion.
  • the BS transceiver module 110 may be herein referred to as a downlink transceiver, or BS transceiver.
  • the downlink transceiver can include RF transmitter circuitry and receiver circuitry that are each coupled to the antenna 112.
  • a downlink duplex switch may alternatively couple the downlink transmitter or receiver to the antenna 112 in time duplex fashion.
  • the operations of the transceivers 110, 130a, and 130b are coordinated in time such that the uplink receiver is coupled to the antenna 132a and 132b for reception of transmissions over the wireless communication channels 155 at the same time that the downlink transmitter is coupled to the antenna 112.
  • the UEs 104a and 104b can use the UE transceivers 130a and 130b through the respective antennas 132a and 132b to communicate with the BS 102 via the wireless communication channels 155.
  • the wireless communication channel 155 can be any wireless channel or other medium suitable for downlink (DL) and/or uplink (UL) transmission of data as described herein.
  • the UE transceiver 130a/130b and the BS transceiver 110 are configured to communicate via the wireless data communication channel 155, and cooperate with a suitably configured antenna arrangement that can support a particular wireless communication protocol and modulation scheme.
  • the UE transceiver 130a/130b and the BS transceiver 110 are configured to support industry standards such as the Long Term Evolution (LTE) and emerging 5G standards, or the like. It is understood, however, that the present disclosure is not necessarily limited in application to a particular standard and associated protocols. Rather, the UE transceiver 130a/130b and the BS transceiver 110 may be configured to support alternate, or additional, wireless data communication protocols, including future standards or variations thereof.
  • LTE Long Term Evolution
  • 5G 5G
  • the processor modules 136a and 136b and 114 may be each implemented, or realized, with a general purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein.
  • a processor may be realized as a microprocessor, a controller, a microcontroller, a state machine, or the like.
  • a processor may also be implemented as a combination of computing devices, e.g., a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other such configuration.
  • the memory modules 116, 134a, 134b can be realized as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or another suitable form of storage medium.
  • the memory modules 116, 134a, and 134b may be coupled to the processor modules 114, 136a, and 136b, respectively, such that the processors modules 114, 136a, and 136b can read information from, and write information to, the memory modules 116, 134a, and 134b, respectively.
  • the memory modules 116, 134a, and 134b may also be integrated into their respective processor modules 114, 136a, and 136b.
  • the memory modules 116, 134a, and 134b may each include a cache memory for storing temporary variables or other intermediate information during execution of instructions to be executed by processor modules 114, 136a, and 136b, respectively.
  • Memory modules 116, 134a, and 134b may also each include non-volatile memory for storing instructions to be executed by the processor modules 114, 136a, and 136b, respectively.
  • the network interface 118 generally represents the hardware, software, firmware, processing logic, and/or other components of the BS 102 that enable bi-directional communication between BS transceiver 110 and other network components and communication nodes configured to communication with the BS 102.
  • the network interface 118 may be configured to support internet or WiMAX traffic.
  • the network interface 118 provides an 802.3 Ethernet interface such that BS transceiver 110 can communicate with a conventional Ethernet based computer network.
  • the network interface 118 may include a physical interface for connection to the computer network (e.g., Mobile Switching Center (MSC) ) .
  • MSC Mobile Switching Center
  • the terms “configured for” or “configured to” as used herein with respect to a specified operation or function refers to a device, component, circuit, structure, machine, signal, etc. that is physically constructed, programmed, formatted and/or arranged to perform the specified operation or function.
  • the network interface 118 can allow the BS 102 to communicate with other BSs or core network over a wired or wireless connection.
  • the BS 102 can communicate with a plurality of UEs (including the UEs 104a and 104b) using multicast or broadcast, collectively referred to as MBS.
  • the plurality of UEs can each receive MBS channel (e.g., MBS PDSCH, MBS PDCCH, and so on) via multicast and/or broadcast.
  • MBS channel e.g., MBS PDSCH, MBS PDCCH, and so on
  • the plurality of UEs have a common understanding on the configurations of the MBS channel, including but not limited to, frequency resource range for resource allocation, scramble identifier (ID) , and so on.
  • ID scramble identifier
  • the same transmission mechanism can be used by a network node (e.g. the BS 102) for transmitting the same information to a group of UEs (e.g., UEs 104a and 104b) or all UEs in a cell.
  • the MBS transmission can be carried on a PDSCH received by the group of UEs or all of the UEs in a cell. Therefore, the PDSCH carrying MBS information is sometimes referred to as a Group-Common (GC) Physical Downlink Shared Channel (PDSCH) or MBS PDSCH.
  • GC Group-Common
  • PDSCH Physical Downlink Shared Channel
  • UEs with similar network environments can be classified into a same UE group. Then, the transmission mechanism selected for the UE group can be better matched to the network environments experienced by each UE in the UE group.
  • MBS information can be carried on a GC PDSCH received by a group of UEs.
  • the GC PDSCH can be scheduled dynamically by a Downlink Control Information (DCI) carried on GC Physical Downlink Control Channel (PDCCH) .
  • DCI Downlink Control Information
  • PDCH Physical Downlink Control Channel
  • the GC PDSCH can be transmitted using a Semi-Persistent Scheduling (SPS) mechanism. That is, some transmission parameters of the GC PDSCH (e.g., transmission period, feedback resource, etc. ) are configured semi-statically, using Radio Resource Control (RRC) signaling.
  • RRC Radio Resource Control
  • the SPS transmission can be activated by an activation PDCCH and deactivated by an deactivation PDCCH.
  • the activation PDCCH indicates other parameters for GC PDSCH transmission, such as time domain resource allocation, frequency domain resource allocation, feedback timing (k1) , etc. This mode can be referred to as SPS-based MBS transmission mode or GC
  • FIG. 2 is a diagram illustrating a transmission mode 200, according to various arrangements.
  • the x-axis corresponds to time
  • the y-axis corresponds to frequency (e.g., carrier or Bandwidth Part (BWP) ) .
  • a UE e.g., UE 104a or 104b
  • the UE can receive data or information from the BS 102 using the downlink slots and send data or information to the BS 102 using the uplink slots.
  • one or more SPS transmission configurations can be configured via RRC signaling.
  • a PDCCH carrying an activation command can be used for activating the SPS-based MBS transmission.
  • Such a PDCCH is referred to as an activation PDCCH 202.
  • the GC PDSCH is transmitted according to the SPS transmission configuration configured via the RRC signaling and indicated by the activation PDCCH 202.
  • the first PDSCH 204 after the activation PDCCH 202 is referred to as an “SPS PDSCH with scheduling PDCCH.
  • Any PDSCH (e.g., second PDSCHs 206) other than the first PDSCH 204 and located between the activation PDCCH 202 and a deactivation PDCCH 208 can be referred to as “SPS PDSCH without scheduling PDCCH” or “SPS PDSCH. ”
  • the activation PDCCH 202 can be shared by a group of UEs. In other words, the BS 102 sends the GC PDCCH 202 to multiple UEs (e.g., the UEs 104a and 104b) . Further, a deactivation PDCCH 208 carrying a SPS release command can be transmitted within a monitoring occasion according to the configuration of a Search Space Set (SSS) and Control Resource Set (CORESET) .
  • SSS Search Space Set
  • CORESET Control Resource Set
  • Each of feedback resources 212 corresponds to a respective one of the first PDSCH 204, the second PDSCHs 206, and the deactivation PDCCH 208 can be used by the UE to provide feedback (e.g., NACK-only feedback) to the BS 102.
  • feedback including at least one of SPS activation PDCCH 202, SPS deactivation PDCCH 208, the first PDSCH 204 (scheduled by the activation PDCCH 202) , and the second PDSCHs 206 (without scheduling PDCCH) ) from a group of UEs for the same multicast information needs to be coordinated.
  • the SPS PDSCH with scheduling PDCCH is treated as a dynamic scheduling PDSCH.
  • the corresponding Hybrid Automatic Repeat Request (HARQ) -ACK feedback bit is inserted into a HARQ-ACK feedback codebook of the dynamic scheduling PDSCH.
  • HARQ-ACK bits corresponding to the other SPS PDSCHs e.g., the PDSCHs without scheduling PDCCH
  • the HARQ-ACK feedback codebook can be divided into two sub-codebooks: a first sub-codebook is for dynamic scheduling PDSCHs (including SPS PDSCH with scheduling PDCCH and the deactivation PDCCH) , and a second sub-codebook is for SPS PDSCHs without scheduling PDCCH.
  • the first sub-codebook is arranged to be in front of or before the second sub-codebook.
  • the feedback modes contain ACK/NACK-based feedback and NACK-only based feedback.
  • the UE For ACK/NACK feedback for SPS PDSCH without scheduling PDCCH, the UE provides the ACK feedback to the network (e.g., to the BS) as long as the UE successfully receives a MBS TB carried on SPS PDSCH without scheduling PDCCH.
  • the UE provides the NACK feedback to the network in response to determining that the UE has failed to receive the MBS TB carried on the SPS PDSCH.
  • the ACK/NACK feedback information is transmitted in a resource (e.g., a Physical Uplink Control Channel (PUCCH) or piggybacked on a Physical Uplink Shared Channel (PUSCH) ) indicated by the network.
  • the feedback resource are typically a UE-specific resource. In other words, for a same MBS TB, the network indicates or configures different independent resources for the different UEs.
  • the ACK/NACK feedback is used for the SPS activation.
  • the ACK/NACK feedback for SPS activation represents receiving status on whether the activation PDCCH is decoded successfully or not, or represents receiving status on whether the PDSCH scheduled by activation PDCCH is received successfully or not.
  • the UE provides the ACK feedback to the network as long as the UE has successfully received an activation command carried on the activation PDCCH within the configured monitoring occasion.
  • the UE provides the ACK feedback to the network as long as the UE has successfully received a MBS TB carried on PDSCH scheduled by activation PDCCH.
  • the UE provides the NACK feedback to the network if the UE fails to detect the activation PDCCH or fails to receive the MBS TB carried on the PDSCH scheduled by activation PDCCH.
  • the ACK/NACK feedback is used for the SPS deactivation. More specifically, the UE provides the ACK feedback to the network as long as the UE has successfully received a SPS release command carried on the deactivation PDCCH. In addition, the UE provides the NACK feedback to the network if the UE fails to detect a SPS release command carried on the deactivation PDCCH within the configured monitoring occasion.
  • a GC-PDSCH is scheduled by a DCI format with CRC scrambled by a GC RNTI for multicast (e.g., G-RNTI) , or whether the GC-PDSCH is a SPS PDSCH, if the feedback mode is configured as ACK/NACK feedback
  • various types of retransmission mechanisms can be used.
  • One mechanism is that the PDSCH carrying retransmission Transport Block (TB) can be scheduled by a DCI format with CRC scrambled by a UE specific RNTI (e.g., C-RNT) .
  • This mechanism can also be referred to as Point-to-Point (PTP) retransmission.
  • PTP Point-to-Point
  • Another mechanism is that the PDSCH carrying retransmission TB is scheduled by a DCI format with CRC scrambled by a GC RNTI (e.g., the same G-RNTI used for initial transmission) .
  • the configuration parameters includes at least one of xOverhead, the maximum number of modulation order (Q m ) , the maximum number of layer ( ⁇ ) , target code rate (R) , the total number of REs allocated for PDSCH (N RE ) , and so on.
  • Such parameters can be configured under the Common Frequency Resource (CFR) for the multicast service or the GC PDSCH transmission.
  • CFR Common Frequency Resource
  • a UE can also be configured with a set of parameters for LBRM and TBS determination for unicast PDSCH.
  • the parameters also include at least one of xOverhead, the maximum number of modulation order (Q m ) , the maximum number of layer ( ⁇ ) , target code rate (R) , the total number of REs allocated for PDSCH (N RE ) , and so on.
  • the parameters can be configured under the active BWP of the UE.
  • the initial transmission of a multicast TB is scheduled by a DCI format with CRC scrambled by a GC RNTI (e.g., G-RNTI) .
  • a GC RNTI e.g., G-RNTI
  • a UE-specific RNTI e.g., C-RNT
  • Methods 1-4 can be used for determined the LBRM and TBS for the PDSCH carrying the multicast TB.
  • Method 1 If the DCI format scheduling the retransmission PDSCH is transmitted within SSS and CORESET configured for GC-PDCCH (or multicast PDCCH) , the LBRM and TBS for the retransmission PDSCH are determined according to the parameters configured for multicast. Otherwise, if the DCI format scheduling the retransmission PDSCH is not transmitted within SSS and CORESET configured for GC-PDCCH (or multicast PDCCH) , the LBRM and TBS for the retransmission PDSCH are determined according to the parameters configured for unicast.
  • Method 2 If a UE is configured that PTP retransmission of a multicast initial transmission is enabled, the UE determines the LBRM and TBS for the retransmission PDSCH scheduled by a DCI format with CRC scrambled with a UE specific RNTI (e.g., C-RNTI) according to the parameters configured for multicast.
  • a UE specific RNTI e.g., C-RNTI
  • Method 3 the UE calculates a first TBS according to the parameters configured for unicast, and calculates a second TBS according to the parameters configured for multicast. Then, the UE determines the final TBS as the larger or smaller one of the first TBS and the second TBS.
  • Method 4 at least one of the parameters for calculating the final TBS is determined according to both of the configured parameters for unicast and the configured parameters for multicast.
  • the xOverhead used for calculating the final TBS is the larger or smaller one of the configured xOverhead for unicast and configured xOverhead for multicast.
  • the maximum number of modulation order (Q m ) for calculating the final TBS can be the larger or smaller one of configured Q m for unicast and configured Q m for multicast.
  • the maximum number of layer ( ⁇ ) for calculating the final TBS can be the larger or smaller one of configured ⁇ for unicast and configured ⁇ for multicast.
  • the target code rate (R) for calculating the final TBS can be the larger or smaller one of configured R for unicast and configured R for multicast.
  • the UE For NACK-only feedback, the UE provides the NACK feedback only if the UE fails to receive the MBS TB carried on PDSCH.
  • the NACK-only feedback resource are typically a GC resource. More specifically, a same NACK-only feedback resource is shared among a group of UEs receiving the same PDSCH carrying MBS TB.
  • the NACK-only feedback can also be used for SPS activation.
  • the UE provides the NACK feedback if the UE fails to detect an activation command carried on PDCCH within the configured monitoring occasion or the UE fails to receive the MBS TB carried on the activation PDSCH scheduled by activation PDCCH.
  • the NACK-only feedback can also be used for SPS deactivation.
  • the UE provides the NACK feedback if the UE fails to detect a SPS release command carried on the deactivation PDCCH within the configured monitoring occasion.
  • the feedback modes can be respectively configured for SPS PDSCH without scheduling PDCCH and SPS activation/deactivation.
  • the configuration signaling can be at least one of RRC signaling, Media Access Control (MAC) Control Element (CE) , DCI, or so on.
  • the feedback mode for SPS activation/deactivation can only be ACK/NACK-based feedback.
  • the feedback mode for SPS PDSCH without scheduling PDCCH can be configured as either ACK/NACK feedback or NACK-only feedback.
  • the feedback function can also be enabled or disabled through the configuration, including at least one of RRC signaling, MAC CE, DCI, and so on.
  • the configuration for enabling or disabling feedback for SPS PDSCH without scheduling PDCCH and SPS activation/deactivation can share a same configuration signaling.
  • the configuration for enabling or disabling feedback for SPS PDSCH without scheduling PDCCH and SPS activation/deactivation are separate and independent from each other.
  • Case 1 refers to the scenario in which feedback is enabled for both SPS PDSCH without scheduling PDCCH and SPS activation/deactivation, and ACK/NACK feedback is used for both SPS PDSCH without scheduling PDCCH and SPS activation/deactivation.
  • Case 2 refers to the scenario in which feedback is enabled for both SPS PDSCH without scheduling PDCCH and SPS activation/deactivation, ACK/NACK feedback is used for SPS activation/deactivation, and NACK-only feedback is used for SPS PDSCH without scheduling PDCCH.
  • Case 3 refers to the scenario in which feedback is enabled for SPS activation/deactivation, and ACK/NACK feedback is used.
  • the feedback function is disabled.
  • Case 4 refers to the scenario in which feedback is enabled for SPS PDSCH without scheduling PDCCH, and ACK/NACK feedback is used.
  • the feedback function is disabled.
  • Case 5 refers to the scenario in which feedback is enabled for SPS PDSCH without scheduling PDCCH, and NACK-only feedback is used. For SPS activation/deactivation, the feedback function is disabled.
  • Case 6 refers to the scenario in which feedback is disabled for both SPS PDSCH without scheduling PDCCH and SPS activation/deactivation.
  • the network may send the configuration information in additional activation PDCCHs repeatedly.
  • the BS 102 retransmits the activation PDCCH in repose to determining that a new UE joins the MBS group after the activation PDCCH has already been transmitted so that the newly added UE also has the complete configuration information.
  • the above operations can be referred to as SPS transmission reactivation without changing transmission parameters.
  • the additional PDCCH can be referred to as reactivation PDCCH for UEs that has already received the activation PDCCH.
  • FIG. 4A is a diagram illustrating a transmission mode 400a including an activation PDCCH and a reactivation PDCCH, according to various arrangements.
  • the x-axis corresponds to time
  • the y-axis corresponds to frequency (e.g., carrier or BWP) .
  • a UE e.g., UE 104a or 104b
  • Each of the slots 401a- 401k corresponds to an uplink slot and a downlink slot.
  • the UE can receive data or information from the BS 102 using the downlink slots 401a-401k and send data or information to the BS 102 using the uplink slots 401a-401k.
  • FIG. 4A illustrates example feedback methods for providing feedback for SPS-based GC transmissions, with respect to Case 2. That is, feedback is enabled for both SPS PDSCH without scheduling PDCCH and SPS activation/deactivation. ACK/NACK feedback is used for SPS activation/deactivation, NACK-only feedback is used for SPS PDSCH without scheduling PDCCH.
  • An activation PDCCH 402 in slot 401a carrying an activation command can be used for activating the SPS-based MBS transmission.
  • the PDSCH 404 in slot 401a for the SPS-based MBS transmission is scheduled by the activation PDCCH 402 and is an SPS PDSCH with scheduling PDCCH.
  • Any PDSCH (e.g., PDSCH 406 in slot 401d) other than the PDSCH 404 and located between the activation PDCCH 402 and a corresponding deactivation PDCCH or an reactivation PDCCH is an SPS PDSCH without scheduling PDCCH or SPS PDSCH.
  • the activation PDCCH 402 can be shared by a group of UEs. In other words, the BS 102 sends the GC PDCCH 402 to multiple UEs (e.g., the UEs 104a and 104b) .
  • a reactivation PDCCH 403 in slot 401g carrying an activation command can be used for activating (reactivating) the SPS-based MBS transmission.
  • the PDSCH 408 in slot 401g for the SPS-based MBS transmission is scheduled by the reactivation PDCCH 403 and is an SPS PDSCH with scheduling PDCCH.
  • Any PDSCH (e.g., PDSCH 410 in slot 401j) other than the PDSCH 408 and located between the activation PDCCH 403 and a corresponding deactivation PDCCH or an reactivation PDCCH is an SPS PDSCH without scheduling PDCCH or SPS PDSCH.
  • the reactivation PDCCH 403 can be shared by a group of UEs. In other words, the BS 102 sends the GC PDCCH 402 to multiple UEs (e.g., the UEs 104a and 104b) .
  • the reactivation PDCCH 403 received by the UE contains a HPN HARQ process number (HPN) value that is the same as a HPN value of the last activation PDCCH (e.g., the activation PDCCH 402) that the UE received.
  • HPN HPN HARQ process number
  • the reactivation PDCCH 403 and the activation PDCCH 402 correspond to a same SPS index.
  • the reactivation PDCCH 403 and the activation PDCCH 402 have a same Radio Temporary Identifier (RNTI) , e.g., a group Configured Scheduling RNTI (G-CS-RNTI) , CS-RNTI, and so on. That is, the Cyclic Redundancy Check (CRC) for DCI carried on the reactivation PDCCH 403 and the activation PDCCH 402 is scrambled with a same RNTI.
  • RNTI Radio Temporary Identifier
  • the PDSCH 408 scheduled by the reactivation PDCCH 403 is one of the PDSCH without scheduling PDCCH activated by the activation PDCCH 404.
  • the PDSCH (e.g., the PDSCH 408) activated by the activation PDCCH 402 becomes a PDSCH with scheduling PDCCH after the reactivation PDCCH 403 is transmitted by the BS 102 for scheduling that PDSCH.
  • At least a part of information fields for DCIs carried on the reactivation PDCCH 403 is the same as at least a part of information fields for DCIs carried on the activation PDCCH 402.
  • the field Time Domain Resource Assignment in DCIs carried on the reactivation PDCCH 403 and the activation PDCCH 402 can be same in some examples but different in other examples.
  • the DCIs carried on the reactivation PDCCH 403 and the DCIs carried on the activation PDCCH 402 can have the same DCI format.
  • the reactivation PDCCH 403 is a GC PDCCH
  • the reactivation PDCCH 403 which is an activation PDCCH to that UE
  • a UE that is currently receiving this MBS service which already received the activation PDCCH 402
  • the first PDSCH 408 after reactivation PDCCH 103 counts as a dynamic scheduling PDSCH.
  • the UE can nevertheless receive the PDSCH 408, and the PDSCH 408 is still treated as a SPS PDSCH without scheduling PDCCH. From the network perspective, the network assumes that the UE has received the reactivation PDCCH 403, resulting in the HARQ-ACK codebook ambiguity.
  • the feedback timing for ACK/NACK feedback of SPS activation e.g., PDSCH-to-HARQ feedback timing indicator (k1 value)
  • k1 value PDSCH-to-HARQ feedback timing indicator
  • NACK-only feedback is used for SPS PDSCH without scheduling PDCCH (e.g., PDSCHs 406 and 410) .
  • the NACK-only feedback resource (e.g., feedback resource 414) can also be indicated in the activation PDCCH 402 and reactivation PDCCH 403.
  • the same or different resource sets can be configured for NACK-only feedback and ACK/NACK feedback.
  • the same or different feedback timing sets can be configured for NACK-only feedback and ACK/NACK feedback.
  • the feedback resource 414 of NACK-only feedback can also be determined according the same information fields (e.g., PDSCH-to-HARQ feedback timing indicator field and PRI field) .
  • the activation/reactivation PDCCH 403 contains a set of information fields (including at least one of PDSCH-to-HARQ feedback timing indicator field and PRI field) for NACK-only feedback resource indication independent of that for ACK/NACK feedback resource indication.
  • there are different sets of information fields including at least one of PDSCH-to-HARQ feedback timing indicator field and PRI field
  • NACK-only feedback resource indication and ACK/NACK feedback resource indication there are different sets of information fields (including at least one of PDSCH-to-HARQ feedback timing indicator field and PRI field) for determination of feedback resource for SPS activation or SPS deactivation and for SPS PDSCH without scheduling PDCCH.
  • the UE can nevertheless receive the PDSCH 408, but the UE considers that PDSCH 408 is a SPS PDSCH without scheduling PDCCH. If the PDSCH 408 is not received correctly, the feedback resource for PDSCH 408 is determined according the parameters sets configuration and information indication in activation PDCCH 402 for SPS PDSCH without scheduling PDCCH or for NACK-only feedback.
  • the NACK-only feedback resource for PDSCH 408 can be located within a slot (e.g., slot 401k) different from a slot (e.g., slot 401j) in which the ACK/NACK feedback resource 412 for SPS activation is located. In other arrangements not shown, the NACK-only feedback resource for PDSCH can be located within the same slot (e.g., slot 401j) as the ACK/NACK feedback resource 412 for SPS activation.
  • the UE considers the reactivation PDCCH 403 as a SPS activation.
  • the feedback resource for the reactivation PDCCH 403 is determined according to the parameters sets configuration and information indication in activation PDCCH for SPS activation or for ACK/NACK feedback. Accordingly, there is no feedback on the NACK-only feedback resource regardless of whether PDSCH 408 is received correctly.
  • the UE has different feedback behaviors in different receiving states whether reactivation PDCCH is detected.
  • the BS 102 cannot determine the receiving status of the UE. As a result, the understanding of feedback information between the UE and the BS 102 is inconsistent.
  • the NACK-only feedback resource if the NACK-only feedback resource is located in a same slot or overlaps in the time domain with another UCI of the UE, the NACK-only feedback (e.g., 1-bit feedback information) is multiplexed with the UCI, and the result is together. For example, if the PDSCH is successfully received, 1 bit with an ACK value (e.g., “1” ) is multiplexed with the UCI. On the other hand, if the UE fails to receive the PDSCH, 1 bit with NACK value (e.g., “0” ) is multiplexed with the UCI.
  • the multiplexing can follow a predefined rule, e.g., cascade the 1 bit NACK-only feedback information after the original UCI information.
  • the NACK-only feedback resource if the NACK-only feedback resource is located in the same slot or overlaps in the time domain with a PUSCH of the UE, the NACK-only feedback (e.g., 1-bit feedback information) piggybacks on the PUSCH to be transmit together. For example, if the PDSCH is successfully received, 1 bit with ACK value (e.g., “1” ) piggybacks on the PUSCH. If the UE fails to receive the PDSCH, 1 bit with NACK value (e.g., “0” ) piggybacks on the PUSCH.
  • piggybacking or multiplexing refers to mapping certain bits (e.g., the feedback information) to resources originally allocated to the PUSCH for transmission.
  • the UE sends NACK feedback using the NACK-only feedback resource 414 in response to determining that the UE has failed to detect the reactivation PDCCH 403 and that the PDSCH 408 has not been received correctly, there is additional 1 bit information multiplexed with the UCI or piggybacked on the PUSCH. Given that the BS 102 is not able to meaningfully distinguish, the performance of the UCI or PUSCH received by the BS 102 is affected.
  • FIG. 4B is a diagram illustrating a transmission mode 400b including an activation PDCCH and a reactivation PDCCH, according to various arrangements.
  • the x-axis corresponds to time
  • the y-axis corresponds to frequency (e.g., carrier or BWP) .
  • a UE e.g., UE 104a or 104b
  • Each of the slots 401a-401k corresponds to an uplink slot and a downlink slot.
  • the UE can receive data or information from the BS 102 using the downlink slots 401a-401k and send data or information to the BS 102 using the uplink slots 401a-401k.
  • FIG. 4B illustrates example feedback methods for providing feedback for SPS-based GC transmissions, with respect to Case 5. That is, NACK-only feedback is enabled for SPS PDSCH without scheduling PDCCH. For SPS activation/deactivation, feedback function is disabled.
  • the feedback timing for NACK-only feedback of SPS activation e.g., PDSCH-to-HARQ feedback timing indicator (k1 value)
  • the feedback timing for NACK-only feedback of SPS activation is indicated from a configured feedback timing set.
  • the specific feedback resource 424 in slot 401k is indicated by a PRI field in the activation PDCCH 402 and/or the reactivation PDCCH 403.
  • NACK-only feedback resource 424 can also be configured via RRC signaling.
  • the UE can nevertheless receive the PDSCH 408, but the UE considers that PDSCH 408 is a SPS PDSCH without scheduling PDCCH. If the PDSCH 408 is not received correctly, the UE provides the NACK feedback in the feedback resource 424 for PDSCH 408.
  • the UE considers the reactivation PDCCH 403 as a SPS activation. There is no feedback information needed.
  • the UE has different feedback behaviors according to different receiving states whether reactivation PDCCH is detected.
  • the BS 102 cannot determine the receiving status of the UE. As a result, the understanding of feedback information between the UE and the BS 102 is inconsistent.
  • the NACK-only feedback resource if the NACK-only feedback resource is located in a same slot or overlaps in the time domain with another UCI of the UE, the NACK-only feedback (e.g., 1-bit feedback information) is multiplexed with the UCI, and the result is together. For example, if the PDSCH is successfully received, 1 bit with an ACK value (e.g., “1” ) is multiplexed with the UCI. On the other hand, if the UE fails to receive the PDSCH, 1 bit with NACK value (e.g., “0” ) is multiplexed with the UCI.
  • the multiplexing can follow a predefined rule, e.g., cascade the 1 bit NACK-only feedback information after the original UCI information.
  • the NACK-only feedback resource if the NACK-only feedback resource is located in the same slot or overlaps in the time domain with a PUSCH of the UE, the NACK-only feedback (e.g., 1-bit feedback information) piggybacks on the PUSCH to be transmit together. For example, if the PDSCH is successfully received, 1 bit with ACK value (e.g., “1” ) piggybacks on the PUSCH. If the UE fails to receive the PDSCH, 1 bit with NACK value (e.g., “0” ) piggybacks on the PUSCH.
  • ACK value e.g., “1”
  • the UE sends NACK feedback using the NACK-only feedback resource 414 in response to determining that the UE has failed to detect the reactivation PDCCH 403 and that the PDSCH 408 has not been received correctly, there is additional 1 bit information multiplexed with the UCI or piggybacked on the PUSCH. Given that the BS 102 is not able to meaningfully distinguish, the performance of the UCI or PUSCH received by the BS 102 is affected.
  • FIG. 5 is a flowchart diagram that illustrates a method 500 for managing SPS-based MBS communications, according to various arrangements.
  • the method 500 can be performed by the network side (e.g., the BS 102) and a UE (e.g., the UE 104a) .
  • the method 500 avoids inconsistency between the understanding of the BS 102 and that of the UE 104a as described herein.
  • the network (e.g., the BS 102) sends a first SPS transmission and a second SPS transmission to the UE 104a.
  • the network configures a first feedback mode for the first SPS transmission for the UE 104a and a second feedback mode for the second SPS transmission for the UE 104a.
  • the UE 104a receives the first SPS transmission and the second SPS transmission.
  • receive means attempts to receive, given that the UE 104a may not receive one or both of the first SPS transmission and the second SPS transmission.
  • the UE 104a determines the reception status (whether a transmission is received) for the first SPS transmission and the second SPS transmission.
  • the UE 104a sends feedback for at least a part of the first SPS transmission using the second feedback mode.
  • the network receives the feedback for at least a part of the first SPS transmission using the second feedback mode.
  • the first SPS transmission includes a PDSCH transmission (e.g., PDSCH 404) scheduled by a first activation PDCCH (e.g., activation PDCCH 402) or a PDSCH transmission (e.g., PDSCH 408) scheduled by a second activation PDCCH (e.g., reactivation PDCCH 403) .
  • the second SPS transmission includes a PDSCH (e.g., PDSCH 406 or 410) without a scheduling PDCCH.
  • reception status of the PDSCH transmission scheduled by the activation or reactivation PDCCH reflects the reception status of activation or reactivation PDCCH, and feedback for the activation or reactivation PDCCH itself is not directly provided.
  • the first SPS transmission includes the first activation PDCCH (e.g., activation PDCCH 402) or the second activation PDCCH (e.g., reactivation PDCCH 403) .
  • the second SPS transmission includes an SPS PDSCH. In such arrangements, reception status of the activation or reactivation PDCCH itself is directly provided.
  • the feedback for the first SPS transmission and feedback for the second SPS transmission are enabled.
  • the first feedback mode includes ACK/NACK feedback.
  • the second feedback mode includes NACK-only feedback.
  • the UE determines whether to provide NACK-only feedback for the first SPS transmission (e.g., the PDSCH 408 scheduled by the reactivation PDCCH 403 or the reactivation PDCCH 403 itself) according to a relationship between the NACK-only feedback resource 414 (carrying the NACK-only feedback) and another uplink transmission from the same UE, where the another uplink transmission is different from the NACK-only feedback resource 414.
  • the NACK-only feedback resource 414 corresponds to (e.g., mapped to or associated with) the first SPS transmission (e.g., the PDSCH 404 or activation PDCCH 402) .
  • the another uplink transmission includes at least one of UCI or PUSCH.
  • the relationship between the NACK-only feedback resource 414 and the another uplink transmission includes at least one of being located in the same slot or overlapping in the time domain.
  • the UE determines that the NACK-only feedback information needs to occupy a corresponding bit in the new UCI after multiplexing. In some arrangements, in response to determining that the NACK-only feedback resource 414 is located in the same slot or overlaps at least partially in the time domain with a PUSCH of the UE, the UE determines that a bit corresponding to the NACK-only feedback information piggybacks on the PUSCH.
  • the UE does not provide feedback for the first SPS transmission on the NACK-only feedback resource 414.
  • the UE needs to provide ACK/NACK feedback for the first SPS transmission. If the feedback information needs to be multiplexed with another uplink transmissions, for this first SPS transmission, ACK/NACK feedback is needed, but also NACK-only feedback is needed.
  • the UE determines whether to provide NACK-only feedback for the first SPS transmission (e.g., the PDSCH scheduled by the activation PDCCH or the activation PDCCH itself) according to a relationship between the NACK-only feedback resource (carrying the NACK-only feedback) and another uplink transmission from the same UE, where the another uplink transmission is different from the NACK-only feedback resource.
  • the NACK-only feedback resource corresponds to (e.g., mapped to or associated with) the first SPS transmission.
  • the another uplink transmission includes at least one of UCI or PUSCH.
  • the relationship between the NACK-only feedback resource and the another uplink transmission includes at least one of being located in the same slot or overlapping in the time domain.
  • the UE determines that the NACK-only feedback information needs to occupy a corresponding bit in the new UCI after multiplexing.
  • the UE determines that a bit corresponding to the NACK-only feedback information piggybacks on the PUSCH.
  • the UE does not provide feedback for the first SPS transmission on the NACK-only feedback resource 414.
  • the UE determines whether to provide NACK-only feedback for the first SPS transmission based on a relationship between a NACK-only feedback resource corresponding to the first SPS transmission and another uplink transmission of the UE different from the NACK-only feedback resource.
  • the another uplink transmission of the UE includes a UCI or a PUSCH.
  • the relationship between a NACK-only feedback resource corresponding to the first SPS transmission and the another uplink transmission includes one of the NACK-only feedback resource and the another uplink transmission being in a same slot, or the NACK-only feedback resource and the another uplink transmission overlapping at least partially in time.
  • each NACK-only feedback occupies 1 bit.
  • the number of bits that is the same as the number of NACK-only feedback are occupied, and the bits of the NACK-only feedback information has an one-to-one mapping with the occupied bits according to a predefined rule.
  • the rule can be associated with at least one of a time-domain order of PDSCHs corresponding to the NACK-only feedback, a MBS service index of the PDSCHs corresponding to the NACK-only feedback, a RNTI order of the PDSCHs corresponding to the NACK-only feedback.
  • feedback for a PDSCH 408 scheduled by reactivation PDCCH 403 is NACK-only. That is, in response to the UE detecting the reactivation PDCCH 403 and failing to detect or receive the corresponding PDSCH 408 scheduled by the reactivation PDCCH 403 correctly, the UE will send a NACK feedback on the NACK-only feedback resource 414 for the PDSCH 408.
  • the DCI carried on the activation/deactivation PDCCH contains a DAI information field, and the feedback for the SPS activation occupies a corresponding bit in the ACK/NACK feedback codebook.
  • feedback for a PDSCH scheduled by an activation PDCCH is NACK-only. That is, in response to the UE detecting the activation PDCCH and failing to detect or receive the corresponding PDSCH scheduled by the activation PDCCH correctly, the UE will send a NACK feedback on the NACK-only feedback resource for that PDSCH.
  • the DCI carried on the activation/deactivation PDCCH contains a DAI information field, and the feedback for the SPS activation occupies a corresponding bit in the ACK/NACK feedback codebook.
  • the first SPS transmission includes a PDSCH scheduled by the first activation PDCCH or the second activation PDCCH (e.g., the reactivation PDCCH) .
  • the second SPS transmission includes a PDSCH without a scheduling PDCCH.
  • the UE fails to receive a PDSCH transmission scheduled by the first activation PDCCH or the second activation PDCCH, the UE sends NACK-only feedback on a NACK-only feedback resource corresponding to the PDSCH transmission.
  • the DAI filed is reserved.
  • the ACK/NACK feedback bit for activation PDCCH or PDSCH scheduled by activation PDCCH is added at the end of dynamic sub-codebook. There is no ACK/NACK feedback bit for reactivation PDCCH or PDSCH scheduled by reactivation PDCCH.
  • feedback for the PDSCH scheduled by reactivation PDCCH is also NACK-only. That is, in response to the UE detecting the reactivation PDCCH failing to detect or receive the corresponding PDSCH scheduled by the reactivation PDCCH correctly, the UE provides NACK feedback on the NACK-only feedback resource for the PDSCH.
  • the UE ignores the DAI field, or the DAI field is reserved, the ACK/NACK feedback is added to an end of a dynamic sub-codebook for the first SPS transmission which includes a first activation PDCCH or a PDSCH transmission scheduled by the first activation PDCCH.
  • the UE sends to the network NACK-only feedback for the first SPS transmission which includes a second activation PDCCH or a PDSCH transmission scheduled by the second activation PDCCH.
  • ACK/NACK feedback can be used for SPS activation/deactivation
  • NACK-only feedback can be used for SPS PDSCH without scheduling PDCCH.
  • feedback for the first SPS transmission is disabled, and the first feedback mode is no feedback.
  • the feedback for the first SPS transmission is enabled, and the second feedback mode is NACK-only feedback.
  • the UE determines whether to provide NACK-only feedback for the first SPS transmission (e.g., the PDSCH 408 scheduled by the reactivation PDCCH 403 or the reactivation PDCCH 403 itself) according to a relationship between the NACK-only feedback resource 424 (carrying the NACK-only feedback) and another uplink transmission from the same UE, where the another uplink transmission is different from the NACK-only feedback resource 424.
  • the NACK-only feedback resource 424 corresponds to (e.g., mapped to or associated with) the first SPS transmission (e.g., the PDSCH 404 or activation PDCCH 402) .
  • the another uplink transmission includes at least one of UCI or PUSCH.
  • the relationship between the NACK-only feedback resource 424 and the another uplink transmission includes at least one of being located in the same slot or overlapping in the time domain.
  • the UE determines that the NACK-only feedback information needs to occupy a corresponding bit in the new UCI after multiplexing.
  • the UE determines that a bit corresponding to the NACK-only feedback information piggybacks on the PUSCH.
  • the UE does not provide feedback for the first SPS transmission on the NACK-only feedback resource 424.
  • the UE determines whether to provide NACK-only feedback for the first SPS transmission (e.g., the PDSCH scheduled by the activation PDCCH or the activation PDCCH itself) according to a relationship between the NACK-only feedback resource (carrying the NACK-only feedback) and another uplink transmission from the same UE, where the another uplink transmission is different from the NACK-only feedback resource.
  • the NACK-only feedback resource corresponds to (e.g., mapped to or associated with) the first SPS transmission.
  • the another uplink transmission includes at least one of UCI or PUSCH.
  • the relationship between the NACK-only feedback resource and the another uplink transmission includes at least one of being located in the same slot or overlapping in the time domain.
  • the UE determines that the NACK-only feedback information needs to occupy a corresponding bit in the new UCI after multiplexing.
  • the UE determines that a bit corresponding to the NACK-only feedback information piggybacks on the PUSCH.
  • the UE does not provide feedback for the first SPS transmission on the NACK-only feedback resource 424.
  • the UE determines whether to provide NACK-only feedback for the first SPS transmission based on a relationship between a NACK-only feedback resource corresponding to the first SPS transmission and another uplink transmission of the UE different from the NACK-only feedback resource.
  • the another uplink transmission of the UE includes a UCI or a PUSCH.
  • the relationship between a NACK-only feedback resource corresponding to the first SPS transmission and the another uplink transmission includes one of the NACK-only feedback resource and the another uplink transmission being in a same slot, or the NACK-only feedback resource and the another uplink transmission overlapping at least partially in time.
  • each NACK-only feedback occupies 1 bit.
  • the number of bits that is the same as the number of NACK-only feedback are occupied, and the bits of the NACK-only feedback information has an one-to-one mapping with the occupied bits according to a predefined rule.
  • the rule defines a mapping order based on at least one of a time-domain order of PDSCHs corresponding to the NACK-only feedback, a MBS service index of the PDSCHs corresponding to the NACK-only feedback, a RNTI order of the PDSCHs corresponding to the NACK-only feedback.
  • feedback for a PDSCH 408 scheduled by reactivation PDCCH 403 is NACK-only. That is, in response to the UE detecting the reactivation PDCCH 403 and failing to detect or receive the corresponding PDSCH 408 scheduled by the reactivation PDCCH 403 correctly, the UE will send a NACK feedback on the NACK-only feedback resource 424 for the PDSCH 408.
  • feedback for a PDSCH scheduled by an activation PDCCH is NACK-only. That is, in response to the UE detecting the activation PDCCH and failing to detect or receive the corresponding PDSCH scheduled by the activation PDCCH correctly, the UE will send a NACK feedback on the NACK-only feedback resource for that PDSCH.
  • the first SPS transmission includes a PDSCH scheduled by the first activation PDCCH or the second activation PDCCH.
  • the second SPS transmission includes a PDSCH without a scheduling PDCCH.
  • the UE fails to receive a PDSCH transmission scheduled by the first activation PDCCH or the second activation PDCCH, the UE sends NACK-only feedback on a NACK-only feedback resource corresponding to the PDSCH transmission.
  • the issues of ambiguous feedback information can be avoided when feedback is enabled for SPS PDSCH without scheduling PDCCH, and NACK-only feedback is be used.
  • the feedback function is disabled.
  • any two components so associated can also be viewed as being “operably connected, " or “operably coupled, " to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being “operably couplable, " to each other to achieve the desired functionality.
  • operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.

Landscapes

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

Abstract

Des modes de réalisation donnés à titre d'exemple comprennent un procédé de communication sans fil comprenant la réception, par un dispositif de communication sans fil à partir d'un réseau, d'une première transmission de planification semi-persistante (SPS) et d'une seconde transmission de SPS. Un premier mode de rétroaction est configuré pour la première transmission de SPS. Un second mode de rétroaction est configuré pour la seconde transmission de SPS. Le dispositif de communication sans fil envoie à la rétroaction de réseau pour au moins une partie des premières transmissions de SPS à l'aide du second mode de rétroaction.
PCT/CN2021/128963 2021-11-05 2021-11-05 Procédé et système de gestion de communications en multidiffusion dans des réseaux de communication sans fil WO2023077418A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202180103807.6A CN118176686A (zh) 2021-11-05 2021-11-05 无线通信方法
PCT/CN2021/128963 WO2023077418A1 (fr) 2021-11-05 2021-11-05 Procédé et système de gestion de communications en multidiffusion dans des réseaux de communication sans fil

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/128963 WO2023077418A1 (fr) 2021-11-05 2021-11-05 Procédé et système de gestion de communications en multidiffusion dans des réseaux de communication sans fil

Publications (1)

Publication Number Publication Date
WO2023077418A1 true WO2023077418A1 (fr) 2023-05-11

Family

ID=86240393

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/128963 WO2023077418A1 (fr) 2021-11-05 2021-11-05 Procédé et système de gestion de communications en multidiffusion dans des réseaux de communication sans fil

Country Status (2)

Country Link
CN (1) CN118176686A (fr)
WO (1) WO2023077418A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180115430A1 (en) * 2015-04-15 2018-04-26 Lg Electronics Inc. Method for performing feedback by terminal in wireless communication system and apparatus therefor
CN113595689A (zh) * 2020-04-30 2021-11-02 华为技术有限公司 通信方法和装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180115430A1 (en) * 2015-04-15 2018-04-26 Lg Electronics Inc. Method for performing feedback by terminal in wireless communication system and apparatus therefor
CN113595689A (zh) * 2020-04-30 2021-11-02 华为技术有限公司 通信方法和装置

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
MODERATOR (HUAWEI): "FL summary#1 on improving reliability for MBS for RRC_CONNECTED UEs", 3GPP TSG RAN WG1 #106BIS-E, R1-2110408, 12 October 2021 (2021-10-12), XP052060383 *
MODERATOR (HUAWEI): "FL summary#1 on improving reliability for MBS for RRC_CONNECTED UEs", 3GPP TSG RAN WG1 #106-E, R1-2108285, 17 August 2021 (2021-08-17), XP052042104 *
NOKIA, NOKIA SHANGHAI BELL: "Reliability Improvements for RRC_CONNECTED UEs", 3GPP TSG RAN WG1 MEETING #104BIS-E, R1-2102656, 6 April 2021 (2021-04-06), XP051993178 *

Also Published As

Publication number Publication date
CN118176686A (zh) 2024-06-11

Similar Documents

Publication Publication Date Title
US11825454B2 (en) Latency reduction techniques in wireless communications
CN110036586B (zh) 用于处理时间缩减信令的系统和方法
US11716609B2 (en) Delaying transmission depending on transmission type and UE processing capabilities
EP3101982A1 (fr) Station de base, procédé de transmission, station mobile et procédé de commande de retransmission
US11647511B2 (en) Methods for inter-system carrier aggregation in advanced wireless communication systems
CN110214432B (zh) 通信网络中载波的激活或去活的方法和节点
WO2020168577A1 (fr) Procédé permettant de transmettre des informations de rétroaction de liaison montante, dispositif de terminal et dispositif de réseau
US9838161B2 (en) Bundling HARQ feedback in a time division duplexing communication system
WO2021029956A1 (fr) Multiplexage d'informations de commande de liaison montante (uci) à autorisation configurée destiné à une nouvelle radio sans licence (nr-u)
JP2016220194A (ja) 無線通信における制御チャネル
KR20220076490A (ko) 무선 통신 방법, 장치 및 통신 시스템
US20220231796A1 (en) Method for feedback information transmission, terminal device, and network device
WO2023077418A1 (fr) Procédé et système de gestion de communications en multidiffusion dans des réseaux de communication sans fil
WO2023102815A1 (fr) Systèmes et procédés de gestion de transmissions de services utilisant des groupes de ressources de fréquence
WO2023050138A1 (fr) Procédé et système de gestion de communications en multidiffusion dans des réseaux de communication sans fil
WO2022205301A1 (fr) Procédé et système de configuration de ressources

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

Country of ref document: EP

Kind code of ref document: A1