Patent Description:
As demand for mobile broadband access continues to increase, there exists a need for further improvements in LTE and NR technologies. These improvements can apply to other multiple access technologies and the telecommunication standards that employ these technologies. <CIT> is directed to beam management and, in particular to beam indication scheme and provides beam recovery scheme in an advanced wireless communication system. Thereby, a UE is configured to monitor a first CORESET. The UE receives DCI A in a first CORESET and the DCI A schedules PDSCH B to the UE <NUM>. The UE can determine whether the scheduling is same-slot scheduling or cross-slot scheduling <NUM>. When the scheduling for PDSCH B is same-slot scheduling <NUM>, the UE can be requested to assume the spatial QCL configuration for PDSCH B and DMRS in PDSCH B is same to the spatial QCL configuration indicated by the TCI state configured for a first CORESET. When the scheduling for PDSCH B is cross-slot scheduling <NUM>, the UE can be requested to assume the spatial QCL configuration for PDSCH B and DMRS in PDSCH B is indicated by the TCI state signaled by N-bit TCI field in DCI A. <CIT> refers to beam management and more specifically to beam management of downlink data and control channel for <NUM> next radio. Thereby beam indication procedure for PDCCH is used, where QCL signaling is assumed to be the realization of beam indication signaling. Further, each CORESET configuration includes an index to a QCL reference. A network may know what CORESET to assign, but not know which QCL reference index to set (until it pulls in a beam group report from the UE. <CIT> is directed to network device that determines a plurality of pieces of quasi co-location information, where the plurality of pieces of quasi co-location information correspond to a plurality of antenna port sets of a first control resource set, and each piece of quasi co-location information in the plurality of pieces of quasi co-location information is used to indicate a quasi co-location characteristic of an antenna port set corresponding to each piece of quasi co-location information. Thereby, the plurality of pieces of quasi co-location information include two or more pieces of quasi co-location information.

The present invention is set out in the independent claims whereas preferred embodiments and further implementations are outlined in the dependent claims, description and figures.

So that the above-recited features of the present disclosure can be understood in detail, a more particular description is provided herein, with some aspects of the disclosure being illustrated in the appended drawings. However, the appended drawings illustrate only some aspects of this disclosure and are therefore not to be considered limiting of the scope of the disclosure.

These apparatuses and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, and/or the like (collectively referred to as "elements" or "features").

While some aspects may be described herein using terminology commonly associated with <NUM> and/or <NUM> wireless technologies, aspects of the present disclosure can be applied in other generation-based communication systems, such as <NUM> and later, including NR technologies.

While aspects and embodiments are described in this application by illustration to some examples, those skilled in the art will understand that additional implementations and use cases may come about in many different arrangements and scenarios. Innovations described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, packaging arrangements. For example, embodiments and/or uses may come about via integrated chip embodiments and/or other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, AI-enabled devices, and/or the like). While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described innovations may occur. Implementations may range a spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or OEM devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating described aspects and features may also necessarily include additional components and features for implementation and practice of claimed and described embodiments. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including one or more antennas, RF-chains, power amplifiers, modulators, buffers, processors, interleavers, adders/summers, and/or the like). It is intended that innovations described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc. of varying sizes, shapes, and constitution.

A UE may 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, a camera, a gaming device, a netbook, a smartbook, an ultrabook, medical device or equipment, biometric sensors/devices, wearable devices (smart watches, smart clothing, smart glasses, smart wrist bands, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicular component or sensor, smart meters/sensors, industrial manufacturing equipment, robotics, drones, implantable devices, augmented reality devices, a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium.

At base station <NUM>, a transmit processor <NUM> can carry out a number of functions associated with communications. For example, transmit processor <NUM> may receive data from a data source <NUM> for one or more UEs, select one or more modulation and coding schemes (MCS) for each UE based at least in part on channel quality indicators (CQIs) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS(s) selected for the UE, and provide data symbols for all UEs.

At UE <NUM>, antennas 252a through 252r may receive downlink signals from base station <NUM> and/or other base stations and may provide received signals to demodulators (DEMODs) 254a through 254r, respectively.

Controller/processor <NUM> of base station <NUM>, controller/processor <NUM> of UE <NUM>, and/or any other component(s) of <FIG> may perform one or more techniques associated with quasi-co-location (QCL) relationship and/or demodulation reference signal (DMRS) port identification, as described in more detail elsewhere herein. For example, controller/processor <NUM> of base station <NUM>, controller/processor <NUM> of UE <NUM>, and/or any other component(s) of <FIG> may perform or direct operations of, for example, process <NUM> of <FIG> and/or other processes as described herein. Memories <NUM> and <NUM> may store data and program codes for base station <NUM> and UE <NUM>, respectively.

In some aspects, UE <NUM> may include means for receiving, from a first transmit receive point (TRP) in a multi-TRP configuration, a downlink control information (DCI) communication, means for identifying one or more QCL) relationships associated with a control resource set (CORESET) or a search space set in which the DCI communication is received, wherein a QCL relationship, of the one or more QCL relationships, is associated with one or more physical downlink shared channel (PDSCH) layers that are transmitted from a second TRP in the multi-TRP configuration, and/or the like. In some aspects, such means may include one or more components of UE <NUM> described in connection with <FIG>, such as antenna <NUM>, DEMOD <NUM>, MOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, controller/processor <NUM>, and/or the like.

<FIG> shows an example frame structure <NUM> for FDD in a telecommunications system (e.g., NR). Each subframe may have a predetermined duration (e.g., <NUM>) and may include a set of slots (e.g., <NUM>m slots per subframe are shown in <FIG>, where m is a numerology used for a transmission, such as <NUM>, <NUM>,<NUM>, <NUM>, <NUM>, and/or the like). In some aspects, a scheduling unit for the FDD may frame-based, subframe-based, slot-based, symbol-based, and/or the like.

Each resource block may cover a set to of subcarriers (e.g., <NUM> subcarriers) in one slot and may include a number of resource elements.

An interlace structure may be used for each of the downlink and uplink for FDD in certain telecommunications systems (e.g., NR). For example, Q interlaces with indices of <NUM> through Q - <NUM> may be defined, where Q may be equal to <NUM>, <NUM>, <NUM>, <NUM>, or some other value. Each interlace may include slots that are spaced apart by Q frames. In particular, interlace q may include slots q, q + Q, q + 2Q, etc., where q ∈ {<NUM>,.

New Radio (NR) may refer to radios configured to operate according to a new air interface (e.g., other than Orthogonal Frequency Divisional Multiple Access (OFDMA)-based air interfaces) or fixed transport layer (e.g., other than Internet Protocol (IP)).

In a wireless network, a UE may be communicatively connected to a plurality of TRPs, referred to a multi-TRP configuration, and may transmit communications to, and/or receive communications from, the plurality of TRPs. In some cases, a TRP, of the plurality of TRPs, may transmit a DCI communication to the UE. The DCI communication may include one or more fields that specify one or more (or multi-panel) parameters for the multi-TRP configuration, such as a transmission configuration indication (TCI) field that indicates one or more TCI states (which may indicate one or more QCL relationships associated with the plurality of TRPs), a DMRS port field (which may indicate one or more DMRS ports associated with the plurality of TRPs), and/or the like.

In some cases, a TRP may be unable to transmit, and/or a UE may be unable to receive, a DCI communication that specifies the one or more parameters for a multi-TRP configuration. For example, the UE may be unable to receive a DCI communication of a particular format that is capable of specifying the one or more parameters, such as a format 1_0 DCI communication (which may also be referred to as a fallback DCI communication), a format 1_1 DCI communication in which a TCI-PresentInDCI field and/or a DMRS port field is not configured, and/or the like. In some cases, a UE may be unable to receive a DCI communication that specifies the one or more parameters for the multi-TRP configuration if the DCI format is monitored in a common search space set (CSS) in which DCI format 1_1 cannot be configured. In some cases, a UE may be unable to receive a DCI communication that specifies the one or more parameters for the multi-TRP configuration if the UE is configured to receive a limited quantity of DCI communication types, and format 1_1 DCI communications is not a DCI communication type that the UE is configured to receive.

As a result of the TRP being unable to transmit, and/or the UE being unable to receive, a DCI communication that specifies one or more parameters for the multi-TRP configuration, the UE may be unable to locate PDCCH communications that are transmitted by the TRP (and other TRPs in the multi-TRP configuration), the UE may be unable to locate PDSCH communications that are transmitted by the TRP (and the other TRPs in the multi-TRP configuration), the UE may be unable to differentiate between communications that are transmitted by the TRP and communications that are transmitted by another TRP in the multi-TRP configuration, and/or the like.

Some aspects described herein provide techniques and apparatuses for QCL relationship and/or DMRS port identification. In some aspects, a UE may receive, from a TRP in a multi-TRP configuration, a DCI communication. The UE may identify one or more QCL relationships and/or one or more DMRS ports associated with a control resource set (CORESET) and/or a search space sets in which the DCI communication is received. The one or more QCL relationships may include a first QCL relationship associated with the TRP, a second QCL relationship associated with another TRP, and/or the like. The one or more DMRS ports may include a first DMRS port associated with the first QCL relationship, a second DMRS port associated with the second QCL relationship, and/or the like.

In this way, the UE is permitted to be configured with one or more parameters for the multi-TRP configuration even if the DCI communication does not include the one or more parameters and/or is not capable of specifying the one or more parameters. This permits the UE to identify the one or more QCL relationships and receive, based at least in part on the one or more QCL relationships, one or more PDSCH layers that are transmitted by the TRP and/or the other TRP. Moreover, this permits the UE to identify the one or more DMRS ports and perform, based at least in part on the one or more DMRS ports, a channel estimation of the one or more PDSCH layers that are transmitted by the TRP and/or the other TRP.

<FIG> are diagrams illustrating an example <NUM> of QCL relationship and/or DMRS port identification, in accordance with various aspects of the present disclosure. As shown in <FIG>, example <NUM> may include a plurality of TRPs (e.g., TRP1, TRP2, and/or the like,) and a UE (e.g., UE <NUM>). In some aspects, each TRP, of the plurality of TRPs illustrated in <FIG>, may correspond to a respective BS (e.g., BS 110a, BS 110b, BS 110c, BS 110d, and/or the like). In some aspects, two or more TRPs, of the plurality of TRPs, may be correspond to the same BS. For example, a first TRP may correspond to a first antenna panel or antenna array of a BS and a second TRP may correspond to a second antenna panel or antenna array of the BS.

In some aspects, the plurality of TRPs, and UE <NUM>, may be included in a wireless network (e.g., wireless network <NUM> and/or the like). UE <NUM> may be communicatively connected with the plurality of TRPs in a multi-TRP configuration. UE <NUM> may receive one or more PDSCH layers from the plurality of TRPs in the multi-TRP configuration. For example, UE <NUM> may receive one or more PDSCH layers from TRP1, may receive one or more PDSCH layers from TRP2 (e.g., the same one or more PDSCH layers as received from TRP1, a different one or more PDSCH layers than the one or more PDSCH layers received from TRP1, and/or the like).

As shown in <FIG>, and by reference number <NUM>, UE <NUM> may receive one or more DCI communications. In some aspects, UE <NUM> may identify one or more parameters, for the multi-TRP configuration, based at least in part on receiving the one or more DCI communications. In some aspects, the one or more DCI communications may include a format 1_0 DCI communication and/or a format 1_1 DCI communication in which a TCI-PresentInDCI field and/or a DMRS port field is not configured.

In some aspects, a TRP, of the plurality of TRPs, may transmit a DCI communication to UE <NUM>. UE <NUM> may receive the DCI communication via a PDCCH transmitted from the TRP. In some aspects, UE <NUM> may receive the DCI communication in a particular CORESET and/or a particular search space set. UE <NUM> may receive the DCI communication by monitoring a plurality of CORESETS and/or search space sets, and identifying the DCI communication in the particular CORESET and/or the particular search space set.

The CORESET may comprise a resource configuration for a control portion of a downlink between the TRP and UE <NUM>. The resource configuration may include information identifying a bandwidth of the control portion and a time duration of the control portion. The information identifying the bandwidth may include information identifying one or more frequency carriers, one or more subcarriers, and/or the like, associated with the control portion. The information identifying the time duration may include information identifying a quantity of symbols, a quantity of slots, a quantity of subframes, and/or the like, associated with the control portion. In some aspects, the search space set may correspond to one or more candidate locations, in the time or frequency domain of the resource configuration for the control portion, at which the DCI communication may be located. The one or more candidate locations may be specified in one or more symbols, one or more slots, one or more subframes, one or more control channel elements, and/or the like.

As further shown in <FIG>, and by reference number <NUM>, UE <NUM> may identify the one or more parameters for the multi-TRP configuration, which may identify one or more QCL relationships, one or more DMRS ports, and/or the like. In some aspects, UE <NUM> may identify the one or more parameters for the multi-TRP configuration based at least in part on the CORESET and/or the search space set in which the DCI communication was received, based at least in part on information included in the DCI communication, and/or the like.

In some aspects, a QCL relationship may indicate one or more channel properties (e.g., Doppler spread, Doppler shift, timing offset-related average delay, delay spread, average gain, and/or the like) for a physical downlink channel (e.g., a PDCCH, one or more PDSCH layers, and/or the like). UE <NUM> may identify and receive a physical downlink channel based at least in part on the one or more channel properties associated with the physical downlink channel.

In some aspects a DMRS port (which may also be referred to as an antenna port) may indicate a resource configuration for one or more downlink slots in which a DMRS is transmitted. In this way, the UE <NUM> may use the resource configuration to identify one or more resource elements that carry the DMRS so that UE <NUM> may detect the DMRS and perform a channel estimation for a corresponding one or more PDSCH layers.

In some aspects, UE <NUM> may identify the one or more QCL relationships and/or DMRS ports based at least in part on determining that the DCI communication is for multi-TRP. In some aspects, UE <NUM> may determine that the DCI communication is for multi-TRP based at least in part on the CORESET and/or the search space set in which the DCI communication is received. For example, the CORESET and/or the search space set may be designated as a multi-TRP CORESET and/or a multi-TRP search space set. Accordingly, any DCI communications that are received in the CORESET and/or the search space set may be identified as being for multi-TRP. In some implementations, a CORESET may be associated with a plurality of search space sets, where a subset of the plurality of search space sets is for multi-TRP and another subset of the plurality of search space sets is for single-TRP. In this way, the CORESET may be flexibly used for multi-TRP and single-TRP.

In some aspects, UE <NUM> may determine that the DCI communication is for multi-TRP based at least in part on an indication in the DCI communication. In some aspects, the indication may include a value, a flag, and/or another type of information included in a field in the DCI communication, such as a multi-TRP field and/or the like. UE <NUM> may determine that the DCI communication is for multi-TRP based at least in part on the value, the flag, and/or the like, specified in the field indicating whether the DCI communication is for multi-TRP.

In some aspects, depending on the multi-TRP scheduling mode that is used in the multi-TRP configuration, UE <NUM> may identify respective QCL relationships and respective DMRS ports for the TRPs in the multi-TRP configuration. In some aspects, when multi-TRP Mode <NUM> (single-DCI based multi-TRP) is used in the multi-TRP configuration, a TRP (e.g., TRP1) may provide multi-TRP scheduling for a plurality of TRPs via the DCI communication. In this case, UE <NUM> may identify, based at least in part on the COREST and/or the search space set in which the DCI communication is received (e.g., from TRP1), a plurality of QCL relationships and/or a plurality of DMRS ports associated with a plurality of TRPs.

For example, where TRP1 provides multi-TRP scheduling for TRP1 and TRP2 via the DCI communication, UE <NUM> may identify, based at least in part on the CORESET and/or the search space set in which the DCI communication is received, a first QCL relationship that is associated with TRP1 (which may be the same QCL relationship that is associated with the PDCCH via which the DCI communication is received or a different QCL relationship) and a second QCL relationship that is associated with TRP2. UE <NUM> may receive one or more PDSCH layers, that are transmitted from TRP1, based at least in part on the one or more channel properties indicated by the first QCL relationship, and may receive one or more PDSCH layers (e.g., one or more PDSCH layers of the same PDSCH as the one or more PDSCH layers transmitted from TRP1, one or more PDSCH layers of a different PDSCH than the one or more PDSCH layers transmitted from TRP1, and/or the like), that are transmitted from TRP2, based at least in part on the one or more channel properties indicated by the second QCL relationship.

In addition, UE <NUM> may identify, based at least in part on the CORESET and/or the search space set in which the DCI communication is received, a first DMRS port that is associated with the first QCL relationship and a second DMRS port that is associated with the second QCL relationship. UE <NUM> may identify, based at least in part on the first DMRS port associated with the first QCL relationship, a DMRS associated with the one or more PDSCH layers that are transmitted from TRP1, and may perform a channel estimation of the one or more PDSCH layers based at least in part on the DMRS. Similarly, UE <NUM> may identify, based at least in part on the second DMRS port associated with the second QCL relationship, a DMRS associated with the one or more PDSCH layers that are transmitted from TRP2, and may perform a channel estimation of the one or more PDSCH layers based at least in part on the DMRS.

In some aspects, UE <NUM> may identify DMRS ports based at least in part on a default DMRS ports associated with the CORSET and/or the search space set. For example, UE <NUM> may identify a DMRS port for the DCI communication as the default DMRS port for the CORSET and/or the search space set based at least in part on the DCI communication being received in the CORSET and/or the search space set. Similarly, if UE <NUM> is deployed in a mode <NUM> multi-TRP deployment (multi-DCI based multi-TRP, e.g., where each TRP transmits a respective DCI communication), UE <NUM> may identify a DMRS port for a DCI communication from TRP1 as the default DMRS port for the CORSET and/or the search space set based at least in part on the DCI communication being received in the CORSET and/or the search space set, and may identify another DMRS port for another DCI communication received from TRP2 as the default DMRS port for another CORSET and/or another search space set based at least in part on the other DCI communication being received in the other CORSET and/or the other search space set.

In some aspects, UE <NUM> may identify DMRS ports based at least in part on explicit indications of the default DMRS ports. For example, UE <NUM> may receive a DCI communication that explicitly indicates the default DMRS port (e.g., DMRS port <NUM>) and the second DMRS port (e.g., DMRS port <NUM>).

In some aspects, where TRP1 provides multi-TRP Mode <NUM> scheduling for a plurality of other TRPs via the DCI communication (e.g., TRP2 and another TRP), UE <NUM> may identify, based at least in part on the CORESET and/or the search space set in which the DCI communication is received, a first QCL relationship that is associated with TRP2 and a second QCL relationship that is associated with the other TRP. Accordingly, UE <NUM> may receive one or more PDSCH layers, that are transmitted from TRP2, based at least in part on the one or more channel properties indicated by the first QCL relationship, and may receive one or more PDSCH layers (e.g., one or more PDSCH layers of the same PDSCH as the one or more PDSCH layers transmitted from TRP2, one or more PDSCH layers of a different PDSCH than the one or more PDSCH layers transmitted from TRP2, and/or the like), that are transmitted from the other TRP, based at least in part on the one or more channel properties indicated by the second QCL relationship.

In addition, UE <NUM> may identify, based at least in part on the CORESET and/or the search space set in which the DCI communication is received, a first DMRS port that is associated with the first QCL relationship and a second DMRS port that is associated with the second QCL relationship. UE <NUM> may identify, based at least in part on the first DMRS port associated with the first QCL relationship, a DMRS associated with the one or more PDSCH layers that are transmitted from TRP2, and may perform a channel estimation of the one or more PDSCH layers based at least in part on the DMRS. Similarly, UE <NUM> may identify, based at least in part on the second DMRS port associated with the second QCL relationship, a DMRS associated with the one or more PDSCH layers that are transmitted from the other TRP, and may perform a channel estimation of the one or more PDSCH layers based at least in part on the DMRS.

In some aspects, respective DCI communications, of a plurality of DCI communications, may provide scheduling for respective TRPs in the multi-TRP configuration (e.g., which may correspond to multi-TRP Mode <NUM>). In some aspects, the plurality of DCI communications may cross-schedule TRPs in the multi-TRP configuration (e.g., a first DCI communication, transmitted from TRP1, may provide multi-TRP scheduling for TRP2, and a second DCI communication, transmitted from TRP2, may provide multi-TRP scheduling for TRP1). In this case, UE <NUM> may identify, based at least in part on a CORESET and/or a search space set in which the first DCI communication is received from TRP1, a first QCL relationship that is associated with TRP2, and may identify, based at least in part on a CORESET and/or a search space set in which the second DCI communication is received from TRP2, a second QCL relationship that is associated with another TRP (e.g., TRP1). Accordingly, UE <NUM> may receive one or more PDSCH layers, that are transmitted from TRP1, based at least in part on the one or more channel properties indicated by the second QCL relationship, and may receive one or more PDSCH layers (e.g., one or more PDSCH layers of the same PDSCH as the one or more PDSCH layers transmitted from TRP1, one or more PDSCH layers of a different PDSCH than the one or more PDSCH layers transmitted from TRP1, and/or the like), that are transmitted from TRP2, based at least in part on the one or more channel properties indicated by the first QCL relationship.

In addition, UE <NUM> may identify respective DMRS ports that are associated with the first QCL relationship and the second QCL relationship. For example, UE <NUM> may identify, based at least in part on the CORESET and/or the search space set in which the first DCI communication is received from TRP1, a first DMRS port that is associated with the first QCL relationship. UE <NUM> may identify, based at least in part on the CORESET and/or the search space set in which the second DCI communication is received from TRP2, a second DMRS port that is associated with the second QCL relationship. UE <NUM> may identify, based at least in part on the first DMRS port associated with the first QCL relationship, a DMRS associated with the one or more PDSCH layers that are transmitted from TRP2, and may perform a channel estimation of the one or more PDSCH layers based at least in part on the DMRS. Similarly, UE <NUM> may identify, based at least in part on the second DMRS port associated with the second QCL relationship, a DMRS associated with the one or more PDSCH layers that are transmitted from TRP1, and may perform a channel estimation of the one or more PDSCH layers based at least in part on the DMRS.

In some aspects, the one or more QCL relationships and/or the one or more DMRS ports that are associated with a CORESET and/or a search space set may be properties of the CORESET and/or the search space set. In some aspects, the one or more QCL relationships and/or the one or more DMRS ports that are associated with a CORESET and/or a search space set may be fixed or static for the CORESET and/or the search space set. In some aspects, the one or more QCL relationships and/or the one or more DMRS ports that are associated with a CORESET and/or a search space set may be configurable for the CORESET.

In some aspects, the one or more DMRS ports that are associated with a CORESET and/or search space set may include a DMRS port that is fixed and/or static for the CORESET and/or the search space set, and may include a DMRS port that is configurable for the CORESET and/or the search space set. In some aspects, the one or more QCL relationships that are associated with a CORESET and/or search space set may be associated with respective DMRS ports such that the respective DMRS ports are associated with different code division multiplexing (CDM) groups.

In some aspects, UE <NUM> may identify the one or more QCL relationships and/or the one or more DMRS ports that are associated with a CORESET and/or a search space set by performing a lookup (e.g., in a look-up table, in a database, and/or in another type of data structure) to identify the one or more QCL relationships and/or one or more DMRS ports. In some aspects, UE <NUM> may be pre-configured with the association between the CORESET and/or the search space set and the one or more QCL relationships and/or the one or more DMRS ports.

As shown in <FIG>, and by reference number <NUM>, UE <NUM> may receive one or more PDSCH layers based at least in part on the one or more QCL relationships that are associated with respective CORESETS and/or search space sets in which the one or more DCI communications were received. For example, UE <NUM> may receive one or more PDSCH layers from TRP1 based at least in part on a QCL relationship associated with the one or more PDSCH layers, may receive one or more PDSCH layers from TRP2 based at least in part on a QCL relationship associated with the one or more PDSCH layers, and/or the like. To receive one or more PDSCH layers from a particular TRP, UE <NUM> may decode and/or interpret the one or more PDSCH layers based at least in part on the one or more channel properties associated with the QCL relationship that is associated with the one or more PDSCH layers.

In some aspects, UE <NUM> may determine which QCL relationship is associated with one or more PDSCH layers that are transmitted from a particular TRP. In some aspects, the one or more QCL relationships associated with a CORESET and/or a search space set may be configured such that a first QCL relationship, of the one or more QCL relationships, is associated with a TRP that transmitted the DCI communication. In this case, if TRP <NUM> transmitted the DCI communication, UE <NUM> may determine that the first QCL relationship is associated with TRP1, and may receive the one or more PDSCH layers, transmitted from TRP1, based at least in part on the first QCL relationship. Accordingly, UE <NUM> may infer that a second QCL relationship, of the one or more QCL relationships, is associated with TRP2, and may accordingly receive the one or more PDSCH layers, transmitted from TRP2, based at least in part on the second QCL relationship.

In some aspects, UE <NUM> may determine which QCL relationship is associated with one or more PDSCH layers that are transmitted from a particular TRP based at least in part on an explicit indication in the one or more DCI communications. For example, a DCI communication may be configured with an explicit indication (e.g., a value, a flag, and/or another type of indication), in a TRP field, that indicates the TRP to which a QCL relationship, associated with the CORESET and/or search space set on which the DCI communication is received, is associated. In this case, if TRP <NUM> transmits the DCI communication, and the DCI communication indicates TRP2 in the TRP field, UE <NUM> may determine that the QCL relationship, associated with the CORESET and/or search space set, is associated with TRP2. Accordingly, UE <NUM> may receive one or more PDSCH layers, transmitted from TRP2, based at least in part on the QCL relationship.

In some aspects, UE <NUM> may determine which QCL relationship is associated with one or more PDSCH layers that are transmitted from a particular TRP based at least in part on determining an implicit indication in the one or more DCI communications. In some aspects, the implicit indication may include any field, in the one or more DCI communications, that specifies information that may implicitly identify the particular TRP. For example, UE <NUM> may determine that a hybrid automatic repeat request (HARQ) process identifier, specified in a HARQ process identifier field included in a DCI communication, is associated with the particular TRP, and accordingly may determine that the QCL relationship, associated with the CORESET and/or search space set on which the DCI communication is received, is associated with the particular TRP.

As shown in <FIG>, and by reference number <NUM>, UE <NUM> may perform one or more respective channel estimations, for one or more PDSCH layers, based at least in part on the one or more DMRS ports that are associated with respective CORESETS and/or search space sets in which the one or more DCI communications were received. For example, UE <NUM> may identify, based at least in part on a resource configuration specified by a DMRS port of the one or more DMRS ports, a reference signal (e.g., a DMRS, a phase tracking reference signal (PTRS), and/or the like) that is transmitted by a particular TRP associated with the DMRS port, may decode the one or more reference signals, and may perform one or more measurements, for a PDSCH layer associated with the DMRS port, based at least in part on the decoded reference signal (e.g., a signal quality measurement, a signal strength measurement, and/or the like).

In some aspects, UE <NUM> may perform a channel estimation for each respective DMRS port that is associated with the one or more QCL relationships that are associated with respective CORESETS and/or search space sets in which the one or more DCI communications were received. For example, UE <NUM> may identify a first QCL relationship of the one or more QCL relationships, may identify a DMRS port associated with the first QCL relationship, may identify a first reference signal (e.g., based at least in part on the DMRS port) associated with a first PDSCH layer, of one or more PDSCH layers that are associated with the first QCL relationship, and may perform a channel estimation of the first PDSCH layer. UE <NUM> may repeat the above steps for each DMRS port that is associated with a QCL relationship of the one or more QCL relationships that are associated with respective CORESETS and/or search space sets in which the one or more DCI communications were received.

In some aspects, UE <NUM> may determine which DMRS port is associated with a particular TRP. In some aspects, the one or more DMRS ports associated with a CORESET and/or a search space set may be configured such that a first DMRS port, of the one or more DMRS ports, is associated with a TRP that transmitted the DCI communication. In this case, if TRP1 transmitted the DCI communication, UE <NUM> may determine that the first DMRS port is associated with TRP1. Accordingly, UE <NUM> may infer that a second DMRS port, of the one or more DMRS ports, is associated with TRP2.

In some aspects, UE <NUM> may determine which DMRS port is associated with a particular TRP based at least in part on an explicit indication in the one or more DCI communications. For example, a DCI communication may be configured with an explicit indication (e.g., a value, a flag, and/or another type of indication), in a TRP field, that indicates the TRP to which a DMRS port, associated with the CORESET and/or search space set on which the DCI communication is received, is associated. In this case, if TRP1 transmits the DCI communication, and the DCI communication indicates TRP2 in the TRP field, UE <NUM> may determine that the DMRS port, associated with the CORESET and/or search space set, is associated with TRP2.

In some aspects, UE <NUM> may determine which DMRS port is associated with a particular TRP based at least in part on determining an implicit indication in the one or more DCI communications. In some aspects, the implicit indication may include any field, in the one or more DCI communications, that specifies information that may implicitly identify the particular TRP. For example, UE <NUM> may determine that a hybrid automatic repeat request (HARQ) process identifier, specified in a HARQ process identifier field included in a DCI communication, is associated with the particular TRP, and accordingly may determine that the DMRS ports, associated with the CORESET and/or search space set on which the DCI communication is received, is associated with the particular TRP.

In this way, UE <NUM> is permitted to be configured with one or more parameters for the multi-TRP configuration even if the one or more DCI communications received from TRP1 and/or TRP2 do not include the one or more parameters and/or are not capable of specifying the one or more parameters. This permits UE <NUM> to identify one or more QCL relationships and receive, based at least in part on the one or more QCL relationships, one or more PDSCH layers that are transmitted by TRP1, TRP2, and/or other TRPs. Moreover, this permits UE <NUM> to identify one or more DMRS ports and perform, based at least in part on the one or more DMRS ports, a channel estimation of the one or more PDSCH layers that are transmitted by TRP1, TRP2, and/or other TRPs.

For example, while <FIG> are described above in the context of multi-TRP, the examples illustrated in <FIG> may similarly be applied to multi-panel, which may refer to different PDSCH layers being transmitted from respective antenna panels. In this case, UE <NUM> may determine that a DCI communication, that is received in a CORESET and/or a search space set, is for multi-panel, and accordingly may identify one or more QCL relationships and/or one or more DMRS ports, that are associated with respective antenna panels, based at least in part on the CORESET and/or the search space set.

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by a UE, in accordance with various aspects of the present disclosure. Example process <NUM> is an example where a UE (e.g., UE <NUM>) performs QCL relationship and/or DMRS port identification.

As shown in <FIG>, in some aspects, process <NUM> may include receiving, from a first transmit receive point in a multi-TRP configuration, a DCI communication (block <NUM>). For example, the UE (e.g., using receive processor <NUM>, controller/processor, <NUM>, memory <NUM>, and/or the like) may receive, from a first transmit receive point in a multi-TRP configuration, a DCI communication, as described above.

As further shown in <FIG>, in some aspects, process <NUM> may include identifying one or more QCL relationships associated with a CORESET or a search space set in which the DCI communication is received, wherein a QCL relationship, of the one or more QCL relationships, is associated with one or more PDSCH layers that are transmitted from a second TRP in the multi-TRP configuration (block <NUM>). For example, the UE (e.g., using controller/processor, <NUM>, memory <NUM>, and/or the like) may identifying one or more QCL relationships associated with a CORESET or a search space set in which the DCI communication is received, as described above. In some aspects, a QCL relationship, of the one or more QCL relationships, is associated with one or more physical downlink shared channel (PDSCH) layers that are transmitted from a second TRP in the multi-TRP configuration.

In a first aspect, the DCI communication comprises one of a format 1_0 DCI communication or a format 1_1 DCI communication in which a TCI-PresentInDCI field is not configured. In a second aspect, alone or in combination with the first aspect, another QCL relationship, of the one or more QCL relationships, is associated with one or more PDSCH layers that are transmitted from the first TRP. In a third aspect, alone or in combination with one or more of the first or second aspects, the other QCL relationship is used for a PDCCH on which the DCI communication is received. In a fourth aspect, alone or in combination with one or more of the first through third aspects, process <NUM> includes determining that the DCI communication is for at least one of multi-TRP or multi-panel, and identifying the one or more QCL relationships based at least in part on determining that the DCI communication is for at least one of multi-TRP or multi-panel.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, determining that the DCI communication is for at least one of multi-TRP or multi-panel comprises determining, based at least in part on the CORESET in which the DCI communication is received, that the DCI communication is for at least one of multi-TRP or multi-panel. In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, determining that the DCI communication is for at least one of multi-TRP or multi-panel comprises determining, based at least in part on the search space set in which the DCI communication is received, that the DCI communication is for at least one of multi-TRP or multi-panel.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, determining that the DCI communication is for at least one of multi-TRP or multi-panel comprises determining, based at least in part on information included in the DCI communication, that the DCI communication is for at least one of multi-TRP or multi-panel. In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, another QCL relationship, of the one or more QCL relationships, is associated with one or more PDSCH layers that are transmitted from a third TRP.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the QCL relationship is a first QCL relationship, a second QCL relationship, of the one or more QCL relationships, is associated with one or more PDSCH layers that are transmitted from the first TRP, and a third QCL relationship, of the one or more QCL relationships, is associated with a PDCCH that is transmitted from the first TRP.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the DCI communication includes an indication that the QCL relationship is associated with the second TRP. In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the indication that the QCL relationship is associated with the second TRP comprises an explicit indication in a TRP field included in the DCI communication. In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the indication that the QCL relationship is associated with the second TRP comprises an implicit indication included in the DCI communication. In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the implicit indication comprises an indication of a HARQ process identifier included in a HARQ process identifier field included in the DCI communication.

In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, another QCL relationship, of the one or more QCL relationships, is associated with one or more PDSCH layers that are transmitted from the first TRP, and process <NUM> includes identifying a first DMRS port associated with the QCL relationship and a second DMRS port associated with the other QCL relationship, performing, based at least in part on the first DMRS port, a channel estimation of a layer that is transmitted from the second TRP, and performing, based at least in part on the second DMRS port, a channel estimation of a layer that is transmitted from the first TRP.

In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, the first DMRS port and the second DMRS port are associated with different CDM groups. In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, at least one of the first DMRS port or the second DMRS port is configurable. In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, the first DMRS port and the second DMRS port are associated with the CORESET or the search space set. In an eighteenth aspect, alone or in combination with one or more of the first through seventeenth aspects, process <NUM> includes identifying a DMRS port associated with the QCL relationship and performing, based at least in part on the DMRS port, a channel estimation of a layer that is transmitted from the second TRP.

In a nineteenth aspect, alone or in combination with one or more of the first through eighteenth aspects, identifying the DMRS port associated with the QCL relationship comprises identifying, based at least in part on the CORESET or the search space set, the DMRS port associated with the QCL relationship. In a twentieth aspect, alone or in combination with one or more of the first through nineteenth aspects, identifying the DMRS port associated with the QCL relationship comprises identifying, based at least in part on determining that the DCI communication is for at least one of multi-TRP or multi-panel, the DMRS port associated with the QCL relationship.

In a twenty-first aspect, alone or in combination with one or more of the first through twentieth aspects, determining that the DCI communication is for at least one of multi-TRP or multi-panel comprises determining, based at least in part on information included in the DCI communication, that the DCI communication is for at least one of multi-TRP or multi-panel. In a twenty-second aspect, alone or in combination with one or more of the first through twenty-first aspects, identifying the DMRS port associated with the QCL relationship comprises identifying the DMRS port, from a plurality of DMRS ports, based at least in part on determining that the DMRS port is associated with the second TRP.

In a twenty-third aspect, alone or in combination with one or more of the first through twenty-second aspects, determining that the DMRS port is associated with the second TRP comprises determining that the DMRS port is associated with the second TRP based at least in part on an indication, included in the DCI communication, that the DMRS port is associated with the second TRP. In a twenty-fourth aspect, alone or in combination with one or more of the first through twenty-third aspects, the indication that the DMRS port is associated with the second TRP comprises an explicit indication in a TRP field included in the DCI communication.

In a twenty-fifth aspect, alone or in combination with one or more of the first through twenty-fourth aspects, the indication that the DMRS port is associated with the second TRP comprises an implicit indication included in the DCI communication. In a twenty-sixth aspect, alone or in combination with one or more of the first through twenty-fifth aspects, the implicit indication comprises an indication of a HARQ process identifier included in a HARQ process identifier field included in the DCI communication.

In a twenty-seventh aspect, alone or in combination with one or more of the first through twenty-sixth aspects, the DCI communication is a format 1_0 DCI communication and process <NUM> further comprises identifying, based at least in part on receiving the DCI communication in the CORESET or the search space set, a DMRS port for a scheduled PDSCH associated with the CORESET or the search space set, wherein the DMRS port is a default DMRS port configured for the scheduled PDSCH associated with the CORSET or the search space set.

In a twenty-eighth aspect, alone or in combination with one or more of the first through twenty-seventh aspects, process <NUM> further comprises receiving another DCI communication from the second TRP in another CORESET or another search space set and identifying, based at least in part on receiving the other DCI communication in the other DMRS or the other search space set, a second DMRS port for the scheduled PDSCH associated with the CORESET or the search space set, wherein the other DMRS port is a default DMRS port for the scheduled PDSCH configured for the other CORSET or the other search space set. In a twenty-ninth aspect, alone or in combination with one or more of the first through twenty-eighth aspects, the DCI communication is a first DCI communication, and process <NUM> further comprises receiving a second DCI communication from the second TRP in another CORESET or another search space set; receiving a third DCI communication; identifying, in the third DCI communication, an explicit indication that a first DMRS port for a PDSCH scheduled by the first DCI communication is a first default DMRS port; and identifying, in the third DCI communication, an explicit indication that a second DMRS port for another PDSCH scheduled by the second DCI communication is a second default DMRS port.

Claim 1:
A method (<NUM>) of wireless communication performed by a user equipment (UE), comprising:
receiving (<NUM>), from a first transmit receive point, TRP, in a multi-TRP configuration, a downlink control information, DCI, communication;
identifying (<NUM>) one or more quasi-co-location, QCL, relationships associated with a control resource set, CORESET, or a search space set in which the DCI communication is received,
wherein a QCL relationship, of the one or more QCL relationships, is associated with one or more physical downlink shared channel, PDSCH, layers that are transmitted from a second TRP in the multi-TRP configuration, wherein the DCI communication is a format 1_0 DCI communication; and
wherein the method further comprises:
identifying, based at least in part on receiving the DCI communication in the CORESET or the search space, a demodulation reference signal, DMRS, port for a scheduled PDSCH associated with the CORESET or the search space set,
wherein the DMRS port is a default DMRS port to use for the scheduled PDSCH, and is configured for the CORESET or the search space set.