Feedback reporting for multicast communications in non-terrestrial networks

By enabling or disabling feedback reporting based on HARQ process ID or multicast G-RNTI in non-terrestrial networks, the lack of feedback reporting mechanism in multicast communication is solved, and communication efficiency and reliability are improved.

CN119137891APending Publication Date: 2024-12-13QUALCOMM INC
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202380037506.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-05-04
Filing Date
2023-05-05
Publication Date
2024-12-13

AI Technical Summary

Technical Problem

The prior art has failed to effectively solve the feedback reporting problem of multicast communication in non-terrestrial networks, especially the lack of mechanisms to enable or disable feedback reporting in multicast NTN environments, resulting in limited communication efficiency and reliability.

Method used

By receiving control information indicating the feedback scheme in a user equipment (UE), enabling or disabling feedback reports based on HARQ process ID or multicast G-RNTI, determining whether feedback associated with multicast sending is reported, realizing multicast communications for multicast communication based on HARQ process ID or multicast G-RNTI Flexible control.

Benefits of technology

It improves the flexibility and reliability of multicast communication, optimizes the utilization of network resources, enhances the feedback mechanism for multicast signals, and improves the communication efficiency and the operation efficiency of user equipment.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119137891A_ABST
    Figure CN119137891A_ABST
Patent Text Reader

Abstract

Methods, systems, and devices for wireless communication are described. The method may include a first network node (e.g., a user equipment (UE)) receiving first control information indicating a first feedback scheme for multicast transmission in a non-terrestrial network (NTN), and determining a feedback scheme for application based on the first feedback scheme. The method may also include the first network node monitoring multicast transmission and operating according to a feedback scheme of the application.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims the benefit of U.S. Provisional Patent Application No. 63 / 339,269, entitled “FEEDBACK REPORTING FOR MULTICAST COMMUNICATION IN A NON-TERRESTRIAL NETWORK,” filed by LIU et al. on May 6, 2022, and U.S. Patent Application No. 18 / 312,549, entitled “FEEDBACK REPORTING FOR MULTICAST COMMUNICATION IN A NON-TERRESTRIAL NETWORK,” filed by LIU et al. on May 4, 2023, each of which is assigned to the assignee of this application. Background Art

[0003] The following relates to wireless communications related to feedback reporting for multicast communications in a non-terrestrial network (NTN).

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Aspects of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced 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 may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communication of communication devices, which may be referred to as user equipment (UE). Summary of the invention

[0005] The described technology relates to improved methods, systems, devices and apparatuses for supporting feedback reporting of multicast communications in non-terrestrial networks (NTNs). For example, the described technology provides for enabling or disabling of feedback reporting in NTNs. In some aspects, a user equipment (UE) may receive control information indicating a feedback scheme. The feedback scheme may be described as a configuration that the UE may use to determine a method for sending report feedback for a multicast downlink that is scheduled to be received by the UE. In one aspect, the feedback scheme may indicate enabling or disabling feedback reporting based on each hybrid automatic repeat request (HARQ) process identifier (ID) or based on each group radio network temporary identifier (G-RNTI). The UE may receive a scheduled multicast downlink signal from a network entity (e.g., a base station) and determine whether to report feedback associated with the downlink signal based on the feedback scheme.

[0006] A method for wireless communication at a first network node is described. The method may include receiving first control information indicating a first feedback scheme for a multicast transmission in an NTN, determining an applied feedback scheme based on the first feedback scheme, monitoring the multicast transmission, and operating according to the applied feedback scheme, wherein operating according to the applied feedback scheme may include operations, features, components, or instructions for determining whether to report feedback associated with the multicast transmission.

[0007] An apparatus for wireless communication at a first network node is described. The apparatus may include a memory and at least one processor coupled to the memory. The at least one processor may be configured to receive first control information indicating a first feedback scheme for a multicast transmission in an NTN, determine an applied feedback scheme based on the first feedback scheme, monitor the multicast transmission, and operate according to the applied feedback scheme, wherein instructions to operate according to the applied feedback scheme are executable by the processor to cause the apparatus to determine whether to report feedback associated with the multicast transmission.

[0008] Another apparatus for wireless communication at a first network node is described. The apparatus may include: means for receiving first control information indicating a first feedback scheme for a multicast transmission in an NTN, means for determining an applied feedback scheme based on the first feedback scheme, means for monitoring the multicast transmission, and means for operating in accordance with the applied feedback scheme, wherein the means for operating in accordance with the applied feedback scheme includes means for determining whether to report feedback associated with the multicast transmission.

[0009] A non-transitory computer readable medium having stored thereon code for wireless communication. The code, when executed by a first network node, causes the first network node to receive first control information indicating a first feedback scheme for multicast transmissions in an NTN, determine an applied feedback scheme based on the first feedback scheme, monitor the multicast transmissions, and operate according to the applied feedback scheme, wherein the instructions to operate according to the applied feedback scheme are executable to determine whether to report feedback associated with the multicast transmissions.

[0010] In some aspects of the methods, apparatus, and non-transitory computer-readable media described herein, the first feedback scheme corresponds to reporting feedback on a per HARQ process ID basis or on a per multicast G-RNTI basis.

[0011] In some aspects of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the first control information may include operations, features, components, or instructions for receiving unicast radio resource control (RRC) signaling, wherein the unicast RRC signaling includes the first control information, and wherein the first feedback scheme corresponds to reporting feedback on a per HARQ process ID basis.

[0012] Some aspects of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for receiving downlink control information (DCI) associating a multicast transmission with a HARQ process ID.

[0013] Some aspects of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving unicast RRC signaling, wherein the unicast RRC signaling includes first control information, and wherein the first feedback scheme corresponds to reporting feedback on a per-multicast G-RNTI basis.

[0014] Some aspects of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for receiving a DCI associating a multicast transmission with a multicast G-RNTI.

[0015] In some aspects of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the first control information may include operations, features, components, or instructions for receiving a multicast DCI, wherein the multicast DCI includes the first control information, and wherein the first feedback scheme corresponds to reporting feedback on a per-multicast G-RNTI basis, the multicast DCI also associating the multicast transmission with the multicast G-RNTI.

[0016] Some aspects of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving second control information indicating a second feedback scheme for multicast transmissions in the NTN, wherein determining the feedback scheme to apply may include operations, features, components, or instructions for determining the feedback scheme to apply based on the first feedback scheme and the second feedback scheme.

[0017] In some aspects of the methods, apparatus, and non-transitory computer-readable media described herein, the first feedback scheme corresponds to enabling feedback reporting for the multicast G-RNTI and the second feedback scheme corresponds to disabling feedback reporting for the HARQ process ID.

[0018] Some aspects of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for receiving a DCI associating a multicast transmission with a multicast G-RNTI and a HARQ ID.

[0019] In some aspects of the methods, apparatus, and non-transitory computer-readable media described herein, the message type of the first control information may be an RRC message type or a DCI message type.

[0020] In some aspects of the methods, apparatus, and non-transitory computer-readable media described herein, an applied feedback scheme may be handled as an error case caused by a first feedback scheme indicated by first control information and a second feedback scheme indicated by second control information.

[0021] In some aspects of the methods, apparatus, and non-transitory computer-readable media described herein, operating according to an applied feedback scheme may include operations, features, components, or instructions for avoiding reporting feedback based on a first feedback scheme indicated by first control information and a second feedback scheme indicated by second control information.

[0022] In some aspects of the methods, apparatus, and non-transitory computer-readable media described herein, operating in accordance with an applied feedback scheme may include operations, features, components, or instructions for filling a codebook with feedback determined from a detection result of a multicast transmission based on a first feedback scheme indicated by a first control information and a second feedback scheme indicated by a second control information.

[0023] In some aspects of the methods, apparatus, and non-transitory computer-readable media described herein, operating in accordance with an applied feedback scheme may include operations, features, components, or instructions for filling a codebook with negative acknowledgement (NACK) feedback based on a first feedback scheme indicated by first control information and a second feedback scheme indicated by second control information.

[0024] Some aspects of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving third control information indicating a set of feedback report alternatives and determining a feedback report alternative from the set of feedback report alternatives based on a first feedback scheme indicated by the first control information and a second feedback scheme indicated by the second control information, wherein the applied feedback scheme may be based on the determined feedback report alternative.

[0025] In some aspects of the methods, apparatus, and non-transitory computer-readable media described herein, an applied feedback scheme may be based on a feedback codebook type configured for multicast transmission.

[0026] Some aspects of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for sending a capability message of the first network node to the second network node, wherein the first feedback scheme indicated in the first control information may be based on the capability message.

[0027] A method for wireless communication at a first network node is described. The method may include sending first control information indicating a first feedback scheme for a multicast transmission in an NTN, sending the multicast transmission, and monitoring feedback associated with the multicast transmission according to an applied feedback scheme used by a second network node, wherein the applied feedback scheme is based on the first feedback scheme.

[0028] An apparatus for wireless communication at a first network node is described. The apparatus may include a memory and at least one processor coupled to the memory. The at least one processor may be configured to send first control information indicating a first feedback scheme for a multicast transmission in an NTN, send the multicast transmission, and monitor feedback associated with the multicast transmission according to an applied feedback scheme used by a second network node, wherein the applied feedback scheme is based on the first feedback scheme.

[0029] Another apparatus for wireless communication at a first network node is described. The apparatus may include means for sending first control information indicating a first feedback scheme for a multicast transmission in an NTN, means for sending the multicast transmission, and means for monitoring feedback associated with the multicast transmission according to an applied feedback scheme used by a second network node, wherein the applied feedback scheme is based on the first feedback scheme.

[0030] A non-transitory computer-readable medium having stored thereon code for wireless communication. The code, when executed by a first network node, causes the first network node to send first control information indicating a first feedback scheme for a multicast transmission in an NTN, send the multicast transmission, and monitor feedback associated with the multicast transmission according to an applied feedback scheme used by a second network node, wherein the applied feedback scheme is based on the first feedback scheme.

[0031] In some aspects of the methods, apparatus, and non-transitory computer-readable media described herein, the first feedback scheme corresponds to reporting feedback on a per HARQ process ID basis or on a per multicast G-RNTI basis.

[0032] In some aspects of the methods, apparatus, and non-transitory computer-readable media described herein, sending the first control information may include operations, features, components, or instructions for sending unicast RRC signaling, wherein the unicast RRC signaling includes the first control information, and wherein the first feedback scheme corresponds to reporting feedback based on each HARQ process ID.

[0033] Some aspects of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for sending a DCI associating a multicast transmission with a HARQ process ID.

[0034] In some aspects of the methods, apparatus, and non-transitory computer-readable media described herein, sending the first control information may include operations, features, components, or instructions for sending unicast RRC signaling, wherein the unicast RRC signaling includes the first control information, and wherein the first feedback scheme corresponds to reporting feedback on a per-multicast G-RNTI basis.

[0035] Some aspects of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for sending a DCI associating a multicast transmission with a multicast G-RNTI.

[0036] In some aspects of the methods, apparatus, and non-transitory computer-readable media described herein, sending the first control information may include operations, features, components, or instructions for sending a multicast DCI, wherein the multicast DCI includes the first control information, and wherein the first feedback scheme corresponds to reporting feedback on a per-multicast G-RNTI basis, the multicast DCI also associating the multicast transmission with the multicast G-RNTI.

[0037] Some aspects of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for transmitting second control information indicating a second feedback scheme for multicast transmissions in the NTN and identifying an applied feedback scheme based on the first feedback scheme and the second feedback scheme.

[0038] In some aspects of the methods, apparatus, and non-transitory computer-readable media described herein, the first feedback scheme corresponds to enabling feedback reporting for the multicast G-RNTI and the second feedback scheme corresponds to disabling feedback reporting for the HARQ process ID.

[0039] In some aspects of the methods, apparatus, and non-transitory computer-readable media described herein, the message type of the first control information may be an RRC message type or a DCI message type.

[0040] Some aspects of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for receiving a DCI associating a multicast transmission with a multicast G-RNTI and a HARQ ID.

[0041] In some aspects of the methods, apparatus, and non-transitory computer-readable media described herein, the applied feedback scheme includes the second network node filling a codebook with feedback associated with the multicast transmission based on a first feedback scheme indicated by the first control information and a second feedback scheme indicated by the second control information.

[0042] In some aspects of the methods, apparatus, and non-transitory computer-readable media described herein, the applied feedback scheme includes the second network node filling a codebook with NACK feedback based on a first feedback scheme indicated by the first control information and a second feedback scheme indicated by the second control information.

[0043] Some aspects of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for sending third control information indicating a set of feedback reporting alternatives, wherein the applied feedback scheme may be based on the set of feedback reporting alternatives.

[0044] In some aspects of the methods, apparatus, and non-transitory computer-readable media described herein, an applied feedback scheme may be based on a feedback codebook type configured for multicast transmission.

[0045] Some aspects of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for receiving, from the second network node, a capability message of the second network node, wherein the first feedback scheme indicated in the first control information may be based on the capability message. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] Figure 1 and Figure 2 Aspects of a wireless communication system supporting feedback reporting for multicast communications in a non-terrestrial network (NTN) in accordance with one or more aspects of the present disclosure are illustrated.

[0047] Figure 3Aspects of a process flow supporting feedback reporting for multicast communications in an NTN in accordance with one or more aspects of the present disclosure are illustrated.

[0048] Figure 4 and Figure 5 A block diagram of an apparatus supporting feedback reporting for multicast communications in an NTN according to one or more aspects of the present disclosure is shown.

[0049] Figure 6 A block diagram of a communications manager supporting feedback reporting for multicast communications in an NTN is shown in accordance with one or more aspects of the present disclosure.

[0050] Figure 7 A diagram of a system including a device supporting feedback reporting for multicast communications in an NTN is shown in accordance with one or more aspects of the present disclosure.

[0051] Figure 8 and Fig. 9 A block diagram of an apparatus supporting feedback reporting for multicast communications in an NTN according to one or more aspects of the present disclosure is shown.

[0052] Fig.10 A block diagram of a communications manager supporting feedback reporting for multicast communications in an NTN is shown in accordance with one or more aspects of the present disclosure.

[0053] Fig.11 A diagram of a system including a device supporting feedback reporting for multicast communications in an NTN is shown in accordance with one or more aspects of the present disclosure.

[0054] Figures 12 to 17 A flow chart illustrating a method of supporting feedback reporting for multicast communications in an NTN according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0055] In some aspects, a user equipment (UE) may report feedback to a network entity (e.g., a base station). The feedback may indicate whether a downlink signal was successfully decoded or unsuccessfully decoded by the UE. The feedback may be reported according to various feedback schemes, depending on what is allowed or configured for a given context. For example, in non-terrestrial network (NTN) unicast communications, the allowed feedback scheme is used to report feedback based on each hybrid automatic repeat request (HARQ) process identifier (ID). That is, feedback is reported for each transmission or transmission set that shares the same HARQ process ID. On the other hand, in terrestrial network (TN) multicast communications, the allowed feedback scheme is used to report feedback based on each multicast group radio network temporary identifier (G-RNTI). That is, feedback is reported for each transmission or transmission set that shares the same multicast G-RNTI. However, feedback schemes for multicast NTNs have not yet been established.

[0056] As described herein, the UE may report feedback associated with a multicast message in the NTN. In some aspects, the UE may receive control information indicating to the UE to enable or disable a certain type of feedback scheme. In one alternative, a unicast radio resource control (RRC) message is sent by the network to the UE to enable or disable each HARQ process ID feedback. In another alternative, a unicast RRC message or a multicast downlink control information (DCI) message may be sent by the network to the UE to enable or disable each multicast G-RNTI feedback. In addition, in a third alternative, the UE may receive first control information that enables or disables each multicast G-RNTI feedback and second control information that disables or enables each HARQ process ID feedback. In such examples, the UE may encounter a scenario in which feedback reporting is enabled and disabled for multicast transmission. In this case, the UE may generate a HARQ codebook that carries an actual HARQ feedback value, carries only a negative feedback value, or carries no value at all.

[0057] First, aspects of the disclosure are described in the context of a wireless communication system. Additional aspects are described in the context of a process flow. Aspects of the disclosure are further illustrated and described by and with reference to apparatus diagrams, system diagrams, and flow diagrams related to feedback reporting of multicast communications in an NTN.

[0058] Figure 1 Aspects of a wireless communication system 100 that supports feedback reporting for multicast communications in an NTN in accordance with one or more aspects of the present disclosure are illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some aspects, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).

[0059] The network entities 105 may be dispersed throughout a geographic area to form a wireless communication system 100, and may include devices in different forms or with different capabilities. In some aspects, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, etc. In some aspects, the network entities 105 and the UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an aspect of a geographic area over which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0060] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or both stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of communicating with various types of devices such as Figure 1 Communicating with other UEs 115 or network entities 105 as shown.

[0061] As described herein, a node (which may be referred to as a node, a network node, a network entity, or a wireless node) may include, may be, or may be included in (e.g., as a component of) a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, an integrated access and backhaul (IAB) node, a distributed unit (DU), a central unit (CU), a remote / radio unit (RU) (which may also be referred to as a remote radio unit (RRU)), and / or another processing entity configured to perform any of the techniques described herein. For example, the network node may be a UE. As another example, the network node may be a base station or a network entity. As another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In further aspects of this example, the first network node, the second network node, and the third network node may be different relative to these examples. Similarly, references to UE, base station, device, equipment, computing system, etc. may include disclosure of UE, base station, device, equipment, computing system, etc. as a network node. For example, a disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with the present disclosure, once a specific example is expanded according to the present disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example where a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node, the first network node may refer to a first UE configured to receive information, a first base station, a first device, a first device, a first computing system, a first group of one or more components, a first processing entity, etc.; and the second network node may refer to a second UE, a second base station, a second device, a second device, a second computing system, a second group of one or more components, a second processing entity, etc.

[0062] As described herein, different terms may be used in various aspects to describe the transmission of information (e.g., any information, signal, etc.). The disclosure of one communication term includes the disclosure of other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this example and consistent with the present disclosure, the disclosure that the first network node is configured to send information to the second network node includes the disclosure that the first network node is configured to provide, send, output, transmit, or send information to the second network node. Similarly, in this example and consistent with the present disclosure, the disclosure that the first network node is configured to send information to the second network node includes the disclosure that the second network node is configured to receive, obtain, or decode information provided, sent, output, communicated, or sent by the first network node.

[0063] In some aspects, the network entities 105 may communicate with the core network 130, or with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some aspects, the network entities 105 may communicate with each other on the backhaul links 120 (e.g., according to X2, Xn, or other interface protocols) directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130). In some aspects, the network entities 105 may communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or fronthaul communication links 168 (e.g., according to a fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0064] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next-generation Node B, or a gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a home Node B, a home evolved Node B, or other suitable terms). In some aspects, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0065] In some aspects, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, an intelligent radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some aspects, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0066] The functional split between CU 160, DU 165, and RU 170 is flexible and may support different functionalities, depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, and RU 170. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some aspects, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DUs 165 and RUs 170, such that the DUs 165 may support one or more layers of the protocol stack, and the RUs 170 may support one or more different layers of the protocol stack. The DUs 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by different ones of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some aspects, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented according to interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 communicating over those communication links.

[0067] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a coupled IAB donor's DU 165. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some aspects, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0068] In the case where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support feedback reporting of multicast communications in the NTN as described herein. For example, some operations described as being performed by the UE 115 or the network entity 105 (e.g., the base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., the IAB node 104, the DU 165, the CU 160, the RU 170, the RIC 175, the SMO 180).

[0069] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some aspects, UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in, for example, an appliance or a vehicle, a meter, etc.

[0070] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 shown.

[0071] The UE 115 and the network entity 105 may communicate with each other wirelessly via one or more communication links 125 (e.g., access links) via one or more carriers. The term "carrier" may refer to a set of RF spectrum resources having a physical layer structure defined for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communication with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0072] The signal waveform transmitted through the carrier may be composed of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM techniques, a resource element may refer to a symbol period (e.g., the duration of a modulation symbol) and a subcarrier resource, in which case the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that the more resource elements a device receives and the higher the order of the modulation scheme, the higher the data rate of the device may be. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources may improve the data rate or data integrity of communications with UE 115.

[0073] The time interval of the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the maximum supported subcarrier spacing, and N f The maximum supported discrete Fourier transform (DFT) size may be indicated. Time intervals of the communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0074] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some aspects, a frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended in front of each symbol period). In some wireless communication systems 100, a time slot may be further divided into a plurality of mini-time slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may include one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0075] A subframe, slot, mini-slot, or symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmit time interval (TTI). In some aspects, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0076] Physical channels may be multiplexed on a carrier according to various techniques. Physical control channels and physical data channels may be multiplexed on a downlink carrier using, for example, one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth of a carrier or a subset of that system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more of the UEs 115 may monitor or search a control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to a plurality of UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0077] In some aspects, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and, therefore, provide communication coverage for mobile coverage areas 110. In some aspects, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In other aspects, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0078] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video, or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0079] In some aspects, a UE 115 may be able to communicate directly with other UEs 115 over a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some aspects, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support various aspects of such D2D communication as configured or scheduled by the network entity 105. In some aspects, one or more UEs 115 in the group may be outside of the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some aspects, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, where each UE 115 transmits to each other UE 115 in the group. In some aspects, the network entity 105 may facilitate scheduling resources for D2D communication. In other aspects, D2D communications may be performed between the UEs 115 without involvement of the network entity 105 .

[0080] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access layer (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP service 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0081] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from about one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than transmission using smaller frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0082] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may use license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in unlicensed bands such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed RF spectrum band, devices such as the network entity 105 and the UE 115 may employ carrier sensing for conflict detection and avoidance. In some aspects, operations in unlicensed bands may be based on a carrier aggregation configuration combined with component carriers operating in a licensed band (e.g., LAA). Operations in the unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.

[0083] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some aspects, antennas or antenna arrays associated with the network entity 105 may be located in different geographic locations. The network entity 105 may have an antenna array having a collection of multiple rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0084] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).

[0085] The network entity 105 or UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the network entity 105 along different directions. For example, the network entity 105 may send signals according to different sets of beamforming weights associated with different transmission directions. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device, such as network entity 105, or by a receiving device, such as UE 115) beam directions for later transmission or reception by the network entity 105.

[0086] Some signals, such as data signals associated with a particular receiving device, may be transmitted by a transmitting device (e.g., a transmitting network entity 105, a transmitting UE 115) along a single beam direction (e.g., a direction associated with a receiving device (such as a receiving network entity 105 or a receiving UE 115)). In some aspects, a beam direction associated with transmission along a single beam direction may be determined based on signals transmitted along one or more beam directions. For example, UE 115 may receive one or more of the signals transmitted by network entity 105 along different directions and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.

[0087] In some aspects, transmission by a device (e.g., by a network entity 105 or a UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from the network entity 105 to the UE 115). The UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured beam set across a system bandwidth or one or more subbands. The network entity 105 may transmit a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may be precoded or not precoded. The UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-faceted codebook, a linear combination codebook, a port selection codebook). Although these techniques are described with reference to signals sent along one or more directions by a network entity 105 (e.g., base station 140, RU 170), UE 115 may use similar techniques to send signals multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115), or to send signals along a single direction (e.g., to send data to a receiving device).

[0088] When receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105), the receiving device (e.g., UE 115) may perform receiving operations (e.g., directional listening) according to multiple receiving configurations. For example, the receiving device may perform reception according to multiple receiving directions by receiving via different antenna subarrays, processing the received signals according to different antenna subarrays, receiving according to different receiving beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing the received signals according to different receiving beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receiving configurations or receiving directions. In some aspects, a receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0089] UE 115 and network entity 105 may support retransmission of data to increase the possibility of successfully receiving data. HARQ feedback is a technique for increasing the possibility of correctly receiving data through a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve the throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some aspects, a device may support simultaneous slot HARQ feedback, in which the device may provide HARQ feedback for data received in a previous symbol in a particular time slot in the time slot. In other aspects, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

[0090] In some aspects, the UE 115 may operate according to a feedback scheme in the NTN. In some aspects, the UE 115 may receive control information indicating a feedback scheme. The feedback scheme may be described as a configuration that the UE 115 may use to determine a method for sending report feedback for a multicast downlink scheduled to be received by the UE 115. In one aspect, the feedback scheme may indicate enabling or disabling feedback reporting on a per-HARQ process ID basis or on a per-G-RNTI basis. The UE may receive a scheduled multicast downlink signal from a network entity 105 (e.g., a base station) and determine whether to report feedback associated with the downlink signal based on the feedback scheme.

[0091] Figure 2 An example of a wireless communication system 200 that supports feedback reporting of multicast communications in an NTN according to one or more aspects of the present disclosure is illustrated. In some aspects, the wireless communication system 200 may implement aspects of the wireless communication system 100. For example, the wireless communication system 200 may include a network entity 105-a and a UE 115, which may be as described in reference Figure 1 Aspects of the network entity 105 and UE 115 are described.

[0092] In some aspects, the network entity 105-a may communicate with one or more UEs 115 in a group of UEs 115. In one aspect, the network entity 105-a may intend to communicate with only one of the UEs 115 (e.g., unicast communication). For example, the network entity 105-a may intend to communicate with UE 115-a but not with UE 115-b or UE 115-c. In such an example, the network entity 105-a may send a DCI scheduling the communication to the UE 115-a, wherein the DCI is scrambled by a cell RNTI (C-RNTI) associated with the UE 115-a (e.g., a cyclic redundancy check (CRC) of the DCI is scrambled). Prior to sending the DCI, the network entity 105-a may assign different C-RNTI values ​​to different UEs 115. Thus, the UE 115-a may determine that the DCI is intended for the UE 115-a based on identifying that the C-RNTI is assigned to the UE 115-a. UE 115-a may then receive the unicast signal scheduled by the DCI.

[0093] Alternatively, the network entity 105-a may intend to communicate with more than one UE 115 (e.g., multicast communication). For example, the network entity 105-a may intend to communicate with UE 115-a, UE 115-b, and UE 115-c. In this example, the network entity 105-a may send DCI to UE 115-a, UE 115-b, and UE 115-c, where the DCI is scrambled (e.g., a CRC of the DCI is scrambled) with a G-RNTI or a G-Configuration Scheduling-RNTI (G-CS-RNTI) associated with UE 115-a, UE 115-b, and UE 115-c. Prior to sending the DCI, the network entity 105-a may assign the same G-RNTI value or the same G-CS-RNTI value to different UEs 115. Thus, UE 115-a, UE 115-b, and UE 115-c may determine that the DCI is intended for UE 115-a, UE 115-b, and UE 115-c based on the identification G-RNTI or G-CS-RNTI assigned to UE 115-a, UE 115-b, and UE 115-c. UE 115-a, UE 115-b, and UE 115-c may then receive the multicast signal scheduled by the DCI.

[0094] In some aspects, the UE 115 may report feedback information to the network entity 105-a. The feedback information may include an indication of whether the UE 115 successfully decodes the downlink signal received from the network entity 105-a. If the UE 115 successfully decodes the downlink signal, the UE 115 may send an acknowledgment (ACK) feedback to the network entity 105-a. Alternatively, if the UE 115 does not successfully decode the downlink signal, the UE 115 may send a negative ACK (NACK) feedback to the network entity 105-a. In response to receiving the NACK feedback, the network entity 105-a may retransmit the downlink signal to the UE 115. In some aspects, the UE 115 may be configured with one of two HARQ codebook types to provide feedback to the network entity 105-a. Examples of HARQ codebook types may be a type 1 HARQ codebook (e.g., a semi-static codebook) and a type 2 HARQ codebook (e.g., a dynamic codebook). The type 1 HARQ codebook may be a fixed size, where the size is the sum of the transmission opportunities of the physical downlink shared channel (PDSCH) within a given time. The size of the type 2 HARQ codebook may change according to the PDSCH resource allocation. That is, unlike the type 1 HARQ codebook, the type 2 HARQ codebook may not take into account the unused transmission opportunities of the PDSCH.

[0095] In some aspects, UE 115 may operate in an NTN. In contrast to a TN, an NTN may refer to any network including non-ground flying objects such as satellites 205, high altitude platform systems (HAPS), air-to-ground networks, unmanned aerial vehicles (UAVs), airplanes, etc. In some aspects, a UE 115 operating in an NTN may use a satellite 205 as a relay device to communicate with a network (e.g., a network entity 105-a) over a long distance. In one aspect, the network entity 105-a may send a unicast signal to a satellite 205, and the satellite 205 may send (e.g., relay) a unicast signal to the UE 115-a. In addition, the UE 115-a may provide feedback about the unicast signal to the network entity 105-a. In some aspects, before receiving the unicast signal, the UE 115-a may receive control signaling (e.g., RRC signaling) indicating that the UE 115-a enables feedback of the unicast signaling associated with the first HARQ process ID. Additionally or alternatively, the control signaling or additional control signaling may instruct UE 115-a to disable feedback of unicast signaling associated with the second HARQ process ID.If the DCI scheduling the unicast signal indicates a HARQ process ID, the unicast signal may be considered associated with the HARQ process ID.

[0096] If UE 115-a is configured with a type 1 HARQ codebook, UE 115-a may report NACK feedback for unicast signals associated with the second HARQ process ID (e.g., regardless of the decoding result), and may report the decoding result (e.g., NACK feedback or ACK feedback) for unicast signaling associated with the first HARQ process ID. In some aspects, regardless of whether feedback reporting for unicast signals is disabled or enabled, the bit field associated with feedback reporting in the corresponding DCI may be unchanged. That is, in either case, the DCI may include bit fields for priority (PRI), physical uplink shared channel (PUSCH) to HARQ feedback timing, and downlink assignment index (DAI). If UE 115-a is configured with a type 2 HARQ codebook, UE 115-a may not report feedback for unicast signals associated with the second HARQ process ID, and may report the decoding result (e.g., NACK feedback or ACK feedback) for unicast signaling associated with the first HARQ process ID. In some aspects, a bit field associated with feedback reporting for a unicast signal in a corresponding DCI may depend on whether feedback reporting for the unicast signal is disabled or enabled. For example, when feedback reporting is enabled, the DCI may include bit fields for PRI, PUSCH to HARQ feedback timing, and DAI, and when feedback reporting is disabled, the DCI may not include one or more of the bit fields for PRI, PUSCH to HARQ feedback timing, and DAI (e.g., counted DAI (C-DAI) or total DAI (T-DAI)). Alternatively, the bit field associated with feedback reporting in the DCI may remain unchanged, and in the event that feedback reporting is disabled for a unicast signal corresponding to the DCI, UE 115-a may ignore one or more of the bit fields associated with feedback reporting.

[0097] Alternatively, UE 115 may operate in a TN. In a TN, network entity 105-a may send a multicast signal directly to a group of UEs 115 (e.g., UE 115-a, UE 115-b, and UE 115-c), and each UE 115 in the group of UEs 115 may report feedback about the multicast signal. In one aspect, UE 115-a may receive the multicast signal and report feedback about the multicast signal. In some aspects, before reporting the feedback, UE 115-a may receive control signaling indicating that UE 115-a enables feedback on multicast signals associated with a first RNTI (e.g., G-RNTI or G-CS-RNTI). Additionally or alternatively, the control signaling or additional control signaling indicates disabling feedback on multicast signals associated with a second RNTI (e.g., G-RNTI or G-CS-RNTI). In some aspects, the control signaling may be an aspect of RRC signaling. On the other hand, the control signaling may be an aspect of DCI signaling. In this example, UE 115-a may receive a second control signaling before receiving the control signaling. The second control signaling may enable or disable a feature for a DCI (e.g., DCI format 4_2) configuration. For example, UE 115-a may receive RRC signaling indicating that if a bit field in the DCI includes a bit with a logical value of 1, UE 115-a may enable feedback for a multicast signal, and if a bit field in the DCI includes a bit with a logical value of 0, UE 115-a may disable feedback for a multicast signal. If the CRC of the DCI that schedules the multicast signal is scrambled by the RNTI, the multicast signal may be considered to be associated with the RNTI.

[0098] If UE 115-a is configured with a type 1 HARQ codebook, UE 115-a may report NACK feedback (e.g., regardless of the decoding result) or a decoding result (e.g., NACK feedback or ACK feedback) for a multicast signal associated with the second RNTI, and may report a decoding result (e.g., NACK feedback or ACK feedback) for multicast signaling associated with the first RNTI. If UE 115-a is configured with a type 2 HARQ codebook, UE 115-a may not report feedback for a multicast broadcast signal associated with the second RNTI, and may report a decoding result (e.g., NACK feedback or ACK feedback) for multicast broadcast signaling associated with the first RNTI. In addition to unicast signaling, multicast signaling may also be supported in the NTN. However, procedures for enabling or disabling reporting of feedback associated with multicast signals in the NTN have not yet been implemented.

[0099] As described herein, UE 115-a may receive control signaling to enable or disable feedback reporting for multicast signaling in the NTN. In one aspect, network entity 105-a may send multicast message 220 to UE 115-a (e.g., via satellite 205). UE 115-a may receive multicast message 220 and determine whether to send feedback about multicast message 220 to network entity 105-a (e.g., using satellite 205 as a relay device). In some aspects, UE 115-a may determine whether to send feedback about multicast message 220 based on a first control message 210 received from network entity 105-a (e.g., via satellite 205) prior to receiving multicast message 220.

[0100] In one aspect, the first control message 210 may indicate enabling feedback reporting for multicast signaling associated with the first HARQ process ID. Additionally or alternatively, the first control message 210 may indicate disabling feedback reporting for multicast signaling associated with the second HARQ process ID. In such an example, the UE 115-a may determine to send a feedback message 225 for the multicast message 220 using a procedure similar to that described with respect to feedback reporting for unicast messages in the NTN. That is, if the UE 115-a is configured with a type 1 HARQ codebook, the UE 115-a may report NACK feedback for the multicast message 220 (e.g., regardless of the decoding result) when the multicast message 220 is associated with the second HARQ process ID, and may report a decoding result (e.g., NACK feedback or ACK feedback) for the multicast message 220 when the multicast message 220 is associated with the first HARQ process ID. If UE 115-a is configured with a type-2 HARQ codebook, UE 115-a may not report feedback for multicast message 220 when multicast message 220 is associated with the second HARQ process ID, or report a decoding result (e.g., NACK feedback or ACK feedback) for multicast message 220, and may report a decoding result (e.g., NACK feedback or ACK feedback) for multicast message 220 when the multicast message is associated with the first HARQ process ID. In such an example, first control message 210 may be an aspect of RRC signaling.

[0101] In some aspects, UE 115-a may determine uplink resources or uplink time slots (e.g., physical uplink control channel (PUCCH) resources or PUCCH time slots) based on DCI associated with enabling or disabling feedback for the HARQ process ID, regardless of what was last received. Alternatively, UE 115-a may determine uplink resources or uplink time slots based on DCI associated with enabling feedback for the HARQ process ID, rather than based on DCI associated with disabling feedback for the HARQ process ID. In some aspects, if configured for multicast signals, the determination of uplink resources or uplink time slots may be different for type 1 HARQ-ACK codebooks and type 2 HARQ-ACK codebooks.

[0102] On the other hand, the first control message 210 may indicate enabling feedback reporting for multicast signaling associated with the first RNTI. Additionally or alternatively, the first control message 210 may indicate disabling feedback reporting for multicast signaling associated with the second RNTI. In this example, the UE 115-a may determine to send feedback for the multicast message 220 using a procedure similar to feedback reporting for multicast messages in the TN. That is, if the UE 115-a is configured with a type 1 HARQ codebook, the UE 115-a may report NACK feedback (e.g., regardless of the decoding result) or no feedback for the multicast message 220 when the multicast message 220 is associated with the second RNTI, and may report the decoding result (e.g., NACK feedback or ACK feedback) for the multicast message 220 when the multicast message 220 is associated with the first RNTI. If UE 115-a is configured with a type 2 HARQ codebook, UE 115-a may not report feedback for multicast message 220 when multicast message 220 is associated with a second RNTI, and may report a decoding result (e.g., NACK feedback or ACK feedback) for multicast message 220 when multicast message 220 is associated with an RNTI. In such an example, first control message 210 may be an aspect of RRC signaling or DCI signaling. In the case where first control message 210 includes DCI signaling, UE 115-a may receive a second control message 215 that configures the first control message 210 to enable or disable a feature before receiving the first control message 210.

[0103] In some aspects, UE 115-a may determine uplink resources or uplink time slots (e.g., physical uplink control channel (PUCCH) resources or PUCCH time slots) based on DCI associated with enabling or disabling feedback for the RNTI, regardless of what was last received. Alternatively, UE 115-a may determine uplink resources or uplink time slots based on DCI associated with enabling feedback for the RNTI, rather than based on DCI associated with disabling feedback for the RNTI. In some aspects, if configured for multicast signals, the determination of uplink resources or uplink time slots may be different for type 1 HARQ-ACK codebooks and type 2 HARQ-ACK codebooks.

[0104] In yet another aspect, the first control message 210 may indicate enabling or disabling of feedback reporting for multicast signaling associated with the HARQ process ID, and the third control message may indicate enabling or disabling of feedback reporting for multicast signaling associated with the RNTI. Table 1 illustrates various aspects of possible combinations of feedback-enabled or feedback-disabled HARQ process IDs and RNTIs that UE 115-a may encounter.

[0105] As shown in Table 1, UE 115-a may encounter a scenario in which a multicast message 220 is associated with HARQ process IDs and RNTIs in different enabled or disabled states. For example, UE 115-a may receive a multicast message 220 associated with an RNTI for which feedback is enabled through RRC signaling and an HARQ process ID for which feedback is disabled through RRC signaling. In such a scenario, UE 115-a may take action according to one of Case 1, Case 2, Case 3, or Case 4 in row 1, column 2 of Table 1. In Case 1, the UE may experience an error case in which UE 115-a is not expected to receive a multicast message 220 associated with an RNTI for which feedback is enabled through RRC signaling and an HARQ process ID for which feedback is disabled through RRC signaling. That is, whether UE 115-a detects the multicast message 220 may depend on the specific implementation of the UE. Even if UE 115-a detects the multicast message 220, UE 115-a may not send feedback for the multicast message 220. In case 2, UE 115-a may detect multicast message 220 but avoid reporting feedback for multicast message 220. In case 3, UE 115-a may detect multicast message 220 and report (e.g., true) decoding results of multicast message 220, and in case 4, UE 115-a may not detect multicast message 220 and report NACK feedback for multicast message 220. In some aspects, network entity 105-a may configure different cases for UE 115-a, and UE 115-a may select which case to implement based on the message type (e.g., RRC or DCI) of first control message 210 and third control message. In some aspects, network entity 105-a may avoid transmitting multicast signals associated with a conflicting state to UE 115-a. For example, network entity 105-a may avoid using DCI associated with a HARQ process ID for which feedback is disabled to schedule a multicast message 220 associated with a RNTI for which feedback is enabled.

[0106] If feedback on the RNTI is enabled via the DCI, the UE 115-a may operate in a similar manner, where the DCI is associated with a HARQ process ID for which feedback is disabled, and the UE 115-a is configured with a type-2 codebook, as illustrated in row 2, column 2 of Table 1. However, if the UE 115-a is configured with a type-1 codebook, the UE 115-a may take action according to case 1 or case 2 of row 2, column 2 of Table 1. In case 1, the UE may experience an error case. That is, whether the UE 115-a detects the multicast message 220 may depend on the specific implementation of the UE. Even if the UE 115-a detects the multicast message 220, the UE 115-a may not send feedback on the multicast message 220. In case 2, the UE 115-a may report the (e.g., true) decoding result of the multicast message 220.

[0107] On the other hand, UE 115-a determines whether to send feedback to multicast message 220 of the conflicting state based on the priority information. For example, UE 115-a may identify that an RNTI for enabling feedback through RRC is associated with a first priority, and an HARQ process ID for disabling feedback through RRC is associated with a second priority. If the second priority is higher than the first priority, UE 115-a may take action according to case 2 and not report feedback, or UE 115-a may take action according to case 4 and report negative feedback. If the first priority is higher than the second priority, UE 115-a may take action according to case 3 and report true feedback or feedback based on the decoding result of multicast message 220.

[0108] On the other hand, UE 115-a may receive a multicast message 220 associated with an RNTI for which feedback is disabled by RRC signaling and a HARQ process ID for which feedback is disabled by RRC signaling. In this scenario, if UE 115-a is configured to use a type-2 codebook, UE 115-a may take action according to case 1 of row 3, column 2 of Table 1 and avoid reporting feedback for the multicast message 220. Alternatively, if UE 115-a is configured to use a type-1 codebook, UE 115-a may implement case 1 or case 2 of row 3, column 2 of Table 1. In case 1, UE 115-a may report a (e.g., true) decoding result of the multicast message 220, and in case 2, UE 115-a may report NACK feedback for the multicast message 220.

[0109] On the other hand, UE 115-a may receive a multicast message 220 associated with an RNTI for which feedback is disabled by DCI signaling and an HARQ process ID for which feedback is disabled by RRC signaling. In this scenario, if UE 115-a is configured to use a type-2 codebook, UE 115-a may take action according to case 1 of row 4, column 2 of Table 1 and avoid reporting feedback for the multicast message 220. Alternatively, if UE 115-a is configured to use a type-1 codebook, UE 115-a may implement case 1, case 2, or case 3 of row 4, column 2 of Table 1. In case 1, UE 115-a may experience an error case. In case 2, UE 115-a may report a (e.g., true) decoding result of the multicast message 220, and in case 3, UE 115-a may report NACK feedback for the multicast message 220.

[0110] In some aspects, UE 115-a may determine uplink resources or uplink time slots (e.g., physical uplink control channel (PUCCH) resources or PUCCH time slots) based on DCI associated with enabling or disabling feedback for an RNTI or HARQ process ID, regardless of what was last received. Alternatively, UE 115-a may determine uplink resources or uplink time slots based on DCI associated with enabling feedback for an RNTI or HARQ process ID, rather than based on DCI associated with disabling feedback for an RNTI or HARQ process ID. In some aspects, if configured for multicast signals, the determination of uplink resources or uplink time slots may be different for type 1 HARQ-ACK codebooks and type 2 HARQ-ACK codebooks.

[0111] Table 1

[0112]

[0113] Figure 3 Aspects of a process flow 300 for supporting feedback reporting of multicast communications in an NTN in accordance with one or more aspects of the present disclosure are illustrated. In some aspects, the process flow 300 may be implemented by aspects of the wireless communication system 100 and the wireless communication system 200. For example, the process flow 300 may be implemented by a UE 115-d or a network entity 105-b, which may be as described in reference to Figure 1 and Figure 2 Various aspects of the network entity 105 or UE 115 described. The following alternative aspects may be implemented in which some of the steps are performed in a different order than described or not performed at all. In some cases, the steps may include additional features not mentioned below, or other steps may be added.

[0114] In some aspects, the UE 115-d and the network entity 105-b may operate in an NTN. When operating in an NTN, the UE 115-d and the network entity 105-b may communicate with each other over long distances using non-terrestrial flying objects (e.g., satellites) as relays.

[0115] At 310, UE 115-d may receive first control information from network entity 105-b. The first control information may indicate a first feedback scheme for multicast transmission in NTN. The first control information may be an aspect of RRC signaling or DCI signaling. In the case where the first control information includes DCI signaling, UE 115-d may receive second control information (e.g., RRC signaling) before the first control information at 305. The second control information may configure the first control message with the capability to indicate the first feedback scheme. Additionally or alternatively, UE 115-d may receive third control information indicating a second feedback scheme for multicast transmission in NTN at 315. In one aspect, the first control information may indicate enabling or disabling feedback reporting based on each RNTI, and the third control information may indicate enabling or disabling feedback reporting based on each HARQ process ID. In some aspects, UE 115-d may send a capability message of UE 115-d to network entity 105-b, and the first feedback scheme indicated in the first control information may be based on the capability message.

[0116] At 320, UE 115-d may determine the feedback scheme to be applied based on the first feedback scheme indicated in the first control information. Additionally or alternatively, UE 115-d may determine the feedback scheme to be applied based on the second feedback scheme. If UE 115-d receives only the first control information, UE 115-d may determine that the scheme to be applied is the first feedback scheme. Similarly, if UE 115-d receives only the third control information, UE 115-d may determine that the scheme to be applied is the second feedback scheme. Alternatively, if UE 115-d receives both the first control information and the third control information, UE 115-d may determine the feedback scheme to be applied based on the first feedback scheme, the second feedback scheme, and potentially based on the message type of the first control information or the third control information. As an example, the feedback scheme to be applied may include UE 115-d avoiding reporting feedback, UE 115-d filling a codebook with feedback determined from a detection result transmitted by multicast, or UE 115-d filling a codebook with NACK. In some aspects, the network entity 105 - b may configure the UE 115 - d with different options for the applied feedback scheme, and the UE 115 - d may select the option for the applied feedback scheme based on one or more conditions.

[0117] At 325, the UE 115-d may monitor and receive the multicast transmission from the network entity 105-b. In some aspects, prior to monitoring the multicast transmission, the UE 115-d may receive DCI signaling scheduling the multicast message. The DCI signaling may associate the multicast transmission with one or both of the HARQ process ID indicated in the first control information or the RNTI indicated in the third control information. For example, the DCI may be a CRC scrambled by the RNTI, and / or the DCI may indicate the HARQ process ID.

[0118] At 330, the UE 115-d may operate according to the applied feedback scheme. That is, the UE 115-d may determine at 335 whether to report feedback associated with the multicast transmission. In one aspect, the UE 115-d may determine to report ACK feedback or NACK feedback (e.g., decoding results) for the multicast transmission based on the third control information indicating the enabled state of the HARQ process ID. Alternatively, the UE 115-d may determine to report NACK feedback for the multicast transmission (e.g., if a type 1 HARQ codebook is configured) or not report feedback for the multicast transmission (e.g., if a type 2 HARQ codebook is configured) based on the third control information indicating the disabled state of the HARQ process ID.

[0119] On the other hand, UE 115-d may determine to report ACK feedback or NACK feedback (e.g., decoding result) for multicast transmission based on the first control information indicating the enabled state of RNTI. Alternatively, UE 115-d may determine to report NACK feedback or ACK feedback for multicast transmission (e.g., if a type 1 HARQ codebook is configured), report only NACK feedback for multicast transmission (e.g., if a type 1 HARQ codebook is configured), or not report feedback for multicast transmission (e.g., if a type 2 HARQ codebook is configured) based on the first control information indicating the disabled state of RNTI.

[0120] On the other hand, UE 115-d may determine whether to report feedback for multicast transmission based on a combination of an enabled state or disabled state of the RNTI and the HARQ process ID. For example, if the first control information indicates an enabled state of the RNTI and the third control information indicates an enabled state of the HARQ process ID, UE 115-d may determine to report ACK feedback or NACK feedback (e.g., a decoding result of the multicast transmission).

[0121] Figure 4A block diagram 400 of a device 405 supporting feedback reporting of multicast communications in an NTN according to one or more aspects of the present disclosure is shown. The device 405 may be an example of aspects of a UE 115 or a network node as described herein. The device 405 may include a receiver 410, a transmitter 415, and a communication manager 420. The device 405 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0122] The receiver 410 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to feedback reporting for multicast communications in the NTN), user data, control information, or any combination thereof. The information may be communicated to other components of the device 405. The receiver 410 may utilize a single antenna or a collection of multiple antennas.

[0123] The transmitter 415 may provide means for transmitting signals generated by other components of the device 405. For example, the transmitter 415 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to feedback reports for multicast communications in the NTN), user data, control information, or any combination thereof. In some aspects, the transmitter 415 may be co-located with the receiver 410 in a transceiver module. The transmitter 415 may utilize a single antenna or a collection of multiple antennas.

[0124] The communication manager 420, the receiver 410, the transmitter 415, or various combinations thereof, or various components thereof, may be aspects of means for performing various aspects of feedback reporting for multicast communications in the NTN as described herein. For example, the communication manager 420, the receiver 410, the transmitter 415, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0125] In some aspects, the communication manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured to or otherwise supports means for performing the functions described herein. In some aspects, the processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0126] Additionally or alternatively, in some aspects, the communication manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting means for performing the functionality described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0127] In some aspects, the communication manager 420 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the receiver 410, the transmitter 415, or both. For example, the communication manager 420 may receive information from the receiver 410, transmit information to the transmitter 415, or be integrated in conjunction with the receiver 410, the transmitter 415, or both to obtain information, output information, or perform various other operations as described herein.

[0128] The communication manager 420 may support wireless communication at a first network node according to various aspects disclosed herein. For example, the communication manager 420 may be configured to or otherwise support a component for receiving a first control information indicating a first feedback scheme for multicast transmission in the NTN. The communication manager 420 may be configured to or otherwise support a component for determining a feedback scheme for an application based on the first feedback scheme. The communication manager 420 may be configured to or otherwise support a component for monitoring multicast transmissions. The communication manager 420 may be configured to or otherwise support a component for operating according to the feedback scheme of the application. In some aspects, in order to operate according to the feedback scheme of the application, the communication manager 420 may be configured to or otherwise support a component for determining whether to report feedback associated with the multicast transmission.

[0129] By including or configuring the communication manager 420 according to various aspects as described herein, the device 405 (e.g., a processor controlling or otherwise coupled to the receiver 410, the transmitter 415, the communication manager 420, or a combination thereof) can support techniques for reducing processing and more efficiently utilizing communication resources.

[0130] Figure 5A block diagram 500 of a device 505 supporting feedback reporting of multicast communications in an NTN according to one or more aspects of the present disclosure is shown. The device 505 may be an example of aspects of the device 405, UE 115, or network node as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. The device 505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0131] The receiver 510 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to feedback reporting for multicast communications in the NTN), user data, control information, or any combination thereof. The information may be communicated to other components of the device 505. The receiver 510 may utilize a single antenna or a collection of multiple antennas.

[0132] The transmitter 515 may provide means for transmitting signals generated by other components of the device 505. For example, the transmitter 515 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to feedback reports for multicast communications in the NTN), user data, control information, or any combination thereof. In some aspects, the transmitter 515 may be co-located with the receiver 510 in a transceiver module. The transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0133] The device 505 or its various components may be aspects of a component for performing various aspects of feedback reporting of multicast communications in the NTN as described herein. For example, the communication manager 520 may include a UE control information component 525, a feedback scheme component 530, a monitoring component 535, a feedback reporting component 540, or any combination thereof. The communication manager 520 may be an example of various aspects of the communication manager 420 as described herein. In some aspects, the communication manager 520 or its various components may be configured to use or otherwise cooperate with the receiver 510, the transmitter 515, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 520 may receive information from the receiver 510, transmit information to the transmitter 515, or be integrated with the receiver 510, the transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.

[0134] The communication manager 520 may support wireless communication at a first network node according to various aspects disclosed herein. The UE control information component 525 may be configured to or otherwise support a component for receiving a first control information indicating a first feedback scheme for multicast transmission in the NTN. The feedback scheme component 530 may be configured to or otherwise support a component for determining a feedback scheme for an application based on the first feedback scheme. The monitoring component 535 may be configured to or otherwise support a component for monitoring multicast transmission. The feedback reporting component 540 may be configured to or otherwise support a component for operating according to the feedback scheme of the application. In some aspects, in order to operate according to the feedback scheme of the application, the feedback reporting component 540 may be configured to or otherwise support a component for determining whether to report feedback associated with the multicast transmission.

[0135] Figure 6 A block diagram 600 of a communication manager 620 supporting feedback reporting of multicast communications in an NTN according to one or more aspects of the present disclosure is shown. The communication manager 620 can be an example of aspects of the communication manager 420, the communication manager 520, or both as described herein. The communication manager 620 or its various components can be aspects of a component for performing various aspects of feedback reporting of multicast communications in an NTN as described herein. For example, the communication manager 620 can include a UE control information component 625, a feedback scheme component 630, a monitoring component 635, a feedback reporting component 640, a UE DCI component 645, a UE capability component 650, a feedback alternative solution component 655, or any combination thereof. Each of these components can communicate with each other directly or indirectly (e.g., via one or more buses).

[0136] The communication manager 620 may support wireless communication at a first network node according to various aspects disclosed herein. The UE control information component 625 may be configured to or otherwise support a component for receiving a first control information indicating a first feedback scheme for multicast transmission in the NTN. The feedback scheme component 630 may be configured to or otherwise support a component for determining a feedback scheme for an application based on the first feedback scheme. The monitoring component 635 may be configured to or otherwise support a component for monitoring multicast transmission. The feedback reporting component 640 may be configured to or otherwise support a component for operating according to the feedback scheme of the application. In some aspects, in order to operate according to the feedback scheme of the application, the feedback reporting component 640 may be configured to or otherwise support a component for determining whether to report feedback associated with the multicast transmission.

[0137] In some aspects, the first feedback scheme corresponds to reporting feedback on a per HARQ process ID basis or on a per multicast G-RNTI basis.

[0138] In some aspects, to support receiving the first control information, the UE control information component 625 may be configured or otherwise support means for receiving unicast RRC signaling, wherein the unicast RRC signaling includes the first control information, and wherein the first feedback scheme corresponds to reporting feedback on a per HARQ process ID basis.

[0139] In some aspects, the UE DCI component 645 may be configured or otherwise support means for receiving DCI associating a multicast transmission with a HARQ process ID.

[0140] In some aspects, unicast RRC signaling is received, wherein the unicast RRC signaling includes first control information, and wherein the first feedback scheme corresponds to reporting feedback on a per multicast G-RNTI basis.

[0141] In some aspects, UE DCI component 645 may be configured or otherwise support means for receiving DCI associating a multicast transmission with a multicast G-RNTI.

[0142] In some aspects, to support receiving the first control information, the UE DCI component 645 may be configured to or otherwise support means for receiving a multicast DCI, wherein the multicast DCI includes the first control information and wherein the first feedback scheme corresponds to reporting feedback on a per-multicast G-RNTI basis, the multicast DCI further associating the multicast transmission with the multicast G-RNTI.

[0143] In some aspects, the UE control information component 625 may be configured or otherwise support means for receiving second control information indicating a second feedback scheme for multicast transmission in the NTN. In some aspects, to determine the feedback scheme for the application, the feedback scheme component 630 may be configured or otherwise support means for determining the feedback scheme for the application based on the first feedback scheme and the second feedback scheme.

[0144] In some aspects, the first feedback scheme corresponds to enabling feedback reporting for the multicast G-RNTI and the second feedback scheme corresponds to disabling feedback reporting for the HARQ process ID.

[0145] In some aspects, the UE DCI component 645 may be configured or otherwise support means for receiving a DCI associating a multicast transmission with a multicast G-RNTI and a HARQ ID.

[0146] In some aspects, the message type of the first control information is an RRC message type or a DCI message type.

[0147] In some aspects, the applied feedback scheme is handled as an error case caused by a first feedback scheme indicated by the first control information and a second feedback scheme indicated by the second control information.

[0148] In some aspects, to support operation according to an applied feedback scheme, feedback reporting component 640 may be configured or otherwise support means for refraining from reporting feedback based on a first feedback scheme indicated by the first control information and a second feedback scheme indicated by the second control information.

[0149] In some aspects, to support operation according to an applied feedback scheme, feedback reporting component 640 may be configured to or otherwise support means for populating a codebook with feedback determined from a detection result transmitted by the multicast based on a first feedback scheme indicated by the first control information and a second feedback scheme indicated by the second control information.

[0150] In some aspects, to support operation according to an applied feedback scheme, feedback reporting component 640 may be configured or otherwise support means for filling a codebook with NACK feedback based on a first feedback scheme indicated by the first control information and a second feedback scheme indicated by the second control information.

[0151] In some aspects, feedback alternatives component 655 may be configured or otherwise support means for receiving third control information indicating a set of feedback reporting alternatives. In some aspects, feedback alternatives component 655 may be configured or otherwise support means for determining a feedback reporting alternative from the set of feedback reporting alternatives based on a first feedback scheme indicated by the first control information and a second feedback scheme indicated by the second control information, wherein the applied feedback scheme is based on the determined feedback reporting alternative.

[0152] In some aspects, the feedback scheme applied is based on the feedback codebook type configured for multicast transmission.

[0153] In some aspects, UE capability component 650 may be configured to or otherwise support means for sending a capability message of the first network node to the second network node, wherein the first feedback scheme indicated in the first control information is based on the capability message.

[0154] Figure 7A diagram of a system 700 including a device 705 supporting feedback reporting of multicast communications in an NTN according to one or more aspects of the present disclosure is shown. The device 705 may be an aspect of a device 405, a device 505, a UE 115, or a network node as described herein or include a component of these devices. The device 705 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). The device 705 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 720, an input / output (I / O) controller 710, a transceiver 715, an antenna 725, a memory 730, a code 735, and a processor 740. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 745).

[0155] I / O controller 710 can manage input and output signals for device 705. I / O controller 710 can also manage peripheral devices that are not integrated into device 705. In some cases, I / O controller 710 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 710 can utilize an operating system such as or another known operating system. Additionally or alternatively, I / O controller 710 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 710 may be implemented as part of a processor such as processor 740. In some cases, a user may interact with device 705 via I / O controller 710 or via hardware components controlled by I / O controller 710.

[0156] In some cases, the device 705 may include a single antenna 725. However, in some other cases, the device 705 may have more than one antenna 725, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 715 may communicate bidirectionally via one or more antennas 725, a wired or wireless link, as described herein. For example, the transceiver 715 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 715 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 725 for transmission; and demodulating packets received from one or more antennas 725. The transceiver 715, or the transceiver 715 and one or more antennas 725 may be aspects of the transmitter 415, the transmitter 515, the receiver 410, the receiver 510, or any combination thereof or components thereof as described herein.

[0157] The memory 730 may include random access memory (RAM) and read-only memory (ROM). The memory 730 may store computer-readable, computer-executable code 735 including instructions that, when executed by the processor 740, cause the device 705 to perform various functions described herein. The code 735 may be stored in a non-transitory computer-readable medium such as a system memory or another type of memory. In some cases, the code 735 may not be directly executable by the processor 740, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 730 may also include, among other things, a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0158] The processor 740 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 740 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 740. The processor 740 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 730) to enable the device 705 to perform various functions (e.g., various functions or tasks of supporting feedback reporting of multicast communications in the NTN). For example, the device 705 or a component of the device 705 may include a processor 740 and a memory 730 coupled to or coupled to the processor 740, and the processor 740 and the memory 730 are configured to perform the various functions described herein.

[0159] The communication manager 720 may support wireless communication at a first network node according to various aspects disclosed herein. For example, the communication manager 720 may be configured to or otherwise support a component for receiving a first control information indicating a first feedback scheme for multicast transmission in the NTN. The communication manager 720 may be configured to or otherwise support a component for determining a feedback scheme for an application based on the first feedback scheme. The communication manager 720 may be configured to or otherwise support a component for monitoring multicast transmissions. The communication manager 720 may be configured to or otherwise support a component for operating according to the feedback scheme of the application. In some aspects, in order to operate according to the feedback scheme of the application, the communication manager 720 may be configured to or otherwise support a component for determining whether to report feedback associated with the multicast transmission.

[0160] By including or configuring the communication manager 720 according to various aspects as described herein, the device 705 can support techniques for improving communication reliability, reducing latency, and improving coordination between devices.

[0161] In some aspects, the communication manager 720 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 715, one or more antennas 725, or any combination thereof. Although the communication manager 720 is illustrated as a separate component, in some aspects, one or more functions described with reference to the communication manager 720 may be supported or performed by the processor 740, the memory 730, the code 735, or any combination thereof. For example, the code 735 may include instructions that are executable by the processor 740 to cause the device 705 to perform various aspects of feedback reporting for multicast communications in the NTN as described herein, or the processor 740 and the memory 730 may be otherwise configured to perform or support such operations.

[0162] Figure 8 A block diagram 800 of a device 805 supporting feedback reporting of multicast communications in an NTN according to one or more aspects of the present disclosure is shown. The device 805 may be an example of aspects of a network entity 105 or a network node as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. The device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0163] The receiver 810 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be communicated to other components of the device 805. In some aspects, the receiver 810 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 810 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof.

[0164] The transmitter 815 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 805. For example, the transmitter 815 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)). In some aspects, the transmitter 815 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 815 may support outputting information by sending signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof. In some aspects, the transmitter 815 and the receiver 810 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0165] The communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof, or various components thereof, may be aspects of means for performing various aspects of feedback reporting for multicast communications in the NTN as described herein. For example, the communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0166] In some aspects, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microprocessor, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured to or otherwise supports means for performing the functions described herein. In some aspects, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0167] Additionally or alternatively, in some aspects, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting means for performing the functionality described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0168] In some aspects, the communication manager 820 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the receiver 810, the transmitter 815, or both. For example, the communication manager 820 may receive information from the receiver 810, transmit information to the transmitter 815, or be integrated with the receiver 810, the transmitter 815, or both to obtain information, output information, or perform various other operations as described herein.

[0169] The communication manager 820 may support wireless communication at the first network node according to various aspects disclosed herein. For example, the communication manager 820 may be configured to or otherwise support means for sending first control information indicating a first feedback scheme for multicast transmissions in the NTN. The communication manager 820 may be configured to or otherwise support means for sending multicast transmissions. The communication manager 820 may be configured to or otherwise support means for monitoring feedback associated with the multicast transmission according to an applied feedback scheme used by the second network node, wherein the applied feedback scheme is based on the first feedback scheme.

[0170] By including or configuring the communication manager 820 according to various aspects as described herein, the device 805 (e.g., a processor controlling or otherwise coupled to the receiver 810, the transmitter 815, the communication manager 820, or a combination thereof) can support techniques for reducing processing and more efficiently utilizing communication resources.

[0171] Fig. 9 A block diagram 900 of a device 905 supporting feedback reporting of multicast communications in an NTN according to one or more aspects of the present disclosure is shown. The device 905 may be an example of aspects of the device 805 or the network entity 105 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0172] The receiver 910 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be communicated to other components of the device 905. In some aspects, the receiver 910 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 910 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof.

[0173] The transmitter 915 may provide means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 905. For example, the transmitter 915 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)). In some aspects, the transmitter 915 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 915 may support outputting information by sending signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof. In some aspects, the transmitter 915 and the receiver 910 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0174] The device 905 or its various components may be aspects of a component for performing various aspects of feedback reporting of multicast communications in the NTN as described herein. For example, the communication manager 920 may include a control information component 925, a signal transmitter 930, a feedback component 935, or any combination thereof. The communication manager 920 may be an example of various aspects of the communication manager 820 as described herein. In some aspects, the communication manager 920 or its various components may be configured to use or otherwise cooperate with the receiver 910, the transmitter 915, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0175] The communication manager 920 may support wireless communication at the first network node according to various aspects disclosed herein. The control information component 925 may be configured as or otherwise support means for sending first control information indicating a first feedback scheme for multicast transmissions in the NTN. The signal transmitter 930 may be configured as or otherwise support means for sending multicast transmissions. The feedback component 935 may be configured as or otherwise support means for monitoring feedback associated with the multicast transmission according to an applied feedback scheme used by the second network node, wherein the applied feedback scheme is based on the first feedback scheme.

[0176] Fig.10A block diagram 1000 of a communication manager 1020 supporting feedback reporting of multicast communications in an NTN according to one or more aspects of the present disclosure is shown. The communication manager 1020 may be an example of aspects of the communication manager 820, the communication manager 920, or both as described herein. The communication manager 1020 or its various components may be aspects of a means for performing various aspects of feedback reporting of multicast communications in an NTN as described herein. For example, the communication manager 1020 may include a control information component 1025, a signal transmitter 1030, a feedback component 1035, a DCI component 1040, a capability component 1045, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105), or any combination thereof.

[0177] The communication manager 1020 may support wireless communication at the first network node according to various aspects disclosed herein. The control information component 1025 may be configured as or otherwise support means for sending first control information indicating a first feedback scheme for multicast transmissions in the NTN. The signal transmitter 1030 may be configured as or otherwise support means for sending multicast transmissions. The feedback component 1035 may be configured as or otherwise support means for monitoring feedback associated with the multicast transmission according to an applied feedback scheme used by the second network node, wherein the applied feedback scheme is based on the first feedback scheme.

[0178] In some aspects, the first feedback scheme corresponds to reporting feedback on a per HARQ process ID basis or on a per multicast G-RNTI basis.

[0179] In some aspects, to support sending the first control information, the control information component 1025 may be configured to or otherwise support means for sending unicast RRC signaling, wherein the unicast RRC signaling includes the first control information, and wherein the first feedback scheme corresponds to reporting feedback on a per HARQ process ID basis.

[0180] In some aspects, DCI component 1040 may be configured or otherwise support means for sending DCI associating a multicast transmission with a HARQ process ID.

[0181] In some aspects, to support sending the first control information, the control information component 1025 may be configured to or otherwise support means for sending unicast RRC signaling, wherein the unicast RRC signaling includes the first control information, and wherein the first feedback scheme corresponds to reporting feedback on a per-multicast G-RNTI basis.

[0182] In some aspects, DCI component 1040 may be configured or otherwise support means for transmitting DCI associating a multicast transmission with a multicast G-RNTI.

[0183] In some aspects, to support sending the first control information, the DCI component 1040 may be configured to or otherwise support means for sending a multicast DCI, wherein the multicast DCI includes the first control information and wherein the first feedback scheme corresponds to reporting feedback on a per-multicast G-RNTI basis, the multicast DCI further associating the multicast transmission with the multicast G-RNTI.

[0184] In some aspects, the control information component 1025 may be configured or otherwise support means for sending second control information indicating a second feedback scheme for multicast transmissions in the NTN. In some aspects, the feedback component 1035 may be configured or otherwise support means for identifying a feedback scheme for an application based on the first feedback scheme and the second feedback scheme.

[0185] In some aspects, the first feedback scheme corresponds to enabling feedback reporting for the multicast G-RNTI and the second feedback scheme corresponds to disabling feedback reporting for the HARQ process ID.

[0186] In some aspects, the message type of the first control information is an RRC message type or a DCI message type.

[0187] In some aspects, DCI component 1040 may be configured or otherwise support means for receiving DCI associating a multicast transmission with a multicast G-RNTI and a HARQ ID.

[0188] In some aspects, the applied feedback scheme includes the second network node populating a codebook with feedback associated with the multicast transmission based on a first feedback scheme indicated by the first control information and a second feedback scheme indicated by the second control information.

[0189] In some aspects, the applied feedback scheme includes the second network node filling a codebook with NACK feedback based on a first feedback scheme indicated by the first control information and a second feedback scheme indicated by the second control information.

[0190] In some aspects, control information component 1025 may be configured or otherwise support means for sending third control information indicating a set of feedback reporting alternatives, wherein the applied feedback scheme is based on the set of feedback reporting alternatives.

[0191] In some aspects, the feedback scheme applied is based on the feedback codebook type configured for multicast transmission.

[0192] In some aspects, capability component 1045 may be configured or otherwise support means for receiving, from the second network node, a capability message of the second network node, wherein the first feedback scheme indicated in the first control information is based on the capability message.

[0193] Fig.11 A diagram of a system 1100 including a device 1105 supporting feedback reporting of multicast communications in an NTN according to one or more aspects of the present disclosure is shown. The device 1105 may be an aspect of a device 805, a device 905, a network entity 105, or a network node as described herein or include a component of these devices. The device 1105 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1105 may include components that support output and acquisition of communications, such as a communication manager 1120, a transceiver 1110, an antenna 1115, a memory 1125, a code 1130, and a processor 1135. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1140).

[0194] The transceiver 1110 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some aspects, the transceiver 1110 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some aspects, the transceiver 1110 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some aspects, the device 1105 may include one or more antennas 1115 that may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1110 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., by one or more antennas 1115, by a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1115, from a wired receiver); and demodulating the signal. The transceiver 1110 or the transceiver 1110 and one or more antennas 1115 or a wired interface (where applicable) may be aspects of the transmitter 815, transmitter 915, receiver 810, receiver 910, or any combination thereof or any components thereof as described herein. In some aspects, the transceiver may be operable to support communications via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0195] The memory 1125 may include RAM and ROM. The memory 1125 may store computer-readable, computer-executable code 1130 including instructions that, when executed by the processor 1135, cause the device 1105 to perform various functions described herein. The code 1130 may be stored in a non-transitory computer-readable medium such as a system memory or another type of memory. In some cases, the code 1130 may not be directly executable by the processor 1135, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 1125 may also include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0196] The processor 1135 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the processor 1135 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1135. The processor 1135 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 1125) to enable the device 1105 to perform various functions (e.g., functions or tasks that support feedback reporting of multicast communications in the NTN). For example, the device 1105 or a component of the device 1105 may include a processor 1135 and a memory 1125 coupled to the processor 1135, and the processor 1135 and the memory 1125 are configured to perform the various functions described herein. Processor 1135 can be an aspect of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functionality for performing functions of device 1105 (e.g., by executing code 1130).

[0197] In some aspects, bus 1140 may support communications of protocol layers (e.g., within protocol layers) of a protocol stack. In some aspects, bus 1140 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within components of device 1105, or between different components of device 1105 that may be co-located or located in different locations (e.g., where device 1105 may refer to a system in which one or more of communication manager 1120, transceiver 1110, memory 1125, code 1130, and processor 1135 may be located in one of these different components or divided between different components).

[0198] In some aspects, the communication manager 1120 can manage aspects of communications with the core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communication manager 1120 can manage the delivery of data communications for client devices such as one or more UEs 115. In some aspects, the communication manager 1120 can manage communications with other network entities 105 and can include a controller or scheduler for controlling communications with the UE 115 in coordination with the other network entities 105. In some aspects, the communication manager 1120 can support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0199] The communication manager 1120 may support wireless communication at the first network node according to various aspects disclosed herein. For example, the communication manager 1120 may be configured to or otherwise support means for sending first control information indicating a first feedback scheme for multicast transmissions in the NTN. The communication manager 1120 may be configured to or otherwise support means for sending multicast transmissions. The communication manager 1120 may be configured to or otherwise support means for monitoring feedback associated with the multicast transmission according to an applied feedback scheme used by the second network node, wherein the applied feedback scheme is based on the first feedback scheme.

[0200] By including or configuring the communications manager 1120 according to aspects as described herein, the device 1105 can support techniques for improving communications reliability, reducing latency, and more efficiently utilizing communications resources.

[0201] In some aspects, the communication manager 1120 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1110, one or more antennas 1115 (e.g., where applicable), or any combination thereof. Although the communication manager 1120 is illustrated as a separate component, in some aspects, one or more functions described with reference to the communication manager 1120 may be supported or performed by the processor 1135, the memory 1125, the code 1130, the transceiver 1110, or any combination thereof. For example, the code 1130 may include instructions that are executable by the processor 1135 to cause the device 1105 to perform various aspects of feedback reporting for multicast communications in the NTN as described herein, or the processor 1135 and the memory 1125 may be otherwise configured to perform or support such operations.

[0202] Fig.12 A flowchart illustrating a method 1200 for supporting feedback reporting of multicast communications in an NTN according to one or more aspects of the present disclosure is shown. The operations of the method 1200 may be implemented by a UE, a network node, or a component thereof as described herein. For example, the operations of the method 1200 may be implemented by a UE, a network node, or a component thereof as described in reference to Figures 1 to 7 The described UE 115 performs. In some aspects, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0203] At 1205, the method may include receiving first control information indicating a first feedback scheme for multicast transmission in the NTN. The operations of 1205 may be performed according to various aspects as disclosed herein. In some aspects, various aspects of the operations of 1205 may be performed as described in reference Figure 6 The described UE control information component 625 performs.

[0204] At 1210, the method may include determining a feedback scheme for the application based on the first feedback scheme. The operations of 1210 may be performed according to various aspects as disclosed herein. In some aspects, various aspects of the operations of 1210 may be performed as described in reference to Figure 6 The feedback scheme component 630 performs as described.

[0205] At 1215, the method may include monitoring the multicast transmission. The operations of 1215 may be performed according to various aspects as disclosed herein. In some aspects, various aspects of the operations of 1215 may be performed as described in reference Figure 6 The monitoring component 635 is described as executing.

[0206] At 1220, the method may include operating in accordance with an applied feedback scheme. In some aspects, operating in accordance with an applied feedback scheme may include determining whether to report feedback associated with a multicast transmission. The operations of 1220 may be performed in accordance with various aspects as disclosed herein. In some aspects, various aspects of the operations of 1220 may be performed as described in reference to Figure 6 The feedback reporting component 640 is described as executing.

[0207] Fig.13 A flowchart illustrating a method 1300 for supporting feedback reporting for multicast communications in an NTN according to one or more aspects of the present disclosure is shown. The operations of the method 1300 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1300 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 7 The described UE 115 performs. In some aspects, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0208] At 1305, the method may include receiving unicast RRC signaling, wherein the unicast RRC signaling includes first control information indicating a first feedback scheme for multicast transmissions in the NTN, and wherein the first feedback scheme corresponds to reporting feedback based on each HARQ process ID. The operations of 1305 may be performed in accordance with various aspects as disclosed herein. In some aspects, various aspects of the operations of 1305 may be performed as described in reference to Figure 6 The described UE control information component 625 performs.

[0209] At 1310, the method may include determining a feedback scheme for the application based on the first feedback scheme. The operations of 1310 may be performed according to various aspects as disclosed herein. In some aspects, various aspects of the operations of 1310 may be performed as described in reference to Figure 6 The feedback scheme component 630 performs as described.

[0210] At 1315, the method may include monitoring the multicast transmission. The operations of 1315 may be performed according to various aspects as disclosed herein. In some aspects, various aspects of the operations of 1315 may be performed as described in reference Figure 6 The monitoring component 635 is described as executing.

[0211] At 1320, the method may include operating in accordance with an applied feedback scheme. In some aspects, operating in accordance with an applied feedback scheme may include determining whether to report feedback associated with a multicast transmission. The operations of 1320 may be performed in accordance with various aspects as disclosed herein. In some aspects, various aspects of the operations of 1320 may be performed as described in reference to Figure 6 The feedback reporting component 640 is described as executing.

[0212] Fig.14 A flowchart illustrating a method 1400 for supporting feedback reporting of multicast communications in an NTN according to one or more aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 7 The described UE 115 performs. In some aspects, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0213] At 1405, the method may include receiving unicast RRC signaling, wherein the unicast RRC signaling includes first control information indicating a first feedback scheme for multicast transmissions in the NTN, and wherein the first feedback scheme corresponds to reporting feedback on a per-multicast G-RNTI basis. The operations of 1405 may be performed in accordance with various aspects as disclosed herein. In some aspects, aspects of the operations of 1405 may be performed as described in reference to Figure 6 The described UE control information component 625 performs.

[0214] At 1410, the method may include determining a feedback scheme for the application based on the first feedback scheme. The operations of 1410 may be performed according to various aspects as disclosed herein. In some aspects, various aspects of the operations of 1410 may be performed as described in reference to Figure 6 The feedback scheme component 630 performs as described.

[0215] At 1415, the method may include monitoring the multicast transmission. The operations of 1415 may be performed according to various aspects as disclosed herein. In some aspects, various aspects of the operations of 1415 may be performed as described in reference Figure 6 The monitoring component 635 is described as executing.

[0216] At 1420, the method may include operating in accordance with an applied feedback scheme. In some aspects, operating in accordance with an applied feedback scheme may include determining whether to report feedback associated with a multicast transmission. The operations of 1420 may be performed in accordance with various aspects as disclosed herein. In some aspects, various aspects of the operations of 1420 may be performed as described in reference to Figure 6 The feedback reporting component 640 is described as executing.

[0217] Fig.15 A flow chart illustrating a method 1500 for supporting feedback reporting of multicast communications in an NTN according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 3 as well as Figures 8 to 11 The described network entity performs. In some aspects, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0218] At 1505, the method may include sending first control information indicating a first feedback scheme for multicast transmissions in the NTN. The operations of 1505 may be performed according to various aspects as disclosed herein. In some aspects, various aspects of the operations of 1505 may be performed as described in reference to Fig.10 The control information component 1025 described performs.

[0219] At 1510, the method may include sending a multicast transmission. The operations of 1510 may be performed according to various aspects as disclosed herein. In some aspects, various aspects of the operations of 1510 may be performed as described in reference Fig.10 The signal transmitter 1030 described performs.

[0220] At 1515, the method may include monitoring feedback associated with the multicast transmission according to an applied feedback scheme used by the second network node, wherein the applied feedback scheme is based on the first feedback scheme. The operations of 1515 may be performed according to various aspects as disclosed herein. In some aspects, various aspects of the operations of 1515 may be performed as described in reference to Fig.10 The feedback component 1035 is described as executing.

[0221] Fig.16 A flowchart illustrating a method 1600 for supporting feedback reporting of multicast communications in an NTN according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 3 as well as Figures 8 to 11The described network entity performs. In some aspects, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0222] At 1605, the method may include sending unicast RRC signaling, wherein the unicast RRC signaling includes first control information indicating a first feedback scheme for multicast transmissions in the NTN, and wherein the first feedback scheme corresponds to reporting feedback based on each HARQ process ID. The operations of 1605 may be performed according to various aspects as disclosed herein. In some aspects, various aspects of the operations of 1605 may be performed as described in reference Fig.10 The control information component 1025 described performs.

[0223] At 1610, the method may include sending a multicast transmission. The operations of 1610 may be performed according to various aspects as disclosed herein. In some aspects, various aspects of the operations of 1610 may be performed as described in reference Fig.10 The signal transmitter 1030 described performs.

[0224] At 1615, the method may include monitoring feedback associated with the multicast transmission according to an applied feedback scheme used by the second network node, wherein the applied feedback scheme is based on the first feedback scheme. The operations of 1615 may be performed according to various aspects as disclosed herein. In some aspects, various aspects of the operations of 1615 may be performed as described in reference to Fig.10 The feedback component 1035 is described as executing.

[0225] Fig.17 A flowchart illustrating a method 1700 for supporting feedback reporting of multicast communications in an NTN according to one or more aspects of the present disclosure is shown. The operations of the method 1700 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 3 as well as Figures 8 to 11 The described network entity performs. In some aspects, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0226] At 1705, the method may include sending unicast RRC signaling, wherein the unicast RRC signaling includes first control information indicating a first feedback scheme for multicast transmissions in the NTN, and wherein the first feedback scheme corresponds to reporting feedback on a per-multicast G-RNTI basis. The operations of 1705 may be performed in accordance with various aspects as disclosed herein. In some aspects, aspects of the operations of 1705 may be performed as described in reference to Fig.10 The control information component 1025 described performs.

[0227] At 1710, the method may include sending a multicast transmission. The operations of 1710 may be performed according to various aspects as disclosed herein. In some aspects, various aspects of the operations of 1710 may be performed as described in reference Fig.10 The signal transmitter 1030 described performs.

[0228] At 1715, the method may include monitoring feedback associated with the multicast transmission according to an applied feedback scheme used by the second network node, wherein the applied feedback scheme is based on the first feedback scheme. The operations of 1715 may be performed according to various aspects as disclosed herein. In some aspects, various aspects of the operations of 1715 may be performed as described in reference to Fig.10 The feedback component 1035 is described as executing.

[0229] The following provides an overview of various aspects of the disclosure:

[0230] Aspect 1: A method for wireless communication at a first network node, comprising: receiving first control information indicating a first feedback scheme for multicast transmission in an NTN; determining an applied feedback scheme based on the first feedback scheme; monitoring multicast transmission; and operating according to the applied feedback scheme, wherein operating according to the applied feedback scheme includes: determining whether to report feedback associated with the multicast transmission.

[0231] Aspect 2: The method according to aspect 1, wherein the first feedback scheme corresponds to reporting feedback on a per-HARQ process ID basis or on a per-multicast G-RNTI basis.

[0232] Aspect 3: A method according to any one of Aspects 1 to 2, wherein receiving the first control information comprises: receiving unicast RRC signaling, wherein the unicast RRC signaling includes the first control information, and wherein the first feedback scheme corresponds to reporting feedback based on each HARQ process ID.

[0233] Aspect 4: The method according to aspect 3 further includes: receiving a DCI associating the multicast transmission with a HARQ process ID.

[0234] Aspect 5: A method according to any one of Aspects 1 to 4, wherein receiving the first control information comprises: receiving unicast RRC signaling, wherein the unicast RRC signaling includes the first control information, and wherein the first feedback scheme corresponds to reporting feedback based on each multicast G-RNTI.

[0235] Aspect 6: The method of claim 5, further comprising: receiving a DCI associating the multicast transmission with a multicast G-RNTI.

[0236] Aspect 7: A method according to Aspect 1, wherein receiving the first control information includes: receiving a multicast DCI, wherein the multicast DCI includes the first control information, and wherein the first feedback scheme corresponds to reporting feedback based on each multicast G-RNTI, and the multicast DCI also associates the multicast transmission with the multicast G-RNTI.

[0237] Aspect 8: The method according to any one of Aspects 1 to 7 further includes: receiving second control information indicating a second feedback scheme for multicast transmission in the NTN, wherein determining the feedback scheme for the application includes: determining the feedback scheme for the application based on the first feedback scheme and the second feedback scheme.

[0238] Aspect 9: The method according to aspect 8, wherein the first feedback scheme corresponds to enabling feedback reporting for multicast G-RNTI, and the second feedback scheme corresponds to disabling feedback reporting for HARQ process ID.

[0239] Aspect 10: The method according to aspect 9 further comprises: receiving a DCI associating the multicast transmission with the multicast G-RNTI and the HARQ ID.

[0240] Aspect 11: The method according to any one of aspects 8 to 10, wherein the message type of the first control information is an RRC message type or a DCI message type.

[0241] Aspect 12: A method according to any one of Aspects 8 to 11, wherein the feedback scheme of the application is processed as an error case, and the error case is caused by the first feedback scheme indicated by the first control information and the second feedback scheme indicated by the second control information.

[0242] Aspect 13: A method according to any one of Aspects 8 to 11, wherein operating according to the feedback scheme of the application includes: avoiding reporting the feedback based on the first feedback scheme indicated by the first control information and the second feedback scheme indicated by the second control information.

[0243] Aspect 14: A method according to any one of Aspects 8 to 11, wherein operating according to the feedback scheme of the application includes: filling a codebook with feedback determined from the detection result of the multicast transmission based on the first feedback scheme indicated by the first control information and the second feedback scheme indicated by the second control information.

[0244] Aspect 15: The method according to any one of aspects 8 to 11, wherein operating according to the applied feedback scheme includes: filling a codebook with NACK feedback based on the first feedback scheme indicated by the first control information and the second feedback scheme indicated by the second control information.

[0245] Aspect 16: The method according to any one of Aspects 8 to 15 further includes: receiving third control information indicating a set of feedback report alternative schemes; and determining a feedback report alternative scheme from the set of feedback report alternative schemes based on the first feedback scheme indicated by the first control information and the second feedback scheme indicated by the second control information, wherein the applied feedback scheme is based on the determined feedback report alternative scheme.

[0246] Aspect 17: The method according to any one of aspects 1 to 16, wherein the applied feedback scheme is based on a feedback codebook type configured for the multicast transmission.

[0247] Aspect 18: The method according to any one of Aspects 1 to 17 further includes: sending a capability message of the first network node to a second network node, wherein the first feedback scheme indicated in the first control information is based on the capability message.

[0248] Aspect 19: A method for wireless communication at a first network node, comprising: sending first control information indicating a first feedback scheme for a multicast transmission in an NTN; sending a multicast transmission; and monitoring feedback associated with the multicast transmission based on a feedback scheme of an application used by a second network node, wherein the feedback scheme of the application is based on the first feedback scheme.

[0249] Aspect 20: The method according to aspect 19, wherein the first feedback scheme corresponds to reporting feedback on a per HARQ process ID basis or on a per multicast G-RNTI basis.

[0250] Aspect 21: A method according to any one of Aspects 19 to 20, wherein sending the first control information comprises: sending unicast RRC signaling, wherein the unicast RRC signaling includes the first control information, and wherein the first feedback scheme corresponds to reporting feedback based on each HARQ process ID.

[0251] Aspect 22: The method according to aspect 21 further comprises: sending a DCI associating the multicast transmission with a HARQ process ID.

[0252] Aspect 23: A method according to any one of Aspects 19 to 22, wherein sending the first control information comprises: sending unicast RRC signaling, wherein the unicast RRC signaling includes the first control information, and wherein the first feedback scheme corresponds to reporting feedback based on each multicast G-RNTI.

[0253] Aspect 24: The method according to aspect 23 further comprises: sending a DCI associating the multicast transmission with a multicast G-RNTI.

[0254] Aspect 25: A method according to Aspect 19, wherein sending the first control information includes: sending a multicast DCI, wherein the multicast DCI includes the first control information, and wherein the first feedback scheme corresponds to reporting feedback based on each multicast G-RNTI, and the multicast DCI also associates the multicast transmission with the multicast G-RNTI.

[0255] Aspect 26: The method according to any one of Aspects 19 to 25 further includes: sending second control information indicating a second feedback scheme for multicast transmission in the NTN; and identifying a feedback scheme for the application based on the first feedback scheme and the second feedback scheme.

[0256] Aspect 27: The method according to aspect 26, wherein the first feedback scheme corresponds to enabling feedback reporting for multicast G-RNTI, and the second feedback scheme corresponds to disabling feedback reporting for HARQ process ID.

[0257] Aspect 28: The method according to any one of Aspects 26 to 27, wherein the message type of the first control information is an RRC message type or a DCI message type.

[0258] Aspect 29: The method according to aspect 28, further comprising: receiving a DCI associating the multicast transmission with the multicast G-RNTI and the HARQ ID.

[0259] Aspect 30: A method according to any one of aspects 26 to 29, wherein the applied feedback scheme comprises the second network node filling a codebook with the feedback associated with the multicast transmission based on the first feedback scheme indicated by the first control information and the second feedback scheme indicated by the second control information.

[0260] Aspect 31: The method according to any one of aspects 26 to 29, wherein the applied feedback scheme comprises the second network node filling a codebook with NACK feedback based on the first feedback scheme indicated by the first control information and the second feedback scheme indicated by the second control information.

[0261] Aspect 32: The method according to any one of Aspects 26 to 31 further includes: sending third control information indicating a set of feedback report alternative schemes, wherein the feedback scheme of the application is based on the set of feedback report alternative schemes.

[0262] Aspect 33: The method according to any one of aspects 19 to 32, wherein the applied feedback scheme is based on a feedback codebook type configured for the multicast transmission.

[0263] Aspect 34: The method according to any one of aspects 19 to 33 further includes: receiving a capability message of the second network node from the second network node, wherein the first feedback scheme indicated in the first control information is based on the capability message.

[0264] Aspect 35: An apparatus for wireless communication at a first network node, comprising a memory and at least one processor coupled to the memory, the at least one processor configured to perform the method according to any one of aspects 1 to 18.

[0265] Aspect 36: An apparatus for wireless communication at a first network node, comprising at least one means for performing a method according to any one of aspects 1 to 18.

[0266] Aspect 37: A non-transitory computer readable medium having stored thereon code for wireless communication, the code, when executed by a first network node, causes the first network node to perform a method according to any one of aspects 1 to 18.

[0267] Aspect 38: An apparatus for wireless communication at a first network node, comprising a memory and at least one processor coupled to the memory, the at least one processor configured to perform the method according to any one of aspects 19 to 34.

[0268] Aspect 39: An apparatus for wireless communication at a first network node, comprising at least one means for performing a method according to any one of aspects 19 to 34.

[0269] Aspect 40: A non-transitory computer readable medium having stored thereon code for wireless communication, the code, when executed by a first network node, causes the first network node to perform a method according to any one of aspects 19 to 34.

[0270] The methods described herein describe possible implementations, and the operations and steps may be rearranged or otherwise modified, and other implementations are possible. In addition, aspects from two or more methods may be combined.

[0271] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0272] The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0273] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed with a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0274] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored on or sent via a computer-readable medium as one or more instructions or codes. Other aspects and specific implementations are within the scope of the present disclosure and claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the functions are implemented at different physical locations.

[0275] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that promotes the transfer of computer program from one place to another place.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code member and can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure Any other non-transient medium.In addition, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0276] As used herein, the term "or" is an inclusive "or" unless restrictive language is used with respect to the listed alternatives. For example, references to "X is based on A or B" should be interpreted as including within its scope X based on A, X based on B, and X based on A and B. In this regard, references to "X is based on A or B" refer to "at least one of A or B" or "one or more of A or B" because "or" is inclusive. Similarly, references to "X is based on A, B, or C" should be interpreted as including within its scope X based on A, X based on B, X based on C, X based on A and B, X based on A and C, X based on B and C, and X based on A, B, and C. In this regard, references to "X is based on A, B, or C" refer to "at least one of A, B, or C" or "one or more of A, B, or C" because "or" is inclusive. As an example of restrictive language, a reference to "X is based on only one of A or B" should be interpreted to include within its scope X being based on A and X being based on B, but not including X being based on both A and B. Furthermore, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based on at least A" unless specifically stated differently. Likewise, as used herein, the phrase "set" should be understood to include the possibility of a set having one member. That is, the phrase "set" should be understood in the same manner as "one or more" or "at least one."

[0277] The terms "determine" or "determining" encompass a wide variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, etc. Additionally, "determining" may include receiving (such as receiving information), accessing (such as accessing data in a memory), etc. Additionally, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

[0278] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between the similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label, regardless of the second or other subsequent reference labels.

[0279] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all aspects that may be implemented or within the scope of the claims. The terms "aspect" or "example" used herein mean "used as an aspect, example, instance, or illustration," rather than "preferred" or "advantageous over other aspects." The specific embodiments include specific details for providing an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some instances, structures and devices are shown in block diagram form to avoid obscuring the concepts of the aspects.

[0280] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the aspects and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A first network node for wireless communication, include: Memory; as well as at least one processor coupled to the memory, wherein the at least one processor is configured to: receiving first control information indicating a first feedback scheme for multicast transmissions in a non-terrestrial network; Determining a feedback scheme for an application based on the first feedback scheme; monitoring multicast transmissions; and The at least one processor is configured to: A determination is made as to whether to report feedback associated with the multicast transmission.

2. The first network node of claim 1, wherein the first feedback scheme corresponds to reporting feedback on a per hybrid automatic repeat request process identifier basis or on a per multicast group radio network temporary identifier basis.

3. The first network node according to claim 1, wherein in order to receive the first control information, the at least one processor is configured to: Unicast radio resource control signaling is received, wherein the unicast radio resource control signaling includes the first control information, and wherein the first feedback scheme corresponds to reporting feedback on a per hybrid automatic repeat request process identifier basis.

4. The first network node of claim 3, wherein the at least one processor is further configured to: Downlink control information is received that associates the multicast transmission with a hybrid automatic repeat request process identifier.

5. The first network node of claim 1 , wherein to receive the first control information, the at least one processor is configured to: Unicast radio resource control signaling is received, wherein the unicast radio resource control signaling includes the first control information, and wherein the first feedback scheme corresponds to reporting feedback on a per multicast group radio network temporary identifier basis.

6. The first network node of claim 5, wherein the at least one processor is further configured to: Downlink control information is received that associates the multicast transmission with a multicast group radio network temporary identifier.

7. The first network node of claim 1 , wherein to receive the first control information, the at least one processor is configured to: receiving multicast downlink control information, wherein the multicast downlink control information includes the first control information, and wherein the first feedback scheme corresponds to reporting feedback on a per multicast group radio network temporary identifier basis, the multicast downlink control information further associating the multicast transmission with a multicast group radio network temporary identifier.

8. The first network node of claim 1 , wherein to determine a feedback scheme for the application, the at least one processor is configured to: receiving second control information indicating a second feedback scheme for multicast transmission in the non-terrestrial network, wherein to determine a feedback scheme for the application based on the first feedback scheme, the at least one processor is configured to: A feedback scheme for the application is determined based on the first feedback scheme and the second feedback scheme.

9. The first network node of claim 8, wherein the first feedback scheme corresponds to enabling feedback reporting of a multicast group radio network temporary identifier and the second feedback scheme corresponds to disabling feedback reporting of a hybrid automatic repeat request process identifier.

10. The first network node of claim 9, wherein the at least one processor is further configured to: Downlink control information is received that associates the multicast transmission with the multicast group radio network temporary identifier and the hybrid automatic repeat request process identifier.

11. The first network node according to claim 8, wherein a message type of the first control information is a radio resource control message type or a downlink control information message type.

12. The first network node according to claim 8, wherein the applied feedback scheme is handled as an error case, the error case being caused by the first feedback scheme indicated by the first control information and the second feedback scheme indicated by the second control information.

13. The first network node of claim 8, wherein to operate according to the applied feedback scheme, the at least one processor is configured to: Avoid reporting the feedback based on the first feedback scheme indicated by the first control information and the second feedback scheme indicated by the second control information.

14. The first network node of claim 8, wherein to operate according to the applied feedback scheme, the at least one processor is configured to: A codebook is populated with feedback determined from the detection result of the multicast transmission based on the first feedback scheme indicated by the first control information and the second feedback scheme indicated by the second control information.

15. The first network node of claim 8, wherein to operate according to the applied feedback scheme, the at least one processor is configured to: A codebook is filled with negative acknowledgement feedback based on the first feedback scheme indicated by the first control information and the second feedback scheme indicated by the second control information.

16. The first network node of claim 1, wherein the applied feedback scheme is based on a feedback codebook type configured for the multicast transmission.

17. The first network node of claim 1, wherein the at least one processor is further configured to: A capability message of the first network node is sent to a second network node, wherein the first feedback scheme indicated in the first control information is based on the capability message.

18. A first network node for wireless communication, include: Memory; as well as at least one processor coupled to the memory, wherein the at least one processor is configured to: transmitting first control information indicating a first feedback scheme for multicast transmission in the non-terrestrial network; Sending a multicast transmission; and Feedback associated with the multicast transmission is monitored according to an applied feedback scheme used by a second network node, wherein the applied feedback scheme is based on the first feedback scheme.

19. The first network node of claim 18, wherein the first feedback scheme corresponds to reporting feedback on a per hybrid automatic repeat request process identifier basis or on a per multicast group radio network temporary identifier basis.

20. The first network node of claim 18, wherein to send the first control information, the at least one processor is configured to: Unicast radio resource control signaling is sent, wherein the unicast radio resource control signaling includes the first control information, and wherein the first feedback scheme corresponds to reporting feedback on a per hybrid automatic repeat request process identifier basis.

21. The first network node of claim 18, wherein to send the first control information, the at least one processor is configured to: Unicast radio resource control signaling is sent, wherein the unicast radio resource control signaling includes the first control information, and wherein the first feedback scheme corresponds to reporting feedback on a per multicast group radio network temporary identifier basis.

22. The first network node of claim 18, wherein to send the first control information, the at least one processor is configured to: sending multicast downlink control information, wherein the multicast downlink control information includes the first control information, and wherein the first feedback scheme corresponds to reporting feedback on a per multicast group radio network temporary identifier basis, the multicast downlink control information further associating the multicast transmission with a multicast group radio network temporary identifier.

23. The first network node of claim 18, wherein the at least one processor is further configured to: transmitting second control information indicating a second feedback scheme for multicast transmissions in the non-terrestrial network; and A feedback scheme for the application is identified based on the first feedback scheme and the second feedback scheme.

24. The first network node of claim 23, wherein the applied feedback scheme comprises the second network node filling a codebook with the feedback associated with the multicast transmission based on the first feedback scheme indicated by the first control information and the second feedback scheme indicated by the second control information.

25. The first network node of claim 18, wherein the applied feedback scheme is based on a feedback codebook type configured for the multicast transmission.

26. The first network node of claim 18, wherein the at least one processor is further configured to: A capability message of the second network node is received from the second network node, wherein the first feedback scheme indicated in the first control information is based on the capability message.

27. A method of wireless communication performed by a first network node, include: receiving first control information indicating a first feedback scheme for multicast transmissions in a non-terrestrial network; Determining a feedback scheme for an application based on the first feedback scheme; Monitor multicast transmissions; as well as Operating according to a feedback scheme of the application, wherein operating according to the feedback scheme of the application comprises: A determination is made as to whether to report feedback associated with the multicast transmission.

28. The method of claim 27, wherein the first feedback scheme corresponds to reporting feedback on a per hybrid automatic repeat request process identifier basis or on a per multicast group radio network temporary identifier basis.

29. A method of wireless communication performed by a first network node, include: transmitting first control information indicating a first feedback scheme for multicast transmission in the non-terrestrial network; send multicast send; as well as Feedback associated with the multicast transmission is monitored according to an applied feedback scheme used by a second network node, wherein the applied feedback scheme is based on the first feedback scheme.

30. The method of claim 29, wherein the first feedback scheme corresponds to reporting feedback on a per hybrid automatic repeat request process identifier basis or on a per multicast group radio network temporary identifier basis.

Citation Information

Patent Citations

  • Feedback reporting for multicast communication in a non-terrestrial network

    US20230361928A1