Multicast transmission feedback and buffering

Abstract

Methods, systems, and devices for wireless communications are described. A user equipment (UE) and a base station may communicate in a wireless communications system. The UE may receive first control signaling indicating a first radio network temporary identifier (RNTI) and a first feedback process identifier, wherein the first RNTI indicates scheduling of unicast downlink transmissions. The UE may also receive second control signaling indicating a second RNTI and a second feedback process identifier, wherein the second RNTI indicates scheduling of multicast downlink transmissions. The UE may manage a hybrid automatic repeat request (HARQ) process associated with unicast downlink transmissions and multicast downlink transmissions at the UE based on the first RNTI, the first feedback process identifier, the second RNTI, and the second feedback process identifier. The UE may also process multicast downlink transmissions and broadcast signaling simultaneously.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 17 / 244,055, entitled “MULTICASTTRANSMISSION FEEDBACK AND BUFFER PROCESSING,” filed by TAKEDA et al. on April 29, 2021, which claims priority to U.S. provisional patent application No. 63 / 017,794, entitled “MULTICASTTRANSMISSION FEEDBACK AND BUFFER PROCESSING,” filed by TAKEDA et al. on April 30, 2020, each of which is assigned to the assignee of this application. Technical Field

[0003] The following relates generally to wireless communications, and more particularly to multicast transmission feedback and buffering. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcasting, etc. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency and power). Examples of such multiple access systems include fourth generation (4G) systems (e.g., long term evolution (LTE) systems, improved LTE (LTE-A) systems or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may use technologies such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA) or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations or one or more network access nodes, each base station or network access node simultaneously supporting communication for multiple communication devices (which may be further referred to as user equipment (UE)).

[0005] A UE may receive different types of transmissions from a base station, such as unicast transmissions, multicast transmissions, or broadcast transmissions. Summary of the invention

[0006] The described technology relates to improved methods, systems, devices and apparatuses for supporting multicast transmission feedback and buffering processing (including hybrid automatic repeat request (HARQ) processes). In summary, the described technology provides data storage in buffers for managing unicast, multicast and broadcast transmissions. A user equipment (UE) and a base station can communicate in a wireless communication system. The UE can receive a first control signaling indicating a first radio network temporary identifier (RNTI) and a first feedback process identifier, wherein the first RNTI indicates scheduling of unicast downlink transmissions. The UE can also receive a second control signaling indicating a second RNTI and a second feedback process identifier, wherein the second RNTI indicates scheduling of multicast downlink transmissions. The UE can manage feedback and buffering processes (e.g., HARQ processes) associated with unicast downlink transmissions and multicast downlink transmissions at the UE based on the first RNTI, the first feedback process identifier, the second RNTI, and the second feedback process identifier.

[0007] The UE may also receive broadcast signaling having a period that meets (e.g., is above) a first threshold, a transport block (TB) size that meets (e.g., is below) a second threshold, or both. The UE may receive a multicast downlink transmission configured without feedback processing. The UE may then process the multicast downlink transmission and the broadcast signaling during the same time period based on the remaining portion of the baseband processing budget for the broadcast signaling processing.

[0008] A method of wireless communication at a UE is described. The method may include: receiving first control signaling indicating a first RNTI and a first feedback process identifier, wherein the first RNTI indicates scheduling of a unicast downlink transmission; receiving second control signaling indicating a second RNTI and a second feedback process identifier, wherein the second RNTI indicates scheduling of a multicast downlink transmission; and managing a hybrid automatic repeat request (HARQ) process associated with the unicast downlink transmission and the multicast downlink transmission at the UE based on the first RNTI, the first feedback process identifier, the second RNTI, and the second feedback process identifier.

[0009] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to perform the following operations: receive first control signaling indicating a first RNTI and a first feedback process identifier, wherein the first RNTI indicates scheduling of a unicast downlink transmission; receive second control signaling indicating a second RNTI and a second feedback process identifier, wherein the second RNTI indicates scheduling of a multicast downlink transmission; and manage HARQ processes associated with the unicast downlink transmission and the multicast downlink transmission at the UE based on the first RNTI, the first feedback process identifier, the second RNTI, and the second feedback process identifier.

[0010] Another apparatus for wireless communication at a UE is described. The apparatus may include means for receiving first control signaling indicating a first RNTI and a first feedback process identifier, wherein the first RNTI indicates scheduling of a unicast downlink transmission; receiving second control signaling indicating a second RNTI and a second feedback process identifier, wherein the second RNTI indicates scheduling of a multicast downlink transmission; and managing HARQ processes associated with the unicast downlink transmission and the multicast downlink transmission at the UE based on the first RNTI, the first feedback process identifier, the second RNTI, and the second feedback process identifier.

[0011] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: receive first control signaling indicating a first RNTI and a first feedback process identifier, wherein the first RNTI indicates scheduling of a unicast downlink transmission; receive second control signaling indicating a second RNTI and a second feedback process identifier, wherein the second RNTI indicates scheduling of a multicast downlink transmission; and manage HARQ processes associated with the unicast downlink transmission and the multicast downlink transmission at the UE based on the first RNTI, the first feedback process identifier, the second RNTI, and the second feedback process identifier.

[0012] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for identifying assignment of the second feedback process identifier for the multicast downlink transmission based on receiving the second control signaling.

[0013] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: storing data associated with the multicast downlink transmission in a buffer; and marking the stored data associated with the multicast downlink transmission with the second feedback process identifier.

[0014] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for determining to avoid storing data associated with the multicast downlink transmission in a buffer based on the second feedback process identifier.

[0015] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for receiving control signaling indicating a buffer storage configuration for storing data associated with the multicast downlink transmission in a buffer.

[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: determining that the first feedback process identifier and the second feedback process identifier correspond to the same feedback process identifier value and the first RNTI may be different from the second RNTI; and based on determining that the first feedback process identifier and the second feedback process identifier correspond to the same identifier value and the first RNTI may be different from the second RNTI, flushing stored data from a buffer.

[0017] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: applying one or more feedback process handling rules to the unicast downlink transmission and the multicast downlink transmission according to a single HARQ process for the unicast downlink transmission and the multicast downlink transmission.

[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: identifying a first data rate for the multicast downlink transmission and a second data rate for the unicast downlink transmission, wherein the first data rate and the second data rate can be dynamically configured based on a component carrier (CC) data rate.

[0019] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: receiving configuration signaling indicating a semi-static assignment of a first set of feedback process identifiers for unicast downlink transmissions and a second set of feedback process identifiers for multicast downlink transmissions.

[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: managing a first HARQ process for the unicast downlink transmission; and managing a second HARQ process for the multicast downlink transmission, wherein the second HARQ process can be managed in parallel with the first HARQ process.

[0021] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: applying one or more feedback process handling rules to both the unicast downlink transmission and the multicast downlink transmission across the first HARQ process and the second HARQ process.

[0022] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: identifying non-sequential ordering between downlink data transmission and corresponding feedback process identifiers across the first HARQ process and the second HARQ process, or non-sequential ordering between control channel transmission and corresponding data transmission across the first HARQ process and the second HARQ process.

[0023] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: receiving configuration signaling, wherein the configuration signaling configures a first physical downlink control channel candidate set for the first control signaling indicating the first RNTI and configures a second physical downlink control channel candidate set for the second control signaling indicating the second RNTI.

[0024] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: receiving configuration signaling, the configuration signaling indicating a first feedback processing timeline for the unicast downlink transmission and a second feedback processing timeline for the multicast downlink transmission, wherein the first feedback processing timeline may be different from the second feedback processing timeline.

[0025] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: identifying a first data rate for the multicast downlink transmission and a second data rate for the unicast downlink transmission, wherein the first data rate and the second data rate can be semi-statically configured based on a component carrier (CC) data rate.

[0026] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: determining that the first feedback process identifier and the second feedback process identifier correspond to the same feedback process identifier value and the first RNTI may be different from the second RNTI; storing data associated with the unicast downlink transmission in a first buffer according to the first HARQ process; and storing data associated with the multicast downlink transmission in a second buffer according to the second HARQ process.

[0027] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: identifying the first feedback process identifier from the first feedback process identifier set; and identifying the second feedback process identifier from the second feedback process identifier set.

[0028] A method of wireless communication at a UE is described. The method may include receiving broadcast signaling having a period above a first threshold, a transport block size below a second threshold, or both; receiving a multicast downlink transmission configured without feedback processing; and processing the multicast downlink transmission and the broadcast signaling during a same time period based on a remaining portion of a baseband processing budget for broadcast signaling processing.

[0029] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to perform the following operations: receive broadcast signaling having a period above a first threshold, a transport block size below a second threshold, or both; receive a multicast downlink transmission configured without feedback processing; and process the multicast downlink transmission and the broadcast signaling during the same time period based on a remaining portion of a baseband processing budget for broadcast signaling processing.

[0030] Another apparatus for wireless communication at a UE is described. The apparatus may include means for receiving broadcast signaling having a period above a first threshold, a transport block size below a second threshold, or both; receiving a multicast downlink transmission configured without feedback processing; and processing the multicast downlink transmission and the broadcast signaling during a same time period based on a remaining portion of a baseband processing budget for broadcast signaling processing.

[0031] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: receive broadcast signaling having a period above a first threshold, a transport block size below a second threshold, or both; receive a multicast downlink transmission configured without feedback processing; and process the multicast downlink transmission and the broadcast signaling during the same time period based on a remaining portion of a baseband processing budget for broadcast signaling processing.

[0032] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: receiving a unicast downlink transmission; and processing the unicast downlink transmission, the multicast downlink transmission, and the broadcast signaling during the same time period based on the remaining portion of the baseband processing budget used for broadcast signaling processing.

[0033] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a combined data rate for the unicast downlink transmission and the multicast downlink transmission may be less than a CC data rate.

[0034] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: receiving configuration signaling indicating a processing allocation of a baseband processing budget between broadcast signaling processing, unicast signaling processing, and multicast signaling processing.

[0035] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the multicast downlink transmission may be received and processed while the UE is in an idle state or an inactive state. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 An example of a wireless communication system supporting multicast transmission feedback and buffering handling in accordance with aspects of the present disclosure is shown.

[0037] Figure 2An example of a wireless communication system supporting multicast transmission feedback and buffering handling in accordance with aspects of the present disclosure is shown.

[0038] Figure 3 An example of a buffer system supporting multicast transmission feedback and buffering according to aspects of the present disclosure is shown.

[0039] Figure 4 An example of a process flow supporting multicast transmission feedback and buffering processing in accordance with aspects of the present disclosure is shown.

[0040] Figure 5 An example of a process flow supporting multicast transmission feedback and buffering processing in accordance with aspects of the present disclosure is shown.

[0041] Figure 6 and 7 A block diagram of an apparatus supporting multicast transmission feedback and buffering processing according to aspects of the present disclosure is shown.

[0042] Figure 8 A block diagram of a communications manager supporting multicast transmission feedback and buffering handling in accordance with aspects of the present disclosure is shown.

[0043] Fig. 9 A diagram of a system including devices supporting multicast transmission feedback and buffering handling in accordance with aspects of the present disclosure is shown.

[0044] Figures 10 to 13 A flow chart illustrating a method of supporting multicast transmission feedback and buffering processing according to aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0045] User equipment (UE) and base stations can communicate on communication channels in a wireless communication system. The base station can also send unicast data as well as multicast data and broadcast data to the UE. Unicast data can include data dedicated to a specific UE. Multicast data can include the same signal sent to multiple UEs served by the base station. Broadcast data can include data sent in a channel that can be received by any UE, and can include data applicable to many UEs.

[0046] The base station may send unicast data, multicast data, and broadcast data in a physical downlink shared channel (PDSCH). The PDSCH containing each type of data may have a cyclic redundancy check (CRC) scrambled by different types of radio network temporary identifiers (RNTIs). For example, in the case of multicast data, one or more UEs may simultaneously receive the PDSCH containing multicast data. The PDSCH containing multicast data may be scheduled by downlink control information (DCI). The DCI may correspond to a DCI format in which a cyclic redundancy check (CRC) is scrambled by a multimedia broadcast multicast service RNTI (M-RNTI) or a group RNTI (G-RNTI). In another example of the case of unicast data, the PDSCH and the corresponding DCI may have a CRC scrambled by a cell RNTI (C-RNTI), where the C-RNTI is UE-specific and therefore corresponds to unicast data.

[0047] When the UE receives unicast data, the UE may also be configured to perform a hybrid automatic repeat request (HARQ) process. The UE may receive control signaling (e.g., DCI) for scheduling unicast data transmission. The UE may then monitor the resources on which the unicast data is sent and may attempt to decode the unicast data. Based on the successful reception and decoding of the unicast data, the UE may send an ACK (ACK) or a negative ACK (NACK) to the base station so that the base station may know whether the UE has successfully received the transmission. The base station may then determine whether to retransmit the unicast data. In addition, each unicast downlink transmission may correspond to a feedback process identifier, such as a HARQ process identifier (HPID). Subsequent retransmissions of the same unicast transmission may correspond to the same HPID. Different unicast transmissions may correspond to different HPIDs. The HPID for each scheduled unicast transmission may be indicated to the UE in the DCI. The UE may send ACK / NACK and process the downlink data in the buffer according to the specific HPID for each downlink transmission.

[0048] To improve spectral efficiency, the UE may also implement a HARQ process for multicast transmissions. The HARQ process may correspond to the process of demodulating, decoding, soft combining data in a buffer (e.g., in the case of retransmissions), and sending ACK / NACK feedback. The UE may be scheduled to receive unicast data in the PDSCH and multicast data in the PDSCH. Unicast data may be indicated by a C-RNTI, and multicast data may be implemented by an M-RNTI.

[0049] The UE may store unicast data in a soft buffer and manage when and how to send ACK / NACK feedback. The UE may store multicast data in the same or different soft buffer as unicast based on multiple parameters. The UE may also determine whether to flush the soft buffer to store different types of data in the buffer (e.g., flush unicast data to store multicast data).

[0050] The UE is also capable of receiving and processing unicast and broadcast PDSCH transmissions simultaneously. The UE may have or be configured with a baseband processing budget set for processing system information (e.g., broadcast transmissions). In the case where the system information (or other broadcast transmissions) is configured with an extended period or reduced TB size within a given time period, the UE may utilize some of the baseband processing budget remaining after processing the system information to process multicast transmissions. Thus, the UE 115 is capable of processing unicast, multicast, or broadcast transmissions simultaneously.

[0051] Aspects of the disclosure are first described in the context of wireless communication systems. Aspects of the disclosure are then described in the context of buffering processes and process flows. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams relating to multicast transmission hybrid automatic repeat request (HARQ) processing.

[0052] Figure 1 An example of a wireless communication system 100 supporting multicast transmission feedback and buffer handling according to aspects of the present disclosure is shown. The wireless communication system 100 may include one or more base stations 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an improved LTE (LTE-A) network, an LTE-A Pro network, or a new radio (NR) network. In some examples, the wireless communication system 100 may support enhanced broadband communications, ultra-reliable (e.g., mission-critical) communications, low-latency communications, or communications with low-cost and low-complexity devices, or any combination thereof.

[0053] Base stations 105 may be dispersed throughout a geographic area to form wireless communication system 100, and may be devices of different forms or capabilities. Base stations 105 and UEs 115 may communicate wirelessly via one or more communication links 125. Each base station 105 may provide a coverage area 110 over which UEs 115 and base stations 105 may establish one or more communication links 125. Geographic coverage areas 110 may be examples of geographic areas over which base stations 105 and UEs 115 may support transmission of signals in accordance with one or more radio access technologies.

[0054] UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary, mobile, or both at different times. UEs 115 may be devices of different forms or with different capabilities. Figure 1 Some example UEs 115 are shown in FIG. 1. The UEs 115 described herein can communicate with various types of devices, such as other UEs 115, base stations 105, or network devices (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network devices), such as Figure 1 shown.

[0055] The base stations 105 may communicate with the core network 130, or communicate with each other, or perform both operations. For example, the base stations 105 may interface with the core network 130 via one or more backhaul links 120 (e.g., via S1, N2, N3 or other interfaces). The base stations 105 may communicate with each other directly (e.g., directly between the base stations 105) on the backhaul links 120 (e.g., via X2, Xn or other interfaces), or communicate with each other indirectly (e.g., via the core network 130), or perform both operations. In some examples, the backhaul links 120 may be or include one or more wireless links.

[0056] One or more of the base stations 105 described herein may include or may be referred to by those skilled in the art as a base station transceiver, a radio base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a Home Node B, a Home Evolved Node B, or some other appropriate terminology.

[0057] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other appropriate terminology, where a "device" may also be referred to as a unit, a station, a terminal, or a client, among other examples. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, among other examples, which may be implemented in various items such as appliances, or vehicles, meters, and among other examples.

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

[0059] The UE 115 and the base station 105 may communicate wirelessly with each other via one or more communication links 125 on one or more carriers. The term "carrier" may refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of a radio frequency spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling to coordinate operations for the carrier, user data, or other signaling. The wireless communication system 100 may support communication with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured with multiple downlink component carriers (CCs) and one or more uplink CCs. Carrier aggregation may be used with both frequency division duplex (FDD) CCs and time division duplex (TDD) CCs.

[0060] In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling that coordinates operations for other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN)) and may be placed according to a channel grid to be discovered by a UE 115. A carrier may operate in a standalone mode, where a UE 115 performs initial acquisition and connection via a carrier, or a carrier may operate in a non-standalone mode, where a different carrier (e.g., of the same or different radio access technology) is used to anchor the connection.

[0061] The communication link 125 shown in the wireless communication system 100 may include an uplink transmission from the UE 115 to the base station 105, or a downlink transmission from the base station 105 to the UE 115. A carrier may carry downlink or uplink communications (e.g., in FDD mode) or may be configured to carry both downlink and uplink communications (e.g., in TDD mode).

[0062] A carrier may be associated with a particular bandwidth of a radio frequency spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a number of determined bandwidths of a carrier for a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)). A device of the wireless communication system 100 (e.g., a base station 105, a UE 115, or both) may have a hardware configuration that supports communication on a particular carrier bandwidth, or may be configurable to support communication on one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a base station 105 or a UE 115 that supports simultaneous communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (e.g., a subband, a BWP) or all of a carrier bandwidth.

[0063] The signal waveform transmitted on the carrier may be composed of multiple subcarriers (e.g., using multicarrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may include a symbol period (e.g., the duration of a modulation symbol) and a subcarrier, wherein the symbol period and the subcarrier spacing are inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both). Therefore, the more resource elements received by the UE 115 and the higher the order of the modulation scheme, the higher the data rate for the UE 115 can be. Wireless communication resources may refer to a combination of radio frequency spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers may further increase the data rate or data integrity for communication with the UE 115.

[0064] One or more numerologies for a carrier may be supported, where the numerologies may include subcarrier spacing (Δf) and cyclic prefixes. A carrier may be divided into one or more BWPs with the same or different numerologies. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications for a UE 115 may be limited to the one or more active BWPs.

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

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

[0067] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in the form of bursts of shortened TTIs (sTTIs)).

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

[0069] Each base station 105 can provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots or other types of cells, or any combination thereof). The term "cell" can refer to a logical communication entity used to communicate with the base station 105 (e.g., on a carrier), and can be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID) or other identifier) ​​for distinguishing adjacent cells. In some examples, a cell can also refer to a geographic coverage area 110 or a portion of a geographic coverage area 110 (e.g., a sector) on which a logical communication entity operates. Depending on various factors (such as the capabilities of the base station 105), the range of such a cell can range from a smaller area (e.g., a structure, a subset of a structure) to a larger area. For example, a cell can be or include a building, a subset of a building, or an external space between or overlapping geographic coverage areas 110, as well as other examples.

[0070] A macro cell typically covers a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 115 with a service subscription to a network provider that supports the macro cell. A small cell may be associated with a lower power base station 105 than a macro cell, and the small cell may operate in the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to a UE 115 with a service subscription to a network provider, or may provide restricted access to a UE 115 associated with a small cell (e.g., a UE 115 in a closed subscriber group (CSG), a UE 115 associated with a user in a residence or office). A base station 105 may support one or more cells, and may also support the use of one or more CCs to communicate on one or more cells.

[0071] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0072] In some examples, base stations 105 may be mobile and, therefore, provide communication coverage for mobile geographic coverage areas 110. In some examples, different geographic coverage areas 110 associated with different technologies may overlap, but the different geographic coverage areas 110 may be supported by the same base station 105. In other examples, overlapping geographic coverage areas 110 associated with different technologies may be supported by different base stations 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of base stations 105 provide coverage for respective geographic coverage areas 110 using the same or different radio access technologies.

[0073] The wireless communication system 100 may support synchronous or asynchronous operation. For synchronous operation, the base stations 105 may have similar frame timing, and transmissions from different base stations 105 may be approximately aligned in time. For asynchronous operation, the base stations 105 may have different frame timing, and in some examples, transmissions from different base stations 105 may not be aligned in time. The techniques described herein may be used for synchronous or asynchronous operation.

[0074] Some UEs 115 (e.g., MTC or IoT devices) may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or base station 105 without human intervention. In some examples, M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application that utilizes the information or presents the information to a human interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, climate and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business billing.

[0075] Some UEs 115 may be configured to employ an operating mode that reduces power consumption, such as half-duplex communication (e.g., a mode that supports one-way communication via transmission or reception rather than transmission and reception simultaneously). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power saving techniques for UE 115 include entering a power-saving deep sleep mode when not participating in active communications, when operating on a limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a guard band of a carrier, or outside a carrier.

[0076] The wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, the wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC) or mission-critical communication. UE115 can be designed to support ultra-reliable, low-latency or critical functions (e.g., mission-critical functions). Ultra-reliable communication can include private communication or group communication, and can be supported by one or more mission-critical services (such as mission-critical push-to-talk (MCPTT), mission-critical video (MCVideo), or mission-critical data (MCData). Support for mission-critical functions can include prioritization of services, and mission-critical services can be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, mission-critical, and ultra-reliable low-latency can be used interchangeably in this article.

[0077] In some examples, UE 115 is able to communicate directly with other UE 115 on a device-to-device (D2D) communication link 135 (e.g., using a peer-to-peer (P2P) or D2D protocol). One or more UEs 115 utilizing D2D communication may be within a geographic coverage area 110 of a base station 105. Other UEs 115 in such a group may be outside the geographic coverage area 110 of the base station 105 or otherwise unable to receive transmissions from the base station 105. In some examples, groups of UEs 115 communicating via D2D communication may utilize a one-to-many (1:M) system, wherein each UE 115 transmits to each other UE 115 in the group. In some examples, the base station 105 facilitates scheduling of resources for D2D communication. In other cases, D2D communication is performed between UEs 115 without involving the base station 105.

[0078] In some systems, the D2D communication link 135 can be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, the vehicle can communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these items. The vehicle can use signals to send information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some examples, the vehicle in the V2X system can communicate with roadside infrastructure (such as a roadside unit), or communicate with the network via one or more network nodes (e.g., base station 105) using vehicle-to-network (V2N) communication, or both operations.

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

[0080] Some of the network devices (e.g., base stations 105) may include subcomponents such as access network entities 140, which may be examples of access node controllers (ANCs). Each access network entity 140 may communicate with the UE 115 through one or more other access network transport entities 145 (which may be referred to as radio heads, smart radio heads, or transmit / receive points (TRPs)). Each access network transport entity 145 may include one or more antenna panels. In some configurations, the various functions of each access network entity 140 or base station 105 may be distributed across various network devices (e.g., radio heads and ANCs) or merged into a single network device (e.g., base station 105).

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

[0082] The wireless communication system 100 may also operate in a super high frequency (SHF) region using a frequency band from 3 GHz to 30 GHz (also referred to as a centimeter band) or in an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also referred to as a millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between UE 115 and base station 105, and the EHF antenna of the corresponding device may be even smaller and more closely spaced than the UHF antenna. In some examples, this may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may suffer from even greater atmospheric attenuation and shorter distances than SHF or UHF transmissions. The technology disclosed herein may be employed across transmissions using one or more different frequency regions, and the designated use of frequency bands across these frequency regions may differ according to countries or regulatory agencies.

[0083] The wireless communication system 100 can utilize both licensed and unlicensed radio frequency spectrum bands. For example, the wireless communication system 100 can employ license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band (such as the 5 GHz industrial, scientific, and medical (ISM) band). When operating in an unlicensed radio frequency spectrum band, devices (such as base stations 105 and UEs 115) can employ carrier sensing for conflict detection and avoidance. In some examples, operations in unlicensed bands can be based on a carrier aggregation configuration combined with CCs operating in a licensed band (e.g., LAA). Operations in unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, as well as other examples.

[0084] The base station 105 or UE 115 may be equipped with multiple antennas, which may be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the base station 105 or UE 115 may be located within one or more antenna arrays or antenna panels (which may support MIMO operations or transmit or receive beamforming). For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, the antennas or antenna arrays associated with the base station 105 may be located at different geographical locations. The base station 105 may have an antenna array having a number of rows and columns of antenna ports that the base station 105 may use to support beamforming for communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support radio frequency beamforming for signals sent via the antenna ports.

[0085] The base station 105 or UE 115 can use MIMO communication to exploit multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such a technology may be referred to as spatial multiplexing. For example, a transmitting device may send multiple signals via different antennas or different combinations of antennas. Similarly, a receiving device may receive multiple signals via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry bits associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technology includes single-user MIMO (SU-MIMO) (where multiple spatial layers are sent to the same receiving device) and multi-user MIMO (MU-MIMO) (where multiple spatial layers are sent to multiple devices).

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

[0087] As part of the beamforming operation, the base station 105 or the UE 115 may use beam scanning techniques. For example, the base station 105 may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communications with the UE 115. The base station 105 may send some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) multiple times in different directions. For example, the base station 105 may send signals based on different sets of beamforming weights associated with different transmission directions. Transmissions in different beam directions may be used (e.g., by a transmitting device (such as the base station 105) or by a receiving device (such as the UE 115)) to identify a beam direction for subsequent transmission or reception by the base station 105.

[0088] Base station 105 may transmit some signals (e.g., data signals associated with a particular receiving device (e.g., UE 115)) in a single beam direction (e.g., a direction associated with the receiving device). In some examples, the beam direction associated with transmission along the single beam direction may be determined based on signals transmitted in one or more beam directions. For example, UE 115 may receive one or more of the signals transmitted by base station 105 in different directions and may report to base station 105 an indication of the signal received by UE 115 having the highest signal quality or otherwise acceptable signal quality.

[0089] In some examples, transmissions by a device (e.g., by a base station 105 or a UE 115) may be performed using multiple beam directions, and the device may generate a combined beam for transmission (e.g., from the base station 105 to the UE 115) using a combination of digital precoding or radio frequency beamforming. The UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured number of beams across the system bandwidth or one or more subbands. The base station 105 may send reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)) that may or may not be precoded. The UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type of codebook, a linear combination type of codebook, a port selection type of codebook). Although these techniques are described with reference to signals sent by base station 105 in one or more directions, UE 115 may employ similar techniques to send signals multiple times in different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115) or to send signals in a single direction (e.g., to send data to a receiving device).

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

[0091] The wireless communication system 100 may be a packet-based network operated according to a layered protocol stack. In the user plane, the communication at the bearer or packet data convergence protocol (PDCP) layer may be IP-based. The radio link control (RLC) layer may perform packet segmentation and reassembly to transmit on a logical channel. The medium access control (MAC) layer may perform priority handling and multiplexing of logical channels to transport channels. The MAC layer may also use error detection techniques, error correction techniques, or both to support retransmission at the MAC layer to improve link efficiency. In the control plane, the radio resource control (RRC) protocol layer may provide the establishment, configuration, and maintenance of an RRC connection (which supports radio bearers for user plane data) between a UE 115 and a base station 105 or a core network 130. At the physical layer, transport channels may be mapped to physical channels.

[0092] UE 115 and base station 105 can support retransmission of data to increase the possibility that the data is successfully received. Hybrid automatic repeat request (HARQ) feedback is a technology for increasing the possibility that data is correctly received on communication link 125. HARQ can include a combination of error detection (e.g., using cyclic redundancy check (CRC)), forward error correction (FEC) and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve the throughput at the MAC layer under poor radio conditions (e.g., low signal and noise conditions). In some examples, the device can support the same time slot HARQ feedback, wherein the device can provide HARQ feedback for data received in the previous symbol in the time slot in a specific time slot. In other cases, the device can provide HARQ feedback in subsequent time slots or according to some other time interval.

[0093] UE 115 and base station 105 may communicate in a wireless communication system. UE 115 may receive first control signaling indicating a first RNTI and a first feedback process identifier from base station 105, wherein the first RNTI indicates scheduling of unicast downlink transmission. UE 115 may also receive second control signaling indicating a second RNTI and a second feedback process identifier from base station 105, wherein the second RNTI indicates scheduling of multicast downlink transmission. UE 115 may manage feedback and buffering processes (e.g., HARQ processes) associated with unicast downlink transmission and multicast downlink transmission at UE 115 based on the first RNTI, the first feedback process identifier, the second RNTI, and the second feedback process identifier.

[0094] UE 115 may also receive broadcast signaling having a period above the first threshold, a TB size below the second threshold, or both from base station 105. UE 115 may receive a multicast downlink transmission configured without feedback processing. UE 115 may then process the multicast downlink transmission and the broadcast signaling during the same time period based on the remaining portion of the baseband processing budget for broadcast signaling processing.

[0095] Figure 2 An example of a wireless communication system 200 that supports multicast transmission feedback and buffer handling according to aspects of the present disclosure is shown. In some examples, the wireless communication system 200 can implement aspects of the wireless communication system 100. The wireless communication system 200 includes a UE 115-a, which can be as described with reference to Figure 1 The wireless communication system 200 also includes a base station 105-a, which may be as described with reference to Figure 1 An example of a base station 105 is depicted. The UE 115-a and the base station 105-a can communicate over a communication channel 205.

[0096] The base station 105-a may send control signaling 220 to the UE 115-a. The control signaling 220 may schedule downlink transmissions to the UE 115-a. The first control signaling 220-a may schedule transmissions of the unicast data 210, and the second control signaling 220-b may schedule transmissions of the multicast data 215. The base station 105-a may send the unicast data 210 and the multicast data 215 to the UE 115-a based on the control signaling 220.

[0097] UE 115-a may be configured to manage soft buffers for unicast data and multicast data. For example, as described herein, from a feedback process and soft buffer management perspective, UE 115-a may be configured to treat multicast data 215 as a unicast data 210 transmission. Additionally or alternatively, from a feedback process and soft buffer management perspective, UE 115-a may treat multicast data 215 as a broadcast data transmission.

[0098] The first control signaling 220-a may also indicate a first RNTI and a first HPID (e.g., a feedback process identifier) ​​corresponding to the unicast data 210. The first RNTI may be a C-RNTI. The first HPID may indicate a HARQ process schedule for transmissions and retransmissions corresponding to the unicast data 210. For example, the UE 115-a may send ACK / NACK feedback for the unicast data 110. Additionally or alternatively, the base station 105-a may wait until a time period corresponding to the HPID ends before sending a retransmission of the unicast data 210.

[0099] The second control signaling 220-b may indicate a second RNTI and a second HPID corresponding to the multicast data 215. The second RNTI may be an M-RNTI. The second HPID may indicate a HARQ process schedule for transmissions and retransmissions corresponding to the multicast data 215. For example, the UE 115-a may send ACK / NACK feedback for the multicast data 215. Additionally or alternatively, the base station 105-a may wait until a time period corresponding to the HPID ends before sending a retransmission of the multicast data 215.

[0100] In some cases, an HPID may be dynamically assigned to each of the unicast data 210 and the multicast data 215. In these cases, the control signaling 220-a scheduling the unicast data may include a C-RNTI, indicating that the data is unicast. In these cases, the UE 115-a does not know the type of data to be sent until the UE 115-a decodes the control signal 220-a (e.g., DCI).

[0101] UE 115-a may manage a HARQ process, which may include a feedback process, a buffering process, or both. For example, UE 115-a may manage a buffering process based on one or more of a C-RNTI, an HPID, an M-RNTI, and a second HPID associated with the M-RNTI. Additionally or alternatively, UE 115-a may manage a feedback process based on one or more of a C-RNTI, an HPID, an M-RNTI, and a second HPID associated with the M-RNTI. In some cases, UE 115-a may manage a feedback process, a buffering process, or both.

[0102] In an example of a buffering process, the UE 115-a may receive unicast data 210 in a PDSCH and may store the unicast data 210 in a soft buffer. The UE 115-a may also receive multicast data 215 in a non-overlapping PDSCH. Since the data in the multicast data 215 is dynamically configured (e.g., the UE 115-a does not know that the data is multicast until the UE 115-a receives control signaling 220-b), the UE 115-a may also determine whether to store the multicast data 215 in the same soft buffer as the unicast data 210. In some cases, the UE 115-a may store the multicast data 215 in the soft buffer, in which case the UE 115-a may flush the unicast data 210 from the soft buffer (e.g., if the HPIDs of the unicast data 210 and the multicast data 215 are the same). In some cases, the UE 115-a may not store the multicast data 215 in the soft buffer. In other cases, the UE 115 - a may be configured (eg, via configuration signaling) to store the multicast data 215 or not to store the multicast data 215 .

[0103] In these cases, in an example of a feedback process, the UE 115-a may be configured to send ACK / NACK feedback to the base station 105-a. For example, the UE 115-a may be configured to send ACK / NACK feedback in the order of the HPID numbers (e.g., the UE 115-a does not send ACK / NACK feedback out of order). Whether the UE 115-a stores the multicast data 215 or does not store the multicast data 215 may be based on whether the unicast HPID is the same as the multicast HPID.

[0104] In other cases, the HPID of each unicast data 210 transmission and multicast data 215 may be semi-statically configured. In this case, the UE 115-a may be configured with one or more HPIDs for multicast transmissions through higher layer signaling. In these cases, soft buffer management may be split between unicast data 210 and multicast data 215 according to the semi-static higher layer configuration. There may be one soft buffer for unicast data 210 and one soft buffer for multicast data 215. In these cases, the UE 115-a may be able to send HARQ feedback (e.g., ACK / NACK) for unicast data 110 and multicast data 215 out of order (e.g., HPID out of order). For example, the UE 115-a may send HARQ feedback for multiple unicast transmissions to the base station 105-a, and may then send HARQ feedback for multicast transmissions, even if the HPID for the multicast transmission is an intermediate number of the HPID for the unicast transmission. In some cases, the HPID for a multicast transmission may be the same as the HPID for a unicast transmission, and the ACK / NACK feedback for each may not be sent simultaneously, and therefore out of order.

[0105] UE 115-a may also manage unicast buffers and multicast buffers using different HARQ processing timeline configurations. For example, UE 115-a may manage unicast buffers according to a first HARQ processing timeline configuration, and UE 115-a may manage multicast buffers according to a second HARQ processing timeline configuration.

[0106] In addition, UE 115-a may also receive multicast data 215 and broadcast data simultaneously (e.g., during the same time period). UE 115-a may have some baseband processing budget for processing system information (e.g., broadcast data). Broadcast signaling may have a period that meets (e.g., is higher than) a first threshold, a TB size that meets (e.g., is lower than) a second threshold, or both. In these cases, UE 115-a is able to process multicast data 215 and broadcast data simultaneously. Therefore, UE 115-a is able to process unicast data, multicast data, and broadcast data simultaneously, even when UE 115-a is operating in an idle or inactive state.

[0107] Figure 3 An example of a buffer system 300 supporting multicast transmission feedback and buffering according to aspects of the present disclosure is shown. In some examples, the buffer system 300 can implement aspects of wireless communication systems 100 and 200. UE 115 can receive unicast transmissions and multicast transmissions, as shown in FIG. Figure 2 UE 115 may store unicast data and multicast data according to buffer system 300.

[0108] UE 115 may receive control signaling from base station 105 indicating an upcoming downlink transmission by base station 105. UE 115 may receive control signaling 305 indicating a transmission of unicast data 315. UE 115 may also receive control signaling 310 indicating a transmission of multicast data 320. Control signaling 305 and 310 may schedule resources for the upcoming downlink transmission and may also include the RNTI and HPID for the upcoming transmission.

[0109] For example, UE 115 may receive control signaling 305-a indicating unicast data 315-a. Control signaling 305-a may include C-RNTI (indicating that the data is unicast) and HPID number of unicast data 315-a. UE 115 may then receive unicast data 315-a and may store unicast data 315-a in unicast buffer 325. UE 115 may use unicast buffer 315 to manage HARQ feedback in an orderly manner. For example, UE 115 may also receive control signaling 305-b indicating unicast data 315-b. Control signaling 305-b may also include C-RNTI (indicating unicast data) and HPID number. UE 115 may also store unicast data 315-b in unicast buffer 325 and may send HARQ feedback for unicast data 315 in an orderly manner. Similarly, the UE 115 may receive the third control signaling 305 - c indicating the unicast data 315 - c and the C-RNTI and HPID of the unicast data 315 - c. Therefore, the unicast data 315 - c may also be stored in the unicast buffer 325 .

[0110] UE 115 may also receive control signaling 310 indicating multicast data 320. Control signaling 310 may include an M-RNTI for the multicast data (indicating that the scheduled data is multicast) and HPID 320. Base station 105 may send control signaling 305 and 310 to UE 115 in a DCI, which may be sent in a physical downlink control channel (PDCCH). Unicast data 315 and multicast data 320 may each be sent by base station 105 in a PDSCH. In some cases, each unicast transmission and each multicast transmission may be sent in a non-overlapping PDSCH.

[0111] In some cases, the HPIDs of the unicast data 315 and the multicast data 320 are dynamically configured. That is, before the UE 115 reads the control signaling 305 or 310, the UE 115 may not know whether the upcoming data is unicast data 315 or multicast data 320. In these dynamic cases, the UE 115 may receive the multicast data 320 and may store the multicast data in the unicast buffer 325, where the stored data is marked by the HPID indicated in the control signaling 310, or the UE may not store the data in the unicast buffer 325. In some cases, the UE 115 may receive configuration information indicating whether to store the multicast data 320 in the unicast buffer 325.

[0112] UE 115 may have stored soft bits of unicast data 315-a having a first HPID in unicast buffer 325. UE 115 may also have stored soft bits of unicast data 315-b corresponding to a second HPID in unicast buffer 325. Then, UE 115 may receive control signaling 310 indicating multicast data 320, and multicast data 320 may have the same HPID as unicast data 315-b. In these cases, UE 115 may refresh the soft bits of unicast data 315-b from unicast buffer 325, and UE 115 may store multicast data 320 in unicast buffer 325. In some cases, the data corresponding to the same HPID (whether unicast data 315-b or multicast data 320) is the same data. In addition, UE 115 may have stored multicast data 320 corresponding to a second HPID, and may also receive control signaling 310-c indicating unicast data 315-c corresponding to the same second HPID. In these cases, the UE 115 may flush the multicast bits from the buffer and store the unicast data 315-c. The UE 115 may perform the buffer management process and flushing regardless of whether the new data indicator (NDI) is toggled in the control signaling 305 or 310. For example, regardless of whether the NDI field is toggled in the control signaling 305-b or the control signaling 310, the UE 115 may flush the unicast data 315-b based on receiving the multicast data 320 having the same HPID.

[0113] In these cases of dynamically configured HPID, UE 115 can avoid sending HARQ feedback until the end of HARQ feedback for PDSCH with the same HPID. In these cases, UE 115 can determine not to perform out-of-order HARQ feedback. UE 115 may also expect downlink scheduling to be orderly, so that the control signaling 305 or 310 in the PDCCH is followed by the corresponding PDSCH, rather than different PDSCHs. In addition, there may be a total data rate of unicast data 315 and multicast data 320. The data rate ratio between unicast data 315 and multicast data 320 can be flexible and dynamic. At some times, more data can be used for unicast data 315, and at other times, more data can be used for multicast data 320. The total data rate can be set for a given frequency resource (such as a component carrier (CC)), and the data rate of each CC cannot be exceeded.

[0114] In other cases, the HPID number may be semi-statically configured. In these cases, higher layer signaling may indicate to UE 115 a plurality of HPIDs allocated for multicast transmission. In these cases, UE 115 may receive control signaling 310. UE 115 may determine that the HPID indicating multicast data 320 is a multicast HPID set. UE 115 may then store multicast data 320 in multicast buffer 330, rather than flushing buffer 325 or determining not to store multicast data 320 in unicast buffer 325.

[0115] In some of these semi-statically configured situations, out-of-order HARQ feedback may be used. For example, unicast data 315-b and multicast data 320 may correspond to the same HPID. As indicated in the control signaling for transmission, UE115 may use different RNTIs for each data transmission to distinguish data with the same HPID. UE 115 may expect to receive unicast data 315-b and multicast data 320 out of order (e.g., not at overlapping times). For out-of-order performance, PDCCHs carrying control signaling 305 and 310 may be selected from different PDCCH candidate sets. For example, some PDCCH candidate sets may correspond to unicast control signaling 305, and other PDCCH candidate sets may correspond to multicast control signaling 310. In addition, each different PDCCH candidate set may correspond to a different search space set configuration. There may also be different HARQ processing timeline configurations between unicast buffer 325 management and multicast buffer 330 management.

[0116] Figure 4An example of a process flow 400 for supporting multicast transmission feedback and buffer handling in accordance with aspects of the present disclosure is shown. In some examples, the process flow 400 can implement aspects of the wireless communication systems 100 and 200. The process flow 400 includes a UE 115-a, which can be an example of a UE 115 as described herein. The process flow 400 also includes a base station 105-a, which can be an example of a base station 105 as described herein.

[0117] At 405, UE 115-b may receive first control signaling indicating a first RNTI identifier and a first feedback process identifier (eg, a first HPID). The first RNTI may indicate scheduling of unicast downlink transmissions. For example, the first RNTI may be a C-RNTI.

[0118] At 410, UE 115-b may receive second control signaling indicating a second RNTI and a second feedback process identifier (e.g., a second HPID). The second RNTI may indicate scheduling of multicast downlink transmissions. For example, the second RNTI may be an M-RNTI.

[0119] In some cases, UE 115-b may also receive control signaling indicating a buffer storage configuration for storing data associated with the multicast downlink transmission in the buffer.UE 115-b may identify assignment of a second feedback process identifier for the multicast downlink transmission based on receiving the second control signaling.

[0120] In some cases, UE 115-b may receive configuration signaling indicating a semi-static assignment of a first set of feedback process identifiers for unicast downlink transmissions and a second set of feedback process identifiers for multicast downlink transmissions. In these cases, UE 115-b may also identify a first data rate for multicast downlink transmissions and a second data rate for unicast downlink transmissions, wherein the first data rate and the second data rate are semi-statically configured based on the CC data rate. For example, the first data rate and the second data rate may be subject to a maximum or limited CC data rate based on each CC. In these cases, UE 115-b may also identify a first feedback process identifier from the first feedback process identifier set, and UE 115-b may identify a second feedback process identifier from the second feedback process identifier set.

[0121] In some cases, UE 115-b may receive configuration signaling indicating a first feedback processing timeline for unicast downlink transmissions and a second feedback processing timeline for multicast downlink transmissions, wherein the first feedback processing timeline is different from the second feedback processing timeline.

[0122] At 415, UE 115-b may manage feedback and buffering processes (e.g., HARQ processes) associated with unicast downlink transmissions and multicast downlink transmissions at UE 115-b based on the first RNTI, the first feedback process identifier, the second RNTI, and the second feedback process identifier. For example, as described herein, in some cases UE 115-b may handle a multicast transmission as a unicast transmission by applying feedback process handling rules to the multicast transmission as if it were a unicast transmission.

[0123] UE 115-b may apply one or more feedback process handling rules to unicast downlink transmissions and multicast downlink transmissions based on a single feedback and buffering process for the unicast downlink transmissions and the multicast downlink transmissions. UE 115-b may also identify a first data rate for the multicast downlink transmission and a second data rate for the unicast downlink transmission, wherein the first data rate and the second data rate are dynamically configured based on the CC data rate.

[0124] In some cases, UE 115-b may store data associated with the multicast downlink transmission in a buffer.UE 115-b may mark the stored data associated with the multicast downlink transmission with a second feedback process identifier.

[0125] In some cases, UE 115-b may determine to avoid storing data associated with the multicast downlink transmission in a buffer based on the second feedback process identifier.

[0126] In some cases, UE 115-b may determine that the first feedback process identifier and the second feedback process identifier correspond to the same feedback process identifier value and the first RNTI is different from the second RNTI. UE 115-b may then flush the stored data from the buffer based on determining that the first feedback process identifier and the second feedback process identifier correspond to the same identifier value and the first RNTI is different from the second RNTI.

[0127] In the event that UE 115-b receives configuration signaling indicating a semi-static assignment of a feedback process identifier, UE 115-b may manage a first feedback and buffering process for unicast downlink transmissions. UE 115-b may manage a second feedback and buffering process for multicast downlink transmissions, wherein the second feedback and buffering process is managed in parallel with the first feedback and buffering process. For example, the first feedback and buffering process may occur based on a unicast soft buffer, and the second feedback and buffering process may occur based on a different multicast soft buffer. UE 115-b may apply one or more feedback process processing rules to both unicast downlink transmissions and multicast downlink transmissions across the first feedback and buffering process and the second feedback and buffering process.

[0128] UE 115-b may also identify non-sequential ordering between downlink data transmissions and corresponding feedback process identifiers across a first feedback and buffering process and a second feedback and buffering process. Alternatively, UE 115-b may identify non-sequential ordering between control channel transmissions and corresponding data transmissions across a first feedback and buffering process and a second feedback and buffering process. In either case, UE 115-b may receive configuration signaling that configures a first PDCCH candidate set for a first control signaling indicating a first RNTI and a second PDCCH set for a second control signaling indicating a second RNTI.

[0129] UE 115-b may determine that the first feedback process identifier and the second feedback process identifier correspond to the same feedback process identifier value, and also determine that the first RNTI is different from the second RNTI. In these cases, UE 115-b may store data associated with unicast downlink transmissions in a first buffer according to the first feedback and buffering process. UE 115-b may also store data associated with multicast downlink transmissions in a second buffer according to the second feedback and buffering process.

[0130] Figure 4 An example of a process flow 500 for supporting multicast transmission feedback and buffer handling in accordance with aspects of the present disclosure is shown. In some examples, the process flow 500 can implement aspects of the wireless communication systems 100 and 200. The process flow 500 includes a UE 115-c, which can be an example of a UE 115 as described herein. The process flow 500 also includes a base station 105-c, which can be an example of a base station 105 as described herein.

[0131] At 505, the UE 115-c may receive broadcast signaling from the base station 105-b having a period above a first threshold, a TB size below a second threshold, or both. In some cases, the UE 115-c may receive configuration signaling indicating a processing allocation of a baseband processing budget between broadcast signaling processing, unicast signaling processing, and multicast signaling processing.

[0132] At 510, UE 115-c may receive a multicast downlink transmission configured without feedback processing. In some cases, UE 115-c may receive a unicast downlink transmission. In some cases, the multicast downlink transmission is received and processed when UE 115-c is in an idle state or an inactive state.

[0133] At 515, the UE 115-c may process the multicast downlink transmission and the broadcast signaling during the same time period (e.g., simultaneously) based on the remaining portion of the baseband processing budget for the broadcast signaling processing. The UE 115-c may process the unicast downlink transmission, the multicast downlink transmission, and / or the broadcast signaling during the same time period based on the remaining portion of the baseband processing budget for the broadcast signaling processing. The combined data rate for the unicast transmission and the multicast downlink transmission is less than the CC data rate.

[0134] Figure 6 A block diagram 600 of a device 605 supporting multicast transmission feedback and buffer handling according to aspects of the present disclosure is shown. The device 605 may be an example of aspects of the UE 115 as described herein. The device 605 may include a receiver 610, a communication manager 615, and a transmitter 620. The device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0135] The receiver 610 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to multicast transmission feedback and buffering, etc.). The information may be communicated to other components of the device 605. The receiver 610 may be a reference Fig. 9 Examples of various aspects of the transceiver 920 are described. The receiver 610 may utilize a single antenna or a group of antennas.

[0136] The communication manager 615 may perform the following operations: receiving a first control signaling indicating a first RNTI and a first feedback process identifier, wherein the first RNTI indicates scheduling of unicast downlink transmission; receiving a second control signaling indicating a second RNTI and a second feedback process identifier, wherein the second RNTI indicates scheduling of multicast downlink transmission; and managing HARQ processes associated with unicast downlink transmission and multicast downlink transmission at the UE based on the first RNTI, the first feedback process identifier, the second RNTI, and the second feedback process identifier. The communication manager 615 may also perform the following operations: receiving broadcast signaling having a period above a first threshold, a transport block size below a second threshold, or both; receiving multicast downlink transmission configured without feedback processing; and processing multicast downlink transmission and broadcast signaling during the same time period based on the remaining portion of the baseband processing budget for broadcast signaling processing. The communication manager 615 may be an example of various aspects of the communication manager 910 described herein.

[0137] The communication manager 615 or its subcomponents may be implemented in hardware, in code (e.g., software or firmware) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 615 or its subcomponents may be performed by a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure.

[0138] The communication manager 615 or its subcomponents may be physically located at various locations, including being distributed so that portions of the functions are implemented by one or more physical components at different physical locations. In some examples, according to various aspects of the present disclosure, the communication manager 615 or its subcomponents may be separate and distinct components. In some examples, according to various aspects of the present disclosure, the communication manager 615 or its subcomponents may be combined with one or more other hardware components (including, but not limited to, input / output (I / O) components, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof).

[0139] The transmitter 620 can transmit signals generated by other components of the device 605. In some examples, the transmitter 620 can be co-located with the receiver 610 in a transceiver module. For example, the transmitter 620 can be a reference Fig. 9 Examples of aspects of the transceiver 920 are described. The transmitter 620 may utilize a single antenna or a group of antennas.

[0140] In some examples, the communication manager 615 described herein may be implemented as a chipset for a wireless modem, and the receiver 610 and the transmitter 620 may be implemented as a collection of analog components (e.g., amplifiers, filters, phase shifters, antennas, etc.). The wireless modem may obtain and decode a signal from the receiver 610 through a receive interface, and may output a signal for transmission to the transmitter 620 through a transmit interface.

[0141] The operations performed by the UE communication manager 615 as described herein may be implemented to achieve one or more potential advantages. An implementation may allow the UE 115 to save power and extend battery life by improving efficiency and communication reliability. The UE 115 may be configured to efficiently manage unicast buffers and multicast buffers to simultaneously manage HARQ feedback for both types of communications. The improved HARQ feedback may also improve efficiency by reducing the number of retransmissions performed by the base station.

[0142] Figure 7 A block diagram 700 of a device 705 supporting multicast transmission feedback and buffer handling according to aspects of the present disclosure is shown. The device 705 may be an example of aspects of the device 605 or UE 115 as described herein. The device 705 may include a receiver 710, a communication manager 715, and a transmitter 750. The device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0143] The receiver 710 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to multicast transmission feedback and buffering, etc.). The information may be communicated to other components of the device 705. The receiver 710 may be a reference Fig. 9 Examples of various aspects of the transceiver 920 are described. The receiver 710 may utilize a single antenna or a group of antennas.

[0144] The communication manager 715 may be an example of aspects of the communication manager 615 as described herein. The communication manager 715 may include a unicast control component 720, a multicast control component 725, a buffer processing component 730, a broadcast reception component 735, a multicast downlink component 740, and a downlink processing component 745. The communication manager 715 may be an example of aspects of the communication manager 910 as described herein.

[0145] The unicast control component 720 can receive first control signaling indicating a first RNTI and a first feedback process identifier, wherein the first RNTI indicates scheduling of unicast downlink transmissions.

[0146] The multicast control component 725 can receive second control signaling indicating a second RNTI and a second feedback process identifier, wherein the second RNTI indicates scheduling of multicast downlink transmissions.

[0147] The buffer handling component 730 can manage HARQ processes associated with unicast downlink transmissions and multicast downlink transmissions at the UE based on the first RNTI, the first feedback process identifier, the second RNTI, and the second feedback process identifier.

[0148] The broadcast receiving component 735 can receive broadcast signaling having a periodicity above a first threshold, a transport block size below a second threshold, or both.

[0149] Multicast downlink component 740 can receive multicast downlink transmissions configured without feedback processing.

[0150] Downlink processing component 745 can process multicast downlink transmissions and broadcast signaling during the same time period based on the remaining portion of the baseband processing budget used for broadcast signaling processing.

[0151] The transmitter 750 can transmit signals generated by other components of the device 705. In some examples, the transmitter 750 can be co-located with the receiver 710 in a transceiver module. For example, the transmitter 750 can be a reference Fig. 9 Examples of aspects of the transceiver 920 are described. The transmitter 750 may utilize a single antenna or a group of antennas.

[0152] A processor of UE 115 (eg, controlling receiver 710, transmitter 750, or Fig. 9 The transceiver 920 described herein can operate the components described herein to achieve one or more potential advantages. For example, the processor can operate the receiver 710 to receive a first control signaling indicating a first RNTI and a first HPID for unicast transmission, and can also receive a second control signaling indicating a second RNTI and a second HPID. The processor can operate the HARQ process to efficiently manage multiple types of data in multiple buffers. This can improve efficiency and communication reliability by providing flexibility in the HARQ feedback process, which can further reduce the number of retransmissions performed by the base station 105.

[0153] The process may also operate the receiver 710 to receive broadcast signaling and receive multicast transmissions. The processor may process the multicast transmissions and the broadcast signaling during the same time period. This may improve efficiency and communication reliability by providing synchronous processing and may further reduce the number of retransmissions performed by the base station 105.

[0154] Figure 8A block diagram 800 of a communication manager 805 supporting multicast transmission feedback and buffer handling in accordance with aspects of the present disclosure is shown. The communication manager 805 can be an example of aspects of the communication manager 615, the communication manager 715, or the communication manager 910 described herein. The communication manager 805 can include a unicast control component 810, a multicast control component 815, a buffer handling component 820, an assignment component 825, a data storage component 830, a data tagging component 835, a feedback identifier component 840, a broadcast reception component 845, a multicast downlink component 850, a downlink processing component 855, a unicast downlink component 860, and a processing budget component 865. Each of these modules can communicate with each other directly or indirectly (e.g., via one or more buses).

[0155] The unicast control component 810 can receive first control signaling indicating a first RNTI and a first feedback process identifier, wherein the first RNTI indicates scheduling of unicast downlink transmissions.

[0156] The multicast control component 815 can receive second control signaling indicating a second RNTI and a second feedback process identifier, wherein the second RNTI indicates scheduling of multicast downlink transmissions.

[0157] The buffer handling component 820 can manage HARQ processes associated with unicast downlink transmissions and multicast downlink transmissions at the UE based on the first RNTI, the first feedback process identifier, the second RNTI, and the second feedback process identifier.

[0158] In some examples, buffer processing component 820 can apply one or more feedback process handling rules to unicast downlink transmissions and multicast downlink transmissions according to a single HARQ process for the unicast downlink transmissions and multicast downlink transmissions.

[0159] In some examples, the buffer processing component 820 can identify a first data rate for multicast downlink transmissions and a second data rate for unicast downlink transmissions, wherein the first data rate and the second data rate are dynamically configured based on the CC data rate.

[0160] In some examples, the buffer processing component 820 can manage a first HARQ process for a unicast downlink transmission.

[0161] In some examples, the buffer processing component 820 can manage a second HARQ process for multicast downlink transmissions, wherein the second HARQ process is managed in parallel with the first HARQ process.

[0162] In some examples, the buffer handling component 820 can apply one or more feedback process handling rules to both unicast downlink transmissions and multicast downlink transmissions across the first HARQ process and the second HARQ process.

[0163] In some examples, buffer processing component 820 can receive configuration signaling indicating a first feedback processing timeline for unicast downlink transmissions and a second feedback processing timeline for multicast downlink transmissions, wherein the first feedback processing timeline is different from the second feedback processing timeline.

[0164] The broadcast receiving component 845 can receive broadcast signaling having a periodicity above a first threshold, a transport block size below a second threshold, or both.

[0165] Multicast downlink component 850 can receive multicast downlink transmissions configured without feedback processing.

[0166] In some cases, multicast downlink transmissions are received and processed while the UE is in an idle or inactive state.

[0167] The downlink processing component 855 can process the multicast downlink transmission and the broadcast signaling during the same time period based on the remaining portion of the baseband processing budget used for broadcast signaling processing.

[0168] In some examples, the downlink processing component 855 can process unicast downlink transmissions, multicast downlink transmissions, and broadcast signaling during the same time period based on the remaining portion of the baseband processing budget used for broadcast signaling processing.

[0169] In some cases, the combined data rate for unicast downlink transmissions and multicast downlink transmissions is less than the CC data rate.

[0170] Assigning component 825 can identify assignment of a second feedback process identifier for the multicast downlink transmission based on receiving the second control signaling.

[0171] Data storage component 830 can store data associated with the multicast downlink transmission in a buffer.

[0172] In some examples, data storage component 830 may determine to avoid storing data associated with the multicast downlink transmission in the buffer based on the second feedback process identifier.

[0173] In some examples, data storage component 830 may receive control signaling indicating a buffer storage configuration for storing data associated with a multicast downlink transmission in a buffer.

[0174] In some examples, the data storage component 830 can flush the stored data from the buffer based on determining that the first feedback process identifier and the second feedback process identifier correspond to the same identifier value and the first RNTI is different from the second RNTI.

[0175] In some examples, data storage component 830 can identify a first data rate for multicast downlink transmissions and a second data rate for unicast downlink transmissions, wherein the first data rate and the second data rate are semi-statically configured based on the CC data rate.

[0176] In some examples, data storage component 830 may store data associated with a unicast downlink transmission in a first buffer according to a first HARQ process.

[0177] In some examples, data storage component 830 may store data associated with the multicast downlink transmission in a second buffer according to a second HARQ process.

[0178] Data marking component 835 can mark stored data associated with the multicast downlink transmission with a second feedback process identifier.

[0179] Feedback identifier component 840 can determine that the first feedback process identifier and the second feedback process identifier correspond to the same feedback process identifier value and that the first RNTI is different than the second RNTI.

[0180] In some examples, feedback identifier component 840 can receive configuration signaling indicating a semi-static assignment of a first set of feedback process identifiers for unicast downlink transmissions and a second set of feedback process identifiers for multicast downlink transmissions.

[0181] In some examples, the feedback identifier component 840 can identify non-sequential ordering between downlink data transmissions and corresponding feedback process identifiers across a first HARQ process and a second HARQ process, or non-sequential ordering between control channel transmissions and corresponding data transmissions across a first HARQ process and a second HARQ process.

[0182] In some examples, feedback identifier component 840 may receive configuration signaling that configures a first physical downlink control channel candidate set for first control signaling indicating a first RNTI and a second physical downlink control channel candidate set for second control signaling indicating a second RNTI.

[0183] In some examples, feedback identifier component 840 can determine that the first feedback process identifier and the second feedback process identifier correspond to the same feedback process identifier value and that the first RNTI is different from the second RNTI.

[0184] In some examples, feedback identifier component 840 can identify the first feedback process identifier from the first set of feedback process identifiers.

[0185] In some examples, feedback identifier component 840 can identify the second feedback process identifier from the set of second feedback process identifiers.

[0186] Unicast downlink component 860 can receive unicast downlink transmissions.

[0187] The processing budget component 865 can receive configuration signaling indicating a processing allocation of the baseband processing budget between broadcast signaling processing, unicast signaling processing, and multicast signaling processing.

[0188] Fig. 9 A diagram of a system 900 including a device 905 supporting multicast transmission feedback and buffer handling according to aspects of the present disclosure is shown. The device 905 may be an example of or include a component of a device 605, a device 705, or a UE 115 as described herein. The device 905 may include components for two-way voice and data communications, including components for sending and receiving communications, including a communication manager 910, an I / O controller 915, a transceiver 920, an antenna 925, a memory 930, and a processor 940. These components may communicate electronically via one or more buses (e.g., a bus 945).

[0189] The communication manager 910 may perform the following operations: receiving a first control signaling indicating a first RNTI and a first feedback process identifier, wherein the first RNTI indicates scheduling of a unicast downlink transmission; receiving a second control signaling indicating a second RNTI and a second feedback process identifier, wherein the second RNTI indicates scheduling of a multicast downlink transmission; and managing HARQ processes associated with unicast downlink transmission and multicast downlink transmission at the UE based on the first RNTI, the first feedback process identifier, the second RNTI, and the second feedback process identifier. The communication manager 910 may also perform the following operations: receiving broadcast signaling having a period above a first threshold, a transport block size below a second threshold, or both; receiving a multicast downlink transmission configured without feedback processing; and processing the multicast downlink transmission and the broadcast signaling during the same time period based on the remaining portion of the baseband processing budget for broadcast signaling processing.

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

[0191] The transceiver 920 may communicate bidirectionally via one or more antennas, wired or wireless links as described above. For example, the transceiver 920 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 920 may also include a modem for modulating packets and providing the modulated packets to an antenna for transmission, and demodulating packets received from an antenna.

[0192] In some cases, a wireless device may include a single antenna 925. However, in some cases, the device may have more than one antenna 925 that are capable of sending or receiving multiple wireless transmissions simultaneously.

[0193] The memory 930 may include random access memory (RAM) and read-only memory (ROM). The memory 930 may store computer-readable, computer-executable code 935, which includes instructions that, when executed, cause the processor to perform various functions described herein. In some cases, the memory 930 may also contain, among other things, a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0194] The processor 940 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 940 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into the processor 940. The processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 930) to cause the device 905 to perform various functions (e.g., functions or tasks that support multicast transmission feedback and buffer processing).

[0195] The code 935 may include instructions for implementing various aspects of the present disclosure, including instructions for supporting wireless communications. The code 935 may be stored in a non-transitory computer-readable medium (e.g., system memory or other types of memory). In some cases, the code 935 may not be directly executable by the processor 940, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0196] Fig.10 A flow chart illustrating a method 1000 for supporting multicast transmission feedback and buffering processing according to aspects of the present disclosure is shown. The operations of the method 1000 may be implemented by a UE 115 or a component thereof as described herein. For example, the operations of the method 1000 may be implemented by a UE 115 or a component thereof as described herein. Figures 6 to 9 In some examples, the UE may execute an instruction set to control the functional units of the UE to perform the functions described herein. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described herein.

[0197] At 1005, the UE may receive first control signaling indicating a first RNTI and a first feedback process identifier, wherein the first RNTI indicates scheduling of unicast downlink transmissions. The operations of 1005 may be performed according to the methods described herein. In some examples, aspects of the operations of 1005 may be performed as described with reference to Figures 6 to 9 Additionally or alternatively, the means for executing 1005 may, but need not necessarily include, for example, an antenna 925, a transceiver 920, a communication manager 910, a memory 930 (including code 935), a processor 940, and / or a bus 945.

[0198] At 1010, the UE may receive second control signaling indicating a second RNTI and a second feedback process identifier, wherein the second RNTI indicates scheduling of multicast downlink transmissions. The operations of 1010 may be performed according to the methods described herein. In some examples, aspects of the operations of 1010 may be performed as described with reference to Figures 6 to 9 Additionally or alternatively, the means for executing 1010 may, but need not necessarily include, for example, an antenna 925, a transceiver 920, a communication manager 910, a memory 930 (including code 935), a processor 940, and / or a bus 945.

[0199] At 1015, the UE may manage HARQ processes associated with unicast downlink transmissions and multicast downlink transmissions at the UE based on the first RNTI, the first feedback process identifier, the second RNTI, and the second feedback process identifier. The operations of 1015 may be performed according to the methods described herein. In some examples, aspects of the operations of 1015 may be performed as described with reference to Figures 6 to 9 Additionally or alternatively, the means for executing 1015 may, but need not necessarily include, for example, an antenna 925, a transceiver 920, a communication manager 910, a memory 930 (including code 935), a processor 940, and / or a bus 945.

[0200] Fig.11 A flow chart illustrating a method 1100 for supporting multicast transmission feedback and buffering processing according to aspects of the present disclosure is shown. The operations of the method 1100 may be implemented by a UE 115 or a component thereof as described herein. For example, the operations of the method 1100 may be implemented by a UE 115 or a component thereof as described herein. Figures 6 to 9 In some examples, the UE may execute an instruction set to control the functional units of the UE to perform the functions described herein. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described herein.

[0201] At 1105, the UE may receive first control signaling indicating a first RNTI and a first feedback process identifier, wherein the first RNTI indicates scheduling of unicast downlink transmissions. The operations of 1105 may be performed according to the methods described herein. In some examples, aspects of the operations of 1105 may be as described with reference to Figures 6 to 9 Additionally or alternatively, the means for executing 1105 may, but need not necessarily include, for example, antenna 925, transceiver 920, communication manager 910, memory 930 (including code 935), processor 940, and / or bus 945.

[0202] At 1110, the UE may receive second control signaling indicating a second RNTI and a second feedback process identifier, wherein the second RNTI indicates scheduling of multicast downlink transmissions. The operations of 1110 may be performed according to the methods described herein. In some examples, aspects of the operations of 1110 may be performed as described with reference to Figures 6 to 9Additionally or alternatively, the means for executing 1110 may, but need not necessarily include, for example, an antenna 925, a transceiver 920, a communication manager 910, a memory 930 (including code 935), a processor 940, and / or a bus 945.

[0203] At 1115, the UE may identify the assignment of a second feedback process identifier for the multicast downlink transmission based on receiving the second control signaling. The operations of 1115 may be performed according to the methods described herein. In some examples, aspects of the operations of 1115 may be performed as described with reference to Figures 6 to 9 Additionally or alternatively, the means for executing 1115 may, but need not necessarily include, for example, an antenna 925, a transceiver 920, a communication manager 910, a memory 930 (including code 935), a processor 940, and / or a bus 945.

[0204] At 1120, the UE may manage HARQ processes associated with unicast downlink transmissions and multicast downlink transmissions at the UE based on the first RNTI, the first feedback process identifier, the second RNTI, and the second feedback process identifier. The operations of 1120 may be performed according to the methods described herein. In some examples, aspects of the operations of 1120 may be performed as described with reference to Figures 6 to 9 Additionally or alternatively, the means for executing 1120 may, but need not necessarily include, for example, an antenna 925, a transceiver 920, a communication manager 910, a memory 930 (including code 935), a processor 940, and / or a bus 945.

[0205] Fig.12 A flow chart illustrating a method 1200 for supporting multicast transmission feedback and buffering processing according to aspects of the present disclosure is shown. The operations of the method 1200 may be implemented by a UE 115 or a component thereof as described herein. For example, the operations of the method 1200 may be implemented by a UE 115 or a component thereof as described herein. Figures 6 to 9 In some examples, the UE may execute an instruction set to control the functional units of the UE to perform the functions described herein. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described herein.

[0206] At 1205, the UE may receive configuration signaling indicating a semi-static assignment of a first feedback process identifier set for unicast downlink transmissions and a second feedback process identifier set for multicast downlink transmissions. The operations of 1205 may be performed according to the methods described herein. In some examples, aspects of the operations of 1205 may be performed as described with reference to Figures 6 to 9Additionally or alternatively, the means for performing 1205 may, but need not necessarily include, for example, antenna 925, transceiver 920, communication manager 910, memory 930 (including code 935), processor 940, and / or bus 945.

[0207] At 1210, the UE may receive first control signaling indicating a first RNTI and a first feedback process identifier, wherein the first RNTI indicates scheduling of unicast downlink transmissions. The operations of 1210 may be performed according to the methods described herein. In some examples, aspects of the operations of 1210 may be as described with reference to Figures 6 to 9 Additionally or alternatively, the means for executing 1210 may, but need not necessarily include, for example, an antenna 925, a transceiver 920, a communication manager 910, a memory 930 (including code 935), a processor 940, and / or a bus 945.

[0208] At 1215, the UE may receive second control signaling indicating a second RNTI and a second feedback process identifier, wherein the second RNTI indicates scheduling of multicast downlink transmissions. The operations of 1215 may be performed according to the methods described herein. In some examples, aspects of the operations of 1215 may be performed as described with reference to Figures 6 to 9 Additionally or alternatively, the means for executing 1215 may, but need not necessarily include, for example, an antenna 925, a transceiver 920, a communication manager 910, a memory 930 (including code 935), a processor 940, and / or a bus 945.

[0209] At 1220, the UE may manage HARQ processes associated with unicast downlink transmissions and multicast downlink transmissions at the UE based on the first RNTI, the first feedback process identifier, the second RNTI, and the second feedback process identifier. The operations of 1220 may be performed according to the methods described herein. In some examples, aspects of the operations of 1220 may be as described with reference to Figures 6 to 9 Additionally or alternatively, the means for executing 1220 may, but need not necessarily include, for example, an antenna 925, a transceiver 920, a communication manager 910, a memory 930 (including code 935), a processor 940, and / or a bus 945.

[0210] Fig.13 A flow chart illustrating a method 1300 for supporting multicast transmission feedback and buffering processing according to aspects of the present disclosure is shown. The operations of the method 1300 may be implemented by the UE 115 or its components as described herein. For example, the operations of the method 1300 may be implemented by the UE 115 or its components as described with reference to Figures 6 to 9In some examples, the UE may execute an instruction set to control the functional units of the UE to perform the functions described herein. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described herein.

[0211] At 1305, the UE may receive broadcast signaling having a period above a first threshold, a transport block size below a second threshold, or both. The operations of 1305 may be performed according to the methods described herein. In some examples, aspects of the operations of 1305 may be as described with reference to Figures 6 to 9 Additionally or alternatively, the means for executing 1305 may, but need not necessarily include, for example, an antenna 925, a transceiver 920, a communication manager 910, a memory 930 (including code 935), a processor 940, and / or a bus 945.

[0212] At 1310, the UE may receive a multicast downlink transmission configured without feedback processing. The operations of 1310 may be performed according to the methods described herein. In some examples, aspects of the operations of 1310 may be performed as described with reference to Figures 6 to 9 Additionally or alternatively, the means for performing 1310 may, but need not necessarily include, for example, antenna 925, transceiver 920, communication manager 910, memory 930 (including code 935), processor 940, and / or bus 945.

[0213] At 1315, the UE may process the multicast downlink transmission and the broadcast signaling during the same time period based on the remaining portion of the baseband processing budget used for broadcast signaling processing. The operations of 1315 may be performed according to the methods described herein. In some examples, aspects of the operations of 1315 may be performed as described with reference to Figures 6 to 9 Additionally or alternatively, the means for executing 1315 may, but need not necessarily include, for example, antenna 925, transceiver 920, communication manager 910, memory 930 (including code 935), processor 940, and / or bus 945.

[0214] The following provides a summary of various aspects of the disclosure:

[0215] Aspect 1: A method for wireless communication at a UE, comprising: receiving first control signaling indicating a first radio network temporary identifier and a first feedback process identifier, wherein the first radio network temporary identifier indicates scheduling of a unicast downlink transmission; receiving second control signaling indicating a second radio network temporary identifier and a second feedback process identifier, wherein the second radio network temporary identifier indicates scheduling of a multicast downlink transmission; and managing a HARQ process associated with the unicast downlink transmission and the multicast downlink transmission at the UE based at least in part on the first radio network temporary identifier, the first feedback process identifier, the second radio network temporary identifier, and the second feedback process identifier.

[0216] Aspect 2: The method according to aspect 1 further includes: identifying the assignment of the second feedback process identifier for the multicast downlink transmission based at least in part on receiving the second control signaling.

[0217] Aspect 3: The method according to aspect 2 further includes: storing data associated with the multicast downlink transmission in a buffer; and marking the stored data associated with the multicast downlink transmission with the second feedback process identifier.

[0218] Aspect 4: The method according to any one of aspects 2 to 3 further includes: determining to avoid storing data associated with the multicast downlink transmission in a buffer based at least in part on the second feedback process identifier.

[0219] Aspect 5: The method according to any one of aspects 2 to 4 further comprises: receiving control signaling indicating a buffer storage configuration for storing data associated with the multicast downlink transmission in a buffer.

[0220] Aspect 6: The method according to any one of Aspects 2 to 5 further includes: determining that the first feedback process identifier and the second feedback process identifier correspond to the same feedback process identifier value and the first radio network temporary identifier is different from the second radio network temporary identifier; and refreshing the stored data from the buffer based at least in part on determining that the first feedback process identifier and the second feedback process identifier correspond to the same identifier value and the first radio network temporary identifier is different from the second radio network temporary identifier.

[0221] Aspect 7: The method according to any one of Aspects 2 to 6 further includes: applying one or more feedback process processing rules to the unicast downlink transmission and the multicast downlink transmission according to a single HARQ process used for the unicast downlink transmission and the multicast downlink transmission.

[0222] Aspect 8: The method according to any one of Aspects 2 to 7 further includes: identifying a first data rate for the multicast downlink transmission and a second data rate for the unicast downlink transmission, wherein the first data rate and the second data rate are dynamically configured at least in part based on a component carrier data rate.

[0223] Aspect 9: The method according to any one of Aspects 1 to 8 further includes: receiving configuration signaling indicating a semi-static assignment of a first plurality of feedback process identifiers for unicast downlink transmission and a second plurality of feedback process identifiers for multicast downlink transmission.

[0224] Aspect 10: The method according to Aspect 9 further includes: managing a first HARQ process for the unicast downlink transmission; and managing a second HARQ process for the multicast downlink transmission, wherein the second HARQ process is managed in parallel with the first HARQ process.

[0225] Aspect 11: The method according to aspect 10 further includes: applying one or more feedback process handling rules to both the unicast downlink transmission and the multicast downlink transmission across the first HARQ process and the second HARQ process.

[0226] Aspect 12: The method according to any one of Aspects 10 to 11 also includes: identifying non-sequential ordering between downlink data transmission and corresponding feedback process identifiers across the first HARQ process and the second HARQ process, or non-sequential ordering between control channel transmission and corresponding data transmission across the first HARQ process and the second HARQ process.

[0227] Aspect 13: The method according to Aspect 12 also includes: receiving configuration signaling, wherein the configuration signaling configures a first physical downlink control channel candidate set for the first control signaling indicating the first radio network temporary identifier and configures a second physical downlink control channel candidate set for the second control signaling indicating the second radio network temporary identifier.

[0228] Aspect 14: The method according to any one of Aspects 10 to 13 further includes: receiving configuration signaling, the configuration signaling indicating a first feedback processing timeline for the unicast downlink transmission and a second feedback processing timeline for the multicast downlink transmission, wherein the first feedback processing timeline is different from the second feedback processing timeline.

[0229] Aspect 15: The method according to any one of Aspects 10 to 14 further includes: identifying a first data rate for the multicast downlink transmission and a second data rate for the unicast downlink transmission, wherein the first data rate and the second data rate are semi-statically configured at least in part based on a component carrier data rate.

[0230] Aspect 16: The method according to any one of Aspects 10 to 15 further includes: determining that the first feedback process identifier and the second feedback process identifier correspond to the same feedback process identifier value and that the first radio network temporary identifier is different from the second radio network temporary identifier; storing data associated with the unicast downlink transmission in a first buffer according to the first HARQ process; and storing data associated with the multicast downlink transmission in a second buffer according to the second HARQ process.

[0231] Aspect 17: The method according to any one of Aspects 9 to 16 further includes: identifying the first feedback process identifier from the first plurality of feedback process identifiers; and identifying the second feedback process identifier from the second plurality of feedback process identifiers.

[0232] Aspect 18: A method for wireless communication at a UE, comprising: receiving broadcast signaling having a period above a first threshold, a transmission block size below a second threshold, or both; receiving a multicast downlink transmission configured without feedback processing; and processing the multicast downlink transmission and the broadcast signaling during the same time period based at least in part on a remaining portion of a baseband processing budget for broadcast signaling processing.

[0233] Aspect 19: The method according to Aspect 18 further includes: receiving a unicast downlink transmission; and processing the unicast downlink transmission, the multicast downlink transmission, and the broadcast signaling during the same time period based at least in part on the remaining portion of the baseband processing budget used for broadcast signaling processing.

[0234] Aspect 20: The method according to aspect 19, wherein a combined data rate for the unicast downlink transmission and the multicast downlink transmission is less than a component carrier data rate.

[0235] Aspect 21: The method according to any one of aspects 18 to 20 further comprises: receiving configuration signaling indicating a processing allocation of a baseband processing budget between broadcast signaling processing, unicast signaling processing and multicast signaling processing.

[0236] Aspect 22: The method according to any one of aspects 18 to 21, wherein the multicast downlink transmission is received and processed when the UE is in an idle state or an inactive state.

[0237] Aspect 23: An apparatus for wireless communication at a UE, comprising: a processor; a memory coupled to the processor; and instructions, which are stored in the memory and can be executed by the processor to enable the apparatus to perform a method according to any one of Aspects 1 to 17.

[0238] Aspect 24: An apparatus for wireless communication at a UE, comprising at least one unit for performing the method according to any one of aspects 1 to 17.

[0239] Aspect 25: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 17.

[0240] Aspect 26: An apparatus for wireless communication at a UE, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of aspects 18 to 22.

[0241] Aspect 27: An apparatus for wireless communication at a UE, comprising at least one unit for performing the method according to any one of aspects 18 to 22.

[0242] Aspect 28: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 18 to 22.

[0243] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified, and other implementations are possible. Furthermore, aspects from two or more methods may be combined.

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

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

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

[0247] 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 sent through a computer-readable medium as one or more instructions or codes. Other examples and implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented in software executed by a processor, hardware, firmware, hard wiring, or any combination of these. Features that implement the functions may also be physically located at various locations, including being distributed so that parts of the functions are implemented at different physical locations.

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

[0249] As used herein (including in the claims), "or" as used in a list of items (e.g., a list of items ending with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so 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). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0250] In the accompanying drawings, similar components or features may have the same reference numeral. In addition, various components of the same type may be distinguished by following the reference numeral with a dash and a second reference numeral, the second reference numeral being used to distinguish between similar components. If only the first reference numeral is used in the specification, the description applies to any of the similar components having the same first reference numeral, without regard to the second reference numeral or other subsequent reference numerals.

[0251] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations, and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "advantageous over other examples." For the purpose of providing an understanding of the described techniques, the detailed description includes specific details. However, these techniques may be implemented without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0252] To enable those skilled in the art to implement or use the present disclosure, the description herein is provided. It will be apparent to those skilled in the art that various modifications to the present disclosure will be apparent, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but is given the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a user equipment (UE), comprising: receiving first control signaling indicating a first radio network temporary identifier and a first feedback process identifier, wherein the first radio network temporary identifier indicates scheduling of a unicast downlink transmission; receiving second control signaling indicating a second radio network temporary identifier and a second feedback process identifier, wherein the second radio network temporary identifier indicates scheduling of a multicast downlink transmission, wherein a combined data rate for the unicast downlink transmission and the multicast downlink transmission is less than a component carrier data rate; and Processing the multicast downlink transmission or the unicast downlink transmission as a new data transmission regardless of whether a new data indicator value is switched in the first control signaling or the second control signaling, the processing being based at least in part on the first radio network temporary identifier, the first feedback process identifier, the second radio network temporary identifier, and the second feedback process identifier.

2. The method according to claim 1, further comprising: An assignment of the second feedback process identifier for the multicast downlink transmission is identified based at least in part on receiving the second control signaling.

3. The method according to claim 2, further comprising: storing data associated with the multicast downlink transmission in a buffer; as well as The stored data associated with the multicast downlink transmission is marked with the second feedback process identifier.

4. The method according to claim 2, further comprising: A determination is made based at least in part on the second feedback process identifier to avoid storing data associated with the multicast downlink transmission in a buffer.

5. The method according to claim 2, further comprising: Control signaling is received indicating a buffer storage configuration for storing data associated with the multicast downlink transmission in a buffer.

6. The method according to claim 2, further comprising: determining that the first feedback process identifier and the second feedback process identifier correspond to the same feedback process identifier value and the first radio network temporary identifier is different from the second radio network temporary identifier; as well as Based at least in part on determining that the first feedback process identifier and the second feedback process identifier correspond to the same identifier value and the first radio network temporary identifier is different from the second radio network temporary identifier, the stored data is flushed from the buffer.

7. The method according to claim 2, further comprising: One or more feedback process handling rules are applied to the unicast downlink transmission and the multicast downlink transmission according to a single hybrid automatic repeat request process for the unicast downlink transmission and the multicast downlink transmission.

8. The method according to claim 2, further comprising: A first data rate for the multicast downlink transmission and a second data rate for the unicast downlink transmission are identified, wherein the first data rate and the second data rate are dynamically configured based at least in part on a component carrier data rate.

9. The method according to claim 1, further comprising: Configuration signaling is received indicating a semi-static assignment of a first plurality of feedback process identifiers for unicast downlink transmissions and a second plurality of feedback process identifiers for multicast downlink transmissions.

10. The method according to claim 9, further comprising: managing a first hybrid automatic repeat request process for the unicast downlink transmission; as well as A second hybrid automatic repeat request process is managed for the multicast downlink transmission, wherein the second hybrid automatic repeat request process is managed in parallel with the first hybrid automatic repeat request process.

11. The method according to claim 10, further comprising: One or more feedback process handling rules are applied to both the unicast downlink transmission and the multicast downlink transmission across the first hybrid automatic repeat request process and the second hybrid automatic repeat request process.

12. The method according to claim 10, further comprising: Identify non-sequential ordering between downlink data transmissions and corresponding feedback process identifiers across the first hybrid automatic repeat request process and the second hybrid automatic repeat request process, or non-sequential ordering between control channel transmissions and corresponding data transmissions across the first hybrid automatic repeat request process and the second hybrid automatic repeat request process.

13. The method according to claim 1, further comprising: Configuration signaling is received, the configuration signaling configuring a first physical downlink control channel candidate set for the first control signaling indicating the first radio network temporary identifier and configuring a second physical downlink control channel candidate set for the second control signaling indicating the second radio network temporary identifier.

14. The method according to claim 1, further comprising: Configuration signaling is received, the configuration signaling indicating a first feedback processing timeline for the unicast downlink transmission and a second feedback processing timeline for the multicast downlink transmission, wherein the first feedback processing timeline is different from the second feedback processing timeline.

15. The method according to claim 10, further comprising: A first data rate for the multicast downlink transmission and a second data rate for the unicast downlink transmission are identified, wherein the first data rate and the second data rate are semi-statically configured based at least in part on the component carrier data rate.

16. The method according to claim 10, further comprising: determining that the first feedback process identifier and the second feedback process identifier correspond to the same feedback process identifier value and the first radio network temporary identifier is different from the second radio network temporary identifier; storing data associated with the unicast downlink transmission in a first buffer according to the first hybrid automatic repeat request process; as well as Data associated with the multicast downlink transmission is stored in a second buffer according to the second hybrid automatic repeat request process.

17. The method according to claim 9, further comprising: identifying the first feedback process identifier from among the first plurality of feedback process identifiers; as well as The second feedback process identifier is identified from the second plurality of feedback process identifiers.

18. An apparatus for wireless communication at a user equipment (UE), comprising: processor, a memory coupled to the processor; as well as Instructions, which are stored in the memory and can be executed by the processor to cause the device to perform the following operations: receiving first control signaling indicating a first radio network temporary identifier and a first feedback process identifier, wherein the first radio network temporary identifier indicates scheduling of a unicast downlink transmission; receiving second control signaling indicating a second radio network temporary identifier and a second feedback process identifier, wherein the second radio network temporary identifier indicates scheduling of a multicast downlink transmission, wherein a combined data rate for the unicast downlink transmission and the multicast downlink transmission is less than a component carrier data rate; and Processing the multicast downlink transmission or the unicast downlink transmission as a new data transmission regardless of whether a new data indicator value is switched in the first control signaling or the second control signaling, the processing being based at least in part on the first radio network temporary identifier, the first feedback process identifier, the second radio network temporary identifier, and the second feedback process identifier.

19. The device according to claim 18, wherein: The instructions may also be executed by the processor to cause the device to perform the following operations: An assignment of the second feedback process identifier for the multicast downlink transmission is identified based at least in part on receiving the second control signaling.

20. The device according to claim 19, wherein The instructions may also be executed by the processor to cause the device to perform the following operations: storing data associated with the multicast downlink transmission in a buffer; and The stored data associated with the multicast downlink transmission is marked with the second feedback process identifier.

21. The device according to claim 19, wherein The instructions may also be executed by the processor to cause the device to perform the following operations: A determination is made based at least in part on the second feedback process identifier to avoid storing data associated with the multicast downlink transmission in a buffer.

22. The device according to claim 19, wherein The instructions may also be executed by the processor to cause the device to perform the following operations: Control signaling is received indicating a buffer storage configuration for storing data associated with the multicast downlink transmission in a buffer.

23. The device according to claim 19, wherein: The instructions may also be executed by the processor to cause the device to perform the following operations: determining that the first feedback process identifier and the second feedback process identifier correspond to the same feedback process identifier value and the first radio network temporary identifier is different from the second radio network temporary identifier; as well as Based at least in part on determining that the first feedback process identifier and the second feedback process identifier correspond to the same identifier value and the first radio network temporary identifier is different from the second radio network temporary identifier, the stored data is flushed from the buffer.

24. The device according to claim 19, wherein The instructions may also be executed by the processor to cause the device to perform the following operations: One or more feedback process handling rules are applied to the unicast downlink transmission and the multicast downlink transmission according to a single hybrid automatic repeat request process for the unicast downlink transmission and the multicast downlink transmission.

25. The device according to claim 19, wherein The instructions may also be executed by the processor to cause the device to perform the following operations: A first data rate for the multicast downlink transmission and a second data rate for the unicast downlink transmission are identified, wherein the first data rate and the second data rate are dynamically configured based at least in part on the component carrier data rate.

26. The device according to claim 18, wherein The instructions may also be executed by the processor to cause the device to perform the following operations: Configuration signaling is received indicating a semi-static assignment of a first plurality of feedback process identifiers for unicast downlink transmissions and a second plurality of feedback process identifiers for multicast downlink transmissions.

27. The device according to claim 26, wherein: The instructions may also be executed by the processor to cause the device to perform the following operations: managing a first hybrid automatic repeat request process for the unicast downlink transmission; as well as A second hybrid automatic repeat request process is managed for the multicast downlink transmission, wherein the second hybrid automatic repeat request process is managed in parallel with the first hybrid automatic repeat request process.

28. The device according to claim 27, wherein The instructions may also be executed by the processor to cause the device to perform the following operations: One or more feedback process handling rules are applied to both the unicast downlink transmission and the multicast downlink transmission across the first hybrid automatic repeat request process and the second hybrid automatic repeat request process.

29. The device according to claim 27, wherein: The instructions may also be executed by the processor to cause the device to perform the following operations: Identify non-sequential ordering between downlink data transmissions and corresponding feedback process identifiers across the first hybrid automatic repeat request process and the second hybrid automatic repeat request process, or non-sequential ordering between control channel transmissions and corresponding data transmissions across the first hybrid automatic repeat request process and the second hybrid automatic repeat request process.

30. The apparatus of claim 18, wherein: The instructions may also be executed by the processor to cause the device to perform the following operations: Configuration signaling is received, the configuration signaling configuring a first physical downlink control channel candidate set for the first control signaling indicating the first radio network temporary identifier and configuring a second physical downlink control channel candidate set for the second control signaling indicating the second radio network temporary identifier.

31. The apparatus of claim 18, wherein: The instructions may also be executed by the processor to cause the device to perform the following operations: Configuration signaling is received, the configuration signaling indicating a first feedback processing timeline for the unicast downlink transmission and a second feedback processing timeline for the multicast downlink transmission, wherein the first feedback processing timeline is different from the second feedback processing timeline.

32. The apparatus of claim 27, wherein: The instructions may also be executed by the processor to cause the device to perform the following operations: A first data rate for the multicast downlink transmission and a second data rate for the unicast downlink transmission are identified, wherein the first data rate and the second data rate are semi-statically configured based at least in part on the component carrier data rate.

33. The apparatus of claim 27, wherein: The instructions may also be executed by the processor to cause the device to perform the following operations: determining that the first feedback process identifier and the second feedback process identifier correspond to the same feedback process identifier value and the first radio network temporary identifier is different from the second radio network temporary identifier; storing data associated with the unicast downlink transmission in a first buffer according to the first hybrid automatic repeat request process; as well as Data associated with the multicast downlink transmission is stored in a second buffer according to the second hybrid automatic repeat request process.

34. The apparatus of claim 26, wherein: The instructions may also be executed by the processor to cause the device to perform the following operations: identifying the first feedback process identifier from among the first plurality of feedback process identifiers; and The second feedback process identifier is identified from the second plurality of feedback process identifiers.

Images