Group downlink control information for multi-user multiple-input-multiple-output communication

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may receive group downlink control information (DCI) indicating multi-user multiple-input-multiple-output (MU-MIMO) scheduling for a multi-user group of UEs. The UE may communicate in accordance with the group DCI. Numerous other aspects are described.

Description

GROUP DOWNLINK CONTROL INFORMATION FOR MULTI-USERMULTIPLE-INPUT-MULTIPLE-OUTPUT COMMUNICATIONCROSS-REFERENCE TO RELATED APPLICATION

[0001] This Patent Application claims priority to U.S. Patent Application No. 18 / 765,946, filed on July 8, 2024, entitled “GROUP DOWNLINK CONTROL INFORMATION FOR MULTI-USER MULTIPLE-INPUT-MULTIPLE-OUTPUT COMMUNICATION,” and assigned to the assignee hereof. The disclosure of the prior Application is considered part of and is incorporated by reference into this Patent Application.FIELD OF THE DISCLOSURE

[0002] Aspects of the present disclosure generally relate to wireless communication and specifically relate to techniques, apparatuses, and methods for group downlink control information (DCI) for multi-user multiple -input-multiple -output (MIMO) communication.BACKGROUND

[0003] Wireless communication systems are widely deployed to provide various services that may include carrying voice, text, messaging, video, data, and / or other traffic. The services may include unicast, multicast, and / or broadcast services, among other examples. Typical wireless communication systems may employ multiple-access radio access technologies (RATs) capable of supporting communication with multiple users by sharing available system resources (for example, time domain resources, frequency domain resources, spatial domain resources, and / or device transmit power, among other examples). Examples of such multiple-access RATs 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, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0004] The above multiple-access RATs have been adopted in various telecommunication standards to provide common protocols that enable different wireless communication devices to communicate on a municipal, national, regional, or global level. An example telecommunication standard is New Radio (NR). NR, which may also be referred to as 5G, is part of a continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3 GPP). NR (and other mobile broadband evolutions beyond NR) may be designed to better support Internet of things (loT) and reduced capability device deployments, industrial connectivity, millimeter wave (mmWave) expansion, licensed and unlicensed spectrum access, non-terrestrial network (NTN) deployment, sidelink and other device-to-device direct communication technologies (for example, cellular vehicle-to-everything (CV2X) communication), massive multiple -input multiple -output (MIMO), disaggregated network architectures and network topology expansions, multiple-subscriber implementations, high- precision positioning, and / or radio frequency (RF) sensing, among other examples. As the demand for mobile broadband access continues to increase, further improvements in NR may be implemented, and other radio access technologies such as 6G may be introduced, to further advance mobile broadband evolution.BRIEF DESCRIPTION OF THE DRAWINGS

[0005] The appended drawings illustrate some aspects of the present disclosure, but are not limiting of the scope of the present disclosure because the description may enable other aspects. Each of the drawings is provided for purposes of illustration and description, and not as a definition of the limits of the claims. The same or similar reference numbers in different drawings may identify the same or similar elements.

[0006] Fig. 1 is a diagram illustrating an example of a wireless communication network in accordance with the present disclosure.

[0007] Fig. 2 is a diagram illustrating an example network node in communication with an example user equipment (UE) in a wireless network in accordance with the present disclosure.

[0008] Fig. 3 is a diagram illustrating an example disaggregated base station architecture in accordance with the present disclosure.

[0009] Fig. 4 is a diagram of an example associated with group downlink control information (DCI) for multi-user multiple-input-multiple-output (MU-MIMO) communication, in accordance with the present disclosure.

[0010] Fig. 5 is a diagram illustrating an example process performed, for example, at a UE or an apparatus of a UE, in accordance with the present disclosure.

[0011] Fig. 6 is a diagram illustrating an example process performed, for example, at a network node or an apparatus of a network node, in accordance with the present disclosure.

[0012] Fig. 7 is a diagram of an example apparatus for wireless communication, in accordance with the present disclosure.

[0013] Fig. 8 is a diagram of an example apparatus for wireless communication, in accordance with the present disclosure.SUMMARY

[0014] Some aspects described herein relate to an apparatus for wireless communication at a user equipment (UE). The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may beconfigured to cause the UE to receive group downlink control information (DCI) indicating multi-user multiple-input-multiple-output (MU-MIMO) scheduling for a multi-user group of UEs. The one or more processors may be configured to cause the UE to communicate in accordance with the group DCL

[0015] Some aspects described herein relate to an apparatus for wireless communication at a network node. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to cause the network node to transmit, for a UE, group DCI indicating MU-MIMO scheduling for a multi-user group of UEs. The one or more processors may be configured to cause the network node to communicate in accordance with the group DCI.

[0016] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving group DCI indicating MU-MIMO scheduling for a multi-user group of UEs. The method may include communicating in accordance with the group DCI.

[0017] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include transmitting, for a UE, group DCI indicating MU-MIMO scheduling for a multi-user group of UEs. The method may include communicating in accordance with the group DCI.

[0018] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive group DCI indicating MU-MIMO scheduling for a multi-user group of UEs. The set of instructions, when executed by one or more processors of the UE, may cause the UE to communicate in accordance with the group DCI.

[0019] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to transmit, for a UE, group DCI indicating MU-MIMO scheduling for a multiuser group of UEs. The set of instructions, when executed by one or more processors of the network node, may cause the network node to communicate in accordance with the group DCI.

[0020] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving group DCI indicating MU-MIMO scheduling for a multi-user group of UEs. The apparatus may include means for communicating in accordance with the group DCI.

[0021] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting, for a UE, group DCI indicating MU-MIMOscheduling for a multi-user group of UEs. The apparatus may include means for communicating in accordance with the group DCI.

[0022] Aspects of the present disclosure may generally be implemented by or as a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, network node, network entity, wireless communication device, and / or processing system as substantially described with reference to, and as illustrated by, the specification and accompanying drawings.

[0023] The foregoing paragraphs of this section have broadly summarized some aspects of the present disclosure. These and additional aspects and associated advantages will be described hereinafter. The disclosed aspects may be used as a basis for modifying or designing other aspects for carrying out the same or similar purposes of the present disclosure. Such equivalent aspects do not depart from the scope of the appended claims. Characteristics of the aspects 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 drawings.DETAILED DESCRIPTION

[0024] Various aspects of the present disclosure are described hereinafter with reference to the accompanying drawings. However, aspects of the present disclosure may be embodied in many different forms and is not to be construed as limited to any specific aspect illustrated by or described with reference to an accompanying drawing or otherwise presented in 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. 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 in combination with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using various combinations or quantities of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover an apparatus having, or a method that is practiced using, other structures and / or functionalities in addition to or other than the structures and / or functionalities with which various aspects of the disclosure set forth herein may be practiced. Any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

[0025] Several aspects of telecommunication systems will now be presented with reference to various methods, operations, apparatuses, and techniques. These methods, operations, 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 (collectively referred to as “elements”). These elements may beimplemented using hardware, software, or a combination of hardware and software. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

[0026] Multiple -input-multiple -output (MIMO) generally refers to transmitting or receiving multiple signals (such as multiple layers or multiple data streams) simultaneously over the same time and frequency resources. MIMO techniques generally exploit multipath propagation. MIMO may be implemented using various spatial processing or spatial multiplexing operations. In some examples, MIMO may support simultaneous transmission to multiple receivers, referred to as multi-user MIMO (MU-MIMO). In MU-MIMO, a network node may communicate with multiple user equipments (UEs) in a multi-user group. The UEs in the multiuser group may be scheduled with a time-frequency resource allocation. The UEs in the multiuser group may share the time -frequency resource but may be assigned to different spatial layers.

[0027] To schedule the UEs in the multi-user group, the network node may transmit multiple downlink control information (DCI) communications to respective UEs in the multi-user group, and each UE in the multi-user group may blindly decode a respective physical downlink control channel (PDCCH). For example, each DCI may have a cyclic redundancy check (CRC) scrambled by a respective cell radio network temporary identifier (C-RNTI) for each UE in the multi-user group. The transmission of separate DCI for each UE in the multi-user group creates significant control signaling overhead. Moreover, the transmission of separate DCI for each UE in the multi-user group may produce PDCCH blocking or other congestion in PDCCH resources, thereby degrading PDCCH performance. In addition, MU-MIMO scheduling, which may be implemented at the network node, may be transparent to UEs in the multi -group (e.g., a UE may be unaware that its respective DCI is associated with scheduling for MU-MIMO communication), and as a result the UEs may not take corrective measures for interference.

[0028] Various aspects relate generally to group DCI for a multi-user group of UEs. Some aspects more specifically relate to group DCI that indicates MU-MIMO scheduling for the multi-user group of UEs, and communication between a network node and the UEs in accordance with MU-MIMO scheduling. In some aspects, the group DCI may include common information for the multi-user group of UEs, and respective UE-specific information (e.g., information intended for a single UE) for each UE in the multi-user group of UEs. For example, the common information may indicate a time and frequency resource that is to be shared by the multi-user group of UEs. In some aspects, in accordance with the MU-MIMO scheduling (e.g., using the shared resource), each UE of the multi-user group may communicate respective data with the network node (e.g., rather than the same data being communicated between the network node and the UEs of the multi-user group). In some aspects, the groupDCI may include an indication of which UEs of the multi-user group are scheduled by the group DCI and which UEs of the multi-user group are not scheduled by the group DCE

[0029] 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, by scheduling MU-MIMO communication for a multi-user group of UEs using group DCI, the described techniques can be used to reduce control signaling overhead and reduce a probability of PDCCH blocking, thereby improving PDCCH performance. In addition, the group DCI provides implicit network assistance information, because UEs that are aware that the scheduling is for MU-MIMO can act to cancel or mitigate multi-user interference in downlink MU-MIMO, thereby improving a performance of downlink communications. Moreover, by including group common information and UE-specific information in the group DCI, the described techniques can be used to provide scheduling flexibility for individual UEs while minimizing an overall payload size of the group DCI to facilitate efficient utilization of network resources. In some examples, by including an indication of which UEs of the multi-user group are, and are not, scheduled by the group DCI, the group DCI may facilitate conservation of radio resources. For example, physical uplink control channel (PUCCH) resources that are allocated to UEs in the multi-user group may be allocated to only the UEs that are scheduled by the group DCI, thereby reducing the number of PUCCH resources that need to be allocated.

[0030] Multiple -access radio access technologies (RATs) have been adopted in various telecommunication standards to provide common protocols that enable wireless communication devices to communicate on a municipal, enterprise, national, regional, or global level. For example, 5G New Radio (NR) is part of a continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP). 5G NR supports various technologies and use cases including enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine-type communication (mMTC), millimeter wave (mmWave) technology, beamforming, network slicing, edge computing, Internet of Things (loT) connectivity and management, and network function virtualization (NFV).

[0031] As the demand for broadband access increases and as technologies supported by wireless communication networks evolve, further technological improvements may be adopted in or implemented for 5G NR or future RATs, such as 6G, to further advance the evolution of wireless communication for a wide variety of existing and new use cases and applications. Such technological improvements may be associated with new frequency band expansion, licensed and unlicensed spectrum access, overlapping spectrum use, small cell deployments, nonterrestrial network (NTN) deployments, disaggregated network architectures and network topology expansion, device aggregation, advanced duplex communication, sidelink and other device-to-device direct communication, loT (including passive or ambient loT) networks, reduced capability (RedCap) UE functionality, industrial connectivity, multiple-subscriberimplementations, high-precision positioning, radio frequency (RF) sensing, and / or artificial intelligence or machine learning (AI / ML), among other examples. These technological improvements may support use cases such as wireless backhauls, wireless data centers, extended reality (XR) and metaverse applications, meta services for supporting vehicle connectivity, holographic and mixed reality communication, autonomous and collaborative robots, vehicle platooning and cooperative maneuvering, sensing networks, gesture monitoring, human-brain interfacing, digital twin applications, asset management, and universal coverage applications using non-terrestrial and / or aerial platforms, among other examples. The methods, operations, apparatuses, and techniques described herein may enable one or more of the foregoing technologies and / or support one or more of the foregoing use cases.

[0032] Fig. 1 is a diagram illustrating an example of a wireless communication network 100 in accordance with the present disclosure. The wireless communication network 100 may be or may include elements of a 5G (or NR) network or a 6G network, among other examples. The wireless communication network 100 may include multiple network nodes 110, shown as a network node (NN) 110a, a network node 110b, a network node 110c, and a network node 1 lOd. The network nodes 110 may support communications with multiple UEs 120, shown as a UE 120a, a UE 120b, a UE 120c, a UE 120d, and a UE 120e.

[0033] The network nodes 110 and the UEs 120 of the wireless communication network 100 may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, carriers, and / or channels. For example, devices of the wireless communication network 100 may communicate using one or more operating bands. In some aspects, multiple wireless networks 100 may be deployed in a given geographic area. Each wireless communication network 100 may support a particular RAT (which may also be referred to as an air interface) and may operate on one or more carrier frequencies in one or more frequency ranges. Examples of RATs include a 4G RAT, a 5G / NR RAT, and / or a 6G RAT, among other examples. In some examples, when multiple RATs are deployed in a given geographic area, each RAT in the geographic area may operate on different frequencies to avoid interference with one another.

[0034] Various operating bands have been defined as frequency range designations FR1 (410 MHz through 7.125 GHz), FR2 (24.25 GHz through 52.6 GHz), FR3 (7.125 GHz through 24.25 GHz), FR4a or FR4-1 (52.6 GHz through 71 GHz), FR4 (52.6 GHz through 114.25 GHz), and FR5 (114.25 GHz through 300 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in some documents and articles. Similarly, FR2 is often referred to (interchangeably) as a “millimeter wave” band in some documents and articles, despite being different than the extremely high frequency (EHF) band (30 GHz through 300 GHz), which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band. The frequencies between FR1 and FR2 are often referred toas mid-band frequencies, which include FR3. Frequency bands falling within FR3 may inherit FR1 characteristics or FR2 characteristics, and thus may effectively extend features of FR1 or FR2 into mid-band frequencies. Thus, “sub-6 GHz,” if used herein, may broadly refer to frequencies that are less than 6 GHz, that are within FR1, and / or that are included in mid -band frequencies. Similarly, the term “millimeter wave,” if used herein, may broadly refer to frequencies that are included in mid-band frequencies, that are within FR2, FR4, FR4-a or FR4- 1, or FR5, and / or that are within the EHF band. Higher frequency bands may extend 5G NR operation, 6G operation, and / or other RATs beyond 52.6 GHz. For example, each of FR4a, FR4-1, FR4, and FR5 falls within the EHF band. In some examples, the wireless communication network 100 may implement dynamic spectrum sharing (DSS), in which multiple RATs (for example, 4G / LTE and 5G / NR) are implemented with dynamic bandwidth allocation (for example, based on user demand) in a single frequency band. It is contemplated that the frequencies included in these operating bands (for example, FR1, FR2, FR3, FR4, FR4- a, FR4-1, and / or FR5) may be modified, and techniques described herein may be applicable to those modified frequency ranges.

[0035] A network node 110 may include one or more devices, components, or systems that enable communication between a UE 120 and one or more devices, components, or systems of the wireless communication network 100. A network node 110 may be, may include, or may also be referred to as an NR network node, a 5G network node, a 6G network node, a Node B, an eNB, a gNB, an access point (AP), a transmission reception point (TRP), a mobility element, a core, a network entity, a network element, a network equipment, and / or another type of device, component, or system included in a radio access network (RAN).

[0036] A network node 110 may be implemented as a single physical node (for example, a single physical structure) or may be implemented as two or more physical nodes (for example, two or more distinct physical structures). For example, a network node 110 may be a device or system that implements part of a radio protocol stack, a device or system that implements a full radio protocol stack (such as a full gNB protocol stack), or a collection of devices or systems that collectively implement the full radio protocol stack. For example, and as shown, a network node 110 may be an aggregated network node (having an aggregated architecture), meaning that the network node 110 may implement a full radio protocol stack that is physically and logically integrated within a single node (for example, a single physical structure) in the wireless communication network 100. For example, an aggregated network node 110 may consist of a single standalone base station or a single TRP that uses a full radio protocol stack to enable or facilitate communication between a UE 120 and a core network of the wireless communication network 100.

[0037] Alternatively, and as also shown, a network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), meaning that the networknode 110 may implement a radio protocol stack that is physically distributed and / or logically distributed among two or more nodes in the same geographic location or in different geographic locations. For example, a disaggregated network node may have a disaggregated architecture. In some deployments, disaggregated network nodes 110 may be used in an integrated access and backhaul (IAB) network, in an open radio access network (O-RAN) (such as a network configuration in compliance with the O-RAN Alliance), or in a virtualized radio access network (vRAN), also known as a cloud radio access network (C-RAN), to facilitate scaling by separating base station functionality into multiple units that can be individually deployed.

[0038] The network nodes 110 of the wireless communication network 100 may include one or more central units (CUs), one or more distributed units (DUs), and / or one or more radio units (RUs). A CU may host one or more higher layer control functions, such as radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, and / or service data adaptation protocol (SDAP) functions, among other examples. A DU may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and / or one or more higher physical (PHY) layers depending, at least in part, on a functional split, such as a functional split defined by the 3GPP. In some examples, a DU also may host one or more lower PHY layer functions, such as a fast Fourier transform (FFT), an inverse FFT (iFFT), beamforming, physical random access channel (PRACH) extraction and filtering, and / or scheduling of resources for one or more UEs 120, among other examples. An RU may host RF processing functions or lower PHY layer functions, such as an FFT, an iFFT, beamforming, or PRACH extraction and filtering, among other examples, according to a functional split, such as a lower layer functional split. In such an architecture, each RU can be operated to handle over the air (OTA) communication with one or more UEs 120.

[0039] In some aspects, a single network node 110 may include a combination of one or more CUs, one or more DUs, and / or one or more RUs. Additionally or alternatively, a network node 110 may include one or more Near-Real Time (Near-RT) RAN Intelligent Controllers (RICs) and / or one or more Non-Real Time (Non-RT) RICs. In some examples, a CU, a DU, and / or an RU may be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among other examples. A virtual unit may be implemented as a virtual network function, such as associated with a cloud deployment.

[0040] Some network nodes 110 (for example, a base station, an RU, or a TRP) may provide communication coverage for a particular geographic area. In the 3GPP, the term “cell” can refer to a coverage area of a network node 110 or to a network node 110 itself, depending on the context in which the term is used. A network node 110 may support one or multiple (for example, three) cells. In some examples, a network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, or another type of cell. A macro cell maycover a relatively large geographic area (for example, several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions. A femto cell may cover a relatively small geographic area (for example, a home) and may allow restricted access by UEs 120 having association with the femto cell (for example, UEs 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. A network node 110 for a femto cell may be referred to as a femto network node or an in-home network node. In some examples, a cell may not necessarily be stationary. For example, the geographic area of the cell may move according to the location of an associated mobile network node 110 (for example, a train, a satellite base station, an unmanned aerial vehicle, or an NTN network node).

[0041] The wireless communication network 100 may be a heterogeneous network that includes network nodes 110 of different types, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, aggregated network nodes, and / or disaggregated network nodes, among other examples. In the example shown in Fig. 1, the network node 110a may be a macro network node for a macro cell 130a, the network node 110b may be a pico network node for a pico cell 130b, and the network node 110c may be a femto network node for a femto cell 130c.Various different types of network nodes 110 may generally transmit at different power levels, serve different coverage areas, and / or have different impacts on interference in the wireless communication network 100 than other types of network nodes 110. For example, macro network nodes may have a high transmit power level (for example, 5 to 40 watts), whereas pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (for example, 0.1 to 2 watts).

[0042] In some examples, a network node 110 may be, may include, or may operate as an RU, a TRP, or a base station that communicates with one or more UEs 120 via a radio access link (which may be referred to as a “Uu” link). The radio access link may include a downlink and an uplink. “Downlink” (or “DL”) refers to a communication direction from a network node 110 to a UE 120, and “uplink” (or “UL”) refers to a communication direction from a UE 120 to a network node 110. Downlink channels may include one or more control channels and one or more data channels. A downlink control channel may be used to transmit downlink control information (DCI) (for example, scheduling information, reference signals, and / or configuration information) from a network node 110 to a UE 120. A downlink data channel may be used to transmit downlink data (for example, user data associated with a UE 120) from a network node 110 to a UE 120. Downlink control channels may include one or more physical downlink control channels (PDCCHs), and downlink data channels may include one or more physical downlink shared channels (PDSCHs). Uplink channels may similarly include one or morecontrol channels and one or more data channels. An uplink control channel may be used to transmit uplink control information (UCI) (for example, reference signals and / or feedback corresponding to one or more downlink transmissions) from a UE 120 to a network node 110. An uplink data channel may be used to transmit uplink data (for example, user data associated with a UE 120) from a UE 120 to a network node 110. Uplink control channels may include one or more physical uplink control channels (PUCCHs), and uplink data channels may include one or more physical uplink shared channels (PUSCHs). The downlink and the uplink may each include a set of resources on which the network node 110 and the UE 120 may communicate.

[0043] Downlink and uplink resources may include time domain resources (frames, subframes, slots, and / or symbols), frequency domain resources (frequency bands, component carriers, subcarriers, resource blocks, and / or resource elements), and / or spatial domain resources (particular transmit directions and / or beam parameters). Frequency domain resources of some bands may be subdivided into bandwidth parts (BWPs). A BWP may be a continuous block of frequency domain resources (for example, a continuous block of resource blocks) that are allocated for one or more UEs 120. A UE 120 may be configured with both an uplink BWP and a downlink BWP (where the uplink BWP and the downlink BWP may be the same BWP or different BWPs). A BWP may be dynamically configured (for example, by a network node 110 transmitting a DCI configuration to the one or more UEs 120) and / or reconfigured, which means that a BWP can be adjusted in real-time (or near-real-time) based on changing network conditions in the wireless communication network 100 and / or based on the specific requirements of the one or more UEs 120. This enables more efficient use of the available frequency domain resources in the wireless communication network 100 because fewer frequency domain resources may be allocated to a BWP for a UE 120 (which may reduce the quantity of frequency domain resources that a UE 120 is required to monitor), leaving more frequency domain resources to be spread across multiple UEs 120. Thus, BWPs may also assist in the implementation of lower-capability UEs 120 by facilitating the configuration of smaller bandwidths for communication by such UEs 120.

[0044] As described above, in some aspects, the wireless communication network 100 may be, may include, or may be included in, an IAB network. In an IAB network, at least one network node 110 is an anchor network node that communicates with a core network. An anchor network node 110 may also be referred to as an IAB donor (or “lAB-donor”). The anchor network node 110 may connect to the core network via a wired backhaul link. For example, an Ng interface of the anchor network node 110 may terminate at the core network. Additionally or alternatively, an anchor network node 110 may connect to one or more devices of the core network that provide a core access and mobility management function (AMF). An IAB network also generally includes multiple non-anchor network nodes 110, which may alsobe referred to as relay network nodes or simply as IAB nodes (or “lAB-nodes”). Each nonanchor network node 110 may communicate directly with the anchor network node 110 via a wireless backhaul link to access the core network, or may communicate indirectly with the anchor network node 110 via one or more other non-anchor network nodes 110 and associated wireless backhaul links that form a backhaul path to the core network. Some anchor network node 110 or other non-anchor network node 110 may also communicate directly with one or more UEs 120 via wireless access links that carry access traffic. In some examples, network resources for wireless communication (such as time resources, frequency resources, and / or spatial resources) may be shared between access links and backhaul links.

[0045] In some examples, any network node 110 that relays communications may be referred to as a relay network node, a relay station, or simply as a relay. A relay may receive a transmission of a communication from an upstream station (for example, another network node 110 or a UE 120) and transmit the communication to a downstream station (for example, a UE 120 or another network node 110). In this case, the wireless communication network 100 may include or be referred to as a “multi-hop network.” In the example shown in Fig. 1, the network node 1 lOd (for example, a relay network node) may communicate with the network node 110a (for example, a macro network node) and the UE 120d in order to facilitate communication between the network node 110a and the UE 120d. Additionally or alternatively, a UE 120 may be or may operate as a relay station that can relay transmissions to or from other UEs 120. A UE 120 that relays communications may be referred to as a UE relay or a relay UE, among other examples.

[0046] The UEs 120 may be physically dispersed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile. A UE 120 may be, may include, or may be included in an access terminal, another terminal, a mobile station, or a subscriber unit. A UE 120 may be, include, or be coupled with 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, a biometric device, a wearable device (for example, a smart watch, smart clothing, smart glasses, a smart wristband, and / or smart jewelry, such as a smart ring or a smart bracelet), an entertainment device (for example, a music device, a video device, and / or a satellite radio), an XR device, a vehicular component or sensor, a smart meter or sensor, industrial manufacturing equipment, a Global Navigation Satellite System (GNSS) device (such as a Global Positioning System device or another type of positioning device), a UE function of a network node, and / or any other suitable device or function that may communicate via a wireless medium.

[0047] A UE 120 and / or a network node 110 may include one or more chips, system -on- chips (SoCs), chipsets, packages, or devices that individually or collectively constitute orcomprise a processing system. The processing system includes processor (or “processing”) circuitry in the form of one or multiple processors, microprocessors, processing units (such as central processing units (CPUs), graphics processing units (GPUs), neural processing units (NPUs) and / or digital signal processors (DSPs)), processing blocks, application-specific integrated circuits (ASIC), programmable logic devices (PUDs) (such as field programmable gate arrays (FPGAs)), or other discrete gate or transistor logic or circuitry (all of which may be generally referred to herein individually as “processors” or collectively as “the processor” or “the processor circuitry”). One or more of the processors may be individually or collectively configurable or configured to perform various functions or operations described herein. A group of processors collectively configurable or configured to perform a set of functions may include a first processor configurable or configured to perform a first function of the set and a second processor configurable or configured to perform a second function of the set, or may include the group of processors all being configured or configurable to perform the set of functions.

[0048] The processing system may further include memory circuitry in the form of one or more memory devices, memory blocks, memory elements or other discrete gate or transistor logic or circuitry, each of which may include tangible storage media such as random-access memory (RAM) or read-only memory (ROM), or combinations thereof (all of which may be generally referred to herein individually as “memories” or collectively as “the memory” or “the memory circuitry”). One or more of the memories may be coupled (for example, operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) with one or more of the processors and may individually or collectively store processor-executable code (such as software) that, when executed by one or more of the processors, may configure one or more of the processors to perform various functions or operations described herein. Additionally or alternatively, in some examples, one or more of the processors may be preconfigured to perform various functions or operations described herein without requiring configuration by software. The processing system may further include or be coupled with one or more modems (such as a Wi-Fi (for example, IEEE compliant) modem or a cellular (for example, 3GPP 4G LTE, 5G, or 6G compliant) modem). In some implementations, one or more processors of the processing system include or implement one or more of the modems. The processing system may further include or be coupled with multiple radios (collectively “the radio”), multiple RF chains, or multiple transceivers, each of which may in turn be coupled with one or more of multiple antennas. In some implementations, one or more processors of the processing system include or implement one or more of the radios, RF chains or transceivers. The UE 120 may include or may be included in a housing that houses components associated with the UE 120 including the processing system.

[0049] Some UEs 120 may be considered machine-type communication (MTC) UEs, evolved or enhanced machine-type communication (eMTC), UEs, further enhanced eMTC (feMTC) UEs, or enhanced feMTC (efeMTC) UEs, or further evolutions thereof, all of which may be simply referred to as “MTC UEs”). An MTC UE may be, may include, or may be included in or coupled with a robot, an uncrewed aerial vehicle, a remote device, a sensor, a meter, a monitor, and / or a location tag. Some UEs 120 may be considered loT devices and / or may be implemented as NB-IoT (narrowband loT) devices. An loT UE or NB-IoT device may be, may include, or may be included in or coupled with an industrial machine, an appliance, a refrigerator, a doorbell camera device, a home automation device, and / or a light fixture, among other examples. Some UEs 120 may be considered Customer Premises Equipment, which may include telecommunications devices that are installed at a customer location (such as a home or office) to enable access to a service provider's network (such as included in or in communication with the wireless communication network 100).

[0050] Some UEs 120 may be classified according to different categories in association with different complexities and / or different capabilities. UEs 120 in a first category may facilitate massive loT in the wireless communication network 100, and may offer low complexity and / or cost relative to UEs 120 in a second category. UEs 120 in a second category may include mission-critical loT devices, legacy UEs, baseline UEs, high-tier UEs, advanced UEs, fullcapability UEs, and / or premium UEs that are capable of URLLC, enhanced mobile broadband (eMBB), and / or precise positioning in the wireless communication network 100, among other examples. A third category of UEs 120 may have mid-tier complexity and / or capability (for example, a capability between UEs 120 of the first category and UEs 120 of the second capability). A UE 120 of the third category may be referred to as a reduced capacity UE (“RedCap UE”), a mid-tier UE, an NR-Light UE, and / or an NR-Lite UE, among other examples. RedCap UEs may bridge a gap between the capability and complexity of NB-IoT devices and / or eMTC UEs, and mission-critical loT devices and / or premium UEs. RedCap UEs may include, for example, wearable devices, loT devices, industrial sensors, and / or cameras that are associated with a limited bandwidth, power capacity, and / or transmission range, among other examples. RedCap UEs may support healthcare environments, building automation, electrical distribution, process automation, transport and logistics, and / or smart city deployments, among other examples.

[0051] In some examples, two or more UEs 120 (for example, shown as UE 120a and UE 120e) may communicate directly with one another using sidelink communications (for example, without communicating by way of a network node 110 as an intermediary). As an example, the UE 120a may directly transmit data, control information, or other signaling as a side link communication to the UE 120e. This is in contrast to, for example, the UE 120a first transmitting data in an UL communication to a network node 110, which then transmits the datato the UE 120e in a DL communication. In various examples, the UEs 120 may transmit and receive sidelink communications using peer-to-peer (P2P) communication protocols, device-to- device (D2D) communication protocols, vehicle-to-everything (V2X) communication protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, and / or vehicle-to-pedestrian (V2P) protocols), and / or mesh network communication protocols. In some deployments and configurations, a network node 110 may schedule and / or allocate resources for sidelink communications between UEs 120 in the wireless communication network 100. In some other deployments and configurations, a UE 120 (instead of a network node 110) may perform, or collaborate or negotiate with one or more other UEs to perform, scheduling operations, resource selection operations, and / or other operations for sidelink communications.

[0052] In various examples, some of the network nodes 110 and the UEs 120 of the wireless communication network 100 may be configured for full -duplex operation in addition to halfduplex operation. A network node 110 or a UE 120 operating in a half-duplex mode may perform only one of transmission or reception during particular time resources, such as during particular slots, symbols, or other time periods. Half-duplex operation may involve timedivision duplexing (TDD), in which DL transmissions of the network node 110 and UL transmissions of the UE 120 do not occur in the same time resources (that is, the transmissions do not overlap in time). In contrast, a network node 110 or a UE 120 operating in a full-duplex mode can transmit and receive communications concurrently (for example, in the same time resources). By operating in a full-duplex mode, network nodes 110 and / or UEs 120 may generally increase the capacity of the network and the radio access link. In some examples, full- duplex operation may involve frequency-division duplexing (FDD), in which DL transmissions of the network node 110 are performed in a first frequency band or on a first component carrier and transmissions of the UE 120 are performed in a second frequency band or on a second component carrier different than the first frequency band or the first component carrier, respectively. In some examples, full-duplex operation may be enabled for a UE 120 but not for a network node 110. For example, a UE 120 may simultaneously transmit an UL transmission to a first network node 110 and receive a DL transmission from a second network node 110 in the same time resources. In some other examples, full-duplex operation may be enabled for a network node 110 but not for a UE 120. For example, a network node 110 may simultaneously transmit a DL transmission to a first UE 120 and receive an UL transmission from a second UE 120 in the same time resources. In some other examples, full-duplex operation may be enabled for both a network node 110 and a UE 120.

[0053] In some examples, the UEs 120 and the network nodes 110 may perform MIMO communication. “MIMO” generally refers to transmitting or receiving multiple signals (such as multiple layers or multiple data streams) simultaneously over the same time and frequencyresources. MIMO techniques generally exploit multipath propagation. MIMO may be implemented using various spatial processing or spatial multiplexing operations. In some examples, MIMO may support simultaneous transmission to multiple receivers, referred to as multi-user MIMO (MU-MIMO). Some RATs may employ advanced MIMO techniques, such as mTRP operation (including redundant transmission or reception on multiple TRPs), reciprocity in the time domain or the frequency domain, single -frequency-network (SFN) transmission, or non -coherent joint transmission (NC-JT).

[0054] In some aspects, the UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive group DCI indicating MU-MIMO scheduling for a multi-user group of UEs; and communicate in accordance with the group DCI. Additionally, or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0055] In some aspects, the network node 110 may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may transmit, for a UE, group DCI indicating MU-MIMO scheduling for a multi-user group of UEs; and communicate in accordance with the group DCI. Additionally, or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0056] As indicated above, Fig. 1 is provided as an example. Other examples may differ from what is described with regard to Fig. 1.

[0057] Fig. 2 is a diagram illustrating an example network node 110 in communication with an example UE 120 in a wireless network in accordance with the present disclosure.

[0058] As shown in Fig. 2, the network node 110 may include a data source 212, a transmit processor 214, a transmit (TX) MIMO processor 216, a set of modems 232 (shown as 232a through 232t, where t > I), a set of antennas 234 (shown as 234a through 234v, where v > I), a MIMO detector 236, a receive processor 238, a data sink 239, a controller / processor 240, a memory 242, a communication unit 244, a scheduler 246, and / or a communication manager 150, among other examples. In some configurations, one or a combination of the antenna(s) 234, the modem(s) 232, the MIMO detector 236, the receive processor 238, the transmit processor 214, and / or the TX MIMO processor 216 may be included in a transceiver of the network node 110. The transceiver may be under control of and used by one or more processors, such as the controller / processor 240, and in some aspects in conjunction with processor-readable code stored in the memory 242, to perform aspects of the methods, processes, and / or operations described herein. In some aspects, the network node 110 may include one or more interfaces, communication components, and / or other components that facilitate communication with the UE 120 or another network node.

[0059] The terms “processor,” “controller,” or “controller / processor” may refer to one or more controllers and / or one or more processors. For example, reference to “a / the processor,” “a / the controller / processor,” or the like (in the singular) should be understood to refer to any one or more of the processors described in connection with Fig. 2, such as a single processor or a combination of multiple different processors. Reference to “one or more processors” should be understood to refer to any one or more of the processors described in connection with Fig. 2. For example, one or more processors of the network node 110 may include transmit processor 214, TX MIMO processor 216, MIMO detector 236, receive processor 238, and / or controller / processor 240. Similarly, one or more processors of the UE 120 may include MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, and / or controller / processor 280.

[0060] In some aspects, a single processor may perform all of the operations described as being performed by the one or more processors. In some aspects, a first set of (one or more) processors of the one or more processors may perform a first operation described as being performed by the one or more processors, and a second set of (one or more) processors of the one or more processors may perform a second operation described as being performed by the one or more processors. The first set of processors and the second set of processors may be the same set of processors or may be different sets of processors. Reference to “one or more memories” should be understood to refer to any one or more memories of a corresponding device, such as the memory described in connection with Fig. 2. For example, operation described as being performed by one or more memories can be performed by the same subset of the one or more memories or different subsets of the one or more memories.

[0061] For downlink communication from the network node 110 to the UE 120, the transmit processor 214 may receive data (“downlink data”) intended for the UE 120 (or a set of UEs that includes the UE 120) from the data source 212 (such as a data pipeline or a data queue). In some examples, the transmit processor 214 may select one or more modulation and coding schemes (MCSs) for the UE 120 in accordance with one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 may process the data (for example, including encoding the data) for transmission to the UE 120 on a downlink in accordance with the MCS(s) selected for the UE 120 to generate data symbols. The transmit processor 214 may process system information (for example, semi-static resource partitioning information (SRPI)) and / or control information (for example, CQI requests, grants, and / or upper layer signaling) and provide overhead symbols and / or control symbols. The transmit processor 214 may generate reference symbols for reference signals (for example, a cell-specific reference signal (CRS), a demodulation reference signal (DMRS), or a channel state information (CSI) reference signal (CSI-RS)) and / or synchronization signals (for example, a primary synchronization signal (PSS) or a secondary synchronization signals (SSS)).

[0062] The TX MIMO processor 216 may perform spatial processing (for example, precoding) on the data symbols, the control symbols, the overhead symbols, and / or the reference symbols, if applicable, and may provide a set of output symbol streams (for example, T output symbol streams) to the set of modems 232. For example, each output symbol stream may be provided to a respective modulator component (shown as MOD) of a modem 232. Each modem 232 may use the respective modulator component to process (for example, to modulate) a respective output symbol stream (for example, for orthogonal frequency division multiplexing (OFDM)) to obtain an output sample stream. Each modem 232 may further use the respective modulator component to process (for example, convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain a time domain downlink signal. The modems 232a through 232t may together transmit a set of downlink signals (for example, T downlink signals) via the corresponding set of antennas 234.

[0063] A downlink signal may include a DCI communication, a MAC control element (MAC-CE) communication, an RRC communication, a downlink reference signal, or another type of downlink communication. Downlink signals may be transmitted on a PDCCH, a PDSCH, and / or on another downlink channel. A downlink signal may carry one or more transport blocks (TBs) of data. A TB may be a unit of data that is transmitted over an air interface in the wireless communication network 100. A data stream (for example, from the data source 212) may be encoded into multiple TBs for transmission over the air interface. The quantity of TBs used to carry the data associated with a particular data stream may be associated with a TB size common to the multiple TBs. The TB size may be based on or otherwise associated with radio channel conditions of the air interface, the MCS used for encoding the data, the downlink resources allocated for transmitting the data, and / or another parameter. In general, the larger the TB size, the greater the amount of data that can be transmitted in a single transmission, which reduces signaling overhead. However, larger TB sizes may be more prone to transmission and / or reception errors than smaller TB sizes, but such errors may be mitigated by more robust error correction techniques.

[0064] For uplink communication from the UE 120 to the network node 110, uplink signals from the UE 120 may be received by an antenna 234, may be processed by a modem 232 (for example, a demodulator component, shown as DEMOD, of a modem 232), may be detected by the MIMO detector 236 (for example, a receive (Rx) MIMO processor) if applicable, and / or may be further processed by the receive processor 238 to obtain decoded data and / or control information. The receive processor 238 may provide the decoded data to a data sink 239 (which may be a data pipeline, a data queue, and / or another type of data sink) and provide the decoded control information to a processor, such as the controller / processor 240.

[0065] The network node 110 may use the scheduler 246 to schedule one or more UEs 120 for downlink or uplink communications. In some aspects, the scheduler 246 may use DCI todynamically schedule DL transmissions to the UE 120 and / or UL transmissions from the UE 120. In some examples, the scheduler 246 may allocate recurring time domain resources and / or frequency domain resources that the UE 120 may use to transmit and / or receive communications using an RRC configuration (for example, a semi-static configuration), for example, to perform semi-persistent scheduling (SPS) or to configure a configured grant (CG) for the UE 120.

[0066] One or more of the transmit processor 214, the TX MIMO processor 216, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, and / or the controller / processor 240 may be included in an RF chain of the network node 110. An RF chain may include one or more filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs), and / or other devices that convert between an analog signal (such as for transmission or reception via an air interface) and a digital signal (such as for processing by one or more processors of the network node 110). In some aspects, the RF chain may be or may be included in a transceiver of the network node 110.

[0067] In some examples, the network node 110 may use the communication unit 244 to communicate with a core network and / or with other network nodes. The communication unit 244 may support wired and / or wireless communication protocols and / or connections, such as Ethernet, optical fiber, common public radio interface (CPRI), and / or a wired or wireless backhaul, among other examples. The network node 110 may use the communication unit 244 to transmit and / or receive data associated with the UE 120 or to perform network control signaling, among other examples. The communication unit 244 may include a transceiver and / or an interface, such as a network interface.

[0068] The UE 120 may include a set of antennas 252 (shown as antennas 252a through 252r, where r > 1), a set of modems 254 (shown as modems 254a through 254u, where u > I), a MIMO detector 256, a receive processor 258, a data sink 260, a data source 262, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, a memory 282, and / or a communication manager 140, among other examples. One or more of the components of the UE 120 may be included in a housing 284. In some aspects, one or a combination of the antenna(s) 252, the modem(s) 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, or the TX MIMO processor 266 may be included in a transceiver that is included in the UE 120. The transceiver may be under control of and used by one or more processors, such as the controller / processor 280, and in some aspects in conjunction with processor-readable code stored in the memory 282, to perform aspects of the methods, processes, or operations described herein. In some aspects, the UE 120 may include another interface, another communication component, and / or another component that facilitates communication with the network node 110 and / or another UE 120.

[0069] For downlink communication from the network node 110 to the UE 120, the set of antennas 252 may receive the downlink communications or signals from the network node 110 and may provide a set of received downlink signals (for example, R received signals) to the set of modems 254. For example, each received signal may be provided to a respective demodulator component (shown as DEMOD) of a modem 254. Each modem 254 may use the respective demodulator component to condition (for example, fdter, amplify, downconvert, and / or digitize) a received signal to obtain input samples. Each modem 254 may use the respective demodulator component to further demodulate or process the input samples (for example, for OFDM) to obtain received symbols. The MIMO detector 256 may obtain received symbols from the set of modems 254, may perform MIMO detection on the received symbols if applicable, and may provide detected symbols. The receive processor 258 may process (for example, decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260 (which may include a data pipeline, a data queue, and / or an application executed on the UE 120), and may provide decoded control information and system information to the controller / processor 280.

[0070] For uplink communication from the UE 120 to the network node 110, the transmit processor 264 may receive and process data (“uplink data”) from a data source 262 (such as a data pipeline, a data queue, and / or an application executed on the UE 120) and control information from the controller / processor 280. The control information may include one or more parameters, feedback, one or more signal measurements, and / or other types of control information. In some aspects, the receive processor 258 and / or the controller / processor 280 may determine, for a received signal (such as received from the network node 110 or another UE), one or more parameters relating to transmission of the uplink communication. The one or more parameters may include a reference signal received power (RSRP) parameter, a received signal strength indicator (RS SI) parameter, a reference signal received quality (RSRQ) parameter, a CQI parameter, or a transmit power control (TPC) parameter, among other examples. The control information may include an indication of the RSRP parameter, the RSSI parameter, the RSRQ parameter, the CQI parameter, the TPC parameter, and / or another parameter. The control information may facilitate parameter selection and / or scheduling for the UE 120 by the network node 110.

[0071] The transmit processor 264 may generate reference symbols for one or more reference signals, such as an uplink DMRS, an uplink sounding reference signal (SRS), and / or another type of reference signal. The symbols from the transmit processor 264 may be precoded by the TX MIMO processor 266, if applicable, and further processed by the set of modems 254 (for example, for DFT-s-OFDM or CP-OFDM). The TX MIMO processor 266 may perform spatial processing (for example, precoding) on the data symbols, the control symbols, the overhead symbols, and / or the reference symbols, if applicable, and may provide a set of output symbolstreams (for example, U output symbol streams) to the set of modems 254. For example, each output symbol stream may be provided to a respective modulator component (shown as MOD) of a modem 254. Each modem 254 may use the respective modulator component to process (for example, to modulate) a respective output symbol stream (for example, for OFDM) to obtain an output sample stream. Each modem 254 may further use the respective modulator component to process (for example, convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain an uplink signal.

[0072] The modems 254a through 254u may transmit a set of uplink signals (for example, R uplink signals or U uplink symbols) via the corresponding set of antennas 252. An uplink signal may include a UCI communication, a MAC-CE communication, an RRC communication, or another type of uplink communication. Uplink signals may be transmitted on a PUSCH, a PUCCH, and / or another type of uplink channel. An uplink signal may carry one or more TBs of data. Sidelink data and control transmissions (that is, transmissions directly between two or more UEs 120) may generally use similar techniques as were described for uplink data and control transmission, and may use sidelink-specific channels such as a physical sidelink shared channel (PSSCH), a physical sidelink control channel (PSCCH), and / or a physical sidelink feedback channel (PSFCH).

[0073] One or more antennas of the set of antennas 252 or the set of antennas 234 may include, or may be included within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, among other examples. An antenna panel, an antenna group, a set of antenna elements, or an antenna array may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or one or more antenna elements coupled with one or more transmission or reception components, such as one or more components of Fig. 2. As used herein, “antenna” can refer to one or more antennas, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays. “Antenna panel” can refer to a group of antennas (such as antenna elements) arranged in an array or panel, which may facilitate beamforming by manipulating parameters of the group of antennas. “Antenna module” may refer to circuitry including one or more antennas, which may also include one or more other components (such as fdters, amplifiers, or processors) associated with integrating the antenna module into a wireless communication device.

[0074] In some examples, each of the antenna elements of an antenna 234 or an antenna 252 may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element cross-polarized with a second sub-element that can be used to independently transmit cross-polarized signals. The antenna elements may include patch antennas, dipole antennas, and / or other types of antennasarranged in a linear patern, a two-dimensional patern, or another patern. A spacing between antenna elements may be such that signals with a desired wavelength transmited separately by the antenna elements may interact or interfere constructively and destructively along various directions (such as to form a desired beam). For example, given an expected range of wavelengths or frequencies, the spacing may provide a quarter wavelength, a half wavelength, or another fraction of a wavelength of spacing between neighboring antenna elements to allow for the desired constructive and destructive interference paterns of signals transmited by the separate antenna elements within that expected range.

[0075] The amplitudes and / or phases of signals transmited via antenna elements and / or subelements may be modulated and shifted relative to each other (such as by manipulating phase shift, phase offset, and / or amplitude) to generate one or more beams, which is referred to as beamforming. The term “beam” may refer to a directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction. “Beam” may also generally refer to a direction associated with such a directional signal transmission, a set of directional resources associated with the signal transmission (for example, an angle of arrival, a horizontal direction, and / or a vertical direction), and / or a set of parameters that indicate one or more aspects of a directional signal, a direction associated with the signal, and / or a set of directional resources associated with the signal. In some implementations, antenna elements may be individually selected or deselected for directional transmission of a signal (or signals) by controlling amplitudes of one or more corresponding amplifiers and / or phases of the signal(s) to form one or more beams. The shape of a beam (such as the amplitude, width, and / or presence of side lobes) and / or the direction of a beam (such as an angle of the beam relative to a surface of an antenna array) can be dynamically controlled by modifying the phase shifts, phase offsets, and / or amplitudes of the multiple signals relative to each other.

[0076] Different UEs 120 or network nodes 110 may include different numbers of antenna elements. For example, a UE 120 may include a single antenna element, two antenna elements, four antenna elements, eight antenna elements, or a different number of antenna elements. As another example, a network node 110 may include eight antenna elements, 24 antenna elements, 64 antenna elements, 128 antenna elements, or a different number of antenna elements. Generally, a larger number of antenna elements may provide increased control over parameters for beam generation relative to a smaller number of antenna elements, whereas a smaller number of antenna elements may be less complex to implement and may use less power than a larger number of antenna elements. Multiple antenna elements may support multiple-layer transmission, in which a first layer of a communication (which may include a first data stream) and a second layer of a communication (which may include a second data stream) are transmited using the same time and frequency resources with spatial multiplexing.

[0077] While blocks in Fig. 2 are illustrated as distinct components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combination component or in various combinations of components. For example, the functions described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0078] Fig. 3 is a diagram illustrating an example disaggregated base station architecture 300 in accordance with the present disclosure. One or more components of the example disaggregated base station architecture 300 may be, may include, or may be included in one or more network nodes (such one or more network nodes 110). The disaggregated base station architecture 300 may include a CU 310 that can communicate directly with a core network 320 via a backhaul link, or that can communicate indirectly with the core network 320 via one or more disaggregated control units, such as a Non-RT RIC 350 associated with a Service Management and Orchestration (SMO) Framework 360 and / or a Near-RT RIC 370 (for example, via an E2 link). The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via Fl interfaces. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective RF access links. In some deployments, a UE 120 may be simultaneously served by multiple RUs 340.

[0079] Each of the components of the disaggregated base station architecture 300, including the CUs 310, the DUs 330, the RUs 340, the Near-RT RICs 370, the Non-RT RICs 350, and the SMO Framework 360, may include one or more interfaces or may be coupled with one or more interfaces for receiving or transmitting signals, such as data or information, via a wired or wireless transmission medium.

[0080] In some aspects, the CU 310 may be logically split into one or more CU user plane (CU-UP) units and one or more CU control plane (CU-CP) units. A CU-UP unit may communicate bidirectionally with a CU-CP unit via an interface, such as the El interface when implemented in an O-RAN configuration. The CU 310 may be deployed to communicate with one or more DUs 330, as necessary, for network control and signaling. Each DU 330 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 340. For example, a DU 330 may host various layers, such as an RLC layer, a MAC layer, or one or more PHY layers, such as one or more high PHY layers or one or more low PHY layers. Each layer (which also may be referred to as a module) may be implemented with an interface for communicating signals with other layers (and modules) hosted by the DU 330, or for communicating signals with the control functions hosted by the CU 310. Each RU 340 may implement lower layer functionality. In some aspects, real-time and non-real-time aspects of control and user plane communication with the RU(s) 340 may be controlled by the corresponding DU 330.

[0081] The SMO Framework 360 may support RAN deployment and provisioning of nonvirtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 360 may support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operations and maintenance interface, such as an 01 interface. For virtualized network elements, the SMO Framework 360 may interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface, such as an 02 interface. A virtualized network element may include, but is not limited to, a CU 310, a DU 330, an RU 340, a non-RT RIC 350, and / or a Near-RT RIC 370. In some aspects, the SMO Framework 360 may communicate with a hardware aspect of a 4G RAN, a 5G NR RAN, and / or a 6G RAN, such as an open eNB (O- eNB) 380, via an 01 interface. Additionally or alternatively, the SMO Framework 360 may communicate directly with each of one or more RUs 340 via a respective 01 interface. In some deployments, this configuration can enable each DU 330 and the CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0082] The Non-RT RIC 350 may include or may implement a logical function that enables non-real-time control and optimization of RAN elements and resources, AI / MU workflows including model training and updates, and / or policy-based guidance of applications and / or features in the Near-RT RIC 370. The Non-RT RIC 350 may be coupled to or may communicate with (such as via an Al interface) the Near-RT RIC 370. The Near-RT RIC 370 may include or may implement a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions via an interface (such as via an E2 interface) connecting one or more CUs 310, one or more DUs 330, and / or an O-eNB with the Near-RT RIC 370.

[0083] In some aspects, to generate AI / MU models to be deployed in the Near-RT RIC 370, the Non-RT RIC 350 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 370 and may be received at the SMO Framework 360 or the Non-RT RIC 350 from non-network data sources or from network functions. In some examples, the Non-RT RIC 350 or the Near-RT RIC 370 may tune RAN behavior or performance. For example, the Non-RT RIC 350 may monitor long-term trends and patterns for performance and may employ AI / MU models to perform corrective actions via the SMO Framework 360 (such as reconfiguration via an 01 interface) or via creation of RAN management policies (such as Al interface policies).

[0084] As indicated above, Fig. 3 is provided as an example. Other examples may differ from what is described with regard to Fig. 3.

[0085] The network node 110, the controller / processor 240 of the network node 110, the UE 120, the controller / processor 280 of the UE 120, the CU 310, the DU 330, the RU 340, or any other component(s) of Figs. 1, 2, or 3 may implement one or more techniques or perform one or more operations associated with group DCI for MU-MIMO communication, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, any other component(s) of Fig. 2, the CU 310, the DU 330, or the RU 340 may perform or direct operations of, for example, process 500 of Fig. 5, process 600 of Fig. 6, or other processes as described herein (alone or in conjunction with one or more other processors). The memory 242 may store data and program codes for the network node 110, the network node 110, the CU 310, the DU 330, or the RU 340. The memory 282 may store data and program codes for the UE 120. In some examples, the memory 242 or the memory 282 may include a non-transitory computer-readable medium storing a set of instructions (for example, code or program code) for wireless communication. The memory 242 may include one or more memories, such as a single memory or multiple different memories (of the same type or of different types). The memory 282 may include one or more memories, such as a single memory or multiple different memories (of the same type or of different types). For example, the set of instructions, when executed (for example, directly, or after compiling, converting, or interpreting) by one or more processors of the network node 110, the UE 120, the CU 310, the DU 330, or the RU 340, may cause the one or more processors to perform process 500 of Fig. 5, process 600 of Fig. 6, or other processes as described herein. In some examples, executing instructions may include running the instructions, converting the instructions, compiling the instructions, and / or interpreting the instructions, among other examples.

[0086] In some aspects, the UE 120 includes means for receiving group DCI indicating MU- MIMO scheduling for a multi-user group of UEs; and / or means for communicating in accordance with the group DCI. The means for the UE 120 to perform operations described herein may include, for example, one or more of communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0087] In some aspects, the network node 110 includes means for transmitting, for a UE, group DCI indicating MU-MIMO scheduling for a multi-user group of UEs; and / or means for communicating in accordance with the group DCI. The means for the network node 110 to perform operations described herein may include, for example, one or more of communication manager 150, transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler

[0088] As indicated above, Fig. 3 is provided as an example. Other examples may differ from what is described with regard to Fig. 3.

[0089] To schedule UEs in a multi-user group for MU-MIMO, a network node may transmit multiple DCI communications to respective UEs in the multi-user group, and each UE in the multi-user group may blindly decode a respective PDCCH. For example, each DCI may have a CRC scrambled by a respective C-RNTI for each UE in the multi-user group. The transmission of separate DCI for each UE in the multi-user group creates significant control signaling overhead. Moreover, the transmission of separate DCI for each UE in the multi-user group may produce PDCCH blocking or other congestion in PDCCH resources, thereby degrading PDCCH performance. In addition, MU-MIMO scheduling, which may be implemented at the network node, may be transparent to UEs in the multi -group (e.g., a UE may be unaware that its respective DCI is associated with scheduling for MU-MIMO communication), and as a result the UEs may not take corrective measures for interference.

[0090] Various aspects relate generally to group DCI for a multi-user group of UEs. Some aspects more specifically relate to group DCI that indicates MU-MIMO scheduling for the multi-user group of UEs, and communication between a network node and the UEs in accordance with MU-MIMO scheduling. In some aspects, the group DCI may include common information for the multi-user group of UEs, and respective UE-specific information (e.g., information intended for a single UE) for each UE in the multi-user group of UEs. For example, the common information may indicate a time and frequency resource that is to be shared by the multi-user group of UEs. In some aspects, in accordance with the MU-MIMO scheduling (e.g., using the shared resource), each UE of the multi-user group may communicate respective data with the network node (e.g., rather than the same data being communicated between the network node and the UEs of the multi-user group). In some aspects, the group DCI may include an indication of which UEs of the multi-user group are scheduled by the group DCI and which UEs of the multi-user group are not scheduled by the group DCI.

[0091] 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, by scheduling MU-MIMO communication for a multi-user group of UEs using group DCI, the described techniques can be used to reduce control signaling overhead and reduce a probability of PDCCH blocking, thereby improving PDCCH performance. In addition, the group DCI provides implicit network assistance information, because UEs that are aware that the scheduling is for MU-MIMO can act to cancel or mitigate multi-user interference in downlink MU-MIMO, thereby improving a performance of downlink communications. Moreover, by including group common information and UE-specific information in the group DCI, the described techniques can be used to provide scheduling flexibility for individual UEs while minimizing an overall payload size of the group DCI to facilitate efficient utilization of networkresources. In some examples, by including an indication of which UEs of the multi-user group are, and are not, scheduled by the group DCI, the group DCI may facilitate conservation of radio resources. For example, physical uplink control channel (PUCCH) resources that are allocated to UEs in the multi-user group may be allocated to only the UEs that are scheduled by the group DCI, thereby reducing the number of PUCCH resources that need to be allocated.

[0092] Fig. 4 is a diagram of an example 400 associated with group DCI for MU-MIMO communication, in accordance with the present disclosure. As shown in Fig. 4, a network node (e.g., network node 110, a CU, a DU, and / or an RU) may communicate with a plurality of UEs (e.g., UEs 120). In some aspects, the network node and the UEs may be part of a wireless network (e.g., wireless network 100). The UEs and the network node may have established wireless connections prior to operations shown in Fig. 4. In the description to follow, operations are described with reference to a single UE of the plurality of UEs. However, each of the UEs, of the plurality of UEs, may perform the operations that are described.

[0093] As shown by reference number 405, the network node may transmit, and the UE may receive, configuration information. In some aspects, the UE may receive the configuration information via one or more of system information (e.g., a master information block (MIB) and / or a system information block (SIB), among other examples), RRC signaling, one or more MAC-CEs, and / or DCI, among other examples.

[0094] In some aspects, the configuration information may indicate one or more candidate configurations and / or communication parameters. In some aspects, the one or more candidate configurations and / or communication parameters may be selected, activated, and / or deactivated by a subsequent indication. For example, the subsequent indication may select a candidate configuration and / or communication parameter from the one or more candidate configurations and / or communication parameters. In some aspects, the subsequent indication (e.g., an indication described herein) may include a dynamic indication, such as one or more MAC-CEs and / or one or more DCI messages, among other examples.

[0095] In some aspects, the configuration information may indicate that the UE is to communicate using MU-MIMO and / or may indicate one or more configurations relating to MU- MIMO. In some aspects, the configuration information may configure one or more multi-user groups for the UE. For example, a configuration of a multi-user group may indicate a group radio network temporary identifier (RNTI) used for the multi-user group (e.g., a group-MU- RNTI (G-MU-RNTI)), a quantity of UEs in the multi-user group, and / or a UE index for the UE in the multi-user group (e.g., the UE may have a UE index associated with each G-MU-RNTI configured for the UE). For example, the UE may be configured with one or more G-MU- RNTIs, each associated with a different multi-user group. In some aspects, the configuration information may configure one or more PUCCH resources for the UE. For example, a configuration for a PUCCH resource may indicate time and / or frequency resources of thePUCCH resource, or a format of the PUCCH resource (e.g., a format that supports UE multiplexing or a format that does not support UE multiplexing). The UE may configure itself based at least in part on the configuration information. In some aspects, the UE may be configured to perform one or more operations described herein based at least in part on the configuration information.

[0096] As shown by reference number 410, the UE may transmit, and the network node may receive, a capabilities report (e.g., UE capability information). The capabilities report may indicate whether the UE supports a feature and / or one or more parameters related to the feature. For example, the capability information may indicate a capability and / or parameter for MU- MIMO communication. In particular, the capabilities report may indicate a capability and / or parameter relating to a maximum quantity of multi-user groups (e.g., a maximum quantity of G- MU-RNTIs) supported by the UE (e.g., a maximum number of G-MU-RNTIs supported by the UE may be reported as a UE capability). The maximum quantity of multi-user groups may be greater than a minimum quantity of multi-user groups (e.g., a minimum quantity of G-MU- RNTIs) that are defined in a standard or configured for the UE. One or more operations described herein may be based on capability information of the capabilities report. For example, the UE may perform a communication in accordance with the capability information, or may receive configuration information that is in accordance with the capability information. In some aspects, the capabilities report may indicate UE support for MU-MIMO.

[0097] In some aspects, the configuration information described in connection with reference number 405 and / or the capabilities report may include information transmitted via multiple communications. Additionally, or alternatively, the network node may transmit the configuration information, or a communication including at least a portion of the configuration information, before and / or after the UE transmits the capabilities report. For example, the network node may transmit a first portion of the configuration information before the capabilities report, the UE may transmit at least a portion of the capabilities report, and the network node may transmit a second portion of the configuration information after receiving the capabilities report.

[0098] As shown by reference number 415, the network node may transmit, and the UE may receive, multi-user group information for a multi-user group of UEs (e.g., which may be a part of the configuration information described in connection with reference number 405). For example, the multi-user group information may indicate a group RNTI (e.g., a G-MU-RNTI) for the multi-user group, a UE index for the UE within the multi-user group, or the like. The multiuser group information may be communicated via DCI and / or a MAC-CE. The multi-user group of UEs may include the plurality of UEs, which may include the UE and one or more additional UEs.

[0099] As shown by reference number 420, the network node may transmit, and the UE may receive, an indication of an activation of the multi-user group (e.g., by indicating the G-MU- RNTI of the multi-user group). For example, if the UE is configured with multiple multi-user groups, the activation may be of one of the multiple multi-user groups. In response to the activation of the multi-user group, the UE may begin monitoring DCI associated with the group RNTI (e.g., DCI having a CRC scrambled by the group RNTI) for the multi-user group. In a similar manner, the network node may transmit, and the UE may receive, an indication of a deactivation of the multi-user group (e.g., by indicating the G-MU-RNTI of the multi-user group). In response to the deactivation of the multi-user group, the UE may stop monitoring DCI associated with the group RNTI for the multi-user group. The indication of the activation and / or the indication of the deactivation may be communicated via DCI and / or a MAC-CE.

[0100] As shown by reference number 425, the network node may transmit, and the UE (e.g., the plurality of UEs) may receive, group DCI indicating MU-MIMO scheduling for a multi-user group of UEs (e.g., one of the multi-user groups configured and activated for the UE). In some aspects, the group DCI may provide downlink MU-MIMO scheduling or uplink MU-MIMO scheduling. For example, the MU-MIMO scheduling may schedule data transmissions to or from multiple UEs of the multi-user group of UEs, and the data transmissions may have respective data for each of the UEs (e.g., each of the UEs scheduled by the group DCI may transmit or receive different data in the scheduled resources).

[0101] The group DCI may provide non-transparent MU-MIMO scheduling (e.g., because the group DCI is used, each UE in the multi -group is aware that the scheduling is for MU- MIMO). In this way, the group DCI (e.g., the MU-MIMO scheduling) provides implicit network assistance information because UEs, that are aware that the scheduling is for MU- MIMO, can act to cancel or mitigate multi-user interference for downlink MU-MIMO. In some aspects, the MU-MIMO scheduling in the group DCI may indicate the same resource allocation (e.g., time and frequency resources) for the multi-user group of UEs (e.g., via a group-common field in the group DCI, as described herein). The group DCI may have a single CRC that is scrambled by the group RNTI used for the multi-user group of UEs (e.g., a C-RNTI should not be used because the group DCI includes MU-MIMO scheduling targeted for the multi-user group of UEs), thereby simplifying network node operations, relative to using multiple CRCs attached to multiple DCI for multiple UEs.

[0102] The group DCI may include common information for the multi-user group of UEs (e.g., multi-user group common information), and UE-specific information for each UE in the multi-user group of UEs. For example, the group DCI may include respective UE-specific information for each UE in the multi-user group of UEs. As an example, the UE-specific information for the UE may be at a position in the group DCI associated with the configured UE index for the UE.

[0103] In some aspects, the group DCI may schedule MU-MIMO data transmissions for fewer UEs than a size of the multi-user group of UEs. For example, the network may configure a multi-user group size of ' UEs. and the group DCI may schedule MU-MIMO data transmission for M UEs, where M< N. In some aspects, the common information in the group DCI may include a bitmap that indicates, for each of the plurality of UEs, whether the MU- MIMO scheduling is for that UE. For example, each bit in the bitmap may map to a respective UE and may indicate whether that UE is scheduled by the MU-MIMO scheduling in the group DCI (e.g., the bitmap may have a size A, such that the bitmap can indicate, for each UE in the multi-user group, whether that UE is scheduled by the group DCI). In some aspects, for one or more UEs, the UE-specific information in the group DCI may include a defined payload to indicate that the MU-MIMO scheduling is not for the one or more UEs. For example, there may be a special payload definition (e.g., an all “1” payload, or an all “0” payload) that, when used in the UE-specific information for a UE index, indicates that there is no data transmission scheduled for that UE index.

[0104] By indicating which UEs are scheduled by the group DCI and which UEs are not scheduled by the group DCI, the group DCI may improve an efficiency of network resource use. For example, indicating non-scheduled UEs may enable improved PUCCH resource allocation. As an example, a configured PUCCH format may allow multiplexing of a maximum of four UEs, M= 4, and N= 8 (e.g., UEs 1, 3, 5, and 7 are scheduled by the group DCI, and UEs 2, 4, 6, and 8 are not scheduled by the group DCI). Continuing with the example, if there is no indication of non-scheduled UEs in the group DCI, then UEs 1, 2, 3, and 4 may be scheduled for a first PUCCH resource, which may be used only by UEs 1 and 3, and UEs 5, 6, 7, and 8 may be scheduled for a second PUCCH resource, which may be used only by UEs 5 and 7. However, if there is an indication of non-scheduled UEs in the group DCI, then UEs 1, 3, 5, and 7 may be scheduled for the first PUCCH resource, and there will be no second PUCCH resource allocation.

[0105] In some aspects, the group DCI may schedule only an initial transmission. For example, the group DCI may schedule one or more initial transmissions for the multi-user group of UEs, and one or more retransmissions for the multi-user group of UEs may be scheduled by UE-specific DCI (e.g., a retransmission for each UE may be scheduled by legacy DCI). In cases in which the group DCI may schedule only initial transmissions, the common information for MU-MIMO scheduling in the group DCI may indicate a time domain and / or frequency domain resource assignment, a virtual resource block (VRB)-to-physical resource block (PRB) mapping, a hybrid automatic repeat request (HARQ) process number, a downlink assignment index, a PDSCH-to-HARQ feedback timing indicator, and / or a PUCCH resource indicator if a configured PUCCH format supports UE multiplexing (e.g., if there are 8 UEs in the multi-user group, but the PUCCH format allows only 4 UEs to be multiplexed, then the first four UEsbased on UE indices of the multi-user group can be multiplexed in a first PUCCH resource, and the last four UEs based on UE indices of the multi-user group can be multiplexed in a second PUCCH resource that may have a time and / or frequency offset from the first PUCCH resource), among other examples. Moreover, in cases in which the group DCI may schedule only initial transmissions, the UE-specific information for MU-MIMO scheduling in the group DCI may indicate, for the UE, the UE’s UE index in the multi-user group, an MCS, a TPC command for a scheduled PUCCH, and / or a PUCCH resource indicator if the configured PUCCH format does not support UE multiplexing, among other examples.

[0106] In some aspects, the group DCI may schedule both an initial transmission and a retransmission. In one example, the group DCI may schedule one or more initial transmissions for the multi-user group of UEs, and one or more retransmissions for the multi-user group of UEs may be scheduled by additional group DCI (e.g., the group DCI is enabled to schedule both initial transmissions and retransmissions). In another example, the group DCI may schedule one or more initial transmissions for one or more first UEs of the multi-user group of UEs, and one or more retransmissions for one or more second UEs of the multi-user group of UEs (e.g., initial transmissions for some UEs and retransmissions for other UEs can be scheduled in the same group DCI).

[0107] In cases in which the group DCI may schedule both initial transmissions and retransmissions, the common information for MU-MIMO scheduling in the group DCI may indicate a time domain and / or frequency domain resource assignment, a VRB-to-PRB mapping, a new data indicator and a redundancy version indication (e.g., where only one of an initial transmission or a retransmission can be scheduled in the same group DCI), an HARQ process number (e.g., only TBs with the same HARQ process number, that are negatively acknowledged, can be scheduled in a multi-user transmission), a downlink assignment index, a PDSCH-to-HARQ feedback timing indicator, and / or a PUCCH resource indicator if a configured PUCCH format supports UE multiplexing, among other examples. Moreover, in cases in which the group DCI may schedule both initial transmissions and retransmissions, the UE-specific information for MU-MIMO scheduling in the group DCI may indicate, for the UE, the UE’s UE index in the multi-user group, an MCS, a TPC command for a scheduled PUCCH, a new data indicator and a redundancy version indication (e.g., where both of an initial transmission and a retransmission can be scheduled in the same group DCI), an HARQ process number (e.g., TBs with different HARQ process numbers, that are negatively acknowledged, can be scheduled in a multi-user transmission), and / or a PUCCH resource indicator if the configured PUCCH format does not support UE multiplexing, among other examples. Some information may be indicated either in the common information or in UE-specific information. Including information in the UE-specific information provides more scheduling flexibility, but increases the overall payload size of the group DCI.

[0108] In some aspects, the group DCI may schedule one or more retransmissions for the multi-user group of UEs responsive to a threshold quantity of UEs, of the multi-user group of UEs, reporting negative acknowledgment feedback for MU-MIMO initial transmissions. For example, for an initial transmission for MU-MIMO, if the quantity of UEs that report negative acknowledgment (NACK) feedback is greater than a threshold, then the network may use group DCI for scheduling retransmissions. Otherwise, if the quantity of UEs is not greater than the threshold, then the network may use a legacy DCI for scheduling retransmissions. In some aspects, the group DCI may schedule one or more first retransmissions (e.g., first time retransmissions) for the multi-user group of UEs, and one or more second retransmissions (e.g., second time retransmissions) for the multi-user group of UEs may be scheduled by UE-specific DCI (e.g., legacy DCI). For example, for a first time retransmission, group DCI for MU-MIMO retransmission scheduling may be used, and for a second time or greater retransmission, legacy DCI for retransmission scheduling may be used (e.g., because a residual block error rate (BLER) after an initial transmission may be 10%, whereas a residual BLER after a first retransmission may be 1%, a residual BLER after a second retransmission may be 0.1%, and so forth).

[0109] In some aspects, a search space type used for the group DCI is a common search space (CSS), such as a Type 3 CSS (sometimes referred to as a Type 3 PDCCH). In some aspects, a search space type used for the group DCI is a user-specific search space. As described in 3GPP Technical Specification 38.213, for a search space set 5 associated with a control resource set (CORESET) p, the control channel element (CCE) indexes for an aggregation level L corresponding to a PDCCH candidate ms nciof the search space set in a slot for an active downlink bandwidth part of a serving cell corresponding to a carrier indicator field value nCIare given by the following equation:For a common search space, the parameter Yp n= 0. In some aspects, for a user-specific s,f search space, the parameter Yp n(e.g., for a hashing function) may be initialized using the s,f group RNTI (e.g., G-MU-RNTI) associated with the multi-user group rather than using a C- RNTI, which may be different for different UEs.

[0110] As shown by reference number 430, the network node and the UE may communicate in accordance with the group DCI (e.g., using the time and frequency resource and using other communication parameters indicated in the group DCI). In some aspects, to communicate in accordance with the group DCI, the network node may transmit, and the UE may receive, a downlink data transmission in accordance with the group DCI. In some aspects, to communicate in accordance with the group DCI, the UE may transmit, and the network nodemay receive, an uplink data transmission in accordance with the group DCI. In some aspects, the downlink data transmission or the uplink data transmission (e.g., the data scheduled by the group DCI) may be scrambled using the C-RNTI for the UE, rather than the group RNTI for the multi-user group of UEs, for security (e.g., the C-RNTI is different for each UE in the multiuser group of UEs). The downlink data transmission or the uplink data transmission may be an initial transmission or a retransmission, as described herein. In some aspects, the downlink data transmission or the uplink data transmission is an MU-MIMO transmission. For example, the network node may transmit respective downlink data transmissions (e.g., each having different data) to the plurality of UEs (or multiple UEs of the plurality of UEs) in accordance with the group DCI. As another example, the plurality of UEs (or multiple UEs of the plurality of UEs) may transmit respective uplink data transmissions (e.g., each having different data) to the network node in accordance with the group DCI.

[0111] By scheduling MU-MIMO communication for the multi-user group of UEs using the group DCI, the techniques described herein can be used to reduce control signaling overhead and reduce a probability of PDCCH blocking, thereby improving PDCCH performance.

[0112] As indicated above, Fig. 4 is provided as an example. Other examples may differ from what is described with respect to Fig. 4.

[0113] Fig. 5 is a diagram illustrating an example process 500 performed, for example, at a UE or an apparatus of a UE, in accordance with the present disclosure. Example process 500 is an example where the apparatus or the UE (e.g., UE 120) performs operations associated with group DCI for MU-MIMO communication.

[0114] As shown in Fig. 5, in some aspects, process 500 may include receiving group DCI indicating MU-MIMO scheduling for a multi-user group of UEs (block 510). For example, the UE (e.g., using reception component 702 and / or communication manager 706, depicted in Fig. 7) may receive group DCI indicating MU-MIMO scheduling for a multi-user group of UEs, as described above in connection with Fig. 4. As an example, the group DCI may include common information for the multi-user group of UEs, and UE-specific information for each UE in the multi-user group of UEs.

[0115] As further shown in Fig. 5, in some aspects, process 500 may include communicating in accordance with the group DCI (block 520). For example, the UE (e.g., using reception component 702, transmission component 704, and / or communication manager 706, depicted in Fig. 7) may communicate in accordance with the group DCI, as described above in connection with Fig. 4. As an example, communication in accordance with the group DCI may include a downlink data transmission or an uplink data transmission.

[0116] Process 500 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in connection with one or more other processes described elsewhere herein.

[0117] In a first aspect, a cyclic redundancy check of the group DCI is scrambled by a group radio network temporary identifier used for the multi-user group of UEs.

[0118] In a second aspect, alone or in combination with the first aspect, the group DCI includes common information for the multi-user group of UEs, and UE-specific information for each UE in the multi-user group of UEs.

[0119] In a third aspect, alone or in combination with one or more of the first and second aspects, the group DCI schedules one or more initial transmissions for the multi-user group of UEs, and one or more retransmissions for the multi-user group of UEs are to be scheduled by UE-specific DCI.

[0120] In a fourth aspect, alone or in combination with one or more of the first through third aspects, the group DCI schedules one or more initial transmissions for the multi-user group of UEs, and one or more retransmissions for the multi-user group of UEs are to be scheduled by additional group DCI.

[0121] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the group DCI schedules one or more initial transmissions for one or more first UEs of the multi-user group of UEs and one or more retransmissions for one or more second UEs of the multi-user group of UEs.

[0122] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the group DCI schedules one or more retransmissions for the multi-user group of UEs responsive to a threshold quantity of UEs, of the multi-user group of UEs, reporting negative acknowledgment feedback for MU-MIMO initial transmissions.

[0123] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the group DCI schedules one or more first retransmissions for the multi-user group of UEs, and one or more second retransmissions for the multi-user group of UEs are to be scheduled by UE-specific DCI.

[0124] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the group DCI includes common information for the multi-user group of UEs, and the common information includes a bitmap that indicates, for each UE of the multi-user group of UEs, whether the MU-MIMO scheduling is for that UE.

[0125] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the group DCI includes UE-specific information for each UE in the multi-user group of UEs, and the UE-specific information for one or more UEs, in the multi-user group of UEs,includes a defined payload to indicate that the MU-MIMO scheduling is not for the one or more UEs.

[0126] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, process 500 includes receiving, via DCI or a MAC-CE, multi-user group information for the multi-user group of UEs.

[0127] In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, process 500 includes receiving, via DCI or a MAC-CE, an indication of an activation or a deactivation of the multi-user group of UEs.

[0128] In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, a search space type for the group DCI is a common search space or a userspecific search space.

[0129] In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, process 500 includes transmitting UE capability information indicating a maximum quantity of multi-user groups supported by the UE.

[0130] Although Fig. 5 shows example blocks of process 500, in some aspects, process 500 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 5. Additionally, or alternatively, two or more of the blocks of process 500 may be performed in parallel.

[0131] Fig. 6 is a diagram illustrating an example process 600 performed, for example, at a network node or an apparatus of a network node, in accordance with the present disclosure. Example process 600 is an example where the apparatus or the network node (e.g., network node 110) performs operations associated with group DCI for MU-MIMO communication.

[0132] As shown in Fig. 6, in some aspects, process 600 may include transmitting, for a UE, group DCI indicating MU-MIMO scheduling for a multi-user group of UEs (block 610). For example, the network node (e.g., using transmission component 804 and / or communication manager 806, depicted in Fig. 8) may transmit, for a UE, group DCI indicating MU-MIMO scheduling for a multi-user group of UEs, as described above in connection with Fig. 4. As an example, the group DCI may include common information for the multi-user group of UEs, and UE-specific information for each UE in the multi-user group of UEs.

[0133] As further shown in Fig. 6, in some aspects, process 600 may include communicating in accordance with the group DCI (block 620). For example, the network node (e.g., using reception component 802, transmission component 804, and / or communication manager 806, depicted in Fig. 8) may communicate in accordance with the group DCI, as described above in connection with Fig. 4. As an example, communication in accordance with the group DCI may include a downlink data transmission or an uplink data transmission.

[0134] Process 600 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in connection with one or more other processes described elsewhere herein.

[0135] In a first aspect, a cyclic redundancy check of the group DCI is scrambled by a group radio network temporary identifier used for the multi-user group of UEs.

[0136] In a second aspect, alone or in combination with the first aspect, the group DCI includes common information for the multi-user group of UEs, and UE-specific information for each UE in the multi-user group of UEs.

[0137] In a third aspect, alone or in combination with one or more of the first and second aspects, the group DCI schedules one or more initial transmissions for the multi-user group of UEs, and one or more retransmissions for the multi-user group of UEs are to be scheduled by UE-specific DCI.

[0138] In a fourth aspect, alone or in combination with one or more of the first through third aspects, the group DCI schedules one or more initial transmissions for the multi-user group of UEs, and one or more retransmissions for the multi-user group of UEs are to be scheduled by additional group DCI.

[0139] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the group DCI schedules one or more initial transmissions for one or more first UEs of the multi-user group of UEs and one or more retransmissions for one or more second UEs of the multi-user group of UEs.

[0140] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the group DCI schedules one or more retransmissions for the multi-user group of UEs responsive to a threshold quantity of UEs, of the multi-user group of UEs, reporting negative acknowledgment feedback for MU-MIMO initial transmissions.

[0141] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the group DCI schedules one or more first retransmissions for the multi-user group of UEs, and one or more second retransmissions for the multi-user group of UEs are to be scheduled by UE-specific DCI.

[0142] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the group DCI includes common information for the multi-user group of UEs, and the common information includes a bitmap that indicates, for each UE of the multi-user group of UEs, whether the MU-MIMO scheduling is for that UE.

[0143] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the group DCI includes UE-specific information for each UE in the multi-user group of UEs, and the UE-specific information for one or more UEs, in the multi-user group of UEs,includes a defined payload to indicate that the MU-MIMO scheduling is not for the one or more UEs.

[0144] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, process 600 includes receiving, via DCI or a MAC-CE, multi-user group information for the multi-user group of UEs.

[0145] In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, process 600 includes receiving, via DCI or a MAC-CE, an indication of an activation or a deactivation of the multi-user group of UEs.

[0146] In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, a search space type for the group DCI is a common search space or a userspecific search space.

[0147] In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, process 600 includes receiving UE capability information indicating a maximum quantity of multi-user groups supported by the UE.

[0148] Although Fig. 6 shows example blocks of process 600, in some aspects, process 600 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 6. Additionally, or alternatively, two or more of the blocks of process 600 may be performed in parallel.

[0149] Fig. 7 is a diagram of an example apparatus 700 for wireless communication, in accordance with the present disclosure. The apparatus 700 may be a UE, or a UE may include the apparatus 700. In some aspects, the apparatus 700 includes a reception component 702, a transmission component 704, and / or a communication manager 706, which may be in communication with one another (for example, via one or more buses and / or one or more other components). In some aspects, the communication manager 706 is the communication manager 140 described in connection with Fig. 1. As shown, the apparatus 700 may communicate with another apparatus 708, such as a UE or a network node (such as a CU, a DU, an RU, or a base station), using the reception component 702 and the transmission component 704.

[0150] In some aspects, the apparatus 700 may be configured to perform one or more operations described herein in connection with Fig. 4. Additionally, or alternatively, the apparatus 700 may be configured to perform one or more processes described herein, such as process 500 of Fig. 5, or a combination thereof. In some aspects, the apparatus 700 and / or one or more components shown in Fig. 7 may include one or more components of the UE described in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 7 may be implemented within one or more components described in connection with Fig. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in one or more memories. For example, acomponent (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the functions or operations of the component.

[0151] The reception component 702 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 708. The reception component 702 may provide received communications to one or more other components of the apparatus 700. In some aspects, the reception component 702 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 of the apparatus 700. In some aspects, the reception component 702 may include one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receive processors, one or more controllers / processors, one or more memories, or a combination thereof, of the UE described in connection with Fig. 2.

[0152] The transmission component 704 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 708. In some aspects, one or more other components of the apparatus 700 may generate communications and may provide the generated communications to the transmission component 704 for transmission to the apparatus 708. In some aspects, the transmission component 704 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 708. In some aspects, the transmission component 704 may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or a combination thereof, of the UE described in connection with Fig. 2. In some aspects, the transmission component 704 may be co-located with the reception component 702 in one or more transceivers.

[0153] The communication manager 706 may support operations of the reception component 702 and / or the transmission component 704. For example, the communication manager 706 may receive information associated with configuring reception of communications by the reception component 702 and / or transmission of communications by the transmission component 704. Additionally, or alternatively, the communication manager 706 may generate and / or provide control information to the reception component 702 and / or the transmission component 704 to control reception and / or transmission of communications.

[0154] The reception component 702 may receive group DCI indicating MU-MIMO scheduling for a multi-user group of UEs. The reception component 702 and / or the transmission component 704 may communicate in accordance with the group DCI.

[0155] The reception component 702 may receive, via DCI or a MAC-CE, multi-user group information for the multi-user group of UEs.

[0156] The reception component 702 may receive, via DCI or a MAC-CE, an indication of an activation or a deactivation of the multi-user group of UEs.

[0157] The transmission component 704 may transmit UE capability information indicating a maximum quantity of multi-user groups supported by the UE.

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

[0159] Fig. 8 is a diagram of an example apparatus 800 for wireless communication, in accordance with the present disclosure. The apparatus 800 may be a network node, or a network node may include the apparatus 800. In some aspects, the apparatus 800 includes a reception component 802, a transmission component 804, and / or a communication manager 806, which may be in communication with one another (for example, via one or more buses and / or one or more other components). In some aspects, the communication manager 806 is the communication manager 150 described in connection with Fig. 1. As shown, the apparatus 800 may communicate with another apparatus 808, such as a UE or a network node (such as a CU, a DU, an RU, or a base station), using the reception component 802 and the transmission component 804.

[0160] In some aspects, the apparatus 800 may be configured to perform one or more operations described herein in connection with Fig. 4. Additionally, or alternatively, the apparatus 800 may be configured to perform one or more processes described herein, such as process 600 of Fig. 6, or a combination thereof. In some aspects, the apparatus 800 and / or one or more components shown in Fig. 8 may include one or more components of the network node described in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 8 may be implemented within one or more components described in connection with Fig. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in one or more memories. 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 one or more controllers or one or more processors to perform the functions or operations of the component.

[0161] The reception component 802 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 808. The reception component 802 may provide received communications to one or more other components of the apparatus 800. In some aspects, the reception component 802 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 of the apparatus 800. In some aspects, the reception component 802 may include one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receive processors, one or more controllers / processors, one or more memories, or a combination thereof, of the network node described in connection with Fig. 2. In some aspects, the reception component 802 and / or the transmission component 804 may include or may be included in a network interface. The network interface may be configured to obtain and / or output signals for the apparatus 800 via one or more communications links, such as a backhaul link, a midhaul link, and / or a fronthaul link.

[0162] The transmission component 804 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 808. In some aspects, one or more other components of the apparatus 800 may generate communications and may provide the generated communications to the transmission component 804 for transmission to the apparatus 808. In some aspects, the transmission component 804 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 808. In some aspects, the transmission component 804 may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or a combination thereof, of the network node described in connection with Fig. 2. In some aspects, the transmission component 804 may be co-located with the reception component 802 in one or more transceivers.

[0163] The communication manager 806 may support operations of the reception component 802 and / or the transmission component 804. For example, the communication manager 806 may receive information associated with configuring reception of communications by the reception component 802 and / or transmission of communications by the transmissioncomponent 804. Additionally, or alternatively, the communication manager 806 may generate and / or provide control information to the reception component 802 and / or the transmission component 804 to control reception and / or transmission of communications.

[0164] The transmission component 804 may transmit, for a UE, group DCI indicating MU- MIMO scheduling for a multi-user group of UEs. The reception component 802 and / or the transmission component 804 may communicate in accordance with the group DCI.

[0165] The reception component 802 may receive, via DCI or a MAC-CE, multi-user group information for the multi-user group of UEs.

[0166] The reception component 802 may receive, via DCI or a MAC-CE, an indication of an activation or a deactivation of the multi-user group of UEs.

[0167] The reception component 802 may receive UE capability information indicating a maximum quantity of multi-user groups supported by the UE.

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

[0169] The following provides an overview of some Aspects of the present disclosure:

[0170] Aspect 1 : A method of wireless communication performed by a user equipment (UE), comprising: receiving group downlink control information (DCI) indicating multi-user multiple- input-multiple-output (MU-MIMO) scheduling for a multi-user group of UEs; and communicating in accordance with the group DCI.

[0171] Aspect 2: The method of Aspect 1, wherein a cyclic redundancy check of the groupDCI is scrambled by a group radio network temporary identifier used for the multi-user group of UEs.

[0172] Aspect 3: The method of any of Aspects 1-2, wherein the group DCI includes common information for the multi-user group of UEs, and UE-specific information for each UE in the multi-user group of UEs.

[0173] Aspect 4: The method of any of Aspects 1-3, wherein the group DCI schedules one or more initial transmissions for the multi-user group of UEs, and wherein one or more retransmissions for the multi-user group of UEs are to be scheduled by UE-specific DCI.

[0174] Aspect 5: The method of any of Aspects 1-3, wherein the group DCI schedules one or more initial transmissions for the multi-user group of UEs, and wherein one or more retransmissions for the multi-user group of UEs are to be scheduled by additional group DCI.

[0175] Aspect 6: The method of any of Aspects 1-3, wherein the group DCI schedules one or more initial transmissions for one or more first UEs of the multi-user group of UEs and one or more retransmissions for one or more second UEs of the multi-user group of UEs.

[0176] Aspect 7: The method of any of Aspects 1-3 or 6, wherein the group DCI schedules one or more retransmissions for the multi-user group of UEs responsive to a threshold quantity of UEs, of the multi-user group of UEs, reporting negative acknowledgment feedback for MU- MIMO initial transmissions.

[0177] Aspect 8: The method of any of Aspects 1-3 or 6-7, wherein the group DCI schedules one or more first retransmissions for the multi-user group of UEs, and wherein one or more second retransmissions for the multi-user group of UEs are to be scheduled by UE-specific DCI.

[0178] Aspect 9: The method of any of Aspects 1-8, wherein the group DCI includes common information for the multi-user group of UEs, and the common information includes a bitmap that indicates, for each UE of the multi-user group of UEs, whether the MU-MIMO scheduling is for that UE.

[0179] Aspect 10: The method of any of Aspects 1-9, wherein the group DCI includes UE- specific information for each UE in the multi-user group of UEs, and the UE-specific information for one or more UEs, in the multi-user group of UEs, includes a defined payload to indicate that the MU-MIMO scheduling is not for the one or more UEs.

[0180] Aspect 11: The method of any of Aspects 1-10, further comprising: receiving, via DCI or a medium access control control element (MAC-CE), multi-user group information for the multi-user group of UEs.

[0181] Aspect 12: The method of any of Aspects 1-11, further comprising: receiving, via DCI or a medium access control control element (MAC-CE), an indication of an activation or a deactivation of the multi-user group of UEs.

[0182] Aspect 13: The method of any of Aspects 1-12, wherein a search space type for the group DCI is a common search space or a user-specific search space.

[0183] Aspect 14: The method of any of Aspects 1-13, further comprising: transmitting UE capability information indicating a maximum quantity of multi-user groups supported by the UE.

[0184] Aspect 15: A method of wireless communication performed by a network node, comprising: transmitting, for a user equipment (UE), group downlink control information (DCI) indicating multi-user multiple -input-multiple -output (MU-MIMO) scheduling for a multi-user group of UEs; and communicating in accordance with the group DCI.

[0185] Aspect 16: The method of Aspect 15, wherein a cyclic redundancy check of the group DCI is scrambled by a group radio network temporary identifier used for the multi-user group of UEs.

[0186] Aspect 17: The method of any of Aspects 15-16, wherein the group DCI includes common information for the multi-user group of UEs, and UE-specific information for each UE in the multi-user group of UEs.

[0187] Aspect 18: The method of any of Aspects 15-17, wherein the group DCI schedules one or more initial transmissions for the multi-user group of UEs, and wherein one or more retransmissions for the multi-user group of UEs are to be scheduled by UE-specific DCI.

[0188] Aspect 19: The method of any of Aspects 15-17, wherein the group DCI schedules one or more initial transmissions for the multi-user group of UEs, and wherein one or more retransmissions for the multi-user group of UEs are to be scheduled by additional group DCI.

[0189] Aspect 20: The method of any of Aspects 15-17, wherein the group DCI schedules one or more initial transmissions for one or more first UEs of the multi-user group of UEs and one or more retransmissions for one or more second UEs of the multi-user group of UEs.

[0190] Aspect 21: The method of any of Aspects 15-17 or 20, wherein the group DCI schedules one or more retransmissions for the multi-user group of UEs responsive to a threshold quantity of UEs, of the multi-user group of UEs, reporting negative acknowledgment feedback for MU-MIMO initial transmissions.

[0191] Aspect 22: The method of any of Aspects 15-17 or 20-21, wherein the group DCI schedules one or more first retransmissions for the multi-user group of UEs, and wherein one or more second retransmissions for the multi-user group of UEs are to be scheduled by UE-specific DCI.

[0192] Aspect 23: The method of any of Aspects 15-22, wherein the group DCI includes common information for the multi-user group of UEs, and the common information includes a bitmap that indicates, for each UE of the multi-user group of UEs, whether the MU-MIMO scheduling is for that UE.

[0193] Aspect 24: The method of any of Aspects 15-23, wherein the group DCI includes UE- specific information for each UE in the multi-user group of UEs, and the UE-specific information for one or more UEs, in the multi-user group of UEs, includes a defined payload to indicate that the MU-MIMO scheduling is not for the one or more UEs.

[0194] Aspect 25: The method of any of Aspects 15-24, further comprising: receiving, via DCI or a medium access control control element (MAC-CE), multi-user group information for the multi-user group of UEs.

[0195] Aspect 26: The method of any of Aspects 15-25, further comprising: receiving, via DCI or a medium access control control element (MAC-CE), an indication of an activation or a deactivation of the multi-user group of UEs.

[0196] Aspect 27: The method of any of Aspects 15-26, wherein a search space type for the group DCI is a common search space or a user-specific search space.

[0197] Aspect 28: The method of any of Aspects 15-27, further comprising: receiving UE capability information indicating a maximum quantity of multi-user groups supported by the UE.

[0198] Aspect 29: A system configured to perform one or more operations recited in one or more of Aspects 1-28.

[0199] Aspect 30: An apparatus comprising means for performing one or more operations recited in one or more of Aspects 1-28.

[0200] Aspect 31 : A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising one or more instructions that, when executed by a device, cause the device to perform one or more operations recited in one or more of Aspects 1-28.

[0201] Aspect 32: A computer program product comprising instructions or code for executing one or more operations recited in one or more of Aspects 1-28.

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

[0203] As used herein, the term “component” is intended to be broadly construed as hardware or a combination of hardware and at least one of software or firmware. “Software” shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a “processor” is implemented in hardware 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 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 are described herein without reference to specific software code, because those skilled in the art will understand that software and hardware can be designed to implement the systems or methods based, at least in part, on the description herein. A component being configured to perform a function means that thecomponent has a capability to perform the function, and does not require the function to be actually performed by the component, unless noted otherwise.

[0204] 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, or not equal to the threshold, among other examples.

[0205] As used herein, 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).

[0206] 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 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 that do not limit an element that they modify (for example, an element “having” A may also have B). Further, the phrase “based on” is intended to mean “based on or otherwise in association with” 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 “and / or,” unless explicitly stated otherwise (for example, if used in combination with “either” or “only one of’). It should be understood that “one or more” is equivalent to “at least one.”

[0207] 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. Many of these features may be combined in ways not specifically recited in the claims or disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set.

Claims

WHAT IS CLAIMED IS:

1. An apparatus for wireless communication at a user equipment (UE), comprising: one or more memories; and one or more processors, coupled to the one or more memories, configured to cause the UE to: receive group downlink control information (DCI) indicating multi-user multiple-input-multiple-output (MU-MIMO) scheduling for a multi-user group of UEs; and communicate in accordance with the group DCL2. The apparatus of claim 1, wherein a cyclic redundancy check of the group DCI is scrambled by a group radio network temporary identifier used for the multi-user group of UEs.

3. The apparatus of claim 1, wherein the group DCI includes common information for the multi-user group of UEs, and UE-specific information for each UE in the multi-user group of UEs.

4. The apparatus of claim 1, wherein the group DCI schedules one or more initial transmissions for the multi-user group of UEs, and wherein one or more retransmissions for the multi-user group of UEs are to be scheduled by UE-specific DCI.

5. The apparatus of claim 1, wherein the group DCI schedules one or more initial transmissions for the multi-user group of UEs, and wherein one or more retransmissions for the multi-user group of UEs are to be scheduled by additional group DCI.

6. The apparatus of claim 1, wherein the group DCI schedules one or more initial transmissions for one or more first UEs of the multi-user group of UEs and one or more retransmissions for one or more second UEs of the multi-user group of UEs.

7. The apparatus of claim 1, wherein the group DCI schedules one or more retransmissions for the multi-user group of UEs responsive to a threshold quantity of UEs, of the multi-user group ofUEs, reporting negative acknowledgment feedback for MU-MIMO initial transmissions.

8. The apparatus of claim 1, wherein the group DCI schedules one or more first retransmissions for the multi-user group of UEs, and wherein one or more second retransmissions for the multi-user group of UEs are to be scheduled by UE-specific DCL9. The apparatus of claim 1, wherein the group DCI includes common information for the multi-user group of UEs, and the common information includes a bitmap that indicates, for each UE of the multi-user group of UEs, whether the MU-MIMO scheduling is for that UE.

10. The apparatus of claim 1, wherein the group DCI includes UE-specific information for each UE in the multi-user group of UEs, and the UE-specific information for one or more UEs, in the multi-user group of UEs, includes a defined payload to indicate that the MU-MIMO scheduling is not for the one or more UEs.

11. The apparatus of claim 1, wherein the one or more processors are further configured to cause the UE to: receive, via DCI or a medium access control control element (MAC-CE), multi-user group information for the multi-user group of UEs, or an indication of an activation or a deactivation of the multi-user group of UEs.

12. The apparatus of claim 1, wherein a search space type for the group DCI is a common search space or a user-specific search space.

13. The apparatus of claim 1, wherein the one or more processors are further configured to cause the UE to: transmit UE capability information indicating a maximum quantity of multi-user groups supported by the UE.

14. An apparatus for wireless communication at a network node, comprising: one or more memories; and one or more processors, coupled to the one or more memories, configured to cause the network node to: transmit, for a user equipment (UE), group downlink control information (DCI) indicating multi-user multiple-input-multiple-output (MU-MIMO) scheduling for a multi-user group of UEs; and communicate in accordance with the group DCI.

15. The apparatus of claim 14, wherein a cyclic redundancy check of the group DCI is scrambled by a group radio network temporary identifier used for the multi-user group of UEs.

16. The apparatus of claim 14, wherein the group DCI includes common information for the multi-user group of UEs, and UE-specific information for each UE in the multi-user group of UEs.

17. The apparatus of claim 14, wherein the group DCI schedules one or more initial transmissions for the multi-user group of UEs, and wherein one or more retransmissions for the multi-user group of UEs are to be scheduled by UE-specific DCI.

18. The apparatus of claim 14, wherein the group DCI schedules one or more initial transmissions for the multi-user group of UEs, and wherein one or more retransmissions for the multi-user group of UEs are to be scheduled by additional group DCI.

19. The apparatus of claim 14, wherein the group DCI schedules one or more initial transmissions for one or more first UEs of the multi-user group of UEs and one or more retransmissions for one or more second UEs of the multi-user group of UEs.

20. The apparatus of claim 14, wherein the group DCI schedules one or more retransmissions for the multi-user group of UEs responsive to a threshold quantity of UEs, of the multi-user group of UEs, reporting negative acknowledgment feedback for MU-MIMO initial transmissions.

21. The apparatus of claim 14, wherein the group DCI schedules one or more first retransmissions for the multi-user group of UEs, and wherein one or more second retransmissions for the multi-user group of UEs are to be scheduled by UE-specific DCI.

22. The apparatus of claim 14, wherein the group DCI includes common information for the multi-user group of UEs, and the common information includes a bitmap that indicates, for each UE of the multi-user group of UEs, whether the MU-MIMO scheduling is for that UE.

23. The apparatus of claim 14, wherein the group DCI includes UE-specific information for each UE in the multi-user group of UEs, and the UE-specific information for one or more UEs,in the multi-user group of UEs, includes a defined payload to indicate that the MU-MIMO scheduling is not for the one or more UEs.

24. The apparatus of claim 14, wherein the one or more processors are further configured to cause the network node to: receive, via DCI or a medium access control control element (MAC-CE), multi-user group information for the multi-user group of UEs, or an indication of an activation or a deactivation of the multi-user group of UEs.

25. The apparatus of claim 14, wherein a search space type for the group DCI is a common search space or a user-specific search space.

26. The apparatus of claim 14, wherein the one or more processors are further configured to cause the network node to: receive UE capability information indicating a maximum quantity of multi-user groups supported by the UE.

27. A method of wireless communication performed by a user equipment (UE), comprising: receiving group downlink control information (DCI) indicating multi-user multiple- input-multiple-output (MU-MIMO) scheduling for a multi-user group of UEs; and communicating in accordance with the group DCI.

28. The method of claim 27, wherein the group DCI includes common information for the multi-user group of UEs, and UE-specific information for each UE in the multi-user group of UEs.

29. A method of wireless communication performed by a network node, comprising: transmitting, for a user equipment (UE), group downlink control information (DCI) indicating multi-user multiple -input-multiple -output (MU-MIMO) scheduling for a multi-user group of UEs; and communicating in accordance with the group DCI.

30. The method of claim 29, wherein the group DCI includes common information for the multi-user group of UEs, and UE-specific information for each UE in the multi-user group of UEs.

Images