Multi-user scheduling indication for demodulation of reference signals

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive signaling that schedules a shared channel and indicates a set of demodulation reference signal (DMRS) ports scheduled for the UE, the signaling including a field for communicating indicators of UEs for co-scheduling of the set of DMRS ports. The UE may communicate a set of DMRSs based at least in part on the signaling. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Non-Provisional Patent Application No. 18 / 480,367, filed on October 3, 2023, entitled “MULTI-USER SCHEDULING INDICATION FOR DEMODULATION REFERENCE SIGNALS” and U.S. Provisional Patent Application No. 63 / 379,122, filed on October 11, 2022, entitled “MULTI-USER SCHEDULING INDICATION FOR DEMODULATION REFERENCE SIGNALS” and assigned to the assignee of this application. The disclosure of the prior application is considered a part of and incorporated by reference into this patent application. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for multi-user scheduling indication for a demodulation reference signal. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network nodes that support communications for wireless communication devices, such as user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network node to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communications, such as via a local link (e.g., a side link (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, etc.).

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by: improving spectrum efficiency; reducing costs; improving services; utilizing new spectrum; and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards; and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0007] Some aspects described herein relate to a method of wireless communication performed by an apparatus of a user equipment (UE). The method may include receiving signaling that schedules a shared channel and indicates a set of demodulation reference signal (DMRS) ports scheduled for the UE, the signaling including a field for conveying an indicator of a co-scheduled UE for the set of DMRS ports. The method may include communicating the DMRS set based at least in part on the signaling.

[0008] Some aspects described herein relate to a method of wireless communication performed by an apparatus of a network node. The method may include sending signaling that schedules a shared channel and indicates a set of DMRS ports scheduled for a target UE, the signaling including a field for conveying an indicator of a co-scheduled UE for the set of DMRS ports. The method may include communicating the DMRS set according to the signaling.

[0009] Some aspects described herein relate to a UE for wireless communication. The UE 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 receive signaling that schedules a shared channel and indicates a set of DMRS ports scheduled for the UE, the signaling including a field for conveying an indicator of a co-scheduled UE for the set of DMRS ports. The one or more processors may be configured to communicate the DMRS set based at least in part on the signaling.

[0010] Some aspects described herein relate to a network node for wireless communication. The network node 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 send signaling that schedules a shared channel and indicates a DMRS port set scheduled for a target UE, the signaling including a field for conveying an indicator of a co-scheduled UE for the DMRS port set. The one or more processors may be configured to communicate the DMRS set according to the signaling.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, can cause the UE to receive signaling that schedules a shared channel and indicates a set of DMRS ports scheduled for the UE, the signaling including a field for conveying an indicator of a co-scheduled UE for the set of DMRS ports. The instruction set, when executed by one or more processors of the UE, can cause the UE to communicate the DMRS set based at least in part on the signaling.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network node. The instruction set, when executed by one or more processors of the network node, can cause the network node to send signaling that schedules a shared channel and indicates a DMRS port set scheduled for a target UE, the signaling including a field for conveying an indicator of a co-scheduled UE for the DMRS port set. The instruction set, when executed by one or more processors of the network node, can cause the network node to communicate the DMRS set according to the signaling.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving signaling that schedules a shared channel and indicates a set of DMRS ports scheduled for the apparatus, the signaling including a field for conveying an indicator of a co-scheduled UE for the set of DMRS ports. The apparatus may include means for communicating the DMRS set based at least in part on the signaling.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include a component for sending signaling that schedules a shared channel and indicates a set of DMRS ports scheduled for a target UE, the signaling including a field for conveying an indicator of a co-scheduled UE for the set of DMRS ports. The apparatus may include a component for communicating the DMRS set according to the signaling.

[0015] Aspects collectively include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the drawings and description and as illustrated in the drawings and description.

[0016] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of limitations to the claims.

[0017] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0019] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0020] Figure 2 is a diagram illustrating an example of communication between a network node and a UE in a wireless network according to the present disclosure.

[0021] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0022] Figure 4 is a diagram illustrating an example of physical channels and reference signals in a wireless network according to the present disclosure.

[0023] FIG. 5A to FIG. 5D is a diagram illustrating an example associated with a multi-user scheduling indication for a demodulation reference signal (DMRS) according to the present disclosure.

[0024] Figure 6 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0025] Figure 7 is a diagram illustrating an example process, for example, performed by a network node, according to the present disclosure.

[0026] Figure 8 and Fig. 9 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0027] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. On the contrary, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods implemented using other structures, functions, or structures and functions in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0028] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0029] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or RATs beyond 5G (e.g., 6G).

[0030] A network node may assign a UE in a user equipment (UE) group to a DMRS port in a demodulation reference signal (DMRS) port group for communicating DMRS (e.g., for the network node to send DMRS to the UE or for the UE to send DMRS to the network node). In some cases, such as in a multi-user (MU) multiple-input multiple-output (MIMO) (MU-MIMO) communication system, a network node may schedule a target UE using a set of DMRS ports, and may co-schedule one or more other UEs using a set of DMRS ports. The network node may assign different orthogonal cover codes (OCCs) to each of the target UE and one or more other UEs to enable co-scheduling. Co-scheduling may enable a larger number of UEs to operate in a communication system using a shared set of resources. However, co-scheduling may introduce additional sources of interference. For example, communication between a network node and one or more other UEs may interfere with communication between a target UE and a network node.

[0031] Some aspects described herein enable a network node to provide a target UE with information identifying a set of DMRS ports for the target UE and information about the DMRS ports of other co-scheduled UEs. For example, the network node may send signaling, such as downlink control information (DCI) or a medium access control (MAC) control element (CE) (MAC-CE), which includes one or more fields indicating whether there are any co-scheduled UEs, how many co-scheduled UEs there are, and / or resource block allocations for any co-scheduled UEs. In this case, the target UE may use the information about the co-scheduled UEs for channel estimation performed in conjunction with, for example, receiving DMRS from the network node. Based at least in part on improving channel estimation, the network node and the UE improve communication performance by reducing the likelihood of dropped communications and / or the decoding complexity associated with communications.

[0032] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), one UE 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), which means that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0033] In some examples, the network node 110 is or includes a network node (such as an RU) that communicates with the UE 120 via a radio access link. In some examples, the network node 110 is or includes a network node (such as a DU) that communicates with other network nodes 110 via a fronthaul link or a midhaul link. In some examples, the network node 110 is or includes a network node (such as a CU) that communicates with other network nodes 110 via a midhaul link or communicates with the core network via a backhaul link. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. The network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul, midhaul, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks) using any suitable transport network.

[0034] In some examples, the network node 110 can provide communication coverage for a specific geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" can refer to the coverage area of ​​the network node 110 and / or the network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 can provide communication coverage for a macro cell, a micro cell, a femto cell, and / or another type of cell. A macro cell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by a UE 120 with a service subscription. A micro cell can cover a relatively small geographic area and can allow unrestricted access by a UE 120 with a service subscription. A femto cell can cover a relatively small geographic area (e.g., a home) and can allow restricted access by a UE 120 associated with a femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell can be referred to as a macro network node. A network node 110 for a micro cell can be referred to as a micro network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1 In the example shown, network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

[0035] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with network node 110). In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of a plurality of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions, but not another base station function. In this way, a single device may include more than one base station.

[0036] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown, a network node 110d (e.g., a relay network node) may communicate with a network node 110a (e.g., a macro network node) and a UE 120d to facilitate communication between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, etc.

[0037] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0038] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless backhaul communication link or a wired backhaul communication link. In some aspects, the network controller 130 may be, or may include, a CU or a core network device.

[0039] UE 120 can be distributed throughout the wireless network 100, and each UE 120 can be stationary or mobile. UE 120 can include, for example, an access terminal, a terminal, a mobile station and / or a subscriber unit. UE 120 can be a cellular phone (e.g., 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 computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, a UE function of a network node and / or any other suitable device configured to communicate via a wireless or wired medium.

[0040] Some UE 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UE. MTC UE and / or eMTC UE may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor and / or a location tag, which may communicate with a network node, another device (e.g., a remote device) or some other entity. Some UE 120 may be considered as an Internet of Things (IoT) device and / or may be implemented as a NB-IoT (narrowband IoT) device. Some UE 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operationally coupled, communicatively coupled, electronically coupled and / or electrically coupled.

[0041] Generally speaking, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, an air interface, etc. Frequency may be referred to as a carrier, a frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0042] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more side link channels (e.g., without using network node 110 as an intermediary to communicate with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0043] The devices of the wireless network 100 can communicate using an electromagnetic spectrum that can be subdivided into various categories, bands, channels, etc. according to frequency or wavelength. For example, the devices of the wireless network 100 can communicate using one or more operating bands. In 5GNR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. Similar naming issues sometimes occur with reference to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0044] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, so the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz–71GHz), FR4 (52.6GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.

[0045] In view of the above examples, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term can be broadly representative of frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term can be broadly representative of frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0046] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may: receive signaling that schedules a shared channel and indicates a set of DMRS ports scheduled for the UE, the signaling including a field for conveying an indicator of a co-scheduled UE for the set of DMRS ports; and communicate the DMRS set based at least in part on the signaling. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0047] 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: send signaling that schedules a shared channel and indicates a DMRS port set scheduled for a target UE, the signaling including a field for conveying an indicator of a co-scheduled UE for the DMRS port set; and communicate the DMRS set according to the signaling. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0048] As indicated above, Figure 1 is provided as an example. Other examples can be found in the Figure 1 The content described is different.

[0049] Figure 2 2 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 254. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0050] At the network node 110, a transmit processor 220 may receive data intended for a UE 120 (or a set of UEs 120) from a data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or DMRS) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) MIMO processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0051] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) can receive downlink signals from the network node 110 and / or other network nodes 110 and can provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal can be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 can use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert and / or digitize) the received signal to obtain input samples. Each modem 254 can use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 can obtain received symbols from the modem 254, can perform MIMO detection on the received symbols where applicable, and can provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0052] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0053] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2One or more antenna elements of one or more components in.

[0054] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform operations described herein (eg, with reference to FIG. 5A to FIG. 9 ) or any aspects of any of the methods described herein.

[0055] At the network node 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component (shown as DEMOD) of the modem 232), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink communication and / or uplink communication. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein (e.g., reference 200 to FIG. 1 ). FIG. 5A to FIG. 9 ).

[0056] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component in may perform one or more techniques associated with multi-user scheduling indication for DMRS, 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, and / or Figure 2 Any other component of may perform or direct e.g. Figure 6 The process of 600 Figure 7 700 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly executed, or executed after compilation, conversion, and / or interpretation), may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Figure 6 The process of 600 Figure 7 The process 700 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0057] In some aspects, the UE 120 includes means for receiving signaling that schedules a shared channel and indicates a set of DMRS ports scheduled for the UE, the signaling including a field for conveying an indicator of a co-scheduled UE for the set of DMRS ports; and / or means for communicating the DMRS set based at least in part on the signaling. Means for the UE 120 to perform operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0058] In some aspects, the network node 110 includes a means for sending a signaling that schedules a shared channel and indicates a DMRS port set scheduled for a target UE, the signaling including a field for conveying an indicator of a co-scheduled UE for the DMRS port set; and / or a means for communicating the DMRS set according to the signaling. The means for the network node 110 to perform the operations described herein may include, for example, one or more of the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0059] Although Figure 2 The blocks in the 200 and 210 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for 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.

[0060] As indicated above, Figure 2 is provided as an example. Other examples can be found in the Figure 2 The content described is different.

[0061] The deployment of communication systems such as 5G NR systems can be arranged in a variety of ways with various components or components. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) performing base station functionality can be implemented as an aggregated base station (also called an independent base station or a monolithic base station) or a decomposed base station. A "network entity" or a "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs or a combination thereof).

[0062] An aggregated base station (e.g., an aggregated network node) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) can be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the CU can be implemented within a network node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed across one or more other network nodes. The DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), and the like.

[0063] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate scaling of the communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Individual units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0064] Figure 3 3 is a diagram illustrating an example disaggregated base station architecture 300 according to the present disclosure. The disaggregated base station architecture 300 may include a CU 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units, such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via an F1 interface. 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 radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0065] Each of the units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO framework 305 may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of the units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, the wireless interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, or both.

[0066] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, etc. Each control function may be implemented using an interface configured to transmit signals with other control functions hosted by CU 310. CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some specific implementations, CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 310 may be implemented to communicate with DU 330 for network control and signaling.

[0067] Each DU 330 may correspond to a logical unit including one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a MAC layer, and one or more high physical (PHY) layers, at least in part according to a functional partitioning (such as a functional partitioning defined by 3GPP). In some aspects, one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as by one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0068] Each RU 340 may implement lower layer functionality. In some deployments, a RU 340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc. based on a functional split (e.g., a functional split defined by 3GPP) (such as a lower layer functional split). In this architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of communicating with the control plane and user plane of the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0069] The SMO framework 305 may be configured to support RAN deployment and configuration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via an O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0070] The non-RT RIC 315 may be configured to include logic functions that implement non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that implement near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0071] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0072] As indicated above, Figure 3 is provided as an example. Other examples can be found in the Figure 3 The content described is different.

[0073] Figure 4 4 is a diagram illustrating an example 400 of physical channels and reference signals in a wireless network according to the present disclosure. Figure 4 As shown in , the downlink channel and the downlink reference signal may carry information from the network node 110 to the UE 120 , and the uplink channel and the uplink reference signal may carry information from the UE 120 to the network node 110 .

[0074] As shown, the downlink channels may include a physical downlink control channel (PDCCH) carrying DCI, a physical downlink shared channel (PDSCH) carrying downlink data, or a physical broadcast channel (PBCH) carrying system information, etc. In some aspects, PDSCH communications may be scheduled by PDCCH communications. As further shown, uplink channels may include a physical uplink control channel (PUCCH) carrying uplink control information (UCI), a physical uplink shared channel (PUSCH) carrying uplink data, or a PRACH for initial network access, etc. In some aspects, UE 120 may send acknowledgement (ACK) or negative acknowledgement (NACK) feedback (e.g., ACK / NACK feedback or ACK / NACK information) in the UCI on the PUCCH and / or PUSCH.

[0075] As further shown, the downlink reference signal may include a synchronization signal block (SSB), a channel state information (CSI) reference signal (CSI-RS), a DMRS, a positioning reference signal (PRS), or a phase tracking reference signal (PTRS), etc. As also shown, the uplink reference signal may include a sounding reference signal (SRS), a DMRS, or a PTRS, etc.

[0076] The SSB may carry information used for initial network acquisition and synchronization, such as PSS, SSS, PBCH, and PBCH DMRS. The SSB is sometimes referred to as a synchronization signal / PBCH (SS / PBCH) block. In some aspects, the network node 110 may send multiple SSBs on multiple corresponding beams, and the SSBs may be used for beam selection.

[0077] The CSI-RS may carry information for downlink channel estimation (e.g., downlink CSI acquisition), which may be used for scheduling, link adaptation, or beam management, among other things. The network node 110 may configure a CSI-RS set for the UE 120, and the UE 120 may measure the configured CSI-RS set. Based at least in part on the measurements, the UE 120 may perform channel estimation and may report channel estimation parameters such as CQI, precoding matrix indicator (PMI), CSI-RS resource indicator (CRI), layer indicator (LI), rank indicator (RI), or RSRP, among other things, to the network node 110 (e.g., in a CSI report). The network node 110 may use the CSI report to select transmission parameters for downlink communication with the UE 120, such as the number of transmission layers (e.g., rank), precoding matrix (e.g., precoder), MCS, or a refined downlink beam (e.g., using a beam refinement process or a beam management process), among other things.

[0078] DMRS may carry information for estimating a radio channel to demodulate an associated physical channel (e.g., PDCCH, PDSCH, PBCH, PUCCH, or PUSCH). The design and mapping of DMRS may be specific to the physical channel that the DMRS is used to estimate. DMRS is UE-specific, may be beamformed, may be restricted to scheduled resources (e.g., rather than being sent over a wideband), and may be sent only when necessary. As shown, DMRS is used for both downlink and uplink communications.

[0079] Different specifications may specify different numbers of DMRS ports. For example, for UEs and network nodes that comply with 3GPP Release (Rel) 18, a larger number of DMRS ports are configured than for UEs and network nodes that comply with 3GPP Release 15, Release 16, or Release 17 (and do not comply with Release 18). The increased number of DMRS ports is achieved by the UE and network nodes using a larger scale of frequency division (FD) orthogonal cover codes (OCC) (FD-OCC). This allows a larger number of DMRS ports to be multiplexed into a common set of resources using FD-OCC. The number of DMRS ports can be further increased by the UE and network nodes using two DMRS symbols for DMRS communication instead of one DMRS symbol.

[0080] PTRS can carry information for compensating for oscillator phase noise. Typically, phase noise increases with the increase of the oscillator carrier frequency. Therefore, PTRS can be used at high carrier frequencies (such as millimeter wave frequencies) to mitigate phase noise. PTRS can be used to track the phase of the local oscillator and to achieve suppression of phase noise and common phase error (CPE). As shown, PTRS is used for both downlink communications (e.g., on PDSCH) and uplink communications (e.g., on PUSCH).

[0081] The PRS may carry information for implementing timing or ranging measurements of the UE 120 based on signals sent by the network node 110 to improve observed time difference of arrival (OTDOA) positioning performance. For example, the PRS may be a pseudo-random quadrature phase shift keying (QPSK) sequence mapped in a diagonal pattern with a frequency offset and a time offset to avoid conflicts with cell-specific reference signals and control channels (e.g., PDCCH). In general, the PRS may be designed to improve the detectability of the UE 120, which may need to detect downlink signals from multiple adjacent neighboring network nodes in order to perform OTDOA-based positioning. Therefore, the UE 120 may receive the PRS from multiple cells (e.g., a reference cell and one or more neighboring cells), and may report a reference signal time difference (RSTD) based on the OTD measurements associated with the PRS received from the multiple cells. In some aspects, the network node 110 may then calculate the position of the UE 120 based on the RSTD measurements reported by the UE 120.

[0082] The SRS may carry information for uplink channel estimation, which may be used for scheduling, link adaptation, pre-decoder selection, or beam management, etc. The network node 110 may configure one or more SRS resource sets for the UE 120, and the UE 120 may send the SRS on the configured SRS resource sets. The SRS resource sets may have configured purposes, such as uplink CSI acquisition, downlink CSI acquisition for reciprocity-based operation, uplink beam management, etc. The network node 110 may measure the SRS, may perform channel estimation based at least in part on these measurement results, and may use the SRS measurement results to configure communications with the UE 120.

[0083] As indicated above, Figure 4 is provided as an example. Other examples can be found in the Figure 4 The content described is different.

[0084] The network node may assign a UE group to a DMRS port group for communicating DMRS (e.g., for the network node to send DMRS to the UE or for the UE to send DMRS to the network node). In some cases, such as in a MU-MIMO communication system, the network node may schedule the target UE using a DMRS port set, and may co-schedule one or more other UEs using a DMRS port set. The network node may assign different OCCs to each of the target UE and one or more other UEs to enable co-scheduling. Co-scheduling may enable a larger number of UEs to operate in a communication system using a shared set of resources. However, co-scheduling may introduce additional interference sources. For example, communication between a network node and one or more other UEs may interfere with communication between the target UE and the network node.

[0085] Some aspects described herein enable a network node to provide a target UE with information identifying a set of DMRS ports for the target UE and information about the DMRS ports of other co-scheduled UEs. For example, the network node may send signaling, such as a DCI or MAC-CE, that includes one or more fields indicating whether there are any co-scheduled UEs, how many co-scheduled UEs there are, and / or resource block allocations for any co-scheduled UEs. In this case, the target UE may use the information about the co-scheduled UEs for channel estimation performed in conjunction with, for example, receiving DMRS from the network node. Based at least in part on improving channel estimation, the network node and UE improve communication performance by reducing the likelihood of dropped communications and / or decoding compounding associated with communications.

[0086] FIG. 5A to FIG. 5D is a diagram illustrating an example 500 associated with a multi-user scheduling indication for DMRS according to the present disclosure. Figure 5A As shown in , example 500 includes communications between a network node 110 and a target UE 120.

[0087] like Figure 5A, and further illustrated by reference numeral 510, the target UE 120 may receive signaling from the network node 110. For example, the target UE 120 may receive a DCI or MAC-CE that schedules a PDSCH communication or a PUSCH communication. Additionally or alternatively, the target UE 120 may receive signaling (e.g., a DCI or MAC-CE) indicating a set of DMRS ports to be used in conjunction with the scheduled communication (e.g., for receiving DMRS and performing channel estimation). In some aspects, the signaling (e.g., a DCI or MAC-CE) may include co-scheduling information. For example, the network node 110 may identify information about one or more UEs 120 co-scheduled with the target UE 120. In some aspects, the co-scheduling information may include information indicating whether there are any other co-scheduled UEs 120 (e.g., whether co-scheduling is ongoing), how many other co-scheduled UEs 120 there are, or resource block allocations associated with any other co-scheduled UEs 120, as described in more detail herein. For example, the network node 110 may communicate an indicator of whether there are any co-scheduled UEs 120 (e.g., an indicator of the presence or absence of any co-scheduled UEs) or an indicator of the number of these co-scheduled UEs (e.g., an indicator of 0 co-scheduled UEs, 1 co-scheduled UE, 2 co-scheduled UEs, 3 co-scheduled UEs, or another number of co-scheduled UEs).

[0088] In some aspects, the target UE 120 may receive a 1-bit indicator identifying whether there are co-scheduled UEs 120 for a set of DMRS ports assigned to the target UE 120. For example, the target UE 120 may receive signaling (e.g., DCI or MAC-CE) and parse the signaling to identify the 1-bit indicator that is set to indicate whether there are any other UEs 120 co-scheduled with the target UE 120 within its resource block (RB) allocation. Figure 5B An example of a bit indication is shown. Figure 5B, the target UE 120 is scheduled with a rank 2 PDSCH on DMRS ports 0 and 1. In this case, the network node 110 includes a 1-bit indicator in the signaling (e.g., DCI or MAC-CE) to indicate to the target UE 120 whether DMRS ports 8 and 9 (e.g., which may be in the same code division multiplexing (CDM) group as DMRS ports 0 and 1) are co-scheduled with any other UE 120. As shown, a first value (e.g., "1") of the 1-bit indicator may indicate that there is a co-scheduled UE 120 with respect to DMRS ports 8 and 9. In this case, the UE 120 may use DMRS ports 0 and 1 to utilize FD-OCC 4 for channel estimation. Alternatively, a second value (e.g., "0") of the 1-bit indicator may indicate that there is no co-scheduled UE 120 with respect to DMRS ports 8 and 9. In this case, the UE 120 may use DMRS ports 0 and 1 to utilize FD-OCC 2 for channel estimation. Although some aspects are described in terms of a 1-bit indicator, it is contemplated that aspects described herein may be performed in conjunction with a multi-bit indicator, such as a 2-bit indicator, a 3-bit indicator, or a 4-bit indicator. For example, a multi-bit indicator may be used to convey multiple different possible configurations as described herein.

[0089] In some aspects, the target UE 120 may be configured for two-symbol DMRS and may receive a 1-bit indicator identifying whether there is a co-scheduled UE 120 for the set of DMRS ports assigned to the target UE 120. In a first example, as in Figure 5CIn the example and as shown by reference numeral 550, UE 120 may be configured with a 1-bit indicator to divide the DMRS port set into a first subset of the DMRS port set {0, 1, 4, 5} and a second subset of the DMRS port set {8, 9, 12, 13} in the CDM group. In this case, when the target UE 120 is scheduled using the DMRS ports within the first subset of the DMRS port set (e.g., by the value of the 1-bit indicator), the target UE 120 may determine that there are one or more co-scheduled UEs 120 within the second subset of the DMRS port set. In a second example, as shown by reference numeral 552, UE 120 may be configured with a 1-bit indicator to divide the DMRS port set by a TD-OCC code. In this case, the target UE 120 is scheduled using a DMRS port in a first subset of a DMRS port set {0,1,8,9} associated with a TD-OCC code [1,1] or a DMRS port in a second subset of a DMRS port set {4,5,12,13} associated with a TD-OCC code [1,-1]. In this second example, when the target UE 120 is scheduled using a DMRS port in a first subset of a DMRS port set (e.g., by a value of a 1-bit indicator), the target UE 120 may determine that there are co-scheduled UEs 120 in a second subset of the DMRS port set. In some aspects, the target UE 120 may receive configuration information identifying which type of partitioning will be mapped to a 1-bit indicator in signaling (e.g., DCI or MAC-CE). For example, according to the first example or according to the second example, the target UE 120 may indicate that the UE 120 will interpret the 1-bit indicator in the signaling (e.g., DCI or MAC-CE) RRC configuration information.

[0090] In some aspects, the target UE 120 may receive a multi-bit indicator, such as a 2-bit indicator that conveys co-scheduling information. For example, the target UE 120 may receive a 2-bit indicator that indicates the presence of co-scheduled UEs 120 and the number of co-scheduled UEs 120 that are present. Additionally or alternatively, the target UE 120 may receive a 2-bit indicator that indicates which DMRS ports one or more co-scheduled UEs 120 are associated with. For example, for single-symbol DMRS, the target UE 120 may be scheduled using a rank 2 PDSCH on DMRS ports 0 and 1, such as Figure 5D. The target UE 120 may receive a 2-bit indicator that maps to a set of different options for co-scheduling, such as "00" that is not mapped to a UE 120 co-scheduled on DMRS ports 8 and 9, "01" that is mapped to a co-scheduled UE 120 with rank 1 on DMRS ports 8 or 9, "10" that is mapped to a co-scheduled UE 120 with rank 2 on DMRS ports 8 and 9, and "11" that is mapped to a first co-scheduled UE 120 with rank 1 on DMRS port 8 and a second co-scheduled UE 120 with rank 1 on DMRS port 9. In this case, by using a 2-bit indicator to distinguish between, for example, a single UE 120 on DMRS ports 8 and 9 and a pair of UEs 120 on DMRS ports 8 and 9, it is possible to achieve improved channel estimation by improving the accuracy of interference power determination relative to treating these two cases as the same. Other mappings and / or other size bit indicators may be used to indicate additional information or map to additional co-scheduling configurations. For example, a 3-bit indicator may be used to indicate additional information or map to additional co-scheduling configurations.

[0091] In some aspects, the target UE 120 may receive a 1-bit indicator of the RB allocations of the co-scheduled UEs 120. For example, the UE 120 may receive a 1-bit indicator that maps to different RB assignments, such as a "1" indicating that the co-scheduled UE 120 is present in all of the assigned RBs of the target UE 120 and a "0" indicating that the co-scheduled UE 120 is present in only a subset of the assigned RBs of the target UE 120. In this case, the UE 120 may use blind detection to identify which RBs have the co-scheduled UE 120 and which RBs do not have the co-scheduled UE 120. In some aspects, the target UE 120 may receive multiple bit indicators. For example, the target UE 120 may receive a 2-bit indicator of the presence and number of co-scheduled UEs 120 and a 1-bit indicator of the RB allocations of the co-scheduled UEs 120. Other combinations of indicators and values ​​may be used.

[0092] As in Figure 5A 1 and further illustrated by reference numeral 520, UE 120 and network node 110 may perform one or more DMRS-related procedures. For example, UE 120 may receive DMRS, estimate a channel, and receive and decode a scheduled PDSCH based at least in part on estimating the channel. Additionally or alternatively, UE 120 may send a DMRS for network node 110 to estimate the channel, and may send a DMRS that network node 110 may receive and decode a scheduled PUSCH based at least in part on network node 110 estimating the channel.

[0093] As indicated above, FIG. 5A to FIG. 5D are provided as examples. Other examples can be found in the FIG. 5A to FIG. 5D The content described is different.

[0094] Figure 6 is a diagram illustrating an example process 600 performed, for example, by a UE in accordance with the present disclosure. Example process 600 is an example in which a UE (eg, UE 120) performs operations associated with a multi-user scheduling indication for a DMRS.

[0095] like Figure 6 As shown in , in some aspects, process 600 may include receiving signaling that schedules a shared channel and indicates a set of DMRS ports scheduled for a UE, the signaling including a field for conveying at least one of: an indicator of co-scheduled UEs for the set of DMRS ports, a number of co-scheduled UEs for the set of DMRS ports, or a resource block allocation for the co-scheduled UEs (block 610). For example, a UE (e.g., using Figure 8 The antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, controller / processor 280, communication manager 140 or receive component 802 depicted in the figure can receive signaling that schedules a shared channel and indicates a set of DMRS ports scheduled for a UE, the signaling including a field for conveying at least one of: an indicator of UEs co-scheduled for the DMRS port set, the number of UEs co-scheduled for the DMRS port set, or a resource block allocation for the co-scheduled UEs, as described above.

[0096] like Figure 6 As further shown in FIG. 6 , in some aspects, process 600 may include communicating a DMRS set based at least in part on signaling (block 620). Figure 8 The antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, communication manager 140, or receive component 802 or transmit component 804 depicted in the figure can communicate the DMRS set based at least in part on signaling, as described above.

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

[0098] In a first aspect, the signaling includes a bit indicator of the co-scheduled UEs.

[0099] In a second aspect, alone or in combination with the first aspect, transmitting the set of DMRS includes estimating a channel based at least in part on content of the field.

[0100] In a third aspect, alone or in combination with one or more of the first and second aspects, content of the field indicates an orthogonal cover code for the co-scheduled UEs, and communicating the DMRS set includes estimating a channel based at least in part on the orthogonal cover codes for the co-scheduled UEs.

[0101] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the field includes a first bit for indicating that the co-scheduled UE is within the resource block allocation of the UE.

[0102] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the field conveys information associated with partitioning DMRS port sets by port number or orthogonal cover code type.

[0103] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the field comprises one or more bit indicators mapped to indicate at least one of the number, rank, or port of co-scheduled UEs.

[0104] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the field is configured to indicate whether a resource block allocation for a co-scheduled UE overlaps with one or more assigned resource blocks of the UE.

[0105] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the bit indicator is a 1-bit indicator.

[0106] In a ninth aspect, alone or in combination with one or more of the first to ninth aspects, the signaling includes downlink control information.

[0107] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the signaling comprises MAC-CE.

[0108] although Figure 6 An example block diagram of process 600 is shown, but in some aspects, process 600 may include Figure 6 The blocks depicted in the process 600 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 600. Additionally or alternatively, two or more blocks in the blocks of the process 600 may be performed in parallel.

[0109] Figure 7is a diagram illustrating an example process 700, performed, for example, by a network node, in accordance with the present disclosure. The example process 700 is an example in which a network node (eg, network node 110) performs operations associated with a multi-user scheduling indication for a demodulation reference signal.

[0110] like Figure 7 As shown in , in some aspects, process 700 may include sending signaling that schedules a shared channel and indicates a set of DMRS ports scheduled for a target UE, the signaling including a field for conveying at least one of: an indicator of co-scheduled UEs for the set of DMRS ports, a number of co-scheduled UEs for the set of DMRS ports, or a resource block allocation for the co-scheduled UEs (block 710). For example, a network node (e.g., using Fig. 9 The controller / processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, communication manager 150, or transmit component 904 depicted in the figure can send signaling that schedules a shared channel and indicates a set of DMRS ports scheduled for a target UE, the signaling including a field for conveying at least one of: an indicator of UEs co-scheduled for the DMRS port set, the number of UEs co-scheduled for the DMRS port set, or a resource block allocation for the co-scheduled UEs, as described above.

[0111] like Figure 7 As further shown in FIG. 7 , in some aspects, process 700 may include communicating a DMRS set according to signaling (block 720). For example, a network node (e.g., using Fig. 9 The controller / processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, communication manager 150, or receive component 902 or transmit component 904 depicted in the figure can communicate the DMRS set according to signaling, as described above.

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

[0113] In a first aspect, the signaling includes a bit indicator of the co-scheduled UEs.

[0114] In a second aspect, alone or in combination with the first aspect, the channel estimation is based at least in part on content of the field.

[0115] In a third aspect, alone or in combination with one or more of the first and second aspects, the content of the field indicates an orthogonal cover code of the co-scheduled UEs, and the channel estimation is based at least in part on the orthogonal cover codes of the co-scheduled UEs.

[0116] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the field includes a first bit for indicating that the co-scheduled UE is within the resource block allocation of the target UE.

[0117] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the field conveys information associated with partitioning DMRS port sets by port number or orthogonal cover code type.

[0118] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the field comprises one or more bit indicators mapped to indicate at least one of the number, rank, or port of co-scheduled UEs.

[0119] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the field is configured to indicate whether a resource block allocation for a co-scheduled UE overlaps with one or more assigned resource blocks of a target UE.

[0120] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the bit indicator is a 1-bit indicator.

[0121] In a ninth aspect, alone or in combination with one or more of the first to ninth aspects, the signaling includes downlink control information.

[0122] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the signaling comprises MAC-CE.

[0123] although Figure 7 An example block diagram of process 700 is shown, but in some aspects, process 700 may include Figure 7 The blocks depicted in the process 700 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 700. Additionally or alternatively, two or more blocks in the blocks of the process 700 may be performed in parallel.

[0124] Figure 8800 is a diagram of an example apparatus 800 for wireless communication according to the present disclosure. Apparatus 800 may be a UE, or a UE may include apparatus 800. In some aspects, apparatus 800 includes a receiving component 802 and a transmitting component 804 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 800 may communicate with another apparatus 806 (such as a UE, a base station, or another wireless communication device) using receiving component 802 and transmitting component 804. As further shown, apparatus 800 may include a communication manager 140. Communication manager 140 may include a channel estimation component 808, among other things.

[0125] In some aspects, the apparatus 800 may be configured to perform the FIG. 5A to FIG. 5D Additionally or alternatively, the apparatus 800 may be configured to perform one or more processes described herein, such as Figure 6 The process 600. In some aspects, Figure 8 The apparatus 800 and / or one or more components shown in FIG. 8 may include a combination of Figure 2 Additionally or alternatively, Figure 8 One or more of the components shown in the figure may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as an instruction or code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0126] The receiving component 802 may receive communications from the apparatus 806, such as reference signals, control information, data communications, or a combination thereof. The receiving component 802 may provide the received communications to one or more other components of the apparatus 800. In some aspects, the receiving component 802 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the apparatus 800. In some aspects, the receiving component 802 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of a described UE.

[0127] The transmitting component 804 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 806. In some aspects, one or more other components of the device 800 may generate communications and may provide the generated communications to the transmitting component 804 for transmission to the device 806. In some aspects, the transmitting component 804 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 806. In some aspects, the transmitting component 804 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 804 can be co-located with the receive component 802 in a transceiver.

[0128] The receiving component 802 may receive signaling that schedules a shared channel and indicates a set of DMRS ports scheduled for a UE, the signaling including a field for conveying an indicator of a co-scheduled UE for the set of DMRS ports. The receiving component 802 or the sending component 804 may communicate the DMRS set based at least in part on the signaling. The channel estimation component 808 may estimate the channel based at least in part on the contents of the field.

[0129] Figure 8 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Figure 8 The components shown in the figure may include additional components, fewer components, different components, or components arranged in a different manner. Figure 8 Two or more components shown in the figure may be implemented in a single component, or Figure 8 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Figure 8 The assembly of (one or more) components shown in the figure may perform the operations described as being performed by Figure 8 Another set of components shown in the figure performs one or more functions.

[0130] Fig. 9900 is a diagram of an example apparatus 900 for wireless communication according to the present disclosure. Apparatus 900 may be a network node, or a network node may include apparatus 900. In some aspects, apparatus 900 includes a receiving component 902 and a transmitting component 904 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 900 may communicate with another apparatus 906 (such as a UE, a base station, or another wireless communication device) using receiving component 902 and transmitting component 904. As further shown, apparatus 900 may include a communication manager 150. Communication manager 150 may include a scheduling component 908, among other things.

[0131] In some aspects, the apparatus 900 may be configured to perform the FIG. 5A to FIG. 5D Additionally or alternatively, the apparatus 900 may be configured to perform one or more processes described herein, such as Figure 7 The process 700. In some aspects, Fig. 9 The apparatus 900 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 Additionally or alternatively, Fig. 9 One or more of the components shown in the figure may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as an instruction or code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0132] The receiving component 902 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the apparatus 906. The receiving component 902 may provide the received communications to one or more other components of the apparatus 900. In some aspects, the receiving component 902 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the apparatus 900. In some aspects, the receiving component 902 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described network nodes.

[0133] Transmit component 904 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 906. In some aspects, one or more other components of device 900 may generate communications and may provide the generated communications to transmit component 904 for transmission to device 906. In some aspects, transmit component 904 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 906. In some aspects, transmit component 904 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network nodes. In some aspects, the transmit component 904 can be co-located with the receive component 902 in a transceiver.

[0134] The sending component 904 can send signaling that schedules a shared channel and indicates a DMRS port set scheduled for a target UE, the signaling including a field for conveying an indicator of a UE co-scheduled for the DMRS port set. The receiving component 902 or the sending component 904 can communicate the DMRS set according to the signaling. The scheduling component 908 can schedule one or more users using the DMRS set.

[0135] Fig. 9 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig. 9 The components shown in the figure may include additional components, fewer components, different components, or components arranged in a different manner. Fig. 9 Two or more components shown in the figure may be implemented in a single component, or Fig. 9 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Fig. 9 The assembly of (one or more) components shown in the figure may perform the operations described as being performed by Fig. 9 Another set of components shown in the figure performs one or more functions.

[0136] The following provides an overview of some aspects of the disclosure:

[0137] Aspect 1: A method of wireless communication performed by a device of a user equipment (UE), comprising: receiving signaling that schedules a shared channel and indicates a set of demodulation reference signal (DMRS) ports scheduled for the UE, the signaling comprising a field for conveying at least one of: an indicator of co-scheduled UEs for the DMRS port set, the number of co-scheduled UEs for the DMRS port set, or resource block allocation for the co-scheduled UEs; and conveying the DMRS set based at least in part on the signaling.

[0138] Aspect 2: The method according to aspect 1, wherein the signaling includes a bit indicator of the co-scheduled UE.

[0139] Aspect 3: The method according to aspect 2, wherein the bit indicator is a 1-bit indicator.

[0140] Aspect 4: The method according to any one of aspects 1 to 3, wherein communicating the DMRS set includes: estimating a channel based at least in part on the content of the field.

[0141] Aspect 5: A method according to any one of Aspects 1 to 4, wherein the content of the field indicates an orthogonal cover code of the co-scheduled UE, and wherein communicating the DMRS set includes: estimating a channel based at least in part on the orthogonal cover code of the co-scheduled UE.

[0142] Aspect 6: The method according to any one of aspects 1 to 5, wherein the field comprises a first bit for indicating the co-scheduled UE within the resource block allocation of the UE.

[0143] Aspect 7: The method according to any one of aspects 1 to 6, wherein the field conveys information associated with partitioning the DMRS port set by port number or orthogonal cover code type.

[0144] Aspect 8: The method according to any one of aspects 1 to 7, wherein the field comprises one or more bit indicators mapped to indicate at least one of the following: the number, rank or port of the co-scheduled UEs.

[0145] Aspect 9: The method according to any one of aspects 1 to 8, wherein the field is configured to indicate whether the resource block allocation for the co-scheduled UE overlaps with one or more assigned resource blocks of the UE.

[0146] Aspect 10: A method according to any one of aspects 1 to 9, wherein the signaling includes downlink control information.

[0147] Aspect 11: The method according to any one of aspects 1 to 9, wherein the signaling comprises a medium access control (MAC) control element (CE).

[0148] Aspect 12: A method of wireless communication performed by a device of a network node, comprising: sending signaling that schedules a shared channel and indicates a set of demodulation reference signal (DMRS) ports scheduled for a target user equipment (UE), the signaling comprising a field for conveying at least one of the following: an indicator of a co-scheduled UE for the DMRS port set, the number of co-scheduled UEs for the DMRS port set, or a resource block allocation for the co-scheduled UE; and conveying the DMRS set according to the signaling.

[0149] Aspect 13: The method according to aspect 12, wherein the signaling includes a bit indicator of the co-scheduled UE.

[0150] Aspect 14: The method according to aspect 13, wherein the bit indicator is a 1-bit indicator.

[0151] Aspect 15: The method according to any one of aspects 12 to 14, wherein the channel estimation is based at least in part on the content of the field.

[0152] Aspect 16: A method according to any one of aspects 12 to 15, wherein the content of the field indicates an orthogonal cover code of the co-scheduled UE, and wherein channel estimation is based at least in part on the orthogonal cover code of the co-scheduled UE.

[0153] Aspect 17: The method according to any one of aspects 12 to 16, wherein the field comprises a first bit for indicating that the co-scheduled UE is within the resource block allocation of the target UE.

[0154] Aspect 18: The method according to any one of aspects 12 to 17, wherein the field conveys information associated with partitioning the DMRS port set by port number or orthogonal cover code type.

[0155] Aspect 19: The method according to any one of aspects 12 to 18, wherein the field comprises one or more bit indicators mapped to indicate at least one of: the number, rank or port of the co-scheduled UEs.

[0156] Aspect 20: The method according to any one of aspects 12 to 19, wherein the field is configured to indicate whether the resource block allocation for the co-scheduled UE overlaps with one or more assigned resource blocks of the target UE.

[0157] Aspect 21: A method according to any one of aspects 12 to 20, wherein the signaling includes downlink control information.

[0158] Aspect 22: The method according to any one of aspects 12 to 21, wherein the signaling comprises a medium access control (MAC) control element (CE).

[0159] Aspect 17: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 22.

[0160] Aspect 23: A device for wireless communication, comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 22.

[0161] Aspect 24: An apparatus for wireless communication, comprising: at least one component for performing the method according to one or more of aspects 1 to 22.

[0162] Aspect 25: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 22.

[0163] Aspect 26: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 22.

[0164] 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 foregoing disclosure or may be acquired from practice of the various aspects.

[0165] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to a specific software code herein to describe the operation and behavior of the system and / or method, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0166] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0167] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (it includes a single member). 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, and any combination with multiple identical elements (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).

[0168] Any element, action or instruction used herein should not be interpreted as critical or necessary unless clearly stated. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If you only want to refer to an item, the phrase "only one" or similar terms will be used. Moreover, as used herein, the term "having" etc. is intended to be an open term, which does not limit the elements they modify (for example, "having" A elements can also have B). In addition, the phrase "based on" is intended to mean "based at least in part on", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and may be used interchangeably with "and / or" unless explicitly stated otherwise (e.g., if used in conjunction with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, comprising: one or more memories; and one or more processors, the one or more processors coupled to the one or more memories, the one or more processors configured to: receiving signaling that schedules a shared channel and indicates a set of demodulation reference signal (DMRS) ports scheduled for the UE, the signaling including a field for conveying an indicator of a co-scheduled UE for the set of DMRS ports; and A DMRS set is communicated based at least in part on the signaling. 2 . The UE of claim 1 , wherein the field conveys information associated with a number of co-scheduled UEs for the DMRS port set or resource block allocations for the co-scheduled UEs.

3. The UE of claim 2, wherein the field conveys information indicating whether there are any co-scheduled UEs. The UE of claim 1 , wherein the signaling comprises a bit indicator of the co-scheduled UE. The UE according to claim 3 , wherein the bit indicator is a 1-bit indicator. The UE according to claim 3 , wherein the bit indicator is a multi-bit indicator.

7. The UE of claim 1 , wherein to communicate the DMRS set, the one or more processors are configured to: A channel is estimated based at least in part on the contents of the field.

8. The UE of claim 1 , wherein the content of the field indicates an orthogonal cover code of the co-scheduled UE, and wherein communicating the DMRS set comprises: A channel is estimated based at least in part on the orthogonal cover codes for the co-scheduled UEs.

9. The UE of claim 1, wherein the field comprises a first bit for indicating that the co-scheduled UE is within a resource block allocation of the UE.

10. The UE of claim 1, wherein the field conveys information associated with partitioning the DMRS port set by port number or orthogonal cover code type.

11. The UE of claim 1 , wherein the field comprises one or more bit indicators mapped to indicate at least one of: the number of co-scheduled UEs, rank, or port.

12. The UE of claim 1, wherein the field is configured to indicate whether the resource block allocation for the co-scheduled UE overlaps with one or more assigned resource blocks of the UE.

13. The UE of claim 1, wherein the signaling comprises downlink control information.

14. The UE of claim 1, wherein the signaling comprises a Medium Access Control (MAC) Control Element (CE).

15. A network node for wireless communication, comprising: one or more memories; and one or more processors, the one or more processors coupled to the one or more memories, the one or more processors configured to: sending signaling that schedules a shared channel and indicates a set of demodulation reference signal (DMRS) ports scheduled for a target user equipment (UE), the signaling including a field for conveying an indicator of a co-scheduled UE for the set of DMRS ports; and The DMRS set is communicated according to the signaling.

16. The network node of claim 15, wherein the field conveys information associated with a number of co-scheduled UEs for the DMRS port set or resource block allocations for the co-scheduled UEs.

17. The network node of claim 15, wherein the signaling comprises a bit indicator of the co-scheduled UE.

18. The network node of claim 17, wherein the bit indicator is a 1-bit indicator.

19. The network node of claim 17, wherein the bit indicator is a multi-bit indicator.

20. The network node of claim 15, wherein channel estimation is based at least in part on content of the field.

21. The network node of claim 15, wherein the content of the field indicates an orthogonal cover code for the co-scheduled UEs, and wherein channel estimation is based at least in part on the orthogonal cover codes for the co-scheduled UEs.

22. The network node of claim 15, wherein the field comprises a first bit for indicating that the co-scheduled UE is within a resource block allocation of the target UE.

23. The network node of claim 15, wherein the field conveys information associated with partitioning the DMRS port sets by port number or orthogonal cover code type.

24. The network node of claim 15, wherein the field comprises one or more bit indicators mapped to indicate at least one of: the number of co-scheduled UEs, rank, or port.

25. The network node of claim 15, wherein the field is configured to indicate whether the resource block allocation for the co-scheduled UE overlaps with one or more assigned resource blocks of the target UE.

26. The network node of claim 15, wherein the signaling comprises downlink control information.

27. The network node of claim 15, wherein the signaling comprises a medium access control (MAC) control element (CE).

28. A method of wireless communication performed by a device of a user equipment (UE), comprising: receiving signaling that schedules a shared channel and indicates a set of demodulation reference signal (DMRS) ports scheduled for the UE, the signaling including a field for conveying an indicator of a co-scheduled UE for the set of DMRS ports; and A DMRS set is communicated based at least in part on the signaling.

29. The method of claim 28, wherein the signaling comprises a bit indicator of the co-scheduled UE.

30. A method of wireless communication performed by an apparatus of a network node, comprising: sending signaling that schedules a shared channel and indicates a set of demodulation reference signal (DMRS) ports scheduled for a target user equipment (UE), the signaling including a field for conveying an indicator of a co-scheduled UE for the set of DMRS ports; and The DMRS set is communicated according to the signaling.

Images