HARQ operation for multicast service

Abstract

Aspects of the present disclosure relate to HARQ operations for multicast services. In one aspect, a UE receives data for a multicast service from a base station. The data is associated with a first configuration, and the first configuration is associated with a mapping between the data and the HARQ. The UE determines a HARQ operation associated with the data based on the first configuration. In this manner, a scheme for HARQ operation for MBS multicast service may be proposed. The mechanisms for mapping data to HARQ processes and thereby determining HARQ operations may help avoid potential misalignment in the design for HARQ operations for data and HARQ processes, thus ensuring a unified solution for HARQ operations that meets requirements for both multicast services and HARQ processes.

Description

Technical Field

[0001] This disclosure relates to wireless communications, and more particularly to user equipment (UE), base station, processor, method, and non-transitory computer-readable medium for performing Hybrid Automatic Repeat Request (HARQ) operations for multicast services. Background Technology

[0002] A wireless communication system may include one or more network communication devices (such as base stations), which may also be referred to as eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. Each network communication device (such as a base station) may support wireless communication for one or more user communication devices, which may also be referred to as user equipment (UE), or other suitable terms. The wireless communication system may support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). Additionally, the wireless communication system may support wireless communication across a variety of radio access technologies, including third-generation (3G) radio access technology, fourth-generation (4G) radio access technology, fifth-generation (5G) radio access technology, and other suitable radio access technologies other than 5G (e.g., sixth-generation (6G)).

[0003] In 3GPP Rel-17, the features of Multicast and Broadcast Services (MBS) were introduced for New Radio (NR) to provide Point-to-Multipoint (PTM) services with substantial improvements in efficient resource utilization and user experience. MBS introduced HARQ feedback options for multicast services to meet different requirements. Further research on implementing HARQ operations for multicast services is still needed. Summary of the Invention

[0004] This disclosure relates to a UE, a base station, a processor, a method for wireless communication, and a non-transitory computer-readable medium for performing HARQ operations for multicast services.

[0005] In a first aspect of this solution, the UE receives data from the base station for multicast services. The data is associated with a first configuration, and this first configuration is associated with a mapping between the data and the HARQ process. Based on the first configuration, the UE determines the HARQ operation associated with the data. In this way, a scheme for HARQ operations for MBS multicast services can be proposed. The mechanism for mapping data to the HARQ process and thus determining the HARQ operation can help avoid potential misalignments in the design of HARQ operations for both data and the HARQ process, thus ensuring a unified solution for HARQ operations that meets the requirements for both multicast services and the HARQ process.

[0006] In some implementations of the methods and apparatus described herein, a first HARQ feedback configuration for data may be absent, and a second HARQ feedback configuration for the HARQ process may be disabled.

[0007] In some implementations of the methods and apparatus described herein, HARQ operations may include skipping the generation and reporting of HARQ acknowledgment (HARQ-ACK) information for data mapped to the HARQ process.

[0008] In some implementations of the methods and apparatus described herein, the HARQ operation may include: generating a negative acknowledgment (NACK) for the HARQ-ACK information when a first type of HARQ-ACK codebook is configured for HARQ-ACK information for data, and reporting a NACK for the data mapped to the HARQ process.

[0009] In some implementations of the methods and apparatus described herein, a first HARQ feedback configuration for data can be enabled, and a second HARQ feedback configuration for the HARQ process can be enabled.

[0010] In some implementations of the methods and apparatus described herein, the multicast service may be associated with a non-terrestrial network (NTN). Some implementations of the methods and apparatus described herein may further include: sending HARQ-ACK information to a base station indicating a request for retransmission of data; and monitoring retransmissions multicast from the base station after a first duration following the transmission of the HARQ-ACK information. The first duration may be associated with a round-trip time (RTT) value between the user equipment and the base station.

[0011] In some implementations of the methods and apparatus described herein, the first duration may be based on a first HARQ-RTT timer whose duration corresponds to the sum of the duration of a second HARQ-RTT timer for point-to-multipoint (PTM) services in a terrestrial network and the RTT value, wherein the first HARQ-RTT timer may be associated with the duration for skipping monitoring of multicast retransmissions of data for multicast services in an NTN.

[0012] In some implementations of the methods and apparatus described herein, the first duration may be based on a second HARQ-RTT timer whose duration is extended by an RTT value.

[0013] In some implementations of the methods and apparatus described herein, the first duration may be based on a second HARQ-RTT timer whose duration corresponds to the duration of a third HARQ-RTT timer used for point-to-point (PTP) services in the NTN.

[0014] In some implementations of the methods and apparatus described herein, multicast services may be associated with NTN. Some implementations of the methods and apparatus described herein may also include: in ACK-NACK feedback mode, sending HARQ-ACK information to the base station, wherein the HARQ-ACK information indicates a request for retransmission of data; and monitoring unicast retransmissions from the base station after a second duration following the transmission of the HARQ-ACK information. The second duration may be associated with the RTT value between the user equipment and the base station.

[0015] In some implementations of the methods and apparatus described herein, the second duration may be based on a fifth HARQ-RTT timer, the duration of which corresponds to the sum of the fourth HARQ-RTT timer and the RTT value for PTP service in the terrestrial network. The fifth HARQ-RTT timer may be associated with the duration for skipping the monitoring of retransmissions of data for unicast service in the NTN.

[0016] In some implementations of the methods and apparatus described herein, the second duration may be based on a sixth HARQ-RTT timer, the duration of which corresponds to the duration of a third HARQ-RTT timer used for PTP services in the NTN. The sixth HARQ-RTT timer may be associated with a duration used to skip monitoring retransmissions of data used for unicast services in the NTN.

[0017] In some implementations of the methods and apparatus described herein, the second duration may be based on a third HARQ-RTT timer used for PTP services in NTN.

[0018] In some implementations of the methods and apparatus described herein, a first HARQ feedback configuration for data can be enabled, a NACK-only feedback mode can be configured for data, a first type of HARQ-ACK codebook can be configured for HARQ-ACK information for data, and a second HARQ feedback configuration for the HARQ process can be disabled.

[0019] Some implementations of the methods and apparatus described herein may also include: generating a NACK for HARQ-ACK information when data is not correctly decoded; and sending a NACK to the base station indicating a request for retransmission of the data.

[0020] In some implementations of the methods and apparatus described herein, the multicast service may be associated with an NTN. Some implementations of the methods and apparatus described herein may also include monitoring retransmissions of multicast from the base station after a third duration following the transmission of a NACK. This third duration may be associated with the RTT value between the user equipment and the base station.

[0021] In some implementations of the methods and apparatus described herein, the third duration may be based on a first HARQ-RTT timer whose duration corresponds to the sum of the duration of a second HARQ-RTT timer for PTM services in the terrestrial network and the RTT value. The first HARQ-RTT timer may be associated with the duration for skipping multicast retransmissions of data used for multicast services in the NTN.

[0022] In some implementations of the methods and apparatus described herein, the third duration may be based on a second HARQ-RTT timer whose duration is extended by an RTT value.

[0023] In some implementations of the methods and apparatus described herein, the third duration may be based on a second HARQ-RTT timer whose duration corresponds to the duration of a third HARQ-RTT timer used for PTP services in the NTN.

[0024] Some implementations of the methods and apparatus described herein may further include receiving, via dedicated signaling or via common signaling, an indication from a base station to enable a first HARQ feedback configuration for data.

[0025] Some implementations of the methods and apparatus described herein may also include receiving from a base station, via Radio Resource Control (RRC) signaling or in downlink control information (DCI), an indication to disable or enable a second HARQ feedback configuration for the HARQ process.

[0026] In a second aspect of this solution, the base station determines a mapping between data used for multicast services and the Hybrid Automatic Repeat Request (HARQ) process. The base station sends data associated with a first configuration to the user equipment. This first configuration can be associated with the mapping. By providing a mapping between data used for multicast services and the HARQ process, potential misalignments in the design of HARQ operations for both data and the HARQ process can be avoided, thus ensuring a unified solution for HARQ operations that meets the requirements of both multicast services and the HARQ process.

[0027] In some implementations of the methods and apparatus described herein, a first HARQ feedback configuration for data may be absent, and a second HARQ feedback configuration for the HARQ process may be disabled.

[0028] In some implementations of the methods and apparatus described herein, a first HARQ feedback configuration for data can be enabled, and a second HARQ feedback configuration for the HARQ process can be enabled.

[0029] In some implementations of the methods and apparatus described herein, a first HARQ feedback configuration for data can be enabled, a negative acknowledgment-only (NACK-only) feedback mode can be configured for data, a first type of HARQ-ACK codebook can be configured for HARQ-ACK information for data, and a second HARQ feedback configuration for the HARQ process can be disabled.

[0030] Some implementations of the methods and apparatus described herein may also include: receiving a NACK for data from the user equipment in a HARQ-ACK message; decoding the NACK; and retransmitting the data to the user equipment.

[0031] Some implementations of the methods and apparatus described herein may also include sending an indication to the user equipment via dedicated signaling or public signaling to enable a first HARQ feedback configuration for data.

[0032] Some implementations of the methods and apparatus described herein may also include sending an indication to the user equipment via Radio Resource Control (RRC) signaling or in Downlink Control Information (DCI) to enable or disable a second HARQ feedback configuration for the HARQ process. Attached Figure Description

[0033] Figure 1 An example of a wireless communication system supporting HARQ operation for multicast services according to various aspects of this disclosure is illustrated.

[0034] Figure 2 An example signaling diagram illustrating an example procedure for supporting HARQ operations for multicast services according to various aspects of this disclosure is shown.

[0035] Figure 3 An example process for supporting HARQ operations for multicast services according to various aspects of this disclosure is illustrated.

[0036] Figures 4 to 5 An example of a device supporting HARQ operation for multicast services according to various aspects of this disclosure is illustrated.

[0037] Figures 6 to 7 An example of a processor supporting HARQ operations for multicast services according to various aspects of this disclosure is illustrated.

[0038] Figures 8 to 11 The diagram illustrates a flowchart of a method for supporting HARQ operations for multicast services according to various aspects of this disclosure. Detailed Implementation

[0039] The principles of this disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of this disclosure. This disclosure described herein can be implemented in various ways other than those described below.

[0040] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0041] References to "an embodiment," "example embodiment," "embodiment," "some embodiments," etc., in this disclosure indicate that the embodiments(s) described may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same(s) embodiments(s). Additionally, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is believed that in conjunction with other embodiments (whether explicitly described or not) affecting such feature, structure, or characteristic is within the knowledge of those skilled in the art.

[0042] It should be understood that although the terms “first” and “second”, etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may also be referred to as a second element without departing from the scope of the embodiments, and similarly, a second element may also be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.

[0043] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” as used herein are also intended to include the plural forms. It should also be understood that the terms “comprising,” “including,” “having,” “having,” “containing,” and / or “comprising” as used herein specify the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. For example, the term “includes” and variations thereof should be understood as open terms meaning “including, but not limited to.” The term “based on” should be understood as “at least partially based on.” The terms “one embodiment” and “embodiment” should be understood as “at least one embodiment.” The term “another embodiment” should be understood as “at least one other embodiment.” The use of expressions such as “A and / or B” can mean “only A” or “only B” or “both A and B.” Other explicit or implicit definitions may be included below.

[0044] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as 5G New Radio (NR), Long Term Evolution (LTE), LTE-A Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in a communication network can be performed according to any suitable generation of communication protocols, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G) communication protocols, and / or any other currently known or to be developed in the future. Embodiments of this disclosure can be applied to various communication systems. Given the rapid development of communications, there will certainly be future types of communication technologies and systems in which this disclosure can be embodied. This should not be construed as limiting the scope of this disclosure to the systems described above.

[0045] As used herein, the term "network device" generally refers to a node in a communication network through which terminal devices can access and receive services. Network devices can refer to base stations (BS) or access points (APs), such as Node B (NodeB or NB), Radio Access Network (RAN) nodes, Evolved Node B (eNodeB or eNB), NRNB (also known as gNB), Remote Radio Unit (RRU), Radio Header (RH), infrastructure equipment for V2X (vehicle-to-everything) communication, Transmitter Receiver Point (TRP), Receiver Point (RP), Remote Radio Header (RRH), relay, Integrated Access and Backhaul (IAB) nodes, low-power nodes (such as femto-BS, pico-BS, etc.), depending on the terminology and technology applied.

[0046] As used herein, the term "terminal device" generally refers to any terminal device capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), end user equipment, subscriber station (SS), unmanned aerial vehicle (UAV), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smartphones, VoIP phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (such as digital cameras), gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop-mounted devices (LMEs), Universal Serial Bus (USB) dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices (e.g., remote surgical equipment), industrial equipment (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics devices, and devices operating on commercial and / or industrial wireless networks. In the following description, the terms "terminal device," "communication device," "terminal," "user equipment," and "UE" may be used interchangeably.

[0047] In 3GPP Rel-17, the characteristics of non-terrestrial networks (NTN) were specified to support the deployment of radio access networks (RAN) on satellites. NTN refers to a network or network segment that uses radio frequency (RF) resources on satellites. Satellites in NTN can be geostationary orbit (GEO) satellites with a fixed position relative to the Earth, or low Earth orbit (LEO) satellites orbiting the Earth.

[0048] NTNs with large coverage areas are well-suited for supporting MBS (Multicast Broadcast Service) to provide services to more UEs with greater resource efficiency. Therefore, the latest 3GPP RAN workshop for Rel-19 coverage proposed supporting MBS in Rel-19 NTNs and explored potential enhancements. For MBS multicast services in NTNs, the following objectives were proposed:

[0049] In Rel-17 and the ongoing Rel-18, MBS and NTN are studied separately; that is, MBS deployment within NTN is not considered, and NTN is not considered for providing MBS services (or only unicast). Specifically, for HARQ operation, MBS introduces HARQ feedback options for multicast services to meet different requirements. In the following description, the terms "multicast service" and "MBS multicast service" are used interchangeably.

[0050] As specified in Rel-17, MBS supports HARQ feedback options for configuring each group of Radio Network Temporary Identifiers (G-RNTI) / group configured Scheduling RNTI (G-CS-RNTI). harq-FeedbackEnablerMulticast Information Elements (IE) and harq-FeedbackOptionMulticast IE. Table 1 shows the HARQ feedback options and corresponding HARQ codebook configurations for multicast transport blocks (TB). Table 1: HARQ feedback options and corresponding HARQ codebook configurations for multicast TB

[0051] harq-FeedbackEnablerMulticast The IE indicates to the UE whether HARQ feedback should be provided for MBS multicast. When used for harq-FeedbackEnablerMulticast IE fields Does not exist At this time, the UE does not provide HARQ feedback for MBS multicast. It is assumed that the UE does not generate HARQ acknowledgment (HARQ-ACK) information associated with the G-RNTI used for multicast, or the G-CS-RNTI with disabled HARQ-ACK information.

[0052] when harq-FeedbackEnablerMulticast IE is configured with the value ' dci-enabler This means that whether the UE should provide HARQ feedback for MBS multicast is indicated by the DCI. As shown in Table 1, if the UE is provided with HARQ-ACK information for multicast... pdsch-HARQ-ACK-Codebook = semi-static Then the UE is not expected to be provided with G-RNTI or G-CS-RNTI set to dci-enabler The value of harq-FeedbackEnablerMulticast .when harq- FeedbackEnablerMulticast IE is configured with the value ' Enable This means that the UE should always provide HARQ feedback for MBS multicast.

[0053] harq-FeedbackOptionMulticast The IE indicator specifies the feedback mode used for MBS multicast. The UE can be configured by... harq- FeedbackOptionMulticast IE configuration, for G-RNTI for multicast or for G-CS-RNTI, to provide HARQ-ACK information for the reception of transport blocks associated with G-RNTI for multicast or G-CS-RNTI, according to a first HARQ-ACK reporting mode or according to a second HARQ-ACK reporting mode.

[0054] when harq-FeedbackOptionMulticast IE is configured with the value ' ack-nack This means that the UE should provide normal HARQ feedback according to the first HARQ-ACK reporting mode. For the indication of the first HARQ-ACK reporting mode ( harq-FeedbackOptionMulticast = ack-nack When the UE correctly decodes the TB, the UE generates a HARQ-ACK message with an ACK value, while when the UE fails to decode the TB correctly, the UE generates a HARQ-ACK message with a negative acknowledgment (NACK) value.

[0055] when harq-FeedbackOptionMulticast IE is configured with the value ' nack-only This means that the UE should only report NACK according to the second HARQ-ACK reporting mode. As shown in Table 1, for those indicated as the second HARQ-ACK reporting mode ( harq-FeedbackOptionMulticast = nack-only For UEs that do not expect to be provided with HARQ-ACK information for multicast, pdsch-HARQ-ACK-Codebook = semi-static .

[0056] The design for HARQ operations in NTN is separate from the design for HARQ operations used in MBS. NTN introduces HARQ feedback to enable HARQ processes to reduce conflicts. As specified in Rel-17, NTN supports configuring HARQ feedback to be enabled per HARQ process. downlinkHARQ-FeedbackDisabled IE. downlinkHARQ- Feedback Disabled IE is optional and is a configuration to enable HARQ feedback for each downlink (DL) HARQ process. The first / leftmost bit corresponds to HARQ process ID 0, the next bit corresponds to HARQ process ID 1, and so on. downlinkHARQ-FeedbackDisabledThe corresponding bit identifier set to one (1) in the bitmap has the corresponding HARQ process with the DL HARQ feedback disabled, and downlinkHARQ-FeedbackDisabled The corresponding bit identifier set to zero (0) in the bitmap is the corresponding HARQ process with enabled DL HARQ feedback.

[0057] Type-1 HARQ-ACK codebook ( pdsch-HARQ-ACK-Codebook = semi-static The NACK bit has a fixed length. When the HARQ-ACK information used for the HARQ process associated with the TB is disabled, the UE reports the NACK value for the HARQ-AK information bits corresponding to the TB in the Type-1 HARQ-ACK codebook and does not consider the TB to have been received. The gNB does not decode the NACK bit.

[0058] When HARQ-ACK information used for the HARQ process associated with TB is disabled, the UE is not in the Type-2 HARQ-ACK codebook. pdsch-HARQ-ACK-Codebook = dynamic The HARQ-ACK information bits corresponding to TB are multiplexed in the )

[0059] Since MBS and NTN are discussed and introduced separately in Rel-17, there may be potential misalignments between the design of HARQ operations for NTN and the design of HARQ operations for MBS when MBS multicast service is provided in NTN.

[0060] In view of the above, embodiments of this disclosure provide a solution for performing HARQ operations for multicast services. In an aspect of this solution, a UE can receive data for multicast services from a base station. The data can be associated with a first configuration. The first configuration can be associated with a mapping between the data and a HARQ process. The UE can determine the HARQ operation associated with the data based on the first configuration. In this way, a scheme for HARQ operations for MBS multicast services can be proposed. The mechanism for mapping data to HARQ processes and thus determining HARQ operations can help avoid potential misalignments in the design of HARQ operations for data and for HARQ processes, thus ensuring a unified solution for HARQ operations that meets the requirements for both multicast services and HARQ processes.

[0061] It should be understood that although this technical problem is introduced with respect to HARQ operations for MBS multicast services in NTN, the scope of this disclosure is not limited in this respect, and embodiments of this disclosure can be applied to HARQ operations for MBS multicast services in other scenarios. Aspects of this disclosure are described in the context of wireless communication systems.

[0062] Figure 1 An example of a wireless communication system 100 supporting HARQ operations for multicast services according to various aspects of this disclosure is illustrated. The wireless communication system 100 may include one or more network entities 102 (also referred to as network devices (NEs)), one or more UEs 104, a core network 106, and a packet data network 108. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communication system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable radio access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support radio access technologies other than 5G. In addition, the wireless communication system 100 can support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0063] One or more network entities 102 may be distributed throughout a geographic area to form a wireless communication system 100. One or more network entities among the network entities 102 described herein may be, include, or may be referred to as network nodes, base stations, network elements, radio access networks (RANs), base transceiver stations, access points, NodeBs, eNodeBs (eNBs), next-generation NodeBs (gNBs), or other suitable terms. Network entities 102 and UE 104 may communicate via communication link 110, which may be a wireless or wired connection. For example, network entities 102 and UE 104 may perform wireless communication (e.g., receive signaling, send signaling) via a Uu interface.

[0064] In an NTN scenario, network entity 102 in satellite form can communicate directly with UE 104 using the NR / LTE Uu interface. The satellite can be a transparent satellite or a regenerated satellite. For an NTN with a transparent satellite, the base station on Earth can communicate with the UE via the satellite. For an NTN with a regenerated satellite, the base station can be onboard and communicate directly with the UE.

[0065] Network entity 102 may provide a geographic coverage area 112 for which network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcasting, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, network entity 102 and UE 104 may support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) based on one or more wireless access technologies. In some implementations, network entity 102 may be mobile, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but different geographic coverage areas 112 may be associated with different network entities 102. The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0066] One or more UEs 104 may be distributed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or be referred to as a mobile device, wireless device, remote device, remote unit, handheld device, or subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, or other examples. Alternatively or additionally, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, or other examples. In some implementations, UE 104 may be stationary within the wireless communication system 100. In some other implementations, UE 104 may be mobile within the wireless communication system 100.

[0067] One or more UEs 104 can be devices of different forms or with different capabilities. Some examples of UEs 104 are shown in... Figure 1 The diagram shows that UE 104 can communicate with various types of devices, such as network entity 102, other UEs 104, or network devices (e.g., core network 106, packet data network 108, relay equipment, integrated access and backhaul (IAB) node, or another network device). Figure 1 As shown. Alternatively or concurrently, UE 104 may support communication with other network entities 102 or UE 104, and may act as a relay in wireless communication system 100.

[0068] UE 104 can also support direct wireless communication with other UE 104s via communication link 114. For example, UE 104 can support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular V2X deployments, communication link 114 may be referred to as a sidelink. For example, UE 104 can support direct wireless communication with another UE 104 via a PC5 interface.

[0069] Network entity 102 may support communication with core network 106, or with another network entity 102, or both. For example, network entity 102 may interface with core network 106 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). Network entities 102 may communicate with each other via backhaul links 116 (e.g., via X2, Xn, or another network interface). In some implementations, network entities 102 may communicate directly with each other (e.g., between network entities 102). In some other implementations, network entities 102 may communicate with each other or indirectly (e.g., via core network 106). In some implementations, one or more network entities 102 may include sub-components, such as access network entities, which may be examples of access node controllers (ANCs). The ANC may communicate with one or more UEs 104 via one or more other access network transport entities (which may be referred to as radio heads, smart radio heads, or transmit-receive points (TRPs)).

[0070] In some implementations, network entity 102 can be configured with a decomposed architecture that can utilize protocol stacks physically or logically distributed across two or more network entities 102, 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, network entity 102 may include one or more of the following: a central unit (CU), a distributed unit (DU), a radio unit (RU), a RAN intelligent controller (RIC) (e.g., a near real-time RIC, a non-real-time RIC), a service management and orchestration (SMO) system, or any combination thereof.

[0071] An RU can also be referred to as a radio head, intelligent radio head, remote radio head (RRH), remote radio unit (RRU), or transmit-receive point (TRP). One or more components of network entity 102 in a decomposed RAN architecture can be co-located, or one or more components of network entity 102 can be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 in a decomposed RAN architecture can be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0072] The functional splitting among CU, DU, and RU can be flexible and can depend on which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof) are executed at the CU, DU, or RU to support different functions. For example, protocol stack functional splitting can be adopted between CU and DU so that CU can support one or more layers of the protocol stack, and DU can support one or more different layers of the protocol stack. In some implementations, CU can host upper-layer protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU can be connected to one or more DU or RU, and one or more DU or RU can host lower-layer protocol layer, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Media Access Control (MAC) layer) functions and signaling, and each can be at least partially controlled by CU 160.

[0073] Alternatively or concurrently, functional splitting of the protocol stack can be employed between the DU and RU, such that the DU can support one or more layers of the protocol stack, and the RU can support one or more different layers of the protocol stack. The DU can support one or more different cells (e.g., via one or more RUs). In some implementations, functional splitting between the CU and DU, or between the DU and RU, can be performed within the protocol layer (e.g., some functions for the protocol layer can be performed by one of the CU, DU, or RU, while other functions of the protocol layer are performed by a different one of the CU, DU, or RU).

[0074] The CU can be further functionally divided into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU can be connected to one or more DUs via midhaul communication links (e.g., F1, F1-c, F1-u), and the DUs can be connected to one or more RUs via fronthaul communication links (e.g., open fronthaul (FH) interfaces). In some implementations, the midhaul or fronthaul communication links can be implemented based on interfaces (e.g., channels) between layers of a protocol stack supported by corresponding network entities 102 communicating via such communication links.

[0075] Core network 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. Core network 106 can be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., a mobility management entity (MME), access and mobility management functions (AMF)) and user plane entities that route packets or interconnections to external networks (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.) for one or more UEs 104 served by one or more network entities 102 associated with core network 106.

[0076] Core network 106 can communicate with packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). Packet data network 108 may include application server 118. In some implementations, one or more UEs 104 may communicate with application server 118. UE 104 may establish a session with core network 106 (e.g., Protocol Data Unit (PDU) session, etc.) via network entity 102. Core network 106 can use the established session (e.g., an established PDU session) to route services (e.g., control information, data, etc.) between UE 104 and application server 118. A PDU session may be an example of a logical connection between UE 104 and core network 106 (e.g., one or more network functions of core network 106).

[0077] In the wireless communication system 100, network entity 102 and UE 104 can use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, network entity 102 and UE 104 can support different resource structures. For example, network entity 102 and UE 104 can support different frame structures. In some implementations, such as in 4G, network entity 102 and UE 104 can support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, network entity 102 and UE 104 can support various frame structures (i.e., multiple frame structures). Network entity 102 and UE 104 can support various frame structures based on parameter sets.

[0078] One or more parameter sets may be supported in the wireless communication system 100, and the parameter sets may include subcarrier spacing and cyclic prefix. The first parameter set (e.g., μ =0) can be associated with the first subcarrier spacing (e.g., 15kHz) and the normal cyclic prefix. In some implementations, the first parameter set (e.g., ) associated with the first subcarrier spacing (e.g., 15kHz) is... μ =0) can utilize one time slot per subframe. The second parameter set (e.g., μ =1) can be associated with the second subcarrier spacing (e.g., 30kHz) and the normal cyclic prefix. The third parameter set (e.g., μ =2) can be associated with the third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. The fourth parameter set (e.g., μ =3) can be associated with the fourth subcarrier spacing (e.g., 120 kHz) and the normal cyclic prefix. The fifth parameter set (e.g., μ =4) can be associated with the fifth subcarrier spacing (e.g., 240 kHz) and the normal cyclic prefix.

[0079] The time intervals of resources (e.g., communication resources) can be organized according to frames (also known as radio frames). Each frame can have a duration, for example, 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0080] Alternatively or concurrently, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more parameter sets supported in the wireless communication system 100. For example, a first parameter set, a second parameter set, a third parameter set, a fourth parameter set, and a fifth parameter set (i.e., ...) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz. μ =0、 μ =1、 μ =2、 μ =3、 μ =4) One time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe can be used respectively. Each time slot can include a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of time slots used for a subframe can depend on the parameter set. For a normal cyclic prefix, a time slot can include 14 symbols. For an extended cyclic prefix (e.g., for a 60kHz subcarrier spacing), a time slot can include 12 symbols. The relationship between the number of symbols per time slot, the number of time slots per subframe, and the number of time slots per frame for both normal and extended cyclic prefixes can depend on the parameter set. It should be understood that for a first parameter set (e.g., quantity) associated with a first subcarrier spacing (e.g., 15kHz), μ The reference of (=0) can be used interchangeably between subframes and time slots.

[0081] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc., based on frequency or wavelength. For example, the wireless communication system 100 can support one or more operating frequency bands, such as frequency range names FR1 (410MHz-7.125GHz), FR2 (24.25GHz-52.6GHz), FR3 (7.125GHz-24.25GHz), FR4 (52.6GHz-114.25GHz), FR4a or FR4-1 (52.6GHz-71GHz), and FR5 (114.25GHz-300GHz). In some implementations, network entity 102 and UE 104 can perform wireless communication through one or more operating frequency bands. In some implementations, FR1 can be used by other devices or apparatuses such as network entity 102 and UE 104 for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by other devices or apparatuses such as network entity 102 and UE 104 for short-range, high data rate capabilities.

[0082] FR1 can be associated with one or more parameter sets (e.g., at least three parameter sets). For example, FR1 can be associated with the following: the first parameter set (e.g., μ =0), which includes a 15kHz subcarrier spacing; the second parameter set (e.g., μ =1), which includes a 30kHz subcarrier spacing; and a third parameter set (e.g., μ =2), which includes a subcarrier spacing of 60 kHz. FR2 can be associated with one or more parameter sets (e.g., at least two parameter sets). For example, FR2 can be associated with the following: a third parameter set (e.g., μ =2), which includes a 60kHz subcarrier spacing; and a fourth parameter set (e.g., μ =3), which includes a subcarrier spacing of 120kHz.

[0083] Figure 2 An example signaling diagram of an example procedure 200 supporting HARQ operations for multicast services according to various aspects of this disclosure is illustrated. For discussion purposes, procedure 200 will refer to... Figure 1 To describe, and process 200 may involve, for example Figure 1 The diagram shows UE 104 and network entity 102. Network entity 102 can also be referred to as base station 102. It should be understood that... Figure 2 The steps and their order are for illustration only and not for limitation. It should be understood that process 200 may also include additional boxes not shown and / or omit some boxes shown, and the scope of this disclosure is not limited in this respect.

[0084] like Figure 2 As shown, base station 102 determines 202 the mapping between data 206 for multicast service and HARQ process, and sends 204 the data 206 associated with a first configuration to UE 104. The first configuration is associated with the mapping. UE 104 receives 208 the data 206 and determines 210 the HARQ operation associated with the data 206 based on the first configuration. In this way, a scheme for HARQ operation for MBS multicast service can be proposed. The mechanism for mapping data and HARQ process and thus determining HARQ operation can help avoid potential misalignments in the design of HARQ operation for data and HARQ process, thus ensuring a unified solution for HARQ operation that meets the requirements of both multicast service and HARQ process.

[0085] Some embodiments of this disclosure will be described in detail below in conjunction with the potential problems to be solved. It should be understood that the embodiments of this disclosure can be applied to other scenarios or situations.

[0086] A first specific aspect of this disclosure is how to map data to a HARQ process. Some embodiments of this disclosure provide a scheme for associating data with a HARQ process.

[0087] In some embodiments, a first HARQ feedback configuration for data may be absent, and a second HARQ feedback configuration for the HARQ process may be disabled. In other words, data with a absent HARQ feedback configuration can be mapped to a HARQ process with a disabled HARQ feedback configuration. For example, data with... harq-FeedbackEnablerMulticast = Does not exist Data can be mapped to have downlinkHARQ-FeedbackDisabled In the bitmap, it is set to =1 (i.e., To enable The corresponding bit of the HARQ process.

[0088] In some embodiments, a first HARQ feedback configuration for data can be enabled, and a second HARQ feedback configuration for the HARQ process can be enabled. In other words, data with an enabled HARQ feedback configuration can be mapped to a HARQ process with an enabled HARQ feedback configuration. For example, having... harq-FeedbackEnablerMulticast = dci- enabler or Enable Data can be mapped to have downlinkHARQ-FeedbackDisabled The bitmap is set to =0 (i.e., Enable The corresponding bit of the HARQ process.

[0089] In some implementations, UE 104 may receive an indication from base station 102 to enable a first HARQ feedback configuration for data via dedicated signaling (e.g., RRC signaling or DCI). In some alternative implementations, UE 104 may receive an indication from base station 102 to enable a first HARQ feedback configuration for data via common signaling (e.g., broadcast or multicast signaling).

[0090] In some implementations, UE 104 may receive from base station 102 an indication to enable or disable a second HARQ feedback configuration for the HARQ process via RRC signaling or in DCI.

[0091] A second specific aspect of this disclosure is whether and how the UE generates HARQ-ACK information, and whether the UE reports HARQ-ACK information when data with a non-existent HARQ feedback configuration is mapped to a HARQ process with a disabled HARQ feedback configuration.

[0092] In some embodiments, when data with a non-existent HARQ feedback configuration is mapped to a HARQ process with a disabled HARQ feedback configuration, UE 104 may skip generating and reporting HARQ-ACK information for the data mapped to the HARQ process. In other words, UE 104 does not generate HARQ-ACK information for HARQ process data, nor does it report HARQ-ACK information for data associated with the HARQ process. For example, when data with a non-existent HARQ feedback configuration is mapped to a HARQ process, UE 104 may skip generating and reporting HARQ-ACK information for the data mapped to the HARQ process. harq-FeedbackEnablerMulticast = Does not exist The data is mapped to have downlinkHARQ-FeedbackDisabled The bitmap is set to =1 (i.e., To enable When the HARQ process for the corresponding bit of ) is in progress, harq-FeedbackEnablerMulticast If not present, HARQ operations can follow the HARQ operation rules used for MBS.

[0093] In some alternative embodiments, when data with a non-existent HARQ feedback configuration is mapped to a HARQ process with a disabled HARQ feedback configuration, if a Type-1 HARQ-ACK codebook is configured for HARQ-ACK information used for the data, UE 104 can generate a negative acknowledgment (NACK) for the HARQ-ACK information and report a NACK for the data mapped to the HARQ process. In other words, if a Type-1 HARQ-ACK codebook is configured (i.e., PDSCH-HARQ- ACK-Codebook yes semi-static If UE 104 always generates HARQ-ACK information as NACK and reports NACK for the multicast TB associated with the HARQ process, then UE 104 will always generate HARQ-ACK information as NACK and report NACK for the multicast TB associated with the HARQ process. For example, when having harq-FeedbackEnablerMulticast = Does not exist The data is mapped to have downlinkHARQ-FeedbackDisabled The bitmap is set to =1 (i.e., Disable When the HARQ process is performed on the corresponding bit of the UE, and if the UE is provided with HARQ-ACK information for multicasting... pdsch-HARQ- ACK-Codebook = Semi-static Then the HARQ operation can follow the rules for having downlinkHARQ-FeedbackDisabled The HARQ operation rules for NTN with corresponding bit = 1 in the bitmap.

[0094] In some implementations, multicast services are associated with the NTN. For example, base station 102 may be located on or communicate with UE 104 via a satellite. A third specific aspect of this disclosure is how the DL HARQ round-trip time (RTT) timer for PTM is handled when data with an enabled HARQ feedback configuration is mapped to a HARQ process with an enabled HARQ feedback configuration. The DL HARQ RTT timer for PTM (e.g., drx-HARQ-RTT-TimerDL-PTM This is used to determine the duration during which DL retransmissions for multicast are not expected. In other words, while the timer is running, the UE does not need to monitor possible multicast retransmissions for the corresponding HARQ process. In NTNs where the RTT can be tens or hundreds of milliseconds, DL retransmissions for multicast are not expected during the RTT duration, and therefore the duration of the DL HARQ RTT timer for PTM in the NTN should also take into account the RTT duration.

[0095] In some embodiments, when data with an enabled HARQ feedback configuration is mapped to a HARQ process with an enabled HARQ feedback configuration, UE 104 may send HARQ-ACK information to base station 102 indicating a request for retransmission of the data, and monitor retransmissions multicast from base station 102 after a first duration following the transmission of the HARQ-ACK information. The first duration may be associated with the RTT value between UE 104 and base station 102.

[0096] In some implementations, the first duration can be based on a first HARQ-RTT timer, the duration of which corresponds to the sum of the duration of a second HARQ-RTT timer for point-to-multipoint (PTM) services in the terrestrial network and the RTT value. The first HARQ-RTT timer can be associated with the duration for skipping multicast retransmissions of data used for multicast services in the NTN.

[0097] For example, parameters HARQ-RTT-TimerDL-NTN-PTM This can be set and defined as the minimum duration before the DL allocation for HARQ retransmission is expected by the MAC entity for PTM service in NTN. The first duration can be determined by parameters used for the corresponding HARQ process. HARQ-RTT-TimerDL-NTN-PTM Configure it. Parameters used for the corresponding HARQ process. HARQ-RTT-TimerDL-NTN-PTM It can be equal to drx-HARQ-RTT-TimerDL-PTM Add the UE-gNB RTT value. Parameter drx-HARQ-RTT-TimerDL-PTM This is the minimum duration before the DL allocation for HARQ retransmission is expected by the MAC entity for PTM service in the terrestrial network. It should be understood that the parameter... HARQ-RTT-TimerDL-NTN-PTM This is for illustrative purposes only; other parameters may be applied.

[0098] In some implementations, the first duration can be based on a second HARQ-RTT timer, the duration of which is extended by the RTT value. For example, the first duration can be determined by parameters used for the corresponding HARQ process. drx- HARQ-RTT-TimerDL-PTM The duration can be extended by increasing the UE-gNB RTT value.

[0099] In some implementations, the first duration can be based on a second HARQ-RTT timer, the duration of which corresponds to the duration of a third HARQ-RTT timer used for point-to-point (PTP) services in the NTN. For example, the first duration can be determined by parameters used for the corresponding HARQ process. drx-HARQ-RTT-TimerDL-PTM To configure, if the same value is configured as HARQ-RTT-TimerDL and HARQ-RTT-TimerDL-PTM Then its duration can be extended to the parameter. HARQ-RTT-TimerDL-NTN The value of the parameter. HARQ-RTT-TimerDL-NTN This is the minimum duration before the DL allocation for HARQ retransmission is expected by the MAC entity for PTP service in NTN. Parameter HARQ-RTT-TimerDL This is the minimum duration before the DL allocation for HARQ retransmission is expected by the MAC entity for PTP service in the terrestrial network. Parameter HARQ-RTT-TimerDL-PTM It is the minimum duration before the DL allocation for HARQ retransmission is expected by the MAC entity for PTM service in NTN.

[0100] In some implementations, the multicast service is associated with the NTN. For example, base station 102 may be located on a satellite or communicate with UE 104 via a satellite. A fourth specific aspect of this disclosure is how the DL HARQ RTT timer for PTP is handled when data for multicast service with an enabled HARQ feedback configuration is mapped to a HARQ process with an enabled HARQ feedback configuration. The DL HARQ RTT timer for PTP (e.g., drx-HARQ-RTT-TimerDL ) is used to determine the duration for which DL retransmissions for unicast are not expected. For multicast services, when the normal HARQ feedback pattern (i.e., harq- FeedbackOptionMulticast = ack-nack When configured and used, DL retransmissions for multicast can be delivered via unicast, and therefore the DL HARQ RTT timer for PTP in NTN can be started. If this occurs in NTN, the duration of the DL HARQ RTT timer for PTP in NTN should also take into account the RTT duration.

[0101] In some embodiments, when data with an enabled HARQ feedback configuration is mapped to a HARQ process with an enabled HARQ feedback configuration, UE 104 may send HARQ-ACK information to base station 102 in ACK-NACK feedback mode. If the HARQ-ACK information can indicate a request for retransmission of data, UE 104 may monitor unicast retransmissions from base station 102 after a second duration following the transmission of the HARQ-ACK information. The second duration may be associated with the RTT value between UE 104 and base station 102.

[0102] In some implementations, the second duration can be based on a fifth HARQ-RTT timer, the duration of which corresponds to the sum of the fourth HARQ-RTT timer and the RTT value used for PTP services in the terrestrial network. The fifth HARQ-RTT timer can be associated with the duration used to skip monitoring retransmissions of data used for unicast services in the NTN.

[0103] For example, the second duration can be determined by parameters used in the corresponding HARQ process. HARQ-RTT-TimerDL-NTN- PTP Configure it. Parameters used for the corresponding HARQ process. HARQ-RTT-TimerDL-NTN-PTP It can be equal to drx-HARQ- RTT-TimerDL Add the UE-gNB RTT value. Parameter drx-HARARARARQ-RTT-TimerDL This is the minimum duration prior to the DL allocation for HARQ retransmission, which the MAC entity anticipates for PTP service on the terrestrial network. It should be understood that the parameter... HARQ-RTT- TimerDL-NTN-PTP This is for illustrative purposes only; other parameters may be applied.

[0104] In some implementations, the second duration can be based on a sixth HARQ-RTT timer, the duration of which corresponds to the duration of a third HARQ-RTT timer used for PTP services in the NTN. The sixth HARQ-RTT timer can be associated with the duration used to skip monitoring retransmissions of data used for unicast services in the NTN.

[0105] For example, the second duration can be determined by parameters used in the corresponding HARQ process. HARQ-RTT-TimerDL-NTN- PTP Configure it. Parameters used for the corresponding HARQ process. HARQ-RTT-TimerDL-NTN-PTP It can be equal to HARQ-RTT- TimerDL-NTN The value of the parameter. HARQ-RTT-TimerDL-NTN This is the minimum duration before the DL allocation for HARQ retransmission is expected by the MAC entity for PTP service in NTN. It should be understood that the parameter... HARQ-RTT-TimerDL-NTN-PTPThis is for illustrative purposes only; other parameters may be applied.

[0106] In some implementations, the second duration can be based on a third HARQ-RTT timer used for PTP services in NTN. For example, parameters HARQ-RTT-TimerDL-NTN This parameter can be used in the corresponding HARQ process and has an equal to drx- HARQ-RTT-TimerDL Add the UE-gNB RTT value.

[0107] The fifth specific aspect of this disclosure is whether and when data with an enabled HARQ feedback configuration can be mapped to a HARQ process with an enabled HARQ feedback configuration. As specified for MBS in Rel-17, multicast TBs configured with only NACK HARQ feedback (i.e., harq-FeedbackOptionMulticast = nack-only It is not expected to have a Type-1 HARQ-ACK codebook (i.e., pdsch-HARQ-ACK-Codebook = Semi-static Additionally, as specified in Rel-17 for NTN, when HARQ-ACK messages used for the HARQ process associated with TB are disabled ( downlinkHARQ- FeedbackDisabled The corresponding bit in the bitmap is 1, that is, Disable ), UE in Type-1 HARQ-ACK codebook (i.e., pdsch-HARQ-ACK-Codebook = Semi-static The NACK value for the HARQ-ACK information bits corresponding to the TB is reported in the Type-1 HARQ-ACK codebook. In future versions, if the Type-1 HARQ-ACK codebook (i.e., pdsch-HARQ-ACK-Codebook = Semi-static It is possible to provide only NACK HARQ feedback (i.e., harq-FeedbackOptionMulticast = nack-only Then, by utilizing the UE's NACK report, the corresponding multicast TB is linked to the HARQ process that was disabled in the NTN due to the HARQ feedback being disabled. downlinkHARQ-FeedbackDisabled The corresponding bit in the bitmap is 1, that is, Disable This allows for the efficient utilization of opportunities associated with HARQ, and thus the efficient use of HARQ processes that are deactivated in response to HARQ feedback.

[0108] In some embodiments, a first HARQ feedback configuration for data can be enabled, a NACK-only feedback mode can be configured for data, a first type of HARQ-ACK codebook can be configured for HARQ-ACK information used for data, and a second HARQ feedback configuration for the HARQ process can be disabled. In other words, if the NACK-only feedback mode is configured for data and the first type of HARQ-ACK codebook is configured, data with the enabled HARQ feedback configuration can be mapped to a HARQ process with the disabled HARQ feedback configuration. For example, if the UE is provided with multicast HARQ-ACK information. pdsch-HARQ-ACK-Codebook = Semi-static And only NACK HARQ feedback is configured for data (i.e., harq-FeedbackOptionMulticast = nack-only ), then it has harq-FeedbackEnablerMulticast = dci-enabler or Enable Data can be mapped to have downlinkHARQ-FeedbackDisabled =1 in the bitmap (i.e., To enable The corresponding bit of the HARQ process.

[0109] In some implementations, UE 104 may receive an indication from base station 102 to enable a first HARQ feedback configuration for data via dedicated signaling (e.g., RRC signaling or DCI). In some alternative implementations, UE 104 may receive an indication from base station 102 to enable a first HARQ feedback configuration for data via common signaling (e.g., broadcast or multicast signaling).

[0110] In some implementations, UE 104 may receive from base station 102 an indication to enable or disable a second HARQ feedback configuration for the HARQ process via RRC signaling or in DCI.

[0111] When data with an enabled HARQ feedback configuration is mapped to a HARQ process with a disabled HARQ feedback configuration, if the data is not correctly decoded, UE 104 can generate a NACK for the HARQ-ACK information and send a NACK to base station 102 indicating a request for data retransmission. Base station 102 can receive the NACK from UE 104 for the data in the HARQ-ACK information, decode the NACK, and send a retransmission of the data to UE 104.

[0112] In some implementations, multicast service is associated with NTN. For example, base station 102 may be located on or communicate with UE 104 via a satellite. UE 104 may monitor retransmissions multicast from base station 102 after a third duration following the transmission of NACK. The third duration may be associated with the RTT value between UE 104 and base station 102.

[0113] In some embodiments, the third duration may be based on a first HARQ-RTT timer, the duration of which corresponds to the sum of the duration of a second HARQ-RTT timer for point-to-multipoint (PTM) services in the terrestrial network and the RTT value. The first HARQ-RTT timer may be associated with a duration for skipping multicast retransmissions of data used to monitor multicast services in the NTN.

[0114] For example, parameters HARQ-RTT-TimerDL-NTN-PTM This can be set and defined as the minimum duration before the DL allocation for HARQ retransmission is expected by the MAC entity for PTM service in NTN. A third duration can be specified by parameters used for the corresponding HARQ process. HARQ-RTT-TimerDL-NTN-PTM Configure it. Parameters used for the corresponding HARQ process. HARQ-RTT-TimerDL-NTN-PTM It can be equal to drx-HARQ-RTT-TimerDL-PTM Add the UE-gNB RTT value. Parameter drx-HARQ-RTT-TimerDL-PTM This is the minimum duration before the DL allocation for HARQ retransmission is expected by the MAC entity for PTM service in the terrestrial network. It should be understood that the parameter... HARQ-RTT-TimerDL-NTN-PTM This is for illustrative purposes only; other parameters may be applied.

[0115] In some implementations, the third duration can be based on the second HARQ-RTT timer, whose duration is extended by the RTT value. For example, the third duration can be determined by parameters used for the corresponding HARQ process. drx- HARQ-RTT-TimerDL-PTM The duration can be extended by increasing the UE-gNB RTT value.

[0116] In some implementations, the third duration can be based on the second HARQ-RTT timer, the duration of which corresponds to the duration of the third HARQ-RTT timer used for point-to-point (PTP) services in the NTN. For example, the third duration can be determined by parameters used for the corresponding HARQ process. drx-HARQ-RTT-TimerDL-PTM To configure, if the same value is configured as HARQ-RTT-TimerDL and HARQ-RTT-TimerDL-PTM Then its duration can be extended to the parameter. HARQ-RTT-TimerDL-NTN The value of the parameter. HARQ-RTT-TimerDL-NTNThis is the minimum duration before the DL allocation for HARQ retransmission is expected by the MAC entity for PTP service in NTN. Parameter HARQ-RTT-TimerDL This is the minimum duration before the DL allocation for HARQ retransmission is expected by the MAC entity for PTP service in the terrestrial network. Parameter HARQ-RTT-TimerDL-PTM It is the minimum duration before the DL allocation for HARQ retransmission is expected by the MAC entity for PTM service in the terrestrial network.

[0117] Figure 3 An example procedure 300 supporting HARQ operations for multicast services according to various aspects of this disclosure is illustrated. For discussion purposes, the communication procedure 300 will be referenced. Figure 1 To describe. It should be understood that although the communication process 300 has been referenced Figure 1 While the network environment 100 is used to describe this, the communication process 300 can also be applied to other similar communication scenarios. The communication process 300 can be considered as... Figure 2 A specific example implementation of process 200. Process 300 may involve, for example... Figure 1 The UE 104 shown is served by the base station 102. The base station 102 can also be referred to as the serving BS.

[0118] like Figure 3 As shown, at point 302, base station 102 can be determined to be configured with / without. harq- FeedbackEnablerMulticast / harq-FeedbackOptionMulticast Multicast TB and configured with downlinkHARQ-FeedbackDisabled The association between the multicast TB and HARQ processes. The terms "association between multicast TB and HARQ processes" and "mapping between multicast TB and HARQ processes" are used interchangeably. In some embodiments, the association between the multicast TB and HARQ processes can be determined based on the three types of associations shown in Table 2. Table 2: Correlation between Multicast TB and HARQ processes in NTN

[0119] In association #1, no configuration is provided. harq-FeedbackEnablerMulticast (Right now, harq- FeedbackEnablerMulticast = Does not exist The G-RNTI / G-CS-RNTI multicast TB can be configured with downlinkHARQ-FeedbackDisabled =1 in the bitmap (i.e., To enable The HARQ process is associated with the corresponding bit of ). Association #1 is independent of the type of HARQ-ACK codebook configured (i.e., PDSCH-HARQ-ACK-Codebook = Half static or dynamic In other words, for association #1, two types of HARQ-ACK codebooks can be configured (i.e., PDSCH-HARQ- ACK-Codebook yes semi-static or dynamic ).

[0120] In association #2, it is configured with harq-FeedbackEnablerMulticast G-RNTI / G-CS-RNTI multicast TB (i.e., harq-FeedbackEnablerMulticast = dci-enabler And the corresponding enabled DCI is received, or harq-FeedbackEnablerMulticast = Enable It can be at least configured with downlinkHARQ- Feedback Disabled =0 in the bitmap (i.e., Enable The HARQ process is associated with the corresponding bit of ). Association #2 is independent of which HARQ-ACK mode is configured (i.e., harq-FeedbackOptionMulticast It can be ack-nack or nack-only Association #2 is independent of the type of HARQ-ACK codebook configured (i.e., PDSCH-HARQ-ACK- Codebook = semi-static or dynamic In other words, for association #2, two types of HARQ-ACK codebooks can be configured (i.e., PDSCH-HARQ-ACK-Codebook yes semi-static or dynamic ), and both types of HARQ-ACK modes can be configured (i.e., harq-FeedbackOptionMulticast for ack-nack or nack-only ).

[0121] In association #3, it is configured with harq-FeedbackEnablerMulticast (Right now, harq- FeedbackEnablerMulticast = dci-enabler And the corresponding enabled DCI is received, or harq- FeedbackEnablerMulticast = Enable HARQ-ACK mode with only NACK (i.e., harq- FeedbackOptionMulticast = nack-only ) and the Type-1 HARQ-ACK codebook (i.e., PDSCH-HARQ-ACK- Codebook = Semi-static The G-RNTI / G-CS-RNTI multicast TB can be configured with downlinkHARQ- FeedbackDisabled =1 in the bitmap (i.e.,Disable The corresponding bit of the HARQ process is associated with the UE 104. If association #3 is applied, base station 102 should process the NACK reported by UE 104 in the Type-1 HARQ codebook.

[0122] At position 304, base station 102 can send each G-RNTI / G-CS-RNTI to UE 104. harq- FeedbackEnablerMulticast and harq-FeedbackOptionMulticast The configuration. At 306, base station 102 can send the configuration for each HARQ process to UE 104. downlinkHARQ-FeedbackDisabled Configuration. At 308, base station 102 can send a multicast TB associated with the determined HARQ process to UE 104.

[0123] UE 104 can receive a multicast TB associated with a determined HARQ process and determine the HARQ operation for the multicast TB based on the association between the multicast TB and the HARQ process.

[0124] At 310, UE 104 can process the generation and reporting of HARQ-ACK information for multicast TB based on the determined association. For example, if multicast TB application association #1, UE 104 may not generate HARQ-ACK information and may not report HARQ-ACK information for multicast TB associated with the HARQ process. Alternatively, if multicast TB application association #1, UE 104 may generate HARQ-ACK information as NACK, and if a Type-1 HARQ-ACK codebook is configured (i.e., PDSCH-HARQ- ACK-Codebook yes Semi-static If the multicast TB is associated with the HARQ process, then the NACK for the multicast TB will be reported. In another example, if the multicast TB application is associated with #3, then UE 104 can generate HARQ-ACK information (ACK and NACK) normally and only report the NACK for the multicast TB associated with the HARQ process.

[0125] At 312, UE 104 can process the HARQ process associated with the multicast TB based on the determined association. drx-HARQ-RTT-TimerDL-PTM For example, if a multicast TB application is associated with #2 or #3, then drx-HARQ-RTT- TimerDL-PTM The duration can be extended by the UE-gNB RTT value. In one example implementation, UE 104 can set a timer for the corresponding HARQ process. HARQ-RTT-TimerDL-NTN-PTM Its duration is equal to drx-HARQ-RTT- TimerDL-PTMAdd the UE-gNB RTT value. In another example implementation, it is used for the corresponding HARQ process. drx-HARQ- RTT-TimerDL-PTM The duration can be extended by adding the UE-gNB RTT value. In another example implementation, if the same value is configured as... HARQ-RTT-TimerDL and HARQ-RTT-TimerDL-PTM Then it is used for the corresponding HARQ process. drx-HARQ-RTT-TimerDL-PTM The duration can be extended to HARQ-RTT-TimerDL-NTN The value of .

[0126] At 314, UE 104 can process the HARQ process associated with the multicast TB based on the determined association. drx-HARQ-RTT-TimerDL For example, if a multicast TB application is associated with #2, and in normal HARQ feedback mode (i.e., harq-FeedbackOptionMulticast = ack-nack When configured and used, drx-HARQ-RTT-TimerDL The duration can be extended by the UE-gNB RTT value. In one example implementation, UE 104 can set a timer for the corresponding HARQ process. HARQ-RTT-TimerDL-NTN-PTP It has equal to drx-HARQ-RTT-TimerDL Add the UE-gNBRTT value, or equal to the value HARQ-RTT-TimerDL-NTN The duration. In another example implementation, UE 104 can use the duration for the corresponding HARQ process. HARQ-RTT-TimerDL-NTN HARQ process, which has equal to drx-HARQ-RTT- TimerDL Add the UE-gNB RTT value.

[0127] According to some embodiments of this disclosure, some potential problems in supporting HARQ operations for multicast services in NTN can be solved. Specifically, some embodiments of this disclosure address potential problems in supporting HARQ operations for MBS multicast services in NTN scenarios, focusing on the relationship between multicast TBs configured with different HARQ feedback options and NTN HARQ processes configured with different HARQ feedbacks to enable them. As mentioned above, in Rel-17, MBS and NTN are studied separately. The HARQ configuration for MBS per G-RNTI / G-CS-RNTI does not take into account the situation in NTN, for example, when the HARQ process is configured with downlinkHARQ-FeedbackDisabledIn this case, how to specify the association between the TB and the HARQ process, and how to determine the UE's behavior when generating and reporting HARQ-ACK information. Furthermore, the de-enabling configuration in the NTN for each HARQ process does not consider the situation in the MBS. For example, when the multicast TB used for G-RNTI / G-CS-RNTI is configured with different HARQ feedback options and codebooks, how to specify the association between the TB and the HARQ process, and how to determine the UE's behavior when generating and reporting HARQ-ACK information. Additionally, in Rel-17 NTN, the NTN HARQ RTT timer processing only considers the unicast case, that is, "the timer used for the corresponding HARQ process..." HARQ-RTT-TimerDL-NTN Set to equal to drx-HARQ-RTT-TimerDL The operation of adding the latest available UE-gNB RTT value only applies to the case where UE-specific DRX is configured, and not to the case where multicast DRX is configured.

[0128] For example, when MBS multicast service is provided in NTN, different HARQ feedback options are configured (e.g., harq-FeedbackEnablerMulticast / harq-FeedbackOptionMulticast The multicast TB and the configuration with different HARQ feedback configurations (e.g., configured with or without) downlinkHARQ-FeedbackDisabled The relationships between HARQ processes need to be determined, for example, considering the different types of processes. pdsch-HARQ-ACK-Codebook And the corresponding UE behavior restrictions. In the example solution, the association between the multicast TB and HARQ processes in the NTN can be designed as associations #1, #2, and #3 as shown in Table 2. In this way, it is configured with / without harq-FeedbackEnablerMulticast / harq-FeedbackOptionMulticast Multicast TB and configured with downlinkHARQ-FeedbackDisabled The relationships between HARQ processes are designed. Table 3 also illustrates some potential sub-problems addressed by some embodiments of this disclosure. Table 3: Potential sub-problems regarding the relationship between multicast TB and HARQ processes in NTN

[0129] Issue #1a concerns multicast TB that is disabled in response to HARQ feedback. harq- FeedbackEnablerMulticast for Does not exist ) and HARQ processes that are deenabled in response to HARQ feedback ( downlinkHARQ-FeedbackDisabled When the corresponding bit in the bitmap is associated with deactivation, it determines whether and how the UE generates HARQ-ACK information, and whether the UE reports HARQ-ACK information. In Rel-17 MBS, for multicast TBs deactivated in response to HARQ feedback (harq-FeedbackEnablerMulticast (Not present), assuming the UE does not generate HARQ-ACK information associated with a G-RNTI used for multicast or a G-CS-RNTI with disabled HARQ-ACK information. However, in Rel-17 NTN, it is assumed the UE generates HARQ-ACK information regardless of whether the PDSCH reception is as described. downlinkHARQ- Feedback Disabled The indicated TB is provided for the HARQ process with deenabled HARQ-ACK information. If both configurations exist, it is uncertain whether the UE should generate HARQ-ACK information. If so, it is uncertain whether the UE should use the Type-1 HARQ-ACK codebook ( pdsch-HARQ-ACK-Codebook = Semi-static The report in the document is the NACK value used for the HARQ-ACK information bits.

[0130] In the example embodiment, in the case of association #1, the UE processing of HARQ-ACK information generation and reporting can follow the rules for MBS (i.e., for when harq-Feedback Enabler Multicast (If it does not exist). In other words, in the case of association #1, the UE does not generate HARQ-ACK information for these multicast TBs, nor does it report HARQ-ACK information for these multicast TBs associated with the HARQ process.

[0131] In another example embodiment, in the case of association #1, the UE processing of HARQ-ACK information generation and reporting can follow the rules for NTN (i.e., for when...). downlink HARQ-Feedback Disabled When the corresponding bit in the bitmap is 1). In other words, in the case of association #1, if the Type-1 HARQ-ACK codebook is configured (i.e., PDSCH-HARQ- ACK-Codebook yes Semi-static If the UE always generates HARQ-ACK information as NACK, it will also report NACK for the multicast TB associated with the HARQ process.

[0132] In this way, based on the designed association #1, the option for the UE to generate and report HARQ-ACK information is proposed when HARQ feedback for multicast service and HARQ process is disabled.

[0133] Question 1b concerns multicast TBs enabled in response to HARQ feedback ( harq- Feedback Enabler Multicast for dci-enabler And the corresponding enabling DCI is received or enabled) and the HARQ process is deenabled in response to HARQ feedback ( downlink HARQ-Feedback DisabledWhen the corresponding bit in the bitmap is enabled, how is the DL HARQ RTT timer for PTM handled? The DL HARQ RTT timer for PTM (e.g., ...) drx-HARQ-RTT-TimerDL-PTM This is used to determine the duration during which DL retransmissions for multicast are not expected; that is, when the timer is running, the UE does not need to monitor possible retransmissions for the corresponding HARQ process. In NTNs where the RTT can be tens or hundreds of milliseconds, DL retransmissions for multicast are not expected during the RTT duration, and therefore the duration of the DL HARQ RTT timer for PTM in the NTN should also take the RTT into account.

[0134] In some embodiments, in the case of association #2, the following two conditions are met. drx-HARQ-RTT- TimerDL-PTM UE processing can be applied to: (1) G-RNTI / G-CS-RNTI multicast TB is configured with harq- Feedback Enabler Multicast (Right now, harq-Feedback Enabler Multicast for dci-enabler (and the corresponding enabled DCI is received or enabled); and (2) the multicast TB of G-RNTI / G-CS-RNTI and the configured downlink HARQ-Feedback Disabled =0 in the bitmap (i.e., Enable The corresponding bit of the HARQ process is associated with the process.

[0135] drx-HARQ-RTT-TimerDL-PTM The duration can be extended through alternative timer behaviors. For example, a timer for the corresponding HARQ process. HARQ-RTT-TimerDL-NTN-PTM It can be equal to drx-HARQ- RTT-TimerDL-PTM Add the duration of the UE-gNB RTT value to the setting.

[0136] Alternative sites drx-HARQ-RTT-TimerDL-PTM The duration can be extended through modified timer behavior. For example, for the corresponding HARQ process. drx-HARQ-RTT-TimerDL-PTM The duration can be extended by increasing the UE-gNB RTT value. In another example implementation, if the same value is configured as... HARQ-RTT- TimerDL and HARQ-RTT-TimerDL-PTM Then it is used for the corresponding HARQ process. drx-HARQ-RTT-TimerDL-PTM The duration can be extended to HARQ-RTT-TimerDL-NTN The value of .

[0137] In this way, based on the designed association #2, when HARQ feedback for multicast service and HARQ process is enabled, options for UE processing of HARQ RTT timers for retransmissions via multicast are proposed.

[0138] Issue #1c concerns multicast TB enabled in response to normal HARQ feedback ( harq- Feedback Enabler Multicast for dci-enabler And the corresponding enabled DCI is received or is Enable ,and harq-Feedback Option Multicast for ack-nack ) and HARQ processes enabled for HARQ feedback ( downlink HARQ-Feedback Disabled When the corresponding bit in the bitmap is enabled, how should the DL HARQ RTT timer used for PTP be handled? Similar to Question 1b, the DL HARQ RTT timer used for PTP (i.e., drx-HARQ- RTT-TimerDL ) is used to determine the duration during which unicast DL retransmission is not expected. In multicast, when normal HARQ feedback ( harq-Feedback Option Multicast for ack-nack When configured and used, DL retransmissions for multicast can be delivered via unicast, and therefore drx-HARQ-RTT-TimerDL It can be started. If this occurs in NTN, the duration of the DL HARQ RTT timer used for PTP should also take RTT into account.

[0139] In some embodiments, the association #2 case is confirmed when the following three conditions are met. drx-HARQ-RTT- TimerDL UE processing can be applied to: (1) G-RNTI / G-CS-RNTI multicast TB is configured with harq- Feedback Enabler Multicast (Right now, harq-Feedback Enabler Multicast for dci-enabler And the corresponding enabled DCI is received or is Enable (2) G-RNTI / G-CS-RNTI multicast TB and configured with downlink HARQ- Feedback Disabled =0 in the bitmap (i.e., Enable The corresponding bits of the HARQ process are associated with (3) the multicast TB of G-RNTI / G-CS-RNTI is configured with normal HARQ-ACK mode as normal ACK-NACK (i.e., harq- Feedback Option Multicast for ack-nack ).

[0140] drx-HARQ-RTT-TimerDL The duration can be extended through alternative timer behaviors. In the example embodiment, a timer is used for the corresponding HARQ process. HARQ-RTT-TimerDL-NTN-PTP It can be equal to drx- HARQ-RTT-TimerDLAdd the UE-gNB RTT value, or equal to of HARQ-RTT-TimerDL-NTN The value is set based on its duration.

[0141] Alternative sites drx-HARQ-RTT-TimerDL The duration can be extended through modified timer behavior. For example, the UE can use the timer behavior for the corresponding HARQ process. HARQ-RTT-TimerDL-NTN It has equal to drx- HARQ-RTT-TimerDL Add the HARQ process value to the UE-gNB RTT value.

[0142] In this way, based on the designed association #2, when HARQ feedback for multicast services and HARQ processes is enabled, options for UE processing of the HARQ RTT timer for retransmissions via unicast are proposed.

[0143] Question #1d concerns when multicast TB is enabled for only NACK HARQ feedback ( harq- FeedbackEnablerMulticast for dci-enabler And the corresponding enabled DCI is received or is Enable ,and harq-FeedbackOptionMulticast for nack-only It can be used with HARQ processes that are disabled in response to HARQ feedback. downlinkHARQ-FeedbackDisabled The corresponding bit in the bitmap is associated with de-enabling, and how HARQ operation is performed in this case. In Rel-17 MBS, multicast TBs configured with only NACK HARQ feedback ( harq- FeedbackOptionMulticast for nack-only Not applicable to Type-1 HARQ-ACK codebooks ( semi-static In Rel-17 NTN, when the HARQ-ACK message used for the HARQ process associated with the TB is deactivated ( downlinkHARQ- Feedback Disabled When the corresponding bit in the bitmap is deenabled, the UE in the Type-1 HARQ-ACK codebook ( Semi-quiet state The NACK value for the HARQ-AK information bits corresponding to the TB is reported in the Type-1 HARQ-ACK codebook. In future versions, if the Type-1 HARQ-ACK codebook ( semi-static ) For NACK HARQ feedback only ( harq-FeedbackOptionMulticast for nack-only If it is possible, then there exists a way to leverage the UE's NACK report to disable the corresponding multicast TB and the HARQ process that was disabled in the NTN by using the HARQ feedback that was disabled in the NTN. downlinkHARQ-FeedbackDisabledThe corresponding bit in the bitmap is associated with de-enable, and thus the opportunity to efficiently utilize the de-enable opportunity of HARQ processes that are de-enabled in response to HARQ feedback is taken into account.

[0144] As defined in association #3, when the Type-1 HARQ-ACK codebook (i.e., PDSCH-HARQ-ACK-Codebook = semi-static When configured, it is configured with harq-FeedbackEnablerMulticast (Right now, harq- FeedbackEnablerMulticast = dci-enabler And the corresponding enabled DCI is received, or harq- FeedbackEnablerMulticast = Enable ) and HARQ-ACK mode is NACK only (i.e., harq- FeedbackOptionMulticast = nack-only The HARQ process G-RNTI / G-CS-RNTI's multicast TB can communicate with the configured... downlinkHARQ-FeedbackDisabled =1 in the bitmap (i.e., To enable The corresponding bit of the HARQ process is associated with the process.

[0145] In an example embodiment, the UE can generate HARQ-ACK information (ACK and NACK) in normal mode and only report NACKs for multicast TBs associated with the HARQ process. The reported NACKs should be processed by the gNB to understand the failure of TB delivery.

[0146] In some embodiments, the association #3 case is confirmed when the following four conditions are met. drx-HARQ-RTT- TimerDL UE processing can be applied to: (1) G-RNTI / G-CS-RNTI multicast TB is configured with harq- FeedbackEnablerMulticast (Right now, harq-FeedbackEnablerMulticast for dci-enabler And the corresponding enabled DCI is received or is Enable (2) The multicast TB of G-RNTI / G-CS-RNTI is configured with normal HARQ-ACK mode for NACK only (i.e., harq-FeedbackOptionMulticast for nack-only (3) The Type-1 HARQ-ACK codebook is configured (i.e., PDSCH-HARQ-ACK-Codebook for semi-static ); and (4) G-RNTI / G-CS-RNTI multicast TB and configured with downlinkHARQ-FeedbackDisabled =1 in the bitmap (i.e., To enable The corresponding bit of the HARQ process is associated with the process.

[0147] drx-HARQ-RTT-TimerDL-PTMThe duration can be extended through alternative timer behaviors. For example, a timer for the corresponding HARQ process. HARQ-RTT-TimerDL-NTN-PTM It can be equal to drx-HARQ- RTT-TimerDL-PTM Add the duration of the UE-gNB RTT value to the setting.

[0148] Alternative sites drx-HARQ-RTT-TimerDL-PTM The duration can be extended through modified timer behavior. For example, for the corresponding HARQ process. drx-HARQ-RTT-TimerDL-PTM The duration can be extended by increasing the UE-gNB RTT value. In another example implementation, if the same value is configured as... HARQ-RTT- TimerDL and HARQ-RTT-TimerDL-PTM Then it is used for the corresponding HARQ process. drx-HARQ-RTT-TimerDL-PTM The duration can be extended to HARQ-RTT-TimerDL-NTN The value of .

[0149] In this way, based on the designed association #3, when only NACK HARQ feedback for multicast services is enabled, an additional option is proposed to allow association with a HARQ process that has de-enabled HARQ feedback to report only NACK.

[0150] To address the aforementioned issues, some embodiments of this disclosure propose a series of solutions to determine the association and design corresponding to UE behavior and base station behavior, thereby ensuring a unified solution for HARQ operations in multicast NTN that meets the requirements for both multicast services and HARQ processes, and thus efficiently utilizing a limited number of HARQ processes with a large RTT in NTN.

[0151] Figure 4 An example of a device 400 supporting HARQ operations for multicast services according to various aspects of this disclosure is illustrated. Device 400 may be an example of a UE 104 as described herein. Device 400 may support wireless communication with one or more network entities 102, UE 104, or any combination thereof. Device 400 may include components for bidirectional communication, including components for transmitting and receiving communications, such as processor 402, memory 404, transceiver 406, and optional I / O controller 408. These components may communicate electronically or be otherwise coupled (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., bus).

[0152] Processor 402, memory 404, transceiver 406, or various combinations thereof or various components thereof may be examples of components used to perform various aspects of the present disclosure described herein. For example, processor 402, memory 404, transceiver 406, or various combinations thereof or components thereof may support methods for performing one or more of the operations described herein.

[0153] In some implementations, processor 402, memory 404, transceiver 406, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise supporting components for performing the functions described in this disclosure. In some implementations, processor 402 and memory 404 coupled to processor 402 may be configured to perform one or more of the functions described herein (e.g., instructions stored in memory 404 are executed by processor 402).

[0154] For example, according to the examples disclosed herein, processor 402 may support wireless communication at device 400. Processor 402 may be configured to operate to support: components for receiving data from a base station for multicast services, wherein the data is associated with a first configuration and the first configuration is associated with a mapping between the data and a Hybrid Automatic Repeat Request (HARQ) process; and components for determining HARQ operations associated with the data based on the first configuration.

[0155] Processor 402 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, processor 402 may be configured to use a memory controller to operate a memory array. In some other implementations, the memory controller may be integrated into processor 402. Processor 402 may be configured to execute computer-readable instructions stored in memory (e.g., memory 404) to cause device 400 to perform various functions of this disclosure, enabling device 400 to perform references. Figures 2 to 6 Any process discussed in this disclosure.

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

[0157] I / O controller 408 can manage input and output signals for device 400. I / O controller 408 can also manage peripheral devices not integrated into device M02. In some implementations, I / O controller 408 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 408 can utilize an operating system such as iOS®, ANDROID®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In some implementations, I / O controller 408 can be implemented as part of a processor, such as processor 406. In some implementations, a user can interact with device 400 via I / O controller 408 or via hardware components controlled by I / O controller 408.

[0158] In some implementations, device 400 may include a single antenna 410. However, in other implementations, device 400 may have more than one antenna 410 (i.e., multiple antennas), including multiple antenna panels or antenna arrays capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 406 may communicate bidirectionally via one or more antennas 410, wired, or wireless links as described herein. For example, transceiver 406 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 406 may also include a modem for modulating packets to provide modulated packets to one or more antennas 410 for transmission, and for demodulating packets received from one or more antennas 410. Transceiver 406 may include one or more transmit chains, one or more receive chains, or combinations thereof.

[0159] The transmission chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator for modulating data onto a carrier signal, preparing it for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes (e.g., phase shift keying (PSK) or quadrature amplitude modulation (QAM)). The transmission chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmission chain may also include one or more antennas 410 for transmitting the amplified signal into the air or wireless medium.

[0160] The receiver chain can be configured to receive signals (e.g., control information, data, packets) via a wireless medium. For example, the receiver chain may include one or more antennas 410 for receiving signals over the air or via a wireless medium. The receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain may include at least one demodulator configured to demodulate the received signal and acquire transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0161] Figure 5 An example of a device 500 supporting HARQ operations for multicast services according to various aspects of this disclosure is illustrated. Device 500 may be an example of a network entity 102 as described herein. Device 500 may support wireless communication with one or more network entities 102, UE 104, or any combination thereof. Device 500 may include components for bidirectional communication, including components for transmitting and receiving communications, such as a processor 502, a memory 504, a transceiver 506, and an optional I / O controller 508. These components may communicate electronically or be otherwise coupled (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., a bus).

[0162] Processor 502, memory 504, transceiver 506, or various combinations thereof or various components thereof may be examples of components used to perform the various aspects of this disclosure described herein. For example, processor 502, memory 504, transceiver 506, or various combinations thereof or components thereof may support methods for performing one or more of the operations described herein.

[0163] In some implementations, processor 502, memory 504, transceiver 506, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise supporting components for performing the functions described in this disclosure. In some implementations, processor 502 and memory 504 coupled to processor 502 may be configured to perform one or more of the functions described herein (e.g., instructions stored in memory 504 are executed by processor 502).

[0164] For example, according to the examples disclosed herein, processor 502 may support wireless communication at device 500. Processor 502 may be configured to operate to support: components for determining a mapping between data for multicast services and a Hybrid Automatic Repeat Request (HARQ) process; and components for sending data associated with a first configuration to a user equipment, wherein the first configuration is associated with the mapping.

[0165] Processor 502 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, processor 502 may be configured to use a memory controller to operate a memory array. In some other implementations, the memory controller may be integrated into processor 502. Processor 502 may be configured to execute computer-readable instructions stored in memory (e.g., memory 504) to cause device 500 to perform various functions of this disclosure, enabling device 500 to perform references. Figures 2 to 6 Any process discussed in this disclosure.

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

[0167] I / O controller 508 can manage input and output signals for device 500. I / O controller 508 can also manage peripheral devices not integrated into device M02. In some implementations, I / O controller 508 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 508 can utilize an operating system such as iOS®, ANDROID®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In some implementations, I / O controller 508 can be implemented as part of a processor, such as processor 506. In some implementations, a user can interact with device 500 via I / O controller 508 or via hardware components controlled by I / O controller 508.

[0168] In some implementations, device 500 may include a single antenna 510. However, in other implementations, device 500 may have more than one antenna 510 (i.e., multiple antennas), including multiple antenna panels or antenna arrays capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 506 may communicate bidirectionally via one or more antennas 510, wired, or wireless links as described herein. For example, transceiver 506 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 506 may also include a modem for modulating packets to provide modulated packets to one or more antennas 510 for transmission, and for demodulating packets received from one or more antennas 510. Transceiver 506 may include one or more transmit chains, one or more receive chains, or combinations thereof.

[0169] The transmission chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator for modulating data onto a carrier signal, preparing it for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes (e.g., phase shift keying (PSK) or quadrature amplitude modulation (QAM)). The transmission chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmission chain may also include one or more antennas 510 for transmitting the amplified signal into the air or wireless medium.

[0170] The receiver chain can be configured to receive signals (e.g., control information, data, packets) via a wireless medium. For example, the receiver chain may include one or more antennas 510 for receiving signals over the air or via a wireless medium. The receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain may include at least one demodulator configured to demodulate the received signal and acquire transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0171] Figure 6 An example of a processor 600 supporting HARQ operations for multicast services according to various aspects of this disclosure is illustrated. Processor 600 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 600 may be implemented in a device or a component thereof as described herein. For example, the device may be an example of UE 104 described herein. Processor 600 may include a controller 602 configured to perform various operations according to the examples described herein. Processor 600 may optionally include at least one memory 604, such as an L1 / L2 / L3 cache. Additionally or alternatively, processor 600 may optionally include one or more arithmetic logic units (ALUs) 600. One or more of these components may be electronically communicated or otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0172] Processor 600 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, send, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to the processor chipset or included in the processor chipset (e.g., processor 600)), or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase-change memory (PCM), etc.).

[0173] Controller 602 can be configured to manage and coordinate various operations of processor 600 (e.g., signaling, receiving, acquiring, retrieving, sending, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 600 to support various operations according to the examples described herein. For example, controller 602 can operate as a control unit of processor 600, generating control signals that manage the operation of various components of processor 600. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating operation timing.

[0174] Controller 602 can be configured to fetch (e.g., acquire, retrieve, receive) instructions from memory 604 and determine subsequent instructions(s) to be executed, enabling processor 600 to support various operations according to the examples described herein. Controller 602 can be configured to track the memory addresses of instructions associated with memory 604. Controller 602 can be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 602 can be configured to interpret instructions and determine control signals to be output to other components of processor 600, enabling processor 600 to support various operations according to the examples described herein. Additionally or alternatively, controller 602 can be configured to manage data flow within processor 600. Controller 602 can be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 600.

[0175] Memory 604 may include one or more caches (e.g., memory native to or included in processor 600), or other memories such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, memory 604 may reside within or on the processor chipset (e.g., native to processor 600). In some other implementations, memory 604 may reside external to the processor chipset (e.g., remote from processor 600).

[0176] Memory 604 may store computer-readable, computer-executable code, including instructions that, when executed by processor 600, cause processor 600 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. Controller 602 and / or processor 600 may be configured to execute the computer-readable instructions stored in memory 604 to cause processor 600 to perform various functions. For example, processor 600 and / or controller 602 may be coupled to or coupled to memory 604, and processor 600, controller 602, and memory 604 may be configured to perform the various functions described herein. In some examples, processor 600 may include multiple processors, and memory 604 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein.

[0177] One or more ALU 606s can be configured to support various operations according to the examples described herein. In some implementations, one or more ALU 606s may reside within or on a processor chipset (e.g., processor 600). In some other implementations, one or more ALU 606s may reside outside the processor chipset (e.g., processor 600). One or more ALU 606s can perform one or more calculations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 606s can receive input operands and an opcode that determines the operation to be performed. One or more ALU 606s are configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Additionally or alternatively, one or more ALU 606s may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALU 606s to handle conditional operations, comparisons, and bitwise operations.

[0178] Based on the examples disclosed herein, processor 600 may support wireless communication. Processor 600 may be configured or operable to support: components for receiving data from a base station for multicast services, wherein the data is associated with a first configuration and the first configuration is associated with a mapping between the data and a Hybrid Automatic Repeat Request (HARQ) process; and components for determining HARQ operations associated with the data based on the first configuration.

[0179] Figure 7An example of a processor 700 supporting HARQ operations for multicast services according to various aspects of this disclosure is illustrated. Processor 700 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 700 may be implemented in a device or component thereof as described herein. For example, a device may be an example of network entity 102 as described herein. Processor 700 may include a controller 702 configured to perform various operations according to the examples described herein. Processor 700 may optionally include at least one memory 704, such as an L1 / L2 / L3 cache. Additionally or alternatively, processor 700 may optionally include one or more arithmetic logic units (ALUs) 700. One or more of these components may be electronically communicated or otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0180] Processor 700 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, send, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to the processor chipset or included in the processor chipset (e.g., processor 700)), or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase-change memory (PCM), etc.).

[0181] Controller 702 can be configured to manage and coordinate various operations of processor 700 (e.g., signaling, receiving, acquiring, retrieving, sending, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 700 to support various operations according to the examples described herein. For example, controller 702 can operate as a control unit of processor 700, generating control signals that manage the operation of various components of processor 700. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating operation timing.

[0182] Controller 702 can be configured to fetch (e.g., acquire, retrieve, receive) instructions from memory 704 and determine subsequent instructions(s) to be executed, enabling processor 700 to support various operations according to the examples described herein. Controller 702 can be configured to track the memory addresses of instructions associated with memory 704. Controller 702 can be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 702 can be configured to interpret instructions and determine control signals to be output to other components of processor 700, enabling processor 700 to support various operations according to the examples described herein. Additionally or alternatively, controller 702 can be configured to manage data flow within processor 700. Controller 702 can be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 700.

[0183] Memory 704 may include one or more caches (e.g., memory local to or included in processor 700) or other memories such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, memory 704 may reside within or on the processor chipset (e.g., locally to processor 700). In some other implementations, memory 704 may reside outside the processor chipset (e.g., remotely from processor 700).

[0184] Memory 704 may store computer-readable, computer-executable code, including instructions that, when executed by processor 700, cause processor 700 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. Controller 702 and / or processor 700 may be configured to execute the computer-readable instructions stored in memory 704 to cause processor 700 to perform various functions. For example, processor 700 and / or controller 702 may be coupled to or coupled to memory 704, and processor 700, controller 702, and memory 704 may be configured to perform the various functions described herein. In some examples, processor 700 may include multiple processors, and memory 704 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein.

[0185] One or more ALU 700s can be configured to support various operations according to the examples described herein. In some implementations, one or more ALU 700s may reside within or on a processor chipset (e.g., processor 700). In some other implementations, one or more ALU 700s may reside outside the processor chipset (e.g., processor 700). One or more ALU 700s can perform one or more calculations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 700s can receive input operands and an opcode that determines the operation to be performed. One or more ALU 700s are configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Additionally or alternatively, one or more ALU 700s may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALU 700s to handle conditional operations, comparisons, and bitwise operations.

[0186] Based on the examples disclosed herein, processor 700 may support wireless communication. Processor 700 may be configured or operable to support: components for determining a mapping between data for multicast services and a Hybrid Automatic Repeat Request (HARQ) process; and components for transmitting data associated with a first configuration to a user equipment, wherein the first configuration is associated with the mapping.

[0187] Figure 8 A flowchart illustrating a method 800 for performing HARQ operations for multicast services, supported by various aspects of this disclosure, is shown. The operation of method 800 can be implemented by the device or components thereof described herein. For example, the operation of method 800 can be performed by the UE 104 described herein. In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or additionally, the device can use dedicated hardware to perform aspects of the described functions.

[0188] At 805, the method may include: receiving data from a base station for multicast service, wherein the data is associated with a first configuration, and the first configuration is associated with a mapping between the data and a Hybrid Automatic Repeat Request (HARQ) process. The operation of 805 can be performed according to the examples described herein. In some implementations, aspects of the operation of 805 may be derived from references... Figure 1 The device described is used to perform this action.

[0189] At 810, the method may include: determining a HARQ operation associated with the data based on a first configuration. The operation at 810 can be performed according to the examples described herein. In some implementations, aspects of the operation at 810 may be derived from references... Figure 1 The device described is used to perform this action.

[0190] Figure 9 A flowchart illustrating a method 900 for performing HARQ operations for multicast services, supported by various aspects of this disclosure, is shown. The operation of method 900 can be implemented by the device or components thereof described herein. For example, the operation of method 900 can be performed by UE 104 described herein. In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or additionally, the device can use dedicated hardware to perform aspects of the described functions. Method 900 can be considered a continuation of method 800.

[0191] At 905, the method may include: sending HARQ-ACK information to the base station indicating a request for retransmission of data, wherein the multicast service is associated with a non-terrestrial network (NTN), a first HARQ feedback configuration for the data is enabled, and a second HARQ feedback configuration for the HARQ process is enabled. The operation of 905 can be performed according to the examples described herein. In some implementations, aspects of the operation of 905 may be derived from references... Figure 1 The device described is used to perform this action.

[0192] At 910, the method may include: monitoring retransmissions of multicast from the base station after a first duration following the transmission of the HARQ-ACK information, wherein the first duration is associated with a round-trip time (RTT) value between the user equipment and the base station. The operation of 910 can be performed according to the examples described herein. In some implementations, aspects of the operation of 910 may be derived from references... Figure 1 The device described is used to perform this action.

[0193] Figure 10 A flowchart illustrating a method 1000 for performing HARQ operations for multicast services, supported by various aspects of this disclosure, is shown. The operation of method 1000 may be implemented by the device or components thereof described herein. For example, the operation of method 1000 may be performed by network entity 102 described herein. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or additionally, the device may use dedicated hardware to perform aspects of the described functions.

[0194] At point 1005, the method may include determining a mapping between data for the multicast service and the Hybrid Automatic Repeat Request (HARQ) process. The operation at point 1005 can be performed according to the examples described herein. In some implementations, aspects of the operation at point 1005 may be derived from references... Figure 1 The device described is used to perform this action.

[0195] At point 1010, the method may include: sending data associated with a first configuration to a user equipment, wherein the first configuration is associated with a mapping. The operation of 1010 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1010 may be derived from references... Figure 1 The device described is used to perform this action.

[0196] Figure 11 A flowchart illustrating a method 1100 for performing HARQ operations for multicast services, supported by various aspects of this disclosure, is shown. The operation of method 1100 can be implemented by the device or components thereof described herein. For example, the operation of method 1100 can be performed by network entity 102 described herein. In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or additionally, the device can use dedicated hardware to perform aspects of the described functions. Method 1100 can be considered a continuation of method 1000.

[0197] At 1105, the method may include: receiving a NACK for data from a user equipment in a HARQ-ACK message, wherein a first HARQ feedback configuration for data is enabled, a negative acknowledgment-only (NACK-only) feedback mode is configured for data, a first type of HARQ-ACK codebook is configured for the HARQ-ACK message for data, and a second HARQ feedback configuration for the HARQ process is disabled. The operation at 1105 can be performed according to the examples described herein. In some implementations, aspects of the operation at 1105 may be derived from references. Figure 1 The device described is used to perform this action.

[0198] At 1110, the method may include: decoding the NACK. The operation at 1110 can be performed according to the examples described herein. In some implementations, aspects of the operation at 1110 can be found in the references. Figure 1 The device described is used to perform this action.

[0199] At step 1115, the method may include: retransmitting data to the user equipment. The operation at step 1115 can be performed according to the examples described herein. In some implementations, aspects of the operation at step 1115 can be found in the references. Figure 1 The device described is used to perform this action.

[0200] It should be noted that the methods described in this paper describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are also possible. Furthermore, aspects from two or more methods can be combined.

[0201] The various illustrated boxes and components described in connection with this disclosure may be implemented or performed by the following: a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. A general-purpose processor may be a microprocessor, but alternatively, 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 combined with a DSP core, or any other such configuration).

[0202] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of the foregoing. Features implementing the functions may also be physically located in various locations, including being distributed such that portions of the functions are implemented at different physical locations.

[0203] Computer-readable media include both non-transitory computer storage media and communication media, with the latter including any medium that facilitates the transfer of a computer program from one place to another. Non-transitory storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer. For example, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

[0204] As used herein, including in the claims, the article “a” preceding an element is unrestricted and should be understood to mean “at least one” or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein, including in the claims, the use of “or” in a list of items (e.g., a list of items prefixed with phrases such as “at least one of…” or “one or more of…” or “one or two of…”) indicates an inclusive list, such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase “based on” should not be construed as a reference to a closed set of conditions. For example, an example step described as “based on condition A” could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as the phrase “at least partially based on.” Furthermore, as used herein, including in the claims, “set” can include one or more elements.

[0205] The description herein is provided to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment, comprising: processor; as well as A transceiver, which is coupled to the processor, The processor is configured as follows: Data for multicast service is received from a base station via the transceiver, wherein the data is associated with a first configuration and the first configuration is associated with a mapping between the data and a Hybrid Automatic Repeat Request (HARQ) process; as well as Based on the first configuration, determine the HARQ operation associated with the data.

2. The user equipment of claim 1, wherein a first HARQ feedback configuration for the data is absent, and a second HARQ feedback configuration for the HARQ process is disabled.

3. The user equipment according to claim 2, wherein the HARQ operation includes one of the following: Skip generating and reporting HARQ acknowledgment (HARQ-ACK) messages for the data mapped to the HARQ process; or When the first type of HARQ-ACK codebook is configured for HARQ-ACK information for the data, a negative acknowledgment (NACK) for the HARQ-ACK information is generated, and the NACK for the data mapped to the HARQ process is reported.

4. The user equipment of claim 1, wherein a first HARQ feedback configuration for the data is enabled, and a second HARQ feedback configuration for the HARQ process is enabled.

5. The user equipment of claim 4, wherein the multicast service is associated with a non-terrestrial network (NTN), and the processor is further configured to: The transceiver sends a HARQ-ACK message to the base station, indicating a request for retransmission of the data; and After a first duration following the transmission of the HARQ-ACK information, the retransmissions multicast from the base station are monitored, wherein the first duration is associated with the round-trip time (RTT) value between the user equipment and the base station.

6. The user equipment of claim 5, wherein the first duration is based on one of the following: A first HARQ-RTT timer, the duration of which corresponds to the sum of the duration of a second HARQ-RTT timer for point-to-multiple (PTM) services in the terrestrial network and the RTT value, wherein the first HARQ-RTT timer is associated with the duration of multicast retransmission for skipping monitoring of data for multicast services in the NTN. The duration of the second HARQ-RTT timer is extended by the RTT value; or The duration of the second HARQ-RTT timer corresponds to the duration of the third HARQ-RTT timer used for point-to-point (PTP) services in the NTN.

7. The user equipment of claim 4, wherein the multicast service is associated with an NTN, and the processor is further configured to: In ACK-NACK feedback mode, HARQ-ACK information is sent to the base station via the transceiver, wherein the HARQ-ACK information indicates a request for retransmission of the data; and After a second duration following the transmission of the HARQ-ACK information, the retransmission unicast from the base station is monitored, wherein the second duration is associated with the RTT value between the user equipment and the base station.

8. The user equipment of claim 7, wherein the second duration is based on one of the following: A fifth HARQ-RTT timer, the duration of which corresponds to the sum of the fourth HARQ-RTT timer for PTP service in the terrestrial network and the RTT value, wherein the fifth HARQ-RTT timer is associated with the duration of monitoring retransmission of data for unicast service in NTN; A sixth HARQ-RTT timer, the duration of which corresponds to the duration of a third HARQ-RTT timer for PTP service in NTN, wherein the sixth HARQ-RTT timer is associated with the duration for skipping the monitoring of retransmissions of data for unicast service in NTN; or The third HARQ-RTT timer.

9. The user equipment of claim 1, wherein a first HARQ feedback configuration for the data is enabled, a NACK-only feedback mode is configured for the data, a first type of HARQ-ACK codebook is configured for HARQ-ACK information for the data, and a second HARQ feedback configuration for the HARQ process is disabled.

10. The user equipment of claim 9, wherein the processor is further configured to: If the data is not correctly decoded, generate a NACK for the HARQ-ACK information; and The transceiver sends a NACK to the base station, indicating a request for retransmission of the data.

11. The user equipment of claim 10, wherein the multicast service is associated with an NTN, and the processor is further configured to: After a third duration following the transmission of the NACK, the retransmission multicast from the base station is monitored, wherein the third duration is associated with the RTT value between the user equipment and the base station, and wherein the third duration is based on one of the following: A first HARQ-RTT timer, the duration of which corresponds to the sum of the duration of a second HARQ-RTT timer for PTM services in the terrestrial network and the RTT value, wherein the first HARQ-RTT timer is associated with the duration of multicast retransmission for skipping monitoring of data for multicast services in the NTN. The duration of the second HARQ-RTT timer is extended by the RTT value; or The duration of the second HARQ-RTT timer corresponds to the duration of the third HARQ-RTT timer used for PTP service in NTN.

12. The user equipment according to any one of claims 2 to 11, wherein the processor is further configured to: The transceiver receives from the base station via Radio Resource Control (RRC) signaling or in Downlink Control Information (DCI) an indication to disable or enable the second HARQ feedback configuration for the HARQ process.

13. A base station, comprising: processor; as well as A transceiver, which is coupled to the processor, The processor is configured as follows: Determine the mapping between the data used for multicast services and the Hybrid Automatic Repeat Request (HARQ) process; and Data associated with a first configuration, which is associated with the mapping, is sent to the user equipment via the transceiver.

14. The base station of claim 13, wherein a first HARQ feedback configuration for the data is absent, and a second HARQ feedback configuration for the HARQ process is disabled.

15. The base station of claim 13, wherein a first HARQ feedback configuration for the data is enabled, and a second HARQ feedback configuration for the HARQ process is enabled.

16. The base station of claim 13, wherein a first HARQ feedback configuration for the data is enabled, a negative acknowledgment-only (NACK-only) feedback mode is configured for the data, a first type of HARQ-ACK codebook is configured for HARQ-ACK information for the data, and a second HARQ feedback configuration for the HARQ process is disabled.

17. The base station according to claim 16, wherein the processor is further configured to: In the HARQ-ACK message, a NACK for the data is received from the user equipment via the transceiver; Decode the NACK; and The data is retransmitted to the user equipment via the transceiver.

18. The base station according to any one of claims 14 to 17, wherein the processor is further configured to: The transceiver sends an indication to the user equipment via Radio Resource Control (RRC) signaling or in Downlink Control Information (DCI) to enable or disable the second HARQ feedback configuration for the HARQ process.

19. A method performed by a user equipment, comprising: Data for multicast service is received from a base station, wherein the data is associated with a first configuration and the first configuration is associated with a mapping between the data and a Hybrid Automatic Repeat Request (HARQ) process; as well as Based on the first configuration, determine the HARQ operation associated with the data.

20. A method performed by a base station, comprising: Determine the mapping between the data used for multicast services and the Hybrid Automatic Repeat Request (HARQ) process; as well as The data associated with a first configuration is sent to the user equipment, wherein the first configuration is associated with the mapping.

Images