WO2022016484A1

WO2022016484A1 - Downlink formats for multicast communications

Info

Publication number: WO2022016484A1
Application number: PCT/CN2020/104017
Authority: WO
Inventors: Min Huang; Chao Wei; Hao Xu
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2020-07-24
Filing date: 2020-07-24
Publication date: 2022-01-27
Anticipated expiration: 2023-01-24

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment may receive, from a base station, a configuration for a multicast session indicating a plurality of multicast downlink formats; and receive, from the base station and during the multicast session, a multicast downlink communication in accordance with a multicast downlink format of the plurality of multicast downlink formats. Numerous other aspects are provided.

Description

DOWNLINK FORMATS FOR MULTICAST COMMUNICATIONS

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wireless communication and specifically, to configuring downlink formats for multicast communications associated with a multicast session.

BACKGROUND

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (for example, bandwidth, or transmit power, among other examples, or a combination thereof) . Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency-division multiple access (FDMA) systems, orthogonal frequency-division multiple access (OFDMA) systems, single-carrier frequency-division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE) . LTE/LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP) .

The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different user equipments (UEs) to communicate on a municipal, national, regional, and even global level. New Radio (NR) , which may also be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by the 3GPP. NR is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink (DL) , using CP-OFDM or SC-FDMA (for example, also known as discrete Fourier transform spread OFDM (DFT-s-OFDM) ) on the uplink (UL) , as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. However, as the demand for mobile broadband access continues to increase, there exists a need for further improvements in LTE and NR technologies. Preferably, these improvements are applicable to other multiple access technologies and the telecommunication standards that employ these technologies.

In some wireless communication systems, a base station, for a multicast session, may schedule a single multicast physical downlink shared channel (PDSCH) communication to transmit a common data packet for multicast data for all UEs subscribed to (or configured with) the multicast session. The multicast PDSCH communication may be scheduled by a single downlink control information (DCI) in a physical downlink control channel (PDCCH) communication, which is decoded by all UEs subscribed to (or configured with) the multicast session. To ensure that reduced capability (RedCap) UEs subscribed to (or configured with) the multicast session are able to receive the multicast PDSCH communication, the base station may transmit the PDCCH communication and the multicast PDSCH communication using low transport formats (for example, a lower modulation and coding scheme, a lower modulation level, a lower coding rate, less spatial layers, a lower spectrum efficiency in a PDSCH, or a higher aggregation level in a PDCCH, among other examples) , more resources (for example, more time domain resources, more frequency domain resources, or more spatial domain resource) , among other examples, due to a lower communicative capability of RedCap UEs relative to baseline UEs. However, transmitting the PDCCH communication and the multicast PDSCH communication using low transport formats, or more resources, among other examples, may reduce throughput, increase latency, or increase power consumption, for baseline UEs.

SUMMARY

In some aspects, a method of wireless communication performed by a user equipment (UE) may include receiving, from a base station, a configuration for a multicast session indicating a plurality of multicast downlink formats. The method may include receiving, from the base station and during the multicast session, a multicast downlink communication in accordance with a multicast downlink format of the plurality of multicast downlink formats.

In some aspects, a method of wireless communication performed by a base station may include transmitting a configuration for a multicast session indicating a plurality of multicast downlink formats. The method may include transmitting, for multicast data, a plurality of multicast downlink communications associated with the multicast data in accordance with the plurality of multicast downlink formats.

In some aspects, a UE for wireless communication may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to receive, from a base station, a configuration for a multicast session indicating a plurality of multicast downlink formats. The memory and the one or more processors may be configured to receive, from the base station and during the multicast session, a multicast downlink communication in accordance with a multicast downlink format of the plurality of multicast downlink formats.

In some aspects, a base station for wireless communication may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to transmit a configuration for a multicast session indicating a plurality of multicast downlink formats. The memory and the one or more processors may be configured to transmit, for multicast data, a plurality of multicast downlink communications associated with the multicast data in accordance with the plurality of multicast downlink formats.

In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication may include one or more instructions that, when executed by one or more processors of a UE, may cause the UE to receive, from a base station, a configuration for a multicast session indicating a plurality of multicast downlink formats. In some aspects, the set of instructions for wireless communication may include one or more instructions that, when executed by one or more processors of a UE, may cause the UE to receive, from the base station and during the multicast session, a multicast downlink communication in accordance with a multicast downlink format of the plurality of multicast downlink formats.

In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication may include one or more instructions that, when executed by one or more processors of a base station, may cause the base station to transmit a configuration for a multicast session indicating a plurality of multicast downlink formats. In some aspects, the set of instructions for wireless communication may include one or more instructions that, when executed by one or more processors of a base station, may cause the base station to transmit, for multicast data, a plurality of multicast downlink communications associated with the multicast data in accordance with the plurality of multicast downlink formats.

In some aspects, an apparatus for wireless communication may include means for receiving, from a base station, a configuration for a multicast session indicating a plurality of multicast downlink formats. The apparatus may include means for receiving, from the base station and during the multicast session, a multicast downlink communication in accordance with a multicast downlink format of the plurality of multicast downlink formats.

In some aspects, an apparatus for wireless communication may include means for transmitting a configuration for a multicast session indicating a plurality of multicast downlink formats. The apparatus may include means for transmitting, for multicast data, a plurality of multicast downlink communications associated with the multicast data in accordance with the plurality of multicast downlink formats.

Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, wireless communication device, or processing system as substantially described with reference to and as illustrated by the drawings and specification.

The foregoing has outlined rather broadly the features and technical advantages of examples in accordance with the disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The conception and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. Characteristics of the concepts disclosed herein, both their organization and method of operation, together with associated advantages will be better understood from the following description when considered in connection with the accompanying figures. Each of the figures is provided for the purposes of illustration and description, and not as a definition of the limits of the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the above-recited features of the present disclosure can be understood in detail, a more particular description, briefly summarized above, may be had by reference to aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only some typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects. The same reference numbers in different drawings may identify the same or similar elements.

Figure 1 is a diagram illustrating an example of a wireless network in accordance with various aspects of the present disclosure.

Figure 2 is a diagram illustrating an example base station (BS) in communication with a user equipment (UE) in a wireless network in accordance with various aspects of the present disclosure.

Figure 3 is a diagram illustrating an example resource structure for wireless communication, in accordance with various aspects of the present disclosure.

Figure 4 is a diagram illustrating an example of a multicast session configuration, in accordance with various aspects of the present disclosure.

Figure 5 is a diagram illustrating an example 500 associated with downlink formats for multicast communications, in accordance with various aspects of the present disclosure.

Figure 6 is a diagram illustrating examples associated with multicast physical downlink shared channel (PDSCH) formats, in accordance with various aspects of the present disclosure.

Figure 7 is a diagram illustrating examples associated with multicast physical downlink control channel formats, in accordance with various aspects of the present disclosure.

Figure 8 is a diagram illustrating an example associated with multicast PDSCH communications, in accordance with various aspects of the present disclosure.

Figure 9 is a flowchart illustrating an example process performed, for example, by a UE in accordance with various aspects of the present disclosure.

Figure 10 is a flowchart illustrating an example process performed, for example, by a base station in accordance with various aspects of the present disclosure.

Figures 11-12 are block diagrams of example apparatuses for wireless communication in accordance with various aspects of the present disclosure.

DETAILED DESCRIPTION

Various aspects of the disclosure are described more fully hereinafter with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and are not to be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Based on the teachings herein one skilled in the art may appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or combined with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using any quantity of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method which is practiced using other structure, functionality, or structure and functionality in addition to or other than the various aspects of the disclosure set forth herein. Any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

Several aspects of telecommunication systems will now be presented with reference to various apparatuses and techniques. These apparatuses and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms, among other examples, or combinations thereof (collectively referred to as “elements” ) . These elements may be implemented using hardware, software, or combinations thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

Various aspects relate generally to configuring downlink formats for multicast communications associated with a multicast session. Some aspects more specifically relate to configuring a first downlink format for baseline user equipments (UEs) subscribed to (or configured with) the multicast session and a second downlink format for reduced capability (RedCap) UEs subscribed to (or configured with) the multicast session. In some aspects, the first downlink format may be associated with a higher transport format (for example, a higher modulation and coding scheme, a higher modulation level, a higher coding rate, more spatial layers, a higher spectrum efficiency, or a lower aggregation level, among other examples) , or less resources (for example, less time domain resources, or less frequency domain resource, among other examples) relative to the second downlink format. In some aspects, a base station may transmit multicast data in accordance with the first downlink format and may transmit the same multicast data in accordance with the second downlink format. In some aspects, a UE subscribed to (or configured with) the multicast session may determine a downlink format to use for receiving multicast communications associated with the multicast session based at least in part on a capability associated with the UE.

Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, the described techniques can be used to increase throughput for baseline UEs subscribed to (or configured with) the multicast session, as the baseline UEs may use a downlink format for receiving multicast communications that uses a higher transport format or less resources than would have otherwise been used with a common downlink format for all UEs. In some examples, the described techniques can be used to reduce latency for baseline UEs subscribed to (or configured with) the multicast session, as the baseline UEs receive other communications sooner (for example, as other PDSCH communications may be scheduled by a base station during resources that would have otherwise been used with a common downlink format for all UEs) . In some examples, the described techniques can be used to reduce power consumption by baseline UEs, as less resources may be consumed by the baseline UEs than would have otherwise been used with a common downlink format for all UEs when receiving the multicast communications. In some examples, the described techniques can realize one or more of the above potential advantages for baseline UEs while also ensuring that RedCap UEs that are subscribed to (or configured with) the multicast session are enabled to receive multicast communications (for example, by using a downlink format for RedCap UEs that utilizes a lower transport format or more resources than a downlink format used for baseline UEs) .

Figure 1 is a diagram illustrating an example of a wireless network in accordance with various aspects of the present disclosure. The wireless network may be or may include elements of a 5G (NR) network or an LTE network, among other examples. The wireless network may include one or more base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A base station (BS) is an entity that communicates with user equipment (UEs) and may also be referred to as an NR BS, a Node B, a gNB, a 5G node B (NB) , an access point, or a transmit receive point (TRP) , among other examples. Each BS may provide communication coverage for a particular geographic area. In 3GPP, the term “cell” can refer to a coverage area of a BS or a BS subsystem serving this coverage area, depending on the context in which the term is used.

A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, or another type of cell. A macro cell may cover a relatively large geographic area (for example, several kilometers in radius) and may allow unrestricted access by UEs with service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription. A femto cell may cover a relatively small geographic area (for example, a home) and may allow restricted access by UEs having association with the femto cell (for example, UEs in a closed subscriber group (CSG) ) . A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. A BS may support one or multiple (for example, three) cells.

The wireless network may be a heterogeneous network that includes BSs of different types, for example, macro BSs, pico BSs, femto BSs, or relay BSs, among other examples, or combinations thereof. These different types of BSs may have different transmit power levels, different coverage areas, and different impacts on interference in the wireless network. For example, macro BSs may have a high transmit power level (for example, 5 to 40 watts) whereas pico BSs, femto BSs, and relay BSs may have lower transmit power levels (for example, 0.1 to 2 watts) . In the example shown in Figure 1, a BS 110a may be a macro BS for a macro cell 102a, a BS 110b may be a pico BS for a pico cell 102b, and a BS 110c may be a femto BS for a femto cell 102c. A network controller 130 may couple to the set of

BSs

102a, 102b, 110a and 110b, and may provide coordination and control for these BSs. Network controller 130 may communicate with the BSs via a backhaul. The BSs may also communicate with one another, for example, directly or indirectly via a wireless or wireline backhaul.

In some aspects, a cell may not be stationary, rather, the geographic area of the cell may move in accordance with the location of a mobile BS. In some aspects, the BSs may be interconnected to one another or to one or more other BSs or network nodes (not shown) in the wireless network through various types of backhaul interfaces such as a direct physical connection, or a virtual network, among other examples, or combinations thereof using any suitable transport network.

The wireless network may also include relay stations. A relay station is an entity that can receive a transmission of data from an upstream station (for example, a BS or a UE) and send a transmission of the data to a downstream station (for example, a UE or a BS) . A relay station may also be a UE that can relay transmissions for other UEs. In the example shown in Figure 1, a relay BS 110d may communicate with macro BS 110a and a UE 120d in order to facilitate communication between BS 110a and UE 120d. A relay BS may also be referred to as a relay station, a relay base station, or a relay, among other examples, or combinations thereof.

UEs 120 (for example, 120a, 120b, 120c) may be dispersed throughout the wireless network, and each UE may be stationary or mobile. A UE may also be referred to as an access terminal, a terminal, a mobile station, a subscriber unit, or a station, among other examples, or combinations thereof. A UE may be a cellular phone (for example, a smart phone) , a personal digital assistant (PDA) , a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, biometric sensors/devices, wearable devices (smart watches, smart clothing, smart glasses, smart wrist bands, smart jewelry (for example, smart ring, smart bracelet) ) , an entertainment device (for example, a music or video device, or a satellite radio) , a vehicular component or sensor, smart meters/sensors, industrial manufacturing equipment, a global positioning system device, or any other suitable device that is configured to communicate via a wireless medium.

Some UEs may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors or location tags, among other examples, or combinations thereof, that may communicate with a base station, another device (for example, remote device) , or some other entity. A wireless node may provide, for example, connectivity for or to a network (for example, a wide area network such as Internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered Internet-of-Things (IoT) devices, or may be implemented as NB-IoT (narrowband internet of things) devices. Some UEs may be considered a Customer Premises Equipment (CPE) . UE 120 may be included inside a housing that houses components of UE 120, such as processor components, or memory components, among other examples, or combinations thereof.

In general, any quantity of wireless networks may be deployed in a given geographic area. Each wireless network may support a particular radio access technology (RAT) and may operate on one or more frequencies or frequency channels. A frequency may also be referred to as a carrier among other examples. Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

In some aspects, two or more UEs 120 (for example, shown as UE 120a and UE 120e) may communicate directly with one another using one or more sidelink channels (for example, without using a base station 110 as an intermediary) . For example, the UEs 120 may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (for example, which may include a vehicle-to-vehicle (V2V) protocol, or a vehicle-to-infrastructure (V2I) protocol, among other examples, or combinations thereof) , or a mesh network, among other examples, or combinations thereof. In such examples, the UE 120 may perform scheduling operations, resource selection operations, or other operations described elsewhere herein as being performed by the base station 110.

Devices of the wireless network may communicate using the electromagnetic spectrum, which may be subdivided based on frequency or wavelength into various classes, bands, or channels. For example, devices of the wireless network may communicate using an operating band having a first frequency range (FR1) , which may span from 410 MHz to 7.125 GHz. As another example, devices of the wireless network may communicate using an operating band having a second frequency range (FR2) , which may span from 24.25 GHz to 52.6 GHz. The frequencies between FR1 and FR2 are sometimes referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to as a “sub-6 GHz” band. Similarly, FR2 is often referred to as a “millimeter wave” band despite being different from the extremely high frequency (EHF) band (30 GHz –300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band. Thus, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” may broadly represent frequencies less than 6 GHz, frequencies within FR1, mid-band frequencies (for example, greater than 7.125 GHz) , or a combination thereof. Similarly, unless specifically stated otherwise, it should be understood that the term “millimeter wave” may broadly represent frequencies within the EHF band, frequencies within FR2, mid-band frequencies (for example, less than 24.25 GHz) , or a combination thereof. The frequencies included in FR1 and FR2 may be modified, and techniques described herein are applicable to those modified frequency ranges.

Figure 2 is a diagram illustrating an example base station in communication with a UE in a wireless network in accordance with various aspects of the present disclosure. The base station may correspond to base station 110 of Figure 1. Similarly, the UE may correspond to UE 120 of Figure 1.

Base station 110 may be equipped with T antennas 234a through 234t, and UE 120 may be equipped with R antennas 252a through 252r, where in general T ≥ 1 and R ≥1. At base station 110, a transmit processor 220 may receive data from a data source 212 for one or more UEs, select one or more modulation and coding schemes (MCSs) for each UE based at least in part on channel quality indicators (CQIs) received from the UE, process (for example, encode) the data for each UE based at least in part on the MCS (s) selected for the UE, and provide data symbols for all UEs. Transmit processor 220 may also process system information (for example, for semi-static resource partitioning information (SRPI) among other examples) and control information (for example, CQI requests, grants, or upper layer signaling, among other examples, or combinations thereof) and provide overhead symbols and control symbols. Transmit processor 220 may also generate reference symbols for reference signals and synchronization signals. A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (for example, precoding) on the data symbols, the control symbols, the overhead symbols, or the reference symbols, if applicable, and may provide T output symbol streams to T modulators (MODs) 232a through 232t. Each MOD 232 may process a respective output symbol stream (for example, for OFDM among other examples) to obtain an output sample stream. Each MOD 232 may further process (for example, convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. T downlink signals from MODs 232a through 232t may be transmitted via T antennas 234a through 234t, respectively.

At UE 120, antennas 252a through 252r may receive the downlink signals from base station 110 or other base stations and may provide received signals to R demodulators (DEMODs) 254a through 254r, respectively. Each DEMOD 254 may condition (for example, filter, amplify, downconvert, and digitize) a received signal to obtain input samples. Each DEMOD 254 may further process the input samples (for example, for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from all R DEMODs 254a through 254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 258 may process (for example, decode) the detected symbols, provide decoded data for UE 120 to a data sink 260, and provide decoded control information and system information to a controller/processor 280. The term “controller/processor” may refer to one or more controllers, one or more processors, or a combination thereof. A channel processor may determine a reference signal received power (RSRP) , a received signal strength indicator (RSSI) , a reference signal received quality (RSRQ) , or a channel quality indicator (CQI) , among other examples, or combinations thereof. In some aspects, one or more components of UE 120 may be included in a housing.

Network controller 130 may include communication unit 294, controller/processor 290, and memory 292. Network controller 130 may include, for example, one or more devices in a core network. Network controller 130 may communicate with base station 110 via communication unit 294.

On the uplink, at UE 120, a transmit processor 264 may receive and process data from a data source 262 as well as control information (for example, for reports including RSRP, RSSI, RSRQ, or CQI, among other examples, or combinations thereof) from controller/processor 280. Transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by MODs 254a through 254r (for example, for discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-s-OFDM) , or orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) , among other examples, or combinations thereof) , and transmitted to base station 110. In some aspects, the UE 120 includes a transceiver. The transceiver may include any combination of antenna (s) 252, modulators 254, demodulators 254, MIMO detector 256, receive processor 258, transmit processor 264, or TX MIMO processor 266. The transceiver may be used by a processor (for example, controller/processor 280) and memory 282 to perform aspects of any of the methods described herein.

At base station 110, the uplink signals from UE 120 and other UEs may be received by antennas 234, processed by DEMODs 232, detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by UE 120. Receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to controller/processor 240. Base station 110 may include communication unit 244 and communicate to network controller 130 via communication unit 244. Base station 110 may include a scheduler 246 to schedule UEs 120 for downlink and uplink communications. In some aspects, the base station 110 includes a transceiver. The transceiver may include any combination of antenna (s) 234, modulators 232, demodulators 232, MIMO detector 236, receive processor 238, transmit processor 220, or TX MIMO processor 230. The transceiver may be used by a processor (for example, controller/processor 240) and memory 242 to perform aspects of any of the methods described herein.

Controller/processor 240 of base station 110, controller/processor 280 of UE 120, or any other component (s) of Figure 2 may perform one or more techniques associated with downlink formats for multicast communications, as described in more detail elsewhere herein. For example, controller/processor 240 of base station 110, controller/processor 280 of UE 120, or any other component (s) of Figure 2 may perform or direct operations of, for example, process 900 of Figure 9, process 1000 of Figure 10, or other processes as described herein.

Memories

242 and 282 may store data and program codes for base station 110 and UE 120, respectively. In some aspects, memory 242 or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (for example, code or program code) for wireless communication. For example, the one or more instructions, when executed (for example, directly, or after compiling, converting, or interpreting) by one or more processors of the base station 110 or the UE 120, may cause the one or more processors, the UE 120, or the base station 110 to perform or direct operations of, for example, process 800 of Figure 8, process 900 of Figure 9, or other processes as described herein. In some aspects, executing instructions may include running the instructions, converting the instructions, compiling the instructions, or interpreting the instructions, among other examples.

In some aspects, UE 120 may include means for receiving, from a base station, a configuration for a multicast session indicating a plurality of multicast downlink formats, means for receiving, from the base station and during the multicast session, a multicast downlink communication in accordance with a multicast downlink format of the plurality of multicast downlink formats, among other examples, or combinations thereof. In some aspects, such means may include one or more components of UE 120 described in connection with Figure 2, such as controller/processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, DEMOD 254, MIMO detector 256, or receive processor 258.

In some aspects, base station 110 may include means for transmitting a configuration for a multicast session indicating a plurality of multicast downlink formats, means for transmitting, for multicast data, a plurality of multicast downlink communications associated with the multicast data in accordance with the plurality of multicast downlink formats, among other examples, or combinations thereof. In some aspects, such means may include one or more components of base station 110 described in connection with Figure 2, such as antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller/processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, or antenna 234, among other examples.

Figure 3 is a diagram illustrating an example resource structure 300 for wireless communication, in accordance with various aspects of the present disclosure. Resource structure 300 shows an example of various groups of resources described herein. As shown, resource structure 300 may include a subframe 305. Subframe 305 may include multiple slots 310. While resource structure 300 is shown as including 2 slots per subframe, a different number of slots may be included in a subframe (for example, 4 slots, 8 slots, 16 slots, or 32 slots, among other examples) . In some aspects, different types of transmission time intervals (TTIs) may be used, other than subframes or slots. A slot 310 may include multiple symbols 315, such as 7 symbols or 14 symbols per slot.

The potential control region of a slot 310 may be referred to as a control resource set (CORESET) 320 and may be structured to support an efficient use of resources, such as by flexible configuration or reconfiguration of resources of the CORESET 320 for one or more PDCCHs, or one or more physical downlink shared channels (PDSCHs) . In some aspects, the CORESET 320 may occupy the first symbol 315 of a slot 310, the first two symbols 315 of a slot 310, or the first three symbols 315 of a slot 310. Thus, a CORESET 320 may include multiple resource blocks (RBs) in the frequency domain, and either one, two, or three symbols 315 in the time domain. In 5G, a quantity of resources included in the CORESET 320 may be flexibly configured, such as by using radio resource control (RRC) signaling to indicate a frequency domain region (for example, a quantity of resource blocks) or a time domain region (for example, a quantity of symbols) for the CORESET 320.

As illustrated, a symbol 315 that includes CORESET 320 may include one or more control channel elements (CCEs) 325, shown as two CCEs 325 as an example, that span a portion of the system bandwidth. A CCE 325 may include downlink control information (DCI) that is used to provide control information for wireless communication. A base station may transmit DCI during multiple CCEs 325 (as shown) , where the quantity of CCEs 325 used for transmission of DCI represents the aggregation level (AL) used by the BS for the transmission of DCI. In Figure 3, an aggregation level of two is shown as an example, corresponding to two CCEs 325 in a slot 310. In some aspects, different aggregation levels may be used, such as 1, 4, 8, or 16, among other examples.

Each CCE 325 may include a fixed quantity of resource element groups (REGs) 330, shown as 4 REGs 330, or may include a variable quantity of REGs 330. In some aspects, the quantity of REGs 330 included in a CCE 325 may be specified by a REG bundle size. A REG 330 may include one resource block, which may include 12 resource elements (REs) 335 within a symbol 315. A resource element 335 may occupy one subcarrier in the frequency domain and one OFDM symbol in the time domain.

A search space may include all possible locations (for example, in time or frequency) where a PDCCH may be located. A CORESET 320 may include one or more search spaces, such as a UE-specific search space, a group-common search space, or a common search space. A search space may indicate a set of CCE locations where a UE may find PDCCHs that can potentially be used to transmit control information to the UE. The possible locations for a PDCCH may depend on whether the PDCCH is a UE-specific PDCCH (for example, for a single UE) or a group-common PDCCH (for example, for multiple UEs) , or an aggregation level being used, among other examples. A possible location (for example, in time or frequency) for a PDCCH may be referred to as a PDCCH candidate, and the set of all possible PDCCH locations may be referred to as a search space. For example, the set of all possible PDCCH locations for a particular UE may be referred to as a UE-specific search space. Similarly, the set of all possible PDCCH locations across all UEs may be referred to as a common search space. The set of all possible PDCCH locations for a particular group of UEs may be referred to as a group-common search space.

A CORESET 320 may be interleaved or non-interleaved. An interleaved CORESET 320 may have CCE-to-REG mapping such that adjacent CCEs are mapped to scattered REG bundles in the frequency domain (for example, adjacent CCEs are not mapped to consecutive REG bundles of the CORESET 320) . A non-interleaved CORESET 320 may have a CCE-to-REG mapping such that all CCEs are mapped to consecutive REG bundles (for example, in the frequency domain) of the CORESET 320.

Figure 4 is a diagram illustrating an example 400 of a multicast session configuration, in accordance with various aspects of the present disclosure. A radio access technology (RAT) , such as LTE, may provide a multimedia broadcast or multicast service (MBMS) . An MBMS communication may be transmitted to a set of UEs on a physical multicast channel (PMCH) , or may be transmitted on a unicast channel to UEs that are to receive the MBMS communication. As shown in Figure 4, a base station 110 may configure a UE 120 with one or more MBMS sessions.

In a first operation 405, the base station 110 may transmit one or more multicast configurations to the UE 120 to establish the one or more MBMS sessions. The base station 110 may transmit a system information block (SIB) that includes a configuration for a multicast control channel (MCCH) for an MBMS. The MCCH may be a single cell MCCH (SC-MCCH) . The UE 120 may receive the SIB, and may decode the SIB to obtain an MCCH configuration. The base station 110 may use SC-MCCH signaling to transmit a downlink control information (DCI) communication to all UEs located within the cell associated with the base station 110. The DCI may configure one or more multicast sessions (for example, one or more MBMS sessions) .

A multicast session may be associated with a discontinuous reception (DRX) configuration and a group radio network temporary identifier (G-RNTI) value. A DRX configuration may indicate a DRX cycle associated with the multicast session (for example, a cycle period, an offset, an on duration length, or an inactivity timer length) . A DRX cycle may include a DRX on duration (for example, during which a UE 120 is awake or in an active state) and an opportunity to enter a DRX sleep state. As used herein, the time during which the UE 120 is configured to be in an active state during the DRX on duration 310 may be referred to as an active time, and the time during which the UE 120 is configured to be in the DRX sleep state 315 may be referred to as an inactive time. As described below, the UE 120 may monitor a physical downlink control channel (PDCCH) during the active time, and may refrain from monitoring the PDCCH during the inactive time.

During a DRX on duration (for example, the active time) , the UE 120 may monitor a downlink control channel (for example, a PDCCH) . For example, the UE 120 may monitor the PDCCH for DCI pertaining to the UE 120 and the multicast session. If the UE 120 does not detect or successfully decode any PDCCH communications intended for the UE 120 during the DRX on duration, then the UE 120 may enter the sleep state (for example, for the inactive time) at the end of the DRX on duration. In this way, the UE 120 may conserve battery power and reduce power consumption. The DRX cycle may repeat with a configured periodicity according to the DRX configuration.

If the UE 120 detects or successfully decodes a PDCCH communication intended for the UE 120, then the UE 120 may remain in an active state (for example, awake) for the duration of a DRX inactivity timer indicated by the DRX configuration (for example, which may extend the active time) . The UE 120 may start the DRX inactivity timer at a time at which the PDCCH communication is received (for example, in a transmission time interval (TTI) in which the PDCCH communication is received, such as a slot, or a subframe, among other examples) . The UE 120 may remain in the active state until the DRX inactivity timer expires, at which time the UE 120 may enter the sleep state (for example, for the inactive time) . During the duration of the DRX inactivity timer, the UE 120 may continue to monitor for PDCCH communications, may obtain a multicast downlink data communication (for example, on a downlink data channel, such as a physical downlink shared channel (PDSCH) ) scheduled by the PDCCH communication, may prepare or transmit an uplink communication (for example, on a physical uplink shared channel (PUSCH) ) scheduled by the PDCCH communication) , among other examples. The UE 120 may restart the DRX inactivity timer after each detection of a PDCCH communication for the UE 120 for an initial transmission (for example, but not for a retransmission) . By operating in this manner, the UE 120 may conserve battery power and reduce power consumption by entering the sleep state.

As shown in Figure 4, the base station 110 (or one or more base stations 110) may configure the UE 120 with one or more multicast sessions. A first multicast session may be associated with a DRX cycle 410. The DRX cycle 410 may include DRX on durations 415. During the DRX cycle on durations 415, the UE 120 may monitor a PDCCH for DCI that is associated with a G-RNTI value associated with the first multicast session. For example, the UE 120 may monitor the PDCCH for DCI that is scrambled with the G-RNTI value associated with the first multicast session.

A second multicast session may be associated with a DRX cycle 420. The DRX cycle 420 may include DRX on durations 425. During the DRX cycle on durations 425, the UE 120 may monitor a PDCCH for DCI that is associated with a G-RNTI value associated with the second multicast session. For example, the UE 120 may monitor the PDCCH for DCI that is scrambled with the G-RNTI value associated with the second multicast session.

A third multicast session may be associated with a DRX cycle 430. The DRX cycle 440 may include DRX on durations 435. During the DRX cycle on durations 435, the UE 120 may monitor a PDCCH for DCI that is associated with a G-RNTI value associated with the third multicast session. For example, the UE 120 may monitor the PDCCH for DCI that is scrambled with the G-RNTI value associated with the third multicast session.

Therefore, the UE 120 may monitor a PDCCH during all on durations associated with multicast sessions configured by the base station 110. The UE 120 may receive DCI during an on duration. The UE 120 may receive multicast data in a multicast downlink data communication scheduled by the DCI.

In some wireless communication systems, a base station 110 may configure a plurality of UEs 120 with a multicast configuration for a multicast session. For example, a plurality of UEs 120 may subscribe to a multicast session in a cell associated with the base station 110. Some UEs 120 subscribed to the multicast session may be associated with a reduced capability relative to a baseline UE 120 (for example, an enhanced mobile broadband (eMBB) UE 120, among other examples) .

For example, a reduced capability (RedCap) UE 120 may be an Internet of Things (IoT) UE 120, a machine-type communication (MTC) UE 120, or an NR-Light UE 120. A RedCap UE 120 may be associated with a reduced capability relative to a baseline UE 120 (for example, an eMBB UE 120) . A RedCap UE 120 may be used for an industrial wireless sensor, a video surveillance device, or a smart wearable device, among other examples. A RedCap UE 120 may have a lower communicative capability, relative to a baseline UE 120 (for example, an eMBB UE 120 among other examples) . For example, a RedCap UE 120 may be limited in terms of maximum bandwidth (for example, 5 MHz, 10 MHz, or 20 MHz, among other examples) , maximum transmission power (for example, 20 dBm, or 14 dBm, among other examples) , or number of receive antennas (for example, 1 receive antenna, or 2 receive antennas, among other examples) among other examples. A RedCap UE 120 may have a lower processing capability (for example, less processing hardware, lower channel coding capability, or lower channel estimation capability, among other examples) relative to a baseline UE 120. A RedCap UE 120 may also have a prolonged battery life, relative to a baseline UE 120. RedCap UEs 120 may co-exist with UEs 120 implementing protocols such as eMBB, ultra-reliable low latency communication (URLLC) , or LTE NB-IoT/MTC, among other examples. In some aspects, RedCap UEs 120, such as industrial wireless sensors, may be associated with intensive uplink traffic, moderate reliability and latency (for example, non-URLLC) , small packet size with a relatively long transmit interval (for example, low data rate) , and high capacity (for example, up to 1 UE per square meter) .

As a result, given a same MCS for a communication, a RedCap UE 120 may have a lower receive performance than a baseline UE 120 located at the same position. For example, a RedCap UE 120 may require a lower transport format (for example, a lower MCS, a lower modulation level, a lower coding rate, less spatial layers, a lower spectrum efficiency in a PDSCH, or a higher aggregation level in a PDCCH, among other examples) than a baseline UE 120 to receive the communication. Additionally or alternatively, a RedCap UE 120 may require more resources (for example, more time domain resources, more frequency domain resources, a larger bandwidth, a larger number of symbols, or a larger number of slots, among other examples) than a baseline UE 120 to receive the communication.

The base station 110, for a multicast session, may schedule a single multicast PDSCH communication to transmit a common data packet for multicast data for all UEs 120 subscribed to (or configured with) the multicast session. The multicast PDSCH communication may be scheduled by a single DCI in a PDCCH communication, which is decoded by all UEs 120 subscribed to (or configured with) the multicast session. To ensure that RedCap UEs 120 subscribed to the multicast session are able to receive the multicast PDSCH communication, the base station 110 may transmit the PDCCH communication and the multicast PDSCH communication using low transport formats, or more resources, due to the lower communicative capability of RedCap UEs 120 relative to baseline UEs 120. However, transmitting the PDCCH communication and the multicast PDSCH communication using low transport formats, or more resources, may reduce throughput, increase latency, or increase power consumption, for baseline UEs 120.

For example, the multicast PDSCH communication transmitted by the base station 110 may occupy more resources (for example, more time domain resources, more frequency domain resources, or more spatial domain resources, among other examples) than are necessary for baseline UEs 120 to receive the multicast PDSCH communication. As a result, unicast transfer of other data to the baseline UEs 120 cannot be scheduled during the resources occupied by the multicast PDSCH communication. This reduces the overall data throughput, or increases data transfer latency, among other examples, for baseline UEs 120.

Additionally or alternatively, the PDCCH communication associated with the multicast session may utilize more CCEs than are necessary for baseline UEs 120 to receive and decode the PDCCH communication. As a result, a processing capability of baseline UEs 120 for receiving or decoding other PDCCH communications in a same slot as the PDCCH communication is reduced. For example, the baseline UEs 120 may only receive PDCCH communications that utilize less CCEs than the PDCCH communication. This may increase a risk of a decoding error associated with decoding the PDCCH communication or associated with decoding other PDCCH communications received by baseline UEs 120.

Various aspects relate generally to configuring multicast downlink formats for multicast communications associated with a multicast session. Some aspects more specifically relate to configuring a first multicast downlink format for baseline UEs 120 subscribed to (or configured with) the multicast session and a second multicast downlink format for RedCap UEs subscribed to (or configured with) the multicast session. In some aspects, the first multicast downlink format may be associated with a higher transport format, less resources (for example, less time domain resources, or less frequency domain resources, among other examples) relative to the second downlink format. In some aspects, a base station 110 may transmit multicast data in accordance with the first multicast downlink format and may transmit the same multicast data in accordance with the second multicast downlink format. In some aspects, a UE 120 subscribed to (or configured with) the multicast session may determine a multicast downlink format to use for receiving multicast communications associated with the multicast session based at least in part on a capability associated with the UE 120.

Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, the described techniques can be used to increase throughput for baseline UEs 120 subscribed to (or configured with) the multicast session, as the baseline UEs 120 may use a multicast downlink format for receiving multicast communications that uses a higher transport format or less resources than would have otherwise been used with a common multicast downlink format for all UEs 120. In some examples, the described techniques can be used to reduce latency for baseline UEs 120 subscribed to (or configured with) the multicast session, as the baseline UEs 120 receive other communications sooner (for example, as other PDSCH communications may be scheduled by a base station 110 during resources that would have otherwise been used with a common multicast downlink format for all UEs 120) . In some examples, the described techniques can be used to reduce power consumption by baseline UEs 120, as less resources may be consumed by the baseline UEs 120 than would have otherwise been used with a common multicast downlink format for all UEs 120 when receiving the multicast communications. In some examples, the described techniques can realize one or more of the above potential advantages for baseline UEs 120 while also ensuring that RedCap UEs 120 that are subscribed to (or configured with) the multicast session are enabled to receive multicast communications (for example, by using a downlink format for RedCap UEs 120 that utilizes a lower transport format or more resources than a downlink format used for baseline UEs 120) .

Figure 5 is a diagram illustrating an example 500 associated with downlink formats for multicast communications, in accordance with various aspects of the present disclosure. As shown in Figure 5, a base station 110 and a UE 120 may communicate with one another in a wireless network (for example, wireless network 100) . In some aspects, the base station 110 may provide a multicast service, such as an MBMS, to the UE 120.

In a first operation 505, the base station 110 may determine whether to transmit multicast data associated with a multicast session using a common PDSCH communication for all UEs 120 associated with the base station 110 or using different PDSCHs for different subsets of UEs 120, of all UEs, associated with the base station 110. For example, a first subset of UEs 120 may include all baseline UEs 120 subscribed to (or configured with) the multicast session. A second subset of UEs 120 may include all RedCap UEs 120 subscribed to (or configured with) the multicast session. In some aspects, a subset of UEs 120 may include a first set of baseline UEs 120 associated with a first communicative capability, and another subset of UEs 120 may include a second set of baseline UEs 120 associated with a second communicative capability.

The base station 110 may determine to transmit multicast data using different PDSCHs for different subsets of UEs 120, of all UEs, associated with the base station 110, based at least in part on determining that the base station 110 is to schedule a unicast data transfer during one or more slots associated with scheduled multicast communications. Similarly, the base station 110 may determine to transmit multicast data using different PDSCHs for different subsets of UEs 120, of all UEs, associated with the base station 110, based at least in part on determining that the base station 110 is to transmit a high aggregation level DCI for a unicast communication during one or more slots associated with scheduled multicast communications. In some aspects, the base station 110 may determine to transmit multicast data using different PDSCHs for different subsets of UEs 120, of all UEs, associated with the base station 110, based at least in part on determining that the base station 110 is to conserve power of baseline UEs 120 subscribed to the multicast session. In some aspects, the base station 110 may determine to transmit multicast data using different PDSCHs for different subsets of UEs 120, of all UEs, associated with the base station 110, based at least in part on determining that there is one or more (or greater than or equal to a threshold quantity of) RedCap UEs 120 subscribed to the multicast session.

The base station 110 may determine to transmit multicast data using a common PDSCH communication for all UEs 120 subscribed to the multicast session based at least in part on determining that the base station 110 is not to schedule a unicast data transfer or a high aggregation level DCI communication during one or more slots associated with scheduled multicast communications. In some aspects, the base station 110 may determine to transmit multicast data using a common PDSCH communication for all UEs 120 subscribed to the multicast session based at least in part on determining that there are no (or less than a threshold quantity of) RedCap UEs 120 subscribed to the multicast session. In this way, the base station 110 may conserve resources that would have otherwise been used sending multiple PDSCH communications for the same multicast data if the multiple PDSCH communications are not necessary.

In a second operation 510, the base station 110 may determine a configuration for the multicast session indicating one or more downlink formats for multilink communications. For example, if the base station 110 determines to transmit multicast data using a common PDSCH communication for all UEs 120 subscribed to the multicast session, the base station 110 may determine that the configuration is to indicate a single multicast downlink format (for example, a PDCCH format and a PDSCH format associated with the single multicast downlink format) for multicast communications associated with the multicast sessions. If the base station 110 determines to transmit multicast data using different PDSCHs for different subsets of UEs 120, of all UEs, associated with the base station 110, the base station 110 may determine that the configuration is to indicate multiple multicast downlink formats for multicast communications associated with the multicast session.

The base station 110 may determine the configuration for the multicast session indicating multiple multicast downlink formats based at least in part on capabilities of UEs 120 associated with the base station 110 (for example, subscribed to the multicast session) . For example, the base station 110 may determine a first multicast downlink format associated with baseline UEs 120 and a second multicast downlink format associated with RedCap UEs 120. In some aspects, the base station 110 may determine multiple multicast downlink formats associated with baseline UEs 120 (or subsets of the baseline UEs 120) . In some aspects, the base station 110 may determine multiple multicast downlink formats associated with RedCap UEs 120 (or subsets of RedCap UEs 120) .

The base station 110 may determine a PDCCH format and a PDSCH format for each multicast downlink format. A PDCCH format may be associated with transmitting DCI communications during the multicast session that schedule multicast PDSCH communications. A PDSCH format may be associated with transmitting multicast PDSCH communications carrying multicast data.

The base station 110 may determine whether resources (for example, time domain resources, or frequency domain resources, among other examples) associated with a first PDSCH format are to overlap with resources associated with a second PDSCH format. For example, the base station 110 may determine whether resources associated with a PDSCH format for baseline UEs 120 are to overlap with resources associated with a PDSCH format for RedCap UEs 120. The configuration for the multicast session may indicate whether resources associated with the first PDSCH format are to overlap with resources associated with the second PDSCH format.

If the base station 110 determines that resources associated with the first PDSCH format are not to overlap with resources associated with the second PDSCH format, the base station 110 may determine that the first PDSCH format is associated with a first transport format and the second PDSCH format is associated with a second transport format. A transport format may indicate an MCS, a modulation level, a coding rate, a number of spatial layers, a spectrum efficiency associated with PDSCH communications, or an aggregation level associated with PDCCH communications, among other examples. For example, the base station 110 may determine that a PDSCH format associated with baseline UEs 120 is associated with a higher transport format (for example, a higher MCS, a higher modulation level, a higher coding rate, more spatial layers, a higher spectrum efficiency, or a lower aggregation level, among other examples) relative to a PDSCH format associated with RedCap UEs 120. The configuration for the multicast session may indicate a transport format associated with each multicast downlink format.

In some aspects, if the base station 110 determines that resources associated with the first PDSCH format are not to overlap with resources associated with the second PDSCH format, the base station 110 may determine that the first PDSCH format is associated with fewer resources (for example, fewer time domain resources, fewer frequency domain resources, fewer OFDM symbols, or fewer RBs, among other examples) than the second PDSCH format. For example, the base station 110 may determine that a PDSCH format associated with baseline UEs 120 is associated with fewer resources relative to a PDSCH format associated with RedCap UEs 120. That is, the PDSCH format associated with baseline UEs 120 may use fewer resources than the PDSCH format associated with RedCap UEs 120 for communicating the same multicast data. The configuration for the multicast session may indicate that the PDSCH format associated with baseline UEs 120 is associated with fewer resources relative to the PDSCH format associated with RedCap UEs 120.

In some aspects, the PDSCH format associated with baseline UEs 120 may be associated with a higher transport format and less resources than the PDSCH format associated with RedCap UEs 120. In some aspects, the PDSCH format associated with baseline UEs 120 may be associated with a higher transport format and the same quantity of resources as the PDSCH format associated with RedCap UEs 120. In some aspects, the PDSCH format associated with baseline UEs 120 may be associated with the same transport format and less resources than the PDSCH format associated with RedCap UEs 120.

If the base station 110 determines that resources associated with the first PDSCH format are to at least partially overlap with resources associated with the second PDSCH format, the base station 110 may determine that the resources associated with the first PDSCH format are a subset of the resources associated with the second PDSCH format. For example, the base station 110 may determine that PDSCH communications associated with the first PDSCH format and the second PDSCH format are to be transmitted in a same slot. The base station 110 may determine that the second PDSCH format is to be associated with a set of OFDM symbols in the slot. The base station 110 may determine that the first PDSCH format is to be associated with a subset of OFDM symbols of the set of OFDM symbols in the slot.

In some aspects, the base station 110 may determine that the time domain resources associated with the first PDSCH format start at a first time domain resource (for example, a first OFDM symbol) associated with the second PDSCH format. In this way, baseline UEs may receive and decode multicast PDSCH communications sooner, thereby reducing latency associated with receiving the multicast communication or with scheduling other data communications after receiving the multicast communication. In some aspects, the time domain resources associated with the first PDSCH format may be located at other locations within a set of time domain resource associated with the second PDSCH format. For example, the time domain resources associated with the first PDSCH format may end at a last time domain resource (for example, a last OFDM symbol) associated with the second PDSCH format.

In some aspects, the base station 110 may determine that the second PDSCH format (for example, associated with RedCap UEs 120) is to be transmitted across multiple slots. The base station 110 may determine that the first PDSCH format (for example, associated with baseline UEs 120) is associated with one or more slots of the multiple slots. For example, the base station 110 may determine that the second PDSCH format is associated with two slots. The base station 110 may determine that the first PDSCH format is associated with a slot (for example, the first slot or the second slot) of the two slots. In some aspects, the base station 110 may determine that the first PDSCH format is associated with a portion of one or more slots of the multiple slots associated with the second PDSCH format.

In some aspects, the base station 110 may determine that frequency domain resources associated with the first PDSCH format at least partially overlap with frequency domain resources associated with the second PDSCH format. In some aspects, the first PDSCH format may be associated with time domain resources that are a subset of the time domain resources associated with the second PDSCH format, and the first PDSCH format may be associated with frequency domain resources that are the same as the frequency domain resources associated with the second PDSCH format. In some aspects, the first PDSCH format may be associated with time domain resources that are a subset of the time domain resources associated with the second PDSCH format, and the first PDSCH format may be associated with frequency domain resources that are a subset of the frequency domain resources associated with the second PDSCH format. In some aspects, the first PDSCH format may be associated with time domain resources that are the same as the time domain resources associated with the second PDSCH format, and the first PDSCH format may be associated with frequency domain resources that are a subset of the frequency domain resources associated with the second PDSCH format. By transmitting PDSCH communications using PDSCH formats associated with resources that are to at least partially overlap, the base station 110 may conserve resources.

The configuration for the multicast session may indicate whether resources associated with the first PDSCH format overlap with resources associated with the second PDSCH format, and may indicate how the resources associated with the first PDSCH format overlap with resources associated with the second PDSCH format (for example, in a time domain, in a frequency domain, in a single slot, or across one or more slots, among other examples) .

In some aspects, the base station 110 may determine that the second PDSCH format (for example, associated with RedCap UEs 120) includes multiple segments. For example, the second PDSCH format may include multiple repetitions, or multiple redundant versions, among other examples. The base station 110 may determine that the first PDSCH format (for example, associated with baseline UEs 120) is associated with one or more segments of the multiple segments. For example, the first PDSCH format may be associated with one or more repetitions of multicast data of multiple repetitions of multicast data that are associated with the second PDSCH format. The second PDSCH format may be associated with one or more redundant versions of multicast data of multiple redundant versions of multicast data that are associated with the second PDSCH format. The configuration for the multicast session may indicate that the second PDSCH format includes multiple segments, that the first PDSCH format is associated with one or more of the multiple segments, or which segments of the multiple segments the PDSCH format is associated with, among other examples.

As described above, the base station 110 may determine a PDCCH format for each multicast downlink format. A PDCCH format may indicate how a DCI, that schedules a PDSCH, is to be sent by the base station 110. The base station 110 may determine a first PDCCH format associated with baseline UEs 120 (for example, associated with scheduling PDSCH communications using the first PDSCH format described above) . The base station 110 may determine a second PDCCH format associated with RedCap UEs 120 (for example, associated with scheduling PDSCH communications using the second PDSCH format described above) .

The base station 110 may determine that a first DCI (for example, associated with the first PDCCH format) is to be transmitted in a first search space (for example, in a first CORESET) . The first search space may be a common search space associated with baseline UEs 120 associated with the base station 110. The base station 110 may determine that a second DCI (for example, associated with the second PDCCH format) is to be transmitted in a second search space (for example, in a second CORESET) . In some aspects, the first search space (for example, associated with baseline UEs 120) may use less CCEs than the second search space (for example, associated with RedCap UEs 120) . The second search space may be a common search space associated with RedCap UEs 120 associated with the base station 110. The DCIs may be group common DCIs. In some aspects, if the base station 110 determines that the first DCI and the second DCI are to be transmitted in different search spaces, the base station 110 may determine that the first DCI and the second DCI are to be associated with a same group radio network temporary identifier (G-RNTI) value. In some aspects, the base station 110 may determine that the first DCI sent in the first search space is to be associated with a first G-RNTI value and the second DCI sent in the second search space is to be associated with a second G-RNTI.

The base station 110 may determine that the first DCI (for example, associated with the first PDCCH format) and the second DCI (for example, associated with the second PDCCH format) are to be transmitted in a same search space (for example, a common search space for all UEs 120 associated with the base station 110) . The base station 110 may determine that the first DCI is to be associated with a first G-RNTI value and the second DCI is to be associated with a second G-RNTI value when the first DCI and the second DCI are to be transmitted in the same search space (for example, in the same CORESET) .

The configuration for the multicast session may indicate a search space and a G-RNTI value associated with each multicast downlink format (for example, associated with each PDCCH format) . In some aspects, the configuration for the multicast session may indicate a UE 120 capability associated with each multicast downlink format. For example, the configuration may indicate that a first multicast downlink format is associated with baseline UEs 120 and a second multicast downlink format is associated with RedCap UEs 120.

In a third operation 515, the base station 110 may transmit the configuration for the multicast session. The configuration for the multicast session may indicate multiple downlink formats for multicast communications. The configuration for the multicast session may indicate a UE 120 capability associated with each of the multiple downlink formats for multicast communications. The base station 110 may transmit the configuration for the multicast session using radio resource control (RRC) signaling (for example, by transmitting a system information block (SIB) ) , medium access control (MAC) signaling (for example, MAC control element (MAC-CE) signaling) , or DCI signaling (for example, group common DCI signaling) , among other examples. In some aspects, the base station 110 may transmit the configuration for the multicast session using a combination of RRC signaling, MAC signaling, or DCI signaling. For example, the base station 110 may transmit a portion of the configuration for the multicast session using RRC signaling, other portions of the configuration for the multicast session using MAC signaling, or other portions of the configuration for the multicast sessions using DCI signaling. For example, the base station 110 may determine that one or more aspects of the configuration for the multicast session are to be changed or updated. The base station 110 may transmit the one or more aspects of the configuration for the multicast session that are to be changed or updated semi-statically (for example, using MAC signaling) or dynamically (for example, using DCI signaling) .

In some aspects, the base station 110 may dynamically signal the configuration for the multicast session for one or more PDSCH communications (for example, for one or more multicast data transfers) using DCI signaling. In some aspects, the base station 110 may semi-statically signal the configuration for the multicast session for one or more PDSCH communications (for example, for one or more multicast data transfers) using MAC signaling. In some aspects, the base station 110 may signal the configuration for the multicast session for all PDSCH communications using RRC signaling.

In a fourth operation 520, the UE 120 may receive the configuration for the multicast sessions and determine a multicast downlink format to use for the multicast session from information included in the configuration. The UE 120 may determine the multicast downlink format to use for the multicast session based at least in part on a capability of the UE 120. For example, if the UE 120 is a baseline UE 120, the UE 120 may determine to use a first multicast downlink format that is associated with baseline UEs 120. If the UE 120 is a RedCap UE 120, the UE 120 may determine to use a second multicast downlink format that is associated with RedCap UEs 120.

For example, the UE 120 may determine a search space to monitor for DCI communications from the base station 110 (for example, if the configuration for the multicast session indicates multiple search spaces) . The UE 120 may determine a G-RNTI value to use associated with DCI communications from the base station 110 (for example, if the configuration for the multicast session indicates multiple G-RNTI values) . The UE 120 may monitor for DCI communications from the base station 110 in the search space or using the G-RNTI value (for example, during an on duration of a DRX cycle associated with the multicast session) .

In a fifth operation 525, the base station 110 may transmit one or more DCIs in accordance with one or more multicast downlink formats (for example, one or more PDCCH formats) . For example, the base station 110 may associate a first DCI and a second DCI with the same G-RNTI value (for example, the base station 110 may scramble the first DCI with the G-RNTI value and scramble the second DCI with the same G-RNTI value) . The base station 110 may transmit the first DCI in a first search space (for example, in a first CORESET) . The base station 110 may transmit the second DCI in a second search space (for example, in a second CORESET) .

In some aspects, the base station 110 may associate a first DCI with a first G-RNTI value (for example, the base station 110 may scramble the first DCI with the first G-RNTI value) . The base station 110 may associate a second DCI with a second G-RNTI value (for example, the base station 110 may scramble the second DCI with the second G-RNTI value) . The base station 110 may transmit the first DCI and the second DCI in a common search space (for example, in a same CORESET) . In some aspects, the base station 110 may transmit the first DCI associated with the first G-RNTI value in a first search space (for example, in a first CORESET) . The base station 110 may transmit the second DCI associated with the second G-RNTI value in a second search space (for example, in a second CORESET) .

The one or more DCIs may be group common DCIs. A group common DCI may be associated with a group of UEs 120. For example, a first group common DCI transmitted by the base station 110 may be associated with baseline UEs 120. A second group common DCI transmitted by the base station 110 may be associated with RedCap UEs 120.

The one or more DCIs may schedule one or more multicast PDSCH communications (for example, in accordance with the PDSCH formats described above) . For example, a first DCI associated with a first multicast downlink format may schedule a first multicast PDSCH in accordance with a PDSCH format associated with the first multicast downlink format (for example, associated with baseline UEs 120) . A second DCI associated with a second multicast downlink format may schedule a second multicast PDSCH in accordance with a PDSCH format associated with the second multicast downlink format (for example, associated with RedCap UEs 120) .

In a sixth operation 530, the UE 120 may receive a DCI of the one or more DCIs transmitted by the base station 110. The UE 120 may receive the DCI of the one or more DCIs based at least in part on determining the multicast downlink format to use for the multicast session. For example, the UE 120 may determine a search space to use for the multicast session. The UE 120 may monitor a PDCCH for DCI communications in the search space. The UE 120 may receive and decode the DCI of the one or more DCIs based at least in part on monitoring the PDCCH for DCI communications in the search space. The DCI may schedule a multicast PDSCH communication in accordance with the multicast downlink format that the UE 120 determined to use for the multicast session (for example, the DCI may be a scheduling grant, or the DCI may allocate resources for the multicast PDSCH communication, among other examples) .

In some aspects, the UE 120 determine a G-RNTI value to use for the multicast session. The UE 120 may monitor a PDCCH for DCI communications associated with the G-RNTI value in a common search space. The UE 120 may receive and decode the DCI of the one or more DCIs based at least in part on monitoring the PDCCH for DCI communications associated with the G-RNTI value in a common search space.

In a seventh operation 535, the base station 110 may transmit the same multicast data in one or more multicast PDSCH communications in accordance with the multicast downlink formats. For example, if the base station 110 determined that resources associated with a first PDSCH format are not to overlap with resources associated with a second PDSCH format, the base station 110 may transmit a first multicast PDSCH communication carrying the multicast data using a first set of resources (for example, a first set of time-frequency resources) . The base station 110 may transmit a second multicast PDSCH communication carrying the multicast data using a second set of resources (for example, a second set of time-frequency resources) . In some aspects, the base station 110 may transmit the first multicast PDSCH communication using a first transport format. The base station 110 may transmit the second multicast PDSCH communication using a second transport format.

If the base station 110 determined that resources associated with a first PDSCH format are to overlap with resources associated with a second PDSCH format, the base station 110 may transmit a multicast PDSCH communication using resources associated with one multicast downlink format. For example, resources associated with a first PDSCH format (for example, associated with baseline UEs 120) may be a subset of the resources associated with a second PDSCH format (for example, associated with RedCap UEs 120) . The base station 110 may transmit a multicast PDSCH communication using the resources associated with the second PDSCH format. For example, the base station 110 may transmit a first multicast PDSCH communication for baseline UEs 120 using the subset of resources associated with the second PDSCH format. The base station 110 may transmit a second multicast PDSCH communication for RedCap UEs 120 using all of the resources associated with the second PDSCH format. The one or more DCIs transmitted by the base station 110 may have scheduled UEs 120 associated with the first PDSCH format to only receive the multicast PDSCH communication using the subset of the resources associated with a second PDSCH format.

In some aspects, the base station 110 may divide a multicast PDSCH communication into multiple segments. For example, the base station 110 may divide resources associated with a multicast PDSCH communication into multiple repetitions. The base station 110 may encode, rate match, or map the multicast data to a first repetition of the multiple repetitions. The remaining repetitions of the multiple repetitions may repeat the same multicast data. The base station 110 may transmit the multiple repetitions using the resources associated with the multicast PDSCH communication. A DCI transmitted by the base station 110 may have scheduled UEs 120 associated with the first PDSCH format (for example, baseline UEs 120) to only receive one or more of the multiple repetitions. Another DCI transmitted by the base station 110 may have scheduled UEs 120 associated with the second PDSCH format (for example, RedCap UEs 120) to receive all of the multiple repetitions. As a result, the multicast PDSCH communication received by baseline UEs 120 may have a higher spectrum efficiency than the multicast PDSCH communication received by RedCap UEs 120.

In some aspects, the base station 110 may divide resources associated with a multicast PDSCH communication into multiple redundant versions. The base station 110 may encode or rate match the multicast data into the multiple redundant versions. The multiple redundant versions may be mapped to the resources associated with the multicast PDSCH communication in a pre-defined order. The base station 110 may transmit the multiple redundant versions using the resources associated with the multicast PDSCH communication. A DCI transmitted by the base station 110 may have scheduled UEs 120 associated with the first PDSCH format (for example, baseline UEs 120) to only receive one or more of the multiple redundant versions. Another DCI transmitted by the base station 110 may have scheduled UEs 120 associated with the second PDSCH format (for example, RedCap UEs 120) to receive all of the multiple redundant versions. As a result, the multicast PDSCH communication received by baseline UEs 120 may have a higher spectrum efficiency than the multicast PDSCH communication received by RedCap UEs 120.

In an eighth operation 540, the UE 120 may receive a multicast PDSCH communication of the one or more multicast PDSCH communications transmitted by the base station 110. The UE 120 may receive the multicast PDSCH communication in accordance with the multicast downlink format that the UE 120 determined to use for the multicast session. For example, as described above with reference to operation 530, the UE 120 may receive a DCI that schedules a multicast PDSCH communication. The UE 120 may receive the PDSCH communication in accordance with the scheduling information included in the DCI.

For example, the UE 120 may receive the multicast PDSCH communication using a set of resources indicated in the DCI communication. In some aspects, if the UE 120 is a baseline UE 120, the UE 120 may receive one or more segments of a multicast PDSCH communication (for example, one or more repetitions, or one or more redundant versions, among other examples) . In some aspects, if the UE 120 is a RedCap UE 120, the UE 120 may receive all segments of a multicast PDSCH communication (for example, all repetitions, or all redundant versions, among other examples) . This may enable the UE 120 to obtain the multicast data in accordance with a capability of the UE 120.

Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, the described techniques can be used to increase throughput for baseline UEs 120 subscribed to (or configured with) the multicast session, as the baseline UEs 120 may use a downlink format for receiving multicast communications that uses a higher transport format or less resources than would have otherwise been used with a common downlink format for all UEs 120. In some examples, the described techniques can be used to reduce latency for baseline UEs 120 subscribed to (or configured with) the multicast session, as the baseline UEs 120 receive other communications sooner (for example, as other PDSCH communications may be scheduled by a base station 110 during resources that would have otherwise been used with a common downlink format for all UEs 120) . In some examples, the described techniques can be used to reduce power consumption by baseline UEs 120, as less resources may be consumed by the baseline UEs 120 than would have otherwise been used with a common downlink format for all UEs 120 when receiving the multicast communications. In some examples, the described techniques can realize one or more of the above potential advantages for baseline UEs 120 while also ensuring that RedCap UEs 120 that are subscribed to (or configured with) the multicast session are enabled to receive multicast communications (for example, by using a downlink format for RedCap UEs 120 that utilizes a lower transport format or more resources than a downlink format used for baseline UEs 120) .

Figure 6 is a diagram illustrating examples 600, 605, 610, and 615 associated with multicast PDSCH formats, in accordance with various aspects of the present disclosure. As shown in Figure 6, a base station 110 may transmit multiple DCI communications to schedule multiple multicast PDSCH communications during a multicast session, as described above with reference to Figure 5.

As shown in examples 600 and 605, the multiple PDSCH communications may not overlap. That is, resources associated with one PDSCH communication may not overlap with resources associated with another PDSCH communication. As shown in examples 610 and 615, the multiple PDSCH communications may overlap. That is, resources associated with one PDSCH communication may overlap with resources associated with another PDSCH communication.

As shown in example 600, a first DCI 620 may schedule a first multicast PDSCH communication 630. A second DCI 625 may schedule a second multicast PDSCH communication 635. The first multicast PDSCH communication 630 and the second multicast PDSCH communication 635 may carry the same multicast data. In some aspects, the first multicast PDSCH communication 630 may be associated with baseline UEs 120. In some aspects, the second multicast PDSCH communication 635 may be associated with RedCap UEs 120. As shown in Figure 6, the first multicast PDSCH communication 630 may use less time domain resources than the second multicast PDSCH communication 635. As baseline UEs 120 may have a higher communicative capability than RedCap UEs 120, the baseline UEs 120 may be capable of receiving the same multicast data using less time domain resources than RedCap UEs 120. Transmitting the first multicast PDSCH communication 630 and the second multicast PDSCH communication 635 in this manner may increase throughput, decrease latency, or decrease power consumption, among other examples, for baseline UEs 120 while also ensuring that RedCap UEs 120 are enabled to receive the multicast data.

As shown in example 605, a first DCI 640 may schedule a first multicast PDSCH communication 650. A second DCI 645 may schedule a second multicast PDSCH communication 655. The first multicast PDSCH communication 650 and the second multicast PDSCH communication 655 may carry the same multicast data. In some aspects, the first multicast PDSCH communication 650 may be associated with baseline UEs 120. In some aspects, the second multicast PDSCH communication 655 may be associated with RedCap UEs 120. As shown in Figure 6, the first multicast PDSCH communication 650 may use less frequency domain resources than the second multicast PDSCH communication 655. As baseline UEs 120 may have a higher communicative capability than RedCap UEs 120, the baseline UEs 120 may be capable of receiving the same multicast data using less frequency domain resources than RedCap UEs 120. Transmitting the first multicast PDSCH communication 650 and the second multicast PDSCH communication 655 in this manner may increase throughput, decrease latency, or decrease power consumption, among other examples, for baseline UEs 120 while also ensuring that RedCap UEs 120 are enabled to receive the multicast data. In some aspects, a base station 110 may transmit a first multicast PDSCH communication (for example, the first multicast PDSCH communication 630 or the first multicast PDSCH communication 650) using less time domain resources and less frequency domain resources than a second multicast PDSCH communication (for example, the second multicast PDSCH communication 635 or the second multicast PDSCH communication 655) .

As shown in example 610, a first DCI 660 may schedule a first multicast PDSCH communication 670. A second DCI communication 665 may schedule a second multicast PDSCH communication 675. The first multicast PDSCH communication 670 and the second multicast PDSCH communication 675 may carry the same multicast data. The first multicast PDSCH communication 670 and the second multicast PDSCH communication 675 may be transmitted by a base station 110 in single slot. In some aspects, the first multicast PDSCH communication 670 may be associated with a subset of OFDM symbols that are associated with the second multicast PDSCH communication 675. In some aspects, the subset of OFDM symbols associated with the first multicast PDSCH communication 670 may start at a first OFDM symbol associated with the second multicast PDSCH communication 675, as shown in Figure 6. In some aspects, the subset of OFDM symbols associated with the first multicast PDSCH communication 670 may start at a different location within the OFDM symbols associated with the second multicast PDSCH communication 675. For example, a last OFDM symbol associated with the first multicast PDSCH communication 670 may be a last OFDM symbol associated with the second multicast PDSCH communication 675. Transmitting the first multicast PDSCH communication 670 and the second multicast PDSCH communication 675 in this manner may conserve resources associated with the base station 110 transmitting the first multicast PDSCH communication 670 and the second multicast PDSCH communication 675.

As shown in example 615, a first DCI 680 may schedule a first multicast PDSCH communication 690. A second DCI communication 685 may schedule a second multicast PDSCH communication 695. The first multicast PDSCH communication 690 and the second multicast PDSCH communication 695 may carry the same multicast data. The second multicast PDSCH communication 695 may be transmitted by a base station 110 in multiple slots (for example, a first slot and a second slot, as shown in Figure 6) . The first multicast PDSCH communication 690 may be transmitted by the base station 110 in one or more slots of the multiple slots. For example, as shown in Figure 6, the base station 110 may transmit the first multicast PDSCH communication 690 in the first slot. The base station 110 may transmit the second multicast PDSCH communication 695 in the first slot and the second slot. In some aspects, the first multicast PDSCH communication 690 may be transmitted by the base station 110 using a portion of the first slot (for example, using a portion of the OFDM symbols associated with the first slot) . Transmitting the first multicast PDSCH communication 690 and the second multicast PDSCH communication 695 in this manner may conserve resources associated with the base station 110 transmitting the first multicast PDSCH communication 690 and the second multicast PDSCH communication 695.

Figure 7 is a diagram illustrating examples 700 and 705 associated with multicast PDCCH formats, in accordance with various aspects of the present disclosure. As shown in Figure 7, a base station 110 may transmit multiple DCI communications to schedule multiple multicast PDSCH communications during a multicast session, as described above with reference to Figure 5 or Figure 6.

As shown in example 700, the base station 110 may configure a first CORESET 710 (including a first search space) and a second CORESET 715 (including a second search space) . In some aspects, the first CORESET 710 may be associated with baseline UEs 120 and the second CORESET 715 may be associated with RedCap UEs 120. That is, the base station 110 may configure baseline UEs 120 to monitor a PDCCH for DCIs associated with the multicast session in the first CORESET 710 (for example, in the first search space) . The base station 110 may configure RedCap UEs 120 to monitor a PDCCH for DCIs associated with the multicast session in the second CORESET 715 (for example, in the second search space) . The first search space may be a common search space associated with baseline UEs 120. The second search space may be a common search space associated with RedCap UEs 120. The base station 110 may configure all UEs with a common G-RNTI value for receiving DCIs associated with the multicast session.

The base station 110 may transmit a first DCI 720 in the first CORESET 710. The first DCI 720 may schedule a first multicast PDSCH communication 730. The base station 110 may transmit a second DCI 725 in the second CORESET 715. The second DCI 725 may schedule a second multicast PDSCH communication 735. The first multicast PDSCH communication 730 may be scheduled for baseline UEs 120. The second multicast PDSCH communication 735 may be scheduled for RedCap UEs 120. The first multicast PDSCH communication 730 and the second multicast PDSCH communication 735 may carry the same multicast data. In some aspects, the first DCI communication 720 and the second DCI communication 725 may be associated with the same G-RNTI value. In some aspects, the first DCI communication 720 and the second DCI communication 725 may be associated with different G-RNTI values. In some aspects, the first DCI communication 720 may use less CCEs than the second DCI communication 725.

As shown in example 705, the base station 110 may configure a CORESET 740 (including a common search space) for all UEs 120 subscribed to (or configured with) the multicast session. The base station 110 may configure baseline UEs 120 with a first G-RNTI value. The base station 110 may configure RedCap UEs 120 with a second G-RNTI value. Therefore, baseline UEs 120 may be configured to monitor a PDCCH in the common search space for DCIs that are associated with the first G-RNTI value. RedCap UEs 120 may be configured to monitor a PDCCH in the common search space for DCIs that are associated with the second G-RNTI value.

The base station 110 may transmit a first DCI communication 745 that is scrambled with the first G-RNTI value. The first DCI communication may schedule a first multicast PDSCH communication 755. The base station 110 may transmit a second DCI communication 750 that is scrambled with the second G-RNTI value. The second DCI communication may schedule a second multicast PDSCH communication 760. The first multicast PDSCH communication 755 may be scheduled for baseline UEs 120. The second multicast PDSCH communication 760 may be scheduled for RedCap UEs 120. The first multicast PDSCH communication 755 and the second multicast PDSCH communication 755 may carry the same multicast data.

Figure 8 is a diagram illustrating an example 800 associated with multicast PDSCH communications, in accordance with various aspects of the present disclosure. As shown in Figure 8, a base station 110 may transmit multiple DCI communications to schedule multiple multicast PDSCH communications during a multicast session, as described above with reference to Figures 5, 6, or 7.

As shown in Figure 8, the base station 110 may divide a multicast PDSCH communication into multiple segments 810. A segment 810 may be a repetition of multicast data, or a redundant version of multicast data, among other examples. For example, the base station 110 may encode bits of a multicast data packet, rate match the encoded bits, and map the encoded bits to resources associated with a first repetition 810 of the multicast PDSCH communication. The remaining repetitions may be repetitions of the first repetition.

In some aspects, the base station 110 may encode bits of a multicast data packet into multiple redundant versions (for example, the multiple segments 810) . The multiple redundant versions may be mapped to multiple parts of time domain resources of the multicast PDSCH communication (for example, may be mapped to the multiple segments 810) . The base station 110 may map the multiple redundant versions in accordance with a pre-configured order.

The base station 110 may transmit a first DCI communication 815 that schedules a first multicast PDSCH communication 825. The first multicast PDSCH communication 825 may include one or more segments 810 of the multiple segments 810 (for example, one or more repetitions, or one or more redundant versions, among other examples) . The base station 110 may transmit a second DCI communication 820 that schedules a second multicast PDSCH communication 830. The second multicast PDSCH communication 830 may include all of the multiple segments 810 (for example, all of the repetitions, or all of the redundant versions, among other examples) . In some aspects, the first multicast PDSCH communication 825 may be associated with baseline UEs 120 (for example, may be scheduled for baseline UEs 120) . The second multicast PDSCH communication 830 may be associated with RedCap UEs 120 (for example, may be scheduled for RedCap UEs 120) .

The base station 110 may transmit a configuration for the multicast session to all UEs associated with the base station 110. The configuration for the multicast session may indicate whether a PDSCH format for baseline UEs 120 overlaps with a PDSCH format for RedCap UEs 120 (for example, in a bit of an RRC signal, a MAC-CE signal, or a DCI signal, among other examples) . The configuration for the multicast session may indicate a format used for the overlapping PDSCH formats (for example, indicating if the PDSCH formats include repetitions, or redundant versions, among other examples) . The format used for the overlapping PDSCH formats may be indicated in another bit of an RRC signal, a MAC-CE signal, or a DCI signal, among other examples.

Figure 9 is a flowchart illustrating an example process 900 performed, for example, by a UE in accordance with various aspects of the present disclosure. Example process 900 is an example where the UE (for example, UE 120, among other examples) performs operations associated with downlink formats for multicast communications.

As shown in Figure 9, in some aspects, process 900 may include receiving, from a base station, a configuration for a multicast session indicating a plurality of multicast downlink formats (block 910) . For example, the UE (for example, using receive processor 258, transmit processor 264, controller/processor 280, memory 282, or another component) may receive, from a base station, a configuration for a multicast session indicating a plurality of multicast downlink formats, as described above.

As further shown in Figure 9, in some aspects, process 900 may include receiving, from the base station and during the multicast session, a multicast downlink communication in accordance with a multicast downlink format of the plurality of multicast downlink formats (block 920) . For example, the UE (for example, using receive processor 258, transmit processor 264, controller/processor 280, memory 282, or another component) may receive, from the base station and during the multicast session, a multicast downlink communication in accordance with a multicast downlink format of the plurality of multicast downlink formats, as described above.

Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below or in connection with one or more other processes described elsewhere herein.

In a first aspect, process 900 includes determining, based at least in part on a capability of the UE, the multicast downlink format of the plurality of multicast downlink formats.

In a second additional aspect, alone or in combination with the first aspect, the configuration for the multicast session indicates a first physical downlink shared channel (PDSCH) format associated with a first multicast downlink format and a second PDSCH format associated with a second multicast downlink format.

In a third additional aspect, alone or in combination with one or more of the first and second aspects, the configuration for the multicast session indicates that resources associated with the first PDSCH format do not overlap with resources associated with the second PDSCH format.

In a fourth additional aspect, alone or in combination with one or more of the first through third aspects, the configuration for the multicast session indicates that the first PDSCH format is associated with a first transport format and that the second PDSCH format is associated with a second transport format.

In a fifth additional aspect, alone or in combination with one or more of the first through fourth aspects, the configuration for the multicast session indicates that resources associated with the first PDSCH format at least partially overlap with resources associated with the second PDSCH format.

In a sixth additional aspect, alone or in combination with one or more of the first through fifth aspects, the configuration for the multicast session indicates that the resources associated with the first PDSCH format are a subset of the resources associated with the second PDSCH format.

In a seventh additional aspect, alone or in combination with one or more of the first through sixth aspects, the configuration for the multicast session indicates that the second PDSCH format includes a plurality of segments.

In an eighth additional aspect, alone or in combination with one or more of the first through seventh aspects, the configuration for the multicast session indicates that the first PDSCH format is associated with one or more segments of the plurality of segments associated with the second PDSCH format.

In a ninth additional aspect, alone or in combination with one or more of the first through eighth aspects, the configuration for the multicast session indicates that the second PDSCH format includes a plurality of repetitions of multicast data.

In a tenth additional aspect, alone or in combination with one or more of the first through ninth aspects, the configuration for the multicast session indicates that the second PDSCH format includes a plurality of redundant versions of multicast data.

In an eleventh additional aspect, alone or in combination with one or more of the first through tenth aspects, the configuration for the multicast session indicates a first search space associated with a first multicast downlink format and a second search space associated with a second multicast downlink format.

In a twelfth additional aspect, alone or in combination with one or more of the first through eleventh aspects, the configuration for the multicast session indicates a group radio network temporary identifier (G-RNTI) value associated with the first multicast downlink format and associated with the second multicast downlink format.

In a thirteenth additional aspect, alone or in combination with one or more of the first through twelfth aspects, process 900 includes determining, based at least in part on a capability of the UE, a search space, from the first search space and the second search space, to use for receiving multicast downlink communications during the multicast session.

In a fourteenth additional aspect, alone or in combination with one or more of the first through thirteenth aspects, receiving the multicast downlink communication in accordance with the multicast downlink format of the plurality of multicast downlink formats comprises monitoring a physical downlink control channel (PDCCH) for downlink control information (DCI) communications in the search space based at least in part on determining the search space, from the first search space and the second search space, to use for receiving multicast downlink communications during the multicast session; receiving, from the base station, a group-common DCI communication, based at least in part on monitoring the PDCCH for DCI communications in the search space, the group-common DCI communication scheduling a multicast PDSCH communication, and receiving, from the base station, the multicast PDSCH communication based at least in part on receiving the group common DCI communication.

In a fifteenth additional aspect, alone or in combination with one or more of the first through fourteenth aspects, the configuration for the multicast session indicates a first G-RNTI value associated with a first multicast downlink format and a second G-RNTI value associated with a second multicast downlink format.

In a sixteenth additional aspect, alone or in combination with one or more of the first through fifteenth aspects, the configuration for the multicast session indicates a search space associated with the first multicast downlink format and associated with the second multicast downlink format.

In a seventeenth additional aspect, alone or in combination with one or more of the first through sixteenth aspects, process 900 includes determining, based at least in part on a capability of the UE, a G-RNTI value, from the first G-RNTI value and the second G-RNTI value, to use for receiving multicast downlink communications during the multicast session.

In an eighteenth additional aspect, alone or in combination with one or more of the first through seventeenth aspects, receiving the multicast downlink communication in accordance with the multicast downlink format of the plurality of multicast downlink format comprises monitoring a PDCCH in a search space for DCI communications associated with the G-RNTI value based at least in part on determining the G-RNTI value, from the first G-RNTI value and the second G-RNTI value, to use for receiving multicast downlink communications during the multicast session; receiving, from the base station, a group-common DCI communication, associated with the G-RNTI value, scheduling a multicast PDSCH communication, and receiving, from the base station, the multicast PDSCH communication based at least in part on receiving the group-common DCI communication.

In a nineteenth additional aspect, alone or in combination with one or more of the first through eighteenth aspects, receiving the configuration for the multicast session comprises receiving the configuration for the multicast session using at least one of radio resource control (RRC) signaling, medium access control (MAC) signaling, or downlink control information (DCI) signaling.

Figure 10 is a flowchart illustrating an example process 1000 performed, for example, by a base station in accordance with various aspects of the present disclosure. Example process 1000 is an example where the base station (for example, base station 110, among other examples) performs operations associated with downlink formats for multicast communications.

As shown in Figure 10, in some aspects, process 1000 may include transmitting a configuration for a multicast session indicating a plurality of multicast downlink formats (block 1010) . For example, the base station (for example, using transmit processor 220, receive processor 238, controller/processor 240, memory 242, or another component) may transmit a configuration for a multicast session indicating a plurality of multicast downlink formats, as described above.

As further shown in Figure 10, in some aspects, process 1000 may include transmitting, for multicast data, a plurality of multicast downlink communications associated with the multicast data in accordance with the plurality of multicast downlink formats (block 1020) . For example, the base station (for example, using transmit processor 220, receive processor 238, controller/processor 240, memory 242, or another component) may transmit, for multicast data, a plurality of multicast downlink communications associated with the multicast data in accordance with the plurality of multicast downlink formats, as described above.

Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below or in connection with one or more other processes described elsewhere herein.

In a first aspect, process 1000 includes determining whether to transmit multicast data using a common PDSCH communication for all UEs associated with the base station or using different PDSCHs for different subsets of UEs, of all UEs, associated with the base station.

In a second additional aspect, alone or in combination with the first aspect, transmitting the configuration for the multicast session indicating the plurality of multicast downlink formats is based at least in part on determining to transmit multicast data using different PDSCHs for different subsets of UEs, of all UEs, associated with the base station.

In a third additional aspect, alone or in combination with one or more of the first and second aspects, process 1000 includes determining the configuration for the multicast session indicating the plurality of multicast downlink formats based at least in part on capabilities of UEs associated with the base station.

In a fourth additional aspect, alone or in combination with one or more of the first through third aspects, the configuration for the multicast session indicating the plurality of multicast downlink formats comprises an indication of a first PDSCH format associated with a first multicast downlink format, and an indication of a second PDSCH format associated with a second multicast downlink format.

In a fifth additional aspect, alone or in combination with one or more of the first through fourth aspects, the configuration for the multicast session indicating the plurality of multicast downlink formats comprises an indication of whether resources associated with the first PDSCH format overlap with resources associated with the second PDSCH format.

In a sixth additional aspect, alone or in combination with one or more of the first through fifth aspects, the configuration for the multicast session indicating the plurality of multicast downlink formats comprises an indication that resources associated with a first PDSCH format do not overlap with resources associated with a second PDSCH format; an indication that the first PDSCH format is associated with a first transport format, and an indication that the second PDSCH format is associated with a second transport format.

In a seventh additional aspect, alone or in combination with one or more of the first through sixth aspects, transmitting the plurality of multicast downlink communications associated with the multicast data in accordance with the plurality of multicast downlink formats comprises transmitting a first multicast PDSCH communication indicating the multicast data using a first set of resources in accordance with the first PDSCH format, and transmitting a second multicast PDSCH communication indicating the multicast data using a second set of resources in accordance with the second PDSCH format.

In an eighth additional aspect, alone or in combination with one or more of the first through seventh aspects, the configuration for the multicast session indicating the plurality of multicast downlink formats comprises an indication that resources associated with a first PDSCH format do overlap with resources associated with a second PDSCH format, and an indication that the resources associated with the first PDSCH format are a subset of the resources associated with the second PDSCH format.

In a ninth additional aspect, alone or in combination with one or more of the first through eighth aspects, transmitting the plurality of multicast downlink communications associated with the multicast data in accordance with the plurality of multicast downlink formats comprises transmitting a first multicast PDSCH communication indicating the multicast data in accordance with the first PDSCH format using the subset of the resources associated with the second PDSCH format, and transmitting a second multicast PDSCH communication indicating the multicast data in accordance with the second PDSCH format using the resources associated with the second PDSCH format.

In a tenth additional aspect, alone or in combination with one or more of the first through ninth aspects, the resources associated with the second PDSCH format include a plurality of slots in a time domain, and transmitting the plurality of multicast downlink communications associated with the multicast data in accordance with the plurality of multicast downlink formats comprises transmitting a first multicast PDSCH communication indicating the multicast data in accordance with the first PDSCH format in one or more slots of the plurality of slots, and transmitting a second multicast PDSCH communication indicating the multicast data in accordance with the second PDSCH format in the plurality of slots.

In an eleventh additional aspect, alone or in combination with one or more of the first through tenth aspects, the configuration for the multicast session indicating the plurality of multicast downlink formats comprises an indication that the second PDSCH format includes a plurality of segments, and an indication that the first PDSCH format is associated with one or more segments of the plurality of segments.

In a twelfth additional aspect, alone or in combination with one or more of the first through eleventh aspects, the configuration for the multicast session indicating the plurality of multicast downlink formats comprises an indication that the second PDSCH format includes a plurality of repetitions, and an indication that the first PDSCH format is associated with one or more repetitions of the plurality of repetitions.

In a thirteenth additional aspect, alone or in combination with one or more of the first through twelfth aspects, transmitting the plurality of multicast downlink communications associated with the multicast data in accordance with the plurality of multicast downlink formats comprises transmitting the plurality of repetitions of the multicast data in a multicast PDSCH communication, wherein one or more repetitions of the plurality of repetitions are associated with the first PDSCH format and all repetitions of the plurality of repetitions are associated with the second PDSCH format.

In a fourteenth additional aspect, alone or in combination with one or more of the first through thirteenth aspects, transmitting the plurality of multicast downlink communications associated with the multicast data in accordance with the plurality of multicast downlink formats comprises transmitting a first group-common DCI communication to schedule the one or more repetitions of the plurality of repetitions that are associated with the first PDSCH format, and transmitting a second group-common DCI communication to schedule all repetitions of the plurality of repetitions that are associated with the second PDSCH format.

In a fifteenth additional aspect, alone or in combination with one or more of the first through fourteenth aspects, the configuration for the multicast session indicating the plurality of multicast downlink formats comprises an indication that the second PDSCH format includes a plurality of redundant versions, and an indication that the first PDSCH format is associated with one or more redundant versions of the plurality of redundant versions.

In a sixteenth additional aspect, alone or in combination with one or more of the first through fifteenth aspects, transmitting the plurality of multicast downlink communications associated with the multicast data in accordance with the plurality of multicast downlink formats comprises transmitting the plurality of redundant versions of the multicast data in a multicast PDSCH communication, wherein one or more redundant versions of the plurality of redundant versions are associated with the first PDSCH format and all redundant versions of the plurality of redundant versions are associated with the second PDSCH format.

In a seventeenth additional aspect, alone or in combination with one or more of the first through sixteenth aspects, transmitting the plurality of multicast downlink communications associated with the multicast data in accordance with the plurality of multicast downlink formats comprises transmitting a first group-common DCI communication to schedule the one or more redundant versions of the plurality of redundant versions that are associated with the first PDSCH format, and transmitting a second group-common DCI communication to schedule all redundant versions of the plurality of redundant versions that are associated with the second PDSCH format.

In an eighteenth additional aspect, alone or in combination with one or more of the first through seventeenth aspects, the configuration for the multicast session indicating the plurality of multicast downlink formats comprises an indication of a first search space associated with a first multicast downlink format, an indication of a second search space associated with a second multicast downlink format, and an indication of a G-RNTI value associated with the first multicast downlink format and the second multicast downlink format.

In a nineteenth additional aspect, alone or in combination with one or more of the first through eighteenth aspects, transmitting the plurality of multicast downlink communications associated with the multicast data in accordance with the plurality of multicast downlink formats comprises transmitting a first group-common DCI communication associated with the G-RNTI value in the first search space that schedules a first multicast PDSCH communication for the multicast data, and transmitting a second group-common DCI communication associated with the G-RNTI value in the second search space that schedules a second multicast PDSCH communication for the multicast data.

In a twentieth additional aspect, alone or in combination with one or more of the first through nineteenth aspects, the configuration for the multicast session indicating the plurality of multicast downlink formats comprises an indication of a first G-RNTI value associated with a first multicast downlink format, an indication of a second G-RNTI value associated with a second multicast downlink format, and an indication of a search space associated with the first multicast downlink format and the second multicast downlink format.

In a twenty-first additional aspect, alone or in combination with one or more of the first through twentieth aspects, transmitting the plurality of multicast downlink communications associated with the multicast data in accordance with the plurality of multicast downlink formats comprises transmitting a first group-common DCI communication associated with the first G-RNTI value in the search space that schedules a first multicast PDSCH communication for the multicast data, and transmitting a second group-common DCI communication associated with the second G-RNTI value in the search space that schedules a second multicast PDSCH communication for the multicast data.

In a twenty-second additional aspect, alone or in combination with one or more of the first through twenty-first aspects, transmitting the configuration for the multicast session indicating the plurality of multicast downlink formats comprises transmitting, to all UEs associated with the base station, the configuration for the multicast session indicating the plurality of multicast downlink formats.

In a twenty-third additional aspect, alone or in combination with one or more of the first through twenty-second aspects, transmitting the configuration for the multicast session indicating the plurality of multicast downlink formats comprises transmitting the configuration for the multicast session indicating the plurality of multicast downlink formats using at least one of RRC signaling, MAC signaling, or DCI signaling.

Figure 11 is a block diagram of an example apparatus 1100 for wireless communication in accordance with various aspects of the present disclosure. The apparatus 1100 may be a user equipment, or a user equipment may include the apparatus 1100. In some aspects, the apparatus 1100 includes a reception component 1102, a communication manager 1104, and a transmission component 1106, which may be in communication with one another (for example, via one or more buses) . As shown, the apparatus 1100 may communicate with another apparatus 1108 (such as a UE, a base station, or another wireless communication device) using the reception component 1102 and the transmission component 1106.

In some aspects, the apparatus 1100 may be configured to perform one or more operations described herein in connection with Figures 5-8. Additionally or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as process 900 of Figure 9, or a combination thereof. In some aspects, the apparatus 1100 may include one or more components of the user equipment described above in connection with Figure 2.

The reception component 1102 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1108. The reception component 1102 may provide received communications to one or more other components of the apparatus 1100, such as the communication manager 1104. In some aspects, the reception component 1102 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples) , and may provide the processed signals to the one or more other components. In some aspects, the reception component 1102 may include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the user equipment described above in connection with Figure 2.

The transmission component 1106 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1108. In some aspects, the communication manager 1104 may generate communications and may transmit the generated communications to the transmission component 1106 for transmission to the apparatus 1108. In some aspects, the transmission component 1106 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) , and may transmit the processed signals to the apparatus 1108. In some aspects, the transmission component 1106 may include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the user equipment described above in connection with Figure 2. In some aspects, the transmission component 1106 may be co-located with the reception component 1102 in a transceiver.

The communication manager 1104 may receive or more cause the reception component 1102 to receive, from a base station, a configuration for a multicast session indicating a plurality of multicast downlink formats. The communication manager 1104 may receive or more cause the reception component 1102 to receive, from the base station and during the multicast session, a multicast downlink communication in accordance with a multicast downlink format of the plurality of multicast downlink formats. In some aspects, the communication manager 1104 may include a controller/processor, a memory, or a combination thereof, of the user equipment described above in connection with Figure 2.

In some aspects, the communication manager 1104 may include a set of components, such as a determination component 1110, or a combination thereof. Alternatively, the set of components may be separate and distinct from the communication manager 1104. In some aspects, one or more components of the set of components may include or may be implemented within a controller/processor, a memory, or a combination thereof, of the user equipment described above in connection with Figure 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.

The determination component 1110 may determine, based at least in part on a capability of the user equipment, the multicast downlink format of the plurality of multicast downlink formats. The determination component 1110 may determine, based at least in part on a capability of the user equipment, a search space, from a first search space and a second search space, to use for receiving multicast downlink communications during the multicast session. The determination component 1110 may determine, based at least in part on a capability of the user equipment, a G-RNTI value, from a first G- RNTI value and a second G-RNTI value, to use for receiving multicast downlink communications during the multicast session.

The number and arrangement of components shown in Figure 11 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Figure 11. Furthermore, two or more components shown in Figure 11 may be implemented within a single component, or a single component shown in Figure 11 may be implemented as multiple, distributed components. Additionally or alternatively, a set of (one or more) components shown in Figure 11 may perform one or more functions described as being performed by another set of components shown in Figure 11.

Figure 12 is a block diagram of an example apparatus 1200 for wireless communication in accordance with various aspects of the present disclosure. The apparatus 1200 may be a base station, or a base station may include the apparatus 1200. In some aspects, the apparatus 1200 includes a reception component 1202, a communication manager 1204, and a transmission component 1206, which may be in communication with one another (for example, via one or more buses) . As shown, the apparatus 1200 may communicate with another apparatus 1208 (such as a UE, a base station, or another wireless communication device) using the reception component 1202 and the transmission component 1206.

In some aspects, the apparatus 1200 may be configured to perform one or more operations described herein in connection with Figures 5-8. Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as process 1000 of Figure 10, or a combination thereof. In some aspects, the apparatus 1200 may include one or more components of the base station described above in connection with Figure 2.

The reception component 1202 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1208. The reception component 1202 may provide received communications to one or more other components of the apparatus 1200, such as the communication manager 1204. In some aspects, the reception component 1202 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples) , and may provide the processed signals to the one or more other components. In some aspects, the reception component 1202 may include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the base station described above in connection with Figure 2.

The transmission component 1206 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1208. In some aspects, the communication manager 1204 may generate communications and may transmit the generated communications to the transmission component 1206 for transmission to the apparatus 1208. In some aspects, the transmission component 1206 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) , and may transmit the processed signals to the apparatus 1208. In some aspects, the transmission component 1206 may include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the base station described above in connection with Figure 2. In some aspects, the transmission component 1206 may be co-located with the reception component 1202 in a transceiver.

The communication manager 1204 may transmit, or may cause the transmission component 1206 to transmit, a configuration for a multicast session indicating a plurality of multicast downlink formats. The communication manager 1204 may transmit, or may cause the transmission component 1206 to transmit, for multicast data, a plurality of multicast downlink communications associated with the multicast data in accordance with the plurality of multicast downlink formats. In some aspects, the communication manager 1204 may include a controller/processor, a memory, a scheduler, a communication unit, or a combination thereof, of the base station described above in connection with Figure 2.

In some aspects, the communication manager 1204 may include a set of components, such as a determination component 1210, or a combination thereof. Alternatively, the set of components may be separate and distinct from the communication manager 1204. In some aspects, one or more components of the set of components may include or may be implemented within a controller/processor, a memory, a scheduler, a communication unit, or a combination thereof, of the base station described above in connection with Figure 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.

The determination component 1210 may determine whether to transmit multicast data using a common PDSCH communication for all UEs associated with the base station or using different PDSCHs for different subsets of UEs, of all UEs, associated with the base station. The determination component 1210 may determine the configuration for the multicast session indicating the plurality of multicast downlink formats based at least in part on capabilities of UEs associated with the base station.

The number and arrangement of components shown in Figure 12 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Figure 12. Furthermore, two or more components shown in Figure 12 may be implemented within a single component, or a single component shown in Figure 12 may be implemented as multiple, distributed components. Additionally or alternatively, a set of (one or more) components shown in Figure 12 may perform one or more functions described as being performed by another set of components shown in Figure 12.

The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the aspects.

As used herein, the term “component” is intended to be broadly construed as hardware, firmware, or a combination of hardware and software. As used herein, a processor is implemented in hardware, firmware, or a combination of hardware and software. It will be apparent that systems or methods described herein may be implemented in different forms of hardware, firmware, or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems or methods is not limiting of the aspects. Thus, the operation and behavior of the systems or methods were described herein without reference to specific software code-it being understood that software and hardware can be designed to implement the systems or methods based, at least in part, on the description herein.

As used herein, satisfying a threshold may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, or combinations thereof.

Even though particular combinations of features are recited in the claims or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. In fact, many of these features may be combined in ways not specifically recited in the claims or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set. A phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (for example, a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c) .

No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more. ” Further, as used herein, the article “the” is intended to include one or more items referenced in connection with the article “the” and may be used interchangeably with “the one or more. ” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items (for example, related items, unrelated items, or a combination of related and unrelated items) , and may be used interchangeably with “one or more. ” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has, ” “have, ” “having, ” and similar terms are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “or, ” unless explicitly stated otherwise (for example, if used in combination with “either” or “only one of” ) .

Claims

A method of wireless communication performed by a user equipment (UE) , comprising:

receiving, from a base station, a configuration for a multicast session indicating a plurality of multicast downlink formats; and

receiving, from the base station and during the multicast session, a multicast downlink communication in accordance with a multicast downlink format of the plurality of multicast downlink formats.
The method of claim 1, further comprising:

determining, based at least in part on a capability of the UE, the multicast downlink format of the plurality of multicast downlink formats.
The method of claim 1, wherein the configuration for the multicast session indicates a first physical downlink shared channel (PDSCH) format associated with a first multicast downlink format and a second PDSCH format associated with a second multicast downlink format.
The method of claim 3, wherein the configuration for the multicast session indicates that resources associated with the first PDSCH format do not overlap with resources associated with the second PDSCH format.
The method of claim 4, wherein the configuration for the multicast session indicates that the first PDSCH format is associated with a first transport format and that the second PDSCH format is associated with a second transport format.
The method of claim 3, wherein the configuration for the multicast session indicates that resources associated with the first PDSCH format at least partially overlap with resources associated with the second PDSCH format.
The method of claim 6, wherein the configuration for the multicast session indicates that the resources associated with the first PDSCH format are a subset of the resources associated with the second PDSCH format.
The method of claim 6, wherein the configuration for the multicast session indicates that the second PDSCH format includes a plurality of segments.
The method of claim 8, wherein the configuration for the multicast session indicates that the first PDSCH format is associated with one or more segments of the plurality of segments associated with the second PDSCH format.
The method of claim 6, wherein the configuration for the multicast session indicates that the second PDSCH format includes a plurality of repetitions of multicast data.
The method of claim 6, wherein the configuration for the multicast session indicates that the second PDSCH format includes a plurality of redundant versions of multicast data.
The method of claim 1, wherein the configuration for the multicast session indicates a first search space associated with a first multicast downlink format and a second search space associated with a second multicast downlink format.
The method of claim 12, wherein the configuration for the multicast session indicates a group radio network temporary identifier value associated with the first multicast downlink format and associated with the second multicast downlink format.
The method of claim 12, further comprising:

determining, based at least in part on a capability of the UE, a search space, from the first search space and the second search space, to use for receiving multicast downlink communications during the multicast session.
The method of claim 14, wherein receiving the multicast downlink communication in accordance with the multicast downlink format of the plurality of multicast downlink formats comprises:

monitoring a physical downlink control channel (PDCCH) for downlink control information (DCI) communications in the search space based at least in part on determining the search space, from the first search space and the second search space, to use for receiving multicast downlink communications during the multicast session;

receiving, from the base station, a group-common DCI communication, based at least in part on monitoring the PDCCH for DCI communications in the search space, the group-common DCI communication scheduling a multicast physical downlink shared channel (PDSCH) communication; and

receiving, from the base station, the multicast PDSCH communication based at least in part on receiving the group common DCI communication.
The method of claim 1, wherein the configuration for the multicast session indicates a first group radio network temporary identifier (G-RNTI) value associated with a first multicast downlink format and a second G-RNTI value associated with a second multicast downlink format.
The method of claim 16, wherein the configuration for the multicast session indicates a search space associated with the first multicast downlink format and associated with the second multicast downlink format.
The method of claim 16, further comprising:

determining, based at least in part on a capability of the UE, a G-RNTI value, from the first G-RNTI value and the second G-RNTI value, to use for receiving multicast downlink communications during the multicast session.
The method of claim 18, wherein receiving the multicast downlink communication in accordance with the multicast downlink format of the plurality of multicast downlink format comprises:

monitoring a physical downlink control channel (PDCCH) in a search space for downlink control information (DCI) communications associated with the G-RNTI value based at least in part on determining the G-RNTI value, from the first G-RNTI value and the second G-RNTI value, to use for receiving multicast downlink communications during the multicast session;

receiving, from the base station, a group-common DCI communication, associated with the G-RNTI value, scheduling a multicast physical downlink shared channel (PDSCH) communication; and

receiving, from the base station, the multicast PDSCH communication based at least in part on receiving the group-common DCI communication.
The method of claim 1, wherein receiving the configuration for the multicast session comprises:

receiving the configuration for the multicast session using at least one of:

radio resource control (RRC) signaling,

medium access control (MAC) signaling, or

downlink control information (DCI) signaling.
A method of wireless communication performed by a base station, comprising:

transmitting a configuration for a multicast session indicating a plurality of multicast downlink formats; and

transmitting, for multicast data, a plurality of multicast downlink communications associated with the multicast data in accordance with the plurality of multicast downlink formats.
The method of claim 21, further comprising:

determining whether to transmit multicast data using a common physical downlink shared channel (PDSCH) communication for all user equipments (UEs) associated with the base station or using different PDSCHs for different subsets of UEs, of all UEs, associated with the base station.
The method of claim 22, wherein transmitting the configuration for the multicast session indicating the plurality of multicast downlink formats is based at least in part on determining to transmit multicast data using different PDSCHs for different subsets of UEs, of all UEs, associated with the base station.
The method of claim 21, further comprising:

determining the configuration for the multicast session indicating the plurality of multicast downlink formats based at least in part on capabilities of user equipments associated with the base station.
The method of claim 21, wherein the configuration for the multicast session indicating the plurality of multicast downlink formats comprises:

an indication of a first physical downlink shared channel (PDSCH) format associated with a first multicast downlink format; and

an indication of a second PDSCH format associated with a second multicast downlink format.
The method of claim 25, wherein the configuration for the multicast session indicating the plurality of multicast downlink formats comprises:

an indication of whether resources associated with the first PDSCH format overlap with resources associated with the second PDSCH format.
The method of claim 21, wherein the configuration for the multicast session indicating the plurality of multicast downlink formats comprises:

an indication that resources associated with a first physical downlink shared channel (PDSCH) format do not overlap with resources associated with a second PDSCH format;

an indication that the first PDSCH format is associated with a first transport format; and

an indication that the second PDSCH format is associated with a second transport format.
The method of claim 27, wherein transmitting the plurality of multicast downlink communications associated with the multicast data in accordance with the plurality of multicast downlink formats comprises:

transmitting a first multicast PDSCH communication indicating the multicast data using a first set of resources in accordance with the first PDSCH format; and

transmitting a second multicast PDSCH communication indicating the multicast data using a second set of resources in accordance with the second PDSCH format.
The method of claim 21, wherein the configuration for the multicast session indicating the plurality of multicast downlink formats comprises:

an indication that resources associated with a first physical downlink shared channel (PDSCH) format do overlap with resources associated with a second PDSCH format; and

an indication that the resources associated with the first PDSCH format are a subset of the resources associated with the second PDSCH format.
The method of claim 29, wherein transmitting the plurality of multicast downlink communications associated with the multicast data in accordance with the plurality of multicast downlink formats comprises:

transmitting a first multicast PDSCH communication indicating the multicast data in accordance with the first PDSCH format using the subset of the resources associated with the second PDSCH format; and

transmitting a second multicast PDSCH communication indicating the multicast data in accordance with the second PDSCH format using the resources associated with the second PDSCH format.
The method of claim 29, wherein the resources associated with the second PDSCH format include a plurality of slots in a time domain, and wherein transmitting the plurality of multicast downlink communications associated with the multicast data in accordance with the plurality of multicast downlink formats comprises:

transmitting a first multicast PDSCH communication indicating the multicast data in accordance with the first PDSCH format in one or more slots of the plurality of slots; and

transmitting a second multicast PDSCH communication indicating the multicast data in accordance with the second PDSCH format in the plurality of slots.
The method of claim 29, wherein the configuration for the multicast session indicating the plurality of multicast downlink formats comprises:

an indication that the second PDSCH format includes a plurality of segments; and

an indication that the first PDSCH format is associated with one or more segments of the plurality of segments.
The method of claim 29, wherein the configuration for the multicast session indicating the plurality of multicast downlink formats comprises:

an indication that the second PDSCH format includes a plurality of repetitions; and

an indication that the first PDSCH format is associated with one or more repetitions of the plurality of repetitions.
The method of claim 33, wherein transmitting the plurality of multicast downlink communications associated with the multicast data in accordance with the plurality of multicast downlink formats comprises:

transmitting the plurality of repetitions of the multicast data in a multicast PDSCH communication, wherein one or more repetitions of the plurality of repetitions are associated with the first PDSCH format and all repetitions of the plurality of repetitions are associated with the second PDSCH format.
The method of claim 34, wherein transmitting the plurality of multicast downlink communications associated with the multicast data in accordance with the plurality of multicast downlink formats comprises:

transmitting a first group-common downlink control information (DCI) communication to schedule the one or more repetitions of the plurality of repetitions that are associated with the first PDSCH format; and

transmitting a second group-common DCI communication to schedule all repetitions of the plurality of repetitions that are associated with the second PDSCH format.
The method of claim 29, wherein the configuration for the multicast session indicating the plurality of multicast downlink formats comprises:

an indication that the second PDSCH format includes a plurality of redundant versions; and

an indication that the first PDSCH format is associated with one or more redundant versions of the plurality of redundant versions.
The method of claim 36, wherein transmitting the plurality of multicast downlink communications associated with the multicast data in accordance with the plurality of multicast downlink formats comprises:

transmitting the plurality of redundant versions of the multicast data in a multicast PDSCH communication, wherein one or more redundant versions of the plurality of redundant versions are associated with the first PDSCH format and all redundant versions of the plurality of redundant versions are associated with the second PDSCH format.
The method of claim 37, wherein transmitting the plurality of multicast downlink communications associated with the multicast data in accordance with the plurality of multicast downlink formats comprises:

transmitting a first group-common downlink control information (DCI) communication to schedule the one or more redundant versions of the plurality of redundant versions that are associated with the first PDSCH format; and

transmitting a second group-common DCI communication to schedule all redundant versions of the plurality of redundant versions that are associated with the second PDSCH format.
The method of claim 21, wherein the configuration for the multicast session indicating the plurality of multicast downlink formats comprises:

an indication of a first search space associated with a first multicast downlink format;

an indication of a second search space associated with a second multicast downlink format; and

an indication of a group radio network temporary identifier (G-RNTI) value associated with the first multicast downlink format and the second multicast downlink format.
The method of claim 39, wherein transmitting the plurality of multicast downlink communications associated with the multicast data in accordance with the plurality of multicast downlink formats comprises:

transmitting a first group-common downlink control information (DCI) communication associated with the G-RNTI value in the first search space that schedules a first multicast PDSCH communication for the multicast data; and

transmitting a second group-common DCI communication associated with the G-RNTI value in the second search space that schedules a second multicast PDSCH communication for the multicast data.
The method of claim 21, wherein the configuration for the multicast session indicating the plurality of multicast downlink formats comprises:

an indication of a first group radio network temporary identifier (G-RNTI) value associated with a first multicast downlink format;

an indication of a second G-RNTI value associated with a second multicast downlink format; and

an indication of a search space associated with the first multicast downlink format and the second multicast downlink format.
The method of claim 41, wherein transmitting the plurality of multicast downlink communications associated with the multicast data in accordance with the plurality of multicast downlink formats comprises:

transmitting a first group-common downlink control information (DCI) communication associated with the first G-RNTI value in the search space that schedules a first multicast PDSCH communication for the multicast data; and

transmitting a second group-common DCI communication associated with the second G-RNTI value in the search space that schedules a second multicast PDSCH communication for the multicast data.
The method of claim 21, wherein transmitting the configuration for the multicast session indicating the plurality of multicast downlink formats comprises:

transmitting, to all user equipments associated with the base station, the configuration for the multicast session indicating the plurality of multicast downlink formats.
The method of claim 21, wherein transmitting the configuration for the multicast session indicating the plurality of multicast downlink formats comprises:

transmitting the configuration for the multicast session indicating the plurality of multicast downlink formats using at least one of:

radio resource control (RRC) signaling,

medium access control (MAC) signaling, or

downlink control information (DCI) signaling.
A user equipment (UE) for wireless communication, comprising:

a memory; and

one or more processors operatively coupled to the memory, the memory and the one or more processors configured to:

receive, from a base station, a configuration for a multicast session indicating a plurality of multicast downlink formats; and

receive, from the base station and during the multicast session, a multicast downlink communication in accordance with a multicast downlink format of the plurality of multicast downlink formats.
A base station for wireless communication, comprising:

a memory; and

one or more processors operatively coupled to the memory, the memory and the one or more processors configured to:

transmit a configuration for a multicast session indicating a plurality of multicast downlink formats; and

transmit, for multicast data, a plurality of multicast downlink communications associated with the multicast data in accordance with the plurality of multicast downlink formats.
A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising:

one or more instructions that, when executed by one or more processors of a user equipment (UE) , cause the UE to:

receive, from a base station, a configuration for a multicast session indicating a plurality of multicast downlink formats; and

receive, from the base station and during the multicast session, a multicast downlink communication in accordance with a multicast downlink format of the plurality of multicast downlink formats.
A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising:

one or more instructions that, when executed by one or more processors of a base station, cause the base station to:

transmit a configuration for a multicast session indicating a plurality of multicast downlink formats; and

transmit, for multicast data, a plurality of multicast downlink communications associated with the multicast data in accordance with the plurality of multicast downlink formats.
An apparatus for wireless communication, comprising:

means for receiving, from a base station, a configuration for a multicast session indicating a plurality of multicast downlink formats; and

means for receiving, from the base station and during the multicast session, a multicast downlink communication in accordance with a multicast downlink format of the plurality of multicast downlink formats.
An apparatus for wireless communication, comprising:

means for transmitting a configuration for a multicast session indicating a plurality of multicast downlink formats; and

means for transmitting, for multicast data, a plurality of multicast downlink communications associated with the multicast data in accordance with the plurality of multicast downlink formats.