Multiple feedback control for group common physical downlink shared channel (GC-PDSCH) in multimedia broadcast multicast service

Abstract

The present disclosure provides systems, methods, and apparatus, including computer programs encoded on computer storage media, for enabling a wireless system implementing multicast transmissions to control feedback reporting from multiple user equipments (UEs) and to address feedback codebook misalignment issues. In particular, aspects provide a multicast transmission grant including a plurality of feedback timing indicators (K1), where the multicast transmission grant is configured to configure different UEs for multicast transmission feedback reporting, where feedback codebooks sent from the different UEs in various uplink control transmission occasions have the same size. Other aspects and features are also claimed and described.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefit of the following applications: U.S. Patent Application No. 17 / 450,248, filed October 7, 2021, entitled “MULTIPLE FEEDBACK CONTROL FOR GROUP COMMON-PHYSICAL DOWNLINK SHARED CHANNEL (GC-PDSCH) IN MULTIMEDIA BROADCAST MULTICAST SERVICE (MBMS)”; and U.S. Provisional Patent Application No. 63 / 090,132, filed October 9, 2020, entitled “MULTIPLE FEEDBACK CONTROL FOR GROUP COMMON-PHYSICAL DOWNLINK SHARED CHANNEL (GC-PDSCH) IN MULTIMEDIA BROADCAST MULTICAST SERVICE (MBMS)”, the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003] In summary, aspects of this disclosure relate to wireless communication systems, and more specifically, aspects of this disclosure relate to feedback controlling the transmission of Group Common Physical Downlink Shared Channel (GC-PDSCH) in Multimedia Broadcast Multicast Service (MBMS) from multiple user equipments (UEs) to a base station. Background Technology

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, and broadcasting. Wireless multiple access communication systems can include multiple base stations or network access nodes, each supporting communication with multiple communication devices (which may also be referred to as User Equipment (UE)) simultaneously. These systems are able to support communication with multiple UEs by sharing available system resources (such as time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, improved LTE (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems can employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM).

[0005] In current Multimedia Broadcast Multicast Service (MBMS) systems, a base station can be configured to send broadcast or multicast messages to multiple UEs. In these current systems, the base station can address a single multicast transmission to a group of user equipments (UEs). This group of UEs can receive the multicast transmission and can be configured to provide feedback associated with the transmission. Specifically, in an example of an MBMS system, the base station can send multiple Group Common Physical Downlink Control Channel (GC-PDCCH) transmissions, each addressable to the group of UEs. In such an example, the base station can configure each GC-PDCCH transmission in the GC-PDCCH transmissions to include an authorization for the corresponding GC Physical Downlink Shared Channel (GC-PDSCH) transmission. It should be noted that, in this specification, a GC-PDCCH transmission including an authorization for a GC-PDSCH transmission can be referred to as a GC-PDCCH transmission authorization. In such an example, each GC-PDCCH transmission authorization sent by the base station may include a feedback timing indicator (K1) and a Physical Uplink Control Channel (PUCCH) resource indicator (PRI). The UE that receives the GC-PDCCH transmission grant can use the included K1 and PRI to determine the resources for providing acknowledgment / negative acknowledgment (ACK / NACK) feedback for the GC-PDSCH transmission associated with the GC-PDCCH transmission grant.

[0006] Some examples of MBMS systems can support UE-specific feedback for MBMS transmissions. For instance, continuing the example above, after receiving a GC-PDSCH transmission from the base station, the UE can provide feedback to the base station indicating a NACK for the GC-PDSCH transmission. In such an example, the base station can retransmit (or schedule a retransmission) of the GC-PDSCH transmission for which the UE provided the NACK. In this example, the base station can specifically address the GC-PDSCH retransmission to the UE that reported the NACK feedback. Summary of the Invention

[0007] The following outlines some aspects of this disclosure to provide a basic understanding of the techniques discussed. This overview is not a general summary of all anticipated features of this disclosure, and is not intended to identify key or essential elements of all aspects of this disclosure, nor to depict the scope of any or all aspects of this disclosure. Its sole purpose is to present some concepts of one or more aspects of this disclosure in an overview form as a prelude to the more detailed description given later.

[0008] One innovative aspect of the subject matter described in this disclosure can be implemented in a method for wireless communication performed by a user equipment (UE). The method includes receiving from a base station multiple multicast transport grants addressed to a plurality of UEs including the UE. Each of the multicast transport grants schedules a multicast transport and includes at least one feedback timing indicator (K1) and at least one physical uplink control channel (PUCCH) resource indicator (PRI) for acknowledgment / negative acknowledgment (ACK / NACK) feedback associated with the respective multicast transport. The method further includes receiving from the base station a first multicast transport associated with a first multicast transport grant among the multiple multicast transport grants. The method further includes transmitting a first feedback codebook to the base station on a first feedback resource. In various aspects, the first feedback resource is determined by the UE at least in part based on the at least one K1 and the at least one PRI in the first multicast transport grant, and the first feedback codebook is configured to transmit ACK / NACK feedback associated with the first multicast transport to the base station.

[0009] Another innovative aspect of the subject matter described in this disclosure can be implemented in a UE. The UE includes: at least one processor; and a memory coupled to the at least one processor and storing processor-readable instructions configured, when executed by the at least one processor, to: receive from a base station multiple multicast transport grants addressed to a plurality of UEs including the UE. Each of the multicast transport grants schedules a multicast transport and includes at least one K1 and at least one PRI for ACK / NACK feedback associated with the respective multicast transport. The at least one processor is also configured to: receive from the base station a first multicast transport associated with a first multicast transport grant among the plurality of multicast transport grants. The at least one processor is further configured to: send a first feedback codebook to the base station on a first feedback resource. In various aspects, the first feedback resource is determined by the UE at least in part based on the at least one K1 and the at least one PRI in the first multicast transport grant, and the first feedback codebook is configured to send ACK / NACK feedback associated with the first multicast transport to the base station.

[0010] Another innovative aspect of the subject matter described in this disclosure can be implemented in an apparatus configured for wireless communication. The apparatus includes: a unit for receiving, from a base station, multiple multicast transmission grants addressed to a plurality of UEs including the UE. Each of the multicast transmission grants schedules a multicast transmission and includes at least one K1 and at least one PRI for ACK / NACK feedback associated with the respective multicast transmission. The apparatus further includes: a unit for receiving from the base station a first multicast transmission associated with a first multicast transmission grant among the multiple multicast transmission grants. The apparatus includes: a unit for transmitting a first feedback codebook to the base station on a first feedback resource. In various aspects, the first feedback resource is determined by the UE at least in part based on the at least one K1 and the at least one PRI in the first multicast transmission grant, and the first feedback codebook is configured to transmit ACK / NACK feedback associated with the first multicast transmission to the base station.

[0011] Another innovative aspect of the subject matter described in this disclosure can be implemented in a non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to perform operations including: receiving from a base station multiple multicast transport grants addressed to a plurality of UEs including the UE. Each of the multicast transport grants schedules a multicast transport and includes at least one K1 and at least one PRI for ACK / NACK feedback associated with the respective multicast transport. The operation further includes: receiving from the base station a first multicast transport associated with a first multicast transport grant among the plurality of multicast transport grants. The operation further includes: sending a first feedback codebook to the base station on a first feedback resource. In various aspects, the first feedback resource is determined by the UE at least in part based on the at least one K1 and the at least one PRI in the first multicast transport grant, and the first feedback codebook is configured to send ACK / NACK feedback associated with the first multicast transport to the base station.

[0012] One innovative aspect of the subject matter described in this disclosure can be implemented in a method for wireless communication performed by a base station. The method includes: sending a plurality of multicast transmission grants to a plurality of UEs. Each of the multicast transmission grants schedules a multicast transmission and includes at least one K1 and at least one PRI for ACK / NACK feedback associated with the respective multicast transmission. The method further includes: sending a first multicast transmission associated with a first multicast transmission grant in the at least one multicast transmission grant to the plurality of UEs; and receiving at least one feedback codebook from at least one of the plurality of UEs. The at least one feedback codebook includes ACK / NACK feedback associated with the first multicast transmission.

[0013] Another innovative aspect of the subject matter described in this disclosure can be implemented in a base station. The base station includes: at least one processor; and a memory coupled to the at least one processor and storing processor-readable code configured, when executed by the at least one processor, to: send a plurality of multicast transmission grants to a plurality of UEs. Each of the multicast transmission grants schedules a multicast transmission and includes at least one K1 and at least one PRI for ACK / NACK feedback associated with the respective multicast transmission. The at least one processor is also configured to: send a first multicast transmission associated with a first multicast transmission grant in the at least one multicast transmission grant to the plurality of UEs; and receive at least one feedback codebook from at least one of the plurality of UEs. The at least one feedback codebook includes ACK / NACK feedback associated with the first multicast transmission.

[0014] Another innovative aspect of the subject matter described in this disclosure can be implemented in an apparatus configured for wireless communication. The apparatus includes: a unit for transmitting a plurality of multicast transmission grants from a base station to a plurality of UEs. Each of the multicast transmission grants schedules a multicast transmission and includes at least one K1 and at least one PRI for ACK / NACK feedback associated with the respective multicast transmission. The method further includes: transmitting a first multicast transmission associated with a first multicast transmission grant in the at least one multicast transmission grant to the plurality of UEs; and receiving at least one feedback codebook from at least one of the plurality of UEs. The at least one feedback codebook includes ACK / NACK feedback associated with the first multicast transmission.

[0015] Another innovative aspect of the subject matter described in this disclosure can be implemented in a non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to perform operations including: sending a plurality of multicast transport grants to a plurality of UEs. Each of the multicast transport grants schedules a multicast transport and includes at least one K1 and at least one PRI for ACK / NACK feedback associated with the respective multicast transport. The operations further include: sending a first multicast transport associated with a first multicast transport grant in the at least one multicast transport grant to the plurality of UEs; and receiving at least one feedback codebook from at least one of the plurality of UEs. The at least one feedback codebook includes ACK / NACK feedback associated with the first multicast transport.

[0016] Other aspects, features, and implementations of this disclosure will become apparent to those skilled in the art after reviewing the following description of specific exemplary implementations of this disclosure in conjunction with the accompanying drawings. While features of this disclosure may be described hereinafter with respect to a particular implementation and drawings, all implementations of this disclosure may include one or more of the advantageous features described herein. In other words, while one or more implementations may be described as having a particular advantageous feature, one or more such features may also be used according to various implementations of this disclosure described herein. Similarly, while example implementations may be described hereinafter as device, system, or method implementations, such example implementations may be implemented in various devices, systems, and methods. Attached Figure Description

[0017] A further understanding of the nature and advantages of this disclosure can be achieved by referring to the following figures. In the figures, similar components or features may have the same reference numerals. Furthermore, various components of the same type may be distinguished by a dash following the reference numeral and a second reference numeral used to differentiate among similar components. If only the first reference numeral is used in the specification, the description applies to any of the similar components having the same first reference numeral, without regard to the second reference numeral.

[0018] Figure 1 This is a block diagram illustrating the details of an example wireless communication system.

[0019] Figure 2 This is a block diagram that conceptually illustrates an example design of a base station and user equipment (UE).

[0020] Figure 3This is a timing diagram showing an example of a report on feedback for multicast transport associated with a multicast transport grant, which includes multiple feedback timing indicator (K1) fields and multiple physical uplink control channel (PUCCH) resource indicator (PRI) fields.

[0021] Figure 4 This is a diagram illustrating an example communication flow for the management and control of report multicast transmission feedback in an implementation between a UE and a base station, according to some aspects of this disclosure.

[0022] Figure 5 This is a timing diagram illustrating examples of feedback regarding multicast transport associated with multicast transport authorizations, which include Public K1 and multiple PRIs, according to some aspects of this disclosure.

[0023] Figure 6 This is a timing diagram illustrating an example of feedback transmission for multicast transmission reported based on scheduling constraints, according to some aspects of this disclosure.

[0024] Figure 7 This is a timing diagram illustrating an example of sending a feedback transmission on a resource determined based on relative K1, according to some aspects of this disclosure.

[0025] Figure 8 This is a flowchart illustrating an example process for feedback regarding multicast transmission, based on a supporting report of some aspects of this disclosure.

[0026] Figure 9 This is a flowchart illustrating an example process for managing and controlling feedback for multicast transmissions based on the configuration of K1 and PRI, in accordance with some aspects of this disclosure.

[0027] Figure 10 This is a block diagram of an example UE providing feedback on multicast transmission based on some aspects of this disclosure.

[0028] Figure 11 This is a block diagram of an example base station that supports the management and control of feedback for multicast transmission based on some aspects of this disclosure.

[0029] Similar reference numerals and naming conventions are used in the various figures to indicate similar elements. Detailed Implementation

[0030] The various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be embodied in many different forms and should not be construed as limited to any particular structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of this disclosure to those skilled in the art. Based on the teachings herein, it will be understood by those skilled in the art that the scope of this disclosure is intended to cover any aspect of the disclosure herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, an apparatus or a method may be implemented using any number of the aspects set forth herein. Furthermore, the scope of this disclosure is intended to cover such apparatuses or methods implemented using structures, functions, or structures and functions other than those set forth herein or different from those set forth herein. Any aspect of this disclosure may be embodied by one or more elements of the claims.

[0031] Current wireless communication systems suffer from a feedback codebook misalignment problem, which is associated with the current use of multiple feedback timing indicators (K1) in the Group Common (GC) - Physical Downlink Control Channel (GC-PDCCH) transmission grant. Due to the use of multiple K1s, the feedback codebooks reported from different UEs in the Physical Uplink Control Channel (PUCCH) timing have different sizes.

[0032] In summary, the various aspects disclosed herein relate to the management and control of feedback reporting associated with broadcast or multicast transmissions. More specifically, some aspects of this disclosure relate to enabling a group of UEs to report feedback to a base station for Group Common (GC)-Physical Downlink Shared Channel (GC-PDSCH) transmissions associated with Multimedia Broadcast Multicast Service (MBMS). In some examples, the base station may schedule and send GC-PDCCH transmission grants, which schedule corresponding GC-PDSCH transmissions, and may also include feedback control information that allows UEs or sets of UEs in a group receiving the GC-PDSCH transmissions to determine the appropriate feedback resource in which to report feedback codebooks for the GC-PDSCH transmissions. For example, the base station may send a GC-PDCCH transmission grant to a group of UEs that includes a common K1 and multiple different Physical Uplink Control Channel (PUCCH) Resource Indicators (PRIs), each PRI associated with a corresponding UE in the UE set. Each UE in the UE set can use the common K1 indicator to determine the same time (such as within a time slot or sub-time slot) and can use its corresponding PRI to determine the PUCCH resource for reporting its feedback codebook within the time slot or sub-time slot.

[0033] Alternatively, the base station may send a GC-PDCCH transmission grant to the group of UEs, the GC-PDCCH transmission grant including an indication of one or more scheduling constraints to limit feedback reporting from individual UEs in the group such that the feedback codebooks reported by the UEs in PUCCH timings each have the same size. In some examples, the base station may configure the scheduling constraints by indicating different corresponding K1s to different UEs in the group to ensure that, for a given PUCCH timing, different UEs report feedback for the same number of GC-PDSCH transmissions. In some other examples, each UE may be configured with a relative K1, which the UE can add to the K1 indicated by the base station in the GC-PDCCH transmission grant to obtain a total K1. In such examples, each UE can use its corresponding total K1 to determine the feedback resources in which to report the feedback codebook for the GC-PDSCH transmissions associated with the GC-PDCCH transmission grant.

[0034] Specific implementations of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some aspects, the techniques described herein enable feedback reporting from a group of UEs to a base station, such that the feedback codebooks reported by different UEs at PUCCH timings have the same size. In such aspects, the base station can send GC-PDCCH transmission grants including one or more K1 fields while ensuring that the feedback codebooks reported from different UEs at PUCCH timings have the same size. Furthermore, the techniques described herein enable the base station to distribute feedback reports associated with GC-Physical Downlink Shared Channel (GC-PDSCH) transmissions among multiple UEs over time in a fixed relative pattern by providing a mechanism for ensuring that the feedback codebooks reported by different UEs at PUCCH timings have the same size. These techniques provide the advantage that the control overhead of PUCCH transmissions can also be distributed over time.

[0035] In various implementations, the technologies and apparatus described can be used in wireless communication networks such as: Code Division Multiple Access (CDMA) networks, Time Division Multiple Access (TDMA) networks, Frequency Division Multiple Access (FDMA) networks, Orthogonal FDMA (OFDMA) networks, Single Carrier FDMA (SC-FDMA) networks, LTE networks, GSM networks, 5th Generation (5G) or New Radio (NR) networks (sometimes referred to as "5G NR" networks, systems, or devices), and other communication networks. As described herein, the terms "network" and "system" are used interchangeably.

[0036] CDMA networks can implement radio technologies such as Universal Terrestrial Radio Access (UTRA) and CDMA2000. UTRA includes Wideband CDMA (W-CDMA) and Low Code Rate (LCR). CDMA2000 covers the IS-2000, IS-95, and IS-856 standards.

[0037] TDMA networks can implement radio technologies such as the Global System for Mobile Communications (GSM). 3GPP defines standards for the GSMEDGE (Enhanced Data Rate for GSM Evolution) Radio Access Network (RAN) (also referred to as GERAN). The GERAN, along with the network connecting base stations (e.g., Ater and Abis interfaces, and other examples) and base station controllers (e.g., A interface, and other examples), is a radio component of GSM or GSM EDGE. The radio access network represents the component of a GSM network through which telephone calls and packet data are routed from the Public Switched Telephone Network (PSTN) and the Internet to the subscriber's mobile phone (also referred to as the user terminal or user equipment (UE)) and from the subscriber's mobile phone to the PSTN and the Internet. A mobile phone operator's network may include one or more GERANs; in the case of UMTS or GSM networks, the GERAN may be coupled with the UTRAN. Additionally, an operator's network may include one or more LTE networks or one or more other networks. Different network types may use different radio access technologies (RATs) and radio access networks (RANs).

[0038] OFDMA networks can implement radio technologies such as Evolved UTRA (E-UTRA), IEEE 802.11, IEEE 802.16, IEEE 802.20, and Flash OFDM. UTRA, E-UTRA, and GSM are part of the Universal Mobile Telecommunications System (UMTS). Specifically, Long Term Evolution (LTE) is a version of UMTS using E-UTRA. UTRA, E-UTRA, GSM, UMTS, and LTE are described in documents from an organization called the 3rd Generation Partnership Project (3GPP), and cdma2000 is described in documents from an organization called 3rd Generation Partnership Project 2 (3GPP2). These various radio technologies and standards are either known or under development. For example, 3GPP is a collaboration among telecommunications associations aimed at defining globally applicable third-generation (3G) mobile phone specifications. 3GPP Long Term Evolution (LTE) is a 3GPP initiative aimed at improving the Universal Mobile Telecommunications System (UMTS) mobile phone standard. 3GPP can define specifications for next-generation mobile networks, mobile systems, and mobile devices. This disclosure may refer to LTE, 4G, 5G, or NR technologies in certain aspects; however, this description is not intended to be limited to any particular technology or application, and one or more aspects described with reference to one technology may be understood to be applicable to another technology. In fact, one or more aspects of this disclosure relate to shared access to radio spectrum between networks using different radio access technologies or radio air interfaces.

[0039] 5G networks are expected to enable diverse deployments, diverse spectrum, and diverse services and devices using a unified OFDM-based air interface. To achieve these goals, in addition to developing new radio technologies for 5G NR networks, further enhancements to LTE and LTE-A are also being considered. 5G NR will be able to scale to provide coverage for: (1) massive Internet of Things (IoT) coverage with ultra-high density (e.g., ~1M nodes / km2), ultra-low complexity (e.g., ~10s bits / second), ultra-low energy (e.g., ~10+ years of battery life) and deep coverage with the ability to reach challenging locations; (2) mission-critical control with strong security for protecting sensitive personal, financial or confidential information, ultra-high reliability (e.g., ~99.9999% reliability), ultra-low latency (e.g., ~1 millisecond (ms)) and a wide range of users with or without mobility; and (3) enhanced mobile broadband with ultra-high capacity (e.g., ~10Tbps / km2), extreme data rates (e.g., multi-Gbps rates, 100+Mbps user experience rates) and improved discovery and optimized deep sensing.

[0040] 5G NR devices, networks, and systems can be implemented using optimized OFDM-based waveform characteristics. These characteristics can include: scalable digital schemes and transmission time intervals (TTI); a common, flexible framework to efficiently multiplex services and characteristics using dynamic, low-latency time-division duplex (TDD) or frequency-division duplex (FDD) designs; and improved radio technologies such as massive MIMO, robust millimeter-wave (mmWave) transmission, advanced channel coding, and device-centric mobility. The scalability of the digital schemes in 5G NR (with scaling of subcarrier spacing) can efficiently address the operation of different services across different spectrums and deployments. For example, in various outdoor and macro coverage deployments implemented with FDD or TDD below 3 GHz, subcarrier spacing can occur at 15 kHz over bandwidths such as 1, 5, 10, and 20 MHz. For other various outdoor and small-cell coverage deployments with TDD above 3 GHz, subcarrier spacing can occur at 30 kHz over bandwidths of 80 or 100 MHz. For various other indoor broadband implementations using TDD on the unlicensed portion of the 5 GHz band, subcarrier spacing can occur at 60 kHz over a 160 MHz bandwidth. Finally, for various deployments utilizing mmWave components of TDD at 28 GHz, subcarrier spacing can occur at 120 kHz over a 500 MHz bandwidth.

[0041] 5G NR's scalable digital schemes facilitate scalable TTIs for varying latency and Quality of Service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. Efficient multiplexing of long and short TTIs allows transmissions to begin at symbol boundaries. 5G NR also anticipates self-contained integrated subframe designs where uplink or downlink scheduling information, data, and acknowledgments are contained within the same subframe. Self-contained integrated subframes support communication in unlicensed or contention-based shared spectrum, and adaptive uplink or downlink (which can be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet current service demands).

[0042] For clarity, certain aspects of the apparatus and technology may be described below with reference to example 5G NR implementations or in a 5G-centric manner, and 5G terminology may be used as illustrative examples in various sections of the description below; however, the description is not intended to be limited to 5G applications.

[0043] Furthermore, it should be understood that, in operation, wireless communication networks adapted according to the concepts herein can operate using any combination of licensed or unlicensed spectrum, depending on load and availability. Therefore, it will be apparent to those skilled in the art that the systems, apparatuses, and methods described herein can be applied to other communication systems and applications besides the specific examples provided.

[0044] Figure 1 This is a block diagram illustrating details of an example wireless communication system. The wireless communication system may include a wireless network 100. Wireless network 100 may, for example, include a 5G wireless network. As those skilled in the art will understand, in Figure 1 The components appearing in this may have corresponding counterparts in other network arrangements (including, for example, cellular network arrangements and non-cellular network arrangements such as device-to-device, peer-to-peer, or self-organizing network arrangements and other examples)).

[0045] exist Figure 1The wireless network 100 shown includes multiple base stations 105 and other network entities. A base station can be a station communicating with a UE and can be referred to as an evolved Node B (eNB), a next-generation eNB (gNB), an access point, etc. Each base station 105 can provide communication coverage for a specific geographic area. In 3GPP, the term "cell" can refer to that specific geographic coverage area of ​​a base station or a base station subsystem serving that coverage area, depending on the context in which the term is used. In the implementation of the wireless network 100 herein, base stations 105 can be associated with the same operator or different operators (e.g., the wireless network 100 may include multiple operator wireless networks). Additionally, in the implementation of the wireless network 100 herein, base station 105 can use one or more frequencies (e.g., one or more bands of licensed spectrum, unlicensed spectrum, or combinations thereof) from the same frequencies as neighboring cells to provide wireless communication. In some examples, a single base station 105 or UE 115 can be operated by more than one network operating entity. In some other examples, each base station 105 and UE 115 can be operated by a single network operating entity.

[0046] Base stations can provide communication coverage for macrocells, small cells (such as picocells or femtocells), or other types of cells. Macrocells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access by UEs with service subscriptions to a network provider. Small cells (such as picocells) will typically cover a relatively small geographic area and allow unrestricted access by UEs with service subscriptions to a network provider. Small cells (such as femtocells) will also typically cover a relatively small geographic area (such as a residential area) and, in addition to unrestricted access, provide restricted access by UEs associated with the femtocell (e.g., UEs in a Closed Subscriber Group (CSG), UEs for users in a residential area, etc.). Base stations used for macrocells can be called macro base stations. Base stations used for small cells can be called small cell base stations, picocells, femtocells, or home base stations. Figure 1 In the examples shown, base stations 105d and 105e are conventional macro base stations, while base stations 105a-105c are macro base stations implemented using one of 3D MIMO, full-dimensional (FD) MIMO, or massive MIMO. Base stations 105a-105c utilize their higher-dimensional MIMO capabilities to employ 3D beamforming in both elevation and azimuth beamforming to increase coverage and capacity. Base station 105f is a small cell base station, which can be a home node or a portable access point. A base station can support one or more cells (such as two cells, three cells, four cells, etc.).

[0047] Wireless Network 100 can support synchronous or asynchronous operation. For synchronous operation, base stations can have similar frame timings, and transmissions from different base stations can be approximately time-aligned. For asynchronous operation, base stations can have different frame timings, and transmissions from different base stations can be time-disaligned. In some scenarios, the network can be enabled or configured to handle dynamic switching between synchronous and asynchronous operation.

[0048] UE 115 is distributed throughout the wireless network 100, and each UE can be stationary or mobile. It should be understood that although mobile devices are generally referred to as User Equipment (UE) in standards and specifications published by 3GPP, such devices may be otherwise referred to by those skilled in the art as mobile station (MS), subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile subscriber station, access terminal (AT), mobile terminal, radio terminal, remote terminal, handphone, terminal, user agent, mobile client, client, or some other suitable term. Within this document, a “mobile” device or UE does not necessarily need to be mobile and can be stationary. Some non-limiting examples of mobile devices may include implementations of one or more of UE 115, including mobile devices, cellular phones, smartphones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, laptop computers, personal computers (PCs), notebooks, netbooks, smartbooks, tablet devices, and personal digital assistants (PDAs). Mobile devices can also be “Internet of Things” (IoT) or “Internet of Everything” (IoE) devices, such as automobiles or other vehicles, satellite radio units, Global Positioning System (GPS) devices, logistics controllers, drones, multi-wing aircraft, quadcopters, smart energy or security devices, solar panels or solar arrays, municipal lighting, water supply or other infrastructure; industrial automation and enterprise equipment; consumer and wearable devices, such as glasses, wearable cameras, smartwatches, health or fitness trackers, mammalian implantable devices, posture tracking devices, medical devices, digital audio players (such as MP3 players), cameras or game consoles, and other examples; and digital home or smart home devices, such as home audio, video and multimedia equipment, appliances, sensors, vending machines, smart lighting, home security systems or smart meters, and other examples. In one aspect, the UE can be a device that includes a Universal Integrated Circuit Card (UICC). In another aspect, the UE 115 can be a device that does not include a UICC. In some aspects, a UE that does not include a UICC can be referred to as an IoE device. Figure 1The UEs 115a-115d shown in the implementation are examples of mobile smartphone-type devices accessing the wireless network 100. The UE can be a machine specifically configured for connected communications, including Machine-Type Communication (MTC), Enhanced MTC (eMTC), Narrowband IoT (NB-IoT), etc. Figure 1 The UE 115e-115k shown is an example of various machines configured for communication access to the 5G network 100.

[0049] Mobile devices (such as UE 115) can communicate with any type of base station (whether macro base station, pico base station, femto base station, repeater, etc.). Figure 1 In this context, a communication link (represented by a lightning bolt) indicates a radio transmission between the UE and a serving base station (which is designated to serve the UE on the downlink or uplink), or a desired transmission between base stations, and a backhaul transmission between base stations. Backhaul communication between base stations of the wireless network 100 can occur using wired or wireless communication links.

[0050] In the operation of the 5G network 100, base stations 105a-105c use 3D beamforming and cooperative spatial technologies (such as Cooperative Multipoint (CoMP) or Multi-Connection) to serve UEs 115a and 115b. Macro base station 105d performs backhaul communication with base stations 105a-105c and the small cell (base station 105f). Macro base station 105d also transmits multicast services customized and received by UEs 115c and 115d. Such multicast services may include mobile television or streaming video, or may include other services for providing community information, such as weather emergencies or alerts (such as Amber Alerts or Grey Alerts).

[0051] Each implemented wireless network 100 supports mission-critical communication for mission-critical devices (such as UE 115e, which is a drone) using ultra-reliable and redundant links. Redundant communication links with UE 115e include those from macro base stations 105d and 105e, and from small cell base station 105f. Other machine-type devices (such as UE 115f (thermometer), UE 115g (smart meter), and UE 115h (wearable device)) can communicate directly with base stations (such as small cell base station 105f and macro base station 105e) via wireless network 100, or via another user device relaying its information to the network (such as UE 115f transmitting temperature measurement information to a smart meter (UE 115g), which is then reported to the network via small cell base station 105f) in a multi-hop configuration. The 5G network 100 can provide additional network efficiency through dynamic, low-latency TDD or FDD communication, such as in vehicle-to-vehicle (V2V) mesh networks between UEs 115i-115k communicating with macro base station 105e.

[0052] Figure 2 This is a block diagram conceptually illustrating an example design for base station 105 and UE 115. Base station 105 and UE 115 can be... Figure 1 One of the base stations and one of the UEs. For restricted association scenarios (as mentioned above), base station 105 can be... Figure 1 The base station 105f is a small cell base station, and UE 115 can be UE 115c or 115d operating within the service area of ​​base station 105f. In order to access small cell base station 105f, UE 115c or 115d will be included in the list of accessible UEs for small cell base station 105f. Alternatively, base station 105 can be some other type of base station. Figure 2 As shown, base station 105 may be equipped with antennas 234a to 234t, and UE 115 may be equipped with antennas 252a to 252r to facilitate wireless communication.

[0053] At base station 105, transmit processor 220 can receive data from data source 212 and control information from controller 240. The control information can be used for the Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), Physical Hybrid ARQ (Automatic Repeat Request) Indicator Channel (PHICH), Physical Downlink Control Channel (PDCCH), Enhanced Physical Downlink Control Channel (EPDCCH), or MTC Physical Downlink Control Channel (MPDCCH), and other examples. Data can be used for PDSCH, and other examples. Transmit processor 220 can process (e.g., encoding and symbol mapping) the data and control information separately to obtain data symbols and control symbols. Additionally, transmit processor 220 can generate reference symbols such as those for primary synchronization signals (PSS) and secondary synchronization signals (SSS) and cell-specific reference signals. Transmit (TX) Multiple-Input Multiple-Output (MIMO) processor 230 can perform spatial processing (if applicable) on data symbols, control symbols, or reference symbols, and can provide output symbol streams to modulators (MODs) 232a to 232t. For example, spatial processing performed on data symbols, control symbols, or reference symbols may include precoding. Each modulator 232 may (such as for OFDM and other examples) process the corresponding output symbol stream to obtain an output sample stream. Each modulator 232 may additionally or alternatively process the output sample stream to obtain a downlink signal. For example, to process the output sample stream, each modulator 232 may convert the output sample stream to analog, amplify, filter, and up-convert it to obtain a downlink signal. The downlink signal from modulators 232a to 232t may be transmitted via antennas 234a to 234t, respectively.

[0054] At UE 115, antennas 252a to 252r can receive downlink signals from base station 105 and can provide the received signals to demodulators (DEMODs) 254a to 254r respectively. Each demodulator 254 can adjust the corresponding received signal to obtain an input sample. For example, to adjust the corresponding received signal, each demodulator 254 can filter, amplify, down-convert, and digitize the corresponding received signal to obtain an input sample. Each demodulator 254 can further process the input sample (such as for OFDM and other examples) to obtain received symbols. MIMO detector 256 can obtain the received symbols from demodulators 254a to 254r, perform MIMO detection on the received symbols (if applicable), and provide the detected symbols. Receiver processor 258 can process the detected symbols, provide decoded data for UE 115 to data sink 260, and provide decoded control information to controller 280. For example, to process the detected symbols, receive processor 258 can demodulate, deinterleave, and decode the detected symbols.

[0055] On the uplink, at UE 115, transmit processor 264 can receive and process data from data source 262 (such as for the Physical Uplink Shared Channel (PUSCH)) and control information from controller 280 (such as for the Physical Uplink Control Channel (PUCCH)). Additionally, transmit processor 264 can generate reference symbols for reference signals. Symbols from transmit processor 264 can be pre-encoded (if applicable) by TX MIMO processor 266, further processed by modulators 254a to 254r (such as for SC-FDM and other examples), and transmitted to base station 105. At base station 105, uplink signals from UE 115 can be received by antenna 234, processed by demodulator 232, detected by MIMO detector 236 (if applicable), and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 115. The receiver processor 238 can provide decoded data to the data sink 239 and decoded control information to the controller / processor 240.

[0056] Controllers 240 and 280 can respectively direct operations at base station 105 and UE 115. Controller 240 or other processors and modules at base station 105, or controller 280 or other processors and modules at UE 115, can execute or direct the execution of various processes used in the techniques described herein, such as executing or directing operations at... Figure 8 and 9 The execution and / or other processes used in the techniques described herein are shown in the diagram. Memory 242 and 282 may store data and program code for base station 105 and UE 115, respectively. Scheduler 244 may schedule the UE to transmit data on the downlink or uplink.

[0057] In some cases, UE 115 and base station 105 may operate in a shared radio frequency spectrum band, which may include licensed or unlicensed (such as contention-based) spectrum. In the unlicensed frequency portion of the shared radio frequency spectrum band, UE 115 or base station 105 may typically perform a medium sensing procedure to compete for access to the spectrum. For example, UE 115 or base station 105 may perform a Listen-Before-Speak or Listen-Before-Transmit (LBT) procedure (such as Clear Channel Assessment (CCA)) before communication to determine whether the shared channel is available. CCA may include a power detection procedure to determine if any other active transmissions are present. For example, the device may infer that a change in the Received Signal Strength Indicator (RSSI) of the power meter indicates that the channel is occupied. Specifically, a signal power concentrated in a bandwidth and exceeding a predetermined noise floor may indicate another wireless transmitter. In some implementations, CCA may include the detection of a specific sequence indicating channel usage. For example, another device may send a specific preamble before transmitting a data sequence. In some cases, the LBT process may include: the wireless node adjusting its own backoff window based on the amount of energy detected on the channel or on the acknowledgment or negative acknowledgment (ACK or NACK) feedback of packets it sends as a proxy for collisions.

[0058] In examples of Multimedia Broadcast Multicast Service (MBMS) systems, the base station may indicate multiple K1 and PRI fields in different fields of the GC-PDCCH transmission grant. In these example systems, each UE receiving the GC-PDCCH transmission can be configured to monitor one of the multiple K1 and PRI fields. In some examples, multiple UEs can be configured to monitor the same K1 and PRI fields, but can also be configured to interpret the same PRI field in different ways. In such examples, multiple UEs configured to monitor the same PRI field but interpret the PRI differently can determine which feedback resources (such as PUCCH resources) to report for the feedback codebook of the GC-PDSCH transmission granted in the GC-PDCCH transmission grant. However, in these example systems, indicating multiple K1 and PRI causes feedback codebook misalignment problems. For example, since different UEs may report feedback codebooks for different GC-PDSCH transmissions at the same PUCCH timing, the feedback codebooks reported by different UEs may have different sizes.

[0059] In summary, the various aspects disclosed herein relate to the management and control of feedback reporting associated with broadcast or multicast transmissions. More specifically, some aspects of this disclosure relate to enabling a group of UEs to report feedback to a base station for Group Common (GC)-Physical Downlink Shared Channel (GC-PDSCH) transmissions associated with Multimedia Broadcast Multicast Service (MBMS). In some examples, the base station may schedule and send GC-Physical Downlink Control Channel (GC-PDCCH) transmission grants, which schedule corresponding GC-PDSCH transmissions and also include feedback control information. UEs or sets of UEs in a group receiving GC-PDSCH transmissions may use the feedback control information to determine the appropriate feedback resource in which to report feedback codebooks for GC-PDSCH transmissions. For example, the base station may send a GC-PDCCH transmission grant to a group of UEs, the GC-PDCCH transmission grant including a common feedback timing indicator (K1) and multiple distinct Physical Uplink Control Channel (PUCCH) Resource Indicators (PRI), each PRI associated with a corresponding UE in the UE set. Each UE in the UE set can use the common K1 indicator to determine the same time (such as within a time slot or sub-time slot) and can use its corresponding PRI to determine the PUCCH resource for reporting its feedback codebook within the time slot or sub-time slot.

[0060] Alternatively, the base station may send a GC-PDCCH transmission grant to the group of UEs, the GC-PDCCH transmission grant including an indication of one or more scheduling constraints to limit feedback reporting from individual UEs in the group such that the feedback codebooks reported by the UEs in PUCCH timings each have the same size. In some examples, the base station may configure the scheduling constraints by indicating different corresponding K1s to different UEs in the group to ensure that, for a given PUCCH timing, different UEs report feedback for the same number of GC-PDSCH transmissions. In some other examples, each UE may be configured with a relative K1, which the UE can add to the K1 indicated by the base station in the GC-PDCCH transmission grant to obtain a total K1. In such examples, each UE can use its corresponding total K1 to determine the feedback resources in which to report the feedback codebook for the GC-PDSCH transmissions associated with the GC-PDCCH transmission grant.

[0061] Specific implementations of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some aspects, the techniques described herein enable feedback to be reported from a group of UEs to a base station, such that the feedback codebooks reported by different UEs at PUCCH timings have the same size. In such aspects, the base station can send GC-PDCCH transmission grants including one or more K1 fields while ensuring that the feedback codebooks reported from different UEs at PUCCH timings have the same size.

[0062] Figure 3This is a timing diagram illustrating an example of reporting feedback for multicast transmissions associated with multicast transmission grants including multiple K1 fields and multiple PRI fields. Specifically, UE0-UE2 may receive multiple multicast transmissions at different times. For example, multiple multicast GC-PDSCH (GC-PDSCH0 to GC-PDSCH2) transmissions may be sent from the base station. In this example, the base station may address the GC-PDSCH transmissions (GC-PDSCH0 to GC-PDSCH2) to UE0-UE2. In this example, each of UE0-UE2 may generate a feedback codebook to report feedback for each of these GC-PDSCH transmissions (GC-PDSCH0 to GC-PDSCH2). However, in this example, the base station may have already indicated different K1 and PRI in different fields of the GC-PDCCH transmission grant associated with each of GC-PDSCH0 to GC-PDSCH2. In such an example, each of UE0-UE2 can be configured to monitor different K1 fields. In this case, each of UE0-UE2 can report a feedback codebook to the base station at different times and on different resources, based on the separately indicated K1 and PRI. For example, UE0 can generate a feedback report for a GC-PDSCH0 transmission and can be configured (e.g., by K1 and PRI indications in a GC-PDCCH transmission authorizing the GC-PDSCH0 transmission) to report a feedback codebook for GC-PDSCH0 in the PUCCH sent from UE0 to the base station at 350. In this case, the feedback codebook reported by UE0 at 350 includes ACK / NACK information for a GC-PDSCH transmission. However, UE0 can also generate feedback reports for GC-PDSCH1 and GC-PDSCH2 transmissions, and can be configured (e.g., via K1 and PRI indications in a GC-PDCCH transmission authorizing GC-PDSCH1 and GC-PDSCH2 transmissions) to report feedback codebooks for GC-PDSCH1 and GC-PDSCH2 together in a PUCCH transmitted at 352. In this case, the feedback codebook reported by UE0 at 352 can include ACK / NACK information for both GC-PDSCH transmissions (instead of one GC-PDSCH transmission). In this example, UE1 reports a feedback codebook including ACK / NACK information for two GC-PDSCH transmissions (such as GC-PDSCH0 and GC-PDSCH1) in a PUCCH transmitted at 351, and reports a feedback codebook including ACK / NACK information for one GC-PDSCH transmission (such as GC-PDSCH2) in a PUCCH transmitted at 352.In this example, UE2 reports a feedback codebook in the PUCCH sent at position 352, which includes ACK / NACK information for three GC-PDSCH transmissions (such as GC-PDSCH0 to GC-PDSCH2).

[0063] Therefore, from Figure 3 As the example shown illustrates, because multiple K1 and PRI values ​​are signaled to different UEs, the UE can report feedback codebooks of different sizes from different UEs at various PUCCH times. Due to the size of the feedback codebooks reported by each UE, managing the downlink allocation index (DAI) counter for GC-PDCCH transmission grants becomes very difficult.

[0064] Figure 4 This diagram illustrates an example communication flow 400 between a UE and a base station according to some aspects of this disclosure, which implements management and control of reported multicast transmission feedback. In some examples, the wireless communication system 400 may implement various aspects of the wireless network 100. The wireless communication system 400 includes a UE 115 and a base station 105. Although one UE 115 and one base station 105 are shown, in some other implementations, the wireless communication system 400 may typically include multiple UEs 115 and may include more than one base station 105.

[0065] UE 115 may include various components (such as architecture, hardware components) for performing one or more of the functions described herein. For example, these components may include one or more processors 402 (hereinafter collectively referred to as “processor 402”), one or more memory devices 404 (hereinafter collectively referred to as “memory 404”), one or more transmitters 416 (hereinafter collectively referred to as “transmitter 416”), and one or more receivers 418 (hereinafter collectively referred to as “receiver 418”). Processor 402 may be configured to execute instructions stored in memory 404 to perform the operations described herein. In some implementations, processor 402 includes or corresponds to one or more of receive processor 258, transmit processor 264, and controller 280, and memory 404 includes or corresponds to memory 282.

[0066] Transmitter 416 is configured to transmit reference signals, control information, and data to one or more other devices, and receiver 418 is configured to receive reference signals, synchronization signals, control information, and data from one or more other devices. For example, transmitter 416 may transmit signaling, control information, and data to base station 105, and receiver 418 may receive signaling, control information, and data from base station 105. In some implementations, transmitter 416 and receiver 418 may be integrated into one or more transceivers. Alternatively or additionally, transmitter 416 or receiver 418 may include or correspond to a reference signal. Figure 2 One or more components of the UE 115 described.

[0067] Base station 105 may include various components (such as architecture, hardware components) for performing one or more of the functions described herein. For example, these components may include one or more processors 452 (hereinafter collectively referred to as "processor 452"), one or more memory devices 454 (hereinafter collectively referred to as "memory 454"), one or more transmitters 456 (hereinafter collectively referred to as "transmitter 456"), and one or more receivers 458 (hereinafter collectively referred to as "receiver 458"). Processor 452 may be configured to execute instructions stored in memory 454 to perform the operations described herein. In some implementations, processor 452 includes or corresponds to one or more of receiver processor 238, transmitter processor 220, and controller 240, and memory 454 includes or corresponds to memory 242.

[0068] Transmitter 456 is configured to transmit reference signals, synchronization signals, control information, and data to one or more other devices, and receiver 458 is configured to receive reference signals, control information, and data from one or more other devices. For example, transmitter 456 may transmit signaling, control information, and data to UE 115, and receiver 458 may receive signaling, control information, and data from UE 115. In some implementations, transmitter 456 and receiver 458 may be integrated into one or more transceivers. Alternatively or additionally, transmitter 456 or receiver 458 may include or correspond to a reference signal. Figure 2 One or more components of the described base station 105.

[0069] In some implementations, the wireless communication system 400 implements a 5G New Radio (NR) network. For example, the wireless communication system 400 may include multiple 5G-capable UEs 115 and multiple 5G-capable base stations 105, such as UEs and base stations configured to operate according to 5G NR network protocols, such as the 5G NR network protocols defined by 3GPP.

[0070] During operation of the wireless communication system 400, base station 105 may send multiple multicast transmission grant messages 470. For example, base station 105 may send multiple GC-PDCCH transmissions, and each GC-PDCCH transmission may grant an associated GC-PDSCH transmission. In various aspects, base station 105 may address GC-PDCCH transmission grants (and associated GC-PDSCH transmissions) to multiple UEs, which may include UE 115. Base station 105 may configure GC-PDCCH transmission grants to include configurations and parameters for the associated GC-PDSCH transmissions. For example, a GC-PDCCH transmission may specify the resources in which a UE may receive a GC-PDSCH transmission, and may also specify and define parameters for feedback reporting. As discussed above, in some implementations, GC-PDCCH transmission grants may include at least one K1 in each GC-PDCCH transmission grant. In some implementations, each GC-PDCCH transmission grant may include multiple K1 fields. In these implementations, different UEs among the multiple UEs addressed by the GC-PDCCH transport grant can be configured to monitor different K1 fields.

[0071] In some embodiments, as will be discussed in more detail below, each GC-PDCCH transmission grant may include a common K1, which may be used by each of a plurality of UEs to determine timing resources in which to report feedback codebooks for GC-PDSCH transmissions associated with the GC-PDCCH transmission. In these embodiments, although the GC-PDCCH transmission grant may specify a common K1, the GC-PDCCH transmission grant may include multiple PRI fields, each PRI field specifying a different PRI for each of the plurality of UEs. In this case, a UE (such as UE 115) may use the common K1 to determine the time slots and / or sub-time slots for reporting feedback codebooks associated with the granted GC-PDSCH transmission, and may use the corresponding PRI to determine the resources in which to report the feedback codebook within the time slot / sub-time slot.

[0072] In some embodiments, as will be discussed in more detail below, it may be permissible for both K1 and PRI in a GC-PDCCH transmission grant to be different for different UEs among multiple UEs (instead of a common K1). However, in these embodiments, the base station may configure the GC-PDCCH transmission grant to specify scheduling constraints for feedback reporting that may limit feedback codebooks reported by different UEs based on different K1s to the same composition and / or size. In these embodiments, the base station may signal the K1 for each of the different UEs to enforce the scheduling constraints. For example, a base station (such as base station 105) may send multiple GC-PDCCH transmission grants, each granting GC-PDSCH transmissions to multiple UEs. In each GC-PDCCH transmission grant, the base station may signal different K1 indications to the UEs among the multiple UEs. The UEs among the multiple UEs may use the different K1s to determine the feedback reporting timing (such as PUCCH timing) for reporting the feedback codebook associated with the granted GC-PDSCH transmission. For example, a first UE can use the K1 indication in the first GC-PDCCH transmission grant and the K1 indication in the second GC-PDCCH transmission grant to determine the PUCCH timing to report feedback codebooks for GC-PDSCH transmissions associated with the first and second GC-PDCCH transmission grants. In this example, a second UE can also use the K1 indication in the first GC-PDCCH transmission grant and the K1 indication in the second GC-PDCCH transmission grant to determine the PUCCH timing to report feedback codebooks for GC-PDSCH transmissions associated with the first and second GC-PDCCH transmission grants. In this example, based on scheduling constraints configured by the base station, the composition and / or size of the feedback codebooks reported by the first UE and the feedback codebooks reported by the second UE can be the same. For example, the K1 indicated by the base station can restrict the feedback codebook from the first UE to include only feedback reports (such as ACK / NACK) for the first GC-PDSCH transmission. In this case, the K1 indicated by the base station can also restrict the feedback codebook from the second UE to include only feedback reports for a single GC-PDSCH transmission (such as the first GC-PDSCH transmission). On the other hand, K1 indicated by the base station can cause the feedback codebook from the first UE to include feedback reports for the first GC-PDSCH transmission and the second GC-PDSCH transmission. In this case, K1 indicated by the base station can also cause the feedback codebook from the second UE to include feedback reports for the first GC-PDSCH transmission and the second GC-PDSCH transmission.

[0073] In some embodiments, the scheduling constraints described above can be achieved by configuring relative K1 for each of a plurality of UEs. In various embodiments, the relative K1 for a UE can be UE-specific and can be a fixed value. In various embodiments, the relative K1 for different UEs can be different. In various embodiments, a UE can add the relative K1 value to the K1 value indicated by a base station (such as base station 105) in a GC-PDCCH transmission grant. A UE (such as UE 115) can use the total K1 value (such as the indicated K1 plus the relative K1) to determine the resources to report in a PUCCH transmission for a feedback codebook associated with a GC-PDCCH transmission grant. In various embodiments, the relative K1 can provide a manner for distributing feedback reports associated with GC-PDSCH transmissions over time in a fixed relative pattern. In this approach, a base station can signal different K1 values ​​to multiple UEs in a multicast transmission grant, but for each UE, the feedback codebook for each PUCCH timing can be the same. In these implementations, the UE's configuration relative to K1 ensures that the codebook size reported by different UEs can be the same for each PUCCH timing.

[0074] During operation, base station 105 may send message 471, which may include at least one multicast transmission associated with at least one of a plurality of multicast transmission grants. As described above, the base station may send GC-PDSCH transmissions granted in each of the plurality of GC-PDCCH transmission grants. In various embodiments, a plurality of UEs, including UE 115, may receive GC-PDSCH transmissions.

[0075] During operation, UE 115 may send message 472, which may include a feedback codebook for GC-PDSCH transmissions sent by base station 105. In various embodiments, as discussed above, the feedback codebook may include feedback (such as ACK / NACK feedback) information for GC-PDSCH transmissions sent by base station 105. In various embodiments, the feedback codebook may include feedback information for one or more GC-PDSCH transmissions.

[0076] In various embodiments, UE 115 can determine the resources in which to send a feedback codebook to the base station. As described above, determining the resources in which to send a feedback codebook for GC-PDSCH transmissions to the base station can be based on K1 and PRI indicated in the GC-PDCCH transmission grant associated with the GC-PDSCH transmission. In some embodiments of this disclosure, as described above, the base station can signal a common K1. In some embodiments, the base station can signal different K1 values ​​to different UEs, but the base station can configure scheduling constraints such that the feedback codebook sent by the UE in a PUCCH timing is the same as the feedback codebook sent by each of a plurality of UEs in the same PUCCH timing. In some embodiments, UE 115 can be configured with a fixed relative K1. The relative K1 of UE 115 can be added to the K1 indicated in the GC-PDCCH transmission grant, and the total K1 value can be used to determine the resources in which to send a feedback codebook in the PUCCH.

[0077] Figure 5 This is a timing diagram 500 illustrating an example of feedback transmissions for multicast transmissions associated with multicast transmission grants according to some aspects of this disclosure, the multicast transmission grants including a common K1 and multiple PRIs. As shown, a base station (such as base station 105) can send multiple multicast transmission grants. For example, base station 105 can send multiple GC-PDCCH transmissions, wherein each GC-PDCCH transmission grants a GC-PDSCH transmission. In various embodiments, base station 105 can utilize control information (such as downlink control information (DCI) messages) including a common K1 to configure the GC-PDCCH transmission grants. In various embodiments, the common K1 can be a value in a field of each GC-PDCCH transmission grant. Each of a plurality of UEs can use the common K1 to determine the timing resources in which to report a feedback codebook for a GC-PDSCH transmission associated with the corresponding GC-PDCCH transmission. For example, base station 105 may specify a common K1 in a first multicast transmission grant 510 among multiple multicast transmission grants. Each of UE0-UE2 can use the common K1 to determine that the feedback codebook for the first multicast transmission associated with the first multicast transmission grant 510 will be reported by each of UE0-UE2 in resource 510. In various embodiments, resource 510 may be a time slot and / or a sub-time slot. In this case, each of the multiple UEs may report the feedback codebook in the same time slot / sub-time slot. Therefore, the size of the feedback codebook transmitted for each of the UEs during the PUCCH timing is the same.

[0078] In various embodiments, in addition to the common K1 indication, the base station may include multiple PRI indications (such as in different fields of the GC-PDCCH transmission grant) in each of the multiple GC-PDCCH transmission grants. In various embodiments, each UE may be configured to monitor different PRI fields. In this way, although multiple UEs are configured to report feedback codebooks for GC-PDSCH transmissions in the same time slot / sub-time slot, the feedback codebook report for each UE may be reported in different resources of the same time slot / sub-time slot. For example, UE0 may send feedback codebook 550 in resource 560, UE1 may send feedback codebook 550 in resource 561, and UE2 may send feedback codebook 550 in resource 562. In this example, each of resources 560-562 is a different resource within time slot / sub-time slot 510.

[0079] In various embodiments, a common counter DAI can be implemented. Specifically, since the size of the feedback codebook transmitted for multiple UEs in each PUCCH timing is the same, a common counter DAI can be used. The common counter DAI can be reset when a new K1 timing is selected for all UEs across multiple UEs. In various embodiments, the common counter DAI can be incremented for each GC-PDCCH in which the same K1 timing is used.

[0080] Figure 6This is a timing diagram 600 illustrating an example of feedback transmissions for multicast transmissions reported based on scheduling constraints according to some aspects of this disclosure. As shown, a base station (such as base station 105) can send multiple multicast transmission grants. For example, base station 105 can send multiple GC-PDCCH transmissions, each GC-PDCCH transmission granting a GC-PDSCH transmission (such as GC-PDSCH0, GC-PDSCH1, and GC-PDSCH2). In various embodiments, base station 105 can configure the GC-PDCCH transmission grants that grant the transmissions of GC-PDSCH0, GC-PDSCH1, and GC-PDSCH2 to include K1 for each of UE0 and UE1, K1 constraining the scheduling of feedback codebooks for each GC-PDSCH0, GC-PDSCH1, and GC-PDSCH2 such that each feedback codebook sent by UE0 and UE1 within each PUCCH timing has the same size. For example, UE0 and UE1 can be configured (e.g., by base station 105) to send a feedback codebook during the first PUCCH timing, which includes feedback (such as ACK / NACK) for a single GC-PDSCH transmission (such as GC-PDSCH0). For example, base station 105 can configure a GC-PDCCH transmission authorized for GC-PDSCH0 to include K1, which configures UE0 to send feedback (such as HARQ feedback) for GC-PDSCH0 at 650 during UE0's first PUCCH timing. In this example, base station 105 can configure a GC-PDCCH transmission authorized for GC-PDSCH0 to include K1, which configures UE1 to send feedback (such as HARQ feedback) for GC-PDSCH0 at 651 during UE1's first PUCCH timing. In this scenario, UE0 can send a feedback codebook 610 for GC-PDSCH0 in PUCCH resource 650, and UE1 can send a feedback codebook 621 for GC-PDSCH0 in PUCCH resource 651. In this case, the feedback codebooks 610 and 621 sent by UE0 and UE1 during their first PUCCH timing can have the same size.

[0081] In this example, UE0 and UE1 can be configured (e.g., by base station 105) to send a feedback codebook during the second PUCCH timing. This feedback codebook includes feedback (such as ACK / NACK) for two GC-PDSCH transmissions (such as GC-PDSCH1 and GC-PDSCH2). In this case, UE0 can send a feedback codebook 612 for GC-PDSCH1 and GC-PDSCH2 in PUCCH resource 652. Similarly, UE1 can send a feedback codebook 622 for GC-PDSCH1 and GC-PDSCH2 in PUCCH resource 652. In this case, feedback codebooks 612 and 622 can have the same size (e.g., they can include feedback information for both GC-PDSCH transmissions).

[0082] Figure 7 This is a timing diagram 700 illustrating an example of transmitting feedback transmissions on resources determined based on a relative K1, according to some aspects of this disclosure. As described above, the UE in the MBMS system can be configured with a relative K1 that can be used as a scheduling constraint to ensure that each feedback codebook transmitted by the UE in each PUCCH timing has the same size as a feedback codebook transmitted by another UE in the same PUCCH timing, and to ensure that PUCCH transmissions including feedback codebooks are distributed over time. Figure 7As shown, base station 105 can transmit multiple GC-PDCCH transmissions, each GC-PDCCH transmission authorizing a GC-PDSCH transmission (such as GC-PDSCH0, GC-PDSCH1, and GC-PDSCH2). In various embodiments, base station 105 may include control information (such as a DCI message) in each of the GC-PDCCH transmission authorizations authorizing the transmissions of GC-PDSCH0, GC-PDSCH1, and GC-PDSCH2. This control information indicates K1, which a UE can use to determine the feedback resource for sending a feedback report for the corresponding GC-PDSCH transmission. For example, base station 105 may include K1 660 in the GC-PDCCH transmission authorization authorizing the GC-PDSCH0 transmission, and one or more UEs (such as UE0 and UE1) can use K1 660 to determine the feedback codebook to be reported in PUCCH resource 650, including feedback for the GC-PDSCH0 transmission. Similarly, base station 105 may include K1 661 in the GC-PDCCH transmission grant for GC-PDSCH1, and one or more UEs (such as UE0 and UE1) may use K1 661 to determine the feedback codebook to be reported in PUCCH resource 652, including feedback for GC-PDSCH1. Furthermore, base station 105 may include K1 662 in the GC-PDCCH transmission grant for GC-PDSCH2, and one or more UEs (such as UE0 and UE1) may use K1 662 to determine the feedback codebook to be reported in PUCCH resource 652, including feedback for GC-PDSCH2.

[0083] like Figure 7 As shown, each of UE0 and UE1 can be configured with a relative K1. For example, UE0 can be configured with a relative K1 670, and UE1 can be configured with a relative K1 671. In various embodiments, the UE can determine the resources for sending a feedback codebook to the base station based at least in part on the relative K1 and the indicated K1. In these embodiments, the UE can add the relative K1 to the indicated K1 to obtain a total K1. The UE can then use the total K1 to determine the feedback resources for reporting the feedback codebook to the base station. For example, when determining the resources for reporting feedback for GC-PDSCH0, UE0 can add the relative K1 670 to K1 660. The result of this sum can be used by UE0 to determine the feedback resources in which the feedback codebook 610 for GC-PDSCH0 is to be sent. When determining the resources for reporting feedback for GC-PDSCH0, UE1 can add the relative K1 671 to K1 660. The result of this sum can be used by UE1 to determine the feedback resources to be sent in the feedback codebook 621 for GC-PDSCH0.

[0084] In the same example, when determining the resources for reporting feedback for GC-PDSCH1 and GC-PDSCH2, UE0 can add the relevant K1 670 to K1 661 and K1 662 respectively. UE0 can use the result of the sum to determine the feedback resources in which to send feedback codebooks for GC-PDSCH1 and GC-PDSCH2 respectively. In this case, since feedback for GC-PDSCH1 and GC-PDSCH2 is reported in the same resources, the codebook reported by UE0 can include feedback reports for both GC-PDSCH1 and GC-PDSCH2. In this example, UE1 determines the resources for reporting feedback for GC-PDSCH1 and GC-PDSCH2 by adding the relative K1 671 to K1 661 and K1 662 respectively. UE1 can use the result of this sum to determine the feedback resources in which to send feedback codebooks for GC-PDSCH1 and GC-PDSCH2 respectively. In this case, UE1 can send a feedback codebook that includes feedback reports for both GC-PDSCH1 and GC-PDSCH2.

[0085] As will be understood, the feedback resources used by UE0 to transmit the feedback codebook 610 for GC-PDSCH0 may differ from the feedback resources used by UE1 to transmit the feedback codebook 621 for GC-PDSCH0, even if the indicated K1 660 is the same. In this example, without a relative K1 for each of UE0 and UE1, both UE0 and UE1 can determine the same feedback resources for transmitting the feedback codebook for GC-PDSCH0. Therefore, as disclosed herein, configuring the UEs in the MBMS system with a relative K1 enables the MBMS system to distribute the feedback reports associated with GC-PDSCH transmissions over time in a fixed relative pattern.

[0086] Figure 8 This is a flowchart illustrating an example process 800 for a support report regarding multicast transmission feedback, based on some aspects of this disclosure. The operation of process 800 can be performed by the UE, as described in the reference above. Figure 1-7 The UE 115 described or as referenced Figure 10 The UE described. For example, according to various aspects of this disclosure, example operations of process 800 (also referred to as “boxes”) can enable UE 115 to perform feedback for multicast (such as MBMS) transmissions.

[0087] In block 802, UE 115 receives multiple multicast transport grants addressed to a plurality of UEs including UE 115. For example, UE 115 may receive multiple GC-PDCCH transmissions, each GC-PDCCH transmission granting a GC-PDSCH transmission. In various embodiments, each multicast transport grant in the multicast transport grants may include at least one K1 and at least one PRI. The indicated K1 and PRI may be used by the UE for ACK / NACK feedback associated with the respective multicast transmission. In some embodiments, the indicated at least one K1 may include a common K1, which may be used by each of the plurality of UEs to determine the resources (such as time slots / sub-time slots) for reporting ACK / NACK feedback. In some embodiments, the indicated at least one K1 may include different K1s for different UEs among the plurality of UEs. In these cases, each of the plurality of UEs may be configured to monitor different K1 fields in the multicast transport grants, and in some embodiments, more than one UE may monitor the same K1 field.

[0088] In block 804, UE 115 receives from the base station a first multicast transmission associated with a first multicast transmission grant among a plurality of multicast transmission grants. For example, UE 115 may receive a first GC-PDSCH transmission associated with a first GC-PDCCH transmission grant.

[0089] In block 806, the first UE 115 determines a first feedback codebook for sending ACK / NACK feedback associated with the first multicast transmission to the base station. For example, UE 115 may generate a feedback report for the first GC-PDSCH transmission. The generated feedback report may be used to generate the first feedback codebook to be reported.

[0090] In block 808, the first UE 115 determines, at least in part, a first feedback resource for transmitting a feedback codebook for the first multicast transmission to the base station based on K1 and PRI in the first multicast transmission grant. For example, the UE 115 may determine, based on K1 and PRI in the first GC-PDCCH transmission grant, a first resource in the PUCCH for transmitting a feedback codebook associated with the first GC-PDSCH transmission.

[0091] In some implementations, the first feedback codebook may include additional feedback reports for other GC-PDSCH transmissions. For example, in some embodiments, UE 115 may determine feedback resources for reporting feedback for a second GC-PDSCH transmission, and the feedback resources for the second GC-PDSCH transmission may be the same as the feedback resources for the first GC-PDSCH transmission. In this case, the feedback codebook may include feedback reports for both the first and second GC-PDSCH transmissions.

[0092] In box 810, the first UE 115 sends a first feedback codebook to the base station on the determined first feedback resource.

[0093] Figure 9 This is a flowchart illustrating an example process 900 for managing and controlling feedback for multicast transmissions based on the configuration of K1 and PRI, according to some aspects of this disclosure. The operation of process 900 can be performed by a base station, as described in the reference above. Figure 1-7 The base station 105 described or as referenced Figure 11 The base station described. For example, according to various aspects of this disclosure, example operation of process 900 can enable base station 105 to control feedback for multicast (such as MBMS) transmissions.

[0094] In block 902, base station 105 sends multiple multicast transport grants to multiple UEs. For example, base station 105 may send multiple GC-PDCCH transmissions, each GC-PDCCH transmission granting GC-PDSCH transmissions to multiple UEs. In various embodiments, each multicast transport grant in the multicast transport grants may include at least one K1 and at least one PRI. The indicated K1 and PRI may be used by UEs among the multiple UEs for ACK / NACK feedback associated with the corresponding multicast transmission. In some embodiments, the indicated at least one K1 may include a common K1, which may be used by each of the multiple UEs to determine the resources (such as time slots / sub-time slots) for reporting ACK / NACK feedback. In some embodiments, the indicated at least one K1 may include different K1s for different UEs among the multiple UEs. In these cases, each of the multiple UEs may be configured to monitor different K1 fields in the multicast transport grants, and in some embodiments, more than one UE may monitor the same K1 field.

[0095] In block 904, base station 105 sends a first multicast transmission associated with a first multicast transmission grant in at least one multicast transmission grant to multiple UEs. For example, base station 105 may send a first GC-PDSCH transmission associated with a first GC-PDCCH transmission grant in a plurality of GC-PDCCH transmission grants. In various embodiments, the first GC-PDSCH transmission may address to multiple UEs.

[0096] In block 906, base station 105 receives at least one feedback codebook from at least one of a plurality of UEs, the at least one feedback codebook including ACK / NACK feedback associated with a first multicast transmission. For example, base station 105 may receive a first feedback codebook from UE 115 including ACK / NACK feedback associated with a first multicast transmission. In some embodiments, base station 105 may receive a second feedback codebook from another UE including ACK / NACK feedback associated with a first multicast transmission. In some embodiments, the first feedback codebook from UE 115 may additionally include ACK / NACK feedback for a second multicast transmission. For example, base station 105 may send a second multicast transmission to a plurality of UEs. UE 115 may generate ACK / NACK feedback for the second multicast transmission and may include the ACK / NACK feedback for the second multicast transmission in the first feedback codebook.

[0097] In some implementations, the feedback resources in which the UE transmits the feedback codebook for GC-PDSCH transmissions can be determined by the UE, for example, in part based on the K1 and PRI indications in the GC-PDSCH transmission grant sent by the base station. The determination of the feedback resources can be based on the above regarding... Figure 8 The discussion.

[0098] Figure 10 This is a block diagram of an example UE1000, providing feedback on multicast transmission based on some aspects of this disclosure. The UE1000 can be configured to perform operations, including referencing... Figure 8 The described process is a box 800. In some implementations, UE 1000 includes a reference. Figure 2 or Figure 3 The UE 1000 shows and describes the structure, hardware, and components. For example, UE 1000 includes a controller 280 that operates to execute logical or computer instructions stored in memory 282, and components that control UE 1000 and provide the features and functions of UE 1000. Under the control of controller 280, UE 1000 transmits and receives signals via wireless radio unit 1001a-r and antenna 252a-r. Wireless radio unit 1001a-r includes components as shown in... Figure 2 The various components and hardware shown for UE 115 include modulators and demodulators 254a-r, MIMO detector 256, receiver processor 258, transmitter processor 264 and TX MIMO processor 266.

[0099] As shown in the figure, the memory 282 may include receiving logic 1002 and feedback determination logic 1003. The receiving logic 1002 can be configured to perform signal receiving operations. According to this disclosure, the feedback determination logic 1003 can be configured to perform feedback codebook and resource determination operations. The UE 1000 can obtain data from one or more network entities (such as...) Figure 1-7 Base station 105 or such Figure 11 The base station shown in the figure receives signals or sends signals to it.

[0100] In some implementations, UE 1000 can be configured to perform Figure 8 The process is described in step 800. For example, under the control of controller 280, UE 1000 can execute receive logic 1002 and feedback determination logic 1003 stored in memory 282. The execution environment of receive logic 1002 provides functionality for performing at least the operations in block 802. The execution environment of feedback determination logic 1003 provides functionality for performing at least the operations in blocks 804-808.

[0101] Figure 11 This is a block diagram of an example base station 1100 that supports the management and control of feedback for multicast transmissions according to some aspects of this disclosure. Base station 1100 can be configured to perform operations, including referencing... Figure 9 The process described is a box 900. In some implementations, base station 1100 includes a reference... Figure 1-7 The base station 105 is shown and described in terms of its structure, hardware, and components. For example, base station 1100 may include a controller 240 that operates to execute logical or computer instructions stored in memory 242, as well as components that control base station 1100 and provide the features and functions of base station 1100. Under the control of controller 240, base station 1100 transmits and receives signals via wireless radio unit 1101a-t and antenna 234a-t. Wireless radio unit 1101a-t includes components as shown in... Figure 2 Various components and hardware are shown for base station 105, including modulators and demodulators 232a-t, transmit processor 220, TX MIMO processor 230, MIMO detector 236, and receive processor 238.

[0102] As shown in the figure, the memory 242 may include transmitting logic 1102 and receiving logic 1103. Transmitting logic 1102 can be configured to perform multicast transmission granting and multicast transmission operations. Receiving logic 1103 can be configured to perform feedback reception operations. The base station 1100 can receive data from one or more UEs (such as...). Figure 1-7 UE 115 or Figure 10 The UE 1000 receives signals or sends signals to it.

[0103] In some implementations, base station 1100 can be configured to perform Figure 9 The process is as follows: For example, under the control of controller 240, base station 111 can execute transmit logic 1102 and receive logic 1103 stored in memory 242. The execution environment of transmit logic 1102 provides functionality for performing at least the operations in blocks 902 and 904. The execution environment of receive logic 1103 provides functionality for performing at least the operations in block 906.

[0104] It should be noted that, for reference Figure 8 and 9 One or more boxes (or operations) described can be combined with one or more boxes (or operations) described with reference to another figure. For example, Figure 8 One or more boxes (or operations) can be combined with Figure 9 Combine one or more boxes (or operations). As another example, with Figure 10 Or 11 associated with one or more boxes can be and with Figure 2 Or, combine one or more related boxes (or operations).

[0105] In some aspects, techniques for managing and controlling feedback reports associated with broadcast or multicast transmissions may include additional aspects, such as any single aspect or any combination of aspects described below or in conjunction with one or more other processes or devices described elsewhere herein. In a first aspect, techniques for managing and controlling feedback reports associated with broadcast or multicast transmissions may include receiving multiple multicast transmission grants addressed to multiple UEs from a base station. Each of the multicast transmission grants schedules a multicast transmission and includes at least one K1 and at least one PRI for ACK / NACK feedback associated with the respective multicast transmission. The techniques in the first aspect may further include: receiving from a base station a first multicast transmission associated with a first multicast transmission grant among the multiple multicast transmission grants; determining a first feedback codebook for sending ACK / NACK feedback associated with the first multicast transmission to the base station; determining a first feedback resource for sending the first feedback codebook to the base station, at least in part based on at least one K1 and at least one PRI in the first multicast transmission grant; and sending the first feedback codebook to the base station on the determined first feedback resource. In some examples, the techniques in the first aspect may be implemented in a method or process. In some examples, the techniques of the first aspect can be implemented in a wireless communication device such as a UE or a component of a UE. In some examples, the wireless communication device may include at least one processing unit or system (which may include an application processor, modem, or other component) and at least one memory device coupled to the processing unit. The processing unit may be configured to perform the operations described herein with respect to the wireless communication device. In some examples, the memory device includes a non-transitory computer-readable medium having program code stored thereon, the program code being configured, when executed by the processing unit, to cause the wireless communication device to perform the operations described herein.

[0106] In the second aspect, either alone or in conjunction with the first aspect, at least one K1 in the first multicast transmission grant is a common K1 shared by each of the plurality of UEs, and at least one PRI in the first multicast transmission grant includes a PRI associated with that UE.

[0107] In the third aspect, either alone or in combination with one or more of the first to second aspects, at least one PRI includes another PRI associated with another UE among a plurality of UEs, the other PRI being associated with common K1 and different from the PRI associated with that UE.

[0108] In the fourth aspect, determining the first feedback resource for transmitting the feedback codebook to the base station, either alone or in combination with one or more of the first to third aspects, includes: determining at least one of the time slots or sub-time slots for transmitting the first feedback codebook based on a common K1 shared by each of the multiple UEs.

[0109] In the fifth aspect, in conjunction with the fourth aspect, determining the first feedback resource for sending the feedback codebook to the base station includes: determining resource elements in a time slot or sub-time slot for sending the first feedback codebook based on the PRI associated with the UE.

[0110] In the sixth aspect, either alone or in conjunction with the first aspect, at least one K1 in the first multicast transmission grant includes a K1 associated with a UE and another K1 in at least one K1 associated with another UE among a plurality of UEs, the other K1 being different from the K1.

[0111] In the seventh aspect, determining the first feedback codebook for reporting ACK / NACK feedback, including the first multicast transmission, to the base station, either alone or in combination with one or more aspects of the first and sixth aspects, includes: determining a first feedback codebook having the same structure as a second feedback codebook of another UE based on scheduling constraints, the scheduling constraints being used to restrict the scheduling of ACK / NACK feedback for different UEs at the same PUCCH timing, such that the feedback codebooks associated with the restricted ACK / NACK feedback have the same size for different UEs.

[0112] In the eighth aspect, determining the first feedback resource for sending the feedback codebook to the base station, either alone or in conjunction with the first aspect, includes adding the relative K1 associated with the UE to at least one K1 in the first multicast transmission grant to generate a total K1 associated with the UE.

[0113] In the ninth aspect, in conjunction with the eighth aspect, determining the first feedback resource for transmitting the feedback codebook to the base station includes: determining at least one of a time slot or sub-time slot for transmitting the first feedback codebook based on the total K1 associated with the UE.

[0114] In the tenth aspect, individually or in combination with one or more aspects of the first, eighth, and ninth aspects, each of the plurality of UEs is configured to be added to at least one K1 in the first multicast grant to determine a corresponding relative K1 for reporting ACK / NACK feedback for the first multicast transmission, respectively.

[0115] In the eleventh aspect, individually or in combination with one or more aspects of the first and eighth to tenth aspects, at least one PRI in the first multicast transport grant includes a PRI associated with a UE and another PRI associated with another UE among a plurality of UEs, the other PRI being different from the PRI associated with that UE.

[0116] In the twelfth aspect, either alone or in combination with one or more aspects of the first and eighth to eleventh aspects, the PRI associated with the UE is associated with the total K1 of the UE, and another PRI associated with another UE is associated with the total K1 of the other UE, the total K1 of the other UE being obtained by adding the relative K1 associated with the other UE to at least one K1.

[0117] In the thirteenth aspect, individually or in combination with one or more of the first and eighth to twelfth aspects, at least one PRI in the first multicast transport grant includes a PRI associated with a UE and another PRI associated with another UE among a plurality of UEs, the other PRI being different from the PRI associated with that UE.

[0118] In the fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, multicast transmission is MBMS transmission on the PDSCH.

[0119] In the fifteenth aspect, individually or in combination with one or more of the first to fourteenth aspects, each of the multiple multicast transport grants is received in the corresponding DCI message of the GC-PDCCH transport.

[0120] In the sixteenth aspect, techniques for managing and controlling feedback reports associated with broadcast or multicast transmissions may include sending multiple multicast transmission grants to multiple UEs. Each multicast transmission grant in the multicast transmission grant schedules a multicast transmission and includes at least one K1 and at least one PRI for ACK / NACK feedback associated with the respective multicast transmission. The techniques in the sixteenth aspect may further include: sending a first multicast transmission associated with a first multicast transmission grant in at least one multicast transmission grant to the multiple UEs; and receiving at least one feedback codebook from at least one of the multiple UEs. The at least one feedback codebook includes ACK / NACK feedback associated with the first multicast transmission. In some examples, the techniques in the sixteenth aspect may be implemented in a method or process. In some examples, the techniques in the sixteenth aspect may be implemented in a wireless communication device such as a base station or a component of a base station. In some examples, the wireless communication device may include at least one processing unit or system (which may include an application processor, modem, or other component) and at least one memory device coupled to the processing unit. The processing unit may be configured to perform the operations described herein with respect to the wireless communication device. In some examples, the memory device includes a non-transitory computer-readable medium having program code stored thereon, the program code being configured, when executed by a processing unit, to cause a wireless communication device to perform the operations described herein.

[0121] In the seventeenth aspect, in conjunction with the sixteenth aspect, at least one K1 in the first multicast transport grant is a common K1 shared by each of the plurality of UEs, and each PRI in the at least one PRI in the first multicast transport grant is associated with a corresponding UE. Each PRI in the at least one PRI is different from each of the other PRIs in the at least one PRI.

[0122] In the eighteenth aspect, alone or in combination with the sixteenth and seventeenth aspects, receiving at least one feedback codebook from at least one of a plurality of UEs includes: receiving a first feedback codebook report from a first UE of the plurality of UEs, the first feedback codebook report being received in a first resource element of a first time slot.

[0123] In the nineteenth aspect, in conjunction with the eighteenth aspect, receiving at least one feedback codebook from at least one of a plurality of UEs comprises: receiving a second feedback codebook report from a second of the plurality of UEs, the second feedback codebook report being received in a second resource element of a first time slot. The second resource element is different from the first resource element.

[0124] In the twentieth aspect, either alone or in combination with one or more aspects of aspects sixteen through nineteen, the technique of aspect sixteen includes: configuring each of a plurality of multicast transport grants to include a common counter DAI to indicate the number of multicast transport grants configured such that each of the plurality of UEs transmits a feedback codebook associated with the multicast transport grant based on a common K1 at the same PUCCH timing.

[0125] In the twenty-first aspect, alone or in combination with one or more aspects of the sixteenth to twentieth aspects, the technique of the sixteenth aspect includes configuring a common K1 in the first multicast transport grant such that each of the plurality of UEs transmits a feedback codebook associated with the first multicast transport grant during the first PUCCH timing.

[0126] In the twenty-second aspect, in conjunction with the twenty-first aspect, the technology of the sixteenth aspect includes: incrementing the common DAI counter in response to configuring a common K1 in the first multicast transport grant such that each of the plurality of UEs sends a feedback codebook associated with the first multicast transport grant at the first PUCCH timing.

[0127] In the twenty-third aspect, either alone or in combination with one or more aspects of aspects sixteen to twenty-two, the technique of aspect sixteen includes: configuring a common K1 in the second multicast transport grant such that each of the plurality of UEs transmits a feedback codebook associated with the second multicast transport grant during the first PUCCH timing.

[0128] In the twenty-fourth aspect, in conjunction with the twenty-third aspect, the sixteenth aspect includes: incrementing the common DAI counter in response to configuring a common K1 in the second multicast transport grant such that each of the plurality of UEs sends a feedback codebook associated with the second multicast transport grant during the first PUCCH timing.

[0129] In the twenty-fifth aspect, alone or in combination with one or more aspects of aspects sixteen to twenty-two, the technique of aspect sixteen includes: configuring a common K1 in a second multicast transport grant such that each of a plurality of UEs transmits a feedback codebook associated with the second multicast transport grant at a second PUCCH timing different from the first PUCCH timing.

[0130] In the 26th aspect, in conjunction with the 25th aspect, the technology of the 16th aspect includes: incrementing the common DAI counter in response to configuring a common K1 in the second multicast transport grant such that each of the plurality of UEs sends a feedback codebook associated with the second multicast transport grant during the second PUCCH timing.

[0131] In the twenty-seventh aspect, in conjunction with the sixteenth aspect, the technique of the sixteenth aspect includes: configuring a scheduling constraint for each of a plurality of UEs, the scheduling constraint being used to restrict the scheduling of ACK / NACK feedback for different UEs at the same PUCCH timing, such that the feedback codebook associated with the restricted ACK / NACK feedback has the same size for different UEs.

[0132] In the twenty-eighth aspect, receiving at least one feedback codebook from at least one of a plurality of UEs, either alone or in combination with one or more of the sixteenth and twenty-seventh aspects, comprises: receiving a first feedback codebook report associated with a first multicast transmission from a first UE of the plurality of UEs, the first feedback codebook report being received in a first time slot.

[0133] In the twentieth aspect, in conjunction with the twentieth aspect, receiving at least one feedback codebook from at least one of a plurality of UEs includes: receiving a second feedback codebook report associated with a first multicast transmission from a second of the plurality of UEs, the second feedback codebook report being received in a first time slot, the structure of the first feedback codebook being the same as the structure of the second feedback codebook.

[0134] In the thirtieth aspect, either alone or in combination with one or more of aspects sixteen and twenty-seven to twenty-nine, the technique of aspect sixteen includes: a base station transmitting a second multicast transmission associated with a second multicast transmission grant in at least one multicast transmission grant. A first feedback codebook report is additionally associated with the second multicast transmission, and a second feedback codebook report is additionally associated with the second multicast transmission.

[0135] In the thirty-first aspect, either alone or in combination with one or more of the sixteenth and twenty-seventh to thirtieth aspects, the technique of the sixteenth aspect includes: configuring each of a plurality of UEs with a corresponding relative K1 to be added to at least one K1 in each of at least one multicast transmission grant, to facilitate the determination of feedback resources for sending ACK / NACK feedback for the corresponding multicast grant.

[0136] In the thirty-second aspect, in conjunction with the sixteenth aspect, the technique of the sixteenth aspect includes: configuring each of a plurality of UEs with a corresponding relative K1, such that each UE adds the relative K1 to at least one K1 indicated in each multicast transmission grant to generate a total K1 associated with each UE.

[0137] In aspect thirty-three, in conjunction with aspect thirty-two, each of the plurality of UEs is configured with a corresponding relative K1 such that each UE determines, based on the total K1 associated with each UE, at least one of the time slots or sub-time slots for transmitting the feedback codebook associated with each multicast transmission grant.

[0138] In aspect thirty-four, alone or in combination with one or more aspects sixteen through thirty-three, multicast transmission is MBMS transmission on PDSCH.

[0139] In aspect 35, individually or in combination with one or more aspects from aspects 16 to 34, each of the multiple multicast transport grants is received in the corresponding DCI message of the GC-PDCCH transport.

[0140] Those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0141] about Figure 1-11 The components, functional blocks, and modules described include processors, electronic devices, hardware devices, electronic components, logic circuits, memory, software code, firmware code, and other examples, or any combination thereof. Furthermore, the features discussed herein can be implemented via dedicated processor circuitry, via executable instructions, or a combination thereof.

[0142] Those skilled in the art will also understand that the various illustrative logic blocks, modules, circuits, and algorithmic steps described in conjunction with the disclosure herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, the functionality of the various illustrative components, blocks, modules, circuits, and steps has been generally described above. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the described functionality in varying ways for each specific application, but such implementation decisions should not be construed as departing from the scope of this disclosure. Those skilled in the art will also readily recognize that the order or combination of components, methods, or interactions described herein is merely illustrative, and that components, methods, or interactions of various aspects of this disclosure can be combined or performed in ways different from those shown and described herein.

[0143] The various illustrative logics, logic blocks, modules, circuits, and algorithmic processes described herein can be implemented as electronic hardware, computer software, or a combination of both. The overall functionality has been described, and the interchangeability of hardware and software has been demonstrated in the various illustrative components, blocks, modules, circuits, and processes described above. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0144] Hardware and data processing apparatuses for implementing the various illustrative logics, logic blocks, modules, and circuits described in conjunction with the aspects disclosed herein may be implemented or executed using general-purpose single-chip or multi-chip processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor, controller, microcontroller, or state machine. In some implementations, the processor may be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. In some implementations, specific processes and methods may be executed by circuitry specific to a given function.

[0145] In one or more aspects, the described functionality can be implemented using hardware, digital electronic circuits, computer software, firmware (including the structures disclosed in this specification and their structural equivalents), or any combination thereof. Implementation of the subject matter described in this specification can also be implemented as one or more computer programs (which are one or more modules of computer program instructions) encoded on a computer storage medium for execution by a data processing apparatus or for controlling the operation of a data processing apparatus.

[0146] If implemented in software, the functionality can be stored on or transmitted via a computer-readable medium as one or more instructions or code. The processes of the methods or algorithms disclosed herein can be implemented in a processor-executable software module that can reside on a computer-readable medium. Computer-readable media include both computer storage media and communication media, wherein the communication medium includes any medium capable of transmitting a computer program from one place to another. Storage media can be any available medium accessible to a computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and is accessible to a computer. Furthermore, any connection can be suitably referred to as a computer-readable medium. As used herein, disks and optical discs include compact optical discs (CDs), laser optical discs, optical discs, digital versatile optical discs (DVDs), floppy disks, and Blu-ray discs, wherein disks typically magnetically copy data, while optical discs utilize lasers to optically copy data. Combinations of the above should also be included within the scope of computer-readable media. In addition, the operation of a method or algorithm may exist as one or any combination or set of code and instructions on a machine-readable medium and a computer-readable medium, which may be incorporated into a computer program product.

[0147] Various modifications to the implementations described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other implementations without departing from the spirit or scope of this disclosure. Therefore, the claims are not intended to limit them to the implementations shown herein, but are intended to impose the broadest scope consistent with this disclosure, the principles disclosed herein, and the novel features.

[0148] In addition, it will be readily apparent to those skilled in the art that the terms “upper” and “lower” are sometimes used for the convenience of describing the figure and indicate the relative position corresponding to the orientation of the figure on a properly oriented page, and may not reflect the correct orientation of any device as implemented.

[0149] Some features described in this specification in the context of separate implementations can also be implemented in combination in a single implementation. Conversely, individual features described in the context of a single implementation can also be implemented individually or in any suitable sub-combination in multiple implementations. Furthermore, although features may be described above as taking action in certain combinations, and even originally claimed in this manner, in some cases, one or more features from the claimed combination may be removed from that combination, and the claimed combination may involve sub-combinations or variations thereof.

[0150] Similarly, although operations are depicted in a specific order in the figures, this should not be construed as requiring such operations to be performed in the shown specific order or sequential order, or to perform all of the shown operations to achieve the desired result. Furthermore, the figures may schematically depict one or more example processes in the form of flowcharts. However, other operations not depicted may be incorporated into the schematically shown example processes. For example, one or more additional operations may be performed before, after, simultaneously with, or between any of the shown operations. In some cases, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the above implementation should not be construed as requiring such separation in all implementations, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products. Additionally, some other implementations are within the scope of the following claims. In some cases, the actions recited in the claims may be performed in a different order and still achieve the desired result.

[0151] As used herein (including in the claims), the term “or” when used in a list of two or more items means that any one of the listed items can be used alone, or any combination of two or more of the listed items can be used. For example, if a composition is described as containing components A, B, or C, the composition may contain: only A; only B; only C; a combination of A and B; a combination of A and C; a combination of B and C; or a combination of A, B, and C. Furthermore, as used herein (including in the claims), “or” as in a list of items ending with “at least one of” indicates a separate list, such that a list such as “at least one of A, B, or C” means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) or any one of these items in any combination thereof. As understood by one of ordinary skill in the art, the term “substantially” is defined as being substantially but not necessarily entirely specified (and includes being specified; for example, substantially 90 degrees includes 90 degrees, and substantially parallel includes parallel). In any publicly disclosed implementation, the term “substantially” can be replaced with “within the specified (percentage)”, where the percentage includes 0.1%, 1%, 5%, or 10%.

[0152] The foregoing description of this disclosure is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit or scope of this disclosure. Therefore, this disclosure is not intended to be limited to the examples and designs described herein, but is to be given the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE), comprising: At least one processor; as well as A memory coupled to the at least one processor and storing processor-readable code configured to, when executed by the at least one processor, be: The network entity receives multiple multicast transport grants addressed to multiple UEs including the UE, the multiple multicast transport grants correspondingly scheduling multiple multicast transports, including a first multicast transport grant scheduling a first multicast transport, each of the multicast transport grants including a corresponding common feedback timing indicator (K1) for acknowledgment / negative acknowledgment (ACK / NACK) feedback associated with a corresponding multicast transport associated with the multicast transport grant and corresponding multiple physical uplink control channel (PUCCH) resource indicators (PRI), the common K1 being shared by the multiple UEs, each of the multiple PRIs being associated with a corresponding UE among the multiple UEs; Receive the first multicast transmission authorized by the first multicast transmission from the network entity; as well as In the first multicast transmission grant, a first feedback codebook is sent to the network entity on the first feedback resource associated with the public K1 and the corresponding PRI associated with the UE. The first feedback codebook carries ACK / NACK feedback associated with the first multicast transmission to the network entity.

2. The UE of claim 1, wherein, The first feedback resource determined for sending the feedback codebook to the network entity includes: At least one of the time slots or sub-time slots for transmitting the first feedback codebook is determined based on the common K1 shared by each of the plurality of UEs; and The resource element for transmitting the first feedback codebook in the time slot or sub-time slot is determined based on the PRI associated with the UE.

3. The UE according to claim 1, wherein, The first feedback resource determined for sending the feedback codebook to the network entity includes: Add the relative K1 associated with the UE to the common K1 in the first multicast transmission grant to generate the total K1 associated with the UE; and At least one of the time slots or sub-time slots for transmitting the first feedback codebook is determined based on the total K1 associated with the UE.

4. The UE according to claim 3, wherein, Each of the plurality of UEs is configured with a corresponding relative K1 to be added to the common K1 in the first multicast authorization to determine feedback resources for reporting ACK / NACK feedback for the first multicast transmission, respectively.

5. A network entity, comprising: At least one processor; as well as A memory coupled to the at least one processor and storing processor-readable code configured to, when executed by the at least one processor, be: Multiple multicast transport grants are sent to multiple user equipments (UEs) to schedule multiple multicast transports accordingly, including a first multicast transport grant to schedule a first multicast transport. Each multicast transport grant includes a corresponding common feedback timing indicator (K1) for acknowledgment / negative acknowledgment (ACK / NACK) feedback associated with a corresponding multicast transport associated with the multicast transport grant and corresponding multiple physical uplink control channel (PUCCH) resource indicators (PRI), wherein the common K1 is shared by the multiple UEs and each of the multiple PRIs is associated with a corresponding UE among the multiple UEs. Send the first multicast transmission authorized by the first multicast transmission to the plurality of UEs; as well as On the first feedback resource associated with the common K1 and the corresponding PRI of the first UE in the first multicast transmission grant, a first feedback codebook is received from the first UE, the first feedback codebook including ACK / NACK feedback associated with the first multicast transmission.

6. The network entity according to claim 5, wherein, The first feedback resource includes a first resource element of a first time slot, and wherein the at least one processor is further configured to receive a second feedback codebook from a second UE among the plurality of UEs, the second feedback codebook being received in a different second resource element of the first time slot, the second resource element being associated with the common K1 and the corresponding PRI associated with the second UE.

7. The network entity according to claim 5, wherein, The at least one processor is further configured to: Each of the plurality of multicast transport grants is configured to include a common counter downlink assignment index (DAI) to indicate the number of multicast transport grants configured such that each of the plurality of UEs transmits a feedback codebook associated with the multicast transport grant based on the common K1 at the same physical uplink control channel (PUCCH) timing.

8. The network entity according to claim 7, wherein, The at least one processor is further configured to: Configure the common K1 in the first multicast transmission grant such that each of the plurality of UEs sends a feedback codebook associated with the first multicast transmission grant during the first PUCCH timing; as well as In response to configuring the common K1 in the first multicast transport grant such that each of the plurality of UEs sends the feedback codebook associated with the first multicast transport grant during the first PUCCH timing, the common DAI counter is incremented.

9. The network entity according to claim 8, wherein, The at least one processor is further configured to: Configure the common K1 in the second multicast transport grant such that each of the plurality of UEs sends a feedback codebook associated with the second multicast transport grant during the first PUCCH timing; as well as In response to configuring the common K1 in the second multicast transport grant such that each of the plurality of UEs sends the feedback codebook associated with the second multicast transport grant during the first PUCCH timing, the common DAI counter is incremented.

10. The network entity according to claim 9, wherein, The at least one processor is further configured to: Configure the common K1 in the second multicast transport grant such that each of the plurality of UEs sends a feedback codebook associated with the second multicast transport grant in a second PUCCH timing different from the first PUCCH timing; as well as In response to configuring the common K1 in the second multicast transport grant such that each of the plurality of UEs sends the feedback codebook associated with the second multicast transport grant during the second PUCCH timing, the common DAI counter is reset.

11. The network entity according to claim 5, wherein, The at least one processor is further configured to: For each of the plurality of UEs, a scheduling constraint is configured to restrict the scheduling of ACK / NACK feedback for different UEs at the same Physical Uplink Control Channel (PUCCH) timing, such that the feedback codebook associated with the restricted ACK / NACK feedback has the same size for the different UEs.

12. The network entity according to claim 11, wherein, The first feedback resource is in a first time slot, and wherein the at least one processor is further configured to receive a second feedback codebook associated with the first multicast transmission from a second UE among the plurality of UEs, the second feedback codebook being received in the first time slot, the first feedback codebook having the same structure as the second feedback codebook.

13. The network entity according to claim 12, wherein, The at least one processor is further configured to: The network entity sends a second multicast transmission associated with a second multicast transmission grant among the plurality of multicast transmission grants, wherein the first feedback codebook is additionally associated with the second multicast transmission, and wherein the second feedback codebook is additionally associated with the second multicast transmission.

14. The network entity according to claim 5, wherein, The at least one processor is further configured to: Each of the plurality of UEs is configured with a corresponding relative K1 to be added to the common K1 in each of the plurality of multicast transmission grants, in order to facilitate the determination of the appropriate feedback resources for sending ACK / NACK feedback for the corresponding multicast transmission.

15. The network entity according to claim 14, wherein, Each of the plurality of UEs is configured with a corresponding relative K1, such that each UE: The corresponding relative K1 is added to the common K1 indicated in each multicast transport grant to generate a corresponding total K1 associated with each UE; as well as Based on the corresponding total K1 associated with each UE, at least one of the corresponding time slots or corresponding sub-time slots for transmitting the corresponding feedback codebook associated with each multicast transmission grant is determined.

16. A method for wireless communication performed by a user equipment (UE), the method comprising: The network entity receives multiple multicast transport grants addressed to multiple UEs including the UE, the multiple multicast transport grants correspondingly scheduling multiple multicast transports, including a first multicast transport grant scheduling a first multicast transport, each of the multicast transport grants including a corresponding common feedback timing indicator (K1) for acknowledgment / negative acknowledgment (ACK / NACK) feedback associated with a corresponding multicast transport associated with the multicast transport grant and corresponding multiple physical uplink control channel (PUCCH) resource indicators (PRI), the common K1 being shared by the multiple UEs, each of the multiple PRIs being associated with a corresponding UE among the multiple UEs; Receive the first multicast transmission authorized by the first multicast transmission from the network entity; as well as In the first multicast transmission grant, a first feedback codebook is sent to the network entity on the first feedback resource associated with the public K1 and the corresponding PRI associated with the UE. The first feedback codebook carries ACK / NACK feedback associated with the first multicast transmission to the network entity.

17. The method according to claim 16, wherein, The first feedback resource determined for sending the feedback codebook to the network entity includes: At least one of the time slots or sub-time slots for transmitting the first feedback codebook is determined based on the common K1 shared by each of the plurality of UEs; and The resource element for transmitting the first feedback codebook in the time slot or sub-time slot is determined based on the PRI associated with the UE.

18. The method according to claim 16, wherein, The first feedback resource determined for sending the feedback codebook to the network entity includes: Add the relative K1 associated with the UE to the common K1 in the first multicast transmission grant to generate the total K1 associated with the UE; and At least one of the time slots or sub-time slots for transmitting the first feedback codebook is determined based on the total K1 associated with the UE.

19. The method according to claim 18, wherein, Each of the plurality of UEs is configured with a corresponding relative K1 to be added to the common K1 in the first multicast authorization to determine feedback resources for reporting ACK / NACK feedback for the first multicast transmission, respectively.

20. A method for wireless communication performed by a network entity, the method comprising: Multiple multicast transport grants are sent to multiple user equipments (UEs) to schedule multiple multicast transports accordingly, including a first multicast transport grant to schedule a first multicast transport. Each multicast transport grant includes a corresponding common feedback timing indicator (K1) for acknowledgment / negative acknowledgment (ACK / NACK) feedback associated with a corresponding multicast transport associated with the multicast transport grant and corresponding multiple physical uplink control channel (PUCCH) resource indicators (PRI), wherein the common K1 is shared by the multiple UEs and each of the multiple PRIs is associated with a corresponding UE among the multiple UEs. Send the first multicast transmission authorized by the first multicast transmission to the plurality of UEs; as well as On the first feedback resource associated with the common K1 and the corresponding PRI of the first UE in the first multicast transmission grant, a first feedback codebook is received from the first UE, the first feedback codebook including ACK / NACK feedback associated with the first multicast transmission.

21. The method according to claim 20, wherein, The first feedback resource includes a first resource element of a first time slot, and the method further includes receiving a second feedback codebook from a second UE among the plurality of UEs, the second feedback codebook being received in a different second resource element of the first time slot, the second resource element being associated with the common K1 and the corresponding PRI associated with the second UE.

22. The method of claim 20, further comprising: Each of the plurality of multicast transport grants is configured to include a common counter downlink assignment index (DAI) to indicate the number of multicast transport grants configured such that each of the plurality of UEs transmits a feedback codebook associated with the multicast transport grant based on the common K1 at the same physical uplink control channel (PUCCH) timing.

23. The method of claim 22, further comprising: Configure the common K1 in the first multicast transmission grant such that each of the plurality of UEs sends a feedback codebook associated with the first multicast transmission grant during the first PUCCH timing; as well as In response to configuring the common K1 in the first multicast transport grant such that each of the plurality of UEs sends the feedback codebook associated with the first multicast transport grant during the first PUCCH timing, the common DAI counter is incremented.

24. The method of claim 23, further comprising: Configure the common K1 in the second multicast transport grant such that each of the plurality of UEs sends a feedback codebook associated with the second multicast transport grant during the first PUCCH timing; as well as In response to configuring the common K1 in the second multicast transport grant such that each of the plurality of UEs sends the feedback codebook associated with the second multicast transport grant during the first PUCCH timing, the common DAI counter is incremented.

25. The method of claim 24, further comprising: Configure the common K1 in the second multicast transport grant such that each of the plurality of UEs sends a feedback codebook associated with the second multicast transport grant in a second PUCCH timing different from the first PUCCH timing; as well as In response to configuring the common K1 in the second multicast transport grant such that each of the plurality of UEs sends the feedback codebook associated with the second multicast transport grant during the second PUCCH timing, the common DAI counter is reset.

26. The method of claim 20, further comprising: For each of the plurality of UEs, a scheduling constraint is configured to restrict the scheduling of ACK / NACK feedback for different UEs at the same Physical Uplink Control Channel (PUCCH) timing, such that the feedback codebook associated with the restricted ACK / NACK feedback has the same size for the different UEs.

27. The method according to claim 26, wherein, The first feedback resource is in a first time slot, and the method further includes receiving a second feedback codebook associated with the first multicast transmission from a second UE among the plurality of UEs, the second feedback codebook being received in the first time slot, the first feedback codebook having the same structure as the second feedback codebook.

28. The method of claim 27, further comprising: The network entity sends a second multicast transmission associated with a second multicast transmission grant among the plurality of multicast transmission grants, wherein the first feedback codebook is additionally associated with the second multicast transmission, and wherein the second feedback codebook is additionally associated with the second multicast transmission.

29. The method of claim 20, further comprising: Each of the plurality of UEs is configured with a corresponding relative K1 to be added to the common K1 in each of the plurality of multicast transmission grants, in order to facilitate the determination of the appropriate feedback resources for sending ACK / NACK feedback for the corresponding multicast transmission.

30. The method according to claim 29, wherein, Each of the plurality of UEs is configured with a corresponding relative K1, such that each UE: The corresponding relative K1 is added to the common K1 indicated in each multicast transport grant to generate a corresponding total K1 associated with each UE; as well as Based on the corresponding total K1 associated with each UE, at least one of the corresponding time slots or corresponding sub-time slots for transmitting the corresponding feedback codebook associated with each multicast transmission grant is determined.

Images